Communication method, communication device, communication system, storage medium, and program product
By monitoring and managing the latency of data streams, the challenge of latency management in immersive communications is solved, thus improving the user experience.
Patent Information
- Application Number
- PCT/CN2025/094023
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Existing communication systems struggle to effectively manage data stream latency when implementing immersive communication, leading to a decline in user experience.
By acquiring and transmitting monitoring information, the duration of the monitoring data stream from motion to rendering to photons is monitored, thereby enabling latency management of the data stream and meeting the time-related QoS requirements of immersive services.
It enhances the communication system's ability to manage latency for immersive service data streams, thereby improving the user experience.
Smart Images

Figure CN2025094023_12112026_PF_FP_ABST
Abstract
Description
Communication methods, communication equipment, communication systems, storage media and software products Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology
[0002] Immersive communication aims to provide users with a better user experience through highly immersive, interactive, and multi-dimensional / multimodal technologies. At the same time, the implementation of immersive communication places higher demands on communication systems, especially on wireless resource management and Quality of Service (QoS) processing related to data streams. Summary of the Invention
[0003] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0004] According to a first aspect of the present disclosure, a communication method is provided. The communication method is executed by a first node. The communication method includes: acquiring monitoring information, wherein the monitoring information is obtained by monitoring a first data stream of a first service for a first delay, the first delay being used to characterize the duration from motion to rendering to photons; and sending the monitoring information to a second node via a user.
[0005] According to a second aspect of the present disclosure, a communication method is provided. This communication method is performed by a second node. The communication method includes: receiving monitoring information sent by a first node through a user plane, wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons.
[0006] According to a third aspect of the present disclosure, a communication method is provided. This communication method is performed by a third node. The communication method includes: sending monitoring information to a first node, wherein the monitoring information is obtained by monitoring a first data stream of a first service for a first time delay, the first time delay being used to characterize the duration from motion to rendering to photons.
[0007] According to a fourth aspect of the present disclosure, a communication method is provided. This communication method is performed by a terminal. The communication method includes: sending monitoring information to a third node, wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons.
[0008] According to a fifth aspect of the present disclosure, a communication method is provided. This communication method is executed by a communication system. The communication system includes a first node, a second node, a third node, and a terminal. The communication method includes at least one of the following: the terminal sends monitoring information to the third node; the third node sends monitoring information to the first node; the first node sends monitoring information to the second node via a user; wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons.
[0009] According to a sixth aspect of the present disclosure, a communication device is provided. This communication device is used to perform the communication methods described in any of the first to fourth aspects.
[0010] According to a seventh aspect of the present disclosure, a communication system is provided. The communication system includes at least one of the following: a first node, a second node, a third node, and a terminal. The first node is configured to perform the communication method as described in the first aspect. The second node is configured to perform the communication method as described in the second aspect. The third node is configured to perform the communication method as described in the third aspect. The terminal is configured to perform the communication method as described in the fourth aspect.
[0011] According to an eighth 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 fifth aspects.
[0012] According to a ninth aspect of the present disclosure, a program product is provided. The program product includes at least one of a program and instructions. When the program and at least one of the instructions are executed by a communication device, they implement the communication method as described in any one of the first to fifth aspects.
[0013] According to a tenth 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 fifth aspects.
[0014] According to an eleventh 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 fifth aspects.
[0015] According to embodiments of this disclosure, it is possible to enhance the latency management of data streams for services such as immersive services in a communication system.
[0016] 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
[0017] 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.
[0018] Figure 1A is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.
[0019] 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.
[0020] 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.
[0021] Figure 2 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.
[0022] Figure 3A is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.
[0023] Figure 3B is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.
[0024] Figure 4 is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.
[0025] Figure 5 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.
[0026] Figure 6A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.
[0027] Figure 6B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. Detailed Implementation
[0028] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0029] In a first aspect, embodiments of this disclosure provide a communication method. This communication method is executed by a first node. The communication method includes: acquiring monitoring information, wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons; and sending the monitoring information to a second node via a user.
[0030] In this embodiment, the first node can acquire monitoring information of the first latency for the first data stream of the first service and provide the monitoring information to the second node through the user plane. In this way, the communication system can monitor the first latency of the first data stream of the first service, thereby meeting the time-related QoS requirements of the first data stream of the first service from motion to rendering to photons. This enhances the latency management of the communication system for data streams of services such as immersive services.
[0031] In conjunction with some embodiments of the first aspect, in some embodiments, obtaining monitoring information includes at least one of the following: receiving monitoring information of the first delay sent by a third node; or obtaining monitoring information of the first delay from a local source.
[0032] In conjunction with some embodiments of the first aspect, in some embodiments, the monitoring information received from the third node includes at least one of the following: monitoring information obtained by the third node performing monitoring of the first delay; monitoring information obtained by the terminal performing monitoring of the first delay; monitoring information obtained by the device performing monitoring of the first delay, wherein the device is connected to the terminal.
[0033] In conjunction with some embodiments of the first aspect, in some embodiments, monitoring information is transmitted on the user plane.
[0034] In conjunction with some embodiments of the first aspect, in some embodiments, obtaining monitoring information includes obtaining monitoring information of the first latency from a local source, and the above method further includes: performing monitoring of the first latency.
[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the monitoring information includes at least one of the following: a measurement of a first latency; a measurement of a round-trip latency from the terminal to the first node; a measurement of an uplink latency from the terminal to the first node; a measurement of a downlink latency from the first node to the terminal; a measurement of a processing latency of the terminal; a measurement of a processing latency of the device; a measurement of a round-trip latency from the terminal to the device; and a measurement of a processing latency of the second node; wherein the device is connected to the terminal.
[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: integrating the acquired monitoring information.
[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the acquired monitoring information is integrated, including: determining a measurement value of a first time delay based on the monitoring information.
[0038] In a second aspect, embodiments of this disclosure provide a communication method. This communication method is executed by a second node. The communication method includes: receiving monitoring information sent by a first node through a user plane, wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons.
[0039] In this embodiment, the second node can obtain monitoring information on the first latency of the first data stream for the first service through the user plane. In this way, the communication system can monitor the first latency of the first data stream for the first service, thereby meeting the time-related QoS requirements of the first data stream for the first service from motion to rendering to photons. This enhances the latency management of the communication system for data streams of services such as immersive experiences.
[0040] In conjunction with some embodiments of the second aspect, in some embodiments, the monitoring information includes at least one of the following: a measurement of a first latency; a measurement of a round-trip latency from the terminal to the first node; a measurement of an uplink latency from the terminal to the first node; a measurement of a downlink latency from the first node to the terminal; a measurement of a processing latency of the terminal; a measurement of a processing latency of the device; a measurement of a round-trip latency from the terminal to the device; and a measurement of a processing latency of the second node; wherein the device is connected to the terminal.
[0041] In a third aspect, embodiments of this disclosure provide a communication method. This communication method is executed by a third node. The communication method includes: sending monitoring information to a first node, wherein the monitoring information is obtained by monitoring a first data stream of a first service for a first time delay, the first time delay being used to characterize the duration from motion to rendering to photons.
[0042] In this embodiment, the third node can provide the first node with monitoring information on the first latency of the first data stream acquired for the first service. In this way, the communication system can monitor the first latency of the first data stream of the first service, thereby meeting the time-related QoS requirements of the first data stream of the first service from motion to rendering to photons. This enhances the latency management of the communication system for data streams of services such as immersive services.
[0043] In conjunction with some embodiments of the third aspect, in some embodiments, monitoring information is transmitted on the user plane.
[0044] In conjunction with some embodiments of the third aspect, in some embodiments, the above method further includes at least one of the following: receiving monitoring information of the first delay from the terminal; and obtaining monitoring information of the first delay from the local machine.
[0045] In conjunction with some embodiments of the third aspect, in some embodiments, the monitoring information received from the terminal includes at least one of the following: monitoring information obtained by the terminal performing monitoring for a first delay; monitoring information obtained by the device performing monitoring for a first delay, wherein the device is connected to the terminal.
[0046] In conjunction with some embodiments of the third aspect, in some embodiments, the monitoring information includes monitoring information of a first latency obtained locally, and the method further includes: performing monitoring of the first latency.
[0047] In conjunction with some embodiments of the third aspect, in some embodiments, the monitoring information includes at least one of the following: a measurement of a first latency; a measurement of a round-trip latency from the terminal to the first node; a measurement of an uplink latency from the terminal to the first node; a measurement of a downlink latency from the first node to the terminal; a measurement of a processing latency of the terminal; a measurement of a processing latency of the device; a measurement of a round-trip latency from the terminal to the device; and a measurement of a processing latency of the second node; wherein the device is connected to the terminal.
[0048] In a fourth aspect, embodiments of this disclosure provide a communication method. This communication method is executed by a terminal. The communication method includes: sending monitoring information to a third node, wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons.
[0049] In this embodiment, the terminal can provide the third node with monitoring information on the first latency of the first data stream for the first service. In this way, the communication system can monitor the first latency of the first data stream for the first service, thereby meeting the time-related QoS requirements of the first data stream for the first service from motion to rendering to photons. This enhances the latency management of the communication system for data streams of services such as immersive experiences.
[0050] In conjunction with some embodiments of the fourth aspect, in some embodiments, monitoring information is transmitted on the user plane.
[0051] In conjunction with some embodiments of the fourth aspect, in some embodiments, the monitoring information includes at least one of the following: monitoring information obtained by monitoring the terminal performing a first delay; monitoring information obtained by monitoring the device performing a first delay, wherein the device is connected to the terminal.
[0052] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above method further includes at least one of the following: performing monitoring of the first delay; receiving monitoring information of the first delay sent by the device, wherein the device is connected to the terminal.
[0053] In conjunction with some embodiments of the fourth aspect, in some embodiments, the monitoring information includes at least one of the following: a measurement of a first latency; a measurement of a round-trip latency from the terminal to the first node; a measurement of an uplink latency from the terminal to the first node; a measurement of a downlink latency from the first node to the terminal; a measurement of a processing latency of the terminal; a measurement of a processing latency of the device; a measurement of a round-trip latency from the terminal to the device; and a measurement of a processing latency of the second node; wherein the device is connected to the terminal.
[0054] In a fifth aspect, embodiments of this disclosure provide a communication method. This communication method is executed by a communication system. The communication system includes a first node, a second node, a third node, and a terminal. The communication method includes at least one of the following: the terminal sends monitoring information to the third node; the third node sends monitoring information to the first node; the first node sends monitoring information to the second node via a user; wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons.
[0055] In a sixth aspect, embodiments of this disclosure provide a communication device. The communication device includes a transceiver module. The transceiver module is configured to: acquire monitoring information, wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons; and send a monitoring report to a second node via a user.
[0056] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transceiver module is configured to perform at least one of the following: receiving monitoring information of the first delay sent by the third node; or obtaining monitoring information of the first delay from the local machine.
[0057] In conjunction with some embodiments of the sixth aspect, in some embodiments, the monitoring information received from the third node includes at least one of the following: monitoring information obtained by the third node performing monitoring of the first delay; monitoring information obtained by the terminal performing monitoring of the first delay; monitoring information obtained by the device performing monitoring of the first delay, wherein the device is connected to the terminal.
[0058] In conjunction with some embodiments of the sixth aspect, in some embodiments, monitoring information is transmitted on the user plane.
[0059] In conjunction with some embodiments of the sixth aspect, in some embodiments, obtaining monitoring information includes obtaining monitoring information of the first delay from the local machine, and the processing module is further configured to perform monitoring of the first delay.
[0060] In conjunction with some embodiments of the sixth aspect, in some embodiments, the monitoring information includes at least one of the following: a measurement of a first latency; a measurement of a round-trip latency from the terminal to the first node; a measurement of an uplink latency from the terminal to the first node; a measurement of a downlink latency from the first node to the terminal; a measurement of a processing latency of the terminal; a measurement of a processing latency of the device; a measurement of a round-trip latency from the terminal to the device; and a measurement of a processing latency of the second node; wherein the device is connected to the terminal.
[0061] In conjunction with some embodiments of the sixth aspect, in some embodiments, the above-mentioned communication device further includes a processing module; the processing module is configured to integrate the acquired monitoring information.
[0062] In conjunction with some embodiments of the sixth aspect, in some embodiments, the processing module is configured to: determine a measurement value of the first delay based on monitoring information.
[0063] In a seventh aspect, embodiments of this disclosure provide a communication device. The communication device includes a transceiver module. The transceiver module is configured to receive monitoring information sent by a first node via a user plane, wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons.
[0064] In conjunction with some embodiments of the seventh aspect, in some embodiments, the monitoring information includes at least one of the following: a measurement of a first latency; a measurement of a round-trip latency from the terminal to the first node; a measurement of an uplink latency from the terminal to the first node; a measurement of a downlink latency from the first node to the terminal; a measurement of a processing latency of the terminal; a measurement of a processing latency of the device; a measurement of a round-trip latency from the terminal to the device; and a measurement of a processing latency of the second node; wherein the device is connected to the terminal.
[0065] In an eighth aspect, embodiments of this disclosure provide a communication device. The communication device includes a transceiver module. The transceiver module is configured to send monitoring information to a first node, wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons.
[0066] In conjunction with some embodiments of the eighth aspect, in some embodiments, monitoring information is transmitted on the user plane.
[0067] In conjunction with some embodiments of the eighth aspect, in some embodiments, the transceiver module is further configured to perform at least one of the following: receiving monitoring information of the first delay from the terminal; or obtaining monitoring information of the first delay from the local machine.
[0068] In conjunction with some embodiments of the eighth aspect, in some embodiments, the monitoring information received from the terminal includes at least one of the following: monitoring information obtained by the terminal performing monitoring for a first delay; monitoring information obtained by the device performing monitoring for a first delay, wherein the device is connected to the terminal.
[0069] In conjunction with some embodiments of the eighth aspect, in some embodiments, the monitoring information includes monitoring information of a first delay obtained locally; the aforementioned communication device further includes a processing module configured to perform monitoring of the first delay.
[0070] In conjunction with some embodiments of the eighth aspect, in some embodiments, the monitoring information includes at least one of the following: a measurement of a first latency; a measurement of a round-trip latency from the terminal to the first node; a measurement of an uplink latency from the terminal to the first node; a measurement of a downlink latency from the first node to the terminal; a measurement of a processing latency of the terminal; a measurement of a processing latency of the device; a measurement of a round-trip latency from the terminal to the device; and a measurement of a processing latency of the second node; wherein the device is connected to the terminal.
[0071] In a ninth aspect, embodiments of this disclosure provide a communication device. The communication device includes a transceiver module. The transceiver module is configured to send monitoring information to a third node, wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons.
[0072] In conjunction with some embodiments of the ninth aspect, in some embodiments, monitoring information is transmitted on the user plane.
[0073] In conjunction with some embodiments of the ninth aspect, in some embodiments, the monitoring information includes at least one of the following: monitoring information obtained by monitoring the terminal performing a first delay; monitoring information obtained by monitoring the device performing a first delay, wherein the device is connected to the terminal.
[0074] In conjunction with some embodiments of the ninth aspect, in some embodiments, the communication device further includes a processing module; the processing module is configured to perform monitoring of the first delay; the transceiver module is further configured to receive monitoring information of the first delay sent by the device, wherein the device is connected to a terminal.
[0075] In conjunction with some embodiments of the ninth aspect, in some embodiments, the monitoring information includes at least one of the following: a measurement of a first latency; a measurement of a round-trip latency from the terminal to the first node; a measurement of an uplink latency from the terminal to the first node; a measurement of a downlink latency from the first node to the terminal; a measurement of a processing latency of the terminal; a measurement of a processing latency of the device; a measurement of a round-trip latency from the terminal to the device; and a measurement of a processing latency of the second node; wherein the device is connected to the terminal.
[0076] In a tenth aspect, embodiments of this disclosure provide a communication device. This communication device is used to perform the communication methods described in any of the first to fourth aspects and their possible implementations.
[0077] In an eleventh aspect, embodiments of this disclosure provide a communication system. The communication system includes at least one of the following: a first node, a second node, a third node, and a terminal. The first node is configured to perform the communication method as described in any of the first aspect and its possible embodiments. The second node is configured to perform the communication method as described in any of the second aspect and its possible embodiments. The third node is configured to perform the communication method as described in any of the third aspect and its possible embodiments. The terminal is configured to perform the communication method as described in any of the fourth aspect and its possible embodiments.
[0078] 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 fifth aspects and their possible embodiments.
[0079] In a thirteenth aspect, embodiments of this disclosure provide a program product. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the communication method as described in any of the first to fifth aspects and their possible embodiments.
[0080] 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 fifth aspects and their possible implementations.
[0081] 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 fifth aspects and their possible implementations.
[0082] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to execute the 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.
[0083] This disclosure provides a communication method, a communication device, a communication system, a storage medium, and a program product. In some embodiments, terms such as communication method, information processing method, and information transmission method can be used interchangeably; terms such as communication device, communication equipment, network equipment, network function, and network entity can be used interchangeably; and terms such as communication system and information processing system can be used interchangeably.
[0084] 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 otherwise specified, 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 implementation methods 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, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
[0085] In the embodiments disclosed herein, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the various 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.
[0086] 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.
[0087] 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.
[0088] In the embodiments of this disclosure, "a plurality of" means two or more.
[0089] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0090] 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 whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.
[0091] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); 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, and C.
[0092] 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.
[0093] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0094] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.
[0095] In some embodiments, terms such as “greater than,” “more than,” “higher than,” and “exceeding” can be used interchangeably; terms such as “greater than or equal to,” “not less than,” “more than or equal to,” “not less than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably; terms such as “less than,” “less than,” and “lower than” can be used interchangeably; and terms such as “less than or equal to,” “not greater than,” “less than or equal to,” “not more than,” “lower than or equal to,” “not higher than,” and “below” can be used interchangeably.
[0096] 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.
[0097] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0098] 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.
[0099] 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.
[0100] 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.
[0101] 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.
[0102] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0103] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0104] 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.
[0105] Figure 1A is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure. As shown in Figure 1A, the communication system 100 includes a terminal 101, a first device 102, and a core network 103.
[0106] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.
[0107] In some embodiments, the first device 102 may be a service consumer. One or more network elements in the core network 103 may act as service providers to provide corresponding network function (NF) services, in which case the first device 102 may be the party receiving the provided NF services.
[0108] In some embodiments, the first device 102 may be an access network device. In some embodiments, the first device 102 may be an access UPF. In some embodiments, the UPF may be deployed directly to and communicate with the terminal 101. In some embodiments, the UPF may be deployed after the access network device and communicate with the terminal 101 through the access network device.
[0109] In some embodiments, the first device 102 may be an access network device. In some embodiments, the first device 102 may be a radio access network device. In some embodiments, the first device 102 may be an access network device employing other technologies. For example, the first device 102 may be a non-3GPP interworking function (N3IWF), a trusted non-3GPP gateway function (TNGF), or a wireless access gateway function (W-AGF).
[0110] 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.
[0111] 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.
[0112] 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.
[0113] In some embodiments, the core network 103 may be a single device, including a first network element 1031, a second network element 1032, a third network element 1033, a fourth network element 1034, a fifth network element 1035, a sixth network element 1036, etc., or it may be multiple devices or a group of devices, each including all or some of the first network element 1031, the second network element 1032, the third network element 1033, the fourth network element 1034, the fifth network element 1035, the sixth network element 1036, etc. The network elements in the core network 103 may be virtual or physical. The core network 103 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a 6G Core Network, and a Next Generation Core (NGC).
[0114] In some embodiments, the first network element 1031 can be used to support a unified policy framework and provide policy rules, the name of which is not limited thereto.
[0115] In some embodiments, the first network element 1031 may be a control plane network element.
[0116] In some embodiments, the first network element 1031 may be, for example, a policy control function (PCF).
[0117] In some embodiments, the second network element 1032 may provide application services, the name of which is not limited thereto.
[0118] In some embodiments, the second network element 1032 may include, for example, an application function (AF) and / or an application server (AS).
[0119] In some embodiments, the third network element 1033 can be used for functions such as session management, execution of PCF-issued control policies, selection of UPF, and allocation of UE Internet Protocol (IP) addresses, and its name is not limited thereto.
[0120] In some embodiments, the third network element 1033 may be a control plane network element.
[0121] In some embodiments, the third network element 1033 may be, for example, a session management function (SMF).
[0122] In some embodiments, the fourth network element 1034 can be used to implement functions such as data forwarding, session / flow-level billing statistics, bandwidth limiting, and QoS processing, and its name is not limited thereto.
[0123] In some embodiments, the fourth network element 1034 may be a user plane network element. In some embodiments, the fourth network element 1034 may be a data plane network element. In some embodiments, the fourth network element 1034 may be a computing plane network element.
[0124] In some embodiments, the fourth network element 1034 may be, for example, a user plane function (UPF).
[0125] In some embodiments, the fifth network element 1035 can be used to ensure the security of external applications to the 3GPP network, and provide external applications with QoS customization capabilities, mobility state time subscription, AF request distribution, etc., and the name is not limited to these.
[0126] In some embodiments, the fifth network element 1035 may be, for example, a network exposure function (NEF).
[0127] In some embodiments, the sixth network element 1036 can be used to perform mobility management, non-access stratum mobility management (NAS MM) signaling processing, NAS session management (SM) signaling routing, security anchor point and security context management, etc., and the name is not limited thereto.
[0128] In some embodiments, the sixth network element 1036 may be a control plane network element.
[0129] In some embodiments, the sixth network element 1036 may be, for example, an access and mobility management function (AMF).
[0130] In some embodiments, the second network element 1032 may be located outside the core network 103, or inside the core network 103, or partially inside and partially outside the core network 103. This disclosure does not specifically limit this.
[0131] In some embodiments, the AF and AS in the second network element 1032 can be deployed centrally or independently, and this disclosure does not specifically limit this.
[0132] In some embodiments, the communication system 100 described above may be a 5G communication system or a 6G 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 5G-A (5G-advanced) communication system, and this disclosure does not specifically limit it in this regard.
[0133] Figures 1B and 1C illustrate the architecture of a communication system using a 5G communication system as an example. Here, terminal 101 can be a UE, and first device 102 can be a RAN.
[0134] Figure 1B is a schematic diagram of the architecture of one implementation of the communication system provided according to an embodiment of the present disclosure. As shown in Figure 1B, the architecture of the 5G communication system is presented in the form of reference points. N1 is the reference point between the UE and AMF. N2 is the reference point between the RAN and AMF. N3 is the reference point between the RAN and UPF. N4 is the reference point between the SMF and UPF. N5 is the reference point between the PCF and AF. N6 is the reference point between the UPF and the data network (DN). N7 is the reference point between the SMF and PCF. N11 is the reference point between the AMF and SMF. N15 is the reference point between the SMF and PCF. Uu is the interface between the UE and the RAN. It should be noted that the NEF is not shown in Figure 1B. However, each network element in the communication system can interact with the NEF.
[0135] Figure 1C is a schematic diagram of the architecture of another implementation of the communication system provided according to an embodiment of the present disclosure. As shown in Figure 1C, the architecture of the 5G communication system is presented in a service-based interface manner. Namf is the service-based interface provided by AMF. Nsmf is the service-based interface provided by SMF. Nnef is the service-based interface provided by NEF. Npcf is the service-based interface provided by PCF. Naf is the service-based interface provided by AF.
[0136] 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.
[0137] 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.
[0138] 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).
[0139] Immersive communication is an extension of enhanced mobile broadband (eMBB) and covers a wide range of cases. In these cases, it can provide users with rich, interactive (immersive) video experiences, including interactions with machine interfaces.
[0140] In some embodiments, with the development of communication technology, immersive extended reality (XR) services in communication systems aim to provide an excellent user experience through capabilities such as ultra-high resolution, high frame rate, wide color gamut, high dynamic range, wide viewing angle, and advanced encoding / compression technologies.
[0141] In some embodiments, immersive XR services can support more natural interaction methods, such as voice interaction, gesture interaction, head interaction, and eye tracking, thereby achieving complex user and environmental awareness. Communication systems and service platforms can collaborate to perform functions such as rendering, synchronization, encoding, distribution, storage, and management of immersive XR services, and support real-time transmission and processing of panoramic video data, field of view (FOV) video data, etc.
[0142] In some embodiments, users of immersive communication technologies expect to work, play, and interact seamlessly in both the real and virtual worlds. Such immersive experiences can be achieved through advanced extended reality (AXR) and multimedia features. These features include, for example, user interaction via a combination of avatar-holographic conferencing, spatial collaboration with high-fidelity three-dimensional (3D) objects, high-resolution immersive 2D-3D cloud gaming, high-resolution 360-degree 2D-3D content streaming, and AI-based multimodal user experiences.
[0143] In related technologies, communication systems for XR multimedia (XRM) service data stream processing have enhanced features such as multimodal service flow indication, round-trip time (RTT) latency support, PDU-based processing, congestion control, data burst marking, next data burst time marking, and data enhancement to accelerate transmission. However, for traffic such as 6G immersive services, the current system cannot meet the QoS requirements of 6G immersive services, which demand ultra-high resolution, ultra-high bandwidth, and ultra-low latency. In particular, the RTT latency cannot meet the QoS requirements of dynamic service characteristics such as latency and jitter in interactive scenarios, including: authorization management of immersive service (IS) network transmission latency and jitter, perception and latency management of processing capabilities of different UE device types, the presence of downstream devices and the latency impact of various UE downstream devices, and latency management of multi-task, multi-terminal processing in end-to-end collaboration (e.g., offloading and latency impact of immersive rendering tasks).
[0144] Therefore, how to ensure support for the QoS requirements of immersive services is a technical problem that urgently needs to be solved.
[0145] Figure 2 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 2, the communication method of the embodiment of the present disclosure includes steps S201 to S216.
[0146] In step S201, the second network element 1032 sends the first information to the fifth network element 1035.
[0147] In some embodiments, the second network element 1032 can send the first information. In some embodiments, the first information can be sent by the second network element 1032, but is not limited thereto, and can also be sent by other entities.
[0148] In some embodiments, the fifth network element 1035 can receive the first information. In some embodiments, the first information can be received by the fifth network element 1035, but is not limited thereto, and can also be received by other entities.
[0149] In some embodiments, the first information may be sent when the second network element 1032 requests the establishment of a session for the first service. In some embodiments, the second network element 1032 may send the first information when it determines that a session needs to be established for the first service.
[0150] In some embodiments, the first service may be a service related to immersive communication. In one example, the first service may include XR service, XRM service, AXR service, or interactive media service. It is understood that the first service may also be other types of services, and this disclosure does not specifically limit them.
[0151] In some embodiments, the first information may be used to request first monitoring of a first data stream of a first service at a first time. In some embodiments, the first information may indicate that first monitoring of a first data stream of a first service at a first time is required. In some embodiments, the first information may indicate that the first data stream of a first service requires monitoring at a first time. In some embodiments, the first information may be used to subscribe to a monitoring report for the first time.
[0152] In some embodiments, the first data flow of the first service may include a service data flow (SDF). In some embodiments, the number of first data flows may be one or more.
[0153] In some embodiments, the first time can be the motion-to-render-to-photon time (M2R2PT). In some embodiments, in the first service, the user's actions and the image displayed on the screen can be correlated. For example, the user's head and / or body can move, and the server of the first service can send corresponding data to one or more of the terminal, the terminal's downstream device, network functions, and network peer devices for rendering and display based on the user's movements. The time from the user's movement to rendering and then to display on the screen (e.g., the screen of terminal 101, the screen of the downstream device, the screen of the peer device communicating with the user's terminal 101, etc.) is the first time.
[0154] In some embodiments, the first time can characterize the duration from user movement to image rendering and then to photon emission, and the first time can also be referred to as the first time delay.
[0155] In some embodiments, referring to FIG1A, the first time may include the following components: the round-trip time between terminal 101 and the second network element 1032, the processing time of the second network element 1032, and the processing time of terminal 101. In some embodiments, the round-trip time between terminal 101 and the second network element 1032 includes the uplink time of the first data stream of the first service from terminal 101 to the second network element 1032, and the downlink time from the second network element 1032 to terminal 101. In some embodiments, the processing time of the second network element 1032 includes the time between the second network element 1032 receiving uplink data from terminal 101 and sending downlink data to terminal 101. It is understood that the transmission of the first data stream may include uplink and downlink transmission. In some embodiments, the transmission of the first data stream may only include uplink transmission, then the first time may include the uplink time between terminal 101 and the second network element 1032, the processing time of the second network element 1032, and the processing time of terminal 101. In some embodiments, the transmission of the first data stream may only include downlink transmission, and the first time may include the downlink time between the terminal 101 and the second network element 1032, the processing time of the second network element 1032, and the processing time of the terminal 101.
[0156] In some embodiments, the processing time of terminal 101 may include at least one of the following: the processing time of terminal 101 on the first data stream, the processing time of the first data stream by a downstream device (or device) of terminal 101, and the transmission time between terminal 101 and the downstream device. In one example, terminal 101 does not have a downstream device. In this case, the processing time of terminal 101 may only include the processing time of terminal 101 on the first data stream. In one example, terminal 101 has a downstream device. In this case, the processing time of terminal 101 may include the processing time of terminal 101 on the first data stream, and may also include the processing time of the downstream device, and the transmission time between terminal 101 and the downstream device. In some embodiments, the transmission time between terminal 101 and the downstream device may include at least one of the following: the transmission time from terminal 101 to the downstream device, and the transmission time from the downstream device to terminal 101.
[0157] In some embodiments, the first time may include the processing time of terminal 101, the uplink time from terminal 101 to second network element 1032, the processing time of second network element 1032, and the downlink time from second network element 1032 to terminal 101. In some embodiments, the first time may include the processing time of downstream device, the transmission time from downstream device to terminal 101, the processing time of terminal 101, the uplink time from terminal 101 to second network element 1032, the processing time of second network element 1032, and the downlink time from second network element 1032 to terminal 101. In some embodiments, the first time may include the processing time of terminal 101, the uplink time from terminal 101 to second network element 1032, the processing time of second network element 1032, the downlink time from second network element 1032 to terminal 101, the transmission time from terminal 101 to downstream device, and the processing time of downstream device. In some embodiments, the transmission time from the downstream device to the terminal 101 and the first time may include the processing time of the terminal 101, the uplink time from the terminal 101 to the second network element 1032, the processing time of the second network element 1032, the downlink time from the second network element 1032 to the terminal 101, the transmission time from the terminal 101 to the downstream device, and the processing time of the downstream device.
[0158] In some embodiments, the name of the first information is not limited, and it may be, for example, a request information, an instruction information, etc.
[0159] In some embodiments, the first information may include at least one of the following: QoS parameters of the first service and auxiliary information of the first service. In some embodiments, the first information may be included in the QoS parameters of the first service. For example, the first information may be at least a portion of the QoS parameters of the first service. In some embodiments, the first information may be included in the auxiliary information of the first service. For example, the first information may be a portion of the auxiliary information of the first service.
[0160] In some embodiments, the first information may include at least one of the following: first indication information and first monitoring parameter information. In some embodiments, the first information may indicate at least one of the following: monitoring the first latency; parameters related to the monitoring of the first latency.
[0161] In some embodiments, the first indication information may indicate monitoring of a first time. In some embodiments, the first indication information may be contained in a field. In one example, the first information may include the field, and the field may have a first value or a second value. The first value indicates monitoring of the first time. The second value may indicate not monitoring of the first time. In one example, the field may include the field with the first value, or it may not include the field. The presence of the field indicates monitoring of the first time. The absence of the field indicates not monitoring of the first time.
[0162] In some embodiments, the first monitoring parameter information may indicate parameters related to monitoring at a first time. In some embodiments, the first monitoring parameter information may be used to configure monitoring at a first time.
[0163] In some embodiments, the first monitoring parameter information may include at least one of the following: monitoring type information, monitoring level information, monitoring threshold information, monitoring time information, and monitoring control information. In some embodiments, the parameters related to the monitoring of the first latency may include at least one of the following: the latency type targeted by the monitoring of the first latency, the granularity of the monitoring of the first latency, the maximum value of the monitoring of the first latency, the execution time of the monitoring of the first latency, and the control cycle of the monitoring of the first latency.
[0164] In some embodiments, monitoring type information may indicate the latency type targeted by the initial monitoring. In some embodiments, the initial monitoring may be performed for one or more latency types.
[0165] In some embodiments, the latency type of the first time monitoring may include at least one of the following: the first time, the round-trip latency from terminal 101 to the fourth network element 1034, the uplink latency from terminal 101 to the fourth network element 1034, the downlink latency from the fourth network element 1034 to terminal 101, the processing latency of terminal 101, the processing latency of the downstream device, the round-trip latency from terminal 101 to the downstream device, and the processing latency of the second network element 1032.
[0166] In some embodiments, monitoring level information may indicate the granularity of monitoring at a given moment. In some embodiments, monitoring at the given moment may be performed at the granularity indicated by the monitoring level information.
[0167] In some embodiments, the granularity of the first-time monitoring indicated by the monitoring level information may include at least one of the following: SDF, session, and task. In some embodiments, first-time monitoring may be performed for one or more SDFs. For example, first-time monitoring may be applied to each SDF related to a first business. In some embodiments, first-time monitoring may be performed for one or more sessions. For example, first-time monitoring may be applied to each session related to a first business. In some embodiments, first-time monitoring may be performed for one or more tasks. For example, first-time monitoring may be applied to each task related to a first business.
[0168] In some embodiments, the monitoring threshold information may indicate the maximum value monitored at the first moment. In some embodiments, the maximum value monitored may be the maximum value allowed for a specific latency type.
[0169] In some embodiments, the maximum value of the first monitoring time may include at least one of the following: the maximum value of the first time, the maximum round-trip delay from terminal 101 to the fourth network element 1034, the maximum uplink delay from terminal 101 to the fourth network element 1034, the maximum downlink delay from the fourth network element 1034 to terminal 101, the maximum processing delay of terminal 101, the maximum processing delay of the downstream device, the maximum round-trip delay from terminal 101 to the downstream device, and the maximum processing delay of the second network element 1032.
[0170] In some embodiments, monitoring time information may indicate the execution time of the first-time monitoring. In some embodiments, monitoring time information may be used to determine when the first-time monitoring starts and / or ends. During the execution of the first-time monitoring, the configuration of the first-time monitoring may be applied.
[0171] In some embodiments, the execution time of the first-time monitoring may include at least one of the following: the start time of the first-time monitoring, the end time of the first-time monitoring, and the duration of the first-time monitoring. In some embodiments, the monitoring time information may indicate at least one of the start time, end time, and duration of the first-time monitoring.
[0172] In some embodiments, monitoring and control information may indicate the control cycle for monitoring at a first time. In some embodiments, the control performed on the monitoring at the first time may be periodic. In this case, the control performed on the monitoring at the first time may be reset with a control cycle. In some embodiments, the periodic control of the monitoring at the first time is reset with the control cycle of the monitoring at the first time.
[0173] In some embodiments, the first information may also be used to request that a first time-based QoS process be performed on the first data stream of the first service. In some embodiments, the first information may be used to determine a QoS policy for the first data stream of the first service. This QoS policy may be used to implement first time-based QoS processing for the first data stream. In some embodiments, the first information may be used to apply first time-based QoS processing to the first data stream of the first service.
[0174] In some embodiments, the first information may further include at least one of the following: second indication information and first parameter information.
[0175] In some embodiments, the second indication information may indicate support for the first time. In some embodiments, the second indication information may indicate that the first data stream of the first service supports the first time. In some embodiments, the second indication information may indicate the application of first time-based QoS processing to the first data stream of the first service. In some embodiments, the second indication information may indicate flexible QoS adaptation for supporting the first time.
[0176] In some embodiments, the second indication information may be included in a field. In one example, the first information may include this field, and the field may have a first value or a second value. The first value indicates support for the first time. The second value may indicate that the first time is not supported. In one example, the field may include the field with the first value, or it may not include the field. The presence of the field indicates support for the first time. The absence of the field indicates that the first time is not supported.
[0177] In some embodiments, the first parameter information may indicate parameters related to a first time. In some embodiments, the first time-related parameters may be used to configure QoS processing based on a first time. In some embodiments, the first parameter information may be used to determine relevant parameters for QoS processing based on a first time. In some embodiments, the first parameter information may be used to implement QoS processing based on a first time.
[0178] In some embodiments, the first parameter information may indicate at least one of the following: at least one maximum value of a first time, or at least one duration range of a first time.
[0179] In some embodiments, the first parameter information may indicate one or more maximum values for a first time period. This maximum value can be used to limit the length of the first time period. In other words, the first parameter information can indicate, through the maximum value, that the length of the first time period does not exceed the maximum value. In some embodiments, different maximum values may correspond to different QoS (Quality of Service).
[0180] In some embodiments, the first parameter information may indicate the maximum value at a first time. In some embodiments, the maximum value at a first time may be the maximum value at a first time. For example, the value at a first time may be less than or equal to the maximum value at a first time. For example, the value at a first time may be less than the maximum value at a first time. It is understood that in some embodiments, the first parameter information may indicate one or more maximum values at a first time.
[0181] In some embodiments, the first parameter information may indicate a list of maximum values at a first time. In some embodiments, the list of maximum values at a first time may include one or more maximum values. Different maximum values in the list of maximum values may be different. It is understood that in some embodiments, the first parameter information may indicate one or more lists of maximum values at a first time. Maximum values in different lists of maximum values may be exactly the same, partially the same, or completely different.
[0182] In some embodiments, the first parameter information may indicate one or more duration ranges for a first time period. This duration range can be used to limit the length of the first time period. In some embodiments, the duration range may be determined by a minimum and a maximum value. In other words, the first parameter information can indicate, through the duration range, that the length of the first time period is not less than the minimum value and not greater than the maximum value. In some embodiments, different duration ranges may correspond to different QoS (Quality of Service).
[0183] In some embodiments, the first parameter information may indicate a duration range of a first time period. In some embodiments, the duration range of the first time period may be defined by a lower limit and a maximum value of the first time period. In one example, the first parameter information may include a lower limit and a maximum value of the first time period to indicate a duration range. It is understood that in some embodiments, the first parameter information may indicate one or more duration ranges of the first time period. At least one of the maximum and lower limits of different duration ranges may be different. For example, different duration ranges may partially overlap or not overlap.
[0184] In some embodiments, the first parameter information in the first information may include one or more maximum values at a first time. In some embodiments, the first parameter information in the first information may include a list of one or more maximum values at a first time. In some embodiments, the first parameter information in the first information may include one or more duration ranges at a first time. In some embodiments, the first parameter information in the first information may include one or more maximum values at a first time, and a list of one or more maximum values at a first time. In some embodiments, the first parameter information in the first information may include one or more maximum values at a first time, and a list of one or more maximum values at a first time, and a range of one or more durations at a first time. In some embodiments, the first parameter information in the first information may include one or more maximum values at a first time, a list of one or more maximum values at a first time, and a range of one or more durations at a first time.
[0185] In some embodiments, the second network element 1032 may send first information through an AF QoS request process or an AF QoS update process. In some embodiments, the first information may be carried in a request message. For example, the first information may be carried in an AF request. In some embodiments, the second network element 1032 may send an AF session resource request. This AF session resource request may carry the first information. In some embodiments, the AF session resource request may be an AF session resource creation request. For example, the AF session resource request may be an Nnef_AFSessionwithQoS_Create request message. In some embodiments, the AF session resource request may be an AF session resource update request. For example, the AF session resource request may be an Nnef_AFSessionwithQoS_Update request message.
[0186] In some embodiments, the first information may be included in the QoS requirements of the first data stream for the first service. In some embodiments, the second network element 1032 may send an AF request to the fifth network element 1035, the AF request may carry the QoS requirements of the first data stream of the first service, and the QoS requirements may include the first information. In some embodiments, the first information may be independent of the QoS requirements.
[0187] In some embodiments, while sending the first information, the second network element 1032 may also send service information of the first service to the fifth network element 1035. The service information may include at least one of the following: QoS requirements, the identifier of terminal 101, the address of terminal 101, the identifier of the second network element 1032, the identifier of the first service, flow description, data network name (DNN), single network slice selection assistance information (S-NSSAI), and QoS parameters. It should be noted that the second network element 1032 may also send other information to the fifth network element 1035, but this embodiment does not specifically limit this.
[0188] In step S202, the fifth network element 1035 performs the authorization.
[0189] In some embodiments, the fifth network element 1035 can authorize a request message carrying first information. In some embodiments, the fifth network element 1035 can authorize first information from the second network element 1032.
[0190] In some embodiments, the second network element 1032 may be an unauthorized network element, in which case the fifth network element 1035 may authorize the request message from the second network element 1032.
[0191] In some embodiments, the second network element 1032 may be an authorized network element, in which case the fifth network element 1035 may not need to authorize the request message from the second network element 1032. In other words, step S202 may be omitted.
[0192] In step S203, the fifth network element 1035 sends the first information to the first network element 1031.
[0193] In some embodiments, the fifth network element 1035 can send first information. In some embodiments, the first information can be sent by the fifth network element 1035, but is not limited thereto, and can also be sent by other entities.
[0194] In some embodiments, the first network element 1031 can receive the first information. In some embodiments, the first information can be received by the first network element 1031, but is not limited thereto, and can also be received by other entities.
[0195] In some embodiments, the fifth network element 1035 may send first information to the first network element 1031. In some embodiments, the fifth network element 1035 may also send at least one of the following to the first network element 1031: the identifier of the first service, the address and / or identifier of the terminal 101, the identifier of the second network element 1032, the application identifier of the first service, the flow description, the DNN, the S-NSSAI, the QoS parameters, and the QoS requirements.
[0196] In some embodiments, the fifth network element 1035 can send the first information in different ways.
[0197] In some embodiments, the fifth network element 1035 may send the first information in the following ways: by sending via time-sensitive communication and time synchronization function (TSCTSF) or by sending directly.
[0198] In some embodiments, the fifth network element 1035 can send the first information to the first network element 1031 via TCSTSF.
[0199] In some embodiments, the fifth network element 1035 can send the first information to the TSCTSF via the service-based interface Ntsftsf, and then the TSCTSF can send the first information to the first network element 1031 via the service-based interface Npcf. In one example, the fifth network element 1035 can send the first information to the TSCTSF via an Ntsctsf_QoSandTSCAssistance_Create request message or an Ntsctsf_QoSandTSCAssistance_Update request message, and then the TSCTSF can send the first information to the first network element 1031 via an Npcf_PolicyAuthorization_Create request message or an Npcf_PolicyAuthorization_Update request message.
[0200] In some embodiments, the fifth network element 1035 can directly send the first information to the first network element 1031.
[0201] In some embodiments, the fifth network element 1035 can send the first information to the first network element 1031 through the service-based interface Npcf. In one example, the fifth network element 1035 can send the first information to the first network element 1031 through an Npcf_PolicyAuthorization_Create request message or an Npcf_PolicyAuthorization_Update request message.
[0202] It is understood that through steps S201 to S203, the first network element 1031 can obtain the first information from the second network element 1032. In some embodiments, the first network element 1031 can obtain the first information through other means. In this case, steps S201 to S203 can be omitted. In one example, the first network element 1031 can determine the first information based on configuration information. For example, the first network element 1031 can determine the first information based on its own operator policy, and / or operations, administration and maintenance (OAM) configuration, and / or local configuration.
[0203] In step S204, the first network element 1031 performs a strategy decision.
[0204] In some embodiments, the first network element 1031 may perform policy decisions based on the received first information, and / or service information of the first service, and / or configuration information of the first network element 1031. In some embodiments, through policy decisions, the first network element 1031 may determine the supported PDU set types.
[0205] In some embodiments, the service information of the first service may include a service level agreement (SLA) related to the first service.
[0206] In some embodiments, the configuration information of the first network element 1031 may include at least one of the following: local configuration, operator policy, and OAM configuration of the first network element 1031.
[0207] In some embodiments, the configuration information of the first network element 1031 may include at least one of the following: first information and priority information.
[0208] In some embodiments, the configuration information of the first network element 1031 may include first information. In this case, the first network element 1031 may not receive the first information provided by the second network element 1032. The first information may be obtained from the configuration information, or the first information may be determined based on the configuration information.
[0209] In some embodiments, the configuration information of the first network element 1031 may include priority information.
[0210] In some embodiments, priority information may indicate the priority between adopting the first time and not adopting the first time. For example, the priority information may indicate the priority of adopting the first time and the priority of not adopting the first time. In this case, the priority information may be used to determine whether to support the first time. In other words, the priority may be used to determine a preference for supporting the first time.
[0211] In some embodiments, priority information may indicate a priority that is measured and provided by a fourth network element 1034 at a first time, and / or a priority that is provided by a second network element 1032 at a first time.
[0212] In some embodiments, step S204 may include: the first network element 1031 authorizing the first data stream of the first service. In some embodiments, the first network element 1031 may perform authorization for the first data stream based at least on first information. In some embodiments, the first network element 1031 may authorize the first data stream of the first service based on at least one of the first information, the service information of the first service, and the configuration information of the first network element 1031.
[0213] In some embodiments, step S204 may include: the first network element 1031 determining a first rule. In some embodiments, the first rule may be determined by the first network element 1031 when authorizing a first data flow of a first service. In some embodiments, the first network element 1031 may determine the first rule based on at least one of first information, service information of the first service, and configuration information of the first network element 1031.
[0214] In some embodiments, the first rule determined by the first network element 1031 may be a new first rule. In some embodiments, the first rule determined by the first network element 1031 may be an updated first rule.
[0215] In some embodiments, the first rule may be a policy and charging control (PCC) rule.
[0216] In some embodiments, the first network element 1031 may send an authorization result to the second network element 1032. In some embodiments, the authorization result may be that the AF request of the second network element 1032 has been authorized. In some embodiments, the first network element 1031 may send a response message to the fifth network element 1035. For example, the first network element 1031 may send an Npcf_PolicyAuthorization_Update response message to the fifth network element 1035. In some embodiments, the fifth network element 1035 may send a response message to the second network element 1032. For example, the fifth network element 1035 may send an Nnef_AFsessionWithQoS_Create response message or an Nnef_AFSessionWithQoS_Update response message to the second network element 1032. These response messages may carry the authorization result of the first network element 1031.
[0217] In step S205, the first network element 1031 sends the second information to the third network element 1033.
[0218] In some embodiments, the first network element 1031 may send second information. In some embodiments, the second information may be sent by the first network element 1031, but is not limited thereto, and may also be sent by other entities.
[0219] In some embodiments, the third network element 1033 may receive the second information. In some embodiments, the second information may be received by the third network element 1033, but is not limited thereto, and may also be received by other entities.
[0220] In some embodiments, the second information may be sent when the first network element 1031 determines that it has authorized the first data stream of the first service.
[0221] In some embodiments, the second information can be used to perform monitoring of the first time. In some embodiments, the second information can be used to perform monitoring and reporting of the first data stream of the first service in the first time.
[0222] In some embodiments, the second information may be determined based on at least one of the following: the first information, the service information of the first service, and the configuration information of the first network element 1031.
[0223] In some embodiments, the second information may include at least one of the following: second monitoring parameter information, monitoring policy information, monitoring activation information, and monitoring object association information. In some embodiments, the second information may indicate at least one of the following: authorization parameters related to the monitoring of the first latency; execution policy for monitoring the first latency; activation of monitoring of the first latency; and keywords associated with at least one of the following: at least one business data flow SDF, at least one session, and at least one task.
[0224] In some embodiments, the second monitoring parameter information may indicate authorized parameters related to monitoring at a first time. In some embodiments, the second monitoring parameter information may be monitoring parameter information authorized by the first network element 1031. In some embodiments, the monitoring parameter information in the second information may be determined based on the first monitoring parameter information in the first information and / or the configuration information of the first network element 1031.
[0225] In some embodiments, the second monitoring parameter information may include at least one of the following: monitoring type information, monitoring level information, monitoring threshold information, monitoring time information, and monitoring control information. In some embodiments, the second monitoring parameter information may include some or all of the contents of the first monitoring parameter information. In some embodiments, the authorization parameters related to the monitoring of the first latency may include at least one of the following: the latency type targeted by the monitoring of the first latency, the granularity of the monitoring of the first latency, the maximum value of the monitoring of the first latency, the execution time of the monitoring of the first latency, and the control cycle of the monitoring of the first latency. In some embodiments, the content of the second monitoring parameter information may differ from the content of the first monitoring parameter information, and this disclosure does not specifically limit this aspect.
[0226] In some embodiments, the monitoring policy information may indicate the monitoring policy for the first-time monitoring. In some embodiments, the monitoring policy information may be used to determine the monitoring policy adopted for the first-time monitoring. In some embodiments, the monitoring policy indicated by the monitoring policy information may be authorized by the first network element 1031.
[0227] In some embodiments, monitoring policy information may be included in a first rule. In some embodiments, the monitoring policy may be part of a first rule. In some embodiments, monitoring parameter information may be included in the monitoring policy indicated by the monitoring policy information.
[0228] In some embodiments, monitoring activation information can be used to activate monitoring at a first time. In some embodiments, in step S204, the first network element 1031 can determine whether to activate monitoring at a first time and / or the time of activation of monitoring at a first time. In some embodiments, if it is determined that monitoring at a first time is activated, the second information may include monitoring activation information. In some embodiments, monitoring activation information may indicate at least one of the following: activation of monitoring at a first time, and the time of activation of monitoring at a first time. In some embodiments, monitoring activation information may indicate at least one of the following: activation time, and activation period. In one example, the activation time may be the moment when monitoring at a first time is activated. For example, monitoring activation information may indicate a moment as the activation time. In one example, the activation period may be the time period during which monitoring at a first time is activated. For example, monitoring activation information may indicate a start time and an end time, then the time period between the start time and the end time is the activation period. For example, monitoring activation information may indicate a start time and a duration, then the time period from the start time to the end of the duration is the activation period. In some embodiments, monitoring activation information may by default indicate immediate activation of monitoring at a first time. For example, monitoring activation information can indicate the activation of the first-time monitoring, so the first-time monitoring can be activated immediately.
[0229] In some embodiments, the monitored object association information may indicate keywords associated with the monitored object. In some embodiments, the monitored object may include one or more SDFs, one or more sessions, or one or more tasks. In some embodiments, the monitored object may include one or more SDFs, and the keywords indicated by the monitored object association information may be associated with the SDF group, and / or terminal, and / or session where the monitored one or more SDFs reside. In some embodiments, the monitored object may include one or more sessions, and the keywords indicated by the monitored object association information may be associated with the SDF, and / or SDF group, and / or terminal where the monitored one or more sessions reside. In some embodiments, the monitored object may include one or more tasks, and the keywords indicated by the monitored object association information may be associated with the SDF, and / or SDF group, and / or terminal, and / or session where the monitored one or more tasks reside.
[0230] In some embodiments, keywords can be used to monitor one or more monitored objects in a group corresponding to a keyword in real time. For example, the group associated with the keyword can be SDF, SDF group, terminal, session, etc.
[0231] In some embodiments, the monitoring object association information may indicate one or more keywords.
[0232] In some embodiments, the second information may further include first indication information. In some embodiments, the first indication information may be obtained from the first information. In some embodiments, the first indication information may be determined based on the first information.
[0233] In some embodiments, the second information may further include at least one of the following: third indication information, second parameter information, and delay information.
[0234] In some embodiments, the third indication information may indicate the performance of QoS processing based on the first time. In some embodiments, the third indication information in the second information may indicate support for the first time. In some embodiments, the third indication information may indicate support for QoS processing based on the first time. In some embodiments, the third indication information may be determined based on the first information.
[0235] In some embodiments, the second parameter information may indicate authorization parameters related to the first time. In some embodiments, the second parameter information may indicate at least one of the following: at least one maximum value of the first time, at least one duration range of the first time. In some embodiments, the second parameter information in the second information may indicate at least one of the following: the maximum value of the first time, a list of maximum values of the first time, and the duration range of the first time.
[0236] In some embodiments, the second parameter information may be the same as or partially the same as the first parameter information included in the first information. In one example, the maximum value of the first time indicated by the second parameter information may include some or all of the maximum values of the first time indicated by the first parameter information in the first information. For example, if the first parameter information in the first information indicates a single maximum value, then the second parameter information may indicate that maximum value. For example, if the first parameter information in the first information indicates multiple maximum values, then the second parameter information may indicate one or more of the multiple maximum values. In one example, the list of maximum values of the first time indicated by the second parameter information may include some or all of the list of maximum values of the first time indicated by the first parameter information in the first information. For example, if the first parameter information in the first information indicates a list of maximum values, then the second parameter information may indicate that list of maximum values. For example, if the first parameter information in the first information indicates multiple maximum value lists, then the second parameter information may indicate one or more of the multiple maximum values. In one example, the maximum value of the first time indicated by the second parameter information may include some or all of the maximum values in the list of maximum values of the first time indicated by the first parameter information in the first information. In one example, the duration range of the first time indicated by the second parameter information may include some or all of the duration range of the first time indicated by the first parameter information in the first information. For example, if the first parameter information in the first information can indicate a duration range, then the second parameter information can indicate that duration range. For example, if the first parameter information in the first information can indicate multiple duration ranges, then the second parameter information can indicate one or more duration ranges among the multiple duration ranges.
[0237] In some embodiments, the second parameter information may differ from the first parameter information included in the first information. In one example, the maximum value of the first time indicated by the second parameter information may differ from the maximum value of the first time indicated by the first parameter information in the first information. For example, the first parameter information in the first information may indicate one or more maximum values, then the maximum value indicated by the second parameter information may differ from these maximum values indicated by the first information. In one example, the list of maximum values of the first time indicated by the second parameter information may differ from the list of maximum values of the first time indicated by the first parameter information in the first information. For example, the first parameter information in the first information may indicate one or more maximum value lists, then the list of maximum values indicated by the second parameter information may differ from these maximum value lists indicated by the first information. In one example, the first parameter information in the first information may indicate one or more maximum value lists, then the maximum value indicated by the second parameter information may not belong to these maximum value lists indicated by the first information. In one example, the duration range of the first time indicated by the second parameter information may differ from the duration range of the first time indicated by the first parameter information in the first information. For example, the first parameter information in the first information may indicate one or more duration ranges, then the duration range indicated by the second parameter information may differ from these duration ranges indicated by the first information.
[0238] In some embodiments, the latency information may be determined by the first information. In some embodiments, the latency information may include a latency QoS parameter mapped by a first time. This latency QoS parameter may be the latency of the entire stage and / or some nodes in the transmission and processing of the first data stream for the first service. For example, the latency QoS parameter may be derived based on the first information.
[0239] In some embodiments, the delay information of the first service may indicate at least one of the following: round-trip delay from terminal 101 to second network element 1032, uplink delay from terminal 101 to second network element 1032, downlink delay from second network element 1032 to terminal 101, delay of terminal 101, and delay of second network element 1032.
[0240] In some embodiments, the round-trip delay from terminal 101 to the second network element 1032 is generated by the process of the first data stream returning to terminal 101 from terminal 101 via the second network element 1032. In some embodiments, the uplink delay from terminal 101 to the second network element 1032 is generated by the process of the first data stream arriving at the second network element 1032 from terminal 101. In some embodiments, the downlink delay from the second network element 1032 to terminal 101 is generated by the process of the first data stream arriving at the terminal 101 from the second network element 1032. In some embodiments, the delay of the second network element 1032 may be generated by the processing of the first data stream by the second network element 1032.
[0241] In some embodiments, terminal 101 does not have a downstream device. In this case, the latency of terminal 101 only includes the processing latency of terminal 101. In some embodiments, the round-trip latency from terminal 101 to the second network element 1032 may include: the processing latency of terminal 101, the transmission latency from terminal 101 to the second network element 1032, the processing latency of the second network element 1032, and the transmission latency from the second network element 1032 to terminal 101. In some embodiments, the uplink latency from terminal 101 to the second network element 1032 may include: the processing latency of terminal 101, the transmission latency from terminal 101 to the second network element 1032, and the processing latency of the second network element 1032. In some embodiments, the uplink latency from terminal 101 to the second network element 1032 may include: the processing latency of terminal 101, the transmission latency from the second network element 1032 to terminal 101, and the processing latency of the second network element 1032.
[0242] In some embodiments, terminal 101 has a downstream device. In this case, the latency of terminal 101 may include at least one of the following: the processing latency of terminal 101, the processing latency of the downstream device, the round-trip latency from the downstream device to terminal 101, the uplink latency from the downstream device to terminal 101, and the downlink latency from terminal 101 to the downstream device.
[0243] In some embodiments, the processing latency of terminal 101 is generated by the processing of the first data stream by terminal 101. In some embodiments, the processing latency of the downstream device is generated by the processing of the first data stream by the downstream device. In some embodiments, the round-trip latency from the downstream device to terminal 101 is generated by the process of the first data stream returning to terminal 101 from terminal 101 via the downstream device. In some embodiments, the uplink latency from the downstream device to terminal 101 is generated by the process of the first data stream arriving at terminal 101 from the downstream device. In some embodiments, the downlink latency from terminal 101 to the downstream device is generated by the process of the first data stream arriving at the downstream device from terminal 101.
[0244] In some embodiments, the round-trip delay from the downstream device to the terminal 101 may include: the processing delay of the terminal 101, the transmission delay from the terminal 101 to the downstream device, the processing delay of the downstream device, and the transmission delay from the downstream device to the terminal 101. In some embodiments, the uplink delay from the downstream device to the terminal 101 may include: the processing delay of the terminal 101, the processing delay of the downstream device, and the transmission delay from the downstream device to the terminal 101. In some embodiments, the downlink delay from the terminal 101 to the downstream device may include: the processing delay of the terminal 101, the processing delay of the downstream device, and the transmission delay from the terminal 101 to the downstream device.
[0245] In some embodiments, terminal 101 may have a downstream device, and the first data stream originates from and terminates at terminal 101. In one example, the round-trip delay from terminal 101 to the second network element 1032 may include: processing delay of terminal 101, transmission delay from terminal 101 to the second network element 1032, processing delay of the second network element 1032, transmission delay from the second network element 1032 to terminal 101, transmission delay from terminal 101 to the downstream device, processing delay of the downstream device, and transmission delay from the downstream device to terminal 101. In one example, the uplink delay from terminal 101 to the second network element 1032 may include: processing delay of terminal 101, transmission delay from terminal 101 to the second network element 1032, processing delay of the second network element 1032, transmission delay from terminal 101 to the downstream device, processing delay of the downstream device, and transmission delay from the downstream device to terminal 101. In one example, the downlink delay from the second network element 1032 to the terminal 101 may include: the processing delay of the terminal 101, the transmission delay from the second network element 1032 to the terminal 101, the processing delay of the second network element 1032, the transmission delay from the terminal 101 to the downstream device, the processing delay of the downstream device, and the transmission delay from the downstream device to the terminal 101.
[0246] In some embodiments, terminal 101 may have a downstream device, and the first data stream originates from and terminates at the downstream device. In one example, the round-trip delay from terminal 101 to the second network element 1032 may include: processing delay of terminal 101, transmission delay from terminal 101 to the second network element 1032, processing delay of the second network element 1032, transmission delay from the second network element 1032 to terminal 101, transmission delay from terminal 101 to the downstream device, processing delay of the downstream device, and transmission delay from the downstream device to terminal 101. In one example, the uplink delay from terminal 101 to the second network element 1032 may include: processing delay of the downstream device, transmission delay from the downstream device to terminal 101, processing delay of terminal 101, transmission delay from terminal 101 to the second network element 1032, and processing delay of the second network element 1032. In one example, the downlink delay from the second network element 1032 to the terminal 101 may include: the processing delay of the second network element 1032, the transmission delay from the second network element 1032 to the terminal 101, the processing delay of the terminal 101, the transmission delay from the terminal 101 to the downstream device, and the processing delay of the downstream device.
[0247] In some embodiments, the second information may be carried in the first rule. In some embodiments, the first network element 1031 may send the first rule, which includes the second information, to the third network element 1033.
[0248] In some embodiments, the second information may be independent of the first rule. In this case, the second information may be sent to the third network element 1033 together with the first rule, or it may be sent to the third network element 1033 separately.
[0249] In some embodiments, the first network element 1031 can send second information to the third network element 1033 through the service-based interface Npcf.
[0250] In some embodiments, the first network element 1031 can initiate an SM policy association modification process. In some embodiments, the first network element 1031 can send an SM policy association modification request message to the third network element 1033. In one example, the first network element 1031 can send second information to the third network element 1033 via an Npcf_SMPolicyControl_UpdateNotify request message.
[0251] In some embodiments, in response, the third network element 1033 may send an SM policy association modification response message to the first network element 1031. In one example, the third network element 1033 may send an Npcf_SMPolicyControl_UpdateNotify response message to the first network element 1031.
[0252] In some embodiments, upon receiving the first rule, the third network element 1033 can determine at least one of the following based on the first rule: QoS profile, QoS rules, and N4 rules. For example, N4 rules may include packet detection rules (PDR), packet delivery rules, QoS enforcement rules (QER), frame error rate (FER) rules, etc. In some embodiments, the QoS profile is used by the first device 102 to perform QoS processing. In some embodiments, the QoS rules are used by the terminal 101 to perform QoS processing. In some embodiments, the N4 rules are used by the fourth network element 1034 to perform QoS processing.
[0253] In some embodiments, the third network element 1033 may consider second information when determining at least one of QoS configuration, QoS rules, and N4 rules. In some embodiments, the QoS configuration may be determined based on the first rule and the second information.
[0254] In some embodiments, in addition to the first rule, the third network element 1033 may also consider its configuration information when determining QoS configuration, QoS rules, and N4 rules. In some embodiments, the configuration information of the third network element 1033 may include at least one of the following: local configuration, operator policy, and OAM configuration.
[0255] In some embodiments, upon receiving the second information, the third network element 1033 can configure the monitoring for the first time. In some embodiments, the third network element 1033 can generate a configuration for the monitoring for the first time.
[0256] In some embodiments, the third network element 1033 may determine third information. In some embodiments, the third information may be determined based on the second information and / or the configuration information of the third network element 1033.
[0257] In some embodiments, the third information can be used to configure the monitoring and reporting in real time. In some embodiments, the third information can be used to provide the configuration for the monitoring and reporting in real time.
[0258] In some embodiments, the third information may be used to instruct the provision of the first-time (monitored) measurement information to the fourth network element 1034. In some embodiments, the third information may instruct the first-time measurement information to be sent to the fourth network element 1034 via the user plane.
[0259] In some embodiments, the third information may include at least one of the following: monitoring object association information and first rule information.
[0260] In some embodiments, the first rule information may indicate the rules for measurement and reporting in the first instance, for example, referred to as the first reporting rule. This rule enables monitoring and reporting in the first instance.
[0261] In some embodiments, the first rule information may be determined based on the second information and / or the configuration information of the third network element 1033.
[0262] In some embodiments, the first rule information may include at least one of the following: a first rule identifier; a reporting trigger event; a periodic measurement threshold; a measurement threshold for a first time; a measurement threshold for the round-trip delay from terminal 101 to the fourth network element 1034; a measurement threshold for the uplink delay from terminal 101 to the fourth network element 1034; a measurement threshold for the downlink delay from the fourth network element 1034 to terminal 101; a measurement threshold for the processing time of the terminal; a measurement threshold for the processing delay of the downstream device; a measurement threshold for the round-trip delay from terminal 101 to the downstream device; a measurement threshold for the processing delay of the second network element 1032; a second rule identifier of one or more second rule information associated with the first rule information; and the delay type for which the first time measurement is performed.
[0263] In some embodiments, a first rule identifier may be used to identify a first reporting rule. In some embodiments, the first reporting rule may be uniquely identified by the first rule identifier.
[0264] In some embodiments, the initial reporting can be periodic. For example, initial reporting can be performed according to a specific cycle. The reporting cycle for the initial time can be set as needed, such as one hour, one day, one week, etc. In some embodiments, the periodic measurement threshold can be the time period for the periodic reporting of the initial time. In some embodiments, the periodic measurement threshold can be the time point for the periodic reporting of the initial time. For example, the periodic measurement threshold can indicate a specific time within a day, a specific time within a week, etc.
[0265] In some embodiments, the first time measurement threshold may refer to the time when the measurement value reaches or exceeds the first time measurement threshold, at which time a first time reporting is performed.
[0266] In some embodiments, the measurement threshold for the round-trip delay between terminal 101 and the fourth network element 1034 may refer to the time when the measured value of the round-trip delay between terminal 101 and the fourth network element 1034 reaches or exceeds the measurement threshold, at which time a first-time report is performed.
[0267] In some embodiments, the uplink delay measurement threshold between terminal 101 and the fourth network element 1034 may refer to the time when the measured value of the uplink delay between terminal 101 and the fourth network element 1034 reaches or exceeds the measurement threshold, at which time a first-time reporting is performed.
[0268] In some embodiments, the measurement threshold for the downlink delay from the fourth network element 1034 to the terminal 101 may refer to the time when the measured value of the downlink delay between the terminal 101 and the fourth network element 1034 reaches or exceeds the measurement threshold, at which point a first-time reporting is performed.
[0269] In some embodiments, the measurement threshold for the processing delay of terminal 101 may refer to the time when the measured value of the processing delay of terminal 101 reaches or exceeds the measurement threshold, at which time a first-time report is performed.
[0270] In some embodiments, the measurement threshold for the processing delay of the downstream device may refer to the time when the measured value of the processing delay of the downstream device reaches or exceeds the measurement threshold, at which point a first-time report is performed.
[0271] In some embodiments, the measurement threshold for the round-trip delay from terminal 101 to the downstream device may refer to the time when the measured value of the round-trip delay from terminal 101 to the downstream device reaches or exceeds the measurement threshold, at which point a first-time reporting is performed.
[0272] In some embodiments, the measurement threshold for the processing delay of the second network element 1032 may refer to the time when the measured value of the processing delay of the second network element 1032 reaches or exceeds the measurement threshold, at which time a first-time reporting is performed.
[0273] It should be noted that the magnitudes of the various measurement thresholds indicated in the first rule information may be the same as or different from the corresponding maximum values monitored at the first time. For example, the measurement thresholds at the first time in the first rule information may be the same as or different from the maximum values at the first time indicated in the second information. For example, the measurement threshold for the round-trip delay between terminal 101 and the fourth network element 1034 in the first rule information may be the same as or different from the maximum value of the round-trip delay between terminal 101 and the fourth network element 1034 indicated in the second information. For example, the measurement threshold for the uplink delay between terminal 101 and the fourth network element 1034 in the first rule information may be the same as or different from the maximum value of the uplink delay between terminal 101 and the fourth network element 1034 indicated in the second information. For example, the measurement threshold for the downlink delay between the fourth network element 1034 and terminal 101 in the first rule information may be the same as or different from the maximum value of the downlink delay between the fourth network element 1034 and terminal 101 indicated in the second information. For example, the measurement threshold for the processing latency of terminal 101 in the first rule information may be the same as or different from the maximum value of the processing latency of terminal 101 indicated in the second information. For example, the measurement threshold for the processing latency of the downstream device in the first rule information may be the same as or different from the maximum value of the processing latency of the downstream device indicated in the second information. For example, the measurement threshold for the round-trip latency from terminal 101 to the downstream device in the first rule information may be the same as or different from the maximum value of the round-trip latency from terminal 101 to the downstream device indicated in the second information. For example, the measurement threshold for the processing latency of the second network element 1032 in the first rule information may be the same as or different from the maximum value of the processing latency of the second network element 1032 indicated in the second information.
[0274] In some embodiments, a reporting trigger event may include one or more events for triggering a first-time reporting. For example, a first-time reporting may be performed when an event is triggered. In some embodiments, a reporting trigger event may include at least one of the following: traffic detection start, traffic detection stop, reaching a periodic measurement threshold, reaching a first-time measurement threshold, reaching a round-trip delay measurement threshold from terminal 101 to the fourth network element 1034, reaching an uplink delay measurement threshold from terminal 101 to the fourth network element 1034, reaching a downlink delay measurement threshold from the fourth network element 1034 to terminal 101, reaching a processing delay measurement threshold from terminal 101, reaching a processing delay measurement threshold from a downstream device, reaching a round-trip delay measurement threshold from terminal 101 to a downstream device, reaching a processing delay measurement threshold from the second network element 1032, immediate reporting, measurement of marked traffic, or receiving a data packet with an end marker.
[0275] In some embodiments, there may be a mapping relationship between the first reporting rule indicated by the first rule information and the keyword indicated by the monitoring object association information. In some embodiments, each keyword may be mapped to a first reporting rule. In some embodiments, the third network element 1033 may determine the corresponding first reporting rule for each keyword.
[0276] In some embodiments, the first rule information may include one or more second rule identifiers. Each second rule identifier indicates a second reporting rule that may be associated with a first reporting rule. Based on the first reporting rule and the one or more second reporting rules, a combined reporting of the first time event can be performed. For example, if a reporting trigger event in either the first or second reporting rule is triggered, a combined reporting of the first time event can be performed based on the first and second reporting rules.
[0277] In some embodiments, the type of delay for the first time measurement can indicate the type of delay to be measured. For example, the type of delay to be measured can include at least one of the following: the first time; the round-trip delay from terminal 101 to the fourth network element 1034; the uplink delay from terminal 101 to the fourth network element 1034; the downlink delay from the fourth network element 1034 to terminal 101; the processing time of terminal 101; the processing delay of the downstream device; the round-trip delay from terminal 101 to the downstream device; and the processing delay of the second network element 1032.
[0278] In step S206, the third network element 1033 sends third information to the fourth network element 1034.
[0279] In some embodiments, the third network element 1033 can send third information. In some embodiments, the third information can be sent by the third network element 1033, but is not limited to this, and can also be sent by other entities.
[0280] In some embodiments, the fourth network element 1034 may receive third information. In some embodiments, the third information may be received by the fourth network element 1034, but is not limited thereto, and may also be received by other entities.
[0281] In some embodiments, the third information may be carried in the N4 rule. In some embodiments, the third network element 1033 may send the N4 rule, which includes the third information, to the fourth network element 1034. In some embodiments, the third information may be independent of the N4 rule. In this case, the third information may be sent to the fourth network element 1034 together with the N4 rule, or it may be sent to the fourth network element 1034 separately.
[0282] In some embodiments, the third network element 1033 can send third information to the fourth network element 1034 through the N4 session establishment process. In one example, the third network element 1033 can send an N4 session establishment request message to the fourth network element 1034. This N4 session establishment request message can carry third information. In one example, in response to the N4 session establishment request message, the fourth network element 1034 can send an N4 session establishment response message to the third network element 1033.
[0283] In some embodiments, the third network element 1033 can send third information to the fourth network element 1034 through the N4 session modification process. In one example, the third network element 1033 can send an N4 session modification request message to the fourth network element 1034. This N4 session modification request message can carry the third information. In one example, in response to the N4 session modification request message, the fourth network element 1034 can send an N4 session modification response message to the third network element 1033.
[0284] In step S207, the third network element 1033 sends third information to the sixth network element 1036.
[0285] In some embodiments, the third network element 1033 can send third information. In some embodiments, the third information can be sent by the third network element 1033, but is not limited to this, and can also be sent by other entities.
[0286] In some embodiments, the sixth network element 1036 can receive third information. In some embodiments, the third information can be received by the sixth network element 1036, but is not limited thereto, and can also be received by other entities.
[0287] In some embodiments, the third information may be carried in at least one of the following: QoS configuration and QoS rules.
[0288] In some embodiments, the third information may be carried in the QoS configuration. In some embodiments, the third network element 1033 may send the QoS configuration, which includes the third information, to the sixth network element 1036. In some embodiments, the third information may be independent of the QoS configuration. In this case, the third information may be sent to the sixth network element 1036 together with the QoS configuration, or it may be sent separately to the sixth network element 1036.
[0289] In some embodiments, the third information may be carried in the QoS rules. In some embodiments, the third network element 1033 may send QoS rules, which include the third information, to the sixth network element 1036. In some embodiments, the third information may be independent of the QoS rules. In this case, the third information may be sent to the sixth network element 1036 together with the QoS rules, or it may be sent to the sixth network element 1036 separately.
[0290] In some embodiments, the third network element 1033 can provide third information to the sixth network element 1036 through the Namf_Communication_N1N2MessageTransfer procedure. In one example, the third network element 1033 can initiate Namf_Communication_N1N2MessageTransfer, which carries the third information.
[0291] In some embodiments, the third network element 1033 can send N2 SM information to the sixth network element 1036 via Namf_Communication_N1N2MessageTransfer. In one example, the N2 SM information may include at least one of the following: QoS flow identifier (QFI), PDU session identifier, and QoS configuration.
[0292] In step S208, the sixth network element 1036 sends third information to the first device 102.
[0293] In some embodiments, the sixth network element 1036 can send third information. In some embodiments, the third information can be sent by the sixth network element 1036, but is not limited to this; it can also be sent by other entities.
[0294] In some embodiments, the first device 102 may receive third information. In some embodiments, the third information may be received by the first device 102, but is not limited thereto, and may also be received by other entities.
[0295] In some embodiments, the third information may be carried in the QoS configuration and / or QoS rules, or it may be independent of the QoS configuration and QoS rules.
[0296] In some embodiments, the sixth network element 1036 may send an N2 message to the first device 102, which carries third information.
[0297] In step S209, the first device 102 sends third information to the terminal 101.
[0298] In some embodiments, the first device 102 may send third information. In some embodiments, the third information may be sent by the first device 102, but is not limited thereto, and may also be sent by other entities.
[0299] In some embodiments, terminal 101 may receive third information. In some embodiments, the third information may be received by terminal 101, but is not limited thereto, and may also be received by other entities.
[0300] In some embodiments, the third information may be carried in the QoS rules or may be independent of the QoS rules.
[0301] In some embodiments, the first device 102 may send an AS message to the terminal 101, which includes third information.
[0302] In step S210, the terminal 101 and the second network element 1032 interact with each other using the first data stream.
[0303] In some embodiments, the first data stream of the first service can be transmitted between terminal 101 and second network element 1032. In some embodiments, the first data stream can be transmitted on at least one of the user plane, data plane, and control plane.
[0304] In some embodiments, in the uplink direction, terminal 101 may send a first data stream to second network element 1032. The first data stream sent in the uplink direction may be referred to as an uplink data stream. In some embodiments, the first data stream sent by terminal 101 may sequentially pass through first device 102 and fourth network element 1034, and arrive at second network element 1032. In some embodiments, terminal 101 may perform QoS processing based on a first time on the first data stream. In some embodiments, the QoS processing performed by terminal 101 may be implemented based on third information.
[0305] In some embodiments, terminal 101 determines that a first data stream is to be sent. In some embodiments, the first data stream may be an uplink data stream. In some embodiments, terminal 101 may perform QoS processing on the first data stream of a first service based on received third information and / or QoS rules. In some embodiments, the QoS processing performed by terminal 101 may be QoS processing based on a first time. In some embodiments, terminal 101 may perform QoS processing based on a first time based on third information and / or N4 rules. In some embodiments, the QoS processing performed by terminal 101 may include QoS implementation. In some embodiments, terminal 101 may perform QoS processing based on a first time based on at least one of second indication information, parameter information at a first time, and delay information of the first service.
[0306] In some embodiments, in the downlink direction, the second network element 1032 can send a first data stream to the terminal 101. The first data stream sent in the downlink direction can be referred to as a downlink data stream. In some embodiments, the first data stream sent by the second network element 1032 can sequentially pass through the fourth network element 1034 and the first device 102 before reaching the terminal 101. In some embodiments, the fourth network element 1034 and the first device 102 can perform QoS processing based on a first time on the first data stream. In some embodiments, the QoS processing performed by each of the fourth network element 1034 and the first device 102 can be implemented based on third information and / or configuration information.
[0307] In some embodiments, the fourth network element 1034 may perform QoS processing on the first data stream of the first service based on received third information, and / or N4 rules, and / or configuration information. In some embodiments, the configuration information of the fourth network element 1034 may include at least one of the following: local configuration, operator policy, and OAM configuration of the fourth network element 1034. In some embodiments, the QoS processing performed by the fourth network element 1034 may include: detecting the first data stream of the first service; and implementing authorization rules for the first data stream. In some embodiments, the QoS processing performed by the fourth network element 1034 may be QoS processing based on a first time. In some embodiments, the fourth network element 1034 may perform QoS processing based on a first time based on second information, and / or N4 rules, and / or configuration information. In some embodiments, the fourth network element 1034 may perform QoS processing based on a first time based on at least one of second indication information, parameter information at a first time, and delay information of the first service.
[0308] In some embodiments, the first device 102 may perform resource management and / or QoS processing based on the received third information. In some embodiments, the first device 102 may perform QoS processing based on the third information. In some embodiments, the third information may be included in a QoS configuration. The first device 102 may perform QoS processing on a first data stream based on a QoS configuration containing the third information. In some embodiments, the QoS processing performed by the first device 102 may include QoS enforcement. In some embodiments, the first device 102 may perform resource management for the first data stream based on the third information. In some embodiments, the resource management of the first data stream may include radio resource management associated with the terminal 101.
[0309] In some embodiments, terminal 101 may have one or more downstream devices. In some embodiments, terminal 101 may send third information to the downstream devices. Subsequently, the downstream devices may send response information to terminal 101. The response information is used by terminal 101 to perform QoS processing based on a first time. Therefore, terminal 101 can perform QoS processing based on a first time according to the third information and the response information.
[0310] In step S211, terminal 101 sends measurement information to first device 102.
[0311] In some embodiments, terminal 101 may send measurement information. In some embodiments, the measurement information may be sent by terminal 101, but is not limited thereto, and may also be sent by other entities.
[0312] In some embodiments, the first device 102 may receive measurement information. In some embodiments, the measurement information may be received by the first device 102, but is not limited thereto, and may also be received by other entities.
[0313] In some embodiments, terminal 101 may send measurement information to first device 102 via at least one of user plane, data plane, and computing plane. In some embodiments, the measurement information may be included in uplink data packets sent by terminal 101. For example, terminal 101 may send uplink data packets in which the header or payload of the data packets may contain measurement information.
[0314] In some embodiments, step S211 may include: performing a first-time monitoring of a first data stream of a first service; and sending first-time measurement information to the first device 102.
[0315] In some embodiments, terminal 101 can support monitoring and reporting of the first data stream. In some embodiments, terminal 101 can monitor the first data stream based on third information. In other words, terminal 101 can perform monitoring of the first data stream. In some embodiments, when a reporting trigger event occurs, i.e., when reporting is triggered, terminal 101 can send measurement information. In some embodiments, this measurement information can be obtained by terminal 101 monitoring the first data stream.
[0316] In some embodiments, upon obtaining third information, terminal 101 can send the third information to a downstream device and receive measurement information sent by the downstream device at a first moment. In some embodiments, the downstream device can perform monitoring at a first moment based on the third information. When the downstream device determines that a reporting trigger event has occurred, the downstream device can send measurement information to terminal 101.
[0317] In some embodiments, the measurement information sent by the downstream device may include at least one of the following: a measurement of the processing time of the downstream device, and a measurement of the round-trip delay from terminal 101 to the downstream device. It is understood that the measurement information sent by the downstream device may also include other measurement values, and this disclosure does not specifically limit this.
[0318] In some embodiments, the measurement information sent by terminal 101 may include at least one of the following: a measurement value at a first time; a measurement value of the round-trip delay from terminal 101 to the fourth network element 1034; a measurement value of the uplink delay from terminal 101 to the fourth network element 1034; a measurement value of the downlink delay from the fourth network element 1034 to terminal 101; a measurement value of the processing time of terminal 101; a measurement value of the processing delay of the downstream device; a measurement value of the round-trip delay from terminal 101 to the downstream device; and a measurement value of the processing delay of the second network element 1032.
[0319] In step S212, the first device 102 sends measurement information to the fourth network element 1034.
[0320] In some embodiments, the first device 102 may transmit measurement information. In some embodiments, the measurement information may be transmitted by the first device 102, but is not limited thereto, and may also be transmitted by other entities.
[0321] In some embodiments, the fourth network element 1034 can receive measurement information. In some embodiments, the measurement information can be received by the fourth network element 1034, but is not limited thereto, and can also be received by other entities.
[0322] In some embodiments, the first device 102 may send measurement information to the third network element 1033 via at least one of the user plane, data plane, and computing plane. In some embodiments, the measurement information may be included in the uplink data packet sent by the terminal 101. For example, the terminal 101 may send an uplink data packet, and the header and / or payload of the data packet may contain measurement information.
[0323] In some embodiments, the measurement information sent by the first device 102 may include at least one of the following: measurement information received from the terminal 101, and measurement information obtained locally by the first device 102.
[0324] In some embodiments, the first device 102 may send the received measurement information to the third network element 1033.
[0325] In some embodiments, the first device 102 can perform first-time monitoring of the first data stream of the first service. In some embodiments, the first device 102 can support first-time monitoring and reporting. In some embodiments, the first device 102 can monitor the first data stream based on third information. In other words, the first device 102 can perform first-time monitoring. In some embodiments, when a reporting trigger event occurs, i.e., when reporting is triggered, the first device 102 can send measurement information. In some embodiments, this measurement information can be obtained by the first device 102 monitoring the first data stream.
[0326] In some embodiments, the measurement information obtained by the first device 102 through monitoring can be added to the header and / or payload of the uplink data packet.
[0327] In some embodiments, the measurement information sent by the first device 102 may include at least one of the following: a measurement value at a first time; a measurement value of the round-trip delay from terminal 101 to the fourth network element 1034; a measurement value of the uplink delay from terminal 101 to the fourth network element 1034; a measurement value of the downlink delay from the fourth network element 1034 to terminal 101; a measurement value of the processing time of terminal 101; a measurement value of the processing delay of the downstream device; a measurement value of the round-trip delay from terminal 101 to the downstream device; and a measurement value of the processing delay of the second network element 1032.
[0328] In step S213, the fourth network element 1034 determines the monitoring report.
[0329] In some embodiments, the fourth network element 1034 can determine a monitoring report based on the measurement information obtained in the first moment. In some embodiments, the monitoring report can be generated based on the measurement information obtained by the fourth network element 1034.
[0330] In some embodiments, step S213 may include: acquiring measurement information; and determining a first-time (monitored) monitoring report based on the measurement information.
[0331] In some embodiments, the measurement information used to determine the monitoring report may include at least one of the following: measurement information received from the first device 102, and measurement information acquired locally.
[0332] In some embodiments, the measurement information of the downstream device obtained through step S212 can be used to determine the monitoring report.
[0333] In some embodiments, the fourth network element 1034 can perform real-time monitoring of the first data stream of the first service. In some embodiments, the fourth network element 1034 can support real-time monitoring and reporting. In some embodiments, the fourth network element 1034 can monitor the first data stream based on third information. In other words, the fourth network element 1034 can perform real-time monitoring. In some embodiments, when a reporting trigger event occurs, i.e., when reporting is triggered, the fourth network element 1034 can send measurement information. In some embodiments, this measurement information can be obtained by the fourth network element 1034 monitoring the first data stream.
[0334] In some embodiments, upon obtaining measurement information, the third network element 1033 can determine a monitoring report based on the measurement information. In some embodiments, the monitoring report can be determined based on the measurement information. In some embodiments, the third network element 1033 can integrate the measurement information. In some embodiments, the integrated measurement information can be referred to as a measurement report or a monitoring report.
[0335] In some embodiments, the measurement information used to determine the monitoring report may include at least one of the following: measurement information obtained by the downstream device performing monitoring at a first time, measurement information obtained by the terminal 101 performing monitoring at a first time, measurement information obtained by the first device 102 performing monitoring at a first time, and measurement information obtained by the fourth network element 1034 performing monitoring at a first time. It is understood that one or more of the fourth network element 1034, the first device 102, the terminal 101, and the downstream device may provide the measurement information.
[0336] In some embodiments, the measurement information obtained by the fourth network element 1034 may include at least one of the following: a measurement value at a first time; a measurement value of the round-trip delay from terminal 101 to the fourth network element 1034; a measurement value of the uplink delay from terminal 101 to the fourth network element 1034; a measurement value of the downlink delay from the fourth network element 1034 to terminal 101; a measurement value of the processing time of terminal 101; a measurement value of the processing delay of the downstream device; a measurement value of the round-trip delay from terminal 101 to the downstream device; and a measurement value of the processing delay of the second network element 1032.
[0337] In some embodiments, the monitoring report may further include at least one of the following: a measurement of the round-trip delay from terminal 101 to the fourth network element 1034; a measurement of the uplink delay from terminal 101 to the fourth network element 1034; a measurement of the downlink delay from the fourth network element 1034 to terminal 101; a measurement of the processing time of terminal 101; a measurement of the processing delay of the downstream device; a measurement of the round-trip delay from terminal 101 to the downstream device; and a measurement of the processing delay of the second network element 1032.
[0338] It should be noted that step S213 is optional. In some embodiments, step S213 may not be performed. In this case, the measurement information acquired by the fourth network element 1034 can be sent as part of the monitoring report.
[0339] In step S214, the fourth network element 1034 sends a monitoring report to the second network element 1032.
[0340] In some embodiments, the fourth network element 1034 can send monitoring reports. In some embodiments, the monitoring reports can be sent by the fourth network element 1034, but are not limited to this; they can also be sent by other entities.
[0341] In some embodiments, the second network element 1032 can receive monitoring reports. In some embodiments, the monitoring reports can be received by the second network element 1032, but are not limited to this; they can also be sent by other entities.
[0342] In some embodiments, the fourth network element 1034 can send a monitoring report to the second network element 1032 through at least one of the user plane, data plane, and computing plane.
[0343] In some embodiments, the monitoring report determined by the fourth network element 1034 can be exposed to the second network element 1032. In some embodiments, the monitoring report can be sent in response to a subscription message. In one example, the second network element 1032 can subscribe to a monitoring report for a given time from the fourth network element 1034 via, for example, first information. In response to this subscription, the fourth network element 1034 can send the monitoring report.
[0344] In some embodiments, the content of the monitoring report may be included in the header and / or payload of the uplink data packet and provided to the second network element 1032.
[0345] In step S215, the fourth network element 1034 sends a monitoring report to the third network element 1033.
[0346] In some embodiments, the fourth network element 1034 can send monitoring reports. In some embodiments, the monitoring reports can be sent by the fourth network element 1034, but are not limited to this; they can also be sent by other entities.
[0347] In some embodiments, the third network element 1033 can receive monitoring reports. In some embodiments, the monitoring reports can be received by the third network element 1033, but are not limited to this; they can also be sent by other entities.
[0348] In some embodiments, the fourth network element 1034 can send a monitoring report to the third network element 1033 through the control plane.
[0349] In step S216, the third network element 1033 sends a monitoring report to the first network element 1031.
[0350] In some embodiments, the third network element 1033 can send monitoring reports. In some embodiments, the monitoring reports can be sent by the third network element 1033, but are not limited to this; they can also be sent by other entities.
[0351] In some embodiments, the first network element 1031 can receive monitoring reports. In some embodiments, the monitoring reports can be received by the first network element 1031, but are not limited to this; they can also be sent by other entities.
[0352] In some embodiments, the third network element 1033 can send a monitoring report to the first network element 1031 through the control plane.
[0353] In some embodiments, a monitoring report may be provided to the first network element 1031 for the first network element 1031 to determine and / or update the first rule related to the first service.
[0354] In some embodiments, the measurement information (or monitoring report) obtained and / or transmitted in one or more of steps S211 to S216 is based on monitoring at a first time. It is understood that the measurement information may also be referred to as monitoring information, reporting information, etc., and this disclosure does not specifically limit this terminology.
[0355] The communication method of this embodiment can be implemented through steps S201 to S216.
[0356] In some embodiments, the first device 102 may be an access network device, and the fourth network element 1034 may be a UPF.
[0357] In some embodiments, the first device 102 may be an access UPF, and the fourth network element 1034 may be a service UPF. For example, the access UPF may be a core network element closer to the terminal 101. For example, the service UPF may be a core network element closer to the service (i.e., the second network element 1032).
[0358] 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.
[0359] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.
[0360] 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.”
[0361] 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.
[0362] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0363] 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.
[0364] 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.
[0365] In some embodiments, the terms “traffic”, “flow”, “stream”, and “data stream” can be used interchangeably.
[0366] In some embodiments, the terms "packet", "message", "PDU", "packet data packet" and other similar terms can be used interchangeably.
[0367] In some embodiments, the terms "header", "packet header", and "data packet header" can be used interchangeably.
[0368] In some embodiments, the terms "QoS processing", "QoS implementation", and "QoS handling" can be used interchangeably.
[0369] The communication method involved in the embodiments of this disclosure may include at least one of steps S201 to S216. For example, step S201 can be implemented as an independent embodiment, step S203 can be implemented as an independent embodiment, step S205 can be implemented as an independent embodiment, step S206 can be implemented as an independent embodiment, step S207 can be implemented as an independent embodiment, step S208 can be implemented as an independent embodiment, step S209 can be implemented as an independent embodiment, step S211 can be implemented as an independent embodiment, step S212 can be implemented as an independent embodiment, step S214 can be implemented as an independent embodiment, the combination of steps S201 and S203 can be implemented as an independent embodiment, the combination of steps S205 and S206 can be implemented as an independent embodiment, the combination of steps S205 and S207 can be implemented as an independent embodiment, and the combination of steps S207 and S208 can be implemented as an independent embodiment. The combination of steps S208 and S209 can be implemented as an independent embodiment, the combination of steps S209 and S211 can be implemented as an independent embodiment, the combination of steps S211 and S212 can be implemented as an independent embodiment, the combination of steps S208 and S212 can be implemented as an independent embodiment, the combination of steps S206 and S214 can be implemented as an independent embodiment, the combination of steps S205, S206 and S207 can be implemented as an independent embodiment, the combination of steps S207, S208 and S209 can be implemented as an independent embodiment, the combination of steps S206, S213 and S214 can be implemented as an independent embodiment, and the combination of steps S211, S212, S213 and S214 can be implemented as an independent embodiment, but is not limited thereto.
[0370] In some embodiments, steps S206 and S207 may be performed in a different order or simultaneously, and steps S214 and S215 may be performed in a different order or simultaneously.
[0371] In some embodiments, steps S202, S203, S204, S205, S206, S207, S208, S209, S210, S211, S212, S213, S214, S215, and S216 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S201, S202, S204, S205, S206, S207, S208, S209, S210, S211, S212, S213, S214, S215, and S216 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S201, S202, S203, S204, S206, S207, S208, S209, S210, S211, S212, S213, S214, S215, and S216 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S201, S202, S203, S204, S205, S206, S208, S209, S210, S211, S212, S213, S214, S215, and S216 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S201, S202, S203, S204, S205, S206, S207, S208, S210, S211, S212, S213, S214, S215, and S216 are optional, and one or more of these steps may be omitted or substituted in different embodiments.In some embodiments, steps S201, S202, S203, S204, S205, S206, S207, S208, S209, S210, S211, S213, S214, S215, and S216 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0372] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0373] 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. As shown in Figure 3A, the method includes steps S3101 to S3110.
[0374] In step S3101, the second network element 1032 sends the first information to the first network element 1031.
[0375] The optional implementations of step S3101 can be found in the optional implementations of steps S201, S202, and S203 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0376] In step S3102, the first network element 1031 performs a strategy decision.
[0377] The optional implementation of step S3102 can be found in the optional implementation of step S204 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0378] In step S3103, the first network element 1031 sends the second information to the third network element 1033.
[0379] The optional implementation of step S3103 can be found in the optional implementation of step S205 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0380] In step S3104, the third network element 1033 sends third information to the fourth network element 1034.
[0381] The optional implementation of step S3104 can be found in the optional implementation of step S206 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0382] In step S3105, the third network element 1033 sends third information to the first device 102.
[0383] The optional implementations of step S3105 can be found in the optional implementations of steps S207 and S208 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0384] In step S3106, the first device 102 sends third information to the terminal 101.
[0385] The optional implementation of step S3106 can be found in the optional implementation of step S209 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0386] In step S3107, terminal 101 sends measurement information to first device 102.
[0387] The optional implementation of step S3107 can be found in the optional implementation of step S211 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0388] In step S3108, the first device 102 sends measurement information to the fourth network element 1034.
[0389] The optional implementation of step S3108 can be found in the optional implementation of step S212 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0390] In step S3109, the fourth network element 1034 determines the monitoring report.
[0391] The optional implementation of step S3109 can be found in the optional implementation of step S213 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0392] In step S3110, the fourth network element 1034 sends a monitoring report to the second network element 1032.
[0393] The optional implementation of step S3110 can be found in the optional implementation of step S214 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0394] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0395] 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. As shown in Figure 3B, the method includes steps S3201 to S3203.
[0396] In step S3201, the terminal sends measurement information to the third node.
[0397] The optional implementation of step S3201 can be found in the optional implementation of step S211 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0398] In some embodiments, the third node may be the first device 102.
[0399] In step S3202, the third node sends measurement information to the first node.
[0400] The optional implementation of step S3202 can be found in the optional implementation of step S212 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0401] In some embodiments, the first node may be the fourth network element 1034.
[0402] In step S3203, the first node sends measurement information to the second node.
[0403] The optional implementation of step S3203 can be found in the optional implementation of step S214 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0404] In some embodiments, the first node can send measurement information and / or monitoring reports through the user plane. In one example, the first node can send the acquired measurement information to the second node. In another example, the first node can integrate the acquired measurements and send the integrated measurement information (or monitoring report) to the second node.
[0405] In some embodiments, measurement information and / or monitoring reports can be transmitted on the user plane. It is understood that measurement information and / or monitoring reports can also be transmitted via the computation plane, data plane, etc., and this disclosure does not specifically limit this.
[0406] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0407] In the following, specific embodiments of the present disclosure will be described by way of example.
[0408] In some embodiments, this disclosure presents immersive service (including XR) information: Motion-to-Render-to-Photon Time (M2R2PT). M2R2PT indicates the equipment-to-equipment (E2E) latency of the immersive service, including round-trip time, UE and tethering device processing time, and server processing time.
[0409] In some embodiments, M2R2PT can be used as a QoS parameter introduced for immersive services or as service auxiliary information for flexible QoS adaptation.
[0410] In some embodiments, monitoring and exposure of the user's experience from motion to rendering to photon time is proposed to support flexible QoS adaptation for immersive services, including:
[0411] -Measurements for M2R2PT monitoring performed by RAN / UPF / UE / backup devices (e.g., based on M2R2PT reporting rules, MRR defines how M2R2PT and related delays of one or more traffic flows should be counted, and when and how the measurements should be reported).
[0412] - Measurement-based M2R2PT monitoring reports are provided to the UPF from the RAN / UE / backup devices.
[0413] - The first UP NF / PSA UPF / service UPF generates an M2R2PT monitoring report based on the measurement report (e.g., calculating M2R2PT based on round-trip time, UE processing time, downstream device processing time, round-trip time between UE and downstream device, and server processing time).
[0414] -M2R2PT monitoring reports are exposed to the data network (e.g., AS / AF) by the UPF (e.g., PSA UPF, Service UPF).
[0415] In some embodiments, for a data network (DN) / AF, the AF provides the network with an M2R2PT monitoring subscription request, which may include, for example, QoS requirements for media streams, a Motion to Render to Photon Time (M2R2PT) indication to indicate Motion to Render to Photon Time support for flexible QoS adaptation, an M2R2PT value for immersive service traffic (indicating the maximum M2R2PT value), or a list of M2R2PT values (indicating different maximum M2R2PT values for QoS requirements), or an M2R2PT time window (indicating the maximum and minimum M2R2PT values).
[0416] In some embodiments, M2R2PT monitors subscription requests, including:
[0417] - Monitoring model / type (i.e., monitoring type information), indicating that the monitoring type is identified as at least one of the following: M2R2PT; round-trip time between UE and PSA UPF (or, DL and UL delays); UE processing time; downstream device processing time; round-trip time between UE and downstream device; server processing time.
[0418] - Monitoring level (i.e., monitoring level information) indicates the monitoring SDF, monitoring session, and monitoring task of a single UE or multiple UEs.
[0419] - Maximum threshold (i.e., monitoring threshold information) indicates the maximum value allowed for a monitoring type, as at least one of the following: M2R2PT threshold; round-trip time threshold between UE and PSA UPF; UE processing time threshold; downstream device processing time threshold; round-trip time threshold between UE and downstream device; server processing time threshold.
[0420] - Start / end time (i.e., monitoring time information): The start / end date and time when the monitoring profile is applied.
[0421] - Reset cycle (i.e., monitoring and control information) is the time period for resetting periodic monitoring and control.
[0422] In some embodiments, the AF receives a notification from the network of an M2R2PT monitoring report sent to the AF. This notification includes the M2R2PT monitoring report, and / or round-trip time, UE-side care time, downstream device processing time, round-trip time between the UE and the downstream device, and server processing time.
[0423] In some embodiments, for the first CP NF / PCF, the first CP NF / PCF determines the M2R2PT monitoring information based on information provided by the AF and / or local configuration. The PCF includes the authorized M2R2PT monitoring policy in the PCC rule and provides it to the second CP NF / SMF.
[0424] In some embodiments, if the second CP NF / SMF reports the M2R2PT monitoring result, the PCF derives the M2R2PT and / or the relevant latency value from the monitoring subscription of the AF based on the result report.
[0425] In some embodiments, for the purpose of M2R2PT monitoring and control, the PCF requests an M2R2PT report trigger and provides the second CP NF / SMF with the necessary M2R2PT monitoring information thresholds, M2R2PT and / or related delay thresholds. In some embodiments, the PCF decides whether and when to activate M2R2PT monitoring to the second CP NF / SMF.
[0426] In some embodiments, M2R2PT monitoring-related information may include:
[0427] - Monitoring model / type, indicating the monitoring type as at least one of the following: M2R2PT; round-trip time between UE and PSA UPF (or, DL and UL delays); UE processing time; downstream device processing time; round-trip time between UE and downstream device; server processing time.
[0428] - Monitoring level indicates the monitoring SDF, monitoring session, and monitoring task for a single UE or multiple UEs.
[0429] - Maximum threshold, indicating the maximum value allowed for the monitoring type, as at least one of the following: M2R2PT threshold; round-trip time threshold between UE and PSA UPF; UE processing time threshold; downstream device processing time threshold; round-trip time threshold between UE and downstream device; server processing time threshold.
[0430] - Start / End Time: Configure the start / end date and time for the monitoring to be applied.
[0431] - Reset cycle refers to the time period during which the periodic monitoring and control are reset.
[0432] In some embodiments, the PCF (e.g., in a PCC rule) authorizes and provides QoS to the SMF for traffic data flows and other network control, which is related to traffic data flow detection, gating, QoS and charging, and takes into account:
[0433] - Motion-to-Render-to-Photon Time (M2R2PT) indication, which indicates M2R2PT support for flexible QoS adaptation;
[0434] -M2R2PT value (indicates the maximum value of M2R2PT);
[0435] - Alternatively, a list of M2R2PT values (indicating different maximum M2R2PT values for QoS requirements);
[0436] - Alternatively, M2R2PT time window (indicating the minimum and maximum values of M2R2PT);
[0437] - and / or, local operator configuration (e.g., UPF measurement and provision of M2R2PT or AS provision of M2R2PT priority, etc.).
[0438] In some embodiments, the PCF determines the PCC rule by taking into account the M2R2PT indication and the M2R2PT auxiliary information described above.
[0439] In some embodiments, the PCF sends authorized M2R2PT support and M2R2PT-related QoS parameters to the second CP NF / SMF via PCC rules, including:
[0440] - Motion to Render to Photon Time (M2R2PT) indicator;
[0441] -M2R2PT value (indicates the maximum value of M2R2PT);
[0442] - Alternatively, a list of M2R2PT values (indicating different maximum M2R2PT values for QoS requirements);
[0443] - Alternatively, M2R2PT time window (indicating the minimum and maximum values of M2R2PT);
[0444] - Alternatively, the delay QoS parameters from the M2R2PT mapping, for example, divided into round-trip delay or UL and DL delay, UE and downstream device processing time, and server processing time;
[0445] - Round-trip time derived from M2R2PT;
[0446] - UL and / or DL delays derived from M2R2PT;
[0447] - UE and subsequent device processing time derived from M2R2PT;
[0448] - Server processing time derived from M2R2PT.
[0449] In some embodiments, for the second CP NF / SMF, the second CP NF / SMF determines the configuration for M2R2PT monitoring measurements (e.g., M2R2PT and / or round-trip time, UE processing time, downstream device processing time, round-trip time between UE and downstream device, server processing time) based on the monitoring information (monitoring policy in PCC rules) provided by the first CP NF / PCF, that is, determines the reporting rules for M2R2PT monitoring measurements.
[0450] In some embodiments, the second CP NF / SMF instructs the RAN / UPF / UE / backup device to perform measurements of the M2R2PT parameters. The second CP NF / SMF instructs the measurement by providing M2R2PT reporting rules to the RAN / UPF / UE / backup device.
[0451] In some embodiments, if an instruction to report to the SMF is provided to the UPF, upon receiving an M2R2PT monitoring report from the RAN / UPF / UE / backup device, the second CP NF / SMF sends a measurement report to the PCF.
[0452] In some embodiments, the second CP NF / SMF requests an M2R2PT monitoring report (e.g., reported to the PSA UPF / Service UPF) based on the M2R2PT monitoring key and trigger event.
[0453] In some embodiments, the second CP NF / SMF generates an M2R2PT reporting rule for each monitoring keyword in a pre-configured or activated PCC rule received from the PCF, and can also maintain the mapping between monitoring keywords and M2R2PT reporting rules.
[0454] In some embodiments, the second CP NF / SMF provides a reporting trigger event to the RAN / UPF / UE / backup device for determining when to report M2R2PT monitoring information.
[0455] In some embodiments, based on PCC rules from the PCF, the SMF generates and provides the NG-RAN with a QoS configuration with authorized QoS parameters (including motion-to-render-to-photon time, or the delay QoS from the motion-to-render-to-photon time mapping, for example, divided into round-trip delay or UL and DL delay, UE and downstream device processing time, and server processing time).
[0456] In some embodiments, motion-to-render-to-photon time, or the latency QoS from the motion-to-render-to-photon time mapping, for example, divided into round-trip latency or UL and DL latency, UE and downstream device processing time, and server processing time, is included in the QoS rules provided to the UE, and / or is included in the PDR rules provided to the first UP NF / PSA UPF / service UPF.
[0457] In some embodiments, the second CP NF / SMF instructs the first UP NF / PSA UPF / Access UPF / Serving UPF to enforce authorization rules (e.g., FAR, QER, PDR), including M2R2PT-related QoS parameters or latency QoS parameters mapped from M2R2PT, such as round-trip delay or UL and DL delay, UE and downstream device processing time, and server processing time. In some embodiments, the SMF configures / activates rules to the first UP NF / PAS UPF / Access UPF / Serving UPF (e.g., via an N4 session).
[0458] In some embodiments, for the first UP NF / PSA UPF / Access UPF / Service UPF, the first UP NF / PSA UPF / Access UPF / Service UPF performs M2R2PT monitoring measurements (e.g., M2R2PT and / or round-trip time, UE processing time, downstream device processing time, round-trip time between UE and downstream device, server processing time), that is, performs monitoring and reporting for M2R2PT based on instructions from the second CP NF / SMF (e.g., M2R2PT reporting rules) and optionally the local configuration of operator policies.
[0459] In some embodiments, the first UP NF / PSA UPF / serving UPF receives measurement reports from the RAN / access UPF / UE / backup device.
[0460] In some embodiments, the first UP NF / PSA UPF / serving UPF generates an M2R2PT monitoring report based on the measurement report (e.g., calculating M2R2PT based on round-trip time, UE processing time, downstream device processing time, round-trip time between UE and downstream device, and server processing time).
[0461] In some embodiments, the first UP NF / PSA UPF / service UPF sends an M2R2PT monitoring report to the PCF (e.g., via the second CP NF / SMF based on M2R2PT reporting rules). In some embodiments, the M2R2PT monitoring report can be used by the PCF to make policy decisions and updates for immersive services.
[0462] In some embodiments, M2R2PT monitoring reports are exposed to the data network (e.g., AS / AF) by the first UP NF / PSA UPF / service UPF (e.g., if the DN has subscribed to M2R2PT monitoring).
[0463] In some embodiments, the first UP NF / PSA UPF / service UPF should be able to support reporting based on different triggering events.
[0464] In some embodiments, M2R2PT monitoring information should be collected and reported in the first UP NF / PSA UPF / service UPF based on monitoring keywords and triggering events.
[0465] In some embodiments, the M2R2PT reporting rule (MRR) defines how the M2R2PT and associated delays of one or more traffic flows should be counted, and when and how the measurements should be reported, as shown in Table 1 below.
[0466] Table 1: MRR Reporting Rules
[0467] In some embodiments, the first UP NF / PSA UPF / access UPF / service UPF detects immersive service data streams and implements authorization rules (e.g., FAR, QER, PDR), including QoS parameters related to M2R2PT or delay QoS parameters mapped from M2R2PT, such as round-trip delay or UL and DL delay, UE and downstream device processing time, and server processing time.
[0468] In some embodiments, for the consumer (e.g., NG-RAN) and the UE / backup device, the consumer (e.g., NG-RAN) and the UE / backup device support reporting M2R2PT information to the first UP NF / PSA UPF / access UPF / serving UPF (directly or indirectly, for example, reported from the UE / backup device to the PSA UPF via the RAN, reported from the RAN / UE / backup device to the serving UPF via the access UPF, or reported from the UE to the PSA UPF or serving UPF via the backup device).
[0469] In some embodiments, the consumer (e.g., NG-RAN) and the UE / backup device perform M2R2PT monitoring measurements (e.g., M2R2PT and / or round-trip time, UE processing time, backup device processing time, round-trip time between the UE and the backup device, server processing time), i.e., perform monitoring and reporting for M2R2PT, based on instructions from the second CP NF / SMF (e.g., M2R2PT reporting rules) and, optionally, local configuration of operator policies.
[0470] In some embodiments, the consumer (e.g., NG-RAN) and the UE / backup device should be able to support reporting based on different triggering events.
[0471] In some embodiments, M2R2PT monitoring information should be collected in the consumer (e.g., NG-RAN) and UE / backup equipment and reported to the first UP NF / PSA UPF / access UPF / service UPF based on monitoring keywords and triggering events.
[0472] In some embodiments, the consumer (e.g., NG-RAN) and the UE / backup device implement authorized QoS configurations (including M2R2PT-related QoS parameters, or delay QoS parameters mapped from M2R2PT, such as round-trip delay or UL and DL delay, UE and backup device processing time, and server processing time) and / or adjust resource management, taking into account information provided by the second CP NF / SMF.
[0473] Figure 4 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 4, the method relates to an AF session establishment process with required QoS.
[0474] In step 1, the AF (i.e., the second network element) sends an AF session resource request, for example, by creating an AF request through an Nnef_AFsessionWithQoS_Create request. The AF carries the QoS requirements of the data streams for immersive services (including XR) and interactive media services in the request message.
[0475] In some embodiments, the AF provides the network with an M2R2PT monitoring subscription request, which may include, for example, QoS requirements for media streams, a Motion to Render to Photon Time (M2R2PT) indication to indicate Motion to Render to Photon Time support for flexible QoS adaptation, an M2R2PT value for immersive service traffic (indicating the maximum M2R2PT value), or a list of M2R2PT values (indicating different maximum M2R2PT values for QoS requirements), or an M2R2PT time window (indicating the maximum and minimum M2R2PT values).
[0476] In some embodiments, M2R2PT monitors subscription requests, including:
[0477] - Monitoring model / type, indicating the monitoring type as at least one of the following: M2R2PT; round-trip time between UE and PSA UPF (or, DL and UL delays); UE processing time; downstream device processing time; round-trip time between UE and downstream device; server processing time.
[0478] - Monitoring level indicates the monitoring SDF, monitoring session, and monitoring task for a single UE or multiple UEs.
[0479] - Maximum threshold, indicating the maximum value allowed for the monitoring type, as at least one of the following: M2R2PT threshold; round-trip time threshold between UE and PSA UPF; UE processing time threshold; downstream device processing time threshold; round-trip time threshold between UE and downstream device; server processing time threshold.
[0480] - Start / End Time: Configure the start / end date and time for the monitoring to be applied.
[0481] - Reset cycle refers to the time period during which the periodic monitoring and control are reset.
[0482] In some embodiments, the AF receives a notification from the network of an M2R2PT monitoring report sent to the AF. This notification includes the M2R2PT monitoring report, and / or round-trip time, UE-side care time, downstream device processing time, round-trip time between the UE and the downstream device, and server processing time.
[0483] In some embodiments, the message may carry XRM service information, identifying the data flow or data flow group of the XRM service (e.g., multimodal service ID), UE address / UE identifier, AF identifier, application identifier, flow description, DNN, S-NSSAI, QoS parameters, and other relevant information. Here, the multimodal service ID can be used to identify all flows in the XRM service group.
[0484] In step 2, the NEF (i.e., the fifth network element) authorizes the AF request. If it is an untrusted AF, the NEF sends the AF request to the PCF. (For example, the NEF performs relevant mappings, including mapping the XRM service identifier (AF service identifier) to the DNN and S-NSSAI, mapping the external application to the CN application identifier; and mapping the external UE identifier to the CN UE identifier (such as SUPI) based on the subscription information of unified data management (UDM), and performing the mapping of the external to the internal XRM service group identifier according to the UDM subscription information.)
[0485] In step 3, the NEF authorizes the AF request and determines whether to invoke the TSCTSF or directly contact the PCF based on the parameters provided by the AF. The PCF receives the attributes provided by the AF from either the NEF or the TSCTSF. The NEF triggers an Npcf_PolicyAuthorization_Create request, sending the AF request to the PCF, carrying indications and QoS requirement information for the PCF's policy decision. In some embodiments, the message carries an SDF M2R2PT monitoring subscription request pointing to the network.
[0486] In step 4, the PCF (i.e., the first network element) performs a policy decision. In some embodiments, the PCF may determine updated or new policy information, which needs to be sent to the SMF.
[0487] In some embodiments, the first CP NF / PCF determines M2R2PT monitoring information based on information provided by the AF and / or local configuration. The PCF includes the authorized M2R2PT monitoring policy in the PCC rule and provides it to the second CP NF / SMF.
[0488] In some embodiments, if the second CP NF / SMF reports the M2R2PT monitoring result, the PCF derives the M2R2PT and / or the relevant latency value from the monitoring subscription of the AF based on the result report.
[0489] In some embodiments, for the purpose of M2R2PT monitoring and control, the PCF requests an M2R2PT report trigger and provides the second CP NF / SMF with the necessary M2R2PT monitoring information thresholds, M2R2PT and / or related delay thresholds. In some embodiments, the PCF decides whether and when to activate M2R2PT monitoring to the second CP NF / SMF.
[0490] In some embodiments, M2R2PT monitoring-related information may include:
[0491] - Monitoring model / type, indicating the monitoring type as at least one of the following: M2R2PT; round-trip time between UE and PSA UPF (or, DL and UL delays); UE processing time; downstream device processing time; round-trip time between UE and downstream device; server processing time.
[0492] - Monitoring level indicates the monitoring SDF, monitoring session, and monitoring task for a single UE or multiple UEs.
[0493] - Maximum threshold, indicating the maximum value allowed for the monitoring type, as at least one of the following: M2R2PT threshold; round-trip time threshold between UE and PSA UPF; UE processing time threshold; downstream device processing time threshold; round-trip time threshold between UE and downstream device; server processing time threshold.
[0494] - Start / End Time: Configure the start / end date and time for the monitoring to be applied.
[0495] - Reset cycle refers to the time period during which the periodic monitoring and control are reset.
[0496] In some embodiments, the PCF (e.g., in a PCC rule) authorizes and provides QoS to the SMF for traffic data flows and other network control, which is related to traffic data flow detection, gating, QoS, and charging, and takes into account:
[0497] - Motion-to-Render-to-Photon Time (M2R2PT) indication, which indicates M2R2PT support for flexible QoS adaptation;
[0498] -M2R2PT value (indicates the maximum value of M2R2PT);
[0499] - Alternatively, a list of M2R2PT values (indicating different maximum M2R2PT values for QoS requirements);
[0500] - Alternatively, M2R2PT time window (indicating the minimum and maximum values of M2R2PT);
[0501] - and / or, local operator configuration (e.g., UPF measurement and provision of M2R2PT or AS provision of M2R2PT priority, etc.).
[0502] In some embodiments, the PCF determines the PCC rule by taking into account the M2R2PT indication and the M2R2PT auxiliary information described above.
[0503] In some embodiments, the PCF sends authorized M2R2PT support and M2R2PT-related QoS parameters to the second CP NF / SMF via PCC rules, including:
[0504] - Motion to Render to Photon Time (M2R2PT) indicator;
[0505] -M2R2PT value (indicates the maximum value of M2R2PT);
[0506] - Alternatively, a list of M2R2PT values (indicating different maximum M2R2PT values for QoS requirements);
[0507] - Alternatively, M2R2PT time window (indicating the minimum and maximum values of M2R2PT);
[0508] - Alternatively, the delay QoS parameters from the M2R2PT mapping, for example, divided into round-trip delay or UL and DL delay, UE and downstream device processing time, and server processing time;
[0509] - Round-trip time derived from M2R2PT;
[0510] - UL and / or DL delays derived from M2R2PT;
[0511] - UE and subsequent device processing time derived from M2R2PT;
[0512] - Server processing time derived from M2R2PT.
[0513] In step 5, in response, PCF sends an Npcf_PolicyAuthorization_Create response to NEF.
[0514] In step 6, NEF sends an Nnef_AFsessionWithQoS_Create response message to AF, which carries the result to indicate whether the request has been authorized.
[0515] In step 7, the PCF initiates an SMF policy association modification request (PCC rule) to the SMF (i.e., the third network element).
[0516] In some embodiments, the second CP NF / SMF determines the configuration for M2R2PT monitoring measurements (e.g., M2R2PT and / or round-trip time, UE processing time, downstream device processing time, round-trip time between UE and downstream device, server processing time) based on the monitoring information (monitoring policy in PCC rules) provided by the first CP NF / PCF, that is, it determines the reporting rules for M2R2PT monitoring measurements.
[0517] In some embodiments, the second CP NF / SMF instructs the RAN / UPF / UE / backup device to perform measurements of the M2R2PT parameters. The second CP NF / SMF instructs the measurement by providing M2R2PT reporting rules to the RAN / UPF / UE / backup device.
[0518] In some embodiments, if an instruction to report to the SMF is provided to the UPF, upon receiving an M2R2PT monitoring report from the RAN / UPF / UE / backup device, the second CP NF / SMF sends a measurement report to the PCF (e.g., to the PSA UPF / serving UPF).
[0519] In some embodiments, the second CP NF / SMF requests an M2R2PT monitoring report based on the M2R2PT monitoring key and the trigger event.
[0520] In some embodiments, the second CP NF / SMF generates an M2R2PT reporting rule for each monitoring keyword in a pre-configured or activated PCC rule received from the PCF, and can also maintain the mapping between monitoring keywords and M2R2PT reporting rules.
[0521] In some embodiments, the second CP NF / SMF provides a reporting trigger event to the RAN / UPF / UE / backup device for determining when to report M2R2PT monitoring information.
[0522] In some embodiments, based on PCC rules from the PCF, the SMF generates and provides the NG-RAN with a QoS configuration with authorized QoS parameters (including motion-to-render-to-photon time, or the delay QoS from the motion-to-render-to-photon time mapping, for example, divided into round-trip delay or UL and DL delay, UE and downstream device processing time, and server processing time).
[0523] In some embodiments, motion-to-render-to-photon time, or the latency QoS from the motion-to-render-to-photon time mapping, for example, divided into round-trip latency or UL and DL latency, UE and downstream device processing time, and server processing time, is included in the QoS rules provided to the UE, and / or is included in the PDR rules provided to the first UP NF / PSA UPF / service UPF.
[0524] In some embodiments, the second CP NF / SMF instructs the first UP NF / PSA UPF / Access UPF / Serving UPF to enforce authorization rules (e.g., FAR, QER, PDR), including M2R2PT-related QoS parameters or latency QoS parameters mapped from M2R2PT, such as round-trip delay or UL and DL delay, UE and downstream device processing time, and server processing time. In some embodiments, the SMF configures / activates rules to the first UP NF / PAS UPF / Access UPF / Serving UPF (e.g., via an N4 session).
[0525] In step 8, the SMF responds to the PCF with an SM policy association modification response.
[0526] In step 9, the SMF initiates an N4 session modification request (M2R2PT reporting rule) to the UPF (i.e., the fourth network element).
[0527] In step 10, the UPF responds to the SMF.
[0528] In some embodiments, the first UP NF / PSA UPF / access UPF / service UPF performs M2R2PT monitoring measurements (e.g., M2R2PT and / or round-trip time, UE processing time, downstream device processing time, round-trip time between UE and downstream device, server processing time), that is, performs monitoring and reporting for M2R2PT based on instructions from the second CP NF / SMF (e.g., M2R2PT reporting rules) and, optionally, local configuration of operator policies.
[0529] In some embodiments, the first UP NF / PSA UPF / serving UPF receives measurement reports from the RAN / access UPF / UE / backup device.
[0530] In some embodiments, the first UP NF / PSA UPF / serving UPF generates an M2R2PT monitoring report based on the measurement report (e.g., calculating M2R2PT based on round-trip time, UE processing time, downstream device processing time, round-trip time between UE and downstream device, and server processing time).
[0531] In some embodiments, the first UP NF / PSA UPF / service UPF sends an M2R2PT monitoring report to the PCF (e.g., via the second CP NF / SMF based on M2R2PT reporting rules). In some embodiments, the M2R2PT monitoring report can be used by the PCF to make policy decisions and updates for immersive services.
[0532] In some embodiments, M2R2PT monitoring reports are exposed to the data network (e.g., AS / AF) by the first UP NF / PSA UPF / service UPF (e.g., if the DN has subscribed to M2R2PT monitoring).
[0533] In some embodiments, the first UP NF / PSA UPF / service UPF should be able to support reporting based on different triggering events.
[0534] In some embodiments, M2R2PT monitoring information should be collected and reported in the first UP NF / PSA UPF / service UPF based on monitoring keywords and triggering events.
[0535] In some embodiments, the M2R2PT reporting rule (MRR) defines how the M2R2PT and associated delays of one or more traffic flows should be counted, and when and how the measurements should be reported, as shown in Table 1.
[0536] In some embodiments, the first UP NF / PSA UPF / access UPF / service UPF detects immersive service data streams and implements authorization rules (e.g., FAR, QER, PDR), including QoS parameters related to M2R2PT or delay QoS parameters mapped from M2R2PT, such as round-trip delay or UL and DL delay, UE and downstream device processing time, and server processing time.
[0537] In step 11, for the modification of the SMF request, the SMF triggers Namf_Communication_N1N2MessageTransfer([N2 SM information](PDU session identifier, QFI, QoS configuration), N1 SM container).
[0538] In step 12, the AMF (i.e., the sixth network element) can send an N2 message ([N2 SM information received from the SMF], NAS message (PDU session identifier, N1 SM container (PDU session modification command))) to the RAN.
[0539] In step 13, the RAN can perform resource establishment with the UE.
[0540] In step 14, the RAN can acknowledge the N2 PDU session request by sending an N2 PDU session acknowledgment message to the AMF.
[0541] In some embodiments, for the consumer (e.g., NG-RAN) and the UE / backup device, the consumer (e.g., NG-RAN) and the UE / backup device support reporting M2R2PT information to the first UP NF / PSA UPF / access UPF / serving UPF (directly or indirectly, for example, reported from the UE / backup device to the PSA UPF via the RAN, reported from the RAN / UE / backup device to the serving UPF via the access UPF, or reported from the UE to the PSA UPF or serving UPF via the backup device).
[0542] In some embodiments, the consumer (e.g., NG-RAN) and the UE / backup device perform M2R2PT monitoring measurements (e.g., M2R2PT and / or round-trip time, UE processing time, backup device processing time, round-trip time between the UE and the backup device, server processing time), i.e., perform monitoring and reporting for M2R2PT, based on instructions from the second CP NF / SMF (e.g., M2R2PT reporting rules) and, optionally, local configuration of operator policies.
[0543] In some embodiments, the consumer (e.g., NG-RAN) and the UE / backup device should be able to support reporting based on different triggering events.
[0544] In some embodiments, M2R2PT monitoring information should be collected in the consumer (e.g., NG-RAN) and UE / backup equipment and reported to the first UP NF / PSA UPF / access UPF / service UPF based on monitoring keywords and triggering events.
[0545] In some embodiments, the consumer (e.g., NG-RAN) and the UE / backup device implement authorized QoS configurations (including M2R2PT-related QoS parameters, or delay QoS parameters mapped from M2R2PT, such as round-trip delay or UL and DL delay, UE and backup device processing time, and server processing time) and / or adjust resource management, taking into account information provided by the second CP NF / SMF.
[0546] In step 15, the AMF forwards the N2 SM information received from the AN to the SMF through the Nsmf_PDUSession_UpdateSMContext service operation.
[0547] In step 16, SMF responds with an Nsmf_PDUSession_UpdateSMContext response.
[0548] In steps 17 and 18, the SMF can update the N4 session of the UPF involved in the PDU session modification by sending an N4 session modification request message to the UPF.
[0549] In step 19, there is a service data stream of downlink immersive service from a third-party AS or proxy AS in the public land mobile network (PLMN) and a UL immersive service data stream from the UE or a downstream device.
[0550] In some embodiments, taking into account M2R2PT monitoring policies and monitoring information, the first UP NF / PSA UPF / access UPF / NG-RAN / serving UPF implements M2R2PT monitoring for immersive SDFs. Reports are provided to the first UP NF by the access UPF / NG-RAN / UE / backup device.
[0551] In some embodiments, the first UP NF / PSA UPF / access UPF / service UPF performs M2R2PT monitoring measurements (e.g., M2R2PT and / or round-trip time, UE processing time, downstream device processing time, round-trip time between UE and downstream device, server processing time), that is, performs monitoring and reporting for M2R2PT based on instructions from the second CP NF / SMF (e.g., M2R2PT reporting rules) and, optionally, local configuration of operator policies.
[0552] In some embodiments, the first UP NF / PSA UPF / serving UPF receives measurement reports from the RAN / access UPF / UE / backup device.
[0553] In some embodiments, the first UP NF / PSA UPF / serving UPF generates an M2R2PT monitoring report based on the measurement report (e.g., calculating M2R2PT based on round-trip time, UE processing time, downstream device processing time, round-trip time between UE and downstream device, and server processing time).
[0554] In some embodiments, the first UP NF / PSA UPF / service UPF sends an M2R2PT monitoring report to the PCF (e.g., via the second CP NF / SMF based on M2R2PT reporting rules). In some embodiments, the M2R2PT monitoring report can be used by the PCF to make policy decisions and updates for immersive services.
[0555] In some embodiments, M2R2PT monitoring reports are exposed to the data network (e.g., AS / AF) by the first UP NF / PSA UPF / service UPF (e.g., if the DN has subscribed to M2R2PT monitoring).
[0556] In some embodiments, the first UP NF / PSA UPF / service UPF should be able to support reporting based on different triggering events.
[0557] In some embodiments, M2R2PT monitoring information should be collected and reported in the first UP NF / PSA UPF / service UPF based on monitoring keywords and triggering events.
[0558] In some embodiments, for the consumer (e.g., NG-RAN) and the UE / backup device, the consumer (e.g., NG-RAN) and the UE / backup device support reporting M2R2PT information to the first UP NF / PSA UPF / access UPF / serving UPF (directly or indirectly, for example, reported from the UE / backup device to the PSA UPF via the RAN, reported from the RAN / UE / backup device to the serving UPF via the access UPF, or reported from the UE to the PSA UPF or serving UPF via the backup device).
[0559] In some embodiments, the consumer (e.g., NG-RAN) and the UE / backup device perform M2R2PT monitoring measurements (e.g., M2R2PT and / or round-trip time, UE processing time, backup device processing time, round-trip time between the UE and the backup device, server processing time), i.e., perform monitoring and reporting for M2R2PT, based on instructions from the second CP NF / SMF (e.g., M2R2PT reporting rules) and, optionally, local configuration of operator policies.
[0560] In some embodiments, the consumer (e.g., NG-RAN) and the UE / backup device should be able to support reporting based on different triggering events.
[0561] In some embodiments, M2R2PT monitoring information should be collected in the consumer (e.g., NG-RAN) and UE / backup equipment and reported to the first UP NF / PSA UPF / access UPF / service UPF based on monitoring keywords and triggering events.
[0562] In some embodiments, the consumer (e.g., NG-RAN) and the UE / backup device, taking into account information provided by the second CP NF / SMF, implement authorized QoS configuration (including M2R2PT-related QoS parameters, or delay QoS parameters mapped from M2R2PT, such as round-trip delay or UL and DL delay, UE and backup device processing time, and server processing time), and / or adjust resource management.
[0563] In step 20, the M2R2PT monitoring report is exposed to the data network (e.g., AS / AF) by the first UP NF / PSA UPF / service UPF (e.g., if the DN has subscribed to M2R2PT monitoring).
[0564] 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.
[0565] In some embodiments, a flexible QoS-adaptive motion-to-render-to-photon-time (M2R2PT) mechanism for immersive services, including M2R2PT indication and maximum M2R2PT values, as well as authorization and implementation processes between different NFs in the operator network and between the operator network and the data network, is introduced for 6G, particularly for immersive services.
[0566] In some embodiments, it is proposed to support flexible QoS adaptation for immersive services by monitoring and exposing users to motion-to-rendering-to-photon-time, including: RAN / UPF / UE / backup devices performing M2R2PT monitoring measurements and providing them to the UPF, and the first UP NF generating an M2R2PT monitoring report based on the measurement report and exposing it to the data network.
[0567] In some embodiments, the communication system has QoS requirements for 6G immersive services that combine ultra-high resolution, ultra-large bandwidth, and ultra-low latency, especially RTT latency to meet the QoS requirements of dynamic service characteristics such as latency and jitter in interactive scenarios. This includes: authorization management of IS network transmission latency and jitter, perception and latency management of processing capabilities of different UE device types, whether there are downstream devices and the latency impact of various UE downstream devices, and latency management of multi-task and multi-terminal processing in end-to-end network-industry collaboration (e.g., the offloading and latency impact of immersive rendering tasks).
[0568] In some embodiments, the M2R2PT mechanism is introduced to better adapt to the QoS requirements of immersive services (including ultra-high resolution, high frame rate, wide color gamut, high dynamic range, wide viewing angle, and advanced encoding / compression technologies) and the efficient resource management of 6G communications.
[0569] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, this disclosure proposes an apparatus that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network device, etc.) in any of the above methods.
[0570] 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.
[0571] 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.
[0572] Figure 5 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. As shown in Figure 5, the communication device 500 may include at least one of the following: a transceiver module 501 and a processing module 502.
[0573] In some embodiments, the communication device 500 may be a first node. In some embodiments, the transceiver module 501 may be configured to: acquire monitoring information, wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons; and send the monitoring information to a second node via a user. Optionally, the transceiver module 501 may be used to perform at least one of the communication steps (e.g., steps S206, S210, S212, S214, S215, but not limited thereto) performed by the first node in any of the above methods, which will not be elaborated here. Optionally, the processing module 502 may be used to perform at least one of the other steps (e.g., step S213, but not limited thereto) performed by the first node in any of the above methods, which will not be elaborated here.
[0574] In some embodiments, the communication device 500 may be a second node. In some embodiments, the transceiver module 501 may be configured to receive monitoring information sent by the first node through the user plane, wherein the monitoring information is obtained by monitoring the first data stream of the first service with a first delay, and the first delay is used to characterize the duration from motion to rendering to photons. Optionally, the transceiver module 501 may be used to perform at least one of the communication steps (e.g., steps S201, S214, but not limited thereto) performed by the second node in any of the above methods, and will not be elaborated further here.
[0575] In some embodiments, the communication device 500 can be a third node. In some embodiments, the transceiver module 501 can be configured to send monitoring information to the first node, wherein the monitoring information is obtained by monitoring the first data stream of the first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons. Optionally, the transceiver module 501 can be used to perform at least one of the communication steps such as sending and / or receiving performed by the third node in any of the above methods (e.g., steps S208, S209, S210, S211, S212, but not limited thereto), which will not be elaborated here.
[0576] In some embodiments, the communication device 500 can be a terminal. In some embodiments, the transceiver module 501 can be configured to send monitoring information to a third node, wherein the monitoring information is obtained by monitoring a first data stream of a first service with a first delay, the first delay being used to characterize the duration from motion to rendering to photons. Optionally, the transceiver module 501 can be used to perform at least one of the communication steps (e.g., steps S209, S210, S211, but not limited thereto) performed by the terminal in any of the above methods, which will not be elaborated here.
[0577] In some embodiments, the communication device shown in FIG5 can also be implemented as a communication equipment.
[0578] 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.
[0579] 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.
[0580] Figure 6A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. The communication device 6100 can be an MC device, a terminal (e.g., a user equipment), a network device (e.g., a core network device, an access network device), a chip, chip system, or processor that supports the MC device in implementing any of the above methods, a chip, chip system, or processor that supports the terminal in implementing any of the above methods, or a chip, chip system, or processor that supports the network device in implementing any of the above methods. The communication device 6100 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.
[0581] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, 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 6100 can be used to execute any of the above methods. Optionally, one or more processors 6101 can be used to invoke instructions to cause the communication device 6100 to execute any of the above methods.
[0582] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceivers 6102 perform at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S201, S203, S205, S206, S207, S208, S209, S210, S211, S212, S214, S215, S216, but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps S202, S204, S213, but not limited thereto). In optional embodiments, the transceivers may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be used interchangeably; and terms such as receiver, receiving unit, receiver, and receiving circuit can be used interchangeably.
[0583] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Optionally, all or part of the memories 6103 may be located outside the communication device 6100. In optional embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memories 6103 and can be used to receive data from the memories 6103 or other devices, and to send data to the memories 6103 or other devices. For example, the interface circuits 6104 can read data stored in the memories 6103 and send that data to the processor 6101.
[0584] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. 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.
[0585] Figure 6B 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 6100 can be a chip or a chip system, please refer to the schematic diagram of the chip 6200 shown in Figure 6B, but it is not limited thereto.
[0586] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.
[0587] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Optionally, all or part of the memories 6203 may be located outside chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data from memory 6203 or other devices, and interface circuit 6202 can be used to send data to memory 6203 or other devices. For example, interface circuit 6202 can read data stored in memory 6203 and send the data to processor 6201.
[0588] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S201, S203, S205, S206, S207, S208, S209, S210, S211, S212, S214, S215, S216, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 6202 performing data interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S202, S204, S213, but not limited thereto).
[0589] 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.
[0590] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 6100, cause the communication device 6100 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.
[0591] This disclosure also provides a program product that, when executed by a communication device 6100, causes the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.
[0592] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
Claims
A communication method performed by a first node, wherein The method comprises: obtaining monitoring information, wherein the monitoring information is obtained by performing monitoring of a first time delay on a first data flow of a first service, the first time delay being used to represent a time length from motion to rendering to photon; sending the monitoring information to a second node through a user plane. The method of claim 1, wherein, The obtaining of the monitoring information comprises at least one of: receiving monitoring information of the first time delay sent by a third node; locally obtaining monitoring information of the first time delay. The method of claim 2, wherein, The monitoring information received from the third node comprises at least one of: monitoring information obtained by the third node performing monitoring of the first time delay; monitoring information obtained by a terminal performing monitoring of the first time delay; monitoring information obtained by a device performing monitoring of the first time delay, wherein the device is connected to the terminal. The method of claim 3, wherein, The monitoring information is transmitted on a user plane. The method of any one of claims 2 to 4, wherein, The obtaining of the monitoring information comprises locally obtaining monitoring information of the first time delay, and the method further comprises: performing monitoring of the first time delay. The method of any one of claims 1 to 5, wherein, The monitoring information comprises at least one of: a measured value of the first time delay; a measured value of a round-trip delay of the terminal to the first node; a measured value of an uplink delay of the terminal to the first node; a measured value of a downlink delay of the first node to the terminal; a measured value of a processing delay of the terminal; a measured value of a processing delay of a device; a measured value of a round-trip delay of the terminal to the device; a measured value of a processing delay of the second node; wherein the device is connected to the terminal. The method of claim 6, wherein, The method further comprises: integrating the obtained monitoring information. The method of claim 7, wherein, The integrating of the obtained monitoring information comprises: determining a measured value of the first time delay based on the monitoring information. A communication method, performed by a second node, wherein The method comprises: receiving monitoring information sent by a first node through a user plane, wherein the monitoring information is obtained by performing monitoring of a first time delay on a first data flow of a first service, the first time delay being used to represent a time length from motion to rendering to photon. The method of claim 9, wherein, The monitoring information comprises at least one of: a measured value of the first time delay; a measured value of a round-trip delay of the terminal to the first node; a measured value of an uplink delay of the terminal to the first node; a measured value of a downlink delay of the first node to the terminal; a measured value of a processing delay of the terminal; a measured value of a processing delay of a device; a measured value of a round-trip delay of the terminal to the device; a measured value of a processing delay of the second node; wherein the device is connected to the terminal. A communication method performed by a third node, wherein The method comprises: sending monitoring information to a first node, wherein the monitoring information is obtained by performing monitoring of a first time delay on a first data flow of a first service, the first time delay being used to represent a time length from motion to rendering to photon. The method of claim 11, wherein, The monitoring information is transmitted on a user plane. The method according to claim 11 or 12, wherein The method further comprises at least one of: receiving monitoring information of the first time delay from a terminal; locally obtaining monitoring information of the first time delay. The method of claim 13, wherein, The monitoring information received from the terminal comprises at least one of: monitoring information obtained by the terminal performing monitoring of the first time delay; monitoring information obtained by a device performing monitoring of the first time delay, wherein the device is connected to the terminal. The method according to claim 13 or 14, wherein The monitoring information comprises monitoring information of the first latency obtained locally, and the method further comprises: performing monitoring of the first latency. The method of any one of claims 11 to 15, wherein, The monitoring information comprises at least one of: a measurement of the first latency; a measurement of a round-trip delay of the terminal to the first node; a measurement of an uplink delay of the terminal to the first node; a measurement of a downlink delay of the first node to the terminal; a measurement of a processing delay of the terminal; a measurement of a processing delay of a device; a measurement of a round-trip delay of the terminal to the device; a measurement of a processing delay of a second node; wherein the device is connected to the terminal. A communication method performed by a terminal, wherein The method comprises: sending monitoring information to a third node, wherein the monitoring information is obtained by performing monitoring of a first latency of a first data flow of first service, and the first latency is used to represent a time length from motion to rendering to photon. The method of claim 17, wherein, The monitoring information is transmitted on a user plane. The method according to claim 17 or 18, wherein The monitoring information comprises at least one of: monitoring information obtained by the terminal performing monitoring of the first latency; monitoring information obtained by a device performing monitoring of the first latency, wherein the device is connected to the terminal. The method of any one of claims 17 to 19, wherein The method further comprises at least one of: performing monitoring of the first latency; receiving monitoring information of the first latency sent by a device, wherein the device is connected to the terminal. The method of any one of claims 17-20, wherein The monitoring information comprises at least one of: a measurement of the first latency; a measurement of a round-trip delay of the terminal to the first node; a measurement of an uplink delay of the terminal to the first node; a measurement of a downlink delay of the first node to the terminal; a measurement of a processing delay of the terminal; a measurement of a processing delay of a device; a measurement of a round-trip delay of the terminal to the device; a measurement of a processing delay of a second node; wherein the device is connected to the terminal. A communication device, wherein, The communication device is configured to perform the communication method according to any one of claims 1-8, 9-10, 11-16, 17-21. A communication system wherein, The communication system comprises a first node, a second node, a third node and a terminal, the first node is configured to implement the communication method according to any one of claims 1-8, the second node is configured to implement the communication method according to any one of claims 9-10, the third node is configured to implement the communication method according to any one of claims 11-16, and the terminal is configured to implement the communication method according to any one of claims 17-21. A storage medium storing instructions, wherein, The instructions, when executed on the communication device, cause the communication device to implement the communication method according to any one of claims 1-8, 9-10, 11-16, 17-21. A program product comprising at least one of a program, instructions, wherein The program, instructions, at least one of which is executed by the communication device, implement the communication method according to any one of claims 1-8, 9-10, 11-16, 17-21.
