WO2022194074A1 - 自回传网络的切换方法、装置及网络侧设备 - Google Patents

自回传网络的切换方法、装置及网络侧设备 Download PDF

Info

Publication number
WO2022194074A1
WO2022194074A1 PCT/CN2022/080575 CN2022080575W WO2022194074A1 WO 2022194074 A1 WO2022194074 A1 WO 2022194074A1 CN 2022080575 W CN2022080575 W CN 2022080575W WO 2022194074 A1 WO2022194074 A1 WO 2022194074A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
network
handover
information
target
Prior art date
Application number
PCT/CN2022/080575
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 维沃移动通信有限公司
Publication of WO2022194074A1 publication Critical patent/WO2022194074A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0064Transmission or use of information for re-establishing the radio link of control information between different access points
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/08Reselecting an access point
    • H04W36/087Reselecting an access point between radio units of access points

Definitions

  • the present invention requires the priority of the Chinese patent application filed on March 17, 2021 with the application number 202110286829.2 and the invention title "Switching method, device and network side equipment for self-backhaul network”. The contents are incorporated herein by reference.
  • the present application belongs to the technical field of wireless communication, and in particular relates to a handover method, device and network side equipment for a self-backhaul network.
  • IAB Integrated Access Backhaul
  • UE which may also be referred to as terminal equipment
  • IAB node IAB node
  • Data is transmitted between the UE and the access node through a wireless access link (access link), and data can be transmitted between the access nodes through a wireless backhaul link (backhaul link).
  • the support centralized unit (Central Unit, CU) node of its IAB network is located in the host (donor) IAB node, called IAB-donor-CU, all directly connected to the donor IAB node Or connecting to the donor IAB node through the downstream IAB node of the donor IAB node belongs to the control of the IAB-donor-CU. That is to say, an IAB node and its downstream nodes (IAB/UE) are all controlled by the IAB-donor-CU of the IAB node, that is, the context information of the mobile IAB network is all in the IAB-donor-CU.
  • the mobile user and the mobile IAB node move together, and the IAB-donor-CU node is fixed.
  • the high-speed train crosses the coverage area of a CU node
  • the mobile IAB node and its downstream nodes (such as IAB node/UE node) deployed on the train need to switch from the original IAB-donor-CU node to the target IAB-donor-CU node.
  • the context information of the mobile IAB node and its downstream nodes also needs to be sent from the original IAB-donor-CU node to the target IAB-donor-CU node, so that the target IAB-donor-CU node can be based on the mobile IAB node and its downstream nodes.
  • the context information generates a reconfiguration message and sends it to the mobile IAB node and its downstream nodes through the original IAB-donor-CU node, which means that there is a large amount of signaling to be transmitted, resulting in the occurrence of signaling storms and the increase of handover delay. big.
  • the embodiments of the present application provide a method, an apparatus, and a network-side device for switching a self-backhaul network, which can solve the problems of signaling storms and large switching delays that may occur during IAB network switching.
  • a method for switching a self-backhaul network is provided, which is performed by an original CU node.
  • the method includes: in the case of triggering switching, sending a second network switching request to a target CU node, the second network switching
  • the handover request includes at least context information of the first network node, the context information is the context information of the first network node when the handover is triggered, and is relative to the context of the first network node included in the first network handover request At least part of the information that the information has changed, the first network handover request is sent by the original CU node to the target CU node before the handover is triggered, and the first network node is any IAB network to be handed over.
  • a network node receiving a second network handover response sent by the target CU node, where the second network handover response at least includes second reconfiguration information, and the second reconfiguration information is configured by the target CU node according to the A second network handover request is generated; the handover of the first network node from the original CU node to the target CU node is configured based on the first reconfiguration information and the second reconfiguration information, and the first reconfiguration information is in the Before the handover is triggered, it is generated by the target CU node according to the first network handover request.
  • a method for switching a self-backhaul network executed by a target CU node, the method includes: receiving a second network switching request sent by an original CU node when switching is triggered, the second network switching request It includes at least the context information of the first network node, and the context information is the context information of the first network node when the handover is triggered, which occurs with respect to the context information of the first network node included in the first network handover request.
  • the first network handover request is sent by the original CU node to the target CU node before the handover is triggered, and the first network node is any network in the IAB network to be handed over node; sending a second network handover response to the original CU node, where the second network handover response includes second reconfiguration information, and the second reconfiguration information is requested by the target CU node according to the second network handover request generate.
  • a switching device for a self-backhaul network includes: a first sending module, configured to send a second network switching request to a target CU node in the case of triggering switching, the second sending module
  • the network handover request includes at least the context information of the first network node, the context information is the context information of the first network node when the handover is triggered, and is relative to the first network node included in the first network handover request.
  • the first network handover request is sent by the original CU node to the target CU node before the handover is triggered, and the first network node is any one of the IAB networks to be handed over a network node; a first receiving module configured to receive a second network handover response sent by the target CU node, where the second network handover response at least includes second reconfiguration information, and the second reconfiguration information is sent by the The target CU node is generated according to the second network handover request; a configuration module is configured to configure the first network node from the original CU node to the target CU node based on the first reconfiguration information and the second reconfiguration information. handover, the first reconfiguration information is generated by the target CU node according to the first network handover request before handover is triggered.
  • a switching device for a self-backhaul network includes: a first sending module, configured to send a second network switching request to a target CU node in the case of triggering switching, the second sending module
  • the network handover request includes at least the context information of the first network node, the context information is the context information of the first network node when the handover is triggered, and is relative to the first network node included in the first network handover request.
  • the first network handover request is sent by the original CU node to the target CU node before the handover is triggered, and the first network node is any one of the IAB networks to be handed over a network node; a first receiving module configured to receive a second network handover response sent by the target CU node, where the second network handover response at least includes second reconfiguration information, and the second reconfiguration information is sent by the The target CU node is generated according to the second network handover request; a configuration module is configured to configure the first network node from the original CU node to the target CU node based on the first reconfiguration information and the second reconfiguration information. handover, the first reconfiguration information is generated by the target CU node according to the first network handover request before handover is triggered.
  • a network-side device in a fifth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the The processor implements the steps of the method as described in the first aspect or the second aspect when executed.
  • a network side device including a processor and a communication interface, wherein the processor and the communication interface are used to implement the steps of the method according to the first aspect or the second aspect.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect, or the The steps of the method of the second aspect.
  • a chip in an eighth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction, and implements the method described in the first aspect. the method described, or implement the method described in the second aspect.
  • a computer program product comprising a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the
  • the processor implements the steps of the method as described in the first aspect or the second aspect when executed.
  • the original CU node before the handover is triggered, the original CU node obtains the first reconfiguration information through the first network handover request, so that when the handover is triggered, only the context information is obtained through the second network handover request In this way, the amount of signaling that needs to be transmitted after the handover is triggered can be greatly reduced, thereby avoiding the occurrence of signaling storms, and at the same time, it can also shorten the handover caused by the need to obtain reconfiguration information. delay to ensure network switching performance.
  • FIG. 1 is a schematic structural diagram of a wireless communication system provided by an exemplary embodiment of the present application.
  • FIG. 2a is a schematic structural diagram of a mobile IAB system provided by an exemplary embodiment of the present application.
  • FIG. 2b is a schematic structural diagram of an IAB network to be handed over according to an exemplary embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a method 300 for switching a self-backhaul network according to an exemplary embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a method 400 for switching a self-backhaul network according to an exemplary embodiment of the present application.
  • FIG. 5 is a schematic diagram of an interaction flow of a method 500 for switching a self-backhaul network provided by an exemplary embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a method 600 for switching a self-backhaul network provided by an exemplary embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a switching apparatus 700 of a self-backhaul network provided by an exemplary embodiment of the present application.
  • FIG. 8 is a schematic block structural diagram of a switching apparatus 800 of a self-backhaul network provided by an exemplary embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a network side device provided by an exemplary embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • 6G 6th Generation
  • FIG. 1 shows a schematic diagram of a result of a wireless communication system to which an embodiment of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12.
  • the terminal 11 may also be called a terminal device or a user terminal, and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted equipment (VUE), pedestrian terminal (PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Send Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms.
  • the base station in the NR system is taken as an example, but the specific type of the base station is not limited.
  • the UE may include, but is not limited to, a mobile station (Mobile Station, MS), a mobile terminal (Mobile Terminal), a mobile phone (Mobile Phone), a mobile phone (handset), a portable device (portable equipment), a vehicle ( vehicle), etc.
  • the UE can communicate with one or more core networks via a radio access network (Radio Access Network, RAN), for example, the UE can provide radio access services by an IAB network node.
  • RAN Radio Access Network
  • the UE may be a mobile phone (or referred to as a "cellular" phone), a computer with wireless communication functions, etc.
  • the terminal device may also be a portable, pocket-sized, hand-held, computer-built or vehicle-mounted mobile device.
  • FIG. 2 a is a CU-DU structural diagram of a mobile IAB system provided by an embodiment of the present application.
  • the DUs in the most upstream IAB network node in the IAB network are all connected to a CU network, and the CU network can pass through F1-
  • the AP protocol configures the DU, and the MT is configured through the Radio Resource Control (Radio Resource Control, RRC) protocol.
  • RRC Radio Resource Control
  • a self-backhaul link also includes a host (Donor) IAB network node (or called IAB Donor), the Donor IAB network node does not have the MT function part, but the Donor IAB network node has a wired transmission network directly connected to it. .
  • Donor IAB network node
  • the Donor IAB network node does not have the MT function part, but the Donor IAB network node has a wired transmission network directly connected to it.
  • the IAB network 1 may include a plurality of IAB network nodes (such as IAB1, IAB2, IAB3...) shown in Fig. 2b, and UEs (UE1, UE2... shown in Fig.
  • network node IAB1 is an IAB
  • network node IAB2 is the parent IAB network node of its adjacent downstream network node IAB3..., in other words , the network node IAB2 is a sub-IAB network node of its adjacent upstream network node IAB1, and the network node IAB3 is a sub-IAB network node of its adjacent downstream network node IAB2.
  • one IAB network node may provide network access services for one or more UEs.
  • FIG. 3 it is a schematic flowchart of a method 300 for switching a self-backhaul network provided by an exemplary embodiment of the present application.
  • the method 300 may be executed by the original CU node, and specifically may be installed in the original CU node. Software and/or hardware implementation.
  • the method 300 includes at least the following steps.
  • S310 In the case of triggering the handover, send a second network handover request to the target CU node.
  • the second network handover request includes at least context information of the first network node
  • the context information is the context information of the first network node when the handover is triggered, relative to the context information included in the first network handover request at least part of the information that the context information of the first network node has changed
  • the first network handover request is sent by the original CU node to the target CU node before the handover is triggered, and the first network node is to be Any network node in the IAB network to be handed over, such as an IAB node or a UE served by an IAB node.
  • the context information of the first network node may be different.
  • the context information includes the IAB-MT The context information and/or the context information of the F1 connection of the IAB-DU; for another example, when the first network node is a UE, the context information of the RRC connection.
  • the first network handover request (that is, the early handover request) is sent by the original CU node to the target CU node before the handover is triggered, so as to obtain in advance the information of each network in the IAB network to be handed over before the handover is triggered.
  • the reconfiguration information of the network node thus, in the case of triggering handover, the original CU node can obtain a small amount of reconfiguration information by sending a second network handover request (ie, a later handover request), such as context information relative to the first
  • a second network handover request ie, a later handover request
  • the predetermined time interval and/or the actual sending time point of the first network handover request before the handover is triggered may be configured through high-level signaling configuration or protocol agreement, or configured by the OAM system, which is not covered in this embodiment. make restrictions.
  • S320 Receive a second network switching response sent by the target CU node.
  • the second network handover response includes at least second reconfiguration information
  • the second reconfiguration information is used by the target CU node according to the second A network handover request is generated.
  • the target CU node since the second network handover request includes the context information of the first network node or the changed part of the context information, in response, the target CU node sends the second network handover response to the original CU node
  • the handover reconfiguration information or the changed part of the handover reconfiguration information corresponding to the context information or the changed part of the context information may also be included.
  • the second reconfiguration information includes radio resource control (Radio Resource Control, RRC) reconfiguration information; when the second network node is an IAB node
  • RRC Radio Resource Control
  • the second reconfiguration information includes the RRC reconfiguration information of the IAB-MT and/or the F1 connection reconfiguration message of the IAB-DU.
  • the second network handover request may include indication information for indicating that it is a later handover request, and the indication information may be configured by a high layer or agreed in a protocol, which is not limited.
  • S330 Configure the handover of the first network node from the original CU node to the target CU node based on the first reconfiguration information and the second reconfiguration information.
  • the first reconfiguration information is generated by the target CU node according to the first network handover request before handover is triggered.
  • the first reconfiguration information may include RRC reconfiguration information; when the second network node is an IAB node
  • the first reconfiguration information may include the RRC reconfiguration information of the IAB-MT and/or the F1 connection reconfiguration message of the IAB-DU.
  • the original CU node sends the IAB network 1 to be handed over (including IAB1, IAB2, IAB3, The context information of UE1, UE2, .
  • the context information of the IAB1 node in the IAB network 1 is relative to the context of the IAB1 node (that is, the aforementioned first network node) included in the first network handover request.
  • the original CU node can send the changed context information in the IAB1 node to the target CU node through the second network handover request again, so as to obtain the corresponding second reconfiguration information, and then based on the second network handover request.
  • the first reconfiguration information configures and the second reconfiguration information configures the handover of the IAB1 node, and configures the handover of other network nodes except the IAB1 node in the IAB network 1 based on the first reconfiguration information, Therefore, after the handover is triggered, the amount of signaling that needs to be transmitted after the handover is triggered can be greatly reduced, thereby avoiding the occurrence of signaling storms, and shortening the handover delay caused by the need to obtain reconfiguration information, ensuring network handover performance.
  • FIG. 4 it is a schematic flowchart of a method 400 for switching a self-backhaul network provided by an exemplary embodiment of the present application.
  • the method 400 may be executed by the original CU node, and specifically may be installed in the original CU node.
  • the method 300 includes at least the following steps.
  • the first network handover request includes at least the context information of the first network node when the original CU node sends the first network handover request. It can be understood that when the IAB network to be switched includes multiple network nodes, the first network switching request may include context information of the multiple network nodes.
  • the first network handover request may further include first information for indicating to the target CU node that the first network handover request is an early handover request.
  • the first network handover request may use a new RRC IE, or reuse an existing handover request IE, such as adding an indication field (that is, an indication field) to the existing handover request IE. first information) to indicate that the target CU node does not need to reserve resources for these nodes to be switched immediately, so as to avoid resource waste.
  • the first information may include a handover occurrence place and/or a handover occurrence time point, wherein the handover occurrence place and/or the handover occurrence time point are the predetermined movement of the original CU node according to the mobile IAB system Routes, movement speeds, and deployment information for alternative IAB hosts are predicted.
  • the predetermined moving route, moving speed, and deployment information of the alternative IAB host of the mobile IAB system may be a protocol agreement or a configuration through high-level signaling, etc., which is not limited herein.
  • S420 Receive a first network switching response sent by the target CU node.
  • the first network handover response is generated by the target CU node according to the first network handover request, that is, the first reconfiguration information included in the first network handover response is generated by the target CU
  • the node is generated according to the context information included in the first network handover request.
  • the first network handover response may also include second information, where the second information is used to indicate that the first network handover response is an early handover response.
  • second information is used to indicate that the first network handover response is an early handover response.
  • a new RRC IE may be used for the second network handover response, or an existing handover request response IE may be reused, such as adding an indication field (that is, the second information) to the existing handover request IE. , to indicate that this is an early handover request response.
  • S430 in the case of triggering the handover, send a second network handover request to the target CU node.
  • the second network handover request includes at least context information of the first network node
  • the context information is the context information of the first network node when the handover is triggered, relative to the context information included in the first network handover request at least part of the information that the context information of the first network node has changed
  • the first network handover request is sent by the original CU node to the target CU node before the handover is triggered, and the first network node is to be Any network node in the switched IAB network.
  • S440 Receive a second network switching response sent by the target CU node.
  • the second network handover response includes at least second reconfiguration information
  • the second reconfiguration information is generated by the target CU node according to the second network handover request.
  • S450 Configure the handover of the first network node from the original CU node to the target CU node based on the first reconfiguration information and the second reconfiguration information.
  • the first reconfiguration information is generated by the target CU node according to the first network handover request before handover is triggered.
  • the first reconfiguration information described in S450 is based on the first reconfiguration information.
  • the second reconfiguration information, configuring the handover of the first network node from the original CU node to the target CU node may include at least one of the following (1)-(2).
  • the original CU node sends a handover trigger notification to the target CU node, where the handover trigger notification is used to notify the target CU node of the node information of the first network node.
  • the handover trigger notification may include a list of handover node identifiers to indicate that the node corresponding to the handover node identifier is a node to be handed over (eg, a first network node).
  • the original CU node sends a handover trigger notification to the target CU node, where the handover trigger notification is used to notify the target CU node that the handover of the first network node is about to occur.
  • the original CU node can simultaneously indicate to the target CU node the node information of the first network node and that the handover of the first network node is about to take place through one of the handover trigger notifications, or it can be
  • the two handover trigger notifications respectively indicate to the target CU node the node information of the first network node and the handover of the first network node, which is not limited.
  • the target CU node can configure resources for the node to be handed over (such as the first network node), and send determination information to the original CU node, the original CU node
  • the node sends the target reconfiguration information to the first network node, so that the timing of handover can be controlled without affecting the UE, ensuring user communication experience.
  • the target reconfiguration information is obtained by replacing or updating the first reconfiguration information by using the second reconfiguration information. That is, if the second network handover response received by the original CU node (that is, the post-handover response message of a node) contains all the reconfiguration parameter settings of the first network node, the second reconfiguration information is directly used.
  • the original CU node that is, a The post-handover response message of the node only contains the reconfiguration parameter settings of the part corresponding to the changed context information, then the original CU will replace the second reconfiguration information (ie post-reconfiguration message) corresponding to the first network node
  • the first reconfiguration information (that is, the previous reconfiguration message) is combined and sent to the first network node as the target reconfiguration information, so as to replace the first reconfiguration information cached earlier.
  • the IAB node stores the received target reconfiguration information, And after the handover is triggered, the stored target reconfiguration information is sent to the UE served by it; or, the IAB node stores the received target reconfiguration information, and sends the target reconfiguration information to the UE served by it.
  • Each of the UEs stores their own reconfiguration information. Therefore, by pre-buffering their own reconfiguration information, each network node can make the switch directly based on the cached reconfiguration information when receiving a trigger notification, thereby Significantly shorten the switching delay.
  • the handover can be sent. sending start notification information to the first network node, where the handover start notification information is used to instruct the first network node to perform handover according to the cached target reconfiguration information, and correspondingly, the first network node receives the handover start
  • the switch is initiated by pressing the switch start notification information.
  • the handover start notification information may be transmitted through F1 signaling, RRC signaling or BAP Control PDU signaling.
  • the context information of the first network node is relative to the first network node.
  • the context information of the first network node included in the network handover request has not changed, then, in the case of triggering the handover, the original CU node can directly configure the first network node from the first reconfiguration information based on the first reconfiguration information. Switching from the original CU node to the target CU node.
  • the original CU node sends a handover trigger notification to the target CU node to notify the target CU node of the node information for notifying the first network node, and/or to the target CU node
  • the target CU node notifies the first network node that the handover is about to take place, and in the case of receiving the confirmation information fed back by the target CU node, sends the first reconfiguration information to the first network node for caching, and/ Or the first network node forwards it to the UE served by it, etc., so that the first network node and/or the UE served by it can perform handover based on the reconfiguration information cached respectively, thereby avoiding the handover process.
  • Obtaining reconfiguration information in the case of triggering can greatly reduce the amount of signaling that needs to be transmitted after triggering the handover, thereby avoiding the occurrence of signaling storms, shortening the handover delay caused by the need to obtain reconfiguration information, and ensuring network handover performance .
  • the original CU node when the original CU node sends the first reconfiguration information to the first network node, it may be before the handover is triggered, or it may be when it is determined that the context information of the first network node has not changed. It may be when the confirmation information sent by the target CU node is received, which is not limited here.
  • the absolute relationship between the original CU node and the target CU node is Most of the signaling (such as Xn interface signaling, etc.) interaction is completed before the handover is triggered, and there is a large timing advance. In this case, if the handover is triggered, the original CU node only needs to be handed over.
  • the context in the IAB network All or part of the configuration parameters of the node whose information has changed is updated to the handover preparation process again, thereby greatly reducing the impact of signaling storms caused by fast handover.
  • the handover process is always under the control of the network, so as to achieve large-scale handover under the circumstance of avoiding handover storms.
  • the IAB network node to be handed over includes a plurality of first
  • the scale switching of multiple first network nodes is simultaneously realized.
  • the original CU node predicts whether the IAB network handover needs to be performed according to the predetermined moving route, moving speed of the mobile IAB system and deployment information of the candidate IAB host.
  • the original CU node sends the first network handover request to the target CU node.
  • the target CU node sends a first network switching response to the original CU node.
  • the target CU node sends a second network switching response to the original CU node.
  • the original CU node sends a handover trigger notification to the target CU node.
  • the target CU node configures resources for the node to be switched, and feeds back confirmation information to the original CU node.
  • the target reconfiguration information sent by the original CU node is IAB node 1
  • the first reconfiguration information sent by the original CU node is IAB node 1
  • the context A node whose information is changed relative to the context information of the IAB node 1 included in the first network handover request
  • the IAB node 2 indicates that after the handover is triggered
  • the context information is relative to the context of the IAB node 2 included in the first network handover request. Nodes whose information has not changed.
  • the IAB node 1 caches the received target reconfiguration information, and/or the IAB node 2 caches the received first reconfiguration information.
  • the IAB node 1 caches the received target reconfiguration information, and/or the IAB node 2 caches the received first reconfiguration information.
  • the target reconfiguration information received by the IAB node 1 is sent to the UE1 served by the IAB node 1, and/or the IAB node 2 sends the received first reconfiguration information to the UE2 served by the IAB node 2.
  • the original CU node sends the handover start notification information to the IAB node 1 and the IAB node 2.
  • the IAB node 1 and the IAB node 2 perform handover based on the cached reconfiguration information.
  • FIG. 6 it is a schematic flowchart of a method 600 for switching a self-backhaul network provided by an exemplary embodiment of the present application.
  • the method 600 can be executed by a target CU node, and specifically can be installed in the target CU node.
  • the method 600 includes at least the following steps.
  • S610 Receive a second network handover request sent by the original CU node when the handover is triggered, where the second network handover request at least includes context information of the first network node, where the context information is the first network when the handover is triggered The context information of the node, relative to at least part of the information that the context information of the first network node included in the first network handover request has changed, the first network handover request is sent by the original CU node before the handover is triggered. sent to the target CU node, where the first network node is any network node in the IAB network to be switched;
  • S620 Send a second network handover response to the original CU node, where the second network handover response includes second reconfiguration information, and the second reconfiguration information is requested by the target CU node according to the second network handover request generate.
  • the target CU node before the handover is triggered, the target CU node generates the first reconfiguration information according to the received first network handover request, and sends it to the original CU node, so that in the case of the handover trigger, it only needs to be based on the received first reconfiguration information.
  • the received second network handover request generates second reconfiguration information and sends it to the source CU node, wherein at least the context information of the first network node included in the second network handover request is the first network node when the handover is triggered.
  • At least part of the information that the context information of the node is changed relative to the context information of the first network node included in the first network handover request thereby greatly reducing the amount of signaling that needs to be transmitted after triggering the handover, thereby avoiding signaling
  • the occurrence of storms, and the shortening of the handover delay caused by the need to obtain reconfiguration information ensure the network handover performance.
  • the method further includes at least one of the following (1)-(2).
  • the method further includes: in the case of receiving the handover trigger notification, feeding back confirmation information to the original CU node, and/or configuring network switching resources corresponding to the first network node.
  • the method before receiving the second network switching request sent by the original CU node, the method further includes: receiving a first network switching request sent by the original CU node, where the first network switching request is Sent by the original CU node when it is predicted that the IAB network handover needs to be performed, the first network handover request at least includes the first network handover request when the original CU node sends the first network handover request.
  • Context information of the network node send a first network handover response to the original CU node, where the first network handover response includes first reconfiguration information, and the first reconfiguration information is sent by the The target CU node is generated according to the first network handover request.
  • the first network handover request further includes first information, which is used to indicate that the first network handover request is an early handover request; and/or the first network handover response further includes Including second information, the second information is used to indicate that the first network handover response is an early handover response.
  • the first information includes a handover occurrence place and/or a handover occurrence time point, wherein the handover occurrence place and/or the handover occurrence time point are the original CU node according to the mobile IAB system
  • the predetermined moving route, moving speed, and deployment information of candidate IAB hosts are predicted.
  • the first reconfiguration information and the second reconfiguration information include RRC reconfiguration information; in the second network node
  • the first reconfiguration information and the second reconfiguration information include the RRC reconfiguration information of the IAB-MT and/or the F1 connection reconfiguration message of the IAB-DU.
  • the execution subject may be a self-backhaul network switching device, or, in the self-backhaul network switching device, the The control modules of the switching methods 300-600 of the self-backhaul network.
  • the switching device of the self-backhaul network provided by the embodiment of the present application is described by taking the self-backhaul network handover method 300 - 600 as an example for executing the self-backhaul network handover method.
  • an apparatus 700 for switching a self-backhaul network includes: a first sending module 710, configured to send a first sending module 710 when switching is triggered.
  • Two network handover requests are sent to the target CU node, the second network handover request includes at least the context information of the first network node, and the context information is the context information of the first network node when the handover is triggered.
  • At least part of the information about the changed context information of the first network node included in the network handover request where the first network handover request is sent by the original CU node to the target CU node before the handover is triggered, and the first network handover request is sent to the target CU node by the original CU node.
  • a network node is any network node in the IAB network to be handed over; the first receiving module 720 is configured to receive a second network handover response sent by the target CU node, where the second network handover response at least includes a second network handover response.
  • the second reconfiguration information is generated by the target CU node according to the second network handover request; a configuration module 730, configured to configure the reconfiguration information based on the first reconfiguration information and the second reconfiguration information In the handover of the first network node from the original CU node to the target CU node, the first reconfiguration information is generated by the target CU node according to the first network handover request before the handover is triggered.
  • the configuration module 730 is configured to at least one of the following: send a handover trigger notification to the target CU node, where the handover trigger notification is used to notify the target CU node of the first network Node information of the node; sending a handover trigger notification to the target CU node, where the handover trigger notification is used to notify the target CU node that the handover of the first network node is about to occur.
  • the first sending module 710 is further configured to send target reconfiguration information to the first network node in the case of receiving the confirmation information fed back by the target CU node, the target reconfiguration information
  • the configuration information is obtained by replacing or updating the first reconfiguration information with the second reconfiguration information.
  • the configuration module 730 is further configured to configure the first network node from the original CU node to the target CU node based on the first reconfiguration information when a handover is triggered switch.
  • the first sending module 710 is further configured to send handover initiation notification information to the first network node, where the handover initiation notification information is used to instruct the first network node to follow the cached The target reconfiguration information and/or the first reconfiguration information is switched.
  • the handover initiation notification information is transmitted through F1 signaling, RRC signaling or BAP Control PDU signaling.
  • the first sending module 710 is further configured to send the first network handover request to the target CU node when it is predicted that the IAB network handover needs to be performed, and the The first network handover request at least includes the context information of the first network node when the original CU node sends the first network handover request; the first receiving module 720 is further configured to receive a message sent by the target CU node The first network handover response includes the first reconfiguration information.
  • the first network handover request further includes first information, which is used to indicate that the first network handover request is an early handover request; and/or the first network handover response further includes Including second information, the second information is used to indicate that the first network handover response is an early handover response.
  • the first information includes a handover occurrence place and/or a handover occurrence time point, wherein the handover occurrence place and/or the handover occurrence time point are the original CU node according to the mobile IAB system
  • the predetermined moving route, moving speed, and deployment information of candidate IAB hosts are predicted.
  • the first reconfiguration information and the second reconfiguration information include RRC reconfiguration information; in the second network node
  • the first reconfiguration information and the second reconfiguration information include the RRC reconfiguration information of the IAB-MT and/or the F1 connection reconfiguration message of the IAB-DU.
  • the apparatus 800 includes: a second receiving module 810, configured to receive a trigger when the original CU node is triggered A second network handover request sent during handover, the second network handover request at least includes context information of the first network node, and the context information is the context information of the first network node when the handover is triggered, relative to the first network node.
  • a network handover request includes at least part of the changed context information of the first network node, the first network handover request is sent by the original CU node to the target CU node before handover is triggered, and the first network handover request is sent by the original CU node to the target CU node.
  • the first network node is any network node in the IAB network to be handed over;
  • the second sending module 820 is configured to send a second network handover response to the original CU node, where the second network handover response includes a second reconfiguration information, the second reconfiguration information is generated by the target CU node according to the second network handover request.
  • the second receiving module 810 is further configured to at least one of the following: receive a handover trigger notification sent by the original CU node, where the handover trigger notification is used to notify the target CU node of all node information of the first network node; receiving a handover trigger notification sent by the original CU node, where the handover trigger notification is used to notify the target CU node that the handover of the first network node is about to occur.
  • the second sending module 820 is further configured to, in the case of receiving the handover trigger notification, feed back confirmation information to the original CU node, and/or configure the same as the first CU node.
  • the second receiving module 810 is further configured to receive a first network handover request sent by the original CU node, where the first network handover request is when the original CU node predicts the need for Sent when the IAB network handover is performed, the first network handover request includes at least the context information of the first network node when the original CU node sends the first network handover request; the first network handover request
  • the second sending module 820 is further configured to send a first network handover response to the original CU node, where the first network handover response includes first reconfiguration information, and the first reconfiguration information is sent by The target CU node is generated according to the first network handover request.
  • the first network handover request further includes first information, which is used to indicate that the first network handover request is an early handover request; and/or the first network handover response further includes Including second information, the second information is used to indicate that the first network handover response is an early handover response.
  • the first information includes a handover occurrence place and/or a handover occurrence time point, wherein the handover occurrence place and/or the handover occurrence time point are the original CU node according to the mobile IAB system
  • the predetermined moving route, moving speed, and deployment information of candidate IAB hosts are predicted.
  • the first reconfiguration information and the second reconfiguration information include RRC reconfiguration information; in the second network node
  • the first reconfiguration information and the second reconfiguration information include the RRC reconfiguration information of the IAB-MT and/or the F1 connection reconfiguration message of the IAB-DU.
  • the switching apparatus 700 or 800 of the self-backhaul network in this embodiment of the present application may be an apparatus, an apparatus having an operating system or an electronic device, or may be a component, an integrated circuit, or a chip in a terminal.
  • the apparatus or electronic device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the switching device 700 or 800 of the self-backhaul network provided in the embodiment of the present application can implement each process implemented by the method embodiments in FIG. 3 to FIG. 6 and achieve the same technical effect. To avoid repetition, details are not described here.
  • An embodiment of the present application further provides a network side device, including a processor and a communication interface, where the processor is configured to implement the steps in the foregoing method embodiments 300-600.
  • This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment, and each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
  • the network device 900 includes: an antenna 901 , a radio frequency device 902 , and a baseband device 903 .
  • the antenna 901 is connected to the radio frequency device 902 .
  • the radio frequency device 902 receives information through the antenna 901, and sends the received information to the baseband device 903 for processing.
  • the baseband device 903 processes the information to be sent and sends it to the radio frequency device 902
  • the radio frequency device 902 processes the received information and sends it out through the antenna 901 .
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 903 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 903 .
  • the baseband apparatus 903 includes a processor 904 and a memory 905 .
  • the baseband device 903 may include, for example, at least one baseband board on which multiple chips are arranged. As shown in FIG. 9 , one of the chips is, for example, the processor 904 and is connected to the memory 905 to call the program in the memory 905 to execute The network devices shown in the above method embodiments operate.
  • the baseband device 903 may further include a network interface 906 for exchanging information with the radio frequency device 902, and the interface is, for example, a common public radio interface (CPRI for short).
  • CPRI common public radio interface
  • the network-side device in the embodiment of the present invention further includes: an instruction or program stored in the memory 905 and executable on the processor 904, and the processor 904 invokes the instruction or program in the memory 905 to execute the instruction or program shown in FIG. 7 or FIG. 8 . In order to avoid repetition, it is not repeated here.
  • An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the above-mentioned embodiment of the method for switching a self-backhaul network is implemented, And can achieve the same technical effect, in order to avoid repetition, it is not repeated here.
  • the processor is the processor in the terminal described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the above self-backhaul network switching
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is configured to run a program or an instruction to implement the above self-backhaul network switching
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • the embodiments of the present application also provide a computer program product, the computer program product includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being When the processor is executed, each process of the above-mentioned embodiment of the switching method for a self-backhaul network can be realized, and the same technical effect can be achieved. In order to avoid repetition, details are not repeated here.

Landscapes

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

Abstract

本申请公开了一种自回传网络的切换方法、装置及网络侧设备,属于无线通信领域。本申请实施例的自回传网络的切换方法包括:在触发切换的情况下,原CU节点发送至少包括第一网络节点的上下文信息的第二网络切换请求给目标CU节点,上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,第一网络切换请求是在触发切换之前,由原CU节点发送给目标CU节点;接收目标CU节点发送的第二网络切换响应,第二网络切换响应中至少包括第二重配置信息;基于第一重配置信息和第二重配置信息配置第一网络节点从原CU节点到目标CU节点的切换。

Description

自回传网络的切换方法、装置及网络侧设备
交叉引用
本发明要求在2021年3月17日提交中国专利局、申请号为202110286829.2、发明名称为“自回传网络的切换方法、装置及网络侧设备”的中国专利申请的优先权,该申请的全部内容通过引用结合在本发明中。
技术领域
本申请属于无线通信技术领域,具体涉及一种自回传网络的切换方法、装置及网络侧设备。
背景技术
在新空口(New Radio,NR)系统中,接入回传一体化(Integrated Access Backhaul,IAB)可以为NR小区提供扩展覆盖,也可以为NR小区提供容量增强,其中,支持用户设备(User Equipment,UE,也可称之为终端设备)的无线接入并且将数据进行无线回传的接入节点称为IAB节点(IAB node,IABN)。UE和接入节点之间通过无线接入链路(access link)传输数据,接入节点之间可通过无线回传链路(backhaul link)传输数据。
其中,对于移动IAB系统(Mobile IAB System),其IAB网络的支持集中式单元(Central Unit,CU)节点位于宿主(donor)IAB节点,称为IAB-donor-CU,所有直接连接到donor IAB节点或通过该donor IAB节点的下游IAB节点连接到该donor IAB节点均属于该IAB-donor-CU控制。就是说,一个IAB节点及其下游的节点(IAB/UE)均受该IAB节点的IAB-donor-CU 控制,即移动IAB网络的上下文(context)信息均在IAB-donor-CU中。
在此情况下,以高速移动场景为例,如果IAB节点部署在高速列车上,移动用户与移动IAB节点伴随移动,而IAB-donor-CU节点是固定的,一旦高速列车穿越一个CU节点覆盖区域边界到达另外一个CU节点覆盖区域,那么部署在该列车上的移动IAB节点及其下游节点(如IAB节点/UE节点)均需要从原IAB-donor-CU节点切换到目标IAB-donor-CU节点,同时移动IAB节点及其下游节点的上下文信息也需要从原IAB-donor-CU节点发送给目标IAB-donor-CU节点,使得目标IAB-donor-CU节点能够基于移动IAB节点及其下游节点的上下文信息生成重配置消息,并经原IAB-donor-CU节点发送给移动IAB节点及其下游节点,而这意味着存在大量的信令需要传输,导致信令风暴的出现以及切换时延的增大。
发明内容
本申请实施例提供一种自回传网络的切换方法、装置及网络侧设备,能够解决IAB网络切换时可能出现的信令风暴以及切换时延大的问题。
第一方面,提供了一种自回传网络的切换方法,由原CU节点执行,所述方法包括:在触发切换的情况下,发送第二网络切换请求给目标CU节点,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由所述原CU节点发送给所述目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点;接收所述目标CU节点发送的第二网络切换响应,所述第二网络切换响应中至少包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第 二网络切换请求生成;基于第一重配置信息和所述第二重配置信息配置所述第一网络节点从所述原CU节点到目标CU节点的切换,所述第一重配置信息是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。
第二方面,提供了一种自回传网络的切换方法,由目标CU节点执行,所述方法包括:接收原CU节点在触发切换时发送的第二网络切换请求,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由所述原CU节点发送给所述目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点;发送第二网络切换响应给所述原CU节点,所述第二网络切换响应包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成。
第三方面,提供了一种自回传网络的切换装置,所述装置包括:第一发送模块,用于在触发切换的情况下,发送第二网络切换请求给目标CU节点,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由原CU节点发送给所述目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点;第一接收模块,用于接收所述目标CU节点发送的第二网络切换响应,所述第二网络切换响应中至少包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成;配置模块,用于基于第一重配置信息和所述第二重配置信息配置所述第一网络节点从所述原CU节点到目标CU节点的切换,所述第一重配置信息是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。
第四方面,提供了一种自回传网络的切换装置,所述装置包括:第一发送模块,用于在触发切换的情况下,发送第二网络切换请求给目标CU节点,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由原CU节点发送给所述目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点;第一接收模块,用于接收所述目标CU节点发送的第二网络切换响应,所述第二网络切换响应中至少包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成;配置模块,用于基于第一重配置信息和所述第二重配置信息配置所述第一网络节点从所述原CU节点到目标CU节点的切换,所述第一重配置信息是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。
第五方面,提供了一种网络侧设备,该网络侧设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第一方面或第二方面所述的方法的步骤。
第六方面,提供了一种网络侧设备,包括处理器及通信接口,其中,所述处理器和通信接口用于实现如第一方面或第二方面所述的方法的步骤。
第七方面,提供了一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤,或者实现如第二方面所述的方法的步骤。
第八方面,提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行网络侧设备程序或指令,实现如第一方面所述的方法,或实现如第二方面所述的方法。
第九方面,提供了一种计算机程序产品,该计算机程序产品包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述 程序或指令被所述处理器执行时实现如第一方面或第二方面所述的方法的步骤。
本申请实施例中,由原CU节点在切换触发之前,通过第一网络切换请求获取第一重配置信息,从而使得在切换触发的情况下,只需通过所述第二网络切换请求获取上下文信息中发生变化的信息对应的重配置信息,由此,可大幅降低触发切换触发后需要传输的信令量,进而避免信令风暴的出现,同时还可缩短由于需要获取重配置信息而造成的切换时延,确保网络切换性能。
附图说明
图1是本申请一示例性实施例提供的无线通信系统的结构示意图。
图2a是本申请一示例性实施例提供的移动IAB系统的结构示意图。
图2b是本申请一示例性实施例提供的待切换的IAB网络的结构示意图。
图3是本申请一示例性实施例提供的自回传网络的切换方法300的流程示意图。
图4是本申请一示例性实施例提供的自回传网络的切换方法400的流程示意图。
图5是本申请一示例性实施例提供的自回传网络的切换方法500的交互流程示意图。
图6是本申请一示例性实施例提供的自回传网络的切换方法600的流程示意图。
图7是本申请一示例性实施例提供的自回传网络的切换装置700的方框结构示意图。
图8是本申请一示例性实施例提供的自回传网络的切换装置800的方框结构示意图。
图9是本申请一示例性实施例提供的网络侧设备的方框结构示意图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚地描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员所获得的所有其他实施例,都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换,以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施,且“第一”、“第二”所区别的对象通常为一类,并不限定对象的个数,例如第一对象可以是一个,也可以是多个。此外,说明书以及权利要求中“和/或”表示所连接对象的至少其中之一,字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是,本申请实施例所描述的技术不限于长期演进型(Long Term Evolution,LTE)/LTE的演进(LTE-Advanced,LTE-A)系统,还可用于其他无线通信系统,诸如码分多址(Code Division Multiple Access,CDMA)、时分多址(Time Division Multiple Access,TDMA)、频分多址(Frequency Division Multiple Access,FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access,OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access,SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用,所描述的技术既可用于以上提及的系统和无线电技术,也可用于其他系统和无线电技术。然而,以下描述出于示例目的描述了新空口NR系统,并且在以下大部分描述中使用NR术语,这些技术也可应用于NR系统应用以外的应用,如第6代(6th Generation,6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的结果示意图。无线 通信系统包括终端11和网络侧设备12。其中,终端11也可以称作终端设备或者用户终端,终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant,PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer,UMPC)、移动上网装置(Mobile Internet Device,MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备,可穿戴式设备包括:手环、耳机、眼镜等。需要说明的是,在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网,其中,基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station,BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set,BSS)、扩展服务集(Extended Service Set,ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point,TRP)或所述领域中其他某个合适的术语,只要达到相同的技术效果,所述基站不限于特定技术词汇,需要说明的是,在本申请实施例中仅以NR系统中的基站为例,但是并不限定基站的具体类型。
在本申请实施例中,UE可以包括但不限于移动台(Mobile Station,MS)、移动终端(Mobile Terminal)、移动电话(Mobile Telephone)、手机(handset)及便携设备(portable equipment)、车辆(vehicle)等,该UE可以经无线接入网(Radio Access Network,RAN)与一个或多个核心网进行通信,如,UE可由IAB网络节点提供无线接入服务等。可选地,UE可以是移动电话(或称为“蜂窝”电话)、具有无线通信功能的计算机等,终端设备还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置。
在此基础上,请结合参阅图2a,该图2a为本申请实施例提供的移动IAB系统的CU-DU结构图。具体的,在一个自回传链路中,IAB网络(如图2a中的IAB网络1)中的最上游的IAB网络节点中的DU均连接到一个CU网 络,而该CU网络可通过F1-AP协议对DU进行配置,以及通过无线资源控制(Radio Resource Control,RRC)协议对MT进行配置。一个自回传链路中还包括一个宿主(Donor)IAB网络节点(或者被称为IAB Donor),该Donor IAB网络节点不具有MT功能部分,但Donor IAB网络节点具有与其直接相连的有线传输网。
在此情况下,以图2a中所示的IAB网络1(也就是待切换的IAB网络)为例,该IAB网络1中可以包括图2b所示的逐级连接的多个IAB网络节点(如图2b中所示的IAB1、IAB2、IAB3……),以及通过各IAB网络节点提供网络接入服务的UE(如图2b中所示的UE1、UE2……),其中,网络节点IAB1为IAB网络1中的最上游的IAB网络节点,网络节点IAB1为与其相邻的下游网络节点IAB2的父IAB网络节点、网络节点IAB2为与其相邻的下游网络节点IAB3的父IAB网络节点……,换言之,网络节点IAB2为与其相邻的上游网络节点IAB1的子IAB网络节点、网络节点IAB3为与其相邻的下游网络节点IAB2的子IAB网络节点。另外,一个IAB网络节点可以为一个或多个UE提供网络接入服务。
下面结合附图,通过一些实施例及其应用场景对本申请实施例提供的技术方案进行详细地说明。
如图3所示,为本申请一示例性实施例提供的自回传网络的切换方法300的流程示意图,该方法300可以由原CU节点执行,具体可以由安装于所述原CU节点中的软件和/或硬件执行。所述方法300至少包括如下步骤。
S310,在触发切换的情况下,发送第二网络切换请求给目标CU节点。
其中,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由所述原CU节点发送给所述目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络 节点,如IAB节点或由IAB节点提供服务的UE。
相应的,根据所述第一网络节点的不同,所述第一网络节点的上下文信息可以不同,例如,在所述第一网络节点为IAB节点的情况下,所述上下文信息包括IAB-MT的上下文信息和/或IAB-DU的F1连接的上下文信息;又例如,在所述第一网络节点为UE的情况下,所述RRC连接的上下文信息。
需要理解的是,所述第一网络切换请求(即早期切换请求)是在触发切换之前,由所述原CU节点发送给目标CU节点,以在触发切换之前预先获取待切换的IAB网络中各网络节点的重配置信息,由此,可在触发切换的情况下,使得所述原CU节点通过发送第二网络切换请求(即后期切换请求)获取少量的重配置信息,如上下文信息相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的信息对应的重配置信息,从而可大幅降低触发切换后需要传输的信令量(如信令和空口的信令等),进而避免信令风暴的出现,以及缩短由于需要获取重配置信息而造成的切换时延。
此外,所述第一网络切换请求的发送时间与所述第二网络切换请求的发送时间之间具有预定时间间隔,以确保在切换触发前,所述原CU节点已经获取到待切换的IAB网络中各网络节点的重配置信息。也就是说,在切换触发之前的一个时间提前量,所述原CU节点为每一个待切换的网络节点触发前期切换准备。
可选的,所述预定时间间隔和/或所述第一网络切换请求在触发切换之前的实际发送时间点可以通过高层信令配置或协议约定或者由OAM系统进行配置,本实施例对此不做限制。
S320,接收所述目标CU节点发送的第二网络切换响应。
其中,与前述S320中所述的第二网络切换请求对应,所述第二网络切换响应中至少包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成。本实施例中,由于所述第二网络切换请求包括第一网络节点的上下文信息或上下文信息的改变部分,那么作为回应, 所述目标CU节点发送给所述原CU节点的第二网络切换响应中也可包括与上下文信息或上下文信息的改变部分对应的切换重配置信息或切换重配置信息的改变部分。
可选地,在所述第一网络节点为UE的情况下,所述第二重配置信息包括无线资源控制(Radio Resource Control,RRC)重配置信息;在所述第二网络节点为IAB节点的情况下,所述第二重配置信息包括IAB-MT的RRC重配置信息和/或IAB-DU的F1连接重配置消息。
另外,所述第二网络切换请求中可包括用于指示其是后期切换请求的指示信息,关于所述指示信息可由高层配置或协议约定,对此不做限制。
S330,基于第一重配置信息和所述第二重配置信息配置所述第一网络节点从所述原CU节点到目标CU节点的切换。
其中,所述第一重配置信息是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。另外,与所述第二重配置信息相似,在所述第一网络节点为UE的情况下,所述第一重配置信息可以包括RRC重配置信息;在所述第二网络节点为IAB节点的情况下,所述第一重配置信息可以包括IAB-MT的RRC重配置信息和/或IAB-DU的F1连接重配置消息。
示例性的,基于前述S310-S330的描述,请再次参阅图2b,假设在触发切换之前,所述原CU节点通过第一网络切换请求发送待切换的IAB网络1(包括IAB1、IAB2、IAB3、UE1、UE2……)的上下文信息给所述目标CU节点,并获取到了与其对应的第一重配置信息,以用于后续的IAB网络1中各网络节点的切换。但在触发切换的情况下,由于某种原因,所述IAB网络1中的IAB1节点的上下文信息相对于所述第一网络切换请求中包括的IAB1节点(即前述的第一网络节点)的上下文信息发生变化,那么,所述原CU节点可再次通过所述第二网络切换请求发送IAB1节点中发生变化的上下文信息给所述目标CU节点,以获取与其对应的第二重配置信息,进而基于第一重配置信息配置和所述第二重配置信息配置所述IAB1节点的切换,以及 基于所述第一重配置信息配置所述IAB网络1中除IAB1节点之外的其他网络节点的切换,由此,可在切换触发后,大幅降低触发切换后需要传输的信令量,进而避免信令风暴的出现,以及缩短由于需要获取重配置信息而造成的切换时延,确保网络切换性能。
如图4所示,为本申请一示例性实施例提供的自回传网络的切换方法400的流程示意图,该方法400可以由原CU节点执行,具体可以由安装于所述原CU节点中的软件和/或硬件执行。所述方法300至少包括如下步骤。
S410,在预测到需要进行所述IAB网络切换的情况下,发送所述第一网络切换请求给所述目标CU节点。
其中,所述第一网络切换请求至少包括所述原CU节点在发送所述第一网络切换请求时的所述第一网络节点的上下文信息。可以理解,在待切换的IAB网络中包括多个网络节点时,所述第一网络切换请求可以包括多个网络节点的上下文信息。
一种实现方式中,所述第一网络切换请求中还可包括第一信息,用于向所述目标CU节点指示所述第一网络切换请求为早期切换请求。可选地,所述第一网络切换请求作为早期切换请求,可以使用一个新的RRC IE,也可以重用现有的切换请求IE,如在现有的切换请求IE中增加一个指示域(也即第一信息),以指示所述目标CU节点不用立即为这些待切换节点保留资源,避免资源浪费。
本实施例中,所述第一信息可以包括切换发生地点和/或切换发生时间点,其中,所述切换发生地点和/或切换发生时间点是所述原CU节点根据移动IAB系统的预定移动路线、移动速度以及备选IAB宿主的部署信息预测得到。可以理解,所述移动IAB系统的预定移动路线、移动速度以及备选IAB宿主的部署信息可以是协议约定或者通过高层信令等配置,在此不做限制。
S420,接收所述目标CU节点发送的第一网络切换响应。
其中,所述第一网络切换响应是由所述目标CU节点根据所述第一网络 切换请求生成,也就是,所述第一网络切换响应中包括的第一重配置信息是由所述目标CU节点根据所述第一网络切换请求中包括的上下文信息生成。
与前述所述第一网络切换请求对应,所述第一网络切换响应中也可包括第二信息,所述第二信息用于指示所述第一网络切换响应为早期切换响应。实际应用中,所述第二网络切换响应可以使用一个新的RRC IE,也可以重用现有的切换请求响应IE,如在现有的切换请求IE中增加一个指示域(也即第二信息),以指示这是一个早期切换请求响应。
S430,在触发切换的情况下,发送第二网络切换请求给目标CU节点。
其中,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由所述原CU节点发送给所述目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点。
S440,接收所述目标CU节点发送的第二网络切换响应。
其中,所述第二网络切换响应中至少包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成。
S450,基于第一重配置信息和所述第二重配置信息配置所述第一网络节点从所述原CU节点到目标CU节点的切换。
其中,所述第一重配置信息是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。
需要说明的是,S430-S450的实现过程除了可参照前述方法实施例300中的相关描述之外,作为本申请实施例中一种可能的实现方式,S450中所述的基于第一重配置信息和所述第二重配置信息,配置所述第一网络节点从所述原CU节点到目标CU节点的切换,可以包括以下(1)-(2)中至少一项。
(1)原CU节点发送切换触发通知给所述目标CU节点,所述切换触发 通知用于向所述目标CU节点通知所述第一网络节点的节点信息。可选地,所述切换触发通知中可包括切换节点识别符列表,以指示与所述切换节点识别符对应的节点为待切换节点(如第一网络节点)。
(2)原CU节点发送切换触发通知给所述目标CU节点,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的切换即将发生。
可以理解,所述原CU节点可以通过一个所述切换触发通知,向所述目标CU节点同时指示所述第一网络节点的节点信息和所述第一网络节点的切换即将发生,也可以,通过两个所述切换触发通知,分别向所述目标CU节点指示所述第一网络节点的节点信息和所述第一网络节点的切换即将发生,对此不做限制。
在前述基础上,所述目标CU节点在接收到所述切换触发通知后,可为待切换节点(如第一网络节点)配置资源,以及向所述原CU节点发送确定信息,所述原CU节点在接收到所述目标CU节点反馈的确认信息的情况下,发送目标重配置信息给第一网络节点,由此,可在不影响UE的前提下,控制切换发生的时机,确保了用户通信体验。
可以理解,所述目标重配置信息是利用所述第二重配置信息对所述第一重配置信息进行替代或更新得到。也就是,如果所述原CU节点接收到的第二网络切换响应(即一个节点的后期切换响应消息)中包含第一网络节点的全部的重配置参数设置,则直接用该第二重配置信息(即后期重配置消息)替代第一重配置信息(即前期重配置消息),作为目标重配置信息发送给第一网络节点;如果所述原CU节点接收到的第二网络切换响应(即一个节点的后期切换响应消息)中仅包含发生变化的上下文信息对应的部分的重配置参数设置,那么所述原CU将对应于第一网络节点的第二重配置信息(即后期重配置消息)替代第一重配置信息(即前期重配置消息)合并起来,作为所述目标重配置信息发送给所述第一网络节点,用来替换早期缓存的第一重配置信息。
进一步,所述原CU节点在将目标重配置信息发送给所述第一网络节点后,如果所述第一网络节点为IAB节点,那么,该IAB节点将接收到的目标重配置信息存储起来,并在切换触发后,将存储的目标重配置信息发送给由其提供服务的UE;或者,该IAB节点将接收到的目标重配置信息存储起来,同时发送目标重配置信息给由其提供服务的UE,再由各自将各自的重配置信息存储起来,由此,各网络节点通过对各自重配置信息的预先缓存,可使得在接收到触发通知时,直接基于缓存的重配置信息进行切换,从而大幅缩短切换时延。
例如,所述原CU节点在确定触发切换(如原CU节点接收到来自移动IAB-MT的测量报告信息,决定进行移动IAB系统从原CU节点切换到目标CU节点)的情况下,可发送切换启动通知信息给所述第一网络节点,所述切换启动通知信息用于指示所述第一网络节点按照缓存的目标重配置信息进行切换,相应的,所述第一网络节点在接收到切换启动通知信息时,开始按切换启动通知信息发起切换。
可选地,所述切换启动通知信息可通过F1信令、RRC信令或BAP Control PDU信令传输。
进一步,除了前述的描述之外,作为一种可能的实现方式,对于上下文信息未发生变化的第一网络节点,也就是,在触发切换后,第一网络节点的上下文信息相对于所述第一网络切换请求中包括的第一网络节点的上下文信息未发生变化,那么,在触发切换的情况下,所述原CU节点可直接基于所述第一重配置信息,配置所述第一网络节点从所述原CU节点到目标CU节点的切换。
例如,在触发切换后,所述原CU节点发送切换触发通知给所述目标CU节点,以通知用于向所述目标CU节点通知所述第一网络节点的节点信息,和/或向所述目标CU节点通知所述第一网络节点的切换即将发生,并在收到所述目标CU节点反馈的确认信息的情况下,发送所述第一重配置信息给第 一网络节点进行缓存,和/或所述第一网络节点将其转发给由其提供服务的UE等,使得第一网络节点和/或由其提供服务的UE可基于各自缓存的重配置信息进行切换,由此,避免在切换触发的情况下获取重配置信息,从而能够大幅降低触发切换后需要传输的信令量,进而避免信令风暴的出现,以及缩短由于需要获取重配置信息而造成的切换时延,确保网络切换性能。
其中,所述原CU节点在将第一重配置信息发送给所述第一网络节点的时机,可以是在切换触发前,也可以是在确定第一网络节点的上下文信息未发生变化时,还可以是在接收到目标CU节点发送的确认信息时,在此不做限制。
本实施例400中,基于多阶段切换流程(如第一网络切换请求对应的早期切换准备流程以及第二网络切换请求对应的后期切换准备流程)中,原CU节点和目标CU节点之间的绝大部分信令(如Xn接口的信令等)交互是在切换触发之前完成,有较大的时间提前量,在此情况下,如果切换触发,原CU节点只需要对待切换的IAB网络中上下文信息发生改变的节点的全部或部分配置参数,进行再次切换准备流程更新,从而很大程度上降低了快速切换带来的信令风暴影响。
此外,本实施给出的自回传网络的切换方法中,切换过程始终在网络的控制之下,达到规避切换风暴的情况下实现规模切换,如在待切换的IAB网络节点包括多个第一网络节点时,同时实现对多个第一网络节点的规模切换。
进一步,基于前述方法实施例300和400的描述,下面结合图5,对本申请提供的自回传网络的切换过程作进一步说明,内容如下。
早期切换准备流程
S502,所述原CU节点根据移动IAB系统的预定移动路线、移动速度以及备选IAB宿主的部署信息预测是否需要进行所述IAB网络切换。
S504,在预测到需要进行所述IAB网络切换的情况下,所述原CU节点 发送所述第一网络切换请求给所述目标CU节点。
S506,所述目标CU节点发送第一网络切换响应给原CU节点。
后期切换准备流程
S508,所述原CU节点确定触发切换的情况下,发送第二网络切换请求给目标CU节点。
S510,所述目标CU节点发送第二网络切换响应给所述原CU节点。
S512,所述原CU节点发送切换触发通知给所述目标CU节点。
S514,所述目标CU节点为待切换节点配置资源,以及反馈确认信息给所述原CU节点。
S516,所述原CU节点发送目标重配置信息为IAB节点1,和/或所述原CU节点发送第一重配置信息为IAB节点1,其中,所述IAB节点1表示在切换触发后,上下文信息相对于第一网络切换请求中包括的IAB节点1的上下文信息发生变化的节点,所述IAB节点2表示在切换触发后,上下文信息相对于第一网络切换请求中包括的IAB节点2的上下文信息未发生变化的节点。
S518,所述IAB节点1对接收到的目标重配置信息进行缓存,和/或所述IAB节点2对接收到的第一重配置信息进行缓存。
S520,所述IAB节点1对接收到的目标重配置信息进行缓存,和/或所述IAB节点2对接收到的第一重配置信息进行缓存。
可选地,IAB节点1接收到的目标重配置信息发送给由其提供服务的UE1,和/或,IAB节点2将接收到的第一重配置信息发送给由其提供服务的UE2。
S522,原CU节点发送切换启动通知信息给IAB节点1和IAB节点2.
S524,在接收到的切换启动通知信息的情况下,IAB节点1和IAB节点2基于缓存的重配置信息进行切换。
需要说明的是,关于前述S502-S524的具体实现过程可参照前述方法实施例300或400的相关描述,并达到相同的技术效果,为避免重复,在此不 再赘述。
如图6所示,为本申请一示例性实施例提供的自回传网络的切换方法600的流程示意图,该方法600可以由目标CU节点执行,具体可以由安装于所述目标CU节点中的软件和/或硬件执行。所述方法600至少包括如下步骤。
S610,接收原CU节点在触发切换时发送的第二网络切换请求,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由所述原CU节点发送给所述目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点;
S620,发送第二网络切换响应给所述原CU节点,所述第二网络切换响应包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成。
本实施例600中,在切换触发之前,目标CU节点根据接收到的第一网络切换请求,生成第一重配置信息并发送给出原CU节点,使得在切换触发的情况下,只需基于接收到的第二网络切换请求生成第二重配置信息并发送给源CU节点,其中,所述第二网络切换请求中至少包括的第一网络节点的上下文信息,是触发切换时所述第一网络节点的上下文信息相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,由此,可大幅降低触发切换后需要传输的信令量,进而避免信令风暴的出现,以及缩短由于需要获取重配置信息而造成的切换时延,确保网络切换性能。
一种可能的实现方式中,发送第二网络切换响应给所述原CU节点之后,所述方法还包括以下(1)-(2)至少一项。
(1)接收所述原CU节点发送的切换触发通知,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的节点信息;
(2)接收所述原CU节点发送的切换触发通知,所述切换触发通知用于 向所述目标CU节点通知所述第一网络节点的切换即将发生。
另一种可能的实现方式中,接收所述原CU节点发送的切换触发通知之后,所述方法还包括:在接收到所述切换触发通知的情况下,反馈确认信息给所述原CU节点,和/或配置与所述第一网络节点对应的网络切换资源。
另一种可能的实现方式中,接收原CU节点发送的第二网络切换请求之前,所述方法还包括:接收所述原CU节点发送的第一网络切换请求,所述第一网络切换请求是所述原CU节点在预测到需要进行所述IAB网络切换的情况下发送的,所述第一网络切换请求至少包括所述原CU节点在发送所述第一网络切换请求时的所述第一网络节点的上下文信息;发送第一网络切换响应给所述原CU节点,所述第一网络切换响应包括第一重配置信息,所述第一重配置信息是是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。
另一种可能的实现方式中,所述第一网络切换请求中还包括第一信息,用于指示所述第一网络切换请求为早期切换请求;和/或所述第一网络切换响应中还包括第二信息,所述第二信息用于指示所述第一网络切换响应为早期切换响应。
另一种可能的实现方式中,所述第一信息包括切换发生地点和/或切换发生时间点,其中,所述切换发生地点和/或切换发生时间点是所述原CU节点根据移动IAB系统的预定移动路线、移动速度以及备选IAB宿主的部署信息预测得到。
另一种可能的实现方式中,在所述第一网络节点为UE的情况下,所述第一重配置信息和所述第二重配置信息包括RRC重配置信息;在所述第二网络节点为IAB节点的情况下,所述第一重配置信息和所述第二重配置信息包括IAB-MT的RRC重配置信息和/或IAB-DU的F1连接重配置消息。
需要说明的是,由于本方法实施例600提供的前述各实现方式具有与前述方法实施例300-500中的各实现方式相同或相应的技术特征,因此,关于 本方法实施例600的实现过程可参照前述方法实施例300-500的相关描述,为避免重复,在此不再赘述。
此外需要说明的是,本申请实施例提供的自回传网络的切换方法300-600,执行主体可以为自回传网络的切换装置,或者,该自回传网络的切换装置中的用于执行自回传网络的切换方法300-600的控制模块。本申请实施例中以自回传网络的切换装置执行自回传网络的切换方法300-600为例,说明本申请实施例提供的自回传网络的切换装置。
如图7所示,为本申请一示例性实施例提供的一种自回传网络的切换装置700,所述装置700包括:第一发送模块710,用于在触发切换的情况下,发送第二网络切换请求给目标CU节点,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由原CU节点发送给所述目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点;第一接收模块720,用于接收所述目标CU节点发送的第二网络切换响应,所述第二网络切换响应中至少包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成;配置模块730,用于基于第一重配置信息和所述第二重配置信息配置所述第一网络节点从所述原CU节点到目标CU节点的切换,所述第一重配置信息是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。
一种可能的实现方式中,所述配置模块730用于以下至少一项:发送切换触发通知给所述目标CU节点,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的节点信息;发送切换触发通知给所述目标CU节点,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的切换即将发生。
另一种可能的实现方式中,所述第一发送模块710还用于在接收到所述目标CU节点反馈的确认信息的情况下,发送目标重配置信息给第一网络节点,所述目标重配置信息是利用所述第二重配置信息对所述第一重配置信息进行替代或更新得到。
另一种可能的实现方式中,所述配置模块730还用于在触发切换的情况下,基于所述第一重配置信息,配置所述第一网络节点从所述原CU节点到目标CU节点的切换。
另一种可能的实现方式中,所述第一发送模块710还用于发送切换启动通知信息给所述第一网络节点,所述切换启动通知信息用于指示所述第一网络节点按照缓存的目标重配置信息和/或所述第一重配置信息进行切换。
另一种可能的实现方式中,所述切换启动通知信息通过F1信令、RRC信令或BAP Control PDU信令传输。
另一种可能的实现方式中,所述第一发送模块710还用于在预测到需要进行所述IAB网络切换的情况下,发送所述第一网络切换请求给所述目标CU节点,所述第一网络切换请求至少包括所述原CU节点在发送所述第一网络切换请求时的所述第一网络节点的上下文信息;所述第一接收模块720还用于接收所述目标CU节点发送的第一网络切换响应,所述第一网络切换响应包括所述第一重配置信息。
另一种可能的实现方式中,所述第一网络切换请求中还包括第一信息,用于指示所述第一网络切换请求为早期切换请求;和/或所述第一网络切换响应中还包括第二信息,所述第二信息用于指示所述第一网络切换响应为早期切换响应。
另一种可能的实现方式中,所述第一信息包括切换发生地点和/或切换发生时间点,其中,所述切换发生地点和/或切换发生时间点是所述原CU节点根据移动IAB系统的预定移动路线、移动速度以及备选IAB宿主的部署信息预测得到。
另一种可能的实现方式中,所述第一网络切换请求的发送时间与所述第二网络切换请求的发送时间之间具有预定时间间隔。
另一种可能的实现方式中,在所述第一网络节点为UE的情况下,所述第一重配置信息和所述第二重配置信息包括RRC重配置信息;在所述第二网络节点为IAB节点的情况下,所述第一重配置信息和所述第二重配置信息包括IAB-MT的RRC重配置信息和/或IAB-DU的F1连接重配置消息。
如图8所示,为本申请一示例性实施例提供的自回传网络的切换装置800的方框结构示意图,所述装置800包括:第二接收模块810,用于接收原CU节点在触发切换时发送的第二网络切换请求,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由所述原CU节点发送给目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点;第二发送模块820,用于发送第二网络切换响应给所述原CU节点,所述第二网络切换响应包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成。
一种可能的实现方式中,所述第二接收模块810还用于以下至少一项:接收所述原CU节点发送的切换触发通知,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的节点信息;接收所述原CU节点发送的切换触发通知,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的切换即将发生。
另一种可能的实现方式中,所述第二发送模块820还用于在接收到所述切换触发通知的情况下,反馈确认信息给所述原CU节点,和/或配置与所述第一网络节点对应的网络切换资源。
另一种可能的实现方式中,所述第二接收模块810还用于接收所述原CU节点发送的第一网络切换请求,所述第一网络切换请求是所述原CU节点在 预测到需要进行所述IAB网络切换的情况下发送的,所述第一网络切换请求至少包括所述原CU节点在发送所述第一网络切换请求时的所述第一网络节点的上下文信息;所述第二发送模块820,还用于发送第一网络切换响应给所述原CU节点,所述第一网络切换响应包括第一重配置信息,所述第一重配置信息是是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。
另一种可能的实现方式中,所述第一网络切换请求中还包括第一信息,用于指示所述第一网络切换请求为早期切换请求;和/或所述第一网络切换响应中还包括第二信息,所述第二信息用于指示所述第一网络切换响应为早期切换响应。
另一种可能的实现方式中,所述第一信息包括切换发生地点和/或切换发生时间点,其中,所述切换发生地点和/或切换发生时间点是所述原CU节点根据移动IAB系统的预定移动路线、移动速度以及备选IAB宿主的部署信息预测得到。
另一种可能的实现方式中,在所述第一网络节点为UE的情况下,所述第一重配置信息和所述第二重配置信息包括RRC重配置信息;在所述第二网络节点为IAB节点的情况下,所述第一重配置信息和所述第二重配置信息包括IAB-MT的RRC重配置信息和/或IAB-DU的F1连接重配置消息。
本申请实施例中的自回传网络的切换装置700或800可以是装置,具有操作系统的装置或电子设备,也可以是终端中的部件、集成电路、或芯片。该装置或电子设备可以是移动终端,也可以为非移动终端。示例性的,移动终端可以包括但不限于上述所列举的终端11的类型,非移动终端可以为服务器、网络附属存储器(Network Attached Storage,NAS)、个人计算机(personal computer,PC)、电视机(television,TV)、柜员机或者自助机等,本申请实施例不作具体限定。
本申请实施例提供的自回传网络的切换装置700或800能够实现图3至 图6的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供一种网络侧设备,包括处理器和通信接口,处理器用于实现前述方法实施例300-600中的步骤。该网络侧设备实施例是与上述网络侧设备方法实施例对应的,上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中,且能达到相同的技术效果。
具体地,本申请实施例还提供了一种网络侧设备。如图9所示,该网络设备900包括:天线901、射频装置902、基带装置903。天线901与射频装置902连接。在上行方向上,射频装置902通过天线901接收信息,将接收的信息发送给基带装置903进行处理。在下行方向上,基带装置903对要发送的信息进行处理,并发送给射频装置902,射频装置902对收到的信息进行处理后经过天线901发送出去。
上述频带处理装置可以位于基带装置903中,以上实施例中网络侧设备执行的方法可以在基带装置903中实现,该基带装置903包括处理器904和存储器905。
基带装置903例如可以包括至少一个基带板,该基带板上设置有多个芯片,如图9所示,其中一个芯片例如为处理器904,与存储器905连接,以调用存储器905中的程序,执行以上方法实施例中所示的网络设备操作。
该基带装置903还可以包括网络接口906,用于与射频装置902交互信息,该接口例如为通用公共无线接口(common public radio interface,简称CPRI)。
具体地,本发明实施例的网络侧设备还包括:存储在存储器905上并可在处理器904上运行的指令或程序,处理器904调用存储器905中的指令或程序执行图7或图8所示各模块执行的方法,并达到相同的技术效果,为避免重复,故不在此赘述。
本申请实施例还提供一种可读存储介质,所述可读存储介质上存储有程 序或指令,该程序或指令被处理器执行时实现上述自回传网络的切换方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
其中,所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质,包括计算机可读存储介质,如计算机只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现上述自回传网络的切换方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片,系统芯片,芯片系统或片上系统芯片等。
本申请实施例还提供了一种计算机程序产品,该计算机程序产品包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时,实现上述自回传网络的切换方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外,需要指出的是,本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能,还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能,例如,可以按不同于所描述的次序来执行所描述的方法,并且还可以添加、省去、或组合各种步骤。另外,参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述,但是本申请并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的,本领域的普通技术人员在本申请的启示下,在不脱离本申请宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本申请的保护之内。

Claims (38)

  1. 一种自回传网络的切换方法,由原CU节点执行,所述方法包括:
    在触发切换的情况下,发送第二网络切换请求给目标CU节点,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由所述原CU节点发送给所述目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点;
    接收所述目标CU节点发送的第二网络切换响应,所述第二网络切换响应中至少包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成;
    基于第一重配置信息和所述第二重配置信息配置所述第一网络节点从所述原CU节点到目标CU节点的切换,所述第一重配置信息是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。
  2. 如权利要求1所述的方法,其中,基于第一重配置信息和所述第二重配置信息,配置所述第一网络节点从所述原CU节点到目标CU节点的切换,包括以下至少一项:
    发送切换触发通知给所述目标CU节点,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的节点信息;
    发送切换触发通知给所述目标CU节点,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的切换即将发生。
  3. 根据权利要求2所述的方法,其中,发送切换触发通知给所述目标CU节点之后,所述方法还包括:
    在接收到所述目标CU节点反馈的确认信息的情况下,发送目标重配置信息给第一网络节点,所述目标重配置信息是利用所述第二重配置信息对所述第一重配置信息进行替代或更新得到。
  4. 如权利要求1所述的方法,其中,所述方法还包括:
    在触发切换的情况下,基于所述第一重配置信息,配置所述第一网络节点从所述原CU节点到目标CU节点的切换。
  5. 如权利要求1-4中任一项所述的方法,其中,所述方法还包括:
    发送切换启动通知信息给所述第一网络节点,所述切换启动通知信息用于指示所述第一网络节点按照缓存的目标重配置信息和/或所述第一重配置信息进行切换。
  6. 如权利要求5所述的方法,其中,所述切换启动通知信息通过F1信令、RRC信令或BAP Control PDU信令传输。
  7. 如权利要求1-6中任一项所述的方法,其中,在触发切换的情况下,发送第二网络切换请求给目标CU节点之前,所述方法还包括:
    在预测到需要进行所述IAB网络切换的情况下,发送所述第一网络切换请求给所述目标CU节点,所述第一网络切换请求至少包括所述原CU节点在发送所述第一网络切换请求时的所述第一网络节点的上下文信息;
    接收所述目标CU节点发送的第一网络切换响应,所述第一网络切换响应包括所述第一重配置信息。
  8. 如权利要求7所述的方法,其中,所述第一网络切换请求中还包括第一信息,用于指示所述第一网络切换请求为早期切换请求;和/或
    所述第一网络切换响应中还包括第二信息,所述第二信息用于指示所述第一网络切换响应为早期切换响应。
  9. 如权利要求8所述的方法,其中,所述第一信息包括切换发生地点和/或切换发生时间点,其中,所述切换发生地点和/或切换发生时间点是所述原CU节点根据移动IAB系统的预定移动路线、移动速度以及备选IAB宿主的部署信息预测得到。
  10. 如权利要求7所述的方法,其中,所述第一网络切换请求的发送时间与所述第二网络切换请求的发送时间之间具有预定时间间隔。
  11. 如权利要求1-10中任一项所述的方法,其中,在所述第一网络节点为UE的情况下,所述第一重配置信息和所述第二重配置信息包括RRC重配置信息;
    在所述第二网络节点为IAB节点的情况下,所述第一重配置信息和所述第二重配置信息包括IAB-MT的RRC重配置信息和/或IAB-DU的F1连接重配置消息。
  12. 一种自回传网络的切换方法,由目标CU节点执行,所述方法包括:
    接收原CU节点在触发切换时发送的第二网络切换请求,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由所述原CU节点发送给所述目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点;
    发送第二网络切换响应给所述原CU节点,所述第二网络切换响应包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成。
  13. 如权利要求12所述的方法,其中,发送第二网络切换响应给所述原CU节点之后,所述方法还包括以下至少一项:
    接收所述原CU节点发送的切换触发通知,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的节点信息;
    接收所述原CU节点发送的切换触发通知,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的切换即将发生。
  14. 如权利要求13所述的方法,其中,接收所述原CU节点发送的切换触发通知之后,所述方法还包括:
    在接收到所述切换触发通知的情况下,反馈确认信息给所述原CU节点,和/或配置与所述第一网络节点对应的网络切换资源。
  15. 如权利要求12所述的方法,其中,接收原CU节点发送的第二网络切换请求之前,所述方法还包括:
    接收所述原CU节点发送的第一网络切换请求,所述第一网络切换请求是所述原CU节点在预测到需要进行所述IAB网络切换的情况下发送的,所述第一网络切换请求至少包括所述原CU节点在发送所述第一网络切换请求时的所述第一网络节点的上下文信息;
    发送第一网络切换响应给所述原CU节点,所述第一网络切换响应包括第一重配置信息,所述第一重配置信息是是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。
  16. 如权利要求15所述的方法,其中,所述第一网络切换请求中还包括第一信息,用于指示所述第一网络切换请求为早期切换请求;和/或
    所述第一网络切换响应中还包括第二信息,所述第二信息用于指示所述第一网络切换响应为早期切换响应。
  17. 如权利要求16所述的方法,其中,所述第一信息包括切换发生地点和/或切换发生时间点,其中,所述切换发生地点和/或切换发生时间点是所述原CU节点根据移动IAB系统的预定移动路线、移动速度以及备选IAB宿主的部署信息预测得到。
  18. 如权利要求12-17中任一项所述的方法,其中,在所述第一网络节点为UE的情况下,所述第一重配置信息和所述第二重配置信息包括RRC重配置信息;
    在所述第二网络节点为IAB节点的情况下,所述第一重配置信息和所述第二重配置信息包括IAB-MT的RRC重配置信息和/或IAB-DU的F1连接重配置消息。
  19. 一种自回传网络的切换装置,所述装置包括:
    第一发送模块,用于在触发切换的情况下,发送第二网络切换请求给目标CU节点,所述第二网络切换请求中至少包括第一网络节点的上下文信息, 所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由原CU节点发送给所述目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点;
    第一接收模块,用于接收所述目标CU节点发送的第二网络切换响应,所述第二网络切换响应中至少包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成;
    配置模块,用于基于第一重配置信息和所述第二重配置信息配置所述第一网络节点从所述原CU节点到目标CU节点的切换,所述第一重配置信息是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。
  20. 如权利要求19所述的装置,其中,所述配置模块用于以下至少一项:
    发送切换触发通知给所述目标CU节点,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的节点信息;
    发送切换触发通知给所述目标CU节点,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的切换即将发生。
  21. 根据权利要求20所述的装置,其中,所述第一发送模块还用于在接收到所述目标CU节点反馈的确认信息的情况下,发送目标重配置信息给第一网络节点,所述目标重配置信息是利用所述第二重配置信息对所述第一重配置信息进行替代或更新得到。
  22. 如权利要求19所述的装置,其中,所述配置模块还用于在触发切换的情况下,基于所述第一重配置信息,配置所述第一网络节点从所述原CU节点到目标CU节点的切换。
  23. 如权利要求19-22中任一项所述的装置,其中,所述第一发送模块还用于发送切换启动通知信息给所述第一网络节点,所述切换启动通知信息用于指示所述第一网络节点按照缓存的目标重配置信息和/或所述第一重配置信息进行切换。
  24. 如权利要求23所述的装置,其中,所述切换启动通知信息通过F1信令、RRC信令或BAP Control PDU信令传输。
  25. 如权利要求19-24中任一项所述的装置,其中,所述第一发送模块还用于在预测到需要进行所述IAB网络切换的情况下,发送所述第一网络切换请求给所述目标CU节点,所述第一网络切换请求至少包括所述原CU节点在发送所述第一网络切换请求时的所述第一网络节点的上下文信息;
    所述第一接收模块还用于接收所述目标CU节点发送的第一网络切换响应,所述第一网络切换响应包括所述第一重配置信息。
  26. 如权利要求25所述的装置,其中,所述第一网络切换请求中还包括第一信息,用于指示所述第一网络切换请求为早期切换请求;和/或
    所述第一网络切换响应中还包括第二信息,所述第二信息用于指示所述第一网络切换响应为早期切换响应。
  27. 如权利要求26所述的装置,其中,所述第一信息包括切换发生地点和/或切换发生时间点,其中,所述切换发生地点和/或切换发生时间点是所述原CU节点根据移动IAB系统的预定移动路线、移动速度以及备选IAB宿主的部署信息预测得到。
  28. 如权利要求25所述的装置,其中,所述第一网络切换请求的发送时间与所述第二网络切换请求的发送时间之间具有预定时间间隔。
  29. 如权利要求19-28中任一项所述的装置,其中,在所述第一网络节点为UE的情况下,所述第一重配置信息和所述第二重配置信息包括RRC重配置信息;
    在所述第二网络节点为IAB节点的情况下,所述第一重配置信息和所述第二重配置信息包括IAB-MT的RRC重配置信息和/或IAB-DU的F1连接重配置消息。
  30. 一种自回传网络的切换装置,所述装置包括:
    第二接收模块,用于接收原CU节点在触发切换时发送的第二网络切换 请求,所述第二网络切换请求中至少包括第一网络节点的上下文信息,所述上下文信息是触发切换时的所述第一网络节点的上下文信息,相对于第一网络切换请求中包括的所述第一网络节点的上下文信息发生变化的至少部分信息,所述第一网络切换请求是在触发切换之前,由所述原CU节点发送给目标CU节点,所述第一网络节点是待切换的IAB网络中的任一网络节点;
    第二发送模块,用于发送第二网络切换响应给所述原CU节点,所述第二网络切换响应包括第二重配置信息,所述第二重配置信息由所述目标CU节点根据所述第二网络切换请求生成。
  31. 如权利要求30所述的装置,其中,所述第二接收模块还用于以下至少一项:
    接收所述原CU节点发送的切换触发通知,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的节点信息;
    接收所述原CU节点发送的切换触发通知,所述切换触发通知用于向所述目标CU节点通知所述第一网络节点的切换即将发生。
  32. 如权利要求31所述的装置,其中,所述第二发送模块还用于在接收到所述切换触发通知的情况下,反馈确认信息给所述原CU节点,和/或配置与所述第一网络节点对应的网络切换资源。
  33. 如权利要求31所述的装置,其中,所述第二接收模块还用于接收所述原CU节点发送的第一网络切换请求,所述第一网络切换请求是所述原CU节点在预测到需要进行所述IAB网络切换的情况下发送的,所述第一网络切换请求至少包括所述原CU节点在发送所述第一网络切换请求时的所述第一网络节点的上下文信息;
    所述第二发送模块,还用于发送第一网络切换响应给所述原CU节点,所述第一网络切换响应包括第一重配置信息,所述第一重配置信息是是在触发切换之前,由所述目标CU节点根据所述第一网络切换请求生成。
  34. 如权利要求33所述的装置,其中,所述第一网络切换请求中还包括 第一信息,用于指示所述第一网络切换请求为早期切换请求;和/或
    所述第一网络切换响应中还包括第二信息,所述第二信息用于指示所述第一网络切换响应为早期切换响应。
  35. 如权利要求34所述的装置,其中,所述第一信息包括切换发生地点和/或切换发生时间点,其中,所述切换发生地点和/或切换发生时间点是所述原CU节点根据移动IAB系统的预定移动路线、移动速度以及备选IAB宿主的部署信息预测得到。
  36. 如权利要求30-35中任一项所述的装置,其中,在所述第一网络节点为UE的情况下,所述第一重配置信息和所述第二重配置信息包括RRC重配置信息;
    在所述第二网络节点为IAB节点的情况下,所述第一重配置信息和所述第二重配置信息包括IAB-MT的RRC重配置信息和/或IAB-DU的F1连接重配置消息。
  37. 一种网络侧设备,包括处理器,存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时,实现如权利要求1至11任一项所述的自回传网络的切换方法的步骤,或者,实现如权利要求12至18任一项所述的自回传网络的切换方法的步骤。
  38. 一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时,实现如权利要求1至11任一项所述的自回传网络的切换方法的步骤,或者,实现如权利要求12至18任一项所述的自回传网络的切换方法的步骤。
PCT/CN2022/080575 2021-03-17 2022-03-14 自回传网络的切换方法、装置及网络侧设备 WO2022194074A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110286829.2A CN115119269B (zh) 2021-03-17 2021-03-17 自回传网络的切换方法、装置及网络侧设备
CN202110286829.2 2021-03-17

Publications (1)

Publication Number Publication Date
WO2022194074A1 true WO2022194074A1 (zh) 2022-09-22

Family

ID=83321596

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/080575 WO2022194074A1 (zh) 2021-03-17 2022-03-14 自回传网络的切换方法、装置及网络侧设备

Country Status (2)

Country Link
CN (1) CN115119269B (zh)
WO (1) WO2022194074A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024065289A1 (en) * 2022-09-28 2024-04-04 Lenovo (Beijing) Limited Method and apparatus for iab node integration

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116033512B (zh) * 2023-03-30 2023-06-23 广州世炬网络科技有限公司 自回传iab网络中iab宿主节点切换方法、装置、设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102369762A (zh) * 2009-04-01 2012-03-07 高通股份有限公司 为切换鲁棒性而能够准备多个邻近接入点的方法和装置
CN111586744A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 一种iab节点的切换方法及装置
WO2020188447A1 (en) * 2019-03-15 2020-09-24 Telefonaktiebolaget Lm Ericsson (Publ) Storing and restoring conditional handover in suspend-resume
WO2020197459A1 (en) * 2019-03-28 2020-10-01 Telefonaktiebolaget Lm Ericsson (Publ) Conditional handover execution probability information to potential target node

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014131159A1 (zh) * 2013-02-27 2014-09-04 华为技术有限公司 小区切换方法、用户设备及基站
CN108471631B (zh) * 2017-02-23 2020-05-12 北京佰才邦技术有限公司 一种切换准备方法、相关基站及ue
CN113301618B (zh) * 2017-03-24 2022-10-04 华为技术有限公司 通信方法、网络设备和终端
CN110536350A (zh) * 2019-02-14 2019-12-03 中兴通讯股份有限公司 Iab链路控制方法、通信单元、计算机可读存储介质
US20210051547A1 (en) * 2019-08-16 2021-02-18 Nokia Solutions And Networks Oy Associating iab mt to iab du at handover-target gnb
CN112512087A (zh) * 2020-04-26 2021-03-16 中兴通讯股份有限公司 网络切换方法、装置、设备及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102369762A (zh) * 2009-04-01 2012-03-07 高通股份有限公司 为切换鲁棒性而能够准备多个邻近接入点的方法和装置
CN111586744A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 一种iab节点的切换方法及装置
WO2020188447A1 (en) * 2019-03-15 2020-09-24 Telefonaktiebolaget Lm Ericsson (Publ) Storing and restoring conditional handover in suspend-resume
WO2020197459A1 (en) * 2019-03-28 2020-10-01 Telefonaktiebolaget Lm Ericsson (Publ) Conditional handover execution probability information to potential target node

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024065289A1 (en) * 2022-09-28 2024-04-04 Lenovo (Beijing) Limited Method and apparatus for iab node integration

Also Published As

Publication number Publication date
CN115119269A (zh) 2022-09-27
CN115119269B (zh) 2023-11-03

Similar Documents

Publication Publication Date Title
CN108811092B (zh) 波束失败恢复处理方法、终端及网络侧设备
US20170311211A1 (en) Method, Apparatus and System for Dual Connectivity Handover Initiated by Source Base Station Becoming the Future Secondary Base Station
WO2022194074A1 (zh) 自回传网络的切换方法、装置及网络侧设备
EP3735028B1 (en) Communication method for deterministic transmission and related apparatus
US11589331B2 (en) Interface establishing method and apparatus
WO2019085728A1 (zh) 通信方法及装置
WO2018038653A1 (en) Identification of potentially neighboring network nodes in a wireless communication network
KR20180105679A (ko) 네트워크 제어된 핸드오버 및 ue 자율적인 핸드오버를 위한 하이브리드 솔루션
KR20180026519A (ko) 다중-연결성을 위한 분할 베어러 향상
WO2023087907A1 (zh) 侧行链路的切换方法、装置、终端、存储介质及程序产品
RU2732736C1 (ru) Способ связи, вторичный узел сети и терминал
CN118077248A (zh) 用于无线网络的pscell的有条件重新配置期间的测量配置更新
US20240040450A1 (en) Information transmission method and apparatus
EP3703422A1 (en) Method and apparatus for identifying user device
JP2018078629A (ja) ページング制御方法、及び基地局
JP2013223218A (ja) 無線通信システムおよびネットワーク
CN114071610B (zh) 切换方法、装置及相关设备
EP3618558A1 (en) Method for enabling network to fall back, terminal device, and access network device
WO2014045151A2 (en) Apparatus and method for communication
JP2023537460A (ja) 端末装置、ネットワーク装置、及び方法
CN114599058A (zh) 通信方法、装置、电子设备及计算机可读存储介质
TWI691230B (zh) 一種使用者設備間的通信及其控制方法及裝置
TWI809452B (zh) 傳輸路徑協調方法及其使用者設備
US20230388890A1 (en) Handover of a communication session
US20240284275A1 (en) Apparatus, method, and computer program

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22770429

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 22770429

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 28.02.24)