Communication indication methods, first network elements, second network elements, and core network devices

Abstract

The present disclosure relates to communication indication methods, first network elements, second network elements, and core network devices. A method comprises: a first network element sending first information to a second network element, wherein the first information is used for indicating an SDF direction corresponding to QoS handling based on a packet data unit (PDU) set; and the second network element generating at least one PCC rule for the SDF on the basis of the first information. In the present embodiment, the first information is used to indicate the direction corresponding to PDU set handling, thus improving data transmission efficiency.

Description

Communication indication method, first network element, second network element, core network device Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a communication indication method, a first network element, a second network element, and a core network device. Background Art

[0002] In wireless communications, data is required to be transferred between multiple devices, but currently the efficiency of transferring data is low.

[0003] Summary of the Invention

[0004] The present invention aims to solve the problem of low data transmission efficiency existing in related technologies.

[0005] The embodiments of the present disclosure provide a communication indication method, a first network element, a second network element, and a core network device.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication indication method is proposed, which is applied to a first network element. The method includes:

[0007] Sending first information to the second network element, wherein the first information is used to indicate the direction of the service data flow SDF corresponding to the quality of service QoS processing based on the packet data unit PDU set, and the first information is used for the second network element to generate at least one policy and charging control PCC rule for the SDF.

[0008] This embodiment indicates the direction corresponding to the packet data unit PDU set processing through the first information, thereby improving the efficiency of data transmission.

[0009] According to a second aspect of an embodiment of the present disclosure, a communication indication method is proposed, which is applied to a second network element. The method includes: receiving first information sent by a first network element, wherein the first information is used to indicate the direction of processing of a packet data unit PDU set; and generating at least one PCC rule for an SDF based on the first information.

[0010] According to a third aspect of an embodiment of the present disclosure, a communication processing method is proposed, the method comprising: a first network element sends first information to a second network element, wherein the first information is used to indicate an SDF direction corresponding to QoS processing based on a PDU set; the second network element generates at least one PCC rule for the SDF based on the first information.

[0011] According to a fourth aspect of an embodiment of the present disclosure, a first network element is proposed, and the device includes: a transceiver module for sending first information to a second network element, wherein the first information is used to indicate the direction of a service data flow SDF corresponding to the quality of service QoS processing based on a packet data unit PDU set, and the first information is used for the second network element to generate at least one policy and charging control PCC rule for the SDF.

[0012] According to a fifth aspect of an embodiment of the present disclosure, a second network element is provided, the device including:

[0013] The transceiver module is configured to receive first information sent by a first network element, wherein the first information is used to indicate a direction of processing a packet data unit (PDU) set; and the processing module is configured to generate at least one PCC rule for the SDF according to the first information.

[0014] According to a sixth aspect of an embodiment of the present disclosure, a core network device is proposed, comprising: a transceiver module for sending first information to a second network element, wherein the first information is used to indicate a direction corresponding to processing of a packet data unit (PDU) set; or, receiving the first information sent by the first network element; and a processing module for the second network element to generate at least one PCC rule for an SDF based on the first information.

[0015] According to a seventh aspect of an embodiment of the present disclosure, a first network element is proposed, comprising: one or more processors; wherein the second network element is used to execute any one of the communication processing methods in the first aspect.

[0016] According to an eighth aspect of an embodiment of the present disclosure, a second network element is proposed, comprising: one or more processors; wherein the second network element is used to execute any one of the communication processing methods in the second aspect.

[0017] According to a ninth aspect of an embodiment of the present disclosure, a core network device is proposed, comprising: one or more processors; wherein the core network device is used to execute the communication processing method of the third aspect.

[0018] According to the tenth aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a first network element and a second network element, wherein the first network element is configured to implement the communication processing method of any one of the first aspects, and the second network element is configured to implement the communication processing method of any one of the second aspects.

[0019] According to the eleventh aspect of the embodiment of the present disclosure, a storage medium is proposed, which stores instructions, and is characterized in that when the instructions are executed on a communication device, the communication device executes a communication processing method as described in any one of the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0023] FIG2 is an exemplary interaction diagram of a communication indication method provided according to an embodiment of the present disclosure.

[0024] FIG3A is a flow chart illustrating a communication indication method according to an embodiment of the present disclosure.

[0025] FIG3B is a flow chart of a communication indication method according to an embodiment of the present disclosure.

[0026] FIG4A is a flow chart illustrating a communication indication method according to an embodiment of the present disclosure.

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

[0028] FIG5A is an interactive schematic diagram illustrating a communication indication method according to an embodiment of the present disclosure.

[0029] FIG6A is a schematic diagram illustrating a communication indication method according to an embodiment of the present disclosure.

[0030] FIG6B is a schematic diagram illustrating a communication indication method according to an embodiment of the present disclosure.

[0031] FIG6C is a schematic diagram illustrating a communication indication method according to an embodiment of the present disclosure.

[0032] FIG7A is a schematic structural diagram of a first network element proposed in an embodiment of the present disclosure.

[0033] FIG7B is a schematic structural diagram of a second network element proposed in an embodiment of the present disclosure.

[0034] FIG8A is a schematic structural diagram of a communication device 8100 proposed in an embodiment of the present disclosure.

[0035] FIG8B is a schematic structural diagram of a chip 8200 according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0036] The embodiments of the present disclosure provide a communication indication method, a first network element, a second network element, and a core network device.

[0037] In a first aspect, an embodiment of the present disclosure proposes a communication indication method, which is applied to a first network element, and the method includes: sending first information to a second network element, wherein the first information is used to indicate the direction of a service data flow SDF corresponding to the quality of service QoS processing based on a packet data unit PDU set, and the first information is used for the second network element to generate at least one policy and charging control PCC rule for the SDF.

[0038] In the above embodiment, the first information is used to provide the second network element with at least one PCC rule for the SDF to support enhanced processing of the PDU set of the uplink or downlink XRM service data flow, which can more effectively ensure end-to-end QoS requirements, adapt resource requirements and allocation, and improve communication efficiency.

[0039] In combination with some embodiments of the first aspect, in some embodiments, the first information is used to indicate at least one of the following: requesting QoS processing for only the downlink PDU set; requesting QoS processing for only the uplink PDU set; requesting QoS processing for both the downlink PDU set and the uplink PDU set; requesting QoS processing for both the downlink PDU set and the uplink PDU set, and the quality of service QoS parameters corresponding to the downlink PDU set and the uplink PDU set are the same; requesting QoS processing for both the downlink PDU set and the uplink PDU set, and the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different; requesting QoS processing for both the downlink PDU set and the uplink PDU set, and the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are obtained based on the network configuration; requesting QoS processing for both the downlink PDU set and the uplink PDU set, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are the same; requesting QoS processing for both the downlink PDU set and the uplink PDU set, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are different.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the network configuration includes at least one of the following:

[0041] Operator policy, configuration, subscription, terminal side support capabilities, radio access network RAN ​​support capabilities, session management function SMF support capabilities, user plane function UPF support capabilities, policy control function PCF support capabilities, terminal side activation capabilities, RAN activation capabilities, SMF activation capabilities, UPF activation capabilities, PCF activation capabilities.

[0042] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending second information to a second network element, wherein the second information is used to indicate processing requirements of a PDU set in a related direction.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the second information is used to indicate at least one of the following: the uplink direction or downlink direction of the QoS parameters of the PDU set applied to the QoS flow; PDU set-specific QoS characteristics; at least one of the uplink PDU set-specific QoS characteristics and the downlink PDU set-specific QoS characteristics; uplink protocol description or downlink protocol description; related information of the uplink SDF and the downlink SDF.

[0044] In combination with some embodiments of the first aspect, in some embodiments, the PDU set-specific QoS characteristics include at least one of the following: a delay budget of the PDU set; an error rate of the PDU set; integrated processing information of the PDU set; and data flow direction information.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the specific QoS characteristics of the uplink PDU set include at least one of the following: a delay budget of the uplink PDU set; an error rate of the uplink PDU set; and integrated processing information of the uplink PDU set.

[0046] In combination with some embodiments of the first aspect, in some embodiments, the specific QoS characteristics of the downlink PDU set include at least one of the following: a delay budget of the downlink PDU set; an error rate of the downlink PDU set; and integrated processing information of the downlink PDU set.

[0047] In combination with some embodiments of the first aspect, in some embodiments, the relevant information of the uplink SDF and the downlink SDF includes: the pairing ID of the uplink SDF and the downlink SDF; the ratio or threshold of the QoS parameters of the uplink PDU set to the QoS parameters of the downlink PDU set.

[0048] In combination with some embodiments of the first aspect, in some embodiments, sending the first information and the second information to the second network element includes any one of the following: sending the first information and the second information to the second network element through a network open function AF session with a QoS request procedure; sending the first information and the second information to the second network element through an AF session with a QoS request update procedure; sending the first information and the second information to the second network element through service-specific parameter allocation; sending the first information and the second information to the second network element through the AF session policy setting process; sending the first information and the second information to the second network element through a third network element; sending the first information and the second information to the second network element through a fourth network element; sending the first information and the second information to the second network element through the third network element and the fourth network element.

[0049] In combination with some embodiments of the first aspect, in some embodiments, the first network element is an AF network element, the second network element is a policy control function PCF network element, the third network element is a network open function NEF network element, and the fourth network element is a time sensitive communication and time synchronization function TSCTSF network element.

[0050] In the second aspect, an embodiment of the present disclosure proposes a communication indication method, which is applied to a second network element. The method includes: receiving first information sent by a first network element, wherein the first information is used to indicate the direction of a service data flow SDF corresponding to the quality of service QoS processing based on a packet data unit PDU set; generating at least one PCC rule for the SDF based on the first information.

[0051] In the above embodiment, the first information is used to provide the second network element with at least one PCC rule for the SDF to support enhanced processing of the PDU set of the uplink or downlink XRM service data flow, which can more effectively ensure end-to-end QoS requirements, adapt resource requirements and allocation, and improve communication efficiency.

[0052] In combination with some embodiments of the second aspect, in some embodiments, the first information is used to indicate at least one of the following: only requesting QoS processing for the downlink PDU set; only requesting QoS processing for the uplink PDU set; requesting QoS processing for the downlink PDU set and the uplink PDU set; requesting QoS processing for the downlink PDU set and the uplink PDU set, and the quality of service QoS parameters corresponding to the downlink PDU set and the uplink PDU set are the same; requesting QoS processing for the downlink PDU set and the uplink PDU set, and the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different; requesting QoS processing for the downlink PDU set and the uplink PDU set, and the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are obtained based on the network configuration; requesting QoS processing for the downlink PDU set and the uplink PDU set, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are the same; requesting QoS processing for the downlink PDU set and the uplink PDU set, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are different.

[0053] In combination with some embodiments of the second aspect, in some embodiments, the network configuration includes at least one of the following: operator policy, configuration, subscription, terminal side support capability, radio access network RAN ​​support capability, session management function SMF support capability, user plane function UPF support capability, policy control function PCF support capability, terminal side activation capability, RAN activation capability, SMF activation capability, UPF activation capability, PCF activation capability.

[0054] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: receiving second information sent by the first network element, wherein the second information is used to indicate the processing requirements of the PDU set in the relevant direction.

[0055] In combination with some embodiments of the second aspect, in some embodiments, the second information is used to indicate at least one of the following: the uplink direction or downlink direction of the QoS parameters of the PDU set applied to the QoS flow; PDU set-specific QoS characteristics; at least one of the uplink PDU set-specific QoS characteristics and the downlink PDU set-specific QoS characteristics; uplink protocol description or downlink protocol description; related information of the uplink SDF and the downlink SDF.

[0056] In combination with some embodiments of the second aspect, in some embodiments, the PDU set-specific QoS characteristics include at least one of the following: a delay budget of the PDU set; an error rate of the PDU set; integrated processing information of the PDU set; and data flow direction information.

[0057] In combination with some embodiments of the second aspect, in some embodiments, the specific QoS characteristics of the uplink PDU set include at least one of the following: a delay budget of the uplink PDU set; an error rate of the uplink PDU set; and integrated processing information of the uplink PDU set.

[0058] In combination with some embodiments of the second aspect, in some embodiments, the specific QoS characteristics of the downlink PDU set include at least one of the following: a delay budget of the downlink PDU set; an error rate of the downlink PDU set; and integrated processing information of the downlink PDU set.

[0059] In conjunction with some embodiments of the second aspect, in some embodiments, the relevant information of the uplink service data flow SDF and the downlink SDF includes: a pairing ID of the uplink SDF and the downlink SDF; and a ratio or threshold between QoS parameters of the uplink PDU set and QoS parameters of the downlink PDU set. In conjunction with some embodiments of the second aspect, in some embodiments, the PCC rules include PDU set-specific QoS characteristics.

[0060] In combination with some embodiments of the second aspect, in some embodiments, if the data flow direction information indicates that the flow direction is uplink, the PCC rule is applied to the uplink QoS flow in the SDF; if the data flow direction information indicates that the flow direction is downlink, the PCC rule is applied to the downlink QoS flow in the SDF; if the data flow direction information indicates that the flow direction is downlink and downlink, the PCC rule is applied to the uplink QoS flow and the downlink QoS flow in the SDF.

[0061] In combination with some embodiments of the second aspect, in some embodiments, the PCC rule includes at least one of the following: a QoS characteristic specific to an uplink PDU set; a QoS characteristic specific to a downlink PDU set.

[0062] In combination with some embodiments of the second aspect, in some embodiments, the specific QoS characteristics of the uplink PDU set are applied to the uplink QoS flow in the SDF, and the specific QoS characteristics of the downlink PDU set are applied to the downlink QoS flow in the SDF.

[0063] In conjunction with some embodiments of the second aspect, in some embodiments, sending the first information and the second information to the second network element includes: sending the first information and the second information to the second network element via a network open function AF session with a QoS request procedure; sending the first information and the second information to the second network element via an AF session with a QoS request update procedure; sending the first information and the second information to the second network element via service-specific parameter allocation; sending the first information and the second information to the second network element via an AF session policy setting procedure; sending the first information and the second information to the second network element via a third network element; sending the first information and the second information to the second network element via a fourth network element; and sending the first information and the second information to the second network element via the third network element and the fourth network element.

[0064] In combination with some embodiments of the second aspect, in some embodiments, the first network element is an AF network element, the second network element is a policy control function PCF network element, the third network element is a network open function NEF network element, and the fourth network element is a time-sensitive communication and time synchronization function TSCTSF network element.

[0065] In a third aspect, a communication processing method is proposed, the method comprising: a first network element sending first information to a second network element, wherein the first information is used to indicate an SDF direction corresponding to QoS processing based on a PDU set;

[0066] The second network element generates at least one PCC rule for the SDF according to the first information.

[0067] In a fourth aspect, a first network element is proposed, and the device includes: a transceiver module for sending first information to a second network element, wherein the first information is used to indicate the direction of the service data flow SDF corresponding to the quality of service QoS processing based on the packet data unit PDU set, and the first information is used for the second network element to generate at least one policy and charging control PCC rule for the SDF.

[0068] In the fifth aspect, a second network element is proposed, and the device includes: a transceiver module for receiving first information sent by the first network element, wherein the first information is used to indicate the direction of processing of the packet data unit PDU set; a processing module for generating at least one PCC rule for the SDF based on the first information.

[0069] In the sixth aspect, a core network device is proposed, which includes: a transceiver module for providing first information to a second network element, wherein the first information is used to indicate the SDF direction corresponding to the QoS processing based on the PDU set; or, receiving first information sent by the first network element, wherein the first information is used to indicate the direction of packet data unit PDU set processing; a processing module for the second network element to generate at least one PCC rule for the SDF based on the first information.

[0070] In a seventh aspect, a first network element is proposed, comprising: one or more processors; wherein the second network element is used to execute any one of the communication processing methods in the first aspect.

[0071] In an eighth aspect, a second network element is proposed, comprising: one or more processors; wherein the second network element is used to execute any one of the communication processing methods in the second aspect.

[0072] In the ninth aspect, a core network device is proposed, comprising: one or more processors; wherein the core network device is used to execute the communication processing method of the third aspect.

[0073] In the tenth aspect, a communication system is proposed, including a first network element and a second network element, wherein the first network element is configured to implement the communication processing method of any one of the first aspects, and the second network element is configured to implement the communication processing method of any one of the second aspects.

[0074] In the eleventh aspect, a storage medium is proposed, which stores instructions, characterized in that when the instructions are executed on a communication device, the communication device executes a communication processing method as described in any one of the first aspect or the second aspect.

[0075] In the twelfth aspect, an embodiment of the present disclosure proposes a first network element, which includes at least one of a transceiver module and a processing module; wherein the first network element is used to execute optional implementation methods of the first and third aspects.

[0076] In the thirteenth aspect, an embodiment of the present disclosure proposes a second network element, which includes at least one of a transceiver module and a processing module; wherein the second network element is used to execute optional implementation methods of the second and third aspects.

[0077] In the fourteenth aspect, an embodiment of the present disclosure proposes a core network device, which includes at least one of a transceiver module and a processing module; wherein the core network device is used to execute optional implementation methods of the first and second aspects.

[0078] In the fifteenth aspect, an embodiment of the present disclosure proposes a first network element, comprising: one or more processors; wherein the above-mentioned first network element is used to execute optional implementation methods of the first and third aspects.

[0079] In the sixteenth aspect, an embodiment of the present disclosure proposes a second network element, comprising: one or more processors; wherein the above-mentioned second network element is used to execute optional implementation methods of the second and third aspects.

[0080] In the seventeenth aspect, an embodiment of the present disclosure proposes a core network device, comprising: one or more processors; wherein the above-mentioned core network device is used to execute optional implementation methods of the first aspect and the second aspect.

[0081] In the eighteenth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a core network device; wherein the core network device is configured to execute the method described in the optional implementation of the first aspect, the second aspect, and the third aspect.

[0082] In the nineteenth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first aspect, the second aspect, and the third aspect.

[0083] In the twentieth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first aspect, the second aspect, and the third aspect.

[0084] In the twenty-first aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect, the second aspect, and the optional implementation of the third aspect.

[0085] In a twenty-second aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first aspect, the second aspect, and the third aspect.

[0086] It is understandable that the first network element, the second network element, the core network device, the communication system, the storage medium, the program product, the computer program, the chip, or the chip system described above are all used to perform the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0087] The embodiments of the present disclosure provide a communication indication method, a first network element, a second network element, and a core network device. In some embodiments, the terms "communication indication method" and "information processing method" and "communication method" are interchangeable; the terms "communication indication device" and "information processing device" and "communication device" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

[0100] 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", "chip", "chip system", "entity", "subject", etc.

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

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

[0103] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

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

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

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

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

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

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

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

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

[0112] In some embodiments, the core network device 103 may be a single device including a first network element 1031, a second network element 1032, etc., or may be a plurality of devices or a device group including all or part of the first network element 1031, the second network element 1032, etc. The network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0113] In some embodiments, the first network element 1031 is, for example, an application function (AF).

[0114] In some embodiments, the first network element 1031 is used for "various services at the application layer", and the name is not limited thereto.

[0115] In some embodiments, the second network element 1032 is, for example, a policy control function (PCF).

[0116] In some embodiments, the second network element 1032 is used to "control communication strategy", and the name is not limited thereto.

[0117] In some embodiments, the third network element 1033 is, for example, a network exposure function (NEF).

[0118] In some embodiments, the third network element 1033 is used to "manage network data open to the outside world", and the name is not limited to this.

[0119] In some embodiments, the third network element 1033 may be independent of the core network device 103 .

[0120] In some embodiments, the third network element 1033 may be part of the core network device 103 .

[0121] In some embodiments, the fourth network element 1034 is, for example, a time sensitive communication and time synchronization function (TSCTSF).

[0122] In some embodiments, the fourth network element 1034 is used to "perform time synchronization", but the name is not limited thereto.

[0123] In some embodiments, the fourth network element 1034 may be independent of the core network device 103 .

[0124] In some embodiments, the fourth network element 1034 may be part of the core network device 103 .

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

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

[0127] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0128] FIG1B is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1B , in one embodiment proposed in this application, the 5G system architecture is composed of the following network functions (NFs):

[0129] Authentication Server Function (AUSF).

[0130] Access and Mobility Management Function (AMF).

[0131] Data Network (DN), such as operator services, Internet access, or third-party services.

[0132] Unstructured Data Storage Network Function (UDSF).

[0133] Network Exposure Function (NEF).

[0134] Network Repository Function (NRF).

[0135] The Network Slice Admission Control Function (NSACF).

[0136] Network Slice Specific Authentication and Authorization Function (NSSAAF).

[0137] Network Slice Selection Function (NSSF).

[0138] Policy Control Function PCF.

[0139] Session Management Function SMF.

[0140] Unified Data Management (UDM).

[0141] Unified Data Repository (UDR).

[0142] User Plane Function (UPF)

[0143] UE radio capability management function (UCMF).

[0144] Application function AF.

[0145] User Equipment UE.

[0146] (Radio) Access Network ((R)AN).

[0147] 5G-Equipment Identity Register (5G-EIR).

[0148] Network Data Analytics Function (NWDAF).

[0149] Charging Function (CHF).

[0150] Time Sensitive Networking AF (TSN AF).

[0151] Time Sensitive Communication and Time Synchronization Function TSCTSF.

[0152] Data Collection Coordination Function (DCCF).

[0153] Analytics Data Repository Function (ADRF).

[0154] Messaging Framework Adaptor Function (MFAF).

[0155] Non-Seamless WLAN Offload Function (NSWOF).

[0156] Optionally, the functions provided by DCCF and / or ADRF can also be hosted by NWDAF.

[0157] Edge Application Server Discovery Function (EASDF).

[0158] The 5G system architecture also includes the following network entities:

[0159] Service Communication Proxy (SCP).

[0160] Security Edge Protection Proxy (SEPP).

[0161] Non-3GPP InterWorking Function (N3IWF).

[0162] Trusted Non-3GPP Gateway Function (TNGF).

[0163] Wired Access Gateway Function (W-AGF)

[0164] Trusted WLAN Interworking Function (TWIF).

[0165] In one embodiment proposed in the present application, mobile media services, cloud virtual reality (VR), augmented reality (AR), mixed reality (MR) and other extended reality (XR) services, cloud games, video-based machine or drone remote control and other services are expected to contribute increasingly higher traffic to 5G networks. XR services involve multimodal data streams. Multimodal data is data input from the same device or different devices (including sensors) that describes the same service / application, and these data may be output to one or more destination device terminals. The data streams in multimodal data often have certain or even strong correlations, such as the synchronization of audio and video streams, the synchronization of touch and vision, etc. The data streams of such media services themselves, the data streams between each other, and the network transmission requirements of these service data streams all have some common characteristics. The effective identification and utilization of these characteristics will be more conducive to the transmission and control of the network and services, and will also be more conducive to service assurance and user experience.

[0166] For augmented reality and media services, multimodal services (eXtended Reality and Media, XRM), and interactive media services, the 5GS system comprehensively considers the Quality of Service (QoS) characteristics of the service's data streams, such as delay-critical GBR data streams, guaranteed flow bit rate (GFBR), packet delay budget (PDB), and maximum default data burst volume (MDBV). This involves ensuring the consistency of QoS authorization and execution for multiple XRM data streams within a single UE, and for XRM data streams across multiple UEs.

[0167] In one possible embodiment, the current 5G system supports AF's enhanced processing of packet data units (PDUs) in XRM service data flows. This supports AF's enhanced QoS awareness and assurance of XRM service data flows, as well as enhanced user experience (QoE).

[0168] In a possible embodiment, the AF enhances the processing function of the PDU set in the XRM service data flow by the following method:

[0169] AF provides PDU set-specific QoS characteristics and protocol descriptions, including PDU set-specific QoS features, specifically including the following:

[0170] PDU Set Delay Budget (PSDB).

[0171] PDU Set Error Rate (PSER).

[0172] PDU Set Integrated Handling Information (PSIHI)

[0173] The Session Management Function (SMF) and the User Plane Function (UPF) can perform the General Packet Radio Service (GPRS) Tunneling Protocol-U (GTP-U) header extension of the corresponding PDU in the corresponding Service Data Flow (SDF) PDU set in combination with the protocol description and protocol header extension provided by the AF, carrying PDU set related information. The PDU set information is used by the Next Generation Radio Access Network (NG-RAN) to perform QoS processing based on the PDU set. Optionally, the PDU set related information includes:

[0174] Sequence number of the PDU set.

[0175] Index ID of the last PDU in the PDU set.

[0176] Sequence number of the PDU in the PDU set.

[0177] The size of the PDU set in bytes.

[0178] Importance of a PDU set, used to identify the relative importance of a PDU set compared to other PDU sets in a QoS flow.

[0179] The above PDU set feature enhancements (PDU set-specific QoS features and PDU set related information) greatly improve 5GS's QoS guarantee for XRM service requirements. However, only downlink data PDU set enhancements are supported.

[0180] How to support PDU set enhanced processing of uplink XRM service data flows, and how to handle PDU set processing enhancement supported by both uplink and downlink. For example, the uplink and downlink service data flows in the same QoS flow currently have symmetric QoS parameter characteristics, while the uplink and downlink latency and bandwidth requirements of XRM services are different. How to support PDU set enhanced processing of uplink and downlink XRM service data flows based on actual needs, especially asymmetric needs, and thus more effectively guarantee end-to-end QoS requirements, better adapt to resource requirements and allocation, and coordinate E2EQoS resources, is still a problem that the current 5GS system requests to be solved.

[0181] Therefore, how to support the enhanced processing of PDU sets for uplink XRM service data flows, and how to support the enhanced processing of PDU sets for both uplink and downlink, especially the enhanced processing of PDU sets for asymmetric QoS requirements for uplink and downlink, to more effectively guarantee end-to-end QoS requirements and adapt to resource requirements and allocation, is the problem that the present disclosure requests to be solved.

[0182] FIG2 is an interactive diagram of a communication indication method according to an embodiment of the present disclosure. As shown in FIG2 , the embodiment of the present disclosure relates to a communication indication method, which includes:

[0183] Step S2101: The first network element 101 sends first information to the second network element 102.

[0184] In some embodiments, the second network element 102 receives the first information.

[0185] In some embodiments, the first information is used to indicate a direction of a service data flow SDF corresponding to the quality of service QoS processing based on a packet data unit (PDU) set. Optionally, the direction includes uplink or downlink.

[0186] In some embodiments, the first information is used by the second network element to generate at least one Policy and Charging Control (PCC) rule for the service data flow SDF.

[0187] In some embodiments, the name of the first information is not limited, and it can be, for example, "PDU set handling Direction indication", "PDU set handling Direction indication", etc.

[0188] In some embodiments, the first information is used to indicate that only the downlink PDU set is requested for QoS processing, that is, the application service data flow (such as XR media service data flow and multimodal service data flow) only requests downlink transmission through the downlink PDU set.

[0189] In some embodiments, the first information is used to indicate that only the uplink PDU set is requested for QoS processing, that is, the application service data flow (such as XR media service data flow and multimodal service data flow) only requests downlink transmission through the uplink PDU set.

[0190] In some embodiments, the first information is used to indicate a request for QoS processing of the downlink PDU set and the uplink PDU set. That is, the application service data flow (such as the XR media service data flow and the multimodal service data flow) only requests downlink / uplink transmission through the uplink PDU set and the uplink PDU set.

[0191] In some embodiments, the first information is used to indicate a request for QoS processing of a downlink PDU set and an uplink PDU set, and the quality of service QoS parameters corresponding to the downlink PDU set and the uplink PDU set are the same.

[0192] In some embodiments, the first information is used to indicate a request for QoS processing of a downlink PDU set and an uplink PDU set, and the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different.

[0193] In some embodiments, the first information is used to indicate a request for QoS processing of a downlink PDU set and an uplink PDU set, and the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are obtained based on a network configuration. Optionally, regardless of whether the QoS parameters of the downlink PDU set and the uplink PDU set are the same, the QoS parameters are obtained based on the network configuration.

[0194] In some embodiments, the network configuration includes at least one of the following: operator policy, configuration, subscription, terminal side support capability, radio access network (RAN) support capability, session management function SMF support capability, user plane function UPF support capability, policy control function PCF support capability, terminal side activation capability, RAN activation capability, SMF activation capability, UPF activation capability, PCF activation capability.

[0195] In some embodiments, the first information is used to indicate a request for QoS processing of a downlink PDU set and an uplink PDU set, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are the same.

[0196] In some embodiments, the first information is used to indicate a request for QoS processing of a downlink PDU set and an uplink PDU set, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are different.

[0197] In some embodiments, the first network element 101 directly sends the first information to the second network element 102. Optionally, the method of directly sending the first information includes:

[0198] The first information and the second information are provided to the second network element via a network open function AF session with a QoS request procedure.

[0199] The first information and the second information are provided to the second network element through the AF session with the QoS request update procedure.

[0200] The first information and the second information are provided to the second network element through service specific parameter provisioning.

[0201] The first information and the second information are provided to the second network element through the AF session setting policy process.

[0202] In some embodiments, the first network element 101 indirectly sends the first information to the second network element 102. Optionally, the indirect sending of the first information includes:

[0203] The first information and the second information are sent to the second network element through the third network element.

[0204] The first information and the second information are sent to the second network element through the fourth network element.

[0205] The first information and the second information are sent to the second network element through the third network element and the fourth network element.

[0206] In some embodiments, the first network element is an AF network element, the second network element is a policy control function PCF network element, the third network element is a network open function NEF network element, and the fourth network element is a time sensitive communication and time synchronization function TSCTSF network element.

[0207] In some embodiments, the first network element 101 sends a session resource request message, wherein the session resource request message includes the first information. Optionally, the second network element 102 receives the session resource request message. The session resource request message may be, for example, "Nnef_AFsessionWithQoS_Create request or Nnef_AFsessionWithQoS_Update request," but is not limited thereto.

[0208] In some embodiments, the first network element 101 sends an AF session resource request, for example, through Nnef_AFsessionWithQoS_Create request, to create an AF request.

[0209] Optionally, the second network element 102 receives an AF session resource request.

[0210] In some embodiments, the AF session resource request includes first information.

[0211] Step S2102 : The first network element 101 sends second information to the second network element 102 .

[0212] In some embodiments, the second network element 102 receives the second information.

[0213] In some embodiments, the second information is used to indicate processing requirements of a PDU set in a related direction. Optionally, the direction includes uplink or downlink.

[0214] In some embodiments, the name of the second information is not limited, and it can be, for example, "PDU set processing requirement indication" or the like.

[0215] In some embodiments, the second information is used to indicate whether the QoS parameters of the PDU set are applied to the QoS flow in the upstream direction or the downstream direction. This information is used to indicate the QoS in the corresponding direction.

[0216] In some embodiments, applying to a QoS flow means applying to packets in the QoS flow. The QoS parameters are applied to all packets in a QoS flow. Here, the second information is used to determine whether to apply to uplink packets or downlink packets.

[0217] In some embodiments, the second information is used to indicate a PDU set specific QoS characteristic.

[0218] In some embodiments, the second information is used to indicate a specific QoS characteristic of an uplink PDU set or a specific QoS characteristic of a downlink PDU set.

[0219] In some embodiments, the second information is used to indicate a specific QoS characteristic of an uplink PDU set and a specific QoS characteristic of a downlink PDU set.

[0220] In some embodiments, the second information is used to indicate an uplink protocol description or a downlink protocol description.

[0221] In some embodiments, the information indicating that the flow direction of the PDU set QoS parameters is applicable to the QoS flow, and the information used to indicate the uplink protocol description or the downlink protocol description, are both independent QoS implementation modes for uplink and downlink respectively. Both are independently bound to the corresponding QoS flows and will not be included in the same QoS flow at the same time.

[0222] In some embodiments, if different PDU sets for uplink and downlink have QoS parameters associated with the corresponding flow direction and the QoS flow of the flow direction, the network function may associate the two paired QoS flows through the group IDs of the uplink and downlink directions.

[0223] In some embodiments, the second information is used to indicate relevant information about the uplink SDF and the downlink SDF. Optionally, the relevant information about the uplink service data flow SDF and the downlink SDF includes: a pairing ID of the uplink SDF and the downlink SDF; and a ratio or threshold between the QoS parameters of the uplink PDU set and the QoS parameters of the downlink PDU set.

[0224] In some embodiments, the ratio of the QoS parameters (eg, delay) of the upstream PDU set to the QoS parameters of the downstream PDU set is less than 20%.

[0225] In some embodiments, the QoS parameter (eg, delay) of the uplink PDU set must be less than or greater than a certain threshold.

[0226] In some embodiments, the PDU set specific QoS characteristics include a delay budget for the PDU set.

[0227] In some embodiments, the PDU set specific QoS characteristic includes an error rate of the PDU set.

[0228] In some embodiments, the PDU set specific QoS characteristics include aggregate processing information for the PDU set.

[0229] In some embodiments, the PDU set specific QoS characteristics include data flow direction information. Optionally, the data flow direction information is uplink, or the data flow direction information is downlink, or the data flow direction information is uplink and downlink.

[0230] In some embodiments, the uplink PDU set specific QoS characteristics include a delay budget for the uplink PDU set.

[0231] In some embodiments, the specific QoS characteristic of the uplink PDU set is an error rate of the uplink PDU set.

[0232] In some embodiments, the uplink PDU set specific QoS characteristics include integrated processing information for the uplink PDU set.

[0233] In some embodiments, the downlink PDU set specific QoS characteristics include a delay budget for the downlink PDU set.

[0234] In some embodiments, the downlink PDU set specific QoS characteristic includes an error rate of the downlink PDU set.

[0235] In some embodiments, the downlink PDU set specific QoS characteristics include integrated processing information of the downlink PDU set.

[0236] Step S2103: The second network element 102 generates a communication rule.

[0237] In some embodiments, the communication rules are PCC rules.

[0238] In some embodiments, PCC rules are used to monitor and reasonably allocate network resources and effectively control the service capabilities of the network, thereby improving user service experience and developing new pricing strategies.

[0239] In some embodiments, the PCC rule includes a set of related information and a set of related operations. Optionally, the PCC rule includes three categories of information: service data flow inspection information, policy control information, and charging related information.

[0240] In some embodiments, the second network element 102 generates at least one PCC rule for the SDF according to the first information.

[0241] In some embodiments, the second network element 102 generates at least one PCC rule for the SDF according to the second information.

[0242] In some embodiments, the second network element 102 generates at least one PCC rule for the SDF according to the first information and the second information.

[0243] In some embodiments, the PCC rule includes a PDU set-specific QoS feature. The QoS flow to which the PCC rule applies is determined by setting QoS feature parameters and the flow direction (uplink, downlink, or uplink and downlink) corresponding to the QoS feature parameters.

[0244] In some embodiments, if the data flow direction information indicates that the flow direction is uplink, the PCC rule is applied to the uplink QoS flow in the SDF.

[0245] In some embodiments, if the data flow direction information indicates that the flow direction is downlink, the PCC rule is applied to the downlink QoS flow in the SDF.

[0246] In some embodiments, if the data flow direction information indicates that the flow direction is uplink and downlink, the PCC rule is applied to the uplink QoS flow and the downlink QoS flow in the SDF.

[0247] In some embodiments, the PCC rules include at least one of the following: QoS characteristics specific to an uplink PDU set; QoS characteristics specific to a downlink PDU set. The PCC rules applicable to the uplink QoS flow and the PCC rules applicable to the downlink QoS flow are determined by setting QoS characteristic parameters for the uplink PDU set and QoS characteristic parameters for the downlink PDU set, respectively. Optionally, the QoS characteristics specific to the uplink PDU set and the QoS characteristics specific to the downlink PDU set can be the same or different.

[0248] In some embodiments, the QoS characteristics specific to an upstream PDU set are applied to the upstream QoS flow in the SDF, and the QoS characteristics specific to a downstream PDU set are applied to the downstream QoS flow in the SDF.

[0249] In some embodiments, the second network element 102 allocates a 5G QoS Identifier (5QI) based on the first information. The 5QI is a scalar that points to a 5G QoS characteristic, where the characteristic corresponds to multiple QoS attributes, and parameters in these QoS attributes are used to control the QoS of QoS flow forwarding processing.

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

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

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

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

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

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

[0256] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2103. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, steps S2101+S2103 may be implemented as independent embodiments, and steps S2101+S2102+S2103 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0257] In some embodiments, steps S2101 and S2102 may be executed in an interchanged order or simultaneously.

[0258] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0259] In some embodiments, step S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0261] FIG3A is a flow chart of a communication indication method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a communication indication method (on the first network element side), the method comprising:

[0262] Step S3101: Send a processing direction indication of a PDU set.

[0263] In some embodiments, the second network element 102 receives a processing direction indication of the PDU set.

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

[0265] In some embodiments, the first network element 101 sends a processing direction indication of the PDU set to the second network element 102, but is not limited thereto. The processing direction indication of the PDU set may also be sent to other entities.

[0266] Step S3102: Send the processing requirements of the PDU set in the relevant direction.

[0267] In some embodiments, the second network element 102 receives a processing requirement for a PDU set in a related direction.

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

[0269] In some embodiments, the first network element 101 sends the processing requirements of the PDU set in the relevant direction to the second network element 102, but is not limited thereto. The processing requirements of the PDU set in the relevant direction may also be sent to other entities.

[0270] The communication 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 are not limited thereto.

[0271] In some embodiments, steps S3101 and S3102 may be executed in an interchanged order or simultaneously.

[0272] In some embodiments, step S3101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0273] In some embodiments, step S3102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0274] FIG3B is a flow chart of a communication indication method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a communication indication method, which includes:

[0275] Step S3201, sending the first information.

[0276] Optional implementations of step S3201 can be found in step S2101 of FIG. 2 , optional implementations of step S3101 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0277] Step S3202, sending the second information.

[0278] Optional implementations of step S3202 can be found in step S2102 of FIG. 2 , optional implementations of step S3102 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0279] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3201 and S3202. For example, step S3201 may be implemented as an independent embodiment, step S3202 may be implemented as an independent embodiment, and steps S3201+S3202 may be implemented as independent embodiments, but are not limited thereto.

[0280] In some embodiments, steps S3201 and S3202 may be executed in an interchanged order or simultaneously.

[0281] In some embodiments, step S3201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0282] In some embodiments, step S3202 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0283] FIG4A is a flow chart of a communication indication method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a communication indication method (on the second network element side), the method comprising:

[0284] Step S4101: Obtain a processing direction indication of a PDU set.

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

[0286] Step S4102: Obtain processing requirements of PDU sets in related directions.

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

[0288] Step S4103: Generate PCC rules.

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

[0290] In some embodiments, the second network element 102 generates a PCC rule according to the first information.

[0291] In some embodiments, the second network element 102 generates a PCC rule according to the second information.

[0292] In some embodiments, the second network element 102 generates a PCC rule according to the first information and the second information.

[0293] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4103. For example, step S4101 may be implemented as an independent embodiment, step S4102 may be implemented as an independent embodiment, and steps S4101+S4102 may be implemented as independent embodiments, but are not limited thereto.

[0294] In some embodiments, steps S4101 and S4102 may be executed in an interchanged order or simultaneously.

[0295] In some embodiments, step S4101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0296] In some embodiments, step S4102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0297] FIG4B is a flow chart of a communication indication method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a communication indication method (on the second network element side), the method comprising:

[0298] Step S4201, obtain first information.

[0299] The optional implementation of step S4201 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0300] Step S4202, obtain the second information.

[0301] The optional implementation of step S4202 can refer to step S2102 in Figure 2, the optional implementation of step S4102 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0302] Step S4203: Determine communication rules.

[0303] The optional implementation of step S4203 can refer to step S2103 in Figure 2, the optional implementation of step S4103 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0304] The communication method involved in the embodiment of the present disclosure may include at least one of steps S4201 to S4203. For example, step S4201 may be implemented as an independent embodiment, step S4202 may be implemented as an independent embodiment, and steps S4201+S4202 may be implemented as independent embodiments, but are not limited thereto.

[0305] In some embodiments, steps S4201 and S4202 may be executed in an interchanged order or simultaneously.

[0306] In some embodiments, step S4201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0307] In some embodiments, step S4202 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0308] FIG5A is an interactive diagram of a communication indication method according to an embodiment of the present disclosure. As shown in FIG5A , the embodiment of the present disclosure relates to a communication indication method, which includes:

[0309] In step S5101 , the first network element 101 provides first information to the second network element 102 .

[0310] The optional implementation of step S5101 can refer to the optional implementation of step S2101 in Figure 2, step S3101 in Figure 3, step S4101 in Figure 4, and other related parts in the embodiments involved in Figures 2, 3, and 4, which will not be repeated here.

[0311] In step S5102 , the first network element 101 provides second information to the second network element 102 .

[0312] The optional implementation of step S5102 can refer to the optional implementation of step S2102 in Figure 2, step S3102 in Figure 3, step S4102 in Figure 4, and other related parts in the embodiments involved in Figures 2, 3, and 4, which will not be repeated here.

[0313] Step S5103: The second network element 102 generates a communication rule.

[0314] The optional implementation of step S5104 can refer to the optional implementation of step S2103 in Figure 2, steps S4103 and S4203 in Figure 4, and other related parts in the embodiments involved in Figures 2 and 4, which will not be repeated here.

[0315] In some embodiments, the above method may include the methods of the above-mentioned embodiments of the communication system side, terminal side, access network equipment side, core network equipment side, first network element side, second network element side, etc., which will not be repeated here.

[0316] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5201 to S5203. For example, step S5201 may be implemented as an independent embodiment, step S5202 may be implemented as an independent embodiment, and steps S5201+S5202 may be implemented as independent embodiments, but are not limited thereto.

[0317] In some embodiments, steps S5201 and S5202 may be executed in an interchanged order or simultaneously.

[0318] In some embodiments, step S5201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0319] In some embodiments, step S5202 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0320] FIG6A is a schematic diagram of a communication indication method according to an embodiment of the present disclosure. As shown in FIG6 , the embodiment of the present disclosure relates to a communication indication method, which includes:

[0321] Step S6101: The AF sends an AF session resource request. Optionally, the AF sends an Nnef_AFsessionWithQoS_Create request to the NEF to create an AF request.

[0322] Optionally, the AF session resource request includes at least one of the following: a processing direction indication of a PDU set, and a processing requirement of a PDU set in a related direction.

[0323] In some embodiments, the processing direction indication of the PDU set is used to indicate at least one of the following:

[0324] Only the downlink PDU set is requested to be processed for QoS.

[0325] Only the upstream PDU set is requested to be processed for QoS.

[0326] Request QoS processing for the downlink PDU set and the uplink PDU set.

[0327] Request QoS processing for the downlink PDU set and the uplink PDU set, and the quality of service QoS parameters corresponding to the downlink PDU set and the uplink PDU set are the same.

[0328] QoS processing is requested for the downlink PDU set and the uplink PDU set, and the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different.

[0329] QoS processing is requested for the downlink PDU set and the uplink PDU set, and the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are obtained based on the network configuration.

[0330] Request QoS processing for the downlink PDU set and the uplink PDU set, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are the same.

[0331] Request QoS processing for the downlink PDU set and the uplink PDU set, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are different.

[0332] Optionally, the network configuration includes at least one of the following:

[0333] Operator policy, configuration, subscription, terminal side support capabilities, radio access network RAN ​​support capabilities, session management function SMF support capabilities, user plane function UPF support capabilities, policy control function PCF support capabilities, terminal side activation capabilities, RAN activation capabilities, SMF activation capabilities, UPF activation capabilities, PCF activation capabilities.

[0334] In some embodiments, the processing requirements of the PDU set in the relevant direction are used to indicate at least one of the following: the flow direction of the PDU set QoS parameters is applicable to the QoS flow; PDU set specific QoS characteristics; uplink PDU set specific QoS characteristics or downlink PDU set specific QoS characteristics; uplink PDU set specific QoS characteristics and downlink PDU set specific QoS characteristics; uplink protocol description or downlink protocol description; related information of uplink SDF and downlink SDF.

[0335] In some embodiments, the PDU set specific QoS characteristics include at least one of the following: a delay budget of the PDU set; an error rate of the PDU set; integrated processing information of the PDU set; and data flow direction information.

[0336] In some embodiments, the specific QoS characteristics of the uplink PDU set include at least one of the following: a delay budget of the uplink PDU set; an error rate of the uplink PDU set; and integrated processing information of the uplink PDU set.

[0337] In some embodiments, the specific QoS characteristics of the downlink PDU set include at least one of the following: a delay budget of the downlink PDU set; an error rate of the downlink PDU set; and integrated processing information of the downlink PDU set.

[0338] In some embodiments, the relevant information of the uplink service data flow SDF and the downlink SDF includes: the pairing ID of the uplink SDF and the downlink SDF; and the ratio or threshold between the QoS parameters of the uplink PDU set and the QoS parameters of the downlink PDU set.

[0339] Optionally, the AF session resource request carries XRM service information, which is used to identify the common index (commonID) information of the XRM service business data flow group, UE address / UE index (UE address / UE Identifier), AF index (AF Identifier), application index (ApplicationID), flow description (Flow description(s)), data network name (Data Network Name, DNN), network slice selection support information (Network Slice Selection Assistance Information, S-NSSAI), QoS parameters and other corresponding information. Here, the common index can be used to identify all data flows (flows) in the XRM service group.

[0340] In some embodiments, the processing direction indication of the PDU set is the above-mentioned first information, and the processing requirement of the PDU set in the relevant direction is the above-mentioned second information.

[0341] In some embodiments, the AF network element is the first network element 101, the policy control function PCF network element is the second network element 102, the network open function NEF network element is the third network element 103, and the time sensitive communication and time synchronization function TSCTSF network element is the fourth network element 104.

[0342] Step S6102: NEF authorizes the AF session resource request.

[0343] In some embodiments, if the AF is an untrusted AF, the AF request is sent to the PCF through the NEF. Optionally, the NEF performs relevant mappings, including: mapping of the XRM service identifier (AF service index) to the 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 the Unified Data Management (UDM) subscription information (such as the Subscriber Permanent Identifier (SUPI)), and performing mapping of external to internal XRM service group identifiers based on the UDM subscription information.

[0344] Step S6103: NEF sends policy authorization creation information to PCF.

[0345] In some embodiments, the policy authorization creation message (Npcf_PolicyAuthorization_Create request) carries an indication of the processing direction of the PDU set and the processing requirements of the PDU set in the corresponding direction for the PCF to make communication policy decisions. Optionally, the message carries information related to the XRM service in the AF request.

[0346] Optionally, after authorizing the AF session resource request, the NEF determines whether to call the TSCTSF or contact the PCF directly based on the parameters provided by the AF to set up the AF session using the required QoS procedures.

[0347] Optionally, the PCF receives AF-provided attributes from the NEF or TSCTSF.

[0348] Step S6104: PCF generates PCC rules.

[0349] In some embodiments, the PCF generates one or more PCC rules for the corresponding service data flow based on the PDU set processing direction indication carried in the policy authorization creation information and the processing requirements of the PDU set in the corresponding direction. Optionally, a 5QI is assigned based on the PDU set processing direction indication.

[0350] In some embodiments, in the corresponding QoS flow direction rule, the processing requirements of the PDU set in the corresponding direction are used to indicate at least one of the following: the flow direction of the PDU set QoS parameters is applicable to the QoS flow; PDU set specific QoS characteristics; uplink PDU set specific QoS characteristics or downlink PDU set specific QoS characteristics; uplink PDU set specific QoS characteristics and downlink PDU set specific QoS characteristics; uplink protocol description or downlink protocol description; related information of uplink SDF and downlink SDF.

[0351] In some embodiments, the PDU set specific QoS characteristics include at least one of the following: a delay budget of the PDU set; an error rate of the PDU set; integrated processing information of the PDU set; and data flow direction information.

[0352] In some embodiments, the specific QoS characteristics of the uplink PDU set include at least one of the following: a delay budget of the uplink PDU set; an error rate of the uplink PDU set; and integrated processing information of the uplink PDU set.

[0353] In some embodiments, the specific QoS characteristics of the downlink PDU set include at least one of the following: a delay budget of the downlink PDU set; an error rate of the downlink PDU set; and integrated processing information of the downlink PDU set.

[0354] In some embodiments, the relevant information of the uplink service data flow SDF and the downlink SDF includes: the pairing ID of the uplink SDF and the downlink SDF; and the ratio or threshold between the QoS parameters of the uplink PDU set and the QoS parameters of the downlink PDU set.

[0355] Step S6105: The PCF sends a policy authorization creation response (Npcf_PolicyAuthorization_Createresponse) to the NEF.

[0356] Step S6106: NEF sends an AF session creation response (Nnef_AFsessionWithQoS_Createresponse) to AF.

[0357] Step S6107: PCF sends a session management (SM) policy association modification request to SMF.

[0358] In some embodiments, the SM policy association modification request includes a PCC rule (eg, a QoS monitoring policy).

[0359] In some embodiments, the SMF generates a QoS monitoring configuration for the UPF (and RAN) according to the QoS monitoring policy used for measurements from the PCF.

[0360] Step S6108: The SMF sends SM Policy Association Modification Response to the PCF.

[0361] Step S6109, SMF sends an N4 session modification request (N4Session Modification Request) to UPF.

[0362] In some embodiments, the N4 session modification request includes a QoS monitoring configuration.

[0363] Step S6110, UPF sends N4 session modification feedback information (N4Session Modification Response) to SMF.

[0364] In some embodiments, the UPF enables measurement and reporting based on the QoS monitoring configuration in the N4 session modification request.

[0365] Step S6111: For the modification of the SMF request, SMF calls the transmission information (Namf_Communication_N1N2MessageTransfer).

[0366] In some embodiments, the transmission information includes: N2SM information (such as PDU session ID, QFI, QoS profile, QoS monitoring configuration) and N1SM container.

[0367] Step S6112: AMF sends an N2 message to the RAN.

[0368] In some embodiments, the N2 message includes: N2SM information received from the SMF, NAS message (such as PDU session ID, N1SM container (PDU session modification command)))).

[0369] Step S6113: RAN enables event measurement and reporting.

[0370] In some embodiments, upon receiving the QoS monitoring configuration, the RAN enables event measurement and reporting (eg, the RAN detects UL delay and DL delay, and takes the sum of UL PDB and DL PDB as RT delay).

[0371] Step S6114: RAN sends an N2 message to AMF.

[0372] In some embodiments, the RAN acknowledges the N2PDU session request by sending an N2PDU Session Ack message to the AMF.

[0373] Step S6115, AMF sends a PDU session SM policy update message (Nsmf_PDUSession_UpdateSMContext) to SMF.

[0374] In some embodiments, the PDU Session SM Policy Update message includes the N2SM information received from the AMF.

[0375] Step S6116, SMF sends PDU session SM policy update feedback (Nsmf_PDUSession_UpdateSMContext response) to AMF.

[0376] Step S6117, SMF sends an N4 session modification request message (N4SessionModificationRequest) to UPF.

[0377] In some embodiments, the N4 session modification request message is used to update the PDU session and modify the N4 session of the UPF involved.

[0378] Step S6118, UPF sends N4 session modification request feedback (N4SessionModificationResponse) to SMF.

[0379] The communication method according to the embodiments of the present disclosure may include at least one of steps S6101 to S6118. For example, step S6101 may be implemented as an independent embodiment, step S6102 may be implemented as an independent embodiment, steps S6101+S6103 may be implemented as independent embodiments, and steps S6101+S6102+S6103 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0380] In some embodiments, steps S6101 and S6103 may be executed in an interchanged order or simultaneously.

[0381] In some embodiments, steps S6105-S6114 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0383] FIG6B is a schematic diagram of a communication indication method according to an embodiment of the present disclosure. As shown in FIG6B , the embodiment of the present disclosure relates to a communication indication method, which includes:

[0384] In step S6201, the UE is registered with the network and selects the PCF to complete session policy association. The UEs are some or all of the UEs associated with the XRM service or multimodal data service. The PCF subscribes to the UDM for change notifications related to the XRM service or multimodal data service subscription information based on the XRM service policy and QoS requirements.

[0385] Step S6202: The AF creates an AF request, which includes information such as the XRM service identifier, universal ID, and UE address or identifier.

[0386] Optionally, the AF carries the first information and the second information in the request message.

[0387] Optionally, the AF provides XRM service or multimodal data service parameters to one or more UEs related to the service through the Nnef_XRMServiceParameter service. The information sent by the AF includes service description (universal ID), service parameters, UE / UE group, and subscription.

[0388] Specifically:

[0389] 1) Service description (universal ID), used to identify XRM services or XRM data services; can be identified by a combination of DNN and S-NSSAI, or XRMID; or represented by AF service ID or external application ID.

[0390] 2) Service parameters. Information related to AF guidance for XRM services or multimodal data services, service-related policies and QoS determination. For example, first information about media data flows related to XRM services, and corresponding second information, a list of rules for associating XRM services or multiple data service application traffic, parameters such as UE policies, pairing IDs / universal IDs or group IDs of uplink and downlink SDFs, or a combination of DNN and S-NSSAI, SSC mode, and selection priorities of corresponding rules (e.g., priority of alternative QoS parameters, priority of corresponding location or time bed, priority of corresponding inclusion type or routing selection, etc.).

[0391] 3) A single UE or multiple UEs associated with the XRM service or multimodal data to which the AF requests the data.

[0392] 4) Subscription. The AF may subscribe to notifications about SM policy results or the execution and changes of AM policy or UE policy; or QoS monitoring events related to media data flows related to XRM services.

[0393] When AF needs to update or delete the corresponding request or subscription, the update or deletion process of the AF request can also be initiated through this service.

[0394] In step S6203, the AF sends the request to the NEF. The NEF authorizes the AF request. The NEF performs relevant mappings, including mapping of XRM services or multimodal data services to DNN and S-NSSAI, mapping of external applications to CN application identifiers; and mapping of external UE identifiers to CN internal UE identifiers (such as SUPI) based on UDM subscription information, as well as mapping of external to internal XRM service group identifiers based on UDM subscription information.

[0395] Step S6204: The NEF stores the requested information in the UDR (eg, as service feature parameter information of application data). Optionally, the NEF may improve the corresponding service parameters according to local configuration.

[0396] Optionally, based on the operator's policy, NEF can combine the subscription information to confirm whether the requested service characteristics are authorizable for the XRM service or multimodal data service of a single UE or multiple UEs and store the corresponding parameters in the UDR.

[0397] If multiple UEs are involved, the NEF transmits the relevant service parameters to the PCF, and each PCF performs the corresponding authorization, as well as the decision or update of policies and rules. Based on the authorization result of the request, the PCF stores the corresponding information in the UDR.

[0398] For multi-UE scenarios, the subscription data of UE group members are associated through XRM service ID or group ID / universal ID, and the data of UEs in the UE group remains consistent (such as service QoS, access and data routing characteristic parameters).

[0399] Receivers such as AF or PCF can subscribe to relevant XRM services or multimodal data-related event triggers through NEF, such as QoS monitoring reports, QoS service updates, UE migration, PCF modifications, etc.

[0400] Receivers such as AF or PCF receive corresponding notifications by receiving NEF reports and execute subsequent application requirements or QoS rule updates.

[0401] Step S6205: NEF returns a create request response message to AF.

[0402] If in step S6201, PCF executes the subscription information update notification after UE registration, then the subsequent process is executed because AF requests to update the UDR subscription information

[0403] Step S6206: PCF receives the contract information change notification sent by UDR.

[0404] Step S6207: The PCF transmits the UE policy to the UE.

[0405] In step S6208, if the AF subscribes to the execution notification of the XRM service-related policy, the PCF sends the relevant execution results to the AF through the NEF. At the same time, if there are changes to the relevant subscription parameters, the PCF updates the changes to the UDR, triggering the service PCFs of other UEs related to the XRM service group to execute policy changes and coordinate.

[0406] In step S6209, after receiving the notification, the NEF first performs mapping of internal and external related parameters, and then sends the related report to the AF.

[0407] FIG6C is a schematic diagram of a communication indication method according to an embodiment of the present disclosure. As shown in FIG6C , the embodiment of the present disclosure relates to a communication indication method, which includes:

[0408] Step S6301: When an event is detected, a report is triggered (eg, a threshold is reached, or a periodic timer times out). Optionally, the UPF triggers a Nupf_EventExposure_Notify message to report measurement information.

[0409] Step S6302: UPF sends a Nupf_EventExposure_Notify message (including QoS status information related to the measured PDU settings) to NEF.

[0410] Step S6303: NEF sends a Nnef_Nnef_EventExposure_Notify message (including the measured PDU setting-related QoS status information) to AF.

[0411] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

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

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

[0414] Figure 7A is a schematic diagram of the structure of a first network element according to an embodiment of the present disclosure. As shown in Figure 7A , the first network element 7100 may include at least one of a transceiver module 7101 and a processing module 7102. In some embodiments, the transceiver module is configured to provide first information to a second network element, where the first information indicates a direction for processing a packet data unit (PDU) set, and the first information is used by the second network element to generate at least one policy and charging control (PCC) rule for a service data flow (SDF).

[0415] Optionally, the transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S2101 and step S2102, but not limited thereto) performed by the first network element 101 in any of the above methods, which are not described in detail here. Optionally, the processing module is used to execute at least one of the other steps (for example, step S2103, but not limited thereto) performed by the first network element 101 in any of the above methods, which are not described in detail here.

[0416] FIG7B is a schematic diagram of the structure of the second network element proposed in an embodiment of the present disclosure. As shown in FIG7B , the second network element 7200 may include:

[0417] At least one of the transceiver module 7201, the processing module 7202, etc. In some embodiments, the transceiver module is configured to receive first information sent by a first network element, wherein the first information is configured to indicate a direction for processing a packet data unit (PDU) set. The processing module is configured to generate at least one PCC rule for the SDF based on the first information.

[0418] Optionally, the transceiver module is configured to execute at least one of the communication steps (e.g., step S2101, step S2102, but not limited thereto) such as sending and / or receiving performed by the second network element 102 in any of the above methods, which are not described in detail here. Optionally, the processing module is configured to execute at least one of the other steps (e.g., step S2103, but not limited thereto) performed by the second network element 102 in any of the above methods, which are not described in detail here.

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

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

[0421] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 8100 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.

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

[0423] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceiver 8102 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101 and step S2102, but not limited thereto), and the processor 8101 performs at least one of the other steps (for example, step S2103, 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.

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

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

[0426] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0427] The chip 8200 includes one or more processors 8201. The chip 8200 is configured to execute any of the above methods.

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

[0429] In some embodiments, the interface circuit 8202 performs at least one of the communication steps (e.g., step S2101 and step S2102, but not limited thereto) of the aforementioned method. The interface circuit 8202 performing the communication steps (e.g., step S2101 and step S2102, but not limited thereto) of the aforementioned method means, for example, that the interface circuit 8202 performs data exchange between the processor 8201, chip 8200, memory 8203, or a transceiver device. In some embodiments, the processor 8201 performs at least one of the other steps (e.g., step S2103, but not limited thereto).

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

[0431] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto, and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and may also be a temporary storage medium.

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

[0433] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A communication indication method, characterized in that: Applied to a first network element, the method includes: Sending first information to a second network element, wherein the first information is used to indicate the service data flow SDF direction corresponding to the quality of service QoS processing based on the packet data unit PDU set, and the first information is used for the second network element to generate at least one policy and charging control PCC rule for the SDF.

2. The method according to claim 1, characterized in that The first information is used to indicate at least one of the following: Only the downlink PDU set is requested for QoS processing; Only the uplink PDU set is requested for QoS processing; Requesting QoS processing for the downlink PDU set and the uplink PDU set; Requesting the downlink PDU set and the uplink PDU set to perform QoS processing, and the quality of service QoS parameters corresponding to the downlink PDU set and the uplink PDU set are the same; Requesting QoS processing for the downlink PDU set and the uplink PDU set, wherein the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different; Requesting QoS processing for the downlink PDU set and the uplink PDU set, wherein QoS parameters corresponding to the downlink PDU set and the uplink PDU set are obtained based on network configuration; Requesting QoS processing for the downlink PDU set and the uplink PDU set, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are the same; The downlink PDU set and the uplink PDU set are requested to perform QoS processing, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are different.

3. The method according to claim 2, characterized in that The network configuration includes at least one of the following: Operator policy, configuration, subscription, terminal side support capabilities, radio access network RAN ​​support capabilities, session management function SMF support capabilities, user plane function UPF support capabilities, policy control function PCF support capabilities, terminal side activation capabilities, RAN activation capabilities, SMF activation capabilities, UPF activation capabilities, PCF activation capabilities.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Sending second information to the second network element, wherein the second information is used to indicate processing requirements of a PDU set in a related direction.

5. The method according to claim 4, characterized in that The second information is used to indicate at least one of the following: The QoS parameters of the PDU set are applied to the QoS flow in the upstream or downstream direction; PDU set specific QoS characteristics; At least one of an uplink PDU set specific QoS characteristic and a downlink PDU set specific QoS characteristic; Uplink protocol description or downlink protocol description; Related information of uplink SDF and downlink SDF.

6. The method according to claim 5, characterized in that The PDU set specific QoS characteristics include at least one of the following: The delay budget of the PDU set; Error rate of PDU set; Integrated processing information of PDU sets; Data flows to information.

7. The method according to claim 5, characterized in that The specific QoS characteristics of the uplink PDU set include at least one of the following: Delay budget for the upstream PDU set; Error rate of uplink PDU set; Integrated processing information of the upstream PDU set.

8. The method according to claim 5, characterized in that The specific QoS characteristics of the downlink PDU set include at least one of the following: Delay budget for the downlink PDU set; Downlink PDU set error rate; Integrated processing information of the downlink PDU set.

9. The method according to claim 5, characterized in that The relevant information of the uplink SDF and the downlink SDF includes: A pairing ID of the uplink SDF and the downlink SDF; A ratio or a threshold of a QoS parameter of the uplink PDU set to a QoS parameter of the downlink PDU set.

10. The method according to any one of claims 1 to 9, characterized in that: Sending the first information and the second information to the second network element includes any one of the following: sending the first information and the second information to the second network element through a network open function AF session with a QoS request procedure; sending the first information and the second information to the second network element through an AF session with a QoS request update procedure; sending the first information and the second information to the second network element through service specific parameter allocation; Sending the first information and the second information to the second network element through an AF session setting policy process; sending the first information and the second information to the second network element through a third network element; sending the first information and the second information to the second network element through a fourth network element; The first information and the second information are sent to the second network element through the third network element and the fourth network element.

11. The method according to any one of claims 1 to 10, characterized in that The first network element is an AF network element, the second network element is a policy control function PCF network element, the third network element is a network open function NEF network element, and the fourth network element is a time sensitive communication and time synchronization function TSCTSF network element.

12. A communication indication method, characterized in that: Applied to a second network element, the method comprises: Receiving first information sent by a first network element, wherein the first information is used to indicate an SDF direction corresponding to a QoS process based on a PDU set; At least one PCC rule is generated for the SDF according to the first information.

13. The method according to claim 12, characterized in that The first information is used to indicate at least one of the following: Only the downlink PDU set is requested for QoS processing; Only the uplink PDU set is requested for QoS processing; Requesting QoS processing for the downlink PDU set and the uplink PDU set; Requesting the downlink PDU set and the uplink PDU set to perform QoS processing, and the quality of service QoS parameters corresponding to the downlink PDU set and the uplink PDU set are the same; Requesting QoS processing for the downlink PDU set and the uplink PDU set, wherein the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different; Requesting QoS processing for the downlink PDU set and the uplink PDU set, wherein QoS parameters corresponding to the downlink PDU set and the uplink PDU set are obtained based on network configuration; Requesting QoS processing for the downlink PDU set and the uplink PDU set, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are the same; The downlink PDU set and the uplink PDU set are requested to perform QoS processing, the QoS parameters corresponding to the downlink PDU set and the uplink PDU set are different, and the QoS parameters corresponding to the downlink PDU and the uplink PDU are different.

14. The method according to claim 13, characterized in that The network configuration includes at least one of the following: Operator policy, configuration, subscription, terminal side support capabilities, radio access network RAN ​​support capabilities, session management function SMF support capabilities, user plane function UPF support capabilities, policy control function PCF support capabilities, terminal side activation capabilities, RAN activation capabilities, SMF activation capabilities, UPF activation capabilities, PCF activation capabilities.

15. The method according to any one of claims 12 to 14, characterized in that: The method further comprises: Receive second information sent by the first network element, wherein the second information is used to indicate processing requirements of a PDU set in a related direction.

16. The method according to claim 15, characterized in that The second information is used to indicate at least one of the following: The QoS parameters of the PDU set are applied to the QoS flow in the upstream or downstream direction; PDU set specific QoS characteristics; At least one of an uplink PDU set specific QoS characteristic and a downlink PDU set specific QoS characteristic; Uplink protocol description or downlink protocol description; Related information of uplink SDF and downlink SDF.

17. The method according to claim 16, characterized in that The PDU set specific QoS characteristics include at least one of the following: The delay budget of the PDU set; Error rate of PDU set; Integrated processing information of PDU sets; Data flows to information.

18. The method according to claim 16, characterized in that The specific QoS characteristics of the uplink PDU set include at least one of the following: Delay budget for the upstream PDU set; Error rate of uplink PDU set; Integrated processing information of the upstream PDU set.

19. The method according to claim 16, characterized in that The specific QoS characteristics of the downlink PDU set include at least one of the following: Delay budget for the downlink PDU set; Downlink PDU set error rate; Integrated processing information of the downlink PDU set.

20. The method according to claim 16, characterized in that The relevant information of the uplink service data flow SDF and the downlink SDF includes: A pairing ID of the uplink SDF and the downlink SDF; A ratio or a threshold between the QoS parameters of the uplink PDU set and the QoS parameters of the downlink PDU set.

21. The method according to any one of claims 12 to 20, characterized in that The PCC rules include QoS characteristics specific to the PDU set.

22. The method according to claim 20, characterized in that If the data flow direction information indicates that the flow direction is uplink, the PCC rule is applied to the uplink QoS flow in the SDF; If the data flow direction information indicates that the flow direction is downlink, the PCC rule is applied to the downlink QoS flow in the SDF; If the data flow direction information indicates that the flow direction is uplink and downlink, the PCC rule is applied to the uplink QoS flow and the downlink QoS flow in the SDF.

23. The method according to any one of claims 12 to 20, characterized in that The PCC rules include at least one of the following: QoS characteristics specific to the uplink PDU set; The downlink PDU set has specific QoS characteristics.

24. The method according to claim 23, characterized in that The specific QoS characteristics of the upstream PDU set are applied to the upstream QoS flow in the SDF, and the specific QoS characteristics of the downstream PDU set are applied to the downstream QoS flow in the SDF.

25. The method according to any one of claims 12 to 24, characterized in that Sending the first information and the second information to the second network element includes: sending the first information and the second information to the second network element through a network open function AF session with a QoS request procedure; sending the first information and the second information to the second network element through an AF session with a QoS request update procedure; sending the first information and the second information to the second network element through service specific parameter allocation; Sending the first information and the second information to the second network element through an AF session setting policy process; sending the first information and the second information to the second network element through a third network element; sending the first information and the second information to the second network element through a fourth network element; The first information and the second information are sent to the second network element through the third network element and the fourth network element.

26. The method according to any one of claims 12 to 25, characterized in that The first network element is an AF network element, the second network element is a policy control function PCF network element, the third network element is a network open function NEF network element, and the fourth network element is a time sensitive communication and time synchronization function TSCTSF network element.

27. A communication processing method, characterized in that: The method comprises: The first network element sends first information to the second network element, wherein the first information is used to indicate an SDF direction corresponding to the QoS processing based on the PDU set; The second network element generates at least one PCC rule for the SDF according to the first information.

28. A first network element, characterized in that: The device comprises: A transceiver module is used to send first information to a second network element, wherein the first information is used to indicate the service data flow SDF direction corresponding to the quality of service QoS processing based on the packet data unit PDU set, and the first information is used for the second network element to generate at least one policy and charging control PCC rule for the SDF.

29. A second network element, characterized in that: The device comprises: A transceiver module, configured to receive first information sent by a first network element, wherein the first information is used to indicate an SDF direction corresponding to a QoS process based on a PDU set; The processing module is configured to generate at least one PCC rule for the SDF according to the first information.

30. A core network device, characterized in that: The device comprises: A transceiver module, configured to send first information to a second network element, wherein the first information is used to indicate an SDF direction corresponding to the QoS processing based on the PDU set; or, receive the first information sent by the first network element; A processing module is used for the second network element to generate at least one PCC rule for the SDF according to the first information.

31. A first network element, characterized in that: include: one or more processors; The second network element is used to execute the communication processing method according to any one of claims 1 to 11.

32. A second network element, characterized in that: include: one or more processors; The second network element is used to execute the communication processing method according to any one of claims 12 to 26.

33. A core network device, characterized in that: include: one or more processors; Wherein, the core network device is used to execute the communication processing method described in claim 27.

34. A communication system, characterized in that: It comprises a first network element and a second network element, wherein the first network element is configured to implement the communication processing method described in any one of claims 1-11, and the second network element is configured to implement the communication processing method described in any one of claims 12-26.

35. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the communication processing method according to any one of claims 1 to 11 or claims 12 to 26.

Images