Communication method, communication apparatus, and communication system

Abstract

A communication method, a communication apparatus, and a communication system. On the basis of the method, a session management network element sends a first rule to a terminal on the basis of capability information of the terminal, and the terminal maps, on the basis of the first rule, different data flows corresponding to the same five-tuple information to corresponding QoS flows. Since the capability information of the terminal is referenced during the determination of the first rule, the terminal can correctly use the first rule, thereby ensuring communication quality. The session management network element sends a second rule to a first user-plane network element on the basis of capability information of the first user-plane network element, and the first user-plane network element maps, on the basis of the second rule, different data flows corresponding to the same five-tuple information to corresponding QoS flows. Since the capability information of the first user-plane network element is referenced during the determination of the second rule, the first user-plane network element can correctly use the second rule, thereby ensuring communication quality.

Description

A communication method, communication device and communication system

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411026508.9, filed on July 28, 2024, entitled "A Communication Method, Communication Device and Communication System", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method, communication device and communication system. Background Technology

[0004] With the development of communication technology, multimedia services, represented by extended reality (XR) services, have experienced exponential growth. XR services combine and allow interaction between physical objects in the real world and digital objects in the virtual world through auxiliary devices, achieving a perfect fusion of the real and virtual worlds. XR services include virtual reality (VR) services, augmented reality (AR) services, and mixed reality (MR) services.

[0005] Multimedia service data streams are categorized into various types, such as video streams, audio streams, and haptic streams. Multiple data streams within the same multimedia service may share the same five-tuple information (i.e., source Internet Protocol (IP) address, source port number, destination IP address, destination port number, and protocol type).

[0006] How to transmit multiple data streams with the same 5-tuple information for the same multimedia service remains to be solved. Summary of the Invention

[0007] This application provides a communication method, communication device, and communication system to transmit multiple data streams with the same 5-tuple information for the same multimedia service, thereby ensuring communication quality.

[0008] In a first aspect, embodiments of this application provide a communication method that can be applied to the network side, such as a session management network element, a module (e.g., a circuit, chip, or chip system) within the session management network element, or a logical node, logical module, or software capable of implementing all or part of the functions of the session management network element. The method includes: acquiring terminal capability information, the capability information indicating whether the terminal has multi-stream processing capability or not; and sending a first rule to the terminal based on the terminal capability information, the first rule including a first packet filter, a second packet filter, information about a first quality of service (QoS) stream corresponding to the first packet filter, and information about a second QoS stream corresponding to the second packet filter. The first packet filter includes information about a first data stream, the second packet filter includes information about a second data stream, the information about the first data stream includes first 5-tuple information, the information about the second data stream includes second 5-tuple information, the second 5-tuple information is the same as the first 5-tuple information, the first packet filter is used to identify the first data stream, and the second packet filter is used to identify the second data stream.

[0009] Based on the above scheme, the session management network element sends a first rule to the terminal based on the terminal's capability information. The terminal then maps different data streams with the same five-tuple information to the corresponding QoS streams according to the first rule. Since the terminal's capability information is referenced when determining the first rule—indicating whether the terminal has multi-stream processing capabilities—the terminal can correctly use the first rule, thereby ensuring communication quality.

[0010] In one possible implementation, a policy and charging control (PCC) rule is received from a policy control network element. The PCC rule is used to indicate information about the first data flow and a first QoS parameter requirement for the first QoS flow, and to indicate information about the second data flow and a second QoS parameter requirement for the second QoS flow. The first QoS parameter requirement is different from the second QoS parameter requirement. The first rule is determined according to the PCC rule.

[0011] Based on the above scheme, a first rule is determined based on the different QoS parameter requirements of different data streams indicated by the PCC rule. This first rule is used to map different data streams to the corresponding QoS streams, which helps to achieve high-quality transmission of data streams.

[0012] In one possible implementation, when the terminal has multi-stream processing capabilities, the QoS flow identifier (QFI) in the information of the first QoS flow is different from the QoS flow identifier in the information of the second QoS flow.

[0013] Based on the above scheme, since the QoS stream identifier contained in the information of the first QoS stream in the first rule is different from the QoS stream identifier contained in the information of the second QoS stream in the first rule, the terminal can map different data streams with the same five-tuple information to different QoS streams according to the first rule, thereby meeting the differentiated transmission requirements of different data streams and ensuring communication quality.

[0014] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0015] Based on the above scheme, when it is identified that the information of the first data stream and the information of the second data stream contain the same five-tuple information, the first data stream and the second data stream are further distinguished by identifying the first information in the information of the first data stream and the second information in the information of the second data stream, and it is determined that the first data stream and the second data stream are different data streams corresponding to the same five-tuple information, thereby achieving correct identification and distinction of different data streams corresponding to the same five-tuple information.

[0016] In one possible implementation, the first information includes at least one of a first payload type (PT), a first synchronization source (SSRC) identifier, or a first mark header fields. The first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first mark header fields indicate the header information of the first data stream. The second information includes at least one of a second payload type, a second synchronization source identifier, or a second mark header fields. The second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second mark header fields indicate the header information of the second data stream. Both the first and second data streams are transmitted via a real-time transport protocol (RTP), a secure real-time transport protocol (SRTP), a real-time transport control protocol (RTCP), or a secure real-time transport control protocol (SRTCP).

[0017] Based on the above scheme, adding payload type, synchronization source identifier, or tag header field information to the data stream information helps to accurately identify different data streams with the same five-tuple information based on the data stream information, and accurately determine whether multiple data streams with the same payload type, synchronization source identifier, or tag header field information need to be mapped to the same QoS stream, and multiple data streams with different payload types, synchronization source identifiers, or tag header field information need to be mapped to different QoS streams, so as to meet the differentiated transmission requirements of different data streams.

[0018] In one possible implementation, the first information includes first metadata, and the second information includes second metadata, wherein the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via a media (MoQ) protocol based on Quick UDP internet connections (QUIC).

[0019] Based on the above scheme, adding metadata to the information of the data stream helps to accurately identify different data streams with the same five-tuple information, and accurately determine whether multiple data streams with the same metadata need to be mapped to the same QoS stream, or multiple data streams with different metadata need to be mapped to different QoS streams, so as to meet the differentiated transmission needs of different data streams.

[0020] In one possible implementation, when the terminal does not have multi-stream processing capabilities, the QoS stream identifier in the information of the first QoS stream is the same as the QoS stream identifier in the information of the second QoS stream.

[0021] Based on the above scheme, when the terminal lacks multi-stream processing capabilities, the session management network element sends a first rule to the terminal. According to the first rule, the terminal can map different data streams with the same five-tuple information to the same QoS stream for transmission. That is, even if the multiple different data streams have different QoS requirements, since the terminal lacks multi-stream processing capabilities, in order to ensure the normal transmission of data streams, the session management network element instructs the terminal to map different data streams with the same five-tuple information to the same QoS stream for transmission through the first rule, thereby ensuring the normal transmission of data streams and improving communication quality.

[0022] In one possible implementation, obtaining the terminal's capability information includes: receiving indication information from the terminal, the indication information being used to indicate the capability information.

[0023] Based on the above scheme, the terminal provides the terminal's capability information to the session management network element, so that the session management network element can accurately determine whether the terminal has multi-stream processing capabilities.

[0024] Secondly, embodiments of this application provide a communication method that can be applied to the network side, such as a session management network element on the network side, a module (e.g., a circuit, chip, or chip system) in the session management network element, or a logical node, logical module, or software that can implement all or part of the functions of the session management network element. The method includes: acquiring capability information of a first user plane network element, the capability information indicating whether the first user plane network element has multi-stream processing capability or not; sending a second rule to the first user plane network element based on the capability information, the second rule including a first packet detection rule (PDR) and a first QoS enforcement rule (QER) corresponding to a first data stream, and a second packet detection rule and a second QoS enforcement rule corresponding to a second data stream; the first packet detection rule including information of the first data stream, the information of the first data stream including first 5-tuple information, the first packet detection rule being used to identify the first data stream, the first QoS enforcement rule being used to indicate that the header of the data packets of the first data stream carries the QoS stream identifier of the first QoS stream corresponding to the first data stream; the second packet detection rule including information of the second data stream, the information of the second data stream including second 5-tuple information, the second 5-tuple information being the same as the first 5-tuple information, the second packet detection rule being used to identify the second data stream, the second QoS enforcement rule being used to indicate that the header of the data packets of the second data stream carries the QoS stream identifier of the second QoS stream corresponding to the second data stream.

[0025] Based on the above scheme, the session management network element sends a second rule to the first user plane network element based on the capability information of the first user plane network element. The first user plane network element then maps different data streams with the same five-tuple information to the corresponding QoS streams according to the second rule. Since the capability information of the first user plane network element is referenced when determining the second rule—which indicates whether the first user plane network element has multi-stream processing capabilities—the first user plane network element can correctly use the second rule, thereby ensuring communication quality.

[0026] In one possible implementation, a PCC rule is received from a policy control network element. The PCC rule is used to indicate information of the first data flow and a first QoS parameter requirement of the first QoS flow, and to indicate information of the second data flow and a first QoS parameter requirement of the second QoS flow, wherein the first QoS parameter requirement is different from the second QoS parameter requirement; and the second rule is determined according to the PCC rule.

[0027] Based on the above scheme, a second rule is determined based on the different QoS parameter requirements of different data streams indicated by the PCC rule. This second rule is used to map different data streams to the corresponding QoS streams, which helps to achieve high-quality transmission of data streams.

[0028] In one possible implementation, when the first user plane network element has multi-stream processing capabilities, the QoS stream identifier of the first QoS stream is different from the QoS stream identifier of the second QoS stream.

[0029] Based on the above scheme, since the QoS flow identifier contained in the information of the first QoS flow in the second rule is different from the QoS flow identifier contained in the information of the second QoS flow in the second rule, the first user plane network element can map different data flows with the same five-tuple information to different QoS flows according to the second rule, thereby meeting the differentiated transmission requirements of different data flows and ensuring communication quality.

[0030] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0031] Based on the above scheme, when it is identified that the information of the first data stream and the information of the second data stream contain the same five-tuple information, the first data stream and the second data stream are further distinguished by identifying the first information in the information of the first data stream and the second information in the information of the second data stream, and it is determined that the first data stream and the second data stream are different data streams corresponding to the same five-tuple information, thereby achieving correct identification and distinction of different data streams corresponding to the same five-tuple information.

[0032] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0033] Based on the above scheme, adding payload type, synchronization source identifier, or tag header field information to the data stream information helps to accurately identify different data streams with the same five-tuple information based on the data stream information, and accurately determine whether multiple data streams with the same payload type, synchronization source identifier, or tag header field information need to be mapped to the same QoS stream, and multiple data streams with different payload types, synchronization source identifiers, or tag header field information need to be mapped to different QoS streams, so as to meet the differentiated transmission requirements of different data streams.

[0034] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0035] Based on the above scheme, adding metadata to the information of the data stream helps to accurately identify different data streams with the same five-tuple information, and accurately determine whether multiple data streams with the same metadata need to be mapped to the same QoS stream, or multiple data streams with different metadata need to be mapped to different QoS streams, so as to meet the differentiated transmission needs of different data streams.

[0036] In one possible implementation, when the first user plane network element does not have multi-stream processing capabilities, the QoS stream identifier in the information of the first QoS stream is the same as the QoS stream identifier in the information of the second QoS stream.

[0037] Based on the above scheme, when the first user plane network element does not have multi-stream processing capabilities, the session management network element sends a second rule to the first user plane network element. According to the second rule, the first user plane network element can map different data streams with the same five-tuple information to the same QoS stream for transmission. That is, even if the multiple different data streams have different QoS requirements, since the first user plane network element does not have multi-stream processing capabilities, in order to ensure the normal transmission of data streams, the session management network element instructs the first user plane network element to map different data streams with the same five-tuple information to the same QoS stream for transmission through the second rule, thereby ensuring the normal transmission of data streams and improving communication quality.

[0038] In one possible implementation, if the first user plane network element does not have multi-stream processing capability, a second user plane network element with multi-stream processing capability is selected; the second rule is sent to the second user plane network element, wherein the QoS flow identifier in the information of the first QoS flow is different from the QoS flow identifier in the information of the second QoS flow.

[0039] Based on the above scheme, when the first user plane network element does not have multi-stream processing capability, a second user plane network element with multi-stream processing capability is selected, and a second rule is sent to the second user plane network element. Thus, the second user plane network element can map different data streams with the same five-tuple information to different QoS streams according to the second rule, thereby meeting the differentiated transmission requirements of different data streams and ensuring communication quality.

[0040] In one possible implementation, first configuration information is sent to the first user plane network element, which instructs the first user plane network element to update the tunnel information from the first user plane network element to the access network device to the tunnel information from the first user plane network element to the second user plane network element; second configuration information is sent to the second user plane network element, which instructs the second user plane network element to add tunnel information from the second user plane network element to the first user plane network element, and to add tunnel information from the second user plane network element to the access network device; and third configuration information is sent to the access network device, which instructs the access network device to update the tunnel information from the access network device to the first user plane network element to the tunnel information from the access network device to the second user plane network element.

[0041] Based on the above scheme, updating the corresponding tunnel information after inserting the second user plane network element helps to achieve correct data flow transmission.

[0042] In one possible implementation, first configuration information is sent to the first user plane network element, the first configuration information being used to instruct the first user plane network element to add information about a tunnel between the first user plane network element and the second user plane network element; second configuration information is sent to the second user plane network element, the second configuration information being used to instruct the second user plane network element to add information about a tunnel between the second user plane network element and the first user plane network element, and to add information about a tunnel between the second user plane network element and the access network device; and third configuration information is sent to the access network device, the third configuration information being used to instruct the access network device to add information about a tunnel between the access network device and the second user plane network element.

[0043] Based on the above scheme, updating the corresponding tunnel information after inserting the second user plane network element helps to achieve correct data flow transmission.

[0044] In one possible implementation, obtaining the capability information of the first user plane network element includes: receiving indication information from the first user plane network element, the indication information being used to indicate the capability information.

[0045] Based on the above scheme, the first user plane network element provides the session management network element with the capability information of the first user plane network element, so that the session management network element can accurately determine whether the first user plane network element has multi-stream processing capability.

[0046] Thirdly, embodiments of this application provide a communication method that can be applied to the network side, such as a policy control network element, a module (e.g., circuit, chip, or chip system) within the policy control network element, or a logical node, logical module, or software capable of implementing all or part of the functions of the policy control network element. The method includes: acquiring terminal capability information, the capability information indicating whether the terminal has multi-stream processing capability or not; and sending a PCC rule to a session management network element based on the terminal capability information, the PCC rule indicating information about a first data stream, information about a second data stream, information about a first QoS stream corresponding to the first data stream, and information about a second QoS stream corresponding to the second data stream. The information about the first data stream includes a first quintuple, the information about the second data stream includes a second quintuple, the second quintuple being the same as the first quintuple, the information about the first QoS stream including a first QoS parameter requirement and / or a QoS stream identifier for the first QoS stream, and the information about the second QoS stream including a second QoS parameter requirement and / or a QoS stream identifier for the second QoS stream.

[0047] Based on the above scheme, the policy control network element sends PCC rules to the session management network element based on the terminal's capability information. The session management network element then determines a first rule based on the PCC rules and sends it to the terminal. The terminal, according to the first rule, maps different data streams with the same five-tuple information to the corresponding QoS streams. Since the terminal's capability information is referenced when determining the PCC rules—indicating whether the terminal has multi-stream processing capabilities—the first rule determined by the session management network element is also related to the terminal's capability information. This ensures that the terminal can correctly use the first rule, thereby guaranteeing communication quality.

[0048] In one possible implementation, when the terminal has multi-stream processing capabilities, the first QoS parameter requirement is different from the second QoS parameter requirement, and the QoS stream identifier of the first QoS stream is different from the QoS stream identifier of the second QoS stream.

[0049] Based on the above scheme, since the first QoS parameter requirements and the second QoS parameter requirements in the PCC rule are different, and the QoS flow identifier of the first QoS flow in the PCC rule is different from that of the second QoS flow, when the session management network element generates the first rule according to the PCC rule, the first rule can be used to map different data flows with the same five-tuple information to different QoS flows, thereby meeting the differentiated transmission requirements of different data flows and ensuring communication quality.

[0050] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0051] Based on the above scheme, when it is identified that the information of the first data stream and the information of the second data stream contain the same five-tuple information, the first data stream and the second data stream are further distinguished by identifying the first information in the information of the first data stream and the second information in the information of the second data stream, and it is determined that the first data stream and the second data stream are different data streams corresponding to the same five-tuple information, thereby achieving correct identification and distinction of different data streams corresponding to the same five-tuple information.

[0052] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0053] Based on the above scheme, adding payload type, synchronization source identifier, or tag header field information to the data stream information helps to identify different data streams with the same five-tuple information based on the data stream information, and accurately determine whether multiple data streams with the same payload type, synchronization source identifier, or tag header field information need to be mapped to the same QoS stream, and multiple data streams with different payload types, synchronization source identifiers, or tag header field information need to be mapped to different QoS streams, so as to meet the differentiated transmission requirements of different data streams.

[0054] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0055] Based on the above scheme, adding metadata to the information of the data stream helps to accurately identify different data streams with the same five-tuple information, and accurately determine whether multiple data streams with the same metadata need to be mapped to the same QoS stream, or multiple data streams with different metadata need to be mapped to different QoS streams, so as to meet the differentiated transmission needs of different data streams.

[0056] In one possible implementation, when the terminal does not have multi-stream processing capabilities, the first QoS parameter requirement is the same as the second QoS parameter requirement, and the QoS stream identifier of the first QoS stream is the same as the QoS stream identifier of the second QoS stream.

[0057] Based on the above scheme, when the terminal does not have multi-stream processing capabilities, the first QoS parameter requirement in the PCC rule is the same as the second QoS parameter requirement, and the QoS stream identifier of the first QoS stream is the same as the QoS stream identifier of the second QoS stream. Therefore, the first rule determined by the session management network element according to the PCC rule can be used to map different data streams with the same five-tuple information to the same QoS stream for transmission, so as to improve communication quality.

[0058] In one possible implementation, the system receives flow description information of the first data stream, transmission requirements of the first data stream, flow description information of the second data stream, and transmission requirements of the second data stream from an application function network element; wherein the flow description information of the first data stream includes the first quintuple information, and the flow description information of the second data stream includes the second quintuple information; the transmission requirements of the first data stream and the transmission requirements of the second data stream are different; and the PCC rule is determined based on the terminal's capability information, the flow description information of the first data stream, the transmission requirements of the first data stream, the flow description information of the second data stream, and the transmission requirements of the second data stream.

[0059] In one possible implementation, an indication message is received from the terminal or the session management network element, the indication message being used to indicate the capability information.

[0060] Based on the above scheme, the terminal or session management network element provides the policy control network element with the terminal's capability information, so that the policy control network element can accurately determine whether the terminal has multi-stream processing capabilities.

[0061] Fourthly, embodiments of this application provide a communication method that can be applied to the network side, such as a policy control network element, a module (e.g., circuit, chip, or chip system) within the policy control network element, or a logical node, logical module, or software capable of implementing all or part of the functions of the policy control network element. The method includes: obtaining capability information of a first user plane network element, the capability information indicating whether the first user plane network element has multi-stream processing capability or not; and sending a PCC rule to a session management network element based on the capability information of the first user plane network element, the PCC rule indicating information about a first data stream, information about a second data stream, information about a first QoS stream corresponding to the first data stream, and information about a second QoS stream corresponding to the second data stream. The information about the first data stream includes first quintuple information, the information about the second data stream includes second quintuple information, the second quintuple information is the same as the first quintuple information, the information about the first QoS stream includes first QoS parameter requirements and / or a QoS stream identifier for the first QoS stream, and the information about the second QoS stream includes second QoS parameter requirements and / or a QoS stream identifier for the second QoS stream.

[0062] Based on the above scheme, the policy control network element sends PCC rules to the session management network element based on the capability information of the first user plane network element. The session management network element can then determine a second rule based on the PCC rules and send it to the first user plane network element. The first user plane network element, according to the second rule, maps different data streams with the same five-tuple information to the corresponding QoS streams. Since the PCC rules are determined with reference to the capability information of the first user plane network element, which indicates whether the first user plane network element has multi-stream processing capabilities, the second rule determined by the session management network element is also related to the capability information of the first user plane network element. Therefore, the first user plane network element can correctly use the second rule, thereby ensuring communication quality.

[0063] In one possible implementation, when the first user plane network element has multi-stream processing capabilities, the first QoS parameter requirements are different from the second QoS parameter requirements, and the QoS stream identifier of the first QoS stream is different from the QoS stream identifier of the second QoS stream.

[0064] Based on the above scheme, since the first QoS parameter requirements and the second QoS parameter requirements in the PCC rule are different, and the QoS flow identifier of the first QoS flow in the PCC rule is different from that of the second QoS flow, when the session management network element generates the second rule according to the PCC rule, the second rule can be used to map different data flows with the same five-tuple information to different QoS flows, thereby meeting the differentiated transmission requirements of different data flows and ensuring communication quality.

[0065] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0066] Based on the above scheme, when it is identified that the information of the first data stream and the information of the second data stream contain the same five-tuple information, the first data stream and the second data stream are further distinguished by identifying the first information in the information of the first data stream and the second information in the information of the second data stream, and it is determined that the first data stream and the second data stream are different data streams corresponding to the same five-tuple information, thereby achieving correct identification and distinction of different data streams corresponding to the same five-tuple information.

[0067] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0068] Based on the above scheme, adding payload type, synchronization source identifier, or tag header field information to the data stream information helps to accurately identify different data streams with the same five-tuple information based on the data stream information, and accurately determine whether multiple data streams with the same payload type, synchronization source identifier, or tag header field information need to be mapped to the same QoS stream, and multiple data streams with different payload types, synchronization source identifiers, or tag header field information need to be mapped to different QoS streams, so as to meet the differentiated transmission requirements of different data streams.

[0069] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0070] Based on the above scheme, adding metadata to the information of the data stream helps to accurately identify different data streams with the same five-tuple information, and accurately determine whether multiple data streams with the same metadata need to be mapped to the same QoS stream, or multiple data streams with different metadata need to be mapped to different QoS streams, so as to meet the differentiated transmission needs of different data streams.

[0071] In one possible implementation, when the first user plane network element does not have multi-stream processing capabilities, the first QoS parameter requirements are the same as the second QoS parameter requirements, and the QoS stream identifier of the first QoS stream is the same as the QoS stream identifier of the second QoS stream.

[0072] Based on the above scheme, when the first user plane network element does not have multi-stream processing capability, the first QoS parameter requirement in the PCC rule is the same as the second QoS parameter requirement, and the QoS stream identifier of the first QoS stream is the same as the QoS stream identifier of the second QoS stream. Therefore, the second rule determined by the session management network element according to the PCC rule can be used to map different data streams with the same five-tuple information to the same QoS stream for transmission, so as to improve communication quality.

[0073] In one possible implementation, the system receives flow description information of the first data stream, transmission requirements of the first data stream, flow description information of the second data stream, and transmission requirements of the second data stream from an application function network element; wherein the flow description information of the first data stream includes the first 5-tuple information, and the flow description information of the second data stream includes the second 5-tuple information; the transmission requirements of the first data stream and the transmission requirements of the second data stream are different; and the PCC rule is determined based on the capability information of the first user plane network element, the flow description information of the first data stream, the transmission requirements of the first data stream, the flow description information of the second data stream, and the transmission requirements of the second data stream.

[0074] In one possible implementation, an indication message is received from the first user plane network element or the session management network element, the indication message being used to indicate the capability information.

[0075] Based on the above scheme, the first user plane network element or the session management network element provides the policy control network element with the capability information of the first user plane network element, so that the policy control network element can accurately determine whether the first user plane network element has multi-stream processing capability.

[0076] Fifthly, embodiments of this application provide a communication method that can be applied to the terminal side, such as a terminal or a communication module in the terminal, or a circuit or chip in the terminal that is responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core). The method includes: sending indication information to a session management network element, the indication information being used to indicate the capability information of a terminal, the capability information being used to indicate that the terminal has multi-stream processing capability, or to indicate that the terminal does not have multi-stream processing capability; receiving a first rule from the session management network element, the first rule being determined based on the capability information of the terminal, the first rule including a first packet filter, a second packet filter, information of a first QoS stream corresponding to the first packet filter, and information of a second QoS stream corresponding to the second packet filter, the first packet filter including information of a first data stream, the second packet filter including information of a second data stream, the information of the first data stream including first 5-tuple information, the information of the second data stream including second 5-tuple information, the second 5-tuple information being the same as the first 5-tuple information, the first packet filter being used to identify the first data stream, and the second packet filter being used to identify the second data stream.

[0077] Based on the above scheme, the session management network element sends a first rule to the terminal based on the terminal's capability information. The terminal then maps different data streams with the same five-tuple information to the corresponding QoS streams according to the first rule. Since the terminal's capability information is referenced when determining the first rule—indicating whether the terminal has multi-stream processing capabilities—the terminal can correctly use the first rule, thereby ensuring communication quality.

[0078] In one possible implementation, when the terminal has multi-stream processing capabilities, the QoS stream identifier in the information of the first QoS stream is different from the QoS stream identifier in the information of the second QoS stream.

[0079] Based on the above scheme, since the QoS stream identifier contained in the information of the first QoS stream in the first rule is different from the QoS stream identifier contained in the information of the second QoS stream in the first rule, the terminal can map different data streams with the same five-tuple information to different QoS streams according to the first rule, thereby meeting the differentiated transmission requirements of different data streams and ensuring communication quality.

[0080] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0081] Based on the above scheme, when it is identified that the information of the first data stream and the information of the second data stream contain the same five-tuple information, the first data stream and the second data stream are further distinguished by identifying the first information in the information of the first data stream and the second information in the information of the second data stream, and it is determined that the first data stream and the second data stream are different data streams corresponding to the same five-tuple information, thereby achieving correct identification and distinction of different data streams corresponding to the same five-tuple information.

[0082] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0083] Based on the above scheme, adding payload type, synchronization source identifier, or tag header field information to the data stream information helps to accurately identify different data streams with the same five-tuple information based on the data stream information, and accurately determine whether multiple data streams with the same payload type, synchronization source identifier, or tag header field information need to be mapped to the same QoS stream, and multiple data streams with different payload types, synchronization source identifiers, or tag header field information need to be mapped to different QoS streams, so as to meet the differentiated transmission requirements of different data streams.

[0084] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0085] Based on the above scheme, adding metadata to the information of the data stream helps to accurately identify different data streams with the same five-tuple information, and accurately determine whether multiple data streams with the same metadata need to be mapped to the same QoS stream, or multiple data streams with different metadata need to be mapped to different QoS streams, so as to meet the differentiated transmission needs of different data streams.

[0086] In one possible implementation, when the terminal does not have multi-stream processing capabilities, the QoS stream identifier in the information of the first QoS stream is the same as the QoS stream identifier in the information of the second QoS stream.

[0087] Based on the above scheme, when the terminal lacks multi-stream processing capabilities, the session management network element sends a first rule to the terminal. According to the first rule, the terminal can map different data streams with the same five-tuple information to the same QoS stream for transmission. That is, even if the multiple different data streams have different QoS requirements, since the terminal lacks multi-stream processing capabilities, in order to ensure the normal transmission of data streams, the session management network element instructs the terminal to map different data streams with the same five-tuple information to the same QoS stream for transmission through the first rule, thereby ensuring the normal transmission of data streams and improving communication quality.

[0088] Sixthly, embodiments of this application provide a communication method that can be applied to the network side, such as a first user plane network element on the network side, a module (e.g., circuit, chip, or chip system) in the first user plane network element, or a logical node, logical module, or software that can implement all or part of the first user plane network element. The method includes: sending indication information to a session management network element, the indication information being used to indicate capability information of a first user plane network element, the capability information being used to indicate that the first user plane network element has multi-stream processing capability, or to indicate that the first user plane network element does not have multi-stream processing capability; receiving a second rule from the session management network element, the second rule being determined based on the capability information of the first user plane network element, the second rule including a first packet detection rule and a first QoS execution rule corresponding to a first data stream, and including a second packet detection rule and a second QoS execution rule corresponding to a second data stream; the first packet detection rule including information of the first data stream, the information of the first data stream including first 5-tuple information, the first packet detection rule being used to identify the first data stream, the first QoS execution rule being used to indicate that the packet header of the data packets of the first data stream carries a QoS stream identifier of the first QoS stream corresponding to the first data stream; the second packet detection rule including information of the second data stream, the information of the second data stream including second 5-tuple information, the second 5-tuple information being the same as the first 5-tuple information, the second packet detection rule being used to identify the second data stream, the second QoS execution rule being used to indicate that the packet header of the data packets of the second data stream carries a QoS stream identifier of the second QoS stream corresponding to the second data stream.

[0089] Based on the above scheme, the session management network element sends a second rule to the first user plane network element based on the capability information of the first user plane network element. The first user plane network element then maps different data streams with the same five-tuple information to the corresponding QoS streams according to the second rule. Since the capability information of the first user plane network element is referenced when determining the second rule—which indicates whether the first user plane network element has multi-stream processing capabilities—the first user plane network element can correctly use the second rule, thereby ensuring communication quality.

[0090] In one possible implementation, when the first user plane network element has multi-stream processing capabilities, the QoS stream identifier of the first QoS stream is different from the QoS stream identifier of the second QoS stream.

[0091] Based on the above scheme, since the QoS flow identifier contained in the information of the first QoS flow in the second rule is different from the QoS flow identifier contained in the information of the second QoS flow in the second rule, the first user plane network element can map different data flows with the same five-tuple information to different QoS flows according to the second rule, thereby meeting the differentiated transmission requirements of different data flows and ensuring communication quality.

[0092] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0093] Based on the above scheme, when it is identified that the information of the first data stream and the information of the second data stream contain the same five-tuple information, the first data stream and the second data stream are further distinguished by identifying the first information in the information of the first data stream and the second information in the information of the second data stream, and it is determined that the first data stream and the second data stream are different data streams corresponding to the same five-tuple information, thereby achieving correct identification and distinction of different data streams corresponding to the same five-tuple information.

[0094] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0095] Based on the above scheme, adding payload type, synchronization source identifier, or tag header field information to the data stream information helps to accurately identify different data streams with the same five-tuple information based on the data stream information, and accurately determine whether multiple data streams with the same payload type, synchronization source identifier, or tag header field information need to be mapped to the same QoS stream, and multiple data streams with different payload types, synchronization source identifiers, or tag header field information need to be mapped to different QoS streams, so as to meet the differentiated transmission requirements of different data streams.

[0096] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0097] Based on the above scheme, adding metadata to the information of the data stream helps to accurately identify different data streams with the same five-tuple information, and accurately determine whether multiple data streams with the same metadata need to be mapped to the same QoS stream, or multiple data streams with different metadata need to be mapped to different QoS streams, so as to meet the differentiated transmission needs of different data streams.

[0098] In one possible implementation, when the first user plane network element does not have multi-stream processing capabilities, the QoS stream identifier in the information of the first QoS stream is the same as the QoS stream identifier in the information of the second QoS stream.

[0099] Based on the above scheme, when the first user plane network element does not have multi-stream processing capabilities, the session management network element sends a second rule to the first user plane network element. According to the second rule, the first user plane network element can map different data streams with the same five-tuple information to the same QoS stream for transmission. That is, even if the multiple different data streams have different QoS requirements, since the first user plane network element does not have multi-stream processing capabilities, in order to ensure the normal transmission of data streams, the session management network element instructs the first user plane network element to map different data streams with the same five-tuple information to the same QoS stream for transmission through the second rule, thereby ensuring the normal transmission of data streams and improving communication quality.

[0100] Seventhly, embodiments of this application provide a communication method that can be applied to the terminal side, such as a terminal or a communication module in the terminal, or a circuit or chip in the terminal that is responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core). The method includes: receiving a first rule from a session management network element, the first rule including a first packet filter, a second packet filter, information of a first QoS flow corresponding to the first packet filter, and information of a second QoS flow corresponding to the second packet filter; the first packet filter including information of a first data flow, the second packet filter including information of a second data flow, the information of the first data flow including first 5-tuple information, the information of the second data flow including second 5-tuple information, the second 5-tuple information being the same as the first 5-tuple information, the first packet filter being used to identify the first data flow, the second packet filter being used to identify the second data flow, and the QoS flow identifier in the information of the first QoS flow being different from the QoS flow identifier in the information of the second QoS flow; upon receiving the first rule, sending indication information to the session management network element, the indication information being used to indicate that the terminal has multi-stream processing capability, or to indicate that the terminal does not have multi-stream processing capability.

[0101] Based on the above scheme, after receiving the first rule, if the terminal has multi-stream processing capabilities, it will map different data streams with the same five-tuple information to different QoS streams for transmission, thereby meeting the differentiated transmission requirements of different data streams. If the terminal does not have multi-stream processing capabilities, the first rule will not be used. Furthermore, the terminal also sends an indication message to the session management network element indicating whether it has multi-stream processing capabilities. This allows the session management network element to accurately determine whether the terminal has multi-stream processing capabilities, and then, based on the indication message, determine whether it is necessary to notify other network elements on the network side to perform further QoS updates for different data streams with the same five-tuple information.

[0102] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0103] Based on the above scheme, when it is identified that the information of the first data stream and the information of the second data stream contain the same five-tuple information, the first data stream and the second data stream are further distinguished by identifying the first information in the information of the first data stream and the second information in the information of the second data stream, and it is determined that the first data stream and the second data stream are different data streams corresponding to the same five-tuple information, thereby achieving correct identification and distinction of different data streams corresponding to the same five-tuple information.

[0104] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0105] Based on the above scheme, adding payload type, synchronization source identifier, or tag header field information to the data stream information helps to accurately identify different data streams with the same five-tuple information based on the data stream information, and accurately determine whether multiple data streams with the same payload type, synchronization source identifier, or tag header field information need to be mapped to the same QoS stream, and multiple data streams with different payload types, synchronization source identifiers, or tag header field information need to be mapped to different QoS streams, so as to meet the differentiated transmission requirements of different data streams.

[0106] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0107] Based on the above scheme, adding metadata to the information of the data stream helps to accurately identify different data streams with the same five-tuple information, and accurately determine whether multiple data streams with the same metadata need to be mapped to the same QoS stream, or multiple data streams with different metadata need to be mapped to different QoS streams, so as to meet the differentiated transmission needs of different data streams.

[0108] Eighthly, embodiments of this application provide a communication method that can be applied to the network side, such as application function network elements, modules (e.g., circuits, chips, or chip systems) within application function network elements, or logical nodes, logical modules, or software capable of implementing all or part of the application function network elements. The method includes: sending a QoS update request, the QoS update request including flow description information of a first data stream, transmission requirements of the first data stream, flow description information of a second data stream, and transmission requirements of the second data stream; wherein the flow description information of the first data stream includes first 5-tuple information, the flow description information of the second data stream includes second 5-tuple information, the second 5-tuple information is the same as the first 5-tuple information, and the transmission requirements of the first data stream are different from the transmission requirements of the second data stream; receiving a notification message, the notification message indicating that the QoS information corresponding to the first data stream and the QoS information corresponding to the second data stream failed to update, the notification message including a reason value, the reason value indicating that the update failure is due to the terminal not having multi-stream processing capability and / or the user plane network element not having multi-stream processing capability; and determining different 5-tuple information for the first data stream and the second data stream.

[0109] Based on the above scheme, when the application function network element determines that the terminal does not have multi-stream processing capability and / or the user plane network element does not have multi-stream processing capability, it can determine different five-tuple information for the first data stream and the second data stream. This can enable different uplink or downlink data streams with different five-tuple information to be mapped to different QoS streams for transmission, so as to meet the differentiated transmission requirements of different data streams.

[0110] In one possible implementation, the stream description information of the first data stream further includes first information, and the stream description information of the second data stream further includes second information. The first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0111] Based on the above scheme, when it is identified that the same five-tuple information is found in the flow description information of the first data stream and the flow description information of the second data stream, the first data stream and the second data stream are further distinguished by identifying the first information in the flow description information of the first data stream and the second information in the flow description information of the second data stream, and it is determined that the first data stream and the second data stream are different data streams corresponding to the same five-tuple information, thereby achieving correct identification and distinction of different data streams corresponding to the same five-tuple information.

[0112] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0113] Based on the above scheme, adding payload type, synchronization source identifier, or tag header field information to the flow description information of the data stream helps to accurately identify different data streams with the same five-tuple information based on the data stream information, and accurately determine whether multiple data streams with the same payload type, synchronization source identifier, or tag header field information need to be mapped to the same QoS stream, and multiple data streams with different payload types, synchronization source identifiers, or tag header field information need to be mapped to different QoS streams, so as to meet the differentiated transmission requirements of different data streams.

[0114] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0115] Based on the above scheme, adding metadata to the information of the data stream helps to accurately identify different data streams with the same five-tuple information, and accurately determine whether multiple data streams with the same metadata need to be mapped to the same QoS stream, or multiple data streams with different metadata need to be mapped to different QoS streams, so as to meet the differentiated transmission needs of different data streams.

[0116] Ninthly, this application provides a communication device that has the functions of the first and second aspects described above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first and second aspects described above. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0117] In a tenth aspect, this application provides a communication device that has the functions of the third and fourth aspects described above. For example, the communication device includes modules, units, or means that perform the operations involved in the third and fourth aspects described above. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0118] In the eleventh aspect, this application provides a communication device that has the functions of the fifth and seventh aspects mentioned above. For example, the communication device includes modules, units or means corresponding to the operations involved in the fifth and seventh aspects mentioned above. The modules, units or means can be implemented by software, or by hardware, or by a combination of software and hardware.

[0119] In a twelfth aspect, this application provides a communication device that has the functions of the sixth aspect described above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the sixth aspect described above. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0120] In a thirteenth aspect, this application provides a communication device that has the functions of the eighth aspect above. For example, the communication device includes modules, units or means corresponding to the operations involved in the eighth aspect above. These modules, units or means can be implemented by software, by hardware, or by a combination of software and hardware.

[0121] In a fourteenth aspect, this application provides a communication device including an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of the necessary computer programs or instructions for implementing the functions described in the first and second aspects above. The one or more processors can execute the computer programs or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the first and second aspects above. The interface circuit is used to implement the communication functions within the communication device and / or the communication functions between the communication device and other devices or components.

[0122] The aforementioned communication device may be a session management network element, a module (e.g., a circuit, chip, or chip system) within a session management network element, or a logical node, logical module, or software capable of implementing all or part of the functions of a session management network element.

[0123] In a fifteenth aspect, this application provides a communication device including an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of the necessary computer programs or instructions for implementing the functions described in the third and fourth aspects above. The one or more processors can execute the computer programs or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the third and fourth aspects above. The interface circuit is used to implement the communication functions within the communication device and / or the communication functions between the communication device and other devices or components.

[0124] The aforementioned communication device may be a policy control network element, a module (e.g., a circuit, chip, or chip system) within a policy control network element, or a logical node, logical module, or software capable of implementing all or part of the functions of a policy control network element.

[0125] In a sixteenth aspect, this application provides a communication device including an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of the necessary computer programs or instructions for implementing the functions described in the fifth and seventh aspects above. The one or more processors are capable of executing the computer programs or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the fifth and seventh aspects above. The interface circuit is used to implement the communication functions within the communication device and / or the communication functions between the communication device and other devices or components.

[0126] In one possible design, the processor is used to communicate with other devices or components through the interface circuit.

[0127] In one possible design, the communication device may also include the memory.

[0128] The aforementioned communication device may be a terminal, a communication module in a terminal, or a chip in a terminal that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0129] In a seventeenth aspect, this application provides a communication device including an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of a computer program or instructions necessary for implementing the functions described in the sixth aspect above. The one or more processors are capable of executing the computer program or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the sixth aspect above. The interface circuit is used to implement the communication functions within the communication device and / or the communication functions between the communication device and other devices or components.

[0130] The aforementioned communication device may be a first user plane network element, a module (e.g., a circuit, chip, or chip system) within the first user plane network element, or a logic node, logic module, or software capable of implementing all or part of the functions of the first user plane network element.

[0131] In an eighteenth aspect, this application provides a communication device including an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of a computer program or instructions necessary for implementing the functions described in the eighth aspect above. The one or more processors are executable to carry out the computer program or instructions, causing the communication device to implement the methods in any possible design or implementation of the eighth aspect above. The interface circuit is used to implement communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0132] The aforementioned communication device may be an application function network element, a module (e.g., a circuit, chip, or chip system) within an application function network element, or a logic node, logic module, or software capable of implementing all or part of the functions of the application function network element.

[0133] In a nineteenth aspect, this application provides a computer-readable storage medium storing a computer program or instructions that, when executed, implement the method in any of the possible designs of the first to eighth aspects described above.

[0134] In a twentieth aspect, this application provides a computer program product comprising a computer program or instructions that, when executed, implement the method in any of the possible designs described in the first to eighth aspects.

[0135] In a twentieth aspect, this application provides a communication system, including a session management network element for performing any implementation of the first aspect described above; and a terminal for performing any implementation of the fifth aspect described above.

[0136] In a twentieth aspect, this application provides a communication system, including a session management network element for performing any implementation method of the second aspect described above; and a first user plane network element for performing any implementation method of the sixth aspect described above.

[0137] In a twentieth aspect, this application provides a communication system including a session management network element and a policy control network element for performing any implementation method of the third aspect described above; the session management network element is used to receive PCC rules from the session management network element.

[0138] In a twentieth aspect, this application provides a communication system including a session management network element and a policy control network element for performing any implementation method of the fourth aspect above; the session management network element is used to receive PCC rules from the session management network element.

[0139] In a twentieth aspect, this application provides a communication system, including a session management network element and a terminal for executing any implementation method of the seventh aspect above; the session management network element is used to send a first rule to the terminal and receive indication information from the terminal, the indication information being used to indicate that the terminal has multi-stream processing capability, or to indicate that the terminal does not have multi-stream processing capability. Attached Figure Description

[0140] Figure 1 is a schematic diagram of a 5G network architecture based on a service-oriented architecture;

[0141] Figure 2(a) is a flowchart illustrating the communication method provided in an embodiment of this application;

[0142] Figure 2(b) is a flowchart illustrating the communication method provided in an embodiment of this application;

[0143] Figure 2(c) is a flowchart illustrating the communication method provided in an embodiment of this application;

[0144] Figure 2(d) is a flowchart illustrating the communication method provided in an embodiment of this application;

[0145] Figure 2(e) is a flowchart illustrating the communication method provided in an embodiment of this application;

[0146] Figure 2(f) is a flowchart illustrating the communication method provided in an embodiment of this application;

[0147] Figure 2(g) is a flowchart illustrating the communication method provided in an embodiment of this application;

[0148] Figure 3 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0149] Figure 4 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0150] Figure 5 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0151] Figure 6 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0152] Figure 7 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0153] Figure 8 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0154] Figure 9 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0155] Figure 10 is a possible exemplary block diagram of the communication device involved in the embodiments of this application;

[0156] Figure 11 is a possible exemplary block diagram of the communication device involved in the embodiments of this application. Detailed Implementation

[0157] To address the challenges of wireless broadband technology and maintain the leading edge of the 3rd Generation Partnership Project (3GPP) network, the 3GPP standards group developed the 5th generation (5G) network architecture. This architecture not only supports radio access technologies defined by the 3GPP standards group (such as Long Term Evolution (LTE) and 5G Radio Access Network (RAN)) to access the 5G core network (CN), but also supports access to the core network using non-3GPP access technologies through non-3GPP interworking functions (N3IWF) or next-generation packet data gateways (ngPDG).

[0158] Figure 1 is a schematic diagram of a service-oriented architecture-based 5G network. The 5G network architecture shown in Figure 1 may include access network equipment and core network equipment. Terminals access the data network (DN) through access network equipment and core network equipment. The core network equipment includes, but is not limited to, some or all of the following network elements: authentication server function (AUSF) network element, unified data management (UDM) network element, unified data repository (UDR) network element, network repository function (NRF) network element, network exposure function (NEF) network element, application function (AF) network element, policy control function (PCF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, and user plane function (UPF) network element.

[0159] Access network equipment, sometimes also called RAN nodes, RAN entities, or access nodes, is used to help terminals achieve wireless access.

[0160] In one possible scenario, the access network device can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system. The access network device can be a macro base station, a micro base station, an indoor station, a relay node, or a donor node. Optionally, the access network device can also be a server, a wearable device, a vehicle, or an in-vehicle device. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the access network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The access network device can also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The access network device can also be configured with program instructions for performing corresponding communication functions and corresponding program instructions. The access network device in this application may also be a logical node, logical module, or software that can implement all or part of the functions of the access network device.

[0161] In another possible scenario, multiple access network devices collaborate to assist the terminal in achieving wireless access, with each device performing a portion of the base station's functions. For example, the access network devices can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be separate entities or included in the same network element, such as a baseband unit (BBU). The RU can be included in radio frequency equipment or radio frequency units, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0162] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open radio access network (ORAN) system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through a software module, a hardware module, or a combination of software and hardware modules.

[0163] A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, transportation vehicles with wireless communication capabilities, communication modules, etc. The embodiments of this application do not limit the device form of the terminal. Terminals typically contain communication modules, circuits, or chips that perform corresponding communication functions. The terminal can also be configured with program instructions for performing the corresponding communication functions.

[0164] Access network devices and terminals can be fixed in location or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on aircraft, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of the access network devices and terminals.

[0165] The AMF (Automatic Mobility Management) network element includes functions such as mobility management and access authentication / authorization. In addition, it is responsible for transmitting user policies between the terminal and the PCF (Programmable Default Function) network element.

[0166] SMF network elements include functions such as performing session management (e.g., session establishment, modification, or deletion), executing control policies issued by PCF network elements, selecting UPF network elements, and allocating IP addresses for terminals.

[0167] UPF network elements include functions such as user plane data forwarding, session / flow-based billing statistics, and bandwidth limiting.

[0168] UDM network elements include functions for managing user subscription data.

[0169] UDR includes access functions for data types such as contract data, policy data, or application data.

[0170] NEF network elements are used to securely expose services and capabilities provided by 3GPP networks.

[0171] AF (Application Provider) network elements convey application-side requests to the network side, such as QoS requirements or user state event subscriptions. AF elements interact with the 3GPP core network to influence service flow routing, access network capability exposure, and policy control. AFs can be third-party functional entities or application services deployed by operators, such as IP Multimedia Subsystem (IMS) voice call services. AF elements include those within the core network (i.e., operator-owned AFs) and third-party AF elements (such as an enterprise's application server).

[0172] PCF network elements include policy control functions such as billing at the session and service flow levels, QoS bandwidth guarantee and mobility management, or terminal policy decisions.

[0173] NRF network elements can be used to provide network element discovery functionality, providing network element information corresponding to the network element type based on requests from other network elements. NRF network elements also provide network element management services, such as network element registration, updates, deregistration, or network element status subscription and push.

[0174] The AUSF network element is responsible for authenticating users to determine whether to allow users or devices to access the network.

[0175] A Domain Provider (DN) is a network located outside the carrier's network. A carrier's network can connect to multiple DNs, and various services can be deployed on a DN, providing data and / or voice services to terminals. For example, a DN might be the private network of a smart factory. Sensors installed in the workshop can act as terminals, and a control server for these sensors is deployed within the DN. The control server provides services to the sensors. Sensors can communicate with the control server, receive instructions from it, and transmit the collected sensor data back to the control server accordingly. Another example is a DN serving as an internal office network for a company. Employees' mobile phones or computers can act as terminals, accessing information and data resources on the company's internal office network.

[0176] In Figure 1, Nausf, Npcf, Nudr, Nudm, Naf, Namf, Nsmf, Nnef, and Nnrf are the service-based interfaces (SBIs) provided by AUSF, PCF, UDR, UDM, AF, AMF, SMF, NEF, and NRF, respectively, used to invoke the corresponding service-based operations. N1, N2, N3, N4, and N6 are interface sequence numbers, and their meanings are as follows:

[0177] 1) N1: The interface between the AMF network element and the terminal, which can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from the AMF network element) to the terminal.

[0178] 2) N2: The interface between the AMF network element and the access network equipment, which can be used to transmit radio bearer control information from the core network side to the access network equipment.

[0179] 3) N3: The interface between the access network equipment and the UPF network element, mainly used to transmit uplink and downlink user plane data between the access network equipment and the UPF network element.

[0180] 4) N4: The interface between SMF network elements and UPF network elements. It can be used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0181] 5) N6: The interface between the UPF network element and the DN, used to transmit uplink and downlink user data streams between the UPF network element and the DN.

[0182] In the architecture shown in Figure 1, the various network function elements are connected via a service-oriented bus and interact through service-oriented interfaces. The advantages of a service-oriented bus are improved network flexibility, openness, scalability, and intelligence, enabling support for diverse service scenarios and requirements. The service-oriented bus can be used to transmit various types of data and signaling. For example, it can be used to transmit latency-sensitive real-time signaling (e.g., service-oriented interface call signaling between network function elements), latency-sensitive real-time data (e.g., real-time AI inference data), and non-real-time data (e.g., offline AI training data). Furthermore, when transmitting this data or signaling, the service-oriented bus couples the data or signaling together; that is, the service-oriented bus can simultaneously transmit real-time signaling, real-time data, and non-real-time data.

[0183] It should be noted that the term "network element" can be omitted when describing the above network elements (such as SMF network elements, UPF network elements, etc.). For example, an SMF network element can be abbreviated as SMF, a UPF network element as UPF, and so on. This abbreviated description is also used in Figure 1.

[0184] It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network element or function can be implemented by one device, multiple devices working together, or a functional module within a single device; this application embodiment does not specifically limit this.

[0185] The user plane network element, mobility management network element, session management network element, application function network element, and policy control network element in this application can be UPF, AMF, SMF, AF, and PCF as shown in Figure 1, or they can be network elements in future communication networks that have the functions of the above-mentioned UPF, AMF, SMF, AF, and PCF. This application does not limit them in this regard.

[0186] With the development of communication technology, multimedia services, represented by XR services, have experienced exponential growth. XR services combine and allow interaction between physical objects in the real world and digital objects in the virtual world through auxiliary devices, achieving a perfect fusion of the real and virtual worlds. XR services include VR services, AR services, and MR services.

[0187] Multimedia service data streams are divided into various types, such as video streams, audio streams, haptic streams, etc. Multiple data streams of the same multimedia service have the same five-tuple information (i.e., source IP address, source port number, destination IP address, destination port number, and protocol type), and these multiple data streams can be transmitted through multi-stream multiplexing, that is, these multiple data streams can be transmitted simultaneously.

[0188] Multiple data streams with the same five-tuple information for the same multimedia service are mapped to the same QoS stream for transmission during the transmission process. However, these multiple data streams may actually have different transmission requirements (such as latency requirements, packet loss rate requirements, etc.). Therefore, it is desirable to select different QoS streams for different data streams of the same multimedia service based on the transmission requirements of the data streams, so as to meet the differentiated transmission needs of different data streams.

[0189] To address the aforementioned issues, this application aims to provide a suitable solution.

[0190] The communication method, communication device, and communication system provided in this application will be described below with reference to the accompanying drawings. It is understood that this application uses a terminal, user plane network element, session management network element, and application function network element as examples to illustrate the execution entities of the interaction, but this application does not limit the execution entities of the interaction. The method executed by the terminal in this application can also be implemented by a communication module in the terminal or a circuit or chip responsible for communication functions in the terminal (such as a modem chip (also known as a baseband chip), or a SoC chip containing a modem core, or a SIP chip). The method executed by the user plane network element in this application can also be implemented by a module (e.g., a circuit, chip, or chip system) in the user plane network element, or a logical node, logical module, or software that can implement all or part of the functions of the user plane network element. The method executed by the session management network element in this application can also be implemented by a module (e.g., a circuit, chip, or chip system) in the session management network element, or a logical node, logical module, or software that can implement all or part of the functions of the session management network element. The methods executed by the policy control network element in this application can also be implemented by modules (e.g., circuits, chips, or chip systems) within the policy control network element, or by logic nodes, logic modules, or software capable of implementing all or part of the functions of the policy control network element. Similarly, the methods executed by the application function network element in this application application can also be implemented by modules (e.g., circuits, chips, or chip systems) within the application function network element, or by logic nodes, logic modules, or software capable of implementing all or part of the functions of the application function network element.

[0191] In this application, data flow is also referred to as service flow or media flow, etc.

[0192] Figure 2(a) is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0193] Step 201a: The policy control network element sends PCC rules to the session management network element. Correspondingly, the session management network element receives the PCC rules.

[0194] This PCC rule is used to indicate information about the first data stream and the first QoS parameter requirements of the first QoS stream, as well as information about the second data stream and the second QoS parameter requirements of the second QoS stream. The first data stream corresponds to the first QoS stream, and the second data stream corresponds to the second QoS stream.

[0195] The information in the first data stream contains the information of the first quintuple, and the information in the second data stream contains the information of the second quintuple, and the information of the first quintuple is the same as that of the second quintuple. That is, the first data stream and the second data stream have the same quintuple information.

[0196] The first QoS parameter requirements (such as latency requirements, packet loss rate requirements, etc.) are different from the second QoS parameter requirements (such as latency requirements, packet loss rate requirements, etc.). In other words, the first data stream and the second data stream have different QoS requirements.

[0197] Step 202a: The session management network element obtains the terminal's capability information.

[0198] This capability information is used to indicate whether the terminal has multi-stream processing capability or not. Multi-stream processing capability can also be referred to as multi-stream mapping capability.

[0199] When a terminal has multi-stream processing capability, it means that the terminal can identify different data streams that correspond to the same five-tuple information and can map different data streams to different QoS streams for transmission.

[0200] When a terminal lacks multi-stream processing capabilities, it means that the terminal cannot map different data streams with the same 5-tuple information to different QoS streams for transmission.

[0201] For example, the session management network element can receive indication information from the terminal, which indicates the terminal's capability information. For instance, in the terminal's registration process, the terminal carries this indication information in the registration request. Or, for example, in the session establishment process, the terminal carries this indication information in the session establishment request.

[0202] For example, the session management network element can also obtain the terminal's subscription information from the UDM network element, which includes the terminal's capability information.

[0203] It should be noted that step 202a can be performed after step 201a or before step 201a, and this application does not limit it in this regard.

[0204] Step 203a: The session management network element sends a first rule to the terminal based on the terminal's capability information. Correspondingly, the terminal receives the first rule.

[0205] This first rule can also be called the QoS rule.

[0206] The first rule is generated by the session management network element based on the PCC rules. That is, the session management network element generates the first rule based on the terminal's capability information and the PCC rules, and sends the first rule to the terminal.

[0207] The first rule will be explained in detail below, with different scenarios.

[0208] Scenario 1: The terminal's capability information indicates that the terminal has multi-stream processing capabilities.

[0209] When the session management network element determines that the terminal has multi-stream processing capabilities, the generated first rule includes a first packet filter, a second packet filter, information about the first QoS stream corresponding to the first packet filter, and information about the second QoS stream corresponding to the second packet filter. The first packet filter includes information about the first data stream, and the second packet filter includes information about the second data stream. The information about the first data stream includes information about a first 5-tuple, and the information about the second data stream includes information about a second 5-tuple. The second 5-tuple information is the same as the first 5-tuple information. The first packet filter is used to identify the first data stream, and the second packet filter is used to identify the second data stream. The QoS stream identifier in the information about the first QoS stream is different from the QoS stream identifier in the information about the second QoS stream. For example, the QoS stream identifier of the first QoS stream is QFI#1, and the QoS stream identifier of the second QoS stream is QFI#2.

[0210] Upon receiving the first rule, the terminal can map a first data stream and a second data stream with the same five-tuple information to different QoS streams. Specifically, the first data stream is mapped to the first QoS stream, and the second data stream is mapped to the second QoS stream. Since the QoS stream identifiers of the first and second QoS streams are different, they possess different QoS guarantee capabilities, such as different latency and packet loss rates. This method can satisfy the differentiated QoS requirements of different data streams with the same five-tuple information, thereby improving communication quality.

[0211] In one possible implementation, the information of the first data stream in the first packet filter includes not only the first quintuple information but also first information; the information of the second data stream in the second packet filter includes not only the second quintuple information but also second information. The first and second information are different. The first and second information are used to distinguish the first data stream and the second data stream that correspond to the same quintuple information. Based on this method, when it is identified that the information of the first data stream and the information of the second data stream contain the same quintuple information, the first data stream and the second data stream are further distinguished by identifying the first information in the information of the first data stream and the second information in the information of the second data stream, and it is determined that the first data stream and the second data stream are different data streams corresponding to the same quintuple information, thereby achieving correct identification and distinction of different data streams corresponding to the same quintuple information.

[0212] In one possible implementation, the information of the first data stream in the first packet filter includes, in addition to the first 5-tuple information, at least one of a first payload type, a first synchronization source identifier, or a first tag header field. The first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream. For example, the type of the first data stream could be a video stream, an audio stream, or a haptic stream. The information of the second data stream in the second packet filter includes, in addition to the second 5-tuple information, at least one of a second payload type, a second synchronization source identifier, or a second tag header field. The second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream. For example, the type of the second data stream could be a video stream, an audio stream, or a haptic stream. Both the first and second data streams are transmitted via RTP, SRTP, RTCP, or SRTCP. Regarding this implementation method, the terminal possesses multi-stream processing capabilities, which can be understood as follows: the terminal can identify the payload type, synchronization source identifier, or tag header field information in the data stream information, thereby distinguishing different data streams with the same five-tuple information. Here, the first payload type, first synchronization source identifier, or first tag header field information can be understood as a specific example of the aforementioned first information, and the second payload type, second synchronization source identifier, or second tag header field information can be understood as a specific example of the aforementioned second information.

[0213] Since different data streams have different synchronization source identifiers, these identifiers can be used to distinguish different data streams that have the same 5-tuple information. That is, the first synchronization source identifier in the information of the first data stream is different from the second synchronization source identifier in the information of the second data stream. Therefore, the first data stream and the second data stream that have the same 5-tuple information can be distinguished by the first synchronization source identifier and the second synchronization source identifier.

[0214] Because the tag header field information of different data streams is different, this tag header field information can be used to distinguish different data streams with the same 5-tuple information. That is, the first tag header field information in the information of the first data stream is different from the second tag header field information in the information of the second data stream. Therefore, the first data stream and the second data stream with the same 5-tuple information can be distinguished by the first tag header field information and the second tag header field information.

[0215] For example, assuming that the information of data stream #1 includes 5-tuple information #1 and payload type #1, the information of data stream #2 includes 5-tuple information #1 and payload type #1, and the information of data stream #3 includes 5-tuple information #1 and payload type #2, where payload type #1 is a video stream and payload type #2 is an audio stream, then data stream #1 and data stream #2 can both be mapped to QoS stream #1, and data stream #3 can both be mapped to QoS stream #2. Based on this method, QoS mapping at the data stream type granularity can be achieved.

[0216] For example, suppose that the information of data stream #1 includes 5-tuple information #1 and synchronization source identifier #1, the information of data stream #2 includes 5-tuple information #1 and synchronization source identifier #2, and the information of data stream #3 includes 5-tuple information #1 and synchronization source identifier #3, wherein synchronization source identifier #1, synchronization source identifier #2, and synchronization source identifier #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved.

[0217] For example, suppose that the information in data stream #1 includes 5-tuple information #1 and tag header field information #1, the information in data stream #2 includes 5-tuple information #1 and tag header field information #2, and the information in data stream #3 includes 5-tuple information #1 and tag header field information #3, wherein tag header field information #1, tag header field information #2, and tag header field information #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved.

[0218] This application is not limited to any particular application scenario. In addition to RTP application scenarios, it can also be applied to QUIC application scenarios or media over QUIC (MoQ) application scenarios based on QUIC.

[0219] In one possible implementation, under the MoQ application scenario, the information of the first data stream includes first quintuple information and first metadata, and the information of the second data stream includes second quintuple information and second metadata. The first and second quintuple information are identical, and different metadata corresponds to different data streams. That is, since the metadata in the information of the first and second data streams is different, the first and second data streams with the same quintuple information can be identified based on the first and second metadata. As a specific example, suppose the information of data stream #1 includes quintuple information #1 and metadata #1, the information of data stream #2 includes quintuple information #1 and metadata #2, and the information of data stream #3 includes quintuple information #1 and metadata #3. Metadata #1, metadata #2, and metadata #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved. For example, different data streams can be indicated by target IDs or other information in the metadata, with different target IDs used to indicate different data streams. Here, the first metadata can be understood as a specific example of the aforementioned first information, and the second metadata can be understood as a specific example of the aforementioned second information.

[0220] In response to scenario one, when the terminal has multi-stream processing capabilities, the session management network element sends a first rule to the terminal. Based on this first rule, the terminal can map different data streams with the same five-tuple information to different QoS streams for transmission, thereby meeting the differentiated transmission requirements of different data streams.

[0221] Scenario 2: The terminal's capability information indicates that the terminal does not have multi-stream processing capabilities.

[0222] When the session management network element determines that the terminal does not have multi-stream processing capabilities, the generated first rule includes a first packet filter, a second packet filter, information about the first QoS stream corresponding to the first packet filter, and information about the second QoS stream corresponding to the second packet filter. The first packet filter includes information about the first data stream, and the second packet filter includes information about the second data stream. The information about the first data stream includes information about a first 5-tuple, and the information about the second data stream includes information about a second 5-tuple. The second 5-tuple information is the same as the first 5-tuple information. The first packet filter is used to identify the first data stream, and the second packet filter is used to identify the second data stream. The QoS stream identifier in the information about the first QoS stream is the same as the QoS stream identifier in the information about the second QoS stream. For example, if the QoS stream identifier of the first QoS stream is QFI#1, the QoS stream identifier of the second QoS stream is also QFI#1.

[0223] Upon receiving a first rule, the terminal can map a first data stream and a second data stream with the same 5-tuple information to the same QoS stream. Specifically, the first data stream is mapped to the first QoS stream, the second data stream is mapped to the second QoS stream, and the first QoS stream and the second QoS stream refer to the same QoS stream. This method can provide corresponding QoS guarantees for different data streams with the same 5-tuple information, thereby improving communication quality.

[0224] In this second scenario, where the terminal lacks multi-stream processing capabilities, the session management network element sends a first rule to the terminal. Based on this first rule, the terminal can map different data streams with the same five-tuple information to the same QoS stream for transmission, thereby improving communication quality.

[0225] Based on the above scheme, the session management network element generates a first rule and sends it to the terminal according to the terminal's capability information and PCC rules. When the terminal has multi-stream processing capabilities, it can map different data streams with the same 5-tuple information to different QoS streams for transmission according to this first rule, thereby meeting the differentiated transmission requirements of different data streams and improving communication quality. When the terminal does not have multi-stream processing capabilities, it can still map different data streams with the same 5-tuple information to the same QoS stream for transmission according to this first rule, thus improving communication quality.

[0226] Figure 2(b) is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0227] Step 201b: The policy control network element obtains the terminal's capability information.

[0228] This capability information is used to indicate whether the terminal has multi-stream processing capability or not. Multi-stream processing capability can also be referred to as multi-stream mapping capability.

[0229] When a terminal has multi-stream processing capability, it means that the terminal can identify different data streams that correspond to the same five-tuple information and can map different data streams to different QoS streams for transmission.

[0230] When a terminal lacks multi-stream processing capabilities, it means that the terminal cannot map different data streams with the same 5-tuple information to different QoS streams for transmission.

[0231] For example, a policy control network element can receive indication information from a terminal, which is used to indicate the terminal's capability information.

[0232] For example, the policy control network element can receive indication information from the session management network element, which is used to indicate the terminal's capability information.

[0233] For example, the policy control network element can also obtain the terminal's subscription information from the UDM network element, which includes the terminal's capability information.

[0234] In step 202b, the policy control network element sends PCC rules to the session management network element based on the terminal's capability information. Correspondingly, the session management network element receives the PCC rules.

[0235] In one possible implementation, the policy control network element receives flow description information of a first data stream, transmission requirements of the first data stream, flow description information of a second data stream, and transmission requirements of the second data stream from the application function network element. The flow description information of the first data stream includes a first 5-tuple, and the flow description information of the second data stream includes a second 5-tuple. The second 5-tuple is identical to the first 5-tuple, meaning the first and second data streams have the same 5-tuple. The transmission requirements of the first and second data streams are different, meaning they have different transmission requirements. The policy control network element determines PCC rules based on the terminal's capability information and the flow description information, transmission requirements, and transmission requirements of the first and second data streams.

[0236] The PCC rule is described below in different scenarios.

[0237] Scenario 1: The terminal's capability information indicates that the terminal has multi-stream processing capabilities.

[0238] When the policy control network element determines that the terminal has multi-stream processing capability, the generated PCC rules are used to indicate the information of the first data stream, the information of the second data stream, the information of the first QoS stream corresponding to the first data stream, and the information of the second QoS stream corresponding to the second data stream.

[0239] The information in the first data stream includes the information of the first quintuple, and the information in the second data stream includes the information of the second quintuple. The information of the second quintuple is the same as that of the first quintuple, that is, the first data stream and the second data stream have the same quintuple information.

[0240] The information of the first QoS flow includes the first QoS parameter requirements and / or the QoS flow identifier of the first QoS flow, and the information of the second QoS flow includes the second QoS parameter requirements and / or the QoS flow identifier of the second QoS flow. The first QoS parameter requirements (e.g., latency requirements, packet loss rate requirements, etc.) are different from the second QoS parameter requirements (e.g., latency requirements, packet loss rate requirements, etc.). The QoS flow identifier of the first QoS flow is different from the QoS flow identifier of the second QoS flow; for example, the QoS flow identifier of the first QoS flow is QFI#1, and the QoS flow identifier of the second QoS flow is QFI#2.

[0241] In one possible implementation, the information of the first data stream in the PCC rule includes not only the first quintuple information but also first information; similarly, the information of the second data stream in the PCC rule includes not only the second quintuple information but also second information. The first and second information are different. The first and second information are used to distinguish between the first and second data streams that correspond to the same quintuple information. Based on this method, when the information of the first and second data streams is identified to contain the same quintuple information, the first and second data streams are further distinguished by identifying the first information in the first data stream and the second information in the second data stream, thus determining that the first and second data streams are different data streams corresponding to the same quintuple information, thereby correctly identifying and distinguishing different data streams corresponding to the same quintuple information.

[0242] In one possible implementation, the information of the first data stream in the PCC rule includes, in addition to the first 5-tuple information, at least one of a first payload type, a first synchronization source identifier, or a first tag header field. The first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream. For example, the type of the first data stream could be a video stream, an audio stream, or a haptic stream. The information of the second data stream in the PCC rule includes, in addition to the second 5-tuple information, at least one of a second payload type, a second synchronization source identifier, or a second tag header field. The second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream. For example, the type of the second data stream could be a video stream, an audio stream, or a haptic stream. Both the first and second data streams are transmitted via RTP, SRTP, RTCP, or SRTCP. Regarding this implementation method, the terminal possesses multi-stream processing capabilities, which can be understood as follows: the terminal can identify the payload type, synchronization source identifier, or tag header field information in the data stream information, thereby distinguishing different data streams with the same five-tuple information. Here, the first payload type, first synchronization source identifier, or first tag header field information can be understood as a specific example of the aforementioned first information, and the second payload type, second synchronization source identifier, or second tag header field information can be understood as a specific example of the aforementioned second information.

[0243] Since different data streams have different synchronization source identifiers, these identifiers can be used to distinguish different data streams that have the same 5-tuple information. That is, the first synchronization source identifier in the information of the first data stream is different from the second synchronization source identifier in the information of the second data stream. Therefore, the first data stream and the second data stream that have the same 5-tuple information can be distinguished by the first synchronization source identifier and the second synchronization source identifier.

[0244] Because the tag header field information of different data streams is different, this tag header field information can be used to distinguish different data streams with the same 5-tuple information. That is, the first tag header field information in the information of the first data stream is different from the second tag header field information in the information of the second data stream. Therefore, the first data stream and the second data stream with the same 5-tuple information can be distinguished by the first tag header field information and the second tag header field information.

[0245] This application is not limited to any particular application scenario. In addition to RTP application scenarios, it can also be applied to QUIC application scenarios or MoQ application scenarios, etc.

[0246] In one possible implementation, within the MoQ application scenario, the information of the first data stream in the PCC rule includes first quintuple information and first metadata, while the information of the second data stream in the PCC rule includes second quintuple information and second metadata. The first and second quintuple information are identical, and different metadata corresponds to different data streams. That is, since the metadata in the information of the first and second data streams is different, the first and second data streams with the same quintuple information can be identified based on the first and second metadata. For example, different data streams can be indicated by target IDs or other information in the metadata, with different target IDs indicating different data streams. Here, the first metadata can be understood as a specific example of the aforementioned first information, and the second metadata can be understood as a specific example of the aforementioned second information.

[0247] Scenario 2: The terminal's capability information indicates that the terminal does not have multi-stream processing capabilities.

[0248] When the policy control network element determines that the terminal does not have multi-stream processing capability, the generated PCC rule is used to indicate the information of the first data stream, the information of the second data stream, the information of the first QoS stream corresponding to the first data stream, and the information of the second QoS stream corresponding to the second data stream.

[0249] The information in the first data stream includes the information of the first quintuple, and the information in the second data stream includes the information of the second quintuple. The information of the second quintuple is the same as that of the first quintuple, that is, the first data stream and the second data stream have the same quintuple information.

[0250] The information of the first QoS flow includes the first QoS parameter requirements and / or the QoS flow identifier of the first QoS flow. The information of the second QoS flow includes the second QoS parameter requirements and / or the QoS flow identifier of the second QoS flow. The first QoS parameter requirements (e.g., latency requirements, packet loss rate requirements, etc.) are the same as the second QoS parameter requirements (e.g., latency requirements, packet loss rate requirements, etc.). The QoS flow identifier of the first QoS flow is the same as the QoS flow identifier of the second QoS flow. For example, if the QoS flow identifier of the first QoS flow is QFI#1, the QoS flow identifier of the second QoS flow is also QFI#1.

[0251] Step 203b: The session management network element sends the first rule to the terminal. Accordingly, the terminal receives the first rule.

[0252] This first rule can also be called the QoS rule.

[0253] The first rule is generated by the session management network element based on the PCC rule.

[0254] Corresponding to scenario one in step 202b above, the first rule generated by the session management network element includes a first packet filter, a second packet filter, information about a first QoS flow corresponding to the first packet filter, and information about a second QoS flow corresponding to the second packet filter. The first packet filter includes information about a first data flow, and the second packet filter includes information about a second data flow. The information about the first data flow includes information about a first 5-tuple, and the information about the second data flow includes information about a second 5-tuple. The second 5-tuple information is the same as the first 5-tuple information. The first packet filter is used to identify the first data flow, and the second packet filter is used to identify the second data flow. The QoS flow identifier in the information about the first QoS flow is different from the QoS flow identifier in the information about the second QoS flow. When the terminal receives the first rule, it can map the first data flow and the second data flow, which have the same 5-tuple information, to different QoS flows according to the first rule. Specifically, the first data flow is mapped to the first QoS flow, and the second data flow is mapped to the second QoS flow. Since the QoS flow identifier of the first QoS flow is different from the QoS flow identifier of the second QoS flow, the first QoS flow and the second QoS flow have different QoS guarantee capabilities, such as different latency and packet loss rates. This method can meet the differentiated QoS requirements of different data streams with the same five-tuple information, thereby improving communication quality. For example, the information of the first data stream in the first packet filter includes, in addition to the first five-tuple information, at least one of a first payload type, a first synchronization source identifier, or a first tag header field. The information of the second data stream in the second packet filter includes, in addition to the second five-tuple information, at least one of a second payload type, a second synchronization source identifier, or a second tag header field. In another example, the information of the first data stream in the first packet filter includes, in addition to the first five-tuple information, metadata. The information of the second data stream in the second packet filter includes, in addition to the second five-tuple information, second metadata.

[0255] Corresponding to scenario two in step 202b above, the first rule generated by the session management network element includes a first packet filter, a second packet filter, information about a first QoS flow corresponding to the first packet filter, and information about a second QoS flow corresponding to the second packet filter. The first packet filter includes information about a first data flow, and the second packet filter includes information about a second data flow. The information about the first data flow includes first 5-tuple information, and the information about the second data flow includes second 5-tuple information. The second 5-tuple information is the same as the first 5-tuple information. The first packet filter is used to identify the first data flow, and the second packet filter is used to identify the second data flow. The QoS flow identifier in the information about the first QoS flow is the same as the QoS flow identifier in the information about the second QoS flow. When the terminal receives the first rule, it can map the first data flow and the second data flow with the same 5-tuple information to the same QoS flow. Specifically, the first data flow is mapped to the first QoS flow, and the second data flow is mapped to the second QoS flow, and the first QoS flow and the second QoS flow refer to the same QoS flow. This method can provide corresponding QoS guarantees for different data flows with the same 5-tuple information, thereby improving communication quality.

[0256] Based on the above scheme, the policy control network element determines the PCC rules according to the terminal's capability information and sends the PCC rules to the session management network element. The session management network element generates a first rule based on the PCC rules and sends the first rule to the terminal. When the terminal has multi-stream processing capabilities, it can map different data streams with the same five-tuple information to different QoS streams for transmission according to the first rule, thereby meeting the differentiated transmission requirements of different data streams and improving communication quality. When the terminal does not have multi-stream processing capabilities, it can still map different data streams with the same five-tuple information to the same QoS stream for transmission according to the first rule, thus improving communication quality.

[0257] Figure 2(c) is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0258] In step 201c, the policy control network element sends PCC rules to the session management network element. Correspondingly, the session management network element receives the PCC rules.

[0259] This PCC rule is used to indicate information about the first data stream and the first QoS parameter requirements of the first QoS stream, as well as information about the second data stream and the second QoS parameter requirements of the second QoS stream. The first data stream corresponds to the first QoS stream, and the second data stream corresponds to the second QoS stream.

[0260] The information in the first data stream contains the information of the first quintuple, and the information in the second data stream contains the information of the second quintuple, and the information of the first quintuple is the same as that of the second quintuple. That is, the first data stream and the second data stream have the same quintuple information.

[0261] The first QoS parameter requirements (such as latency requirements, packet loss rate requirements, etc.) are different from the second QoS parameter requirements (such as latency requirements, packet loss rate requirements, etc.). In other words, the first data stream and the second data stream have different QoS requirements.

[0262] Step 202c: The session management network element obtains the capability information of the first user plane network element.

[0263] This capability information is used to indicate whether the first user plane network element has multi-stream processing capability or not. Multi-stream processing capability can also be referred to as multi-stream mapping capability.

[0264] When the first user plane network element has multi-stream processing capability, it means that the first user plane network element can identify different data streams with the same five-tuple information and can map different data streams to different QoS streams for transmission.

[0265] When the first user plane network element does not have multi-stream processing capability, it means that the first user plane network element cannot map different data streams with the same quintuple information to different QoS streams for transmission.

[0266] For example, the session management network element can receive indication information from the first user plane network element, which is used to indicate the capability information of the first user plane network element.

[0267] It should be noted that step 202c can be performed after step 201c or before step 201c, and this application does not limit it in this regard.

[0268] In step 203c, the session management network element sends the second rule to the first user plane network element based on the capability information of the first user plane network element. Correspondingly, the first user plane network element receives the second rule.

[0269] This second rule can also be called the N4 rule.

[0270] The second rule is generated by the session management network element based on the PCC rules. That is, the session management network element generates the second rule based on the capability information of the first user plane network element and the PCC rules, and sends the second rule to the first user plane network element.

[0271] The second rule will be explained in detail below, with different scenarios for each case.

[0272] Scenario 1: The capability information of the first user plane network element indicates that the first user plane network element has multi-stream processing capability.

[0273] When the session management network element determines that the first user plane network element has multi-stream processing capabilities, the generated second rule includes a first packet detection rule, a second packet detection rule, a first QoS execution rule corresponding to the first packet detection rule, information about the first QoS stream, and a second QoS execution rule corresponding to the second packet detection rule. The first packet detection rule includes information about the first data stream, and the second packet detection rule includes information about the second data stream. The information about the first data stream includes first 5-tuple information, and the information about the second data stream includes second 5-tuple information. The second 5-tuple information is the same as the first 5-tuple information. The first packet detection rule is used to identify the first data stream, and the second packet detection rule is used to identify the second data stream. The first QoS execution rule includes information about the first QoS stream and is used to instruct that the header of the data packets in the first data stream carries the QoS stream identifier of the first QoS stream corresponding to the first data stream. The second QoS execution rule includes information about the second QoS stream and is used to instruct that the header of the data packets in the second data stream carries the QoS stream identifier of the second QoS stream corresponding to the second data stream. The QoS stream identifier of the first QoS stream is different from the QoS stream identifier of the second QoS stream. For example, the QoS flow identifier of the first QoS flow is QFI#1, and the QoS flow identifier of the second QoS flow is QFI#2.

[0274] Upon receiving the second rule, the first user plane network element can map a first data stream and a second data stream with the same five-tuple information to different QoS streams. Specifically, the first data stream is mapped to the first QoS stream, and the second data stream is mapped to the second QoS stream. Since the QoS stream identifiers of the first and second QoS streams are different, they possess different QoS guarantee capabilities, such as different latency and packet loss rates. This method can satisfy the differentiated QoS requirements of different data streams with the same five-tuple information, thereby improving communication quality.

[0275] In one possible implementation, the information of the first data stream in the first packet detection rule includes not only the first quintuple information but also first information; similarly, the information of the second data stream in the second packet detection rule includes not only the second quintuple information but also second information. The first and second information are different. The first and second information are used to distinguish between the first and second data streams that correspond to the same quintuple information. Based on this method, when the information of the first and second data streams is identified to contain the same quintuple information, the first and second data streams are further distinguished by identifying the first information in the first data stream and the second information in the second data stream, thus determining that the first and second data streams are different data streams corresponding to the same quintuple information, thereby correctly identifying and distinguishing different data streams corresponding to the same quintuple information.

[0276] In one possible implementation, the information of the first data stream in the first packet detection rule includes, in addition to the first 5-tuple information, at least one of a first payload type, a first synchronization source identifier, or a first tag header field. The first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream. For example, the type of the first data stream could be a video stream, an audio stream, or a haptic stream. The information of the second data stream in the second packet detection rule includes, in addition to the second 5-tuple information, at least one of a second payload type, a second synchronization source identifier, or a second tag header field. The second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream. For example, the type of the second data stream could be a video stream, an audio stream, or a haptic stream. Both the first and second data streams are transmitted via RTP, SRTP, RTCP, or SRTCP. Regarding this implementation method, the first user plane network element possesses multi-stream processing capabilities, which can be understood as follows: the first user plane network element can identify the payload type, synchronization source identifier, or tag header field information in the data stream information, thereby distinguishing different data streams with the same five-tuple information. Here, the first payload type, first synchronization source identifier, or first tag header field information can be understood as specific examples of the aforementioned first information, and the second payload type, second synchronization source identifier, or second tag header field information can be understood as specific examples of the aforementioned second information.

[0277] Since different data streams have different synchronization source identifiers, these identifiers can be used to distinguish different data streams that have the same 5-tuple information. That is, the first synchronization source identifier in the information of the first data stream is different from the second synchronization source identifier in the information of the second data stream. Therefore, the first data stream and the second data stream that have the same 5-tuple information can be distinguished by the first synchronization source identifier and the second synchronization source identifier.

[0278] Because the tag header field information of different data streams is different, this tag header field information can be used to distinguish different data streams with the same 5-tuple information. That is, the first tag header field information in the information of the first data stream is different from the second tag header field information in the information of the second data stream. Therefore, the first data stream and the second data stream with the same 5-tuple information can be distinguished by the first tag header field information and the second tag header field information.

[0279] For example, assuming that the information of data stream #1 includes 5-tuple information #1 and payload type #1, the information of data stream #2 includes 5-tuple information #1 and payload type #1, and the information of data stream #3 includes 5-tuple information #1 and payload type #2, where payload type #1 is a video stream and payload type #2 is an audio stream, then data stream #1 and data stream #2 can both be mapped to QoS stream #1, and data stream #3 can both be mapped to QoS stream #2. Based on this method, QoS mapping at the data stream type granularity can be achieved.

[0280] For example, suppose that the information of data stream #1 includes 5-tuple information #1 and synchronization source identifier #1, the information of data stream #2 includes 5-tuple information #1 and synchronization source identifier #2, and the information of data stream #3 includes 5-tuple information #1 and synchronization source identifier #3, wherein synchronization source identifier #1, synchronization source identifier #2, and synchronization source identifier #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved.

[0281] For example, suppose that the information in data stream #1 includes 5-tuple information #1 and tag header field information #1, the information in data stream #2 includes 5-tuple information #1 and tag header field information #2, and the information in data stream #3 includes 5-tuple information #1 and tag header field information #3, wherein tag header field information #1, tag header field information #2, and tag header field information #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved.

[0282] This application is not limited to any particular application scenario. In addition to RTP application scenarios, it can also be applied to QUIC application scenarios or MoQ application scenarios, etc.

[0283] In one possible implementation, under the MoQ application scenario, the information of the first data stream includes first quintuple information and first metadata, and the information of the second data stream includes second quintuple information and second metadata. The first and second quintuple information are identical, and different metadata corresponds to different data streams. That is, since the metadata in the information of the first and second data streams is different, the first and second data streams with the same quintuple information can be identified based on the first and second metadata. As a specific example, suppose the information of data stream #1 includes quintuple information #1 and metadata #1, the information of data stream #2 includes quintuple information #1 and metadata #2, and the information of data stream #3 includes quintuple information #1 and metadata #3. Metadata #1, metadata #2, and metadata #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved. For example, different data streams can be indicated by target IDs or other information in the metadata, with different target IDs used to indicate different data streams. Here, the first metadata can be understood as a specific example of the aforementioned first information, and the second metadata can be understood as a specific example of the aforementioned second information.

[0284] In response to scenario one, when the first user plane network element has multi-stream processing capabilities, the session management network element sends a second rule to the first user plane network element. Based on the second rule, the first user plane network element can map different data streams with the same five-tuple information to different QoS streams for transmission, so as to meet the differentiated transmission requirements of different data streams.

[0285] Scenario 2: The capability information of the first user plane network element indicates that the first user plane network element does not have multi-stream processing capability.

[0286] When the session management network element determines that the first user plane network element does not have multi-stream processing capabilities, the generated second rule includes a first packet detection rule, a second packet detection rule, a first QoS execution rule corresponding to the first packet detection rule, and a second QoS execution rule corresponding to the second packet detection rule. The first packet detection rule includes information about the first data stream, and the second packet detection rule includes information about the second data stream. The first data stream information includes first 5-tuple information, and the second data stream information includes second 5-tuple information. The second 5-tuple information is the same as the first 5-tuple information. The first packet detection rule is used to identify the first data stream, and the second packet detection rule is used to identify the second data stream. The first QoS execution rule includes information about the first QoS stream and is used to instruct that the header of the data packets in the first data stream carries the QoS stream identifier of the first QoS stream corresponding to the first data stream. The second QoS execution rule includes information about the second QoS stream and is used to instruct that the header of the data packets in the second data stream carries the QoS stream identifier of the second QoS stream corresponding to the second data stream. The QoS stream identifier of the first QoS stream is the same as the QoS stream identifier of the second QoS stream. For example, the QoS flow identifier of the first QoS flow is QFI#1, and the QoS flow identifier of the second QoS flow is also QFI#1.

[0287] Upon receiving the second rule, the first user plane network element can map a first data stream and a second data stream with the same 5-tuple information to the same QoS stream. Specifically, the first data stream is mapped to a first QoS stream, the second data stream is mapped to a second QoS stream, and the first and second QoS streams refer to the same QoS stream. This method can provide corresponding QoS guarantees for different data streams with the same 5-tuple information, thereby improving communication quality.

[0288] In this second scenario, when the first user plane network element does not have multi-stream processing capabilities, the session management network element sends a second rule to the first user plane network element. According to the second rule, the first user plane network element can map different data streams with the same five-tuple information to the same QoS stream for transmission, thereby improving communication quality.

[0289] Based on the above scheme, the session management network element generates a second rule according to the capability information of the first user plane network element and the PCC rules, and sends the second rule to the first user plane network element. When the first user plane network element has multi-stream processing capabilities, it can map different data streams with the same five-tuple information to different QoS streams for transmission according to the second rule, thereby meeting the differentiated transmission requirements of different data streams and improving communication quality. Even when the first user plane network element does not have multi-stream processing capabilities, it can still map different data streams with the same five-tuple information to the same QoS stream for transmission according to the second rule, thus improving communication quality.

[0290] Furthermore, regarding scenario two above, if the first user plane network element lacks multi-stream processing capabilities, the session management network element may not send the second rule to the first user plane network element. Instead, it may select a second user plane network element with multi-stream processing capabilities and then send the second rule to the second user plane network element. The second rule sent to the second user plane network element is the same as the second rule sent to the first user plane network element in scenario one. That is, the second rule sent to the second user plane network element includes a first packet detection rule, a second packet detection rule, a first QoS execution rule corresponding to the first packet detection rule, information about the first QoS flow, and a second QoS execution rule corresponding to the second packet detection rule. The first packet detection rule includes information about the first data flow, and the second packet detection rule includes information about the second data flow. The information about the first data flow includes first 5-tuple information, and the information about the second data flow includes second 5-tuple information. The second 5-tuple information is the same as the first 5-tuple information. The first packet detection rule is used to identify the first data flow, and the second packet detection rule is used to identify the second data flow. The first QoS enforcement rule includes information about a first QoS flow. This rule instructs that the header of data packets in the first data flow carry the QoS flow identifier corresponding to the first QoS flow. The second QoS enforcement rule includes information about a second QoS flow. This rule instructs that the header of data packets in the second data flow carry the QoS flow identifier corresponding to the second QoS flow. The QoS flow identifiers of the first and second QoS flows are different. For example, the QoS flow identifier of the first QoS flow is QFI#1, and the QoS flow identifier of the second QoS flow is QFI#2.

[0291] In one possible implementation, after selecting the second user plane network element, the session management network element sends first configuration information to the first user plane network element. This first configuration information instructs the first user plane network element to update the tunnel information from the first user plane network element to the access network device with the tunnel information from the first user plane network element to the second user plane network element. Specifically, the first user plane network element deletes the tunnel information from the first user plane network element to the access network device and adds the tunnel information from the first user plane network element to the second user plane network element. The session management network element then sends second configuration information to the second user plane network element. This second configuration information instructs the second user plane network element to add the tunnel information from the second user plane network element to the first user plane network element and to add the tunnel information from the second user plane network element to the access network device. The session management network element also sends third configuration information to the access network device. This third configuration information instructs the access network device to update the tunnel information from the access network device to the first user plane network element to the tunnel information from the access network device to the second user plane network element. Specifically, the access network device can delete the tunnel information from the access network device to the first user plane network element and add the tunnel information from the access network device to the second user plane network element. Based on this implementation method, before inserting the second user plane network element, a user plane tunnel exists between the access network device and the first user plane network element. After inserting the second user plane network element, a user plane tunnel exists between the access network device and the second user plane network element, and a user plane tunnel exists between the second user plane network element and the first user plane network element, but no user plane tunnel exists between the access network device and the first user plane network element. Based on this implementation method, the second user plane network element receives a second rule and can map different data streams with the same five-tuple information to different QoS streams according to the second rule.

[0292] In another possible implementation, after selecting the second user plane network element, the session management network element sends first configuration information to the first user plane network element. This first configuration information instructs the first user plane network element to add tunnel information from the first user plane network element to the second user plane network element; that is, the first user plane network element retains the tunnel information from the first user plane network element to the access network device and adds the tunnel information from the first user plane network element to the second user plane network element. The session management network element then sends second configuration information to the second user plane network element, instructing it to add tunnel information from the second user plane network element to the first user plane network element and add the tunnel information from the second user plane network element to the access network device. Finally, the session management network element sends third configuration information to the access network device, instructing it to add tunnel information from the access network device to the second user plane network element; that is, the access network device retains the tunnel information from the access network device to the first user plane network element and adds the tunnel information from the access network device to the second user plane network element. Based on this implementation method, before inserting the second user plane network element, a user plane tunnel exists between the access network device and the first user plane network element. After inserting the second user plane network element, a user plane tunnel exists between the access network device and the second user plane network element, between the second user plane network element and the first user plane network element, and also between the access network device and the first user plane network element. Based on this implementation method, the second user plane network element receives a second rule and can map different data streams with the same five-tuple information to different QoS streams according to the second rule. Data streams that do not require multi-stream processing (e.g., multiple data streams with different five-tuple information) can be sent to the access network device by the first user plane network element. Optionally, the first user plane network element receives first packet detection information and second packet detection information from the session management network element. The first packet detection information is used by the first user plane network element to detect data streams that do not require multi-stream processing. The first user plane network element sends the data streams that do not require multi-stream processing to the access network device according to the QoS execution rule corresponding to the first packet detection information. The second data packet detection information is used by the first user plane network element to detect data flows requiring multi-stream processing. The first user plane network element, based on the QoS execution rules corresponding to the second data packet detection information, sends the data flows requiring multi-stream processing to the second user plane network element. Optionally, the access network device receives indication information, which indicates the corresponding tunnel information for different QoS flows. Thus, when the access network device transmits uplink data, it can forward different data flows to the first or second user plane network element based on the correspondence between the information of different QoS flows (such as QoS flow identifiers) and the tunnel information of the first or second user plane network element.

[0293] Figure 2(d) is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0294] Step 201d: The policy control network element obtains the capability information of the first user plane network element.

[0295] This capability information is used to indicate whether the first user plane network element has multi-stream processing capability or not. Multi-stream processing capability can also be referred to as multi-stream mapping capability.

[0296] When the first user plane network element has multi-stream processing capability, it means that the first user plane network element can identify different data streams with the same five-tuple information and can map different data streams to different QoS streams for transmission.

[0297] When the first user plane network element does not have multi-stream processing capability, it means that the first user plane network element cannot map different data streams with the same quintuple information to different QoS streams for transmission.

[0298] For example, the policy control network element can receive indication information from the first user plane network element, which is used to indicate the capability information of the first user plane network element.

[0299] For example, the policy control network element can receive indication information from the session management network element, which is used to indicate the capability information of the first user plane network element.

[0300] For example, the policy control network element can also obtain the subscription information of the first user plane network element from the UDM network element, which includes the capability information of the first user plane network element.

[0301] In step 202d, the policy control network element sends PCC rules to the session management network element based on the capability information of the first user plane network element. Correspondingly, the session management network element receives the PCC rules.

[0302] In one possible implementation, the policy control network element receives flow description information of a first data stream, transmission requirements of the first data stream, flow description information of a second data stream, and transmission requirements of the second data stream from an application function network element. The flow description information of the first data stream includes a first 5-tuple, and the flow description information of the second data stream includes a second 5-tuple. The second 5-tuple is identical to the first 5-tuple, meaning the first and second data streams have the same 5-tuple. The transmission requirements of the first and second data streams are different, meaning they have different transmission requirements. The policy control network element determines PCC rules based on the capability information of the first user plane network element and based on the flow description information of the first data stream, the transmission requirements of the first data stream, the flow description information of the second data stream, and the transmission requirements of the second data stream.

[0303] The PCC rule is described below in different scenarios.

[0304] Scenario 1: The capability information of the first user plane network element indicates that the first user plane network element has multi-stream processing capability.

[0305] When the policy control network element determines that the first user plane network element has multi-stream processing capability, the generated PCC rule is used to indicate the information of the first data stream, the information of the second data stream, the information of the first QoS stream corresponding to the first data stream, and the information of the second QoS stream corresponding to the second data stream.

[0306] The information in the first data stream includes the information of the first quintuple, and the information in the second data stream includes the information of the second quintuple. The information of the second quintuple is the same as that of the first quintuple, that is, the first data stream and the second data stream have the same quintuple information.

[0307] The information of the first QoS flow includes the first QoS parameter requirements and / or the QoS flow identifier of the first QoS flow, and the information of the second QoS flow includes the second QoS parameter requirements and / or the QoS flow identifier of the second QoS flow. The first QoS parameter requirements (e.g., latency requirements, packet loss rate requirements, etc.) are different from the second QoS parameter requirements (e.g., latency requirements, packet loss rate requirements, etc.). The QoS flow identifier of the first QoS flow is different from the QoS flow identifier of the second QoS flow; for example, the QoS flow identifier of the first QoS flow is QFI#1, and the QoS flow identifier of the second QoS flow is QFI#2.

[0308] In one possible implementation, the information of the first data stream in the PCC rule includes not only the first quintuple information but also first information; similarly, the information of the second data stream in the PCC rule includes not only the second quintuple information but also second information. The first and second information are different. The first and second information are used to distinguish between the first and second data streams that correspond to the same quintuple information. Based on this method, when the information of the first and second data streams is identified to contain the same quintuple information, the first and second data streams are further distinguished by identifying the first information in the first data stream and the second information in the second data stream, thus determining that the first and second data streams are different data streams corresponding to the same quintuple information, thereby correctly identifying and distinguishing different data streams corresponding to the same quintuple information.

[0309] In one possible implementation, the information of the first data stream in the PCC rule includes, in addition to the first 5-tuple information, at least one of a first payload type, a first synchronization source identifier, or a first tag header field. The first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream. For example, the type of the first data stream could be a video stream, an audio stream, or a haptic stream. The information of the second data stream in the PCC rule includes, in addition to the second 5-tuple information, at least one of a second payload type, a second synchronization source identifier, or a second tag header field. The second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream. For example, the type of the second data stream could be a video stream, an audio stream, or a haptic stream. Both the first and second data streams are transmitted via RTP, SRTP, RTCP, or SRTCP. Regarding this implementation method, the first user plane network element possesses multi-stream processing capabilities, which can be understood as follows: the first user plane network element can identify the payload type, synchronization source identifier, or tag header field information in the data stream information, thereby distinguishing different data streams with the same five-tuple information. Here, the first payload type, first synchronization source identifier, or first tag header field information can be understood as specific examples of the aforementioned first information, and the second payload type, second synchronization source identifier, or second tag header field information can be understood as specific examples of the aforementioned second information.

[0310] Since different data streams have different synchronization source identifiers, these identifiers can be used to distinguish different data streams that have the same 5-tuple information. That is, the first synchronization source identifier in the information of the first data stream is different from the second synchronization source identifier in the information of the second data stream. Therefore, the first data stream and the second data stream that have the same 5-tuple information can be distinguished by the first synchronization source identifier and the second synchronization source identifier.

[0311] Because the tag header field information of different data streams is different, this tag header field information can be used to distinguish different data streams with the same 5-tuple information. That is, the first tag header field information in the information of the first data stream is different from the second tag header field information in the information of the second data stream. Therefore, the first data stream and the second data stream with the same 5-tuple information can be distinguished by the first tag header field information and the second tag header field information.

[0312] This application is not limited to any particular application scenario. In addition to RTP application scenarios, it can also be applied to QUIC application scenarios or MoQ application scenarios, etc.

[0313] In one possible implementation, within the MoQ application scenario, the information of the first data stream in the PCC rule includes first quintuple information and first metadata, while the information of the second data stream in the PCC rule includes second quintuple information and second metadata. The first and second quintuple information are identical, and different metadata corresponds to different data streams. That is, since the metadata in the information of the first and second data streams is different, the first and second data streams with the same quintuple information can be identified based on the first and second metadata. For example, different data streams can be indicated by target IDs or other information in the metadata, with different target IDs indicating different data streams. Here, the first metadata can be understood as a specific example of the aforementioned first information, and the second metadata can be understood as a specific example of the aforementioned second information.

[0314] Scenario 2: The capability information of the first user plane network element indicates that the first user plane network element does not have multi-stream processing capability.

[0315] When the policy control network element determines that the first user plane network element does not have multi-stream processing capability, the generated PCC rule is used to indicate the information of the first data stream, the information of the second data stream, the information of the first QoS stream corresponding to the first data stream, and the information of the second QoS stream corresponding to the second data stream.

[0316] The information in the first data stream includes the information of the first quintuple, and the information in the second data stream includes the information of the second quintuple. The information of the second quintuple is the same as that of the first quintuple, that is, the first data stream and the second data stream have the same quintuple information.

[0317] The information of the first QoS flow includes the first QoS parameter requirements and / or the QoS flow identifier of the first QoS flow. The information of the second QoS flow includes the second QoS parameter requirements and / or the QoS flow identifier of the second QoS flow. The first QoS parameter requirements (e.g., latency requirements, packet loss rate requirements, etc.) are the same as the second QoS parameter requirements (e.g., latency requirements, packet loss rate requirements, etc.). The QoS flow identifier of the first QoS flow is the same as the QoS flow identifier of the second QoS flow. For example, if the QoS flow identifier of the first QoS flow is QFI#1, the QoS flow identifier of the second QoS flow is also QFI#1.

[0318] In step 203d, the session management network element sends the second rule to the first user plane network element. Correspondingly, the first user plane network element receives the second rule.

[0319] This second rule can also be called a QoS rule.

[0320] The second rule is generated by the session management network element based on the PCC rule.

[0321] Corresponding to scenario one in step 202d above, the second rule generated by the session management network element includes a first packet detection rule, a second packet detection rule, a first QoS execution rule corresponding to the first packet detection rule, and a second QoS execution rule corresponding to the second packet detection rule. The first packet detection rule includes information about a first data stream, and the second packet detection rule includes information about a second data stream. The information about the first data stream includes first 5-tuple information, and the information about the second data stream includes second 5-tuple information. The second 5-tuple information is the same as the first 5-tuple information. The first packet detection rule is used to identify the first data stream, and the second packet detection rule is used to identify the second data stream. The first QoS execution rule includes information about a first QoS stream and is used to instruct that the header of the data packets in the first data stream carries the QoS stream identifier of the first QoS stream corresponding to the first data stream. The second QoS execution rule includes information about a second QoS stream and is used to instruct that the header of the data packets in the second data stream carries the QoS stream identifier of the second QoS stream corresponding to the second data stream. The QoS stream identifier of the first QoS stream is different from the QoS stream identifier of the second QoS stream. Upon receiving the second rule, a first user plane network element can map a first data stream and a second data stream with the same five-tuple information to different QoS streams, wherein the first data stream is mapped to a first QoS stream, and the second data stream is mapped to a second QoS stream. Since the QoS stream identifiers of the first and second QoS streams are different, they have different QoS guarantee capabilities, such as different latency and packet loss rates. This method can meet the differentiated QoS requirements of different data streams with the same five-tuple information, thereby improving communication quality. For example, the information of the first data stream in the first packet detection rule includes at least one of the following: a first payload type, a first synchronization source identifier, or a first tag header field, in addition to the first five-tuple information. The information of the second data stream in the second packet detection rule includes at least one of the following: a second payload type, a second synchronization source identifier, or a second tag header field, in addition to the second five-tuple information. In another example, the information of the first data stream in the first packet detection rule includes metadata in addition to the first five-tuple information. The information of the second data stream in the second packet detection rule includes second metadata in addition to the second five-tuple information.

[0322] Corresponding to scenario two in step 202d above, the second rule generated by the session management network element includes a first packet detection rule, a second packet detection rule, a first QoS execution rule corresponding to the first packet detection rule, and a second QoS execution rule corresponding to the second packet detection rule. The first packet detection rule includes information about a first data stream, and the second packet detection rule includes information about a second data stream. The information about the first data stream includes first 5-tuple information, and the information about the second data stream includes second 5-tuple information. The second 5-tuple information is the same as the first 5-tuple information. The first packet detection rule is used to identify the first data stream, and the second packet detection rule is used to identify the second data stream. The first QoS execution rule includes information about a first QoS stream and is used to instruct that the header of the data packets in the first data stream carries the QoS stream identifier of the first QoS stream corresponding to the first data stream. The second QoS execution rule includes information about a second QoS stream and is used to instruct that the header of the data packets in the second data stream carries the QoS stream identifier of the second QoS stream corresponding to the second data stream. The QoS stream identifier of the first QoS stream is the same as the QoS stream identifier of the second QoS stream. Upon receiving the second rule, the first user plane network element can map a first data stream and a second data stream with the same 5-tuple information to the same QoS stream. Specifically, the first data stream is mapped to a first QoS stream, the second data stream is mapped to a second QoS stream, and the first and second QoS streams refer to the same QoS stream. This method can provide corresponding QoS guarantees for different data streams with the same 5-tuple information, thereby improving communication quality.

[0323] Based on the above scheme, the policy control network element determines the PCC rule according to the capability information of the first user plane network element and sends the PCC rule to the session management network element. The session management network element generates a second rule according to the PCC rule and sends the second rule to the first user plane network element. When the first user plane network element has multi-stream processing capabilities, it can map different data streams with the same five-tuple information to different QoS streams for transmission according to the second rule, thereby meeting the differentiated transmission requirements of different data streams and improving communication quality. When the first user plane network element does not have multi-stream processing capabilities, it can still map different data streams with the same five-tuple information to the same QoS stream for transmission according to the second rule, thereby improving communication quality.

[0324] Figure 2(e) is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0325] In step 201e, the session management network element sends the first rule to the terminal. Accordingly, the terminal receives the first rule.

[0326] This first rule can also be called the QoS rule.

[0327] The first rule includes a first packet filter, a second packet filter, information about a first QoS flow corresponding to the first packet filter, and information about a second QoS flow corresponding to the second packet filter. The first packet filter includes information about a first data flow, and the second packet filter includes information about a second data flow. The information about the first data flow includes a first 5-tuple, and the information about the second data flow includes a second 5-tuple. The second 5-tuple is the same as the first 5-tuple. The first packet filter is used to identify the first data flow, and the second packet filter is used to identify the second data flow. The QoS flow identifier in the information about the first QoS flow is different from the QoS flow identifier in the information about the second QoS flow. For example, the QoS flow identifier of the first QoS flow is QFI#1, and the QoS flow identifier of the second QoS flow is QFI#2.

[0328] In one possible implementation, the information of the first data stream in the first packet filter includes not only the first quintuple information but also first information; the information of the second data stream in the second packet filter includes not only the second quintuple information but also second information. The first and second information are different. The first and second information are used to distinguish the first data stream and the second data stream that correspond to the same quintuple information. Based on this method, when it is identified that the information of the first data stream and the information of the second data stream contain the same quintuple information, the first data stream and the second data stream are further distinguished by identifying the first information in the information of the first data stream and the second information in the information of the second data stream, and it is determined that the first data stream and the second data stream are different data streams corresponding to the same quintuple information, thereby achieving correct identification and distinction of different data streams corresponding to the same quintuple information.

[0329] In one possible implementation, the information of the first data stream in the first packet filter includes, in addition to the first 5-tuple information, at least one of a first payload type, a first synchronization source identifier, or a first tag header field. The first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream. For example, the type of the first data stream could be a video stream, an audio stream, or a haptic stream. The information of the second data stream in the second packet filter includes, in addition to the second 5-tuple information, at least one of a second payload type, a second synchronization source identifier, or a second tag header field. The second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream. For example, the type of the second data stream could be a video stream, an audio stream, or a haptic stream. Both the first and second data streams are transmitted via RTP, SRTP, RTCP, or SRTCP. Regarding this implementation method, the terminal possesses multi-stream processing capabilities, which can be understood as follows: the terminal can identify the payload type, synchronization source identifier, or tag header field information in the data stream information, thereby distinguishing different data streams with the same five-tuple information. Here, the first payload type, first synchronization source identifier, or first tag header field information can be understood as a specific example of the aforementioned first information, and the second payload type, second synchronization source identifier, or second tag header field information can be understood as a specific example of the aforementioned second information.

[0330] Since different data streams have different synchronization source identifiers, these identifiers can be used to distinguish different data streams that have the same 5-tuple information. That is, the first synchronization source identifier in the information of the first data stream is different from the second synchronization source identifier in the information of the second data stream. Therefore, the first data stream and the second data stream that have the same 5-tuple information can be distinguished by the first synchronization source identifier and the second synchronization source identifier.

[0331] Because the tag header field information of different data streams is different, this tag header field information can be used to distinguish different data streams with the same 5-tuple information. That is, the first tag header field information in the information of the first data stream is different from the second tag header field information in the information of the second data stream. Therefore, the first data stream and the second data stream with the same 5-tuple information can be distinguished by the first tag header field information and the second tag header field information.

[0332] For example, assuming that the information of data stream #1 includes 5-tuple information #1 and payload type #1, the information of data stream #2 includes 5-tuple information #1 and payload type #1, and the information of data stream #3 includes 5-tuple information #1 and payload type #2, where payload type #1 is a video stream and payload type #2 is an audio stream, then data stream #1 and data stream #2 can both be mapped to QoS stream #1, and data stream #3 can both be mapped to QoS stream #2. Based on this method, QoS mapping at the data stream type granularity can be achieved.

[0333] For example, suppose that the information of data stream #1 includes 5-tuple information #1 and synchronization source identifier #1, the information of data stream #2 includes 5-tuple information #1 and synchronization source identifier #2, and the information of data stream #3 includes 5-tuple information #1 and synchronization source identifier #3, wherein synchronization source identifier #1, synchronization source identifier #2, and synchronization source identifier #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved.

[0334] For example, suppose that the information in data stream #1 includes 5-tuple information #1 and tag header field information #1, the information in data stream #2 includes 5-tuple information #1 and tag header field information #2, and the information in data stream #3 includes 5-tuple information #1 and tag header field information #3, wherein tag header field information #1, tag header field information #2, and tag header field information #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved.

[0335] This application is not limited to any particular application scenario. In addition to RTP application scenarios, it can also be applied to QUIC application scenarios or MoQ application scenarios, etc.

[0336] In one possible implementation, under the MoQ application scenario, the information of the first data stream includes first quintuple information and first metadata, and the information of the second data stream includes second quintuple information and second metadata. The first and second quintuple information are identical, and different metadata corresponds to different data streams. That is, since the metadata in the information of the first and second data streams is different, the first and second data streams with the same quintuple information can be identified based on the first and second metadata. As a specific example, suppose the information of data stream #1 includes quintuple information #1 and metadata #1, the information of data stream #2 includes quintuple information #1 and metadata #2, and the information of data stream #3 includes quintuple information #1 and metadata #3. Metadata #1, metadata #2, and metadata #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved. For example, different data streams can be indicated by target IDs or other information in the metadata, with different target IDs used to indicate different data streams. Here, the first metadata can be understood as a specific example of the aforementioned first information, and the second metadata can be understood as a specific example of the aforementioned second information.

[0337] In step 202e, the terminal sends an indication message to the session management network element. Correspondingly, the session management network element receives the indication message.

[0338] This indication information is used to indicate the terminal's capability information, specifically whether the terminal has multi-stream processing capabilities or not. Multi-stream processing capability can also be referred to as multi-stream mapping capability.

[0339] In one scenario, if the terminal lacks multi-stream processing capabilities, it will not use and / or discard the first rule upon receiving it. Optionally, after receiving indication information indicating that the terminal lacks multi-stream processing capabilities, the session management network element may send a notification message to the policy control network element. This notification message indicates that the QoS information corresponding to the first data stream and the QoS information corresponding to the second data stream failed to update.

[0340] In another scenario, if the terminal possesses multi-stream processing capabilities, after receiving the first rule, the terminal can subsequently use this first rule to map different data streams with the same five-tuple information to different QoS streams for transmission. Optionally, after receiving the indication information indicating that the terminal possesses multi-stream processing capabilities, the session management network element can send a notification message to the policy control network element. This notification message indicates that the QoS information corresponding to the first data stream and the QoS information corresponding to the second data stream have been successfully updated.

[0341] Based on the above scheme, when the terminal has multi-stream processing capabilities, the terminal can map different data streams with the same five-tuple information to different QoS streams for transmission according to the first rule, so as to meet the differentiated transmission requirements of different data streams.

[0342] Figure 2(f) is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0343] In step 201f, the session management network element sends the second rule to the first user plane network element. Correspondingly, the first user plane network element receives the second rule.

[0344] This second rule can also be called the N4 rule.

[0345] The second rule includes a first packet detection rule, a second packet detection rule, a first QoS enforcement rule corresponding to the first packet detection rule, information about the first QoS flow, and a second QoS enforcement rule corresponding to the second packet detection rule. The first packet detection rule includes information about the first data flow, and the second packet detection rule includes information about the second data flow. The information about the first data flow includes first 5-tuple information, and the information about the second data flow includes second 5-tuple information. The second 5-tuple information is the same as the first 5-tuple information. The first packet detection rule is used to identify the first data flow, and the second packet detection rule is used to identify the second data flow. The first QoS enforcement rule includes information about the first QoS flow and is used to instruct that the header of the data packets in the first data flow carries the QoS flow identifier of the first QoS flow corresponding to the first data flow. The second QoS enforcement rule includes information about the second QoS flow and is used to instruct that the header of the data packets in the second data flow carries the QoS flow identifier of the second QoS flow corresponding to the second data flow. The QoS flow identifier of the first QoS flow is different from that of the second QoS flow. For example, the QoS flow identifier of the first QoS flow is QFI#1, and the QoS flow identifier of the second QoS flow is QFI#2.

[0346] Upon receiving the second rule, the first user plane network element can map a first data stream and a second data stream with the same five-tuple information to different QoS streams. Specifically, the first data stream is mapped to the first QoS stream, and the second data stream is mapped to the second QoS stream. Since the QoS stream identifiers of the first and second QoS streams are different, they possess different QoS guarantee capabilities, such as different latency and packet loss rates. This method can satisfy the differentiated QoS requirements of different data streams with the same five-tuple information, thereby improving communication quality.

[0347] In one possible implementation, the information of the first data stream in the first packet detection rule includes not only the first quintuple information but also first information; similarly, the information of the second data stream in the second packet detection rule includes not only the second quintuple information but also second information. The first and second information are different. The first and second information are used to distinguish between the first and second data streams that correspond to the same quintuple information. Based on this method, when the information of the first and second data streams is identified to contain the same quintuple information, the first and second data streams are further distinguished by identifying the first information in the first data stream and the second information in the second data stream, thus determining that the first and second data streams are different data streams corresponding to the same quintuple information, thereby correctly identifying and distinguishing different data streams corresponding to the same quintuple information.

[0348] In one possible implementation, the information of the first data stream in the first packet detection rule includes, in addition to the first 5-tuple information, at least one of a first payload type, a first synchronization source identifier, or a first tag header field. The first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream. For example, the type of the first data stream could be a video stream, an audio stream, or a haptic stream. The information of the second data stream in the second packet detection rule includes, in addition to the second 5-tuple information, at least one of a second payload type, a second synchronization source identifier, or a second tag header field. The second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream. For example, the type of the second data stream could be a video stream, an audio stream, or a haptic stream. Both the first and second data streams are transmitted via RTP, SRTP, RTCP, or SRTCP. Regarding this implementation method, the first user plane network element possesses multi-stream processing capabilities, which can be understood as follows: the first user plane network element can identify the payload type, synchronization source identifier, or tag header field information in the data stream information, thereby distinguishing different data streams with the same five-tuple information. Here, the first payload type, first synchronization source identifier, or first tag header field information can be understood as specific examples of the aforementioned first information, and the second payload type, second synchronization source identifier, or second tag header field information can be understood as specific examples of the aforementioned second information.

[0349] Since different data streams have different synchronization source identifiers, these identifiers can be used to distinguish different data streams that have the same 5-tuple information. That is, the first synchronization source identifier in the information of the first data stream is different from the second synchronization source identifier in the information of the second data stream. Therefore, the first data stream and the second data stream that have the same 5-tuple information can be distinguished by the first synchronization source identifier and the second synchronization source identifier.

[0350] Because the tag header field information of different data streams is different, this tag header field information can be used to distinguish different data streams with the same 5-tuple information. That is, the first tag header field information in the information of the first data stream is different from the second tag header field information in the information of the second data stream. Therefore, the first data stream and the second data stream with the same 5-tuple information can be distinguished by the first tag header field information and the second tag header field information.

[0351] For example, assuming that the information of data stream #1 includes 5-tuple information #1 and payload type #1, the information of data stream #2 includes 5-tuple information #1 and payload type #1, and the information of data stream #3 includes 5-tuple information #1 and payload type #2, where payload type #1 is a video stream and payload type #2 is an audio stream, then data stream #1 and data stream #2 can both be mapped to QoS stream #1, and data stream #3 can both be mapped to QoS stream #2. Based on this method, QoS mapping at the data stream type granularity can be achieved.

[0352] For example, suppose that the information of data stream #1 includes 5-tuple information #1 and synchronization source identifier #1, the information of data stream #2 includes 5-tuple information #1 and synchronization source identifier #2, and the information of data stream #3 includes 5-tuple information #1 and synchronization source identifier #3, wherein synchronization source identifier #1, synchronization source identifier #2, and synchronization source identifier #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved.

[0353] For example, suppose that the information in data stream #1 includes 5-tuple information #1 and tag header field information #1, the information in data stream #2 includes 5-tuple information #1 and tag header field information #2, and the information in data stream #3 includes 5-tuple information #1 and tag header field information #3, wherein tag header field information #1, tag header field information #2, and tag header field information #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved.

[0354] This application is not limited to any particular application scenario. In addition to RTP application scenarios, it can also be applied to QUIC application scenarios or MoQ application scenarios, etc.

[0355] In one possible implementation, under the MoQ application scenario, the information of the first data stream includes first quintuple information and first metadata, and the information of the second data stream includes second quintuple information and second metadata. The first and second quintuple information are identical, and different metadata corresponds to different data streams. That is, since the metadata in the information of the first and second data streams is different, the first and second data streams with the same quintuple information can be identified based on the first and second metadata. As a specific example, suppose the information of data stream #1 includes quintuple information #1 and metadata #1, the information of data stream #2 includes quintuple information #1 and metadata #2, and the information of data stream #3 includes quintuple information #1 and metadata #3. Metadata #1, metadata #2, and metadata #3 are all different. Then, data stream #1 can be mapped to QoS stream #1, data stream #2 can be mapped to QoS stream #2, and data stream #3 can be mapped to QoS stream #3. Based on this method, QoS mapping at the data stream granularity can be achieved. For example, different data streams can be indicated by target IDs or other information in the metadata, with different target IDs used to indicate different data streams. Here, the first metadata can be understood as a specific example of the aforementioned first information, and the second metadata can be understood as a specific example of the aforementioned second information.

[0356] In step 202f, the first user plane network element sends an indication message to the session management network element. Correspondingly, the session management network element receives the indication message.

[0357] This indication information is used to indicate the capability information of the first user plane network element. This capability information indicates whether the first user plane network element has multi-stream processing capability or not. Multi-stream processing capability can also be referred to as multi-stream mapping capability.

[0358] In one scenario, if the first user plane network element lacks multi-stream processing capabilities, it will not use and / or discard the second rule upon receiving it. Optionally, after receiving the indication that the first user plane network element lacks multi-stream processing capabilities, the session management network element may send a notification message to the policy control network element. This notification message indicates that the QoS information corresponding to the first data stream and the QoS information corresponding to the second data stream failed to update.

[0359] In another scenario, if the first user plane network element possesses multi-stream processing capabilities, after receiving the second rule, it can subsequently use this second rule to map different data streams with the same five-tuple information to different QoS streams for transmission. Optionally, after receiving the indication information indicating that the first user plane network element possesses multi-stream processing capabilities, the session management network element can send a notification message to the policy control network element. This notification message indicates that the QoS information corresponding to the first data stream and the QoS information corresponding to the second data stream have been successfully updated.

[0360] Based on the above scheme, when the first user plane network element has multi-stream processing capabilities, the first user plane network element can map different data streams with the same five-tuple information to different QoS streams for transmission according to the second rule, so as to meet the differentiated transmission requirements of different data streams.

[0361] Figure 2(g) is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0362] Step 201g: The application function network element sends a QoS update request.

[0363] For example, the application function network element can send a QoS update request to the policy control network element, and the policy control network element can send a QoS update request to the session management network element.

[0364] The QoS update request includes flow description information for a first data stream, transmission requirements for the first data stream, flow description information for a second data stream, and transmission requirements for the second data stream. Specifically, the flow description information for the first data stream includes a first 5-tuple, and the flow description information for the second data stream includes a second 5-tuple. The second 5-tuple is identical to the first 5-tuple, meaning the first and second data streams have the same 5-tuple information. The transmission requirements for the first and second data streams are different, meaning the first and second data streams have different transmission requirements.

[0365] In one possible implementation, the flow description information of the first data stream includes not only the first quintuple information but also first information; similarly, the flow description information of the second data stream in the second packet detection rule includes not only the second quintuple information but also second information. The first and second information are different. The first and second information are used to distinguish between the first and second data streams that correspond to the same quintuple information. Based on this method, when the same quintuple information is detected in the flow description information of the first and second data streams, the first and second data streams are further distinguished by identifying the first information in the first flow description information and the second information in the second flow description information, thus determining that the first and second data streams are different data streams corresponding to the same quintuple information, thereby correctly identifying and distinguishing different data streams corresponding to the same quintuple information.

[0366] In one possible implementation, the stream description information of the first data stream includes, in addition to the first 5-tuple information, at least one of a first payload type, a first synchronization source identifier, or a first tag header field. The first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream. For example, the type of the first data stream could be a video stream, an audio stream, or a haptic stream. The information of the second data stream includes, in addition to the second 5-tuple information, at least one of a second payload type, a second synchronization source identifier, or a second tag header field. The second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream. For example, the type of the second data stream could be a video stream, an audio stream, or a haptic stream. Both the first and second data streams are transmitted via RTP, SRTP, RTCP, or SRTCP. Regarding this implementation method, the terminal or user plane network element possesses multi-stream processing capabilities, which can be understood as follows: the terminal or user plane network element can identify the payload type, synchronization source identifier, or tag header field information in the data stream information, so as to distinguish different data streams with the same five-tuple information. Here, the first payload type, first synchronization source identifier, or first tag header field information can be understood as a specific example of the aforementioned first information, and the second payload type, second synchronization source identifier, or second tag header field information can be understood as a specific example of the aforementioned second information.

[0367] Since different data streams have different synchronization source identifiers, these identifiers can be used to distinguish different data streams that have the same 5-tuple information. That is, the first synchronization source identifier in the stream description information of the first data stream is different from the second synchronization source identifier in the information of the second data stream. Therefore, the first data stream and the second data stream that have the same 5-tuple information can be distinguished by the first synchronization source identifier and the second synchronization source identifier.

[0368] Because the tag header field information differs between different data streams, this tag header field information can be used to distinguish different data streams with the same 5-tuple information. That is, the first tag header field information in the stream description information of the first data stream is different from the second tag header field information in the information of the second data stream. Therefore, the first data stream and the second data stream with the same 5-tuple information can be distinguished by the first tag header field information and the second tag header field information.

[0369] This application is not limited to any particular application scenario. In addition to RTP application scenarios, it can also be applied to QUIC application scenarios or MoQ application scenarios, etc.

[0370] In one possible implementation, within the MoQ application scenario, the flow description information of the first data stream includes first 5-tuple information and first metadata, while the information of the second data stream includes second 5-tuple information and second metadata. The first and second 5-tuple information are identical, and different metadata corresponds to different data streams. That is, since the metadata in the flow description information of the first data stream and the information of the second data stream are different, the first and second data streams with the same 5-tuple information can be identified based on the first and second metadata. For example, different data streams can be indicated by target IDs or other information in the metadata, with different target IDs indicating different data streams. Here, the first metadata can be understood as a specific example of the aforementioned first information, and the second metadata can be understood as a specific example of the aforementioned second information.

[0371] Step 202g: The application function network element receives the notification message.

[0372] The notification message is used to indicate that the QoS information corresponding to the first data stream and the QoS information corresponding to the second data stream failed to be updated. The notification message includes a reason value, which indicates that the reason for the update failure is that the terminal does not have multi-stream processing capability and / or the user plane network element does not have multi-stream processing capability.

[0373] For example, the session management network element sends a notification message to the policy control network element, which then sends a notification message to the application function network element.

[0374] Step 203g: The application function network element determines different quintuple information for the first data stream and the second data stream.

[0375] For example, if the 5-tuple information of the first data stream and the 5-tuple information of the second data stream are both 5-tuple information #1, and the application function network element learns from the notification message that the terminal does not have multi-stream processing capability and / or the user plane network element does not have multi-stream processing capability, then it will not update the 5-tuple information of the first data stream but will update the 5-tuple information of the second data stream to 5-tuple information #2, or it will not update the 5-tuple information of the second data stream but will update the 5-tuple information of the first data stream to 5-tuple information #3, or it will update the 5-tuple information of the first data stream to 5-tuple information #2 and update the 5-tuple information of the second data stream to 5-tuple information #3.

[0376] Based on the above scheme, when the application function network element determines that the terminal does not have multi-stream processing capability and / or the user plane network element does not have multi-stream processing capability, it can determine different five-tuple information for the first data stream and the second data stream. This can enable different uplink or downlink data streams with different five-tuple information to be mapped to different QoS streams for transmission, so as to meet the differentiated transmission requirements of different data streams.

[0377] The above embodiments are illustrated by taking two data streams with the same quintuple information as examples. This application is not limited to only two data streams, and can also process three or more data streams with the same quintuple information. The processing method is similar to the above embodiments and will not be repeated.

[0378] As an implementation method, any 5-tuple information appearing anywhere in this application can also be replaced with 3-tuple information, namely, source IP address, source port number, and protocol number.

[0379] The embodiments shown in Figures 2(a) to 2(f) will be described in detail below with reference to the accompanying drawings. The embodiments shown in Figures 3 to 9 below are specific examples of the embodiments shown in Figures 2(a) to 2(f). In the embodiments shown in Figures 3 to 9 below, the aforementioned user plane network element, mobility management network element, session management network element, application function network element, and policy control network element are described as UPF, AMF, SMF, AF, and PCF, respectively.

[0380] Figure 3 is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0381] Step 301: The terminal sends a NAS message to the AMF through the access network device. Correspondingly, the AMF receives the NAS message.

[0382] The NAS message includes a PDU session establishment request and indication information, which indicates that the terminal has multi-stream processing capabilities.

[0383] This PDU session establishment request is used to request the establishment of a PDU session. The PDU session establishment request includes this indication information.

[0384] Step 302, AMF selects SMF.

[0385] For example, the AMF selects the SMF based on the instruction information. That is, the AMF selects the appropriate SMF based on the terminal's capability information.

[0386] Step 303: The AMF initiates a PDU session establishment request to the SMF. Accordingly, the SMF receives the PDU session establishment request.

[0387] The PDU session establishment request includes indication information that indicates the terminal has multi-stream processing capabilities.

[0388] Step 304: The SMF sends a PDU session establishment response to the AMF. Correspondingly, the AMF receives the PDU session establishment response.

[0389] Step 305: SMF selects a UPF with multi-stream processing capabilities.

[0390] For example, SMF has information on multiple UPFs locally configured, and the information of each UPF can be used to indicate whether the UPF has multi-stream processing capabilities. SMF selects a UPF with multi-stream processing capabilities based on the information of these multiple UPFs.

[0391] UPF has multi-stream processing capabilities, which means that UPF can identify different data streams that correspond to the same 5-tuple information and can map different data streams to different QoS streams for transmission.

[0392] Step 306: The SMF sends the N4 rule to the UPF. The UPF then receives the N4 rule.

[0393] The N4 rule includes multiple packet inspection rules and a corresponding QoS enforcement rule for each packet inspection rule. The packet inspection rule identifies data flows requiring processing, and the corresponding QoS enforcement rule carries the QoS information for that data flow in the header of the data packets. Furthermore, the different data flows identified by these multiple packet inspection rules share the same 5-tuple information.

[0394] For example, rule N4 includes a first packet detection rule and a first QoS enforcement rule corresponding to a first data stream, and a second packet detection rule and a second QoS enforcement rule corresponding to a second data stream. The first packet detection rule includes information about the first data stream, including 5-tuple information. This first packet detection rule is used to identify the first data stream, and the first QoS enforcement rule is used to instruct that the header of packets in the first data stream carry information about the first QoS stream corresponding to the first data stream. Similarly, the second packet detection rule includes information about the second data stream, including 5-tuple information. This second packet detection rule is used to identify the second data stream, and the second QoS enforcement rule is used to instruct that the header of packets in the second data stream carry information about the second QoS stream corresponding to the second data stream. The 5-tuple information included in the first data stream is the same as that included in the second data stream.

[0395] Here, data stream refers to downlink data stream, and QoS stream refers to downlink QoS stream.

[0396] UPF possesses multi-stream processing capabilities, thus it can identify different data streams corresponding to the same 5-tuple information and map these different data streams to different QoS streams for transmission. Therefore, this UPF can identify different data streams corresponding to the same 5-tuple information based on the N4 rule and map these different data streams to different QoS streams for transmission.

[0397] Step 307: The SMF sends the QoS configuration to the access network device. Correspondingly, the access network device receives the QoS configuration.

[0398] This QoS configuration includes QFI and a series of QoS parameters.

[0399] Access network devices configure radio resource control (RRC) and air interface resources with terminals based on QoS configuration.

[0400] Step 308: The SMF sends QoS rules to the terminal. Correspondingly, the access network device receives the QoS rules.

[0401] This QoS rule includes multiple packet filters and information on multiple QoS flows, with each packet filter corresponding one-to-one with the information on the multiple QoS flows. Each packet filter includes information on a data flow, used to identify that data flow. The information on all data flows includes the same 5-tuple information. The information on all QoS flows includes different QoS flow identifiers. For example, the QoS rule includes a first packet filter, a second packet filter, information on the first QoS flow corresponding to the first packet filter, and information on the second QoS flow corresponding to the second packet filter. The first packet filter includes information on the first data flow, and the second packet filter includes information on the second data flow. The information on the first data flow includes first 5-tuple information, and the information on the second data flow includes second 5-tuple information, which is identical to the first 5-tuple information. The first packet filter identifies the first data flow, and the second packet filter identifies the second data flow. The QoS flow identifiers in the information on the first QoS flow and the information on the second QoS flow are different. For example, the QoS flow identifier for the first QoS flow is QFI#1, and the QoS flow identifier for the second QoS flow is QFI#2. Because the terminal has multi-stream processing capabilities, it can identify different data streams with the same 5-tuple information and map them to different QoS streams for transmission. Therefore, the terminal can identify different data streams with the same 5-tuple information based on QoS rules and map them to different QoS streams for transmission.

[0402] Here, data stream refers to uplink data stream, and QoS stream refers to uplink QoS stream.

[0403] Based on the above scheme, the session management network element sends QoS rules to the terminal. According to these QoS rules, the terminal can map different uplink data streams with the same five-tuple information to different QoS streams for transmission, thereby meeting the differentiated transmission requirements of different data streams and improving communication quality. The session management network element sends N4 rules to the UPF. According to these QoS rules, the UPF can map different downlink data streams with the same five-tuple information to different QoS streams for transmission, also meeting the differentiated transmission requirements of different data streams.

[0404] Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0405] Step 401: The AF sends a QoS update request to the NEF. Correspondingly, the NEF receives the QoS update request.

[0406] The QoS update request includes flow description information for multiple data streams and the transmission requirements for each of these data streams. All of these data streams are downlink data streams.

[0407] The stream description information for each of the multiple data streams includes, for example, a 5-tuple. Optionally, the stream description information for each data stream also includes at least one of a payload type, a synchronization source identifier, or a tag header field. The payload type indicates the type of data stream, such as an audio stream, a video stream, or a haptic stream, while the synchronization source identifier identifies the synchronization source. Since different data streams have different synchronization source identifiers, this identifier can be used to distinguish different data streams with the same 5-tuple information. The tag header field indicates the header information of a second data stream. Since different data streams have different tag header field information, this tag header field can be used to distinguish different data streams with the same 5-tuple information.

[0408] The transmission requirements for each data stream include, for example, latency requirements and packet loss rate requirements.

[0409] For example, the QoS update request includes flow description information for data flow #1, transmission requirement #1 for data flow #1, flow description information for data flow #2, transmission requirement #2 for data flow #2, flow description information for data flow #3, and transmission requirement #3 for data flow #3.

[0410] For example, the QoS update request could be an Nnef_AFsessionWithQoS update request.

[0411] Step 402: NEF authenticates the QoS update request initiated by AF.

[0412] Step 403: After successfully authenticating the QoS update request, the NEF sends a policy update request to the PCF. The PCF then receives the policy update request.

[0413] The policy update request includes flow description information for multiple data streams and the transmission requirements for each of those data streams.

[0414] For example, the policy update request could be an Npcf_PolicyAuthorization update request.

[0415] In step 404, the PCF sends a policy update response to the NEF. Correspondingly, the NEF receives the policy update response.

[0416] In step 405, the NEF sends a QoS update response to the AF. Correspondingly, the AF receives the QoS update response.

[0417] Step 406: The PCF sends the PCC rule to the SMF. Correspondingly, the SMF receives the PCC rule.

[0418] The PCC rule is used to indicate information about multiple data streams and the QoS stream information corresponding to each of the multiple data streams. The QoS stream information includes QoS parameter requirements and / or QoS stream identifiers.

[0419] Step 407: SMF determines whether UPF has multi-stream processing capabilities.

[0420] SMF triggers a determination of whether UPF has multi-stream processing capabilities based on at least one of the payload type, synchronization source identifier, or tag header field information in the data stream information indicated by the PCC rule.

[0421] In one possible implementation, the SMF is locally configured with UPF capability information, which indicates whether the UPF has multi-stream processing capabilities. Therefore, the SMF can determine whether the UPF has multi-stream processing capabilities based on the UPF capability information.

[0422] If the UPF has multi-stream processing capabilities, then step 408 is executed after step 407. If the UPF does not have multi-stream processing capabilities, then steps 409 to 410 are executed after step 407.

[0423] Step 408: If the UPF has multi-stream processing capabilities, the SMF sends the N4 rule to the UPF. Correspondingly, the UPF receives the N4 rule.

[0424] The N4 rule is generated by SMF based on the PCC rule. The N4 rule is used to map different data streams with the same 5-tuple information to different QoS streams for transmission.

[0425] For details regarding the N4 rule, please refer to the description in step 306 above.

[0426] Step 409: If the UPF does not have multi-stream processing capabilities, the SMF sends a notification message to the PCF. Correspondingly, the PCF receives the notification message.

[0427] This notification message is used to indicate that the QoS information update for the corresponding data stream failed. Optionally, the notification message includes a reason value, which indicates that the reason for the update failure is that the UPF does not have multi-stream processing capabilities.

[0428] In step 410, the PCF sends a notification message to the AF. Correspondingly, the AF receives the notification message.

[0429] This notification message is used to indicate that the QoS information update for the corresponding data stream failed. Optionally, the notification message includes a reason value, which indicates that the reason for the update failure is that the UPF does not have multi-stream processing capabilities.

[0430] After receiving the notification message, the AF updates the information of multiple data streams with the same 5-tuple information. For example, it modifies the 5-tuple information corresponding to the same data streams to different 5-tuple information, thereby mapping the multiple data streams to different QoS streams for transmission. This achieves differentiated transmission protection based on the transmission requirements of different data streams and uses corresponding QoS streams. Specifically, the AF can initiate a QoS update request to the PCF. This QoS update request requests the modification of the 5-tuple information corresponding to the same data streams to different 5-tuple information. Then, the PCF generates PCC rules based on the QoS update request, and the SMF generates N4 rules based on the PCC rules and sends the N4 rules to the UPF. Based on the N4 rules, the UPF can map different data streams with different 5-tuple information to different QoS streams.

[0431] It should be noted that in another implementation method, when the UPF does not have multi-stream processing capabilities, steps 409 to 410 above can be omitted. Instead, the SMF sends another N4 rule to the UPF. This N4 rule is used to map different data streams with the same quintuple information to different QoS streams for transmission. This N4 rule includes multiple packet detection rules and multiple QoS enforcement rules, with each packet detection rule corresponding to one of the QoS enforcement rules. For example, the N4 rule includes a first packet detection rule, a second packet detection rule, a first QoS enforcement rule corresponding to the first packet detection rule, and a second QoS enforcement rule corresponding to the second packet detection rule. The first packet detection rule includes information about the first data stream, and the second packet detection rule includes information about the second data stream. The information about the first data stream includes first quintuple information, and the information about the second data stream includes second quintuple information, which is identical to the first quintuple information. The first packet detection rule is used to identify the first data stream, and the second packet detection rule is used to identify the second data stream. The first QoS enforcement rule includes information about a first QoS flow. This rule instructs that the header of data packets in the first data flow carry the QoS flow identifier of the first QoS flow corresponding to the first data flow. The second QoS enforcement rule includes information about a second QoS flow. This rule instructs that the header of data packets in the second data flow carry the QoS flow identifier of the second QoS flow corresponding to the second data flow. The QoS flow identifiers of the first and second QoS flows are the same. For example, the QoS flow identifier of the first QoS flow is QFI#1, and the QoS flow identifier of the second QoS flow is also QFI#1. UPF can map a first data flow and a second data flow with the same five-tuple information to the same QoS flow according to the N4 rule. Specifically, the first data flow is mapped to the first QoS flow, the second data flow is mapped to the second QoS flow, and the first and second QoS flows refer to the same QoS flow. This method can provide corresponding QoS guarantees for different data flows with the same five-tuple information, thereby improving communication quality.

[0432] Based on the above scheme, if the UPF has multi-stream processing capabilities, the SMF sends an N4 rule to the UPF. The UPF then uses the N4 rule to map different downlink data streams with the same 5-tuple information to different QoS streams for transmission, thus meeting the differentiated transmission requirements of different data streams and improving communication quality. If the UPF does not have multi-stream processing capabilities, the SMF sends a notification message to the AF. The AF then uses the notification message to determine different 5-tuple information for different data streams with the same 5-tuple information, thereby mapping different downlink data streams with different 5-tuple information to different QoS streams for transmission, meeting the differentiated transmission requirements of different data streams and improving communication quality. Alternatively, if the UPF does not have multi-stream processing capabilities, the SMF sends an N4 rule, and the UPF uses the N4 rule to map different downlink data streams with the same 5-tuple information to the same QoS stream for transmission, thus improving communication quality.

[0433] Figure 5 is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0434] Steps 501 to 506 are the same as steps 401 to 406 in the embodiment of Figure 4.

[0435] Step 507: The SMF sends the N4 rule to the UPF. The UPF then receives the N4 rule.

[0436] The N4 rule is generated by SMF based on the PCC rule.

[0437] For details regarding the N4 rule, please refer to the description in step 306 above. The N4 rule is used to map different data streams with the same 5-tuple information to different QoS streams for transmission.

[0438] In step 508, the UPF sends an indication message to the SMF. The SMF then receives the indication message.

[0439] This indication information is used to indicate whether the UPF has multi-stream processing capabilities or not.

[0440] Specifically, if the UPF has multi-stream processing capabilities, it can use the received N4 rule to map different data streams with the same 5-tuple information to different QoS streams for transmission. If the UPF does not have multi-stream processing capabilities, the N4 rule is not used.

[0441] Optionally, if the indication information is used to indicate that the UPF does not have multi-stream processing capabilities, then steps 509 to 510 are also executed after step 508.

[0442] Step 509: If the UPF does not have multi-stream processing capabilities, the SMF sends a notification message to the PCF. Correspondingly, the PCF receives the notification message.

[0443] This notification message is used to indicate that the QoS information update for the corresponding data stream failed. Optionally, the notification message includes a reason value, which indicates that the reason for the update failure is that the UPF does not have multi-stream processing capabilities.

[0444] In step 510, the PCF sends a notification message to the AF. Correspondingly, the AF receives the notification message.

[0445] This notification message is used to indicate that the QoS information update for the corresponding data stream failed. Optionally, the notification message includes a reason value, which indicates that the reason for the update failure is that the UPF does not have multi-stream processing capabilities.

[0446] After receiving the notification message, the AF updates the information of multiple data streams with the same 5-tuple information. For example, it modifies the 5-tuple information corresponding to the same data streams to different 5-tuple information, thereby mapping the multiple data streams to different QoS streams for transmission. This achieves differentiated transmission protection based on the transmission requirements of different data streams and uses corresponding QoS streams. Specifically, the AF can initiate a QoS update request to the PCF. This QoS update request requests the modification of the 5-tuple information corresponding to the same data streams to different 5-tuple information. Then, the PCF generates PCC rules based on the QoS update request, and the SMF generates N4 rules based on the PCC rules and sends the N4 rules to the UPF. Based on the N4 rules, the UPF can map different data streams with different 5-tuple information to different QoS streams.

[0447] Based on the above scheme, the SMF sends N4 rules to the UPF. The UPF, according to the N4 rules, maps different downlink data streams with the same quintuple information to different QoS streams for transmission, thus meeting the differentiated transmission requirements of different data streams. The UPF also sends indication information to the SMF to indicate whether it has multi-stream processing capabilities. If the UPF does not have multi-stream processing capabilities, the SMF sends a notification message to the AF. The AF, based on the notification message, determines different quintuple information for different data streams with the same quintuple information, thereby enabling the mapping of different downlink data streams with different quintuple information to different QoS streams for transmission, meeting the differentiated transmission requirements of different data streams.

[0448] Figure 6 is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0449] Step 601: The AF sends a QoS update request to the NEF. Correspondingly, the NEF receives the QoS update request.

[0450] The QoS update request includes flow description information for multiple data streams and the transmission requirements for each of these data streams. All of these data streams are uplink data streams.

[0451] The stream description information for each of the multiple data streams includes, for example, a 5-tuple. Optionally, the stream description information for each data stream also includes at least one of a payload type, a synchronization source identifier, or a tag header field. The payload type indicates the type of data stream, such as an audio stream, a video stream, or a haptic stream, while the synchronization source identifier identifies the synchronization source. Since different data streams have different synchronization source identifiers, this identifier can be used to distinguish different data streams with the same 5-tuple information. The tag header field indicates the header information of a second data stream. Since different data streams have different tag header field information, this tag header field can be used to distinguish different data streams with the same 5-tuple information.

[0452] The transmission requirements for each data stream include, for example, latency requirements and packet loss rate requirements.

[0453] For example, the QoS update request includes flow description information for data flow #1, transmission requirement #1 for data flow #1, flow description information for data flow #2, transmission requirement #2 for data flow #2, flow description information for data flow #3, and transmission requirement #3 for data flow #3.

[0454] For example, the QoS update request could be an Nnef_AFsessionWithQoS update request.

[0455] Step 602: NEF authenticates the QoS update request initiated by AF.

[0456] Step 603: After successfully authenticating the QoS update request, the NEF sends a policy update request to the PCF. The PCF then receives the policy update request.

[0457] The policy update request includes information about multiple data streams and the transmission requirements for each of those data streams.

[0458] For example, the policy update request could be an Npcf_PolicyAuthorization update request.

[0459] In step 604, the PCF sends a policy update response to the NEF. Correspondingly, the NEF receives the policy update response.

[0460] In step 605, the NEF sends a QoS update response to the AF. Correspondingly, the AF receives the QoS update response.

[0461] Step 606: The PCF sends the PCC rule to the SMF. Correspondingly, the SMF receives the PCC rule.

[0462] The PCC rule is used to indicate information about multiple data streams and the information of the stream corresponding to each of the multiple data streams. The QoS stream information includes QoS parameter requirements and / or QoS stream identifiers.

[0463] Step 607: SMF determines whether the terminal has multi-stream processing capabilities.

[0464] Based on at least one of the payload type, synchronization source identifier, or tag header field information in the data stream information indicated by the PCC rule, the SMF triggers the SMF to determine whether the terminal has multi-stream processing capabilities.

[0465] In one possible implementation, the SMF can obtain the terminal's capability information from the UDM or NRF, or obtain the terminal's capability information from the terminal itself. This capability information indicates whether the terminal has multi-stream processing capabilities. Therefore, the SMF can determine whether the terminal has multi-stream processing capabilities based on the terminal's capability information.

[0466] If the terminal has multi-stream processing capabilities, then step 608 is executed after step 607. If the terminal does not have multi-stream processing capabilities, then steps 609 to 610 are executed after step 607.

[0467] Step 608: If the terminal has multi-stream processing capabilities, the SMF sends QoS rules to the terminal. Correspondingly, the terminal receives the QoS rules.

[0468] This QoS rule is generated by SMF based on the PCC rule. This QoS rule is used to map different data streams with the same 5-tuple information to different QoS streams for transmission.

[0469] For details regarding the N4 rule, please refer to the description in step 308 above.

[0470] Step 609: If the terminal does not have multi-stream processing capabilities, the SMF sends a notification message to the PCF. Correspondingly, the PCF receives the notification message.

[0471] This notification message is used to indicate that the QoS information update for the corresponding data stream failed. Optionally, the notification message includes a reason value, which indicates that the reason for the update failure is that the terminal does not have multi-stream processing capabilities.

[0472] In step 610, the PCF sends a notification message to the AF. Correspondingly, the AF receives the notification message.

[0473] This notification message is used to indicate that the QoS information update for the corresponding data stream failed. Optionally, the notification message includes a reason value, which indicates that the reason for the update failure is that the terminal does not have multi-stream processing capabilities.

[0474] After receiving the notification message, the AF updates the information of multiple data streams with the same 5-tuple information. For example, it modifies the 5-tuple information corresponding to the same data streams to different 5-tuple information, thereby mapping the multiple data streams to different QoS streams for transmission. This achieves differentiated transmission protection based on the transmission requirements of different data streams and uses corresponding QoS streams. Specifically, the AF can initiate a QoS update request to the PCF. This QoS update request requests the modification of the 5-tuple information corresponding to the same data streams to different 5-tuple information. Then, the PCF generates PCC rules based on the QoS update request, the SMF generates QoS rules based on the PCC rules, and sends the QoS rules to the terminal. Based on these QoS rules, the terminal can map different data streams with different 5-tuple information to different QoS streams.

[0475] It should be noted that in another implementation method, when the terminal does not have multi-stream processing capabilities, steps 609 to 610 above can be omitted. Instead, the SMF sends another QoS rule to the terminal. This QoS rule includes multiple packet filters and information on multiple QoS flows, with each packet filter corresponding one-to-one with the information on the multiple QoS flows. Each packet filter includes information on a data flow, used to identify that data flow. The information on the multiple data flows includes the same 5-tuple information. The information on the multiple QoS flows includes the same QoS flow identifier. For example, the QoS rule includes a first packet filter, a second packet filter, information on a first QoS flow corresponding to the first packet filter, and information on a second QoS flow corresponding to the second packet filter. The first packet filter includes information on a first data flow, and the second packet filter includes information on a second data flow. The information on the first data flow includes first 5-tuple information, and the information on the second data flow includes second 5-tuple information, which is identical to the first 5-tuple information. The first packet filter is used to identify the first data flow, and the second packet filter is used to identify the second data flow. The QoS flow identifier in the information on the first QoS flow is identical to the QoS flow identifier in the information on the second QoS flow. For example, the QoS stream identifier for the first QoS stream is QFI#1, and the QoS stream identifier for the second QoS stream is also QFI#1. Since the terminal lacks multi-stream processing capabilities, it cannot map different data streams to different QoS streams for transmission. Therefore, the terminal can map different data streams to the same QoS stream for transmission based on QoS rules.

[0476] Based on the above scheme, if the terminal has multi-stream processing capabilities, the SMF sends QoS rules to the terminal. The terminal then maps different uplink data streams with the same 5-tuple information to different QoS streams for transmission according to the QoS rules, thus meeting the differentiated transmission requirements of different data streams and improving communication quality. If the terminal does not have multi-stream processing capabilities, the SMF sends a notification message to the AF. The AF determines different 5-tuple information for different data streams with the same 5-tuple information based on the notification message, thereby mapping different uplink data streams with different 5-tuple information to different QoS streams for transmission, meeting the differentiated transmission requirements of different data streams and improving communication quality. Alternatively, if the terminal does not have multi-stream processing capabilities, the SMF sends QoS rules, and the terminal maps different downlink data streams with the same 5-tuple information to the same QoS stream for transmission according to the QoS rules, thus improving communication quality.

[0477] Figure 7 is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0478] Steps 701 to 706 are the same as steps 601 to 606 in the embodiment of Figure 6.

[0479] Step 707: The SMF sends QoS rules to the terminal. Correspondingly, the terminal receives the QoS rules.

[0480] This QoS rule is generated by SMF based on the PCC rule. This QoS rule is used to map different data streams with the same 5-tuple information to different QoS streams for transmission.

[0481] For details regarding the N4 rule, please refer to the description in step 308 above.

[0482] Step 708: The terminal sends indication information to the SMF. Accordingly, the SMF receives the indication information.

[0483] This indication information is used to indicate whether the terminal has multi-stream processing capabilities or not.

[0484] Specifically, when a terminal has multi-stream processing capabilities, it can use the received QoS rules to map different data streams with the same 5-tuple information to different QoS streams for transmission. When a terminal does not have multi-stream processing capabilities, it will not use these QoS rules.

[0485] Optionally, if the indication information is used to indicate that the terminal does not have multi-stream processing capability, then steps 709 to 710 are also executed after step 708.

[0486] Step 709: If the terminal does not have multi-stream processing capabilities, the SMF sends a notification message to the PCF. Correspondingly, the PCF receives the notification message.

[0487] This notification message is used to indicate that the QoS information update for the corresponding data stream failed. Optionally, the notification message includes a reason value, which indicates that the reason for the update failure is that the terminal does not have multi-stream processing capabilities.

[0488] In step 710, the PCF sends a notification message to the AF. Correspondingly, the AF receives the notification message.

[0489] This notification message is used to indicate that the QoS information update for the corresponding data stream failed. Optionally, the notification message includes a reason value, which indicates that the reason for the update failure is that the terminal does not have multi-stream processing capabilities.

[0490] After receiving the notification message, the AF updates the information of multiple data streams with the same 5-tuple information. For example, it modifies the 5-tuple information corresponding to the same data streams to different 5-tuple information, thereby mapping the multiple data streams to different QoS streams for transmission. This achieves differentiated transmission protection based on the transmission requirements of different data streams and uses corresponding QoS streams. Specifically, the AF can initiate a QoS update request to the PCF. This QoS update request requests the modification of the 5-tuple information corresponding to the same data streams to different 5-tuple information. Then, the PCF generates PCC rules based on the QoS update request, the SMF generates QoS rules based on the PCC rules, and sends the QoS rules to the terminal. Based on these QoS rules, the terminal can map different data streams with different 5-tuple information to different QoS streams.

[0491] Based on the above scheme, the SMF sends QoS rules to the terminal. The terminal then maps different uplink data streams with the same 5-tuple information to different QoS streams for transmission according to the QoS rules, thus meeting the differentiated transmission requirements of different data streams. The terminal also sends an indication message to the SMF to indicate whether it has multi-stream processing capabilities. If the terminal does not have multi-stream processing capabilities, the SMF sends a notification message to the AF. Based on the notification message, the AF determines different 5-tuple information for different data streams with the same 5-tuple information, thereby enabling the mapping of different uplink data streams with different 5-tuple information to different QoS streams for transmission, meeting the differentiated transmission requirements of different data streams.

[0492] Figure 8 is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0493] Steps 801 to 806 are the same as steps 401 to 406 in the embodiment of Figure 4.

[0494] Step 807: SMF determines whether UPF#1 has multi-stream processing capability.

[0495] SMF triggers a determination of whether UPF#1 has multi-stream processing capabilities based on at least one of the payload type, synchronization source identifier, or tag header field information in the data stream information indicated by the PCC rules.

[0496] In one possible implementation, the SMF is locally configured with the capability information of UPF#1, which indicates whether UPF#1 has multi-stream processing capabilities. Therefore, the SMF can determine whether UPF#1 has multi-stream processing capabilities based on the capability information of UPF#1.

[0497] Step 808: If UPF#1 does not have multi-stream processing capability, SMF selects UPF#2 which has multi-stream processing capability.

[0498] In one possible implementation, the SMF is locally configured with capability information for multiple UPFs, which indicates whether the UPF has multi-stream processing capabilities. Therefore, the SMF can select UPF#2, which has multi-stream processing capabilities, based on the capability information of multiple UPFs.

[0499] In step 809, SMF sends configuration information to UPF#1. Correspondingly, UPF#1 receives the configuration information.

[0500] This configuration information instructs UPF#1 to update the tunnel information from UPF#1 to the access network device to the tunnel information from UPF#1 to UPF#2. That is, UPF#1 deletes the tunnel information from UPF#1 to the access network device and adds the tunnel information from UPF#1 to UPF#2. Based on this configuration information, UPF#1 deletes the tunnel from UPF#1 to the access network device and establishes the tunnel from UPF#1 to UPF#2.

[0501] In step 810, SMF sends configuration information to UPF#2. Correspondingly, UPF#2 receives the configuration information.

[0502] This configuration information is used to instruct UPF#2 to add tunnel information from UPF#2 to UPF#1 and tunnel information from UPF#2 to access network devices. Based on this configuration information, UPF#2 establishes tunnels from UPF#2 to UPF#1 and from UPF#2 to access network devices.

[0503] Step 811: The SMF sends configuration information to the access network device. Correspondingly, the access network device receives the configuration information.

[0504] This configuration information instructs the access network device to update the tunnel information from the access network device to UPF#1 to the tunnel information from the access network device to UPF#2. That is, the access network device deletes the tunnel information from the access network device to UPF#1 and adds the tunnel information from the access network device to UPF#2. Based on this configuration information, the access network device deletes the tunnel from the access network device to UPF#1 and establishes the tunnel from the access network device to UPF#2.

[0505] Based on steps 809 to 811 above, UPF#2 is inserted between the access network device and UPF#1. The existing N3 tunnel between the access network device and UPF#1 is updated to the existing N3 tunnel between the access network device and UPF#2, the existing N9 tunnel between UPF#2 and UPF#1, and the existing N3 tunnel between the access network device and UPF#1.

[0506] In step 812, SMF sends the N4 rule to UPF#2. UPF#2 then receives the N4 rule.

[0507] The N4 rule is generated by SMF based on the PCC rule. The N4 rule is used to map different data streams with the same 5-tuple information to different QoS streams for transmission.

[0508] For details regarding the N4 rule, please refer to the description in step 306 above.

[0509] Based on the above scheme, if UPF#1 does not have multi-stream processing capability, SMF selects UPF#2 which has multi-stream processing capability and sends N4 rules to UPF#2. UPF#2 then maps different downlink data streams with the same five-tuple information to different QoS streams for transmission according to the N4 rules, so as to meet the differentiated transmission requirements of different data streams.

[0510] Figure 9 is a flowchart illustrating a communication method provided in an embodiment of this application. The method includes the following steps:

[0511] Steps 901 to 908 are the same as steps 801 to 808 in the embodiment of Figure 8.

[0512] In step 909, SMF sends configuration information to UPF#1. Correspondingly, UPF#1 receives the configuration information.

[0513] This configuration information is used to instruct UPF#1 to add a tunnel from UPF#1 to UPF#2. UPF#1 establishes the tunnel from UPF#1 to UPF#2 based on this configuration information.

[0514] In step 910, SMF sends configuration information to UPF#2. Correspondingly, UPF#2 receives the configuration information.

[0515] This configuration information is used to instruct UPF#2 to add tunnel information from UPF#2 to UPF#1 and tunnel information from UPF#2 to access network devices. Based on this configuration information, UPF#2 establishes tunnels from UPF#2 to UPF#1 and from UPF#2 to access network devices.

[0516] Step 911: The SMF sends configuration information to the access network device. Correspondingly, the access network device receives the configuration information.

[0517] This configuration information is used to instruct the access network device to add a tunnel from the access network device to UPF#2. Based on this configuration information, the access network device establishes the tunnel from the access network device to UPF#2.

[0518] Based on steps 909 to 911 above, UPF#2 is inserted between the access network device and UPF#1. While maintaining the N3 tunnel between the access network device and UPF#1, an N3 tunnel is added between the access network device and UPF#2, and an N9 tunnel is added between UPF#2 and UPF#1. Therefore, after inserting UPF#2, an N3 tunnel exists between the access network device and UPF#1, and an N3 tunnel also exists between the access network device and UPF#2.

[0519] In step 912, SMF sends the N4 rule to UPF#2. UPF#2 then receives the N4 rule.

[0520] The N4 rule is generated by SMF based on the PCC rule. The N4 rule is used to map different data streams with the same 5-tuple information to different QoS streams for transmission.

[0521] For details regarding the N4 rule, please refer to the description in step 306 above.

[0522] Subsequently, UPF#2 receives the N4 rule and can map different data streams with the same 5-tuple information to different QoS streams according to the N4 rule. For data streams that do not require multi-stream processing (e.g., multiple data streams with different 5-tuple information), UPF#1 can send them to the access network device.

[0523] In step 913, the SMF sends an indication message to the access network device. Correspondingly, the access network device receives the indication message.

[0524] This indication information is used to indicate the uplink QoS streams that need to be sent to UPF#1 and the uplink QoS streams that need to be sent to UPF#2. The QFI of the uplink QoS streams that need to be sent to UPF#2 is the same as the QFI of the downlink QoS streams corresponding to the downlink data streams that require multi-stream processing. The downlink data streams that require multi-stream processing refer to the multiple data streams with the same five-tuple information indicated by the QoS update request in step 801 above.

[0525] For example, this instruction information instructs the access network device to send the uplink QoS flows corresponding to QFI#1, QFI#2, and QFI#3 to UPF#1, and to send the uplink QoS flows corresponding to QFI#4, QFI#5, and QFI#6 to UPF#2. Specifically, the QFIs for the downlink QoS flows corresponding to downlink data flows requiring multi-stream processing include QFI#4, QFI#5, and QFI#6, while the QFIs for the downlink QoS flows corresponding to downlink data flows not requiring multi-stream processing include QFI#1, QFI#2, and QFI#3.

[0526] Step 913 above is an optional step. If step 913 is not performed, when UPF#2 maps downlink data streams that require multi-stream processing to corresponding downlink QoS streams, it adds indication information and the QFI of the downlink QoS stream to the header of the data packets of the downlink QoS stream. The indication information is used to instruct the access network device to send the uplink QoS stream corresponding to the QFI to UPF#2.

[0527] Based on the above scheme, if UPF#1 does not have multi-stream processing capability, SMF selects UPF#2 which has multi-stream processing capability and sends N4 rules to UPF#2. UPF#2 then maps different downlink data streams with the same five-tuple information to different QoS streams for transmission according to the N4 rules, so as to meet the differentiated transmission requirements of different data streams.

[0528] Figure 10 illustrates a possible exemplary block diagram of the communication device involved in the embodiments of this application. As shown in Figure 10, the communication device 1000 may include modules or units for implementing the methods described above. In one possible design, the communication device 1000 includes a processing unit 1002 and a communication unit 1003. Optionally, the communication device 1000 may further include a storage unit 1001 for storing device program code and / or data.

[0529] The communication device 1000 can also be a network-side device in the above embodiments, such as a session management network element on the network side, a module (e.g., circuit, chip or chip system) in the session management network element, or a logical node, logical module or software that can implement all or part of the functions of the session management network element.

[0530] For example, in one embodiment, the processing unit 1002 is configured to acquire terminal capability information, the capability information being used to indicate that the terminal has multi-stream processing capability or indicates that the terminal does not have multi-stream processing capability; and based on the terminal capability information, to send a first rule to the terminal via the communication unit 1003, the first rule including a first packet filter, a second packet filter, information of a first QoS stream corresponding to the first packet filter, and information of a second QoS stream corresponding to the second packet filter, the first packet filter including information of a first data stream, the second packet filter including information of a second data stream, the information of the first data stream including first 5-tuple information, the information of the second data stream including second 5-tuple information, the second 5-tuple information being the same as the first 5-tuple information, the first packet filter being used to identify the first data stream, and the second packet filter being used to identify the second data stream.

[0531] In one possible implementation, the communication unit 1003 is further configured to receive PCC rules from the policy control network element, the PCC rules being used to indicate information of the first data stream and the first QoS parameter requirements of the first QoS stream, and to indicate information of the second data stream and the first QoS parameter requirements of the second QoS stream, wherein the first QoS parameter requirements are different from the second QoS parameter requirements; the processing unit 1002 is further configured to determine the first rule according to the PCC rules.

[0532] In one possible implementation, when the terminal has multi-stream processing capabilities, the QoS stream identifier in the information of the first QoS stream is different from the QoS stream identifier in the information of the second QoS stream.

[0533] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0534] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0535] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0536] In one possible implementation, when the terminal does not have multi-stream processing capabilities, the QoS stream identifier in the information of the first QoS stream is the same as the QoS stream identifier in the information of the second QoS stream.

[0537] In one possible implementation, the processing unit 1002 is used to acquire the capability information of the terminal, including: receiving indication information from the terminal through the communication unit 1003, the indication information being used to indicate the capability information.

[0538] For example, in one embodiment, the processing unit 1002 is configured to acquire capability information of a first user plane network element, the capability information being used to indicate whether the first user plane network element has multi-stream processing capability or not; based on the capability information of the first user plane network element, a second rule is sent to the first user plane network element via the communication unit 1003, the second rule including a first packet detection rule and a first QoS execution rule corresponding to a first data stream, and a second packet detection rule and a second QoS execution rule corresponding to a second data stream; the first packet detection rule includes information about the first data stream, the information about the first data stream including first 5-tuple information, the first packet detection rule being used to identify the first data stream, the first QoS execution rule being used to indicate that the header of the data packets of the first data stream carries the QoS stream identifier of the first QoS stream corresponding to the first data stream; the second packet detection rule includes information about the second data stream, the information about the second data stream including second 5-tuple information, the second 5-tuple information being the same as the first 5-tuple information, the second packet detection rule being used to identify the second data stream, the second QoS execution rule being used to indicate that the header of the data packets of the second data stream carries the QoS stream identifier of the second QoS stream corresponding to the second data stream.

[0539] In one possible implementation, the communication unit 1003 is further configured to receive PCC rules from the policy control network element, the PCC rules being used to indicate information of the first data stream and a first QoS parameter requirement of the first QoS stream, and to indicate information of the second data stream and a second QoS parameter requirement of the second QoS stream, wherein the first QoS parameter requirement is different from the second QoS parameter requirement; the processing unit 1002 is further configured to determine the second rule according to the PCC rules.

[0540] In one possible implementation, when the first user plane network element has multi-stream processing capabilities, the QoS stream identifier of the first QoS stream is different from the QoS stream identifier of the second QoS stream.

[0541] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0542] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0543] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0544] In one possible implementation, when the first user plane network element does not have multi-stream processing capabilities, the QoS stream identifier in the information of the first QoS stream is the same as the QoS stream identifier in the information of the second QoS stream.

[0545] In one possible implementation, the processing unit 1002 is further configured to select a second user plane network element that has multi-stream processing capability when the first user plane network element does not have multi-stream processing capability; the communication unit 1003 is further configured to send the second rule to the second user plane network element, wherein the QoS stream identifier in the information of the first QoS stream is different from the QoS stream identifier in the information of the second QoS stream.

[0546] In one possible implementation, the communication unit 1003 is further configured to send first configuration information to the first user plane network element, the first configuration information being used to instruct the first user plane network element to update the tunnel information from the first user plane network element to the access network device to the tunnel information from the first user plane network element to the second user plane network element; send second configuration information to the second user plane network element, the second configuration information being used to instruct the second user plane network element to add tunnel information from the second user plane network element to the first user plane network element, and to add tunnel information from the second user plane network element to the access network device; and send third configuration information to the access network device, the third configuration information being used to instruct the access network device to update the tunnel information from the access network device to the first user plane network element to the tunnel information from the access network device to the second user plane network element.

[0547] In one possible implementation, the communication unit 1003 is further configured to send first configuration information to the first user plane network element, the first configuration information being used to instruct the first user plane network element to add information about a tunnel between the first user plane network element and the second user plane network element; send second configuration information to the second user plane network element, the second configuration information being used to instruct the second user plane network element to add information about a tunnel between the second user plane network element and the first user plane network element, and to add information about a tunnel between the second user plane network element and the access network device; and send third configuration information to the access network device, the third configuration information being used to instruct the access network device to add information about a tunnel between the access network device and the second user plane network element.

[0548] In one possible implementation, the processing unit 1002 is configured to acquire capability information of a first user plane network element, including: receiving indication information from the first user plane network element via the communication unit 1003, wherein the indication information is used to indicate the capability information.

[0549] The communication device 1000 can also be a network-side device in the above embodiments, such as a network-side policy control network element, a module (e.g., circuit, chip or chip system) in the policy control network element, or a logic node, logic module or software that can implement all or part of the policy control network element functions.

[0550] For example, in one embodiment, the processing unit 1002 is used to obtain terminal capability information, which indicates whether the terminal has multi-stream processing capability or not; based on the terminal capability information, the processing unit 1002 sends PCC rules to the session management network element through the communication unit 1003, which indicates information about a first data stream, information about a second data stream, information about a first QoS stream corresponding to the first data stream, and information about a second QoS stream corresponding to the second data stream. The information about the first data stream includes a first quintuple, the information about the second data stream includes a second quintuple, and the second quintuple is the same as the first quintuple. The information about the first QoS stream includes a first QoS parameter requirement and / or a QoS stream identifier for the first QoS stream, and the information about the second QoS stream includes a second QoS parameter requirement and / or a QoS stream identifier for the second QoS stream.

[0551] In one possible implementation, when the terminal has multi-stream processing capabilities, the first QoS parameter requirement is different from the second QoS parameter requirement, and the QoS stream identifier of the first QoS stream is different from the QoS stream identifier of the second QoS stream.

[0552] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0553] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0554] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0555] In one possible implementation, when the terminal does not have multi-stream processing capabilities, the first QoS parameter requirement is the same as the second QoS parameter requirement, and the QoS stream identifier of the first QoS stream is the same as the QoS stream identifier of the second QoS stream.

[0556] In one possible implementation, the communication unit 1003 is further configured to receive the flow description information of the first data stream, the transmission requirements of the first data stream, the flow description information of the second data stream, and the transmission requirements of the second data stream from the application function network element; wherein, the flow description information of the first data stream includes the first quintuple information, and the flow description information of the second data stream includes the second quintuple information; the transmission requirements of the first data stream are different from the transmission requirements of the second data stream; the processing unit 1002 is further configured to determine the PCC rule based on the terminal's capability information, the flow description information of the first data stream, the transmission requirements of the first data stream, the flow description information of the second data stream, and the transmission requirements of the second data stream.

[0557] In one possible implementation, an indication message is received from the terminal or the session management network element, the indication message being used to indicate the capability information.

[0558] For example, in one embodiment, the processing unit 1002 is used to obtain capability information of a first user plane network element, the capability information being used to indicate that the first user plane network element has multi-stream processing capability, or to indicate that the first user plane network element does not have multi-stream processing capability; based on the capability information of the first user plane network element, the processing unit 1002 sends PCC rules to the session management network element through the communication unit 1003, the PCC rules being used to indicate information of a first data stream, information of a second data stream, information of a first QoS stream corresponding to the first data stream, and information of a second QoS stream corresponding to the second data stream, the information of the first data stream including first 5-tuple information, the information of the second data stream including second 5-tuple information, the second 5-tuple information being the same as the first 5-tuple information, the information of the first QoS stream including first QoS parameter requirements and / or QoS stream identifier of the first QoS stream, and the information of the second QoS stream including second QoS parameter requirements and / or QoS stream identifier of the second QoS stream.

[0559] In one possible implementation, when the first user plane network element has multi-stream processing capabilities, the first QoS parameter requirements are different from the second QoS parameter requirements, and the QoS stream identifier of the first QoS stream is different from the QoS stream identifier of the second QoS stream.

[0560] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0561] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0562] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0563] In one possible implementation, when the first user plane network element does not have multi-stream processing capabilities, the first QoS parameter requirements are the same as the second QoS parameter requirements, and the QoS stream identifier of the first QoS stream is the same as the QoS stream identifier of the second QoS stream.

[0564] In one possible implementation, the communication unit 1003 is further configured to receive flow description information of the first data stream, transmission requirements of the first data stream, flow description information of the second data stream, and transmission requirements of the second data stream from the application function network element; wherein, the flow description information of the first data stream includes the first quintuple information, and the flow description information of the second data stream includes the second quintuple information; the transmission requirements of the first data stream are different from the transmission requirements of the second data stream; the processing unit 1002 is further configured to determine the PCC rule based on the capability information of the first user plane network element, the flow description information of the first data stream, the transmission requirements of the first data stream, the flow description information of the second data stream, and the transmission requirements of the second data stream.

[0565] In one possible implementation, the communication unit 1003 is further configured to receive indication information from the first user plane network element or the session management network element, the indication information being used to indicate the capability information.

[0566] The communication device 1000 can be a terminal-side device as described in the above embodiments, such as a terminal or a communication module in a terminal, or a circuit or chip in a terminal that is responsible for communication functions.

[0567] For example, in one embodiment, the communication unit 1003 is configured to send indication information to a session management network element, the indication information being used to indicate the terminal's capability information, the capability information being used to indicate that the terminal has multi-stream processing capability, or to indicate that the terminal does not have multi-stream processing capability; and to receive a first rule from the session management network element, the first rule including a first packet filter, a second packet filter, information of a first QoS stream corresponding to the first packet filter, and information of a second QoS stream corresponding to the second packet filter, the first packet filter including information of a first data stream, the second packet filter including information of a second data stream, the information of the first data stream including first 5-tuple information, the information of the second data stream including second 5-tuple information, the second 5-tuple information being the same as the first 5-tuple information, the first packet filter being used to identify the first data stream, and the second packet filter being used to identify the second data stream.

[0568] In one possible implementation, when the terminal has multi-stream processing capabilities, the QoS stream identifier in the information of the first QoS stream is different from the QoS stream identifier in the information of the second QoS stream.

[0569] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0570] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0571] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0572] In one possible implementation, when the terminal does not have multi-stream processing capabilities, the QoS stream identifier in the information of the first QoS stream is the same as the QoS stream identifier in the information of the second QoS stream.

[0573] For example, in one embodiment, the communication unit 1003 is configured to receive a first rule from a session management network element. The first rule includes a first packet filter, a second packet filter, information about a first QoS stream corresponding to the first packet filter, and information about a second QoS stream corresponding to the second packet filter. The first packet filter includes information about a first data stream, and the second packet filter includes information about a second data stream. The information about the first data stream includes first 5-tuple information, and the information about the second data stream includes second 5-tuple information. The second 5-tuple information is the same as the first 5-tuple information. The first packet filter is used to identify the first data stream, and the second packet filter is used to identify the second data stream. The QoS stream identifier in the information about the first QoS stream is different from the QoS stream identifier in the information about the second QoS stream. Upon receiving the first rule, the communication unit 1003 sends indication information to the session management network element. The indication information is used to indicate that the terminal has multi-stream processing capability or to indicate that the terminal does not have multi-stream processing capability.

[0574] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0575] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0576] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0577] In one possible design, when the communication device 1000 is a terminal or a communication module within a terminal, the function of the processing unit 1002 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The function of the communication unit 1003 can be implemented by transceiver circuitry.

[0578] In one possible design, when the communication device 1000 is a circuit or chip in a terminal responsible for communication functions, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing unit 1002 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 1003 can be implemented by the interface circuitry or data transceiver circuitry on the aforementioned chip.

[0579] The communication device 1000 can also be a network-side device in the above embodiments, such as a first user plane network element on the network side, a module (e.g., circuit, chip or chip system) in the first user plane network element, or a logic node, logic module or software that can implement all or part of the functions of the first user plane network element.

[0580] For example, in one embodiment, the communication unit 1003 is configured to send indication information to a session management network element, the indication information being used to indicate capability information of a first user plane network element, the capability information being used to indicate that the first user plane network element has multi-stream processing capability, or to indicate that the first user plane network element does not have multi-stream processing capability; and to receive a second rule from the session management network element, the second rule including a first packet detection rule and a first QoS execution rule corresponding to a first data stream, and including a second packet detection rule and a second QoS execution rule corresponding to a second data stream; the first packet detection rule includes information about the first data stream, the information about the first data stream including first 5-tuple information, the first packet detection rule being used to identify the first data stream, the first QoS execution rule being used to indicate that the packet header of the data packets of the first data stream carries the QoS stream identifier of the first QoS stream corresponding to the first data stream; the second packet detection rule includes information about the second data stream, the information about the second data stream including second 5-tuple information, the second 5-tuple information being the same as the first 5-tuple information, the second packet detection rule being used to identify the second data stream, the second QoS execution rule being used to indicate that the packet header of the data packets of the second data stream carries the QoS stream identifier of the second QoS stream corresponding to the second data stream.

[0581] In one possible implementation, when the first user plane network element has multi-stream processing capabilities, the QoS stream identifier of the first QoS stream is different from the QoS stream identifier of the second QoS stream.

[0582] In one possible implementation, the information in the first data stream further includes first information, and the information in the second data stream further includes second information, wherein the first information and the second information are different. The first information and the second information are used to distinguish between the first data stream and the second data stream that correspond to the same quintuple information.

[0583] In one possible implementation, the first information includes at least one of a first payload type, a first synchronization source identifier, or a first tag header field, wherein the first payload type indicates the type of the first data stream, the first synchronization source identifier identifies the synchronization source of the first data stream, and the first tag header field indicates the header information of the first data stream; the second information includes at least one of a second payload type, a second synchronization source identifier, or a second tag header field, wherein the second payload type indicates the type of the second data stream, the second synchronization source identifier identifies the synchronization source of the second data stream, and the second tag header field indicates the header information of the second data stream; wherein both the first data stream and the second data stream are transmitted via RTP, SRTP, RTCP, or SRTCP.

[0584] In one possible implementation, the first information includes first metadata, the second information includes second metadata, and the first metadata is different from the second metadata; wherein both the first data stream and the second data stream are transmitted via the MoQ protocol.

[0585] In one possible implementation, when the first user plane network element does not have multi-stream processing capabilities, the QoS stream identifier in the information of the first QoS stream is the same as the QoS stream identifier in the information of the second QoS stream.

[0586] The communication device 1000 can also be a network-side device in the above embodiments, such as an application function network element on the network side, a module (e.g., a circuit, chip, or chip system) in the application function network element, or a logic node, logic module, or software that can implement all or part of the application function network element functions.

[0587] For example, in one embodiment, the communication unit 1003 is configured to send a QoS update request, the QoS update request including flow description information of a first data stream,...

Claims

1. A communication method characterized by comprising: The method comprises: obtaining capability information of a terminal, the capability information being used to indicate that the terminal has a multi-flow processing capability or that the terminal does not have a multi-flow processing capability; sending a first rule to the terminal according to the capability information of the terminal, the first rule comprising a first packet filter, a second packet filter, information of a first quality of service (QoS) flow corresponding to the first packet filter, and information of a second QoS flow corresponding to the second packet filter, the first packet filter comprising information of a first data flow, the second packet filter comprising information of a second data flow, the information of the first data flow comprising first five-tuple information, the information of the second data flow comprising second five-tuple information, the second five-tuple information being the same as the first five-tuple information, the first packet filter being used to identify the first data flow, and the second packet filter being used to identify the second data flow.

2. The method of claim 1, wherein, Further comprising: receiving a policy and charging control (PCC) rule from a policy control network element, the PCC rule being used to indicate the information of the first data flow and first QoS parameter requirements of the first QoS flow, and to indicate the information of the second data flow and second QoS parameter requirements of the second QoS flow, the first QoS parameter requirements being different from the second QoS parameter requirements; determining the first rule according to the PCC rule.

3. The method of claim 1 or 2, wherein, In a case where the terminal has a multi-flow processing capability, a QoS flow identifier in the information of the first QoS flow is different from a QoS flow identifier in the information of the second QoS flow.

4. The method of claim 3, wherein, The information of the first data flow further comprises first information, the information of the second data flow further comprises second information, the first information being different from the second information, and the first information and the second information being used to distinguish the first data flow and the second data flow corresponding to the same five-tuple information.

5. The method of claim 1 or 2, wherein, In a case where the terminal does not have a multi-flow processing capability, the QoS flow identifier in the information of the first QoS flow is the same as the QoS flow identifier in the information of the second QoS flow.

6. The method of any one of claims 1 to 5, wherein, The obtaining of the capability information of the terminal comprises: receiving indication information from the terminal, the indication information being used to indicate the capability information.

7. A communication method characterized by comprising: The method comprises: obtaining capability information of a first user plane network element, the capability information being used to indicate that the first user plane network element has a multi-flow processing capability or that the first user plane network element does not have a multi-flow processing capability; According to the capability information of the first user plane network element, a second rule is sent to the first user plane network element, the second rule including a first packet detection rule and a first QoS execution rule corresponding to a first data flow, and including a second packet detection rule and a second QoS execution rule corresponding to a second data flow; the first packet detection rule including information of the first data flow, the information of the first data flow including first five-tuple information, the first packet detection rule being used to identify the first data flow, and the first QoS execution rule being used to instruct a packet header of a data packet of the first data flow to carry a QoS flow identifier of a first QoS flow corresponding to the first data flow; the second packet detection rule including information of the second data flow, the information of the second data flow including second five-tuple information, the second five-tuple information being the same as the first five-tuple information, the second packet detection rule being used to identify the second data flow, and the second QoS execution rule being used to instruct a packet header of a data packet of the second data flow to carry a QoS flow identifier of a second QoS flow corresponding to the second data flow.

8. The method of claim 7, wherein, Further comprising: a policy and charging control (PCC) rule received from a policy control network element, the PCC rule being used to instruct information of the first data flow and first QoS parameter requirements of the first QoS flow, and to instruct information of the second data flow and second QoS parameter requirements of the second QoS flow, the first QoS parameter requirements being different from the second QoS parameter requirements; the second rule is determined according to the PCC rule.

9. The method of claim 7 or 8, wherein, In a case where the first user plane network element has a multi-flow processing capability, the QoS flow identifier of the first QoS flow is different from the QoS flow identifier of the second QoS flow.

10. The method of claim 9, wherein, The information of the first data flow further includes first information, and the information of the second data flow further includes second information, the first information being different from the second information, and the first information and the second information being used to distinguish the first data flow and the second data flow corresponding to the same five-tuple information.

11. The method of claim 7 or 8, wherein, In a case where the first user plane network element does not have a multi-flow processing capability, the QoS flow identifier in the information of the first QoS flow is the same as the QoS flow identifier in the information of the second QoS flow.

12. The method of claim 7 or 8, wherein, Further comprising: In a case where the first user plane network element does not have a multi-flow processing capability, a second user plane network element having a multi-flow processing capability is selected; the second rule is sent to the second user plane network element, wherein the QoS flow identifier in the information of the first QoS flow is different from the QoS flow identifier in the information of the second QoS flow.

13. The method of claim 12, wherein, Further comprising: first configuration information is sent to the first user plane network element, the first configuration information being used to instruct the first user plane network element to update information of a tunnel from the first user plane network element to an access network device to information of a tunnel from the first user plane network element to the second user plane network element; sending second configuration information to the second user plane network element, the second configuration information being used to instruct the second user plane network element to add information of a tunnel from the second user plane network element to the first user plane network element and information of a tunnel from the second user plane network element to the access network device; sending third configuration information to the access network device, the third configuration information being used to instruct the access network device to update information of a tunnel from the access network device to the first user plane network element to information of a tunnel from the access network device to the second user plane network element.

14. The method of claim 12, wherein, Further comprising: sending first configuration information to the first user plane network element, the first configuration information being used to instruct the first user plane network element to add information of a tunnel between the first user plane network element and the second user plane network element; sending second configuration information to the second user plane network element, the second configuration information being used to instruct the second user plane network element to add information of a tunnel from the second user plane network element to the first user plane network element and information of a tunnel from the second user plane network element to the access network device; sending third configuration information to the access network device, the third configuration information being used to instruct the access network device to add information of a tunnel from the access network device to the second user plane network element.

15. The method of any one of claims 7 to 14, wherein, The obtaining of the capability information of the first user plane network element comprises: receiving indication information from the first user plane network element, the indication information being used to indicate the capability information.

16. A method of communication, comprising: The method comprises: obtaining capability information of a terminal, the capability information being used to indicate that the terminal has a multi-flow processing capability or that the terminal does not have a multi-flow processing capability; sending a policy and charging control (PCC) rule to a session management network element according to the capability information of the terminal, the PCC rule being used to indicate information of a first data flow, information of a second data flow, information of a first quality of service (QoS) flow corresponding to the first data flow, and information of a second QoS flow corresponding to the second data flow, the information of the first data flow comprising first five-tuple information, the information of the second data flow comprising second five-tuple information, the second five-tuple information being the same as the first five-tuple information, the information of the first QoS flow comprising a first QoS parameter requirement and / or a QoS flow identifier of the first QoS flow, and the information of the second QoS flow comprising a second QoS parameter requirement and / or a QoS flow identifier of the second QoS flow.

17. The method of claim 16, wherein, In a case where the terminal has a multi-flow processing capability, the first QoS parameter requirement is different from the second QoS parameter requirement, and the QoS flow identifier of the first QoS flow is different from the QoS flow identifier of the second QoS flow.

18. The method of claim 17, wherein, The information of the first data flow further comprises first information, and the information of the second data flow further comprises second information, the first information being different from the second information, and the first information and the second information being used to distinguish the first data flow and the second data flow corresponding to the same five-tuple information.

19. The method of claim 16, wherein, In a case that the terminal does not have the multi-flow processing capability, the first QoS parameter requirement is same as the second QoS parameter requirement, and the QoS flow identifier of the first QoS flow is same as the QoS flow identifier of the second QoS flow.

20. The method of any one of claims 16 to 19, wherein, Further comprising: receiving flow description information of the first data flow, transmission requirement of the first data flow, flow description information of the second data flow, and transmission requirement of the second data flow from an application function network element; wherein the flow description information of the first data flow comprises the first five-tuple information, and the flow description information of the second data flow comprises the second five-tuple information; the transmission requirement of the first data flow is different from the transmission requirement of the second data flow; determining the PCC rule according to the capability information of the terminal, the flow description information of the first data flow, the transmission requirement of the first data flow, the flow description information of the second data flow, and the transmission requirement of the second data flow.

21. A method of communication, comprising: The method comprises: obtaining capability information of a first user plane network element, the capability information being used to indicate that the first user plane network element has a multi-flow processing capability or that the first user plane network element does not have the multi-flow processing capability; sending, to a session management network element, a policy and charging control (PCC) rule according to the capability information of the first user plane network element, the PCC rule being used to indicate first data flow information, second data flow information, first quality of service (QoS) flow information corresponding to the first data flow, and second QoS flow information corresponding to the second data flow, the first data flow information comprising first five-tuple information, the second data flow information comprising second five-tuple information, the second five-tuple information being same as the first five-tuple information, the first QoS flow information comprising first QoS parameter requirement and / or QoS flow identifier of the first QoS flow, and the second QoS flow information comprising second QoS parameter requirement and / or QoS flow identifier of the second QoS flow.

22. The method of claim 21, wherein, In a case that the first user plane network element has the multi-flow processing capability, the first QoS parameter requirement is different from the second QoS parameter requirement, and the QoS flow identifier of the first QoS flow is different from the QoS flow identifier of the second QoS flow.

23. The method of claim 22, wherein, The first data flow information further comprises first information, the second data flow information further comprises second information, the first information is different from the second information, and the first information and the second information are used to distinguish the first data flow and the second data flow corresponding to the same five-tuple information.

24. The method of claim 21, wherein, In a case that the first user plane network element does not have the multi-flow processing capability, the first QoS parameter requirement is same as the second QoS parameter requirement, and the QoS flow identifier of the first QoS flow is same as the QoS flow identifier of the second QoS flow.

25. The method of any one of claims 21 to 24, wherein, Further comprising: receive flow description information of the first data flow, transmission requirement of the first data flow, flow description information of the second data flow and transmission requirement of the second data flow from an application function network element; wherein the flow description information of the first data flow comprises the first five-tuple information, and the flow description information of the second data flow comprises the second five-tuple information; the transmission requirement of the first data flow is different from the transmission requirement of the second data flow; determine the PCC rule according to the capability information of the first user plane network element, the flow description information of the first data flow, the transmission requirement of the first data flow, the flow description information of the second data flow and the transmission requirement of the second data flow.

26. A communications device, characterized by a module for performing the method of any one of claims 1 to 6, or for performing the method of any one of claims 7 to 15, or for performing the method of any one of claims 16 to 20, or for implementing the method of any one of claims 21 to 25.

27. A computer program product, characterised in that, The computer program product comprises a computer program or instructions, which, when executed, implement the method of any one of claims 1 to 6, or implement the method of any one of claims 7 to 15, or implement the method of any one of claims 16 to 20, or implement the method of any one of claims 21 to 25.

28. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed, implement the method of any one of claims 1 to 6, or implement the method of any one of claims 7 to 15, or implement the method of any one of claims 16 to 20, or implement the method of any one of claims 21 to 25.

29. A communication system, characterized by comprise a session management network element for implementing the method of any one of claims 1 to 6; a terminal for receiving a first rule from the session management network element.

30. A communication system, characterized by comprise a session management network element for implementing the method of any one of claims 7 to 15; a first user plane network element for receiving a second rule from the session management network element.

Images