Communication method and apparatus, communication device, communication system, and storage medium

Abstract

The present disclosure relates to a communication method and apparatus, a communication device, a communication system, a storage medium, and a program product. The method is executed by a first network element. The method comprises: receiving first information, wherein the first information is used for indicating a function associated with DSCP marking, and the DSCP marking is associated with FEC characteristics. The solution of the present disclosure implements FEC characteristic-based DSCP marking.

Description

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

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

[0002] In communication technologies such as the 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 an increasing amount of 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 a specific service data flow (SDF) in a service.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure relate to a communication method and apparatus, communication equipment, a communication system, a storage medium, and a program product.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a first network element. The method includes: receiving first information, wherein the first information is used to indicate a function associated with a DSCP marking, and the DSCP marking is associated with a FEC characteristic.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a second network element. The method includes: receiving second information, wherein the second information is used to indicate implementation of a differential DSCP marking associated with an FEC feature.

[0008] According to a third aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a third network element. The method includes: sending first information, wherein the first information is used to indicate a function associated with a DSCP marking, and the DSCP marking is associated with a FEC characteristic.

[0009] According to a fourth aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a first device and includes: receiving third information, wherein the third information is used to determine a QoS configuration of the first device.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a communication device is provided. The device is disposed in a first network element. The device includes a transceiver module. The transceiver module is configured to receive first information, wherein the first information is used to indicate a function associated with a DSCP marking, where the DSCP marking is associated with a FEC feature.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a communication method is provided. The apparatus is provided in a second network element. The apparatus includes a transceiver module. The transceiver module is configured to receive second information, wherein the second information is used to indicate implementation of a DSCP marking associated with an FEC feature.

[0012] According to a seventh aspect of an embodiment of the present disclosure, a communication method is provided. The apparatus is provided in a third network element. The apparatus includes a transceiver module. The transceiver module is configured to: transmit first information, wherein the first information is used to indicate a function associated with a DSCP marking, where the DSCP marking is associated with a FEC feature.

[0013] According to an eighth aspect of an embodiment of the present disclosure, a communication method is provided. The apparatus is provided on a first device. The apparatus includes a transceiver module. The transceiver module is configured to receive third information, wherein the third information is used to determine a QoS configuration of the first device.

[0014] According to a ninth 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 any one of the first, second, third, and fourth aspects.

[0015] According to a tenth aspect of an embodiment of the present disclosure, a communication system is provided. The communication system includes: a first network element configured to implement the communication method described in the first aspect; a second network element configured to implement the communication method described in the second aspect; a third network element configured to implement the communication method described in the third aspect; and a first device configured to implement the communication method described in the fourth aspect.

[0016] According to an eleventh aspect of the present disclosure, a storage medium is provided. The storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the communication method described in any one of the first, second, third, and fourth aspects.

[0017] According to a twelfth aspect of the embodiments of the present disclosure, a program product is provided. When executed by a communication device, the program product causes the communication device to execute the communication method as described in any one of the first, second, third, and fourth aspects.

[0018] According to a thirteenth 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 as described in any one of the first, second, third, and fourth aspects.

[0019] According to a fourteenth aspect of the present disclosure, a chip or chip system is provided. The chip or chip system includes a processing circuit. The processing circuit is configured to execute the communication method described in any one of the first, second, third, and fourth aspects.

[0020] According to the embodiment of the present disclosure, DSCP marking of data packets in a data stream can be implemented based on the FEC mechanism.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0040] In a first aspect, an embodiment of the present disclosure provides a communication method. The method is performed by a first network element. The method includes: receiving first information, wherein the first information is used to indicate a function associated with a DSCP marking, and the DSCP marking is associated with a FEC characteristic.

[0041] In this embodiment, the first information can indicate the DSCP marking associated with the FEC characteristics. This enables the network device to take the FEC characteristics into account when performing DSCP marking on packets in the data flow. In this way, corresponding DSCP marking values ​​can be added to packets based on their FEC characteristics, thereby achieving more refined QoS processing.

[0042] In combination with some embodiments of the first aspect, in some embodiments, the first information may include at least one of the following information related to FEC characteristics: type information, used to indicate the FEC type; redundancy rate information, used to indicate the FEC redundancy rate; ratio information, used to indicate the FEC ratio; first priority information, used to indicate the priority of the data packet; second priority information, used to indicate the priority of the SDF; first mapping information, used to indicate the mapping relationship between the data packet and the PDU set; second mapping information, used to indicate the mapping relationship between the SDF and the QoS flow.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the FEC characteristics may include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; priority of data packets; priority of SDF; mapping relationship between data packets and PDU sets; mapping relationship between SDF and QoS flows.

[0044] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: sending first information.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the operation of sending the first information may include: sending second information to the second network element, wherein the second information is used to implement a DSCP marking associated with the FEC feature.

[0046] In combination with some embodiments of the first aspect, in some embodiments, the second information may include at least one of the following: first information; DSCP marking value.

[0047] In combination with some embodiments of the first aspect, in some embodiments, the operation of sending the first information may include: sending third information to the first device, wherein the third information is used to determine the QoS configuration of the first device.

[0048] In combination with some embodiments of the first aspect, in some embodiments, the third information may include at least one of the following: the first information; a DSCP indication or DSCP information.

[0049] In a second aspect, an embodiment of the present disclosure provides a communication method. The method is performed by a second network element. The method includes: receiving second information, wherein the second information is used to indicate implementation of a DSCP marking associated with an FEC feature.

[0050] In this embodiment, the second information can indicate the DSCP marking associated with the FEC characteristics. This enables the network device to take the FEC characteristics into account when performing DSCP marking on packets in the data flow. This allows the corresponding DSCP marking value to be added to the packet based on the FEC characteristics of the packet, thereby achieving more refined QoS processing.

[0051] In combination with some embodiments of the second aspect, in some embodiments, the second information may include at least one of the following: first information; DSCP marking value.

[0052] In combination with some embodiments of the second aspect, in some embodiments, the first information may include at least one of the following information related to FEC characteristics: type information, used to indicate the FEC type; redundancy rate information, used to indicate the FEC redundancy rate; ratio information, used to indicate the FEC ratio; first priority information, used to indicate the priority of the data packet; second priority information, used to indicate the priority of the SDF; first mapping information, used to indicate the mapping relationship between the data packet and the PDU set; second mapping information, used to indicate the mapping relationship between the SDF and the QoS flow.

[0053] In combination with some embodiments of the second aspect, in some embodiments, the FEC characteristics may include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; priority of data packets; priority of SDF; mapping relationship between data packets and PDU sets; mapping relationship between SDF and QoS flows.

[0054] In combination with some embodiments of the second aspect, in some embodiments, the second information may include only the first information; wherein the above method may further include: determining a DSCP marking value based on the first information.

[0055] In combination with some embodiments of the second aspect, in some embodiments, the above method may further include: performing DSCP marking according to the second information.

[0056] In a third aspect, embodiments of the present disclosure provide a communication method. The method is performed by a third network element. The method includes: sending first information, wherein the first information is used to indicate a function associated with a DSCP marking, and the DSCP marking is associated with an FEC feature.

[0057] In this embodiment, the first information can indicate the DSCP marking associated with the FEC characteristics. This enables the network device to take the FEC characteristics into account when performing DSCP marking on packets in the data flow. In this way, corresponding DSCP marking values ​​can be added to packets based on their FEC characteristics, thereby achieving more refined QoS processing.

[0058] In combination with some embodiments of the third aspect, in some embodiments, the first information may include at least one of the following information related to FEC characteristics: type information, used to indicate the FEC type; redundancy rate information, used to indicate the FEC redundancy rate; ratio information, used to indicate the FEC ratio; first priority information, used to indicate the priority of the data packet; second priority information, used to indicate the priority of the SDF; first mapping information, used to indicate the mapping relationship between the data packet and the PDU set; second mapping information, used to indicate the mapping relationship between the SDF and the QoS flow.

[0059] In combination with some embodiments of the third aspect, in some embodiments, the FEC characteristics may include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; priority of data packets; priority of SDF; mapping relationship between data packets and PDU sets; mapping relationship between SDF and QoS flows.

[0060] In a fourth aspect, embodiments of the present disclosure provide a communication method, performed by a first device, comprising: receiving third information, wherein the third information is used to determine a QoS configuration of the first device.

[0061] In combination with some embodiments of the fourth aspect, in some embodiments, the third information may include at least one of the following: first information; DSCP indication or DSCP information.

[0062] In combination with some embodiments of the fourth aspect, in some embodiments, the first information may include at least one of the following information related to FEC characteristics: type information, used to indicate the FEC type; redundancy rate information, used to indicate the FEC redundancy rate; ratio information, used to indicate the FEC ratio; first priority information, used to indicate the priority of the data packet; second priority information, used to indicate the priority of the SDF; first mapping information, used to indicate the mapping relationship between the data packet and the PDU set; second mapping information, used to indicate the mapping relationship between the SDF and the QoS flow.

[0063] In combination with some embodiments of the fourth aspect, in some embodiments, the FEC characteristics may include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; priority of data packets; priority of SDF; mapping relationship between data packets and PDU sets; mapping relationship between SDF and QoS flows.

[0064] In combination with some embodiments of the fourth aspect, in some embodiments, the third information may only include the first information; wherein the above method may further include: determining the DSCP indication or DSCP information based on the first information.

[0065] In combination with some embodiments of the fourth aspect, in some embodiments, the above method may further include: determining QoS configuration based on the third information.

[0066] In a fifth aspect, embodiments of the present disclosure provide a communications device. The device is disposed in a first network element. The device includes a transceiver module. The transceiver module is configured to receive first information, wherein the first information indicates a function associated with a DSCP marking, where the DSCP marking is associated with a FEC feature.

[0067] In combination with some embodiments of the fifth aspect, in some embodiments, the first information may include at least one of the following information related to FEC characteristics: type information, used to indicate the FEC type; redundancy rate information, used to indicate the FEC redundancy rate; ratio information, used to indicate the FEC ratio; first priority information, used to indicate the priority of the data packet; second priority information, used to indicate the priority of the SDF; first mapping information, used to indicate the mapping relationship between the data packet and the PDU set; second mapping information, used to indicate the mapping relationship between the SDF and the QoS flow.

[0068] In combination with some embodiments of the fifth aspect, in some embodiments, the FEC characteristics may include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; priority of data packets; priority of SDF; mapping relationship between data packets and PDU sets; mapping relationship between SDF and QoS flows.

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

[0070] In combination with some embodiments of the fifth aspect, in some embodiments, the transceiver module can be configured to: send second information to the second network element, wherein the second information is used to implement a DSCP marking associated with the FEC feature.

[0071] In combination with some embodiments of the fifth aspect, in some embodiments, the second information may include at least one of the following: first information; DSCP marking value.

[0072] In combination with some embodiments of the fifth aspect, in some embodiments, the transceiver module can be configured to: send third information to the first device, wherein the third information is used to determine the QoS configuration of the first device.

[0073] In combination with some embodiments of the fifth aspect, in some embodiments, the third information may include at least one of the following: first information; DSCP indication or DSCP information.

[0074] In a sixth aspect, embodiments of the present disclosure provide a communication device. The device is disposed in a second network element. The device includes a transceiver module configured to receive second information, wherein the second information is used to indicate implementation of a DSCP marking associated with an FEC feature.

[0075] In combination with some embodiments of the sixth aspect, in some embodiments, the second information may include at least one of the following: first information; DSCP marking value.

[0076] In combination with some embodiments of the sixth aspect, in some embodiments, the first information may include at least one of the following information related to FEC characteristics: type information, used to indicate the FEC type; redundancy rate information, used to indicate the FEC redundancy rate; ratio information, used to indicate the FEC ratio; first priority information, used to indicate the priority of the data packet; second priority information, used to indicate the priority of the SDF; first mapping information, used to indicate the mapping relationship between the data packet and the PDU set; second mapping information, used to indicate the mapping relationship between the SDF and the QoS flow.

[0077] In combination with some embodiments of the sixth aspect, in some embodiments, the FEC characteristics may include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; priority of data packets; priority of SDF; mapping relationship between data packets and PDU sets; mapping relationship between SDF and QoS flows.

[0078] In conjunction with some embodiments of the sixth aspect, in some embodiments, the second information may include only the first information. The apparatus may further include a processing module. The processing module is configured to: determine a DSCP marking value based on the first information.

[0079] In combination with some embodiments of the sixth aspect, in some embodiments, the processing module can be configured to: perform DSCP marking according to the second information.

[0080] In a seventh aspect, embodiments of the present disclosure provide a communications device. The device is disposed in a third network element. The device includes a transceiver module configured to transmit first information, wherein the first information indicates a function associated with a DSCP marking, where the DSCP marking is associated with a FEC feature.

[0081] In combination with some embodiments of the seventh aspect, in some embodiments, the first information may include at least one of the following information related to FEC characteristics: type information, used to indicate the FEC type; redundancy rate information, used to indicate the FEC redundancy rate; ratio information, used to indicate the FEC ratio; first priority information, used to indicate the priority of the data packet; second priority information, used to indicate the priority of the SDF; first mapping information, used to indicate the mapping relationship between the data packet and the PDU set; second mapping information, used to indicate the mapping relationship between the SDF and the QoS flow.

[0082] In combination with some embodiments of the seventh aspect, in some embodiments, the FEC characteristics may include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; priority of data packets; priority of SDF; mapping relationship between data packets and PDU sets; mapping relationship between SDF and QoS flows.

[0083] In an eighth aspect, an embodiment of the present disclosure provides a communication apparatus. The apparatus is provided on a first device. The apparatus includes a transceiver module configured to receive third information, wherein the third information is used to determine a QoS configuration of the first device.

[0084] In combination with some embodiments of the eighth aspect, in some embodiments, the third information may include at least one of the following: first information; DSCP indication or DSCP information.

[0085] In combination with some embodiments of the eighth aspect, in some embodiments, the first information may include at least one of the following information related to FEC characteristics: type information, used to indicate the FEC type; redundancy rate information, used to indicate the FEC redundancy rate; ratio information, used to indicate the FEC ratio; first priority information, used to indicate the priority of the data packet; second priority information, used to indicate the priority of the SDF; first mapping information, used to indicate the mapping relationship between the data packet and the PDU set; second mapping information, used to indicate the mapping relationship between the SDF and the QoS flow.

[0086] In combination with some embodiments of the eighth aspect, in some embodiments, the FEC characteristics may include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; priority of data packets; priority of SDF; mapping relationship between data packets and PDU sets; mapping relationship between SDF and QoS flows.

[0087] In conjunction with some embodiments of the eighth aspect, in some embodiments, the third information may include only the first information. The apparatus may further include a processing module. The processing module is configured to: determine a DSCP indication or DSCP information based on the first information.

[0088] In combination with some embodiments of the eighth aspect, in some embodiments, the processing module can be configured to: determine the QoS configuration based on the third information.

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

[0090] 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 second aspect and possible embodiments thereof.

[0091] 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 third aspect and possible embodiments thereof.

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

[0093] In a thirteenth aspect, embodiments of the present disclosure provide a communication system. The communication system includes: a first network element configured to implement the communication method described in the first aspect; a second network element configured to implement the communication method described in the second aspect; a third network element configured to implement the communication method described in the third aspect; and a first device configured to implement the communication method described in the fourth aspect.

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

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

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

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

[0098] It is understandable that the above-mentioned communication devices, communication equipment, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to perform the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0121] 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 , a first device 102 , and a core network 103 .

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

[0123] In some embodiments, the first device 102 may be an access network device.

[0124] In some embodiments, the access network device 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.

[0125] In some embodiments, the first device 102 may be a wireless access network device. In some embodiments, the first device 102 may be an access network device that uses other communication technologies. For example, the first device 102 may be N3IWF, TNGF, or W-AGF.

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

[0127] In some embodiments, the first 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.

[0128] In some embodiments, the core network 103 may be a device including a second network element 1032, a third network element 1033, a fourth network element 1034, a fifth network element 1035, a sixth network element 1036, a seventh network element 1037, etc., or may be multiple devices or a device group including all or part of the second network element 1032, the third network element 1033, the fourth network element 1034, the fifth network element 1035, the sixth network element 1036, the seventh network element 1037, etc. The network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0129] In some embodiments, the first network element may include, for example, a fourth network element 1034 and / or a fifth network element 1035 .

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

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

[0132] In some embodiments, the third network element 1033 may be, for example, an application function (AF).

[0133] In some embodiments, the third network element 1033 may be implemented by an application server and used to provide application services, but the name is not limited thereto.

[0134] In some embodiments, the fourth network element 1034 may be, for example, a session management function (SMF).

[0135] In some embodiments, the fourth network element 1034 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.

[0136] In some embodiments, the fifth network element 1035 may be, for example, a policy control function (PCF).

[0137] In some embodiments, the fifth network element 1035 can be used to support a unified policy framework and provide policy rules, but the name is not limited thereto.

[0138] In some embodiments, the sixth network element 1036 may be, for example, an access and mobility management function (AMF).

[0139] In some embodiments, the sixth network element 1036 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.

[0140] In some embodiments, the seventh network element 1037 may be, for example, a network exposure function (NEF).

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

[0142] In some embodiments, the third network element 1033 may be located outside the core network 103 or may be located inside the core network 103, and this embodiment of the present disclosure does not specifically limit this.

[0143] In some embodiments, the third network element 1033 and the fifth network element 1035 may be deployed centrally or independently, and this embodiment of the present disclosure does not specifically limit this.

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

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

[0146] Figure 1B is an architectural diagram of an implementation method of a communication system provided 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. N1 is a reference point between the UE and the AMF. N2 is a reference point between the RAN and the AMF. N3 is a reference point between the RAN and the UPF. N4 is a reference point between the SMF and the UPF. N5 is a reference point between the PCF and the AF. N6 is a reference point between the UPF and the data network (DN). N7 is a reference point between the SMF and the PCF. N11 is a reference point between the AMF and the SMF. N15 is a reference point between the SMF and the PCF. Uu is the interface between the UE and the RAN. It should be noted that the NEF is not shown in Figure 1B. However, each network element in the communication system can interact with the NEF.

[0147] 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 1B, the architecture of the 5G communication system is presented in the form of service-based interfaces. Namf is a service-based interface provided by the AMF. Nsmf is a service-based interface provided by the SMF. Nnef is a service-based interface provided by the NEF. Npcf is a service-based interface provided by the PCF. Naf is a service-based interface provided by the AF.

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

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

[0150] 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).

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

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

[0153] 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).

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

[0155] In some embodiments, the PDU set information may include at least one of the following: a PDU set sequence number, a start PDU or end PDU of the PDU set, a PDU sequence number within the PDU set, the number of PDUs within the 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.

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

[0157] In some embodiments, to enhance transport layer resource optimization for XRM services, FEC characteristics may be considered during transport layer resource scheduling and configuration. In some embodiments, FEC characteristic information may be considered during implementation of differentiated service code point (DSCP) marking related functions.

[0158] 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 S212.

[0159] In step S201 , the third network element 1033 sends first information to the seventh network element 1037 .

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

[0161] In some embodiments, the first information may be used to indicate a function associated with a DSCP mark, where the DSCP mark is associated with a forward error correction (FEC) feature.

[0162] In some embodiments, the first information may be used to implement DSCP marking associated with the FEC.

[0163] In some embodiments, the name of the first information is not limited, and it can be, for example, FEC characteristic information, DSCP mapping information, etc.

[0164] In some embodiments, DSCP can be used to implement the priority of data packets, PDUs, and PDU sets. In one example, DSCP can include at least one bit. By encoding this at least one bit, it is possible to distinguish between multiple priorities. In some embodiments, DSCP can include 8 bits. In this case, DSCP can have a total of 2 8 Priority.

[0165] In some embodiments, DSCP marking may refer to the operation of prioritizing data packets, PDUs, PDU sets, etc. using DSCP. Specifically, DSCP marking may include adding a DSCP marking value to a data packet, PDU, PDU set, etc. The DSCP marking value may be used to indicate the priority of the corresponding data packet, PDU, PDU set, etc.

[0166] In some embodiments, the first information may be used to indicate an FEC characteristic associated with the DSCP marking.

[0167] In some embodiments, the FEC characteristics may include at least one of the following: FEC type, FEC redundancy rate, FEC ratio, data packet priority, SDF priority, mapping relationship between data packets and PDU sets, and mapping relationship between SDF and QoS flows.

[0168] In some embodiments, the first information may include at least one of the following: type information, redundancy rate information, ratio information, first priority information, second priority information, first mapping information, and second mapping information.

[0169] In some embodiments, the type information may be used to indicate the FEC type. In some embodiments, the type information may be used to indicate supported FEC types.

[0170] In some embodiments, the FEC type may be the type of FEC scheme employed.

[0171] In some embodiments, the FEC type may include: maximum distance separable (MDS) FEC, flexible FEC (flex FEC), uneven level protection (ULP) FEC, and application layer FEC (AL FEC).

[0172] In some embodiments, the MDS FEC type FEC may use one or more coding types. In one example, the MDS FEC type FEC may use Reed-Solomon codes (RS codes).

[0173] In some embodiments, the FEC type of the FEC may enable the receiver to recover k source symbols from any set of k received symbols, where k may be any positive integer.

[0174] In some embodiments, the redundancy rate information may be used to indicate an FEC redundancy rate. In some embodiments, the redundancy rate information may be used to indicate supported FEC redundancy rates. In one example, an MDS-type FEC may have a corresponding FEC redundancy rate. In another example, an ULP-type FEC may have a corresponding FEC redundancy rate. In some embodiments, the redundancy rate information may include the FEC redundancy rate corresponding to an MDS-type FEC. In some embodiments, the redundancy rate information may include the FEC redundancy rate corresponding to an ULP-type FEC.

[0175] In some embodiments, the redundancy rate information may be adapted to indicate the FEC redundancy rate in a scenario where the redundancy rate is determined. In some embodiments, the redundancy rate information may be adapted to indicate the determined FEC redundancy rate.

[0176] In some embodiments, the redundancy rate information may be used to indicate the FEC redundancy rate in a scenario where the redundancy rate is variable. In some embodiments, the redundancy rate information may be used to indicate a variable FEC redundancy rate.

[0177] In some embodiments, the redundancy rate information may statically indicate the FEC redundancy rate. In one example, the redundancy rate information in the first information may indicate the FEC redundancy rate via the control plane. In some embodiments, the FEC redundancy rate indicated by the redundancy rate information may be applicable to scenarios where the redundancy rate is variable as well as scenarios where the redundancy rate is fixed. In one example, the redundancy rate information may preferably indicate a fixed FEC redundancy rate via the control plane. For example, the FEC redundancy rate may be referred to as a "static redundancy rate."

[0178] In some embodiments, the redundancy rate information may dynamically indicate the FEC redundancy rate. In one example, the redundancy rate information may indicate the FEC redundancy rate via the user plane. In some embodiments, the FEC redundancy rate indicated by the redundancy rate information may be applicable to scenarios where the redundancy rate is variable as well as scenarios where the redundancy rate is fixed. In one example, the redundancy rate information may preferably indicate a variable FEC redundancy rate via the user plane. For example, the FEC redundancy rate may be referred to as a "dynamic redundancy rate."

[0179] In some embodiments, the FEC redundancy rate may range from 0 to 100%. In some embodiments, the larger the FEC redundancy rate, the greater the proportion of redundant information used to ensure data correctness.

[0180] In some embodiments, the ratio information may be used to indicate the FEC ratio. In some embodiments, the ratio information may be used to indicate the supported FEC ratio.

[0181] In some embodiments, the FEC ratio may be used to indicate the ratio of the SDF corresponding to the FEC redundancy rate to the total SDF.

[0182] In some embodiments, in the case of multiple SDFs, different portions of the SDFs may correspond to different FEC redundancy rates. In one example, a portion of the multiple SDFs may correspond to a higher FEC redundancy rate, such as 50%, while another portion may correspond to a lower FEC redundancy rate, such as 10%. In another example, the FEC ratio may be such that half of the SDFs correspond to a 50% FEC redundancy rate, and the other half correspond to a 10% FEC redundancy rate.

[0183] In some embodiments, for multiple SDFs, a certain number of redundant SDFs may be distributed across different portions of the multiple SDFs. In one example, the multiple SDFs may include a certain number of redundant SDFs. In one example, 30% of the redundant SDFs may be located in half of the multiple SDFs, and 70% of the redundant SDFs may be located in the other half of the multiple SDFs.

[0184] In some embodiments, the first priority information may be used to indicate the priority of the data packet.

[0185] In some embodiments, the first priority information may be used to indicate the priority of the source data packet and / or the redundant data packet. In some embodiments, the priority of the data packet may include the priority of the source data packet and / or the priority of the redundant data packet.

[0186] In some embodiments, the priority of the data packet may be an absolute priority.

[0187] In some embodiments, the priority of a data packet may be a relative priority. In one example, the priority of a data packet may include a priority relationship between a source data packet and a redundant data packet. In some embodiments, the priority relationship between the source data packet and the redundant data packet may include at least one of the following: the priority of the source data packet is higher than the priority of the redundant data packet; the priority of the source data packet is equal to the priority of the redundant data packet; the priority of the source data packet is lower than the priority of the redundant data packet; the priority of the source data packet is not lower than the priority of the redundant data packet; or the priority of the source data packet is not higher than the priority of the redundant data packet.

[0188] In some embodiments, the second priority information may be used to indicate the priority of the SDF.

[0189] In some embodiments, the second priority information may be used to indicate the priority of an SDF including redundant data packets. In one example, an SDF including redundant data packets may have a high priority. In one example, an SDF including redundant data packets may have a higher priority than an SDF not including redundant data packets.

[0190] In some embodiments, the second priority information may be used to indicate the priority of an SDF that includes only redundant data packets. In one example, an SDF that includes only redundant data packets may have a high priority. In another example, an SDF that includes only redundant data packets may have a higher priority than an SDF that partially includes or does not include redundant data packets.

[0191] In some embodiments, the priority may correspond to a DSCP marking value. In one example, a packet and / or SDF with a higher priority may correspond to a DSCP marking value corresponding to the higher priority. In another example, a packet and / or SDF with a lower priority may correspond to a DSCP marking value corresponding to the lower priority.

[0192] In some embodiments, the first mapping information may be used to indicate a mapping relationship between a data packet and a PDU set.

[0193] In some embodiments, the mapping relationship between the data packet and the PDU set may include a mapping relationship between the data packet using FEC and the PDU set.

[0194] In some embodiments, the second mapping information may be used to indicate a mapping relationship between an SDF and a QoS flow. In some embodiments, the second mapping information may be used to indicate a mapping relationship between an SDF and a QoS flow using an FEC mechanism.

[0195] In some embodiments, multiple SDFs using the FEC mechanism may be grouped, and the SDFs in the same group may correspond to the same or similar DSCP marking values.

[0196] In some embodiments, in one or more SDFs employing the FEC mechanism, source SDFs may be grouped together and redundant SDFs may be grouped together. In some embodiments, the source SDFs may be SDFs containing source data packets. In some embodiments, the redundant SDFs may be SDFs containing redundant data packets.

[0197] In some embodiments, dependencies between different SDFs may be considered in DSCP marking.

[0198] In some embodiments, at least one source SDF and at least one redundant SDF may have a dependency relationship. In some embodiments, at least one source SDF and at least one redundant SDF may be related. In this case, the source SDF and the redundant SDF may have the same or similar DSCP marking values.

[0199] In some embodiments, the source SDF and the redundant SDF having a dependency relationship may be mapped to the same QoS flow. In some embodiments, the same QoS flow to which the source SDF and the redundant SDF having a dependency relationship are mapped may have the same QFI.

[0200] In some embodiments, the source SDF and the redundant SDF having a dependency relationship may be mapped to different QoS flows. In some embodiments, the different QoS flows to which the source SDF and the redundant SDF having a dependency relationship are mapped may have different QFIs.

[0201] In some embodiments, the first information may be carried in an AF request.

[0202] In some embodiments, the third network element 1033 may send an AF session resource request to the seventh network element 1037. The AF session resource request may carry the first information.

[0203] In some embodiments, the AF session resource request may be a Nnef_AFsessionWithQoS_Create request message.

[0204] In some embodiments, the AF session resource request may be a Nnef_AFsessionWithQoS_Update request message.

[0205] In some embodiments, the AF session resource request may also include at least one of the following: an identifier of the first service, an address and / or identifier of the terminal 101, an identifier of the third network element 1033, an application identifier of the first service, a flow description, a data network name (DNN), single network slice selection assistance information (S-NSSAI), and QoS parameters.

[0206] In some embodiments, the identifier of the first service may be used to identify a data stream or data stream group of the first service. In some embodiments, the identifier of the first service may be a multimodal service identifier, and the multimodal service identifier may be used to identify all data streams in the service group. In some embodiments, the data stream or data stream group of the first service may be a service data stream or service data stream group.

[0207] In some embodiments, the first service may be an XRM service.

[0208] In step S202, the seventh network element 1037 performs authorization.

[0209] In some embodiments, the seventh network element 1037 may authorize the AF request.

[0210] In some embodiments, the third network element 1033 may be a non-trusted network element. In this case, the seventh network element 1037 may authorize the AF request from the third network element 1033.

[0211] In some embodiments, the third network element 1033 may be a trusted network element. In this case, the seventh network element 1037 may not need to authorize the AF request from the third network element 1033. Step S202 may be omitted.

[0212] In step S203 , the seventh network element 1037 sends the first information to the fifth network element 1035 .

[0213] In some embodiments, the fifth network element 1035 may receive the first information.

[0214] In some embodiments, the seventh network element 1037 may send the first information in different ways. In some embodiments, the seventh network element 1037 may determine the way to send the first information based on information and / or parameters received from the third network element 1033.

[0215] In some embodiments, the manner in which the seventh network element 1037 sends the first information may include: sending through a time sensitive communication and time synchronization function (TSCTSF) or sending directly.

[0216] In some embodiments, the seventh network element 1037 may determine to send the first information to the fifth network element 1035 via the TSCTSF. In some embodiments, the seventh network element 1037 may send the fourth information to the TSCTSF via the service-based interface Ntsftsf, and then the TSCTSF may send the first information to the fifth network element 1035 via the service-based interface Npcf. In one example, the seventh network element 1037 may send the first information to the TSCTSF via an Ntsctsf_QoSandTSCAssistance_Create request message, and then the TSCTSF may send the first information to the fifth network element 1035 via an Npcf_PolicyAuthorization_Create request message or an Npcf_PolicyAuthorization_Update request message.

[0217] In some embodiments, the seventh network element 1037 may determine to send the first information directly to the fifth network element 1035. In some embodiments, the seventh network element 1037 may send the first information to the fifth network element 1035 via a service-based interface Npcf. In one example, the seventh network element 1037 may send the first information to the fifth network element 1035 via an Npcf_PolicyAuthorization_Create request message.

[0218] In step S204 , the fifth network element 1035 performs policy decision making.

[0219] In some embodiments, the fifth network element 1035 may perform a policy decision after receiving the first information.

[0220] In some embodiments, the fifth network element 1035 may determine the first rule through policy decision-making.

[0221] In some embodiments, the first rule may be determined by the fifth network element 1035 after considering the first information.

[0222] In some embodiments, the first rule may include a policy and charging control (PCC) rule.

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

[0224] In some embodiments, the first rule may be updated. In some embodiments, based on the first information, the first network element may determine to update the existing first rule.

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

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

[0227] In step S205 , the fifth network element 1035 sends the first information to the fourth network element 1034 .

[0228] In some embodiments, the fourth network element 1034 may receive the first information.

[0229] In some embodiments, the first information may be carried in a first rule. In some embodiments, the fifth network element 1035 may send the first rule to the fourth network element 1034. The first rule may include the first information.

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

[0231] In some embodiments, the fifth network element 1035 may initiate an SM Policy Association Modification procedure to send the first information.

[0232] In some embodiments, the first information may be carried in an Npcf_SMPolicyControl_UpdateNotify request message.

[0233] In step S206 , the fourth network element 1034 sends the second information to the second network element 1032 .

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

[0235] In some embodiments, the second information may be used to implement DSCP marking associated with the FEC characteristic.

[0236] In some embodiments, the second information may be used to instruct the second network element 1032 to perform DSCP marking associated with the FEC feature.

[0237] In some embodiments, the second information may be used to enhance QoS processing of the second network element 1032 .

[0238] In some embodiments, the name of the second information is not limited, and it can be, for example, marking information, DSCP marking information, etc.

[0239] In some embodiments, the second information may include at least one of the following: the first information, a DSCP marking value.

[0240] In some embodiments, by sending the first information to the second network element 1032 , the second network element 1032 may be instructed to perform DSCP marking associated with the FEC feature.

[0241] In some embodiments, the DSCP marking value may be a DSCP marking value for a QoS flow.

[0242] In some embodiments, the DSCP marking value may be a DSCP marking value of a data packet of a transport level determined for each QoS flow.

[0243] In some embodiments, the DSCP marking value can be determined by the fourth network element 1034 based on at least one of the following: the first information, 5QI (5G QoS Identifier), the priority of the QoS flow, and the ARP (allocation and retention priority) of the QoS flow.

[0244] In some embodiments, after receiving the first rule, the fourth network element 1034 may determine a second rule. The second rule may be used by the second network element 1032 to perform QoS processing.

[0245] In some embodiments, the second information may be included in the second rule and sent.

[0246] In some embodiments, the second rule may include at least one of the following: a QoS rule, a QoS set parameter.

[0247] In some embodiments, the second network element 1032 may determine the QoS parameters of the QoS flow based on rule information in a second rule bound to the QoS flow. In one example, the second network element 1032 may determine the QoS parameters of the QoS flow based on PCC rule information in a PCC rule bound to the QoS flow.

[0248] In some embodiments, the third network element 1033 may send the second information through an N4 session.

[0249] In some embodiments, the second information may be carried in an N4 Session Modification request message.

[0250] In step S207 , the fourth network element 1034 sends third information to the sixth network element 1036 .

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

[0252] In some embodiments, the third information may be used to determine a QoS profile of the first device 102 .

[0253] In some embodiments, the third information can be used to enhance QoS processing of the first device 102.

[0254] In some embodiments, the name of the third information is not limited, and it can be, for example, QoS configuration indication information, QoS processing indication information, etc.

[0255] In some embodiments, the third information may include at least one of the following: the first information, a DSCP indication, or DSCP information.

[0256] In some embodiments, DSCP indication or DSCP information may be used to indicate information related to DSCP.

[0257] In some embodiments, a DSCP indication or DSCP information may be used to indicate a DSCP corresponding to a QoS configuration.

[0258] In some embodiments, the DSCP indication or DSCP information may take into account the following information: FEC characteristic information, and / or PDU set information and related QoS information for data resource transmission.

[0259] In some embodiments, the DSCP indication or DSCP information may be associated with FEC characteristic information, and / or PDU set information and related QoS information for data resource transmission.

[0260] In some embodiments, after receiving the first rule, the fourth network element 1034 may determine a third rule. The third rule may be used for the first device 102 and / or the terminal 101 to perform QoS processing.

[0261] In some embodiments, the third information may be included in a third rule and sent.

[0262] In some embodiments, the fourth network element 1034 may send the third information via the service-based interface Namf.

[0263] In some embodiments, the third information may be sent to the sixth network element 1036 via the Namf_Communication_N1N2MessageTransfer process.

[0264] In step S208 , the sixth network element 1036 sends third information to the first device 102 .

[0265] In some embodiments, the first device 102 may receive third information.

[0266] In some embodiments, the sixth network element 1036 may send the third information via an N2 message.

[0267] In step S209 , the first device 102 determines a QoS configuration.

[0268] In some embodiments, the first device 102 may receive the first information in the third information, and / or the DSCP indication or the DSCP information.

[0269] In some embodiments, the first device 102 may determine a QoS configuration based on the third information. In one example, the first device 102 may generate a QoS configuration based on the third information. In one example, the first device 102 may modify the QoS configuration based on the third information.

[0270] In some embodiments, the first device 102 may determine a QoS configuration based on the third information and the third rule. In one example, the first device 102 may generate a QoS configuration based on the third information and the third rule. In one example, the first device 102 may modify the QoS configuration based on the third information and the third rule.

[0271] In step S210 , the second network element 1032 performs DSCP marking.

[0272] In some embodiments, the second network element 1032 may perform DSCP marking according to the second information.

[0273] In some embodiments, the second network element 1032 may perform DSCP marking on the data flow of the first service according to the second information.

[0274] In some embodiments, the second network element 1032 may perform DSCP marking on the header of the downlink data packet in the PDU set of the first service according to the second information.

[0275] In some embodiments, the second network element 1032 may perform DSCP marking by adding a DSCP marking value to the header of the downlink data packet in the PDU set.

[0276] In some embodiments, the second network element 1032 may perform DSCP marking on data packets carrying FEC characteristic information.

[0277] In some embodiments, the second network element 1032 may add a corresponding DSCP marking value to the data packet carrying the FEC characteristic information according to the first information included in the second information.

[0278] In some embodiments, when the second information includes a DSCP marking value, the second network element 1032 may implement DSCP marking based on the received DSCP marking value.

[0279] In some embodiments, if the second information does not include a DSCP marking value, the second network element 1032 may determine the DSCP marking value. In some embodiments, the second network element 1032 may determine the DSCP marking value based on at least one of the following: the first information, 5QI, the priority of the QoS flow, and the ARP of the QoS flow.

[0280] In some embodiments, on the user plane, the second network element 1032 may receive the data flow of the first service, perform DSCP marking on the downlink data packets in the data flow, and send the data flow with the added DSCP marking value to the first device 102 .

[0281] In step S211 , the first device 102 sends fourth information to the terminal 101 .

[0282] In some embodiments, terminal 101 may receive fourth information.

[0283] In some embodiments, the fourth information may be used to implement DSCP marking associated with the FEC characteristic.

[0284] In some embodiments, the fourth information may be used to instruct the terminal 101 to perform DSCP marking associated with the FEC feature.

[0285] In some embodiments, the fourth information may be used to enhance QoS processing of terminal 101 .

[0286] In some embodiments, the name of the fourth information is not limited, and it can be, for example, marking information, DSCP marking information, etc.

[0287] In some embodiments, the fourth information may include at least one of the following: the first information, a DSCP marking value.

[0288] In some embodiments, by sending the first information to the terminal 101 , the terminal 101 may be instructed to perform DSCP marking associated with the FEC feature.

[0289] In step S212 , the terminal 101 performs DSCP marking.

[0290] In some embodiments, terminal 101 may perform DSCP marking according to the fourth information.

[0291] In some embodiments, the terminal 101 may perform DSCP marking on the data flow of the first service according to the fourth information.

[0292] In some embodiments, the terminal 101 may perform DSCP marking on the header of the uplink data packet in the PDU set of the first service according to the fourth information.

[0293] In some embodiments, the terminal 101 may perform DSCP marking by adding a DSCP marking value to the header of the uplink data packet in the PDU set.

[0294] In some embodiments, the terminal 101 may perform DSCP marking on data packets carrying FEC characteristic information.

[0295] In some embodiments, the terminal 101 may add a corresponding DSCP marking value to the data packet carrying the FEC characteristic information according to the first information included in the fourth information.

[0296] In some embodiments, when the fourth information includes a DSCP marking value, the terminal 101 may implement DSCP marking based on the received DSCP marking value.

[0297] In some embodiments, when the fourth information does not include a DSCP marking value, terminal 101 may determine the DSCP marking value. In some embodiments, terminal 101 may determine the DSCP marking value based on at least one of the following: the first information, 5QI, the priority of the QoS flow, and the ARP of the QoS flow.

[0298] In some embodiments, on the user plane, the terminal 101 may perform DSCP marking on the uplink data packets in the data flow, and send the data flow with the added DSCP marking value to the first device 102 .

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

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

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

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

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

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

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

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

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

[0308] The communication method involved in the embodiments of the present disclosure may include at least one of steps S201 to S212. For example, step S201 may be implemented as an independent embodiment. For example, step S205 may be implemented as an independent embodiment. For example, step S206 may be implemented as an independent embodiment. For example, step S207 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S2201 to S2205 are not limited to this.

[0309] In some embodiments, at least two of steps S201 to S212 may be performed in an interchanged order or simultaneously. For example, steps S206 and S207 may be performed in an interchanged order or simultaneously. For example, steps S210 and S212 may be performed in an interchanged order or simultaneously.

[0310] In some embodiments, steps S202, S203, S204, S205, S206, S207, S208, S209, S210, S211, and S212 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0311] In some embodiments, steps S201, S202, S203, S204, S206, S207, S208, S209, S210, S211, and S212 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0312] In some embodiments, steps S201, S202, S203, S204, S205, S207, S208, S209, S210, S211, and S212 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0313] In some embodiments, steps S201, S202, S203, S204, S205, S206, S208, S209, S210, S211, and S212 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0315] 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 second network element 1032. As shown in FIG3, the method includes steps S301 to S302.

[0316] In step S301, second information is obtained.

[0317] The optional implementation of step S301 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.

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

[0319] In step S302, DSCP marking is performed.

[0320] The optional implementation of step S302 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.

[0321] In some embodiments, DSCP marking may be performed based on the second information.

[0322] The communication method involved in the embodiments of the present disclosure may include at least one of steps S301 and S302. For example, step S301 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 S302 are not limited to this.

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

[0324] FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method. The communication method is executed by a third network element 1033. As shown in FIG4, the method includes step S401.

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

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

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

[0328] 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 fourth network element 1034. As shown in FIG5, the method includes steps S501 to S503.

[0329] In step S501, first information is obtained.

[0330] The optional implementation of step S501 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.

[0331] In some embodiments, the fourth network element 1034 may receive the first information sent by the fifth network element 1035 , but is not limited thereto and may also receive the first information sent by other entities.

[0332] In step S502, the second information is sent.

[0333] The optional implementation of step S502 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.

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

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

[0336] The optional implementation of step S503 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.

[0337] In some embodiments, the fourth network element 1034 may send the third information to the sixth network element 1036 , but is not limited thereto and the third information may also be sent to other entities.

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

[0339] In some embodiments, at least two of steps S501 to S503 may be performed in an interchangeable order or simultaneously. For example, steps S502 and S503 may be performed in an interchangeable order or simultaneously.

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

[0341] In some embodiments, steps S501 and S503 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0343] 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 executed by the fifth network element 1035. As shown in FIG6, the method includes steps S601 to S603.

[0344] In step S601, first information is obtained.

[0345] The optional implementation of step S601 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.

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

[0347] In step S602 , policy decision is performed.

[0348] The optional implementation of step S602 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.

[0349] In step S603, the first information is sent.

[0350] The optional implementation of step S603 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.

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

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

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

[0354] FIG7 is a flow chart of a communication method according to an embodiment of the present disclosure. The present disclosure relates to a communication method. The communication method is performed by the first device 102. As shown in FIG7, the method includes steps S701 to S703.

[0355] In step S701, third information is obtained.

[0356] The optional implementation of step S701 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.

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

[0358] In step S702, QoS configuration is determined.

[0359] The optional implementation of step S702 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.

[0360] In step S703, the fourth information is sent.

[0361] The optional implementation of step S703 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.

[0362] In some embodiments, the first device 102 may send the fourth information to the terminal 101 , but is not limited thereto and may also send the fourth information to other entities.

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

[0364] In some embodiments, at least two of steps S701 to S703 may be performed in an interchangeable order or simultaneously. For example, steps S702 and S703 may be performed in an interchangeable order or simultaneously.

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

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

[0367] In step S8101, a first network element receives first information.

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

[0369] In some embodiments, the first network element 1031 may be the fourth network element 1034. In some embodiments, the first network element 1031 may receive the first information sent by the fifth network element 1035, but is not limited thereto and may also receive the first information sent by other entities.

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

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

[0372] In step S8201 , the fourth network element 1034 sends second information to the second network element 1032 .

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

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

[0375] In step S8301 , the fourth network element 1034 sends third information to the first device 102 .

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

[0377] In the following, the technical solutions of the embodiments of the present disclosure are exemplarily described through specific implementation methods.

[0378] In some embodiments, the DSCP mapping with FEC characteristic information (i.e., the first information) indicates that the FEC characteristic information can be used to perform DSCP marking at the outer header of the data packet of the PDU set on N3 / N9 in the transport network (i.e., enabling differential processing of transport data packets carrying FEC characteristic information).

[0379] In some embodiments, the FEC characteristic information identifying the FEC mechanism and SDF characteristics includes at least one of the following information:

[0380] - MDS FEC scheme, or supported variable FEC, or ULPFEC (RS coding belongs to the MDS coding category, i.e., it allows the receiver to recover k source symbols from a set of k received symbols);

[0381] - For MDS FEC scheme / ULP FEC, support static (via control plane) or dynamic (via user plane) redundancy rate;

[0382] - For MDS FEC schemes, the FEC ratio of SDF for supported static or dynamic redundancy rates;

[0383] - a priority associated with a source packet or a repair packet (e.g., a repair packet has a higher, lower, or the same priority as the source packet);

[0384] -The mapping relationship between FEC packet groups and PDU sets;

[0385] - Separate SDF for FEC redundant packets (e.g., in case of congestion, the DSCP marking value can be set to high priority for the SDF);

[0386] - Group SDF / QoS for FEC mechanisms (e.g., source and redundant SDFs of packets, DSCP marking taking into account dependencies between SDFs; these SDFs can be mapped to the same or different QoS flows and have the same or different QFIs).

[0387] In some embodiments, the AF (i.e., the third network element) can provide a DSCP mapping with FEC characteristic information to the 5GC (PCF / SMF / UPF) for determining the PCC (e.g., for determining the transport-level packet marking value (e.g., the DSCP value of the outer IP header)).

[0388] In some embodiments, the AF may use the Nnef_AFsessionWithQoS_Create request message or the Nnef_AFsessionWithQoS_Update request message to provide the DSCP mapping with the FEC characteristic information.

[0389] In some embodiments, the first CP NF (ie, the fifth network element) may be, for example, a PCF.

[0390] In some embodiments, the PCF may determine PCC rules taking into account the DSCP mapping with FEC characteristics and send the DSCP mapping with FEC characteristics to the SMF. In some embodiments, the DSCP mapping with FEC characteristics may be sent to the SMF in PCC rules.

[0391] In some embodiments, the second CP NF (ie, the fourth network element) may be, for example, an SMF.

[0392] In some embodiments, the SMF will provide the UPF (or UPF and UE, UPF mapping for downlink, UE mapping for uplink) with the DSCP mapping with FEC characteristics information, thereby indicating the DSCP marking. The DSCP marking takes into account the FEC characteristics information and / or PDU set information and related QoS information.

[0393] In some embodiments, for each QoS flow, the SMF determines the transport-level packet marking value based on the FEC characteristic information, 5QI, priority, and optional ARP priority. The AMF may then provide the transport-level packet marking value (e.g., DSCP in the outer IP header) to the UPF.

[0394] In some embodiments, the FEC characteristic information identifying the FEC mechanism and SDF characteristics includes at least one of the following information:

[0395] - MDS FEC scheme, or supported variable FEC, or ULPFEC (RS coding belongs to the MDS coding category, i.e., it allows the receiver to recover k source symbols from a set of k received symbols);

[0396] - For MDS FEC scheme / ULP FEC, support static (via control plane) or dynamic (via user plane) redundancy rate;

[0397] - For MDS FEC schemes, the FEC ratio of SDF for supported static or dynamic redundancy rates;

[0398] - a priority associated with a source packet or a repair packet (e.g., a repair packet has a higher, lower, or the same priority as the source packet);

[0399] -The mapping relationship between FEC packet groups and PDU sets;

[0400] - Separate SDF for FEC redundant packets (e.g., in case of congestion, the DSCP marking value can be set to high priority for the SDF);

[0401] - Group SDF / QoS for FEC mechanisms (e.g., source and redundant SDFs of packets, DSCP marking taking into account dependencies between SDFs; these SDFs can be mapped to the same or different QoS flows and have the same or different QFIs).

[0402] In some embodiments, the first UP NF may be, for example, a UPF.

[0403] In some embodiments, the PSA UPF will enhance the DSCP marking performed on the outer header of the downstream data packets of the PDU set on N3 / N9 in the transport network, taking into account FEC feature information and / or PDU set information and related QoS information (i.e., enabling differential processing of transport data packets carrying FEC feature information). If the SMF does not provide a transport-level packet marking value, the UPF will determine the transport-level packet marking value (e.g., the DSCP in the outer IP header).

[0404] In some embodiments, the consumer may be, for example, NG-RAN, N3IWF (Non-3GPP InterWorking Function), TNGF (Trusted Non-3GPP Gateway Function), or W-AGF (wireline access gateway function).

[0405] In some embodiments, the NG-RAN enhances the QoS configuration corresponding to the relevant DSCP for transmission resource allocation. The DSCP uses a DSCP indication or DSCP information. The DSCP indication or DSCP information takes into account FEC characteristic information and / or PDU set information and relevant QoS information.

[0406] In some embodiments, the SMF provides the NG-RAN with a DSCP indication or DSCP information. The DSCP indication or DSCP information takes into account FEC characteristics information and / or PDU set information and related QoS information. The NG-RAN will use it to replace the previously stored DSCP indication or DSCP information.

[0407] Figure 9 is an interactive diagram of an exemplary implementation of a communication method according to an embodiment of the present disclosure. The method can be implemented through the following process.

[0408] In step 1, the AF sends an AF session resource creation or update request, such as a Nnef_AFsessionWithQoS_Create request or a Nnef_AFsessionWithQoS_Update request, to create or update the AF session. The AF may use the Nnef_AFsessionWithQoS_Create request message or the Nnef_AFsessionWithQoS_Update request message to provide a DSCP mapping with an FEC feature signal.

[0409] In some embodiments, the AF may provide a DSCP mapping with FEC characteristic information to the 5GC (PCF / SMF / UPF) for use in determining the PCC (e.g., for determining a transport-level packet marking value (e.g., a DSCP value of an outer IP header)).

[0410] In some embodiments, the DSCP mapping with FEC characteristic information indicates that the FEC characteristic information can be used to perform DSCP marking at the outer header of the data packet of the PDU set on N3 / N9 in the transport network (i.e., enabling differential processing of transport data packets carrying FEC characteristic information).

[0411] In some embodiments, the FEC characteristic information identifying the FEC mechanism and SDF characteristics includes at least one of the following information:

[0412] - MDS FEC scheme, or supported variable FEC, or ULPFEC (RS coding belongs to the MDS coding category, i.e., it allows the receiver to recover k source symbols from a set of k received symbols);

[0413] - For MDS FEC scheme / ULP FEC, support static (via control plane) or dynamic (via user plane) redundancy rate;

[0414] - For MDS FEC schemes, the FEC ratio of SDF for supported static or dynamic redundancy rates;

[0415] - a priority level associated with the source data packet or the redundant data packet (e.g., the redundant data packet has a higher, lower, or the same priority as the source data packet);

[0416] -The mapping relationship between FEC packet groups and PDU sets;

[0417] - Separate SDF for FEC redundant packets (e.g., in case of congestion, the DSCP marking value can be set to high priority for the SDF);

[0418] - Group SDF / QoS for FEC mechanisms (e.g., source and redundant SDFs of packets, DSCP marking taking into account dependencies between SDFs; these SDFs can be mapped to the same or different QoS flows and have the same or different QFIs).

[0419] In some embodiments, the XRM 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.

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

[0421] In step 3, the NEF authorizes the AF request and, based on the parameters provided by the AF, determines whether to contact the TSCTSF or directly the PCF. These signaling steps are described in the AF session with required QoS flow. 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 the QoS requirements for the PCF to make a policy decision.

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

[0423] In some embodiments, the PCF may determine PCC rules taking into account the DSCP mapping with FEC characteristics and send the DSCP mapping with FEC characteristics to the SMF. In some embodiments, the DSCP mapping with FEC characteristics may be sent to the SMF in PCC rules.

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

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

[0426] In step 7, the PCF initiates an SM policy association modification request to the SMF.

[0427] After receiving the PCC rules, the SMF determines the QoS rules and QoS set parameters to configure / activate the rules to the UPF (e.g., through N4 call back).

[0428] In some embodiments, the SMF will provide the UPF (or UPF and UE, UPF mapping for downlink, UE mapping for uplink) with the DSCP mapping with FEC characteristics information, thereby indicating the DSCP marking. The DSCP marking takes into account the FEC characteristics information and / or PDU set information and related QoS information.

[0429] In some embodiments, for each QoS flow, the SMF determines the transport-level packet marking value based on the FEC characteristic information, 5QI, priority, and optional ARP priority. The AMF may then provide the transport-level packet marking value (e.g., DSCP in the outer IP header) to the UPF.

[0430] In some embodiments, the FEC characteristic information identifying the FEC mechanism and SDF characteristics includes at least one of the following information:

[0431] - MDS FEC scheme, or supported variable FEC, or ULPFEC (RS coding belongs to the MDS coding category, i.e., it allows the receiver to recover k source symbols from a set of k received symbols);

[0432] - For MDS FEC scheme / ULP FEC, support static (via control plane) or dynamic (via user plane) redundancy rate;

[0433] - For MDS FEC schemes, the FEC ratio of SDF for supported static or dynamic redundancy rates;

[0434] - a priority level associated with the source data packet or the redundant data packet (e.g., the redundant data packet has a higher, lower, or the same priority as the source data packet);

[0435] -The mapping relationship between FEC packet groups and PDU sets;

[0436] - Separate SDF for FEC redundant packets (e.g., in case of congestion, the DSCP marking value can be set to high priority for the SDF);

[0437] - Group SDF / QoS for FEC mechanisms (e.g., source and redundant SDFs of packets, DSCP marking taking into account dependencies between SDFs; these SDFs can be mapped to the same or different QoS flows and have the same or different QFIs).

[0438] In some embodiments, the SMF may provide a DSCP mapping with FEC characteristics to the UPF and / or NG-RAN and / or UE to indicate QoS enhancement.

[0439] In some embodiments, the SMF obtains QoS parameters for the QoS flow based on PCC rule information of the PCC rule bound to the QoS flow.

[0440] In step 8, in reply, the SMF sends an SM policy association modification response to the PCF.

[0441] In step 9, the SMF triggers the PDU session modification procedure and provides QoS configuration to the UPF and / or NG-RAN.

[0442] In some embodiments, the PSA UPF will enhance the DSCP marking performed on the outer header of the downstream data packets of the PDU set on N3 / N9 in the transport network, taking into account FEC feature information and / or PDU set information and related QoS information (i.e., enabling differential processing of transport data packets carrying FEC feature information). If the SMF does not provide a transport-level packet marking value, the UPF will determine the transport-level packet marking value (e.g., the DSCP in the outer IP header).

[0443] In some embodiments, the consumer may be, for example, NG-RAN, N3IWF, TNGF, or W-AGF.

[0444] In some embodiments, the NG-RAN enhances the QoS configuration corresponding to the relevant DSCP for transmission resource allocation. The DSCP uses a DSCP indication or DSCP information. The DSCP indication or DSCP information takes into account FEC characteristic information and / or PDU set information and relevant QoS information.

[0445] In some embodiments, the SMF provides the NG-RAN with a DSCP indication or DSCP information. The DSCP indication or DSCP information takes into account FEC characteristics information and / or PDU set information and related QoS information. The NG-RAN will use it to replace the previously stored DSCP indication or DSCP information.

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

[0447] 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 provide a communication device comprising a unit or module for implementing each step performed by a network element in any of the above methods. For example, the embodiments of the present disclosure provide a communication device comprising a unit or module for implementing each step performed by a first device in any of the above methods. For example, the embodiments of the present disclosure provide a communication device comprising a unit or module for implementing each step performed by a terminal in any of the above methods.

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

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

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

[0451] In some embodiments, the communication device 1000 may be the first network element 1031. In some embodiments, the transceiver module 1001 may be configured to receive first information, wherein the first information is used to indicate a function associated with a DSCP mark, and the DSCP mark is associated with an FEC feature. Optionally, the transceiver module 1001 may be configured to perform at least one of the communication steps such as sending and / or receiving (e.g., steps S203, S205, S206, and S207) performed by the first network element 1031 in any of the above methods, which are not described in detail here. Optionally, the processing module 1002 may be configured to perform at least one of the other steps (e.g., step S204) performed by the first network element 1031 in any of the above methods except the communication steps such as sending and / or receiving, which are not described in detail here.

[0452] In some embodiments, the communication device 1000 may be a second network element 1032. In some embodiments, the transceiver module 1001 may be configured to receive second information, wherein the second information is used to indicate implementation of a DSCP marking associated with an FEC feature. Optionally, the transceiver module 1001 may be configured to perform at least one of the communication steps (e.g., step S206) such as sending and / or receiving performed by the second network element 1032 in any of the above methods, which are not described in detail here. Optionally, the processing module 1002 may be configured to perform at least one of the other steps (e.g., step S210) such as sending and / or receiving performed by the second network element 1032 in any of the above methods, which are not described in detail here.

[0453] In some embodiments, the communication device 1000 may be a third network element 1033. In some embodiments, the transceiver module 1001 may be configured to send first information, where the first information indicates a function associated with a DSCP marking, where the DSCP marking is associated with an FEC feature. Alternatively, 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 third network element 1033 in any of the above methods, which will not be further described herein.

[0454] In some embodiments, the communication apparatus 1000 may be the first device 102. In some embodiments, the transceiver module 1001 may be configured to receive third information, wherein the third information is used to determine the QoS configuration of the first device. Optionally, the transceiver module 1001 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the first device 102 in any of the above methods (e.g., steps S208 and S211), which are not described in detail here. Optionally, the processing module 1002 may be configured to perform at least one of the other steps (e.g., step S209) performed by the first device 102 in any of the above methods except the communication steps such as sending and / or receiving, which are not described in detail here.

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

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

[0457] 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 12100 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.

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

[0459] 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 (e.g., steps S201, S203, S205, S206, S207, S208, and S211, but not limited thereto) of transmitting and / or receiving in the above method, and the processor 11101 performs at least one of the other steps (e.g., steps S202, S204, S209, S210, and S212, 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.

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

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

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

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

[0464] In some embodiments, chip 11200 further includes one or more interface circuits 11202. Alternatively, terms such as 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 12201.

[0465] In some embodiments, the interface circuit 11202 performs at least one of the communication steps (e.g., steps S201, S203, S205, S206, S207, S208, and S211) of the above method. The interface circuit 11202 performing the communication steps (e.g., steps S201, S203, S205, S206, S207, S208, and S211) of 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, S209, S210, and S212, but not limited thereto).

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

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

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

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

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

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

Claims

1. A communication method, performed by a first network element, wherein: The method comprises: First information is received, wherein the first information is used to indicate a function associated with a Differential Code Service Point (DSCP) marking, where the DSCP marking is associated with a forward error correction (FEC) feature.

2. The method according to claim 1, wherein The first information includes at least one of the following information related to the FEC characteristics: Type information, used to indicate the FEC type; Redundancy rate information, used to indicate the FEC redundancy rate; Ratio information, used to indicate the FEC ratio; First priority information, used to indicate the priority of the data packet; The second priority information is used to indicate the priority of the service data flow SDF; First mapping information, used to indicate a mapping relationship between a data packet and a packet data unit (PDU) set; The second mapping information is used to indicate a mapping relationship between the SDF and the quality of service QoS flow.

3. The method according to claim 1 or 2, wherein: The FEC characteristics include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; The priority of the data packet; Priority of SDF; The mapping relationship between data packets and PDU sets; Mapping relationship between SDF and QoS flow.

4. The method according to any one of claims 1 to 3, wherein The method further comprises: The first information is sent.

5. The method according to claim 4, wherein The sending of the first information includes: Second information is sent to the second network element, where the second information is used to implement a DSCP marking associated with the FEC feature.

6. The method according to claim 5, wherein: The second information includes at least one of the following: the first information; DSCP marking value.

7. The method according to claim 4, wherein: The sending of the first information includes: Sending third information to the first device, wherein the third information is used to determine a QoS configuration of the first device.

8. The method according to claim 7, wherein: The third information includes at least one of the following: the first information; DSCP indication or DSCP information.

9. A communication method, performed by a second network element, wherein: The method comprises: Second information is received, wherein the second information is used to indicate implementation of a Differentiated Services Code Point (DSCP) marking associated with a forward error correction (FEC) feature.

10. The method according to claim 9, wherein: The second information includes at least one of the following: First information; DSCP marking value.

11. The method according to claim 10, wherein: The first information includes at least one of the following information related to the FEC characteristics: Type information, used to indicate the FEC type; Redundancy rate information, used to indicate the FEC redundancy rate; Ratio information, used to indicate the FEC ratio; First priority information, used to indicate the priority of the data packet; The second priority information is used to indicate the priority of the service data flow SDF; First mapping information, used to indicate a mapping relationship between a data packet and a packet data unit (PDU) set; The second mapping information is used to indicate a mapping relationship between the SDF and the quality of service QoS flow.

12. The method according to claim 11, wherein The FEC characteristics include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; The priority of the data packet; Priority of SDF; The mapping relationship between data packets and PDU sets; Mapping relationship between SDF and QoS flow.

13. The method according to any one of claims 9 to 12, wherein: The second information only includes the first information; The method further comprises: Determine a DSCP marking value based on the first information.

14. The method according to any one of claims 9 to 13, wherein The method further comprises: The DSCP marking is performed according to the second information.

15. A communication method, performed by a third network element, wherein: The method comprises: First information is sent, wherein the first information is used to indicate a function associated with a Differential Code Service Point (DSCP) marking, where the DSCP marking is associated with a forward error correction (FEC) feature.

16. The method according to claim 15, wherein The first information includes at least one of the following information related to the FEC characteristics: Type information, used to indicate the FEC type; Redundancy rate information, used to indicate the FEC redundancy rate; Ratio information, used to indicate the FEC ratio; First priority information, used to indicate the priority of the data packet; The second priority information is used to indicate the priority of the service data flow SDF; First mapping information, used to indicate a mapping relationship between a data packet and a packet data unit (PDU) set; The second mapping information is used to indicate a mapping relationship between the SDF and the quality of service QoS flow.

17. The method according to claim 15 or 16, wherein The FEC characteristics include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; The priority of the data packet; Priority of SDF; The mapping relationship between data packets and PDU sets; Mapping relationship between SDF and QoS flow.

18. A communication method, performed by a first device, wherein: The method comprises: Receive third information, where the third information is used to determine a quality of service (QoS) configuration of the first device.

19. The method according to claim 18, wherein The third information includes at least one of the following: First information; DSCP indication or DSCP information.

20. The method according to claim 19, wherein The first information includes at least one of the following information related to the FEC characteristics: Type information, used to indicate the FEC type; Redundancy rate information, used to indicate the FEC redundancy rate; Ratio information, used to indicate the FEC ratio; First priority information, used to indicate the priority of the data packet; The second priority information is used to indicate the priority of the service data flow SDF; First mapping information, used to indicate a mapping relationship between a data packet and a packet data unit (PDU) set; The second mapping information is used to indicate a mapping relationship between the SDF and the quality of service QoS flow.

21. The method according to claim 20, wherein The FEC characteristics include at least one of the following: FEC type; FEC redundancy rate; FEC ratio; The priority of the data packet; Priority of SDF; The mapping relationship between data packets and PDU sets; Mapping relationship between SDF and QoS flow.

22. The method according to any one of claims 18 to 21, wherein The third information only includes the first information; The method further comprises: Determine a DSCP indication or DSCP information based on the first information.

23. The method according to any one of claims 18 to 22, wherein The method further comprises: Determine QoS configuration based on the third information.

24. A communication device, provided in a first network element, wherein: The device comprises: The transceiver module is configured to receive first information, wherein the first information is used to indicate a function associated with a Differential Code Service Point (DSCP) mark, and the DSCP mark is associated with a forward error correction (FEC) feature.

25. A communication device, provided in a second network element, wherein: The device comprises: The transceiver module is configured to receive second information, wherein the second information is used to indicate implementation of a Differentiated Services Code Point (DSCP) marking associated with a forward error correction (FEC) feature.

26. A communication device, provided in a third network element, wherein: The device comprises: The transceiver module is configured to send first information, wherein the first information is used to indicate a function associated with a Differential Code Service Point (DSCP) mark, and the DSCP mark is associated with a forward error correction (FEC) feature.

27. A communication device, provided in a first device, wherein: The device comprises: The transceiver module is configured to receive third information, wherein the third information is used to determine the quality of service (QoS) configuration of the first device.

28. A communication device comprising: one or more processors; a memory storing instructions; When the instruction is executed by the communication device, the communication device implements one of the following: The communication method according to any one of claims 1 to 8; The communication method according to any one of claims 9 to 14; The communication method according to any one of claims 15 to 17; The communication method according to any one of claims 18 to 23.

29. A communication system comprising: A first network element, configured to implement the communication method according to any one of claims 1 to 8; A second network element, configured to implement the communication method according to any one of claims 9 to 14; A third network element, configured to implement the communication method according to any one of claims 15 to 17; A first device, configured to implement the communication method according to any one of claims 18 to 23.

30. A storage medium storing instructions, wherein: When the instructions are executed on a communication device, the communication device is caused to implement at least one of the following: The communication method according to any one of claims 1 to 8; The communication method according to any one of claims 9 to 14; The communication method according to any one of claims 15 to 17; The communication method according to any one of claims 18 to 23.

31. A computer program product comprising instructions, wherein when the instructions are executed on a communication device, the communication device is caused to implement at least one of the following: The communication method according to any one of claims 1 to 8; The communication method according to any one of claims 9 to 14; The communication method according to any one of claims 15 to 17; The communication method according to any one of claims 18 to 23.

Images