WO2019242460A1 - 信息传输方法及装置、存储介质、电子装置 - Google Patents

信息传输方法及装置、存储介质、电子装置 Download PDF

Info

Publication number
WO2019242460A1
WO2019242460A1 PCT/CN2019/088657 CN2019088657W WO2019242460A1 WO 2019242460 A1 WO2019242460 A1 WO 2019242460A1 CN 2019088657 W CN2019088657 W CN 2019088657W WO 2019242460 A1 WO2019242460 A1 WO 2019242460A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
node
transmission node
iab
handover
Prior art date
Application number
PCT/CN2019/088657
Other languages
English (en)
French (fr)
Inventor
罗薇
陈琳
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US17/254,530 priority Critical patent/US20210274394A1/en
Priority to EP19821651.7A priority patent/EP3813425B1/en
Priority to MX2021000162A priority patent/MX2021000162A/es
Priority to EP24155995.4A priority patent/EP4340451A2/en
Publication of WO2019242460A1 publication Critical patent/WO2019242460A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • 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
    • 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
    • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • 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/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00838—Resource reservation for handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • 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/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present disclosure relates to the field of communications, and in particular, to an information transmission method and device, a storage medium, and an electronic device.
  • RN Relay Node
  • the RN provides functions and services similar to ordinary eNBs to the UEs accessing its cell.
  • the radio interface between the RN and the UE is called "Access Link", and the RN uses the radio interface in a similar manner to the ordinary UE.
  • Access to a base station eNB serving it, and the eNB serving the RN is called a Donor eNB (DeNB).
  • the radio interface between the RN and the DeNB is called a "backhaul link”.
  • FIG. 1 is a schematic diagram of an IAB link in the related technology of the present disclosure.
  • IAB node A is connected to the core network through an optical fiber, and is an IAB donor.
  • IAB nodes B and C are not connected to the core network, and are ordinary IABs.
  • FIG. 2 is a schematic diagram of a link of an IAB node as a relay in the related technology of the present disclosure.
  • the IAB can transmit data to the IAB donor through multiple IABs as relays, in other words In other words, the IAB is hierarchical.
  • the so-called IAB level represents the number of IAB hops that the IAB transmission needs to pass to reach the IAB donor. Assume that the level of the donor IAB is 0, and the level of the UE accessing the IAB is N. Then, the transmission path of the UE and the core network sequentially passes through the IABs with the levels 1, 2, and ..N.
  • an IAB with a level of n + 1 is a UE for an IAB with a level of n
  • an IAB with a level of n is n
  • the IAB is the serving community. If the IAB at level n + 1 accesses the IAB at level n through the Uu port through the UE, we call the IAB at level n the parent node of the IAB at level n + 1, and the IAB at level n + 1 IAB is a child node of the IAB at level n. Each IAB can choose to access one or more parent nodes.
  • the existing mechanism can only re-establish the process through the reconstruction process, but the interruption delay caused by this may be very long and may not be possible. Meet the latency needs of service business.
  • the existing mechanism can only re-establish the process through the reconstruction process, but the interruption delay caused by this mechanism is very long and may not meet the service business Latency requirements.
  • the embodiments of the present disclosure provide an information transmission method and device, a storage medium, and an electronic device.
  • an information transmission method including: a third transmission node receives context information of the first transmission node or the second transmission node sent by a first transmission node; the third transmission node Save the context information.
  • another information transmission method including: a target service node of a transmission node receives a handover preparation request sent by a source service node of the transmission node, wherein the handover preparation request includes at least the following One: cause information, valid time information, cycle information, and identification information of the target transmission node.
  • the target service node After receiving the handover preparation request information, the target service node sends handover preparation confirmation information to the source service node; wherein the reason information is used to indicate that the cause of the handover preparation request is an early handover preparation request or Rebuild preparation request; the valid time information is used to indicate the validity period of the handover preparation request; the cycle information is used to indicate the cycle in which the handover preparation request message is sent, and no handover or rebuild operation is performed after the cycle time is exceeded When the handover preparation request fails.
  • the reason information is used to indicate that the cause of the handover preparation request is an early handover preparation request or Rebuild preparation request
  • the valid time information is used to indicate the validity period of the handover preparation request
  • the cycle information is used to indicate the cycle in which the handover preparation request message is sent, and no handover or rebuild operation is performed after the cycle time is exceeded When the handover preparation request fails.
  • another information transmission method including: a transmission node receives a mobility control message sent by a target serving node of the transmission node, wherein the mobility control message is used to indicate the transmission node Perform a handover; after receiving the mobility control message, the transmission node executes a handover procedure; wherein the transmission node is a terminal or an IAB.
  • a transmission node receives an RRC connection release message or an RRC connection rejection message sent by a source service node of the transmission node, wherein the RRC connection release message or RRC
  • the connection rejection message includes an IAB list, the IAB list includes: IAB identification information, IAB connection host IAB identification information, public land mobile network PLMN information; when a link connection failure occurs at the transmission node, the priority is selected IAB nodes in the IAB list are reconstructed.
  • an information transmission device including: a receiving module configured to receive context information of the first transmission node or the second transmission node sent by a first transmission node; a saving module, setting To save the context information.
  • a target service node applied to a transmission node includes a receiving module configured to receive a handover preparation request sent by a source service node of the transmission node, where The handover preparation request includes at least one of the following: cause information, valid time information, cycle information, and identification information of the target transmission node.
  • the sending module is configured to send handover preparation confirmation information to the source service node after receiving the handover preparation request information, wherein the reason information is used to indicate that the cause of the handover preparation request is an early handover preparation request or Rebuild preparation request; the valid time information is used to indicate the validity period of the handover preparation request; the cycle information is used to indicate the cycle in which the handover preparation request message is sent, and no handover or rebuild operation is performed after the cycle time is exceeded When the handover preparation request fails.
  • the reason information is used to indicate that the cause of the handover preparation request is an early handover preparation request or Rebuild preparation request
  • the valid time information is used to indicate the validity period of the handover preparation request
  • the cycle information is used to indicate the cycle in which the handover preparation request message is sent, and no handover or rebuild operation is performed after the cycle time is exceeded When the handover preparation request fails.
  • a target switching service node applied to a transmission node includes: a sending module configured to send a movement control message of the transmission node, wherein the mobile The control message is used to instruct the transmission node to perform a handover.
  • the transmission node target switching service node is a source and auxiliary service node of the transmission node.
  • the transmission node is a terminal or an IAB.
  • another information transmission device applied to a transmission node including: a receiving module configured to receive an RRC connection release message or an RRC connection rejection message sent by a source service node of the transmission node.
  • the RRC connection release message or RRC connection rejection message includes an IAB list
  • the IAB list includes: IAB identification information, IAB connection host IAB identification information, public land mobile network PLMN information, and a processing module, which is set to When a link connection failure occurs, the IAB node in the IAB list is preferentially selected for reconstruction.
  • a storage medium stores a computer program, and the computer program is configured to execute the steps in any one of the foregoing method embodiments when running.
  • an electronic device including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute any one of the above. Steps in a method embodiment.
  • the context information can be used for link recovery, avoiding the re-establishment process, and solving the related technology.
  • the technical problem of excessively long restoration delay of link interruption meets the delay requirement of service business.
  • FIG. 1 is a schematic diagram of an IAB link in the related art of the present disclosure
  • FIG. 2 is a schematic diagram of a link of an IAB node as a relay in the related art of the present disclosure
  • FIG. 3 is a flowchart of an information transmission method according to an embodiment of the present disclosure.
  • FIG. 5 is a flowchart of another information transmission method according to an embodiment of the present disclosure.
  • FIG. 6 is a structural block diagram of an information transmission device according to an embodiment of the present disclosure.
  • FIG. 7 is a structural block diagram of another information transmission device according to an embodiment of the present disclosure.
  • FIG. 8 is a structural block diagram of another information transmission device according to an embodiment of the present disclosure.
  • FIG. 9 is a first schematic flowchart of an embodiment of the present disclosure.
  • FIG. 10 is a second schematic flowchart of an embodiment of the present disclosure.
  • FIG. 11 is a third schematic flowchart of an embodiment of the present disclosure.
  • FIG. 12 is a fourth flowchart of an embodiment of the present disclosure.
  • FIG. 3 is a flowchart of an information transmission method according to an embodiment of the present disclosure. As shown in FIG. 3, the process includes the following steps:
  • Step S302 The third transmission node receives the context information of the first transmission node or the second transmission node sent by the first transmission node;
  • Step S304 The third transmission node saves the context information.
  • the context information can be used for link recovery, avoiding the re-establishment process, and solving the related technology.
  • the technical problem of excessively long restoration delay of link interruption meets the delay requirement of service business.
  • the first transmission node is a centralized unit CU
  • the second transmission node is a distributed unit DU
  • the third transmission node includes one or more DUs
  • the first transmission node passes the F1 interface.
  • Send contextual information
  • the method further includes: the third transmission node sends a request for obtaining the context information through the F1 interface. Message.
  • the message that the third transmission node sends to request the context information through the F1 interface includes: when the third transmission node receives the RRC reconstruction request, the third transmission node sends the request message through the F1 interface.
  • the context information includes: a transmission node identifier, and context information of the transmission node.
  • the context information further includes at least one of the following: cause information, where the cause information is used to indicate a reason for sending the context information, where the cause includes one of the following: handover preparation, rebuild preparation; valid time information, where, valid The time information is used to indicate the validity period of the context information; the cycle information is used to indicate the cycle of sending the context information.
  • cause information where the cause information is used to indicate a reason for sending the context information, where the cause includes one of the following: handover preparation, rebuild preparation; valid time information, where, valid The time information is used to indicate the validity period of the context information; the cycle information is used to indicate the cycle of sending the context information.
  • the context information becomes invalid.
  • the first transmission node after the first transmission node sends the context information, the first transmission node sends instruction information for releasing the context information of the first transmission node or the second transmission node.
  • a target transmission node having the same host node as the source serving node of the fourth transmission node is preferentially selected to perform a radio resource control RRC reconstruction process, where the fourth transmission node is a terminal or an IAB.
  • the context information is transmitted through the Xn interface.
  • the relay node includes at least one of the following: a base station, and an integrated access backhaul IAB node.
  • the target transmission node that has the context information of the fourth transmission node is preferentially selected to perform the RRC reestablishment process, where the fourth transmission node is a terminal or an IAB.
  • FIG. 4 is a flowchart of another information transmission method according to an embodiment of the present disclosure. As shown in FIG. 4, the process includes the following steps:
  • Step S402 The target service node of the transmission node receives a handover preparation request sent by the source service node of the transmission node, where the handover preparation request includes at least one of the following: cause information, valid time information, period information, and identification information of the target transmission node;
  • Step S404 After receiving the handover preparation request information, the target service node sends handover preparation confirmation information to the source service node;
  • the reason information is used to indicate that the reason for the handover preparation request is an advance handover preparation request or rebuild preparation request; the valid time information is used to indicate the validity period of the handover preparation request; the period information is used to indicate the cycle of the handover preparation request message.
  • the switchover preparation request becomes invalid.
  • the source service node sends handover preparation request information to multiple target service nodes, where the handover preparation request information is used to request preparation of handover resources, and the identification information of the multiple target transmission nodes corresponds to the multiple target service nodes.
  • the source service node is at least one of the following: centralized unit CU, distributed unit DU, integrated access backhaul IAB node, relay, base station;
  • the target service node is at least one of the following: distributed unit DU, IAB node , Relay, base station.
  • the source service node is a parent node of the IAB node.
  • the target service node after receiving the handover preparation request, sends handover activation indication information to the source service node.
  • the method further includes: receiving handover activation confirmation information sent by the source service node; or receiving serial number SN status information sent by the source service node.
  • the source serving node After the source serving node detects that the serving node has failed to connect to the link, it sends the handover activation instruction information to the target serving node.
  • the handover cancellation instruction information is sent to the target service node.
  • the handover cancellation instruction information includes the cause value of the handover cancellation.
  • the source service node after the source service node sends the handover preparation request information to the target service node, it sends the mobile control information to the transmitting node, where the mobile control information includes handover activation condition information, and the handover activation condition information includes: The transmission period or time information indicating the effective time of the message, or information to perform handover when a wireless link failure occurs.
  • FIG. 5 is a flowchart of another information transmission method according to an embodiment of the present disclosure. As shown in FIG. 5, the process includes the following steps:
  • Step S502 The transmitting node receives a mobility control message sent by a target serving node of the transmitting node, where the mobility control message is used to instruct the transmitting node to perform a handover;
  • Step S504 After receiving the mobility control message, the transmitting node executes a handover process.
  • the transmission node is a terminal or an IAB.
  • the target serving node is a source serving secondary node of the transmitting node.
  • This embodiment also provides an information transmission method, including:
  • the transmitting node receives an RRC connection release message or an RRC connection rejection message sent by the source service node of the transmitting node.
  • the RRC connection release message or the RRC connection rejection message includes an IAB list, and the IAB list includes: IAB identification information, Identification information of the host IAB and PLMN information of the public land mobile network;
  • the IAB node in the IAB list is preferentially selected for reconstruction.
  • the transmission node can be an IAB or a terminal.
  • the method according to the above embodiments can be implemented by means of software plus a necessary universal hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is Better implementation.
  • the technical solution of the present disclosure that is essentially or contributes to related technologies can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, and optical disk) ) Includes instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods of the embodiments of the present disclosure.
  • module may implement a combination of software and / or hardware for a predetermined function.
  • devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and conceived.
  • FIG. 6 is a structural block diagram of an information transmission device according to an embodiment of the present disclosure. As shown in FIG. 6, the device includes:
  • the receiving module 60 is configured to receive context information of the first transmission node or the second transmission node sent by the first transmission node;
  • the saving module 62 is configured to save context information.
  • FIG. 7 is a structural block diagram of another information transmission apparatus according to an embodiment of the present disclosure, which is applied to a target service node of a transmission node. As shown in FIG. 7, the apparatus includes:
  • the receiving module 70 is configured to receive a handover preparation request sent by a source service node of a transmission node, where the handover preparation request includes at least one of the following: cause information, valid time information, period information, and identification information of a target transmission node;
  • the sending module 72 is configured to send handover preparation confirmation information to the source service node after receiving the handover preparation request information
  • the reason information is used to indicate that the reason for the handover preparation request is an advance handover preparation request or rebuild preparation request; the valid time information is used to indicate the validity period of the handover preparation request; the period information is used to indicate the cycle of the handover preparation request message.
  • the switchover preparation request becomes invalid.
  • the sending module is further configured to send the handover activation instruction information to the source service node of the transmission node
  • the receiving module is further used to receive the handover activation instruction information sent by the source service node of the transmission node.
  • FIG. 8 is a structural block diagram of another information transmission apparatus according to an embodiment of the present disclosure, and a target switching service node is applied to a transmission node. As shown in FIG. 8, the apparatus includes:
  • the sending module 80 is configured to send a mobility control message of the transmission node, where the mobility control message is used to instruct the transmission node to perform a handover, wherein the transmission node target switching service node is a source and auxiliary service node of the transmission node; wherein the transmission node is a terminal Or IAB.
  • This embodiment also provides an information transmission device, which is applied to a transmission node and includes a receiving module configured to receive an RRC connection release message or an RRC connection rejection message sent by a source service node of the transmission node, where the RRC connection release message or the RRC connection
  • the rejection message includes the IAB list, and the IAB list includes: the identification information of the IAB, the identification information of the host IAB connected to the IAB, and the public land mobile network PLMN information;
  • a processing module configured to preferentially select an IAB node in the IAB list for reconstruction when a link connection failure occurs.
  • each of the above modules can be implemented by software or hardware.
  • it can be implemented by the following methods, but is not limited to the above: the above modules are all located in the same processor; The forms are located in different processors.
  • This embodiment includes the following implementation manners, which are used to describe the solution of the present application in detail in different scenarios:
  • the terminal or IAB node In order to ensure the success of the reconstruction, the terminal or IAB node should know in advance which cells have their own context information. For the CU / DU split scene, the donor and CU can obtain the IAB context information. Therefore, we propose that the IABs connected to the same donor and CU all obtain the context information of other IABs through the donor CU. Then, if the selected reconstructed IAB is different from the original If the parent IAB is connected to the same donor CU, then the reconstruction is easier to succeed. In this embodiment, the DU and the CU exchange context information through F1AP.
  • the IAB connected to the same donor CU is preferentially selected as the reconstruction target IAB.
  • the IAB donor can also obtain and save the context information of all child IABs that are directly connected or indirectly accessed, and notify other neighboring child IABs, so that IAB nodes can preferentially choose when detecting RLF Other IAB nodes under the same IAB donor are used as reconstruction target IABs.
  • the context information of the child IAB nodes that can be directly accessed through the Xn interface between different IAB nodes, and the parent IAB nodes can inform the child in advance which adjacent IAB nodes have The context information can be used as the preferred reconstruction target IAB in the future.
  • different IAB nodes directly exchange their respective context information through the Xn interface, so that the IAB knows which IAB has its own context information, and uses these IABs with its own context information as the preferred reconstruction target IAB.
  • Step 1 The CU sends the context information of one or more IABs to the DU through the F1 interface.
  • the context information includes: a transmission node identifier (gNB-CU UE F1AP ID), and bearer establishment information. Further, it may further include cause information, where the cause information is used to indicate a reason for sending the context information of the transmission node, for example, to perform RRC reconstruction. Further, it may further include validity time information, which is used to indicate a validity period of the context information. When the handover or RRC rebuilding operation is not performed after the validity time is exceeded, the context information becomes invalid.
  • a transmission node identifier gNB-CU UE F1AP ID
  • cause information where the cause information is used to indicate a reason for sending the context information of the transmission node, for example, to perform RRC reconstruction.
  • validity time information which is used to indicate a validity period of the context information.
  • period information which is used to indicate a period for sending the context information.
  • Step 2 After receiving the context information of one or more DUs sent by the CU, the DU saves the context information.
  • the DU may send a confirmation message to the CU.
  • Embodiment 1-1 For the scenario where the CU and DU are separated, the difference from Embodiment 1-1 is that before the CU sends the context information of one or more DUs to the DU through the F1 interface, the following operations can also be performed:
  • Step 1 The DU sends a message through the F1 interface for requesting to obtain context information of a certain transmission node.
  • the DU after receiving the RRC re-establishment request sent by the transmission node, the DU sends a message request through the F1 interface to obtain context information of the transmission node.
  • the transmission node may be a terminal or an IAB.
  • the request for obtaining the context information of the transmission node includes: the identification of the transmission node (used to indicate the identification of the transmission node for F1 interface identification), the bearer establishment information, and further, the reason information may be included, the reason The information is used to indicate the reason for sending the context information of the transmission node, for example, the value is used to perform reconstruction.
  • the context information of the DU is sent to the potential serving node.
  • the CU may notify the potential service node to release the context information of the DU.
  • Step 1 The IAB directly exchanges the context information of its child nodes through the Xn interface; including the identity of the child node and carrying the establishment information.
  • Step 2 The IAB determines which IAB has the context information of its child IAB, and sends the IAB list to the child IAB.
  • the IAB list includes identification information of the IAB.
  • Step 3 After the child IAB fails to connect to the link, the IAB node in the IAB list is preferentially selected for reconstruction.
  • Step 1 The IAB directly exchanges its own context information through the Xn interface;
  • Step 2 The IAB determines which IABs have their own context information. When a link failure occurs, the IAB preferentially selects the IAB node with its own context information for reconstruction.
  • Step 1 The IAB directly exchanges the context information of its child nodes through the Xn interface; including the identity of the child node and carrying the establishment information.
  • Step 2 The IAB sends an RRC connection release or RRC connection rejection message to its child node or terminal.
  • the RRC connection release or RRC connection rejection message includes an IAB list.
  • the IAB list includes identification information of the IAB, identification information of the host IAB connected to the IAB, and PLMN information.
  • Step 3 When a link failure occurs between the child node or the terminal, the IAB node in the IAB list is preferentially selected for reconstruction.
  • the topology management entity eg.donor, IAB, parent, IAB
  • the topology management entity periodically selects one or more candidate targets for each IAB node or UE, and notifies the IAB node if the topology management entity is the parent IAB.
  • the IAB sends a handover preparation request to the candidate, the target, and the parent.
  • the IAB needs to allocate a C-RNTI to the IAB in advance, a secret key id used to execute the security algorithm, a proprietary RACH resource, and combine this information with the RACH-related SS.
  • Block information, UE-specific CSI-RS, SIB and other information are notified to the IAB.
  • the source parent IAB detects blockage of the IAB or UE, the source parent IAB initiates a handover activation indication to the candidate target IAB, and sends SN status information and performs data forwarding.
  • the IAB will initiate a random access request to the candidate, target, and parent on the given RACH resource, and report a new C-RNTI to complete the handover operation and establish an RRC connection.
  • the UE / IAB when the UE / IAB detects that the link connection fails, it sends a random access request to a candidate target IAB.
  • the candidate target receives a random access request from the UE / IAB, it determines that the handover process is active and sends the request to the source.
  • the IAB sends a handover activation request.
  • the source IAB After the source IAB receives the handover activation request, it sends a confirmation message, or directly sends the SN status information and performs data forwarding.
  • the candidate IAB also needs to allocate resources for the IAB in advance and inform the IAB. Before the handover is activated, this part of the resources can be dynamically dispatched to other terminals for use. After confirming the activation of the switch, it will no longer be assigned to other terminals and left to the IAB.
  • the source parent IAB can also notify other candidate targets that the parent IAB releases the context of the IAB and the related resources reserved for the handover.
  • FIG. 9 is a first schematic flowchart of an embodiment of the present disclosure, including:
  • Step 1 The source service node sends the handover preparation request information to the target service node, and the handover preparation request information includes at least one of the following: cause information, valid time information, period information, and identification information of the target transmission node.
  • the handover preparation information is a special message, such as a handover preparation request message or a reconstruction preparation request message; or the handover preparation request information is carried by a handover request message.
  • the reason information is used to indicate that the reason for the handover preparation request is an advance handover preparation request or a reconstruction preparation request.
  • the validity time information is used to indicate the validity period of the handover preparation request. When the handover operation is not performed after the validity time is exceeded, the handover preparation request information becomes invalid.
  • the period information is used to indicate a period for sending the handover preparation request message.
  • the handover preparation request information is invalid. (Note: The valid time and period are used in the same way here, except that the period is used to indicate that the switching request information is sent periodically.)
  • the source transmission node may send handover request information to multiple target transmission nodes, where the handover request information is used to request reservation of handover resources.
  • the identification information of the target transmission node is used to indicate the identification information of the target transmission node, and may be one or more.
  • Step 2 After receiving the handover preparation request information, the target service node sends a handover preparation request confirmation message to the source service node.
  • the confirmation information includes a C-RNTI allocated to the terminal, a key used to execute a security algorithm, and a dedicated RACH resource. Further, it may further include SS block information related to RACH, a UE-specific CSI-RS, and a system. Messages and more.
  • the handover preparation request confirmation information is a special message, such as a handover preparation request confirmation message or a reconstruction preparation request confirmation message; or the handover preparation request information is carried by a handover request confirmation message.
  • Step 3 After receiving the handover preparation request confirmation information, the source service node sends the mobile control information for indicating handover to the terminal or the IAB node.
  • the mobile control information includes a C-RNTI allocated to a terminal or an IAB, a key used to execute a security algorithm, and a proprietary random access RACH resource. Further, it may further include RACH-related SS block information, which is UE-specific. CSI-RS, system messages and other information.
  • the mobility control information includes handover activation condition information, for example, performing handover when a wireless link failure occurs. Further, the movement control information includes time information for indicating a sending period of the information or indicating a valid time of the message.
  • the source service node When the source service node detects that the terminal has a link interruption, it activates the handover process, which includes the following steps:
  • Step 4 The source service node sends a handover activation request message to the target service node.
  • the handover activation information includes terminal identification information and cause information.
  • the reason information indicates that the handover is active.
  • the target service node may reject the handover activation request based on the current load situation, so if it agrees to activate, it sends a handover activation confirmation message to the source service node.
  • Step 6 After the source service node receives the handover activation confirmation information of the target service node, it starts to perform SN status transmission. If there is unreported data, the user data is forwarded to the target service node.
  • the terminal can activate the handover process and send a random access request to the target serving node according to the received mobile control information.
  • Step 7 After receiving the UE's access request, the target service node executes subsequent access operations to complete the handover process.
  • the terminal includes a terminal node and a terminal function part of the IAB node.
  • the source service node selects multiple candidate target service nodes for the terminal, after the terminal replaces the service node, the source service node notifies the candidate target service node to release the context information of the terminal.
  • the measurement is performed and the measurement result is reported to the source service node.
  • the source service node selects a candidate target service node for the terminal or the IAB according to the measurement result.
  • the source service node After the source service node sends the handover preparation request information to the candidate target service node, before the handover activation information is sent, if the source service node re-selects a new potential target handover service node based on the measurement results reported by the terminal, it can send to the previous
  • the candidate target service node sends handover cancellation instruction information, and the instruction information includes a cause value of the handover cancellation.
  • the target transmission node receives the handover cancellation indication information, the context information of the terminal corresponding to the handover cancellation information is released, and if there is a reserved resource, the reserved resource is further released. This includes:
  • Step 1 The source service node sends handover request information to the candidate target service node, and the handover request information includes at least one of the following: cause information, valid time information, period information, and identification information of the target transmission node.
  • the reason information is used to indicate that the reason for the handover request is an advance handover preparation request or a reconstruction preparation request.
  • the validity time information is used to indicate the validity period of the handover request. When the handover operation is not performed after the validity time is exceeded, the handover request information is invalid.
  • the cycle information is used to indicate a cycle of sending the handover request message.
  • the handover request information is invalid. (Note: The valid time and period are used in the same way here, except that the period is used to indicate that the switching request information is sent periodically.)
  • the source transmission node may send handover request information to multiple candidate target transmission nodes, where the handover request information is used to request reservation of handover resources.
  • the identification information of the target transmission node is used to indicate the identification information of the target transmission node, and may be one or more.
  • Step 2 After receiving the handover request information, the candidate target service node sends a handover request confirmation message to the source service node.
  • the confirmation information includes a C-RNTI allocated to the terminal, a key used to execute a security algorithm, a proprietary RACH resource, and further, it may further include SS block information related to RACH, a UE-specific CSI-RS, and a system. Messages and more.
  • Step 3 After receiving the handover request confirmation information, the source service node sends the mobile control information indicating the handover to the terminal node.
  • the mobile control information includes a C-RNTI allocated by the terminal, a key used to execute a security algorithm, and a dedicated RACH resource. Further, it may further include RACH-related SS block information, a UE-specific CSI-RS, and a system. Messages and more.
  • the mobility control information includes handover activation condition information, for example, performing handover when a wireless link failure occurs. Further, the movement control information includes time information for indicating a sending period of the information or indicating a valid time of the message.
  • Step 4 Based on the measurement result reported by the terminal, the source service node reselects a new candidate target switching service node, and may send handover cancellation instruction information to the previous candidate target service node, where the instruction information includes the reason for the handover cancellation value.
  • Step 5 After receiving the handover cancellation indication information, the candidate target transmission node releases the context information of the terminal corresponding to the handover cancellation information, and if there are reserved resources, further release the reserved resources.
  • FIG. 10 is a second schematic flowchart of an embodiment of the present disclosure, including:
  • Step 1 The source service node sends the handover preparation request information to the target service node, and the handover preparation request information includes at least one of the following: cause information, valid time information, period information, and identification information of the target transmission node.
  • the handover preparation information is a special message, such as a handover preparation request message or a reconstruction preparation request message; or the handover preparation request information is carried by a handover request message.
  • the reason information is used to indicate that the reason for the handover preparation request is an advance handover preparation request or a reconstruction preparation request.
  • the validity time information is used to indicate the validity period of the handover preparation request. When the handover operation is not performed after the validity time is exceeded, the handover preparation request information becomes invalid.
  • the period information is used to indicate a period for sending the handover preparation request message.
  • the handover preparation request information is invalid. (Note: The valid time and period are used in the same way here, except that the period is used to indicate that the switching request information is sent periodically.)
  • the source transmission node may send handover request information to multiple target transmission nodes, where the handover request information is used to request reservation of handover resources.
  • the identification information of the target transmission node is used to indicate the identification information of the target transmission node, and may be one or more.
  • Step 2 After receiving the handover preparation request information, the target service node sends a handover preparation request confirmation message to the source service node.
  • the confirmation information includes a C-RNTI allocated for the terminal, a key used to execute a security algorithm, and a dedicated RACH resource. Further, it may further include SS block information related to RACH, UE-specific CSI-RS, and Messages and more.
  • the handover preparation request confirmation information is a special message, such as a handover preparation request confirmation message or a reconstruction preparation request confirmation message; or the handover preparation request information is carried by a handover request confirmation message.
  • Step 3 After receiving the handover preparation request confirmation information, the source service node sends the mobile control information for indicating handover to the terminal or the IAB node.
  • the mobile control information includes a C-RNTI allocated to a terminal or an IAB, a key used to execute a security algorithm, and a proprietary random access RACH resource. Further, it may further include RACH-related SS block information, which is UE-specific. CSI-RS, system messages and other information.
  • the mobility control information includes handover activation condition information, for example, performing handover when a wireless link failure occurs. Further, the movement control information includes time information for indicating a sending period of the information or indicating a valid time of the message.
  • the terminal or IAB When the terminal or IAB detects that the wireless link fails, it can activate the handover process, which includes the following steps:
  • Step 4 The terminal or the IAB sends a random access request to the target serving node according to the received mobile control information.
  • Step 4 After receiving the random access information initiated by the terminal, the target service node sends handover activation instruction information to the source service node of the terminal.
  • Step 5 Further, after the source service node receives the handover activation information sent by the target service node, it sends a handover activation confirmation message. Alternatively, after receiving the handover activation information sent by the target transmission node, the source transmission node directly sends SN (sequence number) status information to the target transmission node. If there is unreported data, the user data is forwarded to the target service node.
  • SN sequence number
  • Step 6 The target service node performs subsequent access operations and completes the handover process.
  • Embodiment 2 This embodiment is similar to Embodiment 2, but the difference is that this embodiment is applied to the scenario where CU and DU are separated, and CU (Centralized Management Unit) is selected for each DU (Distributed Unit)
  • CU Centralized Management Unit
  • DU Distributed Unit
  • FIG. 11 is a third schematic flowchart of an embodiment of the present disclosure, including:
  • Step 1 The donor CU sends the terminal or IAB context establishment request information to the target DU.
  • the context establishment request information includes at least one of the following: cause information, valid time information, period information, and identification information of the target DU.
  • the reason information is used to indicate that the cause of the context establishment request is an advance handover preparation request or a reconstruction preparation request.
  • the validity time information is used to indicate the validity period of the context establishment request. When the switching or rebuilding operation is not performed after the validity time is exceeded, the context establishment request information becomes invalid.
  • the period information is used to indicate the period for sending the context establishment request message.
  • the context establishment request information becomes invalid.
  • the CU may send context establishment request information to multiple target DUs, where the context establishment request information is used to request preparation of switching resources or preparation of reconstruction information.
  • Step 2 After receiving the context establishment request information, the target DU sends a context establishment request confirmation message to the donor CU.
  • the confirmation information includes a C-RNTI allocated for the terminal or the IAB, a key used to execute a security algorithm, a proprietary RACH resource, and further, it may further include SS block information related to RACH, UE or IAB-specific CSI -RS, system messages, etc.
  • Step 3 After receiving the context establishment request confirmation information, the donor sends the context adjustment request information to the terminal or the source DU of the IAB.
  • Step 4 The source DU sends RRC reconfiguration information to the terminal or IAB.
  • the RRC reconfiguration information includes a C-RNTI allocated for a terminal or an IAB, a secret key used to execute a security algorithm, a proprietary RACH resource, and further, it may further include RACH-related SS block information, and UE-specific CSI -RS, system messages, etc. Further, it further includes handover activation condition information, for example, performing handover when a wireless link fails. Further, it further includes time information, which is used to indicate a sending period of the information or to indicate a valid time of the message.
  • the switchover process is activated, including the following steps:
  • Step 5 The source DU sends context adjustment response information to the donor CU.
  • the context adjustment response information includes terminal or IAB identification information and cause information.
  • the reason information indicates that the handover is active.
  • Step 6 In parallel with step 5, after the terminal or IAB detects that the wireless link fails, it can activate the handover process and send a random access request to the target service node according to the received RRC reconfiguration information.
  • Step 7 After receiving the UE's access request, the target DU sends an RRC reconfiguration completion message to the donor CU.
  • the donor CU requests the source DU to release the context information of the terminal or IAB.
  • the terminal includes a terminal node, and a terminal function part of the terminal node.
  • the CU selects multiple candidate serving IAB nodes for the terminal or IAB, after the terminal or IAB replaces the serving node, or when the CU selects a new serving IAB node for the terminal or IAB, the CU notifies the original The serving IAB node and the candidate serving IAB node release the context information of the terminal or IAB.
  • Step 1 Step 2
  • Step 3 The difference between this embodiment and Embodiment 3-1 is that the order of execution steps has been changed, and Step 1, Step 2, and Step 3 are performed in sequence.
  • step 6 is performed, and the target service DU is executed.
  • the CU After receiving the random access request from the terminal or IAB, the CU is informed of the switching activation, and then the CU sends the switching activation information to the source service DU.
  • the source service DU receives the activation information, it sends the downlink data status information to the CU, and the CU forwards
  • the target service DU performs step 7 and the CU performs steps 8 and 9.
  • the switch is complete.
  • FIG. 12 is a fourth flowchart of an embodiment of the present disclosure.
  • An embodiment of the present disclosure further provides a storage medium that stores a computer program therein, wherein the computer program is configured to execute the steps in any one of the foregoing method embodiments when running.
  • the foregoing storage medium may be configured to store a computer program for performing the following steps:
  • the foregoing storage medium may include, but is not limited to, a U disk, a read-only memory (ROM), a random access memory (Random Access Memory, RAM), A variety of media that can store computer programs, such as removable hard disks, magnetic disks, or optical disks.
  • ROM read-only memory
  • RAM Random Access Memory
  • An embodiment of the present disclosure further provides an electronic device including a memory and a processor.
  • the memory stores a computer program
  • the processor is configured to run the computer program to perform the steps in any one of the foregoing method embodiments.
  • the electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the processor, and the input-output device is connected to the processor.
  • the foregoing processor may be configured to execute the following steps by a computer program:
  • modules or steps of the present disclosure may be implemented by a general-purpose computing device, and they may be centralized on a single computing device or distributed on a network composed of multiple computing devices. Above, optionally, they may be implemented with program code executable by a computing device, so that they may be stored in a storage device and executed by the computing device, and in some cases, may be in a different order than here
  • the steps shown or described are performed, or they are separately made into individual integrated circuit modules, or multiple modules or steps in them are made into a single integrated circuit module for implementation. As such, the present disclosure is not limited to any particular combination of hardware and software.
  • the disclosure is applicable to the communication field.
  • the context information can be used for link recovery, avoiding the re-establishment process and solving the problem.
  • the technical problem of excessively long recovery delay of the link interruption in the related technology meets the delay requirement of the service business.

Landscapes

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

Abstract

本公开提供了一种信息传输方法及装置、存储介质、电子装置，其中，该方法包括：第三传输节点接收第一传输节点发送的所述第一传输节点或者第二传输节点的上下文信息；所述第三传输节点保存所述上下文信息。通过本公开，解决了相关技术中链路中断的恢复时延过长的技术问题。

Description

信息传输方法及装置、存储介质、电子装置 技术领域
本公开涉及通信领域，具体而言，涉及一种信息传输方法及装置、存储介质、电子装置。
背景技术
相关技术为了提升网络容量和覆盖，同时兼顾小区部署灵活性的需求，提出一种支持无线回程传输的中继链路用于实现密集网络的部署。把支持中继功能的节点称之为Relay Node，简称RN。RN对于接入其小区的UE提供与普通eNB类似的功能和服务，RN与UE间的无线接口称之为“接入链路”(Access Link)，RN通过无线接口以类似于普通UE的方式接入一个服务于它的基站eNB，服务于RN的eNB称之为宿主基站(Donor eNB，简称DeNB)。RN与DeNB间的无线接口称之为“回传链路”(Backhaul Link)。
未来通信技术支持更大的带宽且支持更大规模的多天线或者多波束的传输，为这种回传链路和接入链路共享空口资源的中继的实现提供了便利的条件，我们称之为集成接入回程(Integrated Access Backhaul，简称为IAB)。为了进一步的提升部署的灵活性，普通的IAB不需要直接与核心网相连，只有宿主IAB(IAB donor)直接与核心网相连，因此，普通IAB都必须将数据传输到宿主IAB才能与核心网进行通信。参见图1，图1是本公开相关技术中的IAB链路示意图，IAB节点A通过光纤与核心网相连，为IAB donor，而IAB节点B和C不与核心网相连，为普通IAB。
为了进一步的提升部署的灵活性，参见图2，图2是本公开相关技术中的IAB节点作为中继的链路示意图，IAB可以经过多个IAB作为中继将数据传输到达IAB donor，换句话说，IAB是分层级的，所谓IAB层级代表着该IAB传输到达IAB donor需要经过的IAB跳数。假设donor IAB的层级为0，UE接入IAB的层级为N，那么UE与核心网的传输路径是依次经过层级为1，2，..N的IAB。假设IAB与IAB之间建立连接的过程与UE和基站建立连接的过程类似，那么层级为n+1的IAB对于层级为n的IAB来说就是UE，反之，层级为n的IAB对于层级为n的IAB来说就是服务小区。如果层级为n+1的IAB通过Uu口以UE的方式接入到层级为n的IAB，我们称呼层级为n的IAB为层级为n+1的IAB的母节点，而层级为n+1的IAB为层级为n的IAB的子节点。每个IAB可以选择接入一个或者多个母节点。当第n级的IAB由于拥塞或者链路质量不佳等原因导致与其母节点的连接发生中断时，现有机制只能通过重建流程重新建立流程，但这样造成的中断时延非常长，可能无法满足服务业务的时延需求。
由于链路状态不佳或者拥塞等原因导致中继节点与其服务节点链路通信中断时，现有机制只能通过重建流程重新建立流程，但这样造成的中断时延非常长，可能无法满足服务业务的时延需求。
针对相关技术中存在的上述问题，目前尚未发现有效的解决方案。
发明内容
本公开实施例提供了一种信息传输方法及装置、存储介质、电子装置。
根据本公开的一个实施例，提供了一种信息传输方法，包括：第三传输节点接收第一传输节点发送的所述第一传输节点或者第二传输节点的上下文信息；所述第三传输节点保存所述上下文信息。
根据本公开的一个实施例，提供了另一种信息传输方法，包括：传输节点的目标服务节点接收所述传输节点的源服务节点发送的切换准备请求，其中，所述切换准备请求包括以下至少之一：原因信息，有效时间信息，周期信息，所述目标传输节点的标识信息。所述目标服务节点在接收到切换准备请求信息后，向所述源服务节点发送切换准备确认信息；其中，所述原因信息用于指示所述切换准备请求原因为一种提前的切换准备请求或者重建准备请求；所述有效时间信息用于指示所述切换准备请求的有效期；所述周期信息用于指示所述切换准备请求消息发送的周期，当超过所述周期时间后没有执行切换或者重建操作时，所述切换准备请求失效。
根据本公开的一个实施例，提供了又一种信息传输方法，包括：传输节点接收所述传输节点的目标服务节点发送的移动控制消息，其中，所述移动控制消息用于指示所述传输节点执行切换；所述传输节点接收到所述移动控制消息后，执行切换流程；其中，所述传输节点为终端或者IAB。
根据本公开的一个实施例，提供了又一种信息传输方法，传输节点接收所述传输节点的源服务节点发送的RRC连接释放消或者RRC连接拒绝消息，其中，所述RRC连接释放消息或者RRC连接拒绝消息包括IAB列表，所述IAB列表包括：IAB的标识信息，IAB连接的宿主IAB的标识信息，公共陆地移动网络PLMN信息；在所述传输节点发生链路连接失败时，优先选择所述IAB列表中的IAB节点进行重建。
根据本公开的另一个实施例，提供了一种信息传输装置，包括：接收模块，设置为接收第一传输节点发送的所述第一传输节点或者第二传输节点的上下文信息；保存模块，设置为保存所述上下文信息。
根据本公开的另一个实施例，提供了另一种信息传输装置，应用在传输节点的目标服务节点，包括：接收模块，设置为接收所述传输节点的源服务节点发送的切换准备请求，其中，所述切换准备请求包括以下至少之一：原因信息，有效时间信息，周期信息，所述目标传输节点的标识信息。发送模块，设置为在接收到切换准备请求信息后，向所述源服务节点发送切换准备确认信息；其中，所述原因信息用于指示所述切换准备请求原因为一种提前的切换准备请求或者重建准备请求；所述有效时间信息用于指示所述切换准备请求的有效期；所述周期信息用于指示所述切换准备请求消息发送的周期，当超过所述周期时间后没有执行切换或者重建操作时，所述切换准备请求失效。
根据本公开的另一个实施例，提供了又一种信息传输装置，应用在传输节点的目标切换服务节点，包括：发送模块，设置为发送所述传输节点的移动控制消息，其中，所述移动控 制消息用于指示所述传输节点执行切换，其中，所述传输节点目标切换服务节点为所述传输节点的源辅服务节点；其中，所述传输节点为终端或者IAB。
根据本公开的另一个实施例，提供了又一种信息传输装置，应用在传输节点，包括：接收模块，设置为接收所述传输节点的源服务节点发送的RRC连接释放消或者RRC连接拒绝消息，其中，所述RRC连接释放消息或者RRC连接拒绝消息包括IAB列表，所述IAB列表包括：IAB的标识信息，IAB连接的宿主IAB的标识信息，公共陆地移动网络PLMN信息；处理模块，设置为发生链路连接失败时，优先选择所述IAB列表中的IAB节点进行重建。
根据本公开的又一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本公开，通过接收和保存第一传输节点或者第二传输节点的上下文信息，在存在传输节点链路中断时，可以使用上下文信息进行链路恢复，避免了重新建立流程，解决了相关技术中链路中断的恢复时延过长的技术问题，满足了服务业务的时延需求。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是本公开相关技术中的IAB链路示意图；
图2是本公开相关技术中的IAB节点作为中继的链路示意图；
图3是根据本公开实施例的一种信息传输方法的流程图；
图4是根据本公开实施例的另一种信息传输方法的流程图；
图5是根据本公开实施例的又一种信息传输方法的流程图；
图6是根据本公开实施例的一种信息传输装置的结构框图；
图7是根据本公开实施例的另一种信息传输装置的结构框图；
图8是根据本公开实施例的又一种信息传输装置的结构框图；
图9是本公开实施方式的流程示意图一；
图10是本公开实施方式的流程示意图二；
图11是本公开实施方式的流程示意图三；
图12是本公开实施方式的流程示意图四。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等 是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
在本实施例中提供了一种信息传输方法，图3是根据本公开实施例的一种信息传输方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，第三传输节点接收第一传输节点发送的第一传输节点或者第二传输节点的上下文信息；
步骤S304，第三传输节点保存上下文信息。
通过上述步骤，通过接收和保存第一传输节点或者第二传输节点的上下文信息，在存在传输节点链路中断时，可以使用上下文信息进行链路恢复，避免了重新建立流程，解决了相关技术中链路中断的恢复时延过长的技术问题，满足了服务业务的时延需求。
可选地，对于CU,DU分离的场景，第一传输节点为集中单元CU，第二传输节点为分布式单元DU，第三传输节点包括一个或者多个DU时，第一传输节点通过F1接口发送上下文信息。
可选地，在第三传输节点接收第一传输节点发送的第一传输节点或者第二传输节点的上下文信息之前，方法还包括：第三传输节点通过F1接口发送用于请求获取上下文信息的请求消息。
可选地，第三传输节点通过F1接口发送用于请求获取上下文信息的消息包括：第三传输节点在接收到RRC重建请求时，通过F1接口发送请求消息。
可选地，上下文信息包括：传输节点标识，传输节点的上下文信息。
可选地，上下文信息还包括以下至少之一：原因信息，其中，原因信息用于指示发送上下文信息的原因，其中，原因包括以下之一：切换准备，重建准备；有效时间信息，其中，有效时间信息用于指示上下文信息的有效期；周期信息，其中，周期信息用于指示上下文信息发送的周期，当超过周期时间后仍然没有执行切换或者重建操作，上下文信息失效。
可选地，在第一传输节点发送上下文信息之后，第一传输节点发送用于释放第一传输节点或者第二传输节点的上下文信息的指示信息。
在第四传输节点发生链路连接失败时，优先选择与第四传输节点的源服务节点拥有相同宿主节点的目标传输节点执行无线资源控制RRC重建流程，其中，第四传输节点为终端或者IAB。
可选地，对于CU,DU不分离的场景，在第一传输节点，第二传输节点，第三传输节点为中继节点时，上下文信息通过Xn接口进行传输。可选地，中继节点包括以下至少之一：基站，集成接入回程IAB节点。
可选地，在第四传输节点发生链路连接失败时，优先选择拥有第四传输节点上下文信息的目标传输节点执行RRC重建流程，其中，第四传输节点为终端或者IAB。
在本实施例中提供了另一种信息传输方法，图4是根据本公开实施例的另一种信息传输方法的流程图，如图4所示，该流程包括如下步骤：
步骤S402，传输节点的目标服务节点接收传输节点的源服务节点发送的切换准备请求， 其中，切换准备请求包括以下至少之一：原因信息，有效时间信息，周期信息，目标传输节点的标识信息；
步骤S404，目标服务节点在接收到切换准备请求信息后，向源服务节点发送切换准备确认信息；
其中，原因信息用于指示切换准备请求原因为一种提前的切换准备请求或者重建准备请求；有效时间信息用于指示切换准备请求的有效期；周期信息用于指示切换准备请求消息发送的周期，当超过周期时间后没有执行切换或者重建操作时，切换准备请求失效。
可选的，源服务节点向多个目标服务节点发送切换准备请求信息，其中，切换准备请求信息用于请求准备切换资源，多个目标传输节点的标识信息与多个目标服务节点对应。
可选地，源服务节点为以下至少之一：集中单元CU，分布式单元DU,集成接入回程IAB节点，中继，基站；目标服务节点为以下至少之一：分布式单元DU,IAB节点，中继，基站。
可选地，在传输节点为IAB节点时，源服务节点为IAB节点的父节点。
可选地，目标服务节点在接收到切换准备请求后，向源服务节点发送切换激活指示信息。
可选地，在向源服务节点发送切换激活指示信息之后，方法还包括：接收源服务节点发送的切换激活确认信息；或者，接收源服务节点发送的序列号SN状态信息。
可选地，在源服务节点检测到服务节点发生链路连接失败后，向目标服务节点发送切换激活指示信息。
可选地，源服务节点向目标服务节点发送切换准备请求信息后，向目标服务节点发送切换取消指示信息，切换取消指示信息包括切换取消的原因值，当目标服务节点接收到切换取消指示信息后，释放掉切换取消信息对应的传输节点的上下文信息和/或传输节点的预留资源。
可选地，源服务节点向目标服务节点发送切换准备请求信息后，向传输节点发送移动控制信息，其中，移动控制信息包括切换激活条件信息，切换激活条件信息包括：用于指示移动控制信息的发送周期或者指示该消息的有效时间的时间信息，或者，当发生无线链路失败时执行切换的信息。
在本实施例中提供了又一种信息传输方法，图5是根据本公开实施例的又一种信息传输方法的流程图，如图5所示，该流程包括如下步骤：
步骤S502，传输节点接收传输节点的目标服务节点发送的移动控制消息，其中，移动控制消息用于指示传输节点执行切换；
步骤S504，传输节点接收到移动控制消息后，执行切换流程；
其中，传输节点为终端或者IAB。
可选地，目标服务节点为传输节点的源服务辅节点。
本实施例还提供了一种信息传输方法，包括：
S11，传输节点接收传输节点的源服务节点发送的RRC连接释放消或者RRC连接拒绝消息，其中，RRC连接释放消息或者RRC连接拒绝消息包括IAB列表，IAB列表包括：IAB的标识信息，IAB连接的宿主IAB的标识信息，公共陆地移动网络PLMN信息；
S11，在传输节点发生链路连接失败时，优先选择IAB列表中的IAB节点进行重建。其 中，传输节点可以为IAB或终端。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例的方法。
实施例2
在本实施例中还提供了一种信息传输装置，用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图6是根据本公开实施例的一种信息传输装置的结构框图，如图6所示，该装置包括：
接收模块60，用于接收第一传输节点发送的第一传输节点或者第二传输节点的上下文信息；
保存模块62，用于保存上下文信息。
图7是根据本公开实施例的另一种信息传输装置的结构框图，应用在传输节点的目标服务节点，如图7所示，该装置包括：
接收模块70，用于接收传输节点的源服务节点发送的切换准备请求，其中，切换准备请求包括以下至少之一：原因信息，有效时间信息，周期信息，目标传输节点的标识信息；
发送模块72，用于在接收到切换准备请求信息后，向源服务节点发送切换准备确认信息；
其中，原因信息用于指示切换准备请求原因为一种提前的切换准备请求或者重建准备请求；有效时间信息用于指示切换准备请求的有效期；周期信息用于指示切换准备请求消息发送的周期，当超过周期时间后没有执行切换或者重建操作时，切换准备请求失效。
可选的，发送模块还用于：向传输节点的源服务节点发送切换激活指示信息，接收模块还用于：接收传输节点的源服务节点发送的切换激活指示信息。
图8是根据本公开实施例的又一种信息传输装置的结构框图，应用在传输节点的目标切换服务节点，如图8所示，该装置包括：
发送模块80，用于发送传输节点的移动控制消息，其中，移动控制消息用于指示传输节点执行切换，其中，传输节点目标切换服务节点为传输节点的源辅服务节点；其中，传输节点为终端或者IAB。
本实施例还提供了信息传输装置，应用在传输节点，包括：接收模块，用于接收传输节点的源服务节点发送的RRC连接释放消或者RRC连接拒绝消息，其中，RRC连接释放消息或者RRC连接拒绝消息包括IAB列表，IAB列表包括：IAB的标识信息，IAB连接的宿主IAB的标识信息，公共陆地移动网络PLMN信息；
处理模块，用于发生链路连接失败时，优先选择IAB列表中的IAB节点进行重建。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本实施例包括以下实施方式，用于在不同的场景对本申请的方案进行详细说明：
实施方式1
重建优化方案：为了确保重建成功，终端或者IAB节点最好能事先获知哪些cell拥有自己的上下文信息。对于CU/DU split的场景，donor CU可以获得IAB的上下文信息，因此我们提出连接到同一个donor CU的IAB DU都通过donor CU获得其他IAB DU的上下文信息，那么如果选择的重建IAB与原来的parent IAB连接到同一个donor CU，那么重建比较容易获得成功。本实施方式中，DU和CU之间通过F1AP交互上下文信息。
当重建发生时，优先选择连接到相同donor CU下的IAB作为重建目标IAB。
另外，对于non CU/DU split的场景，IAB donor也可以获取保存直接连接或间接接入的所有child IAB的上下文信息并通知给其他相邻child IAB，这样IAB节点在检测到RLF时可以优先选择相同IAB donor下的其他IAB节点作为重建目标IAB；此外不同IAB节点之间可以直接通过Xn接口交互接入的子女IAB节点的上下文信息，父母IAB节点可以事先告知child IAB哪些相邻IAB节点上拥有其上下文信息，后续可以作为优选的重建目标IAB。或者不同IAB节点之间直接通过Xn接口交互各自的上下文信息，这样IAB知道哪些IAB拥有自己的上下文信息，将这些拥有自己上下文信息的IAB作为优选的重建目标IAB。
本实施方式包括：
实施方式1-1
对于CU,DU分离的场景：
步骤1：CU通过F1接口向DU发送一个或者多个IAB的上下文信息。
其中，所述上下文信息包括：传输节点标识(gNB-CU UE F1AP ID)，承载建立信息。进一步的，还可以包括原因信息，所述原因信息用于指示发送所述传输节点的上下文信息的原因，例如用于执行RRC重建。进一步的，还可以包含有效时间信息，用于指示所述上下文信息的有效期，当超过所述有效时间后仍然没有执行切换或者RRC重建操作，那么该上下文信息失效。
进一步地，包括周期信息，用于指示该上下文信息发送的周期，当超过所述周期时间后仍然没有执行切换或者RRC重建操作，该上下文信息信息失效。
步骤2：DU接收到CU发送的一个或者多个DU的上下文信息后，保存所述上下文信息。可选的，DU可向CU发送确认信息。
实施方式1-2
对于CU,DU分离的场景，与实施方式1-1的区别在于，在CU通过F1接口向DU发送一个或者多个DU的上下文信息之前，还可以执行以下操作：
步骤1：DU通过F1接口发送消息用于请求获取某个传输节点的上下文信息。或者：
进一步地，DU在接收到所述传输节点发送的RRC重建请求后，DU通过F1接口发送消息请求获取所述传输节点的上下文信息。其中，传输节点可以为终端或者IAB。
其中，所述请求获取传输节点的上下文信息包括：传输节点标识(用于指示该传输节点的标识，用于F1接口进行识别)，承载建立信息，进一步的，还可以包括原因信息，所述原因信息用于指示发送所述传输节点的上下文信息的原因，例如，取值为用于执行重建。
实施方式1-3
对于CU,DU分离的场景，当CU为DU选择了潜在的服务节点后，将该DU的上下文信息发送给潜在的服务节点，但CU根据信道和业务状况决定为DU更换潜在服务节点后，如果之前选定的某个潜在的服务节点不再作为此时的潜在服务节点后，则CU可以通知所述潜在服务节点释放掉所述DU的上下文信息。
实施方式1-4
对于CU，DU不分离的场景：
步骤1：IAB之间直接通过Xn接口交互其子节点的上下文信息；包括子节点的标识，承载建立信息。
步骤2：IAB确定哪些IAB拥有其child IAB的上下文信息，并将所述IAB列表发送给child IAB。所述IAB列表包括IAB的标识信息。
步骤3：当child IAB发生链路连接失败后，优先选择IAB列表中的IAB节点进行重建。
实施方式1-5
对于CU，DU不分离的场景，
步骤1：IAB之间直接通过Xn接口交互自己的上下文信息；
步骤2：IAB确定哪些IAB拥有自己的上下文信息，当发生链路连接失败后，优先选择拥有自己的上下文信息的IAB节点进行重建。
实施方式1-6
步骤1：IAB之间直接通过Xn接口交互其子节点的上下文信息；包括子节点的标识，承载建立信息。
步骤2：IAB发送RRC连接释放或者RRC连接拒绝消息给其子节点或者终端。所述RRC连接释放或者RRC连接拒绝消息包括IAB列表。所述IAB列表包括IAB的标识信息，IAB连接的宿主IAB的标识信息，PLMN信息。
步骤3：当子节点或者终端发生链路连接失败后，优先选择IAB列表中的IAB节点进行重建。
实施方式2
如果出现突然blockage造成通信中断，此时parent IAB还没有发起切换流程，正常的切换流程也无法进行。根据IAB测量的结果，拓扑管理实体(eg.donor IAB or parent IAB)周期的为每个IAB节点或者UE选择一个或者多个candidate target parent IAB，且通知给IAB节点，如果拓扑管理实体是parent IAB，则向candidate target parent IAB发送切换准备请求，candidate target parent IAB需要预先为IAB分配C-RNTI,用于执行安全算法的秘钥id，专有 的RACH资源，并将这些信息以及RACH相关的SS block信息，UE-specific CSI-RS，SIB等信息告知给IAB。一旦源parent IAB检测到所述IAB或者UE发生blockage，源parent IAB则向candidate target parent IAB发起切换激活指示，并发送SN status信息以及执行data forwarding。而IAB会在给定的RACH资源上向candidate target parent IAB发起随机接入请求，并上报新的C-RNTI，完成切换操作并建立RRC连接。
或者，当UE/IAB检测到链路连接失败后，向一个candidate target parent IAB发送随机接入请求，当candidate target parent IAB接收到UE/IAB的随机接入请求后，判断切换流程激活，向源IAB发送切换激活请求，源IAB接收到切换激活请求后，发送确认信息，或者直接发送SN状态信息并执行数据转发。
进一步地，为了减小切换带来的时延，candidate target parent IAB还需要预先为IAB分配资源并告知IAB，在切换激活之前，这部分资源可以动态调度给其他终端使用，当收到源parent IAB的切换激活确认后，则不再分配给其他终端，留给IAB使用。
进一步地，当切换完成后，源parent IAB还可以通知其他candidate目标parent IAB释放掉IAB的上下文以及为切换预留的相关资源。
具体步骤包括如下：
实施方式2-1
在终端或者IAB选择好服务节点接入后，执行测量并将测量结果上报给源服务节点，源服务节点根据测量结果为终端或者IAB选择候选的目标服务节点。然后开始执行切换准备工作。图9是本公开实施方式的流程示意图一，包括：
步骤1：源服务节点向目标服务节点发送切换准备请求信息，所述切换准备请求信息包括以下至少之一：原因信息，有效时间信息，周期信息，目标传输节点的标识信息。所述切换准备信息为一条专门的消息，例如切换准备请求消息或者重建准备请求消息；或者所述切换准备请求信息通过切换请求消息来携带。
其中，原因信息用于指示所述切换准备请求原因为一种提前的切换准备请求，或者重建准备请求。
有效时间信息用于指示所述切换准备请求的有效期，当超过所述有效时间后仍然没有执行切换操作，那么该切换准备请求信息失效。
周期信息用于指示该切换准备请求消息发送的周期，当超过所述周期时间后仍然没有执行切换操作，该切换准备请求信息失效。(说明：有效时间和周期在这里的使用方式相同，只是周期用于表示切换请求信息是周期发送的。)
进一步地，源传输节点可以向多个目标传输节点发送切换请求信息，所述切换请求信息用于请求预留切换资源。目标传输节点的标识信息用于指示目标传输节点的标识信息，可以是一个或者多个。
步骤2:目标服务节点在接收到切换准备请求信息后，向源服务节点发送切换准备请求确认信息。
所述确认信息包括为终端分配的C-RNTI,用于执行安全算法的秘钥，专有的RACH资源， 进一步地，还可以包括RACH相关的SS block信息，UE专有的CSI-RS，系统消息等信息。与步骤1对应的，所述切换准备请求确认信息为一条专门的消息，例如切换准备请求确认消息或者重建准备请求确认消息；或者所述切换准备请求信息通过切换请求确认消息来携带。
步骤3：源服务节点在接收到切换准备请求确认信息后，发送用于指示切换的移动控制信息给终端或者IAB节点。所述移动控制信息包括为终端或者IAB分配的C-RNTI,用于执行安全算法的秘钥，专有的随机接入RACH资源，进一步地，还可以包括RACH相关的SS block信息，UE专有的CSI-RS，系统消息等信息。进一步地，所述移动控制信息包括切换激活条件信息，例如：当发生无线链路失败时执行切换。进一步地，所述移动控制信息包括时间信息，用于指示该信息的发送周期或者指示该消息的有效时间。
当源服务节点检测发现终端发生链路中断时，则开始激活切换流程，包括以下步骤：
步骤4：源服务节点向目标服务节点发送切换激活请求信息，所述切换激活信息包括终端标识信息，原因信息。所述原因信息指示为切换激活。
步骤5：可选的，目标服务节点基于当前的负载情况，有可能会拒绝切换激活请求，因此如果同意激活，则向源服务节点发送切换激活确认信息。
步骤6：当源服务节点接收到目标服务节点的切换激活确认信息后，开始执行SN状态传输，如果存在未上报成功的数据，则将用户数据转发给目标服务节点。
另一方面，终端检测到自己发生无线链路失败后，可以激活切换流程，根据接收到的移动控制信息，向目标服务节点发送随机接入请求。
步骤7，目标服务节点在接收到UE的接入请求后，执行后续接入操作，完成切换流程。
其中，所述终端包括终端节点，IAB节点的终端功能部分。
进一步地，如果源服务节点为终端选择了多个候选的目标服务节点，当终端更换服务节点后，源服务节点通知候选的目标服务节点释放掉终端的上下文信息。
实施方式2-2
在终端或者IAB选择好服务节点接入后，执行测量并将测量结果上报给源服务节点，源服务节点根据测量结果为终端或者IAB选择候选的目标服务节点。
源服务节点向候选的目标服务节点发送切换准备请求信息后，在切换激活信息发送之前，如果源服务节点基于终端上报的测量结果，重新选择了新的潜在目标切换服务节点，则可以向之前的
候选的目标服务节点发送切换取消指示信息，所述指示信息包括切换取消的原因值。当目标传输节点接收到所述切换取消指示信息后，释放掉所述切换取消信息对应的终端的上下文信息，如果有预留资源，则进一步释放掉预留的资源。具体包括：
步骤1：源服务节点向候选的目标服务节点发送切换请求信息，所述切换请求信息包括以下至少之一：原因信息，有效时间信息，周期信息，目标传输节点的标识信息。
其中，原因信息用于指示所述切换请求原因为一种提前的切换准备请求，或者重建准备请求。
有效时间信息用于指示所述切换请求的有效期，当超过所述有效时间后仍然没有执行切 换操作，那么该切换请求信息失效。
周期信息用于指示该切换请求消息发送的周期，当超过所述周期时间后仍然没有执行切换操作，该切换请求信息失效。(说明：有效时间和周期在这里的使用方式相同，只是周期用于表示切换请求信息是周期发送的。)
进一步地，源传输节点可以向多个候选的目标传输节点发送切换请求信息，所述切换请求信息用于请求预留切换资源。目标传输节点的标识信息用于指示目标传输节点的标识信息，可以是一个或者多个。
步骤2:候选的目标服务节点在接收到切换请求信息后，向源服务节点发送切换请求确认信息。
所述确认信息包括为终端分配的C-RNTI,用于执行安全算法的秘钥，专有的RACH资源，进一步地，还可以包括RACH相关的SS block信息，UE专有的CSI-RS，系统消息等信息。
步骤3：源服务节点在接收到切换请求确认信息后，发送用于指示切换的移动控制信息给终端节点。所述移动控制信息包括终端分配的C-RNTI,用于执行安全算法的秘钥，专有的RACH资源，进一步地，还可以包括RACH相关的SS block信息，UE专有的CSI-RS，系统消息等信息。进一步地，所述移动控制信息包括切换激活条件信息，例如：当发生无线链路失败时执行切换。进一步地，所述移动控制信息包括时间信息，用于指示该信息的发送周期或者指示该消息的有效时间。
步骤4，源服务节点基于终端上报的测量结果，重新选择了新的候选的目标切换服务节点，则可以向之前的候选的目标服务节点发送切换取消指示信息，所述指示信息包括切换取消的原因值。
步骤5，当候选的目标传输节点接收到所述切换取消指示信息后，释放掉所述切换取消信息对应的终端的上下文信息，如果有预留资源，则进一步释放掉预留的资源。
实施方式2-3
本实施方式中，在终端或者IAB选择好服务节点接入后，执行测量并将测量结果上报给源服务节点，源服务节点根据测量结果为终端或者IAB选择候选的目标服务节点。图10是本公开实施方式的流程示意图二，包括：
步骤1：源服务节点向目标服务节点发送切换准备请求信息，所述切换准备请求信息包括以下至少之一：原因信息，有效时间信息，周期信息，目标传输节点的标识信息。所述切换准备信息为一条专门的消息，例如切换准备请求消息或者重建准备请求消息；或者所述切换准备请求信息通过切换请求消息来携带。
其中，原因信息用于指示所述切换准备请求原因为一种提前的切换准备请求，或者重建准备请求。
有效时间信息用于指示所述切换准备请求的有效期，当超过所述有效时间后仍然没有执行切换操作，那么该切换准备请求信息失效。
周期信息用于指示该切换准备请求消息发送的周期，当超过所述周期时间后仍然没有执行切换操作，该切换准备请求信息失效。(说明：有效时间和周期在这里的使用方式相同， 只是周期用于表示切换请求信息是周期发送的。)
进一步地，源传输节点可以向多个目标传输节点发送切换请求信息，所述切换请求信息用于请求预留切换资源。目标传输节点的标识信息用于指示目标传输节点的标识信息，可以是一个或者多个。
步骤2:目标服务节点在接收到切换准备请求信息后，向源服务节点发送切换准备请求确认信息。
所述确认信息包括为终端分配的C-RNTI,用于执行安全算法的秘钥，专有的RACH资源，进一步地，还可以包括RACH相关的SS block信息，UE专有的CSI-RS，系统消息等信息。与步骤1对应的，所述切换准备请求确认信息为一条专门的消息，例如切换准备请求确认消息或者重建准备请求确认消息；或者所述切换准备请求信息通过切换请求确认消息来携带。
步骤3：源服务节点在接收到切换准备请求确认信息后，发送用于指示切换的移动控制信息给终端或者IAB节点。所述移动控制信息包括为终端或者IAB分配的C-RNTI,用于执行安全算法的秘钥，专有的随机接入RACH资源，进一步地，还可以包括RACH相关的SS block信息，UE专有的CSI-RS，系统消息等信息。进一步地，所述移动控制信息包括切换激活条件信息，例如：当发生无线链路失败时执行切换。进一步地，所述移动控制信息包括时间信息，用于指示该信息的发送周期或者指示该消息的有效时间。
当终端或者IAB检测到自己发生无线链路失败后，可以激活切换流程，包括以下步骤：
步骤4：终端或者IAB根据接收到的移动控制信息，向目标服务节点发送随机接入请求。
步骤4：目标服务节点在接收到终端发起的随机接入信息后，向所述终端的源服务节点发送切换激活指示信息。
步骤5：进一步地，源服务节点接收到目标服务节点发送的切换激活信息后，发送切换激活确认信息。或者，源传输节点接收到目标传输节点发送的切换激活信息后，直接向目标传输节点发送SN(sequence number)状态信息。如果存在未上报成功的数据，则将用户数据转发给目标服务节点。
步骤6，目标服务节点执行后续接入操作，完成切换流程。
实施方式3
实施方式3-1
本实施方式与是实施方式2类似，但区别在于，本实施方式应用于CU,DU分离的场景，由CU(集中管理单元)为每个DU(分布式单元)选择
在终端或者IAB选择接入服务节点后，执行测量并将测量结果上报给服务节点，服务节点将测量结果发送给donor CU，donor CU根据测量结果为终端或者IAB选择候选的目标服务节点。然后开始执行切换准备工作。图11是本公开实施方式的流程示意图三，包括：
步骤1：donor CU向目标DU发送终端或者IAB的上下文建立请求信息，所述上下文建立请求信息包括以下至少之一：原因信息，有效时间信息，周期信息，目标DU的标识信息。
其中，原因信息用于指示所述上下文建立请求原因为一种提前的切换准备请求或者重建准备请求。
有效时间信息用于指示所述上下文建立请求的有效期，当超过所述有效时间后仍然没有执行切换或者重建操作，那么该上下文建立请求信息失效。
周期信息用于指示该上下文建立请求消息发送的周期，当超过所述周期时间后仍然没有执行切换或者重建操作，该上下文建立请求信息失效。
进一步地，CU可以向多个目标DU发送上下文建立请求信息，所述上下文建立请求信息用于请求准备切换资源或者准备重建信息。
步骤2:目标DU在接收到上下文建立请求信息后，向donor CU发送上下文建立请求确认信息。
所述确认信息包括为终端或者IAB分配的C-RNTI,用于执行安全算法的秘钥，专有的RACH资源，进一步地，还可以包括RACH相关的SS block信息，UE或者IAB专有的CSI-RS，系统消息等信息。
步骤3：donor CU在接收到上下文建立请求确认信息后，发送上下文调整请求信息给终端或者IAB的源DU。
步骤4：源DU发送RRC重配信息给终端或者IAB。所述RRC重配信息包括为终端或者IAB分配的C-RNTI,用于执行安全算法的秘钥，专有的RACH资源，进一步地，还可以包括RACH相关的SS block信息，UE专有的CSI-RS，系统消息等信息。进一步地，还包括切换激活条件信息，例如：当发生无线链路失败时执行切换。进一步地，还包括时间信息，用于指示该信息的发送周期或者指示该消息的有效时间。
当源DU检测发现终端或者IAB发生链路中断时，则开始激活切换流程，包括以下步骤：
步骤5：源DU向donor CU发送上下文调整响应信息，所述上下文调整响应信息包括终端或者IAB标识信息，原因信息。所述原因信息指示为切换激活。
步骤6：与步骤5并行的，终端或者IAB检测到自己发生无线链路失败后，可以激活切换流程，根据接收到的RRC重配信息，向目标服务节点发送随机接入请求。
步骤7，目标DU在接收到UE的接入请求后，向donor CU发送RRC重配完成消息。
步骤8-9，donor CU要求源DU释放掉终端或者IAB的上下文信息。
其中，所述终端包括终端节点，终端节点的终端功能部分。
实施方式3-2
基于前面一个实施方式，如果CU为终端或者IAB选择了多个候选的服务IAB节点，当终端或者IAB更换服务节点后，或者当CU重新为终端或者IAB选择新的服务IAB节点后，CU通知原来的服务IAB节点以及候选的服务IAB节点释放掉终端或者IAB的上下文信息。
实施方式3-3
本实施方式与实施方式3-1的区别在于，执行步骤的顺序发生了改变，依次执行步骤1，步骤2，步骤3，当终端检测到发生无线链路失败后，执行步骤6，目标服务DU收到终端或者IAB的随机接入请求后告知CU切换激活，然后CU将切换激活信息发生给源服务DU，源服务DU收到激活信息后，将下行数据状态信息发送给CU，CU再转发给目标服务DU， 目标服务DU执行步骤7,CU执行步骤8,9。切换完成。
实施方式4
针对多连接的场景，考虑以下切换优化方案：
在现有机制中如果因为主服务节点MN突然发生无线链路失败RLF，MN无法与终端通信，正常切换流程无法执行，因此，即使是使用现有的多连接，也无法保证不受到MN RLF的影响。但是相比于单连接的方式，当MN发生RLF时，辅服务节点SN的通信链路还有可能的正常的，那么作为一种缩短时延的增强方式，如果确定将SN变为MN,在切换判决已经做出后，我们提出由SN发出RRC连接重配消息来通知UE。图12是本公开实施方式的流程示意图四。
实施例4
本公开的实施例还提供了一种存储介质，该存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的计算机程序：
S1，接收第一传输节点发送的所述第一传输节点或者第二传输节点的上下文信息；
S2，保存所述上下文信息。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行以下步骤：
S1，接收第一传输节点发送的所述第一传输节点或者第二传输节点的上下文信息；
S2，保存所述上下文信息。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、 改进等，均应包含在本公开的保护范围之内。
工业实用性
本公开适用于通信领域，通过接收和保存第一传输节点或者第二传输节点的上下文信息，在存在传输节点链路中断时，可以使用上下文信息进行链路恢复，避免了重新建立流程，解决了相关技术中链路中断的恢复时延过长的技术问题，满足了服务业务的时延需求。

Claims (30)

  1. 一种信息传输方法，包括：
    第三传输节点接收第一传输节点发送的所述第一传输节点或者第二传输节点的上下文信息；
    所述第三传输节点保存所述上下文信息。
  2. 根据权利要求1所述的方法，其中，所述第一传输节点为集中单元CU，所述第二传输节点为分布式单元DU，所述第三传输节点包括一个或者多个DU时，所述第一传输节点通过F1接口发送所述上下文信息。
  3. 根据权利要求2所述的方法，其中，在第三传输节点接收第一传输节点发送的所述第一传输节点或者第二传输节点的上下文信息之前，所述方法还包括：
    所述第三传输节点通过F1接口发送用于请求获取所述上下文信息的请求消息。
  4. 根据权利要求3所述的方法，其中，所述第三传输节点通过F1接口发送用于请求获取所述上下文信息的消息包括：
    所述第三传输节点在接收到RRC重建请求时，通过F1接口发送所述请求消息。
  5. 根据权利要求2或3所述的方法，其中，所述上下文信息包括：传输节点标识，传输节点的上下文信息。
  6. 根据权利要求5所述的方法，其中，所述上下文信息还包括以下至少之一：
    原因信息，其中，所述原因信息用于指示发送所述上下文信息的原因，其中，所述原因包括以下之一：切换准备，重建准备；
    有效时间信息，其中，所述有效时间信息用于指示上下文信息的有效期；
    周期信息，其中，所述周期信息用于指示上下文信息发送的周期，当超过周期时间后仍然没有执行切换或者重建操作，所述上下文信息失效。
  7. 根据权利要求1所述的方法，其中，在所述第一传输节点发送所述上下文信息之后，所述第一传输节点发送用于释放所述第一传输节点或者第二传输节点的上下文信息的指示信息。
  8. 根据权利要求1所述的方法，其中，在所述第一传输节点，所述第二传输节点，所述第三传输节点为中继节点时，所述上下文信息通过Xn接口进行传输。
  9. 根据权利要求8所述的方法，其中，所述中继节点包括以下至少之一：基站，集成接入回程IAB节点。
  10. 根据权利要求2所述的方法，其中，所述方法还包括：
    在第四传输节点发生链路连接失败时，优先选择与所述第四传输节点的源服务节点拥有相同宿主节点的目标传输节点执行无线资源控制RRC重建流程，其中，所述第四传输节点为终端或者IAB。
  11. 根据权利要求8所述的方法，其中，所述方法还包括：
    在第四传输节点发生链路连接失败时，优先选择拥有所述第四传输节点上下文信息的 目标传输节点执行RRC重建流程，其中，所述第四传输节点为终端或者IAB。
  12. 一种信息传输方法，包括：
    传输节点的目标服务节点接收所述传输节点的源服务节点发送的切换准备请求，其中，所述切换准备请求包括以下至少之一：原因信息，有效时间信息，周期信息，目标传输节点的标识信息；
    所述目标服务节点在接收到切换准备请求信息后，向所述源服务节点发送切换准备确认信息；
    其中，所述原因信息用于指示所述切换准备请求原因为一种提前的切换准备请求或者重建准备请求；所述有效时间信息用于指示所述切换准备请求的有效期；所述周期信息用于指示所述切换准备请求消息发送的周期，当超过周期时间后没有执行切换或者重建操作时，所述切换准备请求失效。
  13. 根据权利要求12所述的方法，其中，所述源服务节点向多个所述目标服务节点发送切换准备请求信息，其中，所述切换准备请求信息用于请求准备切换资源，多个所述目标传输节点的标识信息与多个所述目标服务节点对应。
  14. 根据权利要求12所述的方法，其中，所述源服务节点为以下至少之一：集中单元CU，分布式单元DU,集成接入回程IAB节点，中继，基站；所述目标服务节点为以下至少之一：分布式单元DU,IAB节点，中继，基站。
  15. 根据权利要求14所述的方法，其中，在所述传输节点为IAB节点时，所述源服务节点为所述IAB节点的父节点。
  16. 根据权利要求12所述的方法，其中，所述方法还包括：
    所述目标服务节点在接收到所述切换准备请求后，向所述源服务节点发送切换激活指示信息。
  17. 根据权利要求16所述的方法，其中，在向所述源服务节点发送切换激活指示信息之后，所述方法还包括：
    接收所述源服务节点发送的切换激活确认信息；或者，
    接收所述源服务节点发送的序列号SN状态信息。
  18. 根据权利要求12所述的方法，其中，在所述源服务节点检测到所述服务节点发生链路连接失败后，向所述目标服务节点发送切换激活指示信息。
  19. 根据权利要求12所述的方法，其中，所述源服务节点向所述目标服务节点发送切换准备请求信息后，向所述目标服务节点发送切换取消指示信息，所述切换取消指示信息包括切换取消的原因值，当所述目标服务节点接收到所述切换取消指示信息后，释放掉所述切换取消信息对应的传输节点的上下文信息和/或传输节点的预留资源。
  20. 根据权利要求12所述的方法，其中，所述源服务节点向目标服务节点发送切换准备请求信息后，向所述传输节点发送移动控制信息，其中，所述移动控制信息包括切换激活条件信息，所述切换激活条件信息包括：用于指示所述移动控制信息的发送周期或者指 示该消息的有效时间的时间信息，或者，当发生无线链路失败时执行切换的信息。
  21. 一种信息传输方法，包括：
    传输节点接收所述传输节点的目标服务节点发送的移动控制消息，其中，所述移动控制消息用于指示所述传输节点执行切换；
    所述传输节点接收到所述移动控制消息后，执行切换流程；
    其中，所述传输节点为终端或者IAB。
  22. 根据权利要求21所述的方法，其中，所述目标服务节点为所述传输节点的源服务辅节点。
  23. 一种信息传输方法，包括：
    传输节点接收所述传输节点的源服务节点发送的RRC连接释放消或者RRC连接拒绝消息，其中，所述RRC连接释放消息或者RRC连接拒绝消息包括IAB列表，所述IAB列表包括：IAB的标识信息，IAB连接的宿主IAB的标识信息，公共陆地移动网络PLMN信息；
    在所述传输节点发生链路连接失败时，优先选择所述IAB列表中的IAB节点进行重建。
  24. 一种信息传输装置，包括：
    接收模块，设置为接收第一传输节点发送的所述第一传输节点或者第二传输节点的上下文信息；
    保存模块，设置为保存所述上下文信息。
  25. 一种信息传输装置，应用在传输节点的目标服务节点，包括：
    接收模块，设置为接收所述传输节点的源服务节点发送的切换准备请求，其中，所述切换准备请求包括以下至少之一：原因信息，有效时间信息，周期信息，目标传输节点的标识信息；
    发送模块，设置为在接收到切换准备请求信息后，向所述源服务节点发送切换准备确认信息；
    其中，所述原因信息用于指示所述切换准备请求原因为一种提前的切换准备请求或者重建准备请求；所述有效时间信息用于指示所述切换准备请求的有效期；所述周期信息用于指示所述切换准备请求消息发送的周期，当超过周期时间后没有执行切换或者重建操作时，所述切换准备请求失效。
  26. 根据权利要求25所述的装置，其中，发送模块还设置为：向所述传输节点的源服务节点发送切换激活指示信息，所述接收模块还设置为：接收所述传输节点的源服务节点发送的切换激活指示信息。
  27. 一种信息传输装置，应用在传输节点的目标切换服务节点，其中，包括：
    发送模块，设置为发送所述传输节点的移动控制消息，其中，所述移动控制消息用于指示所述传输节点执行切换，其中，所述传输节点目标切换服务节点为所述传输节点的源 辅服务节点；
    其中，所述传输节点为终端或者IAB。
  28. 一种信息传输装置，应用在传输节点，包括：
    接收模块，设置为接收所述传输节点的源服务节点发送的RRC连接释放消或者RRC连接拒绝消息，其中，所述RRC连接释放消息或者RRC连接拒绝消息包括IAB列表，所述IAB列表包括：IAB的标识信息，IAB连接的宿主IAB的标识信息，公共陆地移动网络PLMN信息；
    处理模块，设置为发生链路连接失败时，优先选择所述IAB列表中的IAB节点进行重建。
  29. 一种存储介质，其中，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至23任一项中所述的方法。
  30. 一种电子装置，包括存储器和处理器，其中，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至23任一项中所述的方法。
PCT/CN2019/088657 2018-06-21 2019-05-27 信息传输方法及装置、存储介质、电子装置 WO2019242460A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US17/254,530 US20210274394A1 (en) 2018-06-21 2019-05-27 Information transmission method and device, storage medium, and electronic device
EP19821651.7A EP3813425B1 (en) 2018-06-21 2019-05-27 Information transmission method and device, storage medium, and electronic device
MX2021000162A MX2021000162A (es) 2018-06-21 2019-05-27 Procedimiento y dispositivo de transmisión de información, medio de almacenamiento y dispositivo electrónico.
EP24155995.4A EP4340451A2 (en) 2018-06-21 2019-05-27 Information transmission method and device, storage medium, and electronic device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810645966.9A CN110636561B (zh) 2018-06-21 2018-06-21 信息传输方法及装置、存储介质、电子装置
CN201810645966.9 2018-06-21

Publications (1)

Publication Number Publication Date
WO2019242460A1 true WO2019242460A1 (zh) 2019-12-26

Family

ID=68966441

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/088657 WO2019242460A1 (zh) 2018-06-21 2019-05-27 信息传输方法及装置、存储介质、电子装置

Country Status (5)

Country Link
US (1) US20210274394A1 (zh)
EP (2) EP4340451A2 (zh)
CN (1) CN110636561B (zh)
MX (1) MX2021000162A (zh)
WO (1) WO2019242460A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022071869A1 (en) * 2020-10-02 2022-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Methods and network nodes for handling communication
CN115004658A (zh) * 2020-01-17 2022-09-02 华为技术有限公司 一种通信方法及装置

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110636644B (zh) * 2018-06-21 2023-03-07 中兴通讯股份有限公司 信息传输方法及装置
FR3085098A1 (fr) * 2018-08-16 2020-02-21 Orange Procede de handover et station de base associee
US11963024B2 (en) * 2019-02-15 2024-04-16 Lg Electronics Inc. Method and apparatus for backhaul status reporting in wireless communication system
US20220141890A1 (en) * 2019-03-26 2022-05-05 Apple Inc. Link Establishment in Relay Nodes
CN113747521B (zh) * 2020-05-29 2023-02-17 维沃移动通信有限公司 网络切换方法、装置、通信设备及系统
CN113766582B (zh) * 2020-06-03 2023-03-14 维沃移动通信有限公司 网络切换方法、装置、通信设备及系统
CN116530142A (zh) * 2020-10-22 2023-08-01 华为技术有限公司 一种用于接入回传一体化iab系统中的通信方法及相关设备
CN114390560A (zh) * 2020-10-22 2022-04-22 大唐移动通信设备有限公司 切换方法、装置及相关设备
JP2024039537A (ja) * 2022-09-09 2024-03-22 キヤノン株式会社 通信ノード装置、通信装置、及び通信システム

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070136564A1 (en) * 2005-12-14 2007-06-14 Intel Corporation Method and apparatus to save and restore context using scan cells
CN102104906A (zh) * 2010-12-31 2011-06-22 大唐移动通信设备有限公司 重建准备信息发送及获取方法、系统和装置
CN102291821A (zh) * 2010-06-18 2011-12-21 电信科学技术研究院 一种恢复rrc连接的方法及中继设备rn
CN102685785A (zh) * 2011-03-18 2012-09-19 华为技术有限公司 无线资源控制rrc连接重建立的方法和设备

Family Cites Families (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE60233255D1 (de) * 2001-12-03 2009-09-17 Nokia Corp Auf richtlinien basierende mechanismen zur auswahl von zugriffs-routern und mobilkontext
CN101005692A (zh) * 2006-01-20 2007-07-25 北京三星通信技术研究有限公司 减少终端在lte和3g接入技术间切换的信令的方法
CN100551157C (zh) * 2006-03-29 2009-10-14 中兴通讯股份有限公司 一种基站切换方法
CN101400088B (zh) * 2007-09-30 2011-04-20 华为技术有限公司 一种演进网络中的切换方法及设备
US8718561B2 (en) * 2007-11-20 2014-05-06 Aruba Networks, Inc. Method and apparatus for detecting and avoiding interference in a communications network
WO2010147974A1 (en) * 2009-06-17 2010-12-23 Interdigital Patent Holdings, Inc. Method and apparatus for performing handover with a relay node
CN101998468B (zh) * 2009-08-21 2015-08-19 北京三星通信技术研究有限公司 一种移动通信系统中自优化的实现方法、系统和基站
EP2387270A1 (en) * 2010-05-12 2011-11-16 Nokia Siemens Networks Oy Radio link failure recovery control in communication network having relay nodes
CN102348191A (zh) * 2010-08-06 2012-02-08 中国移动通信集团公司 一种ue上下文获取方法和设备
CN102404807A (zh) * 2010-09-14 2012-04-04 华为技术有限公司 一种切换准备方法和装置
CN102685817B (zh) * 2011-03-11 2017-04-12 中兴通讯股份有限公司 在中继节点切换过程中不需要重建高层安全的方法和系统
CN102752818B (zh) * 2011-04-18 2016-09-28 中兴通讯股份有限公司 无线中继节点切换的处理方法及系统
CN102752821A (zh) * 2011-04-22 2012-10-24 中兴通讯股份有限公司 小区切换方法、设备及系统
WO2013023171A1 (en) * 2011-08-11 2013-02-14 Interdigital Patent Holdings, Inc. Mobile relay handover
CN102957605B (zh) * 2011-08-24 2017-04-12 中兴通讯股份有限公司 一种切换实现方法、系统和源出口隧道路由器
CN103024838B (zh) * 2011-09-27 2015-09-09 普天信息技术研究院有限公司 一种支持中继节点服务网关重定位的方法
US9258745B2 (en) * 2011-11-11 2016-02-09 Blackberry Limited Method and system for mobile relay enablement
CN103124418A (zh) * 2011-11-18 2013-05-29 华为技术有限公司 上行数据转发方法以及装置
CN103313326A (zh) * 2012-03-13 2013-09-18 北京三星通信技术研究有限公司 一种支持中继切换的方法
CN102711204B (zh) * 2012-03-14 2014-10-22 北京邮电大学 移动中继中基于路径预判的无线链路失败恢复方法
CN103945537A (zh) * 2013-01-18 2014-07-23 中兴通讯股份有限公司 无线资源管理方法、装置及系统
US20150327127A1 (en) * 2013-05-10 2015-11-12 Telefonaktiebolaget L M Ericsson (Publ) Handover Procedures for User Equipment in a Wireless Communication Network
WO2016130062A1 (en) * 2015-02-13 2016-08-18 Telefonaktiebolaget Lm Ericsson (Publ) Early handover preparation in a wireless communication network
CN106034343B (zh) * 2015-03-10 2020-02-18 电信科学技术研究院 一种接入方法及装置
US10009260B2 (en) * 2015-06-30 2018-06-26 Qualcomm Incorporated Management of network routing domains in communication networks
WO2017107073A1 (zh) * 2015-12-22 2017-06-29 华为技术有限公司 数据传输处理方法、用户设备和基站
WO2018057076A1 (en) * 2016-09-26 2018-03-29 Intel Corporation Splitting signal radio bearer enhancements for standalone 5g new rat multi-connectivity
CN108337701B (zh) * 2017-01-19 2021-06-04 工业和信息化部电信研究院 一种传输路径切换方法
WO2019110869A1 (en) * 2017-12-04 2019-06-13 Nokia Technologies Oy Link monitoring with self-backhauling for wireless networks
CN110351024B (zh) * 2018-04-04 2021-06-15 华为技术有限公司 数据传输方法和装置
US20210259051A1 (en) * 2018-05-10 2021-08-19 Samsung Electronics Co., Ltd. Method and apparatus for performing communication in wireless communication system
US11950149B2 (en) * 2020-04-30 2024-04-02 Qualcomm Incorporated Inter-donor cell management in integrated access and backhaul

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070136564A1 (en) * 2005-12-14 2007-06-14 Intel Corporation Method and apparatus to save and restore context using scan cells
CN102291821A (zh) * 2010-06-18 2011-12-21 电信科学技术研究院 一种恢复rrc连接的方法及中继设备rn
CN102104906A (zh) * 2010-12-31 2011-06-22 大唐移动通信设备有限公司 重建准备信息发送及获取方法、系统和装置
CN102685785A (zh) * 2011-03-18 2012-09-19 华为技术有限公司 无线资源控制rrc连接重建立的方法和设备

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115004658A (zh) * 2020-01-17 2022-09-02 华为技术有限公司 一种通信方法及装置
CN115004658B (zh) * 2020-01-17 2024-04-12 华为技术有限公司 一种通信方法及装置
WO2022071869A1 (en) * 2020-10-02 2022-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Methods and network nodes for handling communication

Also Published As

Publication number Publication date
CN110636561B (zh) 2022-11-08
US20210274394A1 (en) 2021-09-02
EP3813425B1 (en) 2024-03-13
EP3813425A1 (en) 2021-04-28
MX2021000162A (es) 2021-03-25
EP4340451A2 (en) 2024-03-20
EP3813425A4 (en) 2022-01-26
CN110636561A (zh) 2019-12-31

Similar Documents

Publication Publication Date Title
WO2019242460A1 (zh) 信息传输方法及装置、存储介质、电子装置
JP6673426B2 (ja) 無線通信システム、方法、ユーザ機器および基地局
RU2752242C1 (ru) Способы, обеспечивающие возможность двойного подключения для избыточных путей плоскости пользователя, и соответствующие сетевые узлы
RU2667379C2 (ru) Способ и система для поддержки быстрого восстановления пользовательского оборудования
JP6651633B2 (ja) データスケジューリング方法、基地局およびシステム
US9961707B2 (en) Terminal multiple connection management method, device and system
WO2020030109A1 (zh) 信息传输方法及装置、存储介质和电子装置
JP2019510436A (ja) リソース構成方法、装置及び記憶媒体
JP7186224B2 (ja) 隣接基地局関係を更新するための方法及び装置
WO2020192603A1 (zh) 链路状态的通知方法及装置、链路的处理方法及装置、存储介质、电子装置
JP6898046B2 (ja) 次世代モバイルコアネットワークにおける拡張型セッション管理のためのシステムおよび方法
WO2020253536A1 (zh) 双连接重建立中数据的处理方法及装置
EP4084573A1 (en) Network connection reestablishment method and device, storage medium, and electronic device
CN111417154A (zh) 多连接中保持终端业务连续性的方法、网络单元
US20230156531A1 (en) Coordinated change of protocol data unit session anchors
WO2016184157A1 (zh) 一种移动通信系统中程序的处理方法和装置
US20220286934A1 (en) Methods for Maintaining an Ongoing Communication Even After Site Outage
CN108093470B (zh) 一种终端与从基站之间上行同步信息的处理方法及装置
CN117692981A (zh) 切换处理方法、装置及通信设备
CN116419339A (zh) 通信方法、装置及系统

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019821651

Country of ref document: EP

Effective date: 20210121