Communication methods, terminal, access network device, network element and communication system

Abstract

The present disclosure relates to communication methods, a terminal, an access network device, a network element, a communication system and a storage medium. A method comprises: sending first information, wherein the first information is used for indicating a first rule associated with a first device, with the first device being attached to a terminal, and the first information comprises identification information related to the first device. By means of the solution of the present disclosure, the support for the QoS characteristic of a service data flow of a device attached to a terminal is realized.

Description

Communication method, terminal, access network equipment, network element, communication system Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a communication method, a terminal, an access network device, a network element, a communication system, and a storage medium. Background Art

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

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

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide a communication method, a terminal, an access network device, a network element, a communication system, and a storage medium to provide support for QoS characteristics of service data flows of devices attached to the terminal.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to a first network element. The communication method includes: sending first information, wherein the first information is used to indicate a first rule associated with a first device, the first device being attached to a terminal; wherein the first information includes identification information related to the first device.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to a second network element. The communication method includes: sending fifth information, wherein the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to a terminal; wherein the fifth information includes identification information associated with the first device.

[0008] According to a third aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to a third network element. The communication method includes: receiving fifth information, wherein the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to a terminal; wherein the fifth information includes identification information associated with the first device.

[0009] According to a fourth aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to a fourth network element. The communication method includes receiving seventh information, wherein the seventh information is used to indicate data associated with a first device, the first device being attached to a terminal; wherein the seventh information includes identification information associated with the first device.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to a fifth network element. The communication method includes receiving third information, wherein the third information is used to indicate a second rule associated with a first device, the first device being attached to a terminal, and the second rule is used to implement QoS processing for a first service corresponding to the first device.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to an access network device. The communication method includes receiving eighth information, wherein the eighth information is used to indicate a third rule associated with a first device, the first device being attached to a terminal; wherein the eighth information includes identification information associated with the first device.

[0012] According to a seventh aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is applied to a terminal. The communication method includes receiving first information, wherein the first information is used to indicate a first rule associated with a first device, the first device being attached to the terminal; wherein the first information includes identification information related to the first device.

[0013] According to an eighth aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is performed by a core network. The core network includes a first network element, a second network element, and a third network element. The communication method includes: the second network element sending fifth information to the third network element, wherein the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to a terminal; wherein the first information includes identification information related to the first device; and the first network element sending first information, wherein the first information is used to indicate the first rule associated with the first device, and the first information includes identification information related to the first device.

[0014] According to a ninth aspect of an embodiment of the present disclosure, a communication method is provided. The communication method is performed by a core network. The core network includes a first network element and a fifth network element. The communication method includes: the first network element sending third information to the fifth network element, wherein the third information is used to indicate a second rule associated with a first device, and the second rule is used to implement QoS processing for a first service corresponding to the first device.

[0015] According to a tenth aspect of an embodiment of the present disclosure, a first network element is provided. The first network element includes: a transceiver module configured to send first information, wherein the first information is used to indicate a first rule associated with a first device, the first device being attached to a terminal; wherein the first information includes identification information related to the first device.

[0016] According to an eleventh aspect of an embodiment of the present disclosure, a second network element is provided. The second network element includes: a transceiver module configured to send fifth information, wherein the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to a terminal; wherein the fifth information includes identification information associated with the first device.

[0017] According to a twelfth aspect of an embodiment of the present disclosure, a third network element is provided. The third network element includes: a transceiver module configured to receive fifth information, wherein the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to a terminal; wherein the fifth information includes identification information associated with the first device.

[0018] According to a thirteenth aspect of an embodiment of the present disclosure, a fourth network element is provided. The fourth network element includes: a transceiver module configured to receive seventh information, wherein the seventh information is used to indicate data associated with a first device, the first device being attached to a terminal; wherein the seventh information includes identification information associated with the first device.

[0019] According to a fourteenth aspect of an embodiment of the present disclosure, a fifth network element is provided. The fifth network element includes: a transceiver module configured to receive third information, wherein the third information is used to indicate a second rule associated with a first device, the first device being attached to a terminal, and the second rule is used to implement QoS processing for a first service corresponding to the first device.

[0020] According to a fifteenth aspect of an embodiment of the present disclosure, an access network device is provided. The access network device includes: a transceiver module configured to receive eighth information, wherein the eighth information is used to indicate a third rule associated with a first device, the first device being attached to a terminal; wherein the eighth information includes identification information associated with the first device.

[0021] According to a sixteenth aspect of an embodiment of the present disclosure, a terminal is provided. The terminal includes: a transceiver module configured to receive first information, wherein the first information is used to indicate a first rule associated with a first device, the first device being attached to the terminal; wherein the first information includes identification information related to the first device.

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

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

[0024] According to a nineteenth aspect of an embodiment of the present disclosure, a third network element is provided. The third network element includes: one or more processors, and a memory storing instructions. When the instructions are executed by the third network element, the third network element implements the communication method described in the third aspect.

[0025] According to a twentieth aspect of an embodiment of the present disclosure, a fourth network element is provided. The fourth network element includes: one or more processors, and a memory storing instructions. When the instructions are executed by the fourth network element, the fourth network element implements the communication method described in the fourth aspect.

[0026] According to a twenty-first aspect of an embodiment of the present disclosure, a fifth network element is provided. The fifth network element includes: one or more processors, and a memory storing instructions. When the fifth network element executes the instructions, the fifth network element implements the communication method described in the fifth aspect.

[0027] According to a twenty-second aspect of an embodiment of the present disclosure, an access network device is provided. The access network device includes: one or more processors and a memory storing instructions. When the instructions are executed by the access network device, the access network device implements the communication method described in the sixth aspect.

[0028] According to a twenty-third aspect of an embodiment of the present disclosure, a terminal is provided. The terminal includes: one or more processors, and a memory storing instructions. When the instructions are executed by the terminal, the terminal implements the communication method described in the seventh aspect.

[0029] According to a twenty-fourth aspect of an embodiment of the present disclosure, a communication system is provided. The communication system includes a terminal, an access network device, and a core network device. The terminal is configured to implement the communication method described in the seventh aspect. The access network device is configured to implement the communication method described in the sixth aspect. The core network device is configured to implement the communication method described in the eighth or ninth aspect.

[0030] According to a twenty-fifth aspect of an embodiment of the present disclosure, a storage medium is provided. The storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the communication method as described in any one of the first to ninth aspects.

[0031] According to a twenty-sixth aspect of the embodiments of the present disclosure, a program product is provided. When the program product is executed by a communication device, the communication device executes the communication method as described in any one of the first to ninth aspects.

[0032] According to a twenty-seventh aspect of the embodiments of the present disclosure, a computer program is provided, which, when executed on a computer, causes the computer to execute the communication method according to any one of the first to ninth aspects.

[0033] According to a twenty-eighth aspect of the present disclosure, a chip or chip system is provided. The chip or chip system includes a processing circuit. The processing circuit is configured to execute the communication method described in any one of the first to ninth aspects.

[0034] Through the embodiments of the present disclosure, QoS processing can be performed on service data flows related to devices attached to a terminal, thereby providing support for QoS characteristics of service data flows of devices attached to the terminal.

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

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

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

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

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

[0040] FIG2A is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0062] Embodiments of the present disclosure provide a communication method, a terminal, an access network device, a network element, a communication system, and a storage medium.

[0063] In a first aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a first network element. The communication method includes: sending first information, wherein the first information is used to indicate a first rule associated with a first device, the first device being attached to a terminal; wherein the first information includes identification information related to the first device.

[0064] In the above embodiment, the identification information related to the first device is carried in the transmitted first information, so that the first rule indicated by the first information can be associated with the first device. In this way, the data flow corresponding to the first device can be identified and mapped to the corresponding QoS flow, thereby supporting the QoS characteristics of the service data flow of the first device attached to the terminal.

[0065] In combination with some embodiments of the first aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0066] In the above embodiment, the identification information may include first identification information and / or second identification information. The first identification information may identify the first device, thereby directly identifying the first device. The second identification information may identify an application associated with the first device, thereby indirectly identifying the first device. In this way, different identification methods can provide different identification granularities for the data stream of the first device, enhancing the flexibility of identifying the first device.

[0067] In combination with some embodiments of the first aspect, in some embodiments, the first information may also include first routing information; wherein, the first routing information is used to indicate that the traffic associated with the first device corresponds to one of the following: application service data flow associated with the first device, the same packet data unit (PDU) session, and the same QoS flow group.

[0068] In conjunction with some embodiments of the first aspect, in some embodiments, the first rule may include a user equipment route selection policy (UE route selection policy, URSP) rule.

[0069] In combination with some embodiments of the first aspect, in some embodiments, the identification information may be carried in a traffic descriptor of a URSP rule.

[0070] In conjunction with some embodiments of the first aspect, in some embodiments, the first information may include first routing information, and the first routing information is carried in a routing descriptor of a URSP rule.

[0071] In the above embodiment, the first rule may be a URSP rule. By modifying the URSP rule, adding parameters or reusing parameters, a UE policy for the data flow of the first service of the first device is implemented.

[0072] In combination with some embodiments of the first aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first data network name (DNN); or first single network slice selection assistance information (S-NSSAI).

[0073] In the above embodiment, the identification information of the first device may correspond to one or more of the following: the identification of the first device, the identification of an application associated with the first device, the identification of an application group associated with the first device, the first DNN, and the first S-NSSAI. In this way, different information can be used to correspond to the first service of the first device, providing flexible and multi-granular identification of the first device.

[0074] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: receiving second information, wherein the second information is used to indicate first data associated with the first device; and determining the first rule based on the second information.

[0075] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: sending third information, wherein the third information is used to indicate a second rule associated with the first device, and the second rule is used to implement QoS processing for the first service corresponding to the first device.

[0076] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: receiving fourth information, where the fourth information is used to indicate a service characteristic of the first service; and determining the second rule according to the fourth information.

[0077] In a second aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a second network element. The communication method includes: sending fifth information, wherein the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to a terminal; wherein the fifth information includes identification information associated with the first device.

[0078] In the above embodiment, the second network element can request determination of a first rule associated with the first device by sending the fifth information. By including identification information related to the first device in the fifth information, the first rule determined in response to the fifth information can be associated with the first device. In this way, the data flow corresponding to the first device can be identified and mapped to the corresponding QoS flow, thereby supporting the QoS characteristics of the service data flow of the first device attached to the terminal.

[0079] In combination with some embodiments of the second aspect, in some embodiments, the above method may further include: sending sixth information, wherein the sixth information is used to request session resources for the first service of the first device; wherein the sixth information includes identification information associated with the first device.

[0080] In combination with some embodiments of the second aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0081] In combination with some embodiments of the second aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; and identification information of the first QoS flow group.

[0082] In a third aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a third network element. The communication method includes receiving fifth information, wherein the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to a terminal; wherein the fifth information includes identification information associated with the first device.

[0083] In the above embodiment, the fifth information received by the third network element may request determination of a first rule associated with the first device. By including identification information related to the first device in the fifth information, the first rule determined in response to the fifth information can be associated with the first device. In this way, the data flow corresponding to the first device can be identified and mapped to the corresponding QoS flow, thereby supporting the QoS characteristics of the service data flow of the first device attached to the terminal.

[0084] In combination with some embodiments of the third aspect, in some embodiments, the above method may further include: sending seventh information, where the seventh information is used to indicate data associated with the first device.

[0085] In conjunction with some embodiments of the third aspect, in some embodiments, the method may further include: receiving sixth information, wherein the sixth information is used to request session resources for a first service of the first device; wherein the sixth information includes identification information associated with the first device. In conjunction with some embodiments of the third aspect, in some embodiments, the method may further include: sending fourth information, wherein the fourth information is used to indicate service characteristics of the first service.

[0086] In combination with some embodiments of the third aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0087] In combination with some embodiments of the third aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; and identification information of the first QoS flow group.

[0088] In a fourth aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a fourth network element. The communication method includes receiving seventh information, wherein the seventh information indicates data associated with a first device, the first device being attached to a terminal; wherein the seventh information includes identification information associated with the first device.

[0089] In combination with some embodiments of the fourth aspect, in some embodiments, the above method may further include: sending second information, wherein the second information is used to indicate first data associated with the first device.

[0090] In combination with some embodiments of the fourth aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0091] In combination with some embodiments of the fourth aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; and identification information of the first QoS flow group.

[0092] In a fifth aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a fifth network element. The communication method includes receiving third information, wherein the third information indicates a second rule associated with a first device, the first device being attached to a terminal, and the second rule is used to implement QoS processing for a first service corresponding to the first device.

[0093] In combination with some embodiments of the fifth aspect, in some embodiments, the above method may further include: sending eighth information, wherein the eighth information is used to indicate a third rule associated with the first device; wherein the eighth information includes identification information associated with the first device.

[0094] In combination with some embodiments of the fifth aspect, in some embodiments, the third rule may include a QoS attribute.

[0095] In combination with some embodiments of the fifth aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0096] In combination with some embodiments of the fifth aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; identification information of the first QoS flow group.

[0097] In a sixth aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to an access network device. The communication method includes receiving eighth information, wherein the eighth information indicates a third rule associated with a first device, the first device being attached to a terminal; wherein the eighth information includes identification information associated with the first device.

[0098] In combination with some embodiments of the sixth aspect, in some embodiments, the third rule may include a QoS attribute.

[0099] In combination with some embodiments of the sixth aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0100] In combination with some embodiments of the sixth aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; and identification information of the first QoS flow group.

[0101] In a seventh aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a terminal. The communication method includes receiving first information, wherein the first information indicates a first rule associated with a first device, the first device being attached to the terminal; wherein the first information includes identification information related to the first device.

[0102] In the above embodiment, the first information received by the terminal carries identification information related to the first device, so that the first rule indicated by the first information can be associated with the first device. In this way, the terminal can identify the data flow corresponding to the first device and map it to the corresponding QoS flow, thereby supporting the QoS characteristics of the service data flow of the first device attached to the terminal.

[0103] In combination with some embodiments of the seventh aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0104] In combination with some embodiments of the seventh aspect, in some embodiments, the first information may also include first routing information; wherein, the first routing information is used to indicate that the traffic associated with the first device corresponds to one of the following: application service data flow associated with the first device, the same PDU session, and the same QoS flow group.

[0105] In conjunction with some embodiments of the seventh aspect, in some embodiments, the first rule may include a URSP rule.

[0106] In combination with some embodiments of the seventh aspect, in some embodiments, the identification information may be carried in a traffic descriptor of a URSP rule.

[0107] In combination with some embodiments of the seventh aspect, in some embodiments, the first information may include first routing information, and the first routing information may be carried in a routing descriptor of a URSP rule.

[0108] In combination with some embodiments of the seventh aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; or a first S-NSSAI.

[0109] In combination with some embodiments of the seventh aspect, in some embodiments, the above method may further include: determining a data flow corresponding to the traffic of the first service of the first device according to a first rule, wherein the first rule corresponds to the identification information of the first device.

[0110] In combination with some embodiments of the seventh aspect, in some embodiments, the operation of determining the data flow corresponding to the traffic of the first service of the first device according to the first rule may include one of the following: determining an existing data flow corresponding to the traffic of the first service of the first device; creating a new data flow corresponding to the traffic of the first service of the first device.

[0111] In combination with some embodiments of the seventh aspect, in some embodiments, the data flow may include at least one of the following: application service data flow, PDU session, and QoS flow group.

[0112] In an eighth aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a core network. The core network includes a first network element, a second network element, and a third network element. The communication method includes: the second network element sending fifth information to the third network element, wherein the fifth information is used to request determination of a first rule associated with the first device, the first device being attached to a terminal; wherein the fifth information includes identification information related to the first device; and the first network element sending first information, wherein the first information is used to indicate the first rule associated with the first device, and the first information includes identification information related to the first device.

[0113] In conjunction with some embodiments of the eighth aspect, in some embodiments, the core network further includes a fourth network element. The communication method includes: the third network element sending seventh information to the fourth network element, where the seventh information is used to indicate data associated with the first device; and the fourth network element sending second information to the first network element, where the second information is used to indicate first data associated with the first device.

[0114] In a ninth aspect, embodiments of the present disclosure provide a communication method. The communication method is applied to a core network. The core network includes a first network element and a fifth network element. The communication method includes: the first network element sending third information to the fifth network element, wherein the third information is used to indicate a second rule associated with a first device, and the second rule is used to implement QoS processing for a first service corresponding to the first device.

[0115] In combination with some embodiments of the ninth aspect, in some embodiments, the above-mentioned communication method may also include: the fifth network element sends eighth information, wherein the eighth information is used to indicate the third rule associated with the first device, and the eighth information includes identification information associated with the first device.

[0116] In conjunction with some embodiments of the ninth aspect, in some embodiments, the core network may further include a second network element and a third network element. The communication method may further include: the second network element sending sixth information to the third network element, wherein the sixth information is used to request session resources for the first service of the first device, and the sixth information includes identification information associated with the first device; and the third network element sending fourth information to the first network element, wherein the fourth information is used to indicate service characteristics of the first service.

[0117] In a tenth aspect, an embodiment of the present disclosure provides a first network element. The first network element includes: a transceiver module configured to send first information, wherein the first information is used to indicate a first rule associated with a first device, the first device being attached to a terminal; wherein the first information includes identification information related to the first device.

[0118] In combination with some embodiments of the tenth aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0119] In combination with some embodiments of the tenth aspect, in some embodiments, the first information may also include first routing information; wherein, the first routing information is used to indicate that the traffic associated with the first device corresponds to one of the following: application service data flow associated with the first device, the same PDU session, and the same QoS flow group.

[0120] In combination with some embodiments of the tenth aspect, in some embodiments, the first rule may include a URSP rule.

[0121] In combination with some embodiments of the tenth aspect, in some embodiments, the identification information may be carried in a traffic descriptor of a URSP rule.

[0122] In combination with some embodiments of the tenth aspect, in some embodiments, the first information may include first routing information, and the first routing information is carried in a routing descriptor of a URSP rule.

[0123] In combination with some embodiments of the tenth aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; or a first S-NSSAI.

[0124] In combination with some embodiments of the tenth aspect, in some embodiments, the transceiver module can also be configured to: receive second information, wherein the second information is used to indicate first data associated with the first device; the first network element can also include: a processing module configured to determine the first rule based on the second information.

[0125] In combination with some embodiments of the tenth aspect, in some embodiments, the transceiver module can also be configured to: send third information, wherein the third information is used to indicate a second rule associated with the first device, and the second rule is used to implement QoS processing for the first service corresponding to the first device.

[0126] In combination with some embodiments of the tenth aspect, in some embodiments, the transceiver module can also be configured to: receive fourth information, where the fourth information is used to indicate the service characteristics of the first service; the processing module can also be configured to: determine the second rule based on the fourth information.

[0127] In an eleventh aspect, an embodiment of the present disclosure provides a second network element. The second network element includes: a transceiver module configured to send fifth information, wherein the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to a terminal; wherein the fifth information includes identification information associated with the first device.

[0128] In combination with some embodiments of the eleventh aspect, in some embodiments, the transceiver module can also be configured to: send sixth information, wherein the sixth information is used to request session resources for the first service of the first device; wherein the sixth information includes identification information associated with the first device.

[0129] In combination with some embodiments of the eleventh aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0130] In combination with some embodiments of the eleventh aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; identification information of the first QoS flow group.

[0131] In a twelfth aspect, an embodiment of the present disclosure provides a third network element. The third network element includes: a transceiver module configured to receive fifth information, wherein the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to a terminal; wherein the fifth information includes identification information associated with the first device.

[0132] In combination with some embodiments of the twelfth aspect, in some embodiments, the transceiver module can also be configured to: send seventh information, where the seventh information is used to indicate data associated with the first device.

[0133] In combination with some embodiments of the twelfth aspect, in some embodiments, the transceiver module can also be configured to: receive sixth information, wherein the sixth information is used to request session resources for the first service of the first device; wherein the sixth information includes identification information associated with the first device.

[0134] In combination with some embodiments of the twelfth aspect, in some embodiments, the transceiver module can also be configured to: send fourth information, where the fourth information is used to indicate the service characteristics of the first service.

[0135] In combination with some embodiments of the twelfth aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0136] In combination with some embodiments of the twelfth aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; identification information of the first QoS flow group.

[0137] In a thirteenth aspect, an embodiment of the present disclosure provides a fourth network element. The fourth network element includes: a transceiver module configured to receive seventh information, wherein the seventh information is used to indicate data associated with a first device, the first device being attached to a terminal; wherein the seventh information includes identification information associated with the first device.

[0138] In combination with some embodiments of the thirteenth aspect, in some embodiments, the transceiver module can also be configured to: send second information, wherein the second information is used to indicate first data associated with the first device.

[0139] In combination with some embodiments of the thirteenth aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0140] In combination with some embodiments of the thirteenth aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; identification information of the first QoS flow group.

[0141] In a fourteenth aspect, an embodiment of the present disclosure provides a fifth network element. The fifth network element includes: a transceiver module configured to receive third information, wherein the third information is used to indicate a second rule associated with a first device, the first device being attached to a terminal, and the second rule is used to implement QoS processing for a first service corresponding to the first device.

[0142] In combination with some embodiments of the fourteenth aspect, in some embodiments, the transceiver module can also be configured to: send eighth information, wherein the eighth information is used to indicate a third rule associated with the first device; wherein the eighth information includes identification information associated with the first device.

[0143] In combination with some embodiments of the fourteenth aspect, in some embodiments, the third rule may include a QoS attribute.

[0144] In combination with some embodiments of the fourteenth aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0145] In combination with some embodiments of the fourteenth aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; and identification information of the first QoS flow group.

[0146] In a fifteenth aspect, embodiments of the present disclosure provide an access network device. The access network device includes: a transceiver module configured to receive eighth information, wherein the eighth information is used to indicate a third rule associated with a first device, the first device being attached to a terminal; wherein the eighth information includes identification information associated with the first device.

[0147] In combination with some embodiments of the fifteenth aspect, in some embodiments, the third rule may include a QoS attribute.

[0148] In combination with some embodiments of the fifteenth aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0149] In combination with some embodiments of the fifteenth aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; identification information of the first QoS flow group.

[0150] In a sixteenth aspect, an embodiment of the present disclosure provides a terminal. The terminal includes: a transceiver module configured to receive first information, wherein the first information is used to indicate a first rule associated with a first device, the first device being attached to the terminal; wherein the first information includes identification information related to the first device.

[0151] In combination with some embodiments of the sixteenth aspect, in some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0152] In combination with some embodiments of the sixteenth aspect, in some embodiments, the first information may also include first routing information; wherein, the first routing information is used to indicate that the traffic associated with the first device corresponds to one of the following: application service data flow associated with the first device, the same PDU session, and the same QoS flow group.

[0153] In combination with some embodiments of the sixteenth aspect, in some embodiments, the first rule may include a URSP rule.

[0154] In combination with some embodiments of the sixteenth aspect, in some embodiments, the identification information may be carried in a traffic descriptor of a URSP rule.

[0155] In combination with some embodiments of the sixteenth aspect, in some embodiments, the first information may include first routing information, and the first routing information may be carried in a routing descriptor of a URSP rule.

[0156] In combination with some embodiments of the sixteenth aspect, in some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; or a first S-NSSAI.

[0157] In combination with some embodiments of the sixteenth aspect, in some embodiments, the terminal may further include a processing module configured to determine a data flow corresponding to the traffic of the first service of the first device according to a first rule, wherein the first rule corresponds to the identification information of the first device.

[0158] In combination with some embodiments of the sixteenth aspect, in some embodiments, the processing module can be configured to perform one of the following: determining an existing data flow corresponding to the traffic of the first service of the first device; creating a new data flow corresponding to the traffic of the first service of the first device.

[0159] In combination with some embodiments of the sixteenth aspect, in some embodiments, the data flow may include at least one of the following: application service data flow, PDU session, QoS flow group.

[0160] In a seventeenth aspect, an embodiment of the present disclosure provides a first network element. The first network element includes: one or more processors, and a memory storing instructions. When the instructions are executed by the first network element, the first network element implements the communication method as described in any one of the first aspect and possible implementations thereof.

[0161] In an eighteenth aspect, an embodiment of the present disclosure provides a second network element. The second network element includes: one or more processors and a memory storing instructions. When the instructions are executed by the second network element, the second network element implements the communication method as described in any one of the second aspect and possible implementations thereof.

[0162] In a nineteenth aspect, an embodiment of the present disclosure provides a third network element. The third network element includes: one or more processors and a memory storing instructions. When the third network element executes the instructions, the third network element implements the communication method as described in any one of the third aspect and possible implementations thereof.

[0163] In a twentieth aspect, an embodiment of the present disclosure provides a fourth network element. The fourth network element includes: one or more processors, and a memory storing instructions. When the fourth network element executes the instructions, the fourth network element implements the communication method as described in any one of the fourth aspect and possible implementations thereof.

[0164] In a twenty-first aspect, an embodiment of the present disclosure provides a fifth network element. The fifth network element includes: one or more processors, and a memory storing instructions. When the fifth network element executes the instructions, the fifth network element implements the communication method as described in any one of the fifth aspect and possible implementations thereof.

[0165] In a twenty-second aspect, embodiments of the present disclosure provide an access network device. The access network device includes one or more processors and a memory storing instructions. When executed by the access network device, the instructions enable the access network device to implement the communication method described in any one of the sixth aspect and possible implementations thereof.

[0166] In a twenty-third aspect, an embodiment of the present disclosure provides a terminal. The terminal includes: one or more processors and a memory storing instructions. When the instructions are executed by the terminal, the terminal implements the communication method as described in any one of the seventh aspect and possible implementations thereof.

[0167] In a twenty-fourth aspect, embodiments of the present disclosure provide a communications system. The communications system includes a terminal, an access network device, and a core network device. The terminal is configured to implement the communications method described in any one of the seventh aspect and possible implementations thereof. The access network device is configured to implement the communications method described in any one of the sixth aspect and possible implementations thereof. The core network device is configured to implement the communications method described in any one of the eighth and ninth aspects and possible implementations thereof.

[0168] In a twenty-fifth aspect, an embodiment of the present disclosure provides a storage medium. The storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the communication method as described in any one of the first to ninth aspects and possible implementations thereof.

[0169] In a twenty-sixth aspect, an embodiment of the present disclosure provides a program product. When the program product is executed by a communication device, the communication device executes the communication method as described in any one of the first to ninth aspects and possible implementations thereof.

[0170] In a twenty-seventh aspect, an embodiment of the present disclosure provides a computer program. When the computer program is executed on a computer, the computer executes the communication method as described in any one of the first to ninth aspects and possible implementations thereof.

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

[0172] It is understandable that the first network element, second network element, third network element, fourth network element, fifth network element, access network device, terminal, communication system, storage medium, program product, computer program, chip, and chip system are all used to execute the communication method provided in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0200] In some embodiments, the core network device 103 may be a device including a first network element 1031, a second network element 1032, a third network element 1033, a fourth network element 1034, a fifth network element 1035, a sixth network element 1036, a seventh network element 1037, 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, the third network element 1033, the fourth network element 1034, the fifth network element 1035, the sixth network element 1036, the seventh network element 1037, etc. The network element may be virtual or physical. The core network includes, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

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

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

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

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

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

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

[0207] In some embodiments, the fourth network element 1034 may be, for example, a unified data repository (UDR) function.

[0208] In some embodiments, the fourth network element 1034 may be used for unified data management (UDM) to store subscription data or read subscription data, and for PCF to store policy data or read policy data.

[0209] In some embodiments, the fifth network element 1035 may be, for example, a session management function (SMF).

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

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

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

[0213] In some embodiments, the seventh network element 1037 may be, for example, a UDM.

[0214] In some embodiments, the seventh network element 1037 can be used to store and manage the permanent user ID of the 5G system, subscription information management, user service network element registration management, etc., and the name is not limited to this.

[0215] In some embodiments, the second network element 1032 may be located outside the core network device 103 or may be located inside the core network device 103, which is not specifically limited in the embodiments of the present disclosure.

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

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

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

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

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

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

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

[0223] It should be noted that the UDR is not shown in FIG. 1C , but the UDR may provide a service-based interface Nudr.

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

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

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

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

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

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

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

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

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

[0233] In some cases, a terminal can access a wireless network, and one or more devices can be attached to the terminal. The devices attached to the terminal can be used to implement XRM services or multimedia services. For example, the device can be an XR device, a head-mounted device, an audio device, a display device, a haptic device, etc. In some embodiments, the data streams corresponding to these devices may also have corresponding QoS requirements. Therefore, the communication system needs to implement QoS mapping and guarantee for the data streams of the devices attached to the terminal.

[0234] FIG2A is an interactive diagram of a communication method according to an embodiment of the present disclosure. The communication method according to the embodiment of the present disclosure can be applied to the communication system 100. As shown in FIG2A, the communication method according to the embodiment of the present disclosure includes steps S2101 to S2112.

[0235] In step S2101 , the second network element 1032 creates a request.

[0236] In some embodiments, the request created by the second network element 1032 may be an AF request.

[0237] In some embodiments, the created request may be used to provide fifth information.

[0238] In some embodiments, the fifth information may be used to determine a first rule with the first device.

[0239] In some embodiments, the first device may be a device attached to the terminal 101. In one example, the first device may be attached to the terminal 101 in a wired or wireless manner. In one example, the first device may be an XRM device.

[0240] In some embodiments, the name of the first device is not limited, for example, it can be a tethered device, an external device, etc.

[0241] In some embodiments, the fifth information may include application information. In one example, the fifth information may include application guidance.

[0242] In some embodiments, the fifth information may include at least one of the following: identification information associated with the first device, the first DNN, and the first S-NSSAI.

[0243] In some embodiments, the identification information may be used to identify the first device.

[0244] In some embodiments, the name of the identification information is not limited, for example, it can be an identifier, an index number, an identification code, etc.

[0245] In some embodiments, the identification information may include at least one of the following: first identification information, second identification information.

[0246] In some embodiments, the first identification information may be used to identify the first device.

[0247] In some embodiments, the first identification information may be an identifier of the first device. In one example, the first identification information may be a hardware identifier of the first device. In one example, the first identification information may be an identifier assigned by the manufacturer of the first device. In one example, the first identification information may be an identifier assigned to the first device by a carrier. In some embodiments, identical first devices may have identical first identification information. In one example, XR devices of the same model may have the same identifier.

[0248] In some embodiments, the second identification information can be used to identify the application associated with the first device. In some embodiments, the application associated with the first device may include at least one of the following: an operating system of the first device, an application of the first device. In some embodiments, the application associated with the first device may be dedicated to the first device. At this time, the second identification information used to identify the application associated with the first device may correspond to the first device and may be used to identify the first device. In some embodiments, the application associated with the first device may include at least one of the following: an application, an application group. It can be understood that the application associated with the first device may be a single application or multiple applications. For the latter case, multiple applications may constitute an application group. In some embodiments, the second identification information may include an application identification associated with the first device. In one embodiment, the second identification information may include an application group identification associated with the first device.

[0249] In some embodiments, the identification information may be carried in an application traffic descriptor component of the AF request.

[0250] In some embodiments, the first DNN may be a DNN assigned to traffic related to the first device.

[0251] In some embodiments, the first S-NSSAI may be an S-NSSAI allocated to traffic related to the first device.

[0252] In some embodiments, the second network element 1032 may create a new request. In this case, the AF may invoke the Nnef_ServiceParameter_Create service operation. The new request may include subscription information for the results of UE policy delivery.

[0253] In some embodiments, the second network element 1032 may update or delete an existing request. In this case, the AF may initiate a Nnef_ServiceParameter_Update or Nnef_ServiceParameter_Delete service operation, and the corresponding transaction reference ID may be sent to the second network element 1032 via an Nnef_ServiceParameter_Create response message.

[0254] In some embodiments, before step S2101, the sixth network element 1036 may establish a terminal policy association. In one example, the policy association may be a UE policy association.

[0255] In some embodiments, before step S2101, the first network element 1031 may request the fourth network element 1034 to notify of a data change of the terminal 101. In one example, the data change of the terminal 101 may be a change in the terminal policy information of the terminal 101. In some embodiments, the first network element 1031 may request the fourth network element 1034 to notify of a data change of the first device attached to the terminal 101. In one example, the data change of the first device may be a change in the terminal policy information of the first device.

[0256] In step S2102 , the second network element 1032 sends fifth information to the third network element 1033 .

[0257] In some embodiments, the third network element 1033 may receive the fifth information.

[0258] In some embodiments, the fifth information may be carried in the request created by the second network element 1032 .

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

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

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

[0262] In step S2103 , the third network element 1033 interacts with the seventh network element 1037 .

[0263] In some embodiments, the third network element 1033 may interact with the seventh network element 1037 to implement mapping.

[0264] In some embodiments, the third network element 1033 may interact with the seventh network element 1037 through a Nudm_SDM_Get service operation. In one example, the third network element 1033 may send a Nudm_SDM_Get request message to the seventh network element 1037, and then the seventh network element 1037 may send a Nudm_SDM_Get response message to the third network element 1033.

[0265] In some embodiments, the third network element 1033 may obtain information from the seventh network element 1037 .

[0266] In some embodiments, the third network element 1033 may implement a mapping between a generic public subscription identifier (GPSI) and a subscription permanent identifier (SUPI) of the terminal 101 based on information obtained from the seventh network element 1037 .

[0267] In some embodiments, the third network element 1033 may implement mapping between the external group identifier and the internal group identifier of the terminal 101 based on the information obtained from the seventh network element 1037 .

[0268] In some embodiments, the request from the second network element 1032 may be authorized by the third network element 1033 .

[0269] In some embodiments, a mapping between an AF-Service-Identifier and a combination of a DNN and an S-NSSAI may be implemented based on a local configuration of the third network element 1033. In some embodiments, the combination of a DNN and an S-NSSAI may be a combination of a first DNN and a first S-NSSAI.

[0270] In some embodiments, the external application identifier may be mapped to an application identifier known within the core network. In some embodiments, the second identification information may be an external application identifier. In some embodiments, the second identification information may be an internal application identifier.

[0271] In step S2104, the third network element 1033 performs authorization.

[0272] In some embodiments, the third network element 1033 may manage the authorization of service specific parameters.

[0273] In some embodiments, the third network element 1033 may authorize the service-specific parameter request to the seventh network element 1037. In one example, for the cases of Nnef_ServiceParameter_Create and Nnef_ServiceParameter_Update, the third network element 1033 may send a service-specific parameter provision request to the seventh network element 1037 through the Nudm_ServiceSpecificAuthorisation_Create service operation authorization.

[0274] In some embodiments, the third network element 1033 may remove the authorization of the service-specific parameter provided by the seventh network element 1037. In one example, for the case of Nnef_ServiceParameter_Delete, the third network element 1033 may remove the authorization of the service-specific parameter provided by the seventh network element 1037 through the Nudm_ServiceSpecificAuthorisation_Remove service operation.

[0275] In step S2105 , the third network element 1033 sends seventh information to the fourth network element 1034 .

[0276] In some embodiments, the fourth network element 1034 may receive the seventh information.

[0277] In some embodiments, the seventh information may be used to indicate data associated with the first device.

[0278] In some embodiments, the seventh information may include data associated with the first device.

[0279] In some embodiments, the name of the seventh information is not limited, for example, it can be first device information, terminal information, service information, service-specific information, etc.

[0280] In some embodiments, the seventh information may include identification information associated with the first device.

[0281] In some embodiments, the seventh information may be included in the AF request information.

[0282] In some embodiments, the seventh information may be stored by the fourth network element 1034 as application data.

[0283] In some embodiments, the seventh information may be stored together with a processing reference identifier.

[0284] In step S2106 , the third network element 1033 sends a response message to the second network element 1032 .

[0285] In some embodiments, the second network element 1032 may receive a response message.

[0286] In some embodiments, the response message may be sent by the third network element 1033 in response to the request.

[0287] In some embodiments, the response message may be a Nnef_ServiceParameter_Create response message.

[0288] In some embodiments, the response message may be a Nnef_ServiceParameter_Update response message.

[0289] In some embodiments, the response message may be a Nnef_ServiceParameter_Delete response message.

[0290] In step S2107 , the fourth network element 1034 sends second information to the first network element 1031 .

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

[0292] In some embodiments, the second information may be used to indicate first data associated with the first device.

[0293] In some embodiments, the first data may include at least one of the following: new data associated with the first device, all data associated with the first device, and data that has changed in all data associated with the first device. In some cases, if new data associated with the first device exists in the fourth network element 1034, the second information sent by the fourth network element 1034 may include the new data. For example, if the fourth network element 1034 does not have data associated with the first device and new data associated with the first device is obtained, the fourth network element 1034 may carry the new data in the second information. In some cases, if the data associated with the first device in the fourth network element 1034 changes, the second information sent by the fourth network element 1034 may include all data associated with the first device after the change. In some cases, if the data associated with the first device in the fourth network element 1034 changes, the second information sent by the fourth network element 1034 may include the changed data associated with the first device.

[0294] It is understood that in some embodiments, the second information may be used to indicate a data change associated with the first device. The "data change" here may include providing new data, changing data, deleting data, etc., which is not specifically limited in the present embodiment.

[0295] In some embodiments, the fourth network element 1034 may send the second information upon receiving the seventh information.

[0296] In some embodiments, in the case of Nnef_ServiceParameter_Create, the data associated with the first device in the seventh information received by the fourth network element 1034 may be new data. In this case, the fourth network element 1034 may send the second information upon receiving the seventh information.

[0297] In some embodiments, the first network element 1031 may subscribe to data changes of the terminal 101 and / or the first device from the fourth network element 1034. In this case, the fourth network element 1034 may send the second information upon discovering data changes of the terminal 101 and / or the first device. It is understood that in some cases, there may be no data changes of the terminal 101 and / or the first device, in which case the fourth network element 1034 may not send the second information.

[0298] In some embodiments, the name of the second information is not limited, for example, it can be a policy change indication, data change information, etc.

[0299] In some embodiments, the second information may be carried in a Nudr_DM_Notify message.

[0300] In step S2108 , the first network element 1031 makes a policy decision.

[0301] In some embodiments, the first network element 1031 may perform a policy decision based on the received second information to obtain the first information.

[0302] In some embodiments, the first information may be used to indicate a first rule associated with the first device.

[0303] In some embodiments, the first rule may be used for mapping the traffic of the first service by the terminal 101 .

[0304] In some embodiments, the first rule may be a UE policy, and the first information may be UE policy information.

[0305] In some embodiments, the first information may include identification information.

[0306] In some embodiments, the identification information may correspond to at least one of the following: an identifier of the first device, an application identifier associated with the first device, an application group identifier associated with the first device, a first DNN, and a first S-NSSAI. It will be appreciated that in some embodiments, the identification information may include at least one of the following: an identifier of the first device, an application identifier associated with the first device, an application group identifier associated with the first device, a first DNN, and a first S-NSSAI. In one example, the identification information may include first identification information, and the first identification information may include the identifier of the first device. In this case, the first identification information used to identify the first device may be implemented by the identifier (e.g., an identifier) ​​of the first device. In one example, the identification information may include first identification information, and the first identification information may include the first DNN and the first S-NSSAI. In this case, the first identification information used to identify the first device may be implemented by a combination of the first DNN and the first S-NSSAI. In one example, the identification information may include second identification information, and the second identification information may include the application identifier associated with the first device. In this case, the second identification information used to identify the application associated with the first device may be implemented by an application identifier. In one example, the identification information may include second identification information, and the second identification information may include the application group identifier associated with the first device. In this case, the second identification information used to identify the application associated with the first device can be implemented by an application group identifier. In one example, the identification information may include the second identification information, and the second identification information may include the first DNN and the first S-NSSAI. In this case, the second identification information used to identify the application associated with the first device can be implemented by a combination of the first DNN and the first S-NSSAI. It should be noted that each of the first identification information and the second identification information can be implemented in other ways, and the embodiments of the present disclosure do not specifically limit this.

[0307] In some embodiments, the first information may include first routing information.

[0308] In some embodiments, the first routing information may be used to indicate a mapping relationship of traffic associated with the first device.

[0309] In some embodiments, the first routing information may be used to indicate that traffic associated with the first device corresponds to one of the following: an application service data flow associated with the first device, a same PDU session, and a same QoS flow group.

[0310] In some embodiments, the first routing information may be used to indicate that traffic associated with the first device is mapped to an application service data flow associated with the first device. In some embodiments, the first routing information may be used to indicate that traffic associated with the first device is transmitted via an application service data flow associated with the first device.

[0311] In some embodiments, the first routing information may be used to indicate that traffic associated with the first device is mapped to the same PDU session. In some embodiments, the first routing information may be used to indicate that traffic associated with the first device is transmitted through the same PDU session.

[0312] In some embodiments, the first routing information may be used to indicate that traffic associated with the first device is mapped to the same QoS flow group. In some embodiments, the first routing information may be used to indicate that traffic associated with the first device is transmitted through the same QoS flow group.

[0313] In some embodiments, the first rule may be a URSP rule.

[0314] In some embodiments, the URSP rule may include a first field. The first field includes identification information.

[0315] In some embodiments, the URSP rule may include a second field. The second field includes the first routing information.

[0316] In some embodiments, the URSP rule may include at least one of the following: a traffic descriptor, a routing descriptor.

[0317] In some embodiments, the first field may be included in a traffic descriptor. In this case, the identification information may be carried in the traffic descriptor.

[0318] In some embodiments, the first field may be included in a routing descriptor. In this case, the identification information may be carried in the routing descriptor.

[0319] In some embodiments, the second field may be included in a traffic descriptor. In this case, the first routing information may be carried in the traffic descriptor.

[0320] In some embodiments, the second field may be included in a routing descriptor. In this case, the first routing information may be carried in a traffic descriptor.

[0321] In some embodiments, the traffic descriptor may be used to indicate the traffic descriptor composition of the first rule.

[0322] In some embodiments, the traffic descriptor may include at least one of the following: a rule priority, an application descriptor, and an attached device identification.

[0323] In some embodiments, the rule priority may be used to indicate the priority with which the first rule is applied to the terminal 101 .

[0324] In some embodiments, the sending of the traffic descriptor can be implemented based on at least one of the first S-NSSAI, the first DNN, and the application traffic descriptor component.

[0325] In some embodiments, the application traffic descriptor component may include identification information.

[0326] In some embodiments, the application descriptor may include at least one of the following: an operating system identifier, an application program identifier. In some embodiments, the application descriptor may be second identification information.

[0327] In some embodiments, the attachment device identification may be used to identify the first device. In some embodiments, the attachment device identification may be the first identification information.

[0328] In some embodiments, the routing descriptor may include at least one of: routing descriptor priority, routing component, session and service continuity (SSC) mode selection, network slice selection, DNN selection, PDU session type selection, and attachment device selection.

[0329] In some embodiments, the routing descriptor priority may be used to indicate the priority with which the routing descriptor is applied to the terminal 101 .

[0330] In some embodiments, routing components may be used to define routing components.

[0331] In some embodiments, SSC Mode Select may be used to indicate the SSC mode.

[0332] In some embodiments, the network slice selection may be used to indicate one or more S-NSSAIs.

[0333] In some embodiments, DNN selection may be used to indicate one or more DNNs.

[0334] In some embodiments, a PDU session type selection may be used to indicate the PDU session type.

[0335] In some embodiments, the attachment device selection may be used to indicate at least one of the following: an application service data flow associated with the first device, a same PDU session, and a same QoS flow group. In some embodiments, the attachment device selection may be first routing information.

[0336] In step S2109 , the first network element 1031 sends first information to the terminal 101 .

[0337] In some embodiments, the first network element 1031 may send the first information to the terminal 101 via the sixth network element 1036 and the access network device 102 .

[0338] In some embodiments, the first network element 1031 may send the first information to the terminal 101 through a UE configuration update procedure.

[0339] In step S2110 , the first network element 1031 sends result information to the third network element 1033 .

[0340] In some embodiments, the third network element 1033 may receive result information.

[0341] In some embodiments, the result information may be used to indicate the result of the UE policy delivery.

[0342] In some embodiments, the result information may be carried in the Npcf_EventExposure_Notify message.

[0343] In step S2111 , the third network element 1033 sends a notification message to the second network element 1032 .

[0344] In some embodiments, the second network element 1032 may receive a notification message.

[0345] In some embodiments, the notification message may be a Nnef_ServiceParameter_Notify message.

[0346] In step S2112, the terminal 101 determines the data flow.

[0347] In some embodiments, the terminal 101 may determine the data flow corresponding to the service data flow of the first device based on the first information.

[0348] In some embodiments, the terminal 101 may map the data flow corresponding to the first device to the QoS flow according to the first rule indicated by the first information.

[0349] In some embodiments, the direction of the data flow may include at least one of the following: uplink data flow, downlink data flow.

[0350] In some embodiments, the terminal 101 may determine that the first service associated with the first device matches the identification information in the first information. In this case, the terminal 101 may determine that the first rule is applicable to the data flow of the first application.

[0351] In some embodiments, the first service may be a service corresponding to an application of the first device.

[0352] In some embodiments, terminal 101 may determine the first rule applicable to the first device according to a rule priority and / or a routing descriptor priority.

[0353] In some embodiments, the terminal 101 may determine an existing data flow corresponding to the traffic of the first service of the first device. In some embodiments, the terminal 101 may map the traffic of the first service of the first device to the existing data flow.

[0354] In some embodiments, the terminal 101 may determine a new data flow corresponding to the traffic of the first service of the first device. In some embodiments, the terminal 101 may map the traffic of the first service of the first device to the new data flow.

[0355] In some embodiments, the data flow corresponding to the traffic of the first service of the first device may include at least one of the following: an application service data flow, a PDU session, and a QoS flow group.

[0356] In some embodiments, when it is determined that multiple data streams correspond to traffic of the first service, terminal 101 can select one or more data streams from these data streams. In some embodiments, terminal 101 can select one or more data streams based on protocol provisions, local configuration, high-layer signaling, etc.

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

[0358] In some embodiments, at least two of steps S2101 to S2112 may be performed in an order-switched or synchronously. For example, steps S2106 and S2107 may be performed in an order-switched or synchronously.

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

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

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

[0362] FIG2B is an interactive diagram of a communication method according to an embodiment of the present disclosure. The communication method according to the embodiment of the present disclosure can be applied to the communication system 100. As shown in FIG2B , the communication method according to the embodiment of the present disclosure includes steps S2201 to S2208.

[0363] In step S2201 , the second network element 1032 sends sixth information to the third network element 1033 .

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

[0365] In some embodiments, the sixth information may be used to request determination of the second rule.

[0366] In some embodiments, the sixth information may be used to request session resources for the first service of the first device.

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

[0368] In some embodiments, the sixth information may include identification information associated with the first device.

[0369] In some embodiments, the identification information may include at least one of the following: first identification information, second identification information.

[0370] In some embodiments, the identification information may correspond to at least one of the following: an identifier of the first device, an application identifier associated with the first device, an application group identifier associated with the first device, a first DNN, a first S-NSSAI, and identification information of the first QoS flow group. It will be appreciated that in some embodiments, the identification information may include at least one of the following: an identifier of the first device, an application identifier associated with the first device, an application group identifier associated with the first device, a first DNN, a first S-NSSAI, and identification information of the first QoS flow group. In one example, the identification information may include first identification information, and the first identification information may include the identifier of the first device. In this case, the first identification information used to identify the first device may be implemented by the identifier (e.g., an identifier) ​​of the first device. In one example, the identification information may include first identification information, and the first identification information may include the first DNN and the first S-NSSAI. In this case, the first identification information used to identify the first device may be implemented by a combination of the first DNN and the first S-NSSAI. In one example, the identification information may include first identification information, and the first identification information may include identification information of the first QoS flow group. In this case, the first identification information used to identify the first device may be implemented by the identification information of the first QoS flow group. In one example, the identification information may include second identification information, and the second identification information may include an application identifier associated with the first device. In this case, the second identification information used to identify the application associated with the first device may be implemented by an application identifier. In one example, the identification information may include second identification information, and the second identification information may include an application group identifier associated with the first device. In this case, the second identification information used to identify the application associated with the first device may be implemented by an application group identifier. In one example, the identification information may include second identification information, and the second identification information may include a first DNN and a first S-NSSAI. In one example, the identification information may include second identification information, and the second identification information may include identification information of a first QoS flow group. In this case, the second identification information used to identify the application associated with the first device may be implemented by identification information of the first QoS flow group. In this case, the second identification information used to identify the application associated with the first device may be implemented by a combination of the first DNN and the first S-NSSAI. It should be noted that each of the first identification information and the second identification information may be implemented in other ways, and the present disclosure does not specifically limit this.

[0371] In some embodiments, the application identity associated with the first device may be mapped to a combination of the first DNN and the first S-NSSAI.

[0372] In some embodiments, the application group identifier associated with the first device can be mapped to a combination of the first DNN and the first S-NSSAI.

[0373] In some embodiments, the identification information of the first QoS flow group may be used to identify all QoS flows corresponding to the first service.

[0374] In some embodiments, the identification information of the first QoS flow group may include a group ID.

[0375] In some embodiments, the creation request may further include at least one of the following: UE address, UE identifier, AF identifier, application identifier, flow description, and QoS parameters.

[0376] In some embodiments, the second network element 1032 may create a request, and the sixth information may be carried in the created request.

[0377] In some embodiments, the sixth information may be carried in a request message sent by the second network element 1032 to the third network element 1033. In one example, the request message may be an AF session resource request message. In one example, the AF session resource request message may be an Nnef_AFSessionWithQoS_Create request message.

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

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

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

[0381] In step S2202, the third network element 1033 performs authorization.

[0382] In some embodiments, the third network element 1033 may authorize the request message from the second network element 1032 .

[0383] In some embodiments, the third network element 1033 may perform mapping.

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

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

[0386] In step S2203 , the third network element 1033 sends fourth information to the first network element 1031 .

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

[0388] In some embodiments, the fourth information may be used to indicate a service characteristic of the first service.

[0389] In some embodiments, the fourth information may be used to indicate a QoS attribute of the first service of the first device.

[0390] In some embodiments, the third network element 1033 may send the fourth information based on the sixth information received from the second network element 1032 .

[0391] In some embodiments, the content of the fourth information may be partially or completely identical to the content of the sixth information.

[0392] In some embodiments, the third network element 1033 may send the sixth information in the request message received from the second network element 1032 to the first network element. In this case, the fourth information and the sixth information may be the same.

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

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

[0395] In some embodiments, the third network element 1033 may determine to send the fourth information to the first network element 1031 through the TSCTSF. In some embodiments, the third network element 1033 may send the fourth information to the TSCTSF through the service-based interface Ntsftsf, and then the TSCTSF may send the fourth information to the first network element 1031 through the service-based interface Npcf. In one example, the third network element 1033 may send the fourth information to the TSCTSF through an Ntsctsf_QoSandTSCAssistance_Create request message, and then the TSCTSF may send the fourth information to the first network element 1031 through an Npcf_PolicyAuthorization_Create request message or an Npcf_PolicyAuthorization_Update request message.

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

[0397] In some embodiments, steps S2201 to S2203 may be omitted (ie, not executed). In this case, the first network element 1031 will not obtain the fourth information. Alternatively, the first network element 1031 may obtain the fourth information in other ways.

[0398] In some embodiments, the first network element 1031 may receive the fourth information from another first network element. In one example, after acquiring the fourth information, the other first network element may send the fourth information to the first network element 1031.

[0399] In some embodiments, the first network element 1031 may determine the fourth information based on operator operation and management configuration.

[0400] In some embodiments, the first network element 1031 may determine the fourth information according to local configuration.

[0401] In step S2204 , the first network element 1031 makes a policy decision.

[0402] In some embodiments, the first network element 1031 may perform a policy decision to determine the second rule.

[0403] In some embodiments, the first network element 1031 may determine a second rule associated with the first device based on the fourth information.

[0404] In some embodiments, the second rule is used to implement QoS processing for a first service corresponding to the first device.

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

[0406] In some embodiments, the second rule may be new. In some embodiments, according to the fourth information, the first network element 1031 may determine a new second rule.

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

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

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

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

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

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

[0413] In some embodiments, the response message may be an Npcf_PolicyAuthorization_Create response message. In this case, the Npcf_PolicyAuthorization_Create response message may be sent by the first network element 1031 in response to the Npcf_PolicyAuthorization_Create request message.

[0414] In step S2206 , the third network element 1033 sends a response message to the second network element 1032 .

[0415] In some embodiments, the second network element 1032 may receive a response message.

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

[0417] In some embodiments, the third network element 1033 may send a response message to the second network element 1032 after receiving the response message from the first network element 1031 .

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

[0419] In step S2207 , the first network element 1031 sends third information to the fifth network element 1035 .

[0420] In some embodiments, the fifth network element 1035 may receive the third information.

[0421] In some embodiments, the third information may be used to indicate a second rule associated with the first device.

[0422] In some embodiments, the third information may be sent to the fifth network element 1035 via the service-based interface Npcf.

[0423] In some embodiments, the first network element 1031 may initiate an SM Policy Association Modification process to send the third information.

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

[0425] In step S2208 , the fifth network element 1035 sends eighth information to the access network device 102 .

[0426] In some embodiments, the access network device 102 may receive the eighth information.

[0427] In some embodiments, the eighth information may be used to indicate a third rule associated with the first device.

[0428] In some embodiments, the third rule may include a QoS attribute.

[0429] In some embodiments, the QoS attributes may include at least one of the following: QoS rules, QoS parameters.

[0430] In some embodiments, the QoS rule may be a second rule, or determined based on a second rule.

[0431] In some embodiments, the fifth network element 1035 may send the eighth information to the access network device 102 via the sixth network element 1036 .

[0432] In some embodiments, the QoS attribute may be a user plane policy.

[0433] In some embodiments, steps S2207 and S2208 may be implemented through a PDU Session Modification procedure.

[0434] In some embodiments, the access network device 102 may receive identification information of the first device through the PDU session modification process.

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

[0436] In some embodiments, at least two of steps S2201 to S2108 may be executed in an interchangeable order or simultaneously. For example, steps S2205 and S2207 may be executed in an interchangeable order or simultaneously.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0450] FIG3A is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method. The communication method is performed by a first network element 1031. As shown in FIG3A , the method includes steps S3101 to S3104.

[0451] In step S3101, the second information is obtained.

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

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

[0454] In step S3102 , policy decision is performed.

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

[0456] In some embodiments, the first network element 1031 may perform policy decision based on the second information.

[0457] In step S3103, the first information is sent.

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

[0459] In some embodiments, the first network element 1031 may send the first information to the terminal 101 via the sixth network element 1036 and the access network device 102, but is not limited thereto and the first information may also be sent to other entities.

[0460] In step S3104, the result information is sent.

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

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

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

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

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

[0466] FIG3B is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method. The communication method is performed by the first network element 1031. As shown in FIG3B , the method includes steps S3201 to S3204.

[0467] In step S3201, the fourth information is obtained.

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

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

[0470] In some embodiments, the first network element 1031 may receive fourth information sent by another first network element.

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

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

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

[0474] In some embodiments, the first network element 1031 may determine the fourth information based on an operator operation and maintenance configuration.

[0475] In some embodiments, the first network element 1031 may determine the fourth information according to local configuration.

[0476] In step S3202, policy decision is performed.

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

[0478] In some embodiments, the first network element 1031 may perform policy decision-making based on the fourth information.

[0479] In step S3203, a response message is sent.

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

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

[0482] In step S3204, the third information is sent.

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

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

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

[0486] In some embodiments, at least two of steps S3201 to S3204 may be performed in an order-switched or synchronously. For example, steps S3203 and S3204 may be performed in an order-switched or synchronously.

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

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

[0489] FIG4A is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method. The communication method is performed by the second network element 1032. As shown in FIG4A , the method includes steps S4101 to S4104.

[0490] In step S4101, a request is created.

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

[0492] In some sets of embodiments, fifth information may be carried in the created request.

[0493] In step S4102, the fifth information is sent.

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

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

[0496] In step S4103, a response message is obtained.

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

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

[0499] In step S4104, a notification message is obtained.

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

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

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

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

[0504] FIG4B is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method. The communication method is executed by the second network element 1032. As shown in FIG4B , the method includes steps S4201 to S4202.

[0505] In step S4201, the sixth information is sent.

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

[0507] In some embodiments, the second network element 1032 may send the sixth information to the third network element 1033 , but is not limited thereto and may also send the sixth information to other entities.

[0508] In step S4202, a response message is obtained.

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

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

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

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

[0513] FIG5A is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method. The communication method is executed by a third network element 1033. As shown in FIG5A , the method includes steps S5101 to S5107.

[0514] In step S5101, the fifth information is obtained.

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

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

[0517] In step S5102, mapping is performed.

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

[0519] In some embodiments, the third network element 1033 may interact with the seventh network element 1037 to implement mapping, but is not limited thereto and may also interact with other entities.

[0520] In step S5103, authorization is performed.

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

[0522] In some embodiments, the third network element 1033 may interact with the seventh network element 1037 to implement authorization, but is not limited thereto and may also interact with other entities.

[0523] In step S5104, the seventh information is sent.

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

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

[0526] In step S5105, a response message is sent.

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

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

[0529] In step S5106, the result information is obtained.

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

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

[0532] In step S5107, a response message is sent.

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

[0534] In some embodiments, the third network element 1033 may send a notification message to the second network element 1032 , but is not limited thereto and may also send a notification message to other entities.

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

[0536] In some embodiments, at least two of steps S5101 to S5107 may be executed in an interchangeable order or simultaneously. For example, steps S5104 and S5105 may be executed in an interchangeable order or simultaneously.

[0537] In some embodiments, steps S5102 to S5107 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0539] FIG5B is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method. The communication method is executed by the third network element 1033. As shown in FIG5B , the method includes steps S5201 to S5205.

[0540] In step S5201, the sixth information is obtained.

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

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

[0543] In step S5202, authorization is performed.

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

[0545] In step S5203, the fourth information is sent.

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

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

[0548] In step S5204, a response message is obtained.

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

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

[0551] In step S5205, a response message is sent.

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

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

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

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

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

[0557] FIG6 is a flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method. The communication method is executed by the fourth network element 1034. As shown in FIG6, the method includes steps S601 to S602.

[0558] In step S601, seventh information is obtained.

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

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

[0561] In step S602, the second information is sent.

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

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

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

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

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

[0567] FIG7 is a flow chart of a communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method. The communication method is executed by the fifth network element 1035. As shown in FIG7, the method includes steps S701 to S702.

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

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

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

[0571] In step S702, the eighth information is sent.

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

[0573] In some embodiments, the fifth network element 1035 may send the eighth information to the access network device 102, but is not limited thereto and may also send the eighth information to other entities.

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

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

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

[0577] FIG8 is a flow chart of a communication method according to an embodiment of the present disclosure. The present disclosure relates to a communication method. The communication method is executed by access network device 102. As shown in FIG8, the method includes step S801.

[0578] In step S801, the eighth information is obtained.

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

[0580] In some embodiments, the access network device 102 may receive the eighth information sent by the fifth network element 1035 , but is not limited thereto and may also receive the eighth information sent by other entities.

[0581] FIG9 is a flow chart of a communication method according to an embodiment of the present disclosure. The present disclosure relates to a communication method. The communication method is executed by terminal 101. As shown in FIG9, the method includes steps S901 to S902.

[0582] In step S901, first information is obtained.

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

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

[0585] In step S902, the data flow is determined.

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

[0587] In some embodiments, the first information can be used by the terminal 101 to determine the data flow corresponding to the service data flow of the first device.

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

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

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

[0591] In step S10101 , the first network element 1031 sends first information to the terminal 101 .

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

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

[0594] In step S10201 , the second network element 1032 sends fifth information to the third network element 1033 .

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

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

[0597] In step S10301 , the third network element 1033 sends seventh information to the fourth network element 1034 .

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

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

[0600] In step S10401 , the first network element 1031 sends third information to the fifth network element 1035 .

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

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

[0603] In step S10501 , the fifth network element 1035 sends eighth information to the access network device 102 .

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

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

[0606] In some embodiments, for a subsequent attached device (i.e., first device) of the UE, 5GS supports providing URSP rules to the UE. The URSP rules include a tethered ID (i.e., identification information) as a traffic descriptor.

[0607] In some embodiments, based on the information provided by the AF for the attached device, the URSP with the attachment identifier in the traffic descriptor is sent to the UE (with the attached device) for policy delivery.

[0608] In some embodiments, attached devices are managed at the application layer.

[0609] In some embodiments, in 5GS, the attachment identity is unique within the PLMN and is used in the traffic descriptor of the URSP rule to route dedicated traffic for the attached device to a dedicated combination (e.g., a combination of DNN, S-NSSAI).

[0610] In some embodiments, all data of the same device connected to the UE may use the same PDU session or the same QoS flow group in a PDU session.

[0611] In some embodiments, the PCF (ie, the first network element) may carry an attachment identifier to the UE when issuing the URSP rule.

[0612] In some embodiments, when the UE initiates a response (uplink or downlink) service request, if the requested traffic flow is the SDF of the attached device, and there is an attachment identifier corresponding to the traffic flow in the URSP rule, the existing PDU session or QoS flow group corresponding to the attachment identifier can be selected to send the SDF.

[0613] In some embodiments, the AF (i.e., the second network element) initiates an AF session request to the PCF, which carries an attachment identifier and / or a combination of a DNN and S-NSSAI. The PCF performs policy decisions and authorization. Based on the attachment identifier and / or the combination of a DNN and S-NSSAI received in the AF session request, the PCF generates PCC rules and QoS authorization for the SDF of the attached device.

[0614] In some embodiments, the URSP may explicitly add an attachment identifier and / or an attachment identifier group indication (for example, adding an attachment identifier in a traffic descriptor and / or adding an attachment identifier selection in a routing descriptor) to carry it to the UE; or, the attachment identifier information may be implicitly carried to the UE (for example, carried in an application descriptor).

[0615] In some embodiments, the structure of the URSP rule can be seen in Table 1 and Table 2.

[0616] Table 1: Examples of some URSP content

[0617] In some embodiments, the PCF issues a traffic descriptor with an attachment identifier based on the S-NSSAI / DNN. The attachment identifier is only applied to the send / receive traffic of the device connected to the UE.

[0618] Table 2: Example of some contents of routing descriptor

[0619] In some embodiments, each URSP rule includes a routing descriptor list, which includes one or more routing descriptors. Each routing descriptor has a different routing descriptor priority value. The routing descriptor includes an attachment device selection.

[0620] In some embodiments, attachment device selection is used to indicate that traffic from matching attachment devices is to be transmitted over the same group or PDU session. Traffic can be directed from the device to the network, from the network to the device, or both. For example, if an established PDU session is used to route traffic from an attachment device, all traffic between the same attachment device and a service application connected to the UE should be transmitted over the same PDU session or group.

[0621] In some embodiments, in a UE process of associating an application to a PDU session based on a URSP, the UE may evaluate the URSP rules based on rule priority and determine whether the application matches a traffic descriptor (e.g., attachment identifier) ​​in a URSP rule. When it is determined that a URSP rule is applicable to a given application (e.g., an XRM service associated with a UE with an attached device), the UE may select a routing descriptor (e.g., attachment device selection) from the URSP based on the routing descriptor priority. When a valid routing descriptor is found, the UE may determine whether there is an existing PDU session that matches all components in the selected routing descriptor.

[0622] In some embodiments, when a matching PDU session exists, the UE associates the SDF of the attached device (identified by the attachment identifier) ​​with the existing PDU session, that is, routes traffic associated with the attachment identifier to the PDU session.

[0623] In some embodiments, if the UE determines that there are multiple existing PDU sessions that match, the UE may select a PDU session from these matching PDU sessions.

[0624] In some embodiments, in the process of AF providing service specific parameters (Service specific parameter provisioning by AF), the AF request sent to the NEF (i.e., the third network element) may include the following information:

[0625] (1) Business Description

[0626] The service description is used to identify the service that applies the service parameters. The service description in the AF request can be expressed as a combination of DNN and S-NSSAI, AF service identifier, and external application identifier.

[0627] (2) Business parameters

[0628] Service parameters are service-specific information that needs to be provided in the network and delivered to the UE, so as to support the service identified by the service description.

[0629] In some embodiments, when the AF provides application steering for determining the URSP for an attached device, the application traffic descriptor includes an attachment identifier. In addition, in 5GS, the attachment identifier (or the attachment identifier and the UE identifier) ​​is unique within the PLMN. The attachment identifier (or the attachment identifier and the UE identifier) ​​is used in the traffic descriptor of the URSP rule to route the dedicated traffic of the attached device to a dedicated combination, such as a DNN, S-NSSAI combination.

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

[0631] In some embodiments, the communication method in FIG. 11A may be implemented based on a process of providing service specific parameters (Service specific parameter provisioning by AF).

[0632] In some embodiments, the AF uses the Nnef_ServiceParameter service operation to provide service-specific parameters to the HPLMN and UE. In the roaming case, the PCF can be replaced by the H-PCF, the AMF can interact with the V-PCF, and the V-PCF can interact with the H-PCF.

[0633] As shown in FIG. 11A , the communication method provided by the embodiment of the present disclosure may include steps S11100 a to S11108 .

[0634] In step S11100a, the AMF establishes UE policy association.

[0635] In step S11100b, the PCF requests notification of UE policy information changes from the UDR (ie, the fourth network element).

[0636] In step S11101, the AF initiates the Nnef_ServiceParameter_Create service operation to create a new request. The request may include subscription information to enable reporting of the result of UE policy delivery.

[0637] In some embodiments, to update or delete an existing request, the AF invokes the Nnef_ServiceParameter_Update or Nnef_ServiceParameter_Delete service operation and uses the corresponding transaction reference identifier, which may have been previously provided to the AF in the Nnef_ServiceParameter_Create response message.

[0638] In some embodiments, where the AF provides application steering for determining the URSP for an attached device, the AF request contains the DNN, S-NSSAI allocated to services related to the attached device, and the application traffic descriptor component includes an attachment identifier.

[0639] In some embodiments, the attachment identity is applied to traffic sent / received by a device connected to the UE.

[0640] In step S11102, the AF sends an AF request to the NEF. The NEF authorizes the AF request and performs the following mappings: mapping the AF service identity to a combination of the DNN and S-NSSAI according to local configuration; and mapping the external application identity to a corresponding application identity known in the core network.

[0641] In step S11102a, the NEF may cause the Nudm_SDM_Get service operation to perform the following mappings: mapping the GPSI in the target UE identifier to the SUPI according to the information received from the UDM (i.e., the seventh network element); and mapping the external group identifier in the target UE identifier to the internal group identifier according to the information received from the UDM.

[0642] In some embodiments, if the result of UE policy issuance is subscribed to the AF, the AF may indicate where to receive the corresponding notification.

[0643] In some embodiments, in the case of Nnef_ServiceParameter_Create, the NEF assigns a processing reference identifier to the Nnef_ServiceParameter_Create request.

[0644] In step S11102b, in some embodiments, in the case of Nnef_ServiceParameter_Create or Nnef_ServiceParameter_Update, the NEF may need to authorize the service-specific parameter provision request to the UDM by sending a Nudm_ServiceSpecificAuthorisation_Create service operation.

[0645] In some embodiments, if authorization of a service-specific parameter provisioning request to the UDM is required as a response to an authorization request from the UDM (including SUPI or internal group identity), the NEF may skip mapping of the GPSI or external group identity.

[0646] In some embodiments, in case of Nnef_ServiceParameter_Delete, the NEF requests the UDM to remove the authorization for the provided service specific parameter by sending the Nudm_ServiceSpecificAuthorisation_Remove service operation.

[0647] In step S11103, in some embodiments, in case of Nnef_ServiceParameter_Create or Nnef_ServiceParameter_Update, the NEF stores the AF request information together with the assigned processing reference identifier in the UDR as "application data" (a data subset set to "service-specific information").

[0648] In some embodiments, in case of Nnef_ServiceParameter_Delete, the NEF deletes the AF request information from the UDR.

[0649] In step S11104, the NEF responds to the AF. In the case of an Nnef_ServiceParameter_Create response message, the response message may include an assigned processing reference identifier.

[0650] If the UE is registered with the network and the PCF subscribes to notifications for data modifications in the UDR (e.g., AF service parameter provision information, SUPI, a data set set as "application data", a data subset set as "service-specific information") by causing Nudr_DM_Subscribe in step S11100, the following steps may be performed.

[0651] In step S11105, the PCF receives the Nudr_DM_Notify notification of data change from the UDR.

[0652] In some embodiments, for an SDF associated with an attached device, the PCF generates a URSP and carries the attachment identifier in a traffic descriptor.

[0653] In some embodiments, the attachment identity matches an attachment identity of a dedicated attachment device configured for the UE having the attachment device.

[0654] In some embodiments, the PCF may issue a traffic descriptor with an attachment identifier based on the S-NSSAI / DNN / application traffic descriptor component. If necessary, the application traffic descriptor component may include an attachment identifier.

[0655] In step S11106, the PCF initiates UE policy delivery.

[0656] In some embodiments, based on information provided by the AF and issued by the policy for the attached device, a URSP rule carrying an attachment identifier in a traffic descriptor is sent to the UE (with the attached device).

[0657] In step S11107, when the AF subscribes to the notification of the result of UE policy issuance due to the provision of service-specific parameters, and the AMF (i.e., the fifth network element) notifies the PCF of the UE policy container, the PCF notifies the NEF of the UE policy issuance result contained in the UE policy container as a process result by sending Npcf_EventExposure_Notify. The Npcf_EventExposure_Notify includes the SUPI, GPSI list (if available), and internal group identity (if provided in step S11102a).

[0658] In step S11108, after receiving the Npcf_EventExposure_Notify, the NEF performs information mapping and triggers the appropriate Nnef_ServiceParameter_Notify message. The information mapping may include, for example, mapping the AF Transaction Internal ID provided in the Notification Correlation ID to the AF Transaction ID, mapping the SUPI to the GPSI, and mapping the internal group ID to the external group ID.

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

[0660] In some embodiments, the communication method in FIG. 11B may be implemented based on a process of establishing an AF session with required QoS procedure.

[0661] As shown in FIG. 11B , the communication method provided by the embodiment of the present disclosure may include steps S11201 to S11207 .

[0662] In step S11201, the AF sends an AF session resource request, for example, through the Nnef_AFsessionWithQoS_Create request, to create an AF request. The AF carries the attachment identifier, group identifier (optional), S-NSSAI (optional), DNN (optional), as well as UE address / UE identifier, AF identifier, application identifier, flow description, QoS parameters and other information in the request message. Optionally, the group identifier can be used to identify all flows of the corresponding attachment identifier in the XRM service. Optionally, the XRM service knowledge here is used to identify the flow as an XRM service. Optionally, the association identifier of the attached device can also be implicitly carried through the application identifier. The S-NSSAI and DNN here are carried in the UE AF request. Or the UE carries an external application identifier that can be mapped to a combination of S-NSSAI and DNN.

[0663] In step S11202, the NEF authorizes the AF request. In some embodiments, the NEF performs relevant mappings, including mapping application identifiers to DNNs and S-NSSAIs; or mapping external to internal XRM service group identifiers.

[0664] In step S11203, the NEF authorizes the AF request and, based on the parameters provided by the AF, determines whether to contact the TSCTSF or directly contact the PCF. The PCF receives the attributes provided by the AF from the NEF or TSCTSF. The NEF triggers the Npcf_PolicyAuthorization_Create request, sending the authorized AF request to the PCF with the aforementioned XRM service-related information and QoS information for PCF policy decision making.

[0665] In step S11204, the PCF makes a policy decision. The PCF may determine that updated policy information or new policy information needs to be sent to the SMF. The PCF performs policy decisions and authorizations (generating PCC rules and QoS authorizations for the service data flow of the XRM service based on the S-NSSAI and DNN received in the AF request). The PCF generates or updates PCC rules based on the NEF request. The PCF triggers Npcf_SMPolicyControl_UpdateNotify to update the policy information of the corresponding PDU session of the SMF, including the PCC rules and QoS policies related to the AF request.

[0666] In step S11205, the PCF sends an Npcf_PolicyAuthorization_Create response message to the NEF.

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

[0668] In step S11207, the SMF uses the PCC rules received from step S11204 to determine the authorized QoS for the QoS flow and triggers the Network requested PDU Session Modification procedure, thereby sending the updated QoS attributes as user plane policies to the NG-RAN together with the attachment identification information for the relevant service flow (via the AMF).

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

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

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

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

[0673] FIG12 is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. As shown in FIG12 , the communication device 1200 may include at least one of the following: a transceiver module 1201 and a processing module 1202 .

[0674] In a first aspect, the communication device 1200 may be the first network element 1031. In some embodiments, the transceiver module 1201 may be configured to send first information, where the first information is used to indicate a first rule associated with a first device, the first device being attached to a terminal; and where the first information includes identification information related to the first device.

[0675] In some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; and second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0676] In some embodiments, the first information may also include first routing information; wherein the first routing information is used to indicate that the traffic associated with the first device corresponds to one of the following: application service data flow associated with the first device, the same PDU session, and the same QoS flow group.

[0677] In some embodiments, the first rule may comprise a URSP rule.

[0678] In some embodiments, the identification information may be carried in a traffic descriptor of a URSP rule.

[0679] In some embodiments, the first information may include first routing information, and the first routing information is carried in a routing descriptor of a URSP rule.

[0680] In some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI.

[0681] In some embodiments, the transceiver module 1201 may be further configured to: receive second information, where the second information is used to indicate first data associated with the first device; and the processing module 1202 may be configured to determine the first rule based on the second information.

[0682] In some embodiments, the transceiver module 1201 may be further configured to: send third information, wherein the third information is used to indicate a second rule associated with the first device, and the second rule is used to implement QoS processing for a first service corresponding to the first device.

[0683] In some embodiments, the transceiver module 1201 may be further configured to: receive fourth information, where the fourth information is used to indicate a service characteristic of the first service; and the processing module 1202 may be further configured to: determine the second rule according to the fourth information.

[0684] Optionally, the transceiver module 1201 may be configured to execute at least one of the communication steps such as sending and / or receiving performed by the first network element 1031 in any of the above methods (e.g., steps S2107, S2109, S2110, S2203, S2205, S2207), which are not described in detail here. Optionally, the processing module 1202 may be configured to execute at least one of the other steps (e.g., steps S2108, S2204) other than the communication steps such as sending and / or receiving performed by the first network element 1031 in any of the above methods, which are not described in detail here.

[0685] In the second aspect, the communication device 1200 may be the second network element 1032. In some embodiments, the transceiver module 1201 may be configured to send fifth information, wherein the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to the terminal; wherein the fifth information includes identification information associated with the first device.

[0686] In some embodiments, the transceiver module 1201 may be further configured to: send sixth information, wherein the sixth information is used to request session resources for the first service of the first device; wherein the sixth information includes identification information associated with the first device.

[0687] In some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; and second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0688] In some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; identification information of the first QoS flow group.

[0689] Optionally, the transceiver module 1201 may be configured to execute at least one of the communication steps such as sending and / or receiving performed by the second network element 1032 in any of the above methods (e.g., steps S2102, S2106, S2111, S2201, S2206), which are not described in detail here. Optionally, the processing module 1202 may be configured to execute at least one of the other steps (e.g., step S2101) other than the communication steps such as sending and / or receiving performed by the second network element 1032 in any of the above methods, which are not described in detail here.

[0690] In a third aspect, the communication device 1200 may be the third network element 1033. In some embodiments, the transceiver module 1201 may be configured to receive fifth information, wherein the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to the terminal; wherein the fifth information includes identification information associated with the first device.

[0691] In some embodiments, the transceiver module may be further configured to: send seventh information, where the seventh information is used to indicate data associated with the first device.

[0692] In some embodiments, the transceiver module may be further configured to: receive sixth information, wherein the sixth information is used to request session resources for the first service of the first device; wherein the sixth information includes identification information associated with the first device.

[0693] In some embodiments, the transceiver module may be further configured to: send fourth information, where the fourth information is used to indicate a service characteristic of the first service.

[0694] In some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; and second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0695] In some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; identification information of the first QoS flow group.

[0696] Optionally, the transceiver module 1201 may be configured to execute at least one of the communication steps such as sending and / or receiving performed by the third network element 1033 in any of the above methods (for example, steps S2102, S2103, S2104, S2105, S2106, S2110, S2111, S2201, S2203, S2205, and S2206), which are not described in detail here. Optionally, the processing module 1202 may be configured to execute at least one of the other steps (for example, step S2202) other than the communication steps such as sending and / or receiving performed by the third network element 1033 in any of the above methods, which are not described in detail here.

[0697] In the fourth aspect, the communication device 1200 may be the fourth network element 1034. In some embodiments, the transceiver module 1201 may be configured to receive seventh information, wherein the seventh information is used to indicate data associated with a first device, the first device being attached to the terminal; wherein the seventh information includes identification information associated with the first device.

[0698] In some embodiments, the transceiver module 1201 may be further configured to: send second information, where the second information is used to indicate first data associated with the first device.

[0699] In some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; and second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0700] Optionally, the transceiver module 1201 can be configured to perform at least one of the communication steps such as sending and / or receiving (for example, steps S2105, 2107) performed by the fourth network element 1034 in any of the above methods, which will not be repeated here.

[0701] In the fifth aspect, the communication device 1200 may be the fifth network element 1035. In some embodiments, the transceiver module 1201 may be configured to receive third information, wherein the third information is used to indicate a second rule associated with a first device, the first device being attached to the terminal, and the second rule is used to implement QoS processing for a first service corresponding to the first device.

[0702] In some embodiments, the transceiver module 1201 may be further configured to: send eighth information, wherein the eighth information is used to indicate a third rule associated with the first device; wherein the eighth information includes identification information associated with the first device.

[0703] In some embodiments, the third rule may include a QoS attribute.

[0704] In some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; and second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0705] In some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; identification information of the first QoS flow group.

[0706] Optionally, the transceiver module 1201 can be configured to perform at least one of the communication steps such as sending and / or receiving (for example, steps S2207 and S2208) performed by the fifth network element 1035 in any of the above methods, which will not be repeated here.

[0707] In a sixth aspect, the communication device 1200 may be the access network device 102. In some embodiments, the transceiver module 1201 may be configured to receive eighth information, wherein the eighth information is used to indicate a third rule associated with a first device, the first device being attached to a terminal; wherein the eighth information includes identification information associated with the first device.

[0708] In some embodiments, the third rule may include a QoS attribute.

[0709] In some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; and second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0710] In some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI; identification information of the first QoS flow group.

[0711] Optionally, the transceiver module 1201 may be configured to execute at least one of the communication steps such as sending and / or receiving (eg, step S2208 ) executed by the access network device 102 in any of the above methods, which will not be described in detail here.

[0712] In a seventh aspect, the communication device 1200 may be the terminal 101. In some embodiments, the transceiver module 1201 may be configured to receive first information, wherein the first information is used to indicate a first rule associated with a first device, the first device being attached to the terminal; wherein the first information includes identification information related to the first device.

[0713] In some embodiments, the identification information may include at least one of the following: first identification information, wherein the first identification information is used to identify the first device; and second identification information, wherein the second identification information is used to identify an application associated with the first device.

[0714] In some embodiments, the first information may also include first routing information; wherein the first routing information is used to indicate that the traffic associated with the first device corresponds to one of the following: application service data flow associated with the first device, the same PDU session, and the same QoS flow group.

[0715] In some embodiments, the first rule may comprise a URSP rule.

[0716] In some embodiments, the identification information may be carried in a traffic descriptor of a URSP rule.

[0717] In some embodiments, the first information may include first routing information, and the first routing information may be carried in a routing descriptor of a URSP rule.

[0718] In some embodiments, the identification information may correspond to at least one of the following: an identification of the first device; an application identification associated with the first device; an application group identification associated with the first device; a first DNN; a first S-NSSAI.

[0719] In some embodiments, the processing module 1202 may be configured to determine, according to a first rule, a data flow corresponding to traffic of a first service of the first device, wherein the first rule corresponds to identification information of the first device.

[0720] In some embodiments, the processing module 1202 may be configured to perform one of the following: determining an existing data flow corresponding to the traffic of the first service of the first device; or creating a new data flow corresponding to the traffic of the first service of the first device.

[0721] In some embodiments, the data flow may include at least one of the following: an application service data flow, a PDU session, and a QoS flow group.

[0722] Optionally, the transceiver module 1201 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods (e.g., step S2109), which are not described in detail here. Optionally, the processing module 1202 may be configured to perform at least one of the other steps (e.g., step S2112) other than the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods, which are not described in detail here.

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

[0724] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules each 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.

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

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

[0727] In some embodiments, the communication device 13100 further includes one or more transceivers 13102. When the communication device 13100 includes one or more transceivers 13102, the transceiver 13102 performs at least one of the communication steps of sending and / or receiving in the above method (e.g., steps S2102, S2103, S2104, S2105, S2106, S2107, S2109, S2110, S2111, S2201, S2203, S2205, S2206, S2207, and S2208, but not limited thereto), and the processor 13101 performs at least one of the other steps (e.g., steps S2101, S2108, S2112, S2202, and S2204, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be replaced with each other, terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be replaced with each other, and terms such as receiver, receiving unit, receiver, and receiving circuit can be replaced with each other.

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

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

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

[0731] The chip 13200 includes one or more processors 13201. The chip 13200 is configured to execute any of the above methods.

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

[0733] In some embodiments, the interface circuit 13202 performs at least one of the communication steps of sending and / or receiving in the above method (e.g., steps S2102, S2103, S2104, S2105, S2106, S2107, S2109, S2110, S2111, S2201, S2203, S2205, S2206, S2207, and S2208, but not limited thereto). The interface circuit 13202 performing the communication steps of sending and / or receiving in the above method, for example, means that the interface circuit 13202 performs data exchange between the processor 13201, the chip 13200, the memory 13203, or the transceiver device. In some embodiments, the processor 13201 performs at least one of the other steps (e.g., steps S2101, S2108, S2112, S2202, and S2204, but not limited thereto).

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

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

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

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

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

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

Claims

1. A communication method, which is executed by a first network element, wherein, The method includes: Sending a first piece of information, where the first piece of information is used to indicate a first rule associated with a first device, and the first device is attached to a terminal; Wherein, the first piece of information includes identification information related to the first device.

2. The method according to claim 1, wherein, The identification information includes at least one of the following: First identification information, where the first identification information is used to identify the first device; Second identification information, where the second identification information is used to identify an application associated with the first device.

3. The method according to claim 1 or 2, wherein The first piece of information further includes first routing information; Wherein, the first routing information is used to indicate that the traffic associated with the first device corresponds to one of the following: the application service data stream associated with the first device, the same packet data unit (PDU) session, the same quality of service (QoS) flow group.

4. The method according to any one of claims 1 to 3, wherein The first rule includes a user equipment routing selection policy (URSP) rule.

5. The method according to claim 4, wherein, The identification information is carried in the traffic descriptor of the URSP rule.

6. The method according to claim 4 or 5, wherein, The first piece of information includes first routing information, and the first routing information is carried in the routing selection descriptor of the URSP rule.

7. The method according to any one of claims 1 to 6, wherein, The identification information corresponds to at least one of the following: The identification of the first device; The application identification associated with the first device; The application group identification associated with the first device; First data network name (DNN); First single network slice selection assistance information (S-NSSAI).

8. The method according to any one of claims 1 to 7, wherein, The method further includes: Receiving a second piece of information, where the second piece of information is used to indicate first data associated with the first device; Determining the first rule according to the second piece of information.

9. The method according to any one of claims 1 to 8, wherein The method further includes: Sending a third piece of information, where the third piece of information is used to indicate a second rule associated with the first device, and the second rule is used to implement QoS processing for a first service corresponding to the first device.

10. The method according to claim 9, wherein, The method further includes: Receiving a fourth piece of information, where the fourth piece of information is used to indicate the service characteristics of the first service; Determining the second rule according to the fourth piece of information.

11. A communication method, which is executed by a second network element, wherein, The method includes: Sending a fifth piece of information, where the fifth piece of information is used to request to determine a first rule associated with a first device, and the first device is attached to a terminal; Wherein, the fifth piece of information includes identification information associated with the first device.

12. The method according to claim 11, wherein, The method further includes: Sending a sixth piece of information, where the sixth piece of information is used to request session resources for a first service of the first device; Wherein, the sixth piece of information includes identification information associated with the first device.

13. The method according to claim 11 or 12, wherein, The identification information includes at least one of the following: First identification information, where the first identification information is used to identify the first device; Second identification information, where the second identification information is used to identify an application associated with the first device.

14. The method according to any one of claims 11 to 13, wherein the identification information corresponds to at least one of the following: The identification of the first device; The application identification associated with the first device; The application group identification associated with the first device; First DNN; First S-NSSAI; The identification information of the first quality of service (QoS) flow group.

15. A communication method, which is executed by an access network device, wherein, The method includes: Receive an eighth piece of information, where the eighth piece of information is used to indicate a third rule associated with a first device, and the first device is attached to a terminal; Wherein, the eighth piece of information includes identification information associated with the first device.

16. The method according to claim 15, wherein, The third rule includes Quality of Service (QoS) attributes.

17. The method according to claim 15 or 16, wherein The identification information includes at least one of the following: First identification information, where the first identification information is used to identify the first device; Second identification information, where the second identification information is used to identify an application associated with the first device.

18. The method according to any one of claims 15 to 17, wherein the identification information corresponds to at least one of the following: An identifier of the first device; An application identifier associated with the first device; An application group identifier associated with the first device; A first Data Network Name (DNN); A first Single Network Slice Selection Assistance Information (S-NSSAI); Identification information of a first Quality of Service (QoS) flow group.

19. A communication method, performed by a terminal, wherein, The method includes: Receive a first piece of information, where the first piece of information is used to indicate a first rule associated with a first device, and the first device is attached to the terminal; Wherein, the first piece of information includes identification information related to the first device.

20. The method according to claim 19, wherein The identification information includes at least one of the following: First identification information, where the first identification information is used to identify the first device; Second identification information, where the second identification information is used to identify an application associated with the first device.

21. The method according to claim 19 or 20, wherein, The first piece of information further includes first routing information; Wherein, the first routing information is used to indicate that the traffic associated with the first device corresponds to one of the following: an application service data stream associated with the first device, the same Packet Data Unit (PDU) session, the same Quality of Service (QoS) flow group.

22. The method according to any one of claims 19 to 21, wherein The first rule includes a User Equipment Routing Selection Policy (URSP) rule.

23. The method according to claim 22, wherein, The identification information is carried in a traffic descriptor of the URSP rule.

24. The method according to claim 22 or 23, wherein, The first piece of information includes first routing information, and the first routing information is carried in a routing selection descriptor of the URSP rule.

25. The method according to any one of claims 19 to 24, wherein, The identification information corresponds to at least one of the following: An identifier of the first device; An application identifier associated with the first device; An application group identifier associated with the first device; A first Data Network Name (DNN); A first Single Network Slice Selection Assistance Information (S-NSSAI).

26. The method according to any one of claims 19 to 25, wherein, The method further includes: Determine a data stream corresponding to the traffic of a first service of the first device according to the first rule, where the first rule corresponds to the identification information of the first device.

27. The method according to claim 26, wherein The determining, according to the first rule, a data stream corresponding to the traffic of a first service of the first device includes one of the following: Determine an existing data stream corresponding to the traffic of a first service of the first device; Create a new data stream corresponding to the traffic of a first service of the first device.

28. The method according to claim 26 or 27, wherein, The data stream includes at least one of the following: an application service data stream, a PDU session, a QoS flow group.

29. A communication method, executed by a core network, wherein, The core network includes a first network element, a second network element, and a third network element; Wherein, the method includes: The second network element sends fifth information to the third network element, where the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to a terminal, and the fifth information includes identification information associated with the first device; The first network element sends first information, where the first information is used to indicate a first rule associated with the first device, and the first information includes identification information related to the first device.

30. The method according to claim 29, wherein, The core network further includes a fourth network element; Wherein, the method further includes: The third network element sends seventh information to the fourth network element, where the seventh information is used to indicate data associated with a first device; The fourth network element sends second information to the first network element, where the second information is used to indicate first data associated with a first device.

31. A communication method, which is executed by a core network, wherein, The core network includes a first network element and a fifth network element; Wherein, the method includes: The first network element sends third information to the fifth network element, where the third information is used to indicate a second rule associated with a first device, and the second rule is used to implement QoS processing for a first service corresponding to the first device.

32. The communication method according to claim 31, wherein The method further includes: The fifth network element sends eighth information, where the eighth information is used to indicate a third rule associated with the first device, and the eighth information includes identification information associated with the first device.

33. The communication method according to claim 31 or 32, wherein The core network further includes a second network element and a third network element; Wherein, the method further includes: The second network element sends sixth information to the third network element, where the sixth information is used to request session resources for the first service of the first device, and the sixth information includes identification information associated with the first device; The third network element sends fourth information to the first network element, where the fourth information is used to indicate the service characteristics of the first service.

34. A first network element, comprising: A transceiver module configured to send first information, where the first information is used to indicate a first rule associated with a first device, the first device being attached to a terminal; Wherein, the first information includes identification information related to the first device.

35. A second network element, comprising: A transceiver module configured to send fifth information, where the fifth information is used to request determination of a first rule associated with a first device, the first device being attached to a terminal; Wherein, the fifth information includes identification information associated with the first device.

36. An access network device, comprising: A transceiver module configured to receive eighth information, where the eighth information is used to indicate a third rule associated with a first device, the first device being attached to a terminal; Wherein, the eighth information includes identification information associated with the first device.

37. A terminal, comprising: A transceiver module configured to receive first information, where the first information is used to indicate a first rule associated with a first device, the first device being attached to the terminal; Wherein, the first information includes identification information related to the first device.

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

39. A second network element, comprising: One or more processors; A memory storing instructions; Wherein, when the instructions are executed by the second network element, the second network element implements the communication method according to any one of claims 11 to 14.

40. An access network device, comprising: One or more processors; A memory storing instructions; Wherein, when the instructions are executed by the access network device, the access network device implements the communication method according to any one of claims 15 to 18.

41. A terminal, comprising: One or more processors; A memory storing instructions; Wherein, when the instructions are executed by the terminal, the terminal implements the communication method according to any one of claims 19 to 28.

42. A communication system, comprising a terminal, an access network device, and a core network device; Among them, The terminal is configured to implement the communication method according to any one of claims 19 to 28, the access network device is configured to implement the communication method according to any one of claims 15 to 18, and the core network device is configured to implement the communication method according to any one of claims 29 to 33.

43. A storage medium storing instructions, wherein, When the instructions run on the communication device, the communication device implements the method according to any one of claims 1 to 33.

Images