DE102021114182A1 - SUPPORT FOR EARLY DATA FORWARDING FOR SECONDARY NODE (SN) TERMINATED BEARERS - Google Patents

Abstract

A source gNodeB (gNB) device for operation in a fifth generation network may include a master node (MN). The MN can contain one or more processors. The one or more processors can be configured to send a handover (HO) request message to a destination gNB. The HO request message can request the implementation of a conditional HO (CHO) of user equipments (UE) from the source gNB to the destination gNB. The one or more processors may also be configured to receive a CHO request acknowledgment message from the target gNB. In addition, the one or more processors can be configured in such a way that they provide address information of the transport network layer (TNL) to a secondary node (SN) of the source gNB.

Description

CROSS REFERENCE TO RELATED APPLICATION

This patent application claims the benefit and priority of US Provisional App. 63 / 034,872 , submitted on June 4, 2020.

AREA

Various aspects can generally pertain to the field of wireless communications.

BACKGROUND

Conditional Handover (HO) (CHO) can be included as part of the WI "Neuer Funk (NR) Mobility Enhancement - new radio (NR) Mobility Enhancement" for RP-181433.

Figure list

• 1 beispielhafte Sequenznachrichten-Ablaufdiagramme einer HO-Prozedur von einem Quell-Masterknoten (MN) in Multi-Radio-Access-Technology (RAT)-Dual-Connectivity (MR-DC) mit Fünfte Generation Kern (5GC) und CHO von einem Quell-MN in MR-DC mit 5GC darstellt;
• 2 ein beispielhaftes Sequenznachrichten-Ablaufdiagramm eines HO-Verfahrens, bei dem ein Quell-MN einem Quell-SN anzeigt, dass CHO vor dem Auslösen von CHO in einem Zielnetzwerk stattfinden soll, darstellt;
• 3 ein beispielhaftes Sequenznachrichten-Sequenzdiagramm einer HO-Prozedur, bei der ein Quell-MN einem Quell-SN anzeigt, dass CHO beim Senden von Weiterleitungs-TNL-Informationen aus dem Zielnetzwerk auftreten soll, darstellt;
• 4 ein Netzwerk gemäß verschiedenen Aspekten darstellt;
• 5 schematisch ein Drahtlos-Netzwerk gemäß verschiedenen Aspekten darstellt; und
• 6 ein Blockdiagramm ist, das Komponenten gemäß einigen Beispielaspekten veranschaulicht, die in der Lage sind, Anweisungen von einem maschinenlesbaren oder computerlesbaren Medium (z.B. einem nicht-transitorischen maschinenlesbaren Speichermedium) zu lesen und eine oder mehrere der hierin diskutierten Methoden durchzuführen,

alle gemäß mindestens einem in der vorliegenden Offenbarung beschriebenen Aspekt.Example aspects are described and explained with additional specificity and level of detail through the use of the accompanying drawings in which:

• 1 exemplary sequence message flowcharts of an HO procedure from a source master node (MN) in multi-radio access technology (RAT) -dual connectivity (MR-DC) with fifth generation core (5GC) and CHO from a source MN in MR-DC represents with 5GC;
• 2 Fig. 3 is an exemplary sequence message flow diagram of an HO method in which a source MN indicates to a source SN that CHO should occur before triggering CHO in a destination network;
• 3 Figure 3 is an exemplary sequence message sequence diagram of an HO procedure in which a source MN indicates to a source SN that CHO should occur when sending forwarding TNL information from the destination network;
• 4th depicts a network in accordance with various aspects;
• 5 schematically depicts a wireless network in accordance with various aspects; and
• 6th Figure 3 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing one or more of the methods discussed herein, according to some example aspects,

all in accordance with at least one aspect described in the present disclosure.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or like elements. In the following description, for the purpose of explanation and not limitation, specific details such as certain structures, architectures, interfaces, techniques, etc. are set forth in order to enable a thorough understanding of the various aspects. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various aspects can be practiced in other examples deviating from these specific details. In certain cases, descriptions of known devices, circuits, and methods are omitted in order not to water down the description of the various aspects in unnecessary detail. For the purposes of this document, the terms "A or B" and "A / B" mean (A), (B) or (A and B).

CHO can be included as part of the BISE "NR Mobility Enhancement" for RP-181433. CHO can include situations where target cells can be prepared prior to the CHO. User equipment (UE) can access a target cell that meets the configured conditions. CHO can be implemented in combination with MR-DC, e.g. an MN (e.g. the source MN) can trigger CHO to a destination node while an SN (e.g. the source SN) serves the UE.

CHO can include situations where target cells can be prepared prior to the CHO. The UE can access a target cell that meets the configured conditions. CHO can be implemented in combination with MR-DC (e.g. a master node (MN) (e.g. the source MN)) can trigger CHO to a target node while an SN (e.g. the source SN) is serving the UE. The SN can be released during the legacy HO. In addition, after the HO preparation, data forwarding transport network layer information (TNL) can be provided from the destination to the source SN.

1 Figure 10 illustrates example sequence message flow diagrams 102 and 104 an HO procedure from a source MN in MR-DC with 5GC 102 and CHO from a source MN in MR-DC with 5GC 104 , according to at least one aspect described in the present disclosure.

The SN can be released during the legacy HOs. In addition, data forwarding TNL information can be provided from destination to source SN after HO preparation, as in relation to the sequence message diagram 102 the 1 shown. CHO can only take place when an execution condition is met in the UE and the UE accesses a candidate target cell. The release of the source SN and the provision of the data forwarding TNL can take place after the UE accesses the target cell (e.g. after the source MN determines that various steps (e.g. steps 5/6 of 102 and 104 the 1 ) with the target cell via a handover success message, as in the message sequence diagram 104 the 1 shown).

During an HO, the data forwarding from the source SN can be limited and can take place after the UE has accessed the target cell (alternatively, this is referred to as “late data forwarding”). With CHO, both early and late data forwarding can take place. The source SN can determine whether to perform early or late data forwarding. The source SN can initiate the data forwarding after a CHO preparation phase (if downlink (DL) data radio bearer (DRB) forwarding tunnels are set up and early forwarding is selected). Alternatively, the source SN cannot perform early data forwarding for a bearer terminated by the SN, even if DL-DRB forwarding tunnels are established from the target cell.

The early data forwarding from the source SN during the CHO operation in MR-DC can be activated. For example, step 3c of the sequence message diagram 104 the 1 after the CHO preparation, so that the source SN can determine data forwarding TNL addresses from the target cell at an early stage.

When receiving an Xn-U ADDRESS INDICATION message, the source SN can trigger the data forwarding (including the forwarding of protocol data units (PDUs)). If early data forwarding is performed, the source SN can forward DL packet data convergence protocol (PDCP) service data units (SDUs) with SN assigned by the source SN via the established DL-DRB forwarding tunnels.

• In MR-DC kann der Quell-MN, bevor er einen HO zur Zielzelle auslöst, eine sekundäre Zellgruppen-Konfiguration (SCG) vom Quell-SN abrufen (über eine vom MN initiierte SN-Modifikationsprozedur). Der Quell-MN kann die SCG-Konfiguration für Deltasignalisierungszwecke verwenden. Der Quell-MN kann dem Quell-SN anzeigen, dass CHO stattfinden soll. Der Quell-SN kann eine frühe Datenweiterleitung über die eingerichteten DL-DRB-Weiterleitungstunnel durchführen. Der Quell-SN kann eine frühe Datenweiterleitung auf der Grundlage von weiterleitenden TNL-Adressen aus der Zielzelle durchführen (z. B. über eine Xn-U ADDRESS INDICATION-Nachricht in MR-DC mit 5GC oder über eine DATA FORWARDING ADDRESS INDICATION-Nachricht in E-UTRAN (EN-DC)).

The source MN can indicate to the source SN that CHO will take place before initiating CHO to a target:

• In MR-DC, the source MN can, before triggering an HO to the target cell, retrieve a secondary cell group configuration (SCG) from the source SN (via an SN modification procedure initiated by the MN). The source MN can use the SCG configuration for delta signaling purposes. The source MN can indicate to the source SN that CHO should take place. The source SN can carry out an early data forwarding via the established DL-DRB forwarding tunnels. The source SN can carry out early data forwarding based on forwarding TNL addresses from the target cell (e.g. via an Xn-U ADDRESS INDICATION message in MR-DC with 5GC or via a DATA FORWARDING ADDRESS INDICATION message in E-UTRAN (EN-DC)).

2 Figure 11 illustrates an exemplary sequence message flow diagram 200 an HO method in which a source MN indicates to a source SN that CHO should take place in a target network prior to triggering CHO, according to at least one aspect described in the present disclosure.

The source MN can use an SCG configuration query information element (IE) (which asks the en-gNodeB (en-gNB) to provide the current SCG configuration) to notify the source SN that CHO should take place, as in Table 1 shown. Table 1 IE / group name presence Area IE type and reference Semantic description SCG Configuration Query M. ENUMERATED (True, ..., True due to CHO)

The source MN can use the SCG Configuration Query IE (which asks the S Next Generation (NG) RAN node to provide the current SCG configuration) to notify the source SN that CHO should take place, as in table 2 shown. Table 2 IE / group name presence Area IE type and reference Semantic description SCG Configuration Query M. ENUMERATED (True, ..., True due to CHO)

• Der Quell-SN kann Weiterleitungs-TNL-Adressinformationen erhalten, die weitergegeben werden, bevor die SN-Freigabe ausgelöst wird. Der Quell-SN kann eine frühe Datenweiterleitung über etablierte DL-DRB-Weiterleitungstunnel durchführen. Zu diesem Zweck kann eine Klasse-2-Nachricht definiert werden. Alternativ kann eine Xn-U ADDRESS INDICATION-Nachricht in MR-DC mit 5GC (oder eine X2 Access Plane (X2AP) DATA FORWARDING ADDRESS INDICATION-Nachricht in EN-DC) verwendet werden, um die Weiterleitungs-TNL-Adressinformationen an den Quell-SN zu übermitteln. Die Nachrichten können anzeigen, dass die Bereitstellung aufgrund von CHO erfolgt, so dass eine frühzeitige Datenweiterleitung durch die vom Quell-SN abgeschlossenen Träger des Quell-SN durchgeführt werden kann.

When forwarding TNL information from the destination, the source MN can indicate to the source SN that it is information for CHO:

• The source SN may receive forwarding TNL address information that will be propagated before the SN release is triggered. The source SN can carry out an early data forwarding via established DL-DRB forwarding tunnels. A class 2 message can be defined for this purpose. Alternatively, an Xn-U ADDRESS INDICATION message in MR-DC with 5GC (or an X2 Access Plane (X2AP) DATA FORWARDING ADDRESS INDICATION message in EN-DC) can be used to send the forwarding TNL address information to the source Submit SN. The messages can indicate that the provision takes place on the basis of CHO, so that data can be forwarded at an early stage by the bearers of the source SN terminated by the source SN.

3 Figure 11 illustrates an exemplary sequence message flow diagram 300 an HO method in which a source MN indicates to a source SN that CHO occurs when sending forwarding TNL information from the destination network, according to at least one aspect described in the present disclosure.

The aspects described in the present disclosure may enable the source SN to identify CHO triggers from the source MN during MR-DC operation. The source SN can carry out early data forwarding for the carriers of the source SN terminated by the SN via the DL-DRB forwarding tunnels that have been set up.

This message can be provided by the new NG-RAN node in order to transmit data forwarding information to the old NG-RAN node. This message can be provided by the master NG-RAN (M-NG-RAN) node to provide the secondary NG-RAN (S-NG-RAN) node with data forwarding or Xn-U bearer address information for SN to transmit finished bearer. This message can be implemented as shown in Table 3.

The direction of the message can include: new NG-RAN node → old NG-RAN node, M-NG-RAN node → S-NG-RAN node. IE / group name presence Area IE type and reference Semantic description Critical property Assigned critical property Message Type M. 9.2.3.1 YES Deny New NG-RAN node UE XnAP identifier (ID) reference M. NG-RAN node UE XnAP ID 9.2.3.16 Can be allocated to the new NR-RAN YES To ignore Old NG-RAN node UE XnAP ID reference M. NG-RAN node UE XnAP ID 9.2.3.16 Can be allocated to the old NR-RAN YES To ignore Xn-U Address Information via PDU Session Resources List 1 YES Deny > Xn-U address information via PDU session resources item 1 .. <maxn oofPDUS essions> - >> PDU session ID M. 9.2.3.18 - >> Data Forwarding Information from target NG-RAN node O Data Forwarding Information from target NG-RAN node 9.2.1.16 - >> Secondary Data Forwarding Information from target NG-RAN node list O 9.2.1.31 This IE can exist when the target M-NG-RAN node decides to split a PDU session between the MN and the SN YES To ignore >> PDU Session Resource Setup Complete Information - SN terminated O 9.2.1.30 - >> DRB IDs taken into use O DRB List 9.2.1.29 This IE can specify DRB IDs to be used by the target NG-RAN node. YES Deny Table 3 >> CHO indicator O ENUMERA TED (true, ...) This IE can indicate that data forwarding information from the target NG-RAN node IE or the secondary data forwarding information from the target NG-RAN node list IE can be provided based on the CHO and early data forwarding can be provided by the S -NG-RAN node to be performed YES Deny

This message can be sent by a new evolved NodeB (eNB) or eNB to provide the old eNB or en-gNB with forwarding addresses for each evolved Radio Access Bearer (E-RAB) for data forwarding, as shown in Tables 4 and 5.

The direction of the message can include: new eNB → old eNB or eNB → en-gNB. Table 4 IE / group name presence Area IE type and reference Semantic description Critical property Assigned critical property Message Type M. 9.2.13 YES To ignore New eNB UE X2AP ID M. eNB UE X2AP ID 9.2.24 Allocated to the new eNB YES To ignore New eNB UE X2AP ID Extension O Extended eNB UE X2APID 9.2.86 Allocated to the new eNB YES To ignore Old eNB UE X2AP ID M. eNB UE X2AP ID 9.2.24 Allocated to the new eNB YES To ignore Old eNB UE X2AP ID Extension O Extended eNB UE X2APID 9.2.86 Allocated to the new eNB YES To ignore E-RABs Data Forwarding Address List 1 YES To ignore > E-RABs Data Forwarding Address Item 1 .. <maxnoofB earers> EVERYONE To ignore >> E-RAB ID M. 9.2.23 - >> DL General Packet Radio Service Tunneling Protocol (GTP) Tunnel Endpoint M. GTP Tunnel Endpoint 9.2.1 Identifies the X2 Transport Bearer that is used to forward DL PDUs - CHO indicator O ENUMERAT ED (true, ...) Indicates that the E-RABs Data Forwarding Address List IE is provided due to CHO and thus early forwarding can be decided by the en-gNB, if applicable. YES Deny Table 5 Range limit Explanation maxnoofBearers Maximum number of E-RABs. Value is 256

In the 4-5 various systems, devices, and components are shown that can implement aspects of the disclosed aspects.

4th shows a network 400 according to various aspects. The network 400 can operate in a manner consistent with fifth generation (5G) / NR systems. However, the example aspects are not limited in this regard, and the aspects described may apply to other networks that benefit from the principles described herein, such as future systems of the Third Generation Partnership Project (3GPP) or the like.

The network 400 can a UE 402 which may include any mobile or non-mobile computing device designed to work with a RAN 404 communicate over an over-the-air connection. The UE 402 a smartphone, a tablet computer, a portable computer device, a desktop computer, a laptop computer, an infotainment device in the vehicle, an entertainment device in the vehicle, an instrument cluster, a head-up display device, an onboard diagnostic device, a mobile Dashtop device, a mobile data terminal, electronic motor management system, electronic / motorized control device, electronic / motorized control module, embedded system, sensor, microcontroller, control module, motor management system, networked device, machine-like communication device, machine-to-machine (M2M) or Device-to-device (D2D) device, Internet-of-Things (IoT) device, etc., but is not limited to such.

In some aspects, the network can 400 have a plurality of UEs that are directly connected to one another via a sidelink interface. The UEs can be M2M / D2D devices that communicate via physical sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink downlink channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), Physical Sidelink Feedback Channel (PSFCH), etc.

In some aspects, the UE 402 additionally with an application protocol (AP) 406 communicate over an over-the-air connection. The AP 406 can manage a wireless local area network (WLAN) connection, which can be used to take part / all of the network traffic from the RAN 404 to relieve. The connection between the UE 402 and the AP 406 can conform to any Institute of Electrical and Electronics Engineering (IEEE 802.11) protocol, with the AP 406 could be a Wireless Fidelity (Wi-Fi®) router. In some aspects, the UE 402 , the RAN 404 and the AP 406 use a cell WLAN aggregation. Cellular WLAN aggregation may involve the UE 402 from the RAN 404 configured to use both cellular radio resources and WLAN resources.

The RAN 404 can contain one or more access nodes, e.g. the access network (AN) 408 . ON 408 can use air interface protocols for the UE 402 by providing access layer protocols including radio resource control (RRC), PDCP, radio link control (RLC), medium access control (MAC), and layer 1 (L1) protocols. In this way, the AN 408 a data / voice connection between CN 420 and the UE 402 enable. In some aspects, the AN 408 be implemented in a discrete device or as one or more software entities running on server computers, for example as part of a virtual network that can be referred to as a cloud radio access network (CRAN) or a virtual baseband unit pool. The AN 408 can be referred to as base station (BS), gNB, RAN node, eNB, NodeB, road side unit (RSU), transceiver point (TRxP), transceiver point (TRP), etc. The AN 408 may be a macro cell base station or a base station with low power for the provision of femtocells, picocells or similar cells, which compared to macro cells have smaller coverage areas, a lower user capacity or a higher bandwidth.

In aspects in which the RAN 404 comprises a large number of ANs, these can be coupled to one another via an Xn interface (if the RAN 404 is a 5G RAN). The Xn interfaces, which in some aspects can be separated into control / user plane interfaces, can enable the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

The ANs of the RAN 404 can each manage one or more cells, cell groups, component carriers, etc. to the UE 402 provide an air interface for network access. The UE 402 may be connected to multiple cells at the same time from the same or different ANs of the RAN 404 to be provided. For example, the UE 402 and the RAN 404 Use carrier aggregation to provide the UE 402 to enable connection to a large number of component carriers, each corresponding to a primary cell (Pcell) or secondary cell (Scell). In dual connectivity scenarios, a first AN can be a master node providing a Master Cell Group (MCG) and a second AN can be a secondary node providing an SCG. The first / second ANs can be any combination of gNB, ng-eNB, etc.

The RAN 404 can provide the air interface via a licensed spectrum or an unlicensed spectrum. For operation in the unlicensed spectrum, the nodes can use license-supported access (LAA), extended LAA (eLAA) and / or feLAA mechanisms based on carrier aggregation technology (CA) with PCells / Scells. Prior to access to the unlicensed spectrum, the nodes can perform media / carrier detection operations based, for example, on a listen-before-talk (LBT) protocol.

In Vehicle to Everything (V2X) scenarios, the UE 402 or AN 408 be or act as an RSU, which can refer to any traffic infrastructure unit used for V2X communication. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE can be referred to as a “UE-Type RSU”; a gNB can be referred to as "gNB type RSU"; and similar. In one example, an RSU is a computing device that is coupled to radio frequency circuitry located on the roadside that provides connectivity to the UEs of passing vehicles. The RSU may also contain internal data storage circuitry to store intersection geometry, traffic statistics, media, and applications / software for recording and controlling ongoing vehicle and pedestrian traffic. The RSU can provide the very low latency communication required for high speed events such as accident avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU can provide other cellular / WLAN communication services. The components of the RSU can be housed in a weatherproof housing for installation outdoors and may include a network interface controller to provide a wired connection (e.g., ethernet) to a traffic light controller or a backhaul network.

In some aspects, the RAN 404 an NG-RAN 414 with gNBs, for example gNB 416 , or ng-eNBs, for example ng-eNB 418 , being. The gNB 416 can connect to 5G-capable UEs via a 5G-NR interface. The gNB 416 can connect to a 5G core via an NG interface, which can include an N2 interface or an N3 interface. The ng-eNB 418 can also connect to the 5G core via an NG interface. The gNB 416 and the ng-eNB 418 can connect to each other via an Xn interface.

In some aspects, the NG interface can be split into two parts, an NG-U interface (NG-U), which carries traffic data between the nodes of the NG-RAN 414 and a user level function (UPF) 448 (e.g. N3 interface) transmits, and an NG control plane interface (NG-C), which is a signaling interface between the nodes of the NG-RAN 414 and an access and mobility management function (AMF) 444 (e.g. N2 interface) is.

The NG-RAN 414 can provide a 5G NR air interface with the following features: variable subcarrier spacing (SCS); CP-orthogonal frequency division multiplexing (OFDM) for DL, CP-OFDM and DFT-s-OFDM for uplink (UL); Polar, repeat, simplex and reed-Muller codes for control and LDPC for data. The 5G-NR air interface can refer to the CSI reference signal (CSI-RS), the physical downlink shared channel (PDSCH) / physical downlink control channel (PDCCH) demodulation reference signal (DMRS ) support. The 5G-NR air interface must not use a cell specification reference signal (CRS), but can use the physical broadcast channel (PBCH) DMRS for PBCH demodulation, the phase tracking reference signal (PTRS) for phase tracking for Use PDSCH and the tracking reference signal for time tracking. The 5G-NR air interface can operate on frequency range (FR) 1 bands, which include bands below 6 gigahertz (GHz), or on FR2 bands, which include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include a synchronization signal block (SSB), which is a portion of a downlink resource grid that contains the primary synchronization signal (PSS) / secondary synchronization signal (SSS) / PBCH.

In some aspects, the 5G NR air interface can use parts of bandwidth (BWP) for different purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 402 configured with multiple BWPs, with each BWP configuration having a different SCS. If the UE 402 a BWP change is indicated, the SCS of the transfer is also changed. Another use case example for BWP relates to energy saving. In particular, several BWPs can be used for the UE 402 be configured with different numbers of frequency resources (e.g. physical resource blocks (PRBs)) to support data transmission under different traffic load scenarios. A BWP that contains a smaller number of PRBs can be used for data transmission with a low traffic load and at the same time enables power savings at the UE 402 and in some cases with the gNB 416 . A BWP that contains a larger number of PRBs can be used for scenarios with a higher traffic load.

The RAN 404 is communicative with the CN 420 coupled, which contains network elements to provide various functions to support data and telecommunications services for customers / subscribers (e.g. users of the UE 402 ) to provide. The components of the CN 420 can be implemented in a physical node or in separate physical nodes. In some aspects, network function virtualizations (NFV) can be used to identify any or all of the network elements of the CN 420 to virtualize the functions provided on physical computing / storage resources in servers, switches, etc. A logical instantiation of the CN 420 can be referred to as a network slice, and a logical instantiation of part of the CN 420 can be referred to as a network sub-slice.

In some aspects, the CN 420 a 5GC 440 being. The 5GC 440 an authentication server function (AUSF) 442 , AMF 444 , a session management function (SMF) 446 , a user level function (UPF) 448 , a network slice selection function (NSSF) 450 , a network exposure function (NEF) 452 , a Network Function (NF) Repository Function (NRF) 454 , a policy control function (PCF) 456 , a uniform data management system (UDM) 458 and an application function (AF) 460 that are coupled to one another via interfaces (or "reference points") as shown. The functions of the elements of the 5GC 440 can be briefly introduced as follows.

The AUSF 442 can provide data to authenticate the UE 402 store and handle authentication-related functions. The AUSF 442 can enable a common authentication framework for different types of access. In addition to communicating with other elements of the 5GC 440 Via reference points, as shown, the AUSF 442 have a Nausf service based interface.

The AMF 444 there can be other functions of the 5GC 440 enable with the UE 402 and the RAN 404 to communicate and notify of mobility events related to the UE 402 to subscribe. The AMF 444 can be used for registration management (e.g. for the registration of the UE 402 ), connection management, availability management, mobility management, lawful interception of AMF-related events and access authentication and authorization. The AMF 444 can transport session management (SM) messages between the UE 402 and the SMF 446 and act as a transparent proxy for routing SM messages. AMF 444 can also provide transport for SMS (Short Message Service) messages between the UE 402 and an SMS function (SMSF). AMF 444 can with the AUSF 442 and the UE 402 interact to perform various security anchor and context management functions. In addition, AMF 444 be a termination point of a RAN-CP interface, which is an N2 reference point between the RAN 404 and the AMF 444 may contain or be; and the AMF 444 can be a termination point of the non-access layer (NAS) ( N1 ) Signaling and performing NAS encryption and integrity protection. The AMF 444 can also do NAS signaling with the UE 402 via an N3 interworking function (IWF) interface.

The SMF 446 can be responsible for SM (e.g. session setup, tunnel management between UPF 448 and on 408 ); Assignment and management of IP addresses for the UE (including optional authorization); Selection and control of the UP function; Configuration of the traffic control on the UPF 448 to get traffic to the right destination; Termination of interfaces towards policy control functions; Control of parts of policy enforcement, billing and quality of service (QoS); legitimate interception (for SM events and the interface to the Layer Indicator System (LI)); Termination of SM parts of NAS messages; Downlink data notification; Initiation of AN-specific SM information that is sent via AMF 444 via N2 to AN 408 be sent; and determining the session and service continuity mode (SSC) of a session. SM can refer to the management of a PDU session, and a PDU session or "session" can refer to a PDU link service which enables the exchange of PDUs between the UE 402 and the data network 436 provides or enables.

The UPF 448 can be used as an anchor point for intra-radio access technology (RAT) and inter-RAT mobility, as an external PDU session connection point to the data network 436 and serve as a branch point to support multi-homed PDU sessions. The UPF 448 can also perform packet routing and forwarding, perform packet inspection, enforce the part of the policy rules for the user level, intercept packets lawfully (UP collection), create traffic usage reports, perform QoS handling for a user level (e.g. packet filtering, gating, UL / DL rate enforcement) ), Carry out uplink traffic checking (e.g. SDF-to-QoS flow mapping), carry out packet marking on the transport level in the uplink and downlink and trigger downlink packet buffering and downlink data notification. The UPF 448 may contain an uplink classifier to aid in routing traffic flows to a data network.

The NSSF 450 can select a set of network slice instances that the UE 402 serve. The NSSF 450 can also determine allowed network slice selection assistance information (NSSAI) and the association with the subscribed individual network slice selection assistance information (S-NSSAIs), if necessary. The NSSF 450 can also determine the AMF rate required to operate the UE 402 to be used, or a list of candidate AMFs based on appropriate configuration and possibly by querying the NRF 454 . The selection of a set of network slice instances for the UE 402 can from the AMF 444 , where the UE 402 is registered by interacting with the NSSF 450 triggered, which can lead to a change in the AMF. The NSSF 450 can with the AMF 444 interact via an N22 reference point; and can communicate with another NSSF on a visited network via an N31 reference point (not shown). In addition, the NSSF 450 have an Nnssf service based interface.

The NEF 452 can services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g. AF 460 ), Edge computing or fog computing systems, etc. securely disclose. In such aspects, the NEF 452 authenticate, authorize or throttle the AFs. The NEF 452 can also provide information related to the AF 460 are exchanged, and information that are exchanged with internal network functions. For example, the NEF 452 Translate between an AF service identifier and internal 5GC information. The NEF 452 can also receive information from other network functions (NFs) based on the exposed capabilities of other NFs. This information can be found in the NEF 452 as structured data or in a data storage NF using standardized interfaces. The stored information can then be used by the NEF 452 passed on to other NFs and AFs or used for other purposes, such as analysis. In addition, the NEF 452 have an Nnef service interface.

The NRF 454 can support service discovery functions, receive NF-Discovery requests from NF-instances and pass on the information of the discovered NF-instances to the NF-instances. The NRF 454 also manages information about available NF instances and their supported services. As used herein, the terms “instantiating”, “instantiating” and the like can refer to the creation of an instance, and an “instance” can refer to a specific occurrence of an object that can occur, for example, during the execution of program code. In addition, the NRF 454 have the nnrf service based interface.

The PCF 456 can provide policy rules for control plane functions to enforce, and can also support a unified policy framework to control network behavior. The PCF 456 can also implement a front end to access subscription information necessary for policy decisions in a Unified Data Repository (UDR) of the UDM 458 are relevant. In addition to communicating with functions via reference points, as shown, the PCF 456 an npcf service based interface.

The UDM 458 can process subscription-related information to aid in the handling of communication sessions by the network entities; and subscription data of the UE 402 to save. For example, subscription data can be shared between the UDM 458 and the AMF 444 be communicated. The UDM 458 can comprise two parts, an application front end and a UDR. The UDR can store subscription data and policy data for the UDM 458 and the PCF 456 and / or structured data for exposure and application data (including packet flow descriptions (PFDs) for application discovery, application requirement information for multiple UEs 402 ) for the NEF 452 to save. The Nudr service-based interface can be used by the UDR 221 issued to the UDM 458 , PCF 456 and NEF 452 enable access to a specific set of stored data as well as reading, updating (e.g. adding, changing), deleting and subscribing to notifications of relevant data changes in the UDR. The UDM can contain a UDM front end (FE) that is responsible for processing login data, site management, subscription management, etc. Several different front ends can serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and carries out the processing of authentication credentials, the handling of the user identification, the access authorization, the management of the registration / mobility and the subscription management. In addition to communicating with other NFs via reference points, as shown, the UDM 458 have the Nudm service based interface.

The AF 460 can provide the application's impact on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

In some aspects, the 5GC 440 Enable edge computing by selecting operator / third party services to be geographically close to a point where the UE 402 connected to the network. This can reduce latency and load on the network. To provide edge computing implementations, the 5GC 440 a UPF 448 near the UE 402 and select a traffic control from the UPF 448 to the data network 436 Carry out via the N6 interface. This can be based on the UE subscription data, the UE location and that of the AF 460 information provided. In this way the AF 460 Influence the UPF (re-) selection and traffic routing. Based on the deployment of the network operator, if the AF 460 is considered a trusted entity, the AF 460 allow you to interact directly with relevant NFs. In addition, the AF 460 have a Naf service based interface.

The data network 436 can represent various network operator services, Internet access, or third-party services that can be provided by one or more servers, including, for example, application / content servers 438 .

5 shows schematically a wireless network 500 according to various aspects. The wireless network 500 can a UE 502 in wireless communication with an AN 504 include. The UE 502 and the AN 504 may be similar and essentially interchangeable with like components described elsewhere herein.

The UE 502 can have a connection 506 with the AN 504 be communicatively coupled. The connection 506 is shown as an air interface to enable communicative coupling and may conform to cellular communication protocols such as a 5G NR protocol that operates at millimeter wave (mmWave) or sub-6GHz frequencies.

The UE 502 can be a host platform 508 include those with a modem platform 510 is coupled. The host platform 508 can be a processing circuit 512 included with the protocol processing circuit 514 the fashion platform 510 can be coupled. The processing circuit 512 can have different applications for the UE 502 execute, generate / sink application data. The processing circuit 512 may also implement one or more layer operations to send / receive application data to / from a data network. These layer operations can include transport (e.g. User Datagram Protocol (UDP)) and Internet (e.g. IP) operations

The protocol processing circuit 514 may implement one or more of the layer operations to transmit or receive data over the link 506 to facilitate. The one from the protocol processing circuit 514 implemented layer operations can include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 510 can also have a digital baseband circuit 516 that can implement one or more layer operations that are “below” layer operations that are performed by the protocol processing circuit 514 run on a network protocol stack. These operations can e.g. B. physical LAYER (PHY) operations including one or more hybrid automatic repeat request (HARQ) acknowledgment (ACK) functions, scrambling / descrambling, encoding / decoding, layer mapping / de-mapping, modulation symbol mapping, receive symbol / Bit metric determination, precoding / decoding of multi-antenna connections, the one or more space-time, space-frequency or spatial encodings, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals and others may include related functions.

The modem platform 510 can also have a transmission circuit 518 , a receiving circuit 520 , a high frequency circuit 522 and an RF front end (RFFE) 524 contain one or more antenna fields 526 may contain or be associated with them. In short, the transmission circuit 518 a digital-to-analog converter, a mixer, intermediate frequency components, etc. The receiving circuit 520 may contain an analog-to-digital converter, mixer, IF components, etc.; the RF circuit 522 may include a low noise amplifier, power amplifier, power tracking components, etc .; the RFFE 524 may contain filters (e.g. surface / bulk acoustic wave filters), switches, antenna tuners, beam shaping components (e.g. phase array antenna components), etc. The selection and arrangement of the components of the transmission circuit 518 , the receiving circuit 520 , the RF circuit 522 , the RFFE 524 and the antenna panels 526 (commonly referred to as "transmit / receive components") can be specific to the details of a particular implementation; B. whether the communication takes place in time division multiplex (TDM) or in frequency division multiplex (FDM), in mmWave or sub-6 GHz frequencies etc. In some aspects the transmit / receive components can be arranged in several parallel transmit / receive chains, they can be housed in the same or in different chips / modules, etc.

In some aspects, the processing circuit 514 contain one or more instances of control circuits (not shown) in order to provide control functions for the transmitting / receiving components.

A UE reception can be through and via the antenna fields 526 who have favourited RFFE 524 who have favourited RF circuit 522 , the receiving circuit 520 , the digital baseband circuit 516 and the protocol processing circuit 514 getting produced. In some aspects the antenna fields 526 a transfer from the contractor 504 received by receiving signals from a plurality of antenna / antenna elements of the one or more antenna arrays 526 be received.

A UE transmission can be to and from the protocol processing circuit 514 , the digital baseband circuit 516 , the transmission circuit 518 who have favourited RF circuit 522 who have favourited RFFE 524 and the antenna fields 526 being constructed. In some aspects, the transmit components of the UE 504 apply a spatial filter to the data to be transmitted in order to form a transmission beam that is emitted by the antenna elements of the antenna arrays 526 is sent out.

Similar to the UE 502 can do that 504 a host platform 528 include those with a modem platform 530 is coupled. The host platform 528 can be a processing circuit 532 included with the protocol processing circuit 534 the modem platform 530 is coupled. The modem platform can also have a digital baseband circuit 536 , a transmission circuit 538 , a receiving circuit 540 , an RF circuit 542 , an RFFE circuit 544 and antenna fields 546 contain. The components of the contractor 504 can be similar and essentially interchangeable with components of the UE of the same name 502 being. In addition to performing data transmission / reception as described above, the components of the AN 508 perform various logical functions, e.g. B. radio network controller functions (RNC) such. B. the management of radio bearers, the dynamic management of uplink and downlink radio resources and the planning of data packets.

6th FIG. 12 is a block diagram showing components capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing one or more of the methods discussed herein, according to some example aspects. In particular shows 6th a schematic representation of hardware resources 600 , including one or more processors (or processor cores) 610 , one or more storage / storage devices 620 and one or more communication resources 630 each of which has a bus 640 or another interface circuit can be communicatively coupled. For aspects where node virtualization (e.g. NFV) is used, a hypervisor 602 be executed in order to provide an execution environment for one or more network slices / sub-slices to the hardware resources 600 to use.

The processors 610 can eg use a processor 612 and a processor 614 include. With the processors 610 For example, it can be a central processing unit (CPU), a RISC processor (Reduced Instruction Set Computing), a CISC processor (Complex Instruction Set Computing), a graphics processing unit (GPU) , a digital signal processor (DSP) such as A baseband processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The storage / storage devices 620 may include main memory, disk storage, or any suitable combination thereof. The storage / storage devices 620 can include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory, such as: B. dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, etc.

The communication resources 630 may include link or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 604 or one or more databases 606 or other network elements over a network 608 to communicate. The communication resources 630 For example, wired communication components (e.g. for coupling via Universal Serial Bus (USB), Ethernet, etc.), components for cellular communication, components for near field communication (NFC), Bluetooth® (or Bluetooth® Low Energy), Wi-Fi® - Components and other communication components include.

The instructions 650 may contain software, a program, an application, an applet, an app, or other executable code to run at least one of the processors 610 cause one or more of the methods discussed herein to be performed. The instructions 650 can be fully or partially in at least one of the processors 610 (e.g. in the processor's cache memory), in the storage devices 620 or a suitable combination thereof. In addition, any part of the instructions can 650 from any combination of the peripheral devices 604 or the databases 606 to the hardware resources 600 be transmitted. Accordingly, the memory is the Processors 610 who have favourited Storage / Storage Devices 620 who have favourited peripheral devices 604 and the databases 606 Examples of computer readable and machine readable media.

In one or more aspects, at least one of the components depicted in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods, as set out in the following example section. For example, as described above in connection with one or more of the preceding figures, the baseband circuit can be configured to operate in accordance with one or more of the examples below. As another example, the circuitry associated with a UE, a base station, a network element, etc., as described above in connection with one or more of the preceding figures, can be configured to operate in accordance with one or more of the ones listed in the example section below Examples works.

Example 1 may include a device to be deployed as the next generation eNodeB or NodeB in EPS or 5GS, including: an MN and an SN connected through an X2 or Xn interface; and means of supporting CHO for the UE.

Example 2 may include that before an MN initiates CHO to a potential destination node, the source SN informs that CHO will take place when it retrieves the latest SCG configuration, so that early data forwarding by the source SN later can be decided when the source SN receives forwarding TNL address information from the destination.

Example 3 may include that after preparing the CHO with a potential destination node, the MN informs the source SN that this is done for the CHO when forwarding the TNL address information from the destination so that the early data forwarding by the source SN over the established DL-DRB forwarding tunnel can be decided, if any.

Example 4 may include a method of an MN, the method comprising: determining that a conditional handover is triggered for a UE from a source node to a destination node; Encoding an indication that the conditional handover is triggered for transmission to the source node; and triggering the conditional handover after the notification has been transmitted.

Example 5 may include the method of Example 4, or any other example herein, wherein the indication is included in a message to retrieve an SCG configuration.

Example 6 may include the method of Example 4-5, or another example herein, wherein the source node is to perform early data forwarding when forwarding TNL address information is received from the destination node.

Example 7 may include the method of Example 4-6 or any other example herein, wherein the method is performed by a gNB or a portion thereof.

Example 8 may include a method of an SN, the method comprising: receiving an indication from an MN that a conditional handover is initiated for a UE from the source node to a destination node; Receiving forwarding TNL address information from the destination node; and performing early data forwarding based on the indication and forwarding TNL address information.

Example 9 may include the method of Example 8, or any other example herein, with the indication included in a message to retrieve an SCG configuration.

Example 10 may include an apparatus of a source NB for operation in a fifth generation network, which apparatus may comprise: an MN having one or more processors configured to: send an HO request message to a destination GNB that requests the execution of a CHO from UE from the source GNB to the target GNB; receive a CHO request confirmation message from the target GNB; and provide TNL address information to the transport network layer for forwarding to an SN of the source GNB.

Example 11 may include the apparatus of Example 10, wherein the one or more processors of the MN are configured to provide the forwarding TNL address information prior to providing an SN release request message to the SN.

Example 12 may include the apparatus of any of Examples 10-11, wherein the SN further includes one or more processors configured to perform data forwarding before the UE accesses the target gNB based on the forwarding TNL address information.

Example 13 may include the apparatus of Example 3, wherein the one or more processors of the SN are configured to forward downlink packet data convergence protocol service data units to the destination gNB.

Example 14 may include the apparatus of any of Examples 10-13, wherein: the one or more processors of the MN are configured to provide an SN modification CHO message to the SN prior to initiating the CHO, which is an SCG -Configuration requests; and the one or more processors of the SN are configured to provide an SN modification acknowledgment message to the MN that includes the SCG configuration.

Example 15 may include the apparatus of any of Examples 12-14, wherein the one or more processors of the SN are configured to perform data forwarding before the UE accesses the target gNB by using downlink data radio bearers -Use forwarding tunnels established with the destination gNB.

Example 16 may include the apparatus of any of Examples 10-14, wherein the one or more processors of the MN are configured to use the forwarding TNL address information as an Xn-U ADDRESS INDICATION message while operating the dual connectivity provide multiple radio access technologies.

Example 17 may include the apparatus of any of Examples 10-14, wherein the one or more processors of the MN are configured to provide the forwarding TNL address information as a class 2 message.

Example 18 may include the apparatus of any of Examples 10-14, wherein the one or more processors of the MN are configured to display the forwarding TNL address information as an X2 access level DATA FORWARDING ADDRESS INDICATION message during the developed to provide universal terrestrial radio access network operation.

Example 19 may include an apparatus of a source gNB for operation in a fifth generation network, the apparatus including: an MN containing one or more processors configured to forward TNL address information to an SN provide the source gNB; and the SN includes one or more processors configured to: receive the forwarding TNL address information from the MN; and perform data forwarding before the UE accesses the destination gNB based on the forwarding TNL address information.

Example 20 may include the apparatus of Example 19, wherein the one or more processors of the MN are configured to provide the forwarding TNL address information prior to sending an SN release request message to the SN.

Example 21 may include the apparatus of any of Examples 19-20, wherein the one or more processors of the MN are further configured to: send an HO request message to a target gNB requesting a CHO from UE from the Perform source gNB to target gNB; and receive a CHO request confirmation message from the target gNB, wherein the one or more processors of the MN are further configured to provide the forwarding TNL address information based on the CHO request confirmation message.

Example 22 may include the apparatus of any of Examples 19-21, wherein the one or more processors of the SN are further configured to forward downlink packet data convergence protocol service data units to the destination gNB.

Example 23 may include the apparatus of any of Examples 21-22, wherein: the one or more processors of the MN are further configured to provide an SN modification CHO message to the SN prior to initiating the CHO, which includes a Requests secondary cell group (SCG) configuration; and the one or more processors of the SN are further configured to provide an SN modification confirmation message to the MN that includes the SCG configuration.

Example 24 may include the apparatus of any of Examples 19-23, wherein the one or more processors of the SN are configured to perform data forwarding before the UE accesses the target gNB by using downlink data radio bearers -Use forwarding tunnels established with the destination gNB.

Example 25 may include the apparatus of any of Examples 19-24, wherein the one or more processors of the MN are configured to have the forwarding TNL address information as an Xn-U ADDRESS INDICATION message during dual connectivity operation provide multiple radio access technologies.

Example 26 may include the apparatus of any of Examples 19-24, wherein the one or more processors of the MN are configured to provide the forwarding TNL address information as a class 2 message.

Example 27 may comprise the apparatus of any of Examples 19-24, wherein the one or more processors of the MN are configured to receive the forwarding TNL address information as an X2-LEVEL DATA FORWARDING ADDRESS INDICATION message during of the developed universal terrestrial radio access network operation.

Example 28 may include the apparatus of any of Examples 19-27, wherein the routing TNL address information includes routing addresses for a plurality of evolved radio access bearers.

Example 29 may include an apparatus that includes means for performing one or more elements of a method described in or associated with any of Examples 1-28, or any other method or process described herein.

Example 30 may include one or more non-transitory computer-readable media containing instructions to cause an electronic device, when the instructions are executed by one or more processors of the electronic device, to perform one or more elements of a method described in any of Examples 1 -28 or is related to it, or any other method or process described herein.

Example 31 may include apparatus that includes logic, modules, or circuitry to perform one or more elements of a method described in or related to any of Examples 1-28, or any other method or process described herein .

Example 32 may include a method, technique, or process as described or related to any of Examples 1-28, or portions thereof.

Example 33 may include an apparatus that includes one or more processors and one or more computer readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform the method to perform the technique or process as described in or associated with any of Examples 1-28, or parts thereof.

Example 34 may include a signal as described in or associated with any of Examples 1-9, or portions thereof.

Example 35 may include a datagram, packet, frame, segment, PDU, or message as described or related to any of Examples 1-28, or portions thereof, or otherwise described in the present disclosure.

Example 36 may include a signal encoded with data as described or associated with any of Examples 1-28, or portions thereof, or otherwise described in the present disclosure.

Example 37 may include a signal encoded with a datagram, packet, frame, segment, PDU, or message as described, or relating to, or in any of Examples 1-28 or in parts thereof otherwise described in the present disclosure.

Example 38 may include an electromagnetic signal carrying computer readable instructions, the execution of the computer readable instructions by one or more processors to cause the one or more processors to use the method, technique, or process, as in any of the examples 1-28 or parts thereof described or associated with it.

Example 39 may include a computer program containing instructions, the execution of the program by a processing element intended to cause the processing element to perform the method, technique, or process as described in or associated with any of Examples 1-28, or parts thereof .

Example 40 may include a signal on a wireless network as shown and described herein.

Example 41 may include a method of communicating on a wireless network as shown and described herein.

Example 42 may include a system for providing wireless communication as shown and described herein.

Example 43 may include a device for providing wireless communication as shown and described herein.

Each of the examples described above can be combined with any other example (or any combination of examples), unless expressly stated otherwise. The foregoing description of one or more implementations has been presented for the purpose of illustration and description, but is not intended to be exhaustive or to limit the scope of the aspects to the precise form disclosed. Modifications and variations are possible in light of the above teachings or can be learned from practice of various aspects.

Unless otherwise used here, terms, definitions and abbreviations agree with those in 3GPP TR 21,905 v16.0.0 (2019-06) match defined terms, definitions and abbreviations. For the purposes of this document, the following abbreviations may apply to the examples and aspects discussed here.

For the purposes of this document, the following terms and definitions apply to the examples and aspects discussed here.

The term “circuit” as used herein refers to hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated or group) and / or memory (shared, dedicated or group), an application-specific integrated Circuit (ASIC), a field-programmable component (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-performance PLD (HCPLD), a structured ASIC or a programmable SoC), digital signal processors (DSPs), etc. configured to provide the functionality described. In some aspects, the circuit can execute one or more software or firmware programs to provide at least a portion of the functionality described. The term “circuit” can also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code . From these aspects, the combination of hardware elements and program code can be referred to as a certain type of circuit.

As used herein, the term “processor circuit” refers to a circuit that is or is capable of sequentially and automatically executing a series of arithmetic or logical operations or recording, storing and / or transmitting digital data a part of it. The processing circuitry can contain one or more processor cores for executing instructions and one or more memory structures for storing program and data information. The term "processing circuit" can refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core -Processor and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules and / or functional processes. The processing circuitry can contain other hardware accelerators, which can be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators can include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuit” and / or “baseband circuit” can be viewed as a synonym for “processor circuit” and can be designated as such.

As used herein, the term “interface circuit” refers to a circuit that enables the exchange of information between two or more components or devices, is a part thereof or comprises such a circuit. The term "interface circuit" can refer to one or more hardware interfaces, e.g. B. on buses, I / O interfaces, interfaces of peripheral components, network interface cards and / or the like.

As used herein, the term “user device” or “UE” refers to a device with radio communication capabilities and can describe a remote user of network resources on a communication network. The term "user device" or "UE" can be used as a synonym for client, mobile device, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio, reconfigurable radio , reconfigurable mobile device, etc., and can be referred to as such. Additionally, the term “user device” or “UE” can include any type of wireless / wired device or any computing device with a wireless communication interface.

The term “network element” used here refers to physical or virtualized devices and / or infrastructures that are used to provide network services for wired or wireless communication. The term "network element" can be used as a synonym for and / or as a designation for a networked computer, network hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI and / or the like can be considered.

As used herein, the term “computer system” refers to any type of interconnected electronic device, computing device, or component thereof. In addition, the term “computer system” and / or “system” can refer to various components of a computer that are communicatively coupled to one another. In addition, the term “computer system” and / or “system” can refer to a plurality of computing devices and / or a plurality of computer systems that are communicatively coupled to one another and configured to share computer and / or network resources.

The term “device”, “computing device” or the like, as used herein, refers to a computing device or computer system with program code (e.g. software or firmware) that is specially designed to provide a particular computer resource. A “virtual device” is a virtual machine image that is implemented by a hypervisor-equipped device that virtualizes or emulates a computing device, or is otherwise intended to serve a specific computing resource.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a particular device, such as a computer. B. Computing devices, mechanical devices, storage space, processor / CPU time, processor / CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input / output operations, ports or network sockets, channel / Link allocation, throughput, memory usage, network, database and applications, workload units and / or the like. A "hardware resource" can refer to computing, memory and / or Obtain network resources provided by one or more physical hardware elements. A “virtualized resource” can refer to computing, storage and / or network resources provided by a virtualization infrastructure for an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that computing devices / systems can access over a communication network. The term “system resources” can refer to any type of shared unit for the provision of services and can include computer and / or network resources. System resources can be thought of as a set of related functions, network data objects, or services accessible through a server, such system resources residing on a single host or multiple hosts and being uniquely identifiable.

The term “channel” as used here refers to any tangible or intangible transmission medium that is used to transmit data or a data stream. The term "channel" can be synonymous and / or synonymous with "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "connection", "data connection", "carrier", " Radio Frequency Carrier ”and / or any other similar term used to designate a path or medium over which data is transmitted. In addition, as used herein, the term “link” refers to a connection between two devices over a RAT for the purpose of sending and receiving information.

The terms “instantiating”, “instantiating” and the like used here refer to the creation of an instance. An “instance” also refers to a specific occurrence of an object, e.g. B. can occur when executing program code.

The terms “coupled”, “communicatively coupled” and their derivatives are used here. The term “coupled” can mean that two or more elements are in direct physical or electrical contact with one another, can mean that two or more elements are indirectly in contact with one another but still cooperate or interact with one another, and / or can mean that one or more other elements between the elements that are considered to be coupled, coupled or connected to one another. The term “directly coupled” can mean that two or more elements are in direct contact with one another. The term “communicatively coupled” can mean that two or more elements are in contact with one another via a means of communication, e.g. B. over a wire or other connection, over a wireless communication channel or a wireless connection and / or the like.

The term “information element” refers to a structure element that contains one or more fields. The term “field” refers to the individual content of an information element or to a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configuration that is configured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS / PBCH block.

The term "Primary Cell" refers to the MCG cell operating on the primary frequency on which the UE either performs the initial connection setup procedure or initiates the connection setup procedure.

The term “primary SCG cell” refers to the SCG cell in which the UE carries out random access when it carries out the reconfiguration procedure with sync for DC operation.

The term “secondary cell” refers to a cell that provides additional radio resources in addition to a special cell for a UE configured with CA.

The term “secondary cell group” refers to the subset of serving cells that includes the PSCell and zero or more secondary cells for a UE configured with DC.

The term “serving cell” refers to the primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC as there is only one serving cell including the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells including the special cell (s) and all secondary cells for a UE in RRC_CONNECTED that is configured with CA / DC.

The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise the term “Special Cell” refers to the Pcell.

QUOTES INCLUDED IN THE DESCRIPTION

This list of the documents listed by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent literature cited

• US 63/034872 [0001]

Claims (10)

A source gNodeB (gNB) device for operation on a fifth generation network, the device comprising: a master node (MN) that has one or more processors that are configured to: send a handover (HO) request message to a target gNB requesting the performance of a conditional HO (CHO) of user equipment (UE) from the source gNB to the target gNB receive a CHO request confirmation message from the target gNB; and Provide forwarding transport network layer (TNL) address information to a secondary node (SN) of the source gNB; optionally wherein the one or more processors of the MN are configured to provide the forwarding TNL address information prior to delivering an SN release request message to the SN. The device according to Claim 1 , further comprising wherein the SN comprises one or more processors configured to perform data forwarding prior to the UE accessing the target gNB based on the forwarding TNL address information; optionally wherein the one or more processors of the SN are configured to forward downlink packet data convergence protocol service data units to the destination gNB. The device according to one of the Claims 1 or 2 wherein: the one or more processors of the MN are configured to provide an SN Modification CHO message to the SN requesting configuration of a secondary cell group (SCG) prior to initiating the CHO; and the one or more processors of the SN are configured to provide the MN with an SN modification acknowledgment message having the SCG configuration; and / or wherein the one or more processors of the MN are configured to provide the forwarding TNL address information as an Xn-U ADDRESS INDICATION message during dual connectivity operation with multi-radio access technology. The device according to one of the Claims 2 or 3 wherein the one or more processors of the SN are configured to perform data forwarding prior to the UE accessing the destination gNB using downlink radio bearer relay tunnels established with the destination gNB. The device according to one of the Claims 1 - 4th wherein the one or more processors of the MN are configured to provide the forwarding TNL address information as a class 2 message; or wherein the one or more processors of the MN are configured to provide the forwarding TNL address information as an X2 access level DATA FORWARDING ADDRESS INDICATION message during the evolved universal terrestrial radio access network operation. A source gNodeB (gNB) device for operation on a fifth generation network, the device comprising: a master node (MN) having one or more processors configured to provide address information for the transport network layer (TNL) to a secondary node (SN) of the source gNB; and wherein the SN comprises one or more processors configured to: receive the forwarding TNL address information from the MN; and perform the data forwarding prior to the UE accessing the target gNB based on the forwarding TNL address information; optionally wherein the one or more processors of the MN are configured to provide the forwarding TNL address information prior to delivering an SN release request message to the SN. The device according to Claim 6 , wherein the one or more processors of the MN are further configured: a handover (HO) request message to a destination gNB requesting a conditional HO (CHO) of user equipment (UE) from the source gNB to the destination to carry out, to send gNB; and receive a CHO request confirmation message from the target gNB, wherein the one or more processors of the MN are further configured to provide the forwarding TNL address information based on the CHO request confirmation message; and / or wherein the one or more processors of the SN are further configured to forward downlink packet data convergence protocol service data units to the destination gNB; and / or wherein the one or more processors of the MN are further configured to provide an SN modification CHO message to the SN prior to initiating the CHO, requesting a secondary cell group (SCG) configuration; and the one or more processors of the SN are further configured to provide the MN with an SN modification confirmation message that includes the SCG configuration. The device according to one of the Claims 6 or 7th wherein the one or more processors of the SN are configured to perform data forwarding prior to the UE accessing the target gNB using downlink data radio bearer relay tunnels established with the target gNB; and / or wherein the forwarding TNL address information includes forwarding addresses for a plurality of advanced radio access bearers. The device according to one of the Claims 6 - 8th wherein the one or more processors of the MN are configured to provide the forwarding TNL address information as an Xn-U ADDRESS INDICATION message during dual connectivity operation with multi-radio access technology; or wherein the one or more processors of the MN are configured to provide the forwarding TNL address information as a class 2 message; or wherein the one or more processors of the MN are configured to provide the forwarding TNL address information as an X2 access level DATA FORWARDING ADDRESS INDICATION message during operation of a developed universal terrestrial radio access network. Method of a source node (SN), comprising: Receiving an indication from a master node (MN) that a conditional handover for user equipment (UE) is triggered from the source node to a destination node; Receiving forwarding transport network layer (TNL) address information from the destination node; and Performing an early data forwarding based on the indication and the forwarding TNL address information.

Images