Communication method and apparatus, network element, communication system, storage medium, and program product

Abstract

The present disclosure relates to a communication method and apparatus, a network element, a communication system, a storage medium, and a program product. The method is executed by a first network element. The method comprises: receiving first information sent by a second network element, wherein the first information is used for determining a mapping rule for a multiplexed data stream, the first information comprises identification information, and the identification information is used for identifying at least one sub-stream. The solution of the present disclosure implements QoS processing for the multiplexed data stream.

Description

Communication method and device, network element, communication system, storage medium and program product Technical Field

[0001] The present disclosure relates to the field of wireless communications, and in particular to a communication method and apparatus, a network element, a communication system, a storage medium, and a program product. Background Art

[0002] In a communication system, a packet data unit (PDU) set can be used to provide quality of service (QoS) assurance for extended reality for multimedia (XRM) services.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure relate to a communication method and apparatus, a network element, a communication system, a storage medium, and a program product, thereby implementing QoS processing of multiplexed data streams.

[0005] According to a first aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a first network element. The method includes: receiving first information sent by a second network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream.

[0006] According to a second aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a second network element. The method includes: sending first information to a first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream.

[0007] According to a third aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a third network element. The method includes: receiving first information sent by a first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream, the first information including identification information, the identification information being used to identify at least one substream; and determining a third rule based on the first information.

[0008] According to a fourth aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a terminal. The method includes: receiving third information sent by a first network element, wherein the third information is used to indicate a second rule, the second rule is determined based on identification information, and the identification information is obtained from at least one subflow and is used to identify the at least one subflow.

[0009] According to a fifth aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a core network. The core network includes a first network element and a second network element. The method includes: the second network element sending first information to the first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream.

[0010] According to a sixth aspect of an embodiment of the present disclosure, a first network element is provided. The first network element includes a transceiver module. The transceiver module is configured to: receive first information sent by a second network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream.

[0011] According to a seventh aspect of an embodiment of the present disclosure, a second network element is provided. The second network element includes a transceiver module. The transceiver module is configured to: send first information to a first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream.

[0012] According to an eighth aspect of an embodiment of the present disclosure, a third network element is provided. The third network element includes a transceiver module. The transceiver module is configured to: receive first information sent by a first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream, the first information including identification information, the identification information being used to identify at least one substream; and determine a third rule based on the first information.

[0013] According to a ninth aspect of an embodiment of the present disclosure, a terminal is provided. The terminal includes a transceiver module. The transceiver module is configured to receive third information sent by a first network element, wherein the third information is used to indicate a second rule, the second rule is determined based on identification information, and the identification information is obtained from at least one subflow and is used to identify the at least one subflow.

[0014] According to a tenth aspect of an embodiment of the present disclosure, a communication device is provided. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method described in the first aspect.

[0015] According to an eleventh aspect of the present disclosure, a communication device is provided. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method described in the second aspect.

[0016] According to a twelfth aspect of the embodiments of the present disclosure, a communication device is provided. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method described in the third aspect.

[0017] According to a thirteenth aspect of the embodiments of the present disclosure, a communication device is provided. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method described in the fourth aspect.

[0018] According to a fourteenth aspect of an embodiment of the present disclosure, a communication system is provided. The communication system includes a first network element and a second network element. The first network element is used to implement the communication method described in the first aspect. The second network element is used to implement the communication method described in the second aspect.

[0019] According to a fifteenth aspect of the embodiments of the present disclosure, a storage medium is provided. The storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the communication method described in the first, second, third, fourth, or fifth aspects.

[0020] According to a sixteenth aspect of the embodiments of the present disclosure, a program product is provided. When executed by a communication device, the program product causes the communication device to execute the communication method as described in the first, second, third, fourth, or fifth aspect.

[0021] According to a seventeenth aspect of the embodiments of the present disclosure, a computer program is provided, which, when executed on a computer, causes the computer to execute the communication method according to the first, second, third, fourth, or fifth aspect.

[0022] According to an eighteenth aspect of the embodiments of the present disclosure, a chip or chip system is provided. The chip or chip system includes a processing circuit. The processing circuit is configured to execute the communication method described in the first aspect, the second aspect, the third aspect, the fourth aspect, or the fifth aspect.

[0023] According to the embodiments of the present disclosure, QoS processing of sub-streams in a multiplexed data stream can be implemented.

[0024] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory and do not constitute limitations on the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0026] FIG1A is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0027] FIG1B is a schematic diagram of an architecture of an exemplary implementation of a communication system provided according to an embodiment of the present disclosure.

[0028] FIG1C is a schematic diagram of an architecture of an exemplary implementation of a communication system provided according to an embodiment of the present disclosure.

[0029] FIG2A is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0030] FIG2B is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0031] FIG3A is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0032] FIG3B is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0033] FIG4A is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0034] FIG4B is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0035] FIG5A is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0036] FIG5B is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0037] FIG6A is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0038] FIG6B is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0039] FIG7A is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0040] FIG7B is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0041] FIG7C is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0042] FIG8A is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure.

[0043] FIG8B is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure.

[0044] FIG9 is an exemplary structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0045] FIG10A is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0046] FIG10B is a schematic structural diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0047] Embodiments of the present disclosure provide a communication method and apparatus, a network element, a communication system, a storage medium, and a program product.

[0048] In a first aspect, embodiments of the present disclosure provide a communication method. The method is performed by a first network element. The method includes: receiving first information sent by a second network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream.

[0049] In this embodiment, the first network element can send identification information for identifying at least one subflow via the first message. In this way, the core network can obtain the identification information of the subflow in the multiplexed data flow and then determine a mapping rule for the identified subflow based on the identification information. In this way, the mapping rule for the multiplexed data flow can be obtained, ultimately implementing QoS processing for the subflows in the multiplexed data flow.

[0050] In combination with some embodiments of the first aspect, in some embodiments, the identification information may include at least one of the following: substream identification information, used to identify at least one substream; PSI information, used to indicate the importance of a PDU set in at least one substream.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the identification information may be obtained from at least one sub-stream.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the above method may also include: receiving ninth information sent by a third network element, wherein the ninth information is used to determine the mapping rules of the multiplexed data stream; wherein the ninth information includes identification information, and the identification information is used to identify at least one sub-stream.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: determining a mapping rule according to the first information and / or the ninth information.

[0054] In combination with some embodiments of the first aspect, in some embodiments, the operation of determining the mapping rule based on the first information may include: adding identification information in the first information and / or the ninth information to the packet filter set; and determining the mapping rule based on the packet filter set.

[0055] In combination with some embodiments of the first aspect, in some embodiments, the mapping rule may include a first rule, which is used for QoS processing of the downlink; wherein, the above method may also include: sending second information to the second network element, wherein the second information is used to indicate the first rule.

[0056] In combination with some embodiments of the first aspect, in some embodiments, the mapping rule may include a second rule, and the second rule is used for QoS processing of the uplink; wherein, the above method may also include: sending third information to the terminal, wherein the third information is used to indicate the second rule.

[0057] In combination with some embodiments of the first aspect, in some embodiments, the above method may also include: sending first information to a third network element; receiving fourth information sent by the third network element, wherein the fourth information is used to indicate a third rule, and the third rule is determined based on the first information.

[0058] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: receiving fifth information from a third network element, wherein the fifth information is used to indicate the acquisition of identification information; and sending the fifth information to the second network element.

[0059] In a second aspect, embodiments of the present disclosure provide a communication method. The method is performed by a second network element. The method includes: sending first information to a first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream.

[0060] Through this embodiment, the second network element can receive the first information from the first network element and, based on the first information, obtain identification information for at least one subflow. In this way, the core network can obtain the identification information of the subflow in the multiplexed data flow and then determine a mapping rule for the identified subflow based on the identification information. In this way, the mapping rule for the multiplexed data flow can be obtained, ultimately implementing QoS processing for the subflows in the multiplexed data flow.

[0061] In combination with some embodiments of the second aspect, in some embodiments, the identification information may include at least one of the following: sub-stream identification information, used to identify at least one stream; PSI information, used to indicate the importance of a PDU set in at least one sub-stream.

[0062] In combination with some embodiments of the second aspect, in some embodiments, the above method may further include: receiving at least one sub-stream; and determining identification information based on the at least one sub-stream.

[0063] In combination with some embodiments of the second aspect, in some embodiments, the above method may further include: receiving second information from the first network element, wherein the second information is used to indicate a first rule, and the first rule is used for QoS processing of the downlink.

[0064] In combination with some embodiments of the second aspect, in some embodiments, the above method may further include: receiving fifth information sent by the first network element, wherein the fifth information is used to indicate the acquisition of identification information.

[0065] In a third aspect, embodiments of the present disclosure provide a communication method. The method is performed by a third network element. The method comprises: receiving first information sent by a first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream, the first information including identification information used to identify at least one substream; and determining a third rule based on the first information.

[0066] Through this embodiment, the third network element can receive the first information from the second network element and, based on the first information, obtain identification information for at least one subflow. In this way, the core network can obtain the identification information of the subflow in the multiplexed data flow and, based on the identification information, determine a mapping rule for the identified subflow. In this way, the mapping rule for the multiplexed data flow can be obtained, ultimately implementing QoS processing for the subflows in the multiplexed data flow.

[0067] In combination with some embodiments of the third aspect, in some embodiments, the identification information may include at least one of the following: substream identification information, used to identify the substream; PSI information, used to indicate the importance of the PDU set in at least one substream.

[0068] In conjunction with some embodiments of the third aspect, in some embodiments, the identification information may be obtained from at least one sub-stream.

[0069] In combination with some embodiments of the third aspect, in some embodiments, the above method may also include: sending ninth information to the first network element, wherein the ninth information is used to determine the mapping rules of the multiplexed data stream; wherein the ninth information includes identification information, and the identification information is used to identify at least one sub-stream.

[0070] In combination with some embodiments of the third aspect, in some embodiments, the above method may further include: receiving ninth information sent by the fifth network element.

[0071] In combination with some embodiments of the third aspect, in some embodiments, the above method may further include: sending fourth information to the first network element, wherein the fourth information is used to indicate the third rule.

[0072] In combination with some embodiments of the third aspect, in some embodiments, the above method may further include: sending the first information to the fifth network element.

[0073] In a fourth aspect, embodiments of the present disclosure provide a communication method. The method is performed by a terminal. The method includes: receiving third information sent by a first network element, wherein the third information is used to indicate a second rule, the second rule is determined based on identification information, and the identification information is obtained from at least one subflow and is used to identify the at least one subflow.

[0074] Through this embodiment, a second rule can be determined based on identification information obtained from at least one substream. The second rule can be sent to the terminal via third information. In this way, the terminal can obtain the mapping rule for the multiplexed data stream, ultimately implementing QoS processing for the substreams in the multiplexed data stream.

[0075] In combination with some embodiments of the fourth aspect, in some embodiments, the identification information may include at least one of the following: substream identification information, used to identify at least one substream; PSI information, used to indicate the importance of a PDU set in at least one substream.

[0076] In a fifth aspect, embodiments of the present disclosure provide a communication method. The method is performed by a core network. The core network includes a first network element and a second network element. The method includes: the second network element sending first information to the first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream.

[0077] In combination with some embodiments of the fifth aspect, in some embodiments, the core network may further include a third network element; wherein the above method may further include: the first network element sends first information to the third network element; the third network element determines a third rule based on the first information.

[0078] In a sixth aspect, embodiments of the present disclosure provide a first network element. The first network element includes a transceiver module. The transceiver module is configured to: receive first information sent by a second network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream.

[0079] In combination with some embodiments of the sixth aspect, in some embodiments, the identification information may include at least one of the following: substream identification information, used to identify at least one substream; PSI information, used to indicate the importance of a PDU set in at least one substream.

[0080] In combination with some embodiments of the sixth aspect, in some embodiments, the identification information may be obtained from at least one sub-stream.

[0081] In combination with some embodiments of the sixth aspect, in some embodiments, the transceiver module can also be configured to: receive ninth information sent by a third network element, wherein the ninth information is used to determine the mapping rules of the multiplexed data stream; wherein the ninth information includes identification information, and the identification information is used to identify at least one sub-stream.

[0082] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first network element may further include a processing module, wherein the processing module is configured to: determine a mapping rule according to the first information and / or the ninth information.

[0083] In combination with some embodiments of the sixth aspect, in some embodiments, the processing module can be configured to: add identification information in the first information and / or the ninth information to the packet filter set; and determine a mapping rule based on the packet filter set.

[0084] In combination with some embodiments of the sixth aspect, in some embodiments, the mapping rules may include a first rule, which is used for QoS processing of the downlink; wherein, the transceiver module can also be configured to: send second information to the second network element, wherein the second information is used to indicate the first rule.

[0085] In combination with some embodiments of the sixth aspect, in some embodiments, the mapping rules may include a second rule, which is used for QoS processing of the uplink; wherein the transceiver module can also be configured to: send third information to the terminal, wherein the third information is used to indicate the second rule.

[0086] In combination with some embodiments of the sixth aspect, in some embodiments, the transceiver module can also be configured to: send first information to a third network element; receive fourth information sent by the third network element, wherein the fourth information is used to indicate a third rule, and the third rule is determined based on the first information.

[0087] In combination with some embodiments of the sixth aspect, in some embodiments, the transceiver module can also be configured to: receive fifth information from a third network element, wherein the fifth information is used to indicate the acquisition of identification information; and send the fifth information to the second network element.

[0088] In a seventh aspect, embodiments of the present disclosure provide a second network element. The second network element includes a transceiver module. The transceiver module is configured to: send first information to the first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream.

[0089] In combination with some embodiments of the seventh aspect, in some embodiments, the identification information may include at least one of the following: substream identification information, used to identify at least one substream; PSI information, used to indicate the importance of a PDU set in at least one substream.

[0090] In combination with some embodiments of the seventh aspect, in some embodiments, the transceiver module may further be configured to: receive at least one sub-stream; the above-mentioned second network element may further include: a processing module configured to determine identification information based on at least one sub-stream.

[0091] In combination with some embodiments of the seventh aspect, in some embodiments, the transceiver module can also be configured to: receive second information from the first network element, wherein the second information is used to indicate a first rule, and the first rule is used for QoS processing of the downlink.

[0092] In combination with some embodiments of the seventh aspect, in some embodiments, the transceiver module can also be configured to: receive fifth information sent by the first network element, wherein the fifth information is used to indicate the acquisition of identification information.

[0093] In an eighth aspect, embodiments of the present disclosure provide a third network element. The third network element includes a transceiver module and a processing module. The transceiver module is configured to receive first information sent by a first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream, the first information including identification information used to identify at least one substream. The processing module is configured to determine a third rule based on the first information.

[0094] In combination with some embodiments of the eighth aspect, in some embodiments, the identification information may include at least one of the following: substream identification information, used to identify at least one substream; PSI information, used to indicate the importance of a PDU set in at least one substream.

[0095] In combination with some embodiments of the eighth aspect, in some embodiments, the identification information may be obtained from at least one sub-stream.

[0096] In combination with some embodiments of the eighth aspect, in some embodiments, the transceiver module can also be configured to: send ninth information to the first network element, wherein the ninth information is used to determine the mapping rules of the multiplexed data stream; wherein the ninth information includes identification information, and the identification information is used to identify at least one sub-stream.

[0097] In combination with some embodiments of the eighth aspect, in some embodiments, the transceiver module can also be configured to: receive ninth information sent by the fifth network element.

[0098] In combination with some embodiments of the eighth aspect, in some embodiments, the transceiver module can also be configured to: send fourth information to the first network element, where the fourth information is used to indicate the third rule.

[0099] In combination with some embodiments of the eighth aspect, in some embodiments, the transceiver module can also be configured to: send the first information to the fifth network element.

[0100] In a ninth aspect, embodiments of the present disclosure provide a terminal. The terminal includes a transceiver module. The transceiver module is configured to receive third information sent by a first network element, where the third information indicates a second rule, the second rule being determined based on identification information obtained from at least one subflow and used to identify the at least one subflow.

[0101] In combination with some embodiments of the ninth aspect, in some embodiments, the identification information may include at least one of the following: substream identification information, used to identify at least one substream; PSI information, used to indicate the importance of a PDU set in at least one substream.

[0102] In a tenth aspect, embodiments of the present disclosure provide a communication device. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method as described in any one of the first aspect and possible embodiments thereof.

[0103] In an eleventh aspect, embodiments of the present disclosure provide a communication device. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method as described in any one of the second aspect and possible embodiments thereof.

[0104] In a twelfth aspect, embodiments of the present disclosure provide a communication device. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method as described in any one of the third aspect and possible embodiments thereof.

[0105] In a thirteenth aspect, embodiments of the present disclosure provide a communication device. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method as described in any one of the fourth aspect and possible embodiments thereof.

[0106] In a fourteenth aspect, an embodiment of the present disclosure provides a communication system. The communication system includes a first network element and a second network element. The first network element is configured to implement the communication method as described in any one of the first aspect and possible embodiments thereof. The second network element is configured to implement the communication method as described in any one of the second aspect and possible embodiments thereof.

[0107] In a fifteenth aspect, an embodiment of the present disclosure provides a storage medium. The storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the communication method as described in any one of the first, second, third, fourth, and fifth aspects and possible embodiments thereof.

[0108] In a sixteenth aspect, an embodiment of the present disclosure provides a program product. When the program product is executed by a communication device, the communication device executes the communication method as described in any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, and possible embodiments thereof.

[0109] In a seventeenth aspect, an embodiment of the present disclosure provides a computer program. When the computer program is executed on a computer, the computer executes the communication method as described in any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, and possible embodiments thereof.

[0110] In an eighteenth aspect, an embodiment of the present disclosure provides a chip or chip system. The chip or chip system includes a processing circuit. The processing circuit is configured to perform the communication method as described in any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, and possible embodiments thereof.

[0111] It is understandable that the aforementioned network elements, communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to perform the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can be referenced to the beneficial effects of the corresponding methods and will not be further described here.

[0112] The present disclosure provides a communication method and apparatus, a network element, a communication system, a storage medium, and a program product. In some embodiments, the terms communication method, information processing method, and information transmission method are interchangeable; the terms network element, network device, network function, and network entity are interchangeable; and the terms communication system and information processing system are interchangeable.

[0113] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0114] In the embodiments of the present disclosure, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0115] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0116] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when articles such as "a", "an", "the" in English are used in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0117] In the embodiments of the present disclosure, “plurality” refers to two or more than two.

[0118] In some embodiments, the terms "at least one", "one or more", etc. can be used interchangeably.

[0119] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0120] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0121] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for example, if the description object is "information", then the "second information" and the "first information" can be the same information or different information, and their contents can be the same or different.

[0122] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0123] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0124] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0125] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0126] In some embodiments, "network" can be interpreted as devices included in the network (e.g., access network devices, core network devices, etc.). For example, a network device may include at least one access network device. For another example, a network device may include at least one core network device. For another example, a network device may include at least one access network device and at least one core network device.

[0127] In some embodiments, the core network device may include at least one network element. Then, the network device including the core network device means that the network device may include at least one network element.

[0128] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0129] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0130] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0131] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0132] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0133] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0134] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0135] FIG1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1A , a communication system 100 includes a terminal 101 , an access network device 102 , and a core network device 103 .

[0136] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0137] In some embodiments, the access network device 102 can be, for example, a node or device that accesses the terminal to the wireless network. The access network device 102 may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a satellite base station, a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0138] In some embodiments, the terminal 101 and the core network device 103 may interact through the access network device 102. In some embodiments, the terminal 101 and the core network 103 may interact directly. This is not specifically limited in the embodiments of the present disclosure.

[0139] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0140] In some embodiments, the access network device 102 can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0141] In some embodiments, the core network 103 may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0142] As shown in FIG. 1A , the core network 103 may include at least one of the following: a first network element 1031 , a second network element 1032 , a third network element 1033 , a fourth network element 1034 , a fifth network element 1035 , a sixth network element 1036 , and a seventh network element 1037 .

[0143] In some embodiments, the first network element 1031 may be, for example, a session management function (SMF).

[0144] In some embodiments, the first network element 1031 can be used to implement session management functions, mainly performing session management, execution of PCF control policies, UPF selection, UE Internet Protocol (IP) address allocation and other functions, the name is not limited to this.

[0145] In some embodiments, the second network element 1032 may be, for example, a user plane function (UPF).

[0146] In some embodiments, the second network element 1032 can be used to implement functions such as user plane (UP) data forwarding, session / flow-level billing statistics, bandwidth limitation, UP QoS processing, etc., and the name is not limited thereto.

[0147] In some embodiments, the third network element 1033 may be, for example, a policy control function (PCF).

[0148] In some embodiments, the third network element 1033 can be used to implement policy control functions, and is mainly responsible for policy decisions related to charging policies, QoS bandwidth guarantees and policies for sessions and business flows, and the name is not limited to this.

[0149] In some embodiments, the fourth network element 1034 may be, for example, an application server (AS).

[0150] In some embodiments, the fourth network element 1034 may be configured to provide support for application services subscribed by users.

[0151] In some embodiments, the fifth network element 1035 may be, for example, an application function (AF).

[0152] In some embodiments, the fifth network element 1035 can be used to provide policy management for business services, and the name is not limited thereto.

[0153] In some embodiments, the sixth network element 1036 may be, for example, a network exposure function (NEF).

[0154] In some embodiments, the sixth network element 1036 can be used to ensure the security of external applications to the 3GPP network, provide QoS customization capability opening of external applications, mobility status time subscription, AF request distribution, etc., the name is not limited to this.

[0155] In some embodiments, the seventh network element 1037 may be, for example, an access and mobility management function (AMF).

[0156] In some embodiments, the seventh network element 1037 may be responsible for registration management, connection management, and mobility management, but the names are not limited thereto.

[0157] In some embodiments, the fourth network element 1034 may be located inside the core network 103. Of course, in some scenarios, the fourth network element 1034 may be located outside the core network 103, which is not specifically limited in the embodiments of the present disclosure.

[0158] In some embodiments, the fifth network element 1035 may be located inside the core network 103. Of course, in some scenarios, the fifth network element 1035 may be located outside the core network 103, which is not specifically limited in the embodiments of the present disclosure.

[0159] In some embodiments, the communication system 100 may be a 5G communication system. It should be noted that the communication system 100 may also be other communication systems, such as a 4G communication system or a 6G communication system, which is not specifically limited in the present disclosure.

[0160] 1B and 1C , the architecture of a communication system is exemplarily described by taking a 5G communication system as an example, wherein the terminal 101 may be a UE and the access network device 102 may be a RAN.

[0161] Figure 1B is a schematic diagram of an architecture of an implementation of a communication system according to an embodiment of the present disclosure. As shown in Figure 1B, the architecture of the 5G communication system is presented in the form of reference points.

[0162] N1 is the reference point between the UE and the AMF. N2 is the reference point between the RAN and the AMF. N3 is the reference point between the RAN and the UPF. N4 is the reference point between the SMF and the UPF. N5 is the reference point between the PCF and the AF. N6 is the reference point between the UPF and the data network (DN). N7 is the reference point between the SMF and the PCF. N8 is the reference point between the UDM and the AMF. N10 is the reference point between the UDM and the SMF. N11 is the reference point between the AMF and the SMF. N15 is the reference point between the SMF and the PCF. Uu is the interface between the UE and the RAN.

[0163] It should be noted that NEF and UDR are not shown in FIG1B , but each network element in the communication system can interact with UDR and NEF.

[0164] Figure 1C is a schematic diagram of the architecture of another implementation of a communication system according to an embodiment of the present disclosure. As shown in Figure 1C, the architecture of the 5G communication system is presented in a service-based interface manner.

[0165] Namf is a service-based interface provided by AMF. Nsmf is a service-based interface provided by SMF. Nnef is a service-based interface provided by NEF. Npcf is a service-based interface provided by PCF. Nudm is a service-based interface provided by UDM. Naf is a service-based interface provided by AF.

[0166] It should be noted that the UDR is not shown in FIG1C , but the UDR can provide a service-based interface Nudr.

[0167] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0168] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or some of the entities in the communication system 100 , but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system 100 may include all or some of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities are arbitrary. The entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0169] The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB), and other technologies. Band (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems using other communication methods, and next-generation systems based on and extending these methods. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G) may also be applied.

[0170] In some cases, services such as mobile media services, online AR / VR and other XR services, online gaming, and video-based remote control of machines or drones are expected to contribute increasingly high traffic volumes to communication networks. XR services involve multimodal data. Multimodal data is data describing the same service / application that is input from the same device or different devices (including sensors) and may be output to one or more destination devices. The data streams within multimodal data often have some, or even strong, correlation, such as synchronization between audio and video streams, or between touch and vision. These media services share common characteristics within their data streams, between the data streams themselves, and in terms of the network transmission requirements placed on these service data streams. Effectively identifying and leveraging these characteristics will facilitate network and service transmission and control, as well as enhance service assurance and user experience.

[0171] In further cases, XRM services and interactive media services require the communication system to comprehensively consider the QoS characteristics of the service data flow. Such QoS characteristics may include, for example, at least one of the following: whether parameters such as delay-sensitive guaranteed bit rate (GBR) data flow, guaranteed flow bit rate (GFBR), packet delay budget (PDB), and default maximum data burst volume (MDBV) can be simultaneously met and coordinated. It involves multiple XRM data flows of a terminal, and XRM data flows of multiple terminals, and the consistency of QoS authorization and execution between each other.

[0172] In some embodiments, the service data flow (SDF) of the XRM may support PDU set-based processing, thereby enhancing QoS awareness and assurance of the SDF and improving user quality of experience (QoE).

[0173] In some embodiments, in systems such as 4G, 5G, 6G, and V2X, the AF may provide PDU set QoS parameters and a protocol description. In some embodiments, the PDU set QoS parameters may include at least one of the following: a PDU set control indication, a PDU set delay budget (PSDB), a PDU set error rate (PSER), and a PDU set integrated handling information (PSIHI). Then, the SMF and the UPF may extend the header of the PDU in the PDU set of the SDF in combination with the protocol description and protocol header extension provided by the AF to carry the PDU set information. The PDU information carried may be used by the access network to perform PDU set-based QoS control.

[0174] In some embodiments, the PDU set information may include at least one of the following: a PDU set sequence number, a start PDU or end PDU of a PDU set, a PDU sequence number within a PDU set, the number of PDUs within a PDU set, PDU set importance, PDU set size, and end of data burst (EDB). Here, the PDU set importance is used to indicate the importance of a PDU set relative to other PDU sets in the same QoS flow.

[0175] It can be understood that the UPF performs the mapping of the SDF to the QoS flow based on the PDR, and maps (also referred to as encapsulating) the mutually related PDUs into the PDU set. In addition, the UPF can adopt the same QoS policy for all PDU sets in the QoS flow. For example, the UPF can apply the same PDU set QoS parameters to all PDU sets in the QoS flow. In one example, the UPF can map the application flow to the QoS flow based on the packet detection information in the PDR. Some PDUs in the QoS flow can be associated with media components (for example, intra-frame coded frames and predicted frames), and the UPF classifies these PDUs as belonging to the PDU set and performs corresponding control.

[0176] In some cases, the XRM service may be a multimedia type of service. The data stream (traffic) of the XRM service may be multiplexed in the same 5-tuple for transmission. The 5-tuple constitutes an end-to-end transport layer connection. In this case, the data stream of the XRM service may be referred to as a multiplexed traffic flow. The multiplexed traffic flow may include one or more subflows multiplexed in an end-to-end transport layer connection (e.g., a 5-tuple). In one example, the 5-tuple may be a 5-tuple that complies with the quick UDP internet connections (QUIC) protocol. In some embodiments, different substreams of the XRM service may have different QoS requirements. Then, different data streams may be transmitted using different QUIC connections or different QUIC substreams.

[0177] Therefore, the communication system needs to be able to identify the multiplexed data streams, so as to implement different QoS processing for the multiplexed data streams.

[0178] Figure 2A is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, which is applied to a communication system 100. As shown in Figure 2A, the method includes steps S2101 to S2117.

[0179] In step S2101 , the fifth network element 1035 sends sixth information to the sixth network element 1036 .

[0180] In some embodiments, the sixth network element 1036 may receive sixth information.

[0181] In some embodiments, the sixth information may be used to request determination of a third rule.

[0182] In some embodiments, the sixth information may be used to request the third network element 1033 to make a policy decision.

[0183] In some embodiments, the name of the sixth information is not limited, and it can be, for example, session creation request information, session QoS request information, etc.

[0184] In some embodiments, the sixth information may include indication information, which is used to indicate whether to adopt the multiplexed data stream.

[0185] In some embodiments, the indication information may be used to indicate whether the data stream of the first service is a multiplexed data stream.

[0186] In some embodiments, the indication information may include at least one of the following: a multiplexed data flow indication, a sub-flow QoS mapping indication.

[0187] In some embodiments, the multiplexed data stream indication may be used to indicate that the data stream of the first service is a multiplexed data stream.

[0188] In some embodiments, the sub-flow QoS mapping indication may be used to indicate QoS mapping for a sub-flow in the data flow of the first service.

[0189] In some embodiments, the sixth information may be sent by the fifth network element 1035 to the sixth network element 1036 via the service-based interface Nnef.

[0190] In some embodiments, the sixth information may be carried in a request message. In one example, the request message may be an AF session resource request message. In one example, the AF session resource request message may be an Nnef_AFSessionWithQoS_Create request message.

[0191] In some embodiments, the sixth information may further include description information.

[0192] In some embodiments, the description information may include at least one of the following: protocol description information, encryption auxiliary information, and mapping requirement information.

[0193] In some embodiments, protocol description information may be used to describe the QUIC protocol.

[0194] In some embodiments, the encryption auxiliary information may be used to identify the encryption sub-stream. In one example, the multiplexed data stream may include an encryption sub-stream, and the description information may include the encryption auxiliary information for the encryption sub-stream.

[0195] In some embodiments, mapping requirement information may be used to indicate mapping requirements for the multiplexed data stream.

[0196] In some embodiments, the mapping requirement information may include at least one of the following: media type, mapping type.

[0197] In some embodiments, the media type may be the media type of the substream of the first service. In some embodiments, the media type may include at least one of the following: video, audio. In one example, the media type of one or more substreams of the first service may be video. In one example, the media type of one or more substreams of the first service may be audio. In one example, the media type of one or more substreams of the first service may be video, and the media type of one or more substreams may be audio. It is understandable that the media type may also include other types (e.g., tactile feedback), which is not specifically limited in the embodiments of the present disclosure.

[0198] In some embodiments, the mapping type may include one of the following: one-to-one mapping, one-to-many mapping, many-to-one mapping, and many-to-many mapping. In one example, under the one-to-one mapping type, one subflow of the first service may be mapped to one QoS flow. In one example, under the one-to-many mapping type, one subflow of the first service may be mapped to multiple QoS flows. In one example, under the many-to-one mapping type, multiple subflows of the first service may be mapped to one QoS flow. In one example, under the many-to-many mapping type, multiple subflows of the first service may be mapped to multiple QoS flows.

[0199] In some embodiments, the request message may be a message in an AF QoS request procedure.

[0200] In some embodiments, the request message may be a message in the AF QoS update procedure.

[0201] In some embodiments, the sixth information may be included in the QoS requirement for the first service carried in the AF session resource request message.

[0202] In some embodiments, the AF session resource request message may further include at least one of the following information: protocol description and flow detection information.

[0203] In some embodiments, the protocol description may include at least one of the following information: protocol type, codec type, and media type. In some embodiments, at least one of the protocol type, codec type, and media type may be carried in the flow detection information.

[0204] In some embodiments, the request message may further include business information of the first service.

[0205] In some embodiments, the first service may be an XRM service, an interactive media service, etc. It is understandable that the first service may be other services, which are not specifically limited in the embodiments of the present disclosure.

[0206] In some embodiments, the service information of the first service may include at least one of the following: a subflow identifier of the first service, an address of the terminal 101, an identifier of the terminal 101, an AF service identifier (AF service identifier), an external application identifier, a flow description, single-network slice selection assistance information (S-NSSAI), and a data network name (DNN). It is understandable that the service information of the first service may include other information, which is not specifically limited in the embodiments of the present disclosure.

[0207] In some embodiments, the flow identifier of the first service can be used to identify a sub-flow and / or sub-flow group associated with the first service. In one example, the sub-flow identifier can be a multi-modal service ID. The multi-modal service ID can be used to identify all flows in a group of the first service.

[0208] In step S2102, the sixth network element 1036 performs authorization.

[0209] In some embodiments, the sixth network element 1036 may authorize the request message from the fifth network element 1035 .

[0210] In some embodiments, the fifth network element 1035 may be untrusted. In this case, the request message may be sent by the sixth network element 1036 to the third network element 1033.

[0211] In some embodiments, the sixth network element 1036 may perform mapping.

[0212] In some embodiments, the sixth network element 1036 may implement a mapping between the first service and the DNN and / or S-NSSAI. In one example, the sixth network element 1036 may map the AF service identifier of the first service to the DNN and / or S-NSSAI. In one example, the sixth network element 1036 may map the external application identifier to an application identifier known in the core network.

[0213] In some embodiments, the sixth network element 1036 may implement a mapping between an external identifier and an internal identifier of the terminal 101. In one example, the sixth network element 1036 may map the identifier of the terminal 101 outside the core network 103 to an identifier inside the core network 103 based on subscription information. In one example, the subscription information may be obtained from a unified data management (UDM).

[0214] In some embodiments, the sixth network element 1036 may implement a mapping between an external group identifier and an internal group identifier of the first service. In one example, the sixth network element 1036 may map the group identifier of the first service outside the core network 103 to a group identifier within the core network 103 based on subscription information. In one example, the subscription information may be obtained from the UDM.

[0215] In step S2103 , the sixth network element 1036 sends sixth information to the third network element 1033 .

[0216] In some embodiments, the sixth network element 1036 may send the sixth information received from the fifth network element 1035 to the third network element 1033 .

[0217] In some embodiments, the third network element 1033 may receive the sixth information.

[0218] In some embodiments, the sixth network element 1036 may also send at least one of the following to the third network element 1033: protocol description, flow detection information, and business information of the first service.

[0219] In some embodiments, the sixth network element 1036 may send the sixth information in different ways. In some embodiments, the sixth network element 1036 may determine the way to send the sixth information based on the information and / or parameters received from the fifth network element 1035.

[0220] In some embodiments, the sixth network element 1036 may send the sixth information in a manner including: sending through a time sensitive communication and time synchronization function (TSCTSF) or directly sending.

[0221] In some embodiments, the sixth network element 1036 may determine to send the sixth information to the third network element 1033 via the TSCTSF. In some embodiments, the sixth network element 1036 may send the sixth information to the TSCTSF via the service-based interface Ntsftsf, and the TSCTSF may then send the sixth information to the third network element 1033 via the service-based interface Npcf. In one example, the sixth network element 1036 may send the sixth information to the TSCTSF via an Ntsctsf_QoSandTSCAssistance_Create request message, and the TSCTSF may then send the sixth information to the third network element 1033 via an Npcf_PolicyAuthorization_Create request message or an Npcf_PolicyAuthorization_Update request message.

[0222] In some embodiments, the sixth network element 1036 may determine to send the sixth information directly to the third network element 1033. In some embodiments, the sixth network element 1036 may send the sixth information to the third network element 1033 via a service-based interface Npcf. In one example, the sixth network element 1036 may send the sixth information to the third network element 1033 via an Npcf_PolicyAuthorization_Create request message.

[0223] In some embodiments, steps S2101 to S2103 may be omitted (ie, not executed). In this case, the third network element 1033 will not obtain the sixth information from the fifth network element 1035. The third network element 1033 may obtain the sixth information in other ways.

[0224] In some embodiments, the third network element 1033 may receive the sixth information from the eighth network element (not shown). In one example, the eighth network element may send the sixth information to the third network element 1033 after acquiring the sixth information.

[0225] In some embodiments, the eighth network element may be a core network device having the same function as the third network element 1033. In other words, the eighth network element may be another third network element.

[0226] In some embodiments, the third network element 1033 may determine the sixth information based on operator operation and / or management configuration.

[0227] In some embodiments, the third network element 1033 may determine the sixth information according to local configuration.

[0228] In step S2104, the third network element 1033 makes a policy decision.

[0229] In some embodiments, the third network element 1033 may perform policy decision making to determine the third rule.

[0230] In some embodiments, the third rule may be used for traffic mapping of the multiplexed data stream of the first service.

[0231] In some embodiments, the third rule may be a QoS rule. In some embodiments, the third rule may belong to a QoS rule.

[0232] In some embodiments, the third rule may be new. In some embodiments, based on the sixth information, the third network element 1033 may determine a new first rule.

[0233] In some embodiments, the third rule may be updated. According to the sixth information, the third network element 1033 may determine to update the existing third rule.

[0234] In some embodiments, in determining the third rule, the third network element 1033 may consider the sixth information.

[0235] In some embodiments, the third rule may be determined based on consideration of the sixth information.

[0236] In some embodiments, the third rule may be determined based on consideration of the multiplexed data flow indication and / or the sub-flow QoS mapping indication and / or the sub-flow identification event.

[0237] In some embodiments, the subflow identification event may be a subflow ID / range event.

[0238] In some embodiments, the name of the third rule is not limited, and it can be, for example, a data flow mapping strategy, a data flow mapping rule, or a data flow mapping relationship.

[0239] In some embodiments, the third rule may be included in a policy and charging control (PCC) rule. In one example, the third rule may be part of the PCC rule.

[0240] In step S2105 , the third network element 1033 sends a response message to the sixth network element 1036 .

[0241] In some embodiments, the sixth network element 1036 may receive a response message.

[0242] In some embodiments, the third network element 1033 may send a response message after receiving the sixth information.

[0243] In some embodiments, the response message may be an Npcf_PolicyAuthorization_Create response message. In this case, the Npcf_PolicyAuthorization_Create response message may be sent by the third network element 1033 in response to the Npcf_PolicyAuthorization_Create request message.

[0244] In step S2106 , the sixth network element 1036 sends a response message to the fifth network element 1035 .

[0245] In some embodiments, the fifth network element 1035 may receive a response message.

[0246] In some embodiments, the response message may carry the authorization result of the third network element 1033 to the request message of the fifth network element 1035. In this way, the response message may be used to indicate to the fifth network element 1035 whether the request message is authorized.

[0247] In some embodiments, the sixth network element 1036 may send a response message to the fifth network element 1035 after receiving the response message from the third network element 1033 .

[0248] In some embodiments, the response message may be a Nnef_AFSessionWithQoS_Create response message.

[0249] In step S2107 , the third network element 1033 sends fifth information to the first network element 1031 .

[0250] In some embodiments, the first network element 1031 may receive the fifth information.

[0251] In some embodiments, the fifth information may be used to subscribe to notifications of sub-flow identification events. In other words, the fifth information may be used to indicate reporting of sub-flow identification events. In one example, the fifth information may be used by the third network element 1033 to subscribe to notifications of sub-flow identification events from the first network element 1031.

[0252] In some embodiments, the fifth information may be used to instruct acquisition of identification information.

[0253] In some embodiments, the fifth information may include at least one of the following: a multiplexed data flow indication, a sub-flow QoS mapping indication, and a sub-flow identification event.

[0254] In some embodiments, the fifth information may be determined by the third network element 1033 based on at least one of the following: information provided by the fifth network element 1035 and / or the sixth network element 1036, and operator policy.

[0255] In some embodiments, the information provided by the fifth network element 1035 and / or the sixth network element 1036 may be used to subscribe the third network element 1033 to notifications of sub-flow identification events.

[0256] In some embodiments, the operator policy may include at least one of the following: local configuration, OAM configuration.

[0257] In some embodiments, the fifth information may be sent to the first network element 1031 via the service-based interface Npcf.

[0258] In some embodiments, the third network element 1033 may initiate an SM Policy Association Modification procedure to send the fifth information.

[0259] In some embodiments, the fifth information may be carried in the Npcf_SMPolicyControl_UpdateNotify request message.

[0260] In some embodiments, the fifth information may further include at least one of the following: a first rule, indication information, and description information.

[0261] In step S2108 , the first network element 1031 sends a response message to the third network element 1033 .

[0262] In some embodiments, the third network element 1033 may receive a response message.

[0263] In some embodiments, the first network element 1031 may send a response message after receiving the fifth information.

[0264] In some embodiments, the response message may be an Npcf_SMPolicyControl_UpdateNotify response message.

[0265] In step S2109 , the first network element 1031 sends fifth information to the second network element 1032 .

[0266] In some embodiments, the second network element 1032 may receive the fifth information.

[0267] In some embodiments, the fifth information may be used to subscribe to notifications of sub-flow identification events.

[0268] In some embodiments, the fifth information may be used to subscribe for availability / support changes of PDU set processing.

[0269] In some embodiments, the fifth information may include the first rule.

[0270] In some embodiments, the first rule may be used for data stream mapping of the multiplexed data stream of the first service.

[0271] In some embodiments, the name of the first rule is not limited, and it can be, for example, a data flow mapping strategy, a data flow mapping rule, or a data flow mapping relationship.

[0272] In some embodiments, the first rule may be determined by the first network element 1031 according to the fifth information after receiving the fifth information.

[0273] In some embodiments, the first rule may be determined according to a third rule.

[0274] In some embodiments, the fifth information may include detection information for the packet detection rule.In some embodiments, the first rule may include detection information for the packet detection rule.

[0275] In some embodiments, the detection information may include at least one of the following: CN channel information, network instance, QoS flow identifier (QFI), IP packet filter set, application identifier, FQDN filter of DNS query message, connection identifier, and subflow identifier.

[0276] In some embodiments, the sub-flow identification may be indicated by a sub-flow range.

[0277] In some embodiments, the first network element 1031 may send the fifth information via an N4 session (N4session).

[0278] In some embodiments, the fifth information may be carried in the N4 Session Modification request message.

[0279] In some embodiments, step S2109 may be omitted (ie, not executed). In this case, the second network element 1032 will not obtain the fifth information from the first network element 1031. Then, the second network element 1032 may obtain the first rule in other ways.

[0280] In some embodiments, the first rule may be locally configured. In other words, the first rule may be pre-configured in the second network element 1032 or configured by the second network element 1032 .

[0281] In step S2110 , the second network element 1032 determines a mapping of the multiplexed data stream.

[0282] In some embodiments, the second network element 1032 may determine a mapping of the multiplexed data flow of the first service to the QoS flow according to the first rule.

[0283] In some embodiments, the first rule and / or QoS parameter in the fifth information may be configured to the second network element 1032. In this way, the second network element 1032 may implement mapping of sub-flows in the multiplexed data flow of the first service to QoS flows according to the first rule.

[0284] In some embodiments, upon detecting the traffic of the multiplexed data stream of the first service, the second network element 1032 may map the multiplexed data stream of the first service according to the first rule. In one example, the second network element 1032 may map the multiplexed data stream of the first service to one or more corresponding QoS flows according to the first rule.

[0285] In step S2111 , the second network element 1032 sends a response message to the first network element 1031 .

[0286] In some embodiments, the first network element 1031 may receive a response message.

[0287] In some embodiments, the second network element 1032 may send a response message via an N4 session.

[0288] In some embodiments, the response message may be an N4 Session Modification Response message.

[0289] In step S2112 , the first network element 1031 sends seventh information to the seventh network element 1037 .

[0290] In some embodiments, the seventh network element 1037 may receive the seventh information.

[0291] In some embodiments, the seventh information may be used to indicate QoS related information.

[0292] In some embodiments, the seventh information may include the second rule.

[0293] In some embodiments, the second rule may be the third rule, or be determined based on the third rule.

[0294] In some embodiments, the fourth information may be sent to the seventh network element 1037 via the service-based interface Namf.

[0295] In some embodiments, the first network element 1031 may send the seventh message to the seventh network element 1037 through a Namf_Communication_N1N2MessageTransfer service operation.

[0296] In some embodiments, during the Namf_Communication_N1N2MessageTransfer service operation, the first network element 1031 may send a Namf_Communication_N1N2MessageTransfer request message to the seventh network element 1037, and then the seventh network element 1037 may send a Namf_Communication_N1N2MessageTransfer response message to the first network element 1031. The seventh information may be carried in the Namf_Communication_N1N2MessageTransfer request message.

[0297] In some embodiments, at least one of the following may also be sent through the Namf_Communication_N1N2MessageTransfer service operation: N2 SM information, PDU session identifier, QFI, QoS configuration (QoS profile), and N1 SM container.

[0298] In step S2113 , the seventh network element 1037 sends seventh information to the access network device 102 .

[0299] In some embodiments, the access network device 102 may receive the seventh information.

[0300] In some embodiments, the seventh network element 1037 may send the seventh information to the access network device 102 via an N2 message.

[0301] In some embodiments, the N2 message may be an N2 PDU Session Request message.

[0302] In some embodiments, the N2 message may further include at least one of the following: N2 SM information, NAS message.

[0303] In some embodiments, the NAS message may include at least one of the following: a PDU session identifier, and an N1 SM container.

[0304] In some embodiments, the N1 SM container may include a PDU Session Modification Command.

[0305] In step S2114 , the access network device 102 establishes wireless resources with the terminal 101 .

[0306] In some embodiments, the access network device 102 may send AN dedicated signaling to exchange information with the terminal 101 .

[0307] In some embodiments, the access network device 102 may send the received seventh information to the terminal 101 .

[0308] In some embodiments, the access network device 102 may also send the received N2 SM information and / or NAS message to the terminal 101 .

[0309] In some embodiments, the seventh information enables wireless resources associated with the QoS rule to be established between the terminal 101 and the access network device 102 .

[0310] In step S2115 , the access network device 102 sends a confirmation message to the seventh network element 1037 .

[0311] In some embodiments, the seventh network element 1037 may receive an acknowlegement message (ACK).

[0312] In some embodiments, the access network device may send a confirmation message to the seventh network element 1037 via an N2 message.

[0313] In some embodiments, the confirmation message may be used to indicate an acknowledgement of the N2 PDU Session Request message.

[0314] In some embodiments, the confirmation message may be an N2 PDU Session Confirm message.

[0315] In some embodiments, the confirmation message may carry N2 SM information.

[0316] In step S2116 , the seventh network element 1037 sends the eighth information to the first network element 1031 .

[0317] In some embodiments, the first network element 1031 may receive the eighth information.

[0318] In some embodiments, the eighth information may include N2 SM information.

[0319] In some embodiments, the seventh network element 1037 may send the eighth information to the first network element 1031 through the Nsmf_PDUSession_UpdateSMContext service operation.

[0320] In some embodiments, in the Nsmf_PDUSession_UpdateSMContext service operation, the seventh network element 1037 may send an Nsmf_PDUSession_UpdateSMContext request message to the first network element 1031, and then the first network element 1031 may send an Nsmf_PDUSession_UpdateSMContext response message to the seventh network element 1037. The eighth information may be carried in the Nsmf_PDUSession_UpdateSMContext request message.

[0321] In step S2117 , the first network element 1031 sends the eighth information to the second network element 1032 .

[0322] In some embodiments, the first network element 1031 may send the received eighth information to the second network element 1032 .

[0323] In some embodiments, the second network element 1032 may receive the eighth information.

[0324] In some embodiments, the first network element 1031 may send the eighth information to the second network element 1032 through an N4 Session Modification service operation.

[0325] In some embodiments, during the N4 Session Modification service operation, the first network element 1031 may send an N4 Session Modification request message to the second network element 1032, and then the second network element 1032 may send an N4 Session Modification response message to the first network element 1031. The eighth information may be carried in the N4 Session Modification request message.

[0326] In some embodiments, the eighth information may be used to update the N4 session of the second network element 1032 .

[0327] In some embodiments, with respect to the embodiment shown in FIG2A , the first network element 1031 may be an SMF, the second network element 1032 may be a UPF, the third network element 1033 may be a PCF, the fifth network element 1035 may be an AF, the sixth network element 1036 may be an NEF, and the seventh network element 1037 may be an AMF. It is understood that one or more of the first network element 1031, the second network element 1032, the third network element 1033, the fifth network element 1035, the sixth network element 1036, and the seventh network element 1037 may be other network functions, which are not specifically limited in the present disclosure.

[0328] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2117. For example, step S2101 can be implemented as an independent embodiment. For example, step S2103 can be implemented as an independent embodiment. For example, step S2107 can be implemented as an independent embodiment. For example, step S2109 can be implemented as an independent embodiment. For example, the combination of steps S2107 and S2109 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S2101 to S2117 are not limited to this.

[0329] In some embodiments, at least two of steps S2101 to S2117 may be performed in an order swapped or simultaneously. For example, steps S2105 and S2106 may be performed in an order swapped or simultaneously. For example, steps S2108 and S2109 may be performed in an order swapped or simultaneously.

[0330] In some embodiments, steps S2102 to S2117 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0331] In some embodiments, steps S2101 , S2102 , S2104 to S2117 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0332] In some embodiments, steps S2101 to S2106 and S2108 to S2117 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0333] In some embodiments, steps S2101 to S2108 and S2110 to S2117 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0334] Figure 2B is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which is applied to a communication system 100. As shown in Figure 2B, the method includes steps S2201 to S2213.

[0335] In step S2201 , the fifth network element 1035 sends ninth information to the third network element 1033 .

[0336] In some embodiments, the third network element 1033 may receive the ninth information.

[0337] In some embodiments, the ninth information may be used to determine a mapping rule for the multiplexed data stream.

[0338] In some embodiments, the ninth information may be obtained by the fifth network element 1035 from the fourth network element 1034 .

[0339] In some embodiments, the ninth information may include identification information of one or more sub-streams.

[0340] In some embodiments, the ninth information may be sent together with the sixth information. Specifically, the fifth network element 1035 may simultaneously send the sixth information and the ninth information to the third network element 1033. The sixth information and the ninth information may be carried in the same message.

[0341] In some embodiments, the ninth information may be sent independently of the sixth information.

[0342] In some cases, the implementation of step S2201 can refer to the implementation of steps S2101, S2102, and S2103 in Figure 2A, and will not be repeated here.

[0343] In step S2202 , the third network element 1033 sends ninth information to the first network element 1031 .

[0344] In some embodiments, the first network element 1031 may receive ninth information.

[0345] In some embodiments, the ninth information may be sent together with the fifth information. Specifically, the third network element 1033 may simultaneously send the fifth information and the ninth information to the first network element 1031. The fifth information and the ninth information may be carried in the same message.

[0346] In some embodiments, the ninth information may be sent independently of the fifth information.

[0347] In some cases, the implementation of step S2202 can refer to the implementation of step S2107 in Figure 2A, which is not repeated here.

[0348] It can be understood that steps S2201 and S2202 are optional steps.

[0349] In step S2203 , the second network element 1032 receives a data stream from the fourth network element 1034 .

[0350] In some embodiments, the fourth network element 1034 may send at least one sub-flow to the second network element 1032 .

[0351] In some embodiments, the second network element 1032 may receive the sub-flow on a user plane.

[0352] In some embodiments, the sub-flow received by the second network element 1032 may be for the first service.

[0353] In some embodiments, the sub-flow from the fourth network element 1034 may be a downlink sub-flow.

[0354] In step S2204 , the second network element 1032 receives a data stream from the terminal 101 .

[0355] In some embodiments, the terminal 101 may send at least one sub-flow to the second network element 1032 .

[0356] In some embodiments, the second network element 1032 may receive the sub-flow on a user plane.

[0357] In some embodiments, the sub-flow received by the second network element 1032 may be for the first service.

[0358] In some embodiments, the sub-flow from terminal 101 may be an uplink sub-flow.

[0359] In step S2205 , the second network element 1032 determines identification information.

[0360] In some embodiments, the second network element 1032 may identify at least one sub-flow from the fourth network element 1034 to obtain identification information corresponding to the sub-flow.

[0361] In some embodiments, the identification information may be used to identify the sub-stream.

[0362] In some embodiments, the identification information may include at least one of the following: sub-flow identification information, PSI (PDU set importance) information.

[0363] In some embodiments, sub-stream identification information may be used to identify the sub-stream.

[0364] In some embodiments, the identification information may include at least one of the following: a substream identifier, a substream identifier range, or a substream identifier list. A substream identifier may include identifiers of one or more substreams. A substream identifier range may include an identifier range consisting of identifiers of one or more substreams. A substream identifier list may include identifiers of one or more substreams.

[0365] In some embodiments, a sub-stream in a multiplexed data stream may be a stream.

[0366] In some embodiments, the multiplexed data stream can be implemented based on a protocol such as QUIC. In this case, a connection can be established based on the QUIC protocol. The multiplexed data stream can be carried on the connection. There can be one or more streams in the connection.

[0367] In some embodiments, each stream can be identified by a stream ID. In one example, different streams can be distinguished by the stream ID. In another example, different types of streams can be distinguished by the stream ID.

[0368] In some embodiments, the sub-stream identification information for a stream may include at least one of the following: a stream ID, a stream ID interval, and a stream ID list.

[0369] In some embodiments, a sub-stream in a multiplexed data stream may be a track.

[0370] In some embodiments, the multiplexed data stream may be implemented based on a protocol such as MoQT (media over QUIC transport), in which case the multiplexed data stream may have one or more tracks.

[0371] In some embodiments, each track can be identified by a track ID. In one example, different tracks can be distinguished by track IDs. In another example, different types of tracks can be distinguished by track IDs.

[0372] In some embodiments, the sub-flow identification information for a track may include at least one of the following: a track ID, a track ID interval, and a track ID list.

[0373] In some embodiments, each track can be identified by a track name. In one example, different tracks can be distinguished by track names. In another example, different types of tracks can be distinguished by track names.

[0374] In some embodiments, the sub-flow identification information for a track may include at least one of the following: a track name, a track name interval, and a track name list.

[0375] It is understandable that, for the multiplexed data stream composed of tracks, the tracks can be identified by track IDs and / or track names.

[0376] In some embodiments, the sub-streams in the multiplexed data stream may be encrypted streams.

[0377] In some embodiments, the multiplexed data stream may be implemented based on a method such as RoQ (RTP over QUIC, QUIC carrying RTP). In this case, the multiplexed data stream may include one or more encrypted streams.

[0378] In some embodiments, each encrypted stream can be identified by an encrypted stream ID. In one example, different encrypted streams can be distinguished by the encrypted stream ID. In another example, different types of encrypted streams can be distinguished by the encrypted stream ID.

[0379] In some embodiments, the sub-stream identification information for the encrypted stream may include at least one of the following: an encrypted stream ID, an encrypted stream ID interval, and an encrypted stream ID list.

[0380] In some embodiments, the PSI information may be used to indicate the importance of a PDU set in a sub-stream. In some cases, importance may also be understood as a degree of importance, an importance level, a priority level, and the like.

[0381] In some embodiments, the PSI information may indicate the importance of the PDU set and indirectly identify the sub-flow to which the PDU set corresponds.

[0382] In some embodiments, the PSI information may include at least one of the following: a PSI, a PSI interval, or a PSI list. The PSI may indicate one or more importance values / levels. A PSI interval may include an importance range consisting of one or more values / levels. A PSI list may include one or more importance values / levels.

[0383] In some embodiments, the second network element 1032 may obtain identification information from metadata of a data packet in the sub-flow.

[0384] It should be noted that step S2201 and / or step S2202 and / or step S2203 may be performed by the second network element 1032 itself, or may be performed by the second network element 1032 based on the fifth information from the first network element 1031. The fifth information may be used to subscribe to notifications of subflow identification events. In other words, the fifth information may be used to instruct the acquisition of identification information.

[0385] In practical applications, data flow (traffic) can also be understood as data flow (traffc flow). In some cases, subflow (subflow) can be stream, track, encrypted stream or other types of data, which is not specifically limited in the embodiments of the present disclosure.

[0386] In step S2206 , the second network element 1032 sends the first information to the first network element 1031 .

[0387] In some embodiments, the first network element 1031 may receive the first information.

[0388] In some embodiments, the first information may be used to determine a mapping rule for the multiplexed data stream.

[0389] In some embodiments, the second network element 1032 may send the first information based on a subscription message from the first network element 1031. In one example, the second network element 1032 may determine to send the first information to the first network element 1031 after receiving the fifth information. In this case, the first information may be sent by the second network element 1032 in response to the subscription from the first network element 1031.

[0390] In some embodiments, the second network element 1032 may send the first information according to a protocol. In this case, the first information may be sent by the second network element 1032 itself according to the protocol.

[0391] In some embodiments, the first information may include identification information determined by the second network element 1032 based on the sub-flow.

[0392] In some embodiments, the first information may include one identification information or a group of identification information. In this case, when the second network element 1032 detects new identification information, the second network element 1032 may send the first information. The first information may include the detected new identification information.

[0393] In some embodiments, the first information may be carried in a notification for subscription, so as to notify a subscribed sub-stream identifier / range event.

[0394] In some embodiments, the first information may be sent from the second network element 1032 to the first network element 1031 via the N4 interface.

[0395] In some embodiments, the first information may be carried in an N4 session modification request message. In this case, the second network element 1032 may send an N4 session modification request message to the first network element 1031, and carry the first information in the N4 session modification request message.

[0396] In some embodiments, the first information may be carried in an N4 session modification response message. In this case, the second network element 1032 may send an N4 session modification response message to the first network element 1031, and the N4 session modification response message may carry the first information.

[0397] In step S2207 , the first network element 1031 sends first information to the third network element 1033 .

[0398] In some embodiments, the third network element 1033 may receive the first information.

[0399] In some embodiments, the first network element 1031 may send the first information to the third network element 1033 so that the third network element 1033 can determine the third rule.

[0400] In step S2208 , the third network element 1033 sends the first information to the fifth network element 1035 .

[0401] In some embodiments, when the fifth network element 1035 subscribes to the first information, the third network element 1033 may send the first information to the fifth network element 1035 .

[0402] In some embodiments, when the fifth network element 1035 subscribes to the sub-flow identification event, the third network element 1033 may send identification information to the fifth network element 1035 .

[0403] In some embodiments, the third network element 1033 may directly send the first information to the fifth network element 1035 .

[0404] In some embodiments, the third network element 1033 may send the first information to the fifth network element 1035 via the sixth network element 1036 .

[0405] It can be understood that steps S2203 to S2208 are optional steps.

[0406] In step S2209, the third network element 1033 determines a third rule.

[0407] In some embodiments, the third network element 1033 may obtain the first information and the ninth information. In this case, the third network element 1033 may determine the third rule based on the first information and / or the ninth information. In one example, the third network element 1033 may determine the third rule based on the identification information in the first information and / or the identification information in the ninth information.

[0408] In some embodiments, the third network element 1033 may only obtain the first information. In this case, the third network element 1033 may determine the third rule based on the first information. In one example, the third network element 1033 may determine the third rule based on the identification information in the first information.

[0409] In some embodiments, the third network element 1033 may only obtain the ninth information. In this case, the third network element 1033 may determine the third rule based on the ninth information. In one example, the third network element 1033 may determine the third rule based on the identification information in the ninth information.

[0410] In some embodiments, the third network element 1033 may generate a new third rule based on the first information and / or the ninth information.

[0411] In some embodiments, the third network element 1033 may update the third rule according to the first information and / or the ninth information.

[0412] In some embodiments, the third rule determined by the third network element 1033 may be a PCC rule. The PCC rule may include a QoS policy.

[0413] It should be noted that the identification information in the first information and the identification information in the ninth information may be completely identical, partially identical, or completely different. In some embodiments, the substream identified by the identification information in the first information may be different from the substream identified by the identification information in the ninth information.

[0414] In step S2210 , the third network element 1033 may send fourth information to the first network element 1031 .

[0415] In some embodiments, the first network element 1031 may receive fourth information.

[0416] In some embodiments, the fourth information may be used to indicate a mapping policy for QoS processing.

[0417] In some embodiments, the fourth information may include the third rule.

[0418] It is understood that steps S2207 to S2210 are optional. In some cases, the first network element 1031 may not perform step S2207, i.e., may not send the first information to the third network element 1033. In some cases, the first network element 1031 may perform step S2207, i.e., may send the first information to the third network element 1033; however, the third network element 1033 may not perform step S2208, i.e., may not send the first information to the fifth network element 1035.

[0419] In some embodiments, the fourth information may be sent to the first network element 1031 via the service-based interface Npcf.

[0420] In some embodiments, the third network element 1033 may initiate an SM Policy Association Modification process to send the fourth information.

[0421] In some embodiments, the fourth information may be carried in the Npcf_SMPolicyControl_UpdateNotify request message.

[0422] In some cases, the implementation of step S2210 can refer to the implementation of step S2107 in Figure 2A, and will not be repeated here.

[0423] In step S2211 , the first network element 1031 determines a mapping rule.

[0424] In some embodiments, the first network element 1031 may receive the fourth information. In this case, the first network element 1031 may determine the mapping rule according to the received third rule.

[0425] In some embodiments, the first network element 1031 may not receive the fourth information. In this case, the first network element 1031 may determine the mapping rule according to the received first information.

[0426] In some embodiments, the first network element 1031 may receive the fourth information. In this case, the first network element 1031 may determine the mapping rule according to at least one of the received third rule, the first information, and the ninth information.

[0427] In some embodiments, the first network element 1031 may add the identification information to the packet filter set. In one example, the first network element 1031 may add the identification information of the upstream subflow and / or the identification information of the downstream subflow in the identification information to the packet filter set.

[0428] In some embodiments, the mapping rule may include a first rule and / or a second rule.

[0429] In some embodiments, the first network element 1031 may determine a first rule. The first rule may be used for downlink QoS processing.

[0430] In some embodiments, the first network element 1031 may add identification information of the downstream sub-flow to the packet filter set to determine the first rule.

[0431] In some embodiments, the first network element 1031 may add identification information of the downstream sub-flow to the packet filter set, and determine the first rule in combination with the third rule.

[0432] In some embodiments, the first network element 1031 may determine a second rule. The second rule may be used for uplink QoS processing.

[0433] In some embodiments, the first network element 1031 may add identification information of the upstream sub-flow to the packet filter set to determine the second rule.

[0434] In some embodiments, the first network element 1031 may add identification information of the upstream sub-flow to the packet filter set, and determine the second rule in combination with the third rule.

[0435] In step S2212 , the first network element 1031 sends second information to the second network element 1032 .

[0436] In some embodiments, the second network element 1032 may receive the second information.

[0437] In some embodiments, the second information may be used to indicate the first rule.

[0438] In some embodiments, the second information may be used by the second network element 1032 to perform data stream mapping of the multiplexed data stream.

[0439] In some embodiments, the second information may be used by the second network element 1032 to perform QoS processing on the downlink.

[0440] In some cases, the implementation of step S2212 can refer to the implementation of step S2109 in Figure 2A, and will not be repeated here.

[0441] In step S2213 , the first network element 1031 sends third information to the terminal 101 .

[0442] In some embodiments, the first network element 1031 may send the third information to the terminal 101 via the seventh network element 1037 and the access network device 102 .

[0443] In some embodiments, terminal 101 may receive third information.

[0444] In some embodiments, the third information may be used to indicate the second rule.

[0445] In some embodiments, the third information may be used by the terminal 101 to perform data stream mapping of the multiplexed data stream.

[0446] In some embodiments, the third information may be used by the terminal 101 to perform uplink QoS processing.

[0447] In some cases, the implementation of step S2213 can refer to the implementation of steps S2112 to S2114 in Figure 2A, and will not be repeated here.

[0448] In some embodiments, with respect to the embodiment shown in FIG2B , the first network element 1031 may be an SMF, the second network element 1032 may be a UPF, the third network element 1033 may be a PCF, the fourth network element 1034 may be an AS, the fifth network element 1035 may be an AF, the sixth network element 1036 may be an NEF, and the seventh network element 1037 may be an AMF. It is understood that one or more of the first network element 1031, the second network element 1032, the third network element 1033, the fifth network element 1035, the sixth network element 1036, and the seventh network element 1037 may be other network functions, which are not specifically limited in the present disclosure.

[0449] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2213. For example, step S2202 may be implemented as an independent embodiment. For example, step S2206 may be implemented as an independent embodiment. For example, step S2207 may be implemented as an independent embodiment. For example, step S2213 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S2201 to S2213 are not limited to this.

[0450] In some embodiments, at least two of steps S2201 to S2211 may be swapped in order or performed simultaneously. For example, steps S2202 and S2207 may be swapped in order or performed simultaneously. For example, steps S2203 and S2204 may be swapped in order or performed simultaneously. For example, steps S2208 and S2209 may be swapped in order or performed simultaneously. For example, steps S2212 and S2213 may be swapped in order or performed simultaneously.

[0451] In some embodiments, steps S2201 and S2203 to S2213 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0452] In some embodiments, steps S2201 to S2205 and S2207 to S2213 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0453] In some embodiments, steps S2201 to S2206 and S2208 to S2213 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0454] In some embodiments, steps S2201 to S2212 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0455] It should be noted that the communication system 100 may include at least a part of the first network element 1031, the second network element 1032, the third network element 1033, the fourth network element 1034, the fifth network element 1035, the sixth network element 1036, the seventh network element 1037, and the eighth network element (not shown) involved above.

[0456] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2A and FIG. 2B .

[0457] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0458] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0459] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0460] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0461] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0462] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "some", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, some A, any A, or first A, etc., but not limited to this.

[0463] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0464] Figure 3A is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, an embodiment of the present disclosure relates to a communication method. The communication method in this embodiment can be performed by the first network element 1031. The method includes steps S3101 to S3107.

[0465] In step S3101, the fifth information is obtained.

[0466] The optional implementation of step S3101 can refer to the optional implementation of step S2107 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0467] In some embodiments, the first network element 1031 may receive the fifth information sent by the third network element 1033 , but is not limited thereto and may also receive the fifth information sent by other entities.

[0468] In some embodiments, the first network element 1031 may obtain fifth information specified by the protocol.

[0469] In some embodiments, the first network element 1031 may obtain the fifth information from an upper layer.

[0470] In some embodiments, the first network element 1031 may perform processing to obtain the fifth information.

[0471] In some embodiments, step S3101 may be omitted, and the first network element 1031 may autonomously implement the function indicated by the fifth information, or the above function may be default or by default.

[0472] In step S3102, a response message is sent.

[0473] The optional implementation of step S3102 can refer to the optional implementation of step S2108 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0474] In some embodiments, the first network element 1031 may send a response message to the third network element 1033 , but is not limited thereto and may also send a response message to other entities.

[0475] In step S3103, the fifth information is sent.

[0476] The optional implementation of step S3103 can refer to the optional implementation of step S2109 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0477] In some embodiments, the first network element 1031 may send the fifth information to the second network element 1032 , but is not limited thereto and the fifth information may also be sent to other entities.

[0478] In step S3104, a response message is obtained.

[0479] The optional implementation of step S3104 can refer to the optional implementation of step S2111 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0480] In some embodiments, the first network element 1031 may receive a response message sent by the second network element 1032 , but is not limited thereto and may also receive a response message sent by other entities.

[0481] In step S3105, the seventh information is sent.

[0482] The optional implementation of step S3105 can refer to the optional implementation of step S2112 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0483] In some embodiments, the first network element 1031 may send the seventh information to the seventh network element 1037 , but is not limited thereto and the seventh information may also be sent to other entities.

[0484] In step S3106, the eighth information is obtained.

[0485] The optional implementation of step S3106 can refer to the optional implementation of step S2116 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0486] In some embodiments, the first network element 1031 may receive the eighth information sent by the seventh network element 1037 , but is not limited thereto and may also receive the eighth information sent by other entities.

[0487] In step S3107, the eighth information is sent.

[0488] The optional implementation of step S3107 can refer to the optional implementation of step S2117 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0489] In some embodiments, the first network element 1031 may send the eighth information to the second network element 1032 , but is not limited thereto and the eighth information may also be sent to other entities.

[0490] The communication method according to the embodiments of the present disclosure may include at least one of steps S3101 to S3107. For example, S3103 may be implemented as an independent embodiment, S3105 may be implemented as an independent embodiment, and the combination of steps S3103 and S3105 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0491] In some embodiments, at least two of steps S3101 to S3107 may be executed in an interchangeable order or simultaneously. For example, step S3103 and step S3105 may be executed in an interchangeable order or simultaneously.

[0492] In some embodiments, steps S3101, S3102, S3104, S3105, S3106, and S3107 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0493] In some embodiments, steps S3101, S3102, S3103, S3104, S3106, and S3107 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0494] Figure 3B is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, an embodiment of the present disclosure relates to a communication method. The communication method in this embodiment can be performed by the first network element 1031. The method includes steps S3201 to S3207.

[0495] In step S3201, the ninth information is obtained.

[0496] The optional implementation of step S3201 can refer to the optional implementation of step S2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0497] In some embodiments, the first network element 1031 may receive the ninth information sent by the third network element 1033 , but is not limited thereto and may also receive the ninth information sent by other entities.

[0498] In step S3202, first information is obtained.

[0499] The optional implementation of step S3202 can refer to the optional implementation of step S2206 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0500] In some embodiments, the first network element 1031 may receive the first information sent by the second network element 1032 , but is not limited thereto and may also receive the first information sent by other entities.

[0501] In step S3203, the first information is sent.

[0502] The optional implementation of step S3203 can refer to the optional implementation of step S2207 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0503] In some embodiments, the first network element 1031 may send the first information to the third network element 1033 , but is not limited thereto and may also send the first information to other entities.

[0504] In step S3204, the fourth information is obtained.

[0505] The optional implementation of step S3204 can refer to the optional implementation of step S2210 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0506] In some embodiments, the first network element 1031 may receive the fourth information sent by the third network element 1033 , but is not limited thereto and may also receive the fourth information sent by other entities.

[0507] In step S3205, a mapping rule is determined.

[0508] The optional implementation of step S3205 can refer to the optional implementation of step S2211 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0509] In step S3206, the second information is sent.

[0510] The optional implementation of step S3206 can refer to the optional implementation of step S2212 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0511] In some embodiments, the first network element 1031 may send the second information to the second network element 1032 , but is not limited thereto and the second information may also be sent to other entities.

[0512] In step S3207, the third information is sent.

[0513] The optional implementation of step S3207 can refer to the optional implementation of step S2213 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0514] In some embodiments, the first network element 1031 may send the third information to the terminal 101 , but is not limited thereto and may also send the third information to other entities.

[0515] The communication method according to the embodiments of the present disclosure may include at least one of steps S3201 to S3207. For example, S3201 may be implemented as an independent embodiment, S3202 may be implemented as an independent embodiment, S3203 may be implemented as an independent embodiment, step S3206 may be implemented as an independent embodiment, and the combination of steps S3202 and S3203 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0516] In some embodiments, at least two of steps S3201 to S3207 may be executed in an order swapped or simultaneously. For example, step S3206 and step S3207 may be executed in an order swapped or simultaneously.

[0517] In some embodiments, steps S3202, S3203, S3204, S3205, S3206, and S3207 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0518] In some embodiments, steps S3201, S3203, S3204, S3205, S3206, and S3207 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0519] In some embodiments, steps S3201, S3202, S3204, S3205, S3206, and S3207 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0520] In some embodiments, steps S3201, S3202, S3203, S3204, S3205, and S3207 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0521] Figure 4A is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 4A, an embodiment of the present disclosure relates to a communication method. The communication method in this embodiment can be performed by the second network element 1032. The method includes steps S4101 to S4104.

[0522] In step S4101, the fifth information is obtained.

[0523] The optional implementation of step S4101 can refer to the optional implementation of step S2109 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0524] In some embodiments, the second network element 1032 may receive the fifth information sent by the first network element 1031 , but is not limited thereto and may also receive the fifth information sent by other entities.

[0525] In step S4102, the mapping of the multiplexed data stream is determined.

[0526] The optional implementation of step S4102 can refer to the optional implementation of step S2110 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0527] In step S4103, a response message is sent.

[0528] The optional implementation of step S4103 can refer to the optional implementation of step S2111 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0529] In some embodiments, the second network element 1032 may send a response message to the first network element 1031 , but is not limited thereto and may also send a response message to other entities.

[0530] In step S4104, the eighth information is obtained.

[0531] The optional implementation of step S4104 can refer to the optional implementation of step S2117 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0532] In some embodiments, the second network element 1032 may receive the eighth information sent by the first network element 1031 , but is not limited thereto and may also receive the eighth information sent by other entities.

[0533] The communication method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4104. For example, S4101 may be implemented as an independent embodiment, but is not limited thereto.

[0534] In some embodiments, steps S4102, S4103, and S4104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0535] Figure 4B is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 4B, an embodiment of the present disclosure relates to a communication method. The communication method in this embodiment can be performed by the second network element 1032. The method includes steps S4201 to S4205.

[0536] In step S4201, the downlink data flow is obtained.

[0537] The optional implementation of step S4201 can refer to the optional implementation of step S2201 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0538] In some embodiments, the second network element 1032 may receive a downlink data stream sent by the fourth network element 1034 , but is not limited thereto and may also receive a downlink data stream sent by other entities.

[0539] In step S4202, the uplink data stream is obtained.

[0540] The optional implementation of step S4202 can refer to the optional implementation of step S2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0541] In some embodiments, the second network element 1032 may receive an uplink data stream sent by the terminal 101, but is not limited thereto and may also receive an uplink data stream sent by other entities.

[0542] In step S4203, identification information is determined.

[0543] The optional implementation of step S4203 can refer to the optional implementation of step S2203 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0544] In step S4204, the first information is sent.

[0545] The optional implementation of step S4204 can refer to the optional implementation of step S2204 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0546] In some embodiments, the second network element 1032 may send the first information to the first network element 1031 , but is not limited thereto and may also send the first information to other entities.

[0547] In step S4205, the second information is obtained.

[0548] The optional implementation of step S4205 can refer to the optional implementation of step S2210 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0549] In some embodiments, the second network element 1032 may receive the second information sent by the first network element 1031 , but is not limited thereto and may also send the second information to other entities.

[0550] The communication method involved in the embodiment of the present disclosure may include at least one of steps S4201 to S4205. For example, S4204 may be implemented as an independent embodiment, but is not limited thereto.

[0551] In some embodiments, at least two of steps S4201 to S4205 may be executed in an order-switched or synchronously. For example, step S4201 and step S4202 may be executed in an order-switched or synchronously.

[0552] In some embodiments, steps S4201, S4202, S4203, and S4205 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0553] Figure 5A is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 5A, an embodiment of the present disclosure relates to a communication method. The communication method in this embodiment can be performed by the third network element 1033. The method includes steps S5101 to S5105.

[0554] In step S5101, the sixth information is obtained.

[0555] The optional implementation of step S5101 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0556] In some embodiments, the third network element 1033 may receive the sixth information sent by the sixth network element 1036, but is not limited thereto and may also receive the sixth information sent by other entities.

[0557] In step S5102, policy decision is performed.

[0558] The optional implementation of step S5102 can refer to the optional implementation of step S2104 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0559] In step S5103, a response message is sent.

[0560] The optional implementation of step S5103 can refer to the optional implementation of step S2105 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0561] In some embodiments, the third network element 1033 may send a response message to the sixth network element 1036 , but is not limited thereto and may also send a response message to other entities.

[0562] In step S5104, the fifth information is sent.

[0563] The optional implementation of step S5104 can refer to the optional implementation of step S2107 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0564] In some embodiments, the third network element 1033 may send the fifth information to the first network element 1031 , but is not limited thereto and may also send the fifth information to other entities.

[0565] In step S5105, a response message is obtained.

[0566] The optional implementation of step S5105 can refer to the optional implementation of step S2108 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0567] In some embodiments, the third network element 1033 may receive a response message sent by the first network element 1031 , but is not limited thereto and may also receive a response message sent by other entities.

[0568] The communication method involved in the embodiment of the present disclosure may include at least one of steps S5101 to S5105. For example, S5104 may be implemented as an independent embodiment, but is not limited thereto.

[0569] In some embodiments, steps S5101, S5102, S5103, and S5105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0570] Figure 5B is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 5B, an embodiment of the present disclosure relates to a communication method. The communication method in this embodiment can be performed by the third network element 1033. The method includes steps S5201 to S5206.

[0571] In step S5201, the ninth information is obtained.

[0572] The optional implementation of step S5201 can refer to the optional implementation of step S2201 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0573] In some embodiments, the third network element 1033 may receive the ninth information sent by the fifth network element 1035 , but is not limited thereto and may also receive the ninth information sent by other entities.

[0574] In step S5202, the ninth information is sent.

[0575] The optional implementation of step S5202 can refer to the optional implementation of step S2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0576] In some embodiments, the third network element 1033 may send the ninth information to the first network element 1031 , but is not limited thereto and may also send the ninth information to other entities.

[0577] In step S5203, first information is obtained.

[0578] The optional implementation of step S5203 can refer to the optional implementation of step S2207 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0579] In some embodiments, the third network element 1033 may receive the first information sent by the first network element 1031 , but is not limited thereto and may also receive the first information sent by other entities.

[0580] In step S5204, the first information is sent.

[0581] The optional implementation of step S5204 can refer to the optional implementation of step S2208 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0582] In some embodiments, the third network element 1033 may send the first information to the fifth network element 1035 , but is not limited thereto and may also send the first information to other entities.

[0583] In step S5205, a mapping rule is determined.

[0584] The optional implementation of step S5205 can refer to the optional implementation of step S2209 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0585] In step S5206, the fourth information is sent.

[0586] The optional implementation of step S5206 can refer to the optional implementation of step S2210 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0587] In some embodiments, the third network element 1033 may send the fourth information to the first network element 1031 , but is not limited thereto and may also send the fourth information to other entities.

[0588] The communication method involved in the embodiment of the present disclosure may include at least one of steps S5201 to S5206. For example, S5201 may be implemented as an independent embodiment, and S5203 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0589] In some embodiments, steps S5201, S5203, S5204, S5205, and S5206 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0590] In some embodiments, steps S5201, S5202, S5204, S5205, and S5206 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0591] FIG6A is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG6A , an embodiment of the present disclosure relates to a communication method. The communication method in this embodiment can be executed by terminal 101. The method includes step S6101.

[0592] In step S6101, wireless resources are established.

[0593] The optional implementation of step S6101 can refer to the optional implementation of step S2114 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0594] FIG6B is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG6B , an embodiment of the present disclosure relates to a communication method. The communication method in this embodiment can be executed by terminal 101. The method includes step S6201.

[0595] In step S6201, the third information is obtained.

[0596] The optional implementation of step S6201 can refer to the optional implementation of step S2211 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0597] FIG7A is an exemplary interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG7A , the communication method according to an embodiment of the present disclosure includes step S7101.

[0598] In step S7101 , the second network element 1032 sends first information to the first network element 1031 .

[0599] The optional implementation of step S7101 can refer to the optional implementation of step S2204 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0600] FIG7B is an exemplary interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG7B , the communication method according to an embodiment of the present disclosure includes step S7201.

[0601] In step S7201 , the first network element 1031 sends first information to the third network element 1033 .

[0602] The optional implementation of step S7201 can refer to the optional implementation of step S2205 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0603] Figure 7C is an exemplary interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 7C, the communication method according to an embodiment of the present disclosure includes step S7301.

[0604] In step S7301 , the first network element 1031 sends third information to the terminal 101 .

[0605] The optional implementation of step S7301 can refer to the optional implementation of step S2211 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0606] Hereinafter, the technical solutions of the embodiments of the present disclosure are exemplarily described through specific implementation methods.

[0607] In some embodiments, the UPF identifies a subflow ID / range (i.e., a subflow ID / range identifier, such as a stream ID in QUIC, a track ID / track name in the MoQ protocol, a stream ID of an encrypted stream in the RoQ protocol, etc.), and reports the identified subflow ID / range or ranges to the SMF;

[0608] In some embodiments, the UPF, acting as a relay for end-to-end encrypted streams, can read metadata from data packets. Track IDs / track names in the MoQ protocol, and stream IDs for encrypted streams in the RoQ protocol, are included in the metadata of data packets. In addition to metadata from existing protocols, UDP options can be used to support carrying information such as substream IDs in metadata, such as stream IDs in QUIC.

[0609] In some embodiments, the UPF receives event subscription notifications (sub-flow ID / range) from the SMF, and when the UPF detects a new one or a group of (sub-flow ID / range), it reports it to the SMF.

[0610] In some embodiments, the SMF updates the received sub-flow ID / range to the corresponding packet filter set based on the received sub-flow ID / range report, and updates the corresponding QoS rule.

[0611] In some embodiments, the SMF adds the downstream sub-flow ID / range to the packet filter set, and sends the QoS rules carrying the corresponding packet filter set information to the UPF for the UPF to perform downstream data flow mapping.

[0612] In some embodiments, the SMF adds the uplink sub-flow ID / range to the packet filter set, and sends the QoS rules carrying the corresponding packet filter set information to the UE for performing uplink data flow mapping.

[0613] In some embodiments, the SMF reports the received sub-flow ID / range report to the PCF so that the PCF can generate new PCC rules or update existing corresponding PCC rules.

[0614] In some embodiments, the SMF subscribes to the sub-stream ID / range event notification (i.e., the sub-stream ID / range identifier, for example, the stream ID in QUIC, the track ID / track name in the MoQ protocol, the stream ID of the encrypted stream of the RoQ protocol, etc., these IDs can all be used to identify the sub-stream in the connection (the same quintuple)) to the UPF. The event subscription notification is used to obtain the sub-stream ID / range information identified by the UPF.

[0615] In some embodiments, the event notification may be effective when the SMF / PCF subscription is enabled, or the system default setting may always be effective (there is no need for active subscription, and the event is always valid during the session life cycle).

[0616] In some embodiments, the SMF controls data flow detection on the UPF by providing detection information for each PDR. For a PDU session of IPv4, IPv6, or IPv4v6 type, the detection information may include at least one of the following:

[0617] -CN channel information;

[0618] -CN channel information;

[0619] - Network instance;

[0620] -QFI;

[0621] -IP packet filter set;

[0622] - Application identifier (the application identifier is the index of the application detection rule set configured in the UPF);

[0623] -FQDN filter for DNS query messages;

[0624] - connection identifier;

[0625] - Stream ID / Track ID (Stream ID / Track ID can be specified as a stream / track range).

[0626] In some embodiments, the PCF receives the sub-flow ID / range reported by the SMF, generates a new PCC rule or updates the existing corresponding PCC rule, initiates a session modification process, and carries the updated QoS policy to the SMF.

[0627] In some embodiments, based on information provided by the AF / NEF and / or operator policy (e.g., local configuration or OAM configuration), the PCF subscribes to the SMF for subflow ID / range event notifications. If, based on information provided by the AF / NEF (the PCF receives a subscription request from the AF and initiates an availability change subscription), the PCF receives a subflow ID / range event notification report from the SMF, then it sends a subflow ID / range event notification to the AF.

[0628] In some embodiments, the UE receives a QoS rule issued by the SMF, where the packet filter set in the rule includes sub-flow ID / range information.

[0629] In some embodiments, the UE performs data stream mapping for uplink multiplexing data streams according to the packet filter set (for example, mapping one or more sub-streams with the same QoS requirements in the link to the same QoS stream, and mapping sub-streams with different QoS requirements in the connection to different QoS streams).

[0630] Figure 8A is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 8A , the communication method includes steps S8101 to S8105.

[0631] In some embodiments, if the policy control request trigger is satisfied, the SMF may initiate an SM policy association modification procedure to perform a sub-stream ID / range (i.e., sub-stream ID / range identification, for example, the stream ID in QUIC, the track ID / track name in the MoQ protocol, the stream ID of the encrypted stream of the RoQ protocol, etc.) event notification report.

[0632] In some embodiments, for local breakout roaming, interaction with the HPLMN is not used. In local breakout roaming, the V-PCF interacts with the UDR of the VPLMN.

[0633] In step S8101, when the policy control request trigger is satisfied, the SMF requests to update (Npcf_SMPolicyControl_Update) the SM policy association and provides information for the satisfied conditions.

[0634] In some embodiments, the SMF receives a sub-flow ID / range report sent by the UPF, updates the received sub-flow ID / range to the corresponding packet filter set, and updates the corresponding QoS rules; sends the received report information to the PCF, triggering the session management policy creation or modification process.

[0635] In some embodiments, the SMF adds the downstream sub-flow ID / range to the packet filter set, and sends the QoS rules carrying the corresponding packet filter set information to the UPF for the UPF to perform downstream data flow mapping.

[0636] In some embodiments, the SMF adds the uplink sub-flow ID / range to the packet filter set, and sends the QoS rules carrying the corresponding packet filter set information to the UE for performing uplink data flow mapping.

[0637] In some embodiments, the SMF reports the received sub-flow ID / range report to the PCF so that the PCF can generate new PCC rules or update existing corresponding PCC rules.

[0638] In some embodiments, the SMF subscribes to the sub-stream ID / range event notification (i.e., the sub-stream ID / range identifier, for example, the stream ID in QUIC, the track ID / track name in the MoQ protocol, the stream ID of the encrypted stream of the RoQ protocol, etc., these IDs can all be used to identify the sub-stream in the connection (the same quintuple)) to the UPF. The event subscription notification is used to obtain the sub-stream ID / range information identified by the UPF.

[0639] In some embodiments, the event notification may be effective when the SMF / PCF subscription is enabled, or the system default setting may always be effective (there is no need for active subscription, and the event is always valid during the session life cycle).

[0640] In step S8102, when the AF subscribes to the event and the report from the SMF meets the event, the PCF reports the event to the AF or TSCTSF by initiating the Npcf_PolicyAuthorization_Notify service operation.

[0641] In some embodiments, the PCF receives the sub-flow ID / range reported by the SMF, generates a new PCC rule or updates the existing corresponding PCC rule, initiates a session modification process, and carries the updated QoS policy to the SMF.

[0642] In some embodiments, if based on the information provided by AF / NEF (PCF receives the subscription request from AF and initiates availability change subscription), after PCF receives the sub-stream ID / range event notification report from SMF, it sends the sub-stream ID / range event notification to AF.

[0643] In step S8103, if the PCF determines that a change to the policy counter status reporting is required, the PCF may change the subscribed policy counter list through an initial, intermediate, or final Spending Limit Report Retrieval procedure.

[0644] In step S8104, the PCF may make a policy decision and determine that updated or new policy information needs to be sent to the SMF.

[0645] In some embodiments, the PCF receives the sub-flow ID / range reported by the SMF, generates a new PCC rule or updates the existing corresponding PCC rule, initiates a session modification process, and carries the updated QoS policy to the SMF.

[0646] In step S8105 , the PCF sends an Npcf_SMPolicyControl_Update response as a response, which carries update policy information related to the determined PDU session.

[0647] Figure 8B is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 8B , the communication method includes steps S8201 to S8218.

[0648] In step S8201, the AF sends an AF session resource request, for example, through the Nnef_AFsessionWithQoS_Create request. The AF includes the QoS requirements for the XRM service and interactive media service flows in the request message. The AF sends the multiplexed data flow identification / sub-flow QoS mapping indication to the 5GC (NEF / PCF) during the AF QoS request / update process.

[0649] In some embodiments, the QUCI protocol description, auxiliary information for encryption flow identification, composite flow mapping requirements (for example, media type classification, one-to-one mapping of QoS flows and sub-flows, mapping of a group of sub-flows to one QoS flow), XRM service information identifying the XRM flow or flow group (for example, multimodal service ID), UE address / UE identity, AF identity, application ID, flow description, DNN, S-NSSAI, QoS parameters, and other corresponding information can be carried. Here, the multimodal service ID can be used to identify all flows in the XRM service group.

[0650] In some embodiments, the AF may carry sub-stream ID / range information (i.e., sub-stream ID / range identifier, for example, the stream ID in QUIC, the track ID / track name in the MoQ protocol, the stream ID of the encrypted stream of the RoQ protocol, etc., which can all be used to identify the sub-streams in the connection (the same quintuple)) or PSI importance information. This information may be information obtained by the AF from the corresponding AS server when the AF session is established, or after the session is established. The AF carries the obtained sub-stream differentiation information or different importance information (i.e., the above-mentioned sub-stream ID / range information) in the stream description or packet filter set to the PCF for the PCF to obtain the packet filter set. The AF obtains and provides sub-stream differentiation information or different importance information from the AS, which can be implemented independently or in combination with the UPF detection information.

[0651] In step S8202, the NEF authorizes the AF request. If the AF is untrusted, the AF request is sent to the PCF through the NEF. (Optionally, the NEF performs relevant mappings, including mapping the XRM service (AF service identifier) ​​to the DNN and S-NSSAI, mapping the external application to the CN application identifier; and mapping the external UE identifier to the CN internal UE identifier (such as SUPI) based on the UDM subscription information, and performing external to internal XRM service group identifier mapping based on the UDM subscription information).

[0652] In step S8203, the NEF authorizes the AF request and, based on the parameters provided by the AF, determines whether to contact the TSCTSF or directly contact the PCF. (These signaling steps are identical to the AF session establishment process for QoS-required AFs in Section 4.15.6.6 of TS23.502.) The PCF receives the AF request from the NEF or TSCTSF and provided by the AF. The NEF triggers an Npcf_PolicyAuthorization_Create request to send the AF request to the PCF, carrying QoS requirement information for the PCF to make a policy decision. This message carries the multiplexed data flow indication / sub-flow QoS mapping indication, sub-flow ID, and range event of the response SDF.

[0653] In step S8204, the PCF makes a policy decision and may determine that updated or new policy information needs to be sent to the SMF.

[0654] In some embodiments, the PCF may determine the PCC rule taking into account the multiplexed data flow indication / sub-flow QoS mapping indication and sub-flow ID / range event. The PCF sends the multiplexed data flow indication / sub-flow QoS mapping indication and sub-flow ID / range event to the SMF to subscribe to the trigger report.

[0655] In step S8205, the PCF sends an Npcf_Policy Authorization_Create response to the NEF as a response.

[0656] In step S8206, the NEF sends a Nnef_AFsessionWithQoS_Create message to the AF, which carries a result to inform whether the request is authorized.

[0657] In step S8207, the PCF initiates an SM Policy Association Modification request (sub-flow ID / scope event) to the SMF.

[0658] In some embodiments, the PCF receives the sub-flow ID / range reported by the SMF, generates a new PCC rule or updates the existing corresponding PCC rule, initiates a session modification process, and carries the updated QoS policy to the SMF.

[0659] In some embodiments, based on information provided by the AF / NEF and / or operator policy (e.g., local configuration or OAM configuration), the PCF subscribes to the SMF for sub-flow ID / range event notifications. If, based on information provided by the AF / NEF (the PCF receives a subscription request from the AF and initiates an availability change subscription), the PCF receives a sub-flow ID / range event notification report from the SMF and sends the sub-flow ID / range event notification to the AF.

[0660] In step S8208, the SMF sends an SM Policy Association Modification response to the PCF.

[0661] In step S8209, SMF initiates an N4 Session Modification request (PDU set processing availability / support change) to UPF.

[0662] In some embodiments, the SMF updates the received sub-flow ID / range to the corresponding packet filter set based on the received sub-flow ID / range report, and updates the corresponding QoS rule.

[0663] In some embodiments, the SMF adds the downstream sub-flow ID / range to the packet filter set, and sends the QoS rules carrying the corresponding packet filter set information to the UPF for the UPF to perform downstream data flow mapping.

[0664] In some embodiments, the SMF adds the uplink sub-flow ID / range to the packet filter set, and sends the QoS rules carrying the corresponding packet filter set information to the UE for performing uplink data flow mapping.

[0665] In some embodiments, the SMF reports the received sub-flow ID / range report to the PCF so that the PCF can generate new PCC rules or update existing corresponding PCC rules.

[0666] In some embodiments, the SMF subscribes to the UPF for substream ID / range event notifications (i.e., substream ID / range identification, such as the stream ID in QUIC, the track ID / track name in the MoQ protocol, the stream ID of the encrypted stream of the RoQ protocol, etc., which can be used to identify the substreams in the connection (the same quintuple)) or subscribes to PSI information notifications. This type of event subscription notification is used to obtain the substream ID / range information identified by the UPF, or classification information of PDU sets of different importance.

[0667] In some embodiments, the event notification may be effective when the SMF / PCF subscription is enabled, or the system default setting may always be effective (there is no need for active subscription, and the event is always valid during the session life cycle).

[0668] In some embodiments, the SMF controls data flow detection on the UPF by providing detection information for each PDR. For a PDU session of IPv4, IPv6, or IPv4v6 type, the detection information may include at least one of the following:

[0669] -CN channel information;

[0670] -CN channel information;

[0671] - Network instance;

[0672] -QFI;

[0673] -IP packet filter set;

[0674] - Application identifier (the application identifier is the index of the application detection rule set configured in the UPF);

[0675] -FQDN filter for DNS query messages;

[0676] - connection identifier;

[0677] - stream identifier / track identifier (stream identifier / track identifier can be specified as a stream / track range);

[0678] -PSI information.

[0679] In step S8210, the UPF responds to the SMF.

[0680] In some embodiments, the UPF receives event subscription notifications (sub-flow ID / range) from the SMF, and when the UPF detects a new one or a group of (sub-flow ID / range), it reports it to the SMF.

[0681] In some embodiments, the SMF updates the received sub-flow ID / range to the corresponding packet filter set based on the received sub-flow ID / range report, and updates the corresponding QoS rule.

[0682] In some embodiments, the SMF adds the downstream sub-flow ID / range to the packet filter set, and sends the QoS rules carrying the corresponding packet filter set information to the UPF for the UPF to perform downstream data flow mapping.

[0683] In some embodiments, the SMF adds the uplink sub-flow ID / range to the packet filter set, and sends the QoS rules carrying the corresponding packet filter set information to the UE for performing uplink data flow mapping.

[0684] In some embodiments, the SMF reports the received sub-flow ID / range report to the PCF so that the PCF can generate new PCC rules or update existing corresponding PCC rules.

[0685] In some embodiments, the SMF subscribes to the sub-stream ID / range event notification (i.e., the sub-stream ID / range identifier, for example, the stream ID in QUIC, the track ID / track name in the MoQ protocol, the stream ID of the encrypted stream of the RoQ protocol, etc., these IDs can all be used to identify the sub-stream in the connection (the same quintuple)) to the UPF. The event subscription notification is used to obtain the sub-stream ID / range information identified by the UPF.

[0686] In some embodiments, the SMF updates the received PSI ID / PSI range to the corresponding packet filter set based on the received PSI ID / PSI range report, and updates the corresponding QoS rules.

[0687] In some embodiments, the SMF adds the downstream PSI ID / PSI range to the packet filter set and sends the QoS rules carrying the corresponding packet filter set information to the UPF for the UPF to perform downstream data flow mapping. For example, a downstream multiplexed data stream includes multiple audio substreams and multiple video substreams. The packet filter with enhanced PSI range corresponding to the multiple downstream audio substreams is used to map multiple downstream audio substreams with the same QoS requirements to the same QoS flow. The packet filter with enhanced PSI range corresponding to one or two downstream video substreams is used to map one or two downstream video substreams with the same QoS requirements to another QoS flow.

[0688] In some embodiments, the SMF adds the uplink PSI ID / PSI range to the packet filter set, and sends the QoS rules carrying the corresponding packet filter set information to the UE for performing uplink data flow mapping.

[0689] In some embodiments, the event notification may be effective when the SMF / PCF subscription is enabled, or the system default setting may always be effective (there is no need for active subscription, and the event is always valid during the session life cycle).

[0690] In step S8211, for the modification requested by the SMF, the SMF causes Namf_Communication_N1N2MessageTransfer (N2 SM information (PDU session ID, QFI, QoS configuration, N1 SM container)).

[0691] In step S8212, AMF (i.e., the fifth core network device) can send an N2 message (N2 SM information received from SMF, NAS message (PDU session ID, N1 SM container (PDU session modification command))) to RAN (i.e., access network device).

[0692] In step S8214, the RAN may acknowledge the N2 PDU session request by sending an N2 PDU Session Ack message to the AMF.

[0693] In step S8215, AMF forwards the N2 SM information from the access network to SMF through the Nsmf_PDUSession_UpdateSMContext service operation.

[0694] In step S8216, the SMF replies with an Nsmf_PDUSession_UpdateSMContext response.

[0695] In steps S8217 and S8218, the SMF can update the N4 session of the UPF involved in the PDU session modification by sending an N4 Session Modification request to the UPF.

[0696] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0697] The present disclosure also provides a communication device for implementing any of the above methods. For example, the present disclosure provides a communication device including units or modules for implementing each step performed by a network device in any of the above methods. For example, the present disclosure provides a communication device including units or modules for implementing each step performed by a terminal in any of the above methods.

[0698] It should be understood that the division of the various units or modules in the above devices is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above devices, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0699] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit, a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by a dedicated integrated circuit or a programmable logic device, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0700] FIG9 is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. As shown in FIG9 , the communication device 900 may include at least one of the following: a transceiver module 901 and a processing module 902 .

[0701] In a first aspect, the communication device 900 may be a first network element 1031. In some embodiments, the transceiver module 901 may be configured to receive first information sent by a second network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream. Optionally, the transceiver module 901 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the first network element 1031 in any of the above methods (for example, steps S2107, S2108, S2109, S2111, S2112, S2116, S2117, S2202, S2206, S2207, S2210, S2212, and S2213), which are not further described here. Optionally, the processing module 902 can be configured to perform at least one of the other steps (for example, step S2211) other than the communication steps such as sending and / or receiving performed by the first network element 1031 in any of the above methods, which are not repeated here.

[0702] In the second aspect, the communication device 900 may be a second network element 1032. In some embodiments, the transceiver module 901 may be configured to send first information to the first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; wherein the first information includes identification information, and the identification information is used to identify at least one substream. Optionally, the transceiver module 901 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the second network element 1032 in any of the above methods (for example, steps S2109, S2111, S2117, S2201, S2202, S2204, S2210), which are not described in detail here. Optionally, the processing module 902 may be configured to perform at least one of the other steps (for example, steps S2110, S2203) other than the communication steps such as sending and / or receiving performed by the second network element 1032 in any of the above methods, which are not described in detail here.

[0703] In a third aspect, the communication device 900 may be a third network element 1033. In some embodiments, the transceiver module 901 may be configured to receive first information sent by the first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream, and the first information includes identification information, and the identification information is used to identify at least one substream. The processing module 902 may be configured to determine a third rule based on the first information. Optionally, the transceiver module 901 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the third network element 1033 in any of the above methods (for example, steps S2103, S2105, S2107, S2108, S2201, S2202, S2207, S2208, S2210), which will not be repeated here. Optionally, the processing module 902 can be configured to perform at least one of the other steps (for example, steps S2106, S2209) other than the communication steps such as sending and / or receiving performed by the third network element 1033 in any of the above methods, which are not repeated here.

[0704] In a fourth aspect, the communication device 900 may be a terminal 101. In some embodiments, the transceiver module 901 may be configured to receive third information sent by the first network element, where the third information is used to indicate a second rule, and the second rule is determined based on identification information, and the identification information is obtained from at least one subflow and is used to identify the at least one subflow. Optionally, the transceiver module 901 may be configured to perform at least one of the communication steps (e.g., steps S2114 and S2213) such as sending and / or receiving performed by the terminal 101 in any of the above methods, which are not further described here.

[0705] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0706] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0707] Figure 10A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. Communication device 10100 can be a network device (e.g., an access network device, a core network device, etc.), or a terminal (e.g., a user device, etc.), or a chip, chip system, or processor that supports a network device to implement any of the above methods, or a chip, chip system, or processor that supports a terminal to implement any of the above methods. Communication device 10100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0708] As shown in Figure 10A, the communication device 10100 includes one or more processors 10101. The processor 10101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 10100 is used to perform any of the above methods. Optionally, one or more processors 10101 are used to call instructions to enable the communication device 10100 to perform any of the above methods.

[0709] In some embodiments, the communication device 10100 further includes one or more transceivers 10102. When the communication device 10100 includes one or more transceivers 10102, the transceiver 10102 performs the communication steps such as sending and / or receiving in the above method (for example, steps S2101, S2103, S2105, S2106, S2107, S2108, S2109, S2111, S2112, S2113, S2114, S2115, S2116, S2117). 7, S2201, S2202, S2203, S2204, S2206, S2207, S2208, S2210, S2212, S2213, but not limited thereto), the processor 10101 executes at least one of the other steps (for example, steps S2102, S2104, S2110, S2205, S2209, S2211, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated together. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc. may be interchangeable, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. may be interchangeable, and the terms receiver, receiving unit, receiver, receiving circuit, etc. may be interchangeable.

[0710] In some embodiments, the communication device 10100 further includes one or more memories 10103 for storing data. Alternatively, all or part of the memories 10103 may be located outside the communication device 10100. In alternative embodiments, the communication device 10100 may include one or more interface circuits 10104. Optionally, the interface circuits 10104 are connected to the memories 10103 and may be configured to receive data from the memories 10103 or other devices, or to send data to the memories 10103 or other devices. For example, the interface circuits 10104 may read data stored in the memories 10103 and send the data to the processor 10101.

[0711] The communication device 10100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 10100 described in the present disclosure is not limited thereto, and the structure of the communication device 10100 may not be limited by FIG. 10A . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0712] FIG10B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. If the communication device 10100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 10200 shown in FIG10B , but the present invention is not limited thereto.

[0713] The chip 10200 includes one or more processors 10201. The chip 10200 is configured to execute any of the above methods.

[0714] In some embodiments, chip 10200 further includes one or more interface circuits 10202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 10200 further includes one or more memories 10203 for storing data. Alternatively, all or part of memory 10203 may be located external to chip 10200. Optionally, interface circuit 10202 is connected to memory 10203 and may be configured to receive data from memory 10203 or other devices, or to send data to memory 10203 or other devices. For example, interface circuit 10202 may read data stored in memory 10203 and send the data to processor 10201.

[0715] In some embodiments, the interface circuit 10202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2103, S2105, S2106, S2107, S2108, S2109, S2111, S2112, S2113, S2114, S2115, S2116, S2117, S2201, S2202, S2203, S2204, S2206, S2207, S2208, S2210, S2212, and S2213, but not limited thereto). The interface circuit 10202 performing the communication steps such as sending and / or receiving in the above method, for example, means that the interface circuit 10202 performs data exchange between the processor 10201, the chip 10200, the memory 10203, or the transceiver device. In some embodiments, the processor 10201 executes at least one of the other steps (for example, steps S2102 , S2104 , S2110 , S2205 , S2209 , S2211 , but not limited thereto).

[0716] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0717] The embodiments of the present disclosure further provide a storage medium having instructions stored thereon. When the instructions are executed on the communication device 10100, the communication device 10100 is caused to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0718] The embodiments of the present disclosure further provide a program product, which, when executed by the communication device 10100, enables the communication device 10100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0719] The embodiments of the present disclosure further provide a computer program, which, when executed on a computer, enables the computer to execute any of the above methods.

[0720] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0721] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A communication method, performed by a first network element, wherein: The method comprises: receiving first information sent by a second network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; The first information includes identification information, and the identification information is used to identify at least one sub-stream.

2. The method according to claim 1, wherein The identification information includes at least one of the following: Sub-flow identification information, used to identify the at least one sub-flow; The packet data unit (PDU) set importance information is used to indicate the importance of the PDU set in the at least one sub-flow.

3. The method according to claim 1 or 2, wherein: The identification information is obtained from the at least one sub-stream.

4. The method according to any one of claims 1 to 3, wherein The method further comprises: receiving ninth information sent by the third network element, wherein the ninth information is used to determine a mapping rule for the multiplexed data stream; The ninth information includes identification information, and the identification information is used to identify at least one sub-stream.

5. The method according to any one of claims 1 to 4, wherein The method further comprises: The mapping rule is determined according to the first information and / or the ninth information.

6. The method according to claim 5, wherein: The determining the mapping rule according to the first information includes: adding identification information in the first information and / or the ninth information to a packet filter set; Based on the packet filter set, the mapping rule is determined.

7. The method according to claim 5 or 6, wherein: The mapping rule includes a first rule, wherein the first rule is used for quality of service (QoS) processing of a downlink; The method further comprises: Sending second information to the second network element, where the second information is used to indicate the first rule.

8. The method according to any one of claims 5 to 7, wherein The mapping rule includes a second rule, wherein the second rule is used for QoS processing of the uplink; The method further comprises: Sending third information to the terminal, where the third information is used to indicate the second rule.

9. The method according to any one of claims 1 to 8, wherein The method further comprises: sending the first information to a third network element; Receive fourth information sent by the third network element, wherein the fourth information is used to indicate a third rule, and the third rule is determined according to the first information.

10. The method according to any one of claims 1 to 9, wherein The method further comprises: receiving fifth information from a third network element, wherein the fifth information is used to instruct acquisition of the identification information; Send the fifth information to the second network element.

11. A communication method, performed by a second network element, wherein: The method comprises: Sending first information to the first network element, wherein the first information is used to determine a mapping rule for the multiplexed data stream; The first information includes identification information, and the identification information is used to identify at least one sub-stream.

12. The method according to claim 11, wherein The identification information includes at least one of the following: Sub-flow identification information, used to identify the at least one sub-flow; The packet data unit (PDU) set importance information is used to indicate the importance of the PDU set in the at least one sub-flow.

13. The method according to claim 11 or 12, wherein: The method further comprises: receiving the at least one substream; The identification information is determined based on the at least one sub-flow.

14. The method according to any one of claims 11 to 13, wherein The method further comprises: Second information is received from the first network element, wherein the second information is used to indicate a first rule, and the first rule is used for downlink quality of service (QoS) processing.

15. The method according to any one of claims 11 to 14, wherein The method further comprises: Receive fifth information sent by the first network element, wherein the fifth information is used to instruct to obtain the identification information.

16. A communication method, performed by a third network element, wherein: The method comprises: Receiving first information sent by a first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream, and the first information includes identification information, and the identification information is used to identify at least one sub-stream; A third rule is determined according to the first information.

17. The method according to claim 16, wherein The identification information includes at least one of the following: Sub-flow identification information, used to identify the at least one sub-flow; The packet data unit (PDU) set importance information is used to indicate the importance of the PDU set in the at least one sub-flow.

18. The method according to claim 16 or 17, wherein The identification information is obtained from the at least one sub-stream.

19. The method according to any one of claims 16 to 18, wherein The method further comprises: Sending ninth information to the first network element, wherein the ninth information is used to determine a mapping rule for the multiplexed data stream; The ninth information includes identification information, and the identification information is used to identify at least one sub-stream.

20. The method according to claim 19, wherein The method further comprises: Receive the ninth information sent by the fifth network element.

21. The method according to any one of claims 16 to 20, wherein The method further comprises: Sending fourth information to the first network element, where the fourth information is used to indicate a third rule.

22. The method according to any one of claims 16 to 21, wherein The method further comprises: Send the first information to the fifth network element.

23. A communication method, executed by a terminal, wherein: The method comprises: Receive third information sent by the first network element, wherein the third information is used to indicate a second rule, the second rule is determined according to identification information, and the identification information is obtained from at least one sub-flow and is used to identify the at least one sub-flow.

24. The method according to claim 23, wherein The identification information includes at least one of the following: Sub-flow identification information, used to identify at least one sub-flow; The packet data unit (PDU) set importance information is used to indicate the importance of the PDU set in the at least one sub-flow.

25. A communication method, performed by a core network, wherein: The core network includes a first network element and a second network element; The method comprises: The second network element sends first information to the first network element, wherein the first information is used to determine a mapping rule for the multiplexed data stream; The first information includes identification information, and the identification information is used to identify at least one sub-stream.

26. The communication method according to claim 25, wherein: The core network also includes a third network element; The method further comprises: The first network element sends the first information to the third network element; The third network element determines a third rule according to the first information.

27. A first network element, comprising: a transceiver module configured to receive first information sent by a second network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream; The first information includes identification information, and the identification information is used to identify at least one sub-stream.

28. A second network element, comprising: a transceiver module configured to send first information to the first network element, wherein the first information is used to determine a mapping rule for the multiplexed data stream; The first information includes identification information, and the identification information is used to identify at least one sub-stream.

29. A third network element, comprising: Transceiver module, configured as: Receiving first information sent by a first network element, wherein the first information is used to determine a mapping rule for a multiplexed data stream, and the first information includes identification information, and the identification information is used to identify at least one sub-stream; A third rule is determined according to the first information.

30. A terminal comprising: The transceiver module is configured to receive third information sent by the first network element, wherein the third information is used to indicate a second rule, the second rule is determined based on identification information, and the identification information is obtained from at least one sub-stream and is used to identify the at least one sub-stream.

31. A communication device comprising: one or more processors; a memory storing instructions; When the instruction is executed by the communication device, the communication device implements the method according to any one of claims 1 to 10.

32. A communication device comprising: one or more processors; a memory storing instructions; When the instruction is executed by the communication device, the communication device implements the method according to any one of claims 11 to 15.

33. A communication device comprising: one or more processors; a memory storing instructions; When the instruction is executed by the communication device, the communication device implements the method according to any one of claims 16 to 22.

34. A communication device comprising: one or more processors; a memory storing instructions; When the instruction is executed by the communication device, the communication device implements the method according to claim 23 or 24.

35. A communication system comprising a first network element and a second network element; in, The first network element is used to implement the method according to any one of claims 1 to 10; The second network element is used to implement the method according to any one of claims 11 to 15.

36. A storage medium storing instructions, wherein: When the instructions are executed on a communication device, the communication device is caused to implement at least one of the following: The method according to any one of claims 1 to 10; The method according to any one of claims 11 to 15; The method according to any one of claims 16 to 22; The method of claim 23 or 24.

37. A computer program product comprising instructions, wherein when the instructions are executed on a communication device, the communication device is caused to implement at least one of the following: The method according to any one of claims 1 to 10; The method according to any one of claims 11 to 15; The method according to any one of claims 16 to 22; The method according to claim 23 or 24.

Images