EP4681478A1

EP4681478A1 - Methods and apparatuses for handling ue traffic assistance and device information in dual connectivity

Info

Publication number: EP4681478A1
Application number: EP24712239.3A
Authority: EP
Inventors: Nianshan SHI; Mohammed Yazid LYAZIDI; Fabian DE LAVAL; Richard TANO
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-03-15
Filing date: 2024-03-15
Publication date: 2026-01-21
Also published as: WO2024189225A1; KR20250159719A

Abstract

A method performed by a user equipment (UE) in a dual connectivity (DC) mode with a master node (MN) and a secondary node (SN) is provided. The method includes determining traffic assistance and device information (TADI) for the UE. The method includes sending the TADI towards one or more of the MN and SN.

Description

METHOD FOR HANDLING UE TRAFFIC ASSISTANCE AND

DEVICE INFORMATION IN DUAL CONNECTIVITY

TECHNICAL FIELD

[0001] Disclosed are embodiments related to a method for handling user equipment (UE) traffic assistance and device information (TADI) in dual connectivity (DC).

BACKGROUND

[0002] Extended Reality (XR ) Traffic Characteristics

[0003] XR applications typically generate traffic flows which are, in principle, periodic, e.g., video traffic with 30, 60, 90, or 120 frames per second (fps). However, the traffic arrival moment at the Radio Access Network (RAN) is affected by jitter around the periodicity value, due to processing of the frames at the application (e.g. for compression) and the capabilities of the platform used by the application, as well as transmission through the Core Network (CN). This is modelled in the Third Generation Partnership Project (3GPP) Technical Report (TR) 38.838, by assuming that each data frame arriving at the RAN has a random jitter of [-4; +4] ms (optionally [-5; +5] ms) around the main periodicity. The probability of the jitter value within this interval is given by a truncated Gaussian distribution with mean 0 ms and standard deviation 2 ms.

[0004] However, it is expected that XR traffic is more dynamic than this. In response to events, e.g. network events (such as congestion indications) or application/user triggered events, XR traffic is likely to adapt/change its traffic pattern. For example, an application may react to a congestion notification by lowering the transferred video quality, e.g., lowering the bitrate. In another example, the application may react by lowering the frame rate, for example from 90 fps to 30 fps. Such adaptation is likely to impact the characteristics of the traffic pattern, e.g., periodicity.

[0005] XR traffic has strict delay requirements, in terms of packet delay budget (PDB). PDB is the maximum tolerable delay for a packet to be transmitted from a gNB to a UE. The PDB value depends on the XR traffic type and is overall between 5 ms and 30 ms.

[0006] 3 GPP Background SA2 Conclusions, RAN2 Agreements [0007] In 3GPP, the working group (WG) System Architecture 2 (SA2) has concluded in the study item: “Study on XR (Extended Reality) and media services” for Rel-18 in 3GPP TR 23.700-60vl.3.0 that:

“The following information, to be provided to the NG-RAN [i.e., Next Generation (NG)-RAN] at PDU [i.e., Protocol Data Unit (PDU)] Session Establishment/Modification via an NGAP [i.e., NG Application Protocol (NGAP)] Message, is taken as baseline for normative work:

-Periodicity for UL [i.e., uplink (UL)] and DL [i.e., downlink (DL)] traffic of the QoS [i.e., Quality of Service (QoS)] Flow. In addition to integer periodicity values, non-integer values associated to, e.g. 15 FPS, 30 FPS, 45FPS, 60 FPS, 72 FPS, 90FPS, 120FPS, shall be supported. Such information shall be exchanged by re-using/extending the TSCAI [i.e., Time Sensitive communication (TSC) Assistance Information (Al) (TSCAI)]/TSCAC [i.e., TSC Assistance Container (AC) (TSCAC)] definitions in clause 5.27.2.1 of TS 23.501 [2],

NOTE 1 : The above information can be provided to the 5GC [i.e., 5G Core (5GC)] by the AF [i.e., Application Function (AF)] via an NEF [i.e., Network Exposure Function (NEF)] API. The 5GC can further derive, or be configured, with such information.

-Traffic jitter information (e.g. jitter range) associated with each periodicity. The SMF [i.e., Session Management Function (SMF)] requests the UPF [i.e., User Plane Function (UPF)] to derive jitter (i.e. N6 jitter) for a given periodicity. 5GC derives jitter information accordingly and forwards it to the RAN along with periodicity.

NOTE 2: How the UPF derives the jitter is left for implementation. How the SMF obtains and provides the jitter information will be defined in the normative phase.”

[0008] In addition, the RAN2 WG has in the study item: “Study on XR enhancements for NR [i.e., New Radio (NR)]” for Rel-18 accepted the SA2 conclusions and stated the following in TR 38.835: Delivery of some assistance information (e.g. periodicity) reusing TSCAI as a baseline. Whether additional mechanism is required can be further considered with an assumption that all information may not be always available at UE application.”

[0009] Furthermore, RAN2 has in a new work item (New WID [i.e., Work Item Description (WID)] for XR Enhancements RP-223502) on capacity enhancements for XR agreed to:

“Specify the enhancements related to capacity:

- Multiple CG PUSCH transmission occasions in a period of a single CG PUSCH configuration (RANI, RAN2);

- Dynamic indication of unused CG PUSCH occasion(s) based on UCI by the UE (RANI);

- BSR enhancements including at least new BS Table(s); (RAN2);

- Delay reporting of buffered data in uplink; (RAN2);

- Provision of XR traffic assistance information for DL and UL (e.g. periodicity); (RAN2);

- Discard operation of PDU Sets (RAN2);

[0010] In this disclosure, the penultimate item in the list above (Provision of XR traffic assistance information for DL and UL (e.g. periodicity); (RAN2)) is most relevant.

[0011] The term PDU Set has been defined by 3GPP working group SA2 in 3GPP TR 23.700-60 (Study on XR (Extended Reality) and media services Rel 18) and accepted by RAN2 in TR 38.835 (Study on XR enhancements for NR) and is defined as:

PDU Set: A PDU Set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. a frame or video slice for XRM Services [i.e., Extended Reality and Media services (XRM)], as used in TR 26.926 [6]). In some implementations all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, the application layer can still recover parts or all of the information unit, when some PDUs are missing.

[0012] 5G RAN Architecture

[0013] The overall 5G RAN (NG-RAN) architecture is depicted in FIG. 1. As shown, the 5GC 102 communicates with the NG-RAN 104 over an NG reference point (e.g., an N2 or N3 interface). The NG-RAN 104 comprises a base station such as gNB 106 and gNB 108. gNB 106 and gNB 108 may communicate over an Xn control plane (Xn-C) interface. gNB 108 is shown as comprising a gNB centralized unit (gNB-CU) 110, a gNB distributed unit (gNB-DU) 112, and gNB-DU 114. gNB 108 may have fewer gNB-DU, or may have more gNB-DU. Similarly, gNB 106 may include a gNB-CU and one or more gNB-DU. As shown, the gNB-CU 110 may communicate with the gNB-DU 112,114 over an Fl interface.

[0014] The gNB may have a split architecture such as is depicted in FIG. 2. FIG. 2 shows gNB 108 in more detail, where gNB-CU 110 is split into a gNB-CU control plane (gNB- CU-CP) 202 and one or more gNB-CU user planes (gNB-CU-Ups) 204. The gNB-CU-CP 202 may communicate with the gNB-CU-UP 204 over an El interface. The gNB-CU-CP 202 may communicate with the gNB-DU 112, 114 over an Fl control plane (Fl-C) interface. The gNB- CU-UP 204 may communicate with the gNB-DU 112, 114 over an Fl user plane (Fl-U) interface. The gNB-CU 110 hosts the radio resource control (RRC) and the control plane part of the packet data convergence protocol PDCP). The gNB-DU 112, 114 hosts radio link control (RLC), medium access control (MAC), and the physical layer.

[0015] As shown in FIG. 3, in Dual Connectivity, the master node (MN) 302 and secondary node (SN) 304 host separate RRC in control plane and MAC layers in user plane. MN 302 and SN 304 may serve UE 306. MN 302 and SN 304 may be a base station, such as gNB 106, 108. UE 306 may support multiple bearers, such as a master cell group (MCG) bearer, a split bearer, and a secondary cell group (SCG) bearer, which interact with the Service Data Adaptation Protocol (SDAP) of UE 306, and NR PDCP, MN RLC, MN MAC, SN RLC, and SN MAC layers as shown in FIG. 3.

[0016] In rel-17, up to 4 RLC entity are used in multi-radio DC (MR-DC) duplication, as shown in FIG. 4. [0017] REFERENCES

• Third Generation Partnership Project (3 GPP) Technical Specification (TS) 38.473 (NG-RAN; Fl Application Protocol (Fl AP))

• 3GPP TS 38.423 (NG-RAN; Xn Application Protocol (XnAP))

• 3GPP TS 38.425 (NG-RAN; NR user plane protocol)

SUMMARY

[0018] In case of MR-DC, nodes need to receive the information from the UE, e.g. via

UE Assistance Information (UAI) for scheduling and coordination purposes. Currently, however, there is no solution for providing XR or time sensitive assistance information received from the UE in case of Dual Connectivity configuration and making use of it in the RAN and CN. Embodiments herein provide methods to signal to the network in Dual Connectivity (e.g., from the UE to base station, such as gNB) such XR and time sensitive assistance information (e.g., jitter information, burst arrival time), and, more generally, a UE’s traffic and device related information, which is referred to here as a UE’s Traffic Assistance and Device Information (TADI). Embodiments provide for signaling this information within a dual connectivity network scenario, so that the entity or leg of the network that uses the information can obtain it and use it for coordination among nodes and scheduling. Embodiments further provide, as needed, for sending the TADI, or information determined therefrom, towards the CN.

[0019] The term Traffic Assistance and Device Information (TADI) is used herein, but other terms, e.g., UE Assistance Traffic Information (UAH), could also be used to describe this information. Broadly, TADI (or UATI) refer to information about a UE’s traffic or about the device that can assist nodes or functions in the network, e.g., in serving the UE more effectively.

[0020] According to a first aspect, a method performed by a user equipment (UE) in a dual connectivity (DC) mode with a master node (MN) and a secondary node (SN) is provided. The method includes determining traffic assistance and device information (TADI) for the UE. The method includes sending the TADI towards one or more of the MN and SN.

[0021] According to a second aspect, a method performed by a secondary node (SN) supporting a user equipment (UE) in a dual connectivity (DC) mode, where the UE is further supported by a master node (MN), is provided. The method includes receiving traffic assistance and device information (TADI) from one or more of the UE and the MN. The method includes determining that the SN can use the TADI to coordinate with scheduling resources of the SN. The method includes using the TADI to coordinate with scheduling resources of the SN.

[0022] According to a third aspect, a method performed by a secondary node (SN) supporting a user equipment (UE) in a dual connectivity (DC) mode, where the UE is further supported by a master node (MN), is provided. The method includes receiving traffic assistance and device information (TADI) from one or more of the UE and the MN. The method includes determining that the SN cannot use the TADI to coordinate with scheduling resources of the SN. The method includes sending a message towards the MN indicating that the SN cannot use the TADI to coordinate with scheduling resources of the SN.

[0023] According to a fourth aspect, a user equipment (UE) is provided. The UE includes processing circuitry and a memory. The memory contains instructions executable by the processing circuitry, whereby when executed the processing circuitry is configured to determine traffic assistance and device information (TADI) for the UE. The processing circuitry is further configured to send the TADI towards one or more of the MN and SN.

[0024] According to a fifth aspect, a master node (MN) is provided. The MN includes processing circuitry and a memory. The memory contains instructions executable by the processing circuitry, whereby when executed the processing circuitry is configured to receiving traffic assistance and device information (TADI) from the UE. The processing circuitry is further configured to send the TADI towards a core network (CN).

[0025] According to a sixth aspect, a secondary node (SN) is provided. The SN includes processing circuitry and a memory. The memory contains instructions executable by the processing circuitry, whereby when executed the processing circuitry is configured to receive traffic assistance and device information (TADI) from one or more of the UE and the MN. The processing circuitry is further configured to determine that the SN can use the TADI to coordinate with scheduling resources of the SN. The processing circuitry is further configured to use the TADI to coordinate with scheduling resources of the SN. [0026] According to a seventh aspect, a secondary node (SN) is provided. The SN includes processing circuitry and a memory. The memory contains instructions executable by the processing circuitry, whereby when executed the processing circuitry is configured to receive traffic assistance and device information (TADI) from one or more of the UE and the MN. The processing circuitry is further configured to determine that the SN cannot use the TADI to coordinate with scheduling resources of the SN. The processing circuitry is further configured to send a message towards the MN indicating that the SN cannot use the TADI to coordinate with scheduling resources of the SN.

[0027] According to an eighth aspect, a computer program comprising instructions which when executed by processing circuitry of a node, causes the node to perform the method of any one of the embodiments of the first, second, and third aspects is provided.

[0028] According to a ninth aspect, a carrier containing the computer program of the eighth aspect is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.

BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.

[0030] FIG. 1 illustrates an overview of the 5G RAN Architecture.

[0031] FIG. 2 illustrates a gNB split architecture.

[0032] FIG. 3 illustrates a UE in DC mode.

[0033] FIG. 4 illustrates a MN and SN in DC mode.

[0034] FIG. 5 illustrates a system according to an embodiment.

[0035] FIG. 6 illustrates a system according to an embodiment.

[0036] FIG. 7 illustrates a system according to an embodiment.

[0037] FIG. 8 illustrates a flowchart according to an embodiment.

[0038] FIG. 9 illustrates a flowchart according to an embodiment. [0039] FIG. 10 illustrates a flowchart according to an embodiment.

[0040] FIG. 11 is a block diagram of an apparatus according to an embodiment.

DETAILED DESCRIPTION

[0041] Embodiments provide solutions that, in Dual Connectivity, with or without split bearer, allow the UE to provide the TADI (e.g., via RRC) to the MN, provide for how the UE TADI is transferred within the RAN (e.g., to SNs) and towards the CN. This is further explained below.

[0042] FIG. 5 illustrates a system according to an embodiment. As shown, the UE 502 reports TADI via RRC to the gNB-CU of the MN 504. The gNB-CU of the MN 504, via the F1AP interface, forwards the TADI to the gNB-DU of the MN 504. The gNB-CU of the MN 504 further sends the TADI to the gNB-CU of the SN 506. The gNB-CU of the SN 506, via the F1AP interface, forwards the TADI to the gNB-DU of the SN 506. The gNB-CU of the MN 504 also reports the TADI to the CN 508, shown via an NGAP message. The figure shows one case where TADI is received over RRC in the MN 504.

[0043] FIG. 6 illustrates a system according to an embodiment. The MCG and SCG coordinate over the C-Plane, and the UE 504 reports the TADI in L1/L2, e.g., MAC. The figure shows one case where TADI is received via MAC layer in MN 504. MAC layer is an example of a L1/L2 entity, other L1/L2 entities are also applicable. As shown, the UE reports the TADI to the gNB-DU of the MN 504 via MAC layer. The reporting may be triggered by the UE 502. The gNB-DU of the MN 504, via the F1AP interface, forwards the TADI to the gNB-CU of the MN 504. The gNB-CU of the MN 504 forwards the TADI to the gNB-CU of the SN 506, via the XnAP interface.

[0044] The UE 502 may report the TADI alternatively to one of or both of the MN 504 and the SN 506. If a MAC CE is used, the UE 502 may provide the TADI or Index to the MAC entity in the MN 504 for all RLC. If a MAC CE is used, the UE 502 may provide the TADI to both the MN 504 and the SN 506. The message may be transferred between the MN 504 and the SN 506, or PDCP and RLCs. For example, the MN 504 may be responsible to send the TADI via SN 506. When user plane is used, a PDCP entity may be responsible to send the TADI to RLC. The MN 504 may collect the TADI and send to the CN 508. The PDCP entity may collect the TADI and send to the UPF. The MN 504 may collect the TADI from the UE 502 and the CN 508 makes the (de)activation decision, and conveys it to the gNB-DU of the MN 504 and SN 506.

[0045] FIG. 7 illustrates a system according to an embodiment. The figure shows MCG and SCG coordination in split bearer in DC mode, UE TADI (de)activation in L1/L2, e.g., MAC entity. The figure shows one case where UE TADI reporting is activated and deactivated via L1/L2 entities, e.g., MAC CE, from both MN 504 and SN 506 in the split bearer. The PDCP entity may be located in the MN 504. As shown, the PDCP entity of the MN 504 may inform the RLC of the SN 506 of the UE TADI reporting (de)activation decision. This decision (to activate or deactivate UE TADI reporting) may be conveyed to the UE 502 via a MAC CE by the MN 504 or SN 506.

[0046] UE side embodiments:

[0047] In some embodiments, the UE TADI is sent by the UE towards the MN only, over an RRC message. In some embodiments, the UE TADI is sent to both the MN and the SN, over an RRC message. In some embodiments, the UE TADI is sent via MAC layer to the MN only. In some embodiments, the UE TADI is sent via MAC layer to both the MN and SN, covering the master cell group (MCB) and the secondary cell group (SCG).

[0048] NG-RAN node embodiments:

[0049] Some embodiments provide for handling UE TADI reporting at NG-RAN nodes.

[0050] In some embodiments, such as when UE TADI is sent over RRC to the MN only, one or more of the following actions may be taken:

• The MN (e.g., gNB-CU of the MN) may collect the TADI Information and send it to the SN (e.g., the gNB-CU of the SN).

• The MN (e.g., gNB-CU of the MN) may signal the TADI from the MN (e.g., gNB-CU of the MN) to the SN (e.g., gNB-CU of the SN) over User Plane signaling, e.g., as defined in 3 GPP TS 38.425, e.g., using an Assistance Information Data message. • The SN (e.g., gNB-CU-CP of the SN) may send the TADI information to the SN (e.g., gNB-CU-UP of the SN) over an El interface.

• The MN (e.g., gNB-CU of the MN) may signal the TADI from MN (e.g., gNB-CU of the MN) to the SN (e.g., gNB-CU of the SN) via Control Plane signaling, e.g., as defined in 3GPP TS 38.423, e.g. during a Dual Connectivity procedure, such as S-NODE ADDITION REQUEST or S-NODE MODIFICATION REQUEST messages.

• The SN (e.g., gNB-CU of the SN), upon receiving the TADI information from the MN, may use the TADI to coordinate with its scheduling resources. In case the SN cannot, or finds the TADI too stringent for its current scheduling resources, or cannot satisfy the TADI requirements in terms of data rate and other requirements, the SN may notify the MN (e.g., gNB-CU of MN) with a message, such as an XNAP message.

• The MN (e.g., gNB-CU of the MN) may also transfer the jitter and UE XR traffic characteristics information to the CN.

• The MN (e.g., gNB-CU of the MN) may also transfer the burst arrival time to the AMF, for both UL and DL.

• The MN (e.g., gNB-CU of the MN) may signal all or part of the TADI, or information derived from it, to the SN, over an operations and maintenance interface.

[0051] In some embodiments, such as when UE TADI is sent over RRC to both the MN and SN, one or more of the following actions may be taken:

• The MN and SN gNB-CUs may collect the TADI information and exchange it with each other, e.g., over Xn signaling. For instance, the MN may send the TADI requirements to the SN, in case the SN RRC configures the UE via Signal Radio Bearer 3 (SRB3). This can be done as an early step when setting up the MR-DC resources between the involved nodes. • Alternatively, the UE may decide to which node it should send the RRC message containing the UAL

• The signaling of the TADI from the SN to the MN can be done via Control Plane signaling, such as defined in TS 38.423, e.g. during a Dual Connectivity procedure, such as S-NODE MODIFICATION REQUIRED message.

• The MN (e.g., gNB-CU of the MN), upon receiving the TADI information from the SN, may coordinate with its own scheduling resources to see if it can meet the requirement of the (e.g. XR) UL traffic. In case it cannot, it may notify the SN with an XN message, e.g. S-NODE MODIFICATION REFUSE message.

• The MN may also signal the updated TADI, including jitter information and burst arrival time, after coordination with the SN, to the CN.

[0052] In another embodiment, such as when UE TADI is sent via MAC layer in the MN, one or more of the following actions may be taken:

• The MN (e.g., gNB-DU of the MN) may forward the received TADI information received by MCG via MAC-Common Element (CE) (MAC-CE) internally, e.g., to the gNB-CU of the MN, such as via Fl signaling.

• The MN (e.g., the gNB-CU of the MN) may transmit the TADI from the MN PDCP entity to the SN NR PDCP entity, such as via UP signaling.

• The MN (e.g., the gNB-CU of the MN) may transmit the TADI from the MN PDCP entity to the SN NR PDCP entity, such as via CP signaling.

• Upon receiving the TADI information, the SN NR PDCP entity may forward the received information to the SN MAC layer, such as via Fl signaling.

[0053] In some embodiments, such as when UE TADI is sent via MAC layers to both the

MN and the SN: • The MN and SN may exchange the TADI information over the NR PDCP entities, perform some adjustment and negotiation, and make a final determination.

[0054] Some embodiments provide for NG-RAN nodes activating and deactivating a UE to report TADI in DC mode.

[0055] In some embodiments, if L1/L2 entities (e.g., a MAC entity) are used to activate/deactivate UE TADI reporting, and if only MCG MAC is used, information about whether UE TADI reporting has been activated/deactived may need to be sent to the other NG- RAN node, so it knows how the UE would report TADI. If both MAC entities are allowed to activate/deactivate the UE TADI reporting, the entity (e.g. PDCP entity) may coordinate, such as shown in FIG. 7.

[0056] FIG. 8 is a flowchart illustrating a process 800, according to an embodiment, performed by a user equipment (UE) in a dual connectivity (DC) mode with a master node (MN) and a secondary node (SN). Process 800 may begin in step s802.

[0057] Step s802 comprises determining traffic assistance and device information (TADI) for the UE.

[0058] Step s804 comprises sending the TADI towards one or more of the MN and SN.

[0059] In some embodiments, sending the TADI towards one or more of the MN and SN comprises sending the TADI towards only the MN. In some embodiments, sending the TADI towards one or more of the MN and SN comprises sending the TADI towards both the MN and the SN. In some embodiments, the method further includes determining which node of the MN and SN to send the TADI towards. In some embodiments, sending the TADI towards one or more of the MN and SN comprises sending a radio resource control (RRC) message containing the TADI towards the one or more of the MN and SN. In some embodiments, sending the TADI towards one or more of the MN and SN comprises sending a message containing the TADI towards the one or more of the MN and SN using a medium access control (MAC) layer. In some embodiments, the method further includes receiving a reporting activation message or a reporting deactivation message from the MN or SN indicating, respectively, that the UE should report or should not report TADI to the MN or SN. In some embodiments, the TADI comprises one or more of jitter information and time-sensitive information. In some embodiments, the UE is being used for an extended reality application and the TADI is related to the extended reality application.

[0060] FIG. 9 is a flowchart illustrating a process 900, according to an embodiment, performed by a master node (MN) supporting a user equipment (UE) in a dual connectivity (DC) mode, wherein the UE is further supported by a secondary node (SN). Process 900 may begin in step s902.

[0061] Step s902 comprises receiving traffic assistance and device information (TADI) from the UE.

[0062] Step s904 comprises sending the TADI towards a core network (CN).

[0063] In some embodiments, the TADI from the UE comprises receiving a radio resource control (RRC) message containing the TADI from the UE. In some embodiments, the TADI from the UE comprises receiving a message containing the TADI from the UE using a medium access control (MAC) layer. In some embodiments, the method further includes sending the TADI towards the SN. In some embodiments, sending the TADI towards the SN comprises sending the TADI towards a centralized unit (CU) of the SN, wherein the MN comprises a first gNB and the SN comprises a second gNB. In some embodiments, sending the TADI towards the CU of the SN occurs over user plane signaling. In some embodiments, sending the TADI towards the CU of the SN occurs over control plane signaling during a DC procedure. In some embodiments, the MN comprises a first gNB, the SN comprises a second gNB, and sending the TADI towards the SN comprises a control plane (CP) of a centralized unit (CU) of the first gNB (first gNB-CU-CP) sending the TADI towards a CP of a CU of the second gNB (second gNB-CU-CP) over an El interface. In some embodiments, the method further includes sending the TADI towards a core network (CN). In some embodiments, sending the TADI towards the CN comprises sending a burst arrival time towards an access and mobility management function (AMF) of the CN.

[0064] In some embodiments, the method further includes sending at least part of the TADI towards the SN. In some embodiments, sending at least part of the TADI towards the SN occurs over an operations and maintenance interface. In some embodiments, the method further includes determining that the MN can use the TADI to coordinate with scheduling resources of the MN; and using the TADI to coordinate with scheduling resources of the MN. In some embodiments, the method further includes determining that the MN cannot use the TADI to coordinate with scheduling resources of the MN; and sending a message towards the SN indicating that the MN cannot use the TADI to coordinate with scheduling resources of the MN. In some embodiments, the message comprises an Xn application protocol (XnAP) message. In some embodiments, the method further includes sending a reporting activation message or a reporting deactivation message towards the UE indicating, respectively, that the UE should report or should not report TADI to the MN or SN. In some embodiments, the TADI comprises one or more of jitter information and time-sensitive information.

[0065] FIG. 10 is a flowchart illustrating a process 1000, according to an embodiment, performed by a secondary node (SN) supporting a user equipment (UE) in a dual connectivity (DC) mode, wherein the UE is further supported by a master node (MN). Process 1000 may begin in step si 002.

[0066] Step si 002 comprises receiving traffic assistance and device information (TADI) from one or more of the UE and the MN.

[0067] Step si 004 comprises determining that the SN can use the TADI to coordinate with scheduling resources of the SN.

[0068] Step si 006 comprises using the TADI to coordinate with scheduling resources of the SN.

[0069] FIG. 10 further illustrates a process 1010, according to an embodiment, performed by a secondary node (SN) supporting a user equipment (UE) in a dual connectivity (DC) mode, wherein the UE is further supported by a master node (MN). Process 1010 may begin in step S1008.

[0070] Step sl008 comprises receiving traffic assistance and device information (TADI) from one or more of the UE and the MN.

[0071] Step slOlO comprises determining that the SN cannot use the TADI to coordinate with scheduling resources of the SN. [0072] Step sl012 comprises sending a message towards the MN indicating that the SN cannot use the TADI to coordinate with scheduling resources of the SN.

[0073] In some embodiments, the message comprises an Xn application protocol (XnAP) message.

[0074] FIG. 11 is a block diagram of apparatus 1100 (e.g., gNB 106, 106, MN 302, SN 304, UE 306, gNB-CU 110, gNB-DU 112, 114), according to some embodiments, for performing the methods disclosed herein. As shown in FIG. 11, apparatus 1100 may comprise: processing circuitry (PC) 702, which may include one or more processors (P) 1155 (e.g., a general purpose microprocessor and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like), which processors may be co-located in a single housing or in a single data center or may be geographically distributed (i.e., apparatus 1100 may be a distributed computing apparatus); at least one network interface 1148 comprising a transmitter (Tx) 1145 and a receiver (Rx) 1147 for enabling apparatus 1100 to transmit data to and receive data from other nodes connected to a network 1110 (e.g., an Internet Protocol (IP) network) to which network interface 1148 is connected (directly or indirectly) (e.g., network interface 1148 may be wirelessly connected to the network 1110, in which case network interface 1148 is connected to an antenna arrangement); and a storage unit (a.k.a., “data storage system”) 1108, which may include one or more non-volatile storage devices and/or one or more volatile storage devices. Interface 1160 may connect PC 1102 and storage unit 1108, interface 1162 may connect PC 1102 and network interface 1148, and interface 1164 may connect network interface 1148 and network 1110. In embodiments where PC 1102 includes a programmable processor, a computer program product (CPP) 1141 may be provided. CPP 1141 includes a computer readable medium (CRM) 1142 storing a computer program (CP) 1143 comprising computer readable instructions (CRI) 1144. CRM 1142 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CRI 1144 of computer program 1143 is configured such that when executed by PC 1102, the CRI causes apparatus 1100 to perform steps described herein (e.g., steps described herein with reference to the flow charts). In other embodiments, apparatus 1100 may be configured to perform steps described herein without the need for code. That is, for example, PC 1102 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.

[0075] Concise Description of Certain Embodiments

Al. A method performed by a user equipment (UE) in a dual connectivity (DC) mode with a master node (MN) and a secondary node (SN), the method comprising: determining traffic assistance and device information (TADI) for the UE; and sending the TADI towards one or more of the MN and SN.

A2. The method of embodiment Al, wherein sending the TADI towards one or more of the MN and SN comprises sending the TADI towards only the MN.

A3. The method of embodiment Al, wherein sending the TADI towards one or more of the MN and SN comprises sending the TADI towards both the MN and the SN.

A4. The method of any one of embodiments Al -A3, further comprising determining which node of the MN and SN to send the TADI towards.

A5. The method of any one of embodiments A1-A4, wherein sending the TADI towards one or more of the MN and SN comprises sending a radio resource control (RRC) message containing the TADI towards the one or more of the MN and SN.

A6. The method of any one of embodiments A1-A4, wherein sending the TADI towards one or more of the MN and SN comprises sending a message containing the TADI towards the one or more of the MN and SN using a medium access control (MAC) layer.

A7. The method of any one of embodiments Al -A6, further comprising receiving a reporting activation message or a reporting deactivation message from the MN or SN indicating, respectively, that the UE should report or should not report TADI to the MN or SN. A8. The method of any one of embodiments Al -A7, wherein the TADI comprises one or more of jitter information and time-sensitive information.

A9. The method of any one of embodiments Al -A8, wherein the UE is being used for an extended reality application and the TADI is related to the extended reality application.

Bl. A method performed by a master node (MN) supporting a user equipment (UE) in a dual connectivity (DC) mode, wherein the UE is further supported by a secondary node (SN), the method comprising: receiving traffic assistance and device information (TADI) from the UE; and sending the TADI towards a core network (CN).

B2. The method of embodiment B 1 , wherein the TADI from the UE comprises receiving a radio resource control (RRC) message containing the TADI from the UE.

B3. The method of embodiment B 1 , wherein the TADI from the UE comprises receiving a message containing the TADI from the UE using a medium access control (MAC) layer.

B4. The method of any one of embodiments B1-B3, further comprising sending the TADI towards the SN.

B5. The method of embodiment B4, wherein sending the TADI towards the SN comprises sending the TADI towards a centralized unit (CU) of the SN, wherein the MN comprises a first gNB and the SN comprises a second gNB.

B6. The method of embodiment B5, wherein sending the TADI towards the CU of the SN occurs over user plane signaling. B7. The method of embodiment B5, wherein sending the TADI towards the CU of the SN occurs over control plane signaling during a DC procedure.

B8. The method of embodiment B4, wherein the MN comprises a first gNB, the SN comprises a second gNB, and sending the TADI towards the SN comprises a control plane (CP) of a centralized unit (CU) of the first gNB (first gNB-CU-CP) sending the TADI towards a CP of a CU of the second gNB (second gNB-CU-CP) over an El interface.

B9. The method of any one of embodiments B1-B8, further comprising sending the TADI towards a core network (CN).

BIO. The method of embodiment B9, wherein sending the TADI towards the CN comprises sending a burst arrival time towards an access and mobility management function (AMF) of the CN.

Bl 1. The method of any one of embodiments Bl -BIO, further comprising sending at least part of the TADI towards the SN.

Bl 2. The method of embodiment Bl 1, wherein sending at least part of the TADI towards the SN occurs over an operations and maintenance interface.

B13. The method of any one of embodiments B1-B12, further comprising: determining that the MN can use the TADI to coordinate with scheduling resources of the MN; and using the TADI to coordinate with scheduling resources of the MN.

B14. The method of any one of embodiments B1-B12, further comprising: determining that the MN cannot use the TADI to coordinate with scheduling resources of the MN; and sending a message towards the SN indicating that the MN cannot use the TADI to coordinate with scheduling resources of the MN.

B15. The method of embodiment B14, wherein the message comprises an Xn application protocol (XnAP) message.

Bl 6. The method of any one of embodiments Bl -Bl 5, further comprising sending a reporting activation message or a reporting deactivation message towards the UE indicating, respectively, that the UE should report or should not report TADI to the MN or SN.

Bl 7. The method of any one of embodiments Bl -Bl 6, wherein the TADI comprises one or more of jitter information and time-sensitive information.

Cl. A method performed by a secondary node (SN) supporting a user equipment (UE) in a dual connectivity (DC) mode, wherein the UE is further supported by a master node (MN), the method comprising: receiving traffic assistance and device information (TADI) from one or more of the UE and the MN; determining that the SN can use the TADI to coordinate with scheduling resources of the SN; and using the TADI to coordinate with scheduling resources of the SN.

C2. A method performed by a secondary node (SN) supporting a user equipment (UE) in a dual connectivity (DC) mode, wherein the UE is further supported by a master node (MN), the method comprising: receiving traffic assistance and device information (TADI) from one or more of the UE and the MN; determining that the SN cannot use the TADI to coordinate with scheduling resources of the SN; and sending a message towards the MN indicating that the SN cannot use the TADI to coordinate with scheduling resources of the SN.

C3. The method of embodiment C2, wherein the message comprises an Xn application protocol (XnAP) message.

DI. A user equipment (UE) comprising: processing circuitry (1102); and a memory, the memory containing instructions (1144) executable by the processing circuitry (1102), whereby when executed the processing circuitry (1102) is configured to: determine traffic assistance and device information (TADI) for the UE; and send the TADI towards one or more of the MN and SN.

D2. The UE of embodiment DI, wherein sending the TADI towards one or more of the MN and SN comprises sending the TADI towards only the MN.

D3. The UE of embodiment DI, wherein sending the TADI towards one or more of the MN and SN comprises sending the TADI towards both the MN and the SN.

D4. The UE of any one of embodiments D1-D3, wherein the processing circuitry is further configured to determine which node of the MN and SN to send the TADI towards.

D5. The UE of any one of embodiments D1-D4, wherein sending the TADI towards one or more of the MN and SN comprises sending a radio resource control (RRC) message containing the TADI towards the one or more of the MN and SN.

D6. The UE of any one of embodiments D1-D4, wherein sending the TADI towards one or more of the MN and SN comprises sending a message containing the TADI towards the one or more of the MN and SN using a medium access control (MAC) layer. D7. The UE of any one of embodiments D1-D6, wherein the processing circuitry is further configured to receive a reporting activation message or a reporting deactivation message from the MN or SN indicating, respectively, that the UE should report or should not report TADI to the MN or SN.

D8. The UE of any one of embodiments D1-D7, wherein the TADI comprises one or more of jitter information and time-sensitive information.

D9. The UE of any one of embodiments D1-D8, wherein the UE is being used for an extended reality application and the TADI is related to the extended reality application.

El. A master node (MN) comprising: processing circuitry (1102); and a memory, the memory containing instructions (1144) executable by the processing circuitry (1102), whereby when executed the processing circuitry (1102) is configured to: receiving traffic assistance and device information (TADI) from the UE; and sending the TADI towards a core network (CN).

E2. The MN of embodiment El, wherein the TADI from the UE comprises receiving a radio resource control (RRC) message containing the TADI from the UE.

E3. The MN of embodiment El, wherein the TADI from the UE comprises receiving a message containing the TADI from the UE using a medium access control (MAC) layer.

E4. The MN of any one of embodiments E1-E3, wherein the processing circuitry is further configured to send the TADI towards the SN.

E5. The MN of embodiment E4, wherein sending the TADI towards the SN comprises sending the TADI towards a centralized unit (CU) of the SN, wherein the MN comprises a first gNB and the SN comprises a second gNB. E6. The MN of embodiment E5, wherein sending the TADI towards the CU of the SN occurs over user plane signaling.

E7. The MN of embodiment E5, wherein sending the TADI towards the CU of the SN occurs over control plane signaling during a DC procedure.

E8. The MN of embodiment E4, wherein the MN comprises a first gNB, the SN comprises a second gNB, and sending the TADI towards the SN comprises a control plane (CP) of a centralized unit (CU) of the first gNB (first gNB-CU-CP) sending the TADI towards a CP of a CU of the second gNB (second gNB-CU-CP) over an El interface.

E9. The MN of any one of embodiments E1-E8, wherein the processing circuitry is further configured to send the TADI towards a core network (CN).

E10. The MN of embodiment E9, wherein sending the TADI towards the CN comprises sending a burst arrival time towards an access and mobility management function (AMF) of the CN.

El l. The MN of any one of embodiments El -El 0, wherein the processing circuitry is further configured to send at least part of the TADI towards the SN.

E12. The MN of embodiment El l, wherein sending at least part of the TADI towards the SN occurs over an operations and maintenance interface.

El 3. The MN of any one of embodiments El -El 2, wherein the processing circuitry is further configured to: determine that the MN can use the TADI to coordinate with scheduling resources of the MN; and use the TADI to coordinate with scheduling resources of the MN. E14. The MN of any one of embodiments E1-E12, wherein the processing circuitry is further configured to: determine that the MN cannot use the TADI to coordinate with scheduling resources of the MN; and send a message towards the SN indicating that the MN cannot use the TADI to coordinate with scheduling resources of the MN.

El 5. The MN of embodiment El 4, wherein the message comprises an Xn application protocol (XnAP) message.

El 6. The MN of any one of embodiments El -El 5, wherein the processing circuitry is further configured to send a reporting activation message or a reporting deactivation message towards the UE indicating, respectively, that the UE should report or should not report TADI to the MN or SN.

El 7. The MN of any one of embodiments El -El 6, wherein the TADI comprises one or more of jitter information and time-sensitive information.

Fl. A secondary node (SN) comprising: processing circuitry (1102); and a memory, the memory containing instructions (1144) executable by the processing circuitry (1102), whereby when executed the processing circuitry (1102) is configured to: receive traffic assistance and device information (TADI) from one or more of the UE and the MN; determine that the SN can use the TADI to coordinate with scheduling resources of the SN; and use the TADI to coordinate with scheduling resources of the SN.

F2. A secondary node (SN) comprising: processing circuitry (1102); and a memory, the memory containing instructions (1144) executable by the processing circuitry (1102), whereby when executed the processing circuitry (1102) is configured to: receive traffic assistance and device information (TADI) from one or more of the UE and the MN; determine that the SN cannot use the TADI to coordinate with scheduling resources of the SN; and send a message towards the MN indicating that the SN cannot use the TADI to coordinate with scheduling resources of the SN.

F3. The SN of embodiment F2, wherein the message comprises an Xn application protocol (XnAP) message.

Gl. A computer program (1143) comprising instructions which when executed by processing circuitry (1102) of a node (1100), causes the node (1100) to perform the method of any one of embodiments A1-A9 and Bl -Bl 7 and C1-C3.

G2. A carrier containing the computer program (1143) of embodiment Fl, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium (1142).

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

[0077] Additionally, while the processes described above and illustrated in the drawings are shown as a sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, and some steps may be performed in parallel.

Claims

1. A method performed by a user equipment (UE) (502) in a dual connectivity (DC) mode with a master node (MN) (504) and a secondary node (SN) (506), the method comprising: determining traffic assistance and device information (TADI) for the UE (502); and sending the TADI towards one or more of the MN (504) and SN (506).

2. The method of claim 1, further comprising determining which node of the MN and SN to send the TADI towards.

3. The method of any one of claims 1-2, wherein sending the TADI towards one or more of the MN and SN comprises (i) sending a radio resource control (RRC) message containing the TADI towards the one or more of the MN and SN or (ii) sending a message containing the TADI towards the one or more of the MN and SN using a medium access control (MAC) layer.

4. The method of any one of claims 1-3, further comprising receiving a reporting activation message or a reporting deactivation message from the MN or SN indicating, respectively, that the UE should report or should not report TADI to the MN or SN.

5. The method of any one of claims 1-4, wherein the TADI comprises one or more of jitter information and time-sensitive information, and wherein the UE is being used for an extended reality application and the TADI is related to the extended reality application.

6. A method performed by a master node (MN) (504) supporting a user equipment (UE) (502) in a dual connectivity (DC) mode, wherein the UE (502) is further supported by a secondary node (SN) (506), the method comprising: receiving traffic assistance and device information (TADI) from the UE (502); and sending the TADI towards a core network (CN) (508).

7. The method of claim 6, wherein the TADI from the UE comprises receiving a radio resource control (RRC) message containing the TADI from the UE.

8. The method of claim 6, wherein the TADI from the UE comprises receiving a message containing the TADI from the UE using a medium access control (MAC) layer.

9. The method of any one of claims 6-8, further comprising sending the TADI towards the SN, wherein sending the TADI towards the SN comprises sending the TADI towards a centralized unit (CU) of the SN, wherein the MN comprises a first gNB and the SN comprises a second gNB.

10. The method of claim 9, wherein sending the TADI towards the CU of the SN occurs over user plane signaling.

11. The method of claim 9, wherein sending the TADI towards the CU of the SN occurs over control plane signaling during a DC procedure.

12. The method of claim 9, wherein the MN comprises a first gNB, the SN comprises a second gNB, and sending the TADI towards the SN comprises a control plane (CP) of a centralized unit (CU) of the first gNB (first gNB-CU-CP) sending the TADI towards a CP of a CU of the second gNB (second gNB-CU-CP) over an El interface.

13. The method of any one of claims 6-12, further comprising sending the TADI towards a core network (CN), wherein sending the TADI towards the CN comprises sending a burst arrival time towards an access and mobility management function (AMF) of the CN.

14. The method of any one of claims 6-13, further comprising sending at least part of the TADI towards the SN, wherein sending at least part of the TADI towards the SN occurs over an operations and maintenance interface.

15. The method of any one of claims 6-14, further comprising: determining that the MN can use the TADI to coordinate with scheduling resources of the MN; and using the TADI to coordinate with scheduling resources of the MN.

16. The method of any one of claims 6-14, further comprising: determining that the MN cannot use the TADI to coordinate with scheduling resources of the MN; and sending a message towards the SN indicating that the MN cannot use the TADI to coordinate with scheduling resources of the MN, wherein the message comprises an Xn application protocol (XnAP) message.

17. The method of any one of claims 6-16, further comprising sending a reporting activation message or a reporting deactivation message towards the UE indicating, respectively, that the UE should report or should not report TADI to the MN or SN.

18. The method of any one of claims 6-17, wherein the TADI comprises one or more of jitter information and time-sensitive information.

19. A method performed by a secondary node (SN) (506) supporting a user equipment (UE) (502) in a dual connectivity (DC) mode, wherein the UE (502) is further supported by a master node (MN) (504), the method comprising: receiving traffic assistance and device information (TADI) from one or more of the UE (502) and the MN (504); determining that the SN (506) can use the TADI to coordinate with scheduling resources of the SN (506); and using the TADI to coordinate with scheduling resources of the SN (506).

20. A method performed by a secondary node (SN) (506) supporting a user equipment (UE) (502) in a dual connectivity (DC) mode, wherein the UE (502) is further supported by a master node (MN) (504), the method comprising: receiving traffic assistance and device information (TADI) from one or more of the UE (502) and the MN (504); determining that the SN (506) cannot use the TADI to coordinate with scheduling resources of the SN (506); and sending a message towards the MN (504) indicating that the SN (506) cannot use the TADI to coordinate with scheduling resources of the SN (506).

21. The method of claim 20, wherein the message comprises an Xn application protocol (XnAP) message.

22. A user equipment (UE) comprising: processing circuitry (1102); and a memory, the memory containing instructions (1144) executable by the processing circuitry (1102), whereby when executed the processing circuitry (1102) is configured to: determine traffic assistance and device information (TADI) for the UE; and send the TADI towards one or more of the MN and SN.

23. The UE of claim 22, wherein the processing circuitry is further configured to determine which node of the MN and SN to send the TADI towards, and wherein sending the TADI towards one or more of the MN and SN comprises (i) sending a radio resource control (RRC) message containing the TADI towards the one or more of the MN and SN or (ii) sending a message containing the TADI towards the one or more of the MN and SN using a medium access control (MAC) layer.

24. The UE of any one of claims 22-23, wherein the processing circuitry is further configured to receive a reporting activation message or a reporting deactivation message from the MN or SN indicating, respectively, that the UE should report or should not report TADI to the MN or SN, wherein the TADI comprises one or more of jitter information and time-sensitive information, and wherein the UE is being used for an extended reality application and the TADI is related to the extended reality application.

25. A master node (MN) comprising: processing circuitry (1102); and a memory, the memory containing instructions (1144) executable by the processing circuitry (1102), whereby when executed the processing circuitry (1102) is configured to: receiving traffic assistance and device information (TADI) from the UE; and sending the TADI towards a core network (CN).

26. The MN of claim 25, wherein the processing circuitry is further configured to send the TADI towards the SN, wherein sending the TADI towards the SN comprises sending the TADI towards a centralized unit (CU) of the SN, wherein the MN comprises a first gNB and the SN comprises a second gNB, and wherein sending the TADI towards the CU of the SN (i) occurs over user plane signaling or (ii) occurs over control plane signaling during a DC procedure.

27. The MN of claim 26, wherein the MN comprises a first gNB, the SN comprises a second gNB, and sending the TADI towards the SN comprises a control plane (CP) of a centralized unit (CU) of the first gNB (first gNB-CU-CP) sending the TADI towards a CP of a CU of the second gNB (second gNB-CU-CP) over an El interface.

28. The MN of any one of claims 25-27, wherein the processing circuitry is further configured to send the TADI towards a core network (CN), and wherein sending the TADI towards the CN comprises sending a burst arrival time towards an access and mobility management function (AMF) of the CN.

29. The MN of any one of claims 25-28, wherein the processing circuitry is further configured to send at least part of the TADI towards the SN, and wherein sending at least part of the TADI towards the SN occurs over an operations and maintenance interface.

30. The MN of any one of claims 25-29, wherein the processing circuitry is further configured to send a reporting activation message or a reporting deactivation message towards the UE indicating, respectively, that the UE should report or should not report TADI to the MN or SN.

31. The MN of any one of claims 25-30, wherein the TADI comprises one or more of jitter information and time-sensitive information.

32. A secondary node (SN) comprising: processing circuitry (1102); and a memory, the memory containing instructions (1144) executable by the processing circuitry (1102), whereby when executed the processing circuitry (1102) is configured to: receive traffic assistance and device information (TADI) from one or more of the UE and the MN; determine that the SN can use the TADI to coordinate with scheduling resources of the SN; and use the TADI to coordinate with scheduling resources of the SN.

33. A secondary node (SN) comprising: processing circuitry (1102); and a memory, the memory containing instructions (1144) executable by the processing circuitry (1102), whereby when executed the processing circuitry (1102) is configured to: receive traffic assistance and device information (TADI) from one or more of the UE and the MN; determine that the SN cannot use the TADI to coordinate with scheduling resources of the SN; and send a message towards the MN indicating that the SN cannot use the TADI to coordinate with scheduling resources of the SN.

34. The SN of claim 33, wherein the message comprises an Xn application protocol (XnAP) message.

35. A computer program (1143) comprising instructions which when executed by processing circuitry (1102) of a node (1100), causes the node (1100) to perform the method of any one of claims 1-21.

36. A carrier containing the computer program (1143) of claim 35, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium (1142).