WO2020259811A1 - Transfert intercellulaire assisté par liaison latérale - Google Patents

Transfert intercellulaire assisté par liaison latérale Download PDF

Info

Publication number
WO2020259811A1
WO2020259811A1 PCT/EP2019/066860 EP2019066860W WO2020259811A1 WO 2020259811 A1 WO2020259811 A1 WO 2020259811A1 EP 2019066860 W EP2019066860 W EP 2019066860W WO 2020259811 A1 WO2020259811 A1 WO 2020259811A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
signal
network node
relay
handover
Prior art date
Application number
PCT/EP2019/066860
Other languages
English (en)
Inventor
Lianghai JI
Nuno Manuel KIILERICH PRATAS
Benny Vejlgaard
Poul Olesen
Jakob Lindbjerg Buthler
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2019/066860 priority Critical patent/WO2020259811A1/fr
Publication of WO2020259811A1 publication Critical patent/WO2020259811A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/03—Reselecting a link using a direct mode connection
    • H04W36/033—Reselecting a link using a direct mode connection in pre-organised networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/087—Reselecting an access point between radio units of access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • Various example embodiments generally relate to the field of wireless communications.
  • some example embodiments relate to signaling and execution of a handover in a cellular communication network .
  • a client node such as a mobile phone
  • LTE long-term evolution
  • NR 5G new radio
  • a client node such as a mobile phone
  • LTE long-term evolution
  • NR 5G new radio
  • a client node may be handed over from one base station to another.
  • a client node may be enabled to communicate with a base station via another device, for example a client node operating as a sidelink.
  • an apparatus comprises at least one processor and at least one memory including computer program code, the at least one memory and the computer code configured to, with the at least one processor, cause the apparatus at least to receive a signal from a source network node; receive, from the source network node, a request to establish a sidelink connection to a relay node; establish the sidelink connection and receive the signal from the source network node and from the relay node; receive a request to perform a handover to a target network node; disconnect from the source network node and continue receiving the signal from the relay node; establish a connection to the target network node and receive the signal from the relay node and from the target network node; receive, from the target network node, a request to disconnect from the relay node; and
  • a method comprises receiving a signal from a source network node; receiving, from the source network node, a request to establish a sidelink connection to a relay node; establishing the sidelink connection and receiving the signal from the source network node and from the relay node; receiving a request to perform a handover to a target network node; disconnecting from the source network node and continuing to receive the signal from the relay node; establishing a connection to the target network node and receiving the signal from the relay node and from the target network node; receiving, from the target network node, a request to disconnect from the relay node; and disconnecting from the relay node and continuing to receive the signal from the target network node.
  • a computer program is configured, when executed by an apparatus, to cause the apparatus to receive a signal from a source network node; receive, from the source network node, a request to establish a sidelink connection to a relay node; establish the sidelink connection and receive the signal from the source network node and from the relay node; receive a request to perform a handover to a target network node; disconnect from the source network node and continue receiving the signal from the relay node; establish a connection to the target network node and receive the signal from the relay node and from the target network node; receive, from the target network node, a request to disconnect from the relay node; and disconnect from the relay node and continue receiving the signal from the target network node.
  • an apparatus comprises means for receiving a signal from a source network node; receiving, from the source network node, a request to establish a sidelink connection to a relay node; means for establishing the sidelink connection and means for receiving the signal from the source network node and from the relay node; means for receiving a request to perform a handover to a target network node; means for disconnecting from the source network node and means for continuing to receive the signal from the relay node; means for establishing a connection to the target network node and means for receiving the signal from the relay node and from the target network node; means for receiving, from the target network node, a request to disconnect from the relay node; and means for disconnecting from the relay node and means for continuing to receive the signal from the target network node .
  • an apparatus comprises at least one processor and at least one memory including computer program code, the at least one memory and the computer code configured to, with the at least one processor, cause the apparatus at least to transmit, to a client node, a request to establish a sidelink connection to a relay node; transmit a signal to the client node and transmit the signal to the relay node for forwarding the signal to the client node over the sidelink connection; transmit, to the client node, a request to perform a handover to a target network node; discontinue to transmit the signal to the client node and continue to transmit the signal to the relay node.
  • a method comprises transmitting, to a client node, a request to establish a sidelink connection to a relay node; transmitting a signal to the client node and transmitting the signal to the relay node for forwarding the signal to the client node over the sidelink connection; transmitting, to the client node, a request to perform a handover to a target network node; and discontinuing to transmit the signal to the client node and continuing to transmit the signal to the relay node.
  • a computer program is configured, when executed by an apparatus, to cause the apparatus to transmit, to a client node, a request to establish a sidelink connection to a relay node; transmit a signal to the client node and transmit the signal to the relay node for forwarding the signal to the client node over the sidelink connection; transmit, to the client node, a request to perform a handover to a target network node; discontinue to transmit the signal to the client node and continue to transmit the signal to the relay node.
  • an apparatus comprises means for transmitting, to a client node, a request to establish a sidelink connection to a relay node; means for transmitting a signal to the client node and means for transmitting the signal to the relay node for forwarding the signal to the client node over the sidelink connection; means for transmitting, to the client node, a request to perform a handover to a target network node; means for discontinuing to transmit the signal to the client node and means for continuing to transmit the signal to the relay node.
  • an apparatus comprises at least one processor and at least one memory including computer program code, the at least one memory and the computer code configured to, with the at least one processor, cause the apparatus at least to receive, at a target network node, a request to perform handover of a client node from a source network node to the target network node, wherein the request comprises an indication of a sidelink connection between the client node and a relay node; perform the handover and transmit a signal to the client node; and transmit, to the client node, a request to disconnect the sidelink connection.
  • a method comprises receiving, at a target network node, a request to perform handover of a client node from a source network node to the target network node, wherein the request comprises an indication of a sidelink connection between the client node and a relay node; performing the handover and transmitting a signal to the client node; and transmitting, to the client node, a request to disconnect the sidelink connection.
  • a computer program is configured, when executed by an apparatus, to cause the apparatus to receive, at a target network node, a request to perform handover of a client node from a source network node to the target network node, wherein the request comprises an indication of a sidelink connection between the client node and a relay node; perform the handover and transmit a signal to the client node; and transmit, to the client node, a request to disconnect the sidelink connection.
  • an apparatus comprises means for receiving, at a target network node, a request to perform handover of a client node from a source network node to the target network node, wherein the request comprises an indication of a sidelink connection between the client node and a relay node; means for performing the handover and transmitting a signal to the client node; and means for transmitting, to the client node, a request to disconnect the sidelink connection.
  • FIG. 1 illustrates an example of a network comprising network nodes and client nodes, according to an example embodiment.
  • FIG. 2 illustrates an example of an apparatus configured to operate according to a handover procedure, according to an example embodiment
  • FIG. 3 illustrates an example of a handover procedure involving a client node, a source network node, and a target network node, according to an example embodiment
  • FIG. 4A and FIG. 4B illustrate an example of a handover procedure involving a client node, a relay node, a source network node, and a target network node, according to an example embodiment
  • FIG. 5 illustrates an example of a first mode for performing a direct discovery between client nodes, according to an example embodiment
  • FIG. 6 illustrates an example of a second mode for performing a direct discovery between client nodes, according to an example embodiment
  • FIG. 7 illustrates an example of communication between a client node and a source network node before setting up a relay node, according to an example embodiment .
  • FIG. 8 illustrates an example of communication between a client node, a relay node, and a source network node, according to an example embodiment.
  • FIG. 9 illustrates an example of communication between a client node, a relay node, a source network node, and a target network node, according to an example embodiment .
  • FIG. 10 illustrates an example of communication between a client node and a target network node, according to an example embodiment.
  • FIG. 11 illustrates an example of a method for performing handover at a client node, according to an example embodiment.
  • FIG. 12 illustrates an example of a method for performing handover at a network node, according to an example embodiment.
  • FIG. 13 illustrates an example of a method for performing handover at a network node, according to an example embodiment.
  • a sidelink- assisted handover procedure from a source gNB to a target gNB is provided.
  • Data may be initially communicated over a direct radio link between a remote UE and a source gNB. Before handover another connection to the source gNB may be established via a relay UE . Data may be then communicated between the remote UE and the source gNB over these two separate links to increase communication reliability.
  • the handover procedure may further include disconnecting the direct connection to the source gNB and establishing another direct connection to a target gNB.
  • the UE may be temporarily served by the relay UE to avoid service interruption.
  • the UE may be served by the target gNB over the direct connection and the relay UE to increase communication reliability.
  • Example embodiments may be applied for example in industrial applications using remote controlled and semi-autonomous robots for movement, storage, and inspection of objects, such as for example drums containing chemicals.
  • objects such as for example drums containing chemicals.
  • communication to/from such objects may be difficult and unpredictable.
  • mobile relaying may be exploited, instead of deploying additional network nodes.
  • public safety organizations such as for example the police, the ambulance service, or the fire brigade, may request for ultra-reliable low latency communication (URLLC) to connect their equipment to the network.
  • URLLC ultra-reliable low latency communication
  • a mobile relay may be set up to enhance reliability of the communication, for example in areas with low network deployment density, for example on a highway or rural areas in general .
  • Various example embodiments may apply sidelink communication to assist a user equipment (UE) during a handover (HO) procedure, in order to avoid service interruption during the handover and increase communication reliability of the UE located at the cell border .
  • UE user equipment
  • HO handover
  • FIG. 1 illustrates an example embodiment of a network 100.
  • the network 100 may comprise one or more core network elements such as for example Access and Mobility Management Function (AMF) and/or User Plane Function (UPF) 140, one or more base stations, represented in the example of FIG. 1 by a source gNB 120 and a target gNB 130, which may be associated with coverage areas 121, 131, respectively.
  • An edge of a coverage area may be also referred to as a cell edge or a cell border.
  • the network 100 may further comprise a plurality of client nodes, which may be also referred to as a user nodes or user equipment (UE) .
  • the network may comprise a remote UE 110 and a relay UE 112.
  • the UEs 110, 112 may communicate with one or more of the base stations via wireless radio channel (s) .
  • the remote UE 110 may be located closer to the edge of coverage area 121 than the relay UE 112.
  • the relay UE 112 may therefore have better communication capability to the source gNB 120, for example because of a smaller path loss to source gNB 120.
  • the base stations may be configured to communicate with the core network elements over a communication interface, such as for example control plane or user plane interface NG-C/U.
  • Base stations may be also called radio access network (RAN) nodes. Functionality of a base station may be distributed between a central unit, for example a gNB-CU, and one or more distributed units, for example gNB-DUs.
  • RAN radio access network
  • Network elements AMF/UPF, gNB, gNB-CU, and gNB-DU may be generally referred to as network nodes or network devices. Although depicted as a single device, a network node may not be a stand-alone device, but for example a distributed computing system coupled to a remote radio head. For example, a cloud radio access network (cRAN) may be applied to split control of wireless functions to optimize performance and cost.
  • Network 100 may be configured for example in accordance with the 5th Generation digital cellular communication network, as defined by the 3rd Generation Partnership Project (3GPP) . In one example, network 100 may operate according to 3GPP 5G-NR (5G New Radio) . It is however appreciated that example embodiments presented herein are not limited to this example network and may be applied in any present or future wireless or wired communication networks, for example other type of cellular networks, short-range wireless networks, broadcast networks, or the like.
  • 3GPP 3rd Generation Partnership Project
  • 5G-NR 5G New Radio
  • central unit of a base station may comprise a physical or logical node and may include functions such as for example transfer of user data, mobility control, radio access network sharing, positioning, session management, or the like, except for functions that may be allocated to the distributed unit(s) .
  • the central unit may be connected to the one or more distributed units over a communication interface, for example an FI interface.
  • the one or more distributed units may be physical or logical nodes that may be configured to provide a subset of base station functions, depending on how the functions are split between the central unit and the distributed unit(s) .
  • the distributed unit(s) may be controlled by the central unit through the communication interface.
  • a base station may be connected to other radio access network nodes by another communication interface, for example an Xn interface. It is appreciated that network functionality described herein may be implemented at a gNB, or divided between a gNB-CU and a gNB-DU.
  • Various signaling information may be exchanged in network 100 to provide information related to transmission parameters and allocation of resources for data transmission.
  • Signaling information may be provided on various levels of a protocol stack.
  • Radio resource control may refer to provision of radio resource related control data.
  • An example of such control information is downlink control information (DCI), which may comprise a set of information configured for example to indicate transmission parameters and/or schedule transmissions on at least one downlink data channel, such for example a physical downlink shared channel (PDSCH) , or an uplink data channel, such as for example a physical uplink shared channel (PUSCH) .
  • Downlink control information may be provided in accordance with various formats and transmitted on a downlink control channel, such as for example a physical downlink control channel (PDCCH) .
  • Another example of signaling information is system information, which may be provided as one or more system information blocks (SIB) . System information blocks may be broadcast or targeted to a particular UE 110, 112.
  • SIB system information blocks
  • FIG. 2 illustrates an example of an apparatus
  • Apparatus 200 may comprise at least one processor 202.
  • the at least one processor may comprise, for example, one or more of various processing devices, such as for example a co-processor, a microprocessor, a controller, a digital signal processor (DSP) , a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , a microcontroller unit (MCU) , a hardware accelerator, a special-purpose computer chip, or the like.
  • various processing devices such as for example, a co-processor, a microprocessor, a controller, a digital signal processor (DSP) , a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , a microcontroller unit (MCU) , a hardware accelerator, a special-purpose computer chip, or the like
  • the apparatus may further comprise at least one memory 204.
  • the memory may be configured to store, for example, computer program code or the like, for example operating system software and application software.
  • the memory may comprise one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination thereof.
  • the memory may be embodied as magnetic storage devices (such as hard disk drives, floppy disks, magnetic tapes, etc.), optical magnetic storage devices, or semiconductor memories (such as mask ROM, PROM (programmable ROM) , EPROM (erasable PROM) , flash ROM, RAM (random access memory) , etc . ) .
  • Apparatus 200 may further comprise communication interface 208 configured to enable apparatus 200 to transmit and/or receive information, for example signaling information or data packets to/from other devices.
  • apparatus 200 may use communication interface 208 to transmit or receive signaling information and data in accordance with at least one cellular communication protocol.
  • the communication interface may be configured to provide at least one wireless radio connection, such as for example a 3GPP mobile broadband connection (e.g. 3G, 4G, 5G) .
  • the communication interface may be configured to provide also one or more other type of connections, for example a wireless local area network (WLAN) connection such as for example standardized by IEEE 802.11 series or Wi-Fi alliance; a short range wireless network connection such as for example a Bluetooth, NFC (near-field communication) , or RFID connection; a local wired connection such as for example a local area network (LAN) connection or a universal serial bus (USB) connection, or the like; or a wired Internet connection.
  • WLAN wireless local area network
  • a short range wireless network connection such as for example a Bluetooth, NFC (near-field communication) , or RFID connection
  • a local wired connection such as for example a local area network (LAN) connection or a universal serial bus (USB) connection, or the like
  • Communication interface 208 may comprise, or be coupled to, at least one antenna to transmit and/or receive radio frequency signals.
  • Apparatus 200 may further comprise a user interface 210 comprising an input device and/or an output device.
  • the input device may take various forms such a keyboard, a touch screen, or one or more embedded control buttons.
  • the output device may for example comprise a display, a speaker, a vibration motor, or the like.
  • some component and/or components of the apparatus such as for example the at least one processor and/or the memory, may be configured to implement this functionality.
  • this functionality may be implemented using program code 206 comprised, for example, in the memory 204.
  • the functionality described herein may be performed, at least in part, by one or more computer program product components such as software components.
  • the apparatus comprises a processor or processor circuitry, such as for example a microcontroller, configured by the program code when executed to execute the embodiments of the operations and functionality described.
  • the functionality described herein can be performed, at least in part, by one or more hardware logic components.
  • illustrative types of hardware logic components include Field-programmable Gate Arrays (FPGAs) , application-specific Integrated Circuits (ASICs) , application-specific Standard Products (ASSPs) , System- on-a-chip systems (SOCs) , Complex Programmable Logic Devices (CPLDs) , Graphics Processing Units (GPUs) .
  • FPGAs Field-programmable Gate Arrays
  • ASICs application-specific Integrated Circuits
  • ASSPs application-specific Standard Products
  • SOCs System- on-a-chip systems
  • CPLDs Complex Programmable Logic Devices
  • GPUs Graphics Processing Units
  • the apparatus comprises means for performing at least one method described herein.
  • the means comprises the at least one processor, the at least one memory including program code configured to, when executed by the at least one processor, cause the apparatus to perform the method.
  • Apparatus 200 may comprise for example a computing device such as for example a base station, a server, a mobile phone, a tablet computer, a laptop, an internet of things (IoT) device, or the like.
  • IoT devices include, but are not limited to, consumer electronics, wearables, sensors, and smart home appliances.
  • apparatus 200 may comprise a vehicle such as for example a car.
  • apparatus 200 is illustrated as a single device it is appreciated that, wherever applicable, functions of apparatus 200 may be distributed to a plurality of devices, for example to implement example embodiments as a cloud computing service .
  • FIG. 3 illustrates an example of a handover procedure involving a client node, represented in this example by UE 110, a source network node, represented in this example by source gNB 120, and a target network node, represented in this example by target gNB 130.
  • a handover may be performed when a UE 110 transits from coverage area 121 of source gNB 120 to coverage area 131 of the target gNB 130.
  • a handover procedure may comprise a handover preparation phase, a handover execution phase, and a handover completion phase, as will be further described below.
  • a source gNB may refer to a gNB that is initially serving a UE .
  • a target gNB may refer to a gNB that is initially not serving a UE, but which will take responsibility for serving the UE after handover.
  • a network node serving a UE may be referred to as a serving node.
  • the source gNB 120 may act as a serving network node.
  • the target gNB 130 may act as the serving network node.
  • UE 110 and source gNB 120 may transmit and/or receive data, for example as one or more data packets, to/from each other.
  • UE 110 may be configured to receive downlink signals from source gNB 120 and transmit uplink signals to source gNB 120, and vice versa.
  • UE 110 may be configured to measure strength and/or quality of signal (s) received from one or more gNBs and send at least one measurement report to source gNB 120, for example when the measured signal strength or quality associated with the source gNB 120 and/or other gNBs satisfies a condition.
  • UE 110 may be with one or more measurement events associated with different levels of signal strength and/or quality.
  • UE 110 may compare a reference signal received power (RSRP) of a signal received from source gNB 120 to a threshold. In response to determining that the RSRP is below or equal to the threshold, UE 110 may send a measurement report to source gNB 120 at 303.
  • the measurement report may comprise the value of the received signal strength and/or quality, for example RSRP, or an indication that the measured signal strength and/or quality is below or equal to the threshold.
  • the source gNB 120 may receive the measurement report. Based on the measurement report, the source gNB 120 may determine to initiate a handover at 305. Operation 305 may initiate the handover preparation phase, where the source gNB 120 derives the handover decision based on the measurement report received from the UE 110 and negotiates with the target gNB 130 to perform admission control. At 306, the source gNB 120 may send a handover request to the target gNB 130.
  • the target gNB 130 may perform admission control at 308, for example to determine whether it accepts UE 110 to be handed over to the target gNB 130.
  • the target gNB 130 may send a handover request acknowledgement to source gNB 120, for example to indicate that target gNB 130 accepts UE 110 to be handed over. Reception of the handover request acknowledgement message may complete the handover preparation phase.
  • the source gNB 120 may send a handover command to the UE 110 at 311.
  • Sending the handover command may initiate the handover execution phase, where the UE 110 may try to synchronize with the target gNB 130 and establish a connection to the target gNB 130.
  • the remote UE 110 may receive the handover command.
  • the source gNB 120 may determine to deliver data packet (s) buffered for transmission to UE 110 to the target gNB 130.
  • the source gNB 120 may send a sequential number (SN) status to the target gNB 130.
  • the source gNB 120 may send the buffered data packet (s) to the target gNB 130.
  • the target gNB 130 may receive the SN status and the data packet (s) 317. In response to receiving the SN status and the data packets, at 318 the target gNB 130 may buffer the data packets and assign them with appropriate sequence numbers for transmission to the UE 110.
  • the target gNB 130 and the UE 110 may transmit and receive synchronization information, respectively.
  • the synchronization information may comprise signalling information, such as for example one or more system information blocks, and synchronization signals, such as for example reference signal embedded in the transmitted or received waveform.
  • UE 110 may connect with the target gNB 130. This may be done for example based on transmitting a random access (RA) preamble.
  • the RA preamble may be transmitted in various formats and it may for example comprise a signature identifying the UE 110.
  • the RA preamble may be transmitted for example on a physical random access channel (PRACH) and it may be used to obtain uplink synchronization between UE 110 and target gNB 130 and to obtain resources for transmitting further signalling messages.
  • PRACH physical random access channel
  • the target gNB 130 may send a random access response at 323.
  • the target gNB 130 may further send an uplink allocation and a timing advance (TA) to UE 110.
  • the uplink allocation and the timing advance information may be included in the RA response or be sent as a separate signalling message.
  • the UE 110 may transmit an indication of a completion of radio resource reconfiguration, for example by an RRC reconfiguration complete message at 327 to target gNB 130.
  • the target gNB 130 may initiate communication with UE 110.
  • the target gNB 130 and UE 110 may transmit and/or receive signals to/from each other at 329 and 330.
  • the signals may for example comprise data packets.
  • the source gNB 120 and the target gNB 130 may determine to perform a path switch.
  • the path switch may comprise switching the transfer path of the UE's 110 data from the source gNB 120 to the target gNB 130.
  • the target gNB 130 may communicate with the core network directly to obtain data to be transmitted to UE 110.
  • a transfer path may refer to path to which the core network delivers the data to be sent to a particular UE, for example a path to the source gNB 120 or the target gNB 130.
  • the target gNB 130 may send a context release message to the source gNB.
  • the context release message may be associated with or identify remote UE 110.
  • the source gNB 120 may receive the context release message. In response to receiving the context release message, the source gNB 120 may release context of remote UE 110.
  • the handover procedure may include a service interruption period.
  • a service interruption period In the example of FIG. 3 there may be a service interruption for UE 110 between operations 315 and 328.
  • UP user-plane
  • This time duration may be referred to as the service interruption time in mobile networks.
  • the handover procedure of FIG. 3 enables the UE to be transferred from one gNB to another, but in some circumstances, it may be desired to avoid the long service interruption time. This may be the case for example in ultra-reliable low latency communication (URLLC) , where reliable communication with low latency is desired to support real-time systems and applications.
  • a long service interruption time may decrease reliability of the system and therefore it may be desired to decrease the service interruption time or to avoid it totally.
  • UE 110 may be located near the border of the coverage area 121 and it may therefore experience harsh radio conditions when communicating with source gNB 120.
  • the path loss from the source gNB 120 may be high and also the interference from neighbouring cell (s) may degrade reception performance. Therefore, communication reliability of UE 110 may be lower than that of other UEs located closer to the source gNB 120, for example relay UE 112.
  • UE 110 may for example experience radio link failures due to bad radio conditions. Therefore, the handover procedure may be improved, for example to meet quality of service (QoS) requirements for mission- critical services.
  • QoS quality of service
  • FIG. 4A and FIG. 4B illustrate an example of a handover procedure involving a client node, represented in this example by remote UE 110, a relay node, represented in this example by relay UE 112, a source network node, represented in this example by source gNB 120, and a target network node, represented in this example by target gNB 130, according to an example embodiment.
  • FIG. 4A illustrates an example of setting up a relay UE and the handover preparation phase, according to an example embodiment.
  • remote UE 110 and source gNB 120 may transmit and/or receive data similar to operations 301 and 302.
  • source gNB 120 and remote UE 110 may communicate over a single radio link 701, as illustrated in FIG. 7. It is however appreciated that a single radio link may or may not apply multiantenna techniques to provide a plurality of substantially independent communication paths between source gNB 120 and remote UE 110.
  • Remote UE 110 may be further configured to measure strength and/or quality of signal (s) , as described in connection with FIG. 3.
  • the source gNB 120 may be further configured to derive at least one condition for remote UE 110 for sending a measurement report.
  • the source gNB 120 may transmit the at least one condition for sending a measurement report to remote UE 110.
  • the one condition, or criterion may be included in a radio resource control message, for example in downlink control information, one or more system information blocks or RRC singaling.
  • the condition may be associated with triggering establishment of a sidelink connection between the remote UE 110 and a relay UE 112.
  • the source gNB 120 may select condition such that establishment of the sidelink connection is triggered before a handover procedure.
  • the condition may be also associated with one or more types of data communication, one or more services, or one or more network slices.
  • the condition for sending the measurement report may apply to UE 110 requesting one or more service types , for example an URLLC service.
  • a network slice may refer to one or a plurality of virtual network running on top of a single physical network. Network slicing enables partitioning the network into virtual network slices, where separate services or traffic types can run on different slices independently from one another. Thus, each slice may provide network capabilities that match the needs of a group of services or applications with similar requirements .
  • the condition may comprise a first threshold for a signal strength, a signal quality, or a reference signal strength for the signal received from the source network node.
  • a threshold for signal strength may comprise a received signal strength indicator (RSSI) or a reference signal received power (RSRP) , or in general any suitable measure for determining power level of a received signal.
  • RSSI received signal strength indicator
  • RSRP reference signal received power
  • a threshold for signal quality may for example comprise a threshold for a number or proportion of errors in a decoded data stream, or any other suitable signal quality indicator .
  • the first threshold may be higher than a second threshold associated with triggering the handover. This may ensure that establishment of the sidelink connection is triggered before the handover procedure. This provides the benefit of having sufficient radio links to both the relay UE 112 and the source gNB 120 before the handover.
  • the UE 100 may be configured with a plurality of measurement events associated with different conditions for sending a measurement report.
  • An example of a measurement event is an A2 measurement event, which may be associated with triggering a handover.
  • a specific measurement event or a type of measurement event may be allocated for triggering sidelink establishment, for example a sidelink establishment for assisting in handover.
  • the measurement event may be associated with an identifier that differentiates the new measurement event from other measurement events.
  • the first threshold may be provided as an offset to a second threshold associated with another measurement event.
  • the measurement event for triggering establishment of the sidelink connection for handover purposes may therefore comprise an offset value and a reference to another measurement event, for example a handover measurement event such as measurement event A2.
  • the threshold may be alternatively provided as a power or error level for the received signal or reference signal and expressed for example in dBm, bit error rate, packet error rate, or the like.
  • the measurement event may be associated with one or more particular services, one or more service types, or one or more network slices, for example an URLLC service.
  • An identifier of the service, an identifier of the service type, or an identifier of the network slice may be included in the conditions for sending the measurement report associated with the measurement event.
  • the remote UE 110 may receive the at least one condition for sending the measurement report.
  • the remote UE 110 may be configured to determine whether the condition is satisfied, and in response, send the measurement report to source gNB 120 at 405.
  • the UE 110 may be configured to compare signal strength or quality to a corresponding threshold received in 404. If a signal strength or quality is below the threshold, the UE 110 may send the measurement report.
  • the measurement report may be sent in response to determining that signal strength or quality decreases below the threshold for a signal which includes data of a particular type of data or service, for example URLLC.
  • the type of service, or data type may be preconfigured or received at 404.
  • a direct connection may for example refer to a direct radio link, which may be for example established as an air interface between antennas of two devices.
  • the source gNB 120 may receive the measurement report from the remote UE 110. Based on the received measurement report, at 407 the source gNB 120 may determine whether or not to trigger relay discovery. The source gNB 120 may for example compare the signal strength or quality indications included in the measurement report to the at least one condition sent at 403. Operation 407 may initiate a pre-handover phase, where a relay UE is set up to assist remote UE 110 during handover .
  • the source gNB 120 may determine to trigger relay discovery. For example, at 408 the source gNB 120 may transmit, to remote UE 110, a request to establish a sidelink connection to a relay UE, for example to relay UE 112, which may be in better radio conditions with respect to source gNB 120.
  • the request, or command, to establish the sidelink may be included in a radio resource control message, for example in downlink control information or RRC signaling.
  • the remote UE 110 may receive, for example over a direct connection to the source gNB 120, a request to establish a sidelink connection to a relay node. Upon receiving the request, the remote UE 110 may initiate a direct discovery process 410 to locate one or more other UEs that operate as relays to source gNB 120. The direct discovery may result in establishment of a sidelink connection between the remote UE 110 and the relay UE 112. The direct discovery process is further described in connection with FIG. 5 and FIG. 6. [0076] At 411, the relay UE 112 may send an indication of the established sidelink to source gNB 120. For example, the indication may be provided as a match report.
  • the indication may comprise information of pairing between the remote UE 110 and the relay UE 112.
  • the source gNB 120 may forward the indication of the paired UEs to the core network, for example to a mobility management entity (MME) or an access and mobility management function (AMF) .
  • MME mobility management entity
  • AMF access and mobility management function
  • the remote UE 110 and source gNB 120 may transmit or receive data over dual links.
  • a first link (cellular link) , may comprise a direct connection between the source gNB 120 and the remote UE 110.
  • a second link may use the sidelink connection to communicate data between the source gNB 120 and the remote UE 110 via the relay UE 112.
  • remote UE 110 may receive downlink signal (s) from the source gNB 120 and from the relay UE 112, respectively.
  • the remote UE 110 may also transmit uplink signal (s) to the source gNB 120 and the relay node 112.
  • the source gNB 120 may transmit downlink signal (s) to the remote UE 110 over the direct connection.
  • the source gNB 120 may further transmit the downlink signal to the relay UE 112 for forwarding the downlink signal to the remote UE 110 over the sidelink connection.
  • Source gNB 120 may also receive uplink signal (s) from the remote UE 110 directly or from the relay UE 112.
  • the signals may comprise data packets.
  • receiving the signal from the source gNB 120 and from the relay UE 112 may comprise receiving a plurality of data packets from the source gNB 120 and receiving the same data packets, or a subset thereof, from the relay UE 112. [0078] Due to simultaneous existence of the two links, a diversity gain can be obtained at the remote UE 110 and the source gNB 120.
  • the signal (s) from the source gNB 120 and the relay UE 112, or alternatively from the remote UE 110 and the relay UE 112, may be synchronized or collaborated such that a diversity gain may be obtained based on receiver signal processing, such as for example maximum ratio combining (MRC) .
  • the transmissions over the two links may form a single frequency network (SFN) such that they are seen by a receiver as one signal.
  • SFN single frequency network
  • Diversity gain may be also obtained based on the increased probability of correctly receiving a data packet from one of two separate links. Therefore, a diversity gain may be achieved even if the two signals were not synchronized. Therefore, the benefit of improved communication reliability is achieved .
  • FIG. 8 An example of dual link communication between source gNB 120 and remote UE 110 is illustrated in FIG. 8.
  • the remote UE 110 may be located closer to the edge of coverage area 121 or radio conditions may be otherwise degraded. This may have caused the signal level/quality to decrease below the first threshold and triggered establishment of sidelink connection 802.
  • the direct radio link 801 between the source gNB 120 and remote UE 110 may still be in place and dual link communication before the handover may be used to increase communication reliability.
  • the indirect link, comprising sidelink 802, via the relay UE 112 may be used to avoid service interruption during the handover execution phase.
  • the UE 110 may determine to send another measurement report. This may be for example in response to detecting signal strength or quality to decrease below a second threshold.
  • the second threshold may be for example associated with a second measurement event configured to trigger a handover.
  • the measurement event sent at 416 may be similar to the measurement report sent at 405, but a measurement report may also comprise an identifier of the associated measurement event.
  • the source gNB 120 may receive the measurement report from remote UE 110 and determine to initiate handover preparation phase.
  • the handover preparation phase may comprise the source gNB 120 making a handover decision at 418, sending a handover request at 419; the target gNB 130 receiving the handover request at 420, performing admission control at 421 and sending a handover request acknowledgement at 422; and the source gNB 120 receiving the handover request acknowledgement at 423, similar to operations 305 to 310.
  • the handover request sent at 419 may comprise an indication of the sidelink connection between the remote UE 110 node and the relay UE 112. The indication may for example comprise identifiers of the UEs and a type of the relationship.
  • the source gNB 120 may send a handover command or handover request to the remote UE 110, which the remote UE 110 may receive at 425.
  • Operations 424 and 425 may be similar to operations 311 and 312.
  • Sending or receiving the handover command may complete the handover preparation phase.
  • the handover command transmitted at 424 may comprise a request to perform handover to a target gNB 130.
  • the target gNB 130 may be identified in the handover command. Based on the identification the remote UE 110 may determine transmission and/or reception parameters to synchronize and access to the target gNB 130.
  • FIG. 4B illustrates an example of the handover execution phase and the handover completion phase, according to an example embodiment.
  • the procedure of FIG. 4B may be a continuation of FIG. 4A.
  • the remote UE 110 may detach or disconnect from source gNB 120. After receiving the handover command at 425, the remote UE 110 may stop listening to the source gNB 120 and switch its transceiver to the target gNB 130. Moreover, a timer (T304) may be started for monitoring the handover procedure. If the timer expires before the handover is successfully completed, it may trigger an RRC connection reestablishment procedure, or other actions. The source gNB 120 may not need to perform disconnection after sending the handover command, and it may move to operation 427 to start forwarding buffered packets that have not been acknowledged by the remote UE 110. Disconnecting from the source gNB 120 may comprise disconnecting the direct connection to the source gNB 120. At remote UE 110 this may be in response to receiving the handover command at 424.
  • T304 timer
  • the source gNB 120 may not need to perform disconnection after sending the handover command, and it may move to operation 427 to start forwarding buffered packets that have
  • the handover execution phase may comprise operations 427 to 432 at the source gNB 120 and the target gNB 130, similar to operations 313 to 318.
  • the handover execution may further comprise operations 433 to 446, as will be discussed later.
  • the source gNB 120 may discontinue transmitting the signal to the remote UE 110 over the direct connection.
  • the source gNB 120 may not need to detect the detachment.
  • the handover command sent by the source gNB 120 at 424 may trigger the remote UE 110 to detach from the source gNB 120. Therefore, as source gNB 120 triggered the detachment already, it may not need to detect the detachment.
  • the source gNB 120 may however continue to transmit the signal to the relay UE 112 at 433.
  • the relay UE 112 may forward the signal to remote UE 110.
  • remote UE 110 may continue to receive the signal from the relay UE 112 over the sidelink connection. This provides the benefit of avoiding service interruption during handover, even though the direct connection to the source gNB 120 has been disconnected .
  • the remote UE 110 may establish a connection to the target gNB 130 and receive the signal from the relay UE 112 node and from the target gNB 130. Establishing the connection to the target gNB 130 may comprise operations 435 to 444, similar to operations 319 to 328. At 445, the remote UE 110 may send a sequential number (SN) status indication to the target gNB 130, which the target gNB 130 may receive at 446.
  • the status indication may comprise a status of received packets, for example one or more sequence numbers received packets.
  • the status indication may be sent to target gNB 130 directly.
  • the status indication may be included in the RRC reconfiguration complete message, or it may be transmitted separately.
  • the status indication may be sent to the relay UE 112, which may forward it to target gNB 130 via source gNB 120 and/or other network elements.
  • the status indication may be sent before completion of the handover execution phase.
  • Handover execution phase may be completed after operation 446, for example in response to receiving the SN status indication .
  • the remote UE 110 may transmit or receive data over dual links at operations 447 and 449.
  • a first link (cellular link) may comprise a direct connection between the target gNB 130 and the remote UE 110.
  • a second link may use the sidelink connection to communicate data between the source gNB 120 and the remote UE 110 via the relay UE 112, which may forward data to source gNB 120, which may forward the data to the target gNB 130 or to the core network.
  • the remote UE 110 may receive downlink signal (s) from the target gNB 130 and from the relay UE 112.
  • the remote UE 110 may further transmit uplink signal (s) to the target gNB 130 and the relay node 112.
  • the target gNB 130 may transmit downlink signal (s) to the remote UE 110 or receive uplink signal (s) from the remote UE 110.
  • the source gNB 120 may transmit the downlink signal (s) to the relay UE 112 for forwarding the downlink signal (s) to the remote UE 110.
  • the source gNB 120 may still be responsible for serving the remote UE 110.
  • the source gNB 120 may receive data for the remote UE 110 from the core network.
  • the source gNB 120 may forward the data for the remote UE 110 to the target gNB 130 for transmission over the direct connection to the remote UE 110.
  • the signals may comprise data packets.
  • receiving the signal from the target gNB 130 and from the relay UE 112 may comprise receiving a plurality of data packets from the target gNB 130 and receiving the same data packets, or a subset thereof, from the relay UE 112. Due to simultaneous existence of the two links, a diversity gain can be obtained at the remote UE 110 and the network, for example a network node such as source gNB 120.
  • FIG. 9 illustrates and example of dual link operation between remote UE 110, target gNB 130, relay UE 112, and source gNB 120.
  • the remote UE 110 may be located closer to or even beyond the edge of coverage area 121.
  • Remote UE 110 may however be in radio conditions where establishing a direct radio link 901 to the target gNB 130 is feasible, that is, within coverage area 131 of the target gNB 130.
  • the sidelink connection 902 to the relay UE 112 may still be available. Therefore, remote UE 110 may communicate with the network, for example a network node such as target gNB 130, over the dual links 901, 902.
  • a diversity gain may be obtained at remote UE 110 and the network, for example a network node such as source gNB 120.
  • Path switch 451 may comprise switching the transfer path of the remote UE' s data from the source gNB 120 to the target gNB 130.
  • the target gNB 130 may communicate with the core network directly to obtain data to be transmitted to the remote UE 110.
  • the source gNB 120 is capable of serving the remote UE 110 via the relay UE 112 to maintain service continuity based on the data received from the core network.
  • the source gNB 120 may still serve the remote UE 110 based on data received from the target gNB 130, until the target gNB 130 discontinues delivery of the data to the source gNB 120.
  • the target gNB 130 may determine that relay UE 112 may be disconnected. This may be in response to completing the path switch. Determining whether the relay UE 112 can be disconnected may comprise determining whether radio conditions of the UE 110 are sufficient. For example, the target gNB 130 may determine whether signal strength or quality received from remote UE 110 is sufficient, for example exceeds a threshold. According to an example embodiment, the threshold may be equal to the first threshold that was used for determining whether to establish the sidelink at 407. According to an example embodiment, an offset may be applied on top of the threshold for triggering sidelink establishment. This may ensure that the threshold for disconnection is higher than the threshold for setting up the sidelink, for example in order to avoid or control alternating between establishing and disconnecting the sidelink.
  • the determination may comprise receiving feedback from the remote UE 110 regarding strength or quality of the signal received from target gNB 130.
  • Signal strength may be determined, at the remote UE 110 or the target gNB 130, for example based on at least one reference signal.
  • the target gNB 130 may continue delivering data targeted to UE 110 to the source gNB 120.
  • the target gNB 130 may send a command or request to the remote UE 110 to disconnect from the relay UE 112, for example in response to determining that the signal quality is sufficient.
  • the target gNB 130 may stop forwarding the data of the remote UE 110 to the source gNB 120.
  • the remote UE 110 may receive the request to disconnect from the relay UE 112.
  • the request may be received from the target gNB 130 over the direct connection.
  • the remote UE 110 may disconnect from the relay UE 112.
  • Disconnecting from the relay UE 112 may comprise disconnecting the sidelink connection.
  • the target gNB 130 may determine to release context of the remote UE 110.
  • the target gNB 130 may send a command or indication to the source gNB 120 to release context of the remote UE 110. It is noted that disconnecting from the relay UE 112 may also happen because of degraded radio conditions between the remote UE 110 and the relay UE 112.
  • the remote UE 110 may send an indication of the lost sidelink connection to the target gNB 130.
  • the target gNB 130 may operate similar to operations after an intentional disconnection from relay UE 112.
  • FIG. 10 illustrates communication between the remote UE 110 and the target gNB 130 after the handover and disconnecting from the relay UE 112.
  • the remote UE 110 may for example have moved closer to the target gNB 130 such that radio conditions between the remote UE 110 and the target gNB 130 are sufficient to communicate over the direct connection 1001, without the sidelink connection via relay UE 112.
  • FIG. 5 illustrates an example of a direct discovery operation 410, according to an example embodiment. This procedure may be exploited by the remote UE 110 to discover relay UE 112.
  • a discovery message such as for example an announcement message 501 may be sent by the remote UE 110.
  • the announcement message 501 may be a broadcast message.
  • the announcement message may be received by one or more other UEs monitoring an announcement channel, for example a broadcast announcement channel.
  • the relay UE 112 receiving the announcement message may determine whether it is capable of or configured to act as a relay to the remote UE 110.
  • a sidelink may be then established between the relay UE 112 and the remote UE 110.
  • a remote UE 110 may be configured to send the announcement message in response to receiving the request to establish a sidelink connection from the source gNB 120.
  • FIG. 6 illustrates an example of a direct discovery operation 410, according to an example embodiment.
  • a relay UE 112 may act as a discoverer and may send a discovery solicitation message 601.
  • the solicitation message may be sent to remote UE 110 and/or other UEs.
  • the remote UE 110 may determine whether the relay UE 112 is appropriate for serving the remote UE 110 as a relay UE and send a discovery response message back to the relay UE 112 at 602.
  • a sidelink may be then established between the relay UE 112 and the remote UE 110.
  • a remote UE 110 may be configured to initiate monitoring an announcement channel, for example a direct discovery channel, in response to receiving the request to establish a sidelink connection from the source gNB 120. Determining whether the relay UE 112 is appropriate for serving the remote UE 110 as a relay UE may be based on radio conditions of the sidelink, for example RSRP of the sidelink. Alternatively, or additionally, the determination may comprise determining whether the relay UE 112 is configured/enabled to relay a specified service, or a specified service at a specified quality, required by the remote UE 110. For example, some relay UE may not be capable or relaying some services with strict QoS requirements, but they may be able to forward the services with relaxed QoS requirements.
  • Various example embodiments disclose methods, computer programs and apparatuses for applying sidelink communication to enable a seamless handover, to avoid service interruption during handover, and to increase communication reliability during handover.
  • FIG. 11 illustrates an example of a method 1100 for performing handover at a client node, according to an example embodiment.
  • the method may comprise receiving a signal from a source network node.
  • the method may comprise receiving, for example from the source network node, a request to establish a sidelink connection to a relay node.
  • the method may comprise establishing the sidelink connection and receiving the signal from the source network node and from the relay node.
  • the method may comprise receiving a request to perform a handover to a target network node.
  • the method may comprise disconnecting from the source network node and continuing to receive the signal from the relay node.
  • the method may comprise establishing a connection to the target network node and receiving the signal from the relay node and from the target network node.
  • the method may comprise receiving, from the target network node, a request to disconnect from the relay node.
  • the method may comprise disconnecting from the relay node and continuing to receive the signal from the target network node.
  • FIG. 12 illustrates an example of a method 1200 for performing handover at a network node, according to an example embodiment.
  • the method may comprise transmitting, to a client node, a request to establish a sidelink connection to a relay node.
  • the method may comprise transmitting a signal to the client node and transmitting the signal to the relay node for forwarding the signal to the client node over the sidelink connection.
  • the method may comprise transmitting, to the client node, a request to perform a handover to a target network node.
  • the method may comprise discontinuing to transmit the signal to the client node and continuing to transmit the signal to the relay node.
  • FIG. 13 illustrates an example of a method 1300 for performing handover at a network node, according to an example embodiment.
  • the method may comprise receiving, at a target network node, a request to perform handover of a client node from a source network node to the target network node, wherein the request comprises an indication of a sidelink connection between the client node and a relay node.
  • the method may comprise performing the handover and transmitting a signal to the client node .
  • the method may comprise transmitting, to the client node, a request to disconnect the sidelink connection .
  • An apparatus for example a client node such as a remote UE 110 or a relay UE 112, or a network node such as source gNB 120 or target gNB 130 may be configured to perform or cause performance of any aspect of the method (s) described herein.
  • a computer program may comprise instructions for causing, when executed, an apparatus to perform any aspect of the method (s) described herein.
  • an apparatus may comprise means for performing any aspect of the method (s) described herein.
  • the means comprises at least one processor, and memory including program code, the at least one processor, and program code configured to, when executed by the at least one processor, cause performance of any aspect of the method ( s ) .
  • subjects may be referred to as 'first' or 'second' subjects, this does not necessarily indicate any order or importance of the subjects. Instead, such attributes may be used solely for the purpose of making a difference between subjects.
  • circuitry' may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable) : (i) a combination of analog and/or digital hardware circuit (s) with software/firmware and (ii) any portions of hardware processor (s) with software (including digital signal processor ( s )) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit (s) and or processor ( s ) , such as a microprocessor ( s ) or a portion of a microprocessor ( s ) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
  • This definition of circuitry applies to all uses of this term in this application, including in any claims.
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne, selon divers modes de réalisation donnés à titre d'exemple, une procédure de transfert intercellulaire assistée par liaison latérale à partir d'une source gNB vers une cible gNB. Des données peuvent être initialement communiquées sur une liaison radio directe entre un UE distant et une source gNB. Avant le transfert intercellulaire, une autre connexion à la source gNB peut être établie par l'intermédiaire d'un UE relais. Des données peuvent ensuite être communiquées entre l'UE distant et la source gNB sur ces deux liaisons séparées pour augmenter la fiabilité de communication. La procédure de transfert intercellulaire peut en outre comprendre la déconnexion de la connexion directe à la source gNB et l'établissement d'une autre connexion directe à une cible gNB. L'UE peut être temporairement desservi par l'UE relais pour éviter une interruption de service. En outre, après le transfert intercellulaire, l'UE peut être desservi par la cible gNB sur la connexion directe et l'UE relais pour augmenter la fiabilité de communication après le transfert intercellulaire. L'invention concerne également des appareils, des procédés et des programmes informatiques.
PCT/EP2019/066860 2019-06-25 2019-06-25 Transfert intercellulaire assisté par liaison latérale WO2020259811A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/066860 WO2020259811A1 (fr) 2019-06-25 2019-06-25 Transfert intercellulaire assisté par liaison latérale

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/066860 WO2020259811A1 (fr) 2019-06-25 2019-06-25 Transfert intercellulaire assisté par liaison latérale

Publications (1)

Publication Number Publication Date
WO2020259811A1 true WO2020259811A1 (fr) 2020-12-30

Family

ID=67106043

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2019/066860 WO2020259811A1 (fr) 2019-06-25 2019-06-25 Transfert intercellulaire assisté par liaison latérale

Country Status (1)

Country Link
WO (1) WO2020259811A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115150904A (zh) * 2021-03-30 2022-10-04 维沃移动通信有限公司 通信路径的切换方法、装置及终端
US11477831B2 (en) * 2019-08-19 2022-10-18 Lg Electronics Inc. Method for relaying unstructured traffic, and relay UE
CN115474255A (zh) * 2021-06-11 2022-12-13 维沃移动通信有限公司 基于旁链路的中继服务方法及装置、终端及网络侧设备
US20220418017A1 (en) * 2021-06-23 2022-12-29 Microsoft Technology Licensing, Llc Establishing multiple infrastructure connections to multiple access points via a single wireless network interface controller
US20230096255A1 (en) * 2021-09-27 2023-03-30 Qualcomm Incorporated Sidelink demodulation reference signal (dmrs) bundling trigger
WO2023140283A1 (fr) * 2022-01-21 2023-07-27 京セラ株式会社 Procédé de communication
WO2023137670A1 (fr) * 2022-01-20 2023-07-27 Lenovo (Beijing) Limited Procédés et appareils de gestion de liaisons et de mobilité pour un regroupement de liaisons montantes

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015018232A1 (fr) * 2013-08-05 2015-02-12 中兴通讯股份有限公司 Procédé et appareil de gestion de connexion de dispositif à dispositif et station de base
CN109691174A (zh) * 2016-09-29 2019-04-26 杜塞尔多夫华为技术有限公司 蜂窝网络中的侧行链路辅助切换

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015018232A1 (fr) * 2013-08-05 2015-02-12 中兴通讯股份有限公司 Procédé et appareil de gestion de connexion de dispositif à dispositif et station de base
CN109691174A (zh) * 2016-09-29 2019-04-26 杜塞尔多夫华为技术有限公司 蜂窝网络中的侧行链路辅助切换
US20190223066A1 (en) * 2016-09-29 2019-07-18 Huawei Technologies Duesseldorf Gmbh Sidelink-assisted handover in cellular networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ORSINO A ET AL: "Assisted Handover Based on Device-to-Device Communications in 3GPP LTE Systems", 2015 IEEE GLOBECOM WORKSHOPS (GC WKSHPS), IEEE, 6 December 2015 (2015-12-06), pages 1 - 6, XP032871084, DOI: 10.1109/GLOCOMW.2015.7414095 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11477831B2 (en) * 2019-08-19 2022-10-18 Lg Electronics Inc. Method for relaying unstructured traffic, and relay UE
US20230047009A1 (en) * 2019-08-19 2023-02-16 Lg Electronics Inc. Method for relaying unstructured traffic, and relay ue
US11903057B2 (en) * 2019-08-19 2024-02-13 Lg Electronics Inc. Method for relaying unstructured traffic, and relay UE
CN115150904A (zh) * 2021-03-30 2022-10-04 维沃移动通信有限公司 通信路径的切换方法、装置及终端
CN115150904B (zh) * 2021-03-30 2024-06-04 维沃移动通信有限公司 通信路径的切换方法、装置及终端
CN115474255A (zh) * 2021-06-11 2022-12-13 维沃移动通信有限公司 基于旁链路的中继服务方法及装置、终端及网络侧设备
US20220418017A1 (en) * 2021-06-23 2022-12-29 Microsoft Technology Licensing, Llc Establishing multiple infrastructure connections to multiple access points via a single wireless network interface controller
US11930548B2 (en) * 2021-06-23 2024-03-12 Microsoft Technology Licensing, Llc Establishing multiple infrastructure connections to multiple access points via a single wireless network interface controller
US20230096255A1 (en) * 2021-09-27 2023-03-30 Qualcomm Incorporated Sidelink demodulation reference signal (dmrs) bundling trigger
WO2023137670A1 (fr) * 2022-01-20 2023-07-27 Lenovo (Beijing) Limited Procédés et appareils de gestion de liaisons et de mobilité pour un regroupement de liaisons montantes
WO2023140283A1 (fr) * 2022-01-21 2023-07-27 京セラ株式会社 Procédé de communication

Similar Documents

Publication Publication Date Title
US20210120469A1 (en) Iab node switching method, iab node, and donor base station
WO2020259811A1 (fr) Transfert intercellulaire assisté par liaison latérale
US10178588B2 (en) Wireless device, network nodes and methods therein for handling a device-to-device (D2D) communication during handover in a wireless telecommunications network
EP2878157B1 (fr) Procédé destiné à être utilisé dans la communication de dispositif à dispositif et système de communication sans fil
US20220369181A1 (en) Conditional handover in a dual connectivity system
US20180220303A1 (en) Radio station, radio terminal, and method therefor
WO2017167287A1 (fr) Procédé et dispositif de configuration de ressources, et support d'informations
WO2019110869A1 (fr) Surveillance de liens avec auto-raccordement pour réseaux sans fil
US20210345211A1 (en) Timing advance for rach-less backhaul handover
JP6775665B2 (ja) プライマリセル変更のための方法、デバイス及びコンピュータプログラム
CN104969613A (zh) 用于设备到设备通信切换的无线电通信设备和蜂窝广域无线电基站
WO2014180367A1 (fr) Procédé, dispositif et support de stockage informatique pour connexion radio
CN108713330A (zh) 用于网络控制的切换和ue自主切换的混合方案
US11395206B2 (en) Measurement configuration
CN116134890A (zh) 双活动协议栈和连接/链路失败处理
US11146993B2 (en) Handover with postponed path switch
US11895542B2 (en) Reducing handover interruption with two transmitters and receivers
JP2024505137A (ja) 通信方法
US20220361071A1 (en) Conditional Handover for Wireless Networks
CN112291803B (zh) 一种通信方法、终端设备及计算机可读存储介质
US20230070083A1 (en) Enhanced measurement report for conditional handover procedure
EP4150960A1 (fr) Journalisation d'informations relatives à une exécution de transfert intercellulaire conditionnel à événements multiples pour des réseaux sans fil
KR20210019750A (ko) 무선통신 시스템에서 사이드링크 라디오 베어러를 구성하는 방법 및 장치
WO2023066230A1 (fr) Procédé et appareil utilisés dans un nœud de communication pour une communication sans fil
WO2018224545A1 (fr) Utilisation de mesures de transfert pour des réseaux sans fil sur la base d'une condition de blocage de signal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19734055

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19734055

Country of ref document: EP

Kind code of ref document: A1