[go: up one dir, main page]

WO2018082644A1 - Procédé et dispositif de transfert de relais, terminal, station de base - Google Patents

Procédé et dispositif de transfert de relais, terminal, station de base Download PDF

Info

Publication number
WO2018082644A1
WO2018082644A1 PCT/CN2017/109258 CN2017109258W WO2018082644A1 WO 2018082644 A1 WO2018082644 A1 WO 2018082644A1 CN 2017109258 W CN2017109258 W CN 2017109258W WO 2018082644 A1 WO2018082644 A1 WO 2018082644A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay device
base station
relay
remote
serving base
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/109258
Other languages
English (en)
Chinese (zh)
Inventor
陈琳
陈玉芹
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2018082644A1 publication Critical patent/WO2018082644A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link

Definitions

  • the present application relates to the field of communications, for example, to a relay transfer method and apparatus, a terminal, and a base station.
  • the communication technology between the common user equipment and the relay station may include, but is not limited to, D2D (Device-to-Device) technology, wireless fidelity WiFi technology, Bluetooth technology, and communication technology used in the operator network. .
  • Carrier network communication technologies include, but are not limited to, Long-Term Evolution (LTE) and its evolution technology/Worldwide Interoperability for Microwave Access (Wimax) and its evolution technology/Code Division Multiple Access (Code Division) Multiple Access, CDMA) and its evolution technology.
  • LTE Long-Term Evolution
  • Wimax Worldwide Interoperability for Microwave Access
  • CDMA Code Division Multiple Access
  • the application of D2D technology can reduce the burden of cellular networks, reduce the battery power consumption of user equipment, increase the data rate, and improve the robustness of the network infrastructure, which satisfies the requirements of the above high data rate services and proximity services. .
  • the D2D technology in the related art can work in a licensed band or an unlicensed band, and allows multiple D2D-enabled user equipments (D2D User Equipment, D2D UE) to have a network infrastructure or no network infrastructure.
  • D2D User Equipment D2D UE
  • Direct discovery/direct communication The application scenario of D2D can include the following three types:
  • FIG. 1 is a network architecture diagram of the remote UEs that are differently covered by the present disclosure, and the data is forwarded by the relay, as shown in FIG. 1;
  • the UE relay transmission in the weak/uncovered area allows the UE4 with poor signal quality to communicate with the network through the UE3 with network coverage nearby, which can help the operator to expand coverage and increase capacity;
  • the D2D technology generally includes a D2D discovery technology and a D2D communication technology, wherein the D2D discovery technology refers to a technology for determining/determining whether the first user equipment is adjacent to the second user equipment.
  • D2D user equipment can discover each other by transmitting or receiving discovery signals/information;
  • D2D communication technology refers to a technology in which some or all communication data between D2D user equipments can communicate directly without using a network infrastructure.
  • the UE3 can communicate with the network side using the LTE mode, and can also serve as a relay and out of coverage terminal (the UE4 in the illustration) ) Communication using D2D methods, including D2D Discovery and/or D2D communication. If the terminal UE4 that is out of coverage or has a poor signal transmits data to the base station through the terminal UE3 in the coverage, we call UE4 a remote user equipment (Remote UE), and UE3 is a relay user equipment (Relay UE).
  • Remote UE remote user equipment
  • Relay UE relay user equipment
  • UE6 may forward data packets between UE5 and UE7, UE6 may be referred to as a relay user, and UE5 and UE7 may Call it a remote user.
  • the related art business continuity requirements generated when a user moves between a relay station and a base station, a relay station, and a relay station cannot be solved in the related art.
  • the embodiments of the present disclosure provide a relay transfer method and device, a terminal, and a base station, so as to at least solve the problem that the terminal user is likely to generate service interruption when moving in the related art.
  • a relay transfer method comprising: at a remote user equipment UE, performing path relay switching from a first relay device to performing path relaying from a second relay device In case, the remote UE performs radio link control RLC reestablishment and packet data convergence protocol PDCP operation.
  • the first relay device or the second relay device includes one of: a UE for relaying; a base station for relaying; and a base station without relay capability.
  • the remote UE performs RLC reestablishment And PDCP data recovery operations.
  • the remote UE when the serving base station of the first relay device and the serving base station of the second relay device are different, performing, by the remote UE, RLC reestablishment and PDCP operations, the remote UE performs RLC reestablishment And PDCP reconstruction operations.
  • another relay transfer method including: at a remote user equipment UE, performing path relay switching from a first relay device to performing path relaying from a second relay device
  • the serving base station of the first relay device initiates a handover request message to the serving base station of the second relay device; and receives a handover response message fed back by the serving base station of the second relay device according to the handover request message.
  • the handover request message carries bypass link connection establishment information between the remote UE and the second relay device
  • the handover response message carries bypass link connection configuration information between the remote UE and the second relay device.
  • the method further includes: after the remote UE performs an RLC reestablishment and a PDCP operation, the first relay device performs data transmission of downlink DL data to the second relay device; and And/or, after the remote UE performs the RLC re-establishment and the PDCP operation, the first relay device performs data transmission of the uplink UL data to the second relay device.
  • the DL data includes: a PDCP packet data unit PDU that is not correctly received by the RLC layer between the first relay device and the remote UE; and/or the UL data includes: All PDCP PDUs that are locally buffered by the first relay device have been confirmed to be correctly received by the RLC layer.
  • the method further includes: the serving base station of the first relay device receives the second relay The capability information of the second relay device sent by the serving base station of the device, where the capability information includes one of the following: support DL user UP plane forwarding, support DL/UL UP plane forwarding, support DL control CP plane forwarding, Supports UL CP plane forwarding, supports DL/UL CP plane forwarding, supports DL CP/UP plane forwarding, supports UL CP/UP plane forwarding, and supports DL/UL CP/UP plane forwarding.
  • the capability information is carried in an X2 message, where the X2 message includes at least one of the following: an X2 setup request message, an X2 setup response message, an X2 setup failure message, and a base station configuration. New message, base station configuration update response message, base station configuration update failure message.
  • a relay transfer apparatus comprising: a determining module configured to determine that a remote user equipment UE performs path relay switching from the first relay device to by passing from the second The device performs path relaying; the execution module is configured to perform radio link control RLC reestablishment and packet data convergence protocol PDCP operations.
  • the executing module performs an RLC reestablishment and a PDCP data recovery operation.
  • the executing module when the serving base station of the first relay device and the serving base station of the second relay device are different, the executing module performs an RLC reestablishment and a PDCP reestablishing operation.
  • another relay transfer apparatus which is applied to a serving base station of a first relay device, and includes: a sending module configured to pass the first user equipment in the UE And performing a handover request message to the serving base station of the second relay device when the device performs path relay conversion to the path relay from the second relay device; the first receiving module is configured to receive the second A handover response message fed back by the serving base station of the relay device according to the handover request message.
  • the handover request message carries bypass link connection establishment information between the remote UE and the second relay device
  • the handover response message carries bypass link connection configuration information between the remote UE and the second relay device.
  • the device further includes: a first indication module, configured to: after the remote UE performs an RLC reestablishment and a PDCP operation, instruct the first relay device to perform downlink to the second relay device Data transmission of link DL data; and/or a second indication module configured to instruct the first relay device to the second relay device after the remote UE performs RLC re-establishment and PDCP operations Data transfer of uplink UL data is performed.
  • a first indication module configured to: after the remote UE performs an RLC reestablishment and a PDCP operation, instruct the first relay device to perform downlink to the second relay device Data transmission of link DL data
  • a second indication module configured to instruct the first relay device to the second relay device after the remote UE performs RLC re-establishment and PDCP operations Data transfer of uplink UL data is performed.
  • the apparatus further includes: a second receiving module, configured to receive, by the serving base station, send by the serving base station of the second relay device before the sending module initiates a handover request to the serving base station of the second relay device
  • the capability information of the second relay device includes one of the following: support DL user UP plane forwarding, support DL/UL UP plane forwarding, support DL control CP plane forwarding, support UL CP plane forwarding, Supports DL/UL CP plane forwarding, supports DL CP/UP plane forwarding, supports UL CP/UP plane forwarding, and supports DL/UL CP/UP plane forwarding.
  • the capability information is carried in an X2 message, where the X2 message includes the following One of the less: X2 setup request message, X2 setup response message, X2 setup failure message, base station configuration update message, base station configuration update response message, base station configuration update failure message.
  • a terminal comprising: a processor and a memory storing the processor-executable instructions, when the instructions are executed by the processor, performing an operation of: determining a remote user The device UE transitions from a path relay through the first relay device to a path relay from the second relay device; an execution module configured to perform a radio link control RLC reestablishment and a packet data convergence protocol PDCP operation.
  • the performing RLC re-establishment and PDCP operations by the processor includes: performing RLC re-establishment and PDCP data recovery operations.
  • the performing RLC re-establishment and PDCP operations by the processor includes: performing an RLC re-establishment and a PDCP re-establishment operation.
  • a base station comprising: a processor and a memory storing the processor-executable instructions, when the instructions are executed by the processor, performing an operation of: at a remote user
  • the device UE initiates a handover request message to the serving base station of the second relay device from the path relay transition by the first relay device to the path relay from the second relay device; receiving the second middle A handover response message fed back by the serving base station of the device according to the handover request message.
  • the processor further performs, after the serving base station of the first relay device initiates the handover request to the serving base station of the second relay device, the second base that is sent by the serving base station of the second relay device.
  • Capability information of the relay device includes one of the following: supporting downlink DL user UP plane forwarding, supporting DL/UL UP plane forwarding, supporting DL control CP plane forwarding, supporting UL CP plane forwarding, and supporting DL/UL CP plane forwarding, support for DL CP/UP plane forwarding, support for UL CP/UP plane forwarding, and support for DL/UL CP/UP plane forwarding.
  • the capability information is carried in an X2 message, where the X2 message includes at least one of the following: an X2 setup request message, an X2 setup response message, an X2 setup failure message, a base station configuration update message, and a base station configuration update response. Message, base station configuration update failure message.
  • the handover request message carries bypass link connection establishment information between the remote UE and the second relay device, and / or, the switch
  • the response message carries bypass link connection configuration information between the remote UE and the second relay device.
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • the radio link control RLC re-establishment and packet data convergence protocol PDCP operations are performed in the case where the far-end user equipment UE performs path relay switching through the first relay device to perform path relay from the second relay device.
  • the far-end UE performs radio link control RLC re-establishment and grouping in the case where the far-end user equipment UE performs path relay switching through the first relay device to perform path relaying from the second relay device.
  • the data aggregation protocol PDCP operation solves the problem that the terminal user is prone to business interruption when moving in the related technology, and realizes the business continuity transmission and reception in the mobile process, thereby achieving the effect of business continuity and improving the user experience.
  • 1 is a network architecture diagram of remotely-received remote UEs of the present disclosure by relaying data
  • FIG. 2 is a block diagram showing the hardware structure of a mobile terminal of a relay transfer method according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a relay transfer method in accordance with an embodiment of the present disclosure
  • FIG. 4 is a structural block diagram of a relay transfer device according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of two protocol stack architectures between remote UE-relay UE-eNBs in an embodiment of the present disclosure
  • FIG. 6 is a flowchart of a remote UE switching from a eNB to a relay UE using a protocol stack architecture in an embodiment of the present disclosure
  • FIG. 7 is a flowchart of a remote UE using a b protocol stack architecture to switch from an eNB to a relay UE in an embodiment of the present disclosure
  • FIG. 8 is a flowchart of a remote UE switching from a relay UE to an eNB using a protocol stack architecture in an embodiment of the present disclosure
  • FIG. 9 is a flowchart of a remote UE switching from a relay UE1 to a relay UE2 using a protocol stack architecture in an embodiment of the present disclosure
  • FIG. 10 is a flowchart of a remote UE that uses a protocol stack architecture to switch from eNB1 to a relay UE that belongs to eNB2 in an embodiment of the present disclosure
  • FIG. 11 is a flowchart of a remote UE using a protocol stack architecture switching from a relay UE under eNB1 to an eNB2 in an embodiment of the present disclosure
  • FIG. 12 is a flowchart of a remote UE using a protocol stack architecture in the present disclosure switching from relay UE1 under eNB1 to relay UE2 under eNB2;
  • FIG. 13 is a flowchart of informing the peer eNB 2 of the capability of the relay UE under its jurisdiction in the embodiment of the present disclosure.
  • FIG. 2 is a hardware structural block diagram of a mobile terminal of a relay transfer method according to an embodiment of the present disclosure.
  • the mobile terminal 20 may include one or more (only one shown) processor 202 (the processor 202 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA).
  • the mobile terminal 20 may also include more or fewer components than those shown in FIG. 2, or have a different configuration than that shown in FIG. 2.
  • the memory 204 can be configured as a software program and a module for storing application software, such as program instructions/modules corresponding to the relay transfer method in the embodiment of the present disclosure, and the processor 202 runs the software program and the module stored in the memory 204, thereby The above methods are implemented by performing various functional applications and data processing.
  • Memory 204 can include high speed random access memory and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • memory 204 may also include memory remotely located relative to processor 202, which may be connected to mobile terminal 20 over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Transmission device 206 is configured to receive or transmit data via a network.
  • the network instance described above may include a wireless network provided by a communication provider of the mobile terminal 20.
  • transmission device 206 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet.
  • NIC Network Interface Controller
  • the transmission device 206 can be a Radio Frequency (RF) module configured to communicate with the Internet wirelessly.
  • RF Radio Frequency
  • FIG. 3 is a flowchart of a relay transfer method according to an embodiment of the present disclosure, as shown in FIG. The process includes the following steps:
  • Step S302 The remote UE performs radio link control (Radio Link Control, in the case that the remote user equipment UE performs path relay conversion by the first relay device to perform path relay from the second relay device.
  • Radio Link Control Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • the far-end UE performs radio link control RLC re-establishment and grouping in the case where the far-end user equipment UE performs path relay conversion by the first relay device to perform path relaying from the second relay device.
  • the data aggregation protocol PDCP operation solves the problem that the terminal user is prone to business interruption when moving in the related technology, and realizes the business continuity transmission and reception in the mobile process, thereby achieving the effect of business continuity and improving the user experience.
  • the remote UE of the execution entity of the foregoing step may be a mobile phone, etc.
  • the base station may be an eNB, etc. But it is not limited to this.
  • the first relay device in this embodiment may be, but is not limited to, a relay UE, a base station for relay, and a base station that does not have a relay capability.
  • the second relay device may be, but is not limited to, a UE for relaying, that is, a relaying UE; a base station for relaying.
  • the serving base station of the relay device is itself, and the serving base station may be a base station having a relay capability or a base station not having a relay capability.
  • the remote UE performs RLC reconstruction and PDCP data recovery operations.
  • the serving base station of the first relay device and the serving base station of the second relay device are different, that is, the serving base stations of the first relay device and the second relay device are different base stations or the first relay.
  • the serving base station of the device is a base station other than the serving base station of the second relay device, the remote UE performs an RLC reestablishment and a PDCP reestablishment operation.
  • the method further includes: instructing the serving base station of the first relay device to initiate a handover request message to the serving base station of the second relay device.
  • the handover request message carries the bypass link connection establishment information between the remote UE and the second relay device; and receives a handover response message fed back by the serving base station of the second relay device according to the handover request message, where the handover response
  • the message carries the bypass link connection configuration information between the remote UE and the second relay device.
  • another relay transfer method running on the mobile terminal or the network architecture shown in FIG. 1 is provided to describe the interaction between the relay device and its serving base station, which is a preliminary preparation stage. ,include:
  • the service base station of the first relay device sends the second base station to the second relay device when the remote user equipment UE performs path relay conversion from the first relay device to the path relay from the second relay device.
  • the serving base station initiates a handover request message
  • the handover request message carries a bypass link between the remote UE and the second relay device (Side Link, SL) ) connection establishment information
  • the bypass link may be a PC5 link, a WIFI link, a Bluetooth link, and the like
  • the handover response message carries a side between the remote UE and the second relay device.
  • Road link connection configuration information when the second relay device is a UE for relaying, the handover request message carries a bypass link between the remote UE and the second relay device (Side Link, SL) ) connection establishment information
  • the bypass link may be a PC5 link, a WIFI link, a Bluetooth link, and the like
  • the handover response message carries a side between the remote UE and the second relay device.
  • Road link connection configuration information may be a PC5 link, a WIFI link, a Bluetooth link, and the like
  • the method in this embodiment further includes: after the remote UE performs an RLC reestablishment and a PDCP operation, the first relay device performs downlink (Down Link) to the second relay device. , DL) data transfer of data; and/or, after the remote UE performs RLC re-establishment and PDCP operation, the first relay device performs uplink (Up Link, UL) to the second relay device Data transfer of data.
  • the DL data may include: a PDCP Packet Data Unit (PDU) that is not correctly received by the RLC layer between the first relay device and the remote UE; the UL data includes: all the local caches of the first relay device have been cached. The PDCP PDU that is correctly received is confirmed by the RLC layer.
  • PDU Packet Data Unit
  • the method further includes: receiving, by the serving base station of the first relay device, the serving base station of the second relay device The capability information of the second relay device; wherein the capability information includes one of the following: support DL user UP plane forwarding, support DL/UL UP plane forwarding, support DL control CP plane forwarding, support UL CP plane forwarding, support DL/UL CP plane forwarding, support for DL CP/UP plane forwarding, support for UL CP/UP plane forwarding, and support for DL/UL CP/UP plane forwarding.
  • the capability information is carried in the X2 message, where the X2 message includes at least one of the following: an X2 setup request message, an X2 setup response message, an X2 setup failure message, a base station configuration update message, a base station configuration update response message, and a base station configuration. Update failure message.
  • the method according to the foregoing embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware.
  • the technical solution of the present disclosure which is essential or contributes to the related art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM).
  • the instructions include a number of instructions for causing a terminal device (which may be a cell phone, computer, server, or network device, etc.) to perform the methods of various embodiments of the present disclosure.
  • a relay transfer device In this embodiment, a relay transfer device, a base station, and a terminal are also provided, which are used to implement the foregoing embodiments and implementation manners, and are not described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the device described in the following embodiments can It is implemented by software, but hardware, or a combination of software and hardware, is also possible and conceived.
  • FIG. 4 is a structural block diagram of a relay transfer apparatus according to an embodiment of the present disclosure. As shown in FIG. 4, the apparatus includes:
  • the determining module 40 is configured to determine that the remote user equipment UE performs path relay switching from the first relay device to perform path relaying from the second relay device;
  • the execution module 42 is configured to perform a radio link control RLC reestablishment and a packet data convergence protocol PDCP operation.
  • the executing module performs an RLC reestablishment and a PDCP data recovery operation.
  • the execution module when the serving base station of the first relay device and the serving base station of the second relay device are different, the execution module performs an RLC reconstruction and a PDCP reconstruction operation.
  • the embodiment further provides a relay transfer device, which is applied to the serving base station of the first relay device, and includes: a sending module, configured to perform path relaying on the remote user equipment UE from the first relay device Switching to a handover request message to the serving base station of the second relay device by performing path relay from the second relay device; the first receiving module configured to receive the serving base station of the second relay device according to the handover A handover response message requesting feedback from a message.
  • a relay transfer device which is applied to the serving base station of the first relay device, and includes: a sending module, configured to perform path relaying on the remote user equipment UE from the first relay device Switching to a handover request message to the serving base station of the second relay device by performing path relay from the second relay device; the first receiving module configured to receive the serving base station of the second relay device according to the handover A handover response message requesting feedback from a message.
  • the handover request message carries the bypass link connection establishment information between the remote UE and the second relay device, and/or the handover response message Carrying bypass link connection configuration information between the remote UE and the second relay device.
  • the device further includes: a first indication module, configured to: after the remote UE performs the RLC re-establishment and the PDCP operation, instruct the first relay device to perform data transmission of the downlink DL data to the second relay device; And/or the second indication module is configured to instruct the first relay device to perform data transmission of the uplink UL data to the second relay device after the remote UE performs the RLC re-establishment and the PDCP operation.
  • a first indication module configured to: after the remote UE performs the RLC re-establishment and the PDCP operation, instruct the first relay device to perform data transmission of the downlink DL data to the second relay device
  • the second indication module is configured to instruct the first relay device to perform data transmission of the uplink UL data to the second relay device after the remote UE performs the RLC re-establishment and the PDCP operation.
  • the device further includes: a second receiving module, configured to receive the second relay device sent by the serving base station of the second relay device before the sending module initiates the handover request to the serving base station of the second relay device Capability information; wherein the capability information includes one of the following: support DL user UP plane forwarding, support DL/UL UP plane forwarding, support DL control CP plane forwarding, support UL CP plane forwarding, support DL/UL CP plane forwarding, support DL CP/UP plane forwarding, support for UL CP/UP plane forwarding, support for DL/UL CP/UP plane forwarding.
  • the capability information includes one of the following: support DL user UP plane forwarding, support DL/UL UP plane forwarding, support DL control CP plane forwarding, support UL CP plane forwarding, support DL/UL CP plane forwarding, support DL CP/UP plane forwarding, support for UL CP/UP plane forwarding, support for DL/UL CP/UP plane forwarding.
  • the capability information is carried in the X2 message, where the X2 message includes at least one of the following: an X2 setup request message, an X2 setup response message, an X2 setup failure message, a base station configuration update message, a base station configuration update response message, and a base station configuration. Update failure message.
  • the embodiment further provides a terminal, including: a processor and a memory storing processor executable instructions, when the instruction is executed by the processor, performing an operation of: determining that the remote user equipment UE passes the first relay device Performing path relay conversion to by performing path relay from the second relay device; an execution module configured to perform radio link control RLC reestablishment and packet data convergence protocol PDCP operations.
  • a terminal including: a processor and a memory storing processor executable instructions, when the instruction is executed by the processor, performing an operation of: determining that the remote user equipment UE passes the first relay device Performing path relay conversion to by performing path relay from the second relay device; an execution module configured to perform radio link control RLC reestablishment and packet data convergence protocol PDCP operations.
  • the performing RLC re-establishment and the PDCP operation by the processor includes: performing an RLC re-establishment and a PDCP data recovery operation.
  • the performing RLC re-establishment and the PDCP operation by the processor includes: performing an RLC re-establishment and a PDCP re-establishment operation.
  • the embodiment further provides a base station, including: a processor and a memory storing processor-executable instructions, when the instruction is executed by the processor, performing an operation of: at the remote user equipment UE from passing the first relay device Performing path relay conversion to initiate a handover request message to the serving base station of the second relay device by performing path relay from the second relay device; and receiving feedback from the serving base station of the second relay device according to the handover request message Switch the response message.
  • a base station including: a processor and a memory storing processor-executable instructions, when the instruction is executed by the processor, performing an operation of: at the remote user equipment UE from passing the first relay device Performing path relay conversion to initiate a handover request message to the serving base station of the second relay device by performing path relay from the second relay device; and receiving feedback from the serving base station of the second relay device according to the handover request message Switch the response message.
  • the handover request message carries the bypass link connection establishment information between the remote UE and the second relay device, and/or the handover response message Carrying bypass link connection configuration information between the remote UE and the second relay device.
  • the processor further performs capability information of the second relay device that is sent by the serving base station of the second relay device before the serving base station of the first relay device initiates the handover request to the serving base station of the second relay device.
  • the capability information includes one of the following: support DL user UP plane forwarding, support DL/UL UP plane forwarding, support DL control CP plane forwarding, support UL CP plane forwarding, support DL/UL CP plane forwarding, support DL CP/ UP plane forwarding, support for UL CP/UP plane forwarding, and support for DL/UL CP/UP plane forwarding.
  • the capability information is carried in the X2 message, where the X2 message includes at least one of the following: an X2 setup request message, an X2 setup response message, an X2 setup failure message, a base station configuration update message, a base station configuration update response message, and a base station configuration. Update failure message.
  • the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the above modules are all located in the same processor; or, the above modules are respectively located in different combinations. In the processor.
  • This embodiment is an optional embodiment according to the present disclosure, which is used to describe the application in detail in combination with the scenario:
  • the embodiment provides a method and a device for service continuity in a relay network, including:
  • the relay UE3 When the remote UE performs path conversion between the relay UE1 and the relay UE2, the relay UE3, and the eNB1, where the serving UEs of the relay UE1 and the relay UE2 are the same, and the serving base station of the relay UE3 is the eNB1,
  • the remote UE performs RLC reconstruction and PDCP data recovery operations.
  • the remote UE When the remote UE performs path conversion between the relay UE1 and the relay UE2, the relay UE3, and the eNB1, where the serving base stations of the relay UE1 and the relay UE2 are different, and the serving base station of the relay UE3 and the eNB1 are different,
  • the remote UE performs RLC reconstruction and PDCP reconstruction operations.
  • the two scenarios are performed across the base station and not across the base station; or from the relay.
  • the UE is switched to the eNB, where the eNB is the serving base station of the relay UE; or when the relay UE is switched to the eNB, where the eNB is not the serving base station of the relay UE,
  • Relay UE performs data transmission of DL data to the serving eNB; and/or, the Relay UE performs data transmission of UL data to the serving eNB;
  • the DL data may include all PDCP PDUs that are not correctly received by the RLC layer between the Relay UE and the remote UE;
  • the UL data may include all locally buffered PDCP PDUs that have been acknowledged correctly received by the RLC layer;
  • the remote UE can work on the relay UE under the serving eNB or the serving eNB,
  • the handover request (HO Request) message sent by the serving eNB to the target eNB carries the PC5 connection establishment information between the remote UE and the relay UE under the target eNB;
  • the target eNB corresponding handover request (HO Request Acknowledge) message carries the PC5 connection configuration information between the remote UE and the relay UE under the target eNB.
  • the base station 1 sends the relay UE Capability information to the base station 2, indicating the capability list of some or all of the relay UEs, and the capability indication includes but not limited to only supporting DL UP plane forwarding; only DL/UL UP plane forwarding is supported. Only DL CP plane forwarding is supported; only UL CP plane forwarding is supported; only DL/UL CP plane forwarding is supported; only DL CP/UP plane forwarding is supported; only UL CP/UP plane forwarding is supported; DL/UL CP/UP plane is supported. Forward.
  • the X2 message carrying the relay UE Capability information includes but is not limited to the X2 Setup Request/Response/Failure or the eNB Configuration Update/Update Acknowledge/Update Failure message. .
  • the service interruption problem generated when the remote user moves between the relay station and the base station, the relay station and the relay station is solved.
  • the remote user can implement the service continuity transmission and reception in the mobile process, thereby achieving the effect of business continuity and improving the user experience.
  • the remote user can implement continuous data transmission and reception when moving between the relay UE and the base station, the relay UE, and the relay UE.
  • the remote UEs may be of the following types of devices, such as wearable devices, Cat-0, Cat-1, Cat-M1, and NB-IoT UEs. These devices may be in normal coverage, extended coverage or no coverage, as shown in Figure 1.
  • wearable devices Cat-0, Cat-1, Cat-M1, and NB-IoT UEs.
  • These devices may be in normal coverage, extended coverage or no coverage, as shown in Figure 1.
  • Mode 1 and Mode 2 although the far end UE can directly interact with the network, in order to save power, the far end UE can find surrounding relay UEs to help forward data packets or even control signaling.
  • the remote UE is in the no-cover state, and can only find the surrounding relay UE to access the network and forward the data and control signaling by the relay UE.
  • FIG. 5 is a schematic diagram of two protocol stack architectures between remote UE-relay UE-eNBs in the embodiment of the present disclosure.
  • a protocol stack architecture and a b protocol stack architecture are provided, and two possible LTE schemes are given.
  • the system relay network protocol stack architecture wherein the interface used between the remote UE and the relay UE is a D2D interface (the name in the LTE category is a PC5 interface).
  • the interface used between the remote UE and the relay UE is a D2D interface (the name in the LTE category is a PC5 interface).
  • the end-to-end PDCP layer is maintained between the remote UE and the base station; the protocol stack maintained between the remote UE and the relay UE includes PC5RLC/PC5MAC (Medium Access Control Layer)/PC5PHY (Physical Layer)
  • the protocol stack maintained between the relay UE and the base station includes a Uu RLC/Uu MAC/Uu PHY.
  • the end-to-end PDCP layer and the RLC layer are maintained between the remote UE and the base station; the protocol stack maintained between the remote UE and the relay UE includes the PC5MAC/PC5.
  • the protocol stack maintained between the PHY; relay UE and the base station includes a Uu MAC/Uu PHY.
  • FIG. 6 is a flowchart of a remote UE using a protocol stack architecture to switch from an eNB to a relay UE in the embodiment of the present disclosure, where the relay UE and the remote UE are in the same eNB.
  • Figure 6 shows a flow chart of the remote UE switching from the eNB to the relay UE. The feature of this procedure is that the PDCP layer of the far-end UE is always anchored on the eNB but the RLC/MAC/PHY layer is switched from the eNB to the relay UE.
  • the remote UE After completing the path handover decision from the eNB to the relay UE, the remote UE initiates a Relay UE discovery and a PC5 connection establishment procedure. In the process, the eNB performs processes such as authorization judgment and resource configuration on the remote UE and the relay UE.
  • the PDCP Status Report is sent to the eNB to ensure the continuity of the downlink data reception.
  • the PDCP Status Report of the remote UE indicates the serial number (SN) of all unsuccessfully received PDCP PDUs during RLC re-establishment.
  • the base station After receiving the information, the base station retransmits the PDCP PDU corresponding to the PDCP SN number indicated by the remote UE. Whether the remote UE sends the PDCP Status Report may depend on the configuration of the eNB.
  • the remote UE performs RLC reconstruction and PDCP data recovery operations after completing the communication establishment procedure on the PC5 interface.
  • the remote UE will re-submit the PDCP PDUs that are not RLC ACK (acknowledgement) in the data submitted to the RLC entity before the RLC re-establishment on the link of the far-end UE-relay UE according to the COUNT value (count value).
  • Sent. The eNB may issue a PDCP status report between step 8 and step 10 to assist the UE in performing a PDCP data recovery operation.
  • FIG. 7 is a flowchart of a remote UE using a b protocol stack architecture to switch from an eNB to a relay UE in an embodiment of the present disclosure, where the relay UE and the remote UE are in the same eNB.
  • Figure 7 shows a flow chart of the remote UE switching from the eNB to the relay UE.
  • the feature of this process is that the PDCP layer and the RLC layer of the far-end UE are always anchored on the eNB but the MAC/PHY layer is from the eNB. Switched to the relay UE. Since the RLC layer is always anchored on the eNB, the continuity of data reception can be solved by the ARQ mechanism at the RLC layer in both the uplink and the downlink.
  • the base station may forward all downlink data that is not RLC ACK to the relay UE; the remote UE may forward all uplink data that is not RLC ACK to the relay UE.
  • FIG. 8 is a flowchart of a remote UE switching from a relay UE to an eNB using a protocol stack architecture in the embodiment of the present disclosure, where the relay UE and the remote UE are in the same eNB.
  • FIG. 8 shows a flow chart of the remote UE switching from the relay UE to the eNB.
  • the feature of this procedure is that the PDCP layer of the far-end UE is always anchored on the eNB but the RLC/MAC/PHY layer is switched from the relay UE to the eNB.
  • the remote UE After completing the path handover decision from the relay UE to the eNB, the remote UE initiates a connection establishment procedure (steps 1 and 2) with the eNB, and then releases the PC5 connection between the relay UE and the relay UE (step 3); The relay UE also configures the connection release between the relay UE and the remote UE through RRC signaling (step 4).
  • the relay UE After the relay UE receives the RRC signaling sent by the eNB to configure the release of the connection between the relay UE and the remote UE, in order to ensure the continuity of the downlink data reception of the remote UE, the relay UE will not transmit the local buffer and is not RLCACK.
  • the downlink PDCP PDU is transmitted back to the eNB; the remote UE sends a PDCP status report to the eNB.
  • the PDCP Status Report of the remote UE indicates the SN number of all unsuccessfully received PDCP PDUs during RLC re-establishment.
  • the base station After receiving the information, the base station retransmits the downlink PDCP PDU corresponding to the PDCP SN number indicated by the remote UE. Whether the remote UE sends the PDCP Status Report may depend on the configuration of the eNB.
  • the remote UE performs RLC reconstruction and PDCP data recovery operations after completing the connection configuration with the eNB.
  • the remote UE re-sends the PDCP PDUs that are not RLC ACKs in the data submitted to the RLC entity before the RLC re-establishment on the link between the remote UE-eNBs in descending order of COUNT value.
  • the eNB may send a PDCP status report between steps 2 and 7 to assist the UE in PDCP data recovery. operating.
  • the relay UE may also forward the locally buffered uplink data to the eNB.
  • FIG. 9 is a flowchart of a remote UE using a protocol stack architecture to switch from relay UE1 to relay UE2 in the embodiment of the present disclosure, where the remote UE is the same as the eNB in which relay UE1 and relay UE2 are located, and FIG. 9 shows the far A flow chart of the UE switching from relay UE1 to relay UE2.
  • the feature of this procedure is that the PDCP layer of the far-end UE is always anchored on the eNB but the RLC/MAC/PHY layer is switched from relay UE1 to relay UE2.
  • the remote UE After completing the path decision from relay UE1 to relay UE2, the remote UE initiates a link configuration update between the eNB and the eNB (step 1-2), and releases the PC5 connection between the relay UE1 (step 3), and relay UE2 The PC5 connection is established (step 4).
  • the PC5 connection release configuration operation between the remote UE and the relay UE1 is performed between the relay UE1 and the eNB (step 3), and the configuration of the PC5 connection between the remote UE and the relay UE2 is performed between the relay UE2 and the eNB (step 4).
  • the relay UE1 After the relay UE1 receives the RRC signaling sent by the eNB to configure the release of the PC5 connection between the relay UE1 and the remote UE, in order to ensure the continuity of the downlink data reception of the remote UE, the relay UE1 will not transmit the local cache and is not.
  • the downlink PDCP PDU of the RLC ACK is transmitted back to the eNB; the remote UE sends a PDCP status report to the eNB.
  • the SN number of all PDCP PDUs that are not correctly received is indicated in the PDCP status report sent by the remote UE.
  • the base station After receiving the information, the base station retransmits the downlink PDCP PDU corresponding to the PDCP SN number indicated by the remote UE. Whether the remote UE sends the PDCP status report may depend on the configuration of the eNB.
  • the remote UE performs RLC reconstruction and PDCP data recovery operations after completing the establishment of the PC5 connection with the relay UE2.
  • the remote UE re-sends the PDCP PDUs that are not RLC ACKs in the data submitted to the RLC entity before the RLC re-establishment on the link between the remote UE-relay UE2 in descending order of COUNT value according to the COUNT value.
  • the eNB may issue a PDCP status report between steps 4 and 7 to assist the UE in performing PDCP data recovery operations.
  • the relay UE may also forward the locally buffered uplink data to the eNB.
  • FIG. 10 is a remote UE switching from eNB1 to a subordinate using a protocol stack architecture in an embodiment of the present disclosure
  • FIG. 10 shows a flow chart of the remote UE switching from the eNB1 to the relay UE belonging to the eNB2.
  • the flow is characterized in that the PDCP layer anchor point of the far-end UE is switched from eNB1 to eNB2, and the RLC/MAC/PHY layer is switched from eNB1 to the relay UE.
  • the remote UE After completing the path handover decision from the eNB to the relay UE, the remote UE indicates a PC5 connection establishment request (UE bypass link information) to the source serving eNB (S-eNB), where the cell in which the relay UE is located is globally carried. EUTRAN Cell Global Identifier (ECGI).
  • the remote UE may send a measurement report (MR) to the S-eNB.
  • the serving base station initiates a handover request to the target base station (T-eNB) corresponding to the ECGI, where the PC5 connection establishment request between the remote UE-relay UEs is carried. Whether the serving base station initiates the handover procedure may depend on the information carried in the MR or UE sidelinkinformation.
  • the remote UE initiates a PC5 connection establishment process between the relay UE and the relay UE.
  • the S-eNB forwards the downlink data that has been cached locally but is not successfully sent to the UE to the T-eNB; the remote UE sends the PDCP Status Report to the T-eNB.
  • the PDCP Status Report sent by the remote UE indicates the SN number of all unsuccessfully received PDCP PDUs during RLC reestablishment.
  • the base station After receiving the information, the base station retransmits the PDCP PDU corresponding to the PDCP SN number indicated by the remote UE. Whether the remote UE sends the PDCP Status Report may depend on the configuration of the eNB.
  • the remote UE performs the RLC reconstruction and the PDCP reconstruction operation after completing the communication establishment procedure on the PC5 interface.
  • the remote UE will use the encryption algorithm and the encryption key in the re-establishment process for the PDCP SDU that has not been successfully transmitted before the PDCP re-establishment has been associated with the PDCP SN number.
  • the UE-relay UE is in the low-to-high order according to the COUNT value. Send or resend on the PC5 link.
  • the T-eNB may issue a PDCP status report between step 8 and step 10 to assist the UE in performing a PDCP reestablishment operation.
  • FIG. 11 is a flowchart of a remote UE using a protocol stack architecture to switch from a relay UE under eNB1 to an eNB2 in the embodiment of the present disclosure, where the remote UE and the relay UE are in the same eNB, and FIG. 11 shows the remote end.
  • the HO process is initiated between the S-eNB and the T-eNB.
  • the S-eNB initiates an RRC connection reconfiguration message to the remote UE, where the handover command configured by the T-eNB to the remote UE is carried.
  • the S-eNB also initiates an RRC connection reconfiguration message to the relay UE to release the PC5 connection between the relay UE-remote UEs.
  • the relay UE In order to ensure the continuity of the downlink data reception, the relay UE returns the downlink PDCP PDU that is not transmitted and not RLC ACK to the S-eNB; the DL data returned by the relay UE and the local cache are not transmitted. The DL data and the downlink PDCP PDU that is not RLC ACK are forwarded to the T-eNB.
  • the remote UE sends a PDCP status report to the T-eNB.
  • the SN number of all PDCP PDUs that are not correctly received is indicated in the PDCP status report sent by the remote UE.
  • the T-eNB After receiving the information, the T-eNB retransmits the downlink PDCP PDU corresponding to the PDCP SN indicated by the remote UE. Whether the remote UE sends the PDCP status report may depend on the configuration of the eNB.
  • the remote UE performs RLC reconstruction and PDCP reconstruction operations after completing the handover procedure.
  • the remote UE will use the encryption algorithm and the encryption key in the re-establishment process for the PDCP SDU that has not been successfully transmitted before the PDCP reconstruction has been associated with the PDCP SN number.
  • the UE-T- is in the COUNT value from low to high order.
  • the eNB (UE to the target base station) transmits or retransmits on the link.
  • the T-eNB may issue a PDCP status report between step 8 and step 10 to assist the UE in performing a PDCP reestablishment operation.
  • FIG. 12 is a flowchart of a remote UE using a protocol stack architecture in the present disclosure switching from relay UE1 under eNB1 to relay UE2 under eNB2;
  • FIG. 12 is a diagram showing that the remote UE is handed over from relay UE1 under eNB1 to eNB2.
  • Flowchart of relay UE2. The flow is characterized in that the PDCP layer anchor point of the far-end UE is switched from eNB1 to eNB2, and the RLC/MAC/PHY layer is switched from relay UE1 under eNB1 to relay UE2 under eNB2.
  • the HO process is initiated between the S-eNB and the T-eNB.
  • the S-eNB initiates an RRC connection reconfiguration message to the remote UE, where the handover command and the remote end configured by the T-eNB to the remote UE are carried.
  • the S-eNB also initiates an RRC connection reconfiguration message to the relay UE to release the PC5 connection between the relay UE-remote UEs.
  • the remote UE and the relay UE1 under the S-eNB complete the PC5 connection release and complete the PC5 connection establishment with the relay UE2 under the T-eNB.
  • the relay UE1 In order to ensure the continuity of the downlink data reception, the relay UE1 returns the downlink PDCP PDU that is not transmitted and not RLC ACK to the S-eNB; the DL data returned by the S-eNB and the local cache is not transmitted. The DL data and the downlink PDCP PDU that is not RLC ACK are forwarded to the T-eNB.
  • the remote UE sends a PDCP status report to the T-eNB.
  • the SN number of all PDCP PDUs that are not correctly received is indicated in the PDCP status report sent by the remote UE.
  • the T-eNB After receiving the information, the T-eNB retransmits the downlink PDCP PDU corresponding to the PDCP SN indicated by the remote UE. Whether the remote UE sends the PDCP status report may depend on the configuration of the eNB.
  • the remote UE performs RLC reconstruction and PDCP reconstruction operations after completing the handover procedure.
  • the remote UE will use the encryption algorithm and the encryption key in the re-establishment process for the PDCP SDU that has not been successfully transmitted before the PDCP reconstruction has been associated with the PDCP SN number.
  • the UE-T- is in the COUNT value from low to high order. Transmit or retransmit on the eNB link.
  • the T-eNB may issue a PDCP status report between step 8 and step 10 to assist the UE in performing a PDCP reestablishment operation.
  • FIG. 13 is a flowchart of the eNB1 notifying the peer eNB2 of the capability of the relay UE under its jurisdiction in the embodiment of the present disclosure.
  • the eNB1 in order to support the relay addition operation of the cross-base station in Embodiments 6 and 7, the eNB1 will perform its own operation.
  • the capability of the relay UE is notified to the opposite eNB2, so that the opposite eNB2 makes an HO decision for the remote UE.
  • the message carrying the relay UE capability includes but is not limited to an X2 Setup Request/Response/Failure or an eNB Configuration Update/Update Acknowledge/Update Failure message.
  • the capability in the relay UE capability IE may be applicable to all relay UEs, and may be specifically defined for each relay UE.
  • the list of capabilities can include but is not limited to:
  • the S-eNB may perform the HO decision for the remote UE, which may be based on the measurement of the relay UE by the remote UE, even between the remote UE and the T-eNB. If the measurement result does not meet the requirements, the S-eNB may also perform HO on the remote UE.
  • the S-eNB must consider the measurement result (MR) between the remote UE and the T-eNB when making the HO decision for the remote UE. That is to say, only when the measurement result satisfies the requirement, the S-eNB can perform the HO for the remote UE.
  • MR measurement result
  • Embodiments of the present disclosure also provide a storage medium.
  • a computer readable storage medium storing computer executable instructions arranged to perform the above method.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor performs, according to the stored program code in the storage medium, that the remote user equipment UE performs path relay conversion from the first relay device to the second relay device.
  • path relaying radio link control RLC reestablishment and packet data convergence protocol PDCP operations are performed.
  • the computer readable storage medium may be a transitory computer readable storage medium or a non-transitory computer readable storage medium.
  • modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.
  • the relay transfer method and device, terminal, and base station provided by the present application solve the problem that the terminal user is prone to service interruption when moving in the related art, and realizes service continuity transmission and reception in the mobile process, thereby achieving business continuity.
  • the effect is to improve the user experience.

Landscapes

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

Abstract

La présente invention concerne un procédé et dispositif de transfert de relais, un terminal et une station de base. Le procédé comporte l'étape suivante: lorsqu'un équipement d'utilisateur (UE) distant passe de l'utilisation d'un premier dispositif de relais pour un relais de trajet à l'utilisation d'un deuxième dispositif de relais pour un relais de trajet, l'UE distant effectue un rétablissement de commande de liaison radio (RLC) et une exploitation sous protocole de convergence de données par paquets (PDCP). La présente invention résout le problème rencontré dans la technique apparentée, où les usagers sont susceptibles d'être confrontés à des interruptions de service lorsqu'ils se déplacent, réalisant l'émission et la réception continues de services au cours d'un déplacement, assurant ainsi la continuité de service et améliorant l'agrément d'utilisation.
PCT/CN2017/109258 2016-11-03 2017-11-03 Procédé et dispositif de transfert de relais, terminal, station de base Ceased WO2018082644A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610959091.0A CN108024295B (zh) 2016-11-03 2016-11-03 中继转移方法及装置、终端、基站
CN201610959091.0 2016-11-03

Publications (1)

Publication Number Publication Date
WO2018082644A1 true WO2018082644A1 (fr) 2018-05-11

Family

ID=62076665

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/109258 Ceased WO2018082644A1 (fr) 2016-11-03 2017-11-03 Procédé et dispositif de transfert de relais, terminal, station de base

Country Status (2)

Country Link
CN (1) CN108024295B (fr)
WO (1) WO2018082644A1 (fr)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112514520A (zh) * 2020-11-04 2021-03-16 北京小米移动软件有限公司 中继ue的重选方法、装置、通信设备及存储介质
CN113453272A (zh) * 2020-03-25 2021-09-28 维沃移动通信有限公司 副链路中继架构中的切换方法和设备
CN114390620A (zh) * 2020-10-22 2022-04-22 大唐移动通信设备有限公司 一种下行数据传输方法、装置、中继节点及网络设备
CN115243337A (zh) * 2021-04-23 2022-10-25 华为技术有限公司 数据传输方法及装置
CN115699873A (zh) * 2020-08-19 2023-02-03 Oppo广东移动通信有限公司 中继节点切换方法、终端设备和网络设备
CN115701746A (zh) * 2021-08-02 2023-02-10 维沃移动通信有限公司 传输处理方法、装置、终端及网络侧设备
CN116018876A (zh) * 2020-09-30 2023-04-25 Oppo广东移动通信有限公司 通信方法和通信装置
CN116056093A (zh) * 2021-10-28 2023-05-02 中国移动通信有限公司研究院 传输方法、装置、设备及可读存储介质
CN116347545A (zh) * 2020-10-22 2023-06-27 展讯通信（上海）有限公司 无线通信方法与装置、终端和存储介质
WO2023124932A1 (fr) * 2021-12-27 2023-07-06 华为技术有限公司 Procédé d'établissement de connexion et appareil de communication
WO2023150944A1 (fr) * 2022-02-09 2023-08-17 Oppo广东移动通信有限公司 Procédé de commutation, dispositif terminal et dispositif de réseau
US20230337299A1 (en) * 2020-03-25 2023-10-19 Telefonaktiebolaget Lm Ericsson (Publ) Methods, apparatuses and computer-readable medium for device-to-device communication

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110636562B (zh) * 2018-06-21 2023-06-27 大唐移动通信设备有限公司 一种无线回程路径的数据处理方法和设备
CN111148163B (zh) * 2018-11-02 2021-09-14 华为技术有限公司 通信方法及装置
CN111212459B (zh) * 2018-11-22 2021-09-14 华为技术有限公司 一种中继通信方法及装置
CN110786029A (zh) * 2018-11-30 2020-02-11 深圳市大疆创新科技有限公司 一种通信方法、装置、移动平台及控制终端
CN111586765B (zh) * 2019-02-15 2023-01-13 华为技术有限公司 中继通信的方法和装置
CN111818592A (zh) * 2019-07-31 2020-10-23 维沃移动通信有限公司 一种网络切换方法、网络设备及终端
CN111836334B (zh) * 2019-08-21 2023-03-14 维沃移动通信有限公司 发现节点的方法、链路建立的方法和设备
CN110519724A (zh) * 2019-08-27 2019-11-29 深圳成谷科技有限公司 一种提高pc5接口通信质量的方法和装置
WO2021056573A1 (fr) * 2019-09-29 2021-04-01 Oppo广东移动通信有限公司 Procédé pour établir une session et dispositifs terminaux
CN111901836A (zh) * 2020-02-13 2020-11-06 中兴通讯股份有限公司 链路切换、链路切换配置方法、装置、通信节点及介质
WO2021189269A1 (fr) * 2020-03-24 2021-09-30 华为技术有限公司 Procédé et appareil pour mettre en place une continuité de service
CN113453290A (zh) * 2020-03-25 2021-09-28 维沃移动通信有限公司 数据前转的方法、源节点设备和目标节点设备
WO2021195867A1 (fr) * 2020-03-30 2021-10-07 Mediatek Singapore Pte. Ltd. Mise en correspondance de porteuse pour relais d'ue à ue
WO2021212316A1 (fr) * 2020-04-21 2021-10-28 Mediatek Singapore Pte. Ltd. Procédés et appareil de commutation de chemin pour relais ue-à-réseau de couche 3
CN113630821B (zh) * 2020-05-09 2023-03-10 华为技术有限公司 通信方法及装置
CN113676845B (zh) * 2020-05-13 2023-04-04 成都鼎桥通信技术有限公司 一种近距离业务多跳中继通信方法
JP7549135B2 (ja) * 2020-09-25 2024-09-10 テレフオンアクチーボラゲット エルエム エリクソン（パブル） パス切り替えのための方法および装置
WO2022061913A1 (fr) * 2020-09-28 2022-03-31 华为技术有限公司 Procédé et appareil de communication
CN114641089B (zh) * 2020-12-15 2025-02-28 华为技术有限公司 一种通信方法、装置及系统
CN114650513A (zh) * 2020-12-17 2022-06-21 华为技术有限公司 通信方法及通信装置
WO2022236674A1 (fr) * 2021-05-11 2022-11-17 Qualcomm Incorporated Opérations de commutation de liaison hertzienne dans une communication sans fil
CN115701172B (zh) * 2021-07-28 2025-12-09 大唐移动通信设备有限公司 分组数据汇聚协议状态报告发送方法、设备及装置
CN115996406A (zh) * 2021-10-20 2023-04-21 大唐移动通信设备有限公司 定时器维护方法、装置、设备及存储介质
WO2023065298A1 (fr) * 2021-10-22 2023-04-27 Mediatek Singapore Pte. Ltd. Commutation de trajet indirect-direct avec continuité de service dans un relais ue-réseau de couche 2
CN116367264A (zh) * 2021-12-28 2023-06-30 夏普株式会社 由用户设备执行的方法及用户设备
CN118975384A (zh) * 2022-04-04 2024-11-15 瑞典爱立信有限公司 处理pdcp复制的方法和装置
CN117858183A (zh) * 2022-10-08 2024-04-09 华为技术有限公司 通信方法、装置及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102415140A (zh) * 2009-04-28 2012-04-11 株式会社Ntt都科摩 移动通信系统
CN103442400A (zh) * 2009-04-27 2013-12-11 株式会社Ntt都科摩 移动通信系统
CN105229961A (zh) * 2013-04-04 2016-01-06 诺基亚通信公司 协议数据单元的递送
CN105917727A (zh) * 2014-01-30 2016-08-31 夏普株式会社 用于双连接操作的系统和方法

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1689130A1 (fr) * 2005-02-07 2006-08-09 Lg Electronics Inc. Méthode pour le règlage d'une erreur dans une commande de liaison radioélectrique
GB2449629A (en) * 2007-05-01 2008-12-03 Nec Corp Buffering numbered unsegmented PDCP SDUs in 3GPP system to assist efficient hard handover
US8630259B2 (en) * 2008-08-04 2014-01-14 Qualcomm Incorporated PDCP behaviour at handover and connection re-establishment
CN101686494B (zh) * 2008-09-22 2012-07-04 电信科学技术研究院 一种分组数据汇聚协议层处理数据包的方法和装置
CN101841852B (zh) * 2009-03-20 2013-01-16 中兴通讯股份有限公司 一种跨基站切换时的上行数据传输方法、装置及系统
CN101873655B (zh) * 2009-04-24 2015-06-03 中兴通讯股份有限公司 用户终端切换时应对无线链路失败的处理方法与装置
CN104540177B (zh) * 2009-06-17 2018-06-15 交互数字专利控股公司 一种施主演进型节点b以及由其使用的方法
CN101938798A (zh) * 2009-07-03 2011-01-05 中兴通讯股份有限公司 一种无线中继系统中终端的移动性管理方法及系统
CN101997660B (zh) * 2009-08-14 2014-11-05 中兴通讯股份有限公司 一种避免上行数据丢失的方法及装置
WO2011020233A1 (fr) * 2009-08-17 2011-02-24 上海贝尔股份有限公司 Procédé et dispositif de commande de transmission de données de liaison descendante dans un système de communication à relais à plusieurs bonds
CN101656993A (zh) * 2009-09-16 2010-02-24 华为技术有限公司 一种接入点切换方法及装置
CN102056226B (zh) * 2009-11-10 2016-03-02 中兴通讯股份有限公司 Pdcp状态报告的获取方法和pdcp实体
CN102196496B (zh) * 2010-03-19 2016-05-11 中兴通讯股份有限公司 一种处理回程链路错误的方法和中继节点
EP2442610B1 (fr) * 2010-10-13 2017-12-06 Alcatel Lucent Livraison en séquence de trafic utilisateur en amont pendant le transfert
CN103024930B (zh) * 2011-09-23 2016-01-20 中国移动通信集团公司 数据传输方法、中继节点、汇聚服务器和系统
CN103200627B (zh) * 2012-01-04 2018-05-11 中兴通讯股份有限公司 一种解决切换过程中重建立冲突的方法及移动终端
US8913556B2 (en) * 2012-06-18 2014-12-16 International Business Machines Corporation Reducing packet loss in a mobile data network with data breakout at the edge
CN103916917B (zh) * 2013-01-06 2018-08-07 电信科学技术研究院 一种承载分离场景下进行切换的方法、设备及系统
CN103997762B (zh) * 2013-02-19 2017-08-25 中兴通讯股份有限公司 一种小区切换方法及系统
CN104144521B (zh) * 2013-05-08 2018-09-11 华为技术有限公司 中继通信方法、装置及系统
EP2835925B1 (fr) * 2013-08-09 2018-08-08 Panasonic Intellectual Property Corporation of America Rapport d'état efficace pour des UE dans une connectivité double en mode mobile
US20160255565A1 (en) * 2013-11-01 2016-09-01 Lg Electronics Inc. Method for transmitting cell visited history and wireless equipment thereof
CN105050152B (zh) * 2015-07-14 2017-06-20 宇龙计算机通信科技(深圳)有限公司 一种基于d2d中继通信的业务处理方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103442400A (zh) * 2009-04-27 2013-12-11 株式会社Ntt都科摩 移动通信系统
CN102415140A (zh) * 2009-04-28 2012-04-11 株式会社Ntt都科摩 移动通信系统
CN105229961A (zh) * 2013-04-04 2016-01-06 诺基亚通信公司 协议数据单元的递送
CN105917727A (zh) * 2014-01-30 2016-08-31 夏普株式会社 用于双连接操作的系统和方法

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113453272A (zh) * 2020-03-25 2021-09-28 维沃移动通信有限公司 副链路中继架构中的切换方法和设备
CN113453272B (zh) * 2020-03-25 2023-11-10 维沃移动通信有限公司 副链路中继架构中的切换方法和设备
US20230337299A1 (en) * 2020-03-25 2023-10-19 Telefonaktiebolaget Lm Ericsson (Publ) Methods, apparatuses and computer-readable medium for device-to-device communication
CN115699873A (zh) * 2020-08-19 2023-02-03 Oppo广东移动通信有限公司 中继节点切换方法、终端设备和网络设备
CN116018876A (zh) * 2020-09-30 2023-04-25 Oppo广东移动通信有限公司 通信方法和通信装置
CN116347545A (zh) * 2020-10-22 2023-06-27 展讯通信（上海）有限公司 无线通信方法与装置、终端和存储介质
CN114390620A (zh) * 2020-10-22 2022-04-22 大唐移动通信设备有限公司 一种下行数据传输方法、装置、中继节点及网络设备
CN112514520A (zh) * 2020-11-04 2021-03-16 北京小米移动软件有限公司 中继ue的重选方法、装置、通信设备及存储介质
CN115243337A (zh) * 2021-04-23 2022-10-25 华为技术有限公司 数据传输方法及装置
CN115701746A (zh) * 2021-08-02 2023-02-10 维沃移动通信有限公司 传输处理方法、装置、终端及网络侧设备
CN116056093A (zh) * 2021-10-28 2023-05-02 中国移动通信有限公司研究院 传输方法、装置、设备及可读存储介质
WO2023124932A1 (fr) * 2021-12-27 2023-07-06 华为技术有限公司 Procédé d'établissement de connexion et appareil de communication
WO2023150944A1 (fr) * 2022-02-09 2023-08-17 Oppo广东移动通信有限公司 Procédé de commutation, dispositif terminal et dispositif de réseau

Also Published As

Publication number Publication date
CN108024295B (zh) 2022-04-19
CN108024295A (zh) 2018-05-11

Similar Documents

Publication Publication Date Title
CN108024295B (zh) 中继转移方法及装置、终端、基站
JP7267962B2 (ja) 複数のサイト間のデータ分割
JP7168028B2 (ja) 命令指示方法及び装置、情報交換方法及び装置
EP2850906B1 (fr) Procédé et appareil pour changer les chemins de communication
US10805856B2 (en) Methods and units in a network node for handling communication with a wireless device
CN111328118B (zh) 传输方法及装置
CN103428788B (zh) 一种数据转发的方法、设备及通讯系统
JP2021193804A (ja) ネットワーク接続の復旧装置
CN111602462A (zh) 用户设备、节点以及在其中执行的方法
JP2019083582A (ja) 多重接続性を使用するマルチキャスティングトラフィック
CN115669060A (zh) 在条件切换（cho）时保持/改变mr-dc
CN104113875B (zh) 一种小区切换方法、装置及设备
CN114586416A (zh) 通过侧行链路的恢复
US20230156587A1 (en) Transmission Configuration Method and Device
US20220287126A1 (en) Sidelink transmission continuity
CN103987093B (zh) 切换通信连线模式的方法、通信系统、基地台、传送端及接收端
US20240397357A1 (en) Service continuity of sidelink relay communication
CN107302773A (zh) 连接的建立方法、装置及系统
US20230403623A1 (en) Managing sidelink information, configuration, and communication
CN113556792B (zh) 状态报告传输方法、终端设备和网络设备
CN104053146B (zh) 小小区承载的激活与去激活方法及设备
KR102452958B1 (ko) X2 핸드오버 동안 베어러 관리 방법 및 장치
JP2025504198A (ja) 通信維持方法及び装置
KR20250048084A (ko) 사이드링크 무선 통신 기법
KR20250134685A (ko) 사이드링크(sl) 릴레이를 위한 다중 경로 구성

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: 17867234

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: 17867234

Country of ref document: EP

Kind code of ref document: A1