WO2023236224A1 - Procédé et dispositif de migration - Google Patents

Procédé et dispositif de migration Download PDF

Info

Publication number
WO2023236224A1
WO2023236224A1 PCT/CN2022/098276 CN2022098276W WO2023236224A1 WO 2023236224 A1 WO2023236224 A1 WO 2023236224A1 CN 2022098276 W CN2022098276 W CN 2022098276W WO 2023236224 A1 WO2023236224 A1 WO 2023236224A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
information
migration
iab
node
Prior art date
Application number
PCT/CN2022/098276
Other languages
English (en)
Chinese (zh)
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 PCT/CN2022/098276 priority Critical patent/WO2023236224A1/fr
Priority to CN202280002085.XA priority patent/CN117597889A/zh
Publication of WO2023236224A1 publication Critical patent/WO2023236224A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to a migration method and device.
  • the first entity and the second entity may provide network access connections for the third entity and the terminal equipment under the third entity.
  • the third entity and/or the terminal equipment under the third entity need to provide network access connections from the first entity
  • direct migration may cause the terminal equipment to fail to migrate or switch. Failure affects user experience.
  • Embodiments of the present disclosure provide a migration method and device to avoid terminal device migration failure or handover failure and improve user experience.
  • an embodiment of the present disclosure provides a migration method, which is executed by a first entity.
  • the method includes: sending migration request information of a third entity to a second entity, wherein the third entity and the third entity
  • the terminal device under the three entities is provided with a network access connection by the first entity; and receives the first feedback information sent by the second entity.
  • the first entity sends the migration request information of the third entity to the second entity, wherein the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity ; Receive the first feedback information sent by the second entity.
  • the first entity can consider the first feedback information to decide a migration strategy, perform migration, etc., thereby avoiding terminal device migration failure or handover failure and improving user experience.
  • an embodiment of the present disclosure provides another migration method, which is executed by a second entity.
  • the method includes: receiving migration request information of a third entity sent by the first entity, wherein the third entity and the The terminal device under the third entity is provided with a network access connection by the first entity; and sends first feedback information to the first entity.
  • embodiments of the present disclosure provide a communication device that has some or all of the functions of a network-side device for implementing the method described in the first aspect.
  • the functions of the communication device may include some or all of those in the present disclosure.
  • the functions in all the embodiments may also be used to independently implement any one embodiment of the present disclosure.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may further include a storage module coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.
  • the communication device includes: a transceiver module configured to send migration request information of a third entity to the second entity, wherein the third entity and the terminal under the third entity The device is provided with a network access connection by the first entity; the transceiver module is further configured to receive the first feedback information sent by the second entity.
  • embodiments of the present disclosure provide another communication device that has some or all of the functions of the terminal device in the method example described in the second aspect.
  • the functions of the communication device may have some of the functions in the present disclosure.
  • the functions in all the embodiments may also be provided to implement the functions of any one embodiment in the present disclosure independently.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may further include a storage module coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.
  • the communication device includes: a transceiver module configured to receive the migration request information of the third entity sent by the first entity, wherein the third entity and the terminal device under the third entity The first entity provides a network access connection; the transceiver module is further configured to send first feedback information to the first entity.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the second aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the second aspect above.
  • embodiments of the present disclosure provide a migration system, which includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect and The communication device according to the sixth aspect, or the system includes the communication device according to the seventh aspect and the communication device according to the eighth aspect, or the system includes the communication device according to the ninth aspect and the communication device according to the tenth aspect. the above-mentioned communication device.
  • embodiments of the present invention provide a computer-readable storage medium for storing instructions used by the above-mentioned first entity.
  • the first entity is caused to execute the above-mentioned first aspect. method described.
  • embodiments of the present invention provide a readable storage medium for storing instructions used by the above-mentioned second entity. When the instructions are executed, the second entity is caused to execute the above-mentioned second aspect. Methods.
  • the present disclosure also provides a computer program product including a computer program, which when run on a computer causes the computer to execute the method described in the first aspect.
  • the present disclosure also provides a computer program product including a computer program, which, when run on a computer, causes the computer to execute the method described in the second aspect.
  • the present disclosure provides a chip system, which includes at least one processor and an interface for supporting the first entity to implement the functions involved in the first aspect, for example, determining or processing the functions involved in the above method. At least one of data and information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the first entity.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a chip system, which includes at least one processor and an interface for supporting a second entity to implement the functions involved in the second aspect, for example, determining or processing the functions involved in the above method. At least one of data and information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the second entity.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to execute the method described in the first aspect.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect.
  • Figure 1 is a schematic diagram of an IAB network provided by an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of an IAB architecture provided by an embodiment of the present disclosure
  • Figure 3 is an architectural diagram of a communication system provided by an embodiment of the present disclosure
  • Figure 4 is a schematic structural diagram of a first entity, a second entity, or a third entity provided by an embodiment of the present disclosure
  • Figure 5 is a flow chart of a migration method provided by an embodiment of the present disclosure.
  • Figure 6 is a flow chart of another migration method provided by an embodiment of the present disclosure.
  • Figure 7 is a flow chart of yet another migration method provided by an embodiment of the present disclosure.
  • Figure 8 is a flow chart of yet another migration method provided by an embodiment of the present disclosure.
  • Figure 9 is a structural diagram of a communication device provided by an embodiment of the present disclosure.
  • Figure 10 is a structural diagram of another communication device provided by an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a chip provided by an embodiment of the present disclosure.
  • Embodiments of the present disclosure can be applied to various communication systems, such as wireless local area network (WLAN), narrowband-internet of things (NB-IoT), and global system for mobile communications (GSM), enhanced data rate for gsm evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 system (code division multiple access, CDMA2000 ), time division-synchronization codedivision multiple access (TD-SCDMA), long term evolution (LTE), satellite communications, fifth generation (5th generation, 5G) systems may appear in the future new communication systems, etc.
  • WLAN wireless local area network
  • NB-IoT narrowband-internet of things
  • GSM global system for mobile communications
  • EDGE enhanced data rate for gsm evolution
  • WCDMA wideband code division multiple access
  • CDMA2000 code division multiple access 2000 system
  • TD-SCDMA time division-synchronization codedivision multiple access
  • LTE long term evolution
  • 5G fifth generation
  • the terminal devices involved in the embodiments of the present disclosure may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to wireless modems.
  • the terminal can be a mobile station (MS), subscriber unit (subscriber unit), user equipment (UE), cellular phone (cellular phone), smart phone (smart phone), wireless data card, personal digital assistant (personal digital assistant) Digital assistant (PDA) computers, tablet computers, wireless modems (modems), handheld devices (handsets), laptop computers (laptop computers), machine type communication (MTC) terminals, etc.
  • MS mobile station
  • subscriber unit subscriber unit
  • UE user equipment
  • cellular phone cellular phone
  • smart phone smart phone
  • wireless data card personal digital assistant (personal digital assistant) Digital assistant (PDA) computers, tablet computers, wireless modems (modems), handheld devices (handsets), laptop computers (laptop computers), machine type communication (MTC) terminals, etc.
  • PDA personal digital assistant
  • modems wireless modems
  • IAB Integrated access and backhaul, integrated access and backhaul
  • NG-RAN next generation radio access network, next-generation wireless access network
  • the relay node is also called an IAB node (IAB-node) and supports wireless access and backhaul through NR (New Radio).
  • IAB host node IAB-donor
  • gNB NR nodeB, next-generation base station
  • IAB nodes can be made to support dual connectivity (DC) or multi-connectivity (multi-connectivity) to cope with possible abnormal situations in the backhaul link, such as link failure or blocking. /Abnormalities such as congestion (blockage) or load fluctuations can improve the reliability of transmission.
  • DC dual connectivity
  • multi-connectivity multi-connectivity
  • the IAB network supports multi-hop and multi-connection networking, there may be multiple transmission paths between the terminal device (for example, user equipment (UE)) and the IAB host node (IAB donor).
  • Each transmission path contains multiple nodes, and the multiple nodes can include a UE, one or more IAB nodes, and an IAB donor.
  • the IAB donor is in the form of a centralized unit (CU) and a distributed unit (DU)
  • the IAB donor can include the IAB-donor-DU part (donor DU) and the IAB-donor-CU (donor CU) part, etc.
  • the IAB node can provide wireless access services for terminal equipment.
  • the business data of the terminal equipment is transmitted from the IAB node to the IAB donor through the wireless backhaul link.
  • each IAB node regards the adjacent node that provides the backhaul service as a parent node (or superior node).
  • each IAB node can be regarded as a child node (or subordinate node) of its parent node.
  • the wireless link used by an IAB node to communicate with its child nodes is called an access link, which includes uplink transmission and downlink transmission links. Uplink transmission on the access link is also called uplink transmission of the access link, and downlink transmission is also called downlink transmission of the access link.
  • the wireless link used by an IAB node to communicate with its parent node can be called a backhaul link, including uplink transmission and downlink transmission links.
  • the uplink transmission on the backhaul link is also called the uplink transmission of the backhaul link, and the downlink transmission is also called the downlink transmission of the backhaul link.
  • the parent node of IAB node 1 is the IAB host node (ie, IAB donor), and IAB node 1 is the parent node of IAB node 2 and IAB node 3.
  • IAB node 2 and IAB node Node 3 is the parent node of IAB node 4, and the parent node of IAB node 5 is IAB node 2.
  • path 1 UE1-IAB node 4-IAB node 3-IAB node 1-IAB donor
  • path 2 UE1-IAB node 4-IAB node 2- IAB node 1-IAB donor.
  • path 3 There are three available paths for data transmission between UE2 and IAB donor, path 3: UE2-IAB node 4-IAB node 3-IAB node 1-IAB donor, path 4: UE2-IAB node 4-IAB node 2-node 1 -IABdonor, path 5: UE2-IAB node 5-IAB node 2-IAB node 1-IAB donor.
  • the uplink data packet of each UE can be transmitted to the IAB donor by one or more IAB nodes, and then sent to the mobile gateway device (such as the user plane function (UPF) network element in the 5G core network) by the IAB donor.
  • the downlink data packet can be received by the IAB donor from the mobile gateway device, and then sent to the UE through the IAB node.
  • the mobile gateway device such as the user plane function (UPF) network element in the 5G core network
  • the IAB node can include a mobile terminal (mobile termination, MT) part and a distributed unit (distributed unit, DU) part.
  • MT mobile terminal
  • DU distributed unit
  • an IAB node faces its parent node (its parent node can be another IAB node, or an IAB donor), it can be regarded as a user device, that is, MT; when an IAB node faces its child node (its child node can be another
  • an IAB node (or terminal device) it can be regarded as a network device and is used to provide backhaul services for sub-nodes, that is, DU.
  • the IAB donor can be an access network element with complete access functions, or an access network element in the form of separate CU and DU.
  • the IAB donor can be connected to the core network that serves terminal equipment (for example, 5G Core network (5Gcore, 5GC)) network element and provides wireless backhaul services for IAB nodes.
  • 5G Core 5G Core network
  • the centralized unit of IAB donor is referred to as donor CU (or directly called CU), and the distributed unit of IAB donor is referred to as donor DU.
  • the donor CU may also be in a form where the control plane (CP) and the user plane (UP) are separated.
  • CP control plane
  • UP user plane
  • a CU can be composed of a CU-CP and one (or more) CU-UP.
  • the IAB donor may also be called an IAB host node or a donor node (donor node) or a host base station (DgNB, donor gNodeB), which is not limited by this disclosure.
  • the IAB networking scenario shown in Figure 1 is only exemplary. In the IAB networking scenario that combines multi-hop and multi-connection, there are many other possibilities. For example, a DgNB and an IAB node under another DgNB can form a Dual connectivity serves UE, etc. This disclosure will not list them one by one here.
  • IAB-donor includes one IAB-donor-CU (IAB-host-CU) and one or more IAB-donor-DU (IAB-host-DU).
  • IAB-donor may include one IAB-donor-CU-CP, multiple IAB-donor-CU-UP and multiple IAB-donor-DU.
  • IAB-node connects to the upstream IAB-node or IAB-donor-DU through a subset of terminal functions of the NR Uu interface (called the IAB-MT function in IAB-node).
  • the IAB-node provides wireless backhaul to downstream IAB-nodes and terminals through the network function of the NR Uu interface (called the IAB-DU function of the IAB-node).
  • the F1-C service between IAB-node and IAB-donor-CU is backhauled through IAB-donor-DU and the optional intermediate hop IAB-node.
  • the F1-U service between IAB-node and IAB-donor-CU is backhauled through IAB-donor-DU and the optional intermediate hop IAB-node.
  • FIG. 3 is a schematic architectural diagram of a mobile communication system applied to embodiments of the present disclosure.
  • the mobile communication system includes a terminal device, at least one relay device (the first IAB node and the second IAB node in Figure 3), and a wireless access network device (the host node in Figure 3) and core network equipment.
  • the terminal device is connected to the relay device through a wireless method, and is connected to the wireless access network device through one or more relay devices (some terminal devices can also be directly connected to the wireless access network device through a wireless method).
  • Access network equipment is connected to core network equipment through wireless or wired methods.
  • the wireless links between various devices can communicate through the licensed spectrum (licensed spectrum), the unlicensed spectrum (unlicensed spectrum), or the licensed spectrum and the unlicensed spectrum at the same time.
  • Wireless links between devices can communicate via spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or both below 6 GHz and above 6 GHz.
  • GHz gigahertz
  • the embodiments of the present disclosure do not limit the spectrum resources used by wireless links.
  • the core network equipment and the radio access network equipment can be independent and different physical devices, or the functions of the core network equipment and the logical functions of the radio access network equipment can be integrated on the same physical device, or they can be one
  • the physical device integrates the functions of part of the core network equipment and part of the functions of the wireless access network equipment.
  • Terminal equipment can be fixed or movable.
  • the embodiments of the present disclosure do not limit the number of core network equipment, radio access network equipment, relay equipment and terminal equipment included in the mobile communication system.
  • the wireless access network device may be a terminal device or a relay device that wirelessly accesses the mobile communication system, and may be a base station NodeB, an evolved base station eNodeB, a base station gNodeB in the 5G mobile communication system, or a future mobile base station. Base stations in communication systems or access nodes in WiFi systems, etc.
  • the embodiments of the present disclosure do not limit the specific technologies and specific equipment forms used by wireless access network equipment.
  • Terminal equipment can also be called terminal, UE, mobile station (MS), mobile terminal (mobile terminal, MT), etc.
  • the terminal device can be a mobile phone (mobile phone), a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, an augmented reality (AugmentedReality, AR) terminal device, or an industrial control (industrial control) Wireless terminals in autonomous driving (self-driving), wireless terminals in remote medical surgery, wireless terminals in smart grids, and wireless terminals in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • VR Virtual Reality
  • AR AugmentedReality
  • wireless terminals in remote medical surgery wireless terminals in smart grids
  • wireless terminals in transportation safety Terminals wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the relay device may be a device that provides wireless backhaul service or wireless access service.
  • the wireless backhaul service refers to the data and/or signaling backhaul service provided through the wireless backhaul link.
  • the wireless access service refers to the data and/or signaling backhaul service provided through the wireless backhaul link. Data and/or signaling backhaul services provided by the access link.
  • relay devices can provide wireless access services to terminals through access links (AL); on the other hand, relay devices can be connected through one-hop or multi-hop backhaul links (BL). to the access network equipment, so that the relay equipment can forward data and/or signaling between the terminal and the access network equipment, thereby expanding the coverage of the communication system.
  • AL access links
  • BL multi-hop backhaul links
  • Relay devices can have different names in different communication systems.
  • a relay device can be called a relay node, or it can be called a wireless backhaul node or wireless backhaul device; in a 5G system, a relay node can be It is called the integrated access and backhaul node (IAB node).
  • IAB node integrated access and backhaul node
  • relay nodes can also have different names, which are not limited here.
  • the IAB nodes mentioned in the embodiments of this disclosure can all be replaced by relay nodes.
  • Wireless access network equipment, wireless backhaul equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the sky.
  • the embodiments of the present disclosure do not limit the application scenarios of wireless access network equipment, wireless backhaul equipment, and terminal equipment.
  • the first IAB node or the second IAB node in Figure 3 in this embodiment of the present disclosure may be implemented by a device, or may be a functional module within a device, which is not specifically limited in this embodiment of the present disclosure. It can be understood that the above functions can be either network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform), or a chip system . In the embodiments of the present disclosure, the chip system may be composed of chips, or may include chips and other discrete devices.
  • the device for realizing the functions of the first entity, the second entity, or the third entity provided by the embodiment of the present disclosure can be implemented by the device 400 in FIG. 4 .
  • Figure 4 shows a schematic diagram of the hardware structure of the device 400 provided by an embodiment of the present disclosure.
  • the device 400 includes at least one processor 401, which is used to implement the functions of CU, DU or SN provided by the embodiments of the present disclosure.
  • the device 400 may also include a communication bus 402 and at least one communication interface 404.
  • a memory 403 may also be included in the device 400 .
  • the processor may be a central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor , microcontroller, programmable logic device (PLD).
  • the processor can also be any other device with processing functions, such as an application-specific integrated circuit (ASIC), a field programmable gate array (Field Programmable GateArray, FPGA) or other programmable logic devices, transistor logic devices, Hardware components, software modules, or any combination thereof.
  • ASIC application-specific integrated circuit
  • FPGA Field Programmable GateArray
  • Communication bus 402 may be used to transfer information between the components described above.
  • Communication interface 404 is used to communicate with other devices or communication networks, such as Ethernet, wireless access network (radioaccess network, RAN), wireless local area networks (WLAN), etc.
  • the communication interface 404 may be an interface, a circuit, a transceiver, or other device capable of realizing communication, which is not limited by this disclosure.
  • Communication interface 404 may be coupled to processor 401. Coupling in the embodiments of the present disclosure is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information interaction between devices, units or modules.
  • the memory may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (random access memory, RAM) or a Other types of dynamic storage devices for information and instructions, which may also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or Other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired information in the form of instructions or data structures Program code and any other medium capable of being accessed by a computer, without limitation.
  • the memory may exist independently or may be coupled to the processor, such as through communication bus 402. Memory can also be integrated with the processor.
  • the memory 403 is used to store program instructions, and can be controlled and executed by the processor 401, thereby implementing the methods provided by the following embodiments of the present disclosure.
  • the processor 401 is used to call and execute instructions stored in the memory 403, thereby implementing the methods provided by the following embodiments of the present disclosure.
  • the computer-executed instructions in the embodiments of the disclosure may also be called application codes, which are not specifically limited in the embodiments of the disclosure.
  • memory 403 may be included in processor 401.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4 .
  • the device 400 may include multiple processors, such as the processor 401 and the processor 405 in FIG. 4 .
  • processors may be a single-CPU processor or a multi-CPU processor.
  • a processor here may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the device 400 in Figure 4 may also include a transceiver and an antenna.
  • the device 400 may communicate with other devices (such as an IAB node or terminal) through the transceiver and the antenna.
  • the first IAB node and the second IAB node may also include a transceiver and an antenna.
  • the first IAB node may send data and/or information to the second IAB node through the transceiver and antenna, and the transceiver and antenna of the second IAB node may receive The data and/or information; the second IAB node may send the data and/or information to the first IAB node through the transceiver and antenna, and the transceiver and antenna of the first IAB node receive the data and/or information.
  • the transceiver can be used to convert baseband signals and radio frequency signals and process radio frequency signals.
  • the transceiver can be connected to an antenna.
  • the transceiver includes a transmitter (transmitter, Tx) and a receiver (receiver, Rx).
  • one or more antennas can receive radio frequency signals
  • the receiver of the transceiver is used to receive the radio frequency signals from the antennas and convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and convert the digital baseband signals or
  • the digital intermediate frequency signal is provided to the processor, so that the processor performs further processing on the digital baseband signal or digital intermediate frequency signal, such as demodulation processing and decoding processing.
  • the transmitter Tx in the transceiver is used to receive the modulated digital baseband signal or digital intermediate frequency signal from the processor, and convert the modulated digital baseband signal or digital intermediate frequency signal into a radio frequency signal, and transmit it through one or more
  • the antenna transmits the radio frequency signal.
  • the receiver Rx can selectively perform one or more levels of down-mixing processing and analog-to-digital conversion processing on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency signal.
  • the down-mixing processing and the analog-to-digital conversion processing are The order is adjustable.
  • the transmitter Tx can selectively perform one or more levels of upmixing processing and digital-to-analog conversion processing on the modulated digital baseband signal or digital intermediate frequency signal to obtain a radio frequency signal.
  • the upmixing processing and digital-to-analog conversion processing The order is adjustable.
  • Digital baseband signals and digital intermediate frequency signals can be collectively referred to as digital signals.
  • the transmitter Tx and the receiver Rx can be implemented by different physical structures/circuits, or they can be implemented by the same physical structure/circuit, that is to say, the transmitter Tx and the receiver Rx can be inherited together.
  • a transceiver may also be called a transceiver unit, a transceiver, a transceiver device, etc.
  • the devices used to implement the receiving function in the transceiver unit can be regarded as the receiving unit
  • the devices used in the transceiver unit used to implement the transmitting function can be regarded as the transmitting unit, that is, the transceiver unit includes a receiving unit and a transmitting unit, and the receiving unit also It can be called a receiver, input port, receiving circuit, etc.
  • the sending unit can be called a transmitter, transmitter, or transmitting circuit, etc.
  • a combination of Tx, Rx and antenna can be used as a transceiver.
  • admission and addition have the same meaning, both of which mean that when the second entity wants to receive a request from a migrating node, it needs to determine whether it can admit or add the requested resource in order to provide the migrating node (the third Entity) and UE under the node provide services with QoS (Quality of Service, quality of service) guarantee.
  • QoS Quality of Service, quality of service
  • Figure 5 is a flow chart of a migration method provided by an embodiment of the present disclosure.
  • the method is executed by the first entity.
  • the method may include but is not limited to the following steps:
  • S51 Send the migration request information of the third entity to the second entity, where the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • the first entity determines the third entity that needs to be migrated, and the second entity that the third entity needs to migrate to.
  • the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • the third entity can migrate to the second entity, and the second entity can also provide network access connections for the third entity and terminal devices under the third entity.
  • the third entity can move from the first entity to the second entity.
  • the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • the first entity can obtain corresponding information from the third entity or the terminal equipment under the third entity, thereby determining the third entity that needs to be migrated. and the second entity to which the third entity needs to be migrated.
  • the first entity when the first entity determines the third entity that needs to be migrated and the second entity that the third entity needs to migrate to, the first entity may send the migration request information of the third entity to the second entity.
  • the migration request information of the third entity can be used by the second entity to perform admission control, resource preparation, migration preparation, etc.
  • S52 Receive the first feedback information sent by the second entity.
  • the second entity when the second entity receives the migration request information of the third entity sent by the first entity, the second entity may generate the first feedback information and send it to the first entity.
  • the first feedback information may include the results of admission control and/or resource preparation in the second entity, so that the first entity can learn the results of admission control and/or resource preparation in the second entity, and, On the basis of knowing the business needs of the third entity and the terminal equipment under the third entity, it can be determined whether and/or the extent to which the second entity can meet the business needs of the third entity and the terminal equipment under the third entity. . Thus, when it is determined that the business requirements of the third entity and the terminal equipment under the third entity are met, a migration strategy can be generated and/or migration can be performed to avoid terminal equipment migration failure or handover failure and improve user experience.
  • the method allows the pre-migration service entity (first entity) and the post-migration service entity (second entity) to interact in advance with the admission control of all UEs under the mobile node (third entity) before performing UE migration or handover.
  • Related information and/or resource request related information so that the target entity (second entity) can perform admission control and/or resource preparation before UE migration, and/or so that the source entity (first entity) can perform admission control and/or resource preparation according to the target entity (first entity).
  • the second entity) admission result determines whether to select the target entity (second entity) as the final target of migration, thereby avoiding UE handover failure or migration failure due to insufficient resources of the target entity (second entity), and further ensuring The continuity of all migrated UE services improves user experience.
  • the first entity sends the migration request information of the third entity to the second entity.
  • the first entity and the second entity may be a core network, a base station, gNB-CU, gNB-DU, gNB-CU-CP or gNB-CU-UP.
  • the first entity and the second entity are base stations and have IAB functions, such as IAB-donor or IAB-donor-CU or IAB-donor-CU-CP.
  • IAB functions such as IAB-donor or IAB-donor-CU or IAB-donor-CU-CP.
  • the third entity that needs to request migration can be an IAB node, and the IAB node can be mobile, such as mobile IAB.
  • the first entity and the second entity may be satellites with base station functions or part of base station functions, and the third entity required to request migration in the migration request information of the third entity is with base station functions or part of base stations. Functional satellite.
  • the first entity and the second entity are base stations, gNB-CU, gNB-CU-CP or satellites with base station functions
  • the migration request information of the third entity may be provided by XnAP (Xn Application Protocol, Xn Interface Application Protocol) message transmission
  • XnAP message can be handover request message (Handover Request message), migration request message (Migration Request message), IAB Migration Request message (IAB Migration Request message) or group handover request message (Group Handover Request message) wait.
  • the first entity is a base station, gNB-CU, gNB-CU-CP or a satellite with base station function
  • the second entity is a core network, such as AMF (access and mobility management function), access and Mobility management function
  • the migration request information of the third entity can be transmitted by NGAP (NG Application Protocol, NG Application Protocol) message.
  • the NGAP message can be Handover Required message (Handover Required message), Migration Required message (Migration Required message), IAB Migration requirement message (IAB Migration Required message) or group handover requirement message (Group Handover Required message), etc.
  • the first entity is a core network
  • the second entity is a base station, gNB-CU, gNB-CU-CP or a satellite with base station functions
  • the migration request information of the third entity may be transmitted by an NGAP message.
  • the NGAP message can be a handover request message (Handover Request message), a migration request message (Migration Request message), an IAB migration request message (IAB Migration Request message) or a group handover request message (Group Handover Request message), etc.
  • the migration request information of the third entity includes at least one of the following:
  • the first entity sends the migration request information of the third entity to the second entity, and may send information indicating the node migration mode to the second entity.
  • the first entity sends the migration request information of the third entity to the second entity, and may send information for node migration admission control to the second entity.
  • the first entity sends the migration request information of the third entity to the second entity, and may send information indicating the node migration mode and information for node migration admission control to the second entity.
  • the information used to indicate the node migration mode may be implicit or explicit, and the second entity may consider or prepare resources for the migrated node based on the information used to indicate the node migration mode.
  • the information used to indicate the node migration mode may be partial migration, complete migration, etc.; in another exemplary embodiment, the information used to indicate the node migration mode may be to indicate specific node functions that need to be migrated, for example , IAB-MT, IAB-DU, IAB-node, etc.; in another exemplary embodiment, the information used to indicate the node migration mode is implicitly indicated, for example, when the migration request information of the third entity includes IAB- DU related information indicates complete migration, otherwise it indicates partial migration. It should be understood that the above are only examples, and the information used to indicate the node migration mode is not limited thereto.
  • the information used for node migration access control includes the information required for access control for complete migration (ie, IAB node migration or complete migration).
  • the second entity can consider or perform based on the information used for node migration access control. Admission control, and feedback admission control and/or resource preparation information to the first entity.
  • the second entity performs different actions taking into account the information indicating the node migration mode. For example, if it is a complete migration, the second entity needs to consider performing admission control and/or preparing corresponding resources for the migration node (i.e., the third entity) and all UEs under the migration node; if it is a partial migration, the second entity only needs to Consider some business requirements in the migrated node for admission control and/or access resources.
  • the information used for node migration admission control includes at least one of the following:
  • the first entity sends the migration request information of the third entity to the second entity, and may send to the second entity information related to the terminal device served by the third entity.
  • the first entity sends the migration request information of the third entity to the second entity, and may send relevant information of the services supported by the third entity to the second entity.
  • the first entity sends the migration request information of the third entity to the second entity, and may send to the second entity related information about the terminal device served by the third entity and related information about the services supported by the third entity.
  • the information related to the terminal device served by the third entity includes at least one of the following:
  • the number of terminal devices is the number of terminal devices.
  • the core network node to which the terminal device is connected;
  • PDU Packet data unit
  • the information related to the terminal equipment served by the third entity is used to indicate the information related to all terminal equipment that needs to be migrated or switched to the second entity.
  • the terminal equipment refers to the terminal equipment served under the third entity.
  • Information related to the terminal equipment served by the third entity can be the number of all terminal equipment under IAB-DU, the number of DRB (Data Radio Bearer, data radio bearer)/SRB (Signalling Radio Bearer, signaling radio bearer), Information such as the QoS (Quality of Service, Quality of Service) requirements of the overall or each terminal device, or specific information of each terminal device, such as information such as the core network node to which the terminal device is connected or the PDU (packet data unit) of the terminal device , packet data unit) session-related information, the second entity considers or performs admission control and/or resource preparation based on the relevant information of the terminal device served by the third entity.
  • the relevant information of the terminal devices served by the third entity is the number of terminal devices.
  • the relevant information of the terminal device served by the third entity is the number of data radio bearer DRBs.
  • the relevant information about the terminal equipment served by the third entity is the number of signaling radio bearer SRBs.
  • the relevant information of the terminal devices served by the third entity is the service quality QoS requirement of each terminal device.
  • the relevant information about the terminal devices served by the third entity is the service quality QoS requirements of all terminal devices.
  • the relevant information of the terminal device served by the third entity is the core network node to which the terminal device is connected.
  • the relevant information of the terminal device served by the third entity is the packet data unit (PDU) session information of the terminal device.
  • PDU packet data unit
  • the information related to services supported by the third entity includes one or more service configuration items; wherein the service configuration items include service index, service configuration file, and backhaul BH related configuration.
  • the relevant information of the services supported by the third entity is used to indicate the relevant information of the services supported on the node requesting migration (third entity).
  • the service configuration on the IAB-DU which may include a
  • each configuration project can include a business index, business configuration file (traffic profile), BH ((Backhaul, returnhaul)) related configuration.
  • the business configuration file includes at least one of the following:
  • the service configuration file includes user plane UP (user plane, user plane) service.
  • the service configuration file includes control plane CP (control plane, control plane) services.
  • the service configuration file includes QoS requirements.
  • the service configuration file includes UP services and QoS requirements.
  • the service configuration file includes CP services and QoS requirements.
  • relevant information about services supported by the third entity is sent in the first step of migration, such as during the IAB-MT migration process. This allows the second entity to perform service-related admission control and/or Resource preparation improves the success rate of migration and ensures user business experience.
  • the second entity considers or prepares resources for the third entity after migration based on relevant information about the services supported by the third entity, including but not limited to adding or modifying the BH RLC (BackHaul Radio) after IAB-node migration.
  • Link Control wireless link control of the backhaul link) channel, IP address and/or BAP (backhaul adaptation protocol, backhaul adaptation protocol layer) configuration, and generates the first feedback information including the resource preparation situation, and sends it to the third An entity sends first feedback information.
  • the second entity sends first feedback information to the first entity.
  • the first entity and the second entity are base stations, gNB-CU, gNB-CU-CP, or satellites with base station functions.
  • the first feedback information may be transmitted by an XnAP message, and the XnAP message may be a handover request confirmation message.
  • Handover Request Acknowledge message Migration Request Response message (Migration Request Response message), IAB Migration Response message (IAB Migration Response message), IAB Migration failure message (IAB Migration failure message) or Group Handover Request Acknowledge message (Group Handover Request Acknowledge message) etc.
  • the first entity is a base station, gNB-CU, gNB-CU-CP or a satellite with base station function
  • the second entity is a core network, such as AMF
  • the first feedback information may be transmitted by an NGAP message.
  • the NGAP message can be a handover command message (Handover Command message), a migration command message (Migration Command message), an IAB migration command message (IABMigration Command message) or a group handover command message (Group Handover Command message), etc.
  • the first entity is a core network
  • the second entity is a base station, gNB-CU, gNB-CU-CP, or a satellite with base station functions.
  • the first feedback information may be transmitted by an NGAP message.
  • the NGAP message It can be Handover Request Acknowledge message, Migration Response message, IAB Migration Response message, IAB Migration failure message, or Group switching feedback message. Handover Response message) etc. It should be understood that the above are only examples, and the first entity, the second entity, and the first feedback information are not limited thereto.
  • the second entity sends first feedback information to the first entity.
  • the first feedback information is the migration request information of the third entity sent by the second entity based on the first entity, the resource status of the second entity, the
  • the first feedback information may include information related to feedback of node migration admission control and/or resource preparation results.
  • the first feedback information includes at least one of the following:
  • the second entity when the second entity receives the migration request information of the third entity sent by the first entity, the second entity may generate the first feedback information and send it to the first entity.
  • the second entity sends information about the admission control result of the terminal device to the first entity.
  • the second entity sends the information on the service admission control result to the first entity.
  • the second entity sends resource preparation information to the first entity.
  • the information about the admission control result of the terminal device is used to indicate to the first entity, if the node requesting migration (the third entity) migrates to the second entity, whether the UE under the third entity is admitted successfully. , information related to successful access, and/or information related to failed access, etc.
  • the information about the admission control result of the terminal device includes at least one of the following:
  • the second entity sends information about the admission control result of the terminal device to the first entity, and may send admission success information to the first entity.
  • the second entity sends information about the admission control result of the terminal device to the first entity, and may send admission failure information to the first entity.
  • the second entity sends information about the admission control result of the terminal device to the first entity, and may send admission success information and admission failure information to the first entity.
  • the admission success information includes at least one of the following:
  • the number of access terminal devices is the number of access terminal devices.
  • the admission success information may be an indication, a percentage, a specific number, or specific UE information.
  • the first entity may consider the admission success information to make a migration decision and/or a migration strategy decision. .
  • the admission success information may be information indicating the number of admitted UEs.
  • the admission success information may be information indicating the number of admitted DRBs/SRBs.
  • the admission success information may be information used to indicate the QoS supported after migration, such as the maximum supported transmission bandwidth and other information.
  • the admission success information may be information related to indicating UEs permitted to migrate, for example, it may be a list of UEs permitted to migrate, which includes the ID of each UE and UE-specific information.
  • the admission success information may be the number of admitted terminal devices.
  • the admission success information may be a proportion of the admission terminal equipment.
  • the admission success information may be the number of admitted data radio bearer DRBs.
  • the admission success information may be the number of admission signaling radio bearer SRBs.
  • the admission success information may be QoS information supported after migration.
  • the admission success information may be the maximum transmission bandwidth supported after migration.
  • the admission success information may be information about the terminal device that is allowed to migrate.
  • the second entity sends information about the admission control result of the terminal device to the first entity, and may send admission failure information to the first entity.
  • the admission failure information may be an indication or specific UE information of admission failure, such as UE ID.
  • the service admission control result includes at least one of the following:
  • the service admission control result indicates to the first entity that if the node requesting migration is migrated to the second entity, whether the service addition requested by the node requesting migration (the third entity) is successful, for example, it may include Business indexes added successfully and/or business indexes added failed, etc.
  • the service admission control result is a service index with successful admission.
  • the service admission control result is the service index of failed admission.
  • the service admission control results are the service index of successful admission and the service index of failed admission.
  • the resource preparation information includes: backhaul BH configuration information.
  • the resource preparation information may include, for example, BH configuration information.
  • the first entity may further forward the BH configuration information to the IAB node (third entity) requesting migration, so that the migrating IAB node (third entity) can perform the migration.
  • IAB-DU migration resource preparation information can be included in the RRC (radio resource control, radio resource control) reconfiguration (RRC Reconfiguration) message for transmission.
  • RRC radio resource control, radio resource control
  • the first entity receives the first feedback information, and may make a migration decision, generate a migration policy, and/or execute the migration based on or considering the first feedback information.
  • the first entity may continue the migration process; if only some UEs are successfully admitted, the first entity may consider that some of the UEs that are successfully admitted follow the third entity. Perform migration and continue the migration process.
  • UEs that have not been admitted successfully can switch directly to other base stations without following the third entity to migrate to ensure business continuity; if the first entity receives multiple messages from other entities, (including the second entity), the first entity can select a target entity that has successful admission or has a higher admission success rate or provides a better experience for the UE for migration, and continues the migration process. Therefore, regardless of whether the resources of the target entity are sufficient, the first entity can consider or select the optimal target entity or migration strategy for migration based on the first feedback information to avoid migration failure or UE handover failure or service quality degradation. , to ensure user experience.
  • the first entity is the source integrated access and backhaul IAB host (source IAB-donor)
  • the second entity is the target IAB host (target IAB-donor)
  • the third entity is the IAB node.
  • IAB node In related technology, the location of IAB node (IAB node) is fixed. In order to increase the robustness of IAB, IAB-MT can be migrated to another IAB-donor-CU, and the collocated IAB-DU and its descendant nodes are IAB-DU(s) maintains an F1 connection with the initial IAB-donor-CU. This migration is called Inter-donor partial migration. After the inter-donor partial migration, the F1 traffic of IAB-DU and its descendant nodes will be routed through the BAP layer of the IAB topology to which IAB-MT is migrated.
  • IAB node migration that is, one or more UEs served under IAB-MT, IAB-DU and IAB nodes must be supported. Need to migrate from source IAB-donor-CU (source IAB-donor) to target IAB-donor-CU (target IAB-donor). Among them, the approximate sequence of IAB node migration is as follows:
  • the first step is IAB-MT migration
  • the second step is IAB-DU migration
  • the third step is to migrate the UE under the IAB node.
  • the first and second steps can exchange the order, or the second step can be divided into two stages, occurring before and after IAB-MT migration.
  • the migration of UE must be completed after the migration of IAB-DU.
  • the admission control of multiple UEs is not considered in the first and/or second steps of the interaction between the source IAB-donor and the target IAB-donor. If in the first step The resources of the selected target IAB-donor are not enough to support the service needs of all UEs after migration. After the first and second steps are completed, multiple UEs may fail in the admission control in the third step, resulting in UE migration. Failure or handover failure will eventually interrupt UE services and affect user experience.
  • UE migration can be performed Or before handover, let the source IAB-donor and the target IAB-donor exchange information related to the admission control and/or resource request of all UEs under the IAB node in advance, so that the target IAB-donor can make preparations before the UE migrates.
  • Admission control and/or resource preparation and/or so that the source IAB-donor can determine whether to select the target IAB-donor as the final target of migration based on the admission results of the target IAB-donor, thus avoiding problems caused by insufficient resources of the target IAB-donor.
  • UE handover failure or migration failure thereby further ensuring the continuity of all migrated UE services and improving user experience.
  • Figure 6 is a flow chart of another migration method provided by an embodiment of the present disclosure.
  • the method is executed by the first entity.
  • the method may include but is not limited to the following steps:
  • S61 Send the migration request information of the third entity to the second entity, where the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • S62 Receive the first feedback information sent by the second entity.
  • S63 According to the first feedback information, execute at least one of migration decision, migration policy generation and migration.
  • the first entity after receiving the first feedback information sent by the second entity, the first entity may execute the migration decision.
  • the migration policy may be generated; or, if it is determined that migration cannot be carried out, migration shall be canceled. Wherein, when it is decided to perform migration and a migration policy is generated, the migration can be further performed based on the generated migration policy.
  • the first entity after receiving the first feedback information sent by the second entity, the first entity may perform migration policy generation.
  • migration can be further performed based on the generated migration policy.
  • the first entity after the first entity receives the first feedback information sent by the second entity, it may perform migration.
  • the method allows the pre-migration service entity (first entity) and the post-migration service entity (second entity) to interact in advance with the admission control of all UEs under the mobile node (third entity) before performing UE migration or handover.
  • Related information and/or resource request related information so that the target entity (third entity) can perform admission control and/or resource preparation before UE migration, and/or so that the source entity (first entity) can perform admission control and/or resource preparation according to the target entity (third entity).
  • the second entity) admission result determines whether to select the target entity (second entity) as the final target of migration, thereby avoiding UE handover failure or migration failure due to insufficient resources of the target entity (second entity), and further ensuring The continuity of all migrated UE services improves user experience.
  • Figure 7 is a flow chart of yet another migration method provided by an embodiment of the present disclosure.
  • the method is executed by the second entity.
  • the method may include but is not limited to the following steps:
  • S71 Receive the migration request information of the third entity sent by the first entity, wherein the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • the first entity may determine the third entity that needs to be migrated and the second entity that the third entity needs to migrate to, so as to send the migration request information of the third entity to the second entity.
  • the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • the third entity can migrate to the second entity, and the second entity can also provide network access connections for the third entity and terminal devices under the third entity.
  • the third entity can move from the first entity to the second entity.
  • the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • the first entity can obtain corresponding information from the third entity or the terminal equipment under the third entity, thereby determining the third entity that needs to be migrated. and the second entity to which the third entity needs to be migrated.
  • the migration request information of the third entity may be used by the second entity to perform admission control, resource preparation and/or migration preparation.
  • S72 Send the first feedback information to the first entity.
  • the first feedback information may include the results of admission control and/or resource preparation in the second entity, and the second entity sends the first feedback information to the first entity, so that the first entity can learn the results of the admission control and/or resource preparation in the second entity.
  • the results of admission control and/or resource preparation and on the basis of knowing the business requirements of the third entity and the terminal equipment under the third entity, it can be judged whether the second entity can meet the needs of the third entity and the terminal equipment under the third entity.
  • a migration strategy can be generated and/or migration can be performed to avoid terminal equipment migration failure or handover failure and improve user experience.
  • the method allows the pre-migration service entity (first entity) and the post-migration service entity (second entity) to interact in advance with the admission control of all UEs under the mobile node (third entity) before performing UE migration or handover.
  • Related information and/or resource request related information so that the target entity (third entity) can perform admission control and/or resource preparation before UE migration, and/or so that the source entity (first entity) can perform admission control and/or resource preparation according to the target entity (third entity).
  • the second entity) admission result determines whether to select the target entity (second entity) as the final target of migration, thereby avoiding UE handover failure or migration failure due to insufficient resources of the target entity (second entity), and further ensuring The continuity of all migrated UE services improves user experience.
  • the first entity sends the migration request information of the third entity to the second entity.
  • the first entity and the second entity may be a core network, a base station, gNB-CU, gNB-DU, gNB-CU-CP or gNB-CU-UP.
  • the first entity and the second entity are base stations and have IAB functions, such as IAB-donor or IAB-donor-CU or IAB-donor-CU-CP.
  • IAB functions such as IAB-donor or IAB-donor-CU or IAB-donor-CU-CP.
  • the third entity that needs to request migration can be an IAB node, and the IAB node can be mobile, such as mobile IAB.
  • the first entity and the second entity may be satellites with base station functions or part of base station functions, and the third entity required to request migration in the migration request information of the third entity is with base station functions or part of base stations. Functional satellite.
  • the first entity and the second entity are a base station, gNB-CU, gNB-CU-CP, or a satellite with base station functions.
  • the migration request information of the third entity may be transmitted by an XnAP message.
  • the XnAP message may It is a handover request message (Handover Request message), a migration request message (Migration Request message), an IAB migration request message (IAB Migration Request message) or a group handover request message (Group Handover Request message), etc.
  • the first entity is a base station, gNB-CU, gNB-CU-CP or a satellite with base station functions
  • the second entity is a core network, such as an AMF
  • the migration request information of the third entity may be NGAP message transmission.
  • NGAP messages can be Handover Required message, Migration Required message, IAB Migration Required message, or Group Handover Required message, etc.
  • the first entity is a core network
  • the second entity is a base station, gNB-CU, gNB-CU-CP or a satellite with base station functions
  • the migration request information of the third entity may be transmitted by an NGAP message.
  • the NGAP message can be a handover request message (Handover Request message), a migration request message (Migration Request message), an IAB migration request message (IAB Migration Request message) or a group handover request message (Group Handover Request message), etc.
  • the migration request information of the third entity includes at least one of the following:
  • the first entity sends the migration request information of the third entity to the second entity, and may send information indicating the node migration mode to the second entity.
  • the first entity sends the migration request information of the third entity to the second entity, and may send information for node migration admission control to the second entity.
  • the first entity sends the migration request information of the third entity to the second entity, and may send information indicating the node migration mode and information for node migration admission control to the second entity.
  • the information used to indicate the node migration mode may be implicit or explicit, and the second entity may consider or prepare resources for the migrated node based on the information used to indicate the node migration mode.
  • the information used to indicate the node migration mode may be partial migration, complete migration, etc.; in another exemplary embodiment, the information used to indicate the node migration mode may be to indicate specific node functions that need to be migrated, for example , IAB-MT, IAB-DU, IAB-node, etc.; in another exemplary embodiment, the information used to indicate the node migration mode is implicitly indicated, for example, when the migration request information of the third entity includes IAB- DU related information indicates complete migration, otherwise it indicates partial migration. It should be understood that the above are only examples, and the information used to indicate the node migration mode is not limited thereto.
  • the information used for node migration access control includes the information required for access control for complete migration (ie, IAB node migration or complete migration).
  • the second entity can consider or perform based on the information used for node migration access control. Admission control, and feedback admission control and/or resource preparation information to the first entity.
  • the second entity performs different actions taking into account the information indicating the node migration mode. For example, if it is a complete migration, the second entity needs to consider performing admission control and/or preparing corresponding resources for the migration node (i.e., the third entity) and all UEs under the migration node; if it is a partial migration, the second entity only needs to Consider some business requirements in the migrated node for admission control and/or access resources.
  • the information used for node migration admission control includes at least one of the following:
  • the first entity sends the migration request information of the third entity to the second entity, and may send to the second entity information related to the terminal device served by the third entity.
  • the first entity sends the migration request information of the third entity to the second entity, and may send relevant information of the services supported by the third entity to the second entity.
  • the first entity sends the migration request information of the third entity to the second entity, and may send to the second entity related information about the terminal device served by the third entity and related information about the services supported by the third entity.
  • the information related to the terminal device served by the third entity includes at least one of the following:
  • the number of terminal devices is the number of terminal devices.
  • the core network node to which the terminal device is connected;
  • PDU Packet data unit
  • the information related to the terminal equipment served by the third entity is used to indicate the information related to all terminal equipment that needs to be migrated or switched to the second entity.
  • the terminal equipment refers to the terminal equipment served under the third entity.
  • Information related to the terminal equipment served by the third entity can be the number of all terminal equipment under IAB-DU, the number of DRB (Data Radio Bearer, data radio bearer)/SRB (Signalling Radio Bearer, signaling radio bearer), Information such as the QoS (Quality of Service, Quality of Service) requirements of the overall or each terminal device, or specific information of each terminal device, such as information such as the core network node to which the terminal device is connected or the PDU (packet data unit) of the terminal device , packet data unit) session-related information, the second entity considers or performs admission control and/or resource preparation based on the relevant information of the terminal device served by the third entity.
  • the relevant information of the terminal devices served by the third entity is the number of terminal devices.
  • the relevant information of the terminal device served by the third entity is the number of data radio bearer DRBs.
  • the relevant information about the terminal equipment served by the third entity is the number of signaling radio bearer SRBs.
  • the relevant information of the terminal devices served by the third entity is the service quality QoS requirement of each terminal device.
  • the relevant information about the terminal devices served by the third entity is the service quality QoS requirements of all terminal devices.
  • the relevant information of the terminal device served by the third entity is the core network node to which the terminal device is connected.
  • the relevant information of the terminal device served by the third entity is the packet data unit (PDU) session information of the terminal device.
  • PDU packet data unit
  • the information related to services supported by the third entity includes one or more service configuration items; wherein the service configuration items include service index, service configuration file, and backhaul BH related configuration.
  • the relevant information of the services supported by the third entity is used to indicate the relevant information of the services supported on the node requesting migration (third entity).
  • the service configuration on the IAB-DU which may include a
  • each configuration project can include a business index, business configuration file (traffic profile), BH ((Backhaul, returnhaul)) related configuration.
  • the business configuration file includes at least one of the following:
  • the service configuration file includes user plane UP (user plane, user plane) service.
  • the service configuration file includes control plane CP (control plane, control plane) services.
  • the service configuration file includes QoS requirements.
  • the service configuration file includes UP services and QoS requirements.
  • the service configuration file includes CP services and QoS requirements.
  • relevant information about services supported by the third entity is sent in the first step of migration, such as during the IAB-MT migration process. This allows the second entity to perform service-related admission control and/or Resource preparation improves the success rate of migration and ensures user business experience.
  • the second entity considers or prepares resources for the third entity after migration based on relevant information about the services supported by the third entity, including but not limited to adding or modifying the BH RLC Channel, IP after IAB-node migration.
  • the address and/or BAP are configured, and first feedback information including resource preparation is generated, and the first feedback information is sent to the first entity.
  • the second entity sends first feedback information to the first entity.
  • the first entity and the second entity are base stations, gNB-CU, gNB-CU-CP, or satellites with base station functions.
  • the first feedback information may be transmitted by an XnAP message, and the XnAP message may be a handover request confirmation message.
  • Handover Request Acknowledge message Migration Request Response message (Migration Request Response message), IAB Migration Response message (IAB Migration Response message), IAB Migration failure message (IAB Migration failure message) or Group Handover Request Acknowledge message (Group Handover Request Acknowledge message) etc.
  • the first entity is a base station, gNB-CU, gNB-CU-CP or a satellite with base station function
  • the second entity is a core network, such as AMF
  • the first feedback information may be transmitted by an NGAP message.
  • NGAP messages can be handover command messages (Handover Command message), migration command messages (Migration Command message), IAB migration command messages (IAB Migration Command message) or group handover command messages (Group Handover Command message), etc.
  • the first entity is a core network
  • the second entity is a base station, gNB-CU, gNB-CU-CP, or a satellite with base station functions.
  • the first feedback information may be transmitted by an NGAP message.
  • the NGAP message It can be Handover Request Acknowledge message, Migration Response message, IAB Migration Response message, IAB Migration failure message, or Group switching feedback message. Handover Response message) etc. It should be understood that the above are only examples, the first entity and the second entity, and the feedback information are not limited thereto.
  • the second entity sends first feedback information to the first entity.
  • the first feedback information is the migration request information of the third entity sent by the second entity based on the first entity, the resource status of the second entity, the
  • the first feedback information may include information related to feedback of node migration admission control and/or resource preparation results.
  • the first feedback information includes at least one of the following:
  • the second entity when the second entity receives the migration request information of the third entity sent by the first entity, the second entity may generate the first feedback information and send it to the first entity.
  • the second entity sends information about the admission control result of the terminal device to the first entity.
  • the second entity sends the information on the service admission control result to the first entity.
  • the second entity sends resource preparation information to the first entity.
  • the information about the admission control result of the terminal device is used to indicate to the first entity, if the node requesting migration (the third entity) migrates to the second entity, whether the UE under the third entity is admitted successfully. , information related to successful access, and/or information related to failed access, etc.
  • the information about the admission control result of the terminal device includes at least one of the following:
  • the second entity sends information about the admission control result of the terminal device to the first entity, and may send admission success information to the first entity.
  • the second entity sends information about the admission control result of the terminal device to the first entity, and may send admission failure information to the first entity.
  • the second entity sends information about the admission control result of the terminal device to the first entity, and may send admission success information and admission failure information to the first entity.
  • the admission success information includes at least one of the following:
  • the number of access terminal devices is the number of access terminal devices.
  • the admission success information may be an indication, a percentage, a specific number, or specific UE information.
  • the first entity may consider the admission success information to make a migration decision and/or a migration strategy decision. .
  • the admission success information may be information indicating the number of admitted UEs.
  • the admission success information may be information indicating the number of admitted DRBs/SRBs.
  • the admission success information may be information used to indicate the QoS supported after migration, such as the maximum supported transmission bandwidth and other information.
  • the admission success information may be information related to indicating UEs permitted to migrate, for example, it may be a list of UEs permitted to migrate, which includes the ID of each UE and UE-specific information.
  • the admission success information may be the number of admitted terminal devices.
  • the admission success information may be a proportion of the admission terminal equipment.
  • the admission success information may be the number of admitted data radio bearer DRBs.
  • the admission success information may be the number of admission signaling radio bearer SRBs.
  • the admission success information may be QoS information supported after migration.
  • the admission success information may be the maximum transmission bandwidth supported after migration.
  • the admission success information may be information about the terminal device that is allowed to migrate.
  • the second entity sends information about the admission control result of the terminal device to the first entity, and may send admission failure information to the first entity.
  • the admission failure information may be an indication or specific UE information of admission failure, such as UE ID.
  • the service admission control result includes at least one of the following:
  • the service admission control result indicates to the first entity that if the node requesting migration is migrated to the second entity, whether the service addition requested by the node requesting migration (the third entity) is successful, for example, it may include Business indexes added successfully and/or business indexes added failed, etc.
  • the service admission control result is a service index with successful admission.
  • the service admission control result is the service index of failed admission.
  • the service admission control results are the service index of successful admission and the service index of failed admission.
  • the resource preparation information includes: backhaul BH configuration information.
  • the resource preparation information may include, for example, BH configuration information.
  • the first entity may further forward the BH configuration information to the IAB node (third entity) requesting migration, so that the migrating IAB node (third entity) can perform the migration.
  • IAB-DU migration resource preparation information can be included in the RRC (radio resource control, radio resource control) reconfiguration (RRC Reconfiguration) message for transmission.
  • RRC radio resource control, radio resource control
  • the first entity receives the first feedback information, and may make a migration decision, generate a migration policy, and/or execute the migration based on or considering the first feedback information.
  • the first entity may continue the migration process; if only some UEs are successfully admitted, the first entity may consider that some of the UEs that are successfully admitted follow the third entity. Perform migration and continue the migration process.
  • UEs that have not been admitted successfully can switch directly to other base stations without following the third entity to migrate to ensure business continuity; if the first entity receives multiple messages from other entities, (including the second entity), the first entity can select a target entity that has successful admission or has a higher admission success rate or provides a better experience for the UE for migration, and continues the migration process. Therefore, regardless of whether the resources of the target entity are sufficient, the first entity can consider or select the optimal target entity or migration strategy for migration based on the first feedback information to avoid migration failure or UE handover failure or service quality degradation. , to ensure user experience.
  • the first entity is the source integrated access and backhaul IAB host (source IAB-donor)
  • the second entity is the target IAB host (target IAB-donor)
  • the third entity is the IAB node.
  • IAB node In related technology, the location of IAB node (IAB node) is fixed. In order to increase the robustness of IAB, IAB-MT can be migrated to another IAB-donor-CU, and the collocated IAB-DU and its descendant nodes are IAB-DU(s) maintains an F1 connection with the initial IAB-donor-CU. This migration is called Inter-donor partial migration. After the inter-donor partial migration, the F1 traffic of IAB-DU and its descendant nodes will be routed through the BAP layer of the IAB topology to which IAB-MT is migrated.
  • IAB node migration that is, one or more UEs served under IAB-MT, IAB-DU and IAB nodes must be supported. Need to migrate from source IAB-donor-CU (source IAB-donor) to target IAB-donor-CU (target IAB-donor). Among them, the approximate sequence of IAB node migration is as follows:
  • the first step is IAB-MT migration
  • the second step is IAB-DU migration
  • the third step is to migrate the UE under the IAB node.
  • the first and second steps can exchange the order, or the second step can be divided into two stages, occurring before and after IAB-MT migration.
  • the migration of UE must be completed after the migration of IAB-DU.
  • the admission control of multiple UEs is not considered in the first and/or second steps of the interaction between the source IAB-donor and the target IAB-donor. If in the first step The resources of the selected target IAB-donor are not enough to support the service needs of all UEs after migration. After the first and second steps are completed, multiple UEs may fail in the admission control in the third step, resulting in UE migration. Failure or handover failure will eventually interrupt UE services and affect user experience.
  • UE migration can be performed Or before handover, let the source IAB-donor and the target IAB-donor exchange information related to the admission control and/or resource request of all UEs under the IAB node in advance, so that the target IAB-donor can make preparations before the UE migrates.
  • Admission control and/or resource preparation and/or so that the source IAB-donor can determine whether to select the target IAB-donor as the final target of migration based on the admission results of the target IAB-donor, thus avoiding problems caused by insufficient resources of the target IAB-donor.
  • UE handover failure or migration failure thereby further ensuring the continuity of all migrated UE services and improving user experience.
  • Figure 8 is a flow chart of yet another migration method provided by an embodiment of the present disclosure.
  • the method is executed by the second entity.
  • the method may include but is not limited to the following steps:
  • S81 Receive the migration request information of the third entity sent by the first entity, wherein the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • the first entity may determine the third entity that needs to be migrated and the second entity that the third entity needs to migrate to, so as to send the migration request information of the third entity to the second entity.
  • the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • the third entity can migrate to the second entity, and the second entity can also provide network access connections for the third entity and terminal devices under the third entity.
  • the third entity can move from the first entity to the second entity.
  • the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • the first entity can obtain corresponding information from the third entity or the terminal equipment under the third entity, thereby determining the third entity that needs to be migrated. and the second entity to which the third entity needs to be migrated.
  • the migration request information of the third entity may be used by the second entity to perform admission control, resource preparation and/or migration preparation.
  • S82 According to the migration request information of the third entity, perform node migration admission control and/or prepare resources to generate first feedback information.
  • the second entity receives the migration request information of the third entity sent by the first entity, and can perform node migration admission control and/or prepare resources according to the migration request information of the third entity to generate the first Feedback.
  • the second entity sends first feedback information to the first entity.
  • the first feedback information is the migration request information of the third entity sent by the second entity based on the first entity, the resource status of the second entity, the
  • the first feedback information may include information related to feedback of node migration admission control and/or resource preparation results.
  • S83 Send the first feedback information to the first entity.
  • the method allows the pre-migration service entity (first entity) and the post-migration service entity (second entity) to interact in advance with the admission control of all UEs under the mobile node (third entity) before performing UE migration or handover.
  • Related information and/or resource request related information so that the target entity (third entity) can perform admission control and/or resource preparation before UE migration, and/or so that the source entity (first entity) can perform admission control and/or resource preparation according to the target entity (third entity).
  • the second entity) admission result determines whether to select the target entity (second entity) as the final target of migration, thereby avoiding UE handover failure or migration failure due to insufficient resources of the target entity (second entity), and further ensuring The continuity of all migrated UE services improves user experience.
  • Figure 9 is a flow chart of yet another migration method provided by an embodiment of the present disclosure.
  • the method is executed by the second entity.
  • the method may include but is not limited to the following steps:
  • S91 Send the node migration request information of the third entity to the fourth entity, where the third entity and the terminal equipment under the third entity are provided with network access connections by the second entity.
  • the second entity determines the third entity that needs to be migrated, and the fourth entity that the third entity needs to migrate to.
  • the third entity and the terminal equipment under the third entity are provided with network access connections by the second entity.
  • the third entity can migrate to the fourth entity, and the fourth entity can also provide network access connections for the third entity and terminal devices under the third entity.
  • the third entity can move from the second entity to the fourth entity.
  • the third entity and the terminal equipment under the third entity are provided with network access connections by the second entity.
  • the second entity can obtain corresponding information from the third entity or the terminal equipment under the third entity, thereby determining the third entity that needs to be migrated. and the fourth entity to which the third entity needs to be migrated.
  • the second entity when it determines the third entity that needs to be migrated and the fourth entity that the third entity needs to migrate to, it may send node migration request information to the fourth entity.
  • the fourth entity when the fourth entity receives the node migration request information sent by the second entity, the fourth entity may generate the second feedback information and send it to the second entity.
  • the second feedback information may include the results of admission control and/or resource preparation in the fourth entity, so that the second entity can learn the results of admission control and/or resource preparation in the fourth entity, and, On the basis of knowing the business needs of the third entity and the terminal equipment under the third entity, it can be determined whether and/or the extent to which the fourth entity can meet the business needs of the third entity and the terminal equipment under the third entity. . Thus, when it is determined that the business requirements of the third entity and the terminal equipment under the third entity are met, a migration strategy can be generated and/or migration can be performed to avoid terminal equipment migration failure or handover failure and improve user experience.
  • the method allows the pre-migration service entity (second entity) and the post-migration service entity (fourth entity) to interact in advance with the admission control of all UEs under the mobile node (third entity) before performing UE migration or handover.
  • Related information and/or resource request related information so that the target entity (the fourth entity) can perform admission control and/or resource preparation before the UE migrates, and/or so that the source entity (the second entity) can perform admission control and/or resource preparation according to the target entity (the second entity).
  • the admission result of the four entities (four entities) determines whether to select the target entity (fourth entity) as the final target of migration, thereby avoiding UE handover failure or migration failure due to insufficient resources of the target entity (fourth entity), and further ensuring The continuity of all migrated UE services improves user experience.
  • the second entity sends node migration request information to the fourth entity.
  • the second entity and the fourth entity may be a core network, a base station, gNB-CU, gNB-DU, gNB-CU-CP or gNB-CU-UP.
  • the second entity and the fourth entity are base stations and have IAB functions, such as IAB-donor or IAB-donor-CU or IAB-donor-CU-CP, and the node migration request information needs to request migration.
  • the third entity can be an IAB node, and the IAB node can be mobile, such as mobile IAB.
  • the second entity and the fourth entity may be satellites with base station functions or partial base station functions
  • the third entity that needs to request migration in the node migration request information is a satellite with base station functions or partial base station functions.
  • the second entity and the fourth entity are base stations, gNB-CU, gNB-CU-CP, or satellites with base station functions.
  • the node migration request information may be provided by XnAP (Xn Application Protocol, Xn Interface Application Protocol) ) message transmission.
  • the second entity is a base station, gNB-CU, gNB-CU-CP or a satellite with base station function
  • the fourth entity is a core network, such as AMF (access and mobility management function), access and Mobility management function
  • node migration request information can be transmitted by NGAP (NG Application Protocol, NG Application Protocol) message.
  • NGAP message can be Handover Required message (Handover Required message), Migration Required message (Migration Required message), IAB Migration Required message (IAB Migration Required message) or Group Handover Required message (Group Handover Required message), etc.
  • the second entity is a core network
  • the fourth entity is a base station, gNB-CU, gNB-CU-CP, or a satellite with base station functions
  • the node migration request information may be transmitted by an NGAP message. It can be a handover request message (Handover Request message), a migration request message (Migration Request message), an IAB migration request message (IAB Migration Request message) or a group handover request message (Group Handover Request message), etc.
  • the node migration request information of the third entity includes at least one of the following:
  • the second entity sends the node migration request information of the third entity to the fourth entity, and may send information indicating the node migration mode to the fourth entity.
  • the second entity sends the node migration request information of the third entity to the fourth entity, and may send information for node migration admission control to the fourth entity.
  • the second entity sends the node migration request information of the third entity to the fourth entity, and may send information indicating the node migration mode and information for node migration admission control to the fourth entity.
  • the information used to indicate the node migration mode may be implicit or explicit, and the fourth entity may consider or prepare resources for the migrated node based on the information used to indicate the node migration mode.
  • the information used to indicate the node migration mode may be partial migration, complete migration, etc.; in another exemplary embodiment, the information used to indicate the node migration mode may be to indicate specific node functions that need to be migrated, for example , IAB-MT, IAB-DU, IAB-node, etc.; in another exemplary embodiment, the information used to indicate the node migration mode is implicitly indicated, for example, when the node migration request information of the third entity includes IAB -DU related information indicates complete migration, otherwise, it indicates partial migration. It should be understood that the above are only examples, and the information used to indicate the node migration mode is not limited thereto.
  • the information used for node migration access control includes the information required for access control for complete migration (ie, IAB node migration or complete migration).
  • the fourth entity may consider or perform based on the information used for node migration access control. Admission control, and feedback admission control and/or resource preparation information to the second entity.
  • the fourth entity performs different actions taking into account the information indicating the node migration mode. For example, if it is a complete migration, the fourth entity needs to consider performing admission control and/or preparing corresponding resources for the migration node (i.e., the third entity) and all UEs under the migration node; if it is a partial migration, the fourth entity only needs to Consider some business requirements in the migrated node for admission control and/or access resources.
  • the information used for node migration admission control includes at least one of the following:
  • the second entity sends the node migration request information of the third entity to the fourth entity, and may send relevant information of the terminal device served by the third entity to the fourth entity.
  • the second entity sends the node migration request information of the third entity to the fourth entity, and may send relevant information about services supported by the third entity to the fourth entity.
  • the second entity sends the node migration request information of the third entity to the fourth entity, and may send to the fourth entity related information about the terminal device served by the third entity and related information about the services supported by the third entity.
  • the information related to the terminal device served by the third entity includes at least one of the following:
  • the number of terminal devices is the number of terminal devices.
  • the core network node to which the terminal device is connected;
  • PDU Packet data unit
  • the information related to the terminal equipment served by the third entity is used to indicate the information related to all terminal equipment that needs to be migrated or switched to the fourth entity.
  • the terminal equipment refers to the terminal equipment served under the third entity.
  • Information related to the terminal equipment served by the third entity can be the number of all terminal equipment under IAB-DU, the number of DRB (Data Radio Bearer, data radio bearer)/SRB (Signalling Radio Bearer, signaling radio bearer), Information such as the QoS (Quality of Service, Quality of Service) requirements of the overall or each terminal device, or specific information of each terminal device, such as information such as the core network node to which the terminal device is connected or the PDU (packet data unit) of the terminal device , packet data unit) session-related information, the fourth entity considers or performs admission control and/or resource preparation based on the relevant information of the terminal device served by the third entity.
  • the relevant information of the terminal devices served by the third entity is the number of terminal devices.
  • the relevant information of the terminal device served by the third entity is the number of data radio bearer DRBs.
  • the relevant information about the terminal equipment served by the third entity is the number of signaling radio bearer SRBs.
  • the relevant information of the terminal devices served by the third entity is the service quality QoS requirement of each terminal device.
  • the relevant information about the terminal devices served by the third entity is the service quality QoS requirements of all terminal devices.
  • the relevant information of the terminal device served by the third entity is the core network node to which the terminal device is connected.
  • the relevant information of the terminal device served by the third entity is the packet data unit (PDU) session information of the terminal device.
  • PDU packet data unit
  • the information related to services supported by the third entity includes one or more service configuration items; wherein the service configuration items include service index, service configuration file, and backhaul BH related configuration.
  • the relevant information of the services supported by the third entity is used to indicate the relevant information of the services supported on the node requesting migration (third entity).
  • the service configuration on the IAB-DU which may include a
  • each configuration project can include a business index, business configuration file (traffic profile), BH ((Backhaul, returnhaul)) related configuration.
  • the business configuration file includes at least one of the following:
  • the service configuration file includes user plane UP (user plane, user plane) service.
  • the service configuration file includes control plane CP (control plane, control plane) services.
  • the service configuration file includes QoS requirements.
  • the service configuration file includes UP services and QoS requirements.
  • the service configuration file includes CP services and QoS requirements.
  • relevant information about the services supported by the third entity is sent in the first step of migration, such as during the IAB-MT migration process. This allows the fourth entity to perform service-related admission control and/or Resource preparation improves the success rate of migration and ensures user business experience.
  • the fourth entity considers or prepares resources for the third entity after migration based on relevant information about the services supported by the third entity, including but not limited to adding or modifying the BH RLC (BackHaul Radio) after IAB-node migration.
  • Link Control wireless link control of the backhaul link) channel, IP address and/or BAP (backhaul adaptation protocol, backhaul adaptation protocol layer) configuration, and generates second feedback information including resource preparation status, to the third
  • the two entities send second feedback information.
  • the fourth entity sends second feedback information to the second entity.
  • the second entity and the fourth entity are base stations, gNB-CU, gNB-CU-CP, or satellites with base station functions.
  • the second feedback information may be transmitted by an XnAP message, and the XnAP message may be a handover request confirmation message.
  • Handover Request Acknowledge message Migration Request Response message (Migration Request Response message), IAB Migration Response message (IAB Migration Response message), IAB Migration failure message (IAB Migration failure message) or Group Handover Request Acknowledge message (Group Handover Request Acknowledge message) etc.
  • the second entity is a base station, gNB-CU, gNB-CU-CP or a satellite with base station function
  • the fourth entity is a core network, such as AMF
  • the second feedback information may be transmitted by an NGAP message.
  • NGAP messages can be handover command messages (Handover Command message), migration command messages (Migration Command message), IAB migration command messages (IAB Migration Command message) or group handover command messages (Group Handover Command message), etc.
  • the second entity is a core network
  • the fourth entity is a base station, gNB-CU, gNB-CU-CP, or a satellite with base station functions.
  • the second feedback information may be transmitted by an NGAP message.
  • the NGAP message It can be Handover Request Acknowledge message, Migration Response message, IAB Migration Response message, IAB Migration failure message, or Group switching feedback message. Handover Response message) etc. It should be understood that the above are only examples, and the second entity, the fourth entity, and the second feedback information are not limited thereto.
  • the fourth entity sends second feedback information to the second entity.
  • the second feedback information is the node migration request information of the third entity, the fourth entity resource status, and the fourth entity's resource status sent by the fourth entity based on the second entity.
  • the second feedback information may include information related to feedback of node migration admission control and/or resource preparation results.
  • the second feedback information includes at least one of the following:
  • the fourth entity when the fourth entity receives the node migration request information of the third entity sent by the second entity, the fourth entity may generate the second feedback information and send it to the second entity.
  • the fourth entity sends information about the admission control result of the terminal device to the second entity.
  • the fourth entity sends the information of the service admission control result to the second entity.
  • the fourth entity sends resource preparation information to the second entity.
  • the information about the admission control result of the terminal device is used to indicate to the second entity, if the node requesting migration (the third entity) migrates to the fourth entity, whether the UE under the third entity is admitted successfully. , information related to successful access, and/or information related to failed access, etc.
  • the information about the admission control result of the terminal device includes at least one of the following:
  • the fourth entity sends information about the admission control result of the terminal device to the second entity, and may send admission success information to the second entity.
  • the fourth entity sends information about the admission control result of the terminal device to the second entity, and may send admission failure information to the second entity.
  • the fourth entity sends information about the admission control result of the terminal device to the second entity, and may send admission success information and admission failure information to the second entity.
  • the admission success information includes at least one of the following:
  • the number of access terminal devices is the number of access terminal devices.
  • the admission success information may be an indication, a percentage, a specific number, or specific UE information.
  • the second entity may consider the admission success information to make a migration decision and/or a migration strategy decision. .
  • the admission success information may be information indicating the number of admitted UEs.
  • the admission success information may be information indicating the number of admitted DRBs/SRBs.
  • the admission success information may be information used to indicate the QoS supported after migration, such as the maximum supported transmission bandwidth and other information.
  • the admission success information may be information related to indicating UEs permitted to migrate, for example, it may be a list of UEs permitted to migrate, which includes the ID of each UE and UE-specific information.
  • the admission success information may be the number of admitted terminal devices.
  • the admission success information may be a proportion of the admission terminal equipment.
  • the admission success information may be the number of admitted data radio bearer DRBs.
  • the admission success information may be the number of admission signaling radio bearer SRBs.
  • the admission success information may be QoS information supported after migration.
  • the admission success information may be the maximum transmission bandwidth supported after migration.
  • the admission success information may be information about the terminal device that is allowed to migrate.
  • the fourth entity sends information about the admission control result of the terminal device to the second entity, and may send admission failure information to the second entity.
  • the admission failure information may be an indication or specific UE information of admission failure, such as UE ID.
  • the service admission control result includes at least one of the following:
  • the service admission control result indicates to the second entity, if the node requesting migration is migrated to the fourth entity, whether the service addition requested by the node requesting migration (third entity) is successful, for example, it may include Business indexes added successfully and/or business indexes added failed, etc.
  • the service admission control result is a service index with successful admission.
  • the service admission control result is the service index of failed admission.
  • the service admission control results are the service index of successful admission and the service index of failed admission.
  • the resource preparation information includes: backhaul BH configuration information.
  • the resource preparation information may include, for example, BH configuration information.
  • the second entity may further forward the BH configuration information to the IAB node (third entity) requesting migration, so that the migrating IAB node (third entity) can perform the migration.
  • IAB-DU migration resource preparation information can be included in the RRC (radio resource control, radio resource control) reconfiguration (RRC Reconfiguration) message for transmission.
  • RRC radio resource control, radio resource control
  • the second entity receives the second feedback information, and may make a migration decision, generate a migration policy, and/or execute the migration based on or considering the second feedback information.
  • the second entity may continue the migration process; if only some UEs are admitted successfully, the second entity may consider that some UEs that are admitted successfully follow the third entity. Perform migration and continue the migration process. UEs that have not been admitted successfully can switch directly to other base stations without following the third entity to migrate to ensure business continuity; if the second entity receives multiple messages from other entities, (including the fourth entity), the second entity can select a target entity that has successful admission or has a higher admission success rate or provides a better experience for the UE for migration, and continues the migration process. Therefore, regardless of whether the resources of the target entity are sufficient, the second entity can consider or select the optimal target entity or migration strategy for migration based on the second feedback information to avoid migration failure or UE handover failure or service quality degradation. , to ensure user experience.
  • the second entity is the source integrated access and backhaul IAB host (source IAB-donor)
  • the fourth entity is the target IAB host (target IAB-donor)
  • the third entity is the IAB node.
  • IAB node In related technology, the location of IAB node (IAB node) is fixed. In order to increase the robustness of IAB, IAB-MT can be migrated to another IAB-donor-CU, and the collocated IAB-DU and its descendant nodes are IAB-DU(s) maintains an F1 connection with the initial IAB-donor-CU. This migration is called Inter-donor partial migration. After the inter-donor partial migration, the F1 traffic of IAB-DU and its descendant nodes will be routed through the BAP layer of the IAB topology to which IAB-MT is migrated.
  • IAB node migration that is, one or more UEs served under IAB-MT, IAB-DU and IAB nodes must be supported. Need to migrate from source IAB-donor-CU (source IAB-donor) to target IAB-donor-CU (target IAB-donor). Among them, the approximate sequence of IAB node migration is as follows:
  • the first step is IAB-MT migration
  • the second step is IAB-DU migration
  • the third step is to migrate the UE under the IAB node.
  • the first and second steps can exchange the order, or the second step can be divided into two stages, occurring before and after IAB-MT migration.
  • the migration of UE must be completed after the migration of IAB-DU.
  • the admission control of multiple UEs is not considered in the first and/or second steps of the interaction between the source IAB-donor and the target IAB-donor. If in the first step The resources of the selected target IAB-donor are not enough to support the service needs of all UEs after migration. After the first and second steps are completed, multiple UEs may fail in the admission control in the third step, resulting in UE migration. Failure or handover failure will eventually interrupt UE services and affect user experience.
  • UE migration can be performed Or before handover, let the source IAB-donor and the target IAB-donor exchange information related to the admission control and/or resource request of all UEs under the IAB node in advance, so that the target IAB-donor can make preparations before the UE migrates.
  • Admission control and/or resource preparation and/or so that the source IAB-donor can determine whether to select the target IAB-donor as the final target of migration based on the admission results of the target IAB-donor, thus avoiding problems caused by insufficient resources of the target IAB-donor.
  • UE handover failure or migration failure thereby further ensuring the continuity of all migrated UE services and improving user experience.
  • S91 and S92 can be implemented alone, or can be implemented in combination with any other step in the embodiment of the present disclosure, for example, in combination with S71 and S72 in the embodiment of the present disclosure and/or S81 to S83 are implemented together, and the embodiment of the present disclosure does not limit this.
  • the methods provided by the embodiments of the present disclosure are introduced from the perspectives of network side equipment and terminal equipment respectively.
  • the network side device and the terminal device may include a hardware structure and a software module to implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • a certain function among the above functions can be executed by a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG. 10 is a schematic structural diagram of a communication device 1 provided by an embodiment of the present disclosure.
  • the communication device 1 shown in FIG. 10 may include a transceiver module 11 and a processing module 12.
  • the transceiver module may include a sending module and/or a receiving module.
  • the sending module is used to implement the sending function
  • the receiving module is used to implement the receiving function.
  • the transceiving module may implement the sending function and/or the receiving function.
  • Communication device 1 is the first entity:
  • the communication device 1 includes: a transceiver module 11 and a processing module 12 .
  • the transceiver module 11 is configured to send the migration request information of the third entity to the second entity, wherein the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • the transceiver module 11 is also configured to receive the first feedback information sent by the second entity.
  • the processing module 12 is configured to perform at least one of the following according to the first feedback information:
  • the migration request information of the third entity includes at least one of the following:
  • the information used for node migration admission control includes at least one of the following:
  • the information related to the terminal device served by the third entity includes at least one of the following:
  • the number of terminal devices is the number of terminal devices.
  • the core network node to which the terminal device is connected;
  • PDU Packet data unit
  • the information related to services supported by the third entity includes one or more service configuration items; wherein the service configuration items include service index, service configuration file, and backhaul BH related configuration.
  • the business configuration file includes at least one of the following:
  • the first feedback information includes at least one of the following:
  • the information about the admission control result of the terminal device includes at least one of the following:
  • the admission success information includes at least one of the following:
  • the number of access terminal devices is the number of access terminal devices.
  • the service admission control result includes at least one of the following:
  • the resource preparation information includes: backhaul BH configuration information.
  • the first entity is the source integrated access and backhaul IAB host
  • the second entity is the target IAB host
  • the third entity is the IAB node
  • Communication device 1 is the second entity:
  • the communication device 1 includes: a transceiver module 11 and a processing module 12 .
  • the transceiver module 11 is configured to receive the migration request information of the third entity sent by the first entity, wherein the third entity and the terminal equipment under the third entity are provided with network access connections by the first entity.
  • the transceiver module 11 is also configured to send the first feedback information to the first entity.
  • the processing module 12 is configured to perform node migration admission control and/or prepare resources according to the migration request information of the third entity to generate the first feedback information.
  • the transceiver module 11 is also configured to send the node migration request information of the third entity to the fourth entity, wherein the third entity and the terminal devices under the third entity are provided with network access connections by the second entity. .
  • the transceiver module 11 is also configured to receive the second feedback information sent by the fourth entity.
  • the third entity's migration request information and/or node migration request information includes at least one of the following:
  • the information used for node migration admission control includes at least one of the following:
  • the information related to the terminal device served by the third entity includes at least one of the following:
  • the number of terminal devices is the number of terminal devices.
  • the core network node to which the terminal device is connected;
  • PDU Packet data unit
  • the information related to services supported by the third entity includes one or more service configuration items; wherein the service configuration items include service index, service configuration file, and backhaul BH related configuration.
  • the business configuration file includes at least one of the following:
  • the first feedback information and/or the second feedback information includes at least one of the following:
  • the information about the admission control result of the terminal device includes at least one of the following:
  • the admission success information includes at least one of the following:
  • the number of access terminal devices is the number of access terminal devices.
  • the service admission control result includes at least one of the following:
  • the resource preparation information includes: backhaul BH configuration information.
  • the first entity is the source integrated access and backhaul IAB host
  • the second entity is the target IAB host
  • the third entity is the IAB node
  • the communication device 1 provided in the above embodiments of the present disclosure achieves the same or similar beneficial effects as the migration methods provided in some of the above embodiments, and will not be described again here.
  • FIG. 11 is a schematic structural diagram of another communication device 1000 provided by an embodiment of the present disclosure.
  • the communication device 1000 may be a first entity, a second entity, a chip, a chip system, a processor, etc. that supports the first entity to implement the above method, or a chip, a chip system, or a processor that supports the second entity to implement the above method.
  • Chip system, or processor, etc. The communication device 1000 can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.
  • Communication device 1000 may include one or more processors 1001.
  • the processor 1001 may be a general-purpose processor or a special-purpose processor, or the like.
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processor can be used to process communication devices (such as first entity, second entity, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.) Control, execute computer programs, and process data from computer programs.
  • the communication device 1000 may also include one or more memories 1002, on which a computer program 1004 may be stored.
  • the memory 1002 executes the computer program 1004, so that the communication device 1000 performs the method described in the above method embodiment.
  • the memory 1002 may also store data.
  • the communication device 1000 and the memory 1002 can be provided separately or integrated together.
  • the communication device 1000 may also include a transceiver 1005 and an antenna 1006.
  • the transceiver 1005 may be called a transceiver unit, a transceiver, a transceiver circuit, etc., and is used to implement transceiver functions.
  • the transceiver 1005 may include a receiver and a transmitter.
  • the receiver may be called a receiver or a receiving circuit, etc., used to implement the receiving function;
  • the transmitter may be called a transmitter, a transmitting circuit, etc., used to implement the transmitting function.
  • the communication device 1000 may also include one or more interface circuits 1007.
  • the interface circuit 1007 is used to receive code instructions and transmit them to the processor 1001 .
  • the processor 1001 executes the code instructions to cause the communication device 1000 to perform the method described in the above method embodiment.
  • the communication device 1000 is the first entity: the processor 1001 is used to perform S63 in Figure 6; the transceiver 1005 is used to perform S51 and S52 in Figure 5; and S61 and S62 in Figure 6.
  • the communication device 1000 is the second entity: the transceiver 1005 is used to perform S71 and S72 in Figure 7; S81 and S83 in Figure 8; S91 and S92 in Figure 9; and the processor 1001 is used to perform S82 in Figure 8.
  • the processor 1001 may include a transceiver for implementing receiving and transmitting functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuits, interfaces or interface circuits used to implement the receiving and transmitting functions can be separate or integrated together.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing codes/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transfer.
  • the processor 1001 may store a computer program 1003, and the computer program 1003 runs on the processor 1001, causing the communication device 1000 to perform the method described in the above method embodiment.
  • the computer program 1003 may be solidified in the processor 1001, in which case the processor 1001 may be implemented by hardware.
  • the communication device 1000 may include a circuit, and the circuit may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the processors and transceivers described in this disclosure may be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board (PCB), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS n-type metal oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device in the description of the above embodiments may be the first entity or the second entity, but the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 11 .
  • the communication device may be a stand-alone device or may be part of a larger device.
  • the communication device may be:
  • the IC collection may also include storage components for storing data and computer programs;
  • FIG. 12 is a structural diagram of a chip provided in an embodiment of the present disclosure.
  • Chip 1100 includes processor 1101 and interface 1103.
  • the number of processors 1101 may be one or more, and the number of interfaces 1103 may be multiple.
  • Interface 1103, used to receive code instructions and transmit them to the processor.
  • the processor 1101 is configured to run code instructions to perform the migration method as described in some of the above embodiments.
  • Interface 1103, used to receive code instructions and transmit them to the processor.
  • the processor 1101 is configured to run code instructions to perform the migration method as described in some of the above embodiments.
  • the chip 1100 also includes a memory 1102, which is used to store necessary computer programs and data.
  • Embodiments of the present disclosure also provide a migration system.
  • the system includes a communication device as a first entity and a communication device as a second entity in the aforementioned embodiment of FIG. 10 .
  • the system includes a communication device as the first entity in the aforementioned embodiment of FIG. 11 .
  • the communication device of the entity and the communication device as the second entity.
  • the present disclosure also provides a readable storage medium on which instructions are stored, and when the instructions are executed by a computer, the functions of any of the above method embodiments are implemented.
  • the present disclosure also provides a computer program product, which, when executed by a computer, implements the functions of any of the above method embodiments.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer programs.
  • the computer program When the computer program is loaded and executed on a computer, the processes or functions described in accordance with the embodiments of the present disclosure are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program may be stored in or transferred from one computer-readable storage medium to another, for example, the computer program may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the usable media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks, SSD)) etc.
  • magnetic media e.g., floppy disks, hard disks, magnetic tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks, SSD
  • At least one in the present disclosure can also be described as one or more, and the plurality can be two, three, four or more, and the present disclosure is not limited.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D” etc.
  • the technical features described in “first”, “second”, “third”, “A”, “B”, “C” and “D” are in no particular order or order.
  • each table in this disclosure can be configured or predefined.
  • the values of the information in each table are only examples and can be configured as other values, which is not limited by this disclosure.
  • it is not necessarily required to configure all the correspondences shown in each table.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc.
  • the names of the parameters shown in the titles of the above tables may also be other names understandable by the communication device, and the values or expressions of the parameters may also be other values or expressions understandable by the communication device.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables. wait.
  • Predefinition in this disclosure may be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-burning.

Landscapes

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

Abstract

Des modes de réalisation de la présente divulgation concernent un procédé et un dispositif de migration, qui peuvent être appliqués au domaine technique des communications. Le procédé exécuté par une première entité consiste à : envoyer les informations de demande de migration d'une troisième entité à une deuxième entité, la troisième entité et un dispositif terminal dépendant de la troisième entité accédant à un réseau fourni par la première entité ; et recevoir des premières informations de rétroaction envoyées par la deuxième entité. De cette manière, des défaillances de migration ou des défaillances de commutation du dispositif terminal peuvent être évitées, et l'expérience d'utilisateur est améliorée.
PCT/CN2022/098276 2022-06-10 2022-06-10 Procédé et dispositif de migration WO2023236224A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/098276 WO2023236224A1 (fr) 2022-06-10 2022-06-10 Procédé et dispositif de migration
CN202280002085.XA CN117597889A (zh) 2022-06-10 2022-06-10 迁移方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/098276 WO2023236224A1 (fr) 2022-06-10 2022-06-10 Procédé et dispositif de migration

Publications (1)

Publication Number Publication Date
WO2023236224A1 true WO2023236224A1 (fr) 2023-12-14

Family

ID=89117440

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/098276 WO2023236224A1 (fr) 2022-06-10 2022-06-10 Procédé et dispositif de migration

Country Status (2)

Country Link
CN (1) CN117597889A (fr)
WO (1) WO2023236224A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113747521A (zh) * 2020-05-29 2021-12-03 维沃移动通信有限公司 网络切换方法、装置、通信设备及系统
CN114095949A (zh) * 2020-07-31 2022-02-25 大唐移动通信设备有限公司 从源网元向目标网元迁移过程中配置信息传输方法及装置
CN114390602A (zh) * 2020-10-16 2022-04-22 大唐移动通信设备有限公司 连接建立方法、装置、设备及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113747521A (zh) * 2020-05-29 2021-12-03 维沃移动通信有限公司 网络切换方法、装置、通信设备及系统
CN114095949A (zh) * 2020-07-31 2022-02-25 大唐移动通信设备有限公司 从源网元向目标网元迁移过程中配置信息传输方法及装置
CN114390602A (zh) * 2020-10-16 2022-04-22 大唐移动通信设备有限公司 连接建立方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN117597889A (zh) 2024-02-23

Similar Documents

Publication Publication Date Title
CN110999520B (zh) 无线接入网节点、核心网节点和无线终端及其方法
US20230189091A1 (en) Iab node configuration method and communication apparatus
US10349459B2 (en) Relay node RN, donor eNodeB DeNB and communication method
WO2022082679A1 (fr) Procédé de communication et dispositif associé
CN114600508A (zh) Iab节点双连接建立的方法和通信装置
WO2019192458A1 (fr) Procédé et appareil de communication
WO2019242712A1 (fr) Procédé d'interaction de capacités et dispositif associé
WO2021238882A1 (fr) Procédé et dispositif d'implémentation de continuité de service
US20230262452A1 (en) Communication Method for Terminal and Communication Apparatus
WO2022033543A1 (fr) Procédé de communication de relais, et appareil de communication
CN110622578B (zh) 控制数据复制的方法及相关设备
WO2024065127A1 (fr) Procédé de commande de transmission d'informations de dispositif relais et appareil associé
WO2023236224A1 (fr) Procédé et dispositif de migration
US11979788B2 (en) Communication method and apparatus used in inter-communications system move scenario
WO2020030059A1 (fr) Procédé et appareil d'indication d'informations
CN113473534A (zh) 无线接入能力的上报方法、装置及系统
WO2023246746A1 (fr) Procédé de communication et dispositif associé
WO2022143090A1 (fr) Procédé et appareil de communication
WO2021244078A1 (fr) Procédé et appareil de transfert cellulaire
WO2022233011A1 (fr) Procédé d'établissement de connexion, et dispositif terminal
WO2023220954A1 (fr) Procédé de communication, dispositif terminal et dispositif de réseau
WO2023220941A1 (fr) Procédé de transmission d'informations de transfert de données et appareil
WO2023015950A1 (fr) Procédé de communication et appareil de communication
WO2023193275A1 (fr) Procédé d'annulation de configuration cpc ou de configuration cpa et appareil associé
WO2022237763A1 (fr) Procédé et appareil de surveillance de canal, terminal et dispositif de réseau

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280002085.X

Country of ref document: CN

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

Ref document number: 22945365

Country of ref document: EP

Kind code of ref document: A1