Communication methods and apparatuses, and core network device, communication system and storage medium

Abstract

The present disclosure relates to communication methods and apparatuses, and a core network device, a communication system and a storage medium. A method comprises: determining first information, wherein the first information is used for requesting that a first rule is determined, and the first rule is used for traffic mapping of a multiplexed data flow of a first service. By means of the solution of the present disclosure, the support for different QoS characteristics of a multiplexed data flow is realized.

Description

Communication method, device, core network equipment, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication method, apparatus, core network equipment, communication system, and storage medium. Background Art

[0002] In the fifth generation mobile network (5 th With communication technologies such as fifth-generation mobile networks (5G), mobile media services, online extended reality (XR), online games, and video-based remote control of machines or drones are expected to contribute more and more traffic to communication networks.

[0003] Currently, due to the high throughput, low latency, and high reliability requirements of XRM and eXtended Reality and interactive media services, it is necessary to comprehensively consider the quality of service (QoS) characteristics of different service data flows (SDFs) in a service.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide a communication method, apparatus, core network device, communication system, and storage medium to provide support for different QoS characteristics of multiplexed data streams.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to a first core network device. The communication method includes: determining first information, wherein the first information is used to request determination of a first rule, the first rule being used for traffic mapping of a multiplexed data flow of a first service.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to a second core network device. The communication method includes: sending first information to a first core network device, wherein the first information is used to request determination of a first rule, the first rule being used for traffic mapping of a multiplexed data flow of a first service.

[0008] According to a third aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to a third core network device. The communication method includes receiving second information sent by the third core network device, where the second information includes at least one of the following: a first rule for traffic mapping of a multiplexed data stream of a first service; indication information for indicating whether to adopt the multiplexed data stream; and requirement information for indicating a mapping requirement for the multiplexed data stream.

[0009] According to a fourth aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to a fourth core network device. The communication method includes: determining, based on a second rule, a mapping of a multiplexed data flow of a first service to a QoS flow, wherein the second rule is used for traffic mapping of the multiplexed data flow.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to a core network. The core network includes a first core network device and a third core network device. The communication method includes: the first core network device sends second information to the third core network device, where the second information includes at least one of the following: a first rule for traffic mapping of a multiplexed data stream of a first service; indication information for indicating whether to adopt the multiplexed data stream; and requirement information for indicating a mapping requirement for the multiplexed data stream.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a first core network device is provided. The first core network device includes: a transceiver module configured to obtain first information, wherein the first information is used to request determination of a first rule, the first rule being used for traffic mapping of a multiplexed data flow of a first service.

[0012] According to a seventh aspect of an embodiment of the present disclosure, a second core network device is provided. The second core network device includes: a transceiver module configured to send first information, wherein the first information is used to request determination of a first rule, the first rule being used for traffic mapping of a multiplexed data flow of a first service.

[0013] According to an eighth aspect of an embodiment of the present disclosure, a third core network device is provided. The third core network device includes: a transceiver module configured to receive second information, where the second information includes at least one of the following: a first rule for traffic mapping of a multiplexed data stream of a first service; indication information for indicating whether to adopt the multiplexed data stream; and requirement information for indicating a mapping requirement for the multiplexed data stream.

[0014] According to a ninth aspect of an embodiment of the present disclosure, a fourth core network device is provided. The fourth core network device includes: a processing module configured to determine a mapping of a multiplexed data flow of a first service to a quality of service (QoS) flow according to a second rule, wherein the second rule is used for traffic mapping of the multiplexed data flow.

[0015] 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.

[0016] 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.

[0017] According to a twelfth 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 third aspect.

[0018] 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.

[0019] According to a fourteenth 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 fifth aspect.

[0020] According to a fifteenth aspect of an embodiment of the present disclosure, a communication system is provided. The communication system includes a first core network device and a second core network device. The first core network device is configured to implement the communication method described in the first aspect. The second core network device is configured to implement the communication method described in the second aspect.

[0021] According to a sixteenth aspect of an embodiment 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 as described in any one of the first to fifth aspects.

[0022] According to a seventeenth aspect of the embodiments of the present disclosure, a program product is provided. 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 to fifth aspects.

[0023] According to an eighteenth 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 any one of the first to fifth aspects.

[0024] According to a nineteenth aspect of an embodiment of the present disclosure, a chip or a chip system is provided. The chip or chip system includes a processing circuit. The processing circuit is configured to execute the communication method as described in any one of the first to fifth aspects.

[0025] Through the embodiments of the present disclosure, each data stream in the multiplexed data stream can be mapped to a corresponding QoS stream.

[0026] 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

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

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

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

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

[0031] FIG2 is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.

[0032] FIG3 is a flow chart of a communication method according to an embodiment of the present disclosure.

[0033] FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure.

[0034] FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure.

[0035] FIG6 is a flow chart of a communication method according to an embodiment of the present disclosure.

[0036] FIG7 is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.

[0037] FIG8A is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.

[0038] FIG8B is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.

[0039] FIG8C is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.

[0040] FIG8D is a flow chart of a communication method according to an embodiment of the present disclosure.

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

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

[0043] FIG11A is a schematic structural diagram of a communication device according to an embodiment of the present disclosure.

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

[0045] Embodiments of the present disclosure provide a communication method, apparatus, core network equipment, a communication system, and a storage medium.

[0046] In a first aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a first core network device. The communication method includes determining first information, wherein the first information is used to request determination of a first rule, the first rule being used for traffic mapping of a multiplexed data flow of a first service.

[0047] In the above embodiment, the first core network device can determine first information, and the first information is used to request determination of a first rule. The first information can cause the first core network device to determine the first rule. The first rule is used for traffic mapping of the multiplexed data flow of the first service. In this way, the multiplexed data flow of the first service can be mapped to QoS traffic, thereby supporting different QoS characteristics of the multiplexed data flow.

[0048] In combination with some embodiments of the first aspect, in some embodiments, the operation of determining the first information may include at least one of the following methods: receiving the first information sent by the second core network device; receiving the first information sent by the seventh core network device; determining the first information based on the operator's operation and maintenance and management configuration; determining the first information according to the local configuration.

[0049] In the above embodiment, the first information can be received from the second core network device or the seventh core network device, or can be determined based on the operator's operation and maintenance and management configuration, or can be determined based on local configuration. In this way, the first information can be obtained in various ways when needed, significantly improving the flexibility of configuring traffic mapping of multiplexed data streams and expanding applicable scenarios.

[0050] In combination with some embodiments of the first aspect, in some embodiments, the first information may include at least one of the following: indication information for indicating whether to adopt the multiplexed data stream; and requirement information for indicating the mapping requirement of the multiplexed data stream.

[0051] In the above embodiment, the indication information can indicate whether to adopt the multiplexed data stream. In addition, the requirement information can indicate the requirement for traffic mapping of the multiplexed data stream. In this way, the traffic mapping applied to the first rule determined based on the first information can meet the requirement.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the requirement information may include at least one of the following: mapping type; mapping description; mapping priority.

[0053] In the above embodiment, by including one or more information of mapping type, mapping description, and mapping priority in the requirement information, the indication information can clearly indicate the requirements that need to be met for traffic mapping of the multiplexed data stream, thereby enabling the corresponding traffic mapping rules to be determined.

[0054] In combination with some embodiments of the first aspect, in some embodiments, the mapping type may include at least one of the following: one-to-one mapping; one-to-many mapping; many-to-one mapping; many-to-many mapping.

[0055] In the above embodiment, the mapping type may indicate one-to-one mapping, one-to-many mapping, many-to-one mapping, many-to-many mapping, etc. In this way, different mapping types may be used for different services and / or multiplexed data streams, thereby configuring an appropriate first rule.

[0056] In combination with some embodiments of the first aspect, in some embodiments, the mapping description may include at least one of the following: media type; stream dependency; channel dependency; layer dependency; synchronization dependency.

[0057] In the above embodiment, the mapping description can be used to represent different characteristics such as media type, stream dependency, channel dependency, layer dependency, synchronization dependency, etc. Thus, traffic mapping of the multiplexed data stream of the first service can be implemented by taking these different characteristics into consideration.

[0058] In combination with some embodiments of the first aspect, in some embodiments, the mapping priority may include at least one of the following: mapping requirement priority; mapping type priority; mapping description priority.

[0059] In the above embodiment, when performing traffic mapping for multiplexed data streams, the priority of the mapping rules employed can be determined based on at least one of the following: mapping requirement priority, mapping type priority, and mapping description priority. Thus, different types of mapping priorities can be employed for different scenarios. For example, for services with high synchronization requirements, mapping description priority can be prioritized. For another example, for services with high bandwidth requirements, mapping description priority can be prioritized.

[0060] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: sending second information to a third core network device, wherein the information includes one of the following: a first rule; indication information for indicating whether to adopt multiplexed data streams; and requirement information for indicating mapping requirements for multiplexed data streams.

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

[0062] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: sending the first information to the seventh core network device.

[0063] In a second aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a second core network device. The communication method includes: sending first information to a first core network device, wherein the first information is used to request determination of a first rule for traffic mapping of a multiplexed data flow of a first service.

[0064] In the above embodiment, the second core network device may send first information, and the first information is used to request determination of a first rule. The core network device that receives the first information may determine the first rule. The first rule is used for traffic mapping of the multiplexed data flow of the first service. In this way, the multiplexed data flow of the first service can be mapped to QoS traffic, thereby supporting different QoS characteristics of the multiplexed data flow.

[0065] In combination with some embodiments of the second aspect, in some embodiments, the first information may include at least one of the following: indication information, used to indicate whether to adopt multiplexed data stream; requirement information, used to indicate mapping requirements of the multiplexed data stream.

[0066] In combination with some embodiments of the second aspect, in some embodiments, the requirement information may include at least one of the following: mapping type; mapping description; mapping priority.

[0067] In combination with some embodiments of the second aspect, in some embodiments, the mapping type may include at least one of the following: one-to-one mapping; one-to-many mapping; many-to-one mapping; many-to-many mapping.

[0068] In combination with some embodiments of the second aspect, in some embodiments, the mapping description may include at least one of the following: media type; stream dependency; channel dependency; layer dependency; synchronization dependency.

[0069] In combination with some embodiments of the second aspect, in some embodiments, the mapping priority may include at least one of the following: mapping requirement priority; mapping type priority; mapping description priority.

[0070] In a third aspect, embodiments of the present disclosure provide a communication method. This communication method is applied to a third core network device. The communication method includes receiving second information sent by a first core network device, where the second information includes one of the following: a first rule for traffic mapping of a multiplexed data stream of a first service; indication information for indicating whether to adopt the multiplexed data stream; and requirement information for indicating a mapping requirement for the multiplexed data stream.

[0071] In the above embodiment, the third core network device can receive the second information. Using the second information, the third core network device can obtain the first rule or information related to the first rule. In this way, the third core network device can map the multiplexed data flow of the first service to QoS traffic, thereby supporting different QoS characteristics of the multiplexed data flow.

[0072] In combination with some embodiments of the third aspect, in some embodiments, the requirement information may include at least one of the following: mapping type; mapping description; mapping priority.

[0073] In combination with some embodiments of the third aspect, in some embodiments, the mapping type may include at least one of the following: one-to-one mapping; one-to-many mapping; many-to-one mapping; many-to-many mapping.

[0074] In combination with some embodiments of the third aspect, in some embodiments, the mapping description may include at least one of the following: media type; stream dependency; channel dependency; layer dependency; synchronization dependency.

[0075] In combination with some embodiments of the third aspect, in some embodiments, the mapping priority may include at least one of the following: mapping requirement priority; mapping type priority; mapping description priority.

[0076] In combination with some embodiments of the third aspect, in some embodiments, the first rule may be determined based on indication information and / or requirement information.

[0077] In combination with some embodiments of the third aspect, in some embodiments, the above method may further include: sending third information to a fourth core network device, wherein the third information includes a second rule, and the second rule is used for traffic mapping of the multiplexed data stream of the first service.

[0078] In combination with some embodiments of the third aspect, in some embodiments, the second rule can be determined in one of the following ways: determined according to the rule; determined according to the indication information and / or the requirement information.

[0079] In the above embodiment, the third core network device can receive the second information. Using the second information, the third core network device can obtain the first rule or information related to the first rule. The third core network device can then determine the second rule based on the first rule, or based on at least one of the indication information and the requirement information. In this way, the third core network device can map the multiplexed data flow of the first service to QoS traffic, thereby supporting different QoS characteristics of the multiplexed data flow.

[0080] In a fourth aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a fourth core network device. The communication method includes determining, based on a second rule, a mapping of a multiplexed data flow of a first service to a QoS flow, wherein the second rule is used for traffic mapping of the multiplexed data flow.

[0081] In the above embodiment, the fourth core network device can implement the mapping of the multiplexed data flow of the first service to the QoS flow based on the second rule. According to the second rule, the fourth core network device can map each data flow in the multiplexed data flow to the corresponding QoS flow, thereby supporting different QoS characteristics of the multiplexed data flow.

[0082] In combination with some embodiments of the fourth aspect, in some embodiments, the above method may also include: receiving third information sent by a third core network device, wherein the third information includes a second rule, and the second rule is used for traffic mapping of the multiplexed data stream of the first service.

[0083] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second rule may be locally configured.

[0084] In a fifth aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a core network. The core network includes a first core network device and a third core network device. The communication method includes: the first core network device sending second information to the third core network device, where the second information includes at least one of the following: a first rule for traffic mapping of a multiplexed data stream of a first service; indication information for indicating whether to adopt the multiplexed data stream; and requirement information for indicating a mapping requirement for the multiplexed data stream.

[0085] In a sixth aspect, an embodiment of the present disclosure provides a first core network device, comprising: a transceiver module configured to determine first information, wherein the first information is used to request determination of a first rule, the first rule being used for traffic mapping of a multiplexed data flow of a first service.

[0086] In combination with some embodiments of the sixth aspect, in some embodiments, the first information can be obtained through at least one of the following methods: receiving the first information sent by the second core network device; receiving the first information sent by the seventh core network device; determining the first information based on the operator's operation and maintenance and management configuration; determining the first information based on local configuration.

[0087] In combination with some embodiments of the sixth aspect, in some embodiments, the first information may include at least one of the following: indication information, used to indicate whether to adopt multiplexed data stream; requirement information, used to indicate the mapping requirements of the multiplexed data stream.

[0088] In combination with some embodiments of the sixth aspect, in some embodiments, the requirement information may include at least one of the following: mapping type; mapping description; mapping priority.

[0089] In combination with some embodiments of the sixth aspect, in some embodiments, the mapping type may include at least one of the following: one-to-one mapping; one-to-many mapping; many-to-one mapping; many-to-many mapping.

[0090] In combination with some embodiments of the sixth aspect, in some embodiments, the mapping description may include at least one of the following: media type; stream dependency; channel dependency; layer dependency; synchronization dependency.

[0091] In combination with some embodiments of the sixth aspect, in some embodiments, the mapping priority may include at least one of the following: mapping requirement priority; mapping type priority; mapping description priority.

[0092] In combination with some embodiments of the sixth aspect, in some embodiments, the transceiver module can also be configured to: send second information to the third core network device, wherein the information includes one of the following: a first rule; indication information for indicating whether to adopt multiplexed data stream; requirement information for indicating the mapping requirements of the multiplexed data stream.

[0093] In combination with some embodiments of the sixth aspect, in some embodiments, the first core network device may further include: a processing module configured to determine the first rule based on indication information and / or requirement information.

[0094] In combination with some embodiments of the sixth aspect, in some embodiments, the transceiver module can also be configured to: send first information to the seventh core network device.

[0095] In a seventh aspect, embodiments of the present disclosure provide a second core network device. The second core network device includes: a transceiver module configured to send first information to the first core network device, wherein the first information is used to request determination of a first rule, the first rule being used for traffic mapping of a multiplexed data flow of a first service.

[0096] In combination with some embodiments of the seventh aspect, in some embodiments, the first information may include at least one of the following: indication information, used to indicate whether to adopt multiplexed data stream; requirement information, used to indicate the mapping requirement of the multiplexed data stream.

[0097] In combination with some embodiments of the seventh aspect, in some embodiments, the requirement information may include at least one of the following: mapping type; mapping description; mapping priority.

[0098] In combination with some embodiments of the seventh aspect, in some embodiments, the mapping type may include at least one of the following: one-to-one mapping; one-to-many mapping; many-to-one mapping; many-to-many mapping.

[0099] In combination with some embodiments of the seventh aspect, in some embodiments, the mapping description may include at least one of the following: media type; stream dependency; channel dependency; layer dependency; synchronization dependency.

[0100] In combination with some embodiments of the seventh aspect, in some embodiments, the mapping priority may include at least one of the following: mapping requirement priority; mapping type priority; mapping description priority.

[0101] In an eighth aspect, embodiments of the present disclosure provide a third core network device. The third core network device includes: a transceiver module configured to receive second information sent by a first core network device, where the second information includes one of the following: a first rule for traffic mapping of a multiplexed data stream of a first service; indication information for indicating whether to adopt the multiplexed data stream; and requirement information for indicating a mapping requirement for the multiplexed data stream.

[0102] In combination with some embodiments of the eighth aspect, in some embodiments, the requirement information may include at least one of the following: mapping type; mapping description; mapping priority.

[0103] In combination with some embodiments of the eighth aspect, in some embodiments, the mapping type may include at least one of the following: one-to-one mapping; one-to-many mapping; many-to-one mapping; many-to-many mapping.

[0104] In combination with some embodiments of the eighth aspect, in some embodiments, the mapping description may include at least one of the following: media type; stream dependency; channel dependency; layer dependency; synchronization dependency.

[0105] In combination with some embodiments of the eighth aspect, in some embodiments, the mapping priority may include at least one of the following: mapping requirement priority; mapping type priority; mapping description priority.

[0106] In combination with some embodiments of the eighth aspect, in some embodiments, the first rule can be determined based on indication information and / or requirement information.

[0107] In combination with some embodiments of the eighth aspect, in some embodiments, the transceiver module can also be configured to: send third information to the fourth core network device, wherein the third information includes a second rule, and the second rule is used for traffic mapping of the multiplexed data stream of the first service.

[0108] In combination with some embodiments of the eighth aspect, in some embodiments, the second rule can be determined in one of the following ways: determined according to the rule; determined according to at least one of the indication information and the requirement information.

[0109] In a ninth aspect, an embodiment of the present disclosure provides a fourth core network device. The fourth core network device includes: a processing module configured to determine a mapping of a multiplexed data flow of a first service to a quality of service (QoS) flow according to a second rule, wherein the second rule is used for traffic mapping of the multiplexed data flow.

[0110] In combination with some embodiments of the ninth aspect, in some embodiments, the fourth core network device may further include: a transceiver module configured to receive third information sent by the third core network device, wherein the third information includes a second rule, and the second rule is used for traffic mapping of the multiplexed data stream of the first service.

[0111] In combination with some embodiments of the ninth aspect, in some embodiments, the second rule may be locally configured.

[0112] 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 implementations thereof.

[0113] 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 implementations thereof.

[0114] In a twelfth aspect, an embodiment of the present disclosure provides 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 implementations thereof.

[0115] In a thirteenth aspect, an embodiment of the present disclosure provides 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 implementations thereof.

[0116] In a fourteenth aspect, an embodiment of the present disclosure provides 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 fifth aspect and possible implementations thereof.

[0117] In a fifteenth aspect, embodiments of the present disclosure provide a communications system. The communications system includes a first core network device and a second core network device. The first core network device is configured to implement the communications method described in any one of the first aspect and possible implementations thereof. The second core network device is configured to implement the communications method described in any one of the second aspect and possible implementations thereof.

[0118] In conjunction with some embodiments of the fifteenth aspect, in some embodiments, the communication system may further include a third core network device and a fourth core network device. The third core network device is configured to implement the communication method as described in any one of the third aspect and possible implementations thereof. The fourth core network device is configured to implement the communication method as described in any one of the fourth aspect and possible implementations thereof.

[0119] In conjunction with some embodiments of the fifteenth aspect, in some embodiments, the communication system may further include a fifth core network device, a sixth core network device, and a seventh core network device. The fifth core network device is configured to send fourth information. The fourth information is used to indicate QoS-related information. The sixth core network device is configured to send first information from the second core network device to the first core network device. The seventh core network device is configured to send the first information to the first core network device.

[0120] In a sixteenth aspect, an embodiment of the present disclosure provides a storage medium storing instructions that, when executed on a communication device, cause the communication device to execute the communication method described in any one of the first to fifth aspects and possible implementations thereof.

[0121] In a seventeenth 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 to fifth aspects and possible implementations thereof.

[0122] In an eighteenth 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 to fifth aspects and possible implementations thereof.

[0123] In a nineteenth aspect, an embodiment of the present disclosure provides a chip or a chip system. The chip or chip system includes a processing circuit. The processing circuit is configured to execute the communication method as described in any one of the first to fifth aspects and possible implementations thereof.

[0124] It is understandable that the above-mentioned core network devices (including the first core network device, the second core network device, the third core network device, and the fourth core network device), communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to execute the communication methods provided in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0125] The present disclosure provides a communication method, apparatus, core network device, communication system, and storage medium. In some embodiments, the terms "communication method," "information processing method," and "communication method" are interchangeable; the terms "apparatus," "information processing apparatus," and "communication apparatus" are interchangeable; and the terms "information processing system," "communication system," and "communication system" are interchangeable.

[0126] 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. Unless there is any 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 implementations in a certain embodiment can be arbitrarily combined. In addition, the embodiments can be arbitrarily combined. For example, some or all of the steps of different embodiments can be arbitrarily combined. For another example, a certain embodiment can be arbitrarily combined with the optional implementations of other embodiments.

[0127] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, 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.

[0128] 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.

[0129] 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 using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

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

[0131] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," and the like can be used interchangeably.

[0132] 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.

[0133] 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.

[0134] 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 another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0135] 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.

[0136] 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.

[0137] 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.

[0138] 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.

[0139] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0140] 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.

[0141] 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.

[0142] 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.

[0143] 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.

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

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

[0146] 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.

[0147] 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 103 .

[0148] 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.

[0149] In some embodiments, the access network device 102 is, for example, a node or device that accesses a terminal to a wireless network. The access network device 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 base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0150] In some embodiments, the technical solution of the present disclosure can be applied to the open radio access network (Open RAN) architecture. In this case, the interfaces between access network devices or within 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.

[0151] 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.

[0152] In some embodiments, the core network 103 may be a single device that integrates a first core network device 1031, a second core network device 1032, a third core network device 1033, a fourth core network device 1034, a fifth core network device 1035, a sixth core network device 1036, etc., or may be multiple devices or a device group that respectively include all or part of the first core network device 1031, the second core network device 1032, the third core network device 1033, the fourth core network device 1034, the fifth core network device 1035, the sixth core network device 1036, etc. The core network device may be virtual or physical. For example, the core network includes at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0153] In some embodiments, the first core network device 1031 may be, for example, a policy control function (PCF).

[0154] In some embodiments, the first core network device 1031 can be used to support a unified policy framework and provide policy rules, and the name is not limited thereto.

[0155] In some embodiments, the second core network device 1032 may be, for example, an application function (AF).

[0156] In some embodiments, the second core network device 1032 may be implemented by an application server and used to provide application services, but the name is not limited thereto.

[0157] In some embodiments, the third core network device 1033 may be, for example, a session management function (SMF).

[0158] In some embodiments, the third core network device 1033 can be used to perform session management, execution of PCF control policy, UPF selection, UE Internet Protocol (IP) address allocation and other functions, the name is not limited to this.

[0159] In some embodiments, the fourth core network device 1034 may be, for example, a user plane function (UPF).

[0160] In some embodiments, the fourth core network device 1034 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 to this.

[0161] In some embodiments, the fifth core network device 1035 may be, for example, an access and mobility management function (AMF).

[0162] In some embodiments, the fifth core network device 1035 can be used to complete mobility management, non-access stratum mobility management (NAS MM) signaling processing, NAS session management (SM) signaling routing, security anchor point and security context management, etc., and the name is not limited to this.

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

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

[0165] In some embodiments, the second core network device 1032 may be located inside the core network 103. Of course, in some scenarios, the second core network device 1032 may be located outside the core network 103, which is not specifically limited in the present embodiment.

[0166] 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.

[0167] 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.

[0168] 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.

[0169] 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. 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.

[0170] It should be noted that the NEF is not shown in FIG1B , but each core network device in the communication system can interact with the NEF.

[0171] 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.

[0172] 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. Naf is a service-based interface provided by AF.

[0173] 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.

[0174] 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.

[0175] The embodiments of the present disclosure can 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), 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 utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0176] 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 streams. 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. Effectively identifying and leveraging these characteristics will facilitate network and service transmission and control, as well as enhance service assurance and user experience.

[0177] In further cases, XRM services and interactive media services require the communication system to comprehensively consider the QoS characteristics of service data flows. Such QoS characteristics may include, for example, at least one of the following: whether parameters such as delay-sensitive guaranteed bit rate (GBR) data flows, guaranteed flow bit rate (GFBR), packet delay budget (PDB), and default maximum data burst volume (MDBV) can be simultaneously met and coordinated. It also 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.

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

[0179] 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: PDU set delay budget (PSDB), PDU set error rate (PSER), and PDU set integrated handling information (PSIHI). Then, the SMF and 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 carried PDU information can be used by the access network to perform PDU set-based QoS control.

[0180] In some embodiments, the PDU 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, and PDU set size. 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.

[0181] 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.

[0182] In some cases, the XRM service may be a multimedia type service, which corresponds to multiple data streams. These data streams may be multiplexed in the same quintet for transmission. The quintet constitutes an end-to-end transport layer connection. In this case, one or more data streams multiplexed in an end-to-end transport layer connection (e.g., a quintet) may be referred to as multiplexed data streams. In one example, the quintet may be a quintet that complies with the quick UDP internet connections (QUIC) protocol. In some embodiments, different data streams of the XRM service may have different QoS requirements. Then, different data streams may be transmitted using different QUIC connections or different QUIC streams. This requires the QoS architecture of the communication system to provide support for QoS classification in this scenario.

[0183] Figure 2 is an interactive diagram of a communication method according to an embodiment of the present disclosure. The communication method according to the embodiment of the present disclosure can be applied to a communication system 100. As shown in Figure 2, the communication method according to the embodiment of the present disclosure includes steps S201 to S217.

[0184] In step S201 , the second core network device 1032 sends first information to the sixth core network device 1036 .

[0185] In some embodiments, the sixth core network device 1036 may receive the first information.

[0186] In some embodiments, the first information may be used to request determination of a first rule.

[0187] In some embodiments, the first information may be used to request the first core network device 1031 to make a policy decision.

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

[0189] In some embodiments, the first information may include at least one of the following: instruction information, requirement information.

[0190] In some embodiments, the indication information may be used to indicate whether to adopt the multiplexed data stream.

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

[0192] In some embodiments, the name of the indication information is not limited, and it can be, for example, a multiplexed data stream indication, a multi-channel data stream indication, a multi-channel data stream indication, etc.

[0193] In some embodiments, the requirement information may be used to indicate a mapping requirement for the multiplexed data stream. The mapping requirement may be used by the first core network device 1031 to determine the first rule.

[0194] In some embodiments, the name of the requirement information is not limited, and it can be, for example, stream mapping requirement, mapping parameter information, mapping requirement indication information, etc.

[0195] In some embodiments, the requirement information may include at least one of the following: mapping type, mapping description, and mapping priority.

[0196] In some embodiments, the mapping type may be used to indicate a mapping relationship between a data flow of the first service and a QoS flow.

[0197] 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 data stream of the first service may be mapped to one QoS stream. In one example, under the one-to-many mapping type, one data stream of the first service may be mapped to multiple QoS streams. In one example, under the many-to-one mapping type, multiple data streams of the first service may be mapped to one QoS stream. In one example, under the many-to-many mapping type, multiple data streams of the first service may be mapped to multiple QoS streams.

[0198] In some embodiments, the mapping description may be used to describe mapping-related requirements.

[0199] In some embodiments, the mapping description may be used to describe each data flow of the first service.

[0200] In some embodiments, the mapping description may include at least one of the following: media type, stream dependency, channel dependency, layer dependency, and synchronization dependency. It is understood that the mapping description may also include other information, which is not specifically limited in the embodiments of the present disclosure.

[0201] In some embodiments, the media type may be the media type of the data stream of the first business. 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 data streams of the first business may be video. In one example, the media type of one or more data streams of the first business may be audio. In one example, the media type of one or more data streams of the first business may be video, and the media type of one or more data streams may be audio. It is understandable that the media type may also include other types (for example, tactile feedback), which is not specifically limited in the embodiments of the present disclosure.

[0202] In some embodiments, the stream dependency may be a dependency relationship between data streams in the multiplexed data stream of the first service. In some embodiments, the stream dependency may be used to indicate the dependency of a data stream on the multiplexed data stream of the first service.

[0203] In some embodiments, the channel dependency may be a dependency relationship between different channels of the first service. In some embodiments, the audio data may include data of one or more audio channels, and the channel dependency may be a dependency relationship between the audio channels. In one example, the channel dependency may be used to indicate the dependency of an audio channel on various audio channels of the audio of the first service.

[0204] In some embodiments, layer dependencies may be dependencies between different layers of the first service. In some embodiments, a video is composed of multiple consecutive images. Image data may include data from one or more layers (or layers). Layer dependencies may be dependencies between layers (or layers). In one example, layer dependencies may be used to indicate the dependency of a layer (or layers) on various layers (or layers) of the video image of the first service.

[0205] In some embodiments, the synchronization dependency may be a synchronization requirement and / or delay requirement between data streams in the multiplexed data stream of the first service. In some embodiments, the synchronization dependency may be used to indicate a synchronization rate and / or delay between some or all data streams in the multiplexed data stream of the first service.

[0206] In some embodiments, a mapping priority may be used to indicate a priority between different mapping requirements.

[0207] In some embodiments, the mapping priority may include at least one of the following: a mapping requirement priority, a mapping type priority, and a mapping description priority.

[0208] In some embodiments, a mapping requirement priority may be used to indicate a priority of one or more flow mapping requirements.

[0209] In some embodiments, the mapping type priority can be used to indicate the priority of one or more mapping types. In one example, any two of one-to-one mapping, one-to-many mapping, many-to-one mapping, and many-to-many mapping can have the same or different priorities.

[0210] In some embodiments, a mapping description mapping priority can be used to indicate the priority of multiple mapping descriptions. In one example, the mapping description can be a mapping descriptor. In this case, different mapping descriptors can correspond to the same or different priorities.

[0211] In some embodiments, the first information may be sent by the second core network device 1032 to the sixth core network device 1036 via the service-based interface Nnef.

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

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

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

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

[0216] 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.

[0217] 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.

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

[0219] 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 is not specifically limited in the embodiments of the present disclosure.

[0220] In some embodiments, the service information of the first service may include at least one of the following: a data flow 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.

[0221] In some embodiments, the data flow identifier of the first service can be used to identify a data flow and / or a data flow group related to the first service. In one example, the data 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.

[0222] In step S202, the sixth core network device 1036 performs authorization.

[0223] In some embodiments, the sixth core network device 1036 may authorize the request message from the second core network device 1032 .

[0224] In some embodiments, the second core network device 1032 may be untrusted. In this case, the request message may be sent by the sixth core network device 1036 to the first core network device 1031 .

[0225] In some embodiments, the sixth core network device 1036 may perform the mapping.

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

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

[0228] In some embodiments, the sixth core network device 1036 can implement a mapping between an external group identifier and an internal group identifier for the first service. In one example, the sixth core network device 1036 can map the external group identifier of the first service to an internal group identifier based on subscription information. In one example, the subscription information can be obtained from the UDM.

[0229] In step S203 , the sixth core network device 1036 sends first information to the first core network device 1031 .

[0230] In some embodiments, the sixth core network device 1036 may send the first information received from the second core network device 1032 to the first core network device 1031 .

[0231] In some embodiments, the first core network device 1031 may receive the first information.

[0232] In some embodiments, the sixth core network device 1036 may also send at least one of the following to the first core network device 1031 : protocol description, flow detection information, and service information of the first service.

[0233] In some embodiments, the sixth core network device 1036 may send the first information in different ways. In some embodiments, the sixth core network device 1036 may determine the way to send the first information based on information and / or parameters received from the second core network device 1032.

[0234] In some embodiments, the manner in which the sixth core network device 1036 sends the first information may include: sending through a time sensitive communication and time synchronization function (TSCTSF) or sending directly.

[0235] In some embodiments, the sixth core network device 1036 may determine to send the first information to the first core network device 1031 through the TSCTSF. In some embodiments, the sixth core network device 1036 may send the first information to the TSCTSF through a service-based interface Ntsftsf, and then the TSCTSF may send the first information to the first core network device 1031 through a service-based interface Npcf. In one example, the sixth core network device 1036 may send the first information to the TSCTSF through an Ntsctsf_QoSandTSCAssistance_Create request message, and then the TSCTSF may send the first information to the first core network device 1031 through an Npcf_PolicyAuthorization_Create request message or an Npcf_PolicyAuthorization_Update request message.

[0236] In some embodiments, the sixth core network device 1036 may determine to send the first information directly to the first core network device 1031. In some embodiments, the sixth core network device 1036 may send the first information to the first core network device 1031 via a service-based interface Npcf. In one example, the sixth core network device 1036 may send the first information to the first core network device 1031 via an Npcf_PolicyAuthorization_Create request message.

[0237] In some embodiments, steps S201 to S203 may be omitted (ie, not executed). In this case, the first core network device 1031 will not obtain the first information from the second core network device 1032. The first core network device 1031 may obtain the first information in other ways.

[0238] In some embodiments, the first core network device 1031 may receive the first information from the seventh core network device (not shown). In one example, after acquiring the first information, the seventh core network device may send the first information to the first core network device 1031.

[0239] In some embodiments, the seventh core network device may be a core network device having the same function as the first core network device 1031. In other words, the seventh core network device may be another first core network device.

[0240] In some embodiments, the first core network device 1031 may determine the first information based on operator operation and management configuration.

[0241] In some embodiments, the first core network device 1031 may determine the first information according to local configuration.

[0242] In step S204 , the first core network device 1031 makes a policy decision.

[0243] In some embodiments, the first core network device 1031 may perform a policy decision to determine the first rule.

[0244] In some embodiments, the first rule may be used for traffic mapping of a multiplexed data flow of a first service.

[0245] In some embodiments, the first rule may be a QoS rule. In some embodiments, the first rule may belong to a QoS rule.

[0246] In some embodiments, the first rule may be new. In some embodiments, according to the first information, the first core network device 1031 may determine a new first rule.

[0247] In some embodiments, the first rule may be updated. According to the first information, the first core network device 1031 may determine to update the existing first rule.

[0248] In some embodiments, in the process of determining the first rule, the first core network device 1031 may consider the first information.

[0249] In some embodiments, the first information may be determined based on consideration of the first information.

[0250] In some embodiments, the first information may be determined by taking into account at least one of the indication information and the requirement information.

[0251] In some embodiments, the name of the first rule is not limited, and it can be, for example, a traffic mapping policy, a traffic mapping rule, or a traffic mapping relationship.

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

[0253] In some embodiments, the first rule may include at least one of the following: mapping priority, mapping type, mapping description, media type, media format, stream dependency, channel dependency, layer dependency, synchronization dependency, stream importance, channel importance, and layer importance. Of course, the first rule may also include other information, which is not specifically limited in the present embodiment.

[0254] In some embodiments, mapping priorities can be used to determine the order in which mapping requirements, mapping types, and / or mapping descriptions are applied. In one example, a corresponding mapping priority can be used for each first rule. In one example, a corresponding mapping priority can be used for each mapping type. In one example, a corresponding mapping priority can be used for each mapping description.

[0255] In some embodiments, a mapping type can be used to indicate a mapping mode. In one example, the mapping mode indicated by the mapping type can be at least one of the following: one-to-one mapping, one-to-many mapping, many-to-one mapping, and many-to-many mapping. In one example, the mapping mode can be represented as an m-to-n mapping, where m and n are positive integers. In one example, m and n can be equal or different.

[0256] In some embodiments, the mapping description may include mapping descriptor components required for the first rule.

[0257] In some embodiments, media type can be used to indicate that the mapping considers media type. In one example, media type can include audio and / or video. In this case, the first rule can be applied to all streams of audio and / or video types.

[0258] In some embodiments, the media format may be used to indicate that the mapping takes the media format into account. In an example, the media format may include at least one of the following: media format information, parameters and / or information related to the media format.

[0259] In some embodiments, stream dependency can be used to indicate that mapping takes stream dependency into account. In one example, stream dependency can be used to indicate dependency on a sub-stream of a multiplexed data stream. In this case, the first rule can be applied to the sub-stream of the multiplexed data stream.

[0260] In some embodiments, channel dependency can be used to indicate that the mapping takes channel dependency into account. In one example, channel dependency can be used to indicate the flow of one or more channels of audio. In this case, the first rule can be applied to the flow of one or more channels of audio.

[0261] In some embodiments, layer dependency can be used to indicate that the mapping takes layer dependency into account. In one example, layer dependency can be used to indicate the flow of one or more layers of the video. In this case, the first rule can be applied to the flow of one or more layers of the video.

[0262] In some embodiments, synchronization dependency can be used to indicate that the mapping takes synchronization dependency into account. In one example, synchronization dependency can be used to indicate one or more flows with synchronization requirements and / or delay requirements. In this case, the first rule can be applied to one or more flows with synchronization requirements and / or delay requirements.

[0263] In some embodiments, stream importance can be used to indicate that mapping takes stream importance into account. In one example, stream importance can be used to indicate relatively important (i.e., more important) sub-streams or multiplexed streams. In this case, the first rule can be applied to relatively important (i.e., more important) sub-streams or multiplexed streams.

[0264] In some embodiments, channel importance can be used to indicate that the mapping takes channel importance into account. In one example, channel importance can be used to indicate the streams of one or more channels that are relatively important (i.e., have higher importance) in the audio. In this case, the first rule can be applied to the streams of one or more channels that are relatively important (i.e., have higher importance) in the audio.

[0265] In some embodiments, layer importance can be used to indicate that the mapping takes layer importance into account. In one example, layer importance can be used to indicate the streams of one or more layers in the video that are relatively important (i.e., have higher importance). In this case, a rule can be applied to the streams of one or more layers in the video that are relatively important (i.e., have higher importance).

[0266] In step S205 , the first core network device 1031 sends a response message to the sixth core network device 1036 .

[0267] In some embodiments, the sixth core network device 1036 may receive a response message.

[0268] In some embodiments, the first core network device 1031 may send a response message after receiving the first information.

[0269] 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 first core network device 1031 in response to the Npcf_PolicyAuthorization_Create request message.

[0270] In step S206 , the sixth core network device 1036 sends a response message to the second core network device 1032 .

[0271] In some embodiments, the second core network device 1032 may receive a response message.

[0272] In some embodiments, the response message may carry the authorization result of the first core network device 1031 to the request message of the second core network device 1032. In this way, the response message may be used to indicate to the second core network device 1032 whether the request message is authorized.

[0273] In some embodiments, the sixth core network device 1036 may send a response message to the second core network device 1032 after receiving the response message from the first core network device 1031 .

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

[0275] In step S207 , the first core network device 1031 sends second information to the third core network device 1033 .

[0276] In some embodiments, the third core network device 1033 may receive the second information.

[0277] In some embodiments, the second information may be used by the third core network device 1033 to determine the second rule.

[0278] In some embodiments, the second information may include at least one of the following: a first rule, instruction information, or requirement information. In one example, the second information may include the first rule. In one example, the second information may include instruction information and / or requirement information. In one example, the second information may include the first rule, instruction information, and / or requirement information.

[0279] In some embodiments, the second information may be sent to the third core network device 1033 via the service-based interface Npcf.

[0280] In some embodiments, the first core network device 1031 may initiate an SM Policy Association Modification process to send the second information.

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

[0282] In step S208 , the third core network device 1033 sends a response message to the first core network device 1031 .

[0283] In some embodiments, the first core network device 1031 may receive a response message.

[0284] In some embodiments, the third core network device 1033 may send a response message after receiving the second information.

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

[0286] In step S209 , the third core network device 1033 sends third information to the fourth core network device 1034 .

[0287] In some embodiments, the fourth core network device 1034 may receive the third information.

[0288] In some embodiments, the third information may be used to indicate a mapping rule.

[0289] In some embodiments, the third information may include the second rule.

[0290] In some embodiments, the second rule may be used for traffic mapping of the multiplexed data flow of the first service.

[0291] In some embodiments, the name of the second rule is not limited, and it can be, for example, a traffic mapping policy, a traffic mapping rule, or a traffic mapping relationship.

[0292] In some embodiments, the second rule may be determined by the third core network device 1033 based on the second information after receiving the second information.

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

[0294] In some embodiments, the second rule may be determined according to indication information and / or requirement information.

[0295] In some embodiments, the second rule may be determined according to the first rule, and indication information and / or requirement information.

[0296] In some embodiments, the second rule may be a QoS rule. In some embodiments, the second rule may belong to a QoS rule.

[0297] In some embodiments, the third information may also include QoS parameters.

[0298] In some embodiments, the third core network device 1033 may send the third information through an N4 session.

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

[0300] In some embodiments, step S209 may be omitted (ie, not executed). In this case, the fourth core network device 1034 does not obtain the third information from the third core network device 1033. Then, the fourth core network device 1034 may obtain the second rule in other ways.

[0301] In some embodiments, the second rule may be locally configured. In other words, the second rule may be pre-configured on the third core network device 1033 .

[0302] In step S210 , the fourth core network device 1034 determines the mapping of the multiplexed data stream.

[0303] In some embodiments, the fourth core network device 1034 may determine the mapping of the multiplexed data flow of the first service to the QoS flow according to the second rule.

[0304] In some embodiments, the second rule and / or QoS parameter in the third information may be configured to the fourth core network device 1034. In this way, the fourth core network device 1034 may implement mapping of the multiplexed data flow of the first service to the QoS flow according to the second rule.

[0305] In some embodiments, upon detecting traffic of the multiplexed data stream of the first service, the fourth core network device 1034 may map the multiplexed data stream of the first service according to the second rule. In one example, the fourth core network device 1034 may map the multiplexed data stream of the first service to one or more corresponding QoS flows according to the second rule.

[0306] In step S211 , the fourth core network device 1034 sends a response message to the third core network device 1033 .

[0307] In some embodiments, the third core network device 1033 may receive a response message.

[0308] In some embodiments, the fourth core network device 1034 may send a response message through the N4 session.

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

[0310] In step S212 , the third core network device 1033 sends fourth information to the fifth core network device 1035 .

[0311] In some embodiments, the fifth core network device 1035 may receive the fourth information.

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

[0313] In some embodiments, the fourth information may include at least one of the following: QoS rules, QoS parameters.

[0314] In some embodiments, the QoS rule in the fourth information may be the first rule, or determined based on the first rule.

[0315] In some embodiments, the QoS rule in the fourth information may be the second rule, or determined based on the second rule.

[0316] In some embodiments, the QoS rule in the fourth information may be determined based on the indication information and / or the requirement information.

[0317] In some embodiments, the fourth information can be sent to the fifth core network device 1035 via the service-based interface Namf.

[0318] In some embodiments, the third core network device 1033 may send the fourth information to the fifth core network device 1035 through the Namf_Communication_N1N2MessageTransfer service operation.

[0319] In some embodiments, during a Namf_Communication_N1N2MessageTransfer service operation, the third core network device 1033 may send a Namf_Communication_N1N2MessageTransfer request message to the fifth core network device 1035, after which the fifth core network device 1035 may send a Namf_Communication_N1N2MessageTransfer response message to the third core network device 1033. The fourth information may be carried in the Namf_Communication_N1N2MessageTransfer request message.

[0320] 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, QoS flow identifier (QoS flow identifier, QFI), QoS profile (QoS profile), and N1 SM container.

[0321] In step S213 , the fifth core network device 1035 sends fourth information to the access network device 102 .

[0322] In some embodiments, the access network device 102 may receive the fourth information.

[0323] In some embodiments, the fifth core network device 1035 may send the fourth information to the access network device 102 via an N2 message (N2message).

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

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

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

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

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

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

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

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

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

[0333] In step S215 , the access network device 102 sends a confirmation message to the fifth core network device 1035 .

[0334] In some embodiments, the fifth core network device 1035 may receive an acknowlegement message (ACK).

[0335] In some embodiments, the access network device may send a confirmation message to the fifth core network device 1035 via an N2 message.

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

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

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

[0339] In step S216 , the fifth core network device 1035 sends fifth information to the third core network device 1033 .

[0340] In some embodiments, the third core network device 1033 may receive the fifth information.

[0341] In some embodiments, the fifth information may include N2 SM information.

[0342] In some embodiments, the fifth core network device 1035 may send the fifth information to the third core network device 1033 through the Nsmf_PDUSession_UpdateSMContext service operation.

[0343] In some embodiments, during the Nsmf_PDUSession_UpdateSMContext service operation, the fifth core network device 1035 may send an Nsmf_PDUSession_UpdateSMContext request message to the third core network device 1033, after which the third core network device 1033 may send an Nsmf_PDUSession_UpdateSMContext response message to the fifth core network device 1035. The fifth information may be carried in the Nsmf_PDUSession_UpdateSMContext request message.

[0344] In step S217 , the third core network device 1033 sends fifth information to the fourth core network device 1034 .

[0345] In some embodiments, the third core network device 1033 may send the received fifth information to the fourth core network device 1034 .

[0346] In some embodiments, the fourth core network device 1034 may receive the fifth information.

[0347] In some embodiments, the fourth core network device 1034 may send the fifth information to the fourth core network device 1034 through an N4 Session Modification service operation.

[0348] In some embodiments, during the N4 Session Modification service operation, the third core network device 1033 may send an N4 Session Modification request message to the fourth core network device 1034, and then the fourth core network device 1034 may send an N4 Session Modification response message to the third core network device 1033. The fifth information may be carried in the N4 Session Modification request message.

[0349] In some embodiments, the fifth information may be used to update the N4 session of the fourth core network device 1034 .

[0350] It should be noted that the communication system 100 may include part of the first core network device 1031, the second core network device 1032, the third core network device 1033, the fourth core network device 1034, the fifth core network device 1035, the sixth core network device 1036, and the seventh core network device (not shown) involved above.

[0351] In some embodiments, the communication system 100 may include a first core network device 1031 and a second core network device 1032 .

[0352] In some embodiments, the communication system 100 may further include a third core network device 1033 and / or a fourth core network device 1034. In one example, the communication system 100 may include a first core network device 1031, a second core network device 1032, and a third core network device 1033. In one example, the communication system 100 may include a first core network device 1031, a second core network device 1032, and a fourth core network device 1034. In one example, the communication system 100 may include a first core network device 1031, a second core network device 1032, a third core network device 1033, and a fourth core network device 1034.

[0353] In some embodiments, the communication system 100 may further include one or more of a fifth core network device 1035, a sixth core network device 1036, and a seventh core network device. In one example, the communication system 100 may include a first core network device 1031, a second core network device 1032, and a sixth core network device 1036. In one example, the communication system 100 may include the first core network device 1031, the second core network device 1032, and the seventh core network device. In one example, the communication system 100 may include the first core network device 1031, the second core network device 1032, the third core network device 1033, and the fifth core network device 1035. In one example, the communication system 100 may include the first core network device 1031, the second core network device 1032, the third core network device 1033, the fourth core network device 1034, and the fifth core network device 1035. In an example, the communication system 100 may include a first core network device 1031 , a second core network device 1032 , a third core network device 1033 , a fourth core network device 1034 , a fifth core network device 1035 , and a sixth core network device 1036 .

[0354] 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.

[0355] 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.

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

[0357] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0358] 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.

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

[0360] 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.

[0361] 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.

[0362] In some embodiments, terms such as "traffic", "flow", "stream", and "data flow" can be used interchangeably.

[0363] The communication method involved in the embodiments of the present disclosure may include at least one of steps S201 to S217. For example, step S201 can be implemented as an independent embodiment. For example, step S203 can be implemented as an independent embodiment. For example, step S207 can be implemented as an independent embodiment. For example, step S209 can be implemented as an independent embodiment. For example, step S210 can be implemented as an independent embodiment. For example, the combination of steps S201 and S203 can be implemented as an independent embodiment. For example, the combination of steps S209 and S210 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S201 to S217 are not limited to this.

[0364] In some embodiments, at least two of steps S201 to S217 may be performed in an interchangeable order or simultaneously. For example, steps S205 and S206 may be performed in an interchangeable order or simultaneously. For example, steps S208 and S209 may be performed in an interchangeable order or simultaneously.

[0365] In some embodiments, steps S202 to S217 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0366] In some embodiments, steps S201 , S202 , and S204 to S217 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0367] In some embodiments, steps S201 to S206 and S208 to S217 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0368] In some embodiments, steps S201 to S209 and S211 to S217 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0369] FIG3 is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method. The communication method is executed by the first core network device 1031. As shown in FIG3, the method includes steps S301 to S305.

[0370] In step S301, first information is determined.

[0371] The optional implementation of step S301 can refer to the optional implementation of step S203 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0372] In some embodiments, the first core network device 1031 may receive first information sent by the second core network device 1032 (via the sixth core network device 1036 ), but is not limited thereto and may also receive first information sent by other entities.

[0373] In some embodiments, the first core network device 1031 may receive the first information sent by the seventh core network device.

[0374] In some embodiments, the first core network device 1031 may obtain first information specified by a protocol.

[0375] In some embodiments, the first core network device 1031 may obtain the first information from an upper layer.

[0376] In some embodiments, the first core network device 1031 may perform processing to obtain the first information.

[0377] In some embodiments, the first core network device 1031 may determine the first information based on an operator operation and maintenance configuration.

[0378] In some embodiments, the first core network device 1031 may determine the first information according to local configuration.

[0379] In step S302 , policy decision is performed.

[0380] The optional implementation of step S302 can refer to the optional implementation of step S204 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.

[0381] In some embodiments, the first core network device 1031 may perform a policy decision taking into account the first information.

[0382] In some embodiments, the first rule may be determined by a policy decision.

[0383] In some embodiments, the first rule may be determined taking into account the first information.

[0384] In step S303, a response message is sent.

[0385] The optional implementation of step S303 can refer to the optional implementation of step S205 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0386] In some embodiments, the first core network device 1031 may send a response message to the sixth core network device 1036 , but is not limited thereto and may also send a response message to other entities.

[0387] In step S304, the second information is sent.

[0388] The optional implementation of step S304 can refer to the optional implementation of step S207 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0389] In some embodiments, the first core network device 1031 may send the second information to the third core network device 1033 , but is not limited thereto and the second information may also be sent to other entities.

[0390] In some embodiments, the second information may be used by the third core network device 1033 to determine the second rule.

[0391] In step S305, a response message is obtained.

[0392] The optional implementation of step S305 can refer to the optional implementation of step S208 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

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

[0394] The communication method involved in the embodiments of the present disclosure may include at least one of steps S301 to S305. For example, step S301 may be implemented as an independent embodiment. For example, step S304 may be implemented as an independent embodiment. For example, a combination of steps S301 and S304 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S301 to S305 are not limited to this.

[0395] In some embodiments, at least two of steps S301 to S305 may be performed in an interchangeable order or simultaneously. For example, steps S303 and S304 may be performed in an interchangeable order or simultaneously.

[0396] In some embodiments, steps S302, S303, S304, and S305 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0397] In some embodiments, steps S301 , S302 , S303 , and S305 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0398] FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method. The communication method is performed by the second core network device 1032. As shown in FIG4, the method includes steps S401 to S402.

[0399] In step S401, first information is sent.

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

[0401] In some embodiments, the second core network device 1032 may send the first information to the first core network device 1031 (via the sixth core network device 1036 ), but is not limited thereto and may also send the first information to other entities.

[0402] In some embodiments, the first information may be used by the first core network device 1031 to determine a first rule.

[0403] In step S402, a response message is obtained.

[0404] The optional implementation of step S402 can refer to the optional implementation of step S206 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0405] In some embodiments, the second core network device 1032 may receive a response message sent by the sixth core network device 1036 , but is not limited thereto and may also receive a response message sent by other entities.

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

[0407] In some embodiments, step S402 is optional and may be omitted or replaced in different embodiments.

[0408] FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method. The communication method is executed by the third core network device 1033. As shown in FIG5, the method includes steps S501 to S507.

[0409] In step S501, second information is obtained.

[0410] The optional implementation of step S501 can refer to the optional implementation of step S207 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

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

[0412] In step S502, a response message is sent.

[0413] The optional implementation of step S502 can refer to the optional implementation of step S208 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.

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

[0415] In step S503, the third information is sent.

[0416] The optional implementation of step S503 can refer to the optional implementation of step S209 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0417] In some embodiments, the third core network device 1033 may send the third information to the fourth core network device 1034 , but is not limited thereto and the third information may also be sent to other entities.

[0418] In some embodiments, the third information may be used by the fourth core network device 1034 to map the multiplexed data stream.

[0419] In step S504, a response message is obtained.

[0420] The optional implementation of step S504 can refer to the optional implementation of step S211 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.

[0421] In some embodiments, the third core network device 1033 may receive a response message sent by the fourth core network device 1034 , but is not limited thereto and may also receive a response message sent by other entities.

[0422] In step S505, the fourth information is sent.

[0423] The optional implementation of step S505 can refer to the optional implementation of step S212 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.

[0424] In some embodiments, the third core network device 1033 may send the fourth information to the fifth core network device 1035 , but is not limited thereto and the fourth information may also be sent to other entities.

[0425] In step S506, the fifth information is obtained.

[0426] The optional implementation of step S506 can refer to the optional implementation of step S216 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

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

[0428] In step S507, the fifth information is sent.

[0429] The optional implementation of step S506 can refer to the optional implementation of step S217 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0430] In some embodiments, the third core network device 1033 may send the fifth information to the fourth core network device 1034 , but is not limited thereto and the fifth information may also be sent to other entities.

[0431] The communication method involved in the embodiments of the present disclosure may include at least one of steps S501 to S507. For example, step S501 may be implemented as an independent embodiment. For example, step S503 may be implemented as an independent embodiment. For example, a combination of steps S501 and S503 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S501 to S507 are not limited to this.

[0432] In some embodiments, steps S502 to S507 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0433] In some embodiments, steps S501 , S502 , and S504 to S507 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0434] FIG6 is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method. The communication method is performed by the fourth core network device 1034. As shown in FIG6, the method includes steps S601 to S604.

[0435] In step S601, third information is obtained.

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

[0437] In some embodiments, the fourth core network device 1034 may receive the third information sent by the third core network device 1033 , but is not limited thereto and may also receive the third information sent by other entities.

[0438] In some embodiments, the fourth core network device 1034 may obtain third information specified by the protocol.

[0439] In some embodiments, the fourth core network device 1034 may obtain the third information from a higher layer.

[0440] In some embodiments, the fourth core network device 1034 may perform processing to obtain the third information.

[0441] In step S602, the mapping of the multiplexed data stream is determined.

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

[0443] In step S603, a response message is sent.

[0444] The optional implementation of step S603 can refer to the optional implementation of step S211 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.

[0445] In some embodiments, the fourth core network device 1034 may send a response message to the third core network device 1033 , but is not limited thereto and may also send a response message to other entities.

[0446] In step S604, the fifth information is obtained.

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

[0448] In some embodiments, the fourth core network device 1034 may receive the fifth information sent by the third core network device 1033 , but is not limited thereto and may also receive the fifth information sent by other entities.

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

[0450] In some embodiments, steps S602, S603, and S604 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0451] In some embodiments, steps S601, S603, and S604 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0452] Figure 7 is an interactive diagram of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 7, an embodiment of the present disclosure relates to a communication method. The communication method includes step S701.

[0453] In step S701 , the second core network device 1032 sends first information to the core network device 103 .

[0454] The optional implementation of step S701 can refer to the optional implementation of step S201 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0455] FIG8A is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG8A , the embodiment of the present disclosure relates to a communication method. The communication method includes step S8101.

[0456] In step S8101 , the second core network device 1032 sends first information to the sixth core network device 1036 .

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

[0458] FIG8B is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG8B , the embodiment of the present disclosure relates to a communication method. The communication method includes step S8201.

[0459] In step S8201 , the sixth core network device 1036 sends first information to the first core network device 1031 .

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

[0461] FIG8C is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG8C , the embodiment of the present disclosure relates to a communication method. The communication method includes step S8301.

[0462] In step S8301 , the first core network device 1031 sends second information to the third core network device 1033 .

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

[0464] FIG8D is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG8D , the embodiment of the present disclosure relates to a communication method. The communication method includes step S8401.

[0465] In step S8401, the fourth core network device 1034 determines the mapping of the multiplexed data stream.

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

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

[0468] Figure 9 is an interactive diagram of an exemplary implementation of a communication method according to an embodiment of the present disclosure. As shown in Figure 9 , the communication method according to an embodiment of the present disclosure may include steps S901 to S918.

[0469] In step S901, the AF (ie, the second core network device) sends an AF session resource request, for example, through an Nnef_AFsessionWithQoS_Create request, to create an AF request. The AF carries the QoS requirements of the XRM service and interactive media service data flows in the request message.

[0470] In some embodiments, the AF sends a multiplexed data flow indication (i.e., indication information), and / or a traffic mapping requirement (i.e., requirement information), and / or a protocol description to the 5GC (NEF / PCF).

[0471] In some embodiments, the multiplexed data stream indication is used to indicate whether the media stream is multiplexed.

[0472] In some embodiments, the traffic mapping requirement indicates a mapping requirement corresponding to one or more multiplexed data flows, for the PCF to generate a traffic mapping policy rule.

[0473] In some embodiments, traffic mapping requirements may include:

[0474] (1) Mapping mode: For example, one-to-one, one-to-many, many-to-one, and many-to-many.

[0475] (2) Mapping descriptor: It can be: media type (e.g., audio / video), stream dependency (e.g., substream dependent on a multiplexed stream), channel dependency (e.g., one or more channels of audio), layer dependency (e.g., one or more layers of video), synchronization dependency (e.g., streams with synchronization requirements or similar latency requirements).

[0476] (3) Mapping precedence: Determines the execution order of mapping requirements / mapping types / mapping descriptors.

[0477] In some embodiments, the protocol description or flow detection information provides information such as protocol type, codec type, media type, etc.

[0478] In some embodiments, the AF may send this information to the NEF / PCF during the AF QoS request / update process.

[0479] In some embodiments, the XRM service (i.e., first service) information may be carried to identify the XRM service data flow or data flow group (e.g., multimodal service ID), UE address / UE identifier, AF identifier, application ID, flow description, DNN, S-NSSAI, QoS parameters, and other corresponding information. Here, the multimodal service ID can be used to identify all flows in the XRM service group.

[0480] In step S902, NEF (i.e., the sixth core network device) authorizes the AF request. If it is an untrusted AF, the AF request is sent to the PCF through NEF. (Optionally, NEF performs relevant mappings, including mapping of XRM services (AF service identifiers) to DNN and S-NSSAI, mapping of external applications to core network application identifiers; and mapping of external UE identifiers to UE identifiers within the core network based on UDM subscription information (such as SUPI), as well as mapping of external to internal XRM service group identifiers based on UDM subscription information).

[0481] In step S903, the NEF authorizes the AF request and determines whether to trigger the TSCTSF or directly contact the PCF based on the parameters provided by the AF. These signaling steps can be found in the AF session with required QoS process. The PCF receives the attributes provided by the AF from the NEF or TSCTSF. The NEF triggers Npcf_PolicyAuthorization_Create and sends the AF request to the PCF, carrying QoS requirement information for the PCF (i.e., the first core network device) to make policy decisions. The message carries the multiplexed data flow indication and / or traffic mapping requirements of the corresponding SDF.

[0482] In step S904, the PCF makes a policy decision and may determine that updated or new policy information needs to be sent to the SMF (ie, the third core network device).

[0483] In some embodiments, the PCF determines PCC rules (including traffic mapping policy rules (ie, first rules)) taking into account the multiplexed data flow indication and / or traffic mapping requirements provided by the AF.

[0484] In some embodiments, the PCF sends traffic mapping policy rules to the SMF via PCC rules.

[0485] In some embodiments, the form and content of the traffic mapping policy rules can be seen in Table 1 below.

[0486] Table 1: Traffic mapping policy rules

[0487] In step S905 , the PCF sends an Npcf_Policy Authorization_Create response to the NEF in response.

[0488] In step S906, the NEF sends an Nnef_AFsessionWithQoS_Create response message to the AF, which carries the authorization result to inform whether the request is authorized.

[0489] In step S907, the PCF initiates an SM Policy Association Modification request to the SMF, which carries the PCC rules.

[0490] In some embodiments, upon receiving PCC rules (including traffic mapping policy rules (i.e., the second rules)), the SMF determines QoS rules (including traffic mapping policy rules) and QoS set parameters to configure / or activate traffic mapping policy rules for the UPF (i.e., the fourth core network device) (e.g., through the N4 session).

[0491] In some embodiments, the SMF may obtain traffic mapping policy rules taking into account the multiplexed data flow indication and / or traffic mapping requirements provided by the PCF / AF.

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

[0493] In step S909, the SMF initiates an N4 Session Modification request to the UPF, which includes traffic mapping policy rules.

[0494] In step S910 , the UPF responds to the SMF.

[0495] In some embodiments, the UPF detects traffic and maps multiplexed data flows in a single end-to-end transport connection to one or more QoS flows based on traffic mapping policy rules (provided by the SMF or pre-configured locally).

[0496] In step S911 , 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)).

[0497] In step S912, AMF (ie, the fifth core network device) may send an N2 message (N2 SM information received from SMF, NAS message (PDU session ID, N1 SM container (PDU session modification command))) to RAN (ie, access network device).

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

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

[0500] In step S916, the SMF replies with an Nsmf_PDUSession_UpdateSMContext response.

[0501] In step S917 and step S918, 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.

[0502] 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.

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

[0504] 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.

[0505] 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.

[0506] FIG10 is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. As shown in FIG10 , the communication device 1000 may include at least one of the following: a transceiver module 1001 and a processing module 1002 .

[0507] In some embodiments, the communication device 1000 may be a first core network device 1031. In some embodiments, the transceiver module 1001 may be configured to obtain first information, wherein the first information is used to request determination of a first rule, and the first rule is used for traffic mapping of a multiplexed data stream of a first service. Optionally, the transceiver module 1001 may be configured to execute at least one of the communication steps such as sending and / or receiving (for example, steps S203, S205, S207, S208) executed by the first core network device 1031 in any of the above methods, which are not described in detail here. Optionally, the processing module 1002 may be configured to execute at least one of the other steps (for example, step S204) other than the communication steps such as sending and / or receiving executed by the first core network device 1031 in any of the above methods, which are not described in detail here.

[0508] In some embodiments, the communication device 1000 may be a second core network device 1032. In some embodiments, the transceiver module 1001 may be configured to send first information, where the first information is used to request determination of a first rule, where the first rule is used for traffic mapping of a multiplexed data stream of a first service. Optionally, the transceiver module 1001 may be configured to perform at least one of the communication steps (e.g., step S201) such as sending and / or receiving performed by the second core network device 1032 in any of the above methods, which will not be further described herein.

[0509] In some embodiments, the communication device 1000 may be a third core network device 1033. In some embodiments, the transceiver module 1001 may be configured to receive second information, wherein the second information includes one of the following: a first rule, wherein the first rule is used for traffic mapping of a multiplexed data stream of a first service; at least one of indication information and requirement information, wherein the indication information is used to indicate whether to adopt a multiplexed data stream, and the requirement information is used to indicate a mapping requirement for the multiplexed data stream. Optionally, the transceiver module 1001 may be configured to execute at least one of the communication steps such as sending and / or receiving (for example, steps S207, S208, S209, S211, S212, S216, and S217) executed by the third core network device 1033 in any of the above methods, which will not be repeated here.

[0510] In some embodiments, the communication device 1000 may be a fourth core network device 1034. In some embodiments, the processing module 1002 may be configured to determine the mapping of the multiplexed data stream of the first service to the QoS stream according to the second rule, wherein the second rule is used for traffic mapping of the multiplexed data stream. Optionally, the transceiver module 1001 may be configured to execute at least one of the communication steps such as sending and / or receiving (for example, steps S209, S211, S217) performed by the fourth core network device 1034 in any of the above methods, which will not be repeated here. Optionally, the processing module 1002 may be configured to execute at least one of the other steps (for example, step S210) other than the communication steps such as sending and / or receiving performed by the fourth core network device 1034 in any of the above methods, which will not be repeated here.

[0511] 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.

[0512] 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.

[0513] Figure 11A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. Communication device 11100 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 11100 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.

[0514] As shown in Figure 11A, the communication device 11100 includes one or more processors 11101. The processor 11101 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 11100 is used to perform any of the above methods. Optionally, one or more processors 11101 are used to call instructions to enable the communication device 11100 to perform any of the above methods.

[0515] In some embodiments, the communication device 11100 further includes one or more transceivers 11102. When the communication device 11100 includes one or more transceivers 11102, the transceiver 11102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S201, S203, S205, S206, S207, S208, S209, S211, S212, S213, S214, S215, S216, and S217, but not limited thereto), and the processor 11101 performs at least one of the other steps (e.g., steps S202, S204, and S210, 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. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be replaced with each other, terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be replaced with each other, and terms such as receiver, receiving unit, receiver, and receiving circuit can be replaced with each other.

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

[0517] The communication device 11100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 11100 described in the present disclosure is not limited thereto, and the structure of the communication device 11100 may not be limited to FIG. 11A. 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.

[0518] FIG11B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. If the communication device 11100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 11200 shown in FIG11B , but the present invention is not limited thereto.

[0519] The chip 11200 includes one or more processors 11201. The chip 11200 is configured to execute any of the above methods.

[0520] In some embodiments, chip 11200 further includes one or more interface circuits 11202. Alternatively, the terms interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 11200 further includes one or more memories 11203 for storing data. Alternatively, all or part of memory 11203 may be located external to chip 11200. Optionally, interface circuit 11202 is connected to memory 11203. Interface circuit 11202 may be configured to receive data from memory 11203 or other devices, or to send data to memory 11203 or other devices. For example, interface circuit 11202 may read data stored in memory 11203 and send the data to processor 11201.

[0521] In some embodiments, the interface circuit 11202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S201, S203, S205, S206, S207, S208, S209, S211, S212, S213, S214, S215, S216, and S217, but not limited thereto). The interface circuit 11202 performing the communication steps such as sending and / or receiving in the above method, for example, means that the interface circuit 11202 performs data exchange between the processor 11201, the chip 11200, the memory 11203, or the transceiver device. In some embodiments, the processor 11201 performs at least one of the other steps (e.g., steps S202, S204, and S210, but not limited thereto).

[0522] 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.

[0523] The embodiments of the present disclosure further provide a storage medium having instructions stored thereon. When the instructions are executed on the communication device 11100, the communication device 11100 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.

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

[0525] 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.

[0526] 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.

[0527] 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, which is executed by a first core network device, wherein, The method includes: Determine first information, where the first information is used to request determination of a first rule, and the first rule is used for traffic mapping of multiplexed data streams for a first service.

2. The method according to claim 1, wherein, The determination of the first information includes at least one of the following methods: Receive the first information sent by a second core network device; Receive the first information sent by a seventh core network device; Determine the first information based on operator operation and maintenance and management configurations; Determine the first information according to local configurations.

3. The method according to claim 1 or 2, wherein, The first information includes at least one of the following: An indication information, which is used to indicate whether to adopt multiplexed data streams; Requirement information, which is used to indicate mapping requirements of multiplexed data streams.

4. The method according to claim 3, wherein The requirement information includes at least one of the following: Mapping type; Mapping description; Mapping priority.

5. The method according to claim 4, wherein The mapping type includes at least one of the following: One-to-one mapping; One-to-many mapping; Many-to-one mapping; Many-to-many mapping.

6. The method according to claim 4 or 5, wherein The mapping description includes at least one of the following: Media type; Stream dependency; Channel dependency; Layer dependency; Synchronization dependency.

7. The method according to any one of claims 4 to 6, wherein The mapping priority includes at least one of the following: Mapping requirement priority; Mapping type priority; Mapping description priority.

8. The method according to any one of claims 1 to 7, wherein The method further includes: Send second information to a third core network device; Wherein, the second information includes at least one of the following: The first rule; An indication information, which is used to indicate whether to adopt multiplexed data streams; Requirement information, which is used to indicate mapping requirements of multiplexed data streams.

9. The method according to claim 8, wherein, The method further includes: Determine the first rule according to the indication information and / or the requirement information.

10. The method according to any one of claims 1 to 9, wherein The method further includes: Send the first information to a seventh core network device.

11. A communication method, which is executed by a second core network device, wherein, The method includes: Send first information to a first core network device, where the first information is used to request determination of a first rule, and the first rule is used for traffic mapping of multiplexed data streams for a first service.

12. The method according to claim 11, wherein, The first information includes at least one of the following: An indication information, which is used to indicate whether to adopt multiplexed data streams; Requirement information, which is used to indicate mapping requirements of multiplexed data streams.

13. The method according to claim 12, wherein, The requirement information includes at least one of the following: Mapping type; Mapping description; Mapping priority.

14. The method according to claim 13, wherein, The mapping type includes at least one of the following: One-to-one mapping; One-to-many mapping; Many-to-one mapping; Many-to-many mapping.

15. The method according to claim 13 or 14, wherein The mapping description includes at least one of the following: Media type; Stream dependency; Channel dependency; Layer dependency; Synchronization dependency.

16. The method according to any one of claims 13 to 15, wherein, The mapping priority includes at least one of the following: Mapping requirement priority; Mapping type priority; Mapping description priority.

17. A communication method, which is executed by a third core network device, wherein, The method includes: Receive second information sent by a first core network device, where the second information includes at least one of the following: A first rule, which is used for traffic mapping of multiplexed data streams for a first service; An indication information, which is used to indicate whether to adopt multiplexed data streams; Requirement information, which is used to indicate mapping requirements of multiplexed data streams.

18. The method according to claim 17, wherein The requirement information includes at least one of the following: Mapping type; Mapping description; Mapping priority.

19. The method according to claim 18, wherein, The mapping type includes at least one of the following: One-to-one mapping; One-to-many mapping; Many-to-one mapping; Many-to-many mapping.

20. The method according to claim 18 or 19, wherein The mapping description includes at least one of the following: Media type; Stream dependency; Channel dependency; Layer dependency; Synchronization dependency.

21. The method according to any one of claims 18 to 20, wherein, The mapping priority includes at least one of the following: The priority of the mapping requirement; The priority of the mapping type; The priority of the mapping description.

22. The method according to claim 17, wherein The determination of the first rule refers to at least one of the indication information and the requirement information.

23. The method according to any one of claims 17 to 22, wherein The method further includes: Sending third information to a fourth core network device, where the third information includes the second rule, and the second rule is used for traffic mapping of the multiplexed data stream of the first service.

24. The method according to claim 23, wherein, The second rule is determined by one of the following methods: Determined according to the first rule; Determined according to the indication information and / or the requirement information.

25. A communication method, which is executed by a fourth core network device, wherein, The method includes: Determining the mapping of the multiplexed data stream of the first service to a Quality of Service (QoS) flow according to the second rule, where the second rule is used for traffic mapping of the multiplexed data stream.

26. The method according to claim 25, wherein, The method further includes: Receiving third information sent by a third core network device, where the third information includes the second rule, and the second rule is used for traffic mapping of the multiplexed data stream of the first service.

27. The method according to claim 26, wherein, The second rule is locally configured.

28. A communication method, which is executed by a core network, wherein, The core network includes a first core network device and a third core network device; The method includes: The first core network device sends second information to the third core network device, where the second information includes at least one of the following: The first rule, which is used for traffic mapping of the multiplexed data stream of the first service; Indication information, which is used to indicate whether to adopt the multiplexed data stream; Requirement information, which is used to indicate the mapping requirement of the multiplexed data stream.

29. A first core network device, comprising: A transceiver module, configured to obtain first information, where the first information is used to request the determination of a first rule, and the first rule is used for traffic mapping of the multiplexed data stream of the first service.

30. A second core network device, comprising: A transceiver module, configured to send first information, where the first information is used to request the determination of a first rule, and the first rule is used for traffic mapping of the multiplexed data stream of the first service.

31. A third core network device, comprising: A transceiver module, configured to receive second information, where the second information includes at least one of the following: The first rule, where the first rule is used for traffic mapping of the multiplexed data stream of the first service; Indication information, which is used to indicate whether to adopt the multiplexed data stream; Requirement information, which is used to indicate the mapping requirement of the multiplexed data stream.

32. A fourth core network device, comprising: A processing module, configured to determine the mapping of the multiplexed data stream of the first service to a Quality of Service (QoS) flow according to the second rule, where the second rule is used for traffic mapping of the multiplexed data stream.

33. A communication device, comprising: One or more processors; A memory storing instructions; Wherein, when the instructions are executed by the communication device, the communication device implements the communication method according to any one of claims 1 to 10.

34. A communication device, comprising: One or more processors; A memory storing instructions; Wherein, when the instructions are executed by the communication device, the communication device implements the communication method according to any one of claims 11 to 16.

35. A communication device, comprising: One or more processors; A memory storing instructions; Wherein, when the instructions are executed by the communication device, the communication device implements the communication method according to any one of claims 17 to 24.

36. A communication device, comprising: One or more processors; A memory storing instructions; Wherein, when the instructions are executed by the communication device, the communication device implements the communication method according to any one of claims 25 to 27.

37. A communication device, comprising: One or more processors; A memory storing instructions; Wherein, when the instructions are executed by the communication device, the communication device implements the communication method according to claim 28.

38. A communication system, comprising: A first core network device, a second core network device; Wherein, the first core network device is used to implement the communication method according to any one of claims 1 to 10; The second core network device is used to implement the communication method according to any one of claims 11 to 16.

39. The communication system according to claim 38, wherein The communication system further comprises at least one of the following: a third core network device, a fourth core network device; The third core network device is used to implement the communication method according to any one of claims 17 to 24; The fourth core network device is used to implement the communication method according to any one of claims 25 to 27.

40. The communication system according to claim 38 or 39, wherein, The communication system further comprises at least one of the following: a fifth core network device, a sixth core network device, a seventh core network device; Wherein, the fifth core network device is used to send fourth information, and the fourth information is used to indicate QoS-related information; The sixth core network device is used to send the first information from the second core network device to the first core network device; The seventh core network device is used to send the first information to the first core network device.

41. A storage medium, the storage medium stores instructions, wherein, When the instructions run on the communication device, the communication device implements at least one of the following: The communication method according to any one of claims 1 to 10; The communication method according to any one of claims 11 to 16; The communication method according to any one of claims 17 to 24; The communication method according to any one of claims 25 to 27; The communication method according to claim 28.

Images