Communication method, network element, device, communication system, and storage medium

Abstract

The present disclosure relates to a communication method, a network element, a device, a communication system, and a storage medium. The method comprises: receiving first information, wherein the first information is used for triggering marking processing of a first data stream of a first service, and the first service is a service related to a pose; and on the basis of the first information, performing marking processing on the first data stream. By means of the solution of the present disclosure, the support for the QoS processing of a data stream of a pose-related service is achieved.

Description

Communication methods, network elements, 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, network element, device, 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] Summary of the Invention

[0004] This disclosure provides a communication method, network element, device, communication system, storage medium, and computer program product.

[0005] According to a first aspect of the present disclosure, a communication method is provided. The communication method is executed by a first network element. The communication method includes: receiving first information, wherein the first information is used to trigger marking processing of a first data stream of a first service, the first service being a pose-related service; and marking the first data stream according to the first information.

[0006] According to a second aspect of the present disclosure, a communication method is provided. This communication method is performed by a second network element. The communication method includes: sending first information, wherein the first information is used to trigger marking processing of a first data stream of a first service, the first service being a pose-related service.

[0007] According to a third aspect of the present disclosure, a communication method is provided. The communication method is performed by a first device. The communication method includes: receiving a first data stream of a first service that has undergone tagging processing, wherein the first service is a pose-related service; and determining quality of service (QoS) parameters based on the tagged first data stream.

[0008] According to a fourth aspect of the present disclosure, a communication method is provided. This communication method is performed by a core network. The core network includes a first network element and a second network element. The communication method includes: the second network element sending first information to the first network element, wherein the first information is used to trigger marking processing of a first data stream of a first service, the first service being a pose-related service; and the first network element marking processing of the first data stream according to the first information.

[0009] According to a fifth aspect of the present disclosure, a first network element is provided. The first network element includes a transceiver module and a processing module. The transceiver module is configured to: receive first information, wherein the first information is used to trigger marking processing of a first data stream of a first service, the first service being a pose-related service. The processing module is configured to: perform marking processing on the first data stream according to the first information.

[0010] According to a sixth aspect of the present disclosure, a second network element is provided. The second network element includes a transceiver module. The transceiver module is configured to: send first information, wherein the first information is used to trigger marking processing of a first data stream of a first service, the first service being a pose-related service.

[0011] According to a seventh aspect of the present disclosure, a first device is provided. The first device includes a transceiver module and a processing module. The transceiver module is configured to receive a first data stream of a first service that has undergone tagging processing, wherein the first service is a pose-related service. The processing module is configured to determine QoS parameters based on the tagged first data stream.

[0012] According to an eighth aspect of the present disclosure, a communication device is provided. The communication device includes one or more processors. The communication device is used to perform the communication method as described in the first aspect.

[0013] According to a ninth aspect of the present disclosure, a communication device is provided. The communication device includes one or more processors. The communication device is used to perform the communication method as described in the second aspect.

[0014] According to a tenth aspect of this disclosure, a communication device is provided. The communication device includes one or more processors. The communication device is used to perform the communication method as described in the third aspect.

[0015] According to an eleventh aspect of the present disclosure, a communication system is provided. The communication system includes a first network element, a second network element, and a first device. The first network element is used to implement the communication method as described in the first aspect. The second network element is used to implement the communication method as described in the second aspect. The first device is used to implement the communication method as described in the third aspect.

[0016] According to a twelfth 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 fourth aspects.

[0017] According to a thirteenth 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 fourth aspects.

[0018] According to a fourteenth aspect of the present disclosure, a computer program is provided. When the 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 fourth aspects.

[0019] According to a fifteenth aspect of the present 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 fourth aspects.

[0020] The embodiments disclosed herein enable support for quality of service (QoS) processing of data streams for pose-related services.

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

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

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

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

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

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

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

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

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

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

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

[0032] Figure 5 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

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

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

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

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

[0037] Figure 7C is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

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

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

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

[0041] This disclosure provides a communication method, network element, device, communication system, storage medium, and computer program product.

[0042] In a first aspect, embodiments of this disclosure provide a communication method. The communication method is executed by a first network element. The communication method includes: receiving first information, wherein the first information is used to trigger marking processing of a first data stream of a first service, the first service being a pose-related service; and marking the first data stream according to the first information.

[0043] According to this embodiment, the first network element can be triggered by first information to mark the first data stream of a pose-related first service. In this way, the marked first data stream can be processed using pose-related QoS methods, thereby supporting QoS processing for pose-related services. Based on this QoS processing, the transmission efficiency of the pose-related service data stream can be improved, thus ensuring the communication quality of pose-related services.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the first information may include at least one of the following: indication information for indicating that the first data stream is marked; and protocol description information for indicating the protocol characteristics of the transport protocol associated with the first data stream.

[0045] According to this embodiment, based on the instruction information, the first network element can determine that it is necessary to perform marking processing for the first data stream.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the transport protocol may include at least one of the following: real-time transport protocol (RTP); secure real-time transport protocol (SRTP).

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the protocol features may include at least one of the following: having an RTP extended header; having an RTP payload format.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the indication information may be included in the QoS enforcement rule (QER) associated with the first data stream.

[0049] According to this embodiment, the indication information can be carried in the QER, enabling the first network element to obtain the indication information from the received QER. Thus, when the first network element performs QoS processing according to the QER, it can determine the marking process for the first data stream based on the indication information.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the operation of marking the first data stream according to the first information may include: adding pose information to the extended header or encapsulation header of the data packets of the first data stream.

[0051] According to this embodiment, pose information can be added to the extended header or encapsulation header of the data packets of the first data stream. This allows pose information to be directly obtained from the extended header or encapsulation header, thereby enabling QoS processing for data streams with pose-related services.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments, the pose information may include at least one of the following: type information, for indicating pose type; parameter information, for indicating parameter values ​​of pose; time information, for indicating time corresponding to pose; action information, for indicating action related to pose; flow information, for indicating flow related to pose; and priority information, for indicating priority related to pose.

[0053] According to this embodiment, the pose information may include various pose-related information, including type information, parameter information, time information, action information, stream information, priority information, etc. Based on at least one of these information, the pose information marked in the first data stream can be used to implement QoS processing for different business scenarios and requirements.

[0054] In conjunction with some embodiments of the first aspect, in some embodiments, the pose type may include at least one of the following: six degrees of freedom (6DoF); three degrees of freedom (3DoF).

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the parameter information may include at least one of the following: position-related parameter values; and direction-related parameter values.

[0056] In conjunction with some embodiments of the first aspect, in some embodiments, the motion information may include a motion identifier of at least one motion associated with the pose.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the flow information may include a flow identifier of at least one flow associated with the same pose.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include: receiving second information, wherein the second information is used to stop the marking process of the first data stream; and stopping the marking process of the first data stream according to the second information.

[0059] According to this embodiment, the first network element can be triggered by the second information to stop marking the first data stream of the pose-related first service. In this way, the first data stream can be processed using conventional QoS methods, thereby stopping the special processing of the pose-related service data stream.

[0060] In a second aspect, embodiments of this disclosure provide a communication method. This communication method is executed by a second network element. The communication method includes: sending first information, wherein the first information is used to trigger marking processing of a first data stream of a first service, the first service being a pose-related service.

[0061] According to this embodiment, the second network element can send first information to trigger marking processing of the first data stream of the pose-related first service. In this way, the first data stream after marking processing can be subjected to pose-related QoS processing, thereby supporting QoS processing for pose-related services. Based on this QoS processing, the transmission efficiency of the data stream of pose-related services can be improved, thereby ensuring the communication quality of pose-related services.

[0062] In conjunction with some embodiments of the second aspect, in some embodiments, the first information may include at least one of the following: indication information for indicating that the first data stream is marked; and protocol description information for indicating the protocol characteristics of the transport protocol associated with the first data stream.

[0063] In conjunction with some embodiments of the second aspect, in some embodiments, the transport protocol may include at least one of the following: RTP; SRTP.

[0064] In conjunction with some embodiments of the second aspect, in some embodiments, the protocol features may include at least one of the following: having an RTP extended header; having an RTP payload format.

[0065] In conjunction with some embodiments of the second aspect, in some embodiments, the indication information may be included in the QER associated with the first data stream.

[0066] In conjunction with some embodiments of the second aspect, in some embodiments, the marking process of the first data stream may include adding pose information to the extended header or encapsulation header of the data packets of the first data stream.

[0067] In conjunction with some embodiments of the second aspect, in some embodiments, the pose information may include at least one of the following: type information, used to indicate the pose type; parameter information, used to indicate the parameter values ​​of the pose; time information, used to indicate the time corresponding to the pose; action information, used to indicate the action related to the pose; flow information, used to indicate the flow related to the pose; and priority information, used to indicate the priority related to the pose.

[0068] In conjunction with some embodiments of the second aspect, in some embodiments, the pose type may include at least one of the following: 6DoF; 3DoF.

[0069] In conjunction with some embodiments of the second aspect, in some embodiments, the parameter information includes at least one of the following: position-related parameter values; and direction-related parameter values.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the motion information may include a motion identifier of at least one motion associated with the pose.

[0071] In conjunction with some embodiments of the second aspect, in some embodiments, the flow information includes a flow identifier of at least one flow associated with the same pose.

[0072] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: sending a second message, wherein the second message is used to stop the marking process of the first data stream.

[0073] In a third aspect, embodiments of this disclosure provide a communication method. This communication method is performed by a first device. The communication method includes: receiving a first data stream of a first service that has undergone tagging processing, wherein the first service is a pose-related service; and determining QoS parameters based on the tagged first data stream.

[0074] According to this embodiment, after the first data stream undergoes marking processing, it is sent to the first device. The first device can then determine QoS parameters based on the marked first data stream. Based on the determined QoS parameters, the first device can implement QoS processing for the first data stream. This QoS processing can improve the transmission efficiency of pose-related service data streams, thereby ensuring the communication quality of pose-related services.

[0075] In conjunction with some embodiments of the third aspect, in some embodiments, the header of the data packets of the first data stream after the marking process is marked with pose information, and the QoS parameters are determined based on the pose information in the first data stream after the marking process.

[0076] According to this embodiment, since pose information is marked in the first data stream, the first device can determine QoS parameters based on the pose information. Based on the determined QoS parameters, the first device can implement QoS processing for the first data stream. Because the QoS parameters are determined taking pose information into account, by marking pose information, support for QoS processing of data streams for pose-related services can be achieved.

[0077] In conjunction with some embodiments of the third aspect, in some embodiments, the pose information may include at least one of the following: type information, used to indicate the pose type; parameter information, used to indicate the parameter values ​​of the pose; time information, used to indicate the time corresponding to the pose; action information, used to indicate the action related to the pose; flow information, used to indicate the flow related to the pose; and priority information, used to indicate the priority related to the pose.

[0078] In conjunction with some embodiments of the third aspect, in some embodiments, the pose type may include at least one of the following: 6DoF; 3DoF.

[0079] In conjunction with some embodiments of the third aspect, in some embodiments, the parameter information may include at least one of the following: position-related parameter values; and direction-related parameter values.

[0080] In conjunction with some embodiments of the third aspect, in some embodiments, the motion information may include a motion identifier of at least one motion associated with the pose.

[0081] In conjunction with some embodiments of the third aspect, in some embodiments, the flow information may include a flow identifier of at least one flow associated with the same pose.

[0082] In a fourth 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 and a second network element. The communication method includes: the second network element sending first information to the first network element, wherein the first information is used to trigger marking processing of a first data stream of a first service, the first service being a pose-related service; and the first network element performing marking processing on the first data stream according to the first information.

[0083] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above method may further include: the second network element sending second information to the first network element, wherein the second information is used to stop the marking process of the first data stream; the first network element stopping the marking process of the first data stream according to the second information.

[0084] In a fifth aspect, embodiments of this disclosure provide a first network element. The first network element includes a transceiver module and a processing module. The transceiver module is configured to: receive first information, wherein the first information is used to trigger marking processing of a first data stream of a first service, the first service being a pose-related service. The processing module is configured to: perform marking processing on the first data stream according to the first information.

[0085] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information may include at least one of the following: indication information for indicating that the first data stream is marked; and protocol description information for indicating the protocol characteristics of the transport protocol associated with the first data stream.

[0086] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transport protocol may include at least one of the following: RTP; SRTP.

[0087] In conjunction with some embodiments of the fifth aspect, in some embodiments, the protocol features may include at least one of the following: having an RTP extended header; having an RTP payload format.

[0088] In conjunction with some embodiments of the fifth aspect, in some embodiments, the indication information may be included in the QER associated with the first data stream.

[0089] In conjunction with some embodiments of the fifth aspect, in some embodiments, the operation of marking the first data stream according to the first information may include: adding pose information to the extended header or encapsulation header of the data packets of the first data stream.

[0090] In conjunction with some embodiments of the fifth aspect, in some embodiments, the pose information may include at least one of the following: type information, for indicating pose type; parameter information, for indicating parameter values ​​of pose; time information, for indicating time corresponding to pose; action information, for indicating action related to pose; flow information, for indicating flow related to pose; and priority information, for indicating priority related to pose.

[0091] In conjunction with some embodiments of the fifth aspect, in some embodiments, the pose type may include at least one of the following: 6DoF; 3DoF.

[0092] In conjunction with some embodiments of the fifth aspect, in some embodiments, the parameter information may include at least one of the following: position-related parameter values; and direction-related parameter values.

[0093] In conjunction with some embodiments of the fifth aspect, in some embodiments, the motion information may include a motion identifier of at least one motion associated with the pose.

[0094] In conjunction with some embodiments of the fifth aspect, in some embodiments, the flow information may include a flow identifier of at least one flow associated with the same pose.

[0095] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module may also be configured to: receive second information, wherein the second information is used to stop the marking process of the first data stream; the processing module may also be configured to: stop the marking process of the first data stream according to the second information.

[0096] In a sixth aspect, embodiments of this disclosure provide a second network element. The second network element includes a transceiver module. The transceiver module is configured to: send first information, wherein the first information is used to trigger marking processing of a first data stream of a first service, the first service being a pose-related service.

[0097] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first information may include at least one of the following: indication information for indicating that the first data stream is marked; and protocol description information for indicating the protocol characteristics of the transport protocol associated with the first data stream.

[0098] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transport protocol may include at least one of the following: RTP; SRTP.

[0099] In conjunction with some embodiments of the sixth aspect, in some embodiments, the protocol features may include at least one of the following: having an RTP extended header; having an RTP payload format.

[0100] In conjunction with some embodiments of the sixth aspect, in some embodiments, the indication information may be included in the QER associated with the first data stream.

[0101] In conjunction with some embodiments of the sixth aspect, in some embodiments, the marking process of the first data stream may include adding pose information to the extended header or encapsulation header of the data packets of the first data stream.

[0102] In conjunction with some embodiments of the sixth aspect, in some embodiments, the pose information may include at least one of the following: type information, for indicating pose type; parameter information, for indicating parameter values ​​of pose; time information, for indicating time corresponding to pose; action information, for indicating action related to pose; flow information, for indicating flow related to pose; and priority information, for indicating priority related to pose.

[0103] In conjunction with some embodiments of the sixth aspect, in some embodiments, the pose type may include at least one of the following: 6DoF; 3DoF.

[0104] In conjunction with some embodiments of the sixth aspect, in some embodiments, the parameter information includes at least one of the following: position-related parameter values; and direction-related parameter values.

[0105] In conjunction with some embodiments of the sixth aspect, in some embodiments, the motion information may include a motion identifier of at least one motion associated with the pose.

[0106] In conjunction with some embodiments of the sixth aspect, in some embodiments, the flow information includes a flow identifier of at least one flow associated with the same pose.

[0107] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transceiver module may also be configured to: send second information, wherein the second information is used to stop the marking process of the first data stream.

[0108] In a seventh aspect, embodiments of this disclosure provide a first device. The first device includes a transceiver module and a processing module. The transceiver module is configured to: receive a first data stream of a first service after being marked, wherein the first service is a pose-related service. The processing module is configured to: determine QoS parameters based on the marked first data stream.

[0109] In conjunction with some embodiments of the seventh aspect, in some embodiments, the header of the data packets of the first data stream after the marking process is marked with pose information, and the QoS parameters are determined based on the pose information in the first data stream after the marking process.

[0110] In conjunction with some embodiments of the seventh aspect, in some embodiments, the pose information may include at least one of the following: type information, for indicating pose type; parameter information, for indicating parameter values ​​of pose; time information, for indicating time corresponding to pose; action information, for indicating action related to pose; flow information, for indicating flow related to pose; and priority information, for indicating priority related to pose.

[0111] In conjunction with some embodiments of the seventh aspect, in some embodiments, the pose type may include at least one of the following: 6DoF; 3DoF.

[0112] In conjunction with some embodiments of the seventh aspect, in some embodiments, the parameter information may include at least one of the following: position-related parameter values; and direction-related parameter values.

[0113] In conjunction with some embodiments of the seventh aspect, in some embodiments, the motion information may include a motion identifier of at least one motion associated with the pose.

[0114] In conjunction with some embodiments of the seventh aspect, in some embodiments, the flow information may include a flow identifier of at least one flow associated with the same pose.

[0115] In an eighth aspect, embodiments of this disclosure provide a communication device. The communication device includes one or more processors. The communication device is used to perform the communication method as described in any one of the first aspects and its possible embodiments.

[0116] In a ninth aspect, embodiments of this disclosure provide a communication device. The communication device includes one or more processors. The communication device is used to perform the communication method as described in any one of the second aspects and its possible embodiments.

[0117] In a tenth aspect, embodiments of this disclosure provide a communication device. The communication device includes one or more processors. The communication device is used to perform the communication method as described in any one of the third aspects and their possible implementations.

[0118] In an eleventh aspect, this disclosure provides a communication system. The communication system includes a first network element, a second network element, and a first device. The first network element is used to implement the communication method as described in any of the first aspect and its possible embodiments. The second network element is used to implement the communication method as described in any of the second aspect and its possible embodiments. The first device is used to implement the communication method as described in any of the third aspect and its possible embodiments.

[0119] In a twelfth 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 fourth aspects and their possible embodiments.

[0120] In a thirteenth 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 fourth aspects and their possible embodiments.

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

[0122] In a fifteenth 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 the communication methods described in any of the first to fourth aspects and their possible embodiments.

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

[0124] This disclosure provides a communication method, network element, device, communication system, storage medium, and computer program product. In some embodiments, terms such as communication method, information processing method, and information interaction method can be used interchangeably; terms such as network element, device, communication apparatus, information processing apparatus, and communication equipment can be used interchangeably; and terms such as information processing system and communication system can be used interchangeably.

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

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

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

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

[0129] In the embodiments disclosed herein, "multiple" refers to two or more.

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

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

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

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

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

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

[0136] 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”.

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

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

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

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

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

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

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

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

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

[0146] 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 first device 101 and a core network 102.

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

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

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

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

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

[0152] In some embodiments, the core network 102 may be a single device, including a first network element 1021, a second network element 1022, a third network element 1023, a fourth network element 1024, etc., or it may be multiple devices or a group of devices, each including all or part of the first network element 1021, the second network element 1022, the third network element 1023, the fourth network element 1024, 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).

[0153] In some embodiments, the first network element 1021 may be, for example, a control plane (CP) network function (NF).

[0154] In some embodiments, the first network element 1021 may be, for example, a session management function (SMF).

[0155] In some embodiments, the first network element 1021 can be used for functions such as session management, execution of PCF-issued control policies, selection of UPF, and allocation of UE IP addresses, and its name is not limited to these.

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

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

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

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

[0160] In some embodiments, the third network element 1023 may be, for example, a policy control function (PCF).

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

[0162] In some embodiments, the third network element 1023 may be, for example, an access and mobility management function (AMF).

[0163] In some embodiments, the third network element 1023 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.

[0164] In some embodiments, the fourth network element 1024 may be, for example, a user plane network function.

[0165] In some embodiments, the fourth network element 1024 may be, for example, an application server (AS).

[0166] In some embodiments, the fourth network element 1024 may be used to provide support for user-subscribed services, and its name is not limited thereto.

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

[0168] In some embodiments, one or more of the first network element 1021, the second network element 1022, the third network element 1023, and the fourth network element 1024 in the communication system 100 may also be data plane network elements.

[0169] Figures 1B and 1C illustrate the architecture of a communication system using a 5G communication system as an example.

[0170] Figure 1B is a schematic diagram of one implementation of the system architecture 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.

[0171] 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 RAN.

[0172] It should be noted that NEF is not shown in Figure 1B. However, all core network devices in the communication system can interact with NEF.

[0173] Figure 1C is a schematic diagram of another implementation of the system architecture 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.

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

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

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

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

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

[0179] In further scenarios, XRM services 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 consistency in QoS authorization and execution between multiple XRM data streams from a single terminal and XRM data streams from multiple terminals.

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

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

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

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

[0184] In some embodiments, the RAN can perform further QoS processing based on the QoS features and protocol descriptions provided by 5GC and AF, as well as the enhanced headers identified and marked by UPF.

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

[0186] 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 object's position in space. Orientation information can be used to indicate the object's orientation in space.

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

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

[0189] 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 S2112.

[0190] In step S2101, the third network element 1023 sends third information to the second network element 1022.

[0191] In some embodiments, the second network element 1022 may receive third information.

[0192] In some embodiments, third information may be used to determine whether to mark the first data stream of the first service.

[0193] In some embodiments, the first data flow may be a service-oriented data flow. In some embodiments, the first data flow may be a service data flow (SDF).

[0194] It should be noted that in some cases, the first data stream may be a data stream not specific to any particular service. In some embodiments, the first data stream may be a data stream transmitted on the data plane (DP). In one example, the first data stream may be a data stream transmitted on a data plane proposed in any network (e.g., a 6G network). The first data stream transmitted on the data plane may be unrelated to any specific service.

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

[0196] In some embodiments, third information may be used to indicate that a first data stream of a first service needs to be marked.

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

[0198] In some embodiments, the third information may include at least one of the following: QoS requirements and QoS rules.

[0199] In some embodiments, the third information may include at least one of the following: QoS requirements and QoS rules.

[0200] In some embodiments, QoS requirements can be used to indicate the mapping requirements of a first data stream of a first service.

[0201] In some embodiments, QoS rules can be used to indicate the mapping strategy for the first data stream of the first service.

[0202] In some embodiments, third information may be carried in the first message. In some embodiments, the third network element 1023 may send the first message to the second network element 1022. The first message may include the first information.

[0203] In some embodiments, the third network element 1023 may be an AMF. In some embodiments, the first message may be an Nsmf_PDUSession_UpdateSMContext request message.

[0204] In some embodiments, the third network element 1023 may be a PCF. In some embodiments, the first message may be an Npcf_SMPolicyControl_UpdateNotify request message.

[0205] In step S2102, the second network element 1022 sends the first information to the first network element 1021.

[0206] In some embodiments, the first network element 1021 may receive first information.

[0207] In some embodiments, the first information may be used to trigger the marking process of the first data stream of the first service.

[0208] In some embodiments, the first information can be used to configure the first network element 1021 to perform marking processing on the first data stream. In some embodiments, the first information can be used to activate the first network element 1021 to perform marking processing on the first data stream.

[0209] In some embodiments, the name of the first information is not limited, and it may be, for example, trigger information, configuration information, activation information, etc.

[0210] In some embodiments, the first information may include at least one of the following: instruction information and protocol description information.

[0211] In some embodiments, the indication information can be used to instruct the first data stream to undergo marking processing. In some embodiments, the indication information can be used to instruct the first data stream to undergo marking processing. In some embodiments, the indication information can be used to instruct the data packets of the first data stream to be marked based on pose information. In some embodiments, the indication information can cause the first network element 1021 to perform marking processing on the first data stream.

[0212] In some embodiments, the indication information may be included in the QoS rule associated with the first data stream of the first service. In one example, a field for the indication information may be set in the QoS rule associated with the first data stream of the first service.

[0213] In some embodiments, the QoS rules associated with the data flow of the first service may include QER. In some embodiments, QER may be a rule based on the PFCP (packet forwarding control policy) protocol and may be used to implement and manage QoS. QER can be used to achieve fine-grained control and management of the data flow.

[0214] In some embodiments, the QER may have specific fields for containing indication information. In one example, the indication information may be referred to as pose information marker indication.

[0215] In some embodiments, QER may include at least one of the following: N4 session identification information, rule identification information, QoS flow identification information, and indication information.

[0216] In some embodiments, N4 session identification information can be used to identify an N4 session associated with a QER. In one example, N4 session identification information may include an N4 session identifier.

[0217] In some embodiments, the first information can be sent through the N4 session establishment process or the N4 session modification process. In some embodiments, during the N4 session establishment process or the N4 session modification process, the second network element 1022 can send a QER to the first network element 1021, and the QER can carry the first information. In this case, the N4 session targeted by the N4 session establishment process or the N4 session modification process can be identified by the N4 session identification information in the QER.

[0218] In some embodiments, rule identification information may be used to identify QERs. In one example, rule identification information may include a QER identifier.

[0219] In some embodiments, QoS flow identification information can be used to identify QoS flows. In some embodiments, QoS flow identification information can be inserted into the header of a data packet. Here, the operation of inserting QoS flow identification information into the header of a data packet implements the mapping from data flow to QoS flow.

[0220] In some embodiments, QoS flow identification information may include a QoS flow identifier (QFI).

[0221] It is understood that QER may also contain other information, and this disclosure does not specifically limit this.

[0222] In some embodiments, protocol description information may be used to indicate the protocol characteristics of the transport protocol associated with the first data stream of the first service. In some embodiments, protocol description information may be used to describe the transport protocol of the first data stream.

[0223] In some embodiments, the transport protocol of the first data stream may include at least one of the following: RTP, SRTP.

[0224] In some embodiments, protocol features may include at least one of the following: having an RTP extended header and having an RTP payload format.

[0225] In some embodiments, the protocol description information may indicate that the first data stream uses the RTP protocol and has an RTP extended header. In one example, the protocol description information may indicate that the first data stream uses the RTP protocol and has an RTP extended header for pose information marking. In some embodiments, the protocol description information may indicate that the first data stream uses the RTP protocol and has an RTP static payload format. In one example, the protocol description information may indicate that the first data stream uses the RTP protocol, does not have an RTP extended header, but has an RTP static payload format. In one example, the protocol description information may indicate that the first data stream uses the RTP protocol, has an RTP extended header, and has an RTP static payload format.

[0226] In some embodiments, the protocol description information may indicate that the first data stream uses the SRTP protocol and has an RTP extended header. In one example, the protocol description information may indicate that the first data stream uses the SRTP protocol and has an RTP extended header for pose information marking. In some embodiments, the protocol description information may indicate that the first data stream uses the SRTP protocol and has an RTP static payload format. In one example, the protocol description information may indicate that the first data stream uses the SRTP protocol, does not have an RTP extended header, but has an RTP static payload format. In one example, the protocol description information may indicate that the first data stream uses the SRTP protocol, has an RTP extended header, and has an RTP static payload format.

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

[0228] In some embodiments, the first information may be included in the second message. In some embodiments, the second network element 1022 may send the second message to the first network element 1021. The second message may carry the first information.

[0229] In some embodiments, the first information may be determined based on the third information. In some embodiments, some or all of the content of the first information may be included in the third information. In some embodiments, the second network element 1022 may include information obtained from the third information in the first information.

[0230] In some embodiments, the second message can be used to trigger the establishment of a new PDU session.

[0231] In some embodiments, the second message can be used to trigger modification of an already established PDU session.

[0232] In some embodiments, the second network element 1022 can send first information to the first network element 1021 through an N4 Association Setup process. In some embodiments, the second message can be an N4 Association Setup request message. In some embodiments, the second network element 1022 can send an N4 Association Setup request message to the first network element 1021. This N4 Association Setup request message can carry the first information.

[0233] In some embodiments, the second network element 1022 may send first information to the first network element 1021 through an N4 Session Establishment procedure. In some embodiments, the second message may be an N4 Session Establishment Request message. In some embodiments, the second network element 1022 may send an N4 Session Establishment Request message to the first network element 1021. This N4 Session Establishment Request message may carry the first information.

[0234] In some embodiments, the second network element 1022 can send first information to the first network element 1021 through an N4 Session Modification procedure. In some embodiments, the second message can be an N4 Session Modification Request message. In some embodiments, the second network element 1022 can send an N4 Session Modification Request message to the first network element 1021. This N4 Session Modification Request message can carry the first information.

[0235] In step S2103, the first network element 1021 sends a third message to the second network element 1022.

[0236] In some embodiments, the second network element 1022 may receive a third message.

[0237] In some embodiments, the first network element 1021 may send a third message in response to the received second message.

[0238] In some embodiments, the third message may be a response message to the second message. In some embodiments, if the second message is an N4 association establishment request message, the third message may be an N4 association establishment response message. In some embodiments, if the second message is an N4 session establishment request message, the third message may be an N4 session establishment response message. In some embodiments, if the second message is an N4 session modification request message, the third message may be an N4 session modification response message.

[0239] In some embodiments, the third message may include an indication that the first network element 1021 has received the first information. In one example, the indication may indicate that the first network element 1021 has received the first information. In another example, the indication may indicate that the first network element 1021 has not received the first information.

[0240] In some embodiments, the third message may include configuration result information of the first network element 1021 based on the first information. In one example, the result information may indicate successful configuration. In another example, the result information may indicate configuration failure. In yet another example, the result information may include configuration parameter values ​​of the first network element 1021 based on the first information.

[0241] It is understood that the third message may include any information that the first network element 1021 needs to send to the second network element 1022, and this disclosure does not specifically limit this.

[0242] In step S2104, the second network element 1022 sends a fourth message to the third network element 1023.

[0243] In some embodiments, the third network element 1023 may receive a fourth message.

[0244] In some embodiments, the second network element 1022 may send a fourth message upon receiving a third message. In some embodiments, the second network element 1022 may determine to send a fourth message to the third network element 1023 based on the received third message.

[0245] In some embodiments, the fourth message may be a response message to the first message. In some embodiments, where the first message is an Nsmf_PDUSession_UpdateSMContext request message, the fourth message may be an Nsmf_PDUSession_UpdateSMContext response message. In some embodiments, where the first message is an Npcf_SMPolicyControl_UpdateNotify request message, the fourth message may be an Npcf_SMPolicyControl_UpdateNotify response message.

[0246] In some embodiments, the fourth message may include result information of the second network element 1022 configuring the first network element 1021. In one example, the result information may indicate that the second network element 1022 successfully configured the first information for the first network element 1021. In another example, the result information may indicate that the second network element 1022 failed to configure the first information for the first network element 1021.

[0247] It is understood that the fourth message may include any information that the second network element 1022 needs to send to the third network element 1023, and this disclosure does not specifically limit this.

[0248] In step S2105, the fourth network element 1024 sends the first data stream to the first network element 1021.

[0249] In some embodiments, the first network element 1021 may receive a first data stream.

[0250] In some embodiments, the first data stream may be a downlink data stream of a first service.

[0251] In some embodiments, the first data stream may be transmitted using a specific transport protocol. In one example, the transport protocol may include at least one of the following: RTP, SRTP. In one example, the protocol characteristics of the transport protocol may include at least one of the following: having an RTP extended header, having an RTP payload format.

[0252] In some embodiments, the first data stream may employ the RTP protocol and have an RTP extended header. In one example, the first data stream may employ the RTP protocol and have an RTP extended header for pose information marking. In some embodiments, the first data stream may employ the RTP protocol and have an RTP static payload format. In one example, the first data stream may employ the RTP protocol without an RTP extended header, but has an RTP static payload format. In one example, the first data stream may employ the RTP protocol, have an RTP extended header, and have an RTP static payload format.

[0253] In some embodiments, the first data stream may employ the SRTP protocol and have an RTP extended header. In one example, the first data stream may employ the SRTP protocol and have an RTP extended header for pose information marking. In some embodiments, the first data stream may employ the SRTP protocol and have an RTP static payload format. In one example, the first data stream may employ the SRTP protocol without an RTP extended header, but has an RTP static payload format. In one example, the first data stream may employ the SRTP protocol, have an RTP extended header, and have an RTP static payload format.

[0254] It should be noted that the above transmission protocols and characteristics can be combined arbitrarily, and the embodiments disclosed herein do not impose specific limitations on them. In some embodiments, at least one stream in the first data stream may employ the RTP protocol, and at least one stream may employ the SRTP protocol. In some embodiments, at least one stream in the first data stream may have an RTP extended header, and at least one stream may have an RTP payload format.

[0255] It is understood that the transmission of the first data stream can employ any transmission protocol applicable to XRM services and interactive media services, and this disclosure does not specifically limit this. In some embodiments, the transmission protocol used for the transmission of the first data stream can be indicated by protocol description information.

[0256] In some embodiments, pose information may be carried in packets of the first data stream. In some embodiments, pose information may be carried in the enhanced header of packets of the first data stream. In some embodiments, pose information may be carried in the feature fields of packets of the first data stream. For example, pose information may be carried in the payload type field of packets of the first data stream.

[0257] In some embodiments, the first data stream of the first service can be sent from the fourth network element 1024 to the first network element 1021 on the user plane.

[0258] In some embodiments, the first data stream of the first service can be sent from the fourth network element 1024 to the first network element 1021 on the data plane.

[0259] In some embodiments, the first data stream of the first service can be sent from the fourth network element 1024 to the first network element 1021 via the N6 reference point.

[0260] In some embodiments, when the first service data stream is transmitted between the home public land mobile network (HPLMN) and the visited public land mobile network (VPLMN), the first data stream can be transmitted between the first network element 1021 in the HPLMN and the first network element 1021 in the VPLMN via the N9 reference point.

[0261] In step S2106, the first network element 1021 performs the marking process.

[0262] In some embodiments, the first network element 1021 can mark the first data stream based on the first information. In some embodiments, after receiving the first information, the first network element 1021 can determine to mark the first data stream of the first service. Subsequently, after receiving the first data stream, the first network element 1021 can mark the first data stream.

[0263] In some embodiments, the first network element 1021 can identify and detect the first data stream of the first service. Through identification and detection, the first network element 1021 can obtain the pose information carried in the data packets of the first data stream.

[0264] In some embodiments, pose information may be associated with a first service.

[0265] In some embodiments, pose information may include at least one of the following: type information, parameter information, time information, motion information, flow information, and priority information.

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

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

[0268] In some embodiments, 3DoF may include direction. In one example, direction may be represented in rx, ry, rz, rw dimensions. It is understood that 3DoF may not include position.

[0269] In some embodiments, the parameter information may include at least one of the following: position-related parameter values ​​and direction-related parameter values.

[0270] In some embodiments, position-related parameters may include x, y, and z. In some embodiments, position-related parameter values ​​may include x-axis coordinates, y-axis coordinates, and z-axis coordinates.

[0271] In some embodiments, direction-related parameters may include rx, ry, rz, and rw. In some embodiments, position-related parameter values ​​may include rx-axis coordinates, ry-axis coordinates, rz-axis coordinates, and rw-axis coordinates.

[0272] In some embodiments, when the type information indicates that the pose type is 6DoF, the parameter information may include position-related parameter values ​​and orientation-related parameter values.

[0273] In some embodiments, when the type information indicates that the pose type is 6DoF, the parameter information may include only orientation-related parameter values.

[0274] In some embodiments, time information can be used to indicate the time corresponding to a pose. In one example, the time information can indicate the time when the pose occurred. In some embodiments, the time information can indicate absolute time. For example, the time indicated by the time information can be the same as the time of day for a geographic region. In some embodiments, the time information can indicate relative time. For example, the time indicated by the time information can be an offset relative to a reference time.

[0275] In some embodiments, the time information can be a timestamp. For example, the timestamp can correspond to a pose.

[0276] In some embodiments, motion information can be used to indicate pose-related actions. In some embodiments, pose can be associated with one or more actions. Motion information can indicate one or more actions associated with pose.

[0277] In some embodiments, motion information may include one or more motion identifiers. Motion identifiers can be used to uniquely identify a motion. In other words, different motion identifiers can correspond to different motions. In some embodiments, each motion may be associated with one or more of the pose parameters x, y, z, rx, ry, rz, and rw.

[0278] In some embodiments, action information may include a list of actions. Action identifiers may be included in the action list.

[0279] In some embodiments, flow information can be used to indicate a flow associated with a pose. In some embodiments, a pose can be associated with one or more flows. In one example, at least one flow can correspond to the same pose.

[0280] In some embodiments, the stream associated with a pose may be a media stream. In one example, the media type of the media stream associated with a pose may include: video, audio, or haptic. For example, one or more streams associated with a pose may include at least one of the following: video stream, audio stream, or haptic stream.

[0281] In some embodiments, streaming information may include a list of media streams. This list may include one or more media stream identifiers. These media stream identifiers can be used to identify all media streams corresponding to the same pose. In one example, streaming information may include identifier information for all media streams corresponding to the same pose. In another example, since pose information may be carried in one of multiple media streams, the streaming information may include identifier information for all other media streams corresponding to the same pose, excluding the media stream containing the pose information.

[0282] In some embodiments, priority information can be used to indicate a pose-related priority.

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

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

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

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

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

[0288] In some embodiments, protocol priority can be used to indicate the priority between different transport protocols. In one example, protocol priority can be used to indicate the priority between RTP and SRTP.

[0289] In some embodiments, the marking process of the first network element 1021 on the first data stream can be implemented by adding pose information to the header of the data packets of the first data stream.

[0290] In some embodiments, pose information may be added to the extended header or encapsulation header of the packets in the first data stream. In one example, pose information may be added to the GPRS Tunnelling Protocol for the user plane (GTP-U) header at the user layer.

[0291] In some embodiments, the pose information in the header of the data packet added to the first data stream can be used to distinguish between data packets carrying pose information and data packets not carrying pose information.

[0292] In some embodiments, the pose information in the header of the data packets added to the first data stream can be used to distinguish between data packets carrying different pose information.

[0293] In step S2107, the first network element 1021 sends a first data stream to the first device 101.

[0294] In some embodiments, after marking the first data stream, the first network element 1021 can send the first data stream to the first device 101.

[0295] In some embodiments, the first data stream sent by the first network element 1021 to the first device 101 may be a first data stream that has undergone tagging. In some embodiments, the header of the data packets of the tagged first data stream may carry pose information.

[0296] It is understandable that the first data stream that has not undergone labeling can also be called the unlabeled first data stream, and the first data stream that has undergone labeling can also be called the labeled first data stream.

[0297] In some embodiments, the first data stream of the first service can be sent from the first network element 1021 to the first device 101 on the user plane.

[0298] In some embodiments, the first data stream of the first service can be sent from the first network element 1021 to the first device 101 on the data plane.

[0299] In some embodiments, the first data stream of the first service can be sent from the first network element 1021 to the first device 101 via the N3 reference point.

[0300] In some embodiments, the first network element 1021 may carry information related to the PDU set in the GTP-U header.

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

[0302] In step S2108, the first device 101 performs QoS processing.

[0303] In some embodiments, the first device 101 may perform QoS processing on the first data stream of the received first service.

[0304] In some embodiments, step S2108 may include determining QoS parameters based on the first data stream that has been tagged. In some embodiments, after the first device 101 obtains the first data stream that has been tagged, the first device 101 may determine the QoS parameters based on the first data stream that has been tagged. In some embodiments, the QoS parameters may be used to implement QoS processing for the first data stream.

[0305] In some embodiments, step S2108 may include: determining QoS parameters based on pose information.

[0306] In some embodiments, the first device 101 can obtain pose information from the header of a data packet of the first data stream of the first service received. Then, the first device 101 can adjust and / or manage the QoS parameters related to the first data stream of the first service in the first device 101, taking the pose information into account.

[0307] In some embodiments, the first device 101 may use determined QoS parameters to perform QoS processing on the first data stream.

[0308] In some embodiments, the first data stream may be sent by the first device 101 to a terminal (not shown).

[0309] In step S2109, the third network element 1023 sends the fourth information to the second network element 1022.

[0310] In some embodiments, the second network element 1022 may receive fourth information.

[0311] In some embodiments, the fourth information may be used to determine to stop marking the first data stream of the first service.

[0312] In some embodiments, the fourth information may be used to indicate that the first data stream of the first service no longer needs to be marked.

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

[0314] In some embodiments, the fourth information may be carried in the fifth message. In some embodiments, the third network element 1023 may send the fifth message to the second network element 1022. The fifth message may include the fourth information.

[0315] In some embodiments, the third network element 1023 may be an AMF. In some embodiments, the fifth message may be an Nsmf_PDUSession_UpdateSMContext request message.

[0316] In some embodiments, the third network element 1023 may be a PCF. In some embodiments, the fifth message may be an Npcf_SMPolicyControl_UpdateNotify request message.

[0317] In step S2110, the second network element 1022 sends the second information to the first network element 1021.

[0318] In some embodiments, the first network element 1021 receives the second information.

[0319] In some embodiments, the second information may be used to stop the marking process of the first data stream.

[0320] In some embodiments, the second information may indicate that the first data stream of the first service should no longer be marked.

[0321] In some embodiments, the name of the second information is not limited, and it may be, for example, configuration information, deactivation information, termination information, stop instruction information, etc.

[0322] In some embodiments, the second information can be used to indicate that the marking process for the first data stream should be stopped. In some embodiments, the second information can be used to indicate that the marking process for the first data stream is not required. In some embodiments, the second information can be used to indicate that the packets of the first data stream should no longer be marked based on pose information. In some embodiments, the second information can cause the first network element 1021 to stop marking the first data stream.

[0323] In some embodiments, the second information may be included in the sixth message. In some embodiments, the second network element 1022 may send the sixth message to the first network element 1021. The sixth message may carry the second information.

[0324] In some embodiments, the second information may be determined based on the fourth information. In one example, upon receiving the fourth information, the second network element 1022 may determine to send the second information.

[0325] In some embodiments, the sixth message may include a QER. In some embodiments, the QER may include second information.

[0326] In some embodiments, the second information can be implemented by removing the indication information from the QER. In some embodiments, the second information may include a QER with the indication information removed.

[0327] In some embodiments, the sixth message can be used to trigger the establishment of a new PDU session.

[0328] In some embodiments, the sixth message can be used to trigger modification of an already established PDU session.

[0329] In some embodiments, the second network element 1022 can send second information to the first network element 1021 through the N4 association establishment process.

[0330] In some embodiments, the second network element 1022 may send second information to the first network element 1021 through the N4 session establishment process.

[0331] In some embodiments, the second network element 1022 may send first information to the first network element 1021 through the N4 session modification process.

[0332] In some embodiments, the second information may enable the first network element 1021 to determine not to perform marking processing. In some embodiments, the second information may enable the first network element 1021 to stop marking processing of the first data stream of the first service. In some embodiments, the first network element 1021 may, based on the second information, determine that data packets of the first data stream of the first service received in the future will no longer be marked.

[0333] In step S2111, the first network element 1021 sends a seventh message to the second network element 1022.

[0334] In some embodiments, the second network element 1022 may receive a seventh message.

[0335] In some embodiments, the first network element 1021 may send a seventh message in response to the received sixth message.

[0336] In some embodiments, the seventh message may be a response message to the sixth message. In some embodiments, if the sixth message is an N4 association establishment request message, the seventh message may be an N4 association establishment response message. In some embodiments, if the sixth message is an N4 session establishment request message, the seventh message may be an N4 session establishment response message. In some embodiments, if the sixth message is an N4 session modification request message, the seventh message may be an N4 session modification response message.

[0337] In some embodiments, the seventh message may include an indication that the first network element 1021 has received the second information. In one example, the indication may indicate that the first network element 1021 has received the second information. In another example, the indication may indicate that the first network element 1021 has not received the second information.

[0338] In some embodiments, the seventh message may include configuration result information of the first network element 1021 based on the second information. In one example, the result information may indicate successful configuration. In another example, the result information may indicate configuration failure. In yet another example, the result information may include configuration parameter values ​​of the first network element 1021 based on the second information.

[0339] It is understood that the seventh message may include any information that the first network element 1021 needs to send to the second network element 1022, and this disclosure does not specifically limit this.

[0340] In step S2112, the second network element 1022 sends the eighth message to the third network element 1023.

[0341] In some embodiments, the third network element 1023 may receive the eighth message.

[0342] In some embodiments, the second network element 1022 may send an eighth message upon receiving the seventh message. In some embodiments, the second network element 1022 may determine to send the eighth message to the third network element 1023 based on the received seventh message.

[0343] In some embodiments, the eighth message may be a response message to the fifth message. In some embodiments, where the fifth message is an Nsmf_PDUSession_UpdateSMContext request message, the eighth message may be an Nsmf_PDUSession_UpdateSMContext response message. In some embodiments, where the fifth message is an Npcf_SMPolicyControl_UpdateNotify request message, the eighth message may be an Npcf_SMPolicyControl_UpdateNotify response message.

[0344] In some embodiments, the eighth message may include result information of the second network element 1022 configuring the first network element 1021. In one example, the result information may indicate that the second network element 1022 successfully configured the second information for the first network element 1021. In another example, the result information may indicate that the second network element 1022 failed to configure the second information for the first network element 1021.

[0345] It is understood that the eighth message may include any information that the second network element 1022 needs to send to the third network element 1023, and this disclosure does not specifically limit this.

[0346] The communication method of this embodiment can be implemented through steps S2101 to S2112.

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

[0348] In some embodiments, at least two of steps S2101 to S2112 may be executed in an interchangeable order or simultaneously. For example, steps S2103 and S2105 may be executed in an interchangeable order or simultaneously. For example, steps S2103 and S2106 may be executed in an interchangeable order or simultaneously. For example, steps S2108 and S2109 may be executed in an interchangeable order or simultaneously.

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

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

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

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

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

[0354] 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 S2208.

[0355] In step S2201, the first network element 1021 sends the fifth information to the second network element 1022.

[0356] In some embodiments, the second network element 1022 may receive the fifth information.

[0357] In some embodiments, the fifth information may be used to request the first information from the second network element 1022.

[0358] In some embodiments, the name of the fifth piece of information is not limited; for example, it may be rule request information, rule query information, etc.

[0359] In some embodiments, the interface between the second network element 1022 and the first network element 1021 can be an N4 interface. In other words, the first network element 1021 and the second network element 1022 can interact through the N4 interface. In some embodiments, the fifth information can be sent from the first network element 1021 to the second network element 1022 through the N4 interface. In other words, the fifth information can be received by the second network element 1022 through the N4 interface.

[0360] In some embodiments, the first network element 1021 may send fifth information to the second network element 1022 through the N4 association establishment process. In some embodiments, the first network element 1021 may send an N4 association establishment request message to the second network element 1022. This N4 association establishment request message may carry the fifth information.

[0361] In step S2202, the second network element 1022 sends the first information to the first network element 1021.

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

[0363] In some embodiments, the first information may be carried in the N4 association establishment response message.

[0364] In step S2203, the fourth network element 1024 sends the first data stream to the first network element 1021.

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

[0366] In step S2204, the first network element 1021 performs the marking process.

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

[0368] In step S2205, the first network element 1021 sends a first data stream to the first device 101.

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

[0370] In step S2206, the first device 101 performs QoS processing.

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

[0372] In step S2207, the first network element 1021 sends the sixth information to the second network element 1022.

[0373] In some embodiments, the second network element 1022 may receive the sixth information.

[0374] In some embodiments, the sixth information may be used to request the second information from the second network element 1022.

[0375] In some embodiments, the name of the sixth piece of information is not limited; for example, it may be rule request information, rule query information, etc.

[0376] In some embodiments, the interface between the second network element 1022 and the first network element 1021 can be an N4 interface. In other words, the first network element 1021 and the second network element 1022 can interact through the N4 interface. In some embodiments, the sixth information can be sent from the first network element 1021 to the second network element 1022 through the N4 interface. In other words, the sixth information can be received by the second network element 1022 through the N4 interface.

[0377] In some embodiments, the first network element 1021 may send sixth information to the second network element 1022 through the N4 association establishment process. In some embodiments, the first network element 1021 may send an N4 association establishment request message to the second network element 1022. This N4 association establishment request message may carry the sixth information.

[0378] In step S2208, the second network element 1022 sends the second information to the first network element 1021.

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

[0380] In some embodiments, the second information may be carried in the N4 association establishment response message.

[0381] The communication method of this embodiment can be implemented through steps S2201 to S2208.

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

[0383] In some embodiments, at least two of steps S2201 to S2208 may be executed in an alternate order or simultaneously. For example, steps S2206 and S2207 may be executed in an alternate order or simultaneously.

[0384] In some embodiments, steps S2201, S2203, S2204, S2205, S2206, S2207, and S2208 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0385] In some embodiments, steps S2201, S2202, S2203, S2205, S2206, S2207, and S2208 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

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

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

[0389] It should be noted that the implementation details of the embodiments described with reference to Figures 2A and 2B can be combined arbitrarily. In some embodiments, the manner in which the first information is indicated in the embodiment of Figure 2A can be combined with the manner in which the second information is indicated in the embodiment of Figure 2B. In one example, the first information can be determined based on the third information and sent to the first network element 1021, and the second information can be determined based on the sixth information and sent to the first network element 1021. In some embodiments, the manner in which the second information is indicated in the embodiment of Figure 2A can be combined with the manner in which the first information is indicated in the embodiment of Figure 2B. In one example, the first information can be determined based on the fifth information and sent to the first network element 1021, and the second information can be determined based on the sixth information and sent to the first network element 1021.

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

[0391] 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".

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

[0393] 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.”

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

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

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

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

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

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

[0400] 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 1021. As shown in Figure 3A, the method includes steps S3101 to S3107.

[0401] In step S3101, first information is obtained.

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

[0403] In some embodiments, the first network element 1021 may receive first information sent by the second network element 1022, but is not limited thereto, and may also receive first information sent by other entities.

[0404] In step S3102, a third message is sent.

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

[0406] In some embodiments, the first network element 1021 may send a third message to the second network element 1022, but is not limited thereto; it may also send a third message to other entities.

[0407] In step S3103, the first data stream is acquired.

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

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

[0410] In step S3104, marking processing is performed.

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

[0412] In some embodiments, the first network element 1021 may mark the first data stream according to the first information.

[0413] In step S3105, the first data stream is sent.

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

[0415] In some embodiments, the first network element 1021 may send a first data stream to the first device 101, but is not limited thereto, and may also send a first data stream to other entities.

[0416] In step S3106, the second information is obtained.

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

[0418] In some embodiments, the first network element 1021 may receive second information sent by the second network element 1022, but is not limited thereto, and may also receive second information sent by other entities.

[0419] In step S3107, the seventh message is sent.

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

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

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

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

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

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

[0426] 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 1021. As shown in Figure 3B, the method includes steps S3201 to S3207.

[0427] In step S3201, the fifth message is sent.

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

[0429] In some embodiments, the first network element 1021 may send the fifth information to the second network element 1022, but is not limited thereto, and may also send the fifth information to other entities.

[0430] In step S3202, the first information is obtained.

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

[0432] In some embodiments, the first network element 1021 may receive first information sent by the second network element 1022, but is not limited thereto, and may also receive first information sent by other entities.

[0433] In step S3203, the first data stream is acquired.

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

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

[0436] In step S3204, the marking process is performed.

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

[0438] In some embodiments, the first network element 1021 may mark the first data stream according to the first information.

[0439] In step S3205, the first data stream is sent.

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

[0441] In some embodiments, the first network element 1021 may send a first data stream to the first device 101, but is not limited thereto, and may also send a first data stream to other entities.

[0442] In step S3206, the sixth message is sent.

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

[0444] In some embodiments, the first network element 1021 may send the sixth information to the second network element 1022, but is not limited thereto, and may also send the sixth information to other entities.

[0445] In step S3207, the second information is obtained.

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

[0447] In some embodiments, the first network element 1021 may receive second information sent by the second network element 1022, but is not limited thereto, and may also receive second information sent by other entities.

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

[0449] In some embodiments, steps S3201, S3203, S3204, S3205, S3206, and S3207 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0450] In some embodiments, steps S3201, S3202, S3203, S3205, S3206, and S3207 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0451] In some embodiments, steps S3201, S3202, S3203, S3204, S3206, and S3207 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0452] 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 1022. As shown in Figure 4A, the method includes steps S4101 to S4108.

[0453] In step S4101, third information is obtained.

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

[0455] In some embodiments, the second network element 1022 may receive third information sent by the third network element 1023, but is not limited thereto, and may also receive third information sent by other entities.

[0456] In some embodiments, the second network element 1022 may obtain third information as specified in the protocol.

[0457] In some embodiments, the second network element 1022 can obtain third information from the upper layer.

[0458] In some embodiments, the second network element 1022 can perform processing to obtain third information.

[0459] In some embodiments, step S4101 may be omitted, and the second network element 1022 may autonomously implement the function indicated by the third information, or the above function may be defaulted or set to default.

[0460] In step S4102, the first information is sent.

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

[0462] In some embodiments, the second network element 1022 may send first information to the first network element 1021, but is not limited thereto, and may also send first information to other entities.

[0463] In step S4103, the third message is obtained.

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

[0465] In some embodiments, the second network element 1022 may receive a third message sent by the first network element 1021, but is not limited thereto, and may also receive a third message sent by other entities.

[0466] In step S4104, the fourth message is sent.

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

[0468] In some embodiments, the second network element 1022 may send a fourth message to the third network element 1023, but is not limited thereto; it may also send a fourth message to other entities.

[0469] In step S4105, the fourth information is obtained.

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

[0471] In some embodiments, the second network element 1022 may receive fourth information sent by the third network element 1023, but is not limited thereto, and may also receive fourth information sent by other entities.

[0472] In some embodiments, the second network element 1022 may obtain fourth information as specified in the protocol.

[0473] In some embodiments, the second network element 1022 can obtain fourth information from a higher layer.

[0474] In some embodiments, the second network element 1022 can perform processing to obtain the fourth information.

[0475] In some embodiments, step S4105 may be omitted, and the second network element 1022 may autonomously implement the function indicated by the fourth information, or the above function may be defaulted or set to default.

[0476] In step S4106, the second information is sent.

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

[0478] In some embodiments, the second network element 1022 may send second information to the first network element 1021, but is not limited thereto, and may also send second information to other entities.

[0479] In step S4107, the seventh message is obtained.

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

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

[0482] In step S4108, the eighth message is sent.

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

[0484] In some embodiments, the second network element 1022 may send an eighth message to the third network element 1023, but is not limited thereto; it may also send an eighth message to other entities.

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

[0486] In some embodiments, steps S4101, S4103, S4104, S4105, S4106, S4107, and S4108 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0487] 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 1022. As shown in Figure 4B, the method includes steps S4201 to S4204.

[0488] In step S4201, the fifth piece of information is obtained.

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

[0490] In some embodiments, the second network element 1022 may receive the fifth information sent by the first network element 1021, but is not limited thereto, and may also receive the fifth information sent by other entities.

[0491] In some embodiments, the second network element 1022 may obtain the fifth information specified by the protocol.

[0492] In some embodiments, the second network element 1022 can obtain the fifth information from the higher layer.

[0493] In some embodiments, the second network element 1022 can perform processing to obtain the fifth information.

[0494] In some embodiments, step S4201 may be omitted, and the second network element 1022 may autonomously implement the function indicated by the fifth information, or the above function may be defaulted or set to default.

[0495] In step S4202, the first message is sent.

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

[0497] In some embodiments, the second network element 1022 may send first information to the first network element 1021, but is not limited thereto, and may also send first information to other entities.

[0498] In step S4203, the sixth information is obtained.

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

[0500] In some embodiments, the second network element 1022 may receive the sixth information sent by the first network element 1021, but is not limited thereto, and may also receive the sixth information sent by other entities.

[0501] In some embodiments, the second network element 1022 can obtain the sixth information specified by the protocol.

[0502] In some embodiments, the second network element 1022 can obtain sixth information from a higher layer.

[0503] In some embodiments, the second network element 1022 can perform processing to obtain the sixth information.

[0504] In some embodiments, step S4203 may be omitted, and the second network element 1022 may autonomously implement the function indicated by the sixth information, or the above function may be defaulted or omitted.

[0505] In step S4204, the second information is sent.

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

[0507] In some embodiments, the second network element 1022 may send second information to the first network element 1021, but is not limited thereto, and may also send second information to other entities.

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

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

[0510] Figure 5 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 101. As shown in Figure 5, the method includes steps S501 to S502.

[0511] In step S501, the first data stream is acquired.

[0512] The optional implementations of step S501 can be found in the optional implementations of step S2107 in Figure 2A and step S2205 in Figure 2B, as well as other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

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

[0514] In step S502, QoS processing is performed.

[0515] The optional implementations of step S502 can be found in the optional implementations of step S2108 in Figure 2A and step S2206 in Figure 2B, as well as other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0516] In some embodiments, QoS processing may take into account pose information in the header of packets of the first data stream.

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

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

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

[0520] Figure 6A is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 6A, the present disclosure relates to a communication method. The communication method includes steps S6101 and S6102.

[0521] In step S6101, the second network element 1022 sends the first information to the first network element 1021.

[0522] The optional implementations of step S6101 can be found in the optional implementations of step S2102 in Figure 2A and step S2202 in Figure 2B, as well as other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0523] In step S6102, the first network element 1021 performs the marking process.

[0524] The optional implementations of step S6102 can be found in the optional implementations of step S2106 in Figure 2A and step S2204 in Figure 2B, as well as other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0525] Figure 6B is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 6B, the present disclosure relates to a communication method. The communication method includes steps S6201 and S6202.

[0526] In step S6201, the first network element 1021 sends a first data stream to the first device 101.

[0527] The optional implementation of step S6201 can be found in the optional implementation of step S2107 in Figure 2A and step S2205 in Figure 2B, as well as other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0528] In step S6202, the first device 101 determines the QoS parameters.

[0529] The optional implementation of step S6202 can be found in the optional implementation of step S2108 in Figure 2A and step S2206 in Figure 2B, as well as other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

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

[0531] In some embodiments, a pose information marker indication (i.e., first information) is provided.

[0532] In some embodiments, the pose information marking indication can instruct the UPF to perform XR pose information marking indication. The UPF inserts the XR pose information into the extended header / outer header of the downlink data packet on N3 / N9. In some embodiments, the UPF inserts the XR pose information into the GTP-U or the transport network (e.g., enabling differentiated processing between packets carrying pose information and packets not carrying pose information).

[0533] In some embodiments, the pose information marking indication is provided by the SMF, thereby enabling XR pose information marking of the UPF (e.g., enabling differentiated processing between data packets carrying pose information and data packets not carrying pose information).

[0534] In some embodiments, the pose information tagged by the UPF may include one or more of the following:

[0535] - Pose type, for example, 6DoF XR pose or 3DoF XR pose;

[0536] - Pose information includes the position domains x, y, z, and / or the orientation domains rx, ry, rz, rw;

[0537] -XR timestamp, for example, a timestamp used for XR pose;

[0538] - Action ID, for example, a series of actions corresponding to pose coordinates x, y, z, rx, ry, rz, rw;

[0539] - Media ID, for example, used to indicate a series of media streams corresponding to the same pose.

[0540] In some embodiments, pose information markers may be provided to the UPF in the QER.

[0541] In some embodiments, pose information marking indications may be provided to the UPF during the N4 session establishment or modification process.

[0542] In some embodiments, the pose information tag indication may be sent from the SMF to the UPF at the N4 reference point together with the N4 session identifier, rule identifier, and QoS flow identifier.

[0543] In some embodiments, the QER carrying a pose information marker may be as shown in Table 1.

[0544] Table 1: Attributes in QER

[0545] In some embodiments, taking into account the protocol description (indicating the transport protocol used by the SDF, such as RTP, SRTP, and related information), the pose information tag includes one or more of the following characteristics:

[0546] -RTP or SRTP has an RTP extended header for use in pose information labeling;

[0547] -RTP or SRTP does not have the RTP extended header, but it does have the RTP payload format;

[0548] -RTP or SRTP has an RTP extended header for pose information labeling and an RTP payload format.

[0549] Figure 7A is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure. An N4 association establishment process is used to establish an N4 session between the SMF and UPF, thereby enabling the SMF to use the resources of the UPF for subsequent N4 session establishment. During these processes, the SMF and UPF can exchange functionalities supported by each side.

[0550] In some embodiments, the establishment of an N4 association may be initiated by the SMF. In some embodiments, before establishing the first N4 session with the UPF, the SMF initiates an N4 association establishment process to request the establishment of an N4 association with the UPF.

[0551] In some embodiments, 5GC determines the use of pose information tags for a specific SDF. SMF ensures that UPF applies pose information tags to that SDF (e.g., by setting a pose information tag indicator in the QER associated with the DL PDR).

[0552] In some embodiments, the pose information marking indication can instruct the UPF to perform XR pose information marking indication. The UPF inserts the XR pose information into the extended header / outer header of the downlink data packet on N3 / N9. In some embodiments, the UPF inserts the XR pose information into the GTP-U or the transport network (e.g., enabling differentiated processing between packets carrying pose information and packets not carrying pose information).

[0553] In some embodiments, the pose information marking indication is provided by the SMF, thereby enabling XR pose information marking of the UPF (e.g., enabling differentiated processing between data packets carrying pose information and data packets not carrying pose information).

[0554] In some embodiments, the pose information tag indication may be provided to the UPF in the QER during the N4 session establishment process. In some embodiments, the pose information tag indication may be sent from the SMF to the UPF at the N4 reference point together with the N4 session identifier, rule identifier, and QoS flow identifier.

[0555] In some embodiments, the pose information tagged by the UPF may include one or more of the following:

[0556] - Pose type, for example, 6DoF XR pose or 3DoF XR pose;

[0557] - Pose information includes the position domains x, y, z, and / or the orientation domains rx, ry, rz, rw;

[0558] -XR timestamp, for example, a timestamp used for XR pose;

[0559] - Action identifiers, for example, a series of actions corresponding to pose coordinates x, y, z, rx, ry, rz, rw;

[0560] - Media identifiers, for example, used to indicate a series of media corresponding to all media streams of the same pose.

[0561] In some embodiments, upon receiving an N4 association establishment request, the UPF may send an N4 association establishment response.

[0562] In some embodiments, when the SMF instructs the UPF to apply pose information marking (e.g., when pose information marking is instructed), the UPF inserts the pose information into the extended header and / or encapsulation header at the N4 (or N9) reference point of the SDF's DL packet. In some embodiments, the UPF inserts the pose information into the GTP-U extended header or into the transport network (e.g., enabling differentiated processing between packets carrying pose information and packets not carrying pose information).

[0563] In some embodiments, taking into account the protocol description (indicating the transport protocol used by the SDF, such as RTP, SRTP, and related information), the pose information tag includes one or more of the following characteristics:

[0564] -RTP or SRTP has an RTP extended header for use in pose information labeling;

[0565] -RTP or SRTP does not have the RTP extended header, but it does have the RTP payload format;

[0566] -RTP or SRTP has an RTP extended header for pose information labeling and an RTP payload format.

[0567] Figure 7B 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 7B, the establishment of the N4 association can be initiated by the UPF.

[0568] In some embodiments, before establishing the first N4 session with the UPF, the UPF initiates an N4 association establishment process to request the establishment of an N4 association with the SMF.

[0569] In some embodiments, upon receiving an N4 association establishment request, the SMF sends an N4 association establishment response.

[0570] In some embodiments, 5GC determines the use of pose information tags for a specific SDF. SMF ensures that UPF applies pose information tags to that SDF (e.g., by setting a pose information tag indicator in the QER associated with the DL PDR).

[0571] In some embodiments, the pose information marking indication is provided by the SMF, thereby enabling XR pose information marking of the UPF (e.g., enabling differentiated processing between data packets carrying pose information and data packets not carrying pose information).

[0572] In some embodiments, the pose information tag indication may be provided to the UPF in the QER during the N4 session establishment process. In some embodiments, the pose information tag indication may be sent from the SMF to the UPF at the N4 reference point together with the N4 session identifier, rule identifier, and QoS flow identifier.

[0573] In some embodiments, the pose information tagged by the UPF may include one or more of the following:

[0574] - Pose type, for example, 6DoF XR pose or 3DoF XR pose;

[0575] - Pose information includes the position domains x, y, z, and / or the orientation domains rx, ry, rz, rw;

[0576] -XR timestamp, for example, a timestamp used for XR pose;

[0577] - Action identifiers, for example, a series of actions corresponding to pose coordinates x, y, z, rx, ry, rz, rw;

[0578] - Media identifiers, for example, used to indicate a series of media corresponding to all media streams of the same pose.

[0579] In some embodiments, when the SMF instructs the UPF to apply pose information marking (e.g., when pose information marking is instructed), the UPF inserts the pose information into the extended header and / or encapsulation header at the N4 (or N9) reference point of the SDF's DL packet. In some embodiments, the UPF inserts the pose information into the GTP-U extended header or into the transport network (e.g., enabling differentiated processing between packets carrying pose information and packets not carrying pose information).

[0580] In some embodiments, taking into account the protocol description (indicating the transport protocol used by the SDF, such as RTP, SRTP, and related information), the pose information tag includes one or more of the following characteristics:

[0581] -RTP or SRTP has an RTP extended header for use in pose information labeling;

[0582] -RTP or SRTP does not have the RTP extended header, but it does have the RTP payload format;

[0583] -RTP or SRTP has an RTP extended header for pose information labeling and an RTP payload format.

[0584] Figure 7C is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

[0585] In some embodiments, the N4 session establishment process is used to create an N4 session context for a PDU session on the UPF. The SMF allocates a new N4 session identifier and provides it to the UPF. The N4 session identifier is stored on both the SMF and the UPF and is used to identify the N4 session context during interactions between the SMF and the UPF. The SMF may also store the association between the N4 session identifier and the PDU session for the UE.

[0586] In step 1, the SMF receives a trigger to establish a new PDU session or to change the UPF for an already established PDU session.

[0587] In step 2, the SMF sends an N4 session establishment request message to the UPF. This message contains structured control information that defines the behavior of the UPF.

[0588] In some embodiments, 5GC determines the use of pose information tags for a specific SDF. SMF ensures that UPF applies pose information tags to that SDF (e.g., by setting a pose information tag indicator in the QER associated with the DL PDR).

[0589] In some embodiments, the pose information marking indication can instruct the UPF to perform XR pose information marking indication. The UPF inserts the XR pose information into the extended header / outer header of the downlink data packet on N3 / N9. In some embodiments, the UPF inserts the XR pose information into the GTP-U or the transport network (e.g., enabling differentiated processing between packets carrying pose information and packets not carrying pose information).

[0590] In some embodiments, the pose information marking indication is provided by the SMF, thereby enabling XR pose information marking of the UPF (e.g., enabling differentiated processing between data packets carrying pose information and data packets not carrying pose information).

[0591] In some embodiments, the pose information tag indication may be provided to the UPF in the QER during the N4 session establishment process. In some embodiments, the pose information tag indication may be sent from the SMF to the UPF at the N4 reference point together with the N4 session identifier, rule identifier, and QoS flow identifier.

[0592] In some embodiments, the pose information tagged by the UPF may include one or more of the following:

[0593] - Pose type, for example, 6DoF XR pose or 3DoF XR pose;

[0594] - Pose information includes the position domains x, y, z, and / or the orientation domains rx, ry, rz, rw;

[0595] -XR timestamp, for example, a timestamp used for XR pose;

[0596] - Action identifiers, for example, a series of actions corresponding to pose coordinates x, y, z, rx, ry, rz, rw;

[0597] - Media identifiers, for example, used to indicate a series of media corresponding to all media streams of the same pose.

[0598] In step 3, the UPF sends an N4 session establishment response message as a response. This message contains any information that the UPF needs to provide to the SMF in response to the received control information.

[0599] In some embodiments, when the SMF instructs the UPF to apply pose information marking (e.g., when pose information marking is instructed), the UPF inserts the pose information into the extended header and / or encapsulation header at the N4 (or N9) reference point of the SDF's DL packet. In some embodiments, the UPF inserts the pose information into the GTP-U extended header or into the transport network (e.g., enabling differentiated processing between packets carrying pose information and packets not carrying pose information).

[0600] In some embodiments, taking into account the protocol description (indicating the transport protocol used by the SDF, such as RTP, SRTP, and related information), the pose information tag includes one or more of the following characteristics:

[0601] -RTP or SRTP has an RTP extended header for use in pose information labeling;

[0602] -RTP or SRTP does not have the RTP extended header, but it does have the RTP payload format;

[0603] -RTP or SRTP has an RTP extended header for pose information labeling and an RTP payload format.

[0604] In step 4, the SMF interacts with the network element (e.g., the AMF or PCF) that triggered the N4 session establishment process.

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

[0606] In some embodiments, the flow of the communication method according to the present disclosure (e.g., the flow shown in Figures 7A, 7B, and 7C) may involve at least one of the following: control plane, user plane, and data plane. In some embodiments, the flow of the communication method according to the present disclosure may include at least one of the following: interaction within the control plane, interaction within the user plane, interaction between the control plane and the user plane, interaction within the data plane, interaction between the control plane and the data plane, and interaction between the user plane and the data plane. It should be noted that the flow of the communication method according to the present disclosure may also involve the computation plane or other planes, which are not specifically limited in this regard. In some embodiments, the network elements and devices within the communication system of the present disclosure may be located on one or more planes, including the control plane, user plane, data plane, and computation plane. These network elements and devices may implement request and data processing flows on one or more planes.

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

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

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

[0610] Figure 8 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. As shown in Figure 8, the communication device 800 may include at least one of the following: a transceiver module 801 and a processing module 802.

[0611] In some embodiments, the communication device 800 may be a first network element 1021. In some embodiments, the transceiver module 801 may be configured to: receive first information, wherein the first information is used to trigger marking processing of a first data stream of a first service, the first service being a pose-related service; and mark the first data stream according to the first information. Optionally, the transceiver module 801 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the first network element 1021 in any of the above methods (e.g., steps S2102, S2103, S2105, S2107, S2110, S2111, S2201, S2202, S2203, S2205, S2207, S2208), which will not be elaborated here. Optionally, the processing module 802 may be configured to perform at least one of the other steps (e.g., steps S2106, S2204) besides the communication steps such as sending and / or receiving performed by the first network element 1021 in any of the above methods, which will not be described in detail here.

[0612] In some embodiments, the communication device 800 may be a second network element 1022. In some embodiments, the transceiver module 801 may be configured to: send first information, wherein the first information is used to trigger the marking processing of a first data stream of a first service, and the first service is a pose-related service. Optionally, the transceiver module 801 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the second network element 1022 in any of the above methods (e.g., steps S2101, S2102, S2103, S2104, S2109, S2110, S2111, S2112, S2201, S2202, S2207, S2208), which will not be elaborated here.

[0613] In some embodiments, the communication device 800 may be a first device 101. In some embodiments, the transceiver module 801 may be configured to: receive a first data stream of a first service after being marked, wherein the first service is a pose-related service; and determine QoS parameters based on the marked first data stream. Optionally, the transceiver module 801 may be configured to perform at least one of the communication steps (e.g., steps S2107, S2205) performed by the first device 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module 802 may be configured to perform at least one of other steps (e.g., steps S2108, S2206) besides the communication steps (e.g., steps S2108, S2206) performed by the first device 101 in any of the above methods, which will not be elaborated here.

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

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

[0616] Figure 9A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. The communication device 9100 can be a network device (e.g., an access network device, a core network device, etc.), or a chip, chip system, or processor that supports the network device in implementing any of the above methods. The communication device 9100 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.

[0617] As shown in Figure 9A, the communication device 9100 includes one or more processors 9101. The processor 9101 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 9100 can be used to execute any of the above methods. Optionally, one or more processors 9101 can be used to invoke instructions to cause the communication device 9100 to execute any of the above methods.

[0618] In some embodiments, the communication device 9100 further includes one or more transceivers 9102. When the communication device 9100 includes one or more transceivers 9102, the transceivers 9102 perform at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2102, S2103, S2104, S2105, S2107, S2109, S2110, S2111, S2112, S2201, S2202, S2203, S2205, S2207, S2208, but not limited thereto), and the processor 9101 performs at least one of other steps (e.g., steps S2106, S2108, S2204, S2206, 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, transmitter unit, transmitter, and transmitter circuit can be used interchangeably; and terms such as receiver, receiver unit, receiver, and receiver circuit can be used interchangeably.

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

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

[0621] Figure 9B 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 9100 can be a chip or a chip system, please refer to the schematic diagram of the chip 9200 shown in Figure 9B, but it is not limited thereto.

[0622] Chip 9200 includes one or more processors 9201. Chip 9200 is used to perform any of the methods described above.

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

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

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

[0626] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 9100, cause the communication device 9100 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 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 not limited thereto; it may also be a temporary storage medium.

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

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

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

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

1. A communication method performed by a first network element, wherein, The method comprises: receiving first information, wherein the first information is used to trigger marking processing of a first data flow of a first service, the first service being a pose-related service; performing marking processing on the first data flow according to the first information.

2. The method of claim 1, wherein, The first information comprises at least one of: indication information for indicating that the first data flow is subjected to marking processing; protocol description information for indicating protocol characteristics of a transmission protocol related to the first data flow.

3. The method of claim 2, wherein, The transmission protocol comprises at least one of: real-time transport protocol (RTP); secure real-time transport protocol (SRTP).

4. The method of claim 2 or 3, wherein, The protocol characteristics comprise at least one of: having an RTP extension header; having an RTP payload format.

5. The method of any one of claims 2 to 4, wherein, The indication information is contained in quality of service enforcement rules (QER) related to the first data flow.

6. The method of any one of claims 1 to 5, wherein, The marking processing on the first data flow according to the first information comprises: adding pose information in an extension header or encapsulation header of a data packet of the first data flow.

7. The method of claim 6, wherein, The pose information comprises at least one of: type information for indicating a pose type; parameter information for indicating a parameter value of a pose; time information for indicating a time corresponding to a pose; action information for indicating an action related to a pose; flow information for indicating a flow related to a pose; priority information for indicating a priority related to a pose.

8. The method of claim 7, wherein, The pose type comprises at least one of: six degrees of freedom (6DoF); three degrees of freedom (3DoF).

9. The method of claim 7 or 8, wherein, The parameter information comprises at least one of: a position-related parameter value; a direction-related parameter value.

10. The method of any one of claims 7 to 9, wherein, The action information comprises an action identifier of at least one action related to the pose.

11. The method of any one of claims 7 to 10, wherein, The flow information comprises a flow identifier of at least one flow related to the same pose.

12. The method of any one of claims 1 to 11, wherein, The method further comprises: receiving second information, wherein the second information is used to stop the marking processing on the first data flow; stopping the marking processing on the first data flow according to the second information.

13. A communication method performed by a second network element, wherein, The method comprises: sending first information, wherein the first information is used to trigger marking processing of a first data flow of a first service, the first service being a pose-related service.

14. The method of claim 13, wherein, The first information comprises at least one of: indication information for indicating that the first data flow is subjected to marking processing; protocol description information for indicating protocol characteristics of a transmission protocol related to the first data flow.

15. The method of claim 14, wherein, The transmission protocol comprises at least one of: real-time transport protocol (RTP); secure real-time transport protocol (SRTP).

16. The method of claim 14 or 15, wherein, The protocol characteristics comprise at least one of: having an RTP extension header; having an RTP payload format.

17. The method of any one of claims 14 to 16, wherein, The indication information is contained in quality of service enforcement rules (QER) related to the first data flow.

18. The method of any one of claims 13 to 17, wherein, The marking processing can comprise adding pose information in an extension header or encapsulation header of a data packet of the first data flow.

19. The method of claim 18, wherein, The pose information comprises at least one of: type information for indicating a pose type; parameter information for indicating a parameter value of a pose; time information for indicating a time corresponding to a pose; action information for indicating an action related to a pose; flow information used for indicating a flow related to the pose; priority information used for indicating a priority related to the pose.

20. The method of claim 19, wherein, The pose type includes at least one of: six degrees of freedom (6DoF); three degrees of freedom (3DoF).

21. The method of claim 19 or 20, wherein, The parameter information includes at least one of: a position-related parameter value; a direction-related parameter value.

22. The method of any one of claims 19-21, wherein, The action information includes an action identifier of at least one action related to the pose.

23. The method of any one of claims 19-22, wherein, The flow information includes a flow identifier of at least one flow related to the same pose.

24. The method of any one of claims 13 to 23, wherein, The method further includes: sending second information, wherein the second information is used to stop the marking processing on the first data flow.

25. A communication method performed by a first device, wherein, The method includes: receiving a marked first data flow of a first service, wherein the first service is a service related to a pose; determining a quality of service (QoS) parameter according to the marked first data flow.

26. The method of claim 25, wherein, A header of a data packet of the marked first data flow is marked with pose information, and the QoS parameter is determined according to the pose information in the marked first data flow.

27. The method of claim 26, wherein, The pose information includes at least one of: type information used for indicating a pose type; parameter information used for indicating a parameter value of a pose; time information used for indicating a time corresponding to a pose; action information used for indicating an action related to a pose; flow information used for indicating a flow related to a pose; priority information used for indicating a priority related to a pose.

28. The method of claim 27, wherein, The pose type includes at least one of: six degrees of freedom (6DoF); three degrees of freedom (3DoF).

29. The method of claim 27 or 28, wherein, The parameter information includes at least one of: a position-related parameter value; a direction-related parameter value.

30. The method of any one of claims 27-29, wherein, The action information includes an action identifier of at least one action related to the pose.

31. The method of any one of claims 27-30, wherein, The flow information includes a flow identifier of at least one flow related to the same pose.

32. A communication method performed by a core network, wherein, The core network includes a first network element and a second network element; The method includes: The second network element sends first information to the first network element, wherein the first information is used to trigger marking processing on a first data flow of a first service, and the first service is a service related to a pose; The first network element performs marking processing on the first data flow according to the first information.

33. A first network element, wherein, The first network element includes: a transceiver configured to receive first information, wherein the first information is used to trigger marking processing on a first data flow of a first service, and the first service is a service related to a pose; a processing module configured to perform marking processing on the first data flow according to the first information.

34. A second network element, wherein, The second network element includes: a transceiver configured to send first information, wherein the first information is used to trigger marking processing on a first data flow of a first service, and the first service is a service related to a pose.

35. A first device, wherein, The first device includes: a transceiver configured to receive a marked first data flow of a first service, wherein the first service is a service related to a pose; a processing module configured to determine a quality of service (QoS) parameter according to the marked first data flow.

36. A communication device, comprising: one or more processors; The communication device is configured to perform the communication method of any one of claims 1 to 12, or the communication method of any one of claims 13 to 24, or the communication method of any one of claims 25 to 31.

37. A communication system comprising: a first network element configured to implement the communication method of any one of claims 1 to 12; a second network element configured to implement the communication method of any one of claims 13 to 24; a first device configured to implement the communication method of any one of claims 25 to 31.

38. A storage medium 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 to 12; the communication method of any one of claims 13 to 24; the communication method of any one of claims 25 to 31; the communication method of claim 32.

39. A computer program product comprising instructions, wherein the instructions, when executed on a communication device, cause the communication device to implement at least one of: the communication method of any one of claims 1 to 12; the communication method of any one of claims 13 to 24; the communication method of any one of claims 25 to 31; the communication method of claim 32.

Images