[go: up one dir, main page]

WO2019028811A1 - 一种路径转换方法、相关装置及系统 - Google Patents

一种路径转换方法、相关装置及系统 Download PDF

Info

Publication number
WO2019028811A1
WO2019028811A1 PCT/CN2017/097022 CN2017097022W WO2019028811A1 WO 2019028811 A1 WO2019028811 A1 WO 2019028811A1 CN 2017097022 W CN2017097022 W CN 2017097022W WO 2019028811 A1 WO2019028811 A1 WO 2019028811A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
message
network device
link
path
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/097022
Other languages
English (en)
French (fr)
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2017/097022 priority Critical patent/WO2019028811A1/zh
Priority to CN202210053239.XA priority patent/CN114513822B/zh
Priority to US16/635,764 priority patent/US11419025B2/en
Priority to CN201780093715.8A priority patent/CN111034334B/zh
Priority to EP17921176.8A priority patent/EP3637940B1/en
Publication of WO2019028811A1 publication Critical patent/WO2019028811A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • 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
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • 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
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • 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

  • the present application relates to the field of communications technologies, and in particular, to a path conversion method, related apparatus, and system.
  • a terminal In a mobile communication system, there are two connection modes between a terminal and a network device (such as a base station):
  • Connection mode 1 The terminal directly connects to the network device for data communication. This mode can be referred to as a direct communication mode. In this communication mode, the communication link between the terminal and the network device may be referred to as a direct link;
  • Connection mode 2 The terminal connects to the network device through other terminals to perform data communication.
  • This mode can be referred to as an indirect communication mode.
  • the former may be referred to as a remote terminal, such as a remote user equipment (remote UE), and the latter may be referred to as a relay terminal, such as a relay user equipment (relay UE).
  • relay UE remote user equipment
  • the communication link between the terminal and the network device may be referred to as a non-direct link.
  • the remote terminal can switch between the two connection modes or communication links described above.
  • the UE may choose to connect with the base station through a nearby relay UE. At this time, it is necessary to perform the conversion from the direct communication method to the indirect communication method.
  • FIG. 1B after the relay UE connected by the remote UE moves, the connection between the remote UE and the relay UE may not be maintained. At this time, it is necessary to perform the conversion from the indirect communication mode to the direct connection communication mode.
  • the remote UE After the remote UE triggers the transition from the indirect path to the direct path, the remote UE sends a radio resource control (RRC) message to the base station.
  • the RRC message may be a path switch request message or a measurement report, and the RRC message is sent to the base station by the relay UE.
  • the base station After receiving the RRC message sent by the remote UE, the base station sends an RRC connection reconfiguration message to the remote UE through the relay UE, where the RRC connection reconfiguration message is used to command the remote UE to switch from the indirect path to the direct connection. path.
  • the Remote UE After completing the RRC connection reconfiguration, the Remote UE sends an RRC connection reconfiguration complete message to the base station through the direct connection path.
  • the embodiment of the invention provides a path conversion method, a related device and a system, which can trigger a link conversion of a remote device by a relay terminal, and can be more flexibly adapted to a relay scenario.
  • a path conversion method is provided, which is applied to a first terminal side, and the method includes: the first terminal sending a first message to the first network device.
  • the first message may be used to request that the second terminal switch from the indirect path that communicates with the first network device through the first terminal to the direct path that communicates with the first network device or the second network device.
  • the first message may be used to request to release a link between the first terminal and the second terminal. Then, the first terminal releases the link between the first terminal and the second terminal.
  • the requesting to release the link between the first terminal and the second terminal may include the following two methods:
  • the first type the first terminal sends a first message to the first network device, requesting the first network device to release the link between the first terminal and the second terminal.
  • the second type the first terminal sends a first message to the first network device, and after receiving the response message of the first network device, the first terminal releases the link between the first terminal and the second terminal.
  • the first network device is different from the second network device.
  • the first terminal is the first terminal in the relay communication
  • the second terminal is the second terminal in the relay communication.
  • the implementation manner in which the first terminal releases the link may include the following:
  • the link between the first network device and the second first network device is triggered to be released by the first network device.
  • the first network device sends the first terminal to the first terminal. Sending a third message, triggering the first terminal to release the short-distance link.
  • the short-distance link between the first terminal and the second terminal is triggered to be released by the second terminal.
  • the second terminal after the second terminal receives the configuration information of the link transition sent by the first network device, that is, after the second terminal receives the second message sent by the first network device, the second terminal sends the third terminal to the first terminal.
  • the message triggers the first terminal to release the short-distance link.
  • the third implementation manner is: after the first terminal requests to release the short-distance communication link (that is, the first terminal sends the first message to the first network device), when the first terminal maintains the short-distance link for more than the first time length When the first terminal releases the short-distance link.
  • a second aspect provides a path conversion method, which is applied to a first network device side, where the method includes: receiving, by the first network device, a first message sent by the first terminal.
  • the first message may be used to request that the second terminal switch from the indirect path that communicates with the first network device through the first terminal to the direct path that communicates with the first network device or the second network device.
  • the first message can be used to request release
  • the requesting to release the link between the first terminal and the second terminal may include the following two methods:
  • the first type the first terminal sends a first message to the first network device, requesting the first network device to release the link between the first terminal and the second terminal.
  • the second type the first terminal sends a first message to the first network device, and after receiving the response message of the first network device, the first terminal releases the link between the first terminal and the second terminal.
  • the first network device sends a second message to the second terminal, where the second message is used to configure the second terminal to switch from the indirect path to the direct path.
  • the second message may include at least one of the following: a cell identifier, or random access configuration information, or first indication information, or a first time value.
  • the first indication information may be used to indicate whether the second terminal disconnects the first terminal after performing downlink synchronization on the cell corresponding to the cell identifier.
  • the first time value may be the maximum time allowed by the cell corresponding to the second terminal access cell identifier.
  • a third aspect provides a path conversion method, which is applied to a second terminal side, where the method includes: receiving, by the second terminal, a second message sent by the first network device, and converting from the indirect path according to the second message Go to the direct path.
  • the first network device is different from the second network device.
  • the second message can be used to configure the second terminal to pass the first
  • the indirect path in which the terminal communicates with the first network device is switched to a direct path that communicates with the first network device or the second network device.
  • the second message may include at least one of the following: a cell identifier, or random access configuration information, or first indication information, or a first time value.
  • the first indication information may be used to indicate whether the second terminal disconnects the first terminal after performing downlink synchronization on the cell corresponding to the cell identifier.
  • the first time value may be used to indicate the maximum time allowed by the second terminal to access the cell corresponding to the cell identifier.
  • a fourth aspect provides a path conversion method, which is applied to a first terminal side, where the method includes: the first terminal sends a fourth message to the second terminal.
  • the fourth message is used to instruct the second terminal to switch from the indirect path that communicates with the first network device by using the first terminal to the direct path that communicates with the first network device or the second network device.
  • the fourth message is used to indicate that the link between the first terminal and the second terminal is released. Then, the first terminal releases the link between the first terminal and the second terminal.
  • the first network device is different from the second network device.
  • the fourth message may include at least one of the following: a cell identifier of the serving cell of the first terminal, or configuration information of a public radio resource of the serving cell of the first terminal.
  • the implementation manner of releasing the link by the first terminal may include the following:
  • the first implementation manner the short-distance link between the first terminal and the second terminal is triggered to be released by the first network device.
  • the first network device configures the link transition of the second terminal (that is, the first network device sends the sixth message to the second terminal)
  • the first network device sends a seventh message to the first terminal, triggering the first A terminal releases a short-range link.
  • the short-distance link between the first terminal and the second terminal is triggered to be released by the second terminal.
  • the second terminal after the second terminal receives the configuration information of the link transition sent by the first network device, that is, after the second terminal receives the sixth message sent by the first network device, the second terminal sends the seventh terminal to the first terminal.
  • the message triggers the first terminal to release the short-distance link.
  • the third implementation manner is: after the first terminal notifies the release of the short-range communication link (that is, the fourth message is sent to the second terminal), when the first terminal keeps the short-distance link for more than the specified time threshold, the first terminal Release the short-range link.
  • the first terminal can be set according to actual needs, and is not limited herein.
  • the first terminal may directly perform the release of the short-distance link after notifying the release of the short-distance link, without triggering the condition.
  • a fifth aspect provides a path conversion method, which is applied to a second terminal side, where the method includes: receiving, by the second terminal, a fourth message sent by the first terminal, and converting from the indirect path to the direct according to the fourth message. Even the path.
  • the fourth message may be used to instruct the second terminal to switch from the indirect path that communicates with the first network device through the first terminal to the direct path that communicates with the first network device or the second network device.
  • the fourth message may be used to indicate that the link between the first terminal and the second terminal is released.
  • the first network device is different from the second network device.
  • the second terminal may further send a fifth message to the first network device for requesting a transition from the indirect path to the direct path. Then, the second terminal may receive the sixth message sent by the first network device.
  • the sixth message may include at least one of the following: a cell identifier, or random access configuration information, or first indication information, or a first time value, configured to configure the second terminal to switch from the indirect path to the direct path.
  • the first indication information is used to indicate whether the second terminal disconnects the first terminal after performing downlink synchronization on the cell corresponding to the cell identifier; the first time value is a cell corresponding to the second terminal access cell identifier. The maximum time allowed.
  • the second terminal may also trigger the RRC connection re-establishment process after receiving the fourth message.
  • the second terminal may also access the serving cell of the first terminal, and send the terminal device identifier to the first network device.
  • the terminal device identifier may be a C-RNTI of the second terminal, or the terminal device identifier may be a C-RNTI of the first terminal and a local identifier of the second terminal.
  • the terminal device identifier may be carried in the fourth message.
  • the terminal device identifier is sent by the first terminal to the second terminal before sending the fourth message.
  • the path conversion method described in the first aspect, the second aspect, and the third aspect is implemented, and the first terminal directly notifies the second terminal to perform path conversion, and the path conversion is configured by the first network device, so that the first terminal can be quickly implemented.
  • the trigger path conversion process is implemented, and the first terminal directly notifies the second terminal to perform path conversion, and the path conversion is configured by the first network device, so that the first terminal can be quickly implemented.
  • the application provides a terminal, which is the first terminal in the foregoing first aspect, and may include multiple functional modules for performing the method provided by the first aspect, or the first aspect may The method provided by any of the embodiments.
  • the application provides a network device, where the network device is the first network device in the foregoing second aspect, and may include multiple function modules, for performing the method provided in the second aspect, or A method provided by any of the possible embodiments of the two aspects.
  • the application provides a terminal, which is the second terminal in the foregoing third aspect, and may include multiple functional modules for performing the method provided by the third aspect, or the third aspect may The method provided by any of the embodiments.
  • the application provides a terminal, which is the first terminal in the foregoing fourth aspect, and may include multiple functional modules for performing the method provided by the fourth aspect, or the fourth aspect may The method provided by any of the embodiments.
  • the application provides a terminal, which is the second terminal in the foregoing tenth aspect, and may include multiple functional modules for performing the method provided by the tenth aspect, or the tenth aspect The method provided by any of the embodiments.
  • the present application provides a terminal for performing the path conversion method described in the first aspect.
  • the terminal can include a memory and a processor, transceiver coupled to the memory, wherein the transceiver is for communicating with other communication devices, such as network devices.
  • the memory is for storing implementation code of the path conversion method described in the first aspect
  • the processor is for executing program code stored in the memory, ie performing the method provided by the first aspect, or any one of the possible implementations of the first aspect The method provided.
  • the present application provides a network device for performing the path conversion method described in the second aspect.
  • the network device can include: a memory and a processor coupled to the memory, the transceiver, wherein: the transceiver is for use with Communication equipment (such as terminals) communicate.
  • the memory is for storing the implementation code of the resource allocation method described in the second aspect
  • the processor is configured to execute the program code stored in the memory, that is, to perform the method provided by the second aspect, or any one of the possible implementation manners of the second aspect The method provided.
  • the present application provides a terminal for performing the path conversion method described in the third aspect.
  • the terminal can include a memory and a processor, transceiver coupled to the memory, wherein the transceiver is for communicating with other communication devices, such as network devices.
  • the memory is for storing implementation code of the path conversion method described in the third aspect
  • the processor is configured to execute the program code stored in the memory, that is, to perform the method provided by the third aspect, or any one of the possible implementation manners of the third aspect The method provided.
  • the present application provides a terminal for performing the path conversion method described in the fourth aspect.
  • the terminal can include a memory and a processor, transceiver coupled to the memory, wherein the transceiver is for communicating with other communication devices, such as network devices.
  • the memory is for storing implementation code of the path conversion method described in the fourth aspect
  • the processor is configured to execute the program code stored in the memory, that is, to perform the method provided by the fourth aspect, or any one of the possible implementation manners of the fourth aspect The method provided.
  • the present application provides a terminal for performing the path conversion method described in the fifth aspect.
  • the terminal can include a memory and a processor, transceiver coupled to the memory, wherein the transceiver is for communicating with other communication devices, such as network devices.
  • the memory is for storing implementation code of the path conversion method described in the fifth aspect
  • the processor is configured to execute the program code stored in the memory, that is, to perform the method provided by the fifth aspect, or any one of the possible implementation manners of the fifth aspect The method provided.
  • the present application provides a wireless communication system, including a first terminal, a second terminal, and a network device, where: the first terminal may be the terminal described in the foregoing sixth aspect, and the second terminal may be the foregoing eighth aspect.
  • the terminal, the network device may be the network device described in the seventh aspect above.
  • the first terminal may also be the terminal described in the foregoing eleventh aspect
  • the second terminal may also be the terminal described in the thirteenth aspect
  • the network device may be the network device described in the twelfth aspect.
  • the first terminal may also be the terminal described in the foregoing ninth aspect
  • the second terminal may also be the terminal described in the foregoing tenth aspect.
  • the first terminal may also be the terminal described in the fourteenth aspect
  • the second terminal may also be the terminal described in the fifteenth aspect.
  • a computer readable storage medium storing the resource provided by implementing the resource allocation method provided by the first aspect, or any one of the possible implementation manners of the first aspect
  • a program code of a distribution method the program code comprising an execution instruction of a resource allocation method provided by running the resource allocation method provided by the first aspect, or any one of the possible implementations of the first aspect.
  • a computer readable storage medium storing a resource provided by implementing the resource allocation method provided by the third aspect, or any one of the possible implementation manners of the third aspect
  • the program code of the method comprising the resource allocation method provided by the third aspect, or the execution instruction of the resource allocation method provided by any one of the possible implementations of the third aspect.
  • a computer readable storage medium storing the resource provided by implementing the resource allocation method provided by the fourth aspect, or any one of the possible implementation manners of the fourth aspect
  • a program code of a distribution method the program code comprising an execution instruction of a resource allocation method provided by running the resource allocation method provided by the fourth aspect, or any one of the possible implementations of the fourth aspect.
  • a computer readable storage medium storing the resource allocation method provided by implementing the fifth aspect, or any one of the possible implementation manners of the fifth aspect
  • a program code of a resource allocation method the program code comprising an execution instruction of a resource allocation method provided by running the resource allocation method provided by the fifth aspect, or any one of the possible implementations of the fifth aspect.
  • FIG. 1A-1B illustrate two path switching scenarios in a relay system to which the present application relates
  • FIG. 3 is a schematic structural diagram of a terminal provided by the present application.
  • FIG. 4 is a schematic structural diagram of a network device provided by the present application.
  • FIG. 5 is a schematic flowchart diagram of a path conversion method provided by the present application.
  • FIG. 6 is a schematic flowchart diagram of another path conversion method provided by the present application.
  • FIG. 7 is a schematic flowchart diagram of still another path conversion method provided by the present application.
  • FIG. 8 is a schematic flowchart diagram of still another path conversion method provided by the present application.
  • FIG. 9 is a schematic flowchart diagram of still another path conversion method provided by the present application.
  • FIG. 10 is a schematic flowchart diagram of still another path conversion method provided by the present application.
  • FIG. 11 is a schematic flowchart diagram of still another path conversion method provided by the present application.
  • FIG. 12 is a schematic flowchart diagram of still another path conversion method provided by the present application.
  • FIG. 13 is a schematic flowchart diagram of still another path conversion method provided by the present application.
  • FIG. 14 is a schematic structural diagram of a relay terminal, a remote terminal, a network device, and a wireless communication system provided by the present application.
  • FIG. 2 shows a wireless communication system to which the present application relates.
  • the wireless communication system may be a Long Term Evolution (LTE) system, or may be a future evolution of the 5th Generation (5G) system, a new air interface (NR) system, and machine-to-machine communication ( Machine to Machine, M2M) system, etc.
  • LTE Long Term Evolution
  • 5G 5th Generation
  • NR new air interface
  • M2M machine-to-machine communication
  • the wireless communication system 100 can include a network device 101, a remote terminal 105, and a relay device 103.
  • One relay device 103 can be connected to one or more remote terminals 105. among them:
  • the network device 101 can be a base station, and the base station can be used for communicating with one or more terminals, and can also be used for One or more base stations having partial terminal functions communicate (such as communication between a macro base station and a micro base station, such as an access point).
  • the base station may be a Base Transceiver Station (BTS) in a Time Division Synchronous Code Division Multiple Access (TD-SCDMA) system, or may be an evolved base station in an LTE system (Evolutional Node B). , eNB), and the base station gNB in the 5G system, the new air interface (NR) system.
  • the base station may also be an Access Point (AP), a TransNode (Trans TRP), a Central Unit (CU), or other network entity, and may include some or all of the functions of the above network entities. .
  • the remote terminal 105 can be distributed throughout the wireless communication system 100, either stationary or mobile.
  • the remote terminal 105 may be a smart wearable device, a mobile device, a mobile station, a mobile unit, an M2M terminal, a wireless unit, a remote unit, a user agent, a mobile client. And so on.
  • the relay device 103 may contain two physical layer entities. One of the entities is used to communicate with its subordinate users (ie, the remote terminal 105 that accesses the relay device 103). Another entity has a user function (ie, a terminal function) for communication by the network device 101. In a specific implementation, the relay device 103 may be a relay terminal.
  • the relay device 103 may also be a communication entity such as a Relay Transceiver Node (TRP), a Customer Premise Equipment (CPE), a relay transceiver, and a relay agent.
  • TRP Relay Transceiver Node
  • CPE Customer Premise Equipment
  • a sidelink refers to a short-distance link between the relay device 103 and the remote terminal 105, including an uplink (UL) or a downlink (DL) side chain. road.
  • a backhaul link refers to a radio link between the network device 101 and the relay device 103, including an uplink (UL) or a downlink (DL) backhaul link.
  • the relay device 103 and the remote terminal 105 may be other types of short-distance links, such as any one of WLAN or Bluetooth.
  • the relay device 103 between the network device 101 and the remote terminal 105 can be used to forward wireless signals between the network device 101 and the remote terminal 105. Specifically, during downlink transmission, the relay device 103 is responsible for forwarding the wireless signal transmitted by the network device 101, and finally transmitting the wireless signal to the remote terminal 105. During uplink transmission, the relay device 103 is responsible for forwarding the wireless signal transmitted by the remote terminal 105, and finally transmitting the wireless signal to the network device 101.
  • the relay device 103 needs to actively trigger the remote terminal 105 to perform path conversion, that is, the remote terminal 105 switches from the indirect path that communicates with the network device 101 through the relay device 103 to the network device 101.
  • the direct path of communication For example, when the relay device 103 needs to initiate a call of a circuit switch (CS), the relay device 103 needs to perform Circuit Switch Fallback (CSFB) to access the 2G or 3G network.
  • CSFB Circuit Switch Fallback
  • the relay device 103 accesses the 2G or 3G network, it will no longer be able to provide the relay service to the remote terminal 105.
  • the relay device 103 may no longer provide the relay service to the remote terminal 105.
  • the relay device 103 also needs to actively trigger the remote terminal 105 to perform path switching.
  • the wireless communication system 100 shown in FIG. 2 is only for the purpose of more clearly explaining the technical solutions of the present application, and does not constitute a limitation of the present application.
  • Those skilled in the art may know that with the evolution of the network architecture and new services, The appearance of the scenario, the technical solution provided by the present application is equally applicable to similar technical problems.
  • FIG. 3 illustrates a terminal 200 provided by some embodiments of the present application.
  • the terminal 200 may implement a remote terminal (such as the remote terminal 105 in FIG. 2) involved in the cost application, and may also implement a relay device (such as the relay device 103 in FIG. 2) involved in the cost application.
  • the terminal 200 may include: one or more terminal processors 201, a memory 202, a communication interface 203, a receiver 205, a transmitter 206, a coupler 207, an antenna 208, a user interface 202, and an input and output module. (including audio input and output module 210, key input module 211, display 212, etc.).
  • FIG. 3 is exemplified by a bus connection. among them:
  • Communication interface 203 can be used by terminal 200 to communicate with other communication devices, such as other terminals or network devices.
  • the communication interface 203 may be a Long Term Evolution (LTE) (4G) communication interface, or may be a 5G or a future communication interface of a new air interface.
  • LTE Long Term Evolution
  • 5G Fifth Generation
  • the terminal 200 may be configured with a wired communication interface 203, such as a Local Access Network (LAN) interface.
  • LAN Local Access Network
  • Transmitter 206 can be used to perform transmission processing, such as signal modulation, on signals output by terminal processor 201.
  • Receiver 205 can be used to perform reception processing, such as signal demodulation, on the mobile communication signals received by antenna 208.
  • transmitter 206 and receiver 205 can be viewed as a wireless modem.
  • the number of the transmitter 206 and the receiver 205 may each be one or more.
  • the antenna 208 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line.
  • the coupler 207 is configured to divide the mobile communication signal received by the antenna 208 into multiple channels and distribute it to a plurality of receivers 205.
  • the terminal 200 can be configured with two sets of transceiver devices, wherein one set of transceiver devices is used for the remote terminal (such as the remote terminal 105 in FIG. 2) to access the link of the terminal 200. Another set of transceivers is used for the link of the terminal 200 to access network devices (such as the network device 101 in FIG. 2).
  • the two transceivers can have the same or different transmission and reception characteristics. For example, the corresponding antenna ports of the two transceivers have or do not have Quasi Co-location (QCL) characteristics.
  • QCL Quasi Co-location
  • the terminal 200 may also include other communication components such as a GPS module, a Bluetooth module, a Wireless Fidelity (Wi-Fi) module, and the like. Not limited to the above-described wireless communication signals, the terminal 200 can also support other wireless communication signals such as satellite signals, short-wave signals, and the like. Not limited to wireless communication, the terminal 200 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.
  • a wired network interface such as a LAN interface
  • the input and output module can be used to implement the interaction between the terminal 200 and the user/external environment, and can include the audio input and output module 210, the key input module 211, the display 212, and the like. Specifically, the input and output module may further include: a camera, a touch screen, a sensor, and the like. The input and output modules communicate with the terminal processor 201 through the user interface 209.
  • Memory 202 is coupled to terminal processor 201 for storing various software programs and/or sets of instructions.
  • memory 202 can include high speed random access memory, and can also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory 202 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as ANDROID, IOS, WINDOWS, or LINUX.
  • the memory 202 can also store a network communication program that can be used to communicate with one or more additional devices, one or more terminal devices, one or more network devices.
  • the memory 202 can also store a user interface program, which can realistically display the content of the application through a graphical operation interface, and receive user control operations on the application through input controls such as menus, dialog boxes, and keys. .
  • the memory 202 can be used to store an implementation of the path conversion method provided by one or more embodiments of the present application on the terminal 200 side.
  • the path conversion method provided by one or more embodiments of the present application please refer to the subsequent embodiments.
  • Terminal processor 201 can be used to read and execute computer readable instructions. Specifically, the terminal processor 201 can be used to invoke a program stored in the memory 212, such as an implementation program of the resource allocation method provided by one or more embodiments of the present application on the terminal 200 side, and execute instructions included in the program.
  • a program stored in the memory 212 such as an implementation program of the resource allocation method provided by one or more embodiments of the present application on the terminal 200 side, and execute instructions included in the program.
  • the terminal 200 can be the terminal 103 in the wireless communication system 100 shown in FIG. 5, and can be implemented as a mobile device, a mobile station, a mobile unit, a wireless unit, a remote unit, and a user agent. , mobile client and more.
  • the terminal 200 shown in FIG. 3 is only one implementation manner of the embodiment of the present application. In an actual application, the terminal 200 may further include more or less components, which are not limited herein.
  • network device 300 can include one or more network device processors 301, memory 302, communication interface 303, transmitter 305, receiver 306, coupler 307, and antenna 308. These components can be connected via bus 304 or other types, and FIG. 4 is exemplified by a bus connection. among them:
  • Communication interface 303 can be used by network device 300 to communicate with other communication devices, such as terminal devices or other network devices.
  • the communication interface 303 may be a Long Term Evolution (LTE) (4G) communication interface, or may be a 5G or a future communication interface of a new air interface.
  • LTE Long Term Evolution
  • the network device 300 may also be configured with a wired communication interface 303 to support wired communication.
  • the backhaul link between one network device 300 and other network devices 300 may be a wired communication connection.
  • Transmitter 305 can be used to perform transmission processing, such as signal modulation, on signals output by network device processor 301.
  • Receiver 306 can be used to perform reception processing on the mobile communication signals received by antenna 308. For example, signal demodulation.
  • transmitter 305 and receiver 306 can be viewed as a wireless modem. In the network device 300, the number of the transmitter 305 and the receiver 306 may each be one or more.
  • the antenna 308 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line.
  • Coupler 307 can be used to divide the mobile pass signal into multiple channels and distribute it to multiple receivers 306.
  • Memory 302 is coupled to network device processor 301 for storing various software programs and/or sets of instructions.
  • memory 302 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory 302 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as uCOS, VxWorks, or RTLinux.
  • the memory 302 can also store a network communication program that can be used to communicate with one or more additional devices, one or more terminal devices, one or more network devices.
  • the network device processor 301 can be used to perform wireless channel management, implement call and communication link establishment and teardown, and provide cell handover control and the like for users in the control area.
  • the network device processor 301 may include: an Administration Module/Communication Module (AM/CM) (a center for voice exchange and information exchange), and a Basic Module (BM) (for Complete call processing, signaling processing, radio resource management, radio link management and circuit maintenance functions), code conversion and sub-multiplexer (Transcoder and SubMultiplexer, TCSM) (used to perform multiplexing demultiplexing and code conversion functions) and so on.
  • AM/CM Administration Module/Communication Module
  • BM Basic Module
  • TCSM code conversion and sub-multiplexer
  • the network device processor 301 can be used to read and execute computer readable instructions. Specifically, the network device processor 301 can be used to invoke a program stored in the memory 302, such as the path conversion method provided by one or more embodiments of the present application, on the network device 300 side, and execute the instructions included in the program. .
  • the network device 300 can be the base station 101 in the wireless communication system 100 shown in FIG. 5, and can be implemented as a base transceiver station, a wireless transceiver, a basic service set (BSS), and an extended service set (ESS). NodeB, eNodeB, access point or TRP, etc.
  • the network device 300 shown in FIG. 4 is only one implementation of the embodiment of the present application. In actual applications, the network device 300 may further include more or fewer components, which are not limited herein.
  • the present application provides a path conversion method.
  • the main inventive principles involved in the present application may include: in relay communication, if the relay device can no longer provide a relay service for the remote terminal, the relay device can trigger the remote terminal to communicate with the network device through the relay device.
  • the indirect path is switched to a direct path that communicates directly with the network device and releases the short-distance link between the relay terminal and the remote terminal.
  • the relay device can promptly and quickly trigger the path conversion of the remote terminal according to its own situation, and even realize the path conversion in the case where the side link does not interrupt the data communication, thereby ensuring the remote terminal and the network device. Data communication between the two is not interrupted.
  • the scenario in which the relay device can no longer provide the relay service for the remote terminal may include, but is not limited to, the scenario described in the following example: For example, when the relay device 103 needs to initiate a call of the circuit domain (CS), the relay device 103 needs to perform Circuit domain fallback (CSFB), access to 2G or 3G networks. When the relay device 103 accesses the 2G or 3G network, it will no longer be able to provide the relay service to the remote terminal 105. For another example, when the power of the relay device 103 is insufficient, the relay device 103 may no longer provide the relay service to the remote terminal 105.
  • CS Circuit domain fallback
  • Relay the relay device
  • Remote the remote terminal
  • Solution 1 The Relay requests the network device to trigger Remote to perform path conversion, and the network device configures the path conversion.
  • Solution 2 Relay directly informs Remote to perform path conversion.
  • the relay can release the short-distance link after the Remote switch is switched to the direct connection path, and the service continuity of the Remote in the process of converting from the indirect path to the direct path can be implemented.
  • the Relay directly informs the Remote to perform path switching, which can reduce the time required for the Relay to release the short-distance link.
  • the Relay may be referred to as a first terminal, and the Remote may be referred to as a second terminal.
  • the relay terminal is not limited to the relay terminal.
  • the relay may also be a relay micro base station, a relay transceiver, or the like.
  • FIG. 5 is a schematic flowchart diagram of a path conversion method provided by the present application. Expand below:
  • the upper layer of the relay terminal triggers a short-distance link between the relay terminal and the remote terminal.
  • the relay device and the remote terminal may also be other forms of short-distance links, such as any one of WLAN or Bluetooth.
  • the relay terminal sends a first message to the network device, where the first message is used to request the network device to convert the remote terminal from the indirect path to the direct path, or to request to release the relay terminal and the remote end.
  • the requesting to release the link between the first terminal and the second terminal may include the following two methods:
  • the first type the first terminal sends a first message to the first network device, requesting the first network device to release the link between the first terminal and the second terminal.
  • the second type the first terminal sends a first message to the first network device, and after receiving the response message of the first network device, the first terminal releases the link between the first terminal and the second terminal.
  • the first message may be an RRC message.
  • the first message may include a reason why the relay terminal releases the short-distance link.
  • the relay terminal needs to do circuit domain fallback (CSFB), or the power of the relay terminal is insufficient.
  • CSFB circuit domain fallback
  • the example is only some embodiments provided by the present application. In actual applications, the reason why other relay terminals release the short-distance link may also be included, which is not limited herein.
  • S102 The network device sends a second message to the remote terminal connected to the relay terminal, where the second message is used to configure the remote terminal to switch from the indirect path to the direct path.
  • the second message may be an RRC connection reconfiguration message.
  • the second message includes at least one of the following: a cell identifier, or random access configuration information, or first indication information, or a first time value. among them:
  • the foregoing cell identifier may be an identifier of a cell that is accessed after the remote terminal transits to the direct connection path.
  • the cell identifier may be a physical cell identity (PCI) of the cell, or the cell identifier may be a cell identity capable of uniquely identifying a cell in a public land mobile network (PLMN). Or the cell identifier may be a cell global identity (CGI) that is globally unique.
  • PCI physical cell identity
  • PLMN public land mobile network
  • CGI cell global identity
  • the configuration information of the random access may be resource configuration information when the remote terminal initiates random access in the cell, and may include a preamble configuration of random access and a physical random access channel configuration.
  • the first indication information may be used to indicate whether the remote terminal disconnects from the relay terminal after performing downlink synchronization with the cell corresponding to the cell identifier.
  • the first time value may be the maximum time allowed by the remote terminal to access the cell corresponding to the cell identifier. If the time is exceeded, the remote terminal may be considered to have failed to access the cell.
  • the remote terminal may perform a conversion from the indirect path to the direct path. Moreover, the remote terminal may also start a first timer, where the length of the first timer is equal to the first time value in the second message, and is used to limit the maximum time that the remote terminal accesses the cell corresponding to the cell identifier. If the remote terminal still does not access the cell when the first timer expires, the cell access may be considered to be unsuccessful. If this happens, the remote terminal needs to trigger the RRC connection re-establishment process.
  • the remote terminal can perform the conversion from the indirect path to the direct path in the following three manners:
  • the remote terminal may continue to maintain the connection with the relay terminal, that is, may continue to pass the relay terminal. Data communication with network devices. After the downlink synchronization is completed in the cell corresponding to the cell identifier, the remote terminal The connection with the relay terminal can be disconnected, the data communication between the relay terminal and the network device is stopped, and the data is transmitted and received through the direct connection path with the network device.
  • the remote terminal may disconnect from the relay terminal and stop performing data through the relay terminal and the network device. Communication. After that, the remote terminal may start a downlink synchronization process and a random access procedure of the cell corresponding to the cell identifier.
  • Manner 3 If the first message includes the first indication information, and the first indication information indicates that the remote terminal disconnects from the relay terminal after performing downlink synchronization with the cell, the remote terminal may follow the manner. One performs path conversion. Conversely, the remote terminal can perform path conversion according to mode two.
  • One possible special case is that if the remote terminal does not receive the second message, the relay terminal has disconnected the link with the remote terminal. In this case, when the remote terminal does not detect the discovery message sent by the relay terminal, the remote terminal considers that the link between the terminal and the relay terminal fails, and the remote terminal triggers the RRC connection re-establishment process.
  • the remote terminal may access the cell corresponding to the cell identifier by using a random access procedure, and after the access is successful, may send an RRC connection reconfiguration complete message to the network device.
  • the network device may send a third message to the relay terminal, where the third message may be used to instruct the relay terminal to release the short-distance link.
  • the third message may include:
  • the third message may be a newly defined RRC message.
  • the third message may be an RRC Connection Reconfiguration (RRCConnectionReconfiguration) message.
  • the RRC connection reconfiguration message may include an indication information, which may be used to instruct the relay terminal to release the short-range link.
  • the third message may be an RRC connection reconfiguration message.
  • the third message may be used to configure the relay terminal to release all the side-link bearers, thereby implicitly configuring the relay terminal to release the short-distance link.
  • the network device may trigger the relay terminal to release the short-distance link in the following two scenarios, that is, send the third message to the relay terminal.
  • the first triggering scenario the network device determines that all the remote terminals under the relay terminal have successfully received the second message.
  • condition for determining that the remote terminal has successfully received the second message may include any one of the following ways:
  • the network device receives the HARQ ACK or RLC ACK sent by the remote terminal for the second message
  • the network device receives a random access preamble (preamble) sent by the remote terminal;
  • the network device receives the RRC connection reconfiguration complete message sent by the remote terminal.
  • the second triggering scenario the network device determines that the remote terminal fails to access the cell.
  • the determining condition that the remote terminal accesses the cell fails may include: the network device does not receive the RRC connection reconfiguration complete message sent by the remote terminal within a time limit of the first time value in the second message.
  • the relay terminal may release the short-distance link.
  • the specific implementation of releasing the short-distance link may include the following aspects:
  • the relay terminal releases the side-to-side bearer between all the remote terminals, including releasing the radio link control protocol (RLC) entity and the logical channel carried by all the side links;
  • RLC radio link control protocol
  • the relay terminal requests the network device to trigger the path conversion of the remote terminal, and the network device configures the path conversion of the remote terminal (such as the cell in the second message). Identification, Random Access Configuration, etc.)
  • the release of the short-range link between the relay terminal and the remote terminal is triggered by the network device (via the third message).
  • FIG. 6 is a schematic flowchart diagram of another path conversion method provided by the present application. Expand below:
  • the upper layer of the relay terminal triggers a short-distance link between the relay terminal and the remote terminal.
  • the relay device and the remote terminal may be other forms of short-distance links, such as any one of WLAN or Bluetooth.
  • the relay terminal sends a first message to the network device, where the first message is used to request the network device to convert the remote terminal from the indirect path to the direct path, or to request to release the relay terminal and the remote end.
  • the requesting to release the link between the first terminal and the second terminal may include the following two methods:
  • the first type the first terminal sends a first message to the first network device, requesting the first network device to release the link between the first terminal and the second terminal.
  • the second type the first terminal sends a first message to the first network device, and after receiving the response message of the first network device, the first terminal releases the link between the first terminal and the second terminal.
  • the first message may be an RRC message.
  • the first message may include a reason why the relay terminal releases the short-distance link.
  • the relay terminal needs to do circuit domain fallback (CSFB), or the power of the relay terminal is insufficient.
  • CSFB circuit domain fallback
  • the example is only some embodiments provided by the present application. In actual applications, the reason why other relay terminals release the short-distance link may also be included, which is not limited herein.
  • the network device sends a second message to the remote terminal connected to the relay terminal, where the second message is used to configure the remote terminal to switch from the indirect path to the direct path.
  • the second message may be an RRC connection reconfiguration message.
  • the second message includes at least one of the following: a cell identity, or random access configuration information, or first indication information, or a first time value. among them:
  • the foregoing cell identifier may be an identifier of a cell that is accessed after the remote terminal transits to the direct connection path.
  • the cell identifier may be a physical cell identity (PCI) of the cell, or the cell identifier may be a cell identity capable of uniquely identifying a cell in a public land mobile network (PLMN). Or the cell identifier may be a cell global identity (CGI) that is globally unique.
  • PCI physical cell identity
  • PLMN public land mobile network
  • CGI cell global identity
  • the configuration information of the random access may be resource configuration information when the remote terminal initiates random access in the cell, and may include a preamble configuration of random access and a physical random access channel configuration.
  • the foregoing first indication information may be used to indicate whether the remote terminal performs downlink synchronization with the cell corresponding to the cell identifier. Then disconnect the relay terminal.
  • the first time value may be the maximum time allowed by the remote terminal to access the cell corresponding to the cell identifier. If the time is exceeded, the remote terminal may be considered to have failed to access the cell.
  • the remote terminal may perform a transition from the indirect path to the direct path and send the third message to the relay terminal.
  • the third message may be used to instruct the relay terminal to release the short-distance link between the relay terminal and the remote terminal.
  • the remote terminal may also start a first timer, where the length of the first timer is equal to the first time value in the second message, and is used to restrict the remote terminal from accessing the corresponding cell identifier. The longest time in the community. If the remote terminal still does not access the cell when the first timer expires, the cell access may be considered to have failed. If this happens, the remote terminal triggers the RRC connection re-establishment process.
  • the remote terminal triggers the relay terminal to release the short-distance link (that is, sends the third message) and the time sequence in which the remote terminal performs the transition from the indirect path to the direct path, including the following three modes:
  • the remote terminal may continue to maintain the connection with the relay terminal, that is, may continue to pass the relay terminal. Data communication with network devices. After completing the downlink synchronization of the cell corresponding to the cell identifier, the remote terminal may send a third message to the relay terminal, trigger the relay terminal to release the short-distance link, and stop the data communication with the network device through the relay terminal. Data communication to the network device to the direct connection path.
  • the remote terminal may send a third message to the relay terminal to trigger disconnection from the relay terminal, after the second message is received, whether the first message is included in the second message. Stop data communication through the relay terminal and network device. After that, the remote terminal may start a downlink synchronization process and a random access procedure of the cell corresponding to the cell identifier.
  • Manner 3 If the first message includes the first indication information, and the first indication information indicates that the remote terminal disconnects from the relay terminal after performing downlink synchronization with the cell, the remote terminal may follow the manner. One performs path conversion. Conversely, the remote terminal can perform path conversion according to mode two.
  • One possible special case is that if the remote terminal does not receive the second message, the relay terminal has disconnected the link with the remote terminal. In this case, when the remote terminal does not detect the discovery message sent by the relay terminal, the remote terminal considers that the link between the terminal and the relay terminal fails, and the remote terminal triggers the RRC connection re-establishment process.
  • the remote terminal performs downlink synchronization with the cell corresponding to the cell identifier.
  • the relay terminal After receiving the third message sent by the remote terminal, the relay terminal releases the short-distance link between the relay terminal and the remote terminal.
  • the specific implementation of releasing the short-distance link may include the following aspects:
  • the relay terminal releases the side-to-side bearer between all the remote terminals, including releasing the radio link control protocol (RLC) entity and the logical channel carried by all the side links;
  • RLC radio link control protocol
  • the remote terminal performs a random access procedure on the cell corresponding to the cell identifier, and sends an RRC connection reconfiguration complete message to the network device after the cell access is completed.
  • the relay terminal requests the network device to trigger the path conversion of the remote terminal, and the network device configures the path conversion of the remote terminal (such as the cell in the second message). Identification, random access configuration, etc.).
  • the release of the short-range link between the relay terminal and the remote terminal is triggered by the remote terminal (via the third message).
  • FIG. 7 is a schematic flowchart diagram of still another path conversion method provided by the present application. Expand below:
  • the upper layer of the relay terminal triggers a short-distance link between the relay terminal and the remote terminal.
  • the relay device and the remote terminal may be other forms of short-distance links, such as any one of WLAN or Bluetooth.
  • the relay terminal sends a first message to the network device, where the first message is used to request the network device to convert the remote terminal from the indirect path to the direct path, or to request to release the relay terminal and the remote end.
  • the requesting to release the link between the first terminal and the second terminal may include the following two methods:
  • the first type the first terminal sends a first message to the first network device, requesting the first network device to release the link between the first terminal and the second terminal.
  • the second type the first terminal sends a first message to the first network device, and after receiving the response message of the first network device, the first terminal releases the link between the first terminal and the second terminal.
  • the first message may be an RRC message.
  • the first message may include a reason why the relay terminal releases the short-distance link.
  • the relay terminal needs to do circuit domain fallback (CSFB), or the power of the relay terminal is insufficient.
  • CSFB circuit domain fallback
  • the example is only some embodiments provided by the present application. In actual applications, the reason why other relay terminals release the short-distance link may also be included, which is not limited herein.
  • S302 The network device sends a second message to the remote terminal connected to the relay terminal, where the second message is used to configure the remote terminal to switch from the indirect path to the direct path.
  • the second message may be an RRC connection reconfiguration message.
  • the second message includes at least one of the following: a cell identity, or random access configuration information, or first indication information, or a first time value.
  • a cell identity or random access configuration information
  • first indication information or a first time value.
  • the relay terminal may start a first timer, where the length of the first timer is equal to the first time value in the second message, and is used to indicate that the relay terminal releases the short The time from the link. Once the first timer expires, the relay terminal can release the short-range link.
  • the remote terminal performs downlink synchronization with the cell corresponding to the cell identifier.
  • Steps 303 and 304 have no prioritized sequence of time.
  • the specific implementation of releasing the short-distance link may include the following aspects:
  • the relay terminal releases the side-to-side bearer between all the remote terminals, including releasing the radio link control protocol (RLC) entity and the logical channel carried by all the side links;
  • RLC radio link control protocol
  • the remote terminal performs a random access procedure on the cell corresponding to the cell identifier, and sends an RRC connection reconfiguration complete message to the network device after the cell access is completed.
  • S306 may occur before S305, and S306 may also occur after S305.
  • the sequence between the two steps may depend on the time required for the remote terminal to perform cell synchronization and the size of the first time value. limit.
  • the first time value may be appropriately set to a larger value, so that the remote terminal can successfully connect before the first timer expires. Enter the cell and complete the RRC reconfiguration process.
  • One possible special case is that if the remote terminal does not receive the second message, the relay terminal has disconnected the link with the remote terminal. In this case, when the remote terminal does not detect the discovery message sent by the relay terminal, the remote terminal considers that the link between the terminal and the relay terminal fails, and the remote terminal triggers the RRC connection re-establishment process.
  • the relay terminal requests the network device to trigger the path conversion of the remote terminal, and the network device configures the path conversion of the remote terminal (such as the cell in the second message). Identification, random access configuration, etc.).
  • the release of the short-range link between the relay terminal and the remote terminal is triggered by the relay terminal itself (by the first timer).
  • FIG. 8 is a schematic flowchart diagram of still another path conversion method provided by the present application. Expand below:
  • the upper layer of the relay terminal triggers releasing a short-distance link between the relay terminal and the remote terminal.
  • the relay device and the remote terminal may be other forms of short-distance links, such as any one of WLAN or Bluetooth.
  • the relay terminal sends a fourth message to the remote terminal, where the fourth message is used to notify the relay terminal that the short-distance link is to be released, thereby instructing the remote terminal to switch from the indirect path to the direct connection path.
  • the fourth message may be implemented as, but not limited to, PC5 signaling.
  • the fourth message may include a reason why the relay terminal releases the short-distance link.
  • the relay terminal needs to do circuit domain fallback (CSFB), or the power of the relay terminal is insufficient.
  • CSFB circuit domain fallback
  • the example is only some embodiments provided by the present application. In actual applications, the reason why other relay terminals release the short-distance link may also be included, which is not limited herein.
  • the remote terminal After receiving the fourth message, the remote terminal triggers a transition from the indirect path to the direct path.
  • One possible special case is that if the remote terminal does not receive the second message, the relay terminal has disconnected the link with the remote terminal. In this case, when the remote terminal does not detect the discovery message sent by the relay terminal, the remote terminal considers that the link between the terminal and the relay terminal fails, and the remote terminal triggers the RRC connection re-establishment process.
  • the remote terminal sends a fifth message to the network device, where the fifth message is used to request a transition from the indirect path to the direct path.
  • the fifth message may include a reason why the relay terminal releases the short-distance link. Further, the fifth message can be returned The link quality of the short-distance link between the remote terminal and the relay terminal may be included.
  • S404 The network device sends a sixth message to the remote terminal, where the sixth message is used to configure the remote terminal to switch from the indirect path to the direct path.
  • the sixth message may be an RRC connection reconfiguration message.
  • the sixth message includes at least one of the following: a cell identifier, or random access configuration information, or first indication information, or a first time value.
  • the sixth message is equivalent to the second message in the embodiment of FIG. 5-7.
  • the remote terminal may perform a transition from the indirect path to the direct path and send the seventh message to the relay terminal.
  • the seventh message is equivalent to the third message in the embodiment of FIG. 6, and can be used to instruct the relay terminal to release the short-distance link between the relay terminal and the remote terminal.
  • the remote terminal may also start a first timer, where the length of the first timer is equal to the first time value in the second message, and is used to restrict the remote terminal from accessing the corresponding cell identifier. The longest time in the community. If the remote terminal still does not access the cell when the first timer expires, the cell access may be considered to have failed. If this happens, the remote terminal triggers the RRC connection re-establishment process.
  • the remote terminal triggers the relay terminal to release the short-distance link (that is, sends the seventh message) and the time sequence in which the remote terminal performs the transition from the indirect path to the direct path, including the following three modes:
  • the remote terminal may continue to maintain the connection with the relay terminal during the downlink synchronization process of the cell corresponding to the cell identifier, that is, may continue to pass the relay terminal. Data communication with network devices. After completing the downlink synchronization of the cell corresponding to the cell identifier, the remote terminal may send a seventh message to the relay terminal, trigger the relay terminal to release the short-distance link, and stop the data communication with the network device through the relay terminal. Data communication to the network device to the direct connection path.
  • the remote terminal may send a seventh message to the relay terminal, triggering disconnection from the relay terminal. Stop data communication through the relay terminal and network device. After that, the remote terminal may start a downlink synchronization process and a random access procedure of the cell corresponding to the cell identifier.
  • Manner 3 If the sixth message includes the first indication information, and the first indication information indicates that the remote terminal disconnects from the relay terminal after performing downlink synchronization with the cell, the remote terminal may follow the manner. One performs path conversion. Conversely, the remote terminal can perform path conversion according to mode two.
  • the remote terminal performs downlink synchronization with the cell corresponding to the cell identifier.
  • the relay terminal After receiving the seventh message sent by the remote terminal, the relay terminal releases the short-distance link between the relay terminal and the remote terminal.
  • the specific implementation of releasing the short-distance link may include the following aspects:
  • the relay terminal releases the side-to-side bearer between all the remote terminals, including releasing all the radio link layer control protocol (RLC) entities and logical channels carried by the side links;
  • RLC radio link layer control protocol
  • the remote terminal performs a random access procedure on the cell corresponding to the cell identifier, and sends an RRC connection reconfiguration complete message to the network device after the cell access is completed.
  • the relay terminal (by the fourth message) notifies the remote terminal to perform path conversion.
  • the remote terminal (via the fifth message) requests the network device configuration (sixth message) path conversion.
  • the release of the short-range link between the relay terminal and the remote terminal is triggered by the remote terminal (via the seventh message).
  • FIG. 9 is a schematic flowchart diagram of still another path conversion method provided by the present application.
  • C-RNTI Cell Radio Network Temporary Identifier
  • the upper layer of the relay terminal triggers a short-distance link between the relay terminal and the remote terminal.
  • the relay device and the remote terminal may be other forms of short-distance links, such as any one of WLAN or Bluetooth.
  • the relay terminal sends a fourth message to the remote terminal, where the fourth message is used to notify the remote terminal that the relay terminal is about to release the short-distance link, thereby instructing the remote terminal to switch from the indirect path to the direct connection path.
  • the fourth message may be implemented as, but not limited to, PC5 signaling.
  • the fourth message may include a C-RNTI of the relay terminal, a local ID of the remote terminal, a common radio resource configuration information of the serving cell of the relay terminal, and a cell identifier of the serving cell of the relay terminal.
  • the C-RNTI of the relay terminal and the local ID of the remote terminal can be used to identify the temporary identity of the remote terminal on the network side.
  • the fourth message may further include a reason why the relay terminal releases the short-distance link.
  • the relay terminal needs to do circuit domain fallback (CSFB), or the power of the relay terminal is insufficient.
  • CSFB circuit domain fallback
  • the example is only some embodiments provided by the present application. In actual applications, the reason why other relay terminals release the short-distance link may also be included, which is not limited herein.
  • the relay terminal may release the short-distance link between the relay terminal and the remote terminal after transmitting the fourth message to the remote terminal.
  • the specific implementation of releasing the short-distance link may include the following aspects:
  • the relay terminal releases the side-to-side bearer between all the remote terminals, including releasing all the radio link layer control protocol (RLC) entities and logical channels carried by the side links;
  • RLC radio link layer control protocol
  • the remote terminal After receiving the fourth message, the remote terminal triggers a transition from the indirect path to the direct path, performs downlink synchronization with the cell corresponding to the cell identifier in the fourth message, and triggers a random access procedure.
  • the remote terminal may also start a first timer, and the value of the length of the first timer may be notified by the relay device through the fourth message, or may be a predefined value, used to limit The maximum time that the remote terminal accesses the cell corresponding to the cell identifier. If the remote terminal still does not access the cell when the first timer expires, the cell access may be considered to have failed. If this happens, the remote terminal triggers the RRC connection re-establishment process.
  • a possible special case is that if the remote terminal does not receive the fourth message, the relay terminal has disconnected the link with the remote terminal. In this case, when the remote terminal does not detect the discovery sent by the relay terminal During the interval, the remote terminal considers that the link with the relay terminal fails, and the remote terminal triggers the radio resource control connection reestablishment process.
  • the remote terminal sends a random access preamble to the network device, and the network device feeds back the random access response to the remote terminal.
  • the remote terminal sends a random access message 3 (MSG 3) to the network device, where the message 3 may include: a C-RNTI of the relay terminal, and a local ID of the remote terminal.
  • the message 3 may be an RRC message or a MAC control element (MAC CE).
  • the network device returns a random access message 4 (MSG4) to the remote terminal.
  • the message 4 may include the same content as the randomly accessed message 3 sent by the remote terminal.
  • the message 4 can be an RRC message or a MAC CE.
  • the remote terminal and the network device perform an RRC connection reconfiguration process of the direct connection path.
  • the remote terminal does not have a C-RNTI in the cell where the network device is located.
  • the relay terminal (via the fourth message) notifies the remote terminal to perform path conversion, and configures path conversion of the remote terminal (such as the C-RNTI and remote local ID, cell ID, radio resource configuration information, etc. of the relay).
  • the relay terminal releases the short-distance link after transmitting the fourth message to the remote device, without triggering a condition.
  • FIG. 10 is a schematic flowchart diagram of still another path conversion method provided by the present application.
  • the remote terminal side has a Cell Radio Network Temporary Identifier (C-RNTI).
  • C-RNTI Cell Radio Network Temporary Identifier
  • the C-RNTI of the remote terminal may be sent by the network device to the remote terminal through the relay terminal when the remote terminal establishes a short-distance communication connection with the relay terminal, or directly from the network device when the remote terminal directly connects the path obtain. Expand below:
  • the upper layer of the relay terminal triggers a short-distance link between the relay terminal and the remote terminal.
  • the relay device and the remote terminal may be other forms of short-distance links, such as any one of WLAN or Bluetooth.
  • the relay terminal sends a fourth message to the remote terminal, where the fourth message is used to notify the relay terminal that the short-distance link is to be released, thereby instructing the remote terminal to switch from the indirect path to the direct connection path.
  • the fourth message may be implemented as, but not limited to, PC5 signaling.
  • the fourth message may include public radio resource configuration information of the serving cell of the relay terminal, and a cell identifier of the serving cell of the relay terminal.
  • the fourth message may further include a reason why the relay terminal releases the short-distance link.
  • the relay terminal needs to do circuit domain fallback (CSFB), or the power of the relay terminal is insufficient.
  • CSFB circuit domain fallback
  • the example is only some embodiments provided by the present application, and the fourth message may also include the reason that other relay terminals release the short-distance link, which is not limited herein.
  • the relay terminal After transmitting the fourth message to the remote terminal, the relay terminal releases the short-distance link between the relay terminal and the remote terminal.
  • the specific implementation of releasing the short-distance link may include the following aspects:
  • the relay terminal releases the side-to-side bearer between all the remote terminals, including releasing all the radio link layer control protocol (RLC) entities and logical channels carried by the side links;
  • RLC radio link layer control protocol
  • the remote terminal After receiving the fourth message sent by the relay terminal, the remote terminal triggers a transition from the indirect path to the direct path, and performs downlink synchronization with the cell corresponding to the cell identifier in the fourth message.
  • the remote terminal may also start a first timer, and the value of the length of the first timer may be notified by the relay device through the fourth message, or may be a predefined value, used to limit The maximum time that the remote terminal accesses the cell corresponding to the cell identifier. If the remote terminal still does not access the cell when the first timer expires, the cell access may be considered to have failed. If this happens, the remote terminal triggers the RRC connection re-establishment process.
  • a possible special case is that if the remote terminal does not receive the fourth message, the relay terminal has disconnected the link with the remote terminal. In this case, when the remote terminal does not detect the discovery message sent by the relay terminal, the remote terminal considers that the link between the terminal and the relay terminal fails, and the remote terminal triggers the RRC connection re-establishment process.
  • the remote terminal performs a random access procedure.
  • S605 The RRC connection reconfiguration process of the direct connection path between the remote terminal and the network device.
  • the remote terminal has a C-RNTI in the cell where the network device is located.
  • the relay terminal (by the fourth message) notifies the remote terminal to perform path conversion, and configures (such as cell ID, radio resource configuration information, etc.) path conversion of the remote terminal.
  • the relay terminal releases the short-distance link after transmitting the fourth message to the remote terminal, without triggering a condition.
  • FIG. 11 is a schematic flowchart diagram of still another path conversion method provided by the present application.
  • the remote terminal side has a Cell Radio Network Temporary Identifier (C-RNTI).
  • C-RNTI Cell Radio Network Temporary Identifier
  • the C-RNTI of the remote terminal may be sent by the network device to the remote terminal through the relay terminal when the remote terminal establishes a short-distance communication connection with the relay terminal, or directly from the network device when the remote terminal directly connects the path obtain. Expand below:
  • the upper layer of the relay terminal triggers a short-distance link between the relay terminal and the remote terminal.
  • the relay device and the remote terminal may be other forms of short-distance links, such as any one of WLAN or Bluetooth.
  • the relay terminal sends a fourth message to the remote terminal, where the fourth message is used to notify the relay terminal that the short-distance link is to be released, thereby instructing the remote terminal to switch from the indirect path to the direct path.
  • the fourth message may be implemented as, but not limited to, PC5 signaling.
  • the fourth message may include a reason why the relay terminal releases the short-distance link.
  • the relay terminal needs to do circuit domain fallback (CSFB), or the power of the relay terminal is insufficient.
  • CSFB circuit domain fallback
  • the example is only some embodiments provided by the present application, and the fourth message may also include the reason that other relay terminals release the short-distance link, which is not limited herein.
  • the relay terminal After transmitting the fourth message to the remote terminal, the relay terminal releases the short-distance link between the relay terminal and the remote terminal.
  • the specific implementation of releasing the short-distance link may include the following aspects:
  • the relay terminal releases the side-to-side bearer between all the remote terminals, including releasing all the radio link layer control protocol (RLC) entities and logical channels carried by the side links;
  • RLC radio link layer control protocol
  • the remote terminal After receiving the fourth message sent by the relay terminal, the remote terminal initiates an RRC re-establishment process.
  • a possible special case is that if the remote terminal does not receive the fourth message, the relay terminal has disconnected the link with the remote terminal. In this case, when the remote terminal does not detect the discovery message sent by the relay terminal, the remote terminal considers that the link between the terminal and the relay terminal fails, and the remote terminal triggers the RRC connection re-establishment process.
  • S704 Perform an RRC connection reconfiguration process of the direct connection path between the remote terminal and the network device.
  • the relay terminal (through the fourth message) only informs the remote terminal to perform path conversion, and does not configure path conversion.
  • the remote terminal After receiving the fourth message, the remote terminal triggers re-establishment of the RRC connection, and performs RRC reconfiguration based on the reconstructed RRC connection (direct connection path).
  • the implementation of releasing the short-distance link between the relay terminal and the remote terminal may include the following:
  • the first implementation manner the short-distance link between the relay terminal and the remote terminal is triggered by the network device, and reference may be made to FIG. 5.
  • the network device After the network device configures the link transition of the remote terminal (that is, the network device sends the second message to the remote terminal), the network device sends a third message to the relay terminal, triggering the relay terminal to release the short-distance chain. road.
  • the second implementation manner the short-distance link between the relay terminal and the remote terminal is triggered by the remote terminal, and reference may be made to FIG. 6 .
  • the remote terminal After the remote terminal receives the configuration information of the link translation sent by the network device (that is, the remote terminal receives the second message sent by the network device), the remote terminal sends a third message to the relay terminal, and the triggering is performed. The terminal releases the short-distance link.
  • the third implementation manner is: after the relay terminal requests to release the short-distance communication link (that is, the relay terminal sends the first message to the network device), when the relay terminal keeps the short-distance link for more than the first time length, After the terminal releases the short-distance link, refer to FIG. 7.
  • the implementation of releasing the short-distance link between the relay terminal and the remote terminal may include the following:
  • the first implementation manner the short-distance link between the relay terminal and the remote terminal is triggered and released by the network device.
  • the network device After the network device configures the link transition of the remote terminal (that is, the network device sends the sixth message to the remote terminal), the network device sends a seventh message to the relay terminal, triggering the relay terminal to release the short-distance chain. road.
  • the second implementation manner the short-distance link between the relay terminal and the remote terminal is triggered by the remote terminal, which is shown in FIG. 8.
  • the remote terminal After the remote terminal receives the configuration information of the link translation sent by the network device, that is, the remote terminal receives the sixth message sent by the network device, the remote terminal sends a seventh message to the relay terminal, and the triggering is performed. The terminal releases the short-distance link.
  • the third implementation manner the relay terminal notifies the release of the short-distance communication link (that is, sends the fourth message to the remote terminal) Thereafter, when the relay terminal maintains the short-distance link for more than a specified time threshold, the relay terminal releases the short-distance link.
  • the relay terminal can be set according to actual needs, and is not limited herein.
  • the relay terminal can directly perform the release of the short-distance link after the release of the short-distance link, and the triggering condition is not needed.
  • the relay terminal can directly perform the release of the short-distance link after the release of the short-distance link, and the triggering condition is not needed.
  • the path conversion method provided by the present application may also be applied to a cell handover scenario.
  • the remote terminal may also switch from the indirect path to another network device (which may be referred to as a second network device) that is different from the network device (which may be referred to as the first network device) connected to the relay terminal. .
  • FIG. 12 illustrates a path switching method in a cell handover scenario provided by the present application.
  • the difference from the embodiment of FIG. 5 is that, in the embodiment of FIG. 12, a handover preparation process needs to be performed between the first network device and the second network device, and reference may be made to S102'.
  • the time that the first network device sends the third message may be any one of the following:
  • the first network device receives the HARQ ACK or RLC ACK for the second message sent by the remote terminal.
  • FIG. 13 illustrates another path switching method in the cell handover scenario provided by the present application.
  • the path switching method in the cell switching scenario needs to include the cell handover preparation between the first network device and the second network device, based on the foregoing embodiment of FIG. 5-11 provided by the present application. process.
  • FIG. 14 illustrates a wireless communication system, a terminal, and a network device.
  • the wireless communication system 10 can include a first terminal 400, a second terminal 500, and a first network device 600.
  • the wireless communication system 10 can further include: a second network device 700.
  • the first terminal 400 or the second terminal 500 may be the terminal 200 in the embodiment of FIG. 3, and the first network device 600 or the second network device 700 may be the network device 300 in the embodiment of FIG. 4, and the wireless communication system 10 may be Is the wireless communication system 100 depicted in FIG.
  • the wireless communication system 10 can employ two different path conversion schemes. Described separately below.
  • the first terminal 400 requests the network device 600 to trigger the second terminal 500 to perform path conversion, and the network device 600 configures the path conversion.
  • the second terminal 500 may also switch from the indirect path to another network device different from the first network device 600 connected to the first terminal 400, that is, the second network device 700.
  • the following describes the implementation of the first terminal 400, the second terminal 500, the first network device 600, and the second network device 700:
  • the first terminal 400 may include a processing unit 401 and a communication unit 403. among them:
  • the communication unit 403 can be configured to send the first message to the first network device 600.
  • the first message may be used to request that the second terminal 500 be switched from an indirect path that communicates with the first network device 600 through the first terminal 400 to a line that communicates with the first network device 600 or the second network device 700. Even the path. Or the first message can be used to request to release the link between the first terminal 400 and the second terminal 500.
  • the processing unit 401 can be configured to release a link between the first terminal 400 and the second terminal 500.
  • the processing unit 401 can be used to release the first terminal 400 and the second terminal 500 in the following manners. Link between:
  • the processing unit 401 can be configured to release the link after receiving the third message.
  • the third message may be sent by the first network device 600 or the second terminal 500 after the first network device 600 sends the second message to the second terminal 500, to instruct the first terminal 400 to release the link.
  • the second message may include at least one of the following: a cell identifier, or random access configuration information, or first indication information, or a first time value, configured to configure the second terminal 500 to switch from the indirect path to the direct connection. path;
  • the first indication information may be used to indicate whether the second terminal 500 disconnects the first terminal 400 after performing downlink synchronization on the cell corresponding to the cell identifier.
  • the first time value may be the maximum time allowed by the second terminal 500 to access the cell corresponding to the cell identifier.
  • the processing unit 401 can be configured to release the link when the communication unit 403 keeps the link for a length of time longer than the first time length after transmitting the first message.
  • the first network device 600 may include: a first communication unit 601 and a second communication unit 603. among them:
  • the communication unit 601 can be configured to receive the first message sent by the first terminal 400.
  • the first message may be used to request that the second terminal 500 be switched from an indirect path that communicates with the first network device 600 through the first terminal 400 to a line that communicates with the first network device 600 or the second network device 700.
  • the first message is used to request release of the link between the first terminal 400 and the second terminal 500; wherein the first network device 600 is different from the second network device 700.
  • the communication unit 601 is further configured to send a second message to the second terminal 500, where the second message is used to configure the second terminal 500 to switch from the indirect path to the direct path.
  • the second message may include at least one of the following: a cell identifier, or random access configuration information, or first indication information, or a first time value.
  • the first indication information may be used to indicate whether the second terminal 500 disconnects the first terminal 400 after performing downlink synchronization on the cell corresponding to the cell identifier.
  • the first time value may be the maximum time allowed by the second terminal 500 to access the cell corresponding to the cell identifier.
  • the second terminal 500 may include a processing unit 501 and a communication unit 503. among them:
  • the communication unit 503 is configured to receive the second message sent by the first network device 600, where the second message is used to configure the second terminal 500 to switch from the indirect path that communicates with the first network device 600 through the first terminal 400 to A direct connection path in which the first network device 600 or the second network device 700 performs communication.
  • the processing unit 501 is configured to switch from the indirect path to the direct path according to the second message.
  • the second message may include at least one of the following: a cell identifier, or random access configuration information, or first indication information, or a first time value.
  • the first indication information may be used to indicate whether the second terminal 500 disconnects the first terminal 400 after performing downlink synchronization on the cell corresponding to the cell identifier.
  • the first time value may be used to indicate the maximum time allowed by the second terminal 500 to access the cell corresponding to the cell identifier.
  • the specific implementations of the first terminal 400, the second terminal 500, the first network device 600, and the second network device 700 may refer to the embodiment of FIG. 5-7 or the embodiment of FIG. 12, and other solutions.
  • the second related implementation manner will not be described here.
  • the first terminal 400 directly notifies the second terminal 500 to perform path conversion.
  • the second terminal 500 is further switchable from the indirect path to another network device different from the first network device 600 connected to the first terminal 400.
  • the second network device 700 is prepared. The following describes the implementation of the first terminal 400, the second terminal 500, the first network device 600, and the second network device 700:
  • the first terminal 400 may include a processing unit 401 and a communication unit 403. among them:
  • the communication unit 403 can be configured to send a fourth message to the second terminal.
  • the fourth message may be used to instruct the second terminal to switch from the indirect path that communicates with the first network device through the first terminal to the direct path that communicates with the first network device or the second network device. Or the fourth message is used to indicate that the link between the first terminal and the second terminal is released.
  • the processing unit 401 can be configured to release a link between the first terminal and the second terminal.
  • the processing unit 401 can be used to release the link between the first terminal 400 and the second terminal 500 in the following manners:
  • the processing unit 401 can be configured to release the link after receiving the seventh message.
  • the seventh message may be sent by the first network device or the second terminal after the first network device sends the sixth message to the second terminal, to indicate that the first terminal releases the link.
  • the sixth message may include at least one of the following: a cell identifier, or random access configuration information, or first indication information, or a first time value, configured to configure the second terminal to switch from the indirect path to the direct path. .
  • the processing unit 401 can be configured to release the link when the first terminal keeps the link for a length of time longer than the first time length after transmitting the fourth message.
  • the fourth message may include at least one of the following: a cell identifier of the serving cell of the first terminal, or configuration information of a public radio resource of the serving cell of the first terminal.
  • the second terminal 500 may include a processing unit 501 and a communication unit 503. among them:
  • the communication unit 503 is configured to receive a fourth message sent by the first terminal.
  • the fourth message may be used to indicate that the second terminal switches from the indirect path that communicates with the first network device by using the first terminal to the direct path that communicates with the first network device or the second network device. Or the fourth message may be used to indicate that the link between the first terminal and the second terminal is released.
  • the processing unit 501 is configured to switch from the indirect path to the direct path according to the fourth message.
  • the fourth message may include at least one of the following: a cell identifier of the serving cell of the first terminal, or configuration information of a public radio resource of the serving cell of the first terminal.
  • the communication unit 503 is further configured to: send, to the first network device, a second message, requesting to switch from the indirect path to the direct path. Moreover, the communication unit 503 is further configured to receive a sixth message sent by the first network device.
  • the sixth message may include at least one of the following: a cell identifier, or random access configuration information, or first indication information, or a first time value, configured to configure the second terminal to switch from the indirect path to the direct path .
  • the first indication information may be used to indicate whether the second terminal disconnects the first terminal after performing downlink synchronization on the cell corresponding to the cell identifier.
  • the first time value may be the maximum time allowed by the cell corresponding to the second terminal access cell identifier.
  • the communication unit 503 is further configured to trigger the RRC connection re-establishment process after receiving the fourth message.
  • the communication unit 503 is further configured to: the second terminal accesses the serving cell of the first terminal, and sends the terminal device identifier to the first network device.
  • the terminal device identifier may be a C-RNTI of the second terminal, or may be It is the C-RNTI of the first terminal and the local identifier of the second terminal.
  • the terminal device identifier may be carried in the fourth message. Or the terminal device identifier may be sent by the first terminal to the second terminal before sending the fourth message.
  • the specific implementations of the first terminal 400, the second terminal 500, the first network device 600, and the second network device 700 may refer to the embodiment of FIG. 8-11 or the embodiment of FIG. 13, and other solutions.
  • the second related implementation manner will not be described here.
  • the relay device in the relay communication, if the relay device can no longer provide the relay service for the remote terminal, the relay device can trigger the non-terminal terminal to communicate with the network device through the relay device.
  • the direct path is switched to a direct path that communicates directly with the network device and releases the short-distance link between the relay terminal and the remote terminal.
  • the relay device can promptly and quickly trigger the path conversion of the remote terminal according to its own situation, and even realize the path conversion in the case where the side link does not interrupt the data communication, thereby ensuring the remote terminal and the network device. Data communication between the two is not interrupted.
  • the program can be stored in a computer readable storage medium, when the program is executed
  • the flow of the method embodiments as described above may be included.
  • the foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请公开了一种路径转换方法。该方法包括：第一终端向第一网络设备发送第一消息，所述第一消息用于请求将第二终端从通过所述第一终端与所述第一网络设备进行通信的非直连路径转换到与所述第一网络设备或第二网络设备进行通信的直连路径；或所述第一消息用于请求释放所述第一终端与所述第二终端之间的链路；其中，所述第一网络设备与所述第二网络设备不同；所述第一终端释放所述第一终端与所述第二终端之间的链路。上述方案可实现由中继终端触发远端终端从非直连路径转换到直连路径，可以更加灵活的适应中继场景。

Description

一种路径转换方法、相关装置及系统 技术领域
本申请涉及通信技术领域，特别涉及一种路径转换方法、相关装置及系统。
背景技术
在移动通信系统中，终端与网络设备(如基站)之间的连接模式可以有如下两种：
连接模式一：终端直接与网络设备连接，进行数据通信。该方式可以称为直连通信模式。在这种通信模式中，终端与网络设备之间的通信链路可称为直连链路；
连接模式二：终端通过其他终端与网络设备连接，进行数据通信。该方式可以称为非直连通信模式。此时，前者可以称为远端终端，例如远端终端(remote user equipment，remote UE)，后者可以称为中继终端，例如中继终端(relay user equipment，relay UE)。在这种通信模式中，终端与网络设备之间的通信链路可称为非直连链路。
如图1A-1B所示，远端终端可以在上述两种连接模式或者通信链路间进行转换。例如，如图1A所示，当UE与基站间的链路质量比较差时，UE可以选择通过一个附近的relay UE与基站进行连接。这时需要进行直连通信方式到非直连通信方式的转换。再例如，如图1B所示，当remote UE连接的relay UE移动后，remote UE和relay UE之间的连接可能无法再维持。此时，需要进行非直连通信方式到直连通信方式的转换。
针对从非直连路径到直连路径的转换，目前3GPP讨论的路径转换的基本流程如下：
1.当remote UE触发从非直连路径到直连路径的转换后，remote UE发送一条无线资源控制(radio resource control，RRC)消息给基站。该RRC消息可以为路径转换请求消息或者测量报告，该RRC消息通过relay UE发送给基站。
2.基站收到remote UE发送的所述RRC消息后，通过relay UE发送一条RRC连接重配消息给remote UE，所述RRC连接重配消息用于命令remote UE从非直连路径转换到直连路径。
3.Remote UE完成RRC连接重配后，通过直连路径发送RRC连接重配完成消息给基站。
但是，目前已经讨论的这种路径转换方法适用的场景有限，不利于拓展至更多中继应用场景。
发明内容
本发明实施例提供了一种路径转换方法、相关装置及系统，可实现由中继终端触发远端设备的链路转换，可以更加灵活的适应中继场景。
第一方面，提供了一种路径转换方法，应用于第一终端侧，该方法包括：第一终端向第一网络设备发送第一消息。其中，第一消息可用于请求将第二终端从通过第一终端与第一网络设备进行通信的非直连路径转换到与第一网络设备或第二网络设备进行通信的直连路径。或者，第一消息可用于请求释放第一终端与第二终端之间的链路。然后，第一终端释放第一终端与第二终端之间的链路。
具体的，所述请求释放第一终端与第二终端之间的链路可包括如下两种方式：
第一种：第一终端发第一消息给第一网络设备，请求第一网络设备来释放第一终端与第二终端之间的链路。
第二种：第一终端发第一消息给第一网络设备，收到第一网络设备的响应消息后，第一终端自己释放第一终端与第二终端之间的链路。
这里，第一网络设备与第二网络设备不同。第一终端是中继通信中的第一终端，第二终端是中继通信中的第二终端。
结合第一方面，在一些实施例中，第一终端释放所述链路的实现方式可包括下述几种：
第一种实现方式：第一网络设备与第二第一网络设备之间的所述链路由第一网络设备触发释放。
具体的，在第一网络设备与第二第一网络设备为第二终端的链路转换进行配置(即第一网络设备向第二终端发送第二消息)之后，第一网络设备向第一终端发送第三消息，触发第一终端释放短距离链路。
第二种实现方式：第一终端与第二终端之间的短距离链路由第二终端触发释放。
具体的，在第二终端接收到第一网络设备发送的链路转换的配置信息(即第二终端接收到第一网络设备发送的第二消息)之后，第二终端向第一终端发送第三消息，触发第一终端释放短距离链路。
第三种实现方式：在第一终端请求释放短距离通信链路(即第一终端向第一网络设备发送第一消息)后，当第一终端保持短距离链路的时间超过第一时间长度时，第一终端释放短距离链路。
第二方面，提供了一种路径转换方法，应用于第一网络设备侧，该方法包括：第一网络设备接收第一终端发送的第一消息。其中，第一消息可用于请求将第二终端从通过第一终端与第一网络设备进行通信的非直连路径转换到与第一网络设备或第二网络设备进行通信的直连路径。或第一消息可用于请求释放
具体的，所述请求释放第一终端与第二终端之间的链路可包括如下两种方式：
第一种：第一终端发第一消息给第一网络设备，请求第一网络设备来释放第一终端与第二终端之间的链路。
第二种：第一终端发第一消息给第一网络设备，收到第一网络设备的响应消息后，第一终端自己释放第一终端与第二终端之间的链路。
第一终端与第二终端之间的链路；其中，第一网络设备与第二网络设备不同。然后，第一网络设备向第二终端发送第二消息，第二消息可用于配置第二终端从非直连路径转换到直连路径。
具体的，第二消息可包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值。其中，第一指示信息可用于指示第二终端是否在与小区标识对应的小区进行下行同步后再断开与第一终端的连接。第一时间值可以为第二终端接入小区标识对应的小区所允许的最长时间。
第三方面，提供了一种路径转换方法，应用于第二终端侧，该方法包括：第二终端接收到第一络设备发送的第二消息，并根据第二消息，从非直连路径转换到直连路径。
这里，第一网络设备与第二网络设备不同。第二消息可用于配置第二终端从通过第一 终端与第一网络设备进行通信的非直连路径转换到与第一网络设备或第二网络设备进行通信的直连路径。
具体的，第二消息可以包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值。其中，第一指示信息可以用于指示第二终端是否在与小区标识对应的小区进行下行同步后再断开与第一终端的连接。第一时间值可以用于指示第二终端接入小区标识对应的小区所允许的最长时间。
实施第一方面、第二方面和第三方面描述的路径转换方法，通过第一终端请求第一网络设备触发第二终端执行路径转换，并且通过第一网络设备对路径转换进行配置，可实现由第一终端及时有效的触发路径转换过程。
第四方面，提供了一种路径转换方法，应用于第一终端侧，该方法包括：第一终端向第二终端发送第四消息。其中，第四消息可用于指示第二终端从通过第一终端与第一网络设备进行通信的非直连路径转换到与第一网络设备或第二网络设备进行通信的直连路径。或第四消息可用于指示释放第一终端与第二终端之间的链路。然后，第一终端释放第一终端与第二终端之间的链路。
这里，第一网络设备与第二网络设备不同。
具体的，第四消息可以包括以下至少一项：第一终端的服务小区的小区标识，或者第一终端的服务小区的公共无线资源的配置信息。
结合第四方面，在一些实施例中，第一终端释放链路的实现方式可包括下述几种：
第一种实现方式：第一终端与第二终端之间的短距离链路由第一网络设备触发释放。
具体的，在第一网络设备为第二终端的链路转换进行配置(即第一网络设备向第二终端发送第六消息)之后，第一网络设备向第一终端发送第七消息，触发第一终端释放短距离链路。
第二种实现方式：第一终端与第二终端之间的短距离链路由第二终端触发释放。
具体的，在第二终端接收到第一网络设备发送的链路转换的配置信息(即第二终端接收到第一网络设备发送的第六消息)之后，第二终端向第一终端发送第七消息，触发第一终端释放短距离链路。
第三种实现方式：在第一终端通知释放短距离通信链路(即向第二终端发送第四消息)后，当第一终端保持短距离链路的时间超过指定时间阈值时，第一终端释放短距离链路。关于该指定时间阈值的选取，第一终端可以根据实际需求进行设置，这里不作限制。
另外，可选的，第一终端还可以在通知短距离链路的释放之后，直接执行短距离链路的释放，无需触发条件。
第五方面，提供了一种路径转换方法，应用于第二终端侧，该方法包括：第二终端接收第一终端发送的第四消息，并根据第四消息，从非直连路径转换到直连路径。
这里，第四消息可以用于指示第二终端从通过第一终端与第一网络设备进行通信的非直连路径转换到与第一网络设备或第二网络设备进行通信的直连路径。或第四消息可以用于指示释放第一终端与第二终端之间的链路。其中，第一网络设备与第二网络设备不同。
具体的，第四消息可以包括以下至少一项：第一终端的服务小区的小区标识，或者第一终端的服务小区的公共无线资源的配置信息。
结合第五方面，在一些实施例中，第二终端还可以向第一网络设备发送第五消息，用于请求从非直连路径转换到直连路径。然后，第二终端可以接收第一网络设备发送的第六消息。第六消息可以包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值，用于配置第二终端从非直连路径转换到直连路径。其中，第一指示信息用于指示第二终端是否在与小区标识对应的小区进行下行同步后再断开与第一终端的连接；第一时间值为第二终端接入小区标识对应的小区所允许的最长时间。
结合第五方面，在一些实施例中，第二终端还可以在接收到第四消息后，触发无线资源控制连接重建过程。
结合第五方面，在一些实施例中，述第二终端还可以接入第一终端的服务小区，并向第一网络设备发送终端设备标识。其中，终端设备标识可以为第二终端的C-RNTI，或者终端设备标识可以为第一终端的C-RNTI和第二终端的本地标识。可选的，终端设备标识可以携带在第四消息中。可选的，终端设备标识由第一终端在发送第四消息之前发送给第二终端。
实施第一方面、第二方面和第三方面描述的路径转换方法，通过第一终端直接通知第二终端执行路径转换，并且通过第一网络设备对路径转换进行配置，可实现由第一终端快速的触发路径转换过程。
第六方面，本申请提供了一种终端，该终端为上述第一方面中的第一终端，可包括多个功能模块，用于相应的执行第一方面所提供的方法，或者第一方面可能的实施方式中的任意一种所提供的方法。
第七方面，本申请提供了一种网络设备，该网络设备为上述第二方面中的第一网络设备，可包括多个功能模块，用于相应的执行第二方面所提供的方法，或者第二方面可能的实施方式中的任意一种所提供的方法。
第八方面，本申请提供了一种终端，该终端为上述第三方面中的第二终端，可包括多个功能模块，用于相应的执行第三方面所提供的方法，或者第三方面可能的实施方式中的任意一种所提供的方法。
第九方面，本申请提供了一种终端，该终端为上述第四方面中的第一终端，可包括多个功能模块，用于相应的执行第四方面所提供的方法，或者第四方面可能的实施方式中的任意一种所提供的方法。
第十方面，本申请提供了一种终端，该终端为上述第十方面中的第二终端，可包括多个功能模块，用于相应的执行第十方面所提供的方法，或者第十方面可能的实施方式中的任意一种所提供的方法。
第十一方面，本申请提供了一种终端，用于执行第一方面描述的路径转换方法。终端可包括：存储器以及与存储器耦合的处理器、收发器，其中：收发器用于与其他通信设备(如网络设备)通信。存储器用于存储第一方面描述的路径转换方法的实现代码，处理器用于执行存储器中存储的程序代码，即执行第一方面所提供的方法，或者第一方面可能的实施方式中的任意一种所提供的方法。
第十二方面，本申请提供了一种网络设备，用于执行第二方面描述的路径转换方法。网络设备可包括：存储器以及与存储器耦合的处理器、收发器，其中：收发器用于与其他 通信设备(如终端)通信。存储器用于存储第二方面描述的资源分配方法的实现代码，处理器用于执行存储器中存储的程序代码，即执行第二方面所提供的方法，或者第二方面可能的实施方式中的任意一种所提供的方法。
第十三方面，本申请提供了一种终端，用于执行第三方面描述的路径转换方法。终端可包括：存储器以及与存储器耦合的处理器、收发器，其中：收发器用于与其他通信设备(如网络设备)通信。存储器用于存储第三方面描述的路径转换方法的实现代码，处理器用于执行存储器中存储的程序代码，即执行第三方面所提供的方法，或者第三方面可能的实施方式中的任意一种所提供的方法。
第十四方面，本申请提供了一种终端，用于执行第四方面描述的路径转换方法。终端可包括：存储器以及与存储器耦合的处理器、收发器，其中：收发器用于与其他通信设备(如网络设备)通信。存储器用于存储第四方面描述的路径转换方法的实现代码，处理器用于执行存储器中存储的程序代码，即执行第四方面所提供的方法，或者第四方面可能的实施方式中的任意一种所提供的方法。
第十五方面，本申请提供了一种终端，用于执行第五方面描述的路径转换方法。终端可包括：存储器以及与存储器耦合的处理器、收发器，其中：收发器用于与其他通信设备(如网络设备)通信。存储器用于存储第五方面描述的路径转换方法的实现代码，处理器用于执行存储器中存储的程序代码，即执行第五方面所提供的方法，或者第五方面可能的实施方式中的任意一种所提供的方法。
第十六方面，本申请提供了一种无线通信系统，包括第一终端、第二终端和网络设备，其中：第一终端可以上述第六方面描述的终端，第二终端可以是上述第八方面描述的终端，网络设备可以是上述第七方面描述的网络设备。
可选的，第一终端也可以上述第十一方面描述的终端，第二终端也可以是上述第十三方面描述的终端，网络设备可以是上述第十二方面描述的网络设备。
可选的，第一终端也可以上述第九方面描述的终端，第二终端也可以是上述第十方面描述的终端。
可选的，第一终端也可以上述第十四方面描述的终端，第二终端也可以是上述第十五方面描述的终端。
第十七方面，提供了一种计算机可读存储介质，可读存储介质上存储有实现第一方面所提供的资源分配方法，或者第一方面可能的实施方式中的任意一种所提供的资源分配方法的程序代码，该程序代码包含运行第一方面所提供的资源分配方法，或者第一方面可能的实施方式中的任意一种所提供的资源分配方法的执行指令。
第十八方面，提供了一种计算机可读存储介质，可读存储介质上存储有实现第二方面所提供的资源分配方法，或者第二方面可能的实施方式中的任意一种所提供的资源分配方法的程序代码，该程序代码包含运行第二方面所提供的资源分配方法，或者第二方面可能的实施方式中的任意一种所提供的资源分配方法的执行指令。
第十九方面，提供了一种计算机可读存储介质，可读存储介质上存储有实现第三方面所提供的资源分配方法，或者第三方面可能的实施方式中的任意一种所提供的资源分配方 法的程序代码，该程序代码包含运行第三方面所提供的资源分配方法，或者第三方面可能的实施方式中的任意一种所提供的资源分配方法的执行指令。
第二十方面，提供了一种计算机可读存储介质，可读存储介质上存储有实现第四方面所提供的资源分配方法，或者第四方面可能的实施方式中的任意一种所提供的资源分配方法的程序代码，该程序代码包含运行第四方面所提供的资源分配方法，或者第四方面可能的实施方式中的任意一种所提供的资源分配方法的执行指令。
第二十一方面，提供了一种计算机可读存储介质，可读存储介质上存储有实现第五方面所提供的资源分配方法，或者第五方面可能的实施方式中的任意一种所提供的资源分配方法的程序代码，该程序代码包含运行第五方面所提供的资源分配方法，或者第五方面可能的实施方式中的任意一种所提供的资源分配方法的执行指令。
附图说明
图1A-1B示出了本申请涉及的中继系统中的两种路径转换场景；
图2示出了本申请涉及的无线通信系统的架构示意图；
图3示出了本申请提供的一种终端的结构示意图；
图4示出了本申请提供的一种网络设备的结构示意图；
图5示出了本申请提供的一种路径转换方法的流程示意图；
图6示出了本申请提供的另一种路径转换方法的流程示意图；
图7示出了本申请提供的再一种路径转换方法的流程示意图；
图8示出了本申请提供的再一种路径转换方法的流程示意图；
图9示出了本申请提供的再一种路径转换方法的流程示意图；
图10示出了本申请提供的再一种路径转换方法的流程示意图；
图11示出了本申请提供的再一种路径转换方法的流程示意图；
图12示出了本申请提供的再一种路径转换方法的流程示意图；
图13示出了本申请提供的再一种路径转换方法的流程示意图；
图14示出了本申请提供的中继终端、远端终端、网络设备，以及无线通信系统的结构示意图。
具体实施方式
本发明的实施方式部分使用的术语仅用于对本发明的具体实施例进行解释，而非旨在限定本发明。
图2示出了本申请涉及的无线通信系统。所述无线通信系统可以是长期演进(Long Term Evolution，LTE)系统，也可以是未来演进的第五代移动通信(the 5th Generation，5G)系统、新空口(NR)系统，机器与机器通信(Machine to Machine，M2M)系统等。如图2所示，无线通信系统100可包括：网络设备101，远端终端105，以及中继设备103。一个中继设备103可以连接一个或多个远端终端105。其中：
网络设备101可以为基站，基站可以用于与一个或多个终端进行通信，也可以用于与 一个或多个具有部分终端功能的基站进行通信(比如宏基站与微基站，如接入点，之间的通信)。基站可以是时分同步码分多址(Time Division Synchronous Code Division Multiple Access，TD-SCDMA)系统中的基站收发台(Base Transceiver Station，BTS)，也可以是LTE系统中的演进型基站(Evolutional Node B，eNB)，以及5G系统、新空口(NR)系统中的基站gNB。另外，基站也可以为接入点(Access Point，AP)、传输节点(Trans TRP)、中心单元(Central Unit，CU)或其他网络实体，并且可以包括以上网络实体的功能中的一些或所有功能。
远端终端105可以分布在整个无线通信系统100中，可以是静止的，也可以是移动的。在本申请的一些实施例中，远端终端105可以是智能穿戴设备、移动设备、移动台(mobile station)、移动单元(mobile unit)、M2M终端、无线单元，远程单元、用户代理、移动客户端等等。
中继设备103(又称为中继节点)可以包含两个物理层实体。其中，一个实体用于和其下属用户(即接入到中继设备103的远端终端105)通信。另一个实体具有用户功能(即终端功能)，用于网络设备101通信。具体实现中，中继设备103可以是中继终端。中继设备103还可以是中继收发节点(TRP)，用户终端设备(Customer Premise Equipment，CPE)，中继收发器、中继代理等通信实体。
在无线通信系统100中，侧行链路(sidelink)是指中继设备103与远端终端105之间的短距离链路，包括上行(Uplink，UL)或下行(Downlink，DL)侧行链路。回传链路(backhaul link)是指网络设备101与中继设备103之间的无线链路，包括上行(Uplink，UL)或下行(Downlink，DL)回传链路。除了侧行链路技术，中继设备103与远端终端105之间还可以是其他形式的短距离链路，例如WLAN或蓝牙等链路中的任意一种。
在无线通信系统100中，网络设备101和远端终端105之间的中继设备103可用于对网络设备101和远端终端105之间的无线信号进行转发。具体的，在下行传输时，中继设备103负责对网络设备101发射的无线信号进行转发，最终传输该无线信号至远端终端105。在上行传输时，中继设备103负责对远端终端105发射的无线信号进行转发，最终传输该无线信号至网络设备101。
在一些可能场景中，中继设备103需要主动触发远端终端105进行路径转换，即将远端终端105从通过中继设备103与网络设备101进行通信的非直连路径转换到与网络设备101进行通信的直连路径。例如，当中继设备103需要发起电路域(Circuit Switch，CS)的呼叫时，中继设备103需要执行电路域回退(Circuit Switch Fallback，CSFB)，接入2G或3G网络。当中继设备103接入2G或3G网络后，将无法再继续为远端终端105提供中继服务。再例如，当中继设备103的电量不足时，中继设备103可能也无法再为远端终端105提供中继服务。不限于这些示例描述的场景，在其他场景中，中继设备103也需要主动触发远端终端105进行路径转换。
需要说明的，图2示出的无线通信系统100仅仅是为了更加清楚的说明本申请的技术方案，并不构成对本申请的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
参考图3，图3示出了本申请的一些实施例提供的终端200。终端200可以实施成本申请涉及的远端终端(如图2中的远端终端105)，也可以实施成本申请涉及的中继设备(如图2中的中继设备103)。如图3所示，终端200可包括：一个或多个终端处理器201、存储器202、通信接口203、接收器205、发射器206、耦合器207、天线208、用户接口202，以及输入输出模块(包括音频输入输出模块210、按键输入模块211以及显示器212等)。这些部件可通过总线204或者其他方式连接，图3以通过总线连接为例。其中：
通信接口203可用于终端200与其他通信设备，例如其他终端或网络设备，进行通信。具体的，通信接口203可以是长期演进(LTE)(4G)通信接口，也可以是5G或者未来新空口的通信接口。不限于无线通信接口，终端200还可以配置有有线的通信接口203，例如局域接入网(Local Access Network，LAN)接口。
发射器206可用于对终端处理器201输出的信号进行发射处理，例如信号调制。接收器205可用于对天线208接收的移动通信信号进行接收处理，例如信号解调。在本申请的一些实施例中，发射器206和接收器205可看作一个无线调制解调器。在终端200中，发射器206和接收器205的数量均可以是一个或者多个。天线208可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器207用于将天线208接收到的移动通信信号分成多路，分配给多个的接收器205。
当终端200实施成中继设备时，终端200可配置有两套收发装置，其中，一套收发装置用于远端终端(如图2中的远端终端105)接入到终端200的链路，另一套收发装置用于终端200接入网络设备(如图2中的网络设备101)的链路。具体的，这两套收发装置可具有相同或不同的收发特性，例如这两套收发装置各自对应的天线端口具备或不具备准共址(Quasi Co-location，QCL)特性。
除了图3所示的发射器206和接收器205，终端200还可包括其他通信部件，例如GPS模块、蓝牙(Bluetooth)模块、无线高保真(Wireless Fidelity，Wi-Fi)模块等。不限于上述表述的无线通信信号，终端200还可以支持其他无线通信信号，例如卫星信号、短波信号等等。不限于无线通信，终端200还可以配置有有线网络接口(如LAN接口)来支持有线通信。
所述输入输出模块可用于实现终端200和用户/外部环境之间的交互，可主要包括包括音频输入输出模块210、按键输入模块211以及显示器212等。具体的，所述输入输出模块还可包括：摄像头、触摸屏以及传感器等等。其中，所述输入输出模块均通过用户接口209与终端处理器201进行通信。
存储器202与终端处理器201耦合，用于存储各种软件程序和/或多组指令。具体的，存储器202可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器202可以存储操作系统(下述简称系统)，例如ANDROID，IOS，WINDOWS，或者LINUX等嵌入式操作系统。存储器202还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。存储器202还可以存储用户接口程序，该用户接口程序可以通过图形化的操作界面将应用程序的内容形象逼真的显示出来，并通过菜单、对话框以及按键等输入控件接收用户对应用程序的控制操作。
在本申请的一些实施例中，存储器202可用于存储本申请的一个或多个实施例提供的路径转换方法在终端200侧的实现程序。关于本申请的一个或多个实施例提供的路径转换方法的实现，请参考后续实施例。
终端处理器201可用于读取和执行计算机可读指令。具体的，终端处理器201可用于调用存储于存储器212中的程序，例如本申请的一个或多个实施例提供的资源分配方法在终端200侧的实现程序，并执行该程序包含的指令。
可以理解的，终端200可以是图5示出的无线通信系统100中的终端103，可实施为移动设备，移动台(mobile station)，移动单元(mobile unit)，无线单元，远程单元，用户代理，移动客户端等等。
需要说明的，图3所示的终端200仅仅是本申请实施例的一种实现方式，实际应用中，终端200还可以包括更多或更少的部件，这里不作限制。
参考图4，图4示出了本申请的一些实施例提供的网络设备300。如图4所示，网络设备300可包括：一个或多个网络设备处理器301、存储器302、通信接口303、发射器305、接收器306、耦合器307和天线308。这些部件可通过总线304或者其他式连接，图4以通过总线连接为例。其中：
通信接口303可用于网络设备300与其他通信设备，例如终端设备或其他网络设备，进行通信。具体的，通信接口303通信接口203可以是长期演进(LTE)(4G)通信接口，也可以是5G或者未来新空口的通信接口。不限于无线通信接口，网络设备300还可以配置有有线的通信接口303来支持有线通信，例如一个网络设备300与其他网络设备300之间的回程链接可以是有线通信连接。
发射器305可用于对网络设备处理器301输出的信号进行发射处理，例如信号调制。接收器306可用于对天线308接收的移动通信信号进行接收处理。例如信号解调。在本申请的一些实施例中，发射器305和接收器306可看作一个无线调制解调器。在网络设备300中，发射器305和接收器306的数量均可以是一个或者多个。天线308可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器307可用于将移动通信号分成多路，分配给多个的接收器306。
存储器302与网络设备处理器301耦合，用于存储各种软件程序和/或多组指令。具体的，存储器302可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器302可以存储操作系统(下述简称系统)，例如uCOS、VxWorks、RTLinux等嵌入式操作系统。存储器302还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。
网络设备处理器301可用于进行无线信道管理、实施呼叫和通信链路的建立和拆除，并为本控制区内的用户提供小区切换控制等。具体的，网络设备处理器301可包括：管理/通信模块(Administration Module/Communication Module，AM/CM)(用于话路交换和信息交换的中心)、基本模块(Basic Module，BM)(用于完成呼叫处理、信令处理、无线资源管理、无线链路的管理和电路维护功能)、码变换及子复用单元(Transcoder and SubMultiplexer， TCSM)(用于完成复用解复用及码变换功能)等等。
本申请实施例中，网络设备处理器301可用于读取和执行计算机可读指令。具体的，网络设备处理器301可用于调用存储于存储器302中的程序，例如本申请的一个或多个实施例提供的路径转换方法在网络设备300侧的实现程序，并执行该程序包含的指令。
可以理解的，网络设备300可以是图5示出的无线通信系统100中的基站101，可实施为基站收发台，无线收发器，一个基本服务集(BSS)，一个扩展服务集(ESS)，NodeB，eNodeB，接入点或TRP等等。
需要说明的，图4所示的网络设备300仅仅是本申请实施例的一种实现方式，实际应用中，网络设备300还可以包括更多或更少的部件，这里不作限制。
基于前面实施例中描述的无线通信系统100、终端200及网络设备300，本申请提供了一种路径转换方法。
本申请涉及的主要发明原理可包括：在中继通信中，如果中继设备无法再为远端终端提供中继服务，中继设备可以触发将远端终端从通过中继设备与网络设备进行通信的非直连路径转换到与网络设备直接进行通信的直连路径，并释放中继终端与远端终端之间的短距离链路。这样便于中继设备根据自身状况及时的、快速的触发远端终端的路径转换，甚至可以实现在侧行链路不中断数据通信的情况下实现所述路径转换，从而确保远端终端与网络设备之间的数据通信不中断。
中继设备无法再为远端终端提供中继服务的场景可以包括但不限于下述示例描述的场景：例如，当中继设备103需要发起电路域(CS)的呼叫时，中继设备103需要执行电路域回退(CSFB)，接入2G或3G网络。当中继设备103接入2G或3G网络后，将无法再继续为远端终端105提供中继服务。再例如，当中继设备103的电量不足时，中继设备103可能也无法再为远端终端105提供中继服务。
关于中继设备(下面简称Relay)如何触发远端终端(下面简称Remote)的路径转换，本申请主要提供了下述两个方案：
方案一：Relay请求网络设备触发Remote执行路径转换，网络设备对路径转换进行配置。
方案二：Relay直接通知Remote执行路径转换。
在上述方案一中，Relay可以在Remote切换到直连路径后再释放短距离链路，可实现Remote在从非直连路径到直连路径转换过程中的业务连续性。在上述方案二中，Relay直接通知Remote执行路径切换，可以减少Relay释放短距离链路所需的时间。后续会通过实施例描述上述两个方案，这里先不展开。
本申请中，Relay可以称为第一终端，Remote可以称为第二终端。不限于中继终端，本申请中，Relay还可以是中继微基站、中继收发器等。
首先，结合图5-7实施例，详细说明本申请提供的方案一。
图5示出了本申请提供的一种路径转换方法的流程示意图。下面展开：
S100，中继终端的上层触发释放中继终端与远端终端之间的短距离链路。除了侧行链 路技术，中继设备与远端终端之间还可以是其他形式的短距离链路，例如WLAN或蓝牙等链路中的任意一种。
S101，中继终端向网络设备发送第一消息，所述第一消息可用于向网络设备请求将远端终端从非直连路径转换到直连路径，或用于请求释放中继终端与远端终端间的短距离链路的连接。
具体的，所述请求释放第一终端与第二终端之间的链路可包括如下两种方式：
第一种：第一终端发第一消息给第一网络设备，请求第一网络设备来释放第一终端与第二终端之间的链路。
第二种：第一终端发第一消息给第一网络设备，收到第一网络设备的响应消息后，第一终端自己释放第一终端与第二终端之间的链路。
具体的，第一消息可以为RRC消息。可选的，第一消息中可以包含中继终端释放短距离链路的原因。例如：中继终端需要做电路域回落(CSFB)，或者中继终端的电量不足等。示例仅仅是本申请提供的一些实施例，实际应用中，还可以包括其他中继终端释放短距离链路的原因，这里不作限制。
S102，网络设备向中继终端连接的远端终端发送第二消息，所述第二消息可用于配置远端终端从非直连路径转换到直连路径。
具体的，所述第二消息可以为RRC连接重配消息(RRC connection reconfiguration)消息。所述第二消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值。其中：
上述小区标识可以为远端终端转换到直连路径后接入的小区的标识。上述小区标识可以为小区的物理小区标识(physical Cell Identity，PCI)，或者上述小区标识可以为能够在公共陆地移动网络(public land mobile network，PLMN)中唯一识别小区的小区标识(cell identity)，或者上述小区标识可以为小区全球唯一的小区标识(cell global identity，CGI)。
上述随机接入(Random Access，RA)配置信息可以为远端终端在所述小区发起随机接入时的资源配置信息，可包括随机接入的前导配置和物理随机接入信道配置。
上述第一指示信息可用于指示远端终端是否在与上述小区标识对应小区进行下行同步后再断开与中继终端的连接。
上述第一时间值可以为远端终端接入上述小区标识对应小区所允许的最长时间。如果超出该时间后，则可以认为远端终端接入小区失败。
S103，远端终端在接收到第二消息后，可以执行从非直连路径到直连路径的转换。并且，远端终端还可以启动第一计时器，第一计时器的时间长度等于第二消息中的第一时间值，用于限制远端终端接入上述小区标识对应的小区的最长时间。如果在第一计时器超时时远端终端仍未接入小区，则可以认为小区接入失败。若该情况发生，远端终端需要触发无线资源控制连接重建过程。
本实施例中，远端终端可以通过下述三种方式执行从非直连路径到直连路径的转换：
方式一：无论第二消息中是否包含上述第一指示信息，在与上述小区标识对应的小区进行下行同步过程中，远端终端可以继续保持与中继终端的连接，即可以继续通过中继终端和网络设备进行数据通信。在与上述小区标识对应的小区的完成下行同步后，远端终端 可以断开与中继终端的连接，停止通过中继终端和网络设备进行数据通信，转到与网络设备通过直连路径进行数据的发送和接收。
方式二：无论第二消息中是否包含上述第一指示信息，在收到所述第二消息后，远端终端即可断开与中继终端的连接，停止通过中继终端和网络设备进行数据通信。之后，远端终端可以开始与上述小区标识对应的小区的下行同步过程以及随机接入过程。
方式三：如果所述第一消息包含上述第一指示信息，且上述第一指示信息指示远端终端在与小区进行下行同步后再断开和中继终端的连接，则远端终端可以按照方式一进行路径转换。反之，远端终端可以按照方式二进行路径转换。
可以理解的，采用方式一，能够保证远端终端在从非直连路径到直连路径转换过程中的业务连续性。
一种可能的特殊情况是，远端终端在未接收到所述第二消息的情况下，中继终端已经断开与远端终端的链路的连接。在该情况下，当远端终端检测不到中继终端发送的发现消息时，远端终端认为和中继终端之间的链路发生失败，远端终端触发无线资源控制连接重建过程。
S104，远端终端可以通过随机接入过程接入上述小区标识对应的小区，并在接入成功后，可以向网络设备发送RRC连接重配完成消息。
S105，网络设备可以向中继终端发送第三消息，第三消息可用于指示中继终端释放短距离链路。具体的，第三消息的具体实现可包括：
实现方式一：第三消息可以为新定义的一条RRC消息。
实现方式二：第三消息可以为RRC连接重配(RRCConnectionReconfiguration)消息。RRC连接重配消息可以包含一个指示信息，该指示信息可用于指示中继终端释放短距离链路。
实现方式三：第三消息可以为RRC连接重配消息。第三消息可以用于配置中继终端释放所有的侧行链路承载，从而隐式的配置中继终端释放前述短距离链路。
具体的，网络设备可以在下面两种场景中触发中继终端释放短距离链路，即向中继终端发送所述第三消息。
第一种触发场景：网络设备确定中继终端下的所有远端终端都已经成功接收到所述第二消息。
这里，确定远端终端已经成功接收到第二消息的条件可以包括如下几种方式中的任意一种：
(1)网络设备收到远端终端发送的针对第二消息的HARQ ACK或者RLC ACK；
(2)网络设备收到远端终端发送的随机接入前导(preamble)；
(3)网络设备收到远端终端发送的RRC连接重配完成消息。
第二种触发场景：网络设备确定远端终端接入小区失败。
这里，确定远端终端接入小区失败的判断条件可以包括：网络设备在上述第二消息中的第一时间值所限制的时间内没有接收到远端终端发送的RRC连接重配完成消息。
S106，中继终端在接收到网络设备发送的第三消息后，可以释放短距离链路。
这里，释放短距离链路的具体实现可以包括以下几个方面：
(1)中继终端释放与所有远端终端间的侧行链路承载，包括释放所有侧行链路承载的无线链路层控制协议(radio link control，RLC)实体，逻辑信道；
(2)释放媒体接入控制(media access control，MAC)层与侧行链路相关的配置；
(3)释放物理层(physical layer，PHY)与侧行链路相关的配置；
(4)释放所有侧行链路的资源池和资源配置。
可以理解的，在图5实施例中，中继终端(通过第一消息)请求网络设备触发远端终端的路径转换，网络设备为远端终端的路径转换进行配置(如第二消息中的小区标识、随机接入配置等)在图5实施例中，中继终端与远端终端之间的短距离链路的释放由网络设备(通过第三消息)触发。
图6示出了本申请提供的另一种路径转换方法的流程示意图。下面展开：
S200，中继终端的上层触发释放中继终端与远端终端之间的短距离链路。除了侧行链路技术，中继设备与远端终端之间还可以是其他形式的短距离链路，例如WLAN或蓝牙等链路中的任意一种。
S201，中继终端向网络设备发送第一消息，所述第一消息可用于向网络设备请求将远端终端从非直连路径转换到直连路径，或用于请求释放中继终端与远端终端间的短距离链路的连接。
具体的，所述请求释放第一终端与第二终端之间的链路可包括如下两种方式：
第一种：第一终端发第一消息给第一网络设备，请求第一网络设备来释放第一终端与第二终端之间的链路。
第二种：第一终端发第一消息给第一网络设备，收到第一网络设备的响应消息后，第一终端自己释放第一终端与第二终端之间的链路。
具体的，第一消息可以为RRC消息。可选的，第一消息可以包含中继终端释放短距离链路的原因。例如：中继终端需要做电路域回落(CSFB)，或者中继终端的电量不足等。示例仅仅是本申请提供的一些实施例，实际应用中，还可以包括其他中继终端释放短距离链路的原因，这里不作限制。
S202，网络设备向中继终端连接的远端终端发送第二消息，所述第二消息可用于配置远端终端从非直连路径转换到直连路径。
具体的，第二消息可以为RRC连接重配消息(RRC connection reconfiguration)消息。第二消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值。其中：
上述小区标识可以为远端终端转换到直连路径后接入的小区的标识。上述小区标识可以为小区的物理小区标识(physical Cell Identity，PCI)，或者上述小区标识可以为能够在公共陆地移动网络(public land mobile network，PLMN)中唯一识别小区的小区标识(cell identity)，或者上述小区标识可以为小区全球唯一的小区标识(cell global identity，CGI)。
上述随机接入(Random Access，RA)配置信息可以为远端终端在所述小区发起随机接入时的资源配置信息，可包括随机接入的前导配置和物理随机接入信道配置。
上述第一指示信息可用于指示远端终端是否在与上述小区标识对应小区进行下行同步 后再断开与中继终端的连接。
上述第一时间值可以为远端终端接入上述小区标识对应小区所允许的最长时间。如果超出该时间后，则可以认为远端终端接入小区失败。
S203，远端终端在接收到第二消息后，可以执行从非直连路径到直连路径的转换，并向中继终端发送第三消息。所述第三消息可用于指示中继终端释放中继终端与远端终端之间的短距离链路。在接收到第二消息后，远端终端还可以启动第一计时器，第一计时器的时间长度等于第二消息中的第一时间值，用于限制远端终端接入上述小区标识对应的小区的最长时间。如果在第一计时器计时结束时远端终端仍未接入小区，则可以认为小区接入失败。若该情况发生，远端终端触发无线资源控制连接重建过程。
本实施例中，远端终端触发中继终端释放短距离链路(即发送第三消息)和远端终端执行从非直连路径转换到直连路径的时间顺序，包括如下三种方式：
方式一：无论第二消息中是否包含上述第一指示信息，在与上述小区标识对应的小区进行下行同步过程中，远端终端可以继续保持与中继终端的连接，即可以继续通过中继终端和网络设备进行数据通信。在与上述小区标识对应的小区的完成下行同步后，远端终端可以向中继终端发送第三消息，触发中继终端释放短距离链路，停止通过中继终端与网络设备进行数据通信，转到直连路径与网络设备进行数据通信。
方式二：无论第二消息中是否包含上述第一指示信息，在收到所述第二消息后，远端终端即可向中继终端发送第三消息，触发断开与中继终端的连接，停止通过中继终端和网络设备进行数据通信。之后，远端终端可以开始与上述小区标识对应的小区的下行同步过程以及随机接入过程。
方式三：如果所述第一消息包含上述第一指示信息，且上述第一指示信息指示远端终端在与小区进行下行同步后再断开和中继终端的连接，则远端终端可以按照方式一进行路径转换。反之，远端终端可以按照方式二进行路径转换。
可以理解的，采用方式一，能够保证远端终端在从非直连路径到直连路径转换过程中的业务连续性。
一种可能的特殊情况是，远端终端在未接收到所述第二消息的情况下，中继终端已经断开与远端终端的链路的连接。在该情况下，当远端终端检测不到中继终端发送的发现消息时，远端终端认为和中继终端之间的链路发生失败，远端终端触发无线资源控制连接重建过程。
S204，远端终端与上述小区标识对应的小区进行下行同步。
S205，中继终端在接收到远端终端发送的第三消息之后，释放中继终端与远端终端之间的短距离链路。
这里，释放短距离链路的具体实现可以包括以下几个方面：
(1)中继终端释放与所有远端终端间的侧行链路承载，包括释放所有侧行链路承载的无线链路层控制协议(radio link control，RLC)实体，逻辑信道；
(2)释放媒体接入控制(media access control，MAC)层与侧行链路相关的配置；
(3)释放物理层(physical layer，PHY)与侧行链路相关的配置；
(4)释放所有侧行链路的资源池和资源配置。
S206，远端终端在上述小区标识对应的小区执行随机接入过程，并在小区接入完成后，向网络设备发送RRC连接重配完成消息。
可以理解的，在图6实施例中，中继终端(通过第一消息)请求网络设备触发远端终端的路径转换，网络设备为远端终端的路径转换进行配置(如第二消息中的小区标识、随机接入配置等)。在图6实施例中，中继终端与远端终端之间的短距离链路的释放由远端终端(通过第三消息)触发。
图7示出了本申请提供的再一种路径转换方法的流程示意图。下面展开：
S300，中继终端的上层触发释放中继终端与远端终端之间的短距离链路。除了侧行链路技术，中继设备与远端终端之间还可以是其他形式的短距离链路，例如WLAN或蓝牙等链路中的任意一种。
S301，中继终端向网络设备发送第一消息，所述第一消息可用于向网络设备请求将远端终端从非直连路径转换到直连路径，或用于请求释放中继终端与远端终端间的短距离链路的连接。
具体的，所述请求释放第一终端与第二终端之间的链路可包括如下两种方式：
第一种：第一终端发第一消息给第一网络设备，请求第一网络设备来释放第一终端与第二终端之间的链路。
第二种：第一终端发第一消息给第一网络设备，收到第一网络设备的响应消息后，第一终端自己释放第一终端与第二终端之间的链路。
具体的，第一消息可以为RRC消息。可选的，第一消息可以包含中继终端释放短距离链路的原因。例如：中继终端需要做电路域回落(CSFB)，或者中继终端的电量不足等。示例仅仅是本申请提供的一些实施例，实际应用中，还可以包括其他中继终端释放短距离链路的原因，这里不作限制。
S302，网络设备向中继终端连接的远端终端发送第二消息，所述第二消息可用于配置远端终端从非直连路径转换到直连路径。
具体的，第二消息可以为RRC连接重配消息(RRC connection reconfiguration)消息。第二消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值。关于第二消息中的各项内容的具体定义和解释，可参考图5或图6实施例中的相关内容，这里不再赘述。
S303，中继终端在接收到网络设备发送的第二消息之后，可以启动第一计时器，第一计时器的时间长度等于第二消息中的第一时间值，用于指示中继终端释放短距离链路的时间。一旦第一计时器超时时，中继终端即可释放短距离链路。
S304，远端终端与上述小区标识对应的小区进行下行同步。
步骤303和步骤304没有时间上的先后顺序。
S305，当第一计时器超时时，中继终端释放中继终端与远端终端之间的短距离链路。
这里，释放短距离链路的具体实现可以包括以下几个方面：
(1)中继终端释放与所有远端终端间的侧行链路承载，包括释放所有侧行链路承载的无线链路层控制协议(radio link control，RLC)实体，逻辑信道；
(2)释放媒体接入控制(media access control，MAC)层与侧行链路相关的配置；
(3)释放物理层(physical layer，PHY)与侧行链路相关的配置；
(4)释放所有侧行链路的资源池和资源配置。
S306，远端终端在上述小区标识对应的小区执行随机接入过程，并在小区接入完成后，向网络设备发送RRC连接重配完成消息。
具体的，S306可以发生在S305之前，S306也可以发生在S305之后，这两个步骤之间的先后顺序具体可取决于远端终端执行小区同步需要的时间以及第一时间值的大小，这里不作限制。实际应用中，为了确保远端终端在执行路径转换的过程中的业务连续性，可以适当将第一时间值设置成较大的值，以便远端终端能够在第一计时器超时之前便成功接入小区并完成RRC重配置过程。
一种可能的特殊情况是，远端终端在未接收到所述第二消息的情况下，中继终端已经断开与远端终端的链路的连接。在该情况下，当远端终端检测不到中继终端发送的发现消息时，远端终端认为和中继终端之间的链路发生失败，远端终端触发无线资源控制连接重建过程。
可以理解的，在图7实施例中，中继终端(通过第一消息)请求网络设备触发远端终端的路径转换，网络设备为远端终端的路径转换进行配置(如第二消息中的小区标识、随机接入配置等)。在图7实施例中，中继终端与远端终端之间的短距离链路的释放由中继终端自己(通过第一计时器)触发。
其次，结合图8-11实施例，详细说明本申请提供的方案二。
图8示出了本申请提供的再一种路径转换方法的流程示意图。下面展开：
S400，中继终端的上层触发释放中继终端与远端终端之间的短距离链路。除了侧行链路技术，中继设备与远端终端之间还可以是其他形式的短距离链路，例如WLAN或蓝牙等链路中的任意一种。
S401，中继终端向远端终端发送第四消息，第四消息可用于通知中继终端将要释放短距离链路，从而指示远端终端从非直连路径转换到与直连路径。
具体的，第四消息可以实现为但不限于PC5信令。可选的，第四消息可以包含中继终端释放短距离链路的原因。例如：中继终端需要做电路域回落(CSFB)，或者中继终端的电量不足等。示例仅仅是本申请提供的一些实施例，实际应用中，还可以包括其他中继终端释放短距离链路的原因，这里不作限制。
S402，远端终端在接收到第四消息之后，触发从非直连路径到直连路径的转换。
一种可能的特殊情况是，远端终端在未接收到所述第二消息的情况下，中继终端已经断开与远端终端的链路的连接。在该情况下，当远端终端检测不到中继终端发送的发现消息时，远端终端认为和中继终端之间的链路发生失败，远端终端触发无线资源控制连接重建过程。
S403，远端终端向网络设备发送第五消息，第五消息可用于请求从非直连路径到直连路径的转换。
可选的，第五消息可以包含中继终端释放短距离链路的原因。进一步，第五消息可还 可以包含远端终端和中继终端之间的短距离链路的链路质量。
S404，网络设备向远端终端发送第六消息，第六消息可用于配置远端终端从非直连路径转换到直连路径。
具体的，第六消息可以为RRC连接重配消息(RRC connection reconfiguration)消息。第六消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值。这里，第六消息相当于图5-7实施例中的第二消息，关于第六消息中的各项内容的具体定义和解释，可参考图5-7实施例中第二消息的相关内容，这里不再赘述。
S405，远端终端在接收到第六消息后，可以执行从非直连路径到直连路径的转换，并向中继终端发送第七消息。这里，第七消息相当于图6实施例中的第三消息，可用于指示中继终端释放中继终端与远端终端之间的短距离链路。在收到第七消息后，远端终端还可以启动第一计时器，第一计时器的时间长度等于第二消息中的第一时间值，用于限制远端终端接入上述小区标识对应的小区的最长时间。如果在第一计时器计时结束时远端终端仍未接入小区，则可以认为小区接入失败。若该情况发生，远端终端触发无线资源控制连接重建过程。
本实施例中，远端终端触发中继终端释放短距离链路(即发送第七消息)和远端终端执行从非直连路径转换到直连路径的时间顺序，包括如下三种方式：
方式一：无论第六消息中是否包含上述第一指示信息，在与上述小区标识对应的小区进行下行同步过程中，远端终端可以继续保持与中继终端的连接，即可以继续通过中继终端和网络设备进行数据通信。在与上述小区标识对应的小区的完成下行同步后，远端终端可以向中继终端发送第七消息，触发中继终端释放短距离链路，停止通过中继终端与网络设备进行数据通信，转到直连路径与网络设备进行数据通信。
方式二：无论第六消息中是否包含上述第一指示信息，在收到所述第二消息后，远端终端即可向中继终端发送第七消息，触发断开与中继终端的连接，停止通过中继终端和网络设备进行数据通信。之后，远端终端可以开始与上述小区标识对应的小区的下行同步过程以及随机接入过程。
方式三：如果所述第六消息包含上述第一指示信息，且上述第一指示信息指示远端终端在与小区进行下行同步后再断开和中继终端的连接，则远端终端可以按照方式一进行路径转换。反之，远端终端可以按照方式二进行路径转换。
可以理解的，采用方式一，能够保证远端终端在从非直连路径到直连路径转换过程中的业务连续性。
S406，远端终端与上述小区标识对应的小区进行下行同步。
S407，中继终端在接收到远端终端发送的第七消息之后，释放中继终端与远端终端之间的短距离链路。
这里，释放短距离链路的具体实现可以包括以下几个方面：
(1)中继终端释放与所有远端终端间的侧行链路承载，包括释放所有侧行链路承载的无线链路层控制协议(RLC)实体，逻辑信道；
(2)释放媒体接入控制(MAC)层与侧行链路相关的配置；
(3)释放物理层(PHY)与侧行链路相关的配置；
(4)释放所有侧行链路的资源池和资源配置。
S408，远端终端在上述小区标识对应的小区执行随机接入过程，并在小区接入完成后，向网络设备发送RRC连接重配完成消息。
可以理解的，在图8实施例中，中继终端(通过第四消息)通知远端终端执行路径转换。远端终端(通过第五消息)请求网络设备配置(第六消息)路径转换。在图8实施例中，中继终端与远端终端之间的短距离链路的释放由远端终端(通过第七消息)触发。
图9示出了本申请提供的再一种路径转换方法的流程示意图。在图9实施例中，在网络设备所在的小区，远端终端侧没有小区无线网络临时标识(Cell Radio Network Temporary Identifier，C-RNTI)。下面展开：
S500，中继终端的上层触发释放中继终端与远端终端之间的短距离链路。除了侧行链路技术，中继设备与远端终端之间还可以是其他形式的短距离链路，例如WLAN或蓝牙等链路中的任意一种。
S501，中继终端向远端终端发送第四消息，第四消息可用于通知远端终端中继终端将要释放短距离链路，从而指示远端终端从非直连路径转换到与直连路径。
具体的，第四消息可以实现为但不限于PC5信令。所述第四消息可以包括中继终端的C-RNTI，远端终端的本地标识(local ID)，中继终端的服务小区的公共无线资源配置信息，中继终端的服务小区的小区标识。这里，中继终端的C-RNTI和远端终端的local ID可用于标识远端终端在网络侧的临时身份。
可选的，第四消息还可以包含中继终端释放短距离链路的原因。例如：中继终端需要做电路域回落(CSFB)，或者中继终端的电量不足等。示例仅仅是本申请提供的一些实施例，实际应用中，还可以包括其他中继终端释放短距离链路的原因，这里不作限制。
S502，中继终端可以在向远端终端发送第四消息之后释放中继终端与远端终端之间的短距离链路。
这里，释放短距离链路的具体实现可以包括以下几个方面：
(1)中继终端释放与所有远端终端间的侧行链路承载，包括释放所有侧行链路承载的无线链路层控制协议(RLC)实体，逻辑信道；
(2)释放媒体接入控制(MAC)层与侧行链路相关的配置；
(3)释放物理层(PHY)与侧行链路相关的配置；
(4)释放所有侧行链路的资源池和资源配置。
S503，远端终端在接收到第四消息之后，触发从非直连路径到直连路径的转换，与第四消息中的小区标识对应的小区进行下行同步，并触发随机接入过程。
在收到第四消息后，远端终端还可以启动第一计时器，第一计时器的时间长度的值可以由中继设备通过第四消息通知，也可以为预定义的值，用于限制远端终端接入上述小区标识对应的小区的最长时间。如果在第一计时器计时结束时远端终端仍未接入小区，则可以认为小区接入失败。若该情况发生，远端终端触发无线资源控制连接重建过程。
一种可能的特殊情况是，远端终端在未接收到所述第四消息的情况下，中继终端已经断开与远端终端的链路的连接。在该情况下，当远端终端检测不到中继终端发送的发现消 息时，远端终端认为和中继终端之间的链路发生失败，远端终端触发无线资源控制连接重建过程。
S504-S505，远端终端和网络设备执行随机接入的第一步和第二步。即，远端终端向网络设备发送随机接入前导(preamble)，网络设备向远端终端反馈随机接入响应。
S506，远端终端向网络设备发送随机接入的消息3(MSG 3)，该消息3可包括：中继终端的C-RNTI，远端终端的本地标识(local ID)。具体的，该消息3可以是RRC消息或者MAC层控制实体(MAC control element，MAC CE)。
S507，网络设备向远端终端返回随机接入的消息4(MSG4)。该消息4可包括与远端终端发送的随机接入的消息3中相同的内容。该消息4可以是RRC消息或者MAC CE。
S508，远端终端和网络设备之前进行直连路径的RRC连接重配过程。
可以理解的，在图9实施例中，在网络设备所在的小区，远端终端没有C-RNTI。中继终端(通过第四消息)通知远端终端执行路径转换，并配置(如relay的C-RNTI和remote的localID、cell ID、无线资源配置信息等)远端终端的路径转换。在图9实施例中，中继终端在向远端设备发送第四消息之后便释放短距离链路，无需触发条件。
图10示出了本申请提供的再一种路径转换方法的流程示意图。在图10实施例中，在网络设备所在的小区，远端终端侧具有小区无线网络临时标识(Cell Radio Network Temporary Identifier，C-RNTI)。远端终端的C-RNTI可以在远端终端与中继终端建立短距离通信连接时，由网络设备通过中继终端发送给远端终端，或者由远端终端在直连路径时直接从网络设备获得。下面展开：
S600，中继终端的上层触发释放中继终端与远端终端之间的短距离链路。除了侧行链路技术，中继设备与远端终端之间还可以是其他形式的短距离链路，例如WLAN或蓝牙等链路中的任意一种。
S601，中继终端向远端终端发送第四消息，第四消息可用于通知中继终端将要释放短距离链路，从而指示远端终端从非直连路径转换到与直连路径。
具体的，第四消息可以实现为但不限于PC5信令。所述第四消息可以包括中继终端的服务小区的公共无线资源配置信息，中继终端的服务小区的小区标识。可选的，第四消息还可以包含中继终端释放短距离链路的原因。例如：中继终端需要做电路域回落(CSFB)，或者中继终端的电量不足等。示例仅仅是本申请提供的一些实施例，第四消息还可以包括其他中继终端释放短距离链路的原因，这里不作限制。
S602，中继终端在向远端终端发送第四消息之后，释放中继终端与远端终端之间的短距离链路。
这里，释放短距离链路的具体实现可以包括以下几个方面：
(1)中继终端释放与所有远端终端间的侧行链路承载，包括释放所有侧行链路承载的无线链路层控制协议(RLC)实体，逻辑信道；
(2)释放媒体接入控制(MAC)层与侧行链路相关的配置；
(3)释放物理层(PHY)与侧行链路相关的配置；
(4)释放所有侧行链路的资源池和资源配置。
S603，远端终端在接收到中继终端发送的第四消息之后，触发从非直连路径到直连路径的转换,与第四消息中的小区标识对应的小区进行下行同步。
在收到第四消息后，远端终端还可以启动第一计时器，第一计时器的时间长度的值可以由中继设备通过第四消息通知，也可以为预定义的值，用于限制远端终端接入上述小区标识对应的小区的最长时间。如果在第一计时器计时结束时远端终端仍未接入小区，则可以认为小区接入失败。若该情况发生，远端终端触发无线资源控制连接重建过程。
一种可能的特殊情况是，远端终端在未接收到所述第四消息的情况下，中继终端已经断开与远端终端的链路的连接。在该情况下，当远端终端检测不到中继终端发送的发现消息时，远端终端认为和中继终端之间的链路发生失败，远端终端触发无线资源控制连接重建过程。
S604，远端终端执行随机接入过程。
S605，远端终端与网络设备之间进行直连路径的RRC连接重配过程。
可以理解的，在图10实施例中，在网络设备所在的小区，远端终端具有C-RNTI。中继终端(通过第四消息)通知远端终端执行路径转换，并配置(如cell ID、无线资源配置信息等)远端终端的路径转换。在图10实施例中，中继终端在向远端终端发送第四消息之后便释放短距离链路，无需触发条件。
图11示出了本申请提供的再一种路径转换方法的流程示意图。在图11实施例中，在网络设备所在的小区，远端终端侧具有小区无线网络临时标识(Cell Radio Network Temporary Identifier，C-RNTI)。远端终端的C-RNTI可以在远端终端与中继终端建立短距离通信连接时，由网络设备通过中继终端发送给远端终端，或者由远端终端在直连路径时直接从网络设备获得。下面展开：
S700，中继终端的上层触发释放中继终端与远端终端之间的短距离链路。除了侧行链路技术，中继设备与远端终端之间还可以是其他形式的短距离链路，例如WLAN或蓝牙等链路中的任意一种。
S701，中继终端向远端终端发送第四消息，第四消息可用于通知中继终端将要释放短距离链路，从而指示远端终端从非直连路径转换到与直连路径。
具体的，第四消息可以实现为但不限于PC5信令。可选的，第四消息可以包含中继终端释放短距离链路的原因。例如：中继终端需要做电路域回落(CSFB)，或者中继终端的电量不足等。示例仅仅是本申请提供的一些实施例，第四消息还可以包括其他中继终端释放短距离链路的原因，这里不作限制。
S702，中继终端在向远端终端发送第四消息之后，释放中继终端与远端终端之间的短距离链路。
这里，释放短距离链路的具体实现可以包括以下几个方面：
(1)中继终端释放与所有远端终端间的侧行链路承载，包括释放所有侧行链路承载的无线链路层控制协议(RLC)实体，逻辑信道；
(2)释放媒体接入控制(MAC)层与侧行链路相关的配置；
(3)释放物理层(PHY)与侧行链路相关的配置；
(4)释放所有侧行链路的资源池和资源配置。
S703，远端终端在接收到中继终端发送的第四消息之后，远端终端发起RRC重建过程。
一种可能的特殊情况是，远端终端在未接收到所述第四消息的情况下，中继终端已经断开与远端终端的链路的连接。在该情况下，当远端终端检测不到中继终端发送的发现消息时，远端终端认为和中继终端之间的链路发生失败，远端终端触发无线资源控制连接重建过程。
S704，远端终端与网络设备之间进行直连路径的RRC连接重配过程。
可以理解的，在图11实施例中，中继终端(通过第四消息)仅通知远端终端执行路径转换，不对路径转换进行配置。远端终端在接收到所述第四消息之后，便触发重新建立RRC连接，并基于重建的RRC连接(直连路径)进行RRC重配。
在上述方案一的各个实施例(图5-7实施例)中，释放中继终端与远端终端之间的短距离链路的实现方式可包括下述几种：
第一种实现方式：中继终端与远端终端之间的短距离链路由网络设备触发释放，可参考图5。
具体的，在网络设备为远端终端的链路转换进行配置(即网络设备向远端终端发送第二消息)之后，网络设备向中继终端发送第三消息，触发中继终端释放短距离链路。
第二种实现方式：中继终端与远端终端之间的短距离链路由远端终端触发释放，可参考图6。
具体的，在远端终端接收到网络设备发送的链路转换的配置信息(即远端终端接收到网络设备发送的第二消息)之后，远端终端向中继终端发送第三消息，触发中继终端释放短距离链路。
第三种实现方式：在中继终端请求释放短距离通信链路(即中继终端向网络设备发送第一消息)后，当中继终端保持短距离链路的时间超过第一时间长度时，中继终端释放短距离链路，可参考图7。
本申请中，上述方案一中的几种释放中继终端与远端终端之间的短距离链路的实现方式也可以适用上述方案二的各个实施例。
在上述方案二的各个实施例(图8-11实施例)中，释放中继终端与远端终端之间的短距离链路的实现方式可包括下述几种：
第一种实现方式：中继终端与远端终端之间的短距离链路由网络设备触发释放。
具体的，在网络设备为远端终端的链路转换进行配置(即网络设备向远端终端发送第六消息)之后，网络设备向中继终端发送第七消息，触发中继终端释放短距离链路。
第二种实现方式：中继终端与远端终端之间的短距离链路由远端终端触发释放，图8已示出。
具体的，在远端终端接收到网络设备发送的链路转换的配置信息(即远端终端接收到网络设备发送的第六消息)之后，远端终端向中继终端发送第七消息，触发中继终端释放短距离链路。
第三种实现方式：在中继终端通知释放短距离通信链路(即向远端终端发送第四消息) 后，当中继终端保持短距离链路的时间超过指定时间阈值时，中继终端释放短距离链路。关于该指定时间阈值的选取，中继终端可以根据实际需求进行设置，这里不作限制。
另外，在上述方案二中，中继终端还可以在通知短距离链路的释放之后，直接执行短距离链路的释放，无需触发条件，具体可参考图9-11实施例。
另外，本申请提供的路径转换方法还可以适用小区切换场景。在小区切换场景下，远端终端还可以从非直连路径转换到与中继终端连接的网络设备(可称为第一网络设备)不同的另一网络设备(可称为第二网络设备)。
下面以上述图5实施例和图8实施例为例，说明小区切换场景下的路径转换方法。
基于图5实施例，图12示出了本申请提供的小区切换场景下的一种路径转换方法。
与图5实施例的区别在于，在图12实施例中，第一网络设备和第二网络设备间需要执行切换准备过程，可参考S102’。另外，第一网络设备发送第三消息的时间可以为以下任意一种：
(1)第一网络发送第二消息后。
(2)第一网络设备收到远端终端发送的针对第二消息的HARQ ACK或者RLC ACK.
基于图8实施例，图13示出了本申请提供的小区切换场景下的另一种路径转换方法。
与图8实施例的区别在于，在图13实施例中，第一网络设备和第二网络设备间需要执行切换准备过程，可参考S404’。
从图12和图13的示例可以看出，基于本申请提供的上述图5-11实施例，小区切换场景下的路径转换方法还需要包括第一网络设备和第二网络设备间的小区切换准备过程。
参见图14，图14示出了本申请提供一种无线通信系统、终端及网络设备。无线通信系统10可包括：第一终端400、第二终端500和第一网络设备600。可选的，无线通信系统10还可包括：第二网络设备700。其中，第一终端400或第二终端500可以为图3实施例中的终端200，第一网络设备600或第二网络设备700可以为图4实施例中的网络设备300，无线通信系统10可以是图1描述的无线通信系统100。本申请中，无线通信系统10可以采用两种不同的路径转换方案。下面分别描述。
在方案一中，第一终端400请求网络设备600触发第二终端500执行路径转换，网络设备600对路径转换进行配置。可选的，第二终端500还可以从非直连路径转换到与第一终端400连接的第一网络设备600不同的另一网络设备，即第二网络设备700。下面分别描述第一终端400、第二终端500、第一网络设备600和第二网络设备700的实现：
如图14所示，第一终端400可包括：处理单元401和通信单元403。其中：
通信单元403可用于向第一网络设备600发送第一消息。
这里，第一消息可用于请求将第二终端500从通过第一终端400与第一网络设备600进行通信的非直连路径转换到与第一网络设备600或第二网络设备700进行通信的直连路径。或第一消息可用于请求释放第一终端400与第二终端500之间的链路。
处理单元401可用于释放第一终端400与第二终端500之间的链路。
具体的，处理单元401可用于通过以下几种方式释放第一终端400与第二终端500之 间的链路：
(1)处理单元401可用于在接收到第三消息之后，释放链路。
这里，第三消息可以是在第一网络设备600向第二终端500发送第二消息之后由第一网络设备600或者第二终端500发送的，用于指示第一终端400释放链路。
其中，第二消息可包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值，用于配置第二终端500从非直连路径转换到直连路径；
其中，第一指示信息可用于指示第二终端500是否在与小区标识对应的小区进行下行同步后再断开与第一终端400的连接。第一时间值可以为第二终端500接入小区标识对应的小区所允许的最长时间。
(2)处理单元401可用于当通信单元403在发送第一消息之后保持链路的时间长度超过第一时间长度时，释放链路。
如图14所示，第一网络设备600可包括：第一通信单元601和第二通信单元603。其中：
通信单元601可用于接收第一终端400发送的第一消息。
这里，第一消息可用于请求将第二终端500从通过第一终端400与第一网络设备600进行通信的非直连路径转换到与第一网络设备600或第二网络设备700进行通信的直连路径；或第一消息用于请求释放第一终端400与第二终端500之间的链路；其中，第一网络设备600与第二网络设备700不同。
通信单元601还可用于向第二终端500发送第二消息，第二消息可用于配置第二终端500从非直连路径转换到直连路径。
具体的，第二消息可包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值。其中，第一指示信息可用于指示第二终端500是否在与小区标识对应的小区进行下行同步后再断开与第一终端400的连接。第一时间值可以为第二终端500接入小区标识对应的小区所允许的最长时间。
如图14所示，第二终端500可包括：处理单元501和通信单元503。其中：
通信单元503可用于接收到第一网络设备600发送的第二消息，第二消息可用于配置第二终端500从通过第一终端400与第一网络设备600进行通信的非直连路径转换到与第一网络设备600或第二网络设备700进行通信的直连路径。
处理单元501可用于根据第二消息，从非直连路径转换到直连路径。
具体的，第二消息可包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值。其中，第一指示信息可用于指示第二终端500是否在与小区标识对应的小区进行下行同步后再断开与第一终端400的连接。第一时间值可用于指示第二终端500接入小区标识对应的小区所允许的最长时间。
可以理解的，在方案一中，第一终端400、第二终端500、第一网络设备600和第二网络设备700的具体实现可参考图5-7实施例或图12实施例，以及其他方案二相关的实施方式，这里不再赘述。
在方案二中，第一终端400直接通知第二终端500执行路径转换。可选的，第二终端500还可以从非直连路径转换到与第一终端400连接的第一网络设备600不同的另一网络设 备，即第二网络设备700。下面分别描述第一终端400、第二终端500、第一网络设备600和第二网络设备700的实现：
如图14所示，第一终端400可包括：处理单元401和通信单元403。其中：
通信单元403可用于向第二终端发送第四消息。
这里，第四消息可用于指示第二终端从通过第一终端与第一网络设备进行通信的非直连路径转换到与第一网络设备或第二网络设备进行通信的直连路径。或第四消息可用于指示释放第一终端与第二终端之间的链路。
处理单元401可用于释放第一终端与第二终端之间的链路。
具体的，处理单元401可用于通过以下几种方式释放第一终端400与第二终端500之间的链路：
(1)处理单元401可用于在接收到第七消息之后，释放链路。
这里，第七消息可以是在第一网络设备向第二终端发送第六消息之后由第一网络设备或者第二终端发送的，用于指示第一终端释放链路。
其中，第六消息可包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值，用于配置第二终端从非直连路径转换到直连路径。
(2)处理单元401可用于当第一终端在发送第四消息之后保持链路的时间长度超过第一时间长度时，放链路。
具体的，第四消息可以包括以下至少一项：第一终端的服务小区的小区标识，或者第一终端的服务小区的公共无线资源的配置信息。
如图14所示，第二终端500可包括：处理单元501和通信单元503。其中：
通信单元503可用于接收第一终端发送的第四消息。
其中，第四消息可以用于指示第二终端从通过第一终端与第一网络设备进行通信的非直连路径转换到与第一网络设备或第二网络设备进行通信的直连路径。或第四消息可以用于指示释放第一终端与第二终端之间的链路。
处理单元501可用于根据第四消息，从非直连路径转换到直连路径。
具体的，第四消息可以包括以下至少一项：第一终端的服务小区的小区标识，或者第一终端的服务小区的公共无线资源的配置信息。
可选的实施例中，通信单元503还可用于：向第一网络设备发送第二消息，用于请求从非直连路径转换到直连路径。并且，通信单元503还可用于接收第一网络设备发送的第六消息。
这里，第六消息可以包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值，用于配置第二终端从非直连路径转换到直连路径。其中，第一指示信息可以用于指示第二终端是否在与小区标识对应的小区进行下行同步后再断开与第一终端的连接。第一时间值可以为第二终端接入小区标识对应的小区所允许的最长时间。
可选的实施例中，通信单元503还可用于接收到第四消息后，触发无线资源控制连接重建过程。
可选的实施例中，通信单元503还可用于第二终端接入第一终端的服务小区，并向第一网络设备发送终端设备标识。其中，终端设备标识可以为第二终端的C-RNTI，或者可以 为第一终端的C-RNTI和第二终端的本地标识。具体的，终端设备标识可以携带在第四消息中。或者终端设备标识可以由第一终端在发送第四消息之前发送给第二终端。
可以理解的，在方案二中，第一终端400、第二终端500、第一网络设备600和第二网络设备700的具体实现可参考图8-11实施例或图13实施例，以及其他方案二相关的实施方式，这里不再赘述。
实施本申请提供的技术方案，在中继通信中，如果中继设备无法再为远端终端提供中继服务，中继设备可以触发将远端终端从通过中继设备与网络设备进行通信的非直连路径转换到与网络设备直接进行通信的直连路径，并释放中继终端与远端终端之间的短距离链路。这样便于中继设备根据自身状况及时的、快速的触发远端终端的路径转换，甚至可以实现在侧行链路不中断数据通信的情况下实现所述路径转换，从而确保远端终端与网络设备之间的数据通信不中断。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。

Claims (30)

  1. 一种路径转换方法，其特征在于，包括：
    第一终端向第一网络设备发送第一消息，所述第一消息用于请求将第二终端从通过所述第一终端与所述第一网络设备进行通信的非直连路径转换到与所述第一网络设备或第二网络设备进行通信的直连路径；或所述第一消息用于请求释放所述第一终端与所述第二终端之间的链路；其中，所述第一网络设备与所述第二网络设备不同；
    所述第一终端释放所述第一终端与所述第二终端之间的链路。
  2. 如权利要求1所述的方法，其特征在于，所述第一终端向第一网络设备发送第一消息后，所述第一终端释放所述第一终端与所述第二终端之间的链路，包括：
    所述第一终端在接收到第三消息之后，释放所述链路；所述第三消息是在所述第一网络设备向所述第二终端发送第二消息之后由所述第一网络设备或者所述第二终端发送的，用于指示所述第一终端释放所述链路；
    其中，所述第二消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值，用于配置所述第二终端从所述非直连路径转换到所述直连路径；
    其中，第一指示信息用于指示所述第二终端是否在与所述小区标识对应的小区进行下行同步后再断开与所述第一终端的连接；所述第一时间值为所述第二终端接入所述小区标识对应的小区所允许的最长时间；
    或者，
    当所述第一终端在发送所述第一消息之后保持所述链路的时间长度超过第一时间长度时，所述第一终端释放所述链路。
  3. 一种通信方法，其特征在于，包括：
    第一网络设备接收第一终端发送的第一消息，所述第一消息用于请求将第二终端从通过所述第一终端与所述第一网络设备进行通信的非直连路径转换到与所述第一网络设备或第二网络设备进行通信的直连路径；或所述第一消息用于请求释放所述第一终端与所述第二终端之间的链路；其中，所述第一网络设备与所述第二网络设备不同；
    所述第一网络设备向所述第二终端发送第二消息，所述第二消息用于配置所述第二终端从所述非直连路径转换到所述直连路径。
  4. 如权利要求3所述的方法，其特征在于，所述第二消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值；
    其中，第一指示信息用于指示所述第二终端是否在与所述小区标识对应的小区进行下行同步后再断开与所述第一终端的连接；所述第一时间值为所述第二终端接入所述小区标识对应的小区所允许的最长时间。
  5. 一种通信方法，其特征在于，包括：
    第二终端接收到第一络设备发送的第二消息，所述第二消息用于配置所述第二终端从通过所述第一终端与所述第一网络设备进行通信的非直连路径转换到与所述第一网络设备或第二网络设备进行通信的直连路径；其中，所述第一网络设备与所述第二网络设备不同；
    所述第二终端根据所述第二消息，从所述非直连路径转换到所述直连路径；
    其中，所述第二消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值；
    其中，第一指示信息用于指示所述第二终端是否在与所述小区标识对应的小区进行下行同步后再断开与所述第一终端的连接；第一时间值用于指示所述第二终端接入所述小区标识对应的小区所允许的最长时间。
  6. 一种路径转换方法，其特征在于，包括：
    第一终端向第二终端发送第四消息，所述第四消息用于指示所述第二终端从通过所述第一终端与第一网络设备进行通信的非直连路径转换到与所述第一网络设备或第二网络设备进行通信的直连路径；或所述第四消息用于指示释放所述第一终端与所述第二终端之间的链路；其中，所述第一网络设备与所述第二网络设备不同；
    所述第一终端释放所述第一终端与所述第二终端之间的链路。
  7. 如权利要求6所述的方法，其特征在于，所述第一终端释放所述第一终端与所述第二终端之间的链路，包括：
    所述第一终端在接收到第七消息之后，释放所述链路；所述第七消息是在所述第一网络设备向所述第二终端发送第六消息之后由所述第一网络设备或者所述第二终端发送的，用于指示所述第一终端释放所述链路；
    其中，所述第六消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值，用于配置所述第二终端从所述非直连路径转换到所述直连路径；
    或者，
    当所述第一终端在发送所述第四消息之后保持所述链路的时间长度超过第一时间长度时，所述第一终端释放所述链路。
  8. 如权利要求6所述的方法，其特征在于，所述第四消息包括以下至少一项：所述第一终端的服务小区的小区标识，或者所述第一终端的服务小区的公共无线资源的配置信息。
  9. 一种路径转换方法，其特征在于，包括：
    第二终端接收第一终端发送的第四消息，所述第四消息用于指示所述第二终端从通过所述第一终端与第一网络设备进行通信的非直连路径转换到与所述第一网络设备或第二网络设备进行通信的直连路径；或所述第四消息用于指示释放所述第一终端与所述第二终端之间的链路；其中，所述第一网络设备与所述第二网络设备不同；
    所述第二终端根据所述第四消息，从所述非直连路径转换到所述直连路径。
  10. 如权利要求9所述的方法，其特征在于，还包括：
    所述第二终端向所述第一网络设备发送第五消息，用于请求从所述非直连路径转换到所述直连路径；
    所述第二终端接收所述第一网络设备发送的第六消息，所述第六消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值，用于配置所述第二终端从所述非直连路径转换到所述直连路径；
    其中，第一指示信息用于指示所述第二终端是否在与所述小区标识对应的小区进行下行同步后再断开与所述第一终端的连接；所述第一时间值为所述第二终端接入所述小区标识对应的小区所允许的最长时间。
  11. 如权利要求9所述的方法，其特征在于，还包括：
    所述第二终端接收到所述第四消息后，所述第二终端触发无线资源控制连接重建过程。
  12. 如权利要求9所述的方法，其特征在于，所述第四消息包括以下至少一项：所述第一终端的服务小区的小区标识，或者所述第一终端的服务小区的公共无线资源的配置信息。
  13. 如权利要求12所述的方法，其特征在于，还包括：
    所述第二终端接入所述第一终端的所述服务小区；
    所述第二终端向所述第一网络设备发送终端设备标识；
    其中，所述终端设备标识为所述第二终端的C-RNTI，或者为所述第一终端的C-RNTI和所述第二终端的本地标识。
  14. 如权利要求13所述的方法，其特征在于，所述终端设备标识携带在所述第四消息中，或者所述终端设备标识由所述第一终端在发送所述第四消息之前发送给所述第二终端。
  15. 一种终端，所述终端为第一终端，其特征在于，包括：
    通信单元，用于向第一网络设备发送第一消息，所述第一消息用于请求将第二终端从通过所述第一终端与所述第一网络设备进行通信的非直连路径转换到与所述第一网络设备或第二网络设备进行通信的直连路径；或所述第一消息用于请求释放所述第一终端与所述第二终端之间的链路；其中，所述第一网络设备与所述第二网络设备不同；
    处理单元，用于释放所述第一终端与所述第二终端之间的链路。
  16. 如权利要求15所述的终端，其特征在于，所述处理单元，具体用于在接收到第三消息之后，释放所述链路；所述第三消息是在所述第一网络设备向所述第二终端发送第二消息之后由所述第一网络设备或者所述第二终端发送的，用于指示所述第一终端释放所述链路；
    其中，所述第二消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指 示信息，或第一时间值，用于配置所述第二终端从所述非直连路径转换到所述直连路径；
    其中，第一指示信息用于指示所述第二终端是否在与所述小区标识对应的小区进行下行同步后再断开与所述第一终端的连接；所述第一时间值为所述第二终端接入所述小区标识对应的小区所允许的最长时间；
    或者，
    所述处理单元，具体用于当所述第一终端在发送所述第一消息之后保持所述链路的时间长度超过第一时间长度时，释放所述链路。
  17. 一种网络设备，所述网络设备为第一网络设备，其特征在于，包括：
    第一通信单元，用于接收第一终端发送的第一消息，所述第一消息用于请求将第二终端从通过所述第一终端与所述第一网络设备进行通信的非直连路径转换到与所述第一网络设备或第二网络设备进行通信的直连路径；或所述第一消息用于请求释放所述第一终端与所述第二终端之间的链路；其中，所述第一网络设备与所述第二网络设备不同；
    第二通信单元，用于向所述第二终端发送第二消息，所述第二消息用于配置所述第二终端从所述非直连路径转换到所述直连路径。
  18. 如权利要求17的网络设备，其特征在于，所述第二消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值；
    其中，第一指示信息用于指示所述第二终端是否在与所述小区标识对应的小区进行下行同步后再断开与所述第一终端的连接；所述第一时间值为所述第二终端接入所述小区标识对应的小区所允许的最长时间。
  19. 一种终端，所述终端为第二终端，其特征在于，包括：
    通信单元，用于接收到第一络设备发送的第二消息，所述第二消息用于配置所述第二终端从通过所述第一终端与所述第一网络设备进行通信的非直连路径转换到与所述第一网络设备或第二网络设备进行通信的直连路径；其中，所述第一网络设备与所述第二网络设备不同；
    处理单元，用于根据所述第二消息，从所述非直连路径转换到所述直连路径；
    其中，所述第二消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值；
    其中，第一指示信息用于指示所述第二终端是否在与所述小区标识对应的小区进行下行同步后再断开与所述第一终端的连接；第一时间值用于指示所述第二终端接入所述小区标识对应的小区所允许的最长时间。
  20. 一种终端，所述终端为第一终端，其特征在于，包括：
    通信单元，用于向第二终端发送第四消息，所述第四消息用于指示所述第二终端从通过所述第一终端与第一网络设备进行通信的非直连路径转换到与所述第一网络设备或第二网络设备进行通信的直连路径；或所述第四消息用于指示释放所述第一终端与所述第二终 端之间的链路；其中，所述第一网络设备与所述第二网络设备不同；
    处理单元，用于释放所述第一终端与所述第二终端之间的链路。
  21. 如权利要求20所述的终端，其特征在于，所述处理单元，具体用于在接收到第七消息之后，释放所述链路；所述第七消息是在所述第一网络设备向所述第二终端发送第六消息之后由所述第一网络设备或者所述第二终端发送的，用于指示所述第一终端释放所述链路；
    其中，所述第六消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值，用于配置所述第二终端从所述非直连路径转换到所述直连路径；
    或者，
    所述处理单元，具体用于当所述第一终端在发送所述第四消息之后保持所述链路的时间长度超过第一时间长度时，释放所述链路。
  22. 如权利要求20所述的终端，其特征在于，所述第四消息包括以下至少一项：所述第一终端的服务小区的小区标识，或者所述第一终端的服务小区的公共无线资源的配置信息。
  23. 一种终端，所述终端为第二终端，其特征在于，包括：
    通信单元，用于接收第一终端发送的第四消息，所述第四消息用于指示所述第二终端从通过所述第一终端与第一网络设备进行通信的非直连路径转换到与所述第一网络设备或第二网络设备进行通信的直连路径；或所述第四消息用于指示释放所述第一终端与所述第二终端之间的链路；其中，所述第一网络设备与所述第二网络设备不同；
    处理单元，用于根据所述第四消息，从所述非直连路径转换到所述直连路径。
  24. 如权利要求23所述的终端，其特征在于，
    所述通信单元，还用于向所述第一网络设备发送第五消息，用于请求从所述非直连路径转换到所述直连路径；
    所述通信单元，还用于接收所述第一网络设备发送的第六消息，所述第六消息包括以下至少一项：小区标识，或随机接入配置信息，或第一指示信息，或第一时间值，用于配置所述第二终端从所述非直连路径转换到所述直连路径；
    其中，第一指示信息用于指示所述第二终端是否在与所述小区标识对应的小区进行下行同步后再断开与所述第一终端的连接；所述第一时间值为所述第二终端接入所述小区标识对应的小区所允许的最长时间。
  25. 如权利要求23所述的终端，其特征在于，所述通信单元，还用于接收到所述第四消息后，所述第二终端触发无线资源控制连接重建过程。
  26. 如权利要求23所述的终端，其特征在于，所述第四消息包括以下至少一项：所述 第一终端的服务小区的小区标识，或者所述第一终端的服务小区的公共无线资源的配置信息。
  27. 如权利要求26所述的终端，其特征在于，所述通信单元，还用于接入所述第一终端的所述服务小区，并向所述第一网络设备发送终端设备标识；
    其中，所述终端设备标识为所述第二终端的C-RNTI，或者为所述第一终端的C-RNTI和所述第二终端的本地标识。
  28. 如权利要求27所述的终端，其特征在于，所述终端设备标识携带在所述第四消息中，或者所述终端设备标识由所述第一终端在发送所述第四消息之前发送给所述第二终端。
  29. 一种通信系统，其特征在于，包括：第一终端、第二终端和网络设备，其中：
    所述第一终端是权利要求15或16所述的终端；
    所述第二终端是权利要求19所述的终端；
    所述网络设备是权利要求17或18所述的网络设备。
  30. 一种通信系统，其特征在于，包括：第一终端、第二终端和网络设备，其中：
    所述第一终端是权利要求20-22中任一项所述的终端；
    所述第二终端是权利要求23-28中任一项所述的终端。
PCT/CN2017/097022 2017-08-11 2017-08-11 一种路径转换方法、相关装置及系统 Ceased WO2019028811A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/CN2017/097022 WO2019028811A1 (zh) 2017-08-11 2017-08-11 一种路径转换方法、相关装置及系统
CN202210053239.XA CN114513822B (zh) 2017-08-11 2017-08-11 一种路径转换方法、相关装置及系统
US16/635,764 US11419025B2 (en) 2017-08-11 2017-08-11 Path switching method, apparatus and system
CN201780093715.8A CN111034334B (zh) 2017-08-11 2017-08-11 一种路径转换方法、相关装置及系统
EP17921176.8A EP3637940B1 (en) 2017-08-11 2017-08-11 Path switching method, related apparatus, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/097022 WO2019028811A1 (zh) 2017-08-11 2017-08-11 一种路径转换方法、相关装置及系统

Publications (1)

Publication Number Publication Date
WO2019028811A1 true WO2019028811A1 (zh) 2019-02-14

Family

ID=65273003

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/097022 Ceased WO2019028811A1 (zh) 2017-08-11 2017-08-11 一种路径转换方法、相关装置及系统

Country Status (4)

Country Link
US (1) US11419025B2 (zh)
EP (1) EP3637940B1 (zh)
CN (2) CN114513822B (zh)
WO (1) WO2019028811A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022082434A1 (zh) * 2020-10-20 2022-04-28 Oppo广东移动通信有限公司 用于终端间通信的方法、终端设备和网络设备
CN115380621A (zh) * 2020-04-09 2022-11-22 中兴通讯股份有限公司 无线侧链路通信中资源分配和释放的方法和设备
WO2023179668A1 (zh) * 2022-03-24 2023-09-28 维沃移动通信有限公司 数据传输方法及装置、终端及网络侧设备
WO2023216242A1 (zh) * 2022-05-13 2023-11-16 Oppo广东移动通信有限公司 连接配置方法和终端
WO2024207383A1 (zh) * 2023-04-06 2024-10-10 富士通株式会社 路径处理方法及其装置、通信系统

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020091443A1 (en) * 2018-11-01 2020-05-07 Lg Electronics Inc. Deactivation of configured grant and initiation of connection request upon detection of sidelink failure
US11800579B2 (en) * 2019-05-07 2023-10-24 Qualcomm Incorporated Establishment of millimeter wave relay links between user equipments with base station coordination
WO2020245960A1 (ja) * 2019-06-05 2020-12-10 本田技研工業株式会社 無線基地局、通信システム、プログラム、制御方法、及び無線通信装置
CN111901836A (zh) * 2020-02-13 2020-11-06 中兴通讯股份有限公司 链路切换、链路切换配置方法、装置、通信节点及介质
US11689957B2 (en) * 2020-03-13 2023-06-27 Qualcomm Incorporated Quality of service support for sidelink relay service
US11825330B2 (en) 2020-03-13 2023-11-21 Qualcomm Incorporated Techniques for quality of service support in sidelink communications
CN113573422B (zh) * 2020-04-28 2023-10-20 维沃移动通信有限公司 远端终端的连接管理方法、终端及网络侧设备
CN113825183B (zh) * 2020-06-19 2025-06-17 展讯通信（上海）有限公司 通信方法及装置
CN113873683B (zh) * 2020-06-30 2024-11-15 华为技术有限公司 一种通信方法及装置
CN111818600B (zh) * 2020-07-08 2023-02-21 河南软金通信科技有限公司 一种终端管控方法、装置、设备及存储介质
WO2022022661A1 (en) * 2020-07-31 2022-02-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for radio connection
WO2022027548A1 (en) * 2020-08-07 2022-02-10 Qualcomm Incorporated Radio link failure in sidelink relay
WO2022042146A1 (zh) * 2020-08-25 2022-03-03 华为技术有限公司 一种通信方法及装置
US20220124573A1 (en) * 2020-10-20 2022-04-21 Mediatek Inc. Apparatuses and methods for recovering from sidelink relay failure
KR20220077869A (ko) * 2020-12-02 2022-06-09 아서스테크 컴퓨터 인코포레이션 무선 통신 시스템에서 ue-대-네트워크 릴레이 통신을 지원하기 위한 방법 및 장치
EP4265006A4 (en) * 2020-12-15 2024-07-24 Lenovo (Beijing) Limited METHOD AND DEVICE FOR PATH SWITCHING IN A WIRELESS COMMUNICATIONS SYSTEM
EP4265054A4 (en) * 2020-12-18 2024-09-11 Lenovo (Beijing) Limited METHOD AND DEVICE FOR PATH SWITCHING IN A WIRELESS COMMUNICATIONS SYSTEM
EP4243509B1 (en) * 2021-02-05 2025-04-30 Guangdong Oppo Mobile Telecommunications Corp., Ltd. State switching method, apparatus, device, and storage medium
CN115150904B (zh) * 2021-03-30 2024-06-04 维沃移动通信有限公司 通信路径的切换方法、装置及终端
CN115175176A (zh) * 2021-04-01 2022-10-11 华为技术有限公司 一种中继通信方法及装置
CN115243337B (zh) * 2021-04-23 2024-09-24 华为技术有限公司 数据传输方法及装置
CN118574172A (zh) * 2021-05-07 2024-08-30 北京小米移动软件有限公司 一种释放远端终端设备的方法及其装置
WO2023010278A1 (zh) * 2021-08-03 2023-02-09 Oppo广东移动通信有限公司 无线通信方法及装置
US20240205789A1 (en) * 2021-09-24 2024-06-20 Apple Inc. Multi-path operation in ue-to-nw sidelink relay
WO2023046073A1 (zh) * 2021-09-26 2023-03-30 上海朗帛通信技术有限公司 一种被用于无线通信的方法和设备
CN115884222B (zh) * 2021-09-26 2025-11-25 邦克山科技有限责任公司 一种被用于无线通信的方法和设备
CN118285153A (zh) * 2021-09-29 2024-07-02 日本电气株式会社 通信的方法、设备和计算机存储介质
CN115996406A (zh) * 2021-10-20 2023-04-21 大唐移动通信设备有限公司 定时器维护方法、装置、设备及存储介质
CN116847478A (zh) * 2022-03-24 2023-10-03 维沃移动通信有限公司 路径建立方法及装置、终端及网络侧设备
CN118901279A (zh) * 2022-03-30 2024-11-05 Oppo广东移动通信有限公司 无线通信的方法、网络设备和终端设备
EP4496383A4 (en) * 2022-03-31 2025-04-23 Guangdong Oppo Mobile Telecommunications Corp., Ltd. WIRELESS COMMUNICATION METHOD, NETWORK DEVICE AND TERMINAL DEVICE
JP2025515446A (ja) * 2022-04-21 2025-05-15 華為技術有限公司 通信方法及び装置
CN117098157A (zh) * 2022-05-20 2023-11-21 华为技术有限公司 通信方法和装置
WO2024036573A1 (en) * 2022-08-18 2024-02-22 Mediatek Inc. Method of path addition and removal to support multipath configuration
WO2024060298A1 (en) * 2022-09-29 2024-03-28 Lenovo (Beijing) Limited Method and apparatus for multi-path case
CN115734313A (zh) * 2022-10-17 2023-03-03 华为技术有限公司 多路径配置方法、装置及系统
WO2024096679A1 (en) * 2022-11-03 2024-05-10 Lg Electronics Inc. Method and apparatus for transmitting/receiving wireless signal in wireless communication system
WO2024093104A1 (en) * 2023-03-27 2024-05-10 Lenovo (Beijing) Limited Terminal device, network device and methods for multi-path communications
WO2024207316A1 (zh) * 2023-04-06 2024-10-10 富士通株式会社 多路径的通信方法以及装置
US20240422649A1 (en) * 2023-06-15 2024-12-19 Qualcomm Incorporated Techniques for access link based reliability for sidelink communications
CN119342539A (zh) * 2023-07-20 2025-01-21 大唐移动通信设备有限公司 一种信息指示方法、装置及可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102172072A (zh) * 2008-10-07 2011-08-31 富士通株式会社 中继装置、终端装置以及通信系统
WO2014185708A1 (en) * 2013-05-14 2014-11-20 Samsung Electronics Co., Ltd. System and method for ip session continuity in device-to-device communication system
CN104284449A (zh) * 2013-07-08 2015-01-14 电信科学技术研究院 一种资源释放方法和装置
CN105453694A (zh) * 2013-07-18 2016-03-30 索尼公司 控制装置和通信终端
CN106470382A (zh) * 2015-08-14 2017-03-01 中兴通讯股份有限公司 授权验证方法、配置信息接收方法、装置、基站及终端

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103179575A (zh) * 2011-12-23 2013-06-26 中兴通讯股份有限公司 一种邻近设备通信的方法和系统、网络侧设备和用户设备
KR102115425B1 (ko) * 2013-07-02 2020-06-05 삼성전자주식회사 무선 통신 시스템에서 기본 경로 및 직접 경로 간 전환 장치 및 방법
CN104284321B (zh) * 2013-07-08 2018-09-21 华为终端（东莞）有限公司 一种路径切换的方法、设备和用户设备
CN105684549B (zh) * 2013-11-05 2020-10-02 夏普株式会社 终端装置、中继终端装置以及通信控制方法
US9877349B2 (en) * 2014-03-10 2018-01-23 Lg Electronics Inc. Method for performing proximity service, and user device
ES2948665T3 (es) * 2015-04-07 2023-09-15 Blackberry Ltd Cambio entre operaciones basadas en red y basadas en relés para llamadas de voz de misión crítica
WO2016169015A1 (zh) * 2015-04-23 2016-10-27 华为技术有限公司 网络通信和直接通信之间的切换方法和装置
US20180295534A1 (en) * 2015-05-14 2018-10-11 Zte Corporation Method for Processing Information, and Communication Node
US10602550B2 (en) * 2015-07-23 2020-03-24 Apple Inc. Layer 2 relay protocols and mobility relay method
EP3627723B1 (en) * 2015-07-24 2025-10-15 Panasonic Intellectual Property Corporation of America Improved prose relay ue activation
EP3142453B1 (en) * 2015-09-08 2018-05-16 ASUSTek Computer Inc. Method and apparatus for triggering radio bearer release by a relay ue (user equipment) in a wireless communication system
JP6860560B2 (ja) * 2015-10-26 2021-04-14 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおいて端末間の直接通信方法及びそのための装置
JP6761044B2 (ja) * 2016-03-30 2020-09-23 オッポ広東移動通信有限公司Ｇｕａｎｇｄｏｎｇ Ｏｐｐｏ Ｍｏｂｉｌｅ Ｔｅｌｅｃｏｍｍｕｎｉｃａｔｉｏｎｓ Ｃｏｒｐ．， Ｌｔｄ． データ伝送方法及び端末デバイス
EP3525546A4 (en) * 2016-10-05 2020-06-03 LG Electronics Inc. -1- METHOD FOR CONNECTING TO A NETWORK AND USER
WO2018068358A1 (zh) 2016-10-12 2018-04-19 华为技术有限公司 路径切换方法和装置
US10945179B2 (en) 2017-01-10 2021-03-09 Huawei Technologies Co., Ltd. Communication path switching method and device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102172072A (zh) * 2008-10-07 2011-08-31 富士通株式会社 中继装置、终端装置以及通信系统
WO2014185708A1 (en) * 2013-05-14 2014-11-20 Samsung Electronics Co., Ltd. System and method for ip session continuity in device-to-device communication system
CN104284449A (zh) * 2013-07-08 2015-01-14 电信科学技术研究院 一种资源释放方法和装置
CN105453694A (zh) * 2013-07-18 2016-03-30 索尼公司 控制装置和通信终端
CN106470382A (zh) * 2015-08-14 2017-03-01 中兴通讯股份有限公司 授权验证方法、配置信息接收方法、装置、基站及终端

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3637940A4 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115380621A (zh) * 2020-04-09 2022-11-22 中兴通讯股份有限公司 无线侧链路通信中资源分配和释放的方法和设备
CN115380621B (zh) * 2020-04-09 2025-04-04 中兴通讯股份有限公司 无线侧链路通信中资源分配和释放的方法和设备
US12302326B2 (en) 2020-04-09 2025-05-13 Zte Corporation Method and device for resource allocation and release in wireless sidelink communication
WO2022082434A1 (zh) * 2020-10-20 2022-04-28 Oppo广东移动通信有限公司 用于终端间通信的方法、终端设备和网络设备
CN116114366A (zh) * 2020-10-20 2023-05-12 Oppo广东移动通信有限公司 用于终端间通信的方法、终端设备和网络设备
WO2023179668A1 (zh) * 2022-03-24 2023-09-28 维沃移动通信有限公司 数据传输方法及装置、终端及网络侧设备
WO2023216242A1 (zh) * 2022-05-13 2023-11-16 Oppo广东移动通信有限公司 连接配置方法和终端
WO2024207383A1 (zh) * 2023-04-06 2024-10-10 富士通株式会社 路径处理方法及其装置、通信系统

Also Published As

Publication number Publication date
US11419025B2 (en) 2022-08-16
US20210144606A1 (en) 2021-05-13
CN111034334B (zh) 2022-01-14
CN111034334A (zh) 2020-04-17
CN114513822A (zh) 2022-05-17
EP3637940A4 (en) 2020-10-14
EP3637940A1 (en) 2020-04-15
EP3637940B1 (en) 2024-12-25
CN114513822B (zh) 2024-05-03

Similar Documents

Publication Publication Date Title
CN114513822B (zh) 一种路径转换方法、相关装置及系统
US10057821B2 (en) User equipment, method, and base station
RU2767981C2 (ru) Способ обработки информации и соответствующее устройство
RU2668071C1 (ru) Способ и устройство оптимизации сигнализации
JP2024045709A (ja) Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ及びその方法
RU2602981C2 (ru) Способ обработки сбоя в линии радиосвязи
US9538575B2 (en) Systems and methods for dual-connectivity operation
CN108924949B (zh) 无线网络中的通信方法、装置和系统
CN107295454B (zh) 资源的配置方法及装置
EP3497972B1 (en) Telecommunications system, terminal device, infrastructure equipment and methods
JP6442038B2 (ja) ユーザ機器及び基地局のデュアルコネクティビティにおけるハンドオーバのための方法及び装置
US20220394802A1 (en) Re-establishment method and communication apparatus
CN104468029A (zh) 一种移动终端通信方法、装置及相关设备
WO2022082690A1 (zh) 群组切换的方法、装置和系统
CN111148187A (zh) 通信方法和装置
US9173207B2 (en) Method and device for configuring cell parameters of relay node
WO2019105064A1 (en) Method and apparatus for signal transmission, network equipment
WO2019228459A1 (zh) 通信方法、装置及存储介质
AU2018442251A1 (en) Switching processing method, terminal device and network device
CN118805443A (zh) 路径切换方法及装置
CN118120332A (zh) 信息发送方法、信息接收方法、装置和系统
EP4525518A1 (en) Communication method and apparatus
JP2022501888A (ja) データ伝送方法、端末装置及びネットワーク装置
WO2023050181A1 (zh) 无线通信方法及无线通信装置
JP2014165726A (ja) 端末装置、基地局装置、通信システム及び通信方法

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017921176

Country of ref document: EP

Effective date: 20200108

NENP Non-entry into the national phase

Ref country code: DE