Information transmission method and apparatus, and storage medium

Abstract

The present invention provides an information transmission method and apparatus, and a storage medium. The method comprises: sending a first message to a first core network function node, wherein the first message is used for requesting to create or update an AF session, and the first message is further used for providing, to the first core network function node, DSCP mapping for PDU set correlation. In the present invention, in the process of creating or updating the AF session, the PDU set characteristics can be considered, the resource scheduling and configuration of a transmission layer are optimized, the end-to-end QoS requirement is effectively guaranteed, the resource requirement and allocation are better adapted, and the end-to-end QoS resources are coordinated.

Description

Information transmission method and device, and storage medium Technical Field

[0001] The present disclosure relates to the field of communications, and in particular to an information transmission method and device, and a storage medium. Background Art

[0002] Mobile media services, cloud-based augmented reality (AR), cloud-based virtual reality (VR) and other extended reality (XR) services, cloud gaming, and video-based remote control of machines or drones are expected to contribute increasingly higher traffic to the network.

[0003] Summary of the Invention

[0004] To optimize resource scheduling and configuration at the transport layer, embodiments of the present disclosure provide an information transmission method and apparatus, and a storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, there is provided an information transmission method, the method being performed by an application function (AF) function node, including:

[0006] A first message is sent to a first core network function node, where the first message is used to request creation or update of an AF session, and the first message is further used to provide the first core network function node with a differentiated services code point (DSCP) mapping of a packet data unit (PDU) set correlation.

[0007] According to a second aspect of an embodiment of the present disclosure, there is provided an information transmission method, the method being performed by a first core network function node, including:

[0008] receiving a first message sent by an application function (AF) function node, where the first message is used to request creation or update of an AF session, and the first message is further used to provide a differentiated services code point (DSCP) mapping associated with a packet data unit (PDU) set;

[0009] Determine a policy and charging control (PCC) rule; wherein, when determining the PCC rule, the DSCP mapping of the PDU set correlation is considered.

[0010] According to a third aspect of an embodiment of the present disclosure, there is provided an information transmission method, the method being performed by a second core network function node, including:

[0011] receiving a second message sent by the first core network function node, the second message being used to initiate a session management policy control update request, the second message being further used to provide a differentiated services code point (DSCP) mapping of a packet data unit (PDU) set correlation to the second core network function node;

[0012] A third message is sent to a third core network function node, where the third message is used to initiate a session modification request, and the third message is used to provide the third core network function node with a DSCP mapping of the PDU set correlation.

[0013] According to a fourth aspect of an embodiment of the present disclosure, there is provided an information transmission method, the method being performed by a third core network function node, including:

[0014] receiving a third message sent by the second core network function node, where the third message is used to initiate a session modification request, and the third message is used to provide the third core network function node with a DSCP mapping associated with the PDU set;

[0015] Based on the third message, a DSCP tag value is added to the PDU outer header of the PDU set of the downlink packet.

[0016] According to a fifth aspect of an embodiment of the present disclosure, there is provided an information transmission method, the method being performed by an access network device, including:

[0017] receiving a fourth message sent by the second core network function node, where the fourth message is used to provide the access network device with a DSCP mapping associated with the PDU set;

[0018] Based on the fourth message, DSCP information is determined and used.

[0019] According to a sixth aspect of an embodiment of the present disclosure, there is provided an information transmission method, the method being executed by a terminal, including:

[0020] receiving a fifth message sent by the second core network function node, where the fifth message is used to provide the terminal with a DSCP mapping associated with the PDU set;

[0021] Based on the fifth message, a DSCP tag value is added to the PDU outer header of the PDU set of the uplink packet.

[0022] According to a seventh aspect of an embodiment of the present disclosure, an application function AF function node is provided, including:

[0023] The transceiver module is configured to send a first message to a first core network function node, where the first message is used to request the creation or update of an AF session, and the first message is also used to provide the first core network function node with a differentiated services code point (DSCP) mapping of a packet data unit (PDU) set correlation.

[0024] According to an eighth aspect of an embodiment of the present disclosure, a first core network function node is provided, including:

[0025] a transceiver module configured to receive a first message sent by an application function (AF) function node, where the first message is used to request creation or update of an AF session, and the first message is further used to provide a differentiated services code point (DSCP) mapping associated with a packet data unit (PDU) set;

[0026] The processing module is configured to determine a policy and charging control (PCC) rule; wherein the DSCP mapping of the PDU set correlation is considered when determining the PCC rule.

[0027] According to a ninth aspect of an embodiment of the present disclosure, a second core network function node is provided, including:

[0028] a transceiver module configured to receive a second message sent by the first core network function node, the second message being used to initiate a session management policy control update request, the second message being further used to provide a differentiated services code point (DSCP) mapping of a packet data unit (PDU) set correlation to the second core network function node;

[0029] The transceiver module is further configured to send a third message to a third core network function node, where the third message is used to initiate a session modification request and provide the third core network function node with a DSCP mapping of the PDU set correlation.

[0030] According to a tenth aspect of an embodiment of the present disclosure, a third core network function node is provided, including:

[0031] a transceiver module configured to receive a third message sent by the second core network function node, the third message being used to initiate a session modification request, and the third message being used to provide the third core network function node with a DSCP mapping associated with the PDU set;

[0032] The processing module is configured to add a DSCP tag value to a PDU outer header of a PDU set of a downlink packet based on the third message.

[0033] According to an eleventh aspect of an embodiment of the present disclosure, an access network device is provided, including:

[0034] a transceiver module configured to receive a fourth message sent by the second core network function node, wherein the fourth message is used to provide the access network device with a DSCP mapping associated with the PDU set;

[0035] The processing module is configured to determine and use DSCP information based on the fourth message.

[0036] According to a twelfth aspect of an embodiment of the present disclosure, a terminal is provided, including:

[0037] a transceiver module configured to receive a fifth message sent by the second core network function node, wherein the fifth message is used to provide the terminal with a DSCP mapping associated with the PDU set;

[0038] The processing module is configured to add a DSCP tag value to a PDU outer header of a PDU set of an uplink packet based on the fifth message.

[0039] According to a thirteenth aspect of an embodiment of the present disclosure, an application function AF function node is provided, including:

[0040] one or more processors;

[0041] The processor is used to execute the information transmission method described in any one of the first aspects.

[0042] According to a fourteenth aspect of an embodiment of the present disclosure, a first core network function node is provided, including:

[0043] one or more processors;

[0044] The processor is used to execute the information transmission method described in any one of the second aspects.

[0045] According to a fifteenth aspect of an embodiment of the present disclosure, a second core network function node is provided, including:

[0046] one or more processors;

[0047] The processor is used to execute the information transmission method described in any one of the third aspects.

[0048] According to a sixteenth aspect of an embodiment of the present disclosure, a third core network function node is provided, including:

[0049] one or more processors;

[0050] Wherein, the processor is used to execute the information transmission method described in any one of the fourth aspects.

[0051] According to a seventeenth aspect of an embodiment of the present disclosure, an access network device is provided, including:

[0052] one or more processors;

[0053] Wherein, the processor is used to execute the information transmission method described in any one of the fifth aspects.

[0054] According to an eighteenth aspect of the embodiments of the present disclosure, a terminal is provided, including:

[0055] one or more processors;

[0056] Wherein, the processor is used to execute the information transmission method described in any one of the sixth aspects.

[0057] According to a nineteenth aspect of an embodiment of the present disclosure, there is provided a communication system, including:

[0058] An AF functional node, configured to execute the information transmission method according to any one of the first aspects;

[0059] A first core network function node, configured to execute the information transmission method according to any one of the second aspects;

[0060] A second core network function node is configured to execute the information transmission method according to any one of the third aspects;

[0061] A third core network function node is configured to execute the information transmission method according to the fourth aspect;

[0062] An access network device, configured to execute the information transmission method according to any one of the fifth aspects;

[0063] The terminal is configured to execute the information transmission method described in any one of the sixth aspects.

[0064] According to the twentieth aspect of an embodiment of the present disclosure, a storage medium is provided, which stores instructions. When the instructions are executed on a communication device, the communication device executes the information transmission method as described in any one of the first to sixth aspects.

[0065] In the embodiment of the present disclosure, when creating or updating an AF session, the PDU set characteristics can be considered, the resource scheduling and configuration of the transport layer can be optimized, the end-to-end QoS requirements can be effectively guaranteed, the resource requirements and allocation can be better adapted, and the end-to-end QoS resources can be coordinated.

[0066] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0069] FIG2A is an exemplary interaction diagram of an information transmission method provided according to an embodiment of the present disclosure.

[0070] FIG2B is a schematic diagram of an exemplary flow chart of an information transmission method provided according to an embodiment of the present disclosure.

[0071] FIG3A is a schematic diagram of an exemplary flow chart of an information transmission method provided according to an embodiment of the present disclosure.

[0072] FIG3B is a schematic diagram of an exemplary flow chart of an information transmission method provided according to an embodiment of the present disclosure.

[0073] FIG3C is a schematic diagram of an exemplary flow chart of an information transmission method provided according to an embodiment of the present disclosure.

[0074] FIG3D is a schematic diagram of an exemplary flow chart of an information transmission method provided according to an embodiment of the present disclosure.

[0075] FIG3E is a schematic diagram of an exemplary flow chart of an information transmission method provided according to an embodiment of the present disclosure.

[0076] FIG3F is a schematic diagram of an exemplary flow chart of an information transmission method provided according to an embodiment of the present disclosure.

[0077] FIG4A is an exemplary interaction diagram of an information transmission method provided according to an embodiment of the present disclosure.

[0078] FIG4B is an exemplary interaction diagram of the information transmission method provided according to an embodiment of the present disclosure.

[0079] FIG5A is a schematic diagram of an exemplary structure of an AF function node provided according to an embodiment of the present disclosure.

[0080] FIG5B is a schematic diagram of an exemplary structure of a first core network function node provided according to an embodiment of the present disclosure.

[0081] FIG5C is a schematic diagram of an exemplary structure of a second core network function node provided according to an embodiment of the present disclosure.

[0082] FIG5D is a schematic diagram of an exemplary structure of a third core network function node provided according to an embodiment of the present disclosure.

[0083] FIG5E is a schematic diagram of an exemplary structure of an access network device provided according to an embodiment of the present disclosure.

[0084] FIG5F is a schematic diagram of an exemplary structure of a terminal provided according to an embodiment of the present disclosure.

[0085] FIG6A is a schematic diagram of an exemplary structure of a communication device provided according to an embodiment of the present disclosure.

[0086] FIG6B is a schematic diagram of an exemplary structure of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0087] Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. In the following description, when referring to the drawings, like numbers in different figures represent like or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present invention, as detailed in the appended claims.

[0088] The embodiments of the present disclosure provide an information transmission method, an information transmission device, and a storage medium.

[0089] In a first aspect, an embodiment of the present disclosure provides an information transmission method, which is executed by an application function (AF) function node and includes:

[0090] A first message is sent to a first core network function node, where the first message is used to request creation or update of an AF session, and the first message is further used to provide the first core network function node with a differentiated services code point (DSCP) mapping of a packet data unit (PDU) set correlation.

[0091] In the above embodiment, the AF function node can send a first message to the first core network function node, requesting to create or update an AF session through the first message, and at the same time provide the DSCP mapping of the PDU set correlation to the first core network function node, so that in the process of creating or updating the AF session, the PDU set characteristics are taken into account and the availability is high.

[0092] In conjunction with some embodiments of the first aspect, in some embodiments, the first message includes at least one of the following:

[0093] A DSCP tag value obtained after performing DSCP mapping related to the PDU set;

[0094] First indication information; the first indication information is used to instruct the first core network function node to consider the DSCP mapping of the PDU set relevance when determining the policy and charging control PCC rule;

[0095] The association information is information associated with the DSCP mapping for performing the correlation of the PDU set.

[0096] In the above embodiment, the first message may include but is not limited to at least one of the above information, so that the first core network function node considers the DSCP mapping related to the PDU set when determining the PCC rule, which has high availability.

[0097] In conjunction with some embodiments of the first aspect, in some embodiments, the association information includes at least one of the following:

[0098] Service information; wherein the service information includes multimodal service identification information, the multimodal service identification information is used to identify multiple flows in the service group;

[0099] Terminal address information and / or terminal identification information;

[0100] AF identifier application identification information;

[0101] Stream description information;

[0102] Data network name DNN;

[0103] Single Network Slice Selection Assistance Information S-NSSAI;

[0104] Quality of Service (QoS) parameters.

[0105] In the above embodiment, the associated information may include but is not limited to at least one of the above items, thereby assisting the first core network function node in determining the PCC rules, and simplifying the multimodal data flow of the device in the XR service, which is helpful for service assurance and user experience.

[0106] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0107] Receive a first response message sent by the first core network function node after determining the PCC rule, where the first response message is used to respond to the first message, and the first core network function node considers the DSCP mapping of the PDU set correlation when determining the PCC rule.

[0108] In the above embodiment, the AF function node can receive a first response message sent by the first core network function node after determining the PCC rule. Based on the first response message, it can be determined that the first core network function node considers the DSCP mapping of the PDU set relevance when determining the PCC rule, and the availability is high.

[0109] In a second aspect, an embodiment of the present disclosure provides an information transmission method, which is performed by a first core network function node and includes:

[0110] receiving a first message sent by an application function (AF) function node, where the first message is used to request creation or update of an AF session, and the first message is further used to provide a differentiated services code point (DSCP) mapping associated with a packet data unit (PDU) set;

[0111] Determine a policy and charging control (PCC) rule; wherein, when determining the PCC rule, the DSCP mapping of the PDU set correlation is considered.

[0112] In the above embodiment, the first core network function node considers the DSCP mapping of the PDU set relevance when determining the PCC rule. This optimizes the resource scheduling and configuration of the transport layer, effectively guarantees end-to-end QoS requirements, better adapts resource requirements and allocation, and coordinates end-to-end QoS resources.

[0113] In conjunction with some embodiments of the second aspect, in some embodiments, the first message includes at least one of the following:

[0114] A DSCP tag value obtained after performing DSCP mapping of the PDU set correlation; wherein the DSCP tag value is added to the outer Internet Protocol IP header of the PDU set on the first port in the transmission network;

[0115] First indication information; the first indication information is used to instruct the first core network function node to consider the DSCP mapping of the PDU set relevance when determining the PCC rule;

[0116] The association information is information associated with the DSCP mapping for performing the correlation of the PDU set.

[0117] In conjunction with some embodiments of the second aspect, in some embodiments, the association information includes at least one of the following:

[0118] Service information; wherein the service information includes multimodal service identification information, the multimodal service identification information is used to identify multiple flows in the service group;

[0119] Terminal address information and / or terminal identification information;

[0120] AF identifier application identification information;

[0121] Stream description information;

[0122] Data network name DNN;

[0123] Single Network Slice Selection Assistance Information S-NSSAI;

[0124] QoS parameters.

[0125] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0126] A first response message is sent to the AF function node, where the first response message is used to respond to the first message.

[0127] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0128] A second message is sent to the second core network function node, where the second message is used to initiate a session management policy control update request, and the second message is also used to provide the second core network function node with a DSCP mapping related to the PDU.

[0129] In the above embodiment, the first core network function node can send a second message to the second core network function node, providing the second core network function node with the DSCP mapping associated with the PDU. This allows the second core network function node to provide the DSCP mapping associated with the PDU to the third core network function node. This provides high availability.

[0130] In conjunction with some embodiments of the second aspect, in some embodiments, the second message includes at least one of the following:

[0131] A DSCP tag value obtained after performing DSCP mapping related to the PDU set;

[0132] Second indication information; the second indication information is used to instruct the second core network function node to provide the DSCP mapping associated with the PDU set to the third core network function node;

[0133] The PCC rules.

[0134] In the above embodiment, the first core network function node may send the above content to the second core network function node through the second message, which is simple to implement and has high availability.

[0135] In a third aspect, an embodiment of the present disclosure provides an information transmission method, which is performed by a second core network function node and includes:

[0136] receiving a second message sent by the first core network function node, the second message being used to initiate a session management policy control update request, the second message being further used to provide a differentiated services code point (DSCP) mapping of a packet data unit (PDU) set correlation to the second core network function node;

[0137] A third message is sent to a third core network function node, where the third message is used to initiate a session modification request, and the third message is used to provide the third core network function node with a DSCP mapping of the PDU set correlation.

[0138] In the above embodiment, the second core network function node can provide the DSCP mapping associated with the PDU set to the third core network function node, so that the third core network function node adds the DSCP tag value to the PDU outer header of the PDU set of the downlink packet. This optimizes the resource scheduling and configuration of the transport layer, effectively guarantees end-to-end QoS requirements, better adapts resource requirements and allocation, and coordinates end-to-end QoS resources.

[0139] In conjunction with some embodiments of the third aspect, in some embodiments, the second message includes at least one of the following:

[0140] A DSCP tag value obtained after performing DSCP mapping related to the PDU set;

[0141] Second indication information; the second indication information is used to instruct the second core network function node to provide the DSCP mapping of the PDU set correlation to at least the third core network function node;

[0142] The PCC rules.

[0143] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0144] Based on the PCC rule included in the second message, a quality of service (QoS) parameter is derived, and a QoS rule is determined.

[0145] In the above embodiment, the second core network function node can derive QoS parameters and determine QoS rules based on PCC rules, and provide QoS to the third core network function node for installation and execution, which is simple to implement and has high availability.

[0146] In conjunction with some embodiments of the third aspect, in some embodiments, the third message includes at least one of the following:

[0147] A DSCP tag value obtained after performing DSCP mapping related to the PDU set;

[0148] The third indication information is used to instruct the third core network function node to add a DSCP tag value to the PDU outer header of the PDU set of the downlink packet;

[0149] QoS rules.

[0150] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes at least one of the following:

[0151] Sending a fourth message to the access network device, wherein the fourth message is used to provide the access network device with a DSCP mapping associated with the PDU set;

[0152] A fifth message is sent to the terminal, where the fifth message is used to provide the terminal with a DSCP mapping associated with the PDU set.

[0153] In the above embodiment, the second core network function node can also provide DSCP mapping related to the PDU set to the access network device and / or terminal, optimize the resource scheduling and configuration of the transport layer, effectively guarantee the end-to-end QoS requirements, better adapt resource requirements and allocation, and coordinate end-to-end QoS resources.

[0154] In combination with some embodiments of the third aspect, in some embodiments, a second response message is sent to the first core network function node, and the second response message is used to respond to the second message.

[0155] In a fourth aspect, an embodiment of the present disclosure provides an information transmission method, which is performed by a third core network function node and includes:

[0156] receiving a third message sent by the second core network function node, where the third message is used to initiate a session modification request, and the third message is used to provide the third core network function node with a DSCP mapping associated with the PDU set;

[0157] Based on the third message, a DSCP tag value is added to the PDU outer header of the PDU set of the downlink packet.

[0158] In the above embodiment, the third core network function node can add a DSCP tag value to the PDU outer header of the PDU set of the downlink packet, thereby achieving the purpose of considering the characteristics of the PDU set in the process of creating or updating the AF session, optimizing the resource scheduling and configuration of the transport layer, effectively ensuring end-to-end QoS requirements, better adapting to resource requirements and allocation, and coordinating end-to-end QoS resources.

[0159] In conjunction with some embodiments of the fourth aspect, in some embodiments, the third message includes at least one of the following:

[0160] A DSCP tag value obtained after performing DSCP mapping related to the PDU set;

[0161] The third indication information is used to instruct the third core network function node to add a DSCP tag value to the PDU outer header of the PDU set of the downlink packet;

[0162] QoS rules.

[0163] In a fifth aspect, an embodiment of the present disclosure provides an information transmission method, which is executed by an access network device and includes:

[0164] receiving a fourth message sent by the second core network function node, where the fourth message is used to provide the access network device with a DSCP mapping associated with the PDU set;

[0165] Based on the fourth message, DSCP information is determined and used.

[0166] In the above embodiment, the access network device may use DSCP information to facilitate consistent understanding of DSCP tag values ​​by network devices.

[0167] In conjunction with some embodiments of the fifth aspect, in some embodiments, the method further includes:

[0168] The historical DSCP information is replaced with the determined DSCP information.

[0169] In a sixth aspect, an embodiment of the present disclosure provides an information transmission method, which is executed by a terminal and includes:

[0170] receiving a fifth message sent by the second core network function node, where the fifth message is used to provide the terminal with a DSCP mapping associated with the PDU set;

[0171] Based on the fifth message, a DSCP tag value is added to the PDU outer header of the PDU set of the uplink packet.

[0172] In the above embodiment, the terminal can add a DSCP tag value to the PDU outer header of the PDU set of the uplink packet. This optimizes uplink transmission, effectively guarantees end-to-end QoS requirements, better adapts resource requirements and allocation, and coordinates end-to-end QoS resources.

[0173] In combination with some embodiments of any of the above aspects, in some embodiments, the PDU set correlation is used to identify the correlation or dependency relationship between PDU sets.

[0174] In the above embodiment, the PDU set correlation can be used to identify the correlation or dependency between PDU sets, so that the PDU set characteristics are taken into account during the AF session creation or update process, thereby improving availability.

[0175] In combination with some embodiments of any of the above aspects, in some embodiments, the PDU set correlation is used to identify at least one of the following:

[0176] The correlation or dependency of a PDU set with other PDU sets within the same QoS flow;

[0177] The correlation or dependency between PDU sets of different QoS flows of the same service;

[0178] The correlation or dependency between PDU sets within the media transport flow traffic flow of the same service;

[0179] The correlation or dependency between PDU sets between media transport flows of the same service;

[0180] The correlation or dependency between PDU sets within the same connection stream within the same service connection channel;

[0181] The correlation or dependency between PDU sets in different connection flows within the connection channel of the same service.

[0182] In the above embodiment, the PDU set correlation is described, and the correlation or dependency between PDU sets can be identified at different transmission granularities, thereby improving the availability and reliability of the PDU set characteristic parameter, the PDU set correlation, effectively guaranteeing end-to-end QoS requirements, and better coordinating end-to-end QoS resources.

[0183] In combination with some embodiments of any of the above aspects, in some embodiments, the information on the PDU set correlation has at least one of the following attributes:

[0184] A set of related PDUs belongs to a PDU group;

[0185] Each PDU group includes an anchor PDU set; wherein the PDU set correlation is the correlation or dependency relationship between other PDU sets in the PDU group and the anchor PDU set.

[0186] In combination with some embodiments of any of the above aspects, in some embodiments, the PDU set correlation information is used to indicate at least one of the following:

[0187] If the anchor PDU set in the PDU group is not successfully transmitted, the transmission of other PDU sets in the PDU group is abandoned;

[0188] If the preceding PDU set in the PDU group is not successfully transmitted, the transmission of the subsequent PDU set that has not been transmitted in the PDU group is abandoned;

[0189] The first PDU set does not meet the PDU set delay budget PSDB, and the transmission of the first PDU set is abandoned;

[0190] The priority of the anchor PDU set in a PDU group is set or changed, and the priorities of other PDUs in the PDU group are also set or changed;

[0191] If the PDU set importance of the anchor PDU set in a PDU group changes, the PDU set importances of other PDU sets in the PDU group also change accordingly.

[0192] In a seventh aspect, an embodiment of the present disclosure proposes an information transmission application function AF function node, including:

[0193] The transceiver module is configured to send a first message to a first core network function node, where the first message is used to request the creation or update of an AF session, and the first message is also used to provide the first core network function node with a differentiated services code point (DSCP) mapping of a packet data unit (PDU) set correlation.

[0194] In an eighth aspect, an embodiment of the present disclosure provides a first core network function node, including:

[0195] a transceiver module configured to receive a first message sent by an application function (AF) function node, where the first message is used to request creation or update of an AF session, and the first message is further used to provide a differentiated services code point (DSCP) mapping associated with a packet data unit (PDU) set;

[0196] The processing module is configured to determine a policy and charging control (PCC) rule; wherein the DSCP mapping of the PDU set correlation is considered when determining the PCC rule.

[0197] In a ninth aspect, an embodiment of the present disclosure provides a second core network function node, including:

[0198] a transceiver module configured to receive a second message sent by the first core network function node, the second message being used to initiate a session management policy control update request, the second message being further used to provide a differentiated services code point (DSCP) mapping of a packet data unit (PDU) set correlation to the second core network function node;

[0199] The transceiver module is further configured to send a third message to a third core network function node, where the third message is used to initiate a session modification request and provide the third core network function node with a DSCP mapping of the PDU set correlation.

[0200] In a tenth aspect, an embodiment of the present disclosure provides a third core network function node, including:

[0201] a transceiver module configured to receive a third message sent by the second core network function node, the third message being used to initiate a session modification request, and the third message being used to provide the third core network function node with a DSCP mapping associated with the PDU set;

[0202] The processing module is configured to add a DSCP tag value to a PDU outer header of a PDU set of a downlink packet based on the third message.

[0203] In an eleventh aspect, an embodiment of the present disclosure provides an access network device, including:

[0204] a transceiver module configured to receive a fourth message sent by the second core network function node, wherein the fourth message is used to provide the access network device with a DSCP mapping associated with the PDU set;

[0205] The processing module is configured to determine and use DSCP information based on the fourth message.

[0206] In a twelfth aspect, an embodiment of the present disclosure provides a terminal, including:

[0207] a transceiver module configured to receive a fifth message sent by the second core network function node, wherein the fifth message is used to provide the terminal with a DSCP mapping associated with the PDU set;

[0208] The processing module is configured to add a DSCP tag value to a PDU outer header of a PDU set of an uplink packet based on the fifth message.

[0209] In a thirteenth aspect, an embodiment of the present disclosure proposes an application function AF function node, including:

[0210] one or more processors;

[0211] The processor is used to execute the information transmission method described in any one of the first aspects.

[0212] In a fourteenth aspect, an embodiment of the present disclosure provides a first core network function node, including:

[0213] one or more processors;

[0214] The processor is used to execute the information transmission method described in any one of the second aspects.

[0215] In a fifteenth aspect, an embodiment of the present disclosure provides a second core network function node, including:

[0216] one or more processors;

[0217] The processor is used to execute the information transmission method described in any one of the third aspects.

[0218] In a sixteenth aspect, an embodiment of the present disclosure provides a third core network function node, including:

[0219] one or more processors;

[0220] Wherein, the processor is used to execute the information transmission method described in any one of the fourth aspects.

[0221] In a seventeenth aspect, an embodiment of the present disclosure provides an access network device, including:

[0222] one or more processors;

[0223] Wherein, the processor is used to execute the information transmission method described in any one of the fifth aspects.

[0224] In an eighteenth aspect, an embodiment of the present disclosure provides a terminal, including:

[0225] one or more processors;

[0226] Wherein, the processor is used to execute the information transmission method described in any one of the sixth aspects.

[0227] In a nineteenth aspect, an embodiment of the present disclosure provides a communication system, including:

[0228] An AF functional node, configured to execute the information transmission method according to any one of the first aspects;

[0229] A first core network function node, configured to execute the information transmission method according to any one of the second aspects;

[0230] A second core network function node is configured to execute the information transmission method according to any one of the third aspects;

[0231] A third core network function node is configured to execute the information transmission method according to the fourth aspect;

[0232] An access network device, configured to execute the information transmission method according to any one of the fifth aspects;

[0233] The terminal is configured to execute the information transmission method described in any one of the sixth aspects.

[0234] In the twentieth aspect, an embodiment of the present disclosure proposes a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes the information transmission method as described in any one of the first to sixth aspects.

[0235] It is understandable that the above-mentioned devices, terminals, communication systems, storage media, and computer programs are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods and will not be repeated here.

[0236] The present disclosure provides an information transmission method, apparatus, and storage medium. In some embodiments, the terms "information transmission method," "information processing method," and "communication method" are interchangeable; the terms "information transmission apparatus," "information processing apparatus," and "communication apparatus" are interchangeable; and the terms "information processing system," "communication system," and "communication system" are interchangeable.

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

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

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

[0240] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "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.

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

[0242] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

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

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

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

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

[0247] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "entity", "subject", etc.

[0248] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0249] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or 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)", etc.

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

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

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

[0253] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0254] As shown in FIG1 , a communication system 100 includes but is not limited to an application function (AF) device 101 , a core network function node 102 , an access network device 103 , and a terminal 104 .

[0255] In some embodiments, the AF function node 101 may be an application server that can interact with the core network function node 102 and provide business services. The AF may exist for different application services and may be deployed by an operator or a trusted third party.

[0256] In some embodiments, the core network function node 102 includes but is not limited to at least one of the following:

[0257] A first core network function node 102 - 1 ; a second core network function node 102 - 2 ; and a third core network function node 102 - 3 .

[0258] Each core network function node may be a core network function network element.

[0259] Among them, the first core network function node 102-1 can be a policy control function (PCF), which mainly manages the quality of service (QoS) of each business data flow in the 5G core network.

[0260] Among them, the second core network function node 102-2 can be a session management function (SMF), which mainly manages the quality of service (QoS) of each business data flow in the 5G core network. It is responsible for establishing and managing sessions, terminal Internet Protocol (IP) address allocation and management, etc.

[0261] Among them, the third core network function node 102-3 can be a user plane function (UPF), which is responsible for forwarding traffic, reporting traffic usage, determining QoS policy implementation, etc.

[0262] In some embodiments, the core network function node 102 may further include but is not limited to at least one of the following:

[0263] Fourth core network function node 102 - 4 ; fifth core network function node 102 - 5 ; sixth core network function node 102 - 6 .

[0264] Among them, the fourth core network function node 102-4 can be a network exposure function (NEF), which is a network function entity responsible for opening the 5G core network capabilities to a third party or a non-3rd Generation Partnership Project (3GPP) environment.

[0265] Among them, the fifth core network function node 102-5 can be an access and mobility management function (AMF), which is responsible for terminal identity authentication, authorization, registration, mobility management and connection management functions.

[0266] Among them, the sixth core network function node 102-6 can be a time sensitive communication time synchronization function (Time Sensitive Communication and Time Synchronization Function, TSCTSF), which can associate the time synchronization service request of the network function (NF) consumer with the AF session of the PCF, and / or detect the availability of the 5G system (5G System, 5GS) bridge information of the Ethernet and IP type packet data unit (Packet Data Unit, PDU) sessions reported by the PCF, etc.

[0267] The above description is merely an exemplary description. The core network function node 102 may also include other network functions, which is not limited in this disclosure.

[0268] In some embodiments, the core network function node 102 may be a device including one or more network elements, or may be multiple devices or a group of devices. The network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

[0269] In some embodiments, the access network device 103 is, for example, a node or device that accesses the 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.

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

[0271] In some embodiments, the terminal 104 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, 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.

[0272] In some embodiments, the core network function node 102 and the access network device 103 may be collectively referred to as network devices.

[0273] In some embodiments, the AF function node 101 may be replaced by an application server.

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

[0275] In some embodiments, the terminal 101 is connected to the core network function node 102 through the access network device 103 .

[0276] In some embodiments, the AF function node 101 may be connected to one or more core network function nodes, for example, may be connected to an NEF, a PCF, etc.

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

[0278] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and 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.

[0279] The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.18 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (WiMAX (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (WiMAX (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, systems utilizing other communication methods, and next-generation systems based on these. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G) may also be used.

[0280] XR services involve multimodal data streams. Multimodal data is data describing the same service or application, 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 tactile and visual synchronization. These media services share common characteristics within their data streams, between data streams, 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 service assurance and user experience.

[0281] Extended Reality Multimedia (XRM) and interactive media services require the 5GS system to comprehensively consider the QoS characteristics of relevant data flows. For example, parameters such as the delay critical guaranteed bit rate (GBR) data flow, guaranteed flow bit rate (GFBR), packet delay budget (PDB), and default maximum data burst volume (MDBV) must be met and coordinated. This also involves ensuring the consistency of QoS authorization and execution for multiple XRM data flows within a single terminal and across multiple terminals.

[0282] Currently, AF supports enhanced per-PDU set processing of XRM service data flows to support AF's enhanced QoS awareness and assurance of XRM service data flows, as well as enhanced user Quality of Experience (QoE). The following descriptions include AF's provision of PDU set-specific QoS features and protocols:

[0283] PDU Set specific QoS characteristics;

[0284] PDU Set Delay Budget (PSDB);

[0285] PDU Set Error Rate (PSER);

[0286] PDU Set Integrated Handling Information (PSIHI)

[0287] The SMF and UPF can combine the protocol description and protocol header extension provided by the AF to execute the GPRS Tunneling Protocol-User Plane (GTP-U) used in the GPRS network for the corresponding PDU in the corresponding SDF PDU set, carrying PDU set information. The PDU set information is used by the NG-RAN for QoS processing based on the PDU set. The PDU set information includes:

[0288] PDU Set Sequence Number;

[0289] Indication of End PDU of the PDU Set;

[0290] PDU Sequence Number within a PDU Set;

[0291] PDU Set Size in bytes;

[0292] PDU Set Importance, which identifies the relative importance of a PDU set compared to other PDU sets in the QoS flow.

[0293] The above PDU set feature enhancements have greatly improved 5GS's QoS guarantee for XRM service requirements.

[0294] The above process is an optimization of the network layer. To optimize resource processing for XRM services at the transport layer, this disclosure provides the following information transmission method, apparatus, and storage medium. This can consider PDU set characteristics during the creation or update of AF sessions, optimize transport layer resource scheduling and configuration, effectively guarantee end-to-end QoS requirements, better adapt resource requirements and allocation, and coordinate end-to-end QoS resources.

[0295] FIG2A is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG2A , the present disclosure embodiment relates to an information transmission method, which includes:

[0296] In step S2101, the AF function node 101 sends a first message to the first core network function node 102-1.

[0297] In some embodiments, the first core network function node 102-1 receives the first message. The first core network function node 102-1 is a PCF.

[0298] In some embodiments, the first message is used to request creation or update of an AF session.

[0299] In an example, the first message may be an AF session creation (Nnef_AFsessionWithQoS_Create) request message.

[0300] In an example, the first message may be an AF session update (Nnef_AFsessionWithQoS_Update) request message.

[0301] In some embodiments, the name of the first message is not limited and may be replaced by an AF session creation request message, an AF session update request message, etc.

[0302] In some embodiments, the first message is further used to provide the first core network function node 102-1 with a Differentiated Services Code Point (DSCP) mapping of a PDU set correlation.

[0303] In some embodiments, the first message may include, but is not limited to, at least one of the following:

[0304] A DSCP tag value obtained after performing DSCP mapping related to the PDU set;

[0305] First indication information; the first indication information is used to instruct the first core network function node to consider the DSCP mapping associated with the PDU set when determining a policy and charging control (PCC) rule;

[0306] The association information is information associated with the DSCP mapping for performing the correlation of the PDU set.

[0307] In an example, the AF function node 101 may perform DSCP mapping of the PDU set correlation to obtain the DSCP label value, and directly provide it to the first core network function node 102 - 1 through the first message.

[0308] Exemplarily, the AF function node 101 may perform DSCP mapping of PDU set relevance based on a predefined manner or a mapping relationship agreed upon in a protocol.

[0309] For example, assuming that PDU set relevance is not considered, the DSCP tag value range is [0, N], where N can be 63. When PDU set relevance is considered, the DSCP tag value can be refined. For example, when PDU set relevance is not considered, DSCP tag value #1 is mapped, and DSCP tag values ​​#11, DSCP tag value #12, DSCP tag value #13, and so on are mapped based on different PDU set relevances.

[0310] Alternatively, the value range of the DSCP tag value may be expanded, for example, to [0, M], where M is greater than N.

[0311] The above description is merely an example, and all solutions for obtaining the DSCP label value after the AF function node 101 performs DSCP mapping related to the PDU set should fall within the protection scope of the present disclosure.

[0312] In an example, the AF function node 101 may not perform DSCP mapping of the PDU set correlation, but instead carry first indication information in the first message, and the first indication information is used to instruct the first core network function node 102-1 to consider the DSCP mapping of the PDU set correlation when determining the PCC rule.

[0313] In one example, the above-mentioned association information may include but is not limited to at least one of the following:

[0314] Service information (XRM service information); wherein the service information includes multimodal service identification information, and the multimodal service identification information is used to identify multiple flows in the service group;

[0315] Terminal address information and / or terminal identification information;

[0316] AF identifier application identification information;

[0317] Stream description information;

[0318] Data Network Name (DNN);

[0319] Single Network Slice Selection Assistance Information (S-NSSAI);

[0320] QoS parameters.

[0321] Among them, QoS parameters include but are not limited to at least one of the following: end-to-end delay; 5G QoS identifier, Address Resolution Protocol (ARP), stream bit rate, priority, etc.

[0322] In an example, the first message may include one or more of a DSCP tag value, first indication information, and association information.

[0323] In some embodiments, the PDU set correlation is used to identify a correlation or dependency between PDU sets.

[0324] In one example, the PDU set correlation is used to identify at least one of the following:

[0325] The correlation or dependency of a PDU set with other PDU sets within the same QoS flow;

[0326] The correlation or dependency between PDU sets of different QoS flows of the same service;

[0327] The correlation or dependency between PDU sets within a traffic flow of the same service;

[0328] The correlation or dependency between PDU sets between media traffic flows of the same service;

[0329] The correlation or dependency between PDU sets within the same connection stream within the same service connection;

[0330] The correlation or dependency between PDU sets within different streams within a connection channel of the same service.

[0331] The media transport stream traffic flow may include one or more service data streams, which may be XR service streams such as video streams and audio streams.

[0332] Among them, the connection channel connection may include one or more stream-to-stream streams. In the embodiment of the present disclosure, the PDU set correlation is described, which can identify the correlation or dependency between PDU sets at different transmission granularities (for example, within the same QoS flow, between different QoS flows of the same service, within the media transmission flow traffic flow of the same service, between media transmission flow traffic flows of the same service, within the same connection flow stream in the connection channel connection of the same service, and within different connection flow streams in the connection channel connection of the same service), thereby improving the availability and reliability of the PDU set characteristic parameter, namely, the PDU set correlation, effectively guaranteeing the end-to-end QoS requirements, and better coordinating the end-to-end QoS resources.

[0333] The above description is merely an exemplary description. The correlation or dependency between PDU sets can be identified by PDU set correlation, which is not limited in the present disclosure.

[0334] In some embodiments, the information about the PDU set dependency has at least one of the following properties:

[0335] A set of PDUs with a correlation (or dependency) belongs to a PDU group.

[0336] Each PDU group includes an anchor PDU set (key PDU set); wherein the PDU set correlation is the correlation or dependency relationship between other PDU sets in the PDU group and the anchor PDU set.

[0337] In one example, the PDU set dependency information is used to indicate at least one of the following:

[0338] If the anchor PDU set in the PDU group is not successfully transmitted, the transmission of other PDU sets in the PDU group is abandoned;

[0339] If the preceding PDU set in the PDU group is not successfully transmitted, the transmission of the subsequent PDU set that has not been transmitted in the PDU group is abandoned;

[0340] The first PDU set does not satisfy the PSDB, and the transmission of the first PDU set is abandoned;

[0341] The priority of the anchor PDU set in a PDU group is set or changed, and the priorities of other PDUs in the PDU group are also set or changed;

[0342] If the PDU set importance of the anchor PDU set in a PDU group changes, the PDU set importances of other PDU sets in the PDU group also change accordingly.

[0343] For example, if the second transmitted PDU set in the PDU group is not successfully transmitted, for example, not successfully transmitted to the receiver, the transmission of the third PDU set, the fourth PDU set, etc. in the PDU group may be abandoned.

[0344] For another example, a certain PDU set in the PDU group, that is, the first PDU, does not meet the PSDB, and the transmission of the first PDU set can be abandoned.

[0345] For another example, the anchor PDU set in the PDU group has a priority set, and the priority is 1. The priorities of other PDU sets in the PDU group can be set, assuming that the priorities are all 2.

[0346] For another example, the priority of the anchor PDU set in the PDU group is changed. Suppose the priority is reduced to 2. Then the priorities of other PDU sets in the PDU group need to be changed. Suppose the priorities of other PDU sets are all reduced to 3.

[0347] For another example, the PDU set importance of the anchor PDU set in the PDU group is 1, and the PDU set importance of other PDU sets is 4. When the PDU set importance of the anchor PDU set drops to 2, the PDU set importance of other PDU sets will also drop, assuming it drops to 5.

[0348] In an example, at least one of the above situations may be indicated by bits.

[0349] Exemplarily, the information on the relevance of the PDU set may use at least 5 bits to represent the above situations, and the bit value corresponding to each situation is a first value, such as "1", which is used to indicate the existence of a corresponding situation.

[0350] For example, if the bit value corresponding to the information on the PDU set correlation is "10011", then the information on the PDU set correlation can be used to indicate that the anchor PDU set in the PDU group is not successfully transmitted, and the transmission of other PDU sets in the PDU group is abandoned; and the anchor PDU set in the PDU group sets or changes the priority, and the other PDUs in the PDU group also set or change the priority; and the PDU set importance of the anchor PDU set in the PDU group changes, and the PDU set importance of other PDU sets in the PDU group also changes accordingly.

[0351] Exemplarily, the PDU set relevance information may use multiple bits to represent the above-mentioned situations or combinations of situations. For example, when the bit value corresponding to the PDU set relevance information is "001," it indicates that the anchor PDU set within the PDU group was not successfully transmitted, and the transmission of other PDU sets within the PDU group was abandoned. When the bit value corresponding to the PDU set relevance information is "101," it indicates that the anchor PDU set within the PDU group was not successfully transmitted, and the transmission of other PDU sets within the PDU group was abandoned. In addition, if the priority of the anchor PDU set within the PDU group is set or changed, the priority of other PDUs within the PDU group is also set or changed.

[0352] The above description is merely an example, and any scheme in which the information on the relevance of a PDU set is indicated in a bit manner should fall within the scope of protection of the present disclosure.

[0353] The information on the relevance of the PDU set may also indicate the corresponding situation in other ways.

[0354] Exemplarily, the information on the PDU set relevance may be set to “true” or “false” to indicate a corresponding situation.

[0355] Exemplarily, the corresponding situation can be indicated by carrying the corresponding information element (IE). For example, if the anchor PDU set in the PDU group is not successfully transmitted, the transmission of other PDU sets in the PDU group is abandoned, which corresponds to the first IE (which may also be an IE with another name); if the preceding PDU set in the PDU group is not successfully transmitted, the transmission of the subsequent PDU set that has not been transmitted in the PDU group is abandoned, which corresponds to the second IE, .... If the PDU set correlation information includes the first IE, the PDU set correlation information is used to indicate that the anchor PDU set in the PDU group is not successfully transmitted, and the transmission of other PDU sets in the PDU group is abandoned.

[0356] The above description is merely an exemplary description, and the present disclosure does not limit this description.

[0357] Step S2102: The first core network function node 102-1 determines a PCC rule.

[0358] In some embodiments, the first core network function node 102 - 1 is a PCF.

[0359] In some embodiments, the first core network function node 102 - 1 considers the DSCP mapping associated with the PDU set when determining the PCC rule.

[0360] Exemplarily, the first core network function node 102 - 1 uses the DSCP mapping of the PDU set correlation as one of the conditions for determining the PCC rule.

[0361] The present disclosure does not limit the specific solution of DSCP mapping that considers PDU set relevance when the first core network function node 102-1 determines the PCC rule.

[0362] Step S2103 : The first core network function node 102 - 1 sends a first response message to the AF function node 101 .

[0363] In some embodiments, the first response message is used to respond to the first message.

[0364] In an example, the first message may be an AF session creation (Nnef_AFsessionWithQoS_Create) request message, and the first response message may be an AF session creation response (Nnef_AFsessionWithQoS_Create response) message.

[0365] In an example, the first message may be an AF session update (Nnef_AFsessionWithQoS_Update) request message, and the first response message may be an AF session update response (Nnef_AFsessionWithQoS_Update response) message.

[0366] In some embodiments, the AF function node 101 receives the first response message.

[0367] In some embodiments, the AF function node 101 determines, based on the first response message, that the first core network function node 102 - 1 considers the DSCP mapping of the PDU set correlation when determining the PCC rule.

[0368] Step S2104: The first core network function node 102-1 sends a second message to the second core network function node 102-2.

[0369] In some embodiments, the second core network function node 102-2 receives the second message, and the second core network function node 102-2 may be an SMF device.

[0370] In some embodiments, the second message is used to initiate a session management policy control update request.

[0371] Exemplarily, the second message may be an Npcf_SMPolicyControl_UpdateNotify request message.

[0372] In some embodiments, the second message may include but is not limited to at least one of the following:

[0373] A DSCP tag value obtained after performing DSCP mapping related to the PDU set;

[0374] Second indication information; the second indication information is used to instruct the second core network function node to provide the DSCP mapping associated with the PDU set to the third core network function node;

[0375] The PCC rules.

[0376] Exemplarily, the first core network function node 102 - 1 may perform DSCP mapping related to the PDU set, and send the obtained DSCP label value to the second core network function node 102 - 2 via a second message.

[0377] The way in which the first core network function node 102 - 1 determines the DSCP label value is similar to the way in which the AF function node 101 determines the DSCP label value, and is not described again here.

[0378] Exemplarily, the first core network function node 102-1 may send second indication information to the second core network function node 102-2 via a second message, where the second indication information is used to instruct the second core network function node to provide the DSCP mapping associated with the PDU set to the third core network function node 102-3. The third core network function node 102-3 may be a UPF.

[0379] Exemplarily, the first core network function node 102-1 may send the determined PCC rule to the second core network function node 102-2 via a second message.

[0380] Exemplarily, the PCC rule may include at least one of a DSCP tag value and the second indication information.

[0381] In some embodiments, the name of the second message is not limited and can be interchangeable with a session management policy control update request message, a request message, etc.

[0382] Step S2105: The second core network function node 102-2 sends a second response message to the first core network function node 102-1.

[0383] In some embodiments, the first core network function node 102 - 1 receives the second response message.

[0384] In some embodiments, the second response message is used to respond to the second message.

[0385] In some embodiments, the second response message may be a session management policy control update response message. Exemplarily, the second response message is an Npcf_SMPolicyControl_UpdateNotify response message.

[0386] In some embodiments, the first core network function node 102-1 determines based on the second response message that the second core network function node 102 initiates the SM policy management modification process, and the process considers the DSCP mapping of the PDU set correlation

[0387] Step S2106: The second core network function node 102-2 sends a third message to the third core network function node 102-3.

[0388] In some embodiments, the third core network function node 102 - 3 receives the third message.

[0389] In some embodiments, the third core network function node 102-3 may be a UPF device.

[0390] In some embodiments, the third message is used to initiate a session modification request.

[0391] Exemplarily, the third message may be an N4 Session Modification Request message.

[0392] In some embodiments, the name of the third message is not limited and can be interchangeable with a session modification request message, a request message, etc.

[0393] In some embodiments, the third message is used to provide the third core network function node 102-3 with a DSCP mapping associated with the PDU set.

[0394] In some embodiments, the third message includes but is not limited to at least one of the following:

[0395] A DSCP tag value obtained after performing DSCP mapping related to the PDU set;

[0396] The third indication information is used to instruct the third core network function node to add a DSCP tag value to the PDU outer header of the PDU set of the downlink packet;

[0397] QoS rules.

[0398] Exemplarily, the second core network function node 102 - 2 may perform DSCP mapping related to the PDU set, and provide the obtained DSCP label value to the third core network function node 102 - 3 via a third message.

[0399] The manner in which the second core network function node 102 - 2 determines the DSCP label value is similar to the manner in which the AF function node 101 determines the DSCP label value, and thus will not be described in detail here.

[0400] Exemplarily, the second core network function node 102-2 can send third indication information to the third core network function node 102-3 via a third message, and the third indication information is used to instruct the third core network function node to add a DSCP tag value to the PDU outer header of the PDU set of the downlink packet, thereby achieving improvement of the transport layer.

[0401] For example, the second core network function node 102-2 may derive QoS parameters and determine QoS rules based on the PCC rules included in the second message, and then provide the QoS rules to the third core network function node 102-3 via a third message, for installation and execution by the third core network function node 102-3.

[0402] Step S2107: The third core network function node 102-3 adds a DSCP label value to the PDU outer header of the PDU set of the downlink packet.

[0403] In some embodiments, the third core network function node 102 - 3 adds the DSCP tag value to the PDU outer header of the PDU set of the downlink packet.

[0404] The DSCP tag value may be obtained by the third core network function node 102 - 3 after performing DSCP mapping related to the PDU set.

[0405] Alternatively, the DSCP tag value may be determined by one or more of the AF function node 101, the first core network function node 102-1, and the second core network function node 102-1, and then provided by the second core network function node 102-3 to the third core network function node 102-3 via a third message.

[0406] Step S2108: The third core network function node 102-3 sends a third response message to the second core network function node 102-2.

[0407] In some embodiments, the third response message is used to respond to the third message.

[0408] Exemplarily, the third message is an N4 Session Modification Request message, and the third response message may be an N4 Session Modification Response message.

[0409] Step S2109 : The second core network function node 102 - 2 sends a fourth message to the access network device 103 .

[0410] In some embodiments, the fourth message is used to provide the access network device 103 with a DSCP mapping associated with the PDU set.

[0411] In some embodiments, the second core network function node 102-2 may send the content of the fourth message to the access network device 103 through the fifth core network function node 102-5. The fifth core network function node 102-5 may be an AMF device.

[0412] Exemplarily, the second core network function node 102-2 sends an N1N2 message switching message, such as a Namf_Communication_N1N1Message Tranfer message, to the fifth core network function node 102-5, thereby providing the fifth core network function node 102-5 with a DSCP mapping associated with a PDU set.

[0413] Furthermore, the fifth core network function node 102 - 5 responds to the N1N2 message switching message and provides the access network device 103 with a DSCP mapping associated with the PDU set through an N2 message.

[0414] In some embodiments, the fourth message may include, but is not limited to, at least one of the following:

[0415] A DSCP tag value obtained after performing DSCP mapping related to the PDU set;

[0416] Fourth indication information, the fourth indication information is used to instruct the access network device 103 to use DSCP information;

[0417] DSCP profile.

[0418] In some embodiments, the access network device 103 sends a fourth response message to the second core network function node 102 - 2 (not shown in FIG. 2A ).

[0419] Exemplarily, the access network device 103 may send an N2 message to the fifth core network function node 102-5. Further, the fifth core network function node 102-5 may send an SM context update request message, such as an Nsmf_PDUSession_UpdateSMContext Request message, to the second core network function node. The second core network function node 102-2 updates the SM context and returns an SM context update response message, such as an Nsmf_PDUSession_UpdateSMContext Response message, to the fifth core network function node 102-5.

[0420] It should also be noted that the second core network function node 102-2 may further send an N4 session modification request message (not shown in FIG. 2A ), such as an N4 Session Modification Request message, to the third core network function node 102-3, and receive an N4 session modification response message, such as an N4 Session Modification Response message, returned by the third core network function node 102-3, thereby completing the PDU session modification process.

[0421] Step S2110 , the access network device 103 determines and uses DSCP information.

[0422] In some embodiments, the access network device 103 may determine the DSCP information through the DSCP profile and then use the DSCP information, that is, the access network device 103 may try the QoS profile associated with the DSCP mapping associated with the PDU set.

[0423] In some embodiments, DSCP information includes but is not limited to DSCP tag value, priority information, etc.

[0424] Step S2111: The access network device 103 replaces the historical DSCP information with the determined DSCP information.

[0425] In some embodiments, the access network device 103 may replace the previously stored DSCP information after determining the DSCP information.

[0426] Step S2112 : The second core network function node 102 - 2 sends a fifth message to the terminal 104 .

[0427] In some embodiments, the second core network function node 102 - 2 may send the fifth message to the terminal 104 through the fifth core network function node 102 - 5 and the access network device 103 .

[0428] In some embodiments, the second core network function node 102 - 2 may send a fifth message to the terminal 104 through the access network device 103 .

[0429] In some embodiments, terminal 104 receives the fifth message.

[0430] In some embodiments, the terminal 104 may return a fifth response message to the second core network function node 102-2 through the access network device 103 and the fifth core network function node 102-5 (not shown in FIG. 2A).

[0431] In some embodiments, the fifth message is used to provide the terminal 104 with a DSCP mapping associated with the PDU set.

[0432] In some embodiments, the fifth message may include, but is not limited to, at least one of the following:

[0433] A DSCP tag value obtained after performing DSCP mapping related to the PDU set;

[0434] The fifth indication information is used to instruct the terminal 104 to add a DSCP label value to the PDU outer header of the PDU set of the uplink packet.

[0435] In step S2113 , the terminal 104 adds a DSCP tag value to the PDU outer header of the PDU set of the uplink packet.

[0436] In some embodiments, the terminal 104 may perform DSCP mapping of the PDU set correlation, and add the obtained DSCP tag value to the PDU outer header of the PDU set of the uplink packet.

[0437] In some embodiments, at least one of the AF function node 101, the first core network function node 102-1, the second core network function node 102-2, and the third core network function node 102-3 may perform DSCP mapping of the PDU set correlation to obtain a DSCP label value, which is then sent by the third core network function node 102-3 to the terminal 104 via a fifth message. The terminal 104 adds the DSCP label value to the PDU outer header of the PDU set of the uplink packet.

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

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

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

[0441] In some embodiments, the information transmission method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2113. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, step S2101+S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2101+step S2102+step S2103 can be implemented as an independent embodiment, step S2104 can be implemented as an independent embodiment, step S2105 can be implemented as an independent embodiment, step S2104+S2105 can be implemented as an independent embodiment, step S2106 can be implemented as an independent embodiment, step S2107 can be implemented as an independent embodiment, step S2108 can be implemented as an independent embodiment, and step S2109 can be implemented as an independent embodiment. 06+step S2107+step S2108 can be implemented as an independent embodiment, step S2109 can be implemented as an independent embodiment, step S2110 can be implemented as an independent embodiment, step S2109+step S2110 can be implemented as an independent embodiment, step S2111 can be implemented as an independent embodiment, step S2109+step S2110+step S2111 can be implemented as an independent embodiment, step S2112 can be implemented as an independent embodiment, step S2113 can be implemented as an independent embodiment, step S2112+step S2113 can be implemented as an independent embodiment, and steps S2101 to S2113 can be implemented as independent embodiments, but are not limited thereto.

[0442] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the first core network function node obtains the first message from other execution entities, step S2101 may not be performed.

[0443] In some embodiments, step S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the first core network function node 102-1 does not need to determine the PCC rule, step S2102 may not be performed.

[0444] In some embodiments, step S2103 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the AF function node does not send the first message or the AF function node receives the first response message from another execution entity, step S2103 may not be performed.

[0445] In some embodiments, step S2104 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the second core network function node 102-2 obtains the second message from another execution entity, step S2104 may not be performed.

[0446] In some embodiments, step S2105 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the first core network function node 102-1 does not send the second message or the first core network function node 102-1 receives the second response message from another execution entity, step S2105 may not be performed.

[0447] In some embodiments, step S2106 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the third core network function node 102-3 obtains the third message from another execution entity, step S2106 may not be performed.

[0448] In some embodiments, step S2107 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the third core network function node 102-3 does not need to add a DSCP tag value to the PDU outer header of the PDU set of the downlink packet, step S2107 may not be performed.

[0449] In some embodiments, step S2108 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the second core network function node 102-2 does not send the third message or obtain the third response message from other execution entities, step S2108 may not be performed.

[0450] In some embodiments, step S2109 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the access network device 103 obtains the fourth message from another execution subject, step S2109 may not be performed.

[0451] In some embodiments, step S2111 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the access network device does not store historical DSCP information, step S2111 may not be performed.

[0452] In some embodiments, step S2112 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the terminal 104 obtains the fourth message from another execution subject, step S2112 may not be performed.

[0453] In some embodiments, step S2113 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the terminal 104 does not need to add a DSCP tag to the PDU outer header of the PDU set of the uplink packet, step S2113 may not be performed.

[0454] In some embodiments, the order of steps S2109 to S2111 and steps S2112 to S2113 can be interchanged. For example, steps S2109 to S2111 can be performed first, and then steps S2112 to S2113, or steps S2112 to S2113 can be performed first, and then steps S2109 to S2111.

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

[0456] In the above embodiments, when creating or updating an AF session, the PDU set characteristics can be considered, the resource scheduling and configuration of the transport layer can be optimized, the end-to-end QoS requirements can be effectively guaranteed, the resource requirements and allocation can be better adapted, and the end-to-end QoS resources can be coordinated.

[0457] FIG2B is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG2B , the present disclosure embodiment relates to an information transmission method, which includes:

[0458] In step S2201, the AF function node 101 sends a first message to the fourth core network function node 102-4.

[0459] Among them, the fourth core network function node 102-4 can be a NEF device.

[0460] In some embodiments, if the AF function node 101 is not an untrusted AF function node, the AF function node 101 may first send the first message to the fourth core network function node 102 - 4 so that the fourth core network function node 102 - 4 authorizes the AF function node 101 .

[0461] The implementation method of step S2201 is similar to that of step S2101, except that the receiving end devices involved are different. The specific implementation process will not be repeated here.

[0462] Step S2202: The fourth core network function node 102-4 authorizes the first message.

[0463] In some embodiments, the fourth core network function node 102-4 performs relevant mapping to authorize the first message, i.e., the AF request. Exemplarily, the mapping content includes at least one of the following:

[0464] Identify the mapping of XRM services (AF-Service-Identifier) ​​to DNN and S-NSSAI;

[0465] Mapping of external applications to core network application identifiers;

[0466] Mapping of external terminal identifiers to terminal identifiers within the core network, such as Subscription Permanent Identifiers (SUPI), based on Unified Data Management (UDM) contract information;

[0467] Perform mapping of external to internal XRM business group identifiers based on UDM contract information.

[0468] The internal can be understood as the inside of the communication network provided by the operator, and the external can be understood as the third-party application corresponding to the AF function node.

[0469] Step S2203: The fourth core network function node 102-4 sends a sixth message to the first core network function node 102-1.

[0470] In some embodiments, the fourth core network function node 102-4 may determine whether it is necessary to call the sixth core network function node 102-6 based on the parameters provided by the AF function node 101. The sixth core network function node 102-6 may be a TSCTSF device.

[0471] For example, if fourth core network function node 102-4 determines, based on the first message, that the service has a high latency sensitivity, fourth core network function node 102-4 may determine that it needs to call sixth core network function node 102-6. In this case, fourth core network function node 102-4 may send a sixth message to sixth core network function node 102-6. Upon receiving the message, sixth core network function node 102-6 may associate the time synchronization service request with the PCF's AF session. Furthermore, sixth core network function node 102-6 may send the sixth message to first core network function node 102-1, which may be a PCF device.

[0472] The sixth message may include but is not limited to the message content of the first message.

[0473] For example, the fourth core network function node 102-4 determines, based on the first message, that the service has low delay sensitivity. Then, the fourth core network function node 102-4 may determine that there is no need to call the sixth core network function node 102-6. The fourth core network function node 102-4 may send the sixth message directly to the first core network function node 102-1. The first core network function node 102-1 may be a PCF device.

[0474] The sixth message may be a policy authorization creation request (Npcf_PolicyAuthorization_Create request) message.

[0475] The sixth message may also include QoS requirement information and other information that can be used by the first core network function node 102-1 to determine PCC rules.

[0476] Step S2204: The first core network function node 102-1 determines a PCC rule.

[0477] In some embodiments, the implementation of step S2204 is similar to the implementation of step S2102 described above, and will not be repeated here.

[0478] In step S2205 , the first core network function node 102 - 1 sends a sixth response message to the fourth core network function node 102 - 4 .

[0479] In some embodiments, the sixth response message may be a policy authorization create response message, such as an Npcf_PolicyAuthorization_Create response message.

[0480] Step S2206 : The fourth core network function node 102 - 4 sends a first response message to the AF function node 101 .

[0481] In some embodiments, the implementation of step S2206 is similar to the implementation of step S2103 described above, and will not be repeated here.

[0482] In some embodiments, the first response message also includes the authorization result.

[0483] Step S2207: The first core network function node 102-1 sends a second message to the second core network function node 102-2.

[0484] In some embodiments, the implementation of step S2207 is similar to the implementation of step S2104 described above, and will not be repeated here.

[0485] Step S2208: The second core network function node 102-2 sends a second response message to the first core network function node 102-1.

[0486] In some embodiments, the implementation of step S2208 is similar to the implementation of step S2105 described above and will not be repeated here.

[0487] Step S2209: The second core network function node 102-2 sends a third message to the third core network function node 102-3.

[0488] In some embodiments, the implementation of step S2209 is similar to the implementation of step S2106 described above, and will not be repeated here.

[0489] Step S2210: The third core network function node 102-3 adds a DSCP tag value to the PDU outer header of the PDU set of the downlink packet.

[0490] In some embodiments, the implementation of step S2210 is similar to the implementation of step S2107 described above and will not be repeated here.

[0491] Step S2211: The third core network function node 102-3 sends a third response message to the second core network function node 102-2.

[0492] In some embodiments, the implementation of step S2211 is similar to the implementation of step S2108 described above and will not be repeated here.

[0493] Step S2212 : The second core network function node 102 - 2 sends a fourth message to the access network device 103 .

[0494] In some embodiments, the implementation of step S2212 is similar to the implementation of step S2109 described above and will not be repeated here.

[0495] Step S2213 , the access network device 103 determines and uses DSCP information.

[0496] In some embodiments, the implementation of step S2213 is similar to the implementation of step S2110 described above and will not be repeated here.

[0497] Step S2214: The access network device 103 replaces the historical DSCP information with the determined DSCP information.

[0498] In some embodiments, the implementation of step S2214 is similar to the implementation of step S2111 described above and will not be repeated here.

[0499] Step S2215 , the second core network function node 102 - 2 sends a fifth message to the terminal 104 .

[0500] In some embodiments, the implementation of step S2215 is similar to the implementation of step S2112 described above and will not be repeated here.

[0501] In step S2216, the terminal 104 adds a DSCP tag value to the PDU outer header of the PDU set of the uplink packet.

[0502] In some embodiments, the implementation of step S2216 is similar to the implementation of step S2113 described above and will not be repeated here.

[0503] In some embodiments, the information transmission method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2216.

[0504] In some embodiments, steps S2201 to S2203 are optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, steps S2201 to S2203 may be replaced by step S2101.

[0505] In some embodiments, steps S2205 to S2206 are optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, steps S2205 to S2206 may be replaced by step S2103.

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

[0507] In the above embodiments, when creating or updating an AF session, the PDU set characteristics can be considered, the resource scheduling and configuration of the transport layer can be optimized, the end-to-end QoS requirements can be effectively guaranteed, the resource requirements and allocation can be better adapted, and the end-to-end QoS resources can be coordinated.

[0508] FIG3A is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to an information transmission method, which can be executed by an AF function node 101. The method includes:

[0509] Step S3101, sending the first message.

[0510] In some embodiments, the AF function node 101 may send a first message to the first core network function node 102 - 1 .

[0511] In some embodiments, the AF function node 101 may send a first message to the fourth core network function node 102 - 4 .

[0512] In some embodiments, the optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0513] Step S3102: Obtain a first response message.

[0514] In some embodiments, the AF function node 101 may obtain the first response message from the first core network function node 102 - 1 , but is not limited thereto. The AF function node 101 may also receive the first response message sent by other entities, such as the fourth core network function node.

[0515] In some embodiments, the AF function node 101 obtains a first response message determined according to a predefined rule.

[0516] In some embodiments, the AF function node 101 performs processing to obtain the first response message.

[0517] In some embodiments, step S3102 is omitted, the AF function node 101 autonomously implements the function indicated by the first response message, or the AF function node 101 obtains the first response message based on predefined rules or protocol agreements, or the above function is default or default.

[0518] In some embodiments, the optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0519] In some embodiments, the operation processing method involved in the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, and steps S3101+S3102 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0520] In the above embodiment, the AF function node may provide the first core network function node with a DSCP mapping associated with a PDU set, so that the PDU set characteristics are considered during the process of creating or updating an AF session, thereby achieving high availability.

[0521] FIG3B is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to an information transmission method, which can be executed by the first core network function node 102-1. The method includes:

[0522] Step S3201, obtain the first message.

[0523] In some embodiments, the first core network function node 102-1 can obtain the first message from the AF function node 101, but is not limited to this. It can also receive a sixth message sent by other entities, such as the fourth core network function node 102-4, to determine the message content of the first message.

[0524] In some embodiments, the first core network function node 102 - 1 obtains a first message determined according to a predefined rule.

[0525] In some embodiments, the first core network function node 102 - 1 performs processing to obtain the first message.

[0526] In some embodiments, step S3201 is omitted, the first core network function node 102-1 autonomously implements the function indicated by the first message, or the first core network function node 102-1 obtains the first message based on predefined rules or protocol agreements, or the above functions are default or default.

[0527] In some embodiments, the optional implementation of step S3201 can refer to the optional implementation of step S2101 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0528] Step S3202: Determine PCC rules.

[0529] In some embodiments, the optional implementation of step S3202 can refer to the optional implementation of step S2102 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0530] Step S3203: Send a first response message.

[0531] In some embodiments, the first core network function node 102 - 1 may send a first response message to the AF function node 101 or the fourth core network function node 101 - 4 .

[0532] In some embodiments, the optional implementation of step S3203 can refer to the optional implementation of step S2103 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0533] Step S3204, sending the second message.

[0534] In some embodiments, the first core network function node 102-1 may send a second message to the second core network function node 102-2.

[0535] In some embodiments, the optional implementation of step S3204 can refer to the optional implementation of step S2104 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0536] Step S3205: Obtain a second response message.

[0537] In some embodiments, the first core network function node 102-1 may obtain the second response message from the second core network function node 102-2, but is not limited thereto. The first core network function node 102-1 may also receive a second response message sent by other entities.

[0538] In some embodiments, the first core network function node 102 - 1 obtains a second response message determined according to a predefined rule.

[0539] In some embodiments, the first core network function node 102 - 1 performs processing to obtain the second response message.

[0540] In some embodiments, step S3205 is omitted, the first core network function node 102-1 autonomously implements the function indicated by the second response message, or the first core network function node 102-1 obtains the second response message based on predefined rules or protocol agreements, or the above function is default or default.

[0541] In some embodiments, the optional implementation of step S3205 can refer to the optional implementation of step S2105 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0542] In some embodiments, the operation processing method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3205. For example, step S3201 can be implemented as an independent embodiment, step S3202 can be implemented as an independent embodiment, steps S3201+S3202 can be implemented as an independent embodiment, step S3203 can be implemented as an independent embodiment, steps S3201+S3202+step S3203 can be implemented as an independent embodiment, step S3204 can be implemented as an independent embodiment, step S3205 can be implemented as an independent embodiment, steps S3204+S3205 can be implemented as an independent embodiment, and steps S3201 to S3205 can be implemented as independent embodiments, but are not limited thereto.

[0543] In the above embodiment, the first core network function node can consider the DSCP mapping associated with the PDU set when determining the PCC rule. It can also provide the DSCP mapping associated with the PDU set to the second core network function node. This streamlines transport layer resource scheduling and configuration, effectively ensuring end-to-end QoS requirements, better adapting resource demand and allocation, and coordinating end-to-end QoS resources.

[0544] FIG3C is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to an information transmission method, which can be executed by the second core network function node 102-2. The method includes:

[0545] Step S3301, obtain the second message.

[0546] In some embodiments, the second core network function node 102-2 may obtain the second message from the first core network function node 102-1, but is not limited thereto and may also receive the second message sent by other entities.

[0547] In some embodiments, the second core network function node 102 - 2 obtains a second message determined according to a predefined rule.

[0548] In some embodiments, the second core network function node 102 - 2 performs processing to obtain the second message.

[0549] In some embodiments, step S3301 is omitted, the second core network function node 102-2 autonomously implements the function indicated by the second message, or the second core network function node 102-2 obtains the second message based on predefined rules or protocol agreements, or the above functions are default or default.

[0550] In some embodiments, the optional implementation of step S3301 can refer to the optional implementation of step S2104 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0551] Step S3302: Send a second response message.

[0552] In some embodiments, the second core network function node 102-2 may send a second response message to the first core network function node 102-1.

[0553] In some embodiments, the optional implementation of step S3302 can refer to the optional implementation of step S2105 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0554] Step S3303, sending the third message.

[0555] In some embodiments, the second core network function node 102-2 may send a second message to the third core network function node 102-3.

[0556] In some embodiments, the optional implementation of step S3303 can refer to the optional implementation of step S2106 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0557] Step S3304: Obtain a third response message.

[0558] In some embodiments, the second core network function node 102-2 may obtain the third response message from the third core network function node 102-3, but is not limited thereto and may also receive a third response message sent by other entities.

[0559] In some embodiments, the second core network function node 102 - 2 obtains a third response message determined according to a predefined rule.

[0560] In some embodiments, the second core network function node 102 - 2 performs processing to obtain the third response message.

[0561] In some embodiments, step S3304 is omitted, the second core network function node 102-2 autonomously implements the function indicated by the third response message, or the second core network function node 102-2 obtains the third response message based on predefined rules or protocol agreements, or the above functions are default or default.

[0562] In some embodiments, the optional implementation of step S3304 can refer to the optional implementation of step S2108 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0563] Step S3305: Send the fourth message.

[0564] In some embodiments, the second core network function node 102 - 2 may send a fifth message to the access network device 103 .

[0565] In some embodiments, the optional implementation of step S3305 can refer to the optional implementation of step S2109 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0566] Step S3306, sending the fifth message.

[0567] In some embodiments, the second core network function node 102 - 2 may send a fifth message to the terminal.

[0568] In some embodiments, the optional implementation method of step S3306 can refer to the optional implementation method of step S2112 in Figure 2A and other related parts of the embodiment involved in Figure 2A, or the optional implementation method of step S3305 can refer to the optional implementation method of step S2215 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

[0569] In some embodiments, the operation processing method involved in the embodiments of the present disclosure may include at least one of steps S3301 to S3306. For example, step S3301 can be implemented as an independent embodiment, step S3302 can be implemented as an independent embodiment, steps S3301+S3302 can be implemented as an independent embodiment, step S3303 can be implemented as an independent embodiment, step S3304 can be implemented as an independent embodiment, steps S3303+S3304 can be implemented as an independent embodiment, step S3205 can be implemented as an independent embodiment, step S3206 can be implemented as an independent embodiment, and steps S3301 to S3306 can be implemented as independent embodiments, but are not limited thereto.

[0570] In the above embodiment, the second core network function node can provide a DSCP mapping associated with a PDU set to multiple devices, wherein the third core network function node can add a DSCP tag value to the PDU outer header of the PDU set of the downlink packet based on the DSCP mapping associated with the PDU set. This optimizes resource scheduling and configuration at the transport layer, effectively guarantees end-to-end QoS requirements, better adapts resource requirements and allocation, and coordinates end-to-end QoS resources.

[0571] FIG3D is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3D , the embodiment of the present disclosure relates to an information transmission method, which can be executed by the third core network function node 102-3. The method includes:

[0572] Step S3401, obtain the third message.

[0573] In some embodiments, the third core network function node 102-3 may obtain the third message from the second core network function node 102-2, but is not limited thereto and may also receive the third message sent by other entities.

[0574] In some embodiments, the third core network function node 102 - 3 obtains a third message determined according to a predefined rule.

[0575] In some embodiments, the third core network function node 102 - 3 performs processing to obtain the third message.

[0576] In some embodiments, step S3401 is omitted, the third core network function node 102-3 autonomously implements the function indicated by the third message, or the third core network function node 102-3 obtains the third message based on predefined rules or protocol agreements, or the above functions are default or default.

[0577] In some embodiments, the optional implementation of step S3401 can refer to the optional implementation of step S2106 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0578] Step S3402: Add a DSCP tag value.

[0579] In some embodiments, the third core network function node 102 - 3 adds a DSCP tag value on a PDU outer header of a PDU set of a downlink packet.

[0580] In some embodiments, the optional implementation of step S3402 can refer to the optional implementation of step S2107 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0581] Step S3403: Send a third response message.

[0582] In some embodiments, the third core network function node 102-3 sends a third response message to the second core network function node 102-2.

[0583] In some embodiments, the optional implementation of step S3403 can refer to the optional implementation of step S2108 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0584] In some embodiments, the operation processing method involved in the embodiments of the present disclosure may include at least one of steps S3401 to S3403. For example, step S3401 can be implemented as an independent embodiment, step S3402 can be implemented as an independent embodiment, and step S3403 can be implemented as an independent embodiment. Steps S3401 to S3403 can be implemented as independent embodiments, but are not limited thereto.

[0585] In the above embodiment, the third core network function node can add a DSCP tag value to the PDU outer header of the PDU set of the downlink packet, thereby achieving the purpose of considering the characteristics of the PDU set in the process of creating or updating the AF session, optimizing the resource scheduling and configuration of the transport layer, effectively ensuring end-to-end QoS requirements, better adapting to resource requirements and allocation, and coordinating end-to-end QoS resources.

[0586] FIG3E is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3E , the present disclosure embodiment relates to an information transmission method, which can be executed by the access network device 103. The method includes:

[0587] Step S3501, obtain the fourth message.

[0588] In some embodiments, the access network device 103 may obtain the fourth message from the second core network function node 102 - 2 , but is not limited thereto and may also receive the fourth message sent by other entities.

[0589] In some embodiments, the access network device 103 obtains a fourth message determined according to a predefined rule.

[0590] In some embodiments, the access network device 103 performs processing to obtain the fourth message.

[0591] In some embodiments, step S3501 is omitted, the access network device 103 autonomously implements the function indicated by the fourth message, or the access network device 103 obtains the fourth message based on predefined rules or protocol agreements, or the above functions are default or default.

[0592] In some embodiments, the optional implementation of step S3501 can refer to the optional implementation of step S2109 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0593] Step S3502: Determine and use DSCP information.

[0594] In some embodiments, the optional implementation of step S3502 can refer to the optional implementation of step S2110 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0595] Step S3503: Replace historical DSCP information.

[0596] In some embodiments, the optional implementation of step S3503 can refer to the optional implementation of step S2111 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0597] In some embodiments, the operation processing method involved in the embodiments of the present disclosure may include at least one of steps S3501 to S3503. For example, step S3501 can be implemented as an independent embodiment, step S3502 can be implemented as an independent embodiment, and step S3503 can be implemented as an independent embodiment. Steps S3501 to S3503 can be implemented as independent embodiments, but are not limited thereto.

[0598] In the above embodiment, the access network device may use DSCP information to facilitate consistent understanding of DSCP tag values ​​by network devices.

[0599] FIG3F is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3F , the embodiment of the present disclosure relates to an information transmission method, which can be executed by terminal 104, and the method includes:

[0600] Step S3601, obtain the fifth message.

[0601] In some embodiments, the terminal 104 may obtain the fifth message from the second core network function node 102 - 2 , but is not limited thereto and may also receive the fifth message sent by other entities.

[0602] In some embodiments, the terminal 104 obtains the fifth message determined according to a predefined rule.

[0603] In some embodiments, the terminal 104 performs processing to obtain the fifth message.

[0604] In some embodiments, step S3601 is omitted, the terminal 104 autonomously implements the function indicated by the fifth message, or the terminal 104 obtains the fifth message based on predefined rules or protocol agreements, or the above functions are default or default.

[0605] In some embodiments, the optional implementation of step S3601 can refer to the optional implementation of step S2112 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0606] Step S3602: Add a DSCP tag value.

[0607] In some embodiments, the optional implementation of step S3602 can refer to the optional implementation of step S2113 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0608] In some embodiments, steps S3601 to S3602 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0609] In the above embodiment, the terminal can add a DSCP tag value to the PDU outer header of the PDU set of the uplink packet. This optimizes uplink transmission, effectively guarantees end-to-end QoS requirements, better adapts resource requirements and allocation, and coordinates end-to-end QoS resources.

[0610] The above content is further illustrated below with examples.

[0611] In the implementation of the present disclosure, DSCP mapping with PDU Set Correlation is newly added.

[0612] The DSCP mapping indication of PDU set correlation PDU set correlation information can be used for DSCP marking on the outer header of the PDU set packet on the N3 / N9 interface in the transport network (ie, to implement differentiated processing of transport packets carrying PDU set correlation).

[0613] PDU set correlation can be used to identify how this PDU set is correlated or dependent on other PDU sets.

[0614] In one example, the PDU set correlation is used to identify at least one of the following:

[0615] The correlation or dependency of a PDU set with other PDU sets within the same QoS flow;

[0616] The correlation or dependency between PDU sets of different QoS flows of the same service;

[0617] The correlation or dependency between PDU sets within a traffic flow of the same service;

[0618] The correlation or dependency between PDU sets between media traffic flows of the same service;

[0619] The correlation or dependency between PDU sets within the same connection stream within the same service connection;

[0620] The correlation or dependency between PDU sets within different streams within a connection channel of the same service.

[0621] The media transport stream traffic flow may include one or more service data streams, which may be XR service streams such as video streams and audio streams.

[0622] Among them, the connection channel connection may include one or more stream-to-stream streams. In the embodiment of the present disclosure, the PDU set correlation is described, which can identify the correlation or dependency between PDU sets at different transmission granularities (for example, within the same QoS flow, between different QoS flows of the same service, within the media transmission flow traffic flow of the same service, between media transmission flow traffic flows of the same service, within the same connection flow stream in the connection channel connection of the same service, and within different connection flow streams in the connection channel connection of the same service), thereby improving the availability and reliability of the PDU set characteristic parameter, namely, the PDU set correlation, effectively guaranteeing the end-to-end QoS requirements, and better coordinating the end-to-end QoS resources.

[0623] The information about the relevance of a PDU set has at least one of the following properties:

[0624] a) A related PDU set is part of a PDU set group.

[0625] b) Each group has a PDU set, which represents an "anchor" PDU set.

[0626] In addition, the PDU set dependency information will indicate the dependent PDU set, which can indicate the following dependencies:

[0627] - The "anchor" PDU set fails to be delivered to the receiver (e.g. due to congestion or retransmission timeout, etc.), and the transmission is abandoned.

[0628] - The previous set of PDUs failed to be delivered to the receiver, aborting the transmission.

[0629] -Cannot satisfy PSDB, abort transfer.

[0630] - Prioritize or deprioritize (the anchor PDU set is prioritized or deprioritized).

[0631] -Change the importance of the PDU set (the anchor PDU set changes the importance of the PDU set).

[0632] The AF function node may provide a DSCP mapping with PDU set relevance to the 5G Core (5G Core, 5GC), where the 5GC includes but is not limited to PCF, SMF, UPF and other devices. The DSCP mapping of the PDU set relevance may be used for PCC determination (e.g., for determining a transport-level packet marking value (e.g., a DSCP value of an outer IP header)).

[0633] AF function node:

[0634] The AF function node may use the Nnef_AFsessionWithQoS_Create request message or the Nnef-AFsessionWithQoS_Update request message to provide a DSCP mapping with PDU set correlation.

[0635] First core network function node (PCF equipment):

[0636] The PCF device considers the DSCP mapping with PDU set relevance to determine the PCC rule and sends the DSCP mapping with PDU set relevance to the second core network function node (SMF device). In addition, the DSCP mapping with PDU set relevance can be sent to the SMF in the PCC rule.

[0637] Second core network function node (SMF equipment):

[0638] The SMF device can provide a DSCP mapping with PDU set relevance to at least one of the third core network function node (UPF device) and the terminal, wherein the UPF maps downlink and the terminal maps uplink to indicate the DSCP tag value taking into account the PDU set relevance and / or PDU set information and related QoS information.

[0639] Third core network function node (UPF equipment):

[0640] Taking into account the PDU set correlation and / or PDU set information and related QoS information, the UPF device will add a DSCP tag value to the outer header of the downlink packet of the PDU set on the N3 / N9 interface in the transport network (i.e., implement differentiated processing of transport packets carrying PDU set correlation).

[0641] Access Network Equipment (RAN):

[0642] NG-RAN implements QoS proflie corresponding to the relevant DSCP, i.e., using DSCP indication or DSCP information taking into account PDU set correlation and / or PDU set information and relevant QoS information for transmission resource allocation.

[0643] If the SMF device provides a DSCP indication or DSCP information to the NG-RAN taking into account the PDU set correlation and / or PDU set information and related QoS information, the NG-RAN shall replace the previously stored DSCP indication or DSCP information with it.

[0644] Figure 4A is an interactive diagram illustrating an information transmission method according to an embodiment of the present disclosure. As shown in Figure 4A, the embodiment of the present disclosure relates to an information transmission method. The following uses the first core network function node as a PCF, the second core network function node as an SMF, the third core network function node as a UPF, and the fourth core network function node as an NEF as an example for explanation. The method includes:

[0645] Step S4101: AF sends an AF session resource creation or update request.

[0646] For example, create or update an AF session through Nnef_AFsessionWithQoS_Create / update request.

[0647] The AF may use the Nnef_AFsessionWithQoS_Create request message or the Nnef-AFsessionWithQoS_Update request message to provide the DSCP mapping with PDU set association.

[0648] The AF provides a DSCP mapping with PDU set correlation to the 5GC (PCF / SMF / UPF) for PCC determination, for example, for determining the marking value of the transport level packet, such as the DSCP tag value of the outer IP header.

[0649] DSCP Mapping of PDU Set Correlation Information indicating PDU Set Correlation can be used for DSCP marking on the outer header of packets of the PDU set on the N3 / N9 interface in the transport network (ie, to implement differentiated processing of transport packets carrying PDU set correlation).

[0650] PDU set correlation is used to identify how this PDU set is correlated or dependent on other PDU sets.

[0651] In one example, the PDU set correlation is used to identify at least one of the following:

[0652] The correlation or dependency of a PDU set with other PDU sets within the same QoS flow;

[0653] The correlation or dependency between PDU sets of different QoS flows of the same service;

[0654] The correlation or dependency between PDU sets within a traffic flow of the same service;

[0655] The correlation or dependency between PDU sets between media traffic flows of the same service;

[0656] The correlation or dependency between PDU sets within the same connection stream within the same service connection;

[0657] The correlation or dependency between PDU sets within different streams within a connection channel of the same service.

[0658] The media transport stream traffic flow may include one or more service data streams, which may be XR service streams such as video streams and audio streams.

[0659] The connection channel connection may include one or more stream connection streams.

[0660] PDU set correlation information has at least one of the following attributes:

[0661] a) A related PDU set is part of a PDU set group.

[0662] b) Each group has a PDU set, which represents an "anchor" PDU set.

[0663] In addition, the PDU set dependency information shall indicate the dependent PDU sets, which may indicate the following dependencies:

[0664] - The "anchor" PDU set fails to be delivered to the receiver (e.g. due to congestion or retransmission timeout, etc.), and the transmission is abandoned.

[0665] - The previous set of PDUs failed to be delivered to the receiver, aborting the transmission.

[0666] -Cannot satisfy PSDB, abort transfer.

[0667] - Prioritize or deprioritize (the anchor PDU set is prioritized or deprioritized).

[0668] -Change the importance of the PDU set (the anchor PDU set changes the importance of the PDU set).

[0669] Optionally, it carries XRM service information, identifying the XRM service data flow or data flow group (e.g., multi-modal service ID), terminal address information and / or terminal identification information, AF identifier application identification information, flow description information (Flow description(s)), DNN, S-NSSAI, QoS parameters, and other corresponding information. Here, the multi-modal service ID can be used to identify all flows in the XRM service group.

[0670] Step S4102: NEF authorizes AF's request.

[0671] If it is an untrusted AF, the AF request is sent to the PCF through the NEF.

[0672] Optionally, NEF performs relevant mappings, including mapping of the XRM service identifier (AF-Service-Identifier) ​​to DNN and S-NSSAI, mapping of external applications to CN application identifiers; and mapping of external UE identifiers to UE identifiers within the CN based on UDM subscription information (such as SUPI), and mapping of external to internal XRM service group identifiers based on UDM subscription information).

[0673] Step S4103: NEF determines whether to call TSCTSF or directly contact PCF based on the parameters provided by AF.

[0674] The PCF receives the attributes provided by the AF from the NEF or TSCTSF. The NEF triggers the Npcf_PolicyAuthorization_Create request and sends the AF request to the PCF, carrying the indication and QoS requirement information for the PCF policy decision.

[0675] Step S4104: The PCF makes a policy decision. The PCF may determine that updated or new policy information needs to be sent to the SMF.

[0676] The PCF considers the DSCP mapping with PDU set relevance to determine the PCC rule and sends the DSCP mapping with PDU set relevance to the SMF. In addition, the DSCP mapping with PDU set relevance can be sent to the SMF in the PCC rule.

[0677] In step S4105, the PCF responds to the NEF with an Npcf_Policy Authorization_Create response.

[0678] Step S4106: NEF sends a Nnef_AFsessionWithQoS_Create response message to AF, carrying the result information to inform AF whether the request is authorized.

[0679] Step S4107: PCF initiates an SM policy association modification request to SMF.

[0680] The message may be an Npcf_SMPolicyControl_UpdateNotify request message.

[0681] 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., via the N4 session).

[0682] The SMF shall provide the DSCP mapping of PDU set correlation to at least one of the UPF and the terminal (UPF mapping DL, UE mapping UL) to indicate the DSCP label value taking into account the PDU set correlation and / or PDU set information and related QoS information.

[0683] The SMF shall provide the DSCP mapping with PDU set correlation to the UPF and / or NG-RAN and / or terminal to indicate the QoS implementation.

[0684] The SMF derives the QoS parameters of the QoS flow based on the PCC rule information of the PCC rule bound to the QoS flow.

[0685] Step S4108, SMF replies to PCF with an SM policy association modification response.

[0686] The message may be an Npcf_SMPolicyControl_UpdateNotify response message.

[0687] Step S4109: SMF triggers the PDU session modification process and provides the QoS profile to UPF and / or NG-RAN.

[0688] Taking into account the PDU set correlation and / or PDU set information and related QoS information, the PSA UPF will enforce DSCP marking on the outer header of the downlink packet of the PDU set on the N3 / N9 interface in the transport network (i.e., implement differentiated treatment of transport packets carrying PDU set correlation).

[0689] The NG-RAN implements a QoS profile corresponding to the relevant DSCP, i.e., uses the DSCP indication or DSCP information taking into account the PDU set correlation and / or PDU set information and the relevant QoS information for transport resource allocation.

[0690] If the SMF provides a DSCP indication or DSCP information to the NG-RAN taking into account the PDU set correlation and / or PDU set information and the relevant QoS information, the NG-RAN shall replace the previously stored DSCP indication or DSCP information with it.

[0691] 4B , steps S4201 to S4208 are similar to the aforementioned steps S4101 to S4108 and are not described in detail herein. Step S4109 may include the following steps:

[0692] Step S4209, SMF sends an N4 session modification request message to UPF.

[0693] The message may be an N4 Session Modification Request message, through which the SMF provides the UPF with a DSCP mapping associated with a PDU set.

[0694] Step S4210, UPF sends an N4 session modification response message to SMF.

[0695] The message may be an N4 Session Modification Response message.

[0696] Step S4211-1, SMF sends an N1N2 message switching message to AMF.

[0697] Among them, SMF provides the DSCP mapping related to the PDU set to AMF through the Namf_Communication_N1N1Message Tranfer message.

[0698] Step S4211-2: AMF responds to the N1N2 message switching message.

[0699] In step S4212, the AMF sends an N2 message to the RAN device and provides a DSCP mapping associated with the PDU set.

[0700] In step S4213, the RAN device may perform resource scheduling and configuration for the terminal.

[0701] Among them, step S4213 is an optional step.

[0702] Step S4214: The RAN device sends an N2 message to the AMF device in response to the N2 message previously sent by the AMF.

[0703] Step S4215, AMF sends a session management context update request message to SMF.

[0704] The message may be an Nsmf_PDUSession_UpdateSMContext Request message.

[0705] Step S4216, SMF sends a session management context update response message to AMF.

[0706] The message may be an Nsmf_PDUSession_UpdateSMContext Response message.

[0707] Step S4217, SMF sends an N4 session modification request message to UPF.

[0708] The message may be an N4 Session Modification Request message.

[0709] Step S4218, UPF sends an N4 session modification response message to SMF.

[0710] The message may be an N4 Session Modification Response message.

[0711] The above description is merely an exemplary description. The embodiment of DSCP mapping of PDU set correlation in the AF session creation process refers to the aforementioned solution and specific steps, which will not be repeated here.

[0712] The present disclosure also provides an apparatus for implementing any of the above methods. For example, a device is provided that includes units or modules for implementing each step performed by an AF function node in any of the above methods. For another example, another device is provided that includes units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, etc.) in any of the above methods.

[0713] It should be understood that the division of the various units or modules in the above device 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 device, 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.

[0714] 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 (CPU), 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 an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), 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.

[0715] FIG5A is a schematic diagram of the structure of an AF function node proposed in an embodiment of the present disclosure. As shown in FIG5A , the AF function node 5100 may include: a transceiver module 5101 .

[0716] In some embodiments, the above-mentioned transceiver module 5101 is configured to send a first message to a first core network function node, where the first message is used to request the creation or update of an AF session, and the first message is also used to provide the first core network function node with a differentiated services code point DSCP mapping of a packet data unit PDU set correlation.

[0717] Optionally, the above-mentioned transceiver module 5101 is used to execute at least one of the communication steps such as sending and / or receiving performed by the AF function node 5100 in any of the above methods (for example, step S2101, step S2103, step S2201, step S2206, but not limited to these), which are not repeated here.

[0718] FIG5B is a schematic diagram of the structure of a first core network function node according to an embodiment of the present disclosure. As shown in FIG5B , the first core network function node 5200 may include: a transceiver module 5201 and a processing module 5202 .

[0719] In some embodiments, the above-mentioned transceiver module 5201 is configured to receive a first message sent by an application function AF function node, where the first message is used to request the creation or update of an AF session, and the first message is also used to provide a differentiated services code point DSCP mapping associated with a packet data unit PDU set.

[0720] In some embodiments, the processing module 5202 is configured to determine a policy and charging control (PCC) rule; wherein the DSCP mapping of the PDU set correlation is considered when determining the PCC rule.

[0721] Optionally, the above-mentioned transceiver module 5201 is used to execute at least one of the communication steps such as sending and / or receiving performed by the first core network function node 5200 in any of the above methods (for example, step S2101, step S2103, step S2104, step S2105, step S2203, step S2205, step S2207, step S2208, but not limited to these), which are not repeated here.

[0722] Optionally, the above-mentioned processing module 5202 is used to execute at least one of the other steps (such as step S2102 and step S2204, but not limited to these) performed by the first core network function node 5100 in any of the above methods, which will not be repeated here.

[0723] FIG5C is a schematic diagram of the structure of a second core network function node proposed in an embodiment of the present disclosure. As shown in FIG5C , the second core network function node 5300 may include: a transceiver module 5301 .

[0724] In some embodiments, the above-mentioned transceiver module 5301 is configured to receive a second message sent by the first core network function node, which is used to initiate a session management policy control update request, and the second message is also used to provide the second core network function node with a differentiated service code point DSCP mapping of the packet data unit PDU set correlation.

[0725] In some embodiments, the above-mentioned transceiver module 5301 is also configured to send a third message to a third core network function node, wherein the third message is used to initiate a session modification request, and the third message is used to provide the third core network function node with a DSCP mapping of the PDU set correlation.

[0726] Optionally, the above-mentioned transceiver module 5301 is used to execute at least one of the communication steps such as sending and / or receiving performed by the second core network function node 5300 in any of the above methods (for example, step S2104, step S2105, step S2106, step S2108, step S2109, step S2112, step S2207, step S2208, step S2209, step S2211, step S2212, step S2215, but not limited to these), which will not be repeated here.

[0727] FIG5D is a schematic diagram of the structure of a third core network function node proposed in an embodiment of the present disclosure. As shown in FIG5D , the third core network function node 5400 may include: a transceiver module 5401 and a processing module 5402 .

[0728] In some embodiments, the above-mentioned transceiver module 5401 is configured to receive a third message sent by the second core network function node, and the third message is used to initiate a session modification request, and the third message is used to provide the DSCP mapping of the PDU set correlation to the third core network function node.

[0729] In some embodiments, the processing module 5402 is configured to add a DSCP tag value to a PDU outer header of a PDU set of a downlink packet based on the third message.

[0730] Optionally, the above-mentioned transceiver module 5401 is used to execute at least one of the communication steps such as sending and / or receiving performed by the third core network function node 5400 in any of the above methods (for example, step S2106, step S2108, step S2209, step S2211, but not limited to these), which will not be repeated here.

[0731] Optionally, the above-mentioned processing module 5402 is used to execute at least one of the other steps (such as step S2107, step S2210, but not limited to these) performed by the third core network function node 5400 in any of the above methods, which will not be repeated here.

[0732] FIG5E is a schematic diagram of the structure of an access network device according to an embodiment of the present disclosure. As shown in FIG5E , the access network device 5500 may include a transceiver module 5501 and a processing module 5502 .

[0733] In some embodiments, the transceiver module 5501 is configured to receive a fifth message sent by the second core network function node, where the fifth message is used to provide the access network device with a DSCP mapping of the PDU set correlation.

[0734] In some embodiments, the processing module 5502 is configured to determine and use DSCP information based on the fifth message.

[0735] Optionally, the above-mentioned transceiver module 5501 is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S2109, step S2212, but not limited to this) performed by the access network device 5500 in any of the above methods, which will not be repeated here.

[0736] Optionally, the above-mentioned processing module 5502 is used to execute at least one of the other steps (such as step S2110, step S2111, step S2213, step S2214, but not limited to these) performed by the access network device 5500 in any of the above methods, which will not be repeated here.

[0737] FIG5F is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure. As shown in FIG5F , the terminal 5600 may include: a transceiver module 5601 and a processing module 5602 .

[0738] In some embodiments, the transceiver module 5601 is configured to receive a fifth message sent by the second core network function node, where the fifth message is used to provide the terminal with a DSCP mapping associated with the PDU set.

[0739] In some embodiments, the processing module 5602 is configured to add a DSCP tag value to a PDU outer header of a PDU set of an uplink packet based on the fifth message.

[0740] Optionally, the above-mentioned transceiver module 5601 is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S2112, step S2215, but not limited to this) performed by the terminal 5600 in any of the above methods, which will not be repeated here.

[0741] Optionally, the processing module 5602 is used to execute at least one of the other steps (such as step S2113 and step S2216, but not limited thereto) executed by the terminal 5600 in any of the above methods, which will not be repeated here.

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

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

[0744] Figure 6A is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 can be a network device (e.g., an access network device, a core network function node, etc.), an AF function node, or a terminal (e.g., a user equipment, etc.). It can also be 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 an AF function node to implement any of the above methods. Communication device 6100 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.

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

[0746] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs the communication steps such as sending and / or receiving in the above method (e.g., step S2101, step S2103, step S2104, step S2105, step S2106, step S2108, step S2109, step S2112, step S2201, step S2203, step S2205, step S2206, step S2207, step S2208). 08, step S2209, step S2211, step S2212, and step S2215, but not limited thereto), the processor 6101 executes at least one of the other steps (e.g., step S2102, step S2107, step S2110, step S2111, step S2113, step S2202, step S2204, step S2210, step S2213, step S2214, and step S2216, 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, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be interchangeable, the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be interchangeable, and the terms receiver, receiving unit, receiver, and receiving circuit may be interchangeable.

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

[0748] The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited to FIG6A. 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 and 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.

[0749] 6B is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. If the communication device 6100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 6200 shown in FIG6B , but the present disclosure is not limited thereto.

[0750] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.

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

[0752] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., step S2101, step S2103, step S2104, step S2105, step S2106, step S2108, step S2109, step S2112, step S2201, step S2203, step S2205, step S2206, step S2207, step S2208, step S2209, step S2211, step S2212, and step S2215, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above method, for example, means that the interface circuit 6202 performs data exchange between the processor 6201, chip 6200, memory 6203, or transceiver device. In some embodiments, the processor 6201 executes at least one of the other steps (for example, step S2102, step S2107, step S2110, step S2111, step S2113, step S2202, step S2204, step S2210, step S2213, step S2214, step S2216, but not limited to these).

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

[0754] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 executes 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 transient storage medium.

[0755] The present disclosure also provides a program product, which, when executed by the communication device 6100, enables the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0756] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. An information transmission method, characterized in that, The method is executed by an Application Function (AF) function node and includes: Sending a first message to a first core network function node, where the first message is used to request the creation or update of an AF session, and the first message is also used to provide a Differentiated Services Code Point (DSCP) mapping of the Packet Data Unit (PDU) set correlation to the first core network function node.

2. The method according to claim 1, characterized in that, The first message includes at least one of the following: The DSCP label value obtained after performing the DSCP mapping of the PDU set correlation; First indication information; the first indication information is used to indicate that the first core network function node considers the DSCP mapping of the PDU set correlation when determining a Policy and Charging Control (PCC) rule; Association information, where the association information is information associated with performing the DSCP mapping of the PDU set correlation.

3. The method according to claim 2, wherein The association information includes at least one of the following: Service information; where the service information includes multi-modal service identification information, and the multi-modal service identification information is used to identify multiple flows in a service group; Terminal address information and / or terminal identification information; AF identifier application identification information; Flow description information; Data Network Name (DNN); Single Network Slice Selection Assistance Information (S-NSSAI); Quality of Service (QoS) parameters.

4. The method according to any one of claims 1 to 3, characterized in that The method further includes: Receiving a first response message sent by the first core network function node after determining the PCC rule, where the first response message is used to respond to the first message, and the first core network function node considers the DSCP mapping of the PDU set correlation when determining the PCC rule.

5. The method according to any one of claims 1-4, characterized in that, The PDU set correlation is used to identify the correlation or dependency between PDU sets.

6. The method according to claim 5, characterized in that, The PDU set correlation is used to identify at least one of the following: The correlation or dependency of a PDU set with other PDU sets within the same Quality of Service (QoS) flow; The correlation or dependency of PDU sets between different QoS flows of the same service; The correlation or dependency of PDU sets within the media transmission traffic flow of the same service; The correlation or dependency of PDU sets between media transmission traffic flows of the same service; The correlation or dependency of PDU sets within the same connection stream within a connection channel of the same service; The correlation or dependency of PDU sets between different connection streams within a connection channel of the same service.

7. The method according to any one of claims 1-6, characterized in that, The information of the PDU set correlation has at least one of the following attributes: The PDU sets with correlation belong to a PDU group; Each PDU group includes an anchor PDU set; where the PDU set correlation is the correlation or dependency of other PDU sets in the PDU group with respect to the anchor PDU set.

8. The method according to any one of claims 1-7, characterized in that, The information of the PDU set correlation is used to indicate at least one of the following: If the anchor PDU set within the PDU group fails to be transmitted, abandon transmitting other PDU sets within the PDU group; If the previous PDU sets within the PDU group fail to be transmitted, abandon transmitting the subsequent PDU sets within the PDU group that have not been transmitted; The first PDU set does not meet the PDU set delay budget PSDB, and the transmission of the first PDU set is abandoned; The priority of the anchor PDU set within the PDU group is set or changed, and the priorities of other PDUs within the PDU group are also set or changed; The importance of the PDU set of the anchor PDU set within the PDU group changes, and the importance of the PDU sets of other PDU sets within the PDU group also changes accordingly.

9. An information transmission method, characterized in that, The method is executed by a first core network function node and includes: Receiving a first message sent by an application function AF function node, where the first message is used to request the creation or update of an AF session, and the first message is also used to provide a differentiated service code point DSCP mapping of the packet data unit PDU set correlation; Determining a policy and charging control PCC rule; when determining the PCC rule, the DSCP mapping of the PDU set correlation is considered.

10. The method according to claim 9, wherein The first message includes at least one of the following: The DSCP label value obtained after performing the DSCP mapping of the PDU set correlation; where the DSCP label value is added to the external Internet protocol IP header of the PDU set on the first port in the transmission network; First indication information; the first indication information is used to indicate that the first core network function node considers the DSCP mapping of the PDU set correlation when determining the PCC rule; Association information, where the association information is information associated with performing the DSCP mapping of the PDU set correlation.

11. The method according to claim 10, characterized in that, The association information includes at least one of the following: Service information; where the service information includes multi-modal service identification information, and the multi-modal service identification information is used to identify multiple flows in a service group; Terminal address information and / or terminal identification information; AF identifier application identification information; Flow description information; Data network name DNN; Single network slice selection assistance information S-NSSAI; QoS parameters.

12. The method according to any one of claims 9-11, characterized in that, The method further includes: Sending a first response message to the AF function node, where the first response message is used to respond to the first message.

13. The method according to any one of claims 9 to 12, characterized in that The method further includes: Sending a second message to a second core network function node, where the second message is used to initiate a session management policy control update request, and the second message is also used to provide the DSCP mapping of the PDU correlation to the second core network function node.

14. The method according to claim 13, wherein The second message includes at least one of the following: The DSCP label value obtained after performing the DSCP mapping of the PDU set correlation; Second indication information; the second indication information is used to indicate that the second core network function node provides the DSCP mapping of the PDU set correlation to a third core network function node; The PCC rule.

15. The method according to any one of claims 9-14, characterized in that, The PDU set correlation is used to identify the correlation or dependency between PDU sets.

16. The method according to claim 15, wherein The PDU set correlation is used to identify at least one of the following: The correlation or dependency between a PDU set and other PDU sets within the same quality of service QoS flow; The correlation or dependency between PDU sets between different QoS flows of the same service; The correlation or dependency between PDU sets within the traffic flow of the media transmission flow of the same service; The correlation or dependency relationship of the PDU sets among the media traffic flows of the same service; The correlation or dependency relationship of the PDU sets within the same connection stream in the connection channel of the same service; The correlation or dependency relationship of the PDU sets in different connection streams within the connection channel of the same service.

17. The method according to any one of claims 9-16, characterized in that, The information on the PDU set correlation has at least one of the following attributes: The PDU sets with correlation belong to a PDU group; Each PDU group includes an anchor PDU set; wherein, the PDU set correlation is the correlation or dependency relationship of the other PDU sets in the PDU group relative to the anchor PDU set.

18. The method according to any one of claims 9-17, characterized in that, The information on the PDU set correlation is used to indicate at least one of the following: If the anchor PDU set within the PDU group is not successfully transmitted, abandon transmitting the other PDU sets within the PDU group; If the previous PDU sets within the PDU group are not successfully transmitted, abandon transmitting the subsequent PDU sets within the PDU group that have not been transmitted; If the first PDU set does not meet the PDU set delay budget (PSDB), abandon transmitting the first PDU set; If the priority of the anchor PDU set within the PDU group is set or changed, the priorities of the other PDU sets within the PDU group are also set or changed; If the importance of the PDU set of the anchor PDU set within the PDU group changes, the importance of the PDU sets of the other PDU sets within the PDU group also changes accordingly.

19. An information transmission method, characterized in that, The method is executed by a second core network function node and includes: Receiving a second message sent by a first core network function node, which is used to initiate a session management policy control update request, and the second message is also used to provide a differentiated service code point (DSCP) mapping of the packet data unit (PDU) set correlation to the second core network function node; Sending a third message to a third core network function node, the third message is used to initiate a session modification request, and the third message is used to provide the DSCP mapping of the PDU set correlation to the third core network function node.

20. The method according to claim 19, wherein The second message includes at least one of the following: The DSCP label value obtained after performing the DSCP mapping of the PDU set correlation; Second indication information; the second indication information is used to indicate that the second core network function node provides at least the DSCP mapping of the PDU set correlation to the third core network function node; The PCC rule.

21. The method according to claim 20, wherein The method further includes: Deriving quality of service (QoS) parameters based on the PCC rule included in the second message, and determining QoS rules.

22. The method according to any one of claims 19-21, characterized in that, The third message includes at least one of the following: The DSCP label value obtained after performing the DSCP mapping of the PDU set correlation; Third indication information; the third indication information is used to indicate that the third core network function node adds a DSCP label value to the PDU outer header of the PDU set of the downlink packet; QoS rules.

23. The method according to any one of claims 19 - 22, characterized in that, The method further includes at least one of the following: Sending a fourth message to an access network device, the fourth message is used to provide the DSCP mapping of the PDU set correlation to the access network device; Send a fifth message to the terminal, where the fifth message is used to provide the DSCP mapping of the PDU set correlation to the terminal.

24. The method according to any one of claims 19-23, characterized in that, The method further includes: Send a second response message to the first core network function node, where the second response message is used to respond to the second message.

25. The method according to any one of claims 19-24, characterized in that, The PDU set correlation is used to identify the correlation or dependency between PDU sets.

26. The method according to claim 25, characterized in that, The PDU set correlation is used to identify at least one of the following: The correlation or dependency of one PDU set with other PDU sets within the same Quality of Service (QoS) flow; The correlation or dependency of PDU sets between different QoS flows of the same service; The correlation or dependency of PDU sets within the media traffic flow of the same service; The correlation or dependency of PDU sets between media traffic flows of the same service; The correlation or dependency of PDU sets within the same connection stream within the connection channel of the same service; The correlation or dependency of PDU sets within different connection streams within the connection channel of the same service.

27. The method according to any one of claims 19-26, characterized in that, The information of the PDU set correlation has at least one of the following attributes: The PDU sets with correlation belong to a PDU group; Each PDU group includes an anchor PDU set; where the PDU set correlation is the correlation or dependency of other PDU sets in the PDU group relative to the anchor PDU set.

28. The method according to any one of claims 19-27, characterized in that The information of the PDU set correlation is used to indicate at least one of the following: If the anchor PDU set within the PDU group fails to be transmitted successfully, abandon transmitting other PDU sets within the PDU group; If the previous PDU set within the PDU group fails to be transmitted successfully, abandon transmitting the subsequent PDU sets within the PDU group that have not been transmitted; If the first PDU set does not meet the PDU Set Delay Budget (PSDB), abandon transmitting the first PDU set; If the priority of the anchor PDU set within the PDU group is set or changed, the priorities of other PDU sets within the PDU group are also set or changed; If the importance of the PDU set of the anchor PDU set within the PDU group changes, the importance of the PDU sets of other PDU sets within the PDU group also changes accordingly.

29. An information transmission method, characterized in that, The method is executed by a third core network function node and includes: Receive a third message sent by a second core network function node, where the third message is used to initiate a session modification request, and the third message is used to provide the DSCP mapping of the PDU set correlation to the third core network function node; Based on the third message, add a DSCP label value to the PDU outer header of the PDU set in the downlink packet.

30. The method according to claim 29, wherein The third message includes at least one of the following: The DSCP label value obtained after performing the DSCP mapping of the PDU set correlation; Third indication information; the third indication information is used to indicate that the third core network function node adds a DSCP label value to the PDU outer header of the PDU set in the downlink packet; QoS rules.

31. The method according to claim 29 or 30, characterized in that, The PDU set correlation is used to identify the correlation or dependency between PDU sets.

32. The method according to claim 31, wherein The PDU set correlation is used to identify at least one of the following: The correlation or dependency of one PDU set with other PDU sets within the same Quality of Service (QoS) flow; The correlation or dependency of PDU sets between different QoS flows of the same service; The correlation or dependency of PDU sets within the media traffic flow of the same service; The correlation or dependency of PDU sets between media traffic flows of the same service; The correlation or dependency of PDU sets within the same connection stream within the connection channel of the same service; The correlation or dependency of PDU sets between different connection streams within the connection channel of the same service.

33. The method according to any one of claims 29 to 31, characterized in that, The information of the PDU set correlation has at least one of the following attributes: The PDU sets with correlation belong to a PDU group; Each PDU group includes an anchor PDU set; wherein, the PDU set correlation is the correlation or dependency of other PDU sets in the PDU group with respect to the anchor PDU set.

34. The method according to any one of claims 29-33, characterized in that, The information of the PDU set correlation is used to indicate at least one of the following: If the anchor PDU set within the PDU group fails to be transmitted successfully, abandon transmitting other PDU sets within the PDU group; If the previous PDU sets within the PDU group fail to be transmitted successfully, abandon transmitting the subsequent PDU sets within the PDU group that have not been transmitted; If the first PDU set does not meet the PDU Set Delay Budget (PSDB), abandon transmitting the first PDU set; If the priority of the anchor PDU set within the PDU group is set or changed, the priorities of other PDU sets within the PDU group are also set or changed; If the importance of the PDU set of the anchor PDU set within the PDU group changes, the importance of the PDU sets of other PDU sets within the PDU group also changes accordingly.

35. An information transmission method, characterized in that, The method is executed by an access network device and includes: Receiving a fourth message sent by a second core network function node, where the fourth message is used to provide the DSCP mapping of the PDU set correlation to the access network device; Based on the fourth message, determining and using the DSCP information.

36. The method according to claim 35, characterized in that, The method further includes: Replacing the historical DSCP information with the determined DSCP information.

37. An information transmission method, characterized in that, The method is executed by a terminal and includes: Receiving a fifth message sent by a second core network function node, where the fifth message is used to provide the DSCP mapping of the PDU set correlation to the terminal; Based on the fifth message, adding a DSCP tag value to the PDU outer header of the PDU set of the uplink packet.

38. An application function AF function node, characterized in that, Including: A transceiver module configured to send a first message to a first core network function node, where the first message is used to request the creation or update of an AF session, and the first message is also used to provide the Differentiated Services Code Point (DSCP) mapping of the Packet Data Unit (PDU) set correlation to the first core network function node.

39. A first core network function node, characterized in that, Including: A transceiver module, configured to receive a first message sent by an Application Function (AF) function node, where the first message is used to request the creation or update of an AF session, and the first message is further used to provide a Differentiated Services Code Point (DSCP) mapping for the Packet Data Unit (PDU) set correlation; A processing module, configured to determine a Policy and Charging Control (PCC) rule; wherein, when determining the PCC rule, the DSCP mapping for the PDU set correlation is considered.

40. A second core network function node, characterized in that, Comprising: A transceiver module, configured to receive a second message sent by a first core network function node, where the second message is used to initiate a session management policy control update request, and the second message is further used to provide a DSCP mapping for the PDU set correlation to a second core network function node; The transceiver module is further configured to send a third message to a third core network function node, where the third message is used to initiate a session modification request, and the third message is used to provide the DSCP mapping for the PDU set correlation to the third core network function node.

41. A third core network function node, characterized in that, Comprising: A transceiver module, configured to receive a third message sent by a second core network function node, where the third message is used to initiate a session modification request, and the third message is used to provide the DSCP mapping for the PDU set correlation to the third core network function node; A processing module, configured to add a DSCP label value to the PDU outer header of the PDU set in a downlink packet based on the third message.

42. An access network device, characterized in that, Comprising: A transceiver module, configured to receive a fifth message sent by a second core network function node, where the fifth message is used to provide the DSCP mapping for the PDU set correlation to an access network device; A processing module, configured to determine and use DSCP information based on the fifth message.

43. A terminal, characterized in that, Comprising: A transceiver module, configured to receive a fifth message sent by a second core network function node, where the fifth message is used to provide the DSCP mapping for the PDU set correlation to a terminal; A processing module, configured to add a DSCP label value to the PDU outer header of the PDU set in an uplink packet based on the fifth message.

44. An application function AF function node, characterized in that, Comprising: One or more processors; Wherein, the processor is used to execute the information transmission method according to any one of claims 1-8.

45. A first core network function node, characterized in that, Comprising: One or more processors; Wherein, the processor is used to execute the information transmission method according to any one of claims 9-18.

46. A second core network function node, characterized in that Comprising: One or more processors; Wherein, the processor is used to execute the information transmission method according to any one of claims 19-28.

47. A third core network function node, characterized in that, Comprising: One or more processors; Wherein, the processor is used to execute the information transmission method according to any one of claims 29-34.

48. An access network device, characterized in that, Comprising: One or more processors; Wherein, the processor is used to execute the information transmission method according to claim 35 or 36.

49. A terminal, characterized in that, Comprising: One or more processors; Wherein, the processor is used to execute the information transmission method according to claim 37.

50. A communication system, characterized in that, Comprising: An AF function node, configured to execute the information transmission method according to any one of claims 1-8; The first core network function node is configured to execute the information transmission method described in any one of claims 9-18; The second core network function node is configured to execute the information transmission method described in any one of claims 19-28; The third core network function node is configured to execute the information transmission method described in any one of claims 29-34; The access network device is configured to execute the information transmission method described in claim 35 or 36; The terminal is configured to execute the information transmission method described in claim 37.

51. A storage medium, the storage medium stores instructions, characterized in that, When the instruction runs on the communication device, the communication device is caused to execute the information transmission method described in any one of claims 1-37.

Images