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

Abstract

The present disclosure relates to a communication method and apparatus, a communication device, a communication system, and a storage medium. The method comprises: receiving first information sent by a second network element, wherein the first information is used for determining a QoS policy of a first stream group, the first stream group comprises a plurality of streams, and the plurality of streams are related to a group pose and have a collaborative relationship. By means of the present disclosure, support can be provided for QoS processing of a stream group carrying group pose information.

Description

Communication methods and apparatus, communication equipment, communication systems and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method and apparatus, communication equipment, communication system and storage medium. Background Technology

[0002] In communication technologies such as 5G, mobile media services, online extended reality (XR), online games, and video-based remote control of machines or drones are expected to contribute increasing traffic to communication networks. In numerous application scenarios, pose information is used to achieve consistency between a user's movement in a real-world environment and their movement in a virtual environment.

[0003] Therefore, it is necessary to implement quality of service (QoS) management for pose information.

[0004] Summary of the Invention

[0005] This disclosure provides a communication method and apparatus, a communication device, a communication system, and a storage medium.

[0006] According to a first aspect of the present disclosure, a communication method is provided. The communication method is performed by a first network element. The communication method includes: receiving first information sent by a second network element, wherein the first information is used to determine a QoS policy for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0007] According to a second aspect of the present disclosure, a communication method is provided. The communication method is performed by a second network element. The communication method includes: sending first information to a first network element, wherein the first information is used to determine a QoS policy for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0008] According to a third aspect of the present disclosure, a communication method is provided. This communication method is performed by a third network element. The communication method includes: receiving second information sent by a first network element, wherein the second information is used to implement QoS processing for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0009] According to a fourth aspect of the present disclosure, a communication method is provided. The communication method is performed by a fourth network element. The communication method includes: receiving fourth information sent by a third network element, wherein the fourth information is used to mark a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0010] According to a fifth aspect of the present disclosure, a communication method is provided. The communication method is performed by a first device. The communication method includes: receiving data packets of a first flow group sent by a fourth network element, wherein the data packets contain group pose information, the group pose information being used by the first device to perform QoS processing on the data packets; wherein the first flow group includes multiple flows, the multiple flows being related to the group pose and having a cooperative relationship.

[0011] According to a sixth aspect of the present disclosure, a communication method is provided. This communication method is executed by a core network. The core network includes a first network element, a second network element, a third network element, and a fourth network element. The communication method includes at least one of the following: the first network element executes the communication method as described in the first aspect; the second network element executes the communication method as described in the second aspect; the third network element executes the communication method as described in the third aspect; and the fourth network element executes the communication method as described in the fourth aspect.

[0012] According to a seventh aspect of the present disclosure, a communication apparatus is provided. The communication apparatus is disposed in a first network element. The communication apparatus includes a transceiver module. The transceiver module is configured to receive first information transmitted by a second network element, wherein the first information is used to determine a QoS policy for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0013] According to an eighth aspect of the present disclosure, a communication apparatus is provided. The communication apparatus is disposed in a second network element. The communication apparatus includes a transceiver module. The transceiver module is configured to send first information to a first network element, wherein the first information is used to determine a QoS policy for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0014] According to a ninth aspect of the present disclosure, a communication device is provided. The communication device is disposed in a third network element. The communication device includes a transceiver module. The transceiver module is configured to receive second information sent by a first network element, wherein the second information is used to implement QoS processing for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0015] According to a tenth aspect of the present disclosure, a communication device is provided. The communication device is disposed in a fourth network element. The communication device includes a transceiver module. The transceiver module is configured to receive fourth information transmitted by a third network element, wherein the fourth information is used for marking a first stream group; wherein the first stream group includes multiple streams, and the multiple streams are related to the group pose and have a cooperative relationship.

[0016] According to an eleventh aspect of the present disclosure, a communication device is provided. The communication device is disposed in a first device. The communication device includes a transceiver module. The transceiver module is configured to receive data packets of a first flow group sent by a fourth network element, wherein the data packets contain group pose information, the group pose information being used by the first device to perform QoS processing on the data packets; wherein the first flow group includes multiple flows, the multiple flows being related to the group pose and having a cooperative relationship.

[0017] According to a twelfth aspect of the present disclosure, a communication device is provided. The communication device includes one or more processors and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in the first aspect.

[0018] According to a thirteenth aspect of this disclosure, a communication device is provided. The communication device includes one or more processors and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in the second aspect.

[0019] According to a fourteenth aspect of the present disclosure, a communication device is provided. The communication device includes one or more processors and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in the third aspect.

[0020] According to a fifteenth aspect of the present disclosure, a communication device is provided. The communication device includes one or more processors and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in the fourth aspect.

[0021] According to a sixteenth aspect of the present disclosure, a communication device is provided. The communication device includes one or more processors and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in the fifth aspect.

[0022] According to a seventeenth aspect of the present disclosure, a communication system is provided. The communication system includes: a first network element for implementing the communication method as described in the first aspect; a second network element for implementing the communication method as described in the second aspect; a third network element for implementing the communication method as described in the third aspect; a fourth network element for implementing the communication method as described in the fourth aspect; and a first device for implementing the communication method as described in the fifth aspect.

[0023] According to an eighteenth aspect of the present disclosure, a storage medium is provided. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any one of the first to sixth aspects.

[0024] According to a nineteenth aspect of the present disclosure, a program product is provided. When executed by a communication device, the program product causes the communication device to perform the communication method as described in any one of the first to sixth aspects.

[0025] According to a twentieth aspect of the present disclosure, a computer program is provided. When this computer program is run on a computer, it causes the computer to perform the communication method as described in any one of the first to sixth aspects.

[0026] According to a twenty-first aspect of this disclosure, a chip or chip system is provided. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication method as described in any one of the first to sixth aspects.

[0027] The embodiments disclosed herein enable support for QoS processing of flow groups with pose information.

[0028] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not constitute a limitation on the embodiments of this disclosure. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0030] Figure 1A is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0031] Figure 1B is a schematic diagram of the architecture of one implementation of a communication system provided according to an embodiment of the present disclosure.

[0032] Figure 1C is a schematic diagram of the architecture of another implementation of the communication system provided according to an embodiment of the present disclosure.

[0033] Figure 2A is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0034] Figure 2B is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0035] Figure 3A is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure.

[0036] Figure 3B is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure.

[0037] Figure 4A is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure.

[0038] Figure 4B is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure.

[0039] Figure 5A is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure.

[0040] Figure 5B is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure.

[0041] Figure 6A is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure.

[0042] Figure 6B is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure.

[0043] Figure 7 is a flowchart illustrating the communication method provided according to an embodiment of the present disclosure.

[0044] Figure 8A is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0045] Figure 8B is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0046] Figure 8C is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0047] Figure 8D is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0048] Figure 9A is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

[0049] Figure 9B is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

[0050] Figure 10 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0051] Figure 11A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0052] Figure 11B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. Detailed Implementation

[0053] This disclosure provides a communication method and apparatus, a communication device, a communication system, and a storage medium.

[0054] In a first aspect, embodiments of this disclosure provide a communication method. The communication method is applied to a first network element. The communication method includes: receiving first information sent by a second network element, wherein the first information is used to determine a QoS policy for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0055] According to this embodiment, the first network element can receive first information, and the first information is used to determine the QoS policy of a first flow group related to the group pose. Thus, based on the determined QoS policy, QoS authorization, coordination, and management can be implemented for multiple flows related to the group pose and having a cooperative relationship, thereby improving the user experience.

[0056] In conjunction with some embodiments of the first aspect, in some embodiments, the first information may include at least one of the following: first support information, used to indicate whether group pose is supported; flow group type information, used to indicate the flow group type of the first flow group; and auxiliary information, used to determine the QoS policy.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the flow group type of the first flow group may include at least one of the following: multiple flows correspond to the same pose information; multiple flows correspond to the same or associated timestamps; multiple flows correspond to the same or associated actions.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the auxiliary information may include at least one of the following: pose type information, used to indicate the pose type of the group pose; flow type information, used to indicate the flow type associated with the group pose; protocol information, used to indicate the transmission protocol of the group pose; pose sharing information, used to indicate whether the group pose is used for multiple terminal devices; pose group information, used to indicate the flow group corresponding to the group pose; and priority information, used to indicate the priority associated with the group pose.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include: sending second information to a third network element, wherein the second information is used to implement QoS processing for the first flow group.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the second information may include at least one of the following: second support information for indicating support group pose; flow group type information for indicating the flow group type of the first flow group; and auxiliary information for determining QoS policy.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include: determining a first rule based on first information, wherein the first rule includes second information.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, the second information may further include subscription information for subscribing to events related to the first stream group.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include: receiving third information sent by a third network element, wherein the third information is used to indicate an event related to the first flow group.

[0064] In a second aspect, embodiments of this disclosure provide a communication method. This communication method is applied to a second network element. The communication method includes: sending first information to a first network element, wherein the first information is used to determine a QoS policy for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0065] According to this embodiment, the second network element can send first information to the first network element, and the first information is used to determine the QoS policy of the first flow group related to the group pose. Thus, based on the determined QoS policy, QoS authorization, coordination, and management can be implemented for multiple flows related to the group pose and having a cooperative relationship, thereby improving the user experience.

[0066] In conjunction with some embodiments of the second aspect, in some embodiments, the first information may include at least one of the following: first support information, used to indicate whether group pose is supported; flow group type information, used to indicate the flow group type of the first flow group; and auxiliary information, used to determine the QoS policy.

[0067] In conjunction with some embodiments of the second aspect, in some embodiments, the flow group type of the first flow group may include at least one of the following: multiple flows correspond to the same pose information; multiple flows correspond to the same or associated timestamps; multiple flows correspond to the same or associated actions.

[0068] In conjunction with some embodiments of the second aspect, in some embodiments, the auxiliary information may include at least one of the following: pose type information, used to indicate the pose type of the group pose; flow type information, used to indicate the flow type associated with the group pose; protocol information, used to indicate the transmission protocol of the group pose; pose sharing information, used to indicate whether the group pose is used for multiple terminal devices; pose group information, used to indicate the flow group corresponding to the group pose; and priority information, used to indicate the priority associated with the group pose.

[0069] In a third aspect, embodiments of this disclosure provide a communication method. This communication method is applied to a third network element. The communication method includes: receiving second information sent by a first network element, wherein the second information is used to implement QoS processing for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0070] According to this embodiment, the third network element can receive second information, and the second information is used to implement QoS processing for the first flow group related to the group pose. In this way, corresponding QoS processing can be implemented for multiple flows that are related to the group pose and have a cooperative relationship, thereby improving the user experience.

[0071] In conjunction with some embodiments of the third aspect, in some embodiments, the second information may include at least one of the following: second support information for indicating support group pose; flow group type information for indicating the flow group type of the first flow group; and auxiliary information for determining QoS policy.

[0072] In conjunction with some embodiments of the third aspect, in some embodiments, the flow group type of the first flow group may include at least one of the following: multiple flows correspond to the same pose information; multiple flows correspond to the same or associated timestamps; multiple flows correspond to the same or associated actions.

[0073] In conjunction with some embodiments of the third aspect, in some embodiments, the auxiliary information may include at least one of the following: pose type information, used to indicate the pose type of the group pose; flow type information, used to indicate the flow type associated with the group pose; protocol information, used to indicate the transmission protocol of the group pose; pose sharing information, used to indicate whether the group pose is used for multiple terminal devices; pose group information, used to indicate the flow group corresponding to the group pose; priority information, used to indicate the priority associated with the group pose.

[0074] In conjunction with some embodiments of the third aspect, in some embodiments, the second information may be included in the first rule, which is determined at least based on the first information.

[0075] In conjunction with some embodiments of the third aspect, in some embodiments, the above method may further include: sending fourth information to a fourth network element, wherein the fourth information is used to mark the first flow group.

[0076] In conjunction with some embodiments of the third aspect, in some embodiments, the above method may further include: determining a second rule based on the second information, wherein the second rule includes the fourth information.

[0077] In conjunction with some embodiments of the third aspect, in some embodiments, both the second and fourth information may further include subscription information for subscribing to events related to the first stream group.

[0078] In conjunction with some embodiments of the third aspect, in some embodiments, the above method may further include: receiving third information sent by a fourth network element, wherein the third information is used to indicate an event related to the first flow group; and sending the third information to the first network element.

[0079] In a fourth aspect, embodiments of this disclosure provide a communication method. This communication method is applied to a fourth network element. The communication method includes: receiving fourth information sent by a third network element, wherein the fourth information is used to mark a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0080] According to this embodiment, the fourth network element can receive fourth information, which is used to mark the first flow group related to the group pose. This enables the identification of the first flow group, allowing for appropriate QoS processing of each flow within the first flow group, thereby improving the user experience.

[0081] In conjunction with some embodiments of the fourth aspect, in some embodiments, the fourth information may include at least one of the following: second support information for indicating support group pose; flow group type information for indicating the flow group type of the first flow group; and auxiliary information for determining QoS policies.

[0082] In conjunction with some embodiments of the fourth aspect, in some embodiments, the flow group type of the first flow group may include at least one of the following: multiple flows correspond to the same pose information; multiple flows correspond to the same or associated timestamps; multiple flows correspond to the same or associated actions.

[0083] In conjunction with some embodiments of the fourth aspect, in some embodiments, the auxiliary information may include at least one of the following: pose type information, used to indicate the pose type of the group pose; stream type information, used to indicate the stream type associated with the group pose; protocol information, used to indicate the transmission protocol of the group pose; pose sharing information, used to indicate whether the group pose is used for multiple terminal devices; pose group information, used to indicate the stream group corresponding to the group pose; and priority information, used to indicate the priority associated with the group pose.

[0084] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above method may further include: detecting group pose information in the first stream group according to the fourth information; adding the group pose information to the header of the data packet of the first stream group to realize the marking processing of the first stream group.

[0085] In conjunction with some embodiments of the fourth aspect, in some embodiments, the group pose information may include at least one of the following: a flow identifier for identifying multiple flows in a first flow group; an action identifier for identifying at least one action corresponding to the group pose; a timestamp for indicating the time of multiple flows in the first flow group; orientation coordinate values; position coordinate values; a pose array of multiple objects; and pose time.

[0086] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above method may further include: sending a data packet containing group pose information added to a first stream group to a first device, wherein the group pose information is used by the first device to perform QoS processing on the data packet.

[0087] In conjunction with some embodiments of the fourth aspect, in some embodiments, the fourth information may further include subscription information for subscribing to events related to the first stream group.

[0088] In a fifth aspect, embodiments of this disclosure provide a communication method. This communication method is applied to a first device. The communication method includes: receiving data packets of a first flow group sent by a fourth network element, wherein the data packets contain group pose information, and the group pose information is used by the first device to perform QoS processing on the data packets; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0089] According to this embodiment, the data packets received by the first device may include group pose information as a marker. Thus, the first device can adjust QoS parameters based on the group pose information marked in the data packets, thereby applying appropriate QoS processing to each flow in the first flow group and improving the user experience.

[0090] In conjunction with some embodiments of the fifth aspect, in some embodiments, the group pose information may include at least one of the following: a flow identifier for identifying multiple flows in a first flow group; an action identifier for identifying at least one action corresponding to the group pose; a timestamp for indicating the time of the multiple flows in the first flow group; orientation coordinate values; position coordinate values; a pose array of multiple objects; and pose time.

[0091] In conjunction with some embodiments of the fifth aspect, in some embodiments, the above method may further include: determining the QoS parameters of the QoS flow associated with the first flow group based on the group pose information.

[0092] In a sixth aspect, embodiments of this disclosure provide a communication method. This communication method is applied to a core network. The core network includes a first network element, a second network element, a third network element, and a fourth network element. The communication method includes at least one of the following: the first network element performs the communication method as described in any of the first aspect and its possible embodiments; the second network element performs the communication method as described in any of the second aspect and its possible embodiments; the third network element performs the communication method as described in any of the third aspect and its possible embodiments; and the fourth network element performs the communication method as described in any of the fourth aspect and its possible embodiments.

[0093] In a seventh aspect, embodiments of this disclosure provide a communication device. The communication device is disposed in a first network element. The communication device includes a transceiver module. The transceiver module is configured to receive first information transmitted by a second network element, wherein the first information is used to determine a QoS policy for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0094] In conjunction with some embodiments of the seventh aspect, in some embodiments, the first information may include at least one of the following: first support information for indicating whether group pose is supported; flow group type information for indicating the flow group type of the first flow group; and auxiliary information for determining QoS policy.

[0095] In conjunction with some embodiments of the seventh aspect, in some embodiments, the flow group type of the first flow group may include at least one of the following: multiple flows correspond to the same pose information; multiple flows correspond to the same or associated timestamps; multiple flows correspond to the same or associated actions.

[0096] In conjunction with some embodiments of the seventh aspect, in some embodiments, the auxiliary information may include at least one of the following: pose type information, used to indicate the pose type of the group pose; flow type information, used to indicate the flow type associated with the group pose; protocol information, used to indicate the transmission protocol of the group pose; pose sharing information, used to indicate whether the group pose is used for multiple terminal devices; pose group information, used to indicate the flow group corresponding to the group pose; and priority information, used to indicate the priority associated with the group pose.

[0097] In conjunction with some embodiments of the seventh aspect, in some embodiments, the transceiver module may also be configured to: send second information to a third network element, wherein the second information is used to implement QoS processing for the first flow group.

[0098] In conjunction with some embodiments of the seventh aspect, in some embodiments, the second information may include at least one of the following: second support information for indicating support group pose; flow group type information for indicating the flow group type of the first flow group; and auxiliary information for determining QoS policy.

[0099] In conjunction with some embodiments of the seventh aspect, in some embodiments, the above-described apparatus may further include a processing module. The processing module is configured to: determine a first rule based on first information, wherein the first rule includes second information.

[0100] In conjunction with some embodiments of the seventh aspect, in some embodiments, the second information may further include subscription information for subscribing to events related to the first stream group.

[0101] In conjunction with some embodiments of the seventh aspect, in some embodiments, the transceiver module may also be configured to: receive third information sent by a third network element, wherein the third information is used to indicate an event related to the first flow group.

[0102] In an eighth aspect, embodiments of this disclosure provide a communication device. The communication device is disposed in a second network element. The communication device includes a transceiver module. The transceiver module is configured to send first information to a first network element, wherein the first information is used to determine a QoS policy for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0103] In conjunction with some embodiments of the eighth aspect, in some embodiments, the first information may include at least one of the following: first support information for indicating whether group pose is supported; flow group type information for indicating the flow group type of the first flow group; and auxiliary information for determining QoS policy.

[0104] In conjunction with some embodiments of the eighth aspect, in some embodiments, the flow group type of the first flow group may include at least one of the following: multiple flows correspond to the same pose information; multiple flows correspond to the same or associated timestamps; multiple flows correspond to the same or associated actions.

[0105] In conjunction with some embodiments of the eighth aspect, in some embodiments, the auxiliary information may include at least one of the following: pose type information, used to indicate the pose type of the group pose; flow type information, used to indicate the flow type associated with the group pose; protocol information, used to indicate the transmission protocol of the group pose; pose sharing information, used to indicate whether the group pose is used for multiple terminal devices; pose group information, used to indicate the flow group corresponding to the group pose; and priority information, used to indicate the priority associated with the group pose.

[0106] In a ninth aspect, embodiments of this disclosure provide a communication device. The communication device is disposed in a third network element. The communication device includes a transceiver module. The transceiver module is configured to receive second information sent by a first network element, wherein the second information is used to implement QoS processing for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0107] In conjunction with some embodiments of the ninth aspect, in some embodiments, the second information may include at least one of the following: second support information for indicating support group pose; flow group type information for indicating the flow group type of the first flow group; and auxiliary information for determining QoS policy.

[0108] In conjunction with some embodiments of the ninth aspect, in some embodiments, the flow group type of the first flow group may include at least one of the following: multiple flows correspond to the same pose information; multiple flows correspond to the same or associated timestamps; multiple flows correspond to the same or associated actions.

[0109] In conjunction with some embodiments of the ninth aspect, in some embodiments, the auxiliary information may include at least one of the following: pose type information, used to indicate the pose type of the group pose; flow type information, used to indicate the flow type associated with the group pose; protocol information, used to indicate the transmission protocol of the group pose; pose sharing information, used to indicate whether the group pose is used for multiple terminal devices; pose group information, used to indicate the flow group corresponding to the group pose; and priority information, used to indicate the priority associated with the group pose.

[0110] In conjunction with some embodiments of the ninth aspect, in some embodiments, the second information may be included in the first rule, which is determined at least based on the first information.

[0111] In conjunction with some embodiments of the ninth aspect, in some embodiments, the transceiver module may also be configured to: send fourth information to the fourth network element, wherein the fourth information is used to mark the first flow group.

[0112] In conjunction with some embodiments of the ninth aspect, in some embodiments, the above-described apparatus may further include a processing module. The processing module is configured to: determine a second rule based on second information, wherein the second rule includes fourth information.

[0113] In conjunction with some embodiments of the ninth aspect, in some embodiments, both the second and fourth information may further include subscription information for subscribing to events related to the first stream group.

[0114] In conjunction with some embodiments of the ninth aspect, in some embodiments, the transceiver module may also be configured to: receive third information sent by a fourth network element, wherein the third information is used to indicate an event related to the first flow group; and send the third information to the first network element.

[0115] In a tenth aspect, embodiments of this disclosure provide a communication device. The communication device is disposed in a fourth network element. The communication device includes a transceiver module. The transceiver module is configured to receive fourth information transmitted by a third network element, wherein the fourth information is used to mark a first stream group; wherein the first stream group includes multiple streams, and the multiple streams are related to the group pose and have a cooperative relationship.

[0116] In conjunction with some embodiments of the tenth aspect, in some embodiments, the fourth information may include at least one of the following: second support information for indicating support group pose; flow group type information for indicating the flow group type of the first flow group; and auxiliary information for determining QoS policy.

[0117] In conjunction with some embodiments of the tenth aspect, in some embodiments, the flow group type of the first flow group may include at least one of the following: multiple flows corresponding to the same pose information; multiple flows corresponding to the same or associated timestamps; multiple flows corresponding to the same or associated actions.

[0118] In conjunction with some embodiments of the tenth aspect, in some embodiments, the auxiliary information may include at least one of the following: pose type information, used to indicate the pose type of the group pose; flow type information, used to indicate the flow type associated with the group pose; protocol information, used to indicate the transmission protocol of the group pose; pose sharing information, used to indicate whether the group pose is used for multiple terminal devices; pose group information, used to indicate the flow group corresponding to the group pose; and priority information, used to indicate the priority associated with the group pose.

[0119] In conjunction with some embodiments of the tenth aspect, in some embodiments, the above-described apparatus may further include a processing module. The processing module is configured to: detect group pose information in the first stream group according to the fourth information; and add the group pose information to the header of the data packet of the first stream group to implement marking processing of the first stream group.

[0120] In conjunction with some embodiments of the tenth aspect, in some embodiments, the group pose information may include at least one of the following: a flow identifier for identifying multiple flows in a first flow group; an action identifier for identifying at least one action corresponding to the group pose; a timestamp for indicating the time of multiple flows in the first flow group; orientation coordinate values; position coordinate values; a pose array of multiple objects; and pose time.

[0121] In conjunction with some embodiments of the tenth aspect, in some embodiments, the transceiver module may also be configured to: send data packets containing group pose information added to the first stream group to the first device, wherein the group pose information is used by the first device to perform QoS processing on the data packets.

[0122] In conjunction with some embodiments of the tenth aspect, in some embodiments, the fourth information may further include subscription information for subscribing to events related to the first stream group.

[0123] In an eleventh aspect, embodiments of this disclosure provide a communication device. The communication device is disposed in a first device. The communication device includes a transceiver module. The transceiver module is configured to receive data packets of a first flow group sent by a fourth network element, wherein the data packets contain group pose information, which is used by the first device to perform QoS processing on the data packets; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship.

[0124] In conjunction with some embodiments of the eleventh aspect, in some embodiments, the group pose information may include at least one of the following: a flow identifier for identifying multiple flows in a first flow group; an action identifier for identifying at least one action corresponding to the group pose; a timestamp for indicating the time of the multiple flows in the first flow group; a direction coordinate value; a position coordinate value; a pose array of multiple objects; and a pose time.

[0125] In conjunction with some embodiments of the eleventh aspect, in some embodiments, the above-described apparatus may further include a processing module. The processing module is configured to: determine the QoS parameters of the QoS flow associated with the first flow group based on the group pose information.

[0126] In a twelfth aspect, embodiments of this disclosure provide a communication device. The communication device includes one or more processors and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in any of the first aspect and its possible embodiments.

[0127] In a thirteenth aspect, embodiments of this disclosure provide a communication device. The communication device includes one or more processors and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in any of the second aspect and its possible embodiments.

[0128] In a fourteenth aspect, embodiments of this disclosure provide a communication device. The communication device includes one or more processors and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in any of the third aspect and its possible embodiments.

[0129] In a fifteenth aspect, embodiments of this disclosure provide a communication device. The communication device includes one or more processors and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in any of the fourth aspect and its possible embodiments.

[0130] In a sixteenth aspect, this disclosure provides a communication device. The communication device includes one or more processors and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in any of the fifth aspect and its possible embodiments.

[0131] In a seventeenth aspect, embodiments of this disclosure provide a communication system. The communication system includes at least one of the following: a first network element for implementing the communication method as described in any of the first aspect and its possible embodiments; a second network element for implementing the communication method as described in any of the second aspect and its possible embodiments; a third network element for implementing the communication method as described in any of the third aspect and its possible embodiments; a fourth network element for implementing the communication method as described in any of the fourth aspect and its possible embodiments; and a first device for implementing the communication method as described in any of the fifth aspect and its possible embodiments.

[0132] In an eighteenth aspect, embodiments of this disclosure provide a storage medium storing instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any of the first to sixth aspects and their possible embodiments.

[0133] In a nineteenth aspect, embodiments of this disclosure provide a program product. When executed by a communication device, the program product causes the communication device to perform the communication method as described in any of the first to sixth aspects and their possible embodiments.

[0134] In a twentieth aspect, embodiments of this disclosure provide a computer program. When this computer program is run on a computer, it causes the computer to perform the communication methods described in any of the first to sixth aspects and their possible implementations.

[0135] In a twenty-first aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform a communication method as described in any one of the first to sixth aspects and their possible embodiments.

[0136] It is understood that the aforementioned communication devices, communication equipment, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to execute the communication methods provided in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0137] This disclosure provides a communication method and apparatus, a communication device, a communication system, and a storage medium. In some embodiments, terms such as communication method and information processing method can be used interchangeably; terms such as communication apparatus, communication device, and information processing apparatus can be used interchangeably; and terms such as information processing system and communication system can be used interchangeably.

[0138] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless contradictory, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementations in a particular embodiment can be arbitrarily combined. Moreover, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined. As another example, a particular embodiment can be arbitrarily combined with optional implementations of other embodiments.

[0139] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0140] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0141] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0142] In the embodiments of this disclosure, "multiple" refers to two or more.

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

[0144] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0145] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0146] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0147] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0148] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0149] In some embodiments, the terms “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 lower than,” and “above” can be used interchangeably, as can the terms “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”.

[0150] 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”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0151] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0152] 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," and "bandwidth part (BWP)" can be used interchangeably.

[0153] 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", and "client" can be used interchangeably.

[0154] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0155] 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, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0156] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0158] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0159] Figure 1A is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure. As shown in Figure 1A, the communication system 100 includes a terminal 101, a first device 102, and a core network 103.

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

[0161] In some embodiments, the first device 102 may be an access network device. It is understood that the first device 102 may also be other devices or apparatuses such as terminal devices or core network devices, and this disclosure does not specifically limit them.

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

[0163] In some embodiments, the technical solutions of this disclosure can be applied to Open Radio Access Network (Open RAN) architectures. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0164] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0165] In some embodiments, the core network 103 may be a single 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 it may be multiple devices or a group of devices, each 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. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0166] In some embodiments, the first network element 1031 may be, for example, a control plane network function.

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

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

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

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

[0171] In some embodiments, the third network element 1033 may be, for example, a control plane network function.

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

[0173] In some embodiments, the third network element 1033 can be used for functions such as session management, execution of PCF-issued control policies, selection of UPF, and allocation of UE Internet Protocol (IP) addresses, and its name is not limited thereto.

[0174] In some embodiments, the fourth network element 1034 may be a user plane network function.

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

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

[0177] In some embodiments, the fifth network element 1035 may be, for example, an application server (AS).

[0178] In some embodiments, the fifth network element 1035 may be used to provide support for user-subscribed services, and the name is not limited thereto.

[0179] In some embodiments, the sixth network element 1036 may be a control plane network function.

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

[0181] In some embodiments, the sixth network element 1036 can be used to perform 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 thereto.

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

[0183] In some embodiments, the seventh network element 1037 can be used to ensure the security of external applications to the 3GPP network, and provide external applications with QoS customization capabilities, mobility state time subscription, AF request distribution, etc., and the name is not limited thereto.

[0184] In some embodiments, the second network element 1032 may be located outside the core network device 103 or inside the core network device 103, and this disclosure does not specifically limit this.

[0185] In some embodiments, the fifth network element 1035 may be located outside the core network device 103 or inside the core network device 103, and this disclosure does not specifically limit this.

[0186] In some embodiments, the second network element 1032 and the fifth network element 1035 can be deployed centrally or independently, and this disclosure does not specifically limit this.

[0187] In some embodiments, the communication system 100 described above 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, and this disclosure does not specifically limit the types of communication systems used.

[0188] Figures 1B and 1C illustrate the architecture of a communication system using a 5G communication system as an example. Here, terminal 101 can be a UE, and first device 102 can be a RAN.

[0189] Figure 1B is a schematic diagram of the architecture of one implementation of the communication system provided according to an embodiment of the present disclosure. As shown in Figure 1B, the architecture of the 5G communication system is presented in the form of reference points. N1 is the reference point between the UE and AMF. N2 is the reference point between the RAN and AMF. N3 is the reference point between the RAN and UPF. N4 is the reference point between the SMF and UPF. N5 is the reference point between the PCF and AF. N6 is the reference point between the UPF and the data network (DN). N7 is the reference point between the SMF and PCF. N11 is the reference point between the AMF and SMF. N15 is the reference point between the SMF and PCF. Uu is the interface between the UE and the RAN. It should be noted that the NEF is not shown in Figure 1B. However, each network element in the communication system can interact with the NEF.

[0190] Figure 1C is a schematic diagram of the architecture of another implementation of the communication system provided according to an embodiment of the present disclosure. As shown in Figure 1C, the architecture of the 5G communication system is presented in a service-based interface manner. Namf is the service-based interface provided by AMF. Nsmf is the service-based interface provided by SMF. Nnef is the service-based interface provided by NEF. Npcf is the service-based interface provided by PCF. Naf is the service-based interface provided by AF.

[0191] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0192] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or some of the main components in the communication system 100, but are not limited thereto. The main components shown in FIG1A are illustrative. The communication system 100 may include all or some of the main components in FIG1A, or may include other main components other than those in FIG1A. The number and form of each main component are arbitrary. Each main component may be physical or virtual. The connection relationship between the main components is illustrative. The main components may not be connected or may be connected. The connection may be in any way, such as direct connection or indirect connection, wired connection or wireless connection.

[0193] The embodiments disclosed herein 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), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a 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, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0194] In some cases, mobile media services, online AR / VR and other XR services, online games, and video-based remote control of machines or drones are expected to contribute increasingly higher traffic to communication networks. XR services involve multimodal data streams. Multimodal data describes data input from the same device or different devices (including sensors) for the same service / application, which may be output to one or more destination device terminals. The data streams in multimodal data often have a certain degree of correlation, or even a strong correlation, such as the synchronization of audio and video streams, or the synchronization of haptic and visual senses. The data streams of these media services themselves, the relationships between the data streams, and the network transmission requirements of these service data streams all share some common characteristics. Effective identification and utilization of these characteristics will be more conducive to network and service transmission and control, and will also contribute to service assurance and user experience.

[0195] In further scenarios, XRM services and eXtended Reality and interactive media services require communication systems to comprehensively consider the QoS characteristics of service data streams. These QoS characteristics include, for example, at least one of the following: whether parameters such as delay-sensitive guaranteed bit rate (GBR) data streams, guaranteed flow bit rate (GFBR), packet delay budget (PDB), and default maximum data burst volume (MDBV) can be simultaneously met and consistently maintained. This involves ensuring consistent QoS authorization and execution across multiple XRM data streams from a single terminal and across multiple terminals.

[0196] In some embodiments, the XRM service data flow (SDF) can be processed based on PDU sets, thereby enhancing QoS awareness and assurance of the SDF and improving the user's quality of experience (QoE).

[0197] In some embodiments, such as 4G, 5G, 6G, and V2X systems, the AF (Active Front-End) can 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 (Service Provider Framework) and UPF (User Provider Framework) can combine the protocol description and header extensions provided by the AF to extend the packet headers of the PDUs in the SDF's PDU set to carry PDU set information. The carried PDU information can be used by the access network for PDU set-based QoS control.

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

[0199] Understandably, the UPF performs SDF-to-QoS flow mapping based on the PDR and maps (or encapsulates) interrelated PDUs into a PDU set. Furthermore, the UPF can apply the same QoS policy to all PDU sets within the QoS flow. For example, the UPF can apply the same PDU set QoS parameters to all PDU sets within the QoS flow. In one example, the UPF can map the application flow to the QoS flow based on packet detection information in the PDR. Some PDUs in the QoS flow can be associated with media components (e.g., intra-coded frames and prediction frames), and the UPF classifies these PDUs as belonging to a PDU set and controls them accordingly. In some embodiments, the RAN can implement PDU set-based processing based on the PDU set-specific QoS features and protocol descriptions provided by 5GC and AF, as well as the enhanced headers identified and marked by the UPF.

[0200] In some embodiments, and across numerous application scenarios, pose information is used to ensure consistency between a user's movement in a real-world environment and their movement in a virtual environment. To maintain this consistency, the application can choose a frame of reference to track the real world. The virtual environment provides the user's physical environment and the relationships between other tracked entities.

[0201] In some embodiments, pose can be used to represent the position and / or orientation of an object in space (e.g., real space or virtual space). The pose can be, for example, an XR pose. In some embodiments, pose information can be spatial information. In some embodiments, pose information can include at least one of the following: position information and orientation information. Position information can be used to indicate the position of an object in space, such as position domain information x, y, z. Orientation information can be used to indicate the orientation of an object in space, such as orientation domains rx, ry, rz, rw.

[0202] In some embodiments, when implementing XRM services, the pre-rendered video stream sent to the terminal may include pose information to indicate the pose used for rendering the media. For example, in VR services, the rendering of the video stream corresponding to the image displayed to the user can be performed based on the pose. In some embodiments, the pose can also be used for the audio stream. For example, in VR services, the audio stream corresponding to the sound played for the user can be determined based on the pose.

[0203] In some embodiments, multiple streams (e.g., media streams) can constitute a stream group. Multiple streams within a stream group can be associated with the same pose. In this case, the pose associated with the multiple streams in the stream group can be referred to as a group pose. There may be cooperative relationships between the multiple streams in the stream group corresponding to the group pose.

[0204] Therefore, for data streams related to group pose, the communication system needs to be able to implement corresponding QoS processing.

[0205] Figure 2A is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. The communication method involved in the embodiment of the present disclosure can be applied to the communication system 100. As shown in Figure 2A, the communication method of the embodiment of the present disclosure includes steps S2101 to S2115.

[0206] In step S2101, the second network element 1032 sends a first message to the seventh network element 1037.

[0207] In some embodiments, the seventh network element 1037 can receive the first message.

[0208] In some embodiments, the first message may include first information.

[0209] In some embodiments, the first information may be used to determine the QoS policy of the first flow group.

[0210] In some embodiments, the first information may be used to indicate the QoS requirements for a first flow group.

[0211] In some embodiments, a first stream group may include one or more streams. In some embodiments, a first stream group may include multiple streams. In some embodiments, a first stream group may correspond to a first service. For example, the streams in the first stream group may be streams in the service data stream corresponding to the first service. In other words, one or more streams in the service data stream corresponding to the first service may constitute the first stream group.

[0212] In some embodiments, the streams in the first stream group may be media streams.

[0213] In some embodiments, the first stream group may be associated with a group pose. In some embodiments, one or more streams in the first stream group may be associated with a group pose. In some embodiments, all streams in the first stream group may be associated with a group pose.

[0214] In some embodiments, the first service may be a pose-related service.

[0215] In some embodiments, the data stream of the first service may include pose information.

[0216] In some embodiments, the first service-related pose may correspond to a first stream group. In some embodiments, the pose may be associated with multiple streams within the first stream group. In some embodiments, the pose associated with multiple streams within the first stream group may be referred to as a group pose.

[0217] In some embodiments, multiple streams in a first stream group associated with a group pose may have a cooperative relationship. In some embodiments, the cooperative relationship between multiple streams may include that the multiple streams associated with the group pose can meet latency requirements. For example, the cooperative relationship between multiple streams may include that the multiple streams associated with the group pose can play synchronously on a terminal. It is understood that the cooperative relationship can also be understood as other relationships, and this disclosure does not specifically limit them.

[0218] In some embodiments, the name of the first information is not limited, and it may be, for example, demand information, instruction information, request information, etc.

[0219] In some embodiments, the first information may be included in the QoS requirement information. In one embodiment, the QoS requirement information may be QoS requirement information related to a first service. It is understood that in some embodiments, the first information may be independent of the QoS requirement information.

[0220] In some embodiments, the first information may include at least one of the following: first support information, flow group type information, and auxiliary information. It is understood that the first information may also include other information, and this disclosure does not impose specific limitations on the embodiments described.

[0221] In some embodiments, the first support information can be used to indicate whether group pose is supported. In some embodiments, the first support information can be used to indicate whether group pose needs to be supported. In some embodiments, the first support information can be used to indicate whether group pose information is supported. In some embodiments, the first support information can be used to indicate whether group pose information needs to be supported.

[0222] In some embodiments, group pose information may be information related to group pose. In some embodiments, group pose information may be used to characterize group pose. In some embodiments, group pose may correspond to multiple flows in a first flow group, and the group pose information may be applied to these flows.

[0223] In some embodiments, the first support information may be included in a specific field. In one example, the value of this field may be used to indicate whether group pose information is supported. For example, the first support information may include one bit. When the value of this bit is 1, the first support information may indicate that group pose information is supported. When the value of this bit is 0, the first support information may indicate that group pose information is not supported. In one example, the presence or absence of this field may be used to indicate whether group pose information is supported. For example, the presence of the field corresponding to the first support information indicates that group pose information is supported. For example, the absence of the field corresponding to the first support information indicates that group pose information is not supported.

[0224] In some embodiments, flow group type information can be used to indicate the flow group type of a first flow group.

[0225] In some embodiments, a stream group type may include at least one of the following: multiple streams corresponding to the same pose information, multiple streams corresponding to the same or associated timestamps, or multiple streams corresponding to the same or associated actions. It is understood that the stream group type may also include other types, and this disclosure does not specifically limit these types.

[0226] In some embodiments, multiple streams may correspond to the same pose information. In this case, the pose information may be group pose information. In one example, the same pose information may correspond to multiple streams in a first stream group.

[0227] In some embodiments, multiple streams may correspond to the same or associated timestamps. In some embodiments, multiple streams may correspond to the same timestamp. In other words, the timestamps carried in the data packets of multiple streams may be identical. In some embodiments, multiple streams may correspond to associated timestamps. In other words, the timestamps carried in the data packets of multiple streams may be associated. In one example, the association between the timestamps in multiple streams may be that the times indicated by the timestamps in these streams satisfy a certain delay relationship.

[0228] In some embodiments, the timestamps corresponding to multiple streams can be pose-based timestamps. In some embodiments, the timestamps can be used to indicate the playback time of media data in multiple streams.

[0229] In some embodiments, multiple flows may correspond to the same or related actions. In some embodiments, multiple flows may correspond to the same action, which may be an action related to a group pose. In some embodiments, multiple flows may correspond to related actions. In other words, the actions corresponding to multiple flows may be related to each other. These actions may all be related to a group pose.

[0230] In some embodiments, the number of associated actions may be preset or agreed upon by protocol. For example, the number of associated actions may be less than or equal to 10.

[0231] In some embodiments, multiple flows belonging to at least one of the above flow group types may have a cooperative relationship.

[0232] In some embodiments, the auxiliary information may include at least one of the following: pose type information, flow type information, protocol information, pose sharing information, pose group information, and priority information.

[0233] In some embodiments, pose type information can be used to indicate the pose type of a group pose. In some embodiments, the pose type may include 6DoF and 3DoF. In some embodiments, the pose type of the group pose indicated by the pose type information may include at least one of 6DoF and 3DoF.

[0234] In some embodiments, 6DoF may include position and orientation. In one example, position may be represented by x, y, z dimensions. In another example, orientation may be represented by rx, ry, rz, rw dimensions.

[0235] In some embodiments, 3DoF may include only orientation. In one example, orientation may be represented by rx, ry, rz, and rw dimensions. It is understood that 3DoF may not include position.

[0236] In some embodiments, flow type information can be used to indicate the flow type associated with the group pose.

[0237] In some embodiments, the stream type may include a video stream, an audio stream, a haptic stream, and a state stream. In some embodiments, the stream type information indicates that the stream type may include at least one of a video stream, an audio stream, a haptic stream, and a state stream. In one example, a group pose may be associated with a video stream. For example, a group pose may be used in association with a video stream. In one example, a group pose may be associated with an audio stream. For example, a group pose may be used in association with an audio stream. In one example, a group pose may be associated with a haptic stream. For example, a group pose may be used in association with a haptic stream. In one example, a state stream may be associated with the state of an interactive object (e.g., a user). A state stream can be used to transmit data characterizing the state of an interactive object. For example, a state stream may carry data such as heart rate, blood oxygen, blood pressure, and facial expression. It is understood that the stream type may also include other types, and this disclosure does not specifically limit these types.

[0238] In some embodiments, protocol information may be used to indicate the transmission protocol of the group pose.

[0239] In some embodiments, a transport protocol can be used to implement the transmission of group poses. In some embodiments, the transport protocol can be a real-time transport protocol (RTP) header extension (HE). In one example, protocol information can indicate that the transmission of group poses is implemented via RTP HE.

[0240] In some embodiments, pose sharing information can be used to indicate whether a group pose is used for multiple terminal devices.

[0241] In some embodiments, the group pose can be used for one or more terminal devices. For example, pose sharing information can indicate that the group pose is used for a single terminal device. Alternatively, pose sharing information can indicate that the group pose is used for multiple terminal devices. In this case, the group pose can be shared by multiple terminal devices.

[0242] In some embodiments, multiple terminal devices sharing a group pose may be associated. In one example, one of the multiple terminal devices may communicate with the network side, and other terminal devices may be tethered to that terminal device. In one example, all of the multiple terminal devices may communicate with the network side.

[0243] In some embodiments, pose group information can be used to indicate the flow group corresponding to the group pose.

[0244] In some embodiments, pose group information can be used to indicate a stream group. The stream group may include at least one stream. In one example, all streams in the stream group indicated by the pose group information may share a group pose. In another example, all streams in the stream group indicated by the pose group information may reuse poses. In one example, the streams in the stream group may belong to one or more stream types. For example, pose group information may indicate a stream group, and the stream group may contain at least one video stream, and / or at least one audio stream, and / or at least one haptic stream.

[0245] In some embodiments, pose group information may include identification information for the flow group. This identification information can be used to identify the flow group. For example, the identification information may include a group ID for the flow group.

[0246] In some embodiments, the flow group indicated by the pose group information may be a first flow group. In one example, the pose group information may include identification information of the first flow group. For example, the identification information may include a group identifier of the first flow group.

[0247] In some embodiments, the group pose may be provided by a media stream or a substream. In some embodiments, the group pose may be contained within a media stream. In this case, the group pose provided in the media stream may be multiplexed by a stream group indicated by the group pose group information. In one example, the media stream providing the group pose may be different from the stream group indicated by the pose group information. For example, the media stream providing the group pose may be located outside the stream group. In some embodiments, the group pose may be contained within a substream. In this case, the pose provided by the substream may be multiplexed by a stream group indicated by the pose group information. In one example, the substream providing the group pose may be located within a multiplexed data stream. For example, the substream providing the group pose may be at least one substream in a multiplexed data stream.

[0248] In some embodiments, priority information may be used to indicate the priority associated with the group pose.

[0249] In some embodiments, priority information may include at least one of the following: pose type priority, stream type priority, protocol priority, and group pose priority.

[0250] In some embodiments, pose type priority can be used to indicate the priority between different pose types. In some embodiments, pose type priority can be used to indicate the priority between 6DoF and 3DoF. For example, 6DoF may have a higher priority than 3DoF. For example, 6DoF may have a lower priority than 3DoF. For example, 6DoF and 3DoF may have the same priority.

[0251] In some embodiments, pose type priority can be used to indicate the priority of each pose type individually. In one example, pose type priority may include a first field and a second field. The first field indicates the priority of 6DoF. The second field indicates the priority of 3DoF.

[0252] In some embodiments, pose type priority can be used to indicate the relative priority between different pose types. In one example, pose type priority may include a third field. The third field may have at least one of the following: a first value, a second value, and a third value. The first value may indicate that 6DoF has a higher priority than 3DoF. The second value may indicate that 3DoF has a higher priority than 6DoF. The third value may indicate that 6DoF and 3DoF have the same priority.

[0253] In some embodiments, stream type priority can be used to indicate the priority among different stream types. In some embodiments, stream type priority can be used to indicate the priority among video streams, audio streams, haptic streams, and status streams.

[0254] In some embodiments, group pose priority can be used to indicate the priority between different group poses. In some embodiments, group pose priority can be used to determine the priority between multiple group poses. In some embodiments, group pose priority can be used to determine the priority between flow groups corresponding to different group poses.

[0255] In some embodiments, protocol priority can be used to indicate the priority between different transport protocols.

[0256] In some embodiments, the first message may further include at least one of the following: the identifier of the first service, the address and / or identifier of the terminal 101, the identifier of the second network element 1032, the application identifier of the first service, the flow description, the data network name (DNN), the single network slice selection assistance information (S-NSSAI), and the QoS parameters.

[0257] In some embodiments, the identifier of the first service can be used to identify a data stream or a group of data streams of the first service. In some embodiments, the identifier of the first service can be a multimodal service identifier, which can then be used to identify all data streams in the service group. In some embodiments, the data stream or group of data streams of the first service can be a service data stream or a group of service data streams.

[0258] In some embodiments, the first message may be a request message.

[0259] In some embodiments, the first message may be a message from the Nnef_AFsessionWithQoS service. In one example, the request message may be a message from the Nnef_AFsessionWithQoS_Create service operation (or procedure). In another example, the request message may be a message from the Nnef_AFsessionWithQoS_Update service operation (or procedure).

[0260] In some embodiments, the first 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 or an Nnef_AFSessionWithQoS_Update request message.

[0261] In step S2102, the seventh network element 1037 performs authorization.

[0262] In some embodiments, the seventh network element 1037 can authorize the first message. In some embodiments, the seventh network element 1037 can authorize the first information in the first message.

[0263] In some embodiments, the second network element 1032 may be an unauthorized network element, in which case the seventh network element 1037 may authorize the first message from the second network element 1032.

[0264] In some embodiments, the second network element 1032 may be an authorized network element, in which case the seventh network element 1037 may not need to authorize the first message from the second network element 1032. In other words, step S2102 may be omitted.

[0265] In step S2103, the seventh network element 1037 sends a second message to the first network element 1031.

[0266] In some embodiments, the first network element 1031 may receive a second message.

[0267] In some embodiments, the second message may include the first information.

[0268] In some embodiments, the second message may further include at least one of the following: the identifier of the first service, the address and / or identifier of the terminal 101, the identifier of the second network element 1032, the application identifier of the first service, the flow description, the DNN, the S-NSSAI, the QoS parameters, and the QoS requirement information.

[0269] In some embodiments, the seventh network element 1037 may send the first information in different ways. In some embodiments, the seventh network element 1037 may determine the method of sending the first information based on the first message received from the second network element 1032.

[0270] In some embodiments, the method by which the seventh network element 1037 sends the first information may include: sending it through the time-sensitive communication and time synchronization function (TSCTSF) or sending it directly.

[0271] In some embodiments, the seventh network element 1037 may determine to send first information to the first network element 1031 via the TCSTSF. In some embodiments, the second message may include a message sent by the seventh network element 1037 to the TCSTSF, and a message sent by the TCSTSF to the first network element 1031.

[0272] In some embodiments, the seventh network element 1037 can send the first information to the TSCTSF via the service-based interface Ntsftsf, and then the TSCTSF can send the first information to the first network element 1031 via the service-based interface Npcf. In one example, the seventh network element 1037 can send the first information to the TSCTSF via an Ntsctsf_QoSandTSCAssistance_Create request message or an Ntsctsf_QoSandTSCAssistance_Update request message, and then the TSCTSF can send the first information to the first network element 1031 via an Npcf_PolicyAuthorization_Create request message or an Npcf_PolicyAuthorization_Update request message.

[0273] In some embodiments, the seventh network element 1037 may determine to send the first information directly to the first network element 1031. In some embodiments, the second message may be sent by the seventh network element 1037 to the first network element 1031.

[0274] In some embodiments, the seventh network element 1037 can send the first information to the first network element 1031 through the service-based interface Npcf. In one example, the seventh network element 1037 can send the first information to the first network element 1031 through an Npcf_PolicyAuthorization_Create request message or an Npcf_PolicyAuthorization_Update request message.

[0275] It is understood that through steps S2101 to S2103, the first network element 1031 can obtain the first information from the second network element 1032. In some embodiments, the first network element 1031 can obtain the first information through other means. In this case, steps S2101 to S2103 can be omitted. For example, the first network element 1031 can determine the first information based on operator operation and maintenance and management configuration, and / or local configuration.

[0276] In step S2104, the first network element 1031 performs a strategy decision.

[0277] In some embodiments, the first network element 1031 may execute a policy decision after receiving the second message.

[0278] In some embodiments, the first network element 1031 can determine the QoS policy of the first flow group through policy decision.

[0279] In some embodiments, a QoS policy may include QoS characteristics, policies related to QoS processing of PDU sets, and spatial information policies.

[0280] In some embodiments, the spatial information policy may be a QoS policy related to pose information. For example, the spatial information policy may include at least one of the following: whether QoS flow mapping considers pose information, the priority of QoS mapping between different dimensions of multi-dimensional spatial information, QoS coordination between different dimensions of multi-dimensional spatial information, and whether group QoS policies are executed for the same pose.

[0281] In some embodiments, the QoS policy may include a first rule.

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

[0283] In some embodiments, the first rule may be determined based on first information.

[0284] In some embodiments, the first rule may be used for the identification of the first stream group.

[0285] In some embodiments, the first rule may be used for mapping or routing of the first flow group.

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

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

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

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

[0290] In some embodiments, the first network element 1031 can determine the second information.

[0291] In some embodiments, the first network element 1031 can determine the second information based on the first information.

[0292] In some embodiments, the first network element 1031 can authorize the SDF of the first service through a first rule. Through authorization, the first network element 1031 can obtain second information.

[0293] In some embodiments, the second information can be used to implement QoS processing for the first flow group.

[0294] In some embodiments, the second information may be included in the first rule. It is understood that the second information may be independent of the first rule, and this disclosure does not specifically limit this.

[0295] In some embodiments, the second information may include at least one of the following: second support information, stream group type information, and auxiliary information.

[0296] In some embodiments, the second support information can be used to indicate a support group pose. In some embodiments, the second support information can be used to indicate a need for a support group pose. In some embodiments, the second support information can be used to indicate support group pose information. In some embodiments, the first support information can be used to indicate a need for support group pose information.

[0297] In step S2105, the first network element 1031 sends a third message to the third network element 1033.

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

[0299] In some embodiments, a third message may be used to instruct a first rule.

[0300] In some embodiments, the third message may carry the second information.

[0301] In some embodiments, the third message may also carry subscription information. In one example, the subscription information may be included in the second message.

[0302] In some embodiments, subscription information can be used for event subscriptions associated with the first stream group.

[0303] In some embodiments, subscription information can be used to request reporting or notification of events.

[0304] In some embodiments, the second information can be sent to the third network element 1033 via the service-based interface NPCF.

[0305] In some embodiments, the first network element 1031 may initiate a Policy Association Modification (PAM) process to send the second information.

[0306] In some embodiments, the third message may be an Npcf_SMPolicyControl_UpdateNotify request message.

[0307] In some embodiments, the second information can be used by the third network element 1033 to determine the fourth information.

[0308] In some embodiments, the fourth information can be used by the fourth network element 1034 to perform marking processing on the first flow group.

[0309] In some embodiments, the fourth information can be used to configure the fourth network element 1034 to perform marking processing on the first flow group.

[0310] In some embodiments, the fourth information may be included in the second rule. In some embodiments, the third network element 1033 may determine the second rule based on the second information. In some embodiments, the second rule may include an N4 rule. In some embodiments, the N4 rule may include packet detection rules (PDR).

[0311] It is understood that the policy decision executed by the first network element 1031 in step S2104 can generate a first rule. The first rule can be sent to the third network element 1033 in step S2105 so that the third network element 1033 can perform QoS flow mapping, QoS configuration and / or QoS rule generation.

[0312] In some embodiments, the fourth information may include the second information. In one example, the fourth information may include at least one of the following: second support information, stream group type information, and auxiliary information.

[0313] In some embodiments, the second information can also be used by the third network element 1033 to determine a third rule. In some embodiments, the third rule can be used by the first device 102 to perform QoS processing on the first flow group. In some embodiments, the third rule may include a QoS profile. In some embodiments, the third rule may include the second information.

[0314] In some embodiments, the second information can also be used by the third network element 1033 to determine the fourth rule. In some embodiments, the fourth rule can be used by the terminal 101 to perform QoS processing on the first flow group. In some embodiments, the fourth rule may include QoS rules. In some embodiments, the fourth rule may include the second information.

[0315] In step S2106, the third network element 1033 sends a fourth message to the fourth network element 1034.

[0316] In some embodiments, the fourth network element 1034 can receive a fourth message.

[0317] In some embodiments, the fourth message may carry fourth information.

[0318] In some embodiments, the fourth message may carry the second rule. The second rule may contain the fourth message.

[0319] In some embodiments, the fourth message may also carry subscription information.

[0320] In some embodiments, the third network element 1033 can send fourth information through an N4 session.

[0321] In some embodiments, the fourth message may be an N4 Session Modification request message.

[0322] In step S2107, the third network element 1033 sends a fifth message to the sixth network element 1036.

[0323] In some embodiments, the sixth network element 1036 can receive the fifth message.

[0324] In some embodiments, the fifth message may carry a third rule.

[0325] In some embodiments, the fifth message may carry the fourth rule.

[0326] In some embodiments, the third network element 1033 can send a fifth message through the service-based interface Namf.

[0327] In some embodiments, the fifth message may be a message during the Namf_Communication_N1N2MessageTransfer process.

[0328] In step S2108, the sixth network element 1036 sends a sixth message to the first device 102.

[0329] In some embodiments, the first device 102 may receive a sixth message.

[0330] In some embodiments, the sixth message may carry a third rule.

[0331] In some embodiments, the sixth message may carry a fourth rule. In some embodiments, the fourth rule may be provided by the first device 102 to the terminal 101 for the terminal 101 to implement QoS processing for the uplink data stream.

[0332] In some embodiments, the sixth message may be an N2 message (N2message).

[0333] In step S2109, the fifth network element 1035 sends a data stream to the fourth network element 1034.

[0334] In some embodiments, the fifth network element 1035 may send a first flow group to the fourth network element 1034. The first flow group may include one or more downlink flows.

[0335] In some embodiments, the fourth network element 1034 may receive the first stream group in the user plane.

[0336] In some embodiments, the fourth network element 1034 may receive the first stream group on the data plane.

[0337] In some embodiments, the data packets corresponding to the flows in the first flow group may include group pose information. In some embodiments, the group pose information may be carried in the data packets of at least one flow in the first flow group. In some embodiments, the group pose information may be carried in the header of the data packets of at least one flow in the first flow group. In one example, the transport protocol of the first flow group may be RTP HE. The group pose information may be carried in the RTP HE.

[0338] In step S2110, the fourth network element 1034 performs QoS processing.

[0339] In some embodiments, the fourth network element 1034 may perform QoS processing on the first flow group according to the fourth message.

[0340] In some embodiments, the QoS processing performed by the fourth network element 1034 may include at least one of the following: identification, detection, traffic mapping, and labeling.

[0341] In some embodiments, the fourth network element 1034 may obtain the second rule from the fourth message and identify and / or detect the first flow group according to the second rule.

[0342] In some embodiments, the fourth network element 1034 may identify and / or detect the first flow group based on information carried in the header of the data packets in the data stream.

[0343] In some embodiments, the flow group type of the first flow group can be: multiple flows corresponding to the same pose information. In this case, the same pose information, i.e., the group pose information, can be carried in one flow of the first flow group.

[0344] In some embodiments, the flows carrying group pose information in the first flow group may also carry flow identification information. For example, the flow identification information may be a flow identifier. In some embodiments, the flow identification information may be carried in the header of the data packets of the flow. For example, the flow identification information may be carried in the RTP HE of the flow.

[0345] In some embodiments, flow identification information can be used to determine all flows in a first flow group. In some embodiments, flow identification information can be used to indicate all flows corresponding to group pose information.

[0346] In some embodiments, the flow identification information may include the identification information of all flows in the first flow group. In one example, the first flow group may include four flows: flow 1, flow 2, flow 3, and flow 4, and the group pose information may be carried in flow 1. The flow identification information may be carried in flow 1, and may include the flow identifiers of flow 1, flow 2, flow 3, and flow 4. That is, the flow identification information corresponding to the group pose information may include the flow identification information of the flow where the group pose information is located (i.e., flow 1).

[0347] In some embodiments, the flow identification information may include the identification information of all flows in the first flow group. In one example, the first flow group may include four flows: flow 1, flow 2, flow 3, and flow 4, and the group pose information may be carried in flow 1. The flow identification information may be carried in flow 1, and may include the flow identifiers of flow 2, flow 3, and flow 4. That is, the flow identification information corresponding to the group pose information may not include the flow identification information of the flow containing the group pose information (i.e., flow 1).

[0348] In some embodiments, multiple streams in the first stream group corresponding to the group pose information can all be media streams. In this case, stream identification information can also be referred to as media identification information. For example, media identification information can be a media identifier.

[0349] In some embodiments, the fourth network element 1034 can determine the first flow group based on the flow identifier information corresponding to the group pose information identified in a flow. In one example, the fourth network element 1034 can determine that the first flow group includes flow 1, flow 2, flow 3 and flow 4 based on the flow identifier information in flow 1.

[0350] In some embodiments, each flow in the first flow group may carry a location field and / or a direction field. In some embodiments, the location field and / or direction field may be carried in the header of the data packets of that flow. For example, the location field and / or direction field may be carried in the RTP HE of that flow.

[0351] In some embodiments, the position field may contain position coordinate values ​​corresponding to the group pose. For example, the position coordinate values ​​may include x-coordinate values, y-coordinate values, and z-coordinate values.

[0352] In some embodiments, the orientation field may contain orientation coordinate values ​​corresponding to the group pose. For example, the orientation coordinate values ​​may include rx coordinate values, ry coordinate values, rz coordinate values, and rw coordinate values.

[0353] In some embodiments, because multiple streams correspond to the same pose information, each stream in the first stream group can carry a position field and / or an orientation field, and the position coordinate values ​​in the position field and / or the orientation coordinate values ​​in the orientation field can be the same. In one example, the pose type of the group pose can be 6DoF. In this case, each stream in the first stream group can carry a position field and an orientation field, and the position coordinate values ​​in the position field are the same, and the orientation coordinate values ​​in the orientation field are the same. For example, all streams in the first stream group can have the same x-coordinate, y-coordinate, z-coordinate, rx-coordinate, ry-coordinate, rz-coordinate, and rw-coordinate values. In one example, the pose type of the group pose can be 3DoF. In this case, each stream in the first stream group can carry an orientation field, and the orientation coordinate values ​​in the orientation field are the same. For example, all streams in the first stream group can have the same rx-coordinate, ry-coordinate, rz-coordinate, and rw-coordinate values.

[0354] In some embodiments, the flow group type of the first flow group can be: multiple flows corresponding to the same or associated timestamps.

[0355] In some embodiments, a timestamp may be carried in the header of packets in the first stream group. For example, a timestamp may be carried in the RTP HE of each stream in the first stream group.

[0356] In some embodiments, multiple flows may correspond to the same timestamp. In some embodiments, the header of the data packets of each flow in the first flow group may carry a timestamp. The timestamps in each flow may be the same. Thus, the fourth network element 1034 can identify multiple flows as belonging to the first flow group based on the same timestamp.

[0357] In some embodiments, multiple flows may correspond to associated timestamps. In some embodiments, the header of the data packets of each flow in the first flow group may carry a timestamp. The timestamps in each flow may be associated. Thus, the fourth network element 1034 can identify multiple flows as belonging to the first flow group based on the associated timestamps.

[0358] In some embodiments, the association between timestamps of multiple streams can be set according to actual needs. In one example, the association between timestamps of multiple streams can be: the time interval between the timestamps of multiple streams is less than a preset threshold.

[0359] In some embodiments, the timestamp may be used to indicate the implementation time of the group pose on terminal 101. In some embodiments, the timestamp may be used to indicate the playback time of the media data corresponding to the group pose. In some embodiments, the playback time may be a predicted playback time.

[0360] In some embodiments, the timestamp may be used to indicate the implementation time of the predicted group pose on terminal 101. In some embodiments, the timestamp may be used to indicate the playback time of the media data corresponding to the predicted group pose.

[0361] In some embodiments, the timestamp may be determined based on the time on terminal 101. In one example, the timestamp may be determined based on the runtime on terminal 101. In another example, the timestamp may use the system clock of terminal 101 as a reference.

[0362] In some embodiments, the time accuracy indicated by the timestamp can reach the nanosecond level.

[0363] In some embodiments, the flow group type of the first flow group can be: multiple flows corresponding to the same or associated actions.

[0364] In some embodiments, the flows in the first flow group may also carry action identification information. For example, the action identification information may be an action identifier. In some embodiments, the action identification information may be carried in the header of the data packets of each flow in the first flow group. For example, the action identification information may be carried in the RTP HE.

[0365] In some embodiments, action identification information may include action identifiers for one or more actions. These actions may correspond to position coordinate values ​​and / or orientation coordinate values ​​of a group pose. Each action identifier may be used to uniquely identify an action. In one example, the one or more actions indicated by the action identification information may be a series of sequential actions. For example, there may be dependencies between multiple actions. In another example, the one or more actions indicated by the action identification information may be discontinuous actions.

[0366] In some embodiments, the header of a data packet may include an action identifier field. This field can be used to carry action identifier information.

[0367] In some embodiments, the fourth network element can identify multiple flows as belonging to the first flow group by indicating the same or related actions based on the action identification information in multiple flows.

[0368] In some embodiments, the fourth network element 1034 can perform traffic mapping on the flows in the first flow group. In one example, the fourth network element 1034 can map each flow in the first flow group to a QoS flow according to a second rule.

[0369] In some embodiments, the traffic mapping performed by the fourth network element 1034 can be implemented by marking a QoS flow identifier (QFI) in packets within the first flow group. In one example, after a QFI is added to a packet, the packet is mapped to the QoS flow corresponding to the added QFI.

[0370] In some embodiments, the individual flows in the first flow group may have the same or associated QFI.

[0371] In some embodiments, the fourth network element 1034 can detect the group pose information in the first stream group based on the fourth information.

[0372] In some embodiments, the fourth network element 1034 can perform marking processing on the first stream group based on the detected group pose information.

[0373] In some embodiments, the fourth network element 1034 may add group pose information to the packets of the first flow group. In one example, the group pose information may be added to the extended header of the packets of the first flow group.

[0374] In some embodiments, the transport protocol for the first stream group may be RTP HE. Group pose information may be added to the extended header of the RTP HE.

[0375] In some embodiments, the group pose information may include at least one of the following: a flow identifier, an action identifier, and a timestamp. It is understood that the flow identifier, action identifier, and timestamp may be the flow identifier information, action identifier information, and timestamp described above.

[0376] In some embodiments, the group pose information may further include at least one of the following: orientation coordinate values, position coordinate values, pose array of multiple objects, and pose time.

[0377] In some embodiments, orientation coordinate values ​​can be used to indicate the orientation of a group pose. In one example, orientation coordinate values ​​can include orientation quaternions. For example, orientation coordinate values ​​can include: rx coordinate values, ry coordinate values, rz coordinate values, and rw coordinate values.

[0378] In some embodiments, position coordinate values ​​can be used to indicate the position of a group pose. In one example, position coordinate values ​​may include: x-coordinate values, y-coordinate values, and z-coordinate values.

[0379] In some embodiments, the pose array may include an array of one or more objects associated with a group pose. In one example, the pose array may be an array composed of multiple pose information. Each pose information in the pose array may have a corresponding display time and XR space.

[0380] In some embodiments, pose time can be used to indicate the time corresponding to a group pose. In one example, pose time can be a timestamp corresponding to a group pose, which can indicate the time when the group pose occurred.

[0381] It is understood that the pose information may also include other content, and this disclosure does not specifically limit this.

[0382] In some embodiments, the fourth network element 1034 may identify and / or detect the first flow group based on OAM operation and maintenance configuration, and / or operator policies, and / or local configuration. In some embodiments, if the fourth message does not carry fourth information (i.e., the fourth network element 1034 does not receive any fourth information), the first flow group may be identified based on OAM operation and maintenance configuration, and / or operator policies, and / or local configuration. In some embodiments, if the fourth message does not carry a second rule (i.e., the fourth network element 1034 does not receive any second rule), the first flow group may be identified based on OAM operation and maintenance configuration, and / or operator policies, and / or local configuration.

[0383] In some embodiments, data stream identification can be achieved through at least one of the following methods: matching of Real-Time Transport Protocol (RTP) / Secure Real-Time Transport Protocol (SRTP) headers and payloads; new RTP extension headers; information contained in the N6 encapsulation header; detection of traffic characteristics; and UPF implementation of non-standardized mechanisms.

[0384] In some embodiments, the data packets corresponding to the first flow group identified by the fourth network element 1034 may include the following types: PDU set data packets and non-PDU set data packets.

[0385] In step S2111, the fourth network element 1034 sends a data stream to the first device 102.

[0386] In some embodiments, the fourth network element 1034 can send the data packets corresponding to the downlink data stream of the first stream group to the first device 102. In some embodiments, after completing the QoS processing of the downlink data stream of the first stream group, the fourth network element 1034 can send the data stream to the first device 102.

[0387] In some embodiments, the data stream of the first stream group can be sent to the first device 102 using the GTP-U protocol.

[0388] In some embodiments, the fourth network element 1034 may carry group pose information in the GTP-U header.

[0389] In some embodiments, the fourth network element 1034 may carry information related to the PDU set in the GTP-U header.

[0390] In some embodiments, the relevant information of a PDU set may include at least one of the following: PDU set sequence number, start / end PDU of the PDU set, PDU sequence number within the PDU set, number of PDUs within the PDU set, importance of the PDU set, size of the PDU set, and end of a data burst.

[0391] In step S2112, the first device 102 performs QoS processing.

[0392] In some embodiments, after receiving a data stream from the fourth network element 1034, the first device 102 may perform QoS processing on the data stream in the first stream group.

[0393] In some embodiments, the QoS processing performed by the first device 102 may include QoS adjustment. In some embodiments, QoS adjustment may also be referred to as QoS enforcement.

[0394] In some embodiments, the first device 102 may obtain group pose information from the header of the data packet received from the first stream group.

[0395] In some embodiments, QoS adjustment can be implemented by the first device 102 adjusting its own QoS parameters taking into account the acquired group pose information. In some embodiments, the first device 102 can adjust the fourth rule associated with the first stream group based on the group pose information acquired from the first stream group.

[0396] In step S2113, the first device 102 sends a data stream to the terminal 101.

[0397] In some embodiments, after adjusting the QoS parameters, the first device 102 can send the downlink data stream of the first stream group according to the adjusted QoS parameters. In one example, the first device 102 can send the downlink data stream of the first stream group according to the adjusted third rule.

[0398] In some embodiments, the data stream can be transmitted from the first device 102 to the terminal 101 via a wireless bearer.

[0399] In step S2114, the fourth network element 1034 performs monitoring.

[0400] In some embodiments, the fourth network element 1034 can perform QoS monitoring on the first flow group based on subscription information.

[0401] In some embodiments, the fourth network element 1034 can monitor changes in the first flow group. In one example, the fifth network element 1035 can monitor an increase in flow in the first flow group. In another example, the fifth network element 1035 can monitor a decrease in flow in the first flow group.

[0402] In some embodiments, the fourth network element 1034 can monitor parameter changes in the flow in the first flow group.

[0403] In some embodiments, the fifth network element 1035 can obtain monitoring results by monitoring the first flow group.

[0404] In some embodiments, monitoring results may include at least one of the following: measured values, events.

[0405] In some embodiments, the measured value may be the measured value obtained by the fourth network element 1034 during the monitoring of the first flow group.

[0406] In some embodiments, the event may be an event that the fourth network element 1034 determines to have occurred through monitoring.

[0407] In step S2115, the fourth network element 1034 sends the third information to the fifth network element 1035.

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

[0409] In some embodiments, third information may be used to indicate events associated with the first stream group.

[0410] In some embodiments, third information may be used to indicate the monitoring results of monitoring the first flow group.

[0411] In some embodiments, the name of the third information is not limited, and it may be, for example, event notification information, reporting information, monitoring information, etc.

[0412] In some embodiments, the third information may be sent in at least one of the following ways: periodic sending, event-triggered sending.

[0413] In some embodiments, the event that triggers the transmission of third information may include at least one of the following: the measured value meets a preset threshold, or a trigger message for third information is received.

[0414] In some embodiments, the fourth network element 1034 can send third information to the fifth network element 1035.

[0415] In some embodiments, the fourth network element 1034 can send the third information to the fifth network element 1035 through the N6 interface.

[0416] The communication method of this embodiment can be realized through the above steps S2101 to S2115.

[0417] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2115. For example, step S2101 may be implemented as a standalone embodiment. For example, step S2103 may be implemented as a standalone embodiment. For example, step S2105 may be implemented as a standalone embodiment. For example, step S2106 may be implemented as a standalone embodiment. For example, step S2111 may be implemented as a standalone embodiment. For example, a combination of steps S2101 and S2103 may be implemented as a standalone embodiment. For example, a combination of steps S2105 and S2106 may be implemented as a standalone embodiment. For example, a combination of steps S2106 and S2111 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S2101 to S2115 are not limited thereto.

[0418] In some embodiments, at least two of steps S2101 to S2115 may be executed in an alternate order or simultaneously. For example, steps S2106 and S2107 may be executed in an alternate order or simultaneously. For example, steps S2111 and S2114 may be executed in an alternate order or simultaneously.

[0419] In some embodiments, steps S2102 to S2115 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0420] In some embodiments, steps S2101 to S2102 and S2104 to S2115 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0422] In some embodiments, steps S2101 to S2105 and S2107 to S2115 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0424] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2A.

[0425] Figure 2B is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. The communication method involved in the embodiment of the present disclosure can be applied to the communication system 100. As shown in Figure 2B, the communication method of the embodiment of the present disclosure includes steps S2201 to S2205.

[0426] In step S2201, the fourth network element 1034 performs monitoring.

[0427] The optional implementation of step S2201 can be found in the optional implementation of step S2114 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0428] In step S2202, the fourth network element 1034 sends third information to the third network element 1033.

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

[0430] In some embodiments, third information may be used to indicate events associated with the first stream group.

[0431] In some embodiments, third information may be used to indicate the monitoring results of monitoring the first flow group.

[0432] In some embodiments, the name of the third information is not limited, and it may be, for example, event notification information, reporting information, monitoring information, etc.

[0433] In some embodiments, the third information may be sent in at least one of the following ways: periodic sending, event-triggered sending.

[0434] In some embodiments, the event that triggers the transmission of third information may include at least one of the following: the measured value meets a preset threshold, or a trigger message for third information is received.

[0435] In some embodiments, the fourth network element 1034 may send third information to the third network element 1033 under control.

[0436] In some embodiments, the fourth network element 1034 can send third information to the third network element 1033 through the N4 interface. In some embodiments, the fourth network element 1034 can send third information to the third network element 1033 through an N4 session.

[0437] In some embodiments, third information can be sent via the service-based interface Nupf.

[0438] In some embodiments, the fourth network element 1034 can trigger an event exposure notification. In some embodiments, the fourth network element 1034 can send a Nupf_EventExposure_Notify message, carrying third information therein.

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

[0440] In some embodiments, the first network element 1031 may receive third information.

[0441] In some embodiments, the third network element 1033 can send third information from the fourth network element 1034 to the first network element 1031.

[0442] In some embodiments, the third network element 1033 can send third information to the first network element 1031 through the N7 interface.

[0443] In step S2204, the first network element 1031 sends third information to the seventh network element 1037.

[0444] In some embodiments, the seventh network element 1037 may receive third information.

[0445] In some embodiments, the first network element 1031 can send third information from the third network element 1033 to the seventh network element 1037.

[0446] In some embodiments, the seventh network element 1037 can receive a Nupf_EventExposure_Notify message. The Nupf_EventExposure_Notify message may carry third-party information.

[0447] In step S2205, the seventh network element 1037 sends the third information to the second network element 1032.

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

[0449] In some embodiments, third information can be sent via the service-based interface Nnef.

[0450] In some embodiments, the seventh network element 1037 may send an Nnef_EventExposure_Notify message and carry third information therein.

[0451] The communication method of this embodiment can be realized through the above steps S2201 to S2205.

[0452] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2205. For example, step S2201 may be implemented as a standalone embodiment. For example, step S2202 may be implemented as a standalone embodiment. For example, a combination of steps S2201 and S2202 may be implemented as a standalone embodiment. For example, a combination of steps S2201, S2202, and S2203 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S2201 to S2205 are not limited thereto.

[0453] In some embodiments, steps S2202, S2203, S2204, and S2205 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0454] In some embodiments, steps S2201, S2202, S2203, and S2204 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0455] In some embodiments, other optional implementations may be described before or after the specification corresponding to FIG2B.

[0456] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0457] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0458] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0459] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0460] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0461] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0462] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0463] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0464] In some embodiments, the terms “traffic”, “flow”, “stream”, and “data stream” can be used interchangeably.

[0465] In some embodiments, the terms "header", "packet header", "data packet header", etc., can be used interchangeably.

[0466] Figure 3A is a schematic flowchart of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. The communication method is executed by a first network element 1031. As shown in Figure 3A, the method includes steps S3101 to S3103.

[0467] In step S3101, the second message is obtained.

[0468] The optional implementation of step S3101 can be found in the optional implementation of step S2103 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0469] In some embodiments, the first network element 1031 may receive a second message sent by the seventh network element 1037, but is not limited thereto, and may also receive a second message sent by other entities.

[0470] In step S3102, a strategy decision is made.

[0471] The optional implementation of step S3102 can be found in the optional implementation of step S2104 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0472] In step S3103, a third message is sent.

[0473] The optional implementation of step S3103 can be found in the optional implementation of step S2105 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

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

[0475] The communication method involved in the embodiments of this disclosure may include at least one of steps S3101 to S3103. For example, step S3101 may be implemented as a standalone embodiment. For example, step S3103 may be implemented as a standalone embodiment. For example, a combination of steps S3101 and S3103 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S3101 to S3103 are not limited thereto.

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

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

[0478] Figure 3B is a schematic flowchart of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. The communication method is executed by a first network element 1031. As shown in Figure 3B, the method includes steps S3201 to S3202.

[0479] In step S3201, third information is obtained.

[0480] The optional implementation of step S3201 can be found in the optional implementation of step S2203 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

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

[0482] In step S3202, the third message is sent.

[0483] The optional implementation of step S3202 can be found in the optional implementation of step S2204 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0484] In some embodiments, the first network element 1031 may send third information to the seventh network element 1037, but is not limited thereto; it may also send third information to other entities.

[0485] The communication method involved in the embodiments of this disclosure may include at least one of steps S3201 to S3202. For example, step S3201 may be implemented as a standalone embodiment. For example, step S3202 may be implemented as a standalone embodiment. For example, a combination of steps S3201 and S3202 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S3201 to S3202 are not limited thereto.

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

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

[0488] Figure 4A is a schematic flowchart of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. The communication method is executed by a second network element 1032. As shown in Figure 4A, the method includes step S4101.

[0489] In step S4101, the first message is sent.

[0490] The optional implementation of step S4101 can be found in the optional implementation of step S2101 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0491] In some embodiments, the second network element 1032 may send a first message to the seventh network element 1037, but is not limited thereto; it may also send a first message to other entities.

[0492] Figure 4B is a schematic flowchart of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. The communication method is executed by a second network element 1032. As shown in Figure 4B, the method includes step S4201.

[0493] In step S4201, third information is obtained.

[0494] The optional implementation of step S4201 can be found in the optional implementation of step S2205 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0495] In some embodiments, the second network element 1032 may receive third information sent by the seventh network element 1037, but is not limited thereto, and may also receive third information sent by other network elements.

[0496] Figure 5A is a schematic flowchart of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. The communication method is executed by a third network element 1033. As shown in Figure 5A, the method includes steps S5101 to S5103.

[0497] In step S5101, the third message is obtained.

[0498] The optional implementation of step S5101 can be found in the optional implementation of step S2105 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

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

[0500] In step S5102, a fourth message is sent.

[0501] The optional implementation of step S5102 can be found in the optional implementation of step S2106 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0502] In some embodiments, the third network element 1033 may send a fourth message to the fourth network element 1034, but is not limited thereto; it may also send a fourth message to other entities.

[0503] In step S5103, the fifth message is sent.

[0504] The optional implementation of step S5103 can be found in the optional implementation of step S2107 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0505] In some embodiments, the third network element 1033 may send a fifth message to the sixth network element 1036, but is not limited thereto; it may also send a fifth message to other entities.

[0506] The communication method involved in the embodiments of this disclosure may include at least one of steps S5101 to S5103. For example, step S5101 may be implemented as a standalone embodiment. For example, step S5102 may be implemented as a standalone embodiment. For example, step S5103 may be implemented as a standalone embodiment. For example, a combination of steps S5101 and S5102 may be implemented as a standalone embodiment. For example, a combination of steps S5101 and S5103 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S5101 to S5103 are not limited thereto.

[0507] In some embodiments, at least two of steps S5101 to S5103 may be executed in an alternate order or simultaneously. For example, steps S5102 and S5103 may be executed in an alternate order or simultaneously.

[0508] In some embodiments, steps S5102 and S5103 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0509] In some embodiments, steps S5101 and S5103 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0510] In some embodiments, steps S5101 and S5102 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0511] Figure 5B is a schematic flowchart of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. The communication method is executed by a third network element 1033. As shown in Figure 5B, the method includes steps S5201 to S5202.

[0512] In step S5201, third information is obtained.

[0513] The optional implementation of step S5201 can be found in the optional implementation of step S2202 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

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

[0515] In step S5202, the third message is sent.

[0516] The optional implementation of step S5202 can be found in the optional implementation of step S2203 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

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

[0518] The communication method involved in the embodiments of this disclosure may include at least one of steps S5201 to S5202. For example, step S5201 may be implemented as a standalone embodiment. For example, step S5202 may be implemented as a standalone embodiment. For example, a combination of steps S5201 and S5202 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S5201 to S5202 are not limited thereto.

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

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

[0521] Figure 6A is a schematic flowchart of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. The communication method is executed by a fourth network element 1034. As shown in Figure 6A, the method includes steps S6101 to S6106.

[0522] In step S6101, the fourth message is obtained.

[0523] The optional implementation of step S6101 can be found in the optional implementation of step S2106 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0524] In some embodiments, the fourth network element 1034 may receive a fourth message sent by the third network element 1033, but is not limited thereto; it may also receive a fourth message sent by other entities. In some embodiments, the fourth message may include fourth information.

[0525] In some embodiments, the fourth network element 1034 can obtain fourth information as specified in the protocol.

[0526] In some embodiments, the fourth network element 1034 can obtain fourth information from the upper layer.

[0527] In some embodiments, the fourth network element 1034 can perform processing to obtain fourth information.

[0528] In some embodiments, step S6101 can be omitted, and the fourth network element 1034 can autonomously implement the functions involved in the fourth information, or the above functions are defaulted or set by default.

[0529] In step S6102, the data stream is acquired.

[0530] The optional implementation of step S6102 can be found in the optional implementation of step S2109 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

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

[0532] In some embodiments, the data stream can be a first stream group.

[0533] In step S6103, QoS processing is performed.

[0534] The optional implementation of step S6103 can be found in the optional implementation of step S2110 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0535] In some embodiments, QoS processing can be implemented based on the group pose information corresponding to the first stream group.

[0536] In step S6104, the data stream is sent.

[0537] The optional implementation of step S6104 can be found in the optional implementation of step S2111 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0538] In some embodiments, the fourth network element 1034 may send a data stream to the first device 102, but is not limited thereto, and may also send a data stream to other entities.

[0539] In step S6105, QoS monitoring is performed.

[0540] The optional implementation of step S6105 can be found in the optional implementation of step S2114 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0541] In step S6106, the third information is sent.

[0542] The optional implementation of step S6106 can be found in the optional implementation of step S2115 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0543] In some embodiments, the fourth network element 1034 may send third information to the fifth network element 1035, but is not limited thereto; it may also send third information to other entities.

[0544] The communication method involved in the embodiments of this disclosure may include at least one of steps S6101 to S6106. For example, step S6101 may be implemented as a standalone embodiment. For example, step S6103 may be implemented as a standalone embodiment. For example, step S6106 may be implemented as a standalone embodiment. For example, a combination of steps S6101 and S6103 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S6101 to S6106 are not limited thereto.

[0545] In some embodiments, at least two of steps S6101 to S6106 may be executed in an alternate order or simultaneously. For example, steps S6104 and S6106 may be executed in an alternate order or simultaneously.

[0546] In some embodiments, steps S6102, S6103, S6104, S6105, and S6106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0547] In some embodiments, steps S6101, S6102, S6104, S6105, and S6106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0548] In some embodiments, steps S6101, S6102, S6103, S6104, and S6105 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0549] Figure 6B is a schematic flowchart of a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. The communication method is executed by a fourth network element 1034. As shown in Figure 6B, the method includes steps S6201 to S6202.

[0550] In step S6201, QoS monitoring is performed.

[0551] The optional implementation of step S6201 can be found in the optional implementation of step S2201 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0552] In step S6202, the third message is sent.

[0553] The optional implementation of step S6202 can be found in the optional implementation of step S2202 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

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

[0555] The communication method involved in the embodiments of this disclosure may include at least one of steps S6201 to S6202. For example, step S6201 may be implemented as a standalone embodiment. For example, step S6202 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S6201 to S6202 are not limited thereto.

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

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

[0558] Figure 7 is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. The communication method is executed by a first device 102. As shown in Figure 7, the method includes steps S701 to S704.

[0559] In step S701, the sixth message is obtained.

[0560] The optional implementation of step S701 can be found in the optional implementation of step S2108 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

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

[0562] In step S702, the data stream is acquired.

[0563] The optional implementation of step S702 can be found in the optional implementation of step S2111 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0564] In some embodiments, the first device 102 may receive a data stream sent by the fourth network element 1034, but is not limited thereto, and may also receive a data stream sent by other entities.

[0565] In step S703, QoS processing is performed.

[0566] The optional implementation of step S703 can be found in the optional implementation of step S2112 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0567] In some embodiments, QoS processing can be implemented based on the group pose information corresponding to the first stream group.

[0568] In step S704, the data stream is sent.

[0569] The optional implementation of step S704 can be found in the optional implementation of step S2113 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0570] In some embodiments, the first device 102 may send a data stream to the terminal 101, but is not limited thereto, and may also send a data stream to other entities.

[0571] The communication method involved in the embodiments of this disclosure may include at least one of steps S701 to S704. For example, step S702 may be implemented as a standalone embodiment. For example, step S703 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S701 to S704 are not limited thereto.

[0572] In some embodiments, steps S701, S703, and S704 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0573] In some embodiments, steps S701, S702, and S704 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0574] Figure 8A is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 8A, the present disclosure relates to a communication method. The communication method includes step S8101.

[0575] In step S8101, the second network element 1032 sends the first information to the first network element 1031.

[0576] Optional implementations of step S8101 can be found in optional implementations of steps S2101 and S2103 in FIG2A, as well as other related parts in the embodiments involved in FIG2A, which will not be repeated here.

[0577] Figure 8B is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 8B, the present disclosure relates to a communication method. The communication method includes step S8201.

[0578] In step S8201, the first network element 1031 sends the second information to the third network element 1033.

[0579] The optional implementation of step S8201 can be found in the optional implementation of step S2105 in FIG2A, and other related parts in the embodiment involved in FIG2A, which will not be repeated here.

[0580] Figure 8C is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 8C, the present disclosure relates to a communication method. The communication method includes step S8301.

[0581] In step S8301, the third network element 1033 sends the fourth information to the fourth network element 1034.

[0582] The optional implementation of step S8301 can be found in the optional implementation of step S2106 in FIG2A, and other related parts in the embodiment involved in FIG2A, which will not be repeated here.

[0583] Figure 8D is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 8D, the present disclosure relates to a communication method. The communication method includes step S8401.

[0584] In step S8401, the fourth network element 1034 sends a data stream to the first device 102.

[0585] Optional implementations of step S8401 can be found in optional implementations of step S2111 in FIG2A, and other related parts in the embodiments involved in FIG2A, which will not be repeated here.

[0586] In the following, specific embodiments of the present disclosure will be described by way of example.

[0587] In some embodiments, immersive virtual reality communication adds policy functions such as group pose information recognition and response SDF QoS management.

[0588] In some embodiments, to support immersive virtual reality communication, the identification of group pose information and the coordination of media streams employing group pose information can be proposed. Media streams employing group pose information may include, for example, multiple streams corresponding to the same pose information, multiple streams corresponding to the same or similar XR timestamps, and multiple streams corresponding to the same or associated actions.

[0589] In some embodiments, media streams employing group pose information can be identified as stream groups. Stream groups may include one or more types of streams. For example, multiple streams may correspond to the same pose information. For example, multiple streams may correspond to the same or dependent XR timestamps. For example, multiple streams may correspond to the same or dependent actions.

[0590] In some embodiments, the AF may provide QoS requirements for media streams to the core network (e.g., NEF / PCF) during the AF QoS request / update process. QoS requirements include group pose information support indications and / or coordination of media stream groups employing group pose information. Group pose information support indications may indicate support for group pose information identification.

[0591] In some embodiments, QoS requirements include flow group types. Media streams employing group pose information can be identified as flow groups. A flow group includes one or more types of streams. For example, multiple streams may correspond to the same pose information. For example, multiple streams may correspond to the same or dependent XR timestamps. For example, multiple streams may correspond to the same or dependent actions.

[0592] In some embodiments, the identification of identical poses can be achieved using a media identifier (MID). The MID value indicates all media streams to which the pose RTP HE can be applied. For example, the MID value can be carried in one of all media streams. In some embodiments, the identification of identical poses can use a position field and / or a direction field. Extended attribute media can be accompanied by a spatially independent series of MID values. In one example, if extended attribute media is present, the media description of all bitstreams multiplexed for RTP HE may include a "mid" attribute.

[0593] In some embodiments, pose information includes position fields (including x, y, z) and / or orientation fields (including rx, ry, rz, rw). 6DoF XR pose includes position fields x, y, z and orientation fields rx, ry, rz, rw. 3DoF XR pose does not include position fields rx, ry, rz, rw.

[0594] In some embodiments, the identification of identical or dependent XR timestamps can be achieved using the XR timestamp (timestamp for XR pose). When RTP HE is used to render the pose, this timestamp indicates the playback time predicted by the XR runtime for the rendered image. In some embodiments, this timestamp indicates the playback time for the relevant XR runtime for the predicted XR pose. The XR timestamp uses the XR system clock and is identified in nanoseconds. The timestamp is passed to the XR runtime along with the rendered swapchain image. The receiver can use the XR timestamp and the RTP timestamp to determine the playback time of the media. The receiver's application is free to determine how to use the XR timestamp.

[0595] In some embodiments, the identification of identical or dependent actions can be achieved using an action identifier (action_id). The action of the action identifier can correspond to the x, y, z, rx, ry, rz, and rw coordinates of the pose. The action identifier uniquely identifies the action and can be an action identifier. The number of action identifiers in an RTP HE for an XR pose can not exceed 10. When the RTP HE for an XR pose is sent by the server, the RTP HE can include an action identifier field containing a series of action identifiers to identify the processed action used for frame rendering. When the RTP HE for an XR pose is sent by the UE, the RTP HE can include an action identifier field containing a series of action identifiers to identify the action applied to the pose coordinates.

[0596] In some embodiments, the AF request may include auxiliary pose information to be used as input for PCC rule determination. The auxiliary pose information includes at least one of the following:

[0597] - Group pose support types, such as 6DoF XR pose (XR pose includes position fields x, y, z, and orientation fields rx, ry, rz, rw) and 3DoF XR pose (XR pose does not include position fields x, y, z).

[0598] - The type of stream used by the group pose, for example, the group pose is used for a video stream, and / or an audio stream, and / or a haptic stream;

[0599] - RTP HE for group poses, used to transmit XR poses;

[0600] - Group identifier for pose;

[0601] - The priority or priority list supported by the group pose (e.g., priorities associated with QoS configuration and belonging to different groups).

[0602] In some embodiments, the AF may provide the above information to the core network (e.g., NEF / PCF) during the AF QoS request / update process.

[0603] Figure 9A is an interactive schematic diagram of an exemplary implementation of the communication method provided according to an embodiment of the present disclosure. As shown in Figure 9A, the communication method is implemented through multiple steps.

[0604] In some embodiments, the interaction process in FIG9A involves the UE, consumer, first control plane (CP) network function (NF), second CP NF, third CP NF, first user plane (UP) NF, NEF, and DN / AF.

[0605] In some embodiments, the consumer (or consumer NF) in this embodiment can be the RAN. In some embodiments, a consumer can refer to the object to which the service is addressed. For example, in a service-based scenario, the service can be provided to a consumer. In this case, the RAN can be considered the consumer. It is understood that the consumer can be device-independent. The object to which the service is provided is the consumer.

[0606] In some embodiments, the first CP NF can be a PCF. In some embodiments, the second CP NF can be an SMF. In some embodiments, the third CP NF can be an AMF. In some embodiments, the first UP NF can be a UPF.

[0607] In step 1, the AF (i.e., the second network element) sends an AF session resource request (i.e., the first message), for example, by creating an AF request through an Nnef_AFsessionWithQoS_Create request. The AF carries the QoS requirements for immersive virtual reality communication media streams (e.g., XRM services and interactive media service data streams) in the request message.

[0608] In some embodiments, the AF may provide QoS requirements for media streams to the core network (e.g., NEF / PCF) during the AF QoS request / update process. QoS requirements include group pose information support indications and / or coordination of media stream groups employing group pose information. Group pose information support indications may indicate support for group pose information identification.

[0609] In some embodiments, QoS requirements include flow group types. Media streams employing group pose information can be identified as flow groups. A flow group includes one or more types of streams. For example, multiple streams may correspond to the same pose information. For example, multiple streams may correspond to the same or dependent XR timestamps. For example, multiple streams may correspond to the same or dependent actions.

[0610] In some embodiments, the identification of identical poses can be achieved using a media identifier (MID). The MID value indicates all media streams to which the pose RTP HE can be applied. For example, the MID value can be carried in one of all media streams. In some embodiments, the identification of identical poses can use a position field and / or a direction field. Extended attribute media can be accompanied by a spatially independent series of MID values. In one example, if extended attribute media is present, the media description of all bitstreams multiplexed for RTP HE may include a "mid" attribute.

[0611] In some embodiments, pose information includes position fields (including x, y, z) and / or orientation fields (including rx, ry, rz, rw). 6DoF XR pose includes position fields x, y, z and orientation fields rx, ry, rz, rw. 3DoF XR pose does not include position fields rx, ry, rz, rw.

[0612] In some embodiments, the identification of identical or dependent XR timestamps can be achieved using the XR timestamp (timestamp for XR pose). When RTP HE is used to render the pose, this timestamp indicates the playback time predicted by the XR runtime for the rendered image. In some embodiments, this timestamp indicates the playback time for the relevant XR runtime for the predicted XR pose. The XR timestamp uses the XR system clock and is identified in nanoseconds. The timestamp is passed to the XR runtime along with the rendered swapchain image. The receiver can use the XR timestamp and the RTP timestamp to determine the playback time of the media. The receiver's application is free to determine how to use the XR timestamp.

[0613] In some embodiments, the identification of identical or dependent actions can be achieved using an action identifier (action_id). The action of the action identifier can correspond to the x, y, z, rx, ry, rz, and rw coordinates of the pose. The action identifier uniquely identifies the action and can be an action identifier. The number of action identifiers in an RTP HE for an XR pose can not exceed 10. When the RTP HE for an XR pose is sent by the server, the RTP HE can include an action identifier field containing a series of action identifiers to identify the processed action used for frame rendering. When the RTP HE for an XR pose is sent by the UE, the RTP HE can include an action identifier field containing a series of action identifiers to identify the action applied to the pose coordinates.

[0614] In some embodiments, the AF request may include auxiliary pose information to be used as input for PCC rule determination. The auxiliary pose information includes at least one of the following:

[0615] - Group pose support types, such as 6DoF XR pose (XR pose includes position fields x, y, z, and orientation fields rx, ry, rz, rw) and 3DoF XR pose (XR pose does not include position fields x, y, z).

[0616] - The type of stream used by the group pose, for example, the group pose is used for a video stream, and / or an audio stream, and / or a haptic stream;

[0617] - RTP HE for group poses, used to transmit XR poses;

[0618] - Group identifier for pose;

[0619] - The priority or priority list supported by the group pose (e.g., priorities associated with QoS configuration and belonging to different groups).

[0620] In some embodiments, the AF may provide the above information to the core network (e.g., NEF / PCF) during the AF QoS request / update process.

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

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

[0623] In step 3, the NEF authorizes the AF request and determines whether to initiate TSCTSF or directly contact the PCF based on the parameters provided by the AF. These signaling steps can be found in the AF session with required QoS procedure. The PCF receives the attributes provided by the AF from the NEF or TSCTSF. The NEF triggers Npcf_PolicyAuthorization_Create, sending the AF request to the PCF, carrying QoS requirement information for the PCF to make policy decisions.

[0624] In some embodiments, the message carries a group pose information support indication for the corresponding SDF to indicate support for group pose information identification and / or coordination of media stream groups using group pose information.

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

[0626] In some embodiments, PCF authorizes (e.g., in PCC rules) service data streams, taking into account group pose support indications provided by AF for group pose information identification, and / or coordination of media stream groups using group pose information, and / or local operator configurations (e.g., stream group type, etc.).

[0627] In some embodiments, the PCF may determine a PCC rule (i.e., a first rule) taking into account the indication of group pose information support (indicating support for group pose information identification), and / or the coordination of media stream groups employing group pose information, and / or the stream group type. The PCF may (e.g., via the PCC rule) send authorized group pose information support (i.e., second information) to the SMF.

[0628] In some embodiments, the authorized group pose information supports at least one of the following:

[0629] - Stream group types: multiple streams correspond to the same pose information, multiple streams correspond to the same or similar XR timestamps, and multiple streams correspond to the same or related actions;

[0630] -Group pose support instructions;

[0631] - Group pose support types, such as 6DoF XR pose and 3DoF XR pose;

[0632] - The type of stream used by the group pose, for example, the group pose is used for a video stream, and / or an audio stream, and / or a haptic stream;

[0633] - RTP HE for group poses, used to transmit XR poses;

[0634] - Group identifier for pose;

[0635] - The priority or priority list supported by the group pose (e.g., priorities associated with QoS configuration and belonging to different groups).

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

[0637] In step 6, NEF sends an Nnef_AFsessionWithQoS_Create response message to AF, which carries the result to indicate whether the request has been authorized.

[0638] In step 7, the PCF initiates a Policy Association Modification request to the SMF, which carries the PCC rules.

[0639] In some embodiments, based on the PCC rules from the PCF, the SMF (i.e., the third network element) generates and provides QoS configuration, and provides it along with authorized QoS parameters to the NG-RAN (i.e., the first device).

[0640] In some embodiments, the SMF instructs the UPF (i.e., the fourth network element) to identify / detect XR pose information (e.g., XR pose orientation quaternion coordinates, XR pose position coordinates, pose information object array, pose time, etc.), map or mark the XR pose information into the extended header, and send it to the consumer network function to implement QoS conditioning or QoS enforcement. In some embodiments, the SMF configures / activates rules to the UPF (e.g., via an N4 session).

[0641] In some embodiments, the SMF can configure or activate rules for the UPF, including authorized group pose information (e.g., via an N4 session).

[0642] In some embodiments, the SMF provides a group pose information tag indication to the UPF in the QoS Enforcement Rule (QER). The group pose information tag indication is provided to the UPF during the N4 session establishment or modification process (e.g., at the N4 reference point).

[0643] In step 8, in response, the SMF sends an SM Policy Association Modification response to the PCF.

[0644] In step 9, the SMF initiates an N4 Session Modification request (group pose information, group pose information marker indication) to the UPF.

[0645] In step 10, the UPF responds to the SMF.

[0646] In some embodiments, the first UP NF / UPF detects group pose information (e.g., MID, action identifier, XR timestamp, XR pose orientation quaternion coordinates, XR pose position coordinates, pose information object array, pose time, etc.), maps or marks the group pose information into an extended header (e.g., group identifier, flow group type, group pose type), and sends it to the consumer network function (e.g., sent to NG-RAN via a GTP-U header) to achieve QoS adjustment or QoS execution.

[0647] In some embodiments, when the DN does not provide group pose information through CP and UP, the OAM configuration based on UPF / OAM can achieve this operation.

[0648] In some embodiments, based on OAM configuration or operator policies, the first UP NF / UPF identifies group pose information (e.g., MID, action identifier, XR timestamp, XR pose orientation quaternion coordinates, XR pose location coordinates, pose information object array, pose time, etc.), maps or marks the group pose information into an extended header (e.g., group identifier, flow group type, group pose type), and sends it to the consumer network function (e.g., sent to NG-RAN via GTP-U header) to achieve QoS adjustment or QoS enforcement.

[0649] In step 11, for the modification of the SMF request, the SMF causes Namf_Communication_N1N2MessageTransfer(N2SM information (PDU session ID, QFI, QoS configuration, N1SM container)).

[0650] In step 12, the AMF (i.e., the sixth network element) can send N2 messages (N2SM information received from the SMF, NAS messages (PDU session ID, N1SM container (PDU session modification command))) to the RAN.

[0651] In step 14, the RAN can acknowledge the N2PDU session request by sending an N2PDU session acknowledgment (Session Ack) message to the AMF.

[0652] In some embodiments, NG-RAN can adjust QoS parameters by taking into account group pose information (e.g., group identifier, flow group type, group pose type) mapped or labeled from the first UP NF / UPF.

[0653] In some embodiments, with this QoS adjustment taking into account group pose information, data of a QoS stream (or QoS stream group) can be sent in a timely manner or as a stream group (e.g., a group priority policy is applied to each stream taking into account the latency difference between multiple streams).

[0654] In step 15, the AMF forwards the N2SM information from the access network to the SMF through the Nsmf_PDUSession_UpdateSMContext service operation.

[0655] In step 16, SMF responds with the Nsmf_PDUSession_UpdateSMContext response.

[0656] In steps 17 and 18, the SMF can update the N4 session of the UPF involved in the PDU session modification by sending an N4 session modification request to the UPF.

[0657] Figure 9B is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure. As shown in Figure 9B, the communication method is implemented through multiple steps.

[0658] In step 1a, steps 1 to 7a of the PDU Session Establishment process are performed.

[0659] In step 1b, the AF can send information to the PCF via the Nnef_AfsessionWithQoS_Create request (QoS parameters for each PDU set within the QoS stream, as well as frame identification parameters). The AF can also provide this information to the 5GS before the PDU session is established.

[0660] In some embodiments, the AF carries QoS requirements for immersive virtual reality communication media streams (e.g., XRM services and interactive media service data streams) in the request message.

[0661] In some embodiments, the AF may provide QoS requirements for media streams to the core network (e.g., NEF / PCF) during the AF QoS request / update process. QoS requirements include group pose information support indications and / or coordination of media stream groups employing group pose information. Group pose information support indications may indicate support for group pose information identification.

[0662] In some embodiments, QoS requirements include flow group types. Media streams employing group pose information can be identified as flow groups. A flow group includes one or more types of streams. For example, multiple streams may correspond to the same pose information. For example, multiple streams may correspond to the same or dependent XR timestamps. For example, multiple streams may correspond to the same or dependent actions.

[0663] In some embodiments, the identification of identical poses can be achieved using the MID (Match ID). The MID value indicates all media streams to which the pose RTP HE can be applied. For example, the MID value can be carried in one of all media streams. In some embodiments, the identification of identical poses can use a position field and / or a direction field. Extended attribute media can be accompanied by a spatially independent set of MID values. In one example, if extended attribute media is present, the media description of all bitstreams multiplexed for RTP HE can include a "mid" attribute.

[0664] In some embodiments, pose information includes position fields (including x, y, z) and / or orientation fields (including rx, ry, rz, rw). 6DoF XR pose includes position fields x, y, z and orientation fields rx, ry, rz, rw. 3DoF XR pose does not include position fields rx, ry, rz, rw.

[0665] In some embodiments, the identification of identical or dependent XR timestamps can be achieved using the XR timestamp (timestamp for XR pose). When RTP HE is used to render the pose, this timestamp indicates the playback time predicted by the XR runtime for the rendered image. In some embodiments, this timestamp indicates the playback time for the relevant XR runtime for the predicted XR pose. The XR timestamp uses the XR system clock and is identified in nanoseconds. The timestamp is passed to the XR runtime along with the rendered exchange chain image. The receiver can use the XR timestamp and the RTP timestamp to determine the playback time of the media. The receiver's application is free to determine how to use the XR timestamp.

[0666] In some embodiments, the identification of identical or dependent actions can be achieved using an action identifier (action_id). The action of the action identifier can correspond to the x, y, z, rx, ry, rz, and rw coordinates of the pose. The action identifier uniquely identifies the action and can be an action identifier. The number of action identifiers in an RTP HE for an XR pose can not exceed 10. When the RTP HE for an XR pose is sent by the server, the RTP HE can include an action identifier field containing a series of action identifiers to identify the processed action used for frame rendering. When the RTP HE for an XR pose is sent by the UE, the RTP HE can include an action identifier field containing a series of action identifiers to identify the action applied to the pose coordinates.

[0667] In some embodiments, the AF request may include auxiliary pose information to be used as input for PCC rule determination. The auxiliary pose information includes at least one of the following:

[0668] - Group pose support types, such as 6DoF XR pose (XR pose includes position fields x, y, z, and orientation fields rx, ry, rz, rw) and 3DoF XR pose (XR pose does not include position fields x, y, z).

[0669] - The type of stream used by the group pose, for example, the group pose is used for a video stream, and / or an audio stream, and / or a haptic stream;

[0670] - RTP HE for group poses, used to transmit XR poses;

[0671] - Group identifier for pose;

[0672] - The priority or priority list supported by the group pose (e.g., priorities associated with QoS configuration and belonging to different groups).

[0673] In some embodiments, the AF may provide the above information to the core network (e.g., NEF / PCF) during the AF QoS request / update process.

[0674] In some embodiments, the Application Filter (AF) may provide a protocol description and auxiliary information related to PDU sets. This auxiliary information may include QoS parameters for each QoS set within a QoS flow. QoS parameters include at least one of the following: PDU set processing indication, whether the application layer requires all PDUs for the use of the PDU set, PDU set delay budget, and PDU set bit error rate. In some embodiments, the PDU set processing indication may be used to indicate whether to activate PDU set-based processing for the flow. This indication may be implicitly provided by other PDU set-related information provided by the AF.

[0675] In step 2, the PCF generates appropriate PCC rules. These PCC rules may include QoS parameters related to the PDU set. The PCF can then send the PCC rules to the SMF.

[0676] In some embodiments, PCF authorizes (e.g., in PCC rules) service data streams, taking into account group pose support indications provided by AF for group pose information identification, and / or coordination of media stream groups using group pose information, and / or local operator configurations (e.g., stream group type, etc.).

[0677] In some embodiments, the PCF may determine PCC rules, taking into account indications of group pose information support (indicating support for group pose information identification), and / or the coordination of media stream groups employing group pose information, and / or the stream group type. The PCF may (e.g., via PCC rules) send authorized group pose information support to the SMF.

[0678] In some embodiments, the authorized group pose information supports at least one of the following:

[0679] - Stream group types: multiple streams correspond to the same pose information, multiple streams correspond to the same or similar XR timestamps, and multiple streams correspond to the same or related actions;

[0680] -Group pose support instructions;

[0681] - Group pose support types, such as 6DoF XR pose and 3DoF XR pose;

[0682] - The type of stream used by the group pose, for example, the group pose is used for a video stream, and / or an audio stream, and / or a haptic stream;

[0683] - RTP HE for group poses, used to transmit XR poses;

[0684] - Group identifier for pose;

[0685] - The priority or priority list supported by the group pose (e.g., priorities associated with QoS configuration and belonging to different groups).

[0686] In some embodiments, the QoS parameters related to the PDU set can be new QoS parameters in 5GS for QoS processing based on the PDU set, and can include at least one of the following: PSDB, PSER, whether the application layer needs to use all PDUs for the PDU set, and whether to discard the PDU set when the PSDB is too large.

[0687] In some embodiments, step 2 can be completed through some steps in the PDU session establishment process or the PDU session modification process.

[0688] In some embodiments, step 2 may be triggered by step 1b, in which case the PCF may consider the information provided by the AF to generate PCC rules.

[0689] In step 3, the SMF generates the QoS configuration and N4 rules based on the PCC rules from the PCF. The SMF sends the N4 rules to the UPF and sends the QoS configuration to the RAN via the AMF.

[0690] In some embodiments, based on the PCC rules from the PCF, the SMF generates and provides QoS configuration and authorized QoS parameters to the NG-RAN.

[0691] In some embodiments, the SMF instructs the UPF to identify group pose information (e.g., MID, action identifier, XR timestamp, XR pose orientation quaternion coordinates, XR pose position coordinates, pose information object array, pose time, etc.), map or mark the group pose information into the extended header (e.g., group identifier, flow group type, group pose type), and send it to the consumer network function to achieve QoS adjustment or QoS enforcement.

[0692] In some embodiments, the SMF can configure or activate rules for the UPF, including authorized group pose information (e.g., via an N4 session).

[0693] In some embodiments, the SMF provides a group pose information tag indication to the UPF in the QER. The group pose information tag indication is provided to the UPF during the N4 session establishment or modification process (e.g., at the N4 reference point).

[0694] In some embodiments, step 3 can be completed through some steps in the PDU session establishment process or the PDU session modification process.

[0695] In step 4, the remaining steps of the PDU session establishment process and PDU session modification process are executed.

[0696] In step 5, based on the received N4 rules or local configuration, the UPF identifies relevant information and performs QoS processing based on the PDU set according to the N4 rule instructions.

[0697] In some embodiments,

[0698] The first UP NF / UPF detects group pose information (e.g., MID, action identifier, XR timestamp, XR pose orientation quaternion coordinates, XR pose position coordinates, pose information object array, pose time, etc.), maps or marks the group pose information into the extended header (e.g., group identifier, flow group type, group pose type), and sends it to the consumer network function (e.g., sent to NG-RAN via GTP-U header) to achieve QoS adjustment or QoS enforcement.

[0699] In some embodiments, when the DN does not provide group pose information through CP and UP, the OAM configuration based on UPF / OAM can achieve this operation.

[0700] In some embodiments, based on OAM configuration or operator policies, the first UP NF / UPF identifies group pose information (e.g., MID, action identifier, XR timestamp, XR pose orientation quaternion coordinates, XR pose location coordinates, pose information object array, pose time, etc.), maps or marks the group pose information into an extended header (e.g., group identifier, flow group type, group pose type), and sends it to the consumer network function (e.g., sent to NG-RAN via GTP-U header) to achieve QoS adjustment or QoS enforcement.

[0701] In some embodiments, the PDU set information in the extension header may include at least one of the following: PDU set sequence number, starting or ending PDU of the PDU set, PDU sequence number within the PDU set, number of PDUs within the PDU set, importance of the PDU set, size of the PDU set, and end of data burst.

[0702] In some embodiments, the UPF can identify relevant information through at least one of the following methods and / or mechanisms: matching of RTP / SRTP headers and payloads; new RTP extension headers; information contained in N6 encapsulation headers; detection of flow characteristics; and UPF implementations of non-standardized mechanisms.

[0703] In step 6, the UPF sends PDU set information to the RAN. The UPF sends the aforementioned PDU set information to the RAN. The UPF can add the PDU set information to the GTP-U header.

[0704] In step 7, based on the received PDU set information, the RAN can perform QoS processing based on the PDU set.

[0705] In some embodiments, NG-RAN can adjust QoS parameters by taking into account group pose information (e.g., group identifier, flow group type, group pose type) mapped or labeled from the first UP NF / UPF.

[0706] In some embodiments, with this QoS adjustment taking into account group pose information, data of a QoS stream (or QoS stream group) can be sent in a timely manner or as a stream group (e.g., a group priority policy is applied to each stream taking into account the latency difference between multiple streams).

[0707] In some embodiments, with this QoS adjustment taking into account XR pose information, data for a QoS stream (or QoS stream group) can be sent in a timely manner.

[0708] In the embodiments disclosed herein, 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 in other embodiments.

[0709] This disclosure also provides a communication apparatus for implementing any of the above methods. For example, this disclosure also provides another communication apparatus, including units or modules for implementing the steps performed by the network device (network element, first device) in any of the above methods.

[0710] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0711] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a central processing unit, microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit 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. Furthermore, 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), tensor processing unit (TPU), deep learning processing unit (DPU), etc.

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

[0713] In some embodiments, the communication device 1000 may be a first network element 1031. In some embodiments, the transceiver module 1001 may be configured to receive first information sent by a second network element, wherein the first information is used to determine the QoS policy of a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are associated with the group pose and have a cooperative relationship. Optionally, the transceiver module 1001 may be configured to perform at least one of the communication steps (e.g., steps S2103, S2105, S2203, S2204) performed by the first network element 1031 in any of the above methods, which will not be described in detail here. Optionally, the processing module 1002 may be configured to perform at least one of other steps (e.g., step S2104) besides the communication steps (e.g., step S2104) performed by the first network element 1031 in any of the above methods, which will not be described in detail here.

[0714] In some embodiments, the communication device 1000 may be a second network element 1032. In some embodiments, the transceiver module 1001 may be configured to send first information to a first network element, wherein the first information is used to determine the QoS policy of a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship. Optionally, the transceiver module 1001 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the second network element 1032 in any of the above methods (e.g., steps S2101, S2205), which will not be elaborated here.

[0715] In some embodiments, the communication device 1000 may be a third network element 1033. In some embodiments, the transceiver module 1001 may be configured to receive second information sent by a first network element, wherein the second information is used to implement QoS processing for a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship. Optionally, the transceiver module 1001 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the third network element 1033 in any of the above methods (e.g., steps S2105, S2106, S2107, S2202, S2203), which will not be described in detail here.

[0716] In some embodiments, the communication device 1000 may be a fourth network element 1034. In some embodiments, the transceiver module 1001 may be configured to receive fourth information sent by a third network element, wherein the fourth information is used to mark a first stream group; wherein the first stream group includes multiple streams, and the multiple streams are related to the group pose and have a cooperative relationship. Optionally, the transceiver module 1001 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the fourth network element 1034 in any of the above methods (e.g., steps S2106, S2111, S2115, S2202), which will not be described in detail here. Optionally, the processing module 1002 may be configured to perform at least one of other steps besides the communication steps such as sending and / or receiving performed by the fourth network element 1034 in any of the above methods (e.g., steps S2110, S2114, S2201), which will not be described in detail here.

[0717] In some embodiments, the communication device 1000 may be the first device 102. In some embodiments, the transceiver module 1001 may be configured to: receive data packets of a first flow group sent by a fourth network element, wherein the data packets contain group pose information, and the group pose information is used by the first device to perform QoS processing on the data packets; wherein the first flow group includes multiple flows, and the multiple flows are related to the group pose and have a cooperative relationship. Optionally, the transceiver module 1001 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the first device 102 in any of the above methods (e.g., steps S2108, S2111, S2113), which will not be elaborated here. Optionally, the processing module 1002 may be configured to perform at least one of other steps (e.g., step S2112) besides the communication steps such as sending and / or receiving performed by the first device 102 in any of the above methods, which will not be elaborated here.

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

[0719] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0720] Figure 11A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. The communication device 11100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 11100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0721] As shown in Figure 11A, the communication device 11100 includes one or more processors 11101. The processor 11101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 11100 can be used to execute any of the above methods. Optionally, one or more processors 11101 can be used to invoke instructions to cause the communication device 11100 to execute any of the above methods.

[0722] In some embodiments, the communication device 11100 further includes one or more transceivers 11102. When the communication device 11100 includes one or more transceivers 11102, the transceivers 11102 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2103, S2105, S2106, S2107, S2108, S2109, S2111, S2113, S2115, S2202, S2203, S2204, S2205, but not limited thereto), and the processor 11101 performs at least one of other steps (e.g., steps S2102, S2104, S2110, S2112, S2114, S2201, but not limited thereto). In optional embodiments, the transceivers may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be used interchangeably; and terms such as receiver, receiving unit, receiver, and receiving circuit can be used interchangeably.

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

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

[0725] Figure 11B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. For cases where the communication device 11100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 11200 shown in Figure 11B, but it is not limited thereto.

[0726] Chip 11200 includes one or more processors 11201. Chip 11200 is used to perform any of the above methods.

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

[0728] In some embodiments, the interface circuit 11202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2103, S2105, S2106, S2107, S2108, S2109, S2111, S2113, S2115, S2202, S2203, S2204, S2205, but not limited thereto). The interface circuit 11202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 11202 performing data interaction between the processor 11201, the chip 11200, the memory 11203, or the transceiver device. In some embodiments, the processor 11201 performs at least one of other steps (e.g., steps S2102, S2104, S2110, S2112, S2114, S2201, but not limited thereto).

[0729] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0730] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 11100, cause the communication device 11100 to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto; it 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; it may also be a temporary storage medium.

[0731] This disclosure also proposes a program product that, when executed by the communication device 11100, causes the communication device 11100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0732] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0733] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.

[0734] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

A communication method, performed by a first network element, wherein The method comprises: receiving first information sent by a second network element, wherein the first information is used to determine a quality of service (QoS) policy of a first flow group; wherein the first flow group comprises a plurality of flows, and the plurality of flows are related to a group pose and have a cooperative relationship. The method of claim 1, wherein, The first information comprises at least one of: first support information, used to indicate whether to support the group pose; flow group type information, used to indicate a flow group type of the first flow group; auxiliary information, used to determine the QoS policy. The method of claim 2, wherein, The flow group type of the first flow group comprises at least one of: the plurality of flows correspond to the same pose information; the plurality of flows correspond to the same or associated time stamps; the plurality of flows correspond to the same or associated actions. The method according to claim 2 or 3, wherein The auxiliary information comprises at least one of: pose type information, used to indicate a pose type of the group pose; flow type information, used to indicate a flow type associated with the group pose; protocol information, used to indicate a transmission protocol of the group pose; pose sharing information, used to indicate whether the group pose is used for a plurality of terminal devices; pose group information, used to indicate a flow group corresponding to the group pose; priority information, used to indicate a priority related to the group pose. The method of any one of claims 1 to 4, wherein The method further comprises: sending second information to a third network element, wherein the second information is used to implement QoS processing on the first flow group. The method of claim 5, wherein, The second information comprises at least one of: second support information, used to indicate support for the group pose; flow group type information, used to indicate a flow group type of the first flow group; auxiliary information, used to determine the QoS policy. The method according to claim 5 or 6, wherein The method further comprises: determining a first rule according to the first information, wherein the first rule comprises the second information. The method of any one of claims 5 to 7, wherein, The second information further comprises subscription information, which is used for event subscription related to the first flow group. The method of claim 8, wherein, The method further comprises: receiving third information sent by the third network element, wherein the third information is used to indicate an event related to the first flow group. A communication method, performed by a second network element, wherein The method comprises: sending first information to a first network element, wherein the first information is used to determine a quality of service (QoS) policy of a first flow group; wherein the first flow group comprises a plurality of flows, and the plurality of flows are related to a group pose and have a cooperative relationship. The method of claim 10, wherein, The first information comprises at least one of: first support information, used to indicate whether to support the group pose; flow group type information, used to indicate a flow group type of the first flow group; auxiliary information, used to determine the QoS policy. The method of claim 11, wherein, The flow group type of the first flow group comprises at least one of: the plurality of flows correspond to the same pose information; the plurality of flows correspond to the same or associated time stamps; the plurality of flows correspond to the same or associated actions. The method according to claim 11 or 12, wherein The auxiliary information comprises at least one of: pose type information, used to indicate a pose type of the group pose; flow type information, used to indicate a flow type associated with the group pose; protocol information, used to indicate a transmission protocol of the group pose; pose sharing information, used to indicate whether the group pose is used for a plurality of terminal devices; pose group information, used to indicate a flow group corresponding to the group pose; priority information, used to indicate a priority related to the group pose. A communication method, performed by a third network element, wherein The method comprises: receiving second information sent by a first network element, wherein the second information is used to implement quality of service (QoS) processing for a first flow group; wherein the first flow group comprises a plurality of flows, and the plurality of flows are related to a group pose and have a cooperative relationship. The method of claim 14, wherein, The second information comprises at least one of: Second support information for indicating support for the group pose; Flow group type information for indicating the flow group type of the first flow group; Auxiliary information for determining the QoS policy. The method of claim 15, wherein, The flow group type of the first flow group comprises at least one of: The plurality of flows correspond to the same pose information; The plurality of flows correspond to the same or associated time stamps; The plurality of flows correspond to the same or associated actions. The method according to claim 15 or 16, wherein The auxiliary information comprises at least one of: Pose type information for indicating the pose type of the group pose; Flow type information for indicating the flow type associated with the group pose; Protocol information for indicating the transmission protocol of the group pose; Pose sharing information for indicating whether the group pose is used for multiple terminal devices; Pose group information for indicating the flow group corresponding to the group pose; Priority information for indicating the priority related to the group pose. The method of any one of claims 14 to 17, wherein, The second information is included in a first rule, and the first rule is determined based on at least the first information. The method of any one of claims 14-18, wherein The method further comprises: sending fourth information to a fourth network element, wherein the fourth information is used for marking processing of the first flow group. The method of claim 19, wherein, The method further comprises: determining a second rule according to the second information, wherein the second rule comprises the fourth information. The method of claim 20, wherein, The second information and the fourth information both further comprise subscription information for event subscription related to the first flow group. The method of claim 21, wherein, The method further comprises: receiving third information sent by a fourth network element, wherein the third information is used to indicate an event related to the first flow group; sending the third information to the first network element. A communication method, performed by a fourth network element, wherein The method comprises: receiving fourth information sent by a third network element, wherein the fourth information is used for marking processing of a first flow group; wherein the first flow group comprises a plurality of flows, and the plurality of flows are related to a group pose and have a cooperative relationship. The method of claim 23, wherein, The fourth information comprises at least one of: Second support information for indicating support for the group pose; Flow group type information for indicating the flow group type of the first flow group; Auxiliary information for determining the QoS policy. The method of claim 24, wherein, The flow group type of the first flow group comprises at least one of: The plurality of flows correspond to the same pose information; The plurality of flows correspond to the same or associated time stamps; The plurality of flows correspond to the same or associated actions. The method of claim 24 or 25, wherein, The auxiliary information comprises at least one of: Pose type information for indicating the pose type of the group pose; Flow type information for indicating the flow type associated with the group pose; Protocol information for indicating the transmission protocol of the group pose; Pose sharing information for indicating whether the group pose is used for multiple terminal devices; Pose group information for indicating the flow group corresponding to the group pose; Priority information for indicating the priority related to the group pose. The method of any one of claims 23 to 26, wherein, The method further comprises: detecting group pose information in the first flow group according to the fourth information; add the group pose information to a header of a data packet of the first flow group to implement a marking process on the first flow group. The method of claim 27, wherein, The group pose information comprises at least one of: a flow identifier for identifying the multiple flows in the first flow group; an action identifier for identifying at least one action corresponding to the group pose; a timestamp for indicating a time of the multiple flows in the first flow group; a direction coordinate value; a position coordinate value; a pose array of multiple objects; a pose time. The method of claim 27 or 28, wherein, The method further comprises: sending the data packet with the group pose information added in the first flow group to a first device, wherein the group pose information is used for the first device to perform QoS processing on the data packet. The method of any one of claims 23 to 29, wherein, The fourth information further comprises subscription information, and the subscription information is used for event subscription related to the first flow group. A communication method performed by a first device, wherein The method comprises: receiving a data packet of a first flow group sent by a fourth network element, wherein the data packet contains group pose information, and the group pose information is used for a first device to perform quality of service (QoS) processing on the data packet; wherein the first flow group comprises multiple flows, and the multiple flows are related to a group pose and have a cooperative relationship. The method of claim 31, wherein, The group pose information comprises at least one of: a flow identifier for identifying the multiple flows in the first flow group; an action identifier for identifying at least one action corresponding to the group pose; a timestamp for indicating a time of the multiple flows in the first flow group; a direction coordinate value; a position coordinate value; a pose array of multiple objects; a pose time. The method of claim 31 or 32, wherein, The method further comprises: determining a QoS parameter of a QoS flow related to the first flow group according to the group pose information. A communication method, performed by a core network, wherein The core network comprises a first network element, a second network element, a third network element, and a fourth network element; wherein the method comprises at least one of: the first network element performs the communication method according to any one of claims 1 to 9; the second network element performs the communication method according to any one of claims 10 to 13; the third network element performs the communication method according to any one of claims 14 to 22; the fourth network element performs the communication method according to any one of claims 23 to 30. A communication device is arranged in a first network element, wherein The communication device comprises: a transceiver module configured to receive first information sent by a second network element, wherein the first information is used to determine a quality of service (QoS) policy of a first flow group; and wherein the first flow group comprises multiple flows, and the multiple flows are related to a group pose and have a cooperative relationship. A communication device is arranged in a second network element, wherein The communication device comprises: a transceiver module configured to send first information to a first network element, wherein the first information is used to determine a quality of service (QoS) policy of a first flow group; and wherein the first flow group comprises multiple flows, and the multiple flows are related to a group pose and have a cooperative relationship. The communication device comprises: A communication device is arranged in a third network element, wherein a transceiver module configured to receive second information sent by a first network element, wherein the second information is used to implement quality of service (QoS) processing on a first flow group; and wherein the first flow group comprises multiple flows, and the multiple flows are related to a group pose and have a cooperative relationship. The communication device comprises: A communication device is arranged in a fourth network element, wherein ​ The transceiver is configured to receive fourth information sent by a third network element, wherein the fourth information is used for marking processing of a first flow group; wherein the first flow group includes multiple flows, and the multiple flows are related to a group pose and have a cooperative relationship. A communication device is provided in a first apparatus, wherein The communication device includes: The transceiver is configured to receive a data packet of a first flow group sent by a fourth network element, wherein the data packet contains group pose information, and the group pose information is used for quality of service (QoS) processing of the data packet by the first device; wherein the first flow group includes multiple flows, and the multiple flows are related to a group pose and have a cooperative relationship. A communication device includes: One or more processors; Memory storing instructions; Wherein the instructions, when executed on the communication device, cause the communication device to implement at least one of: The communication method of any one of claims 1-9; The communication method of any one of claims 10-13; The communication method of any one of claims 14-22; The communication method of any one of claims 23-30; The communication method of any one of claims 31-33. A communication system includes: A first network element for implementing the communication method of any one of claims 1-9; A second network element for implementing the communication method of any one of claims 10-13; A third network element for implementing the communication method of any one of claims 14-22; A fourth network element for implementing the communication method of any one of claims 23-30; A first device for implementing the communication method of any one of claims 31-33. A storage medium storing instructions, wherein, When the instructions are run on the communication device, the communication device implements at least one of: The communication method of any one of claims 1-9; The communication method of any one of claims 10-13; The communication method of any one of claims 14-22; The communication method of any one of claims 23-30; The communication method of any one of claims 31-33. A computer program product including instructions, wherein when the instructions are run on the communication device, the communication device implements at least one of: The communication method of any one of claims 1-9; The communication method of any one of claims 10-13; The communication method of any one of claims 14-22; The communication method of any one of claims 23-30; The communication method of any one of claims 31-33.

Images