Method and radio network node for handling communications - Patents.com

The method of sending UP indications for user plane setup during UE handovers in wireless networks addresses the inefficiencies of IAB nodes by reducing resource waste and complexity, ensuring secure and efficient operations.

JP7591585B2Active Publication Date: 2024-11-28TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2022571754
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-05-28
Filing Date
2021-05-27
Publication Date
2024-11-28
Estimated Expiration
2041-05-27

AI Technical Summary

Technical Problem

Existing wireless communication networks face challenges in efficiently managing user equipment (UE) handovers and cell selections for integrated access and backhaul (IAB) nodes without establishing user plane connectivity, leading to resource wastage and increased complexity.

Method used

A method is introduced where wireless network nodes send messages with a first UP indication to determine whether to set up user plane communication for UE, allowing for secure and efficient handovers or cell selections by ignoring unnecessary user plane setup instructions.

Benefits of technology

This approach reduces resource consumption and complexity by avoiding unnecessary user plane connections, while maintaining security and compatibility with legacy UE messages, thus optimizing IAB-MT operations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007591585000007
    Figure 0007591585000007
  • Figure 0007591585000008
    Figure 0007591585000008
  • Figure 0007591585000009
    Figure 0007591585000009
Patent Text Reader

Abstract

[0010] Embodiments herein relate, for example, to a method implemented by a source radio network node (140) for handling communications in a wireless communication network, the source radio network node being adapted to relay data packets between a first radio network node and a UE in the wireless communication network, wherein the source radio network node (140) sends to a target radio network node (150, 12, 15) a message related to cell selection and / or handover for the UE, the message including a first user plane indication, the first user plane indication being an indication of whether to set up user plane communications for the UE.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The embodiments herein relate to source and target radio network nodes, such as integrated access and wireless access backhaul (IAB) nodes, and methods implemented therein for wireless communication. Additionally, computer program products and computer-readable storage media are also provided herein. In particular, the embodiments herein relate to handling communications, such as controlling / managing communication or connection setup during handover or cell selection, in wireless communication networks. [Background technology]

[0002] In a typical wireless communication network, user equipment (UE), also known as wireless communication device, mobile station, station (STA) and / or wireless device, communicates with one or more core networks (CN) through a radio access network (RAN). The RAN covers a geographical area that is divided into service areas or cell areas, each service area or cell area being served by a radio network node, such as an access node, e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may be referred to as a Node B, gNode B, or eNode B. A service area or cell area is a geographical area in which radio coverage is provided by a radio network node. The radio network node operates on radio frequencies to communicate over an air interface with UEs within range of the radio network node. The radio network node communicates to the UEs over a downlink (DL) and the UEs communicate to the radio network node over an uplink (UL).

[0003] The Universal Mobile Telecommunications System (UMTS) is a third generation communication network that evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS Terrestrial Radio Access Network (UTRAN) is essentially a RAN that uses Wideband Code Division Multiple Access (WCDMA) and / or High Speed ​​Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree on standards for current and future generation networks, specifically UTRAN, exploring enhanced data rates and radio capacity. In some RANs, as in the case of UMTS, several radio network nodes may be connected, for example, by landlines or microwaves, to a controller node, such as a radio network controller (RNC) or base station controller (BSC), which monitors and coordinates various activities of multiple radio network nodes connected to the controller node. The RNC is generally connected to one or more core networks.

[0004] Specifications for the Evolved Packet System (EPS) have been finalized within 3GPP, and this work will continue in upcoming 3GPP releases, such as 4G networks and 5G networks, such as New Radio (NR). The EPS comprises an Enhanced Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and an Evolved Packet Core (EPC), also known as the System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology in which radio network nodes are directly connected to the EPC core network. Thus, the Radio Access Network (RAN) of the EPS has an essentially "flat" architecture, with radio network nodes directly connected to one or more core networks.

[0005] In emerging 5G technologies, such as New Radio (NR), the use of a large number of transmit and receive antenna elements is important because it allows for the use of beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmit signal in one or more selected directions and suppress the transmit signal in other directions. Similarly, on the receive side, the receiver can amplify the signal from one or more selected directions and suppress unwanted signals from other directions.

[0006] Next-generation systems are expected to support a wide range of use cases with varying requirements, ranging from fully mobile devices to stationary Internet of Things (IoT) or fixed wireless broadband devices. Traffic patterns associated with many use cases can be expected to consist of short or long bursts of data traffic with waiting periods of varying length in between, referred to herein as inactive states. In NR, both license-assisted access and standalone unlicensed operation will be supported. Therefore, procedures for Physical Random Access Channel (PRACH) transmissions and / or Scheduling Request (SR) transmissions in unlicensed spectrum may be investigated in 3GPP.

[0007] 3GPP is studying potential solutions for the efficient operation of Integrated Access and Radio Access Backhaul (IAB) in NR, or Integrated Access and Backhaul for short. In the context of IAB, there are two types of nodes identified as components of the RAN: IAB Node: A RAN node that supports wireless access to UEs and wirelessly backhauls access traffic. IAB Donor: An IAB node that provides the UE's interface to the core network and wireless backhauling functions to the IAB node, i.e., a RAN node.

[0008] The IAB strives to reuse existing functions and interfaces defined for access. In particular, the Mobile Termination (MT), gNB Distributed Unit (DU), gNB Central Unit (CU), User Plane Function (UPF), Access and Mobility Management Function (AMF) and Session Management Function (SMF), as well as the corresponding interfaces NR Uu, F1, NG, X2 and N4 (between MT and gNB) are used as a baseline for the IAB-architecture. Modifications or extensions to these functions and interfaces for the support of the IAB will be described in the context of the architecture discussion. Additional functionality such as multi-hop forwarding is included in the architecture discussion as it is necessary for understanding of the IAB operation and as some aspects may require standardization.

[0009] The MT function is defined as a component of the mobile equipment. In the context of this study, MT is referred to as the function present on the IAB node that terminates the radio interface layer of the backhaul Uu interface towards the IAB donor or other IAB nodes.

[0010] FIG. 1 shows a reference diagram for the IAB architecture (see 3gpp TR38.874v0.7.0) in standalone mode, including one IAB donor and multiple IAB nodes. The IAB donor may be treated as a single logical node, including a set of functions, such as gNB-DU, gNB-CU control plane (CP), gNB-CU user plane (UP), and potentially other functions. In a deployment, the IAB donor may be split according to these functions, which may be either all co-located or not co-located, as allowed by the 3GPP NG-RAN architecture. When such a split is used, IAB-related aspects may arise. Also, some of the functions currently associated with the IAB donor may eventually be moved outside the IAB donor if it becomes clear that those functions do not perform IAB-specific tasks.

[0011] In EPS, when a Mobility Management Entity (MME) requests UE context establishment in the RAN along with a User Plane (UP) setup for a session, the MME may only provide security keys and UE security capabilities towards the RAN, i.e. only the following S1AP messages (disclosed in 3gpp TS36.413v.16.0.0) may carry security related information:

[0012] Section 9.1.4.1 Initial Context Setup Request of 3gpp TS36.413v16.0.0 discloses an S1AP message that carries security related information according to the following:

[0013] This message is sent by the MME to request the setup of a UE context.

[0014] Direction: MME→eNB TIFF0007591585000001.tif253170

[0015] When there is no need to establish a UP, for example for Control Plane (CP) IoT optimization where data is sent on Non-Access Stratum (NAS) messages without using a UP, the RAN is not required to establish a UE context, there is no Access Stratum (AS) security protection and the MME will not provide security related information as in the above messages. See the following S1AP message from 3gpp TS36.413v.16.0.0, where the MME only asks the RAN to set up a connection for NAS transport during attach:

[0016] Section 9.1.4.20 of 3gpp TS36.413v.16.0.0 Connection Establishment Indication discloses the S1AP message.

[0017] This message is sent by the MME to complete the establishment of the UE associated logical S1 connection.

[0018] Direction: MME→eNB TIFF0007591585000002.tif55170

[0019] However, with the introduction of the IAB node (see 3gpp TS 23.401 v.16.0.0 clause 4.3.32), the IAB-MT / UE part of the IAB node must first be registered in the core network using UE procedures, and a secure connection between the IAB node and the IAB donor node is required. IAB-MT / UE means a node that terminates the radio interface layer of the backhaul interface towards the IAB donor or other IAB nodes.

[0020] In an IAB node, a Data Radio Bearer (DRB) is only required to connect the IAB node with the Operation, Administration and Maintenance (OAM) system. There are other ways to connect to the OAM, such as the Backhaul Radio Link Channel (BH RLC Channel). The connection through the DRB is agreed by RAN3 to be optional, for example, the IAB Baseline (BL) Change Request (CR) for 3gpp TS 38.401 in clause 8.2.x on IAB node mobility states:

[0021] The IAB donor CU sends a UE context setup request message to the target parent node IAB-DU to create a UE context for moving the IAB-MT and to set up one or more bearers that can be used by the moving IAB-MT for its own signaling and optionally data traffic. Summary of the Invention

[0022] The IAB-MT / UE may provide a sufficient and complete set of functionality to meet all IAB node-specific requirements without simultaneously supporting UP.

[0023] To operate in the Access Stratum in a secure manner, i.e. using ciphering and integrity protection, requires that for a given IAB-MT / UE, when it becomes attached to the network on the user plane (UP), the MME provides security key information to the eNodeB to which this IAB-MT / UE connects on the Access Stratum.

[0024] The purpose of the IAB-MT / UE establishing a packet data network (PDN) connection is for the IAB-MT / UE to download the parameters for the cells configured in the IAB-DU, which may also include the OAM configuration, e.g., IP address(es) assigned to the IAB node. However, IAB specifications such as R3-201597 IAB BL CR for TS38.401 allow alternative ways to enable OAM connectivity other than via a PDN connection and IP address assignment other than via OAM. For example, the IAB node may alternatively establish an OAM connection via backhaul connectivity and / or the IAB node may receive an IP address(es) from an IAB donor. Thus, the establishment of a PDN connection, i.e., a UP connection, for the IAB-MT / UE is not mandatory.

[0025] In the working groups for RAN2 and RAN3, it was agreed that the establishment of UP by IAB-MT is optional. In the RAN3 specifications, the procedures for legacy UE handover, secondary node addition, and UE context management are reused to enable IAB-MT context management, secondary node addition, and handover, and therefore the IAB-MT is treated like a UE. However, in some of these legacy messages reused for IAB-MT, the presence of information elements (IEs) related to user plane establishment is mandatory, which contradicts the above agreement. One example of the consequence of keeping these mandatory user plane related IEs is that it is not possible to handover an IAB-MT over X2 or Xn if the IAB-MT does not have an established protocol data unit (PDU) session.

[0026] The relevant specifications and messages are: TS36.413: Messages used in the Handover Resource Allocation and Initial Context Setup S1AP procedures; TS38.413: Messages used in handover preparation and handover resource allocation NGAP procedures; TS36.423: Messages used in handover preparation, SeNB addition preparation, UE context retrieval and SgNB addition preparation X2AP procedures; · TS38.423: Messages used in handover preparation and S-NG-RAN node addition preparation XnAP procedures.

[0027] It should be noted that although there are additional messages in the above specifications where UP related IEs are mandatory, these procedures are therefore specific to UP establishment and therefore not relevant to the issue at hand.

[0028] Methods for enabling establishment of CP connection security for IAB-MT without establishing a UP connection have been disclosed previously. The present disclosure addresses the problem of performing handover and / or secondary node addition without establishing a user plane connection. The embodiments herein also propose a specific signaling solution for the problem at hand.

[0029] It is an object of the present specification to provide mechanisms for enabling communication, for example handling or managing handover or cell selection of a UE, in a secure manner in a wireless communication network.

[0030] According to one aspect, the object is achieved according to an embodiment of the present specification by providing a method for handling communications in a wireless communication network, the method being implemented by a source radio network node, the source radio network node being adapted to relay data packets between a first radio network node and a UE in the wireless communication network, the UE sending a message related to cell selection and / or handover for the UE to a target radio network node, the message including a first UP indication, the first user plane indication being an indication of whether to set up user plane communications for the UE.

[0031] According to another aspect, the object is achieved by providing a method implemented by a target radio network node for handling communication in a wireless communication network according to an embodiment of the present specification. The wireless communication network comprises a source radio network node that relays data packets between a first radio network node and a UE. The target radio network node receives a message related to cell selection or handover for the UE from the source radio network node or the first radio network node, the message including a first user plane indication, the first user plane indication being an indication of whether to set up user plane communication for the UE. The target radio network node further performs a connection setup for the UE based on the first user plane indication. For example, the target radio network node may perform a connection setup for the UE based on the first UP indication, e.g., will not set up a user plane, e.g., the target radio network node will simply ignore information related to user plane resources when the first UP indication indicates a non-UP setup.

[0032] According to another aspect of an embodiment herein, the objective is achieved by providing a source radio network node for handling communications in a wireless communication network, the source radio network node being adapted to relay data packets between a first radio network node and a UE in the wireless communication network, the source radio network node being configured to send to a target radio network node a message related to cell selection and / or handover for the UE, the message including a first UP indication, the first UP indication being an indication of whether to set up user plane communications for the UE.

[0033] According to another aspect of an embodiment herein, the object is achieved by providing a target radio network node, such as an IAB node, for handling or managing communications in a wireless communication network. The wireless communication network comprises a source radio network node that relays data packets between a first radio network node and a UE. The target radio network node is configured to receive a message related to cell selection or handover for the UE from the source radio network node or the first radio network node, the message including a first UP indication, the first user plane indication being an indication of whether to set up user plane communications for the UE. The target radio network node is further configured to perform a connection setup for the UE based on the first user plane indication. The message may include a first UP indication indicating not to use UP setup. The radio network node may then be configured to perform a connection setup for the UE based on the first UP indication, for example, to not set up a user plane or the target radio network node will simply ignore information related to user plane resources.

[0034] Further provided herein is a computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform the above-described method performed by the source radio network node and the target radio network node, respectively. Further provided herein is a computer-readable storage medium having stored thereon a computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform the above-described method performed by the source radio network node and the target radio network node, respectively.

[0035] The embodiments herein introduce a solution with minimal impact to enable IAB-MT operation without the need to set up user plane connections for IAB-MT, i.e., PDU sessions, DRBs for the UE in case of NG-RAN, and E-RABs for the UE in case of E-UTRAN. The embodiments herein avoid unnecessary establishment of user plane connections for the UE, such as IAB-MT. This allows saving resources and memory in the IAB node as well as in the core network, and reduces complexity. Furthermore, it allows using legacy UE messages, minimizing changes to current technology, such as changes to Abstract Syntax Notation One (ASN.1). Thus, the embodiments herein manage handover or cell selection of the UE in a secure and efficient manner.

[0036] Embodiments will now be described in more detail with reference to the enclosed drawings. [Brief description of the drawings]

[0037] [Figure 1] FIG. 1 is a reference diagram illustrating the IAB architecture. [Diagram 2] 1 is an overview illustrating a wireless communication network according to an embodiment herein; [Diagram 3]1 is a combined signaling scheme and flow chart according to some embodiments of the present disclosure. [Figure 4] 4 is a schematic flow chart illustrating a method performed by a source radio network node according to embodiments herein. [Diagram 5] 1 is a schematic flow chart illustrating a method performed by a target radio network node according to embodiments herein. [Figure 6] FIG. 2 is a block diagram illustrating a source radio network node according to embodiments herein. [Figure 7] FIG. 2 is a block diagram illustrating a target wireless network node, according to embodiments herein. [Figure 8] FIG. 1 illustrates a communications network connected to a host computer through an intermediate network, according to some embodiments. [Figure 9] FIG. 2 illustrates a host computer communicating with user equipment via a base station over a partially wireless connection according to some embodiments. [Figure 10] FIG. 1 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 11] FIG. 1 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 12] FIG. 1 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 13] FIG. 1 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0038] The embodiments herein generally relate to wireless communication networks. Figure 2 is an overview of a wireless communication network 1. The wireless communication network 1 comprises one or more RANs and one or more CNs. The wireless communication network 1 may use one or several different technologies. The embodiments herein relate to recent technology trends of particular interest in a New Radio (NR) context, but the embodiments are also applicable in further development of existing wireless communication systems, such as LTE or Wideband Code Division Multiple Access (WCDMA).

[0039] In the wireless communication network 1, user equipment (UE) 10, such as a mobile station, IAB-MT, non-access point (non-AP) STA, STA, wireless device and / or wireless terminal, is provided, which communicates via one or more access networks (ANs), e.g., RANs, to one or more core networks (CNs). It should be understood by those skilled in the art that "UE" is a non-limiting term meaning any terminal, wireless communication terminal, IAB-MT, NB-IoT device, machine-type communication (MTC) device, D2D (device to device) terminal, or node, such as a smartphone, laptop computer, mobile phone, sensor, relay, mobile tablet, or even a small base station, capable of communicating using wireless communication with a wireless network node within an area served by the wireless network node.

[0040] The wireless communication network 1 comprises network nodes 12, such as baseband units (BBUs) such as MME, AMF, IAB donor nodes, access nodes, access controllers, base stations, e.g. radio base stations such as gNode B (gNB), evolved Node B (eNB, eNodeB), Node B, base transceiver stations, wireless remote units, access point base stations, base station routers, wireless local area network (WLAN) access points or access point stations (AP STAs), standalone access points, or any other network units or nodes capable of communicating with UEs in an area served by a wireless network node, e.g. depending on the first radio access technology and terminology used. It is noted that the service area may be indicated as a cell, beam, beam group, or the like to define an area of ​​radio coverage.

[0041] The wireless communication network 1 further comprises a first radio network node 13 connected intermediate the network node 12 and the UE 10, which relays data packets between the network node 13 and the UE 10. The first radio network node 13 may be an IAB node, such as an IAB donor, such as an access node, an antenna unit, e.g. a radio unit of a radio base station, such as a gNodeB (gNB), an evolved NodeB (eNB, eNodeB), a Node B, a base transceiver station, a radio remote unit, an access point base station, a base station router, a wireless local area network (WLAN) access point or access point station (AP STA), a transmission arrangement of a radio base station, a standalone access point, or any other network unit or node capable of communicating with UEs in an area served by the radio network node, e.g. depending on the first radio access technology and terminology used. It is noted that the service area may be indicated as a cell, beam, beam group or the like to define an area of ​​radio coverage.

[0042] The wireless communication network further comprises a second radio network node 14 connected intermediate the first radio network node 13 and the UE 10, which relays data packets between the first radio network node 13 and the UE 10. The second radio network node 14 may be directly connected to the UE 10 and may be an egress point. The second radio network node 14 may be an IAB node, e.g. a radio remote unit (RRU) of an access node, e.g. an antenna unit, e.g. a radio unit of a radio base station, e.g. a gNodeB (gNB), an evolved NodeB (eNB, eNodeB), a Node B, a base transceiver station, a radio remote unit, an access point base station, a base station router, a wireless local area network (WLAN) access point or access point station (AP STA), a transmission arrangement of a radio base station, a standalone access point, or any other network unit or node capable of communicating with wireless devices in an area served by the radio network node, e.g. depending on the first radio access technology and terminology used. It should be noted that a service area may be denoted as a cell, beam, beam group or the like to define an area of ​​radio coverage. The second radio network node 14 is an example of a source radio network node 140 that handles one or more UEs, such as an IAB-MT or the like.

[0043] The wireless communication network further comprises a third radio network node 15 connected intermediate the network node 12 and the UE 10. The third radio network node 15 may be an egress point. The third radio network node 15 may be an IAB node, e.g. a radio remote unit (RRU) of an access node, an antenna unit, e.g. a radio unit of a radio base station such as a gNodeB (gNB), an evolved NodeB (eNB, eNodeB), a NodeB, a base transceiver station, a radio remote unit, an access point base station, a base station router, a wireless local area network (WLAN) access point or access point station (AP STA), a transmission arrangement of a radio base station, a standalone access point, or any other network unit or node capable of communicating with wireless devices in an area served by the dependent radio network node. The third radio network node 15 is an example of a target radio network node 150 that handles handover or cell selection of one or more UEs, e.g. an IAB-MT or similar.

[0044] The embodiments herein disclose a solution in which any network node involved in handover or cell selection of the UE 10, for example during communication, sends a message including one or more first UP indications indicating whether UP communication should be set up for the UE. The message including the first UP indication may be a message used in handover resource allocation and initial context setup S1AP procedure, a message used in handover preparation and handover resource allocation NGAP procedure, a message used in handover preparation, SeNB addition preparation, UE context retrieval and SgNB addition preparation X2AP procedure, and / or a message used in handover preparation and S-NG-RAN node addition preparation XnAP procedure.

[0045] As mentioned above, even though user plane establishment for IAB-MT / UE is optional, information elements (IEs) related to user plane establishment cannot be omitted from messages used to enable IAB-MT operation, since these IEs are mandatory due to the reuse of legacy messages. The first solution proposed herein introduces a new IE, namely a first UP indication, such as an IE called UP to be Setup, which will indicate whether mandatory IEs for UP setup should be ignored. This means that UP setup related IEs are still included in the message, but the receiver of these IEs should ignore these IEs and will not take any other action regarding UP setup. The first UP indication can be an indication of user plane setup or not, or an indication of avoiding user plane setup.

[0046] The new UP setup schedule IE, i.e., the first UP indication, may be mandatory or optional since the IE is added in a message where the IEs for UP setup are mandatory. If the new IE is mandatory and if the UP is to be set up for IAB-MT, the value of the new IE is set to 'true', otherwise the value of the new IE is set to 'false'. If the new IE is optional, it may be absent if the UP is set up and may be present with value 'false' if the UP is not to be set up for IAB-MT.

[0047] The message carrying the first UP indication may be one or more of a message used in a handover resource allocation and initial context setup S1AP procedure, a message used in a handover preparation and handover resource allocation NGAP procedure, a message used in a handover preparation, SeNB addition preparation, UE context retrieval and SgNB addition preparation X2AP procedure, and / or a message used in a handover preparation and S-NG-RAN node addition preparation XnAP procedure.

[0048] Assuming that the IAB-MT is an operator-owned device deployed and operating in an operator-owned network, the operator may reserve / use a special identification, i.e., a first UP indication, for a user plane setup parameter, e.g., PDU Session ID, E-UTRAN Radio Access Bearer (E-RAB) ID or DRB ID, such as a value not in the range specified by 3GPP, and thus a receiver of a message containing such a special identification will not set up a user plane, i.e., the receiver will simply ignore information related to user plane resources. In a subcase of the second solution, the operator may use only a special identification for the first parameter of the user plane setup, i.e., the first parameter to be decoded by the receiver, and thus, when the receiver (of the message) finds that special value, which is an example of a first UP indication for the first parameter, the receiver will ignore the rest of the user plane setup parameters regardless of their values. Receiver in this specification means the target radio network node.

[0049] Solution 1 is illustrated with respect to a non-limiting example of a Handover Request XnAP message (used in the Handover Preparation XnAP procedure), as shown below (new parts are underlined):

[0050] 9.1.1.1 Handover Request This message is sent by the source NG-RAN node to the target NG-RAN node to request the preparation of resources for the handover.

[0051] Direction: Source NG-RAN node → Target NG-RAN node. TIFF0007591585000003.tif255170TIFF0007591585000004.tif65170

[0052] Solution 2 is illustrated with respect to a non-limiting example of a Handover Request XnAP message (used in the Handover Preparation XnAP procedure), as shown below, by using the reserved / dedicated PDU Session ID value (underlined in 9.2.1.1 PDU Session Resource Setup Schedule List (see below)) as the first UP indication to indicate that the PDU Session Resource Setup Schedule List shall be ignored by the target.

[0053] 9.2.1.1 PDU Session Resource Setup Schedule This IE contains PDU session resource related information used in UE context transfer between NG-RAN nodes. TIFF0007591585000005.tif149170TIFF0007591585000006.tif15170

[0054] FIG. 3 is a combined signaling scheme and flow chart illustrating some embodiments of the present disclosure, where the UE is exemplified as an IAB-MT or an IAB-UE, and the radio network nodes 14 and 15 are exemplified as eNodeBs and / or gNBs.

[0055] Action 301. A second radio network node 14, which is an example of a source radio network node 140, may decide to perform a handover of the UE 10 to a third radio network node 15, which is an example of a target radio network node 150, for example, based on a measurement report from the UE 10 or the like.

[0056] Action 302. According to an embodiment herein, the second radio network node 14 sends to the third radio network node 15 a message related to handover or cell selection for the UE 10. The message includes a first UP indication, the first UP indication indicating whether or not UP communication is to be used, i.e., the first UP indication indicates whether or not UP communication for the UE 10 should be set up.

[0057] Action 303. The third radio network node 15 receives the message and performs connection setup based on the first UP indication, e.g., avoids setting up a UP connection if the first UP indication indicates not to use UP communication. This may be beneficial when the UE 10 is an IAB-MT and the message is a legacy message reused for IAB-MT, for which the presence of information elements (IEs) related to user plane establishment is mandatory.

[0058] Next, method actions performed by a source radio network node 140, such as an IAB node, e.g., a second radio network node 14, for handling communication and / or connection setup in a wireless communication network 1 according to an embodiment herein will be described with reference to the flowchart shown in Fig. 4. The wireless communication network 1 may comprise a first radio network node 13, a second radio network node 14 and / or a third radio network node 15 that relay data packets between the network node 12 and the UE 10. The first radio network node 13 may be an intermediate network node between the source radio network node 140 and the network node 12. The source radio network node 140 is adapted to relay data packets between the first radio network node 13 and the UE 10 in the wireless communication network.

[0059] Action 401. The source radio network node 140 may receive a measurement report from a UE and / or another radio network node. Thus, the source radio network node 140 may obtain a cell indication from the UE 10 and / or another radio network node, which indicates a handover or cell selection (secondary cell addition) of the UE 10.

[0060] Action 402. The source radio network node 140 may decide to handover the UE 10 to a target radio network node and / or add a secondary cell for the UE based on the cell indication. The source radio network node 140 may decide to handover the UE 10 to a different radio network node, such as the third radio network node 15, based on, for example, the measurement report(s). Alternatively or additionally, the source radio network node 140 may decide to add a secondary cell for the UE 10 based on, for example, the measurement report.

[0061] Action 403. The source radio network node 140, such as the second radio network node 14, sends a message related to cell selection and / or handover for the UE to the target radio network node 150, the message including a first UP indication. The first UP indication is an indication of whether to set up user plane communication for the UE. The target radio network node 150 may comprise the third radio network node 15, the first radio network node 13, and / or an intermediate radio network node. Thus, the source radio network node 140 may send a message including a first UP indication to a radio network node, such as the network node 12, the first 13 and / or the third radio network node 15, which are examples of a target radio network node, the first UP indication may be an indication of whether to set up user plane communication or not, or an indication of avoiding user plane setup. The message may be a message in the Handover Resource Allocation and Initial Context Setup S1 application protocol procedure, a message used in the Handover Preparation and Handover Resource Allocation NG application protocol procedure, a message used in the Handover Preparation, Secondary Node B (NB) Addition Preparation, Retrieve UE Context and secondary gNB Addition Preparation X2 application protocol procedure, and / or a message used in the Handover Preparation and Secondary NG Radio Access Network Node Addition Preparation Xn application protocol procedure. The first UP indication may include one or more of the following values ​​not in the range specified by 3GPP: PDU Session ID, E-RAB ID, DRB ID, and thus a receiver of a message including such a value or identification will not set up user plane communication.The first UP indication may include a first parameter of the UP setup to be decoded by a receiver of the message, which may then ignore the rest of the UP setup parameters regardless of their values ​​when the first parameter indicates that UP communication should not be set up. The message may be a handover request XnAP message, and the first UP indication may include a PDU session ID value to indicate that the PDU session resource setup schedule list shall be ignored by the target radio network node. The message may be a handover request XnAP message, and the first UP indication may include an information element to indicate that the PDU session resource setup schedule list shall be ignored or not ignored by the target radio network node.

[0062] Action 404. The source radio network node 140 may further receive a confirmation from the target radio network node 150 that it received the message.

[0063] Method actions performed by a target radio network node 150, such as an IAB node, e.g., a third radio network node 15, for handling or managing communication and / or connection setup in a wireless communication network 1 according to embodiments herein will now be described with reference to the flowchart shown in Fig. 5. The wireless communication network 1 comprises a source radio network node 140 that relays data packets between a first radio network node 13 and a UE 10. Thus, the wireless communication network 1 may comprise a first radio network node 13, a second radio network node 14 and / or a third radio network node 15 that relay data packets between a central network node, such as the network node 12, and the UE. The first radio network node 13 may be an intermediate network node between the second radio network node 14 and the central network node. The target radio network node 150 may comprise an IAB donor node, or an intermediate radio network node.

[0064] Action 501. The target radio network node 150 receives a message related to cell selection or handover for the UE 10 from the source radio network node 140 or the first radio network node 13. The message includes a first UP indication, which is an indication of whether to set up user plane communication for the UE. The first UP indication may be an indication of avoiding setting up an UP connection, for example, an indication of avoiding user plane setup. The message may be a message in a handover resource allocation and initial context setup S1 application protocol procedure, a message used in a handover preparation and handover resource allocation NG application protocol procedure, a message used in a handover preparation, a secondary Node B (NB) addition preparation, a UE context retrieval and secondary gNB addition preparation X2 application protocol procedure, and / or a message used in a handover preparation and a secondary NG radio access network node addition preparation Xn application protocol procedure. The first UP indication may include one or more of the following values ​​not in the range specified by 3GPP: PDU Session ID, E-RAB ID, DRB ID, such that a target radio network node receiving a message including such values ​​or identities will not set up user plane communication. The first UP indication may include a first parameter of user plane setup to be decoded by the target radio network node receiving the message, and the target radio network node will ignore the rest of the user plane setup parameters regardless of their remaining values ​​when the first parameter indicates that UP communication should not be set up. The received message may be a handover request XnAP message, and the first UP indication may include a PDU Session ID value to indicate that the PDU session resource setup schedule list shall be ignored by the target radio network node.The message may be a handover request XnAP message, and the first UP instruction may include an information element to indicate that the PDU session resource setup schedule list shall be ignored or not ignored by the target radio network node.

[0065] Action 502. The target radio network node 150 performs a connection setup for the UE 10 based on the first UP indication, e.g., will not set up user plane communication. For example, the target radio network node 150 may not set up user plane communication by ignoring information related to user plane resources.

[0066] The solutions described herein may be implemented in NR unlicensed spectrum, but are not limited to NR unlicensed spectrum (NR-U) scenarios. The embodiments are also applicable to other unlicensed operation scenarios, such as LTE Licensed Assisted Access (LAA) / Enhanced LAA / Further Enhanced LAA or WiFi.

[0067] 6 is a block diagram illustrating source radio network nodes in two embodiments for handling communication of a UE 10 in a wireless communication network 1 according to embodiments herein. The source radio network node 140 is adapted to relay data packets between a first radio network node 13 in the wireless communication network 1 and the UE 10.

[0068] The source radio network node 140 may comprise processing circuitry 601, eg, one or more processors, configured to perform the methods herein.

[0069] The source radio network node 140 may comprise a transmitting unit 602, e.g., a transmitter or transceiver. The source radio network node 140, the processing circuit 601, and / or the transmitting unit 602 are configured to transmit a message related to cell selection and / or handover for the UE 10 to the target radio network node 150, the message including a first UP indication. The first UP indication is an indication of whether to set up user plane communication for the UE 10. Thus, the source radio network node 140 may comprise a third radio network node 15, a first radio network node 13, or an intermediate radio network node. The messages may be messages in the Handover Resource Allocation and Initial Context Setup S1 application protocol procedure, messages used in the Handover Preparation and Handover Resource Allocation NG application protocol procedure, messages used in the Handover Preparation, Secondary Node B (NB) Addition Preparation, UE Context Retrieval and Secondary gNB Addition Preparation X2 application protocol procedure, and / or messages used in the Handover Preparation and Secondary NG Radio Access Network Node Addition Preparation Xn application protocol procedure. The first user plane indication may include one or more of the following values ​​that are not in the range specified by 3GPP: PDU Session ID, E-RAB ID, DRB ID, and thus a receiver of a message including such a value or identification will not set up user plane communication. The first UP indication may include a first parameter of user plane setup to be decoded by a receiver of the message, and the receiver will ignore the rest of the user plane setup parameters regardless of their values ​​when the first parameter indicates that UP communication should not be set up.The message may be a handover request XnAP message and the first user plane indication may include a PDU session ID value to indicate that the PDU session resource setup schedule list shall be ignored by the target radio network node. The message may be a handover request XnAP message and the first UP indication may include an information element to indicate that the PDU session resource setup schedule list shall be ignored or not ignored by the target radio network node 150.

[0070] The source radio network node 140 may comprise a receiving unit 603, for example a receiver or transceiver. The source radio network node 140, the processing circuit 601, and / or the receiving unit 603 may be configured to receive measurement reports from the UE 10.

[0071] The source radio network node 140 may comprise a determining unit 604. The source radio network node 140, the processing circuit 601, and / or the determining unit 604 may be configured to determine to hand over the UE 10 to a target radio network node 150, e.g., an IAB node, and / or to add a secondary cell for the UE 10 based on the cell indication, e.g., based on the received report.

[0072] The source radio network node 140 further comprises a memory 605. The memory 605 comprises one or more units to be used for storing data, such as measurement reports, radio network node IDs, first UP indications, and applications, and the like, for implementing the methods disclosed herein when executed. Furthermore, the source radio network node 140 may comprise a communication interface 608, such as comprising a transmitter, a receiver and / or a transceiver.

[0073] The methods according to the embodiments described herein for the source radio network node 140 may be implemented by, for example, a computer program product 606 or a computer program comprising instructions, i.e., software code portions, that when executed on at least one processor cause the at least one processor to perform actions described herein performed by the source radio network node 140. The computer program product 606 may be stored on a computer readable storage medium 607, for example, a disk, a Universal Serial Bus (USB) stick, or the like. The computer readable storage medium 607 having stored thereon the computer program product may comprise instructions that when executed on at least one processor cause the at least one processor to perform actions described herein performed by the source radio network node 140. In some embodiments, the computer readable storage medium may be a transitory or non-transitory computer readable storage medium. Accordingly, embodiments herein may disclose a source radio network node 140 for handling communications in a wireless communication network, the source radio network node 140 comprising a processing circuit 601 and a memory 605, the memory 605 comprising instructions executable by the processing circuit 601, such that the source radio network node 140 is operable to perform any of the methods herein.

[0074] 7 is a block diagram illustrating a target radio network node 150, such as a first radio network node 13, a second radio network node 14, and a third radio network node 15, in two embodiments, such as a relay node and / or an IAB node, for handling data packets in a wireless communication network 1 or for handling communication of a UE 10 according to an embodiment herein. The wireless communication network 1 comprises a source radio network node 140 that relays data packets between the first radio network node 13 and the UE 10. The target radio network node 150 may comprise the first radio network node 13, such as an IAB donor node, or an intermediate radio network node.

[0075] The target radio network node 150 may comprise processing circuitry 701, eg, one or more processors, configured to perform the methods herein.

[0076] The target radio network node 150 may comprise a receiving unit 702, e.g., a receiver or transceiver. The target radio network node 150, the processing circuit 701, and / or the receiving unit 702 are configured to receive a message related to cell selection or handover for the UE 10 from an intermediate radio network node, the source radio network node 140 or the first radio network node 13. The message includes a first UP indication, which is an indication of whether to set up user plane communications for the UE 10. For example, the target radio network node 140 may receive a message related to handover or cell selection of the UE from another radio network node, such as the network node 12, the second radio network node 14, the source radio network node 140, etc., and the message includes a first UP indication of avoiding user plane setup. The message may be a message in the Handover Resource Allocation and Initial Context Setup S1 application protocol procedure, a message used in the Handover Preparation and Handover Resource Allocation NG application protocol procedure, a message used in the Handover Preparation, Secondary Node B (NB) Addition Preparation, UE Context Retrieval and Secondary gNB Addition Preparation X2 application protocol procedure, and / or a message used in the Handover Preparation and Secondary NG Radio Access Network Node Addition Preparation Xn application protocol procedure. The first UP indication may include one or more of the following values ​​that are not in the ranges specified by 3GPP: Protocol Data Unit (PDU) Session ID, E-RAB ID, DRB ID, and thus a target radio network node receiving a message including such a value or identification will not set up user plane communications.The first UP indication may include a first parameter of a user plane setup to be decoded by the target radio network node receiving the message, and the target radio network node 150 is configured to ignore the rest of the user plane setup parameters regardless of their remaining values ​​when the first parameter indicates that UP communication should not be set up. The message may be a handover request XnAP message, and the first UP indication may include a PDU session ID value for indicating that the PDU session resource setup schedule list shall be ignored by the target radio network node. The message may be a handover request XnAP message, and the first UP indication may include an information element for indicating that the PDU session resource setup schedule list shall be ignored or not ignored by the target radio network node.

[0077] The target radio network node 150 may comprise a connection unit 704. The target radio network node 150, the processing circuit 701, and / or the connection unit 704 are configured to perform a setup of a connection for the UE 10 based on the first UP indication. The target radio network node 150, the processing circuit 701, and / or the connection unit 704 may be configured to perform the setup by not setting up a user plane connection when the first UP indication indicates not to set up UP communication. The target radio network node 150, the processing circuit 701, and / or the connection unit 704 may be configured to not set up user plane communication by ignoring information related to user plane resources.

[0078] The target radio network node 150 further comprises a memory 705. The memory 705 comprises one or more units to be used for storing data, such as a first UP instruction and an application for performing the methods disclosed herein when executed, and the like. Furthermore, the target radio network node 150 may comprise a communication interface 708, such as comprising a transmitter, a receiver and / or a transceiver, along with one or more antennas.

[0079] The methods according to the embodiments described herein for the target radio network node 150 are implemented by, for example, a computer program product 706 or a computer program comprising instructions, i.e., software code portions, that when executed on at least one processor cause the at least one processor to perform actions described herein to be performed by the target radio network node 150. The computer program product 706 may be stored on a computer readable storage medium 707, for example, a disk, a Universal Serial Bus (USB) stick, or the like. The computer readable storage medium 707 having the computer program product stored thereon may comprise instructions that when executed on at least one processor cause the at least one processor to perform actions described herein to be performed by the target radio network node 150. In some embodiments, the computer readable storage medium may be a transitory or non-transitory computer readable storage medium. Accordingly, embodiments herein may disclose a target radio network node 150 for handling communication or control signaling in a wireless communication network, the target radio network node 150 comprising processing circuitry and memory, the memory comprising instructions executable by the processing circuitry, such that the target radio network node 150 is operable to perform any of the methods herein.

[0080] In some embodiments, the more general term "radio network node" is used, and the term "radio network node" can correspond to any type of radio network node or any network node that communicates with a UE, such as a wireless device, and / or communicates with another radio network node. Examples of network nodes are Node B, MeNB, SeNB, network nodes belonging to a Master Cell Group (MCG) or a Secondary Cell Group (SCG), base station (BS), MSR radio node such as a Multi-Standard Radio (MSR) BS, eNode B, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlled relay, base transceiver station (BTS), access point (AP), transmission point, transmitting node, remote radio unit (RRU), remote radio head (RRH), node in a distributed antenna system (DAS), etc.

[0081] In some embodiments, the non-limiting term wireless device or user equipment (UE) is used, where the term wireless device or UE refers to any type of wireless device that communicates with a network node and / or another wireless device in a cellular or mobile communication system. Examples of UEs are IoT-enabled devices, target devices, D2D (device to device) UEs, proximity-enabled UEs (aka ProSe UEs), machine-type UEs or UEs capable of machine-to-machine (M2M) communication, tablets, mobile terminals, smartphones, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles, etc. In particular, in embodiments herein, a UE may be an IAB-MT portion of an IAB node.

[0082] The embodiments are applicable to any RAT or multi-RAT system in which a wireless device receives and / or transmits signals (e.g., data), such as New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications / Enhanced Data Rates for Global System for Mobile Communications Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), to name just a few possible implementations.

[0083] As will be readily understood by those familiar with communications design, the functional means or circuits may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, some or all of the various functions may be implemented together, such as in a single application specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Some of the functions may be implemented, for example, on a processor shared with other functional components of a wireless device or network node.

[0084] Alternatively, some of the functional elements of the described processing means may be provided by using dedicated hardware, and other functional elements may be provided with hardware for executing software, in association with appropriate software or firmware. Thus, the terms "processor" or "controller" as used herein do not refer solely to hardware capable of executing software, but may implicitly include, without limitation, digital signal processor (DSP) hardware and / or programs or application data. Other hardware, conventional and / or custom, may also be included. Designers of communication devices will appreciate the cost, performance, and maintenance tradeoffs inherent in these design choices.

[0085] OTT Figure 8 illustrates a communication network connected to a host computer via an intermediate network according to some embodiments. Referring to Figure 8, according to one embodiment, a communication system includes a communication network 3210, such as a 3GPP type cellular network, comprising an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 comprises a number of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points, which are examples of the above-mentioned radio network nodes 12, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215. A first UE 3291 located in the coverage area 3213c is configured to wirelessly connect to or be paged by the corresponding base station 3212c. A second UE 3292 in the coverage area 3213a can wirelessly connect to the corresponding base station 3212a. Although multiple UEs 3291, 3292, which are examples of wireless devices 10 described above, are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or only one UE connects to the corresponding base station 3212.

[0086] The communication network 3210 is itself connected to a host computer 3230, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 3230 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. The connections 3221 and 3222 between the communication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230, or may proceed via an optional intermediate network 3220. The intermediate network 3220 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and the intermediate network 3220 may be a backbone network or the Internet, if any, and in particular the intermediate network 3220 may comprise two or more sub-networks (not shown).

[0087] The communication system of FIG. 8 as a whole enables connectivity between the connected UEs 3291, 3292 and the host computer 3230. The connectivity may be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and / or signaling via the OTT connection 3250 using the access network 3211, the core network 3214, any intermediate networks 3220, and possible further infrastructure (not shown) as intermediaries. The OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 3212 may not be or need not be informed about the past routing of incoming downlink communications involving data originating from the host computer 3230 to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, the base station 3212 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 3291 and destined for the host computer 3230.

[0088] FIG. 9 illustrates a host computer communicating with user equipment via a base station over a partially wireless connection according to some embodiments.

[0089] Next, an exemplary implementation of the UE, base station and host computer described in the previous paragraph according to an embodiment will be described with reference to FIG. 9. In the communication system 3300, the host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 3300. The host computer 3310 further comprises a processing circuit 3318, which may have storage and / or processing capabilities. In particular, the processing circuit 3318 may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 3310 further comprises software 3311, which is stored in or accessible by the host computer 3310 and is executable by the processing circuit 3318. The software 3311 includes a host application 3312. The host application 3312 may be operable to provide services to a remote user, such as a UE 3330 connecting via an OTT connection 3350 that terminates at the UE 3330 and the host computer 3310. In providing services to a remote user, the host application 3312 may provide user data that is transmitted using the OTT connection 3350.

[0090] The communication system 3300 further includes a base station 3320 provided in the communication system, the base station 3320 comprising hardware 3325 enabling the base station 3320 to communicate with the host computer 3310 and the UE 3330. The hardware 3325 may include a communication interface 3326 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 3300, as well as a wireless interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in FIG. 9) served by the base station 3320. The communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 may be direct or alternatively the connection 3360 may pass through a core network (not shown in FIG. 9) of the communication system and / or one or more intermediate networks outside the communication system. In the illustrated embodiment, the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 3320 further has software 3321 stored internally or accessible via an external connection.

[0091] The communication system 3300 further includes the UE 3330 already mentioned. The hardware 3333 of the UE 3330 may include a wireless interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located. The hardware 3333 of the UE 3330 further includes a processing circuit 3338, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 3330 further includes software 3331 stored in or accessible by the UE 3330 and executable by the processing circuit 3338. The software 3331 includes a client application 3332. The client application 3332 may be operable to provide services to a human or non-human user via the UE 3330 with the support of the host computer 3310. At the host computer 3310, a running host application 3312 may communicate with a running client application 3332 via an OTT connection 3350 that terminates at the UE 3330 and the host computer 3310. In providing a service to a user, the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 may transfer both the request data and the user data. The client application 3332 may interact with the user to generate the user data that the client application 3332 provides.

[0092] It should be noted that the host computer 3310, base station 3320 and UE 3330 shown in Figure 9 may be similar or equivalent to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292, respectively, of Figure 8. That is, the inner workings of these entities may be as shown in Figure 9 and, separately, the surrounding network topology may be that of Figure 8.

[0093] 9, the OTT connection 3350 is depicted abstractly to show communication between the host computer 3310 and the UE 3330 via the base station 3320, without explicit reference to intermediary devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 3330 or from the service provider operating the host computer 3310, or both. The network infrastructure may also make decisions to dynamically change the routing while the OTT connection 3350 is active (e.g., based on load balancing considerations or reconfiguration of the network).

[0094] The wireless connection 3370 between the UE 3330 and the base station 3320 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 3330 using the OTT connection 3350 of which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments allow to perform handover or cell selection without UP communication. Thereby, handling or managing data communication, e.g., communication setup, can be performed efficiently, resulting in better responsiveness and battery time.

[0095] Measurement procedures may be provided for the purpose of monitoring data rates, latency and other factors that one or more embodiments improve upon. There may further be an optional network function for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to fluctuations in the measurement results. The measurement procedures and / or the network function for reconfiguring the OTT connection 3350 may be implemented in the software 3311 and hardware 3315 of the host computer 3310 or in the software 3331 and hardware 3333 of the UE 3330, or both. In an embodiment, sensors (not shown) may be deployed in or in association with the communication device through which the OTT connection 3350 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software 3311, 3331 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 3350 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 3320, and the reconfiguration may be unknown or imperceptible to the base station 3320. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 3310 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in the software 3311 and 3331 causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 3350 while the software 3311 and 3331 monitors propagation times, errors, etc.

[0096] FIG. 10 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments.

[0097] FIG. 10 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 8 and FIG. 9. For simplicity of the disclosure, only drawing references to FIG. 10 are included in this section. In step 3410, the host computer provides user data. In sub-step 3411 of step 3410 (which may be optional), the host computer provides the user data by executing a host application. In step 3420, the host computer initiates a transmission carrying the user data to the UE. In step 3430 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE, according to the teachings of the embodiments described throughout this disclosure. In step 3440 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0098] FIG. 11 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments.

[0099] FIG. 11 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 8 and FIG. 9. For simplicity of the disclosure, only drawing references to FIG. 11 are included in this section. In step 3510 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may go through a base station in accordance with the teachings of the embodiments described throughout this disclosure. In step 3530 (which may be optional), the UE receives the user data carried in the transmission.

[0100] FIG. 12 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments.

[0101] FIG. 12 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 8 and FIG. 9. For simplicity of the disclosure, only drawing reference to FIG. 12 is included in this section. In step 3610 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 3620, the UE provides user data. In sub-step 3621 (which may be optional) of step 3620, the UE provides the user data by executing a client application. In sub-step 3611 (which may be optional) of step 3610, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step 3630 (which may be optional). In method step 3640, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0102] FIG. 13 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments.

[0103] FIG. 13 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 8 and FIG. 9. For simplicity of the disclosure, only a drawing reference to FIG. 13 is included in this section. In step 3710 (which may be optional), the base station receives user data from the UE, according to the teachings of the embodiments described throughout this disclosure. In step 3720 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 3730 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0104] Any suitable steps, methods, features, functions, or benefits disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a corresponding function according to one or more embodiments of the present disclosure.

[0105] Modifications of the disclosed embodiments and other embodiments will occur to those skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. It is therefore to be understood that the embodiment(s) is not to be limited to the specific embodiment disclosed, and that modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0106] Abbreviation Description ACK (Acknowledgement) AUL Autonomous Uplink BLER Block Error Rate BWP Bandwidth Part CAPC Channel Access Priority Class CBG Code Block Group CCA Clear Channel Assessment CO Channel Occupancy COT Channel Occupancy Time CWS Contention Window Size DL Downlink ED Energy Detect eNB 4G base station gNB 5G base station HARQ Hybrid Automatic Repeat Request IS syncing LAA Licensed Assisted Access LBT Listen Before Talk MAC Media Access Control MCOT Maximum Channel Occupancy Time NACK Negative acknowledgment NDI New Data Indicator NR 3GPP-specified 5G radio access technology NR-U NR Unlicensed OOS Out of Sync PCell Primary Cell PCI Physical Cell Identification PDCCH Downlink Control Channel PDU Protocol Data Unit PHICH Physical Channel Hybrid Automatic Repeat Request Indication Channel PLMN Public Land Mobile Network PSCell Primary SCG cell PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QCI QoS Class Identifier QoS Quality of Service RAT Radio Access Technology RLF Radio Link Failure RLM Radio Link Monitoring RLC Radio Link Control RRC Radio Resource Control RS reference signal SCG Secondary Cell Group SDU Service Data Unit SMTC SSB-based measurement timing settings SpCell Special cell (PCell or PSCell) SPS Semi-persistent Scheduling TTI Transmission Time Interval UCI Uplink Control Information UE User Equipment UL Uplink

Claims

1. A method implemented by a source radio network node (140, 14) for handling communications in a wireless communication network, the source radio network node being adapted to relay data packets between a first radio network node and a user equipment (UE) in the wireless communication network, the method comprising: sending (403) to a target radio network node (150, 12, 13, 15) a message related to cell selection and / or handover for the UE, the message including a first user plane indication, the first user plane indication being an indication of whether or not to set up user plane communications for the UE. Including, 11. A method according to claim 10, wherein the first user plane indication includes a first parameter of a user plane setup to be decoded by a receiver of the message, the receiver being to ignore the rest of the user plane setup parameters regardless of their values ​​when the first parameter indicates that user plane communications should not be set up.

2. The method of claim 1 , wherein the target radio network node comprises a third radio network node, the first radio network node, or an intermediate radio network node.

3. 3. The method of claim 1 or 2, wherein the message is a message in a handover resource allocation and initial context setup S1 application protocol procedure, a message used in a handover preparation and handover resource allocation NG application protocol procedure, a message used in a handover preparation, secondary Node B (NB) addition preparation, UE context retrieval and secondary gNB addition preparation X2 application protocol procedure, and / or a message used in a handover preparation and secondary NG radio access network node addition preparation Xn application protocol procedure.

4. 4. The method of claim 1, wherein the first user plane indication comprises one or more of the following values ​​that are not in a range defined by 3GPP: a Protocol Data Unit (PDU) Session ID, an E-UTRAN Radio Access Bearer (E-RAB) ID, a Data Radio Bearer (DRB) ID, such that a receiver of the message containing said value or identification will not set up the user plane communication.

5. 5. The method of claim 1, wherein the message is a handover request XnAP message, and the first user plane indication includes a Protocol Data Unit (PDU) Session ID value to indicate that a PDU session resource setup schedule list shall be ignored by the target radio network node.

6. 6. The method according to claim 1, wherein the message is a handover request XnAP message, and the first user plane indication includes an information element for indicating that a Protocol Data Unit (PDU) session resource setup scheduled list shall be ignored or not ignored by the target radio network node.

7. - based on the cell indication, deciding (402) to handover the UE (10) to the target radio network node (150) and / or to add a secondary cell for the UE; The method of claim 1 , further comprising:

8. A method implemented by a target radio network node (150) for handling communications in a wireless communication network, the wireless communication network comprising a source radio network node (140, 14) relaying data packets between a first radio network node (12, 13) and a user equipment (UE), the method comprising: receiving (501) a message related to cell selection or handover for the UE from the source radio network node or the first radio network node, the message including a first user plane indication, the first user plane indication being an indication of whether or not to set up user plane communications for the UE; performing (502) a connection setup for the UE based on the first user plane indication; Including, 11. A method according to claim 10, wherein the first user plane indication comprises a first parameter of a user plane setup to be decoded by the target radio network node receiving the message, the target radio network node being to ignore the remainder of user plane setup parameters regardless of their remaining values ​​when the first parameter indicates that user plane communications should not be set up.

9. 10. The method of claim 8, wherein performing the setup includes causing the target radio network node to not set up the user plane communications.

10. 10. The method of claim 9, wherein the target radio network node ignores information related to user plane resources, thereby not setting up the user plane communication.

11. The method of claim 8 , wherein the target radio network node comprises an integrated access and radio access backhaul (IAB) donor node, or an intermediate radio network node.

12. 12. The method according to claim 8, wherein the message is a message in a handover resource allocation and initial context setup S1 application protocol procedure, a message used in a handover preparation and handover resource allocation NG application protocol procedure, a message used in a handover preparation, secondary Node B (NB) addition preparation, UE context retrieval and secondary gNB addition preparation X2 application protocol procedure, and / or a message used in a handover preparation and secondary NG radio access network node addition preparation Xn application protocol procedure.

13. 13. The method of any one of claims 8 to 12, wherein the first user plane indication comprises one or more of the following values ​​that are not in a range defined by 3GPP: a Protocol Data Unit (PDU) Session ID, an E-UTRAN Radio Access Bearer (E-RAB) ID, a Data Radio Bearer (DRB) ID, such that the target radio network node receiving the message including said value or identification will not set up the user plane communication.

14. 14. The method of claim 8, wherein the message is a handover request XnAP message, and the first user plane indication includes a Protocol Data Unit (PDU) Session ID value to indicate that a PDU session resource setup schedule list shall be ignored by the target radio network node.

15. 15. The method according to claim 8, wherein the message is a handover request XnAP message, and the first user plane indication includes an information element for indicating that a Protocol Data Unit (PDU) session resource setup schedule list shall be ignored or not ignored by the target radio network node.

16. A source radio network node (140, 14) for handling communications in a wireless communication network, the source radio network node being adapted to relay data packets between a first radio network node (12, 13) and a user equipment (UE) in the wireless communication network, the source radio network node comprising: sending to a target radio network node (150, 12, 13, 15) a message related to cell selection and / or handover for the UE, the message including a first user plane indication, the first user plane indication being an indication of whether or not to set up user plane communications for the UE. It is set to do The first user plane indication includes a first parameter of a user plane setup to be decoded by a receiver of the message, the receiver being to ignore the rest of the user plane setup parameters regardless of their values ​​when the first parameter indicates that user plane communications should not be set up.

17. A source radio network node (140, 14) according to claim 16, further configured to perform the steps according to any one of claims 2 to 7.

18. A target radio network node (150) for handling communications in a wireless communication network, the wireless communication network comprising a source radio network node relaying data packets between a first radio network node and a user equipment (UE), the target radio network node comprising: receiving a message related to cell selection or handover for the UE from the source radio network node or the first radio network node, the message including a first user plane indication, the first user plane indication being an indication of whether to set up user plane communications for the UE; performing a connection setup for the UE based on the first user plane indication; It is set to do a target radio network node (150) receiving the message, the first user plane indication including a first parameter of a user plane setup to be decoded by the target radio network node receiving the message, the target radio network node being to ignore the remainder of the user plane setup parameters regardless of their remaining values ​​when the first parameter indicates that user plane communications should not be set up.

19. The target radio network node (150) of claim 18, further configured to perform the steps of any one of claims 9 to 15.

Citation Information

Patent Citations

  • Mobile communication method and radio base station

    WO2009057684A1