Signaling Jitter Statistics

Abstract

A method implemented by a network node, the method including obtaining jitter information (JI), where the JI may include jitter range information indicating a jitter range. The method also includes transmitting, to a node of an access network, a message including time-sensitive communication (TSC) assistance information, the TSC assistance information including periodicity information and the JI.

Description

[Technical Field]

[0001] SUMMARY OF THE INVENTION Embodiments are disclosed that relate to signaling jitter statistics. [Background technology]

[0002] Extended Reality (XR) Traffic Characteristics

[0003] XR applications (e.g., virtual reality (VR) applications, augmented reality (AR) applications, and mixed reality (MR) applications) generally generate data traffic flows that are periodic in principle (e.g., video traffic with 30, 60, 90, or 120 fps). However, the traffic arrival instant at a network node (e.g., a base station in a radio access network (RAN)) is affected by jitter around the periodicity value due to the processing of data (frames) in the application (e.g., for compression) and the capabilities of the platform used by the application, as well as transmission through the network (e.g., a 3GPP core network). This is modeled in [4] by assuming that each data frame arriving at the RAN has a random jitter of [-4; +4] milliseconds (ms) (arbitrarily [-5; +5] ms) around the main periodicity. The probability of a jitter value within this interval is given by a truncated Gaussian distribution with a mean of 0 ms and a standard deviation of 2 ms.

[0004] XR traffic has strict delay requirements in terms of packet delay budget (PDB), which is the maximum allowable delay for a packet to be transmitted from a base station (e.g., a 5G base station (gNB)) to a user equipment (UE). PDB values ​​depend on the XR traffic type and generally lie between 5 ms and 30 ms (see reference [4]).

[0005] Time Sensitive Communication (TSC) Support Information (TSCAI)

[0006] The TSC Assistance Information (TSCAI) is a 5G system feature that describes TSC flow traffic characteristics at the gNB ingress and UE egress interfaces for traffic in the downlink and uplink directions. The TSCAI can be used by the 5G access network (5G-AN) when provided by the session management function (SMF).

[0007] The current TSCAI includes the following parameters, which can be seen in Table 1 below (see also Reference [2]): TIFF2025537013000002.tif72170

[0008] The information contained in the TSCAI originates from the Application Function (AF). The information is propagated to the Time Sensitive Communications and Time Synchronization Function (TSCTSF) via the Network Publishing Function (NEF). Based on the information provided, the TSCTSF constructs the TSC Support Container (TSCAC), specified below in Table 2. TIFF2025537013000003.tif72170

[0009] The TSCAC is sent to the SMF. The SMF generates the TSCAI from the TSCAC. If the UPF is also connected to an external clock, the SMF can potentially adjust the information element (IE) inside the TSCAC when generating the TSCAI to account for clock drift. The TSCAI is then sent from the SMF to the 5G-AN via the Access and Mobility Management Function (AMF) using the Next Generation Application Protocol (NGAP). The TSCAI is associated with a single TSC QoS flow. Summary of the Invention

[0010] Currently, several challenges exist. For example, in the context of XR and media services, IP traffic is periodic in nature but suffers from jitter. To help the RAN configure UE power saving features, traffic jitter statistics must be known per application flow and signaled to the RAN.

[0011] Thus, in one aspect, a method is provided that includes a network node (control plane node or user plane node) obtaining jitter information (JI), where the JI may include jitter range information indicating a jitter range. The method also includes the network node transmitting a message including time-sensitive communication (TSC) assistance information to a node of an access network. The TSC assistance information includes periodicity information and the JI.

[0012] In another aspect, a method is provided that includes a node of an access network receiving a message including time-sensitive communication (TSC) assistance information associated with a UE. The TSC assistance information includes periodicity information and jitter information (e.g., jitter range information). The method also includes using the JI to configure power saving features for the UE.

[0013] In another aspect, a computer program is provided comprising instructions that, when executed by a processing circuitry of the device, cause the device to perform any of the methods disclosed herein. In one embodiment, a carrier containing the computer program is provided, the carrier being one of an electronic signal, an optical signal, a radio signal, and a computer-readable storage medium. In another aspect, an apparatus (e.g., a network node) configured to perform the methods disclosed herein is provided. The apparatus may include a memory and a processing circuitry coupled to the memory.

[0014] An advantage of the embodiments disclosed herein is that they provide the RAN with information not only about jitter statistics but also about the origin of the jitter statistics. This feature allows the RAN to use this information to decide how to configure power saving features for the UE for optimal latency / UE power consumption trade-off. For example, the RAN can use the information to configure the value of the DRX onDurationTimer (the number of subframes in which the UE shall read the PDCCH during every DRX cycle before entering power saving mode (DRX off)). For example, if the jitter range is derived from an application generating and / or consuming data traffic, it includes only application jitter without additional jitter from the CN. Therefore, the RAN can decide to set the onDurationTimer value to be longer than the signaled jitter range by a certain margin to take into account unknown additional jitter caused by the CN. As another example, if the jitter range is derived by the CN, this jitter range includes both application jitter and CN jitter. Therefore, this jitter range is closer to the jitter in the RAN, and therefore the onDurationTimer value may be set in a more conservative manner, i.e., approximately the same as the jitter range. Another advantage is that embodiments allow the CN to maintain historical information about a user of jitter statistics, which can be used to provide a better estimate of the jitter statistics the next time the UE uses the same service.

[0015] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various embodiments. [Brief explanation of the drawings]

[0016] [Figure 1] A diagram showing the user plane interface for NG-U. [Figure 2] A diagram showing the user plane interface for NG-U. [Figure 3] A diagram showing an architecture for separation of gNB-CU-CP and gNB-CU-UP. [Figure 4] FIG. 1 illustrates a control plane function that provides messages containing jitter statistics to RAN nodes. [Figure 5] FIG. 1 illustrates a user plane function that provides messages containing jitter statistics to a RAN node. [Figure 6] 1 is a flowchart illustrating a process according to one embodiment. [Figure 7] 1 is a flowchart illustrating a process according to one embodiment. [Figure 8] FIG. 2 is a block diagram of a network node according to one embodiment. [Figure 9] FIG. 2 is a block diagram of a base station according to one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0017] User Plane Interface

[0018] Figures 1 and 2 show the user plane interface for the NG-U, sometimes called the N3 interface between the UPF and the NG-RAN, as well as the Xn-U between two NG-RAN nodes.

[0019] 3 shows the overall architecture of a gNB 301 with a separation between a gNB-CU-CP 302 and a gNB-CU-UP 304. The gNB-CU-UP is connected to at least one gNB-DU 306 of the gNB 301 through an F1-U interface. Note that GTP-Uv1, as specified in 3GPP TS29.281 v17.1.0 (“TS29.281”), is used on the N3 / NG-U interface between the UPF and the NG-RAN / CU-UP, as well as on the F1-U interface between the CU-UP and the DU, and that a different NG-RAN / gNB is configured in the CU-UP, where the Xn-U is established. However, details regarding the contents of the GTP-U header are specified in TS38.415 v16.6.0 ("TS38.415") for NG-U / N3, and TS38.425 v16.3.0 ("TS38.425") is applicable for the F1-U and XN-U interfaces.

[0020] In [5], it was proposed to extend TSCAI to include jitter statistics for each flow. Currently, 3GPP SA2 is discussing whether jitter statistics originate from the application or are derived by the CN in the context of [Error! Reference not found.].

[0021] Therefore, we assume here that jitter statistics can either originate from the application or be derived by the CN. The CN sends this jitter statistics to the RAN. The RAN can use the jitter statistics to optimize the UE power saving settings. For XR traffic, it is important that the UE (e.g., UE 101 shown in FIG. 1) saves energy and at the same time limits the delay. For this purpose, the jitter statistics (also known as jitter statistics or jitter information) (e.g., jitter range (or min / max)) can be used by the RAN to set the value of the onDurationTimer for the MAC DRX mechanism. In principle, the onDurationTimer should cover the jitter range observed by the RAN, so that the UE is awake whenever traffic is expected and sleeps the rest of the time. In some cases, traffic delays are potentially longer than those tolerated by the XR application (if the UE is not awake when traffic arrives) or UE energy is wasted (if the onDurationTimer value is too long).

[0022] Depending on where the jitter statistics originate (either from the application or derived by the CN), the jitter range statistics are a closer or looser approximation of the jitter range at the RAN. Thus, if the RAN receives jitter statistics from the CN but does not know the origin of the jitter statistics, the RAN may set either an onDurationTimer value that is too short or too long.

[0023] Therefore, the present disclosure includes new information in the TSCAI (control plane (CP)) and in-band (user plane (UP)) regarding jitter statistics, which refers to jitter statistics regardless of whether they originate from the application or are derived by the CN.

[0024] Control Plane (CP Signaling):

[0025] In one embodiment, the present disclosure provides a signaling method to indicate this information in the NG-C interface to make the NG-RAN aware of jitter statistics or changes thereto for radio resource allocation and early RAN traffic control.

[0026] User Plane (UP) Signaling:

[0027] In one embodiment, the present disclosure provides a signaling method to indicate jitter statistics or its changes in radio resource allocation and early RAN traffic control in the GTP-U extension header to make the NG-RAN aware of the jitter statistics or its changes in the downlink (DL) signaling and early RAN traffic control.

[0028] In some embodiments, feedback relating to jitter statistics is signaled to the CN, for example, in the UP.

[0029] As mentioned above, the present disclosure enables signaling of jitter statistics over the TSCAI and in-band for both DL and UL.

[0030] Information about the origin of jitter statistics via CP signaling

[0031] In one embodiment, a new attribute (herein denoted "JitterStatisticsOrigin") is added to TSCAI and TSCAC. This attribute can be a value or a list of values, where each value corresponds to a different entry for jitter statistics within the same QoS flow.

[0032] Alternatively, the new attribute may be a flag or a list of flags, where each value corresponds to a different entry for jitter statistics within the same QoS flow. For example, a value of "1" may indicate that the jitter statistics originate from the AF, and a value of "0" may indicate that the jitter statistics originate from the application. Alternatively, the interpretation of "0" and "1" may be swapped.

[0033] CP signaling jitter statistics:

[0034] FIG. 4 illustrates an embodiment in which a CP function (CPF) 401 in a CN 402 (e.g., AMF, SMF, TSCTFS) signals jitter statistics information (JSI) (or "jitter information (JI)" for short) to a network node 404 of an NG-RAN 406 (e.g., a gNB 301 or a component of the gNB 301, such as a CU 302 or CU 304 of the gNB) via a message (msg) 408 (e.g., an NG-AP message).

[0035] In one embodiment, the message 408 includes TSCAI periodicity information associated with the jitter statistics information (JSI) and information indicating the origin of the JSI. For example, the NG-AP message may include an information element (e.g., a "TSC Assistance Information" IE) including: i) periodicity information (e.g., a Periodicity IE containing information indicating the time period between the start of two data bursts); and ii) the JSI (e.g., a JSI IE containing the JSI and, optionally, origin information indicating the origin of the JSI). In one embodiment, the origin information indicates whether the origin is the AF or derived by the CN CP function. In one embodiment, the origin indication (i.e., the origin information) may be coded as an enumerated IE or as a flag 0 / 1, where, for example, 0 = from AF and 1 = derived at the CN.

[0036] In another embodiment, the JSI and origination information are signaled from the CN to the NG-RAN via existing NG-AP procedures, which may be, for example, part of a packet data unit (PDU) session management message as specified in section 9.2.1 of 3GPP TS38.413 v17.2.0 ("TS38.413") (e.g., PDU Session Resource Setup / Modify Request).

[0037] In one alternative embodiment to the above embodiment, a new procedure, for example a Class 2 NG-AP "Traffic Parameter Control" message, is defined to introduce or update jitter statistics from the CN to the NG-RAN node.

[0038] Without loss of generality, the following is a non-limiting example of signaling JSI and origin information by extending the existing CP signaling specified in 3GPP TS38.413.

[0039] TSC Traffic Characteristics IE

[0040] The TSC Traffic Characteristics IE provides traffic characteristics of the TSC QoS flow. Table 3 below shows the TSC Traffic Characteristics IE according to one embodiment. As shown in Table 3, the IE may include downlink (DL) TSC assistance information (i.e., a TSC assistance information IE containing DL assistance information) and / or uplink (UL) TSC assistance information (i.e., a separate TSC assistance information IE containing UL assistance information). TIFF2025537013000004.tif21170

[0041] TSC support information IE

[0042] The TSC Assistance Information IE provides TSC assistance information for TSC QoS flows in the uplink or downlink (see 3GPP TS23.501 v17.6.0 ("TS23.501")). Table 4 shows one embodiment of the TSC Assistance Information IE. The embodiment shown in Table 4 is similar to the TSC Assistance Information IE specified in TS38.413, except that the TSC Assistance Information IE according to the embodiment shown in FIG. 4 includes an additional IE called "Jitter Statistics Information." TIFF2025537013000005.tif37170

[0043] 9.3.1.X Jitter Statistics Information (JSI) IE

[0044] Table 5 shows one embodiment of the JSI IE. In the illustrated embodiment, the JSI IE provides the JSI (eg, jitter range information, maximum value, minimum value) and origin information indicating the origin of the JSI. TIFF2025537013000006.tif32170

[0045] In another embodiment, the NG-RAN can inform the CN of the guaranteed jitter statistics either via the existing NGAP procedure, PDU session setup response, or on the new NGAP Class 2 "Traffic Parameter Feedback" message. Alternatively, the interaction between the CN and the NG-RAN on the NG-C can be achieved via any Class 1 request / response procedure.

[0046] JSI UP signaling:

[0047] FIG. 5 illustrates an embodiment in which a UP node (e.g., UPF) 501 signals jitter statistics information (JSI) to a network node 404 (e.g., gNB 301 or a component thereof) of an NG-RAN 406 via a message 508 (e.g., a GTP message).

[0048] GTP-Uv1, specified in 3GPP TS29.281 v17.1.0 ("TS29.281"), is used on the N3 / NG-U interface between the UPF and NG-RAN / CU-UP, and on the F1-U interface between the CU-UP and DU, where a different NG-RAN / gNB is configured in the CU-UP and where the Xn-U is established. However, details regarding the content of the GTP-U header are specified in 3GPP TS38.415 v16.6.0 ("TS38.415") for NG-U / N3, and 3GPP TS38.425 v16.3.0 ("TS38.425") is applicable for the F1-U and XN-U interfaces.

[0049] In one embodiment, one or more fields are added to the GTP header to provide the JSI as in-band information.

[0050] Using the DL PDU Session Information in TS38.415, an example is shown below, without loss of generality, in Table 6. Table 6 shows a DL PDU Session Information frame according to one embodiment. This frame format is defined to allow the NG-RAN to receive several control information elements related to the forwarding of packets on the interface. TIFF2025537013000007.tif101170

[0051] In another embodiment, the DL user data frame in TS38.425 is extended to carry JSI and origination information as shown in Table 7 below. TIFF2025537013000008.tif140170

[0052] In another embodiment, the DL Data Delivery Status (PDU Type 1) format frame in TS38.425 is extended to carry JSI and origin information as shown in Table 8 below. TIFF2025537013000009.tif203170

[0053] The following explanation applies to each of the three above examples. The jitter statistics origin parameter indicates the origin of the jitter statistics information (i.e., traffic jitter range, minimum, and maximum) contained in the frame. At 1, the jitter statistics origin parameter has a length of 1 bit, with a value of 0 indicating that the origin is the AF function and a value of 1 indicating that the origin is the CN function (i.e., value range: {0=AF, 1=CN}). The traffic flow identifier parameter, when present, indicates the traffic flow identifier of the flow associated with the jitter statistics information. The value range is {0...2 8 -1}, and the length of this field is 8 bits (hence, 0 to 2 8 The traffic jitter range parameter indicates the jitter range for the traffic flow. The value range is {0...2 n -1}, and a field length of m octets. The traffic jitter minimum parameter indicates the minimum jitter value for the identified traffic flow. The value range is {0..2 n -1} and the field length is m octets. The traffic jitter max parameter indicates the maximum jitter value for the traffic flow. The value range is {0..2 n -1} and the field length is m octets.

[0054] 6 is a flow chart illustrating a process 600 for providing jitter statistics (or "jitter information (JI)" for short) according to one embodiment. Process 600 may begin at step s602.

[0055] Step s602 includes a network node (control plane node 401 or user plane node 501) obtaining a JI. In one embodiment, the JI includes jitter range information indicating a jitter range.

[0056] Step s604 includes the network node sending a message (e.g., control plane msg 408 or user plane msg 508) including the JI to a node of the access network (e.g., base station 404 or a CU of that base station). In one embodiment, the message includes TSC assistance information, which includes periodicity information and the JI (e.g., jitter range information).

[0057] In one embodiment, the periodicity information indicates the time period between the start of two data bursts.

[0058] In one embodiment, the message is a session management message.

[0059] In one embodiment, the session management message requests a node of the access network to allocate PDU resources.

[0060] In one embodiment, the network node comprises a Session Management Function (SMF).

[0061] In one embodiment, the network node includes or consists of a control unit (CU) (e.g., a CU of a gNB, such as a gNB-CU-CP or gNB-CU-UP), and the node of the access network includes or consists of a distributed unit (DU) (e.g., a DU of a gNB).

[0062] In one embodiment, the JI included in the message further includes origin information indicating the origin of the JI. In one embodiment, the origin information is a single bit. In one embodiment, when the bit is set to a first value, the origin information indicates that the origin of the JI is an application function, and when the bit is set to a second value, the origin information indicates that the origin of the JI is a core network function.

[0063] In one embodiment, the message containing the JI is a control plane message, such as, for example, an F1 interface message or an Xn interface message or other control plane message.

[0064] 7 is a flowchart illustrating a process 700, according to one embodiment. Process 700 may begin at step s702.

[0065] Step s702 includes a node of the access network receiving a message (e.g., control plane msg408 or user plane msg508) including a JI associated with the UE. In one embodiment, the JI includes jitter range information. In one embodiment, the message includes TSC assistance information, which includes periodicity information and the JI (e.g., jitter range information).

[0066] Step s704 includes the node using the JI to configure power saving features for the UE (eg, setting a DRX timer, such as the duration of the "on time" within one DRX cycle).

[0067] 8 is a block diagram of a network node 800 that may implement a CU 302, a CU 304, a CPF 401, or a user plane node 501, according to some embodiments. As shown in FIG. 8, the network node 800 includes a processing circuit (PC) 802 that includes one or more processors (P) 855 (e.g., one or more general-purpose microprocessors and / or one or more other processors, such as application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), etc.), which may be co-sited in a single housing or in a single data center or may be geographically distributed (i.e., the network node 800 may be a distributed computing device), and at least one network interface 848 (e.g., a physical interface or an air interface) that interfaces with the network node 800. The PC 802 may comprise at least one network interface 848, a transmitter (Tx) 845, and a receiver (Rx) 847 for enabling the network node 800 to transmit data to and receive data from other nodes connected to the network 110 (e.g., an Internet Protocol (IP) network) to which the network interface 848 is connected (physically or wirelessly) (e.g., the network interface 848 may be coupled to an antenna configuration comprising one or more antennas for enabling the network node 800 to transmit / receive data wirelessly), and a storage unit (a.k.a. "data storage system") 808, which may include one or more non-volatile storage devices and / or one or more volatile storage devices. In embodiments in which the PC 802 includes a programmable processor, a computer-readable storage medium (CRSM) 842 may be provided. The CRSM 842 may store a computer program (CP) 843 comprising computer-readable instructions (CRI) 844. The CRSM 842 may be a non-transitory computer-readable medium, such as a magnetic medium (e.g., a hard disk), an optical medium, a memory device (e.g., a random access memory, a flash memory), etc.In some embodiments, the CRI 844 of the computer program 843, when executed by the PC 802, is configured such that the CRI causes the network node 800 to perform the steps described herein (e.g., steps described herein with reference to flowcharts). In other embodiments, the network node 800 may be configured to perform the steps described herein without the need for code. That is, for example, the PC 802 may simply consist of one or more ASICs. Thus, features of the embodiments described herein may be implemented in hardware and / or software.

[0068] 9 is a block diagram of a network node 404, according to some embodiments. As shown in FIG. 9, the network node 404 includes a processing circuit (PC) 902 that includes one or more processors (P) 955 (e.g., a general-purpose microprocessor and / or one or more other processors, such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), which may be co-located in a single housing or in a single data center or may be geographically distributed (i.e., a base station may be a distributed computing device), and a network interface 968 that enables the network node 404 to communicate with the network interface. The PC 902 may comprise a network interface 968 having a transmitter (Tx) 965 and a receiver (Rx) 967 for enabling the UE to transmit data to and receive data from other nodes connected to the network 110 (e.g., an Internet Protocol (IP) network) to which the PC 902 is connected, a communication circuit 948 (e.g., a wireless transceiver circuit comprising Rx 947 and Tx 945) coupled to an antenna system 949 for wireless communication with the UE or other nodes, and a storage unit (a.k.a. "data storage system") 908, which may include one or more non-volatile storage devices and / or one or more volatile storage devices. In embodiments in which the PC 902 includes a programmable processor, a computer-readable storage medium (CRSM) 942 may be provided. The CRSM 942 may store a computer program (CP) 943 comprising computer-readable instructions (CRI) 944. The CRSM 942 may be a non-transitory computer-readable medium, such as a magnetic medium (e.g., a hard disk), an optical medium, a memory device (e.g., a random access memory, a flash memory), etc. In some embodiments, the CRI 944 of the computer program 943 is configured such that, when executed by the PC 902, the CRI causes the network node 404 to perform the steps described herein (e.g., the steps described herein with reference to one or more flowcharts).In other embodiments, the network node 404 may be configured to perform the steps described herein without the need for code. That is, for example, the PC 902 may simply consist of one or more ASICs. Thus, features of the embodiments described herein may be implemented in hardware and / or software.

[0069] Additional Embodiments

[0070] A1. A method including a network node (CU302, 304, control plane node 401, or user plane node 501) obtaining a JSI, and the network node sending a message including the JSI to a node of an access network (e.g., base station 404 or DU306).

[0071] A2. A method comprising: a node of an access network receiving a message including a JSI associated with a user equipment (UE); and the node using the JSI to configure power saving features for the UE (e.g., configuring a DRX timer, such as the duration of an "on time" within one DRX cycle).

[0072] A3. The method of embodiment A1 or A2, wherein the message further includes origin information indicating the origin of the JSI.

[0073] A4. The method of embodiment A3, wherein the origin information is a single bit.

[0074] A5. The method of embodiment A4, wherein when the bit is set to a first value, the origination information indicates that the origin of the JSI is an application function, and when the bit is set to a second value, the origination information indicates that the origin of the JSI is a core network function.

[0075] A6. The method of any one of embodiments A1 to A5, wherein the message is a control plane message.

[0076] A7. The method of any one of embodiments A1 to A6, wherein the message is a user plane message.

[0077] B1. A computer program (843) comprising instructions (844) that, when executed by processing circuitry (802) of a network node, cause the network node to perform a method as described in A1 or any one of A3 to A7.

[0078] B2. A computer program (943) comprising instructions (944) that, when executed by processing circuitry (902) of a node of an access network, cause the node to perform a method according to any one of A2 to A7.

[0079] B3. A carrier containing the computer program of embodiment B1 or B2, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer-readable storage medium (842, 942).

[0080] C1. A network node, the network node comprising a processing circuit and a memory including instructions executable by the processing circuit for configuring the network node to perform a process, the process including obtaining a JSI and sending a message including the JSI to a node of an access network (e.g., a base station 404).

[0081] C2. The network node of embodiment C1, wherein the network node is configured to perform the method of any one of embodiments A3 to A7.

[0082] D1. A node for use in an access network, the node comprising: processing circuitry; and memory comprising instructions executable by the processing circuitry for configuring the node to perform a process, the process comprising receiving a message including a JSI associated with a user equipment (UE); and using the JSI to configure power saving features for the UE (e.g., setting a DRX timer, such as the duration of an "on time" within one DRX cycle).

[0083] D2. The network node of embodiment D1, wherein the network node is configured to perform the method of any one of embodiments A2 to A7.

[0084] conclusion

[0085] As detailed above, the present disclosure relates to signaling jitter statistics from the Core Network (CN) to the RAN, and involves signaling as an attribute of the Time Sensitive Communications Assistance Information (TSCAI). For example, the present disclosure proposes a new attribute for jitter statistics in the GTP-U extension header.

[0086] While various embodiments have been described herein, it should be understood that these embodiments have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, unless otherwise indicated herein or clearly contradicted by context, any combination of the above-described elements in all possible variations thereof is encompassed by the present disclosure.

[0087] As used herein, sending a message "to" or "toward" an intended recipient encompasses sending the message directly to the intended recipient or sending the message indirectly to the intended recipient (i.e., one or more other nodes are used to relay the message from the source node to the intended recipient). Similarly, as used herein, receiving a message "from" a sender encompasses receiving the message directly from the sender or receiving the message indirectly from the sender (i.e., one or more nodes are used to relay the message from the sender to the receiving node). Additionally, as used herein, "a" means "at least one" or "one or more."

[0088] Additionally, while the processes described above and illustrated in the figures have been shown as a sequence of steps, this has been done for purposes of illustration only, and it is therefore contemplated that some steps may be added, some steps may be omitted, the order of steps may be rearranged, and some steps may be performed in parallel.

[0089] References

[0090] [1] 3GPP TR23.700-60 v1.2.0, (2022-10) Research on XR (Extended Reality) and Media Services (Release 18)

[0091] [2] 3GPP TS23.501 v17.6.0(2022-09), Section 5.27 Enablers for Time-Sensitive Communications and Time Synchronization.

[0092] [3]3GPP TS38.413 v17.2.0 (“TS 38.413”)

[0093] [4] 3GPP, TR38.838 V17.0.0(2021-12), “Research on XR (Extended Reality) Evaluation for 4R.”

[0094] [5] International Patent Publication No. WO2013187014, “TIME SENSITIVE COMMUNICATION ASSISTANCE INFORMATION.”

[0095] [6]3GPP TS38.415 v17.0.0.

[0096] [7]3GPP TS38.425 v17.1.0.

Claims

1. A method (600) implemented by a network node (302, 304, 401, 501, 800), said method comprising: Obtaining jitter information (JI) (s602); Sending (s604) to a node (301, 306, 404) of an access network (406) a message (408, 508) including time-sensitive communication (TSC) support information, wherein the TSC support information is: periodicity information; The above JI and Sending (s604) a message (408, 508) including: The method (600) includes:

2. The method of claim 1 , wherein the periodicity information indicates a time period between the start of two data bursts.

3. The method of claim 1 or 2, wherein the message is a session management message.

4. 4. The method of claim 3, wherein the session management message requests the node of the access network to allocate packet data unit (PDU) resources.

5. the network node comprises a Session Management Function (SMF), or The network nodes comprise control units (CU) (302, 304), and the nodes of the access network comprise distribution units (DU) (306), 5. The method according to any one of claims 1 to 4.

6. The method according to claim 1 , wherein the JI included in the message further includes origin information indicating the origin of the JI.

7. The method of claim 6 , wherein the origin information is a single bit.

8. When the single bit is set to a first value, the origin information indicates that the origin of the JI is an application function; When the single bit is set to a second value, the origin information indicates that the origin of the JI is a core network function. The method of claim 7.

9. The method of claim 1 , wherein the message is a control plane message, such as an F1 interface message or an Xn interface message.

10. The method of claim 1 , wherein the JI includes jitter range information indicating a jitter range.

11. A method (700) implemented by a node (301, 306, 404) of an access network (406), said method comprising: Receiving (s702) a message (408, 508) containing time-sensitive communication (TSC) support information associated with a user equipment (UE) (101), wherein the TSC support information is: periodicity information; Jitter information (JI) receiving (s702) a message (408, 508) including: using the JI to configure power saving features for the UE (s704); A method (700) comprising:

12. The method of claim 11 , wherein the periodicity information indicates a time period between the start of two data bursts.

13. The method of claim 11 or 12, wherein the message is a session management message.

14. 14. The method of claim 13, wherein the session management message requests the node of the access network to allocate packet data unit (PDU) resources.

15. the message is sent by a network node (302, 304, 401, 501); the network node comprises a Session Management Function (SMF), or the network nodes comprise control units (CU) (302, 304), and the nodes of the access network comprise distribution units (DU) (306); 15. The method according to any one of claims 11 to 14.

16. The method according to claim 11 , wherein the JI included in the message further includes origin information indicating the origin of the JI.

17. The method of claim 16 , wherein the origin information is a single bit.

18. When the single bit is set to a first value, the origin information indicates that the origin of the JI is an application function; When the single bit is set to a second value, the origin information indicates that the origin of the JI is a core network function.

18. The method of claim 17.

19. 19. The method of any one of claims 11 to 18, wherein the message is a control plane message, such as an F1 interface message or an Xn interface message.

20. 20. The method of claim 11, wherein the JI includes jitter range information.

21. A network node (302, 304, 401, 501, 800), said network node comprising: A processing circuit (802); a memory (842) storing instructions (844) executable by said processing circuitry for configuring said network node to perform a process; wherein the process comprises: Acquiring jitter information (JI) (s602), wherein the JI includes jitter range information indicating a jitter range; Sending (s604) to a node (301, 306, 404) of an access network (406) a message (408, 508) including time-sensitive communication (TSC) support information, wherein the TSC support information is: periodicity information; the JI including the jitter range information; Sending (s604) a message (408, 508) including: A network node (302, 304, 401, 501, 800) including:

22. 12. The network node according to claim 11, wherein the network node is further configured to perform the method according to any one of claims 2 to 10.

23. A node (301, 306, 404) for use in an access network (406), said node comprising: A processing circuit (902); a memory (942) storing instructions (944) executable by said processing circuitry for configuring said node to perform a process; wherein the process comprises: Receiving (s702) a message (408, 508) containing time-sensitive communication (TSC) support information associated with a user equipment (UE) (101), wherein the TSC support information is: periodicity information; Jitter information including jitter range information and receiving (s702) a message (408, 508) including: using the JSI to configure power saving features for the UE (s704); Nodes (301, 306, 404) including:

24. 24. A network node according to claim 23, further configured to perform a method according to any one of claims 12 to 20.

Images