CN117597889A

CN117597889A - Migration method and migration device

Info

Publication number: CN117597889A
Application number: CN202280002085.XA
Authority: CN
Inventors: 李艳华
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2022-06-10
Filing date: 2022-06-10
Publication date: 2024-02-23
Also published as: WO2023236224A1

Abstract

The embodiment of the disclosure discloses a migration method and a migration device, which can be applied to the technical field of communication, wherein the method executed by a first entity comprises the following steps: the migration request information of a third entity is sent to a second entity, wherein the third entity and terminal equipment under the third entity are connected by a first entity in a network access manner; and receiving the first feedback information sent by the second entity. Therefore, the migration failure or the switching failure of the terminal equipment can be avoided, and the user experience is improved.

Description

Migration method and migration device

Technical Field

The disclosure relates to the technical field of communication, and in particular relates to a migration method and device.

Background

In the related art, the first entity and the second entity may provide network access connection for the third entity and the terminal device under the third entity, and when the third entity and/or the terminal device under the third entity needs to migrate from the network access connection provided by the first entity to the network access connection provided by the second entity, the second entity may not support the service requirement of the terminal device under the third entity, and if migration is directly performed, migration failure or handover failure of the terminal device may be caused, so that user experience is affected.

Disclosure of Invention

The embodiment of the disclosure provides a migration method and a migration device, so as to avoid migration failure or switching failure of terminal equipment and improve user experience.

In a first aspect, embodiments of the present disclosure provide a migration method, the method performed by a first entity, the method comprising: transmitting migration request information of a third entity to a second entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity; and receiving the first feedback information sent by the second entity.

In the technical scheme, a first entity sends migration request information of a third entity to a second entity, wherein the third entity and terminal equipment under the third entity are connected by the first entity in a network access manner; and receiving the first feedback information sent by the second entity. The first entity can consider the first feedback information to determine a migration strategy, execute migration and the like, so that migration failure or switching failure of the terminal equipment can be avoided, and user experience is improved.

In a second aspect, embodiments of the present disclosure provide another migration method, the method performed by a second entity, the method comprising: receiving migration request information of a third entity sent by a first entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity; and sending first feedback information to the first entity.

In a third aspect, an embodiment of the present disclosure provides a communication apparatus, where the communication apparatus has a function of implementing part or all of the network side device in the method described in the first aspect, for example, a function of the communication apparatus may be provided with a function in part or all of the embodiments of the present disclosure, or may be provided with a function of implementing any one of the embodiments of the present disclosure separately. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

In one implementation, the communication device may include a transceiver module and a processing module in a structure configured to support the communication device to perform the corresponding functions in the method. The transceiver module is used for supporting communication between the communication device and other equipment. The communication device may further comprise a memory module for coupling with the transceiver module and the processing module, which holds the necessary computer programs and data of the communication device.

In one implementation, the communication device includes: the receiving and transmitting module is configured to send migration request information of a third entity to the second entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity; the transceiver module is further configured to receive first feedback information sent by the second entity.

In a fourth aspect, an embodiment of the present disclosure provides another communication apparatus having a function of implementing part or all of the terminal device in the method example described in the second aspect, for example, a function of the communication apparatus may be provided with a function in part or all of the embodiments of the present disclosure, or may be provided with a function of implementing any one of the embodiments of the present disclosure separately. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

In one implementation, the communication device may include a transceiver module and a processing module in a structure configured to support the communication device to perform the corresponding functions of the method. The transceiver module is used for supporting communication between the communication device and other equipment. The communication device may further comprise a memory module for coupling with the transceiver module and the processing module, which holds the necessary computer programs and data of the communication device.

In one implementation, the communication device includes: the receiving and transmitting module is configured to receive migration request information of a third entity sent by a first entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity; the transceiver module is further configured to send first feedback information to the first entity.

In a fifth aspect, embodiments of the present disclosure provide a communication device comprising a processor, which when invoking a computer program in memory, performs the method of the first aspect described above.

In a sixth aspect, embodiments of the present disclosure provide a communication device comprising a processor that, when invoking a computer program in memory, performs the method of the second aspect described above.

In a seventh aspect, embodiments of the present disclosure provide a communication apparatus comprising a processor and a memory, the memory having a computer program stored therein; the processor executes the computer program stored in the memory to cause the communication device to perform the method of the first aspect described above.

In an eighth aspect, embodiments of the present disclosure provide a communication apparatus comprising a processor and a memory, the memory having a computer program stored therein; the processor executes the computer program stored in the memory to cause the communication device to perform the method of the second aspect described above.

In a ninth aspect, embodiments of the present disclosure provide a communications apparatus comprising a processor and interface circuitry for receiving code instructions and transmitting to the processor, the processor being configured to execute the code instructions to cause the apparatus to perform the method of the first aspect described above.

In a tenth aspect, embodiments of the present disclosure provide a communications device comprising a processor and interface circuitry for receiving code instructions and transmitting to the processor, the processor being configured to execute the code instructions to cause the device to perform the method of the second aspect described above.

In an eleventh aspect, an embodiment of the disclosure provides a migration system, where the system includes a communication device according to the third aspect and a communication device according to the fourth aspect, or where the system includes a communication device according to the fifth aspect and a communication device according to the sixth aspect, or where the system includes a communication device according to the seventh aspect and a communication device according to the eighth aspect, or where the system includes a communication device according to the ninth aspect and a communication device according to the tenth aspect.

In a twelfth aspect, an embodiment of the present invention provides a computer readable storage medium, configured to store instructions for use by the first entity, where the instructions, when executed, cause the first entity to perform the method of the first aspect.

In a thirteenth aspect, an embodiment of the present invention provides a readable storage medium, configured to store instructions for use by the second entity, where the instructions, when executed, cause the second entity to perform the method according to the second aspect.

In a fourteenth aspect, the present disclosure also provides a computer program product comprising a computer program which, when run on a computer, causes the computer to perform the method of the first aspect described above.

In a fifteenth aspect, the present disclosure also provides a computer program product comprising a computer program which, when run on a computer, causes the computer to perform the method of the second aspect described above.

In a sixteenth aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a first entity to implement the functionality referred to in the first aspect, e.g. to determine or process at least one of data and information referred to in the above-mentioned method. In one possible design, the system-on-chip further includes a memory to hold the computer programs and data necessary for the first entity. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

In a seventeenth aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a second entity to implement the functionality referred to in the second aspect, e.g. to determine or process at least one of data and information referred to in the above-described method. In one possible design, the system-on-chip further includes a memory to hold computer programs and data necessary for the second entity. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

In an eighteenth aspect, the present disclosure provides a computer program which, when run on a computer, causes the computer to perform the method of the first aspect described above.

In a nineteenth aspect, the present disclosure provides a computer program which, when run on a computer, causes the computer to perform the method of the second aspect described above.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background of the present disclosure, the following description will explain the drawings that are required to be used in the embodiments or the background of the present disclosure.

Fig. 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 embodiments of the present disclosure;

fig. 3 is an architecture diagram of a communication system provided by an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of a first entity, a second entity, or a third entity according to an embodiment of the present disclosure;

FIG. 5 is a flow chart of a migration method provided by an embodiment of the present disclosure;

FIG. 6 is a flow chart of another migration method provided by an embodiment of the present disclosure;

FIG. 7 is a flow chart of yet another migration method provided by an embodiment of the present disclosure;

FIG. 8 is a flow chart of yet another migration method provided by an embodiment of the present disclosure;

Fig. 9 is a block diagram of a communication device provided by an embodiment of the present disclosure;

fig. 10 is a block diagram of another communication device provided by an embodiment of the present disclosure;

fig. 11 is a schematic structural diagram of a chip according to an embodiment of the disclosure.

Detailed Description

To facilitate an understanding of the present disclosure, some concepts related to the embodiments of the present disclosure are briefly described herein.

The embodiments of the present disclosure may be applied to various communication systems, such as a wireless local area network system (wireless localarea network, WLAN), a narrowband internet of things system (NB-IoT), a global system for mobile communications (global system for mobile communications, GSM), an enhanced data rates for GSM evolution system (enhanced data rate for GSM evolution, EDGE), a wideband code division multiple access system (widebandcode division multiple access, WCDMA), a code division multiple access 2000 system (code division multipleaccess, CDMA 2000), a time division synchronous code division multiple access system (time division-synchronization codedivision multiple access, TD-SCDMA), a long term evolution system (long term evolution, LTE), satellite communications, a fifth generation (5th generation,5G) system, or new communication systems that will emerge in the future, etc.

The terminal devices referred to in the embodiments of the present disclosure may include various handheld devices, vehicle mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities. The terminal may be a Mobile Station (MS), a subscriber Unit (UE), a User Equipment (UE), a cellular phone (cellular phone), a smart phone (smart phone), a wireless data card, a personal digital assistant (personal digital assistant, PDA) computer, a tablet computer, a wireless modem (modem), a handheld device (handset), a laptop computer (laptop computer), a machine type communication (machinetype communication, MTC) terminal, etc.

1. The IAB (Integrated access and backhaul) supports wireless access and backhaul of the millimeter wave base station, so that the deployment requirement of newly-added optical fibers can be effectively reduced when a dense network is deployed, and wireless relay in the NG-RAN (next generation radio access network, next generation wireless access network) is possible. Wherein, the relay node is also called as an IAB node (IAB-node) and supports wireless access and backhaul through NR (New Radio). The home node returned by the network side NR is called an IAB home node (IAB-donor), and is a gNB (NR node b) with an IAB function added.

In the current standard of 5G, considering that the coverage area of the high frequency band is small, in order to ensure the coverage performance of the network, multi-hop networking can be adopted in the IAB network. Considering the requirement of service transmission reliability, the IAB node can be enabled to support dual connection (dual connectivity, DC) or multiple connection (multi-connectivity) to cope with the possible abnormal situations of the backhaul link, such as failure or congestion/congestion (blocking) or load fluctuation of the link, and the like, so as to improve the transmission reliability.

Since the IAB network supports multi-hop and multi-connection networking, there may be multiple transmission paths between a terminal device (e.g., user Equipment (UE)) and an IAB host node (IAB node). Each transmission path contains a plurality of nodes, which may include a UE, one or more IAB nodes, and an IAB node. If the IAB donor is in a form in which a Centralized Unit (CU) and a Distributed Unit (DU) are separated, the IAB donor may include an IAB-donor-DU part (donor DU) and an IAB-donor-CU (donor CU) part, etc. In the IAB network, the IAB node may provide a radio access service for the terminal device, and service data of the terminal device is transmitted to the IAB node by the IAB node through a radio backhaul link.

Wherein each IAB node treats the neighboring node for which backhaul service is provided as a parent node (or an upper node), and accordingly, each IAB node may be treated as a child node (or a lower node) of its parent node. The radio link used when a certain IAB node communicates with its child nodes is called an access link, which includes both uplink and downlink links. The uplink transmission on the access link is also referred to as uplink transmission of the access link, and the downlink transmission is also referred to as downlink transmission of the access link. The wireless link used when a certain IAB node communicates with its parent node may be referred to as a backhaul link, including both uplink and downlink links. The uplink transmission on the backhaul link is also referred to as uplink transmission of the backhaul link, and the downlink transmission is also referred to as downlink transmission of the backhaul link.

For example, in the wireless relay scenario shown in fig. 1, the parent node of the IAB node 1 is an IAB host node (i.e., IAB node), the IAB node 1 is a parent node of the IAB node 2 and the IAB node 3, the IAB node 2 and the IAB node 3 are both parent nodes of the IAB node 4, and the parent node of the IAB node 5 is the IAB node 2. Wherein, there are two available paths for data transmission between UE1 and IAB node, path 1: UE1-IAB node 4-IAB node 3-IAB node 1-IABdonor, path 2: UE1-IAB node 4-IAB node 2-IAB node 1-IAB node dor. There are three paths available for data transmission between UE2 and IAB node, path 3: UE2-IAB node 4-IAB node 3-IAB node 1-IAB node 2-IAB node 4: UE2-IAB node 4-IAB node 2-node 1-IABdonor, path 5: UE2-IAB node 5-IAB node 2-IAB node 1-IAB node dor. The uplink data packet of each UE may be transmitted to the IAB node by one or more IAB nodes, and then sent to the mobile gateway device (e.g., a user plane function (user plane function, UPF) network element in the 5G core network) by the IAB node, and the downlink data packet may be received by the IAB node from the mobile gateway device and then sent to the UE by the IAB node.

The IAB node may include, among other things, a mobile terminal (mobile termination, MT) portion and a Distributed Unit (DU) portion. When an IAB node is towards its parent node (which may be another IAB node, or IAB node), it may be considered as a user equipment, MT; when an IAB node is towards its child node (which may be another IAB node, or a terminal device), it may be regarded as a network device for providing backhaul services, i.e. DUs, for the child node.

The IAB node may be an access network element with a complete access function, or an access network element with a separation form of CU and DU, where the IAB node may be connected to a core network (e.g., 5G core,5 gc) network element serving a terminal device, and provide a wireless backhaul service for an IAB node. For ease of description, the centralized unit of IAB donor is simply referred to as a donor CU (or directly referred to as a CU), and the distributed unit of IAB donor is simply referred to as a donor DU. Where the donor CU may also be in a form where the Control Plane (CP) and User Plane (UP) are separate, e.g. a CU may consist of one CU-CP and one (or more) CU-UP. In the embodiments of the present disclosure, the IAB donor may also be referred to as an IAB host node or a host node (donor node) or a host base station (DgNB, donor gnob), which is not limited in the present disclosure.

The IAB networking scenario shown in fig. 1 is merely exemplary, and there are many other possibilities in the multi-hop and multi-connection combined IAB networking scenario, for example, the DgNB and the IAB node under another DgNB may constitute a dual connection to serve the UE, etc., which is not explicitly recited herein.

The backhaul may be performed by single-hop or multi-hop, and the IAB architecture is shown in fig. 2. The NG-RAN supports IABs by being wirelessly connected via an IAB-node to a gNB (referred to as an IAB-node, also referred to as an IAB host) capable of serving the IAB-node. The IAB-donor includes one IAB-donor-CU (IAB-host-CU) and one or more IAB-donor-DUs (IAB-host-DUs). When gNB-CU-CP and gNB-CU-UP are separated, IAB-donor may include one IAB-donor-CU-CP, multiple IAB-donor-CU-UP, and multiple IAB-donor-DU. Wherein the IAB-node connects upstream IAB-node or IAB-donor-DUs through a terminal function subset of the NR Uu interface, called IAB-MT function in the IAB-node. The IAB-node provides wireless backhaul to downstream IAB-nodes and terminals through the network functions of the NR Uu interface (the IAB-DU functions of the IAB-node).

F1-C traffic between IAB-node and IAB-donor-CU is passed back through IAB-donor-DU and optional intermediate hop IAB-node. F1-U traffic between IAB-node and IAB-donor-CU is passed back through IAB-donor-DU and optional intermediate hop IAB-node.

In order to better understand a migration method and apparatus disclosed in an embodiment of the present disclosure, a description is first given below of a communication system to which the embodiment of the present disclosure is applicable.

Fig. 3 is a schematic architecture diagram of a mobile communication system to which an embodiment of the present disclosure is applied. As shown in fig. 3, the mobile communication system includes a terminal device, at least one relay device (e.g., a first IAB node and a second IAB node in fig. 3), a radio access network device (e.g., a home node in fig. 3), and a core network device. The terminal equipment is connected with the relay equipment in a wireless mode and is connected with the wireless access network equipment through one or more relay equipment (part of terminal equipment can also be directly connected with the wireless access network equipment in a wireless mode), and the wireless access network equipment is connected with the core network equipment in a wireless or wired mode.

The wireless links between the devices can communicate through a licensed spectrum (licensed spectrum), an unlicensed spectrum (unlicensed spectrum), or both. The wireless link between devices may communicate over a frequency spectrum below 6G megahertz (GHz), over a frequency spectrum above 6GHz, and may also communicate using both a frequency spectrum below 6GHz and a frequency spectrum above 6 GHz. Embodiments of the present disclosure do not limit the spectrum resources used by the wireless link.

The core network device and the radio access network device may be separate physical devices, or the functions of the core network device and the logic functions of the radio access network device may be integrated on the same physical device, or the functions of part of the core network device and the functions of part of the radio access network device may be integrated on one physical device. The terminal device may be fixed in position or may be movable. The embodiments of the present disclosure do not limit the number of core network devices, radio access network devices, relay devices, and terminal devices included in the mobile communication system.

The radio access network device may be an access device that is accessed to the mobile communication system by a terminal device or a relay device through a wireless manner, and may be a base station NodeB, an evolved base station eNodeB, a base station gnob in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc., where the specific technology and the specific device configuration adopted by the radio access network device are not limited in the embodiments of the present disclosure.

The terminal device may also be referred to as a terminal (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc. The terminal device may be a mobile phone, a tablet (Pad), a computer with wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (AugmentedReality, AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (self-driving), a wireless terminal in teleoperation (remote medical surgery), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), etc.

The relay device may be a device that provides a wireless backhaul service, which refers to a data and/or signaling backhaul service provided over a wireless backhaul link, or a wireless access service, which refers to a data and/or signaling backhaul service provided over a wireless access link. In one aspect, a relay device may provide a wireless access service for a terminal through an Access Link (AL); on the other hand, the relay device may be connected to the access network device through a Backhaul Link (BL), so that the relay device may implement forwarding of data and/or signaling between the terminal and the access network device, and expand the coverage area of the communication system.

The relay device may have different names in different communication systems, for example, the relay device may be referred to as a relay node, or may be referred to as a wireless backhaul node or a wireless backhaul device; in a 5G system, the relay node may be referred to as an access backhaul integrated node (integrated access and backhaul node, IAB node). Of course, in future communication systems, the relay node may also have a different name, which is not limited herein. The IAB nodes mentioned in the embodiments of the present disclosure may be replaced by relay nodes.

The wireless access network device, the wireless backhaul device, and the terminal device may be deployed on land, including indoor or outdoor, handheld, or vehicle-mounted; the device can be deployed on the water surface; but also on aerial planes, balloons and satellites. The embodiment of the disclosure does not limit the application scenarios of the wireless access network device, the wireless backhaul device and the terminal device.

The first IAB node or the second IAB node in fig. 3 may be implemented by a device or may be a functional module in a device according to the embodiments of the present disclosure, which is not limited in detail. It will be appreciated that the above described functionality may be either a network element in a hardware device, or a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform), or a system on a chip. In the embodiments of the present disclosure, the chip system may be formed by a chip, and may also include a chip and other discrete devices.

For example, the means for implementing the functions of the first entity or the second entity or the third entity provided by the embodiments of the present disclosure may be implemented by the apparatus 400 in fig. 4. Fig. 4 is a schematic hardware structure of an apparatus 400 according to an embodiment of the disclosure. At least one processor 401 is included in the apparatus 400 to implement the functions of CU, DU or SN provided by the embodiments of the present disclosure. Also included in apparatus 400 may be a communication bus 402 and at least one communication interface 404. Memory 403 may also be included in apparatus 400.

In the disclosed embodiments, the processor may be a central processing unit (central processing unit, CPU), a general purpose processor, a network processor (network processor, NP), a digital signal processor (digital signalprocessing, DSP), a microprocessor, a microcontroller, a programmable logic device (programmable logic device, PLD). The processor may also be any other device having processing functionality, such as an application-specific integrated circuit (ASIC), a field programmable gate array (Field Programmable gate array), or other programmable logic device, transistor logic device, hardware component, software module, or any combination thereof.

Communication bus 402 may be used to transfer information between the above-described components.

A communication interface 404 for communicating with other devices or communication networks, such as ethernet, radio access network (radioaccess network, RAN), wireless local area network (wireless local area networks, WLAN), etc. The communication interface 404 may be an interface, circuit, transceiver, or other device capable of communication, without limitation. The communication interface 404 may be coupled to the processor 401. The 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 form for information interaction between the devices, units, or modules.

In the disclosed embodiments, the memory may be, but is not limited to, read-only memory (ROM) or other type of static storage device that may store static information and instructions, random access memory (random access memory, RAM) or other type of dynamic storage device that may store information and instructions, but may also be electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), compact disc read-only memory (compact disc read-only memory) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be separate or coupled to the processor, such as through communication bus 402. The memory may also be integrated with the processor.

The memory 403 is used for storing program instructions and can be controlled by the processor 401 to execute the methods provided in the embodiments disclosed below. The processor 401 is configured to invoke and execute instructions stored in the memory 403, thereby implementing the methods provided by the embodiments of the present disclosure.

Alternatively, computer-executable instructions in embodiments of the present disclosure may also be referred to as application code, which embodiments of the present disclosure are not particularly limited.

Optionally, a memory 403 may be included in the processor 401.

In a particular implementation, processor 401 may include one or more CPUs, such as CPU0 and CPU1 of FIG. 4, as an embodiment.

In a particular implementation, as one embodiment, apparatus 400 may include a plurality of processors, such as processor 401 and processor 405 in FIG. 4. Each of these processors may be a single-core (single-CPU) processor or may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

Optionally, the apparatus 400 of fig. 4 may further include a transceiver and an antenna, through which the apparatus 400 may communicate with other apparatuses (e.g., IAB nodes or terminals). For example, the first IAB node and the second IAB node may further include a transceiver and an antenna, the first IAB node may transmit data and/or information to the second IAB node via the transceiver and the antenna, and the transceiver and the antenna of the second IAB node may receive the data and/or information; the second IAB node may transmit data and/or information to the first IAB node via a transceiver and an antenna, which may receive the data and/or information.

The transceiver may be used for conversion of baseband signals to radio frequency signals and processing of radio frequency signals, and may be coupled to an antenna. The transceiver includes a transmitter (Tx) and a receiver (Rx). In particular, one or more antennas may receive radio frequency signals, and a receiver of the transceiver is configured 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 provide the digital baseband signals or digital intermediate frequency signals to the processor, so that the processor may perform further processing, such as demodulation processing and decoding processing, on the digital baseband signals or digital intermediate frequency signals. In addition, a transmitter Tx in the transceiver is used to receive a modulated digital baseband signal or digital intermediate frequency signal from the processor, and convert the modulated digital baseband signal or digital intermediate frequency signal to a radio frequency signal and transmit the radio frequency signal through one or more antennas. In particular, the receiver Rx may selectively perform one or more steps of down-mixing and analog-to-digital conversion on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency signal, where the order of the down-mixing and analog-to-digital conversion is adjustable. The transmitter Tx may selectively perform one or more stages of up-mixing processing and digital-to-analog conversion processing on the modulated digital baseband signal or the digital intermediate frequency signal to obtain a radio frequency signal, and the sequence of the up-mixing processing and the digital-to-analog conversion processing may be adjustable. The digital baseband signal and the digital intermediate frequency signal may be collectively referred to as a digital signal. Alternatively, the transmitter Tx and the receiver Rx may be implemented by different physical structures/circuits, or may be implemented by the same physical structure/circuit, that is, the transmitter Tx and the receiver Rx may inherit together.

The transceiver may also be referred to as a transceiver unit, transceiver device, etc. Alternatively, the device for implementing the receiving function in the transceiver unit may be regarded as a receiving unit, and the device for implementing the transmitting function in the transceiver unit may be regarded as a transmitting unit, that is, the transceiver unit includes a receiving unit and a transmitting unit, where the receiving unit may also be referred to as a receiver, an input port, a receiving circuit, etc., and the transmitting unit may be referred to as a transmitter, or a transmitting circuit, etc. Alternatively, the combination of Tx, rx and antenna may be made into a transceiver.

It may be understood that, the communication system described in the embodiments of the present disclosure is for more clearly describing the technical solutions of the embodiments of the present disclosure, and is not limited to the technical solutions provided in the embodiments of the present disclosure, and those skilled in the art can know that, with the evolution of the system architecture and the appearance of new service scenarios, the technical solutions provided in the embodiments of the present disclosure are equally applicable to similar technical problems.

In the embodiment of the present disclosure, admittance and addition have the same meaning, and when the second entity is to receive the request of the migration node, it needs to determine whether the requested resource can be admitted or added, so as to provide the service with QoS (Quality of Service ) guarantee for the migrated node (third entity) and the UE under the node.

A migration method and apparatus provided by the present disclosure are described in detail below with reference to the accompanying drawings.

Referring to fig. 5, fig. 5 is a flowchart of a migration method according to an embodiment of the disclosure.

As shown in fig. 5, the method is performed by a first entity, and may include, but is not limited to, the steps of:

s51: and sending migration request information of a third entity to the second entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity.

In the embodiment of the disclosure, the first entity determines a third entity to be migrated, and the second entity to which the third entity is to be migrated, and the third entity and the terminal device under the third entity provide network access connection by the first entity.

It will be appreciated that the third entity may migrate to the second entity, which may also provide network access connections for the third entity and for the terminal devices under the third entity.

Wherein the third entity is movable from the first entity to the second entity. The third entity and the terminal equipment under the third entity provide network access connection by the first entity, and the first entity can acquire corresponding information from the third entity or the terminal equipment under the third entity, so as to determine the third entity needing to be migrated and the second entity to which the third entity needs to be migrated.

In the embodiment of the disclosure, when determining the third entity to be migrated and the second entity to which the third entity is to be migrated, the first entity may send migration request information of the third entity to the second entity.

Wherein the migration request information of the third entity may be used for admission control, resource preparation and/or migration preparation etc. by the second entity.

S52: and receiving the first feedback information sent by the second entity.

In the embodiment of the disclosure, the second entity may generate the first feedback information and send the first feedback information to the first entity when receiving the migration request information of the third entity sent by the first entity.

The first feedback information may include a result of admission control and/or resource preparation in the second entity, so that the first entity may learn the result of admission control and/or resource preparation in the second entity, and determine, based on knowing the service requirements of the third entity and the terminal device under the third entity, whether the second entity can meet the service requirements and/or the satisfaction degree of the third entity and the terminal device under the third entity. Therefore, under the condition that the service requirements of the third entity and the terminal equipment under the third entity are met, a migration strategy can be generated and/or migration and the like can be performed, so that the terminal equipment migration failure or switching failure is avoided, and the user experience is improved.

In the embodiment of the present disclosure, when a mobile node (third entity) serving multiple UEs needs to migrate from one service entity (first entity) to another service entity (second entity), by the method in the foregoing embodiment, before performing UE migration or handover, the service entity (first entity) before migration and the service entity (second entity) after migration may interact with information related to admission control and/or information related to resource request of all UEs under the mobile node (third entity) in advance, so that the target entity (second entity) performs admission control and/or resource preparation before UE migration, and/or so that the source entity (first entity) determines whether to select the target entity (second entity) as a final target of migration according to a result of admission of the target entity (second entity), thereby avoiding UE handover failure or migration failure caused by insufficient resources of the target entity (second entity), further ensuring continuity of all UE services, and improving user experience.

In the embodiment of the disclosure, a first entity sends migration request information of a third entity to a second entity. The first entity and the second entity may be a core network, a base station, a gNB-CU, a gNB-DU, a gNB-CU-CP or a gNB-CU-UP.

In an exemplary embodiment, the first entity and the second entity are base stations and have an IAB function, for example, an IAB-donor or an IAB-donor-CU-CP, and the third entity in the migration request information of the third entity that needs to request for migration may be an IAB node, where the IAB node may be mobile, for example, a mobile IAB.

In another exemplary embodiment, the first entity and the second entity may be satellites having a base station function or a part of a base station function, and the third entity in the migration request information of the third entity that needs to request migration is a satellite having a base station function or a part of a base station function.

It should be appreciated that the above is merely an example, and the first entity, the second entity, and the third entity that needs to request migration are not limited thereto.

In an exemplary embodiment, the first entity and the second entity are base stations, gNB-CU-CP, or satellites with base station functionality, the migration request information of the third entity may be transmitted by an XnAP (Xn Application Protocol, xn interface application protocol) message, which may 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.

In another exemplary embodiment, the first entity is a base station, a gNB-CU-CP, or a satellite with base station functionality, the second entity is a core network, such as an AMF (acess and mobility management function, access and mobility management function), and the migration request information of the third entity may be transmitted by an NGAP (NG Application Protocol ) message, which may be a handover required message (Handover Required message), a migration required message (Migration Required message), an IAB migration required message (IAB Migration Required message), or a group handover required message (Group Handover Required message), etc.

In yet another exemplary embodiment, the first entity is a core network, the second entity is a base station, a gNB-CU-CP, or a satellite with base station functionality, the migration request information of the third entity may be transmitted by an NGAP message, which may 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.

It should be appreciated that the above is merely an example, and the messages of the migration request information of the first and second entities, and the third entity are not limited thereto.

In some embodiments, the migration request information of the third entity includes at least one of:

information for indicating a node migration mode;

information for node migration admission control.

In the embodiment of the disclosure, the first entity sends the migration request information of the third entity to the second entity, and may send information for indicating the node migration mode to the second entity.

In the embodiment of the disclosure, 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.

In the embodiment of the disclosure, the first entity sends the migration request information of the third entity to the second entity, and can send the information for indicating the node migration mode and the information for controlling the node migration admittance to the second entity.

The information for indicating the node migration mode may be implicit or displayed, and the second entity may consider or prepare resources for the migrated node according to the information for indicating the node migration mode.

In an exemplary embodiment, the information for indicating the node migration manner may be partial migration, complete migration, or the like; in another exemplary embodiment, the information for indicating the node migration mode may be a function of the node indicating that the migration is specifically required, for example, an IAB-MT, an IAB-DU, an IAB-node, etc.; in yet another exemplary embodiment, the information for indicating the node migration manner is implicitly indicated, for example, when the migration request information of the third entity includes information related to the IAB-DU, the description is a complete migration, and otherwise, the description is a partial migration. It should be appreciated that the above is merely an example, and the information for indicating the node migration manner is not limited thereto.

Wherein the information for node migration admission control includes information that requires admission control for complete migration (i.e., IAB node migration or complete migration), the second entity may consider or based on the information for node migration admission control, perform admission control, and feed back the information for admission control and/or resource preparation to the first entity.

In some embodiments, the second entity performs different actions taking into account information indicating the manner in which the node is migrated. For example, if the migration is complete, the second entity needs to consider admission control and/or prepare corresponding resources for the migration node (i.e., the third entity) and all UEs under the migration node; if the migration is partial, the second entity only needs to consider partial service requirements in the migration node to perform admission control and/or admit resources.

In some embodiments, the information for node migration admission control includes at least one of:

related information of terminal equipment served by a third entity;

related information of the services supported by the third entity.

In the embodiment of the disclosure, the first entity sends the migration request information of the third entity to the second entity, and may send the related information of the terminal device served by the third entity to the second entity.

In the embodiment of the disclosure, the first entity sends the migration request information of the third entity to the second entity, and may send the related information of the service supported by the third entity to the second entity.

In the embodiment of the disclosure, the first entity sends the migration request information of the third entity to the second entity, and the related information of the terminal device served by the third entity and the related information of the service supported by the third entity can be sent to the second entity.

In some embodiments, the information about the terminal device served by the third entity includes at least one of:

the number of terminal devices;

the number of data radio bearers DRB;

signaling the number of radio bearers SRBs;

quality of service QoS requirements for each terminal device;

quality of service QoS requirements for all terminal devices;

a core network node connected with the terminal equipment;

packet data unit, PDU, session information for the terminal device.

In this embodiment of the present disclosure, the related information of the terminal device served by the third entity is information related to all terminal devices that need to be migrated or switched to the second entity, where the terminal device refers to a terminal device served by the third entity, and the related information of the terminal device served by the third entity may be information such as the number of all terminal devices under an IAB-DU, the DRB (Data Radio Bearer )/SRB (Signalling Radio Bearer, signaling radio bearer) number, the QoS (Quality of Service ) requirement of the whole or each terminal device, or specific information of each terminal device, for example, information of a core network node to which the terminal device is connected or information related to a PDU (packet data unit) session of the terminal device, where the second entity considers or performs admission control and/or resource preparation according to the related information of the terminal device served by the third entity.

In the embodiment of the present disclosure, the information about the terminal devices served by the third entity is the number of the terminal devices.

In the embodiment of the present disclosure, the related information of the terminal device served by the third entity is the number of data radio bearers DRBs.

In the embodiment of the present disclosure, the related information of the terminal device served by the third entity is the number of signaling radio bearers SRBs.

In the embodiment of the present disclosure, the related information of the terminal device served by the third entity is a quality of service QoS requirement of each terminal device.

In the embodiment of the present disclosure, the related information of the terminal device served by the third entity is the quality of service QoS requirement of all the terminal devices.

In the embodiment of the present disclosure, the information related to the terminal device served by the third entity is a core network node connected to the terminal device.

In the embodiment of the present disclosure, the related information of the terminal device served by the third entity is packet data unit PDU session information of the terminal device.

It should be noted that the foregoing embodiments are not exhaustive, but are merely illustrative of some embodiments, and the embodiments may be implemented alone or in combination of two or more, and the embodiments are merely illustrative, and are not intended to limit the scope of the embodiments of the present disclosure.

In some embodiments, the information about the services supported by the third entity includes one or more service configuration items; the service configuration items comprise service indexes, service configuration files and backhaul BH related configurations.

In the embodiment of the present disclosure, the related information of the service supported by the third entity is used to indicate the related information of the service supported on the node (third entity) requesting migration, for example, may be a service configuration on an IAB-DU, and may include one or more service configuration items, where each configuration item may include a service index, a service profile (service profile), and a BH (Backhaul) related configuration.

In some embodiments, the service profile includes at least one of:

user plane UP service;

control plane CP services;

QoS requirements;

UP traffic and QoS requirements;

CP traffic and QoS requirements.

In the embodiment of the present disclosure, the service configuration file includes a user plane UP (user plane) service.

In the embodiment of the present disclosure, the service configuration file includes a control plane CP (control plane) service.

In the embodiment of the disclosure, the service configuration file includes QoS requirements.

In the embodiment of the disclosure, the service configuration file includes UP service and QoS requirements.

In the embodiment of the disclosure, the service configuration file includes CP service and QoS requirements.

In some embodiments, the related information of the service supported by the third entity is sent in the first step of migration, for example, in the IAB-MT migration process, so that the second entity can perform admission control and/or resource preparation related to the service in advance, thereby improving the success rate of migration and ensuring the service experience of the user.

In the embodiment of the disclosure, the second entity considers or according to the related information of the service supported by the third entity, prepares the resources after the third entity migrates, including but not limited to adding or modifying the BH RLC (BackHaul Radio Link Control, radio link control) channel, IP address and/or BAP (backhaul adaptation protocol, backhaul adaptation protocol layer) configuration after the IAB-node migrates, and generates first feedback information including the condition of resource preparation, and sends the first feedback information to the first entity.

In some embodiments, the second entity sends the first feedback information to the first entity.

In an exemplary embodiment, the first entity and the second entity are base stations, gNB-CU-CP, or satellites with base station functionality, the first feedback information may be transmitted by an XnAP message, which may be a handover request acknowledgement message (Handover Request Acknowledge message), a migration request feedback message (Migration Request Response message), an IAB migration feedback message (IAB Migration Response message), an IAB migration failure message (IAB Migration failure message), or a group handover request acknowledgement message (Group Handover Request Acknowledge message), etc.

In another exemplary embodiment, the first entity is a base station, a gNB-CU-CP, or a satellite with base station functionality, the second entity is a core network, e.g., an AMF, and the first feedback information may be transmitted by an NGAP message, which may be a handover command message (Handover Command message), a migration command message (Migration Command message), an IAB migration command message (IABMigration Command message), a group handover command message (Group Handover Command message), or the like.

In yet another exemplary embodiment, the first entity is a core network, the second entity is a base station, a gNB-CU-CP, or a satellite with base station functionality, the first feedback information may be transmitted by an NGAP message, which may be a handover request acknowledgement message (Handover Request Acknowledge message), a migration feedback message (Migration Response message), an IAB migration feedback message (IAB Migration Response message), an IAB migration failure message (IAB Migration failure message), or a group handover feedback message (Group Handover Response message), etc. It should be appreciated that the above is merely an example, and the first and second entities, and the first feedback information are not limited thereto.

In the embodiment of the present disclosure, the second entity sends first feedback information to the first entity, where the first feedback information is generated by the second entity according to migration request information of the third entity sent by the first entity, a resource state of the second entity, a second entity admission control policy, and/or a resource preparation situation, and the first feedback information may include information related to a feedback node migration admission control and/or a resource preparation result.

In some embodiments, the first feedback information includes at least one of:

information of admission control results of the terminal equipment;

information of service admission control results;

information of resource preparation.

And the second entity sends the information of the admission control result of the terminal equipment to the first entity.

And the second entity sends the information of the service admission control result to the first entity.

The second entity sends the resource preparation information to the first entity.

In the embodiment of the present disclosure, information of an admission control result of a terminal device is used to indicate to a first entity, if a node (a third entity) requesting migration migrates to a second entity, whether a UE under the third entity is admitted successfully, information related to admission success, and/or information related to admission failure, etc.

In some embodiments, the information of the admission control result of the terminal device includes at least one of the following:

admission success information;

admission failure information.

In the embodiment of the present disclosure, the second entity sends information of the admission control result of the terminal device to the first entity, and may send admission success information to the first entity.

In the embodiment of the present disclosure, the second entity sends information of the admission control result of the terminal device to the first entity, and may send admission failure information to the first entity.

In the embodiment of the present disclosure, the second entity sends information of an 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.

In some embodiments, the admission success information includes at least one of:

the number of the access terminal devices;

the proportion of the admission terminal devices;

admitting the number of data radio bearers DRB;

the number of the admission signaling radio bearers SRB;

QoS information supported after migration;

maximum transmission bandwidth supported after migration;

information of terminal devices permitted to migrate.

In the embodiment of the disclosure, the admission success information may be an indication, a percentage, a specific number or specific UE information, and the first entity may consider the admission success information to make a decision of migration and/or a decision of a migration policy.

In the embodiment of the present disclosure, the admission success information may be information for indicating the number of admitted UEs.

In the embodiment of the present disclosure, the admission success information may be information indicating the number of admitted DRBs/SRBs.

In the embodiment of the present disclosure, the admission success information may be information for indicating QoS supported after migration, for example, information such as a maximum transmission bandwidth that may be supported.

In the embodiment of the present disclosure, the admission success information may be information about UEs for indicating permission of migration, for example, may be information such as a list of UEs permitted of migration, including an ID of each UE and UE-specific information.

In the embodiment of the present disclosure, the admission success information may be the number of admission terminal devices.

In the embodiment of the present disclosure, the admission success information may be the proportion of admitted terminal devices.

In the embodiment of the present disclosure, the admission success information may be the number of admitted data radio bearers DRBs.

In the embodiment of the present disclosure, the admission success information may be the number of admission signaling radio bearers SRBs.

In the embodiment of the present disclosure, the admission success information may be QoS information supported after migration.

In the embodiment of the present disclosure, the admission success information may be a maximum transmission bandwidth supported after the migration.

In the embodiment of the present disclosure, the admission success information may be information of terminal devices that admit migration.

In the embodiment of the present disclosure, the second entity sends information of 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 the admission failure, such as a UE ID.

In some embodiments, the traffic admission control result includes at least one of:

a successful service index is admitted;

traffic index of admission failure.

In the embodiment of the disclosure, the service admission control result indicates to the first entity, if the node requesting migration migrates to the second entity, whether the service addition requested by the node requesting migration (the third entity) is successful or not may include, for example, a successfully added service index and/or a failed added service index.

In the embodiment of the disclosure, the service admission control result is a successful admission service index.

In the embodiment of the disclosure, the service admission control result is a service index of admission failure.

In the embodiment of the disclosure, the service admission control result is a successful admission service index and a failed admission service index.

In some embodiments, the resource preparation information includes: backhaul BH configuration information.

In an embodiment of the present disclosure, the resource preparation information may include BH configuration information, for example, and the first entity may further forward the BH configuration information to the IAB node (third entity) requesting the migration, so that the IAB node (third entity) performing the migration of the IAB-DU, and the resource preparation information may be included in the RRC (radio resource control ) reconfiguration (RRC Reconfiguration) message for transmission.

In the embodiment of the disclosure, the first entity receives the first feedback information, and may perform the decision of migration, policy generation of migration and/or execution of migration according to or in consideration of the first feedback information.

In some embodiments, if all UEs and traffic are admitted successfully, the first entity may proceed with the migration procedure; if only part of the UE is admitted successfully, the first entity can consider that the admitted part of the UE migrates along with the third entity and continue to execute the migration process, and the UE which is not admitted successfully can be directly switched to other base stations without migrating along with the third entity so as to ensure the continuity of the service; if the first entity receives a plurality of first feedback information from other entities (including the second entity), the first entity can select a target entity with successful admission or higher admission success rate or better experience for the UE to migrate, and continue the migration process. Therefore, whether the resources of the target entity are sufficient or not, the first entity can consider or select the optimal target entity or migration strategy to migrate according to the first feedback information, so that migration failure or UE handover failure or service quality degradation is avoided, and user experience is ensured.

In some embodiments, the first entity is a source integrated access and backhaul (IAB-donor) host, the second entity is a target IAB host (target IAB-donor) and the third entity is an IAB node.

In the related art, the position of an IAB node (IAB node) is fixed, so as to increase the robustness of an IAB, an IAB-MT may migrate to another IAB-donor-CU, and an IAB-DU(s) of a collocated IAB-DU and its descendant nodes remain F1 connected to the original IAB-donor-CU, and this migration is called Inter-donor partial migration. After the Inter-donor partial migration, the F1 traffic of the IAB-DU and its descendent nodes will be routed through the BAP layer of the IAB topology to which the IAB-MT is migrated. However, if mobile IAB is to be supported, i.e. IAB node can move between different IAB-donor-CUs, full IAB migration, i.e. one or more UEs served under IAB-MT, IAB-DU and IAB node all need to migrate from source IAB-donor-CU (source IAB-donor) to target IAB-donor-CU (target IAB-donor), has to be supported. The general sequence of the IAB node migration is as follows:

first, IAB-MT migration;

step two, IAB-DU migration;

and thirdly, migrating the UE under the IAB node.

Wherein the first step and the second step may exchange sequences, or the second step may be in two stages, one before and one after the transfer of the IAB-MT. Whereas the migration of the UE must be done after the migration of the IAB-DU.

However, no matter which migration scheme is used, no admission control of multiple UEs is considered in the first step and/or the second step of interaction of the source IAB-donor and the target IAB-donor, if the resources of the target IAB-donor selected in the first step are insufficient to support the service requirements of all UEs after migration, after the first step and the second step are completed, the multiple UEs may fail in admission control in the third step, resulting in UE migration failure or handover failure, and finally, UE service interruption, and affecting user experience.

Based on this, in the embodiment of the present disclosure, when a mobile IAB node needs to migrate from one IAB-donor (i.e., a source IAB-donor) to another IAB-donor (i.e., a target IAB-donor), before performing UE migration or handover, information related to admission control and/or information related to resource requests of all UEs under the target IAB-donor are interacted with by the source IAB-donor in advance, so that the target IAB-donor makes admission control and/or resource preparation before the UE migrates, and/or so that the source IAB-donor determines whether to select the target IAB-donor as a final target for migration according to a result of the target IAB-donor, thereby avoiding UE handover failure or migration failure caused by insufficient resources of the target IAB-donor, further ensuring continuity of all mobile UE services, and improving user experience.

Referring to fig. 6, fig. 6 is a flowchart of another migration method according to an embodiment of the disclosure.

As shown in fig. 6, the method is performed by a first entity, and may include, but is not limited to, the steps of:

s61: and sending migration request information of a third entity to the second entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity.

The manner in which the first entity sends the migration request information of the third entity to the second entity may be referred to the related description in the above embodiment, and the same contents are not repeated here.

The description of the migration request information of the third entity may be referred to the description of the foregoing embodiment, and the same contents are not repeated herein.

S62: and receiving the first feedback information sent by the second entity.

The manner in which the first entity receives the first feedback information sent by the second entity may be referred to the related description in the above embodiment, and the same contents are not repeated herein.

The description of the first feedback information may be referred to the description of the foregoing embodiments, and the same contents are not repeated herein.

In the embodiment of the present disclosure, the description of S61 and S62 may be referred to the description of the above embodiment, and the same contents are not repeated here.

S63: and executing at least one of judgment of migration, policy generation of migration and migration according to the first feedback information.

In the embodiment of the present disclosure, after the first entity receives the first feedback information sent by the second entity, the migration decision may be performed.

Wherein, in case of deciding to migrate, policy generation of migration can be performed; or in the case that the migration is judged to be impossible, the migration is canceled. Under the condition that the policy generation of migration execution migration is judged, the migration can be further carried out according to the generated migration policy.

In the embodiment of the present disclosure, after the first entity receives the first feedback information sent by the second entity, the first entity may execute the policy generation of the migration.

In the case of performing the migration policy generation, the migration may be further performed according to the generated migration policy.

In the embodiment of the present disclosure, after the first entity receives the first feedback information sent by the second entity, migration may be performed.

In the embodiment of the present disclosure, when a mobile node (third entity) serving multiple UEs needs to migrate from one service entity (first entity) to another service entity (second entity), by the method in the foregoing embodiment, before performing UE migration or handover, the service entity (first entity) before migration and the service entity (second entity) after migration may interact with information related to admission control and/or information related to resource request of all UEs under the mobile node (third entity) in advance, so that the target entity (third entity) performs admission control and/or resource preparation before UE migration, and/or so that the source entity (first entity) determines whether to select the target entity (second entity) as a final target of migration according to a result of admission of the target entity (second entity), thereby avoiding UE handover failure or migration failure caused by insufficient resources of the target entity (second entity), further ensuring continuity of all UE services, and improving user experience.

Referring to fig. 7, fig. 7 is a flowchart of another migration method according to an embodiment of the disclosure.

As shown in fig. 7, the method is performed by a second entity, and the method may include, but is not limited to, the steps of:

s71: and receiving migration request information of a third entity sent by the first entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity.

In the embodiment of the disclosure, the first entity may determine a third entity to be migrated and a second entity to which the third entity is to be migrated, so as to send migration request information of the third entity to the second entity.

The third entity and the terminal equipment under the third entity provide network access connection by the first entity.

Wherein the migration request information of the third entity may be used for admission control, resource preparation and/or migration preparation by the second entity.

S72: the first feedback information is sent to the first entity.

The first feedback information may include a result 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 may learn the result of admission control and/or resource preparation in the second entity, and may determine, on the basis of knowing the service requirements of the third entity and the terminal device under the third entity, whether the second entity can meet the service requirements and/or the satisfaction degree of the third entity and the terminal device under the third entity. Therefore, under the condition that the service requirements of the third entity and the terminal equipment under the third entity are met, a migration strategy can be generated and/or migration and the like can be performed, so that the terminal equipment migration failure or switching failure is avoided, and the user experience is improved.

In an exemplary embodiment, the first entity and the second entity are base stations, gNB-CU-CP, or satellites with base station functionality, and the migration request information of the third entity may be transmitted by an XnAP message, which may 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.

In another exemplary embodiment, the first entity is a base station, a gNB-CU-CP, or a satellite with base station functionality, the second entity is a core network, such as an AMF, and the migration request information of the third entity may be transmitted by an NGAP message, which may be a handover required message (Handover Required message), a migration required message (Migration Required message), an IAB migration required message (IAB Migration Required message), or a group handover required message (Group Handover Required message), etc.

Information for indicating a node migration mode;

information for node migration admission control.

related information of terminal equipment served by a third entity;

related information of the services supported by the third entity.

the number of terminal devices;

the number of data radio bearers DRB;

signaling the number of radio bearers SRBs;

quality of service QoS requirements for each terminal device;

quality of service QoS requirements for all terminal devices;

a core network node connected with the terminal equipment;

packet data unit, PDU, session information for the terminal device.

In some embodiments, the service profile includes at least one of:

user plane UP service;

control plane CP services;

QoS requirements;

UP traffic and QoS requirements;

CP traffic and QoS requirements.

In the embodiment of the present disclosure, the second entity considers or according to the related information of the service supported by the third entity, prepares the resources after the third entity migrates, including but not limited to adding or modifying the BH RLC Channel, the IP address and/or the BAP configuration after the IAB-node migrates, generates the first feedback information including the condition of resource preparation, and sends the first feedback information to the first entity.

In another exemplary embodiment, the first entity is a base station, a gNB-CU-CP, or a satellite with base station functionality, the second entity is a core network, e.g., an AMF, and the first feedback information may be transmitted by an NGAP message, which may be a handover command message (Handover Command message), a migration command message (Migration Command message), an IAB migration command message (IAB Migration Command message), a group handover command message (Group Handover Command message), or the like.

In yet another exemplary embodiment, the first entity is a core network, the second entity is a base station, a gNB-CU-CP, or a satellite with base station functionality, the first feedback information may be transmitted by an NGAP message, which may be a handover request acknowledgement message (Handover Request Acknowledge message), a migration feedback message (Migration Response message), an IAB migration feedback message (IAB Migration Response message), an IAB migration failure message (IAB Migration failure message), or a group handover feedback message (Group Handover Response message), etc. It should be appreciated that the above is merely an example, and the first and second entities, and the feedback information are not limited thereto.

In some embodiments, the first feedback information includes at least one of:

information of admission control results of the terminal equipment;

information of service admission control results;

information of resource preparation.

admission success information;

admission failure information.

the number of the access terminal devices;

the proportion of the admission terminal devices;

admitting the number of data radio bearers DRB;

the number of the admission signaling radio bearers SRB;

QoS information supported after migration;

maximum transmission bandwidth supported after migration;

information of terminal devices permitted to migrate.

a successful service index is admitted;

traffic index of admission failure.

first, IAB-MT migration;

step two, IAB-DU migration;

and thirdly, migrating the UE under the IAB node.

Referring to fig. 8, fig. 8 is a flowchart of another migration method according to an embodiment of the disclosure.

As shown in fig. 8, the method is performed by a second entity, and the method may include, but is not limited to, the steps of:

s81: and receiving migration request information of a third entity sent by the first entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity.

In the embodiment of the present disclosure, the description of S81 may be referred to the description of the above embodiment, and the same contents are not repeated here.

S82: and executing node migration admission control and/or resource preparation according to the migration request information of the third entity so as to generate first feedback information.

In the embodiment of the present disclosure, when the second entity receives the migration request information of the third entity sent by the first entity, the node migration admission control and/or resource preparation may be performed according to the migration request information of the third entity, so as to generate the first feedback information.

S83: the first feedback information is sent to the first entity.

In the embodiment of the present disclosure, the description of S83 may be referred to the description of the above embodiment, and the same contents are not repeated here.

Referring to fig. 9, fig. 9 is a flowchart of yet another migration method according to an embodiment of the disclosure.

As shown in fig. 9, the method is performed by a second entity, and the method may include, but is not limited to, the steps of:

s91: and sending node migration request information of the third entity to the fourth entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the second entity.

In the embodiment of the disclosure, the second entity determines a third entity to be migrated, and a fourth entity to which the third entity is to be migrated, and the third entity and the terminal device under the third entity provide network access connection by the second entity.

It may be appreciated that the third entity may migrate to the fourth entity, which may also provide network access connection for the third entity and the terminal device under the third entity.

Wherein the third entity is movable from the second entity to the fourth entity. The third entity and the terminal equipment under the third entity provide network access connection by the second entity, and the second entity can acquire corresponding information from the third entity or the terminal equipment under the third entity, so as to determine the third entity needing to be migrated and the fourth entity to which the third entity needs to be migrated.

In the embodiment of the disclosure, the second entity may send node migration request information to the fourth entity when determining the third entity to be migrated and the fourth entity to which the third entity is to be migrated.

S92: and receiving second feedback information sent by the fourth entity.

In the embodiment of the disclosure, the fourth entity may generate the second feedback information and send the second feedback information to the second entity when receiving the node migration request information sent by the second entity.

The second feedback information may include a result of admission control and/or resource preparation in the fourth entity, so that the second entity may learn a result of admission control and/or resource preparation in the fourth entity, and determine, based on knowing the service requirements of the third entity and the terminal device under the third entity, whether the fourth entity can meet the service requirements and/or the satisfaction degree of the third entity and the terminal device under the third entity. Therefore, under the condition that the service requirements of the third entity and the terminal equipment under the third entity are met, a migration strategy can be generated and/or migration and the like can be performed, so that the terminal equipment migration failure or switching failure is avoided, and the user experience is improved.

In the embodiment of the present disclosure, when a mobile node (third entity) serving multiple UEs needs to migrate from one service entity (second entity) to another service entity (fourth entity), by the method in the foregoing embodiment, before performing UE migration or handover, the service entity (second entity) before migration and the service entity (fourth entity) after migration may interact with information related to admission control and/or information related to resource requests of all UEs under the mobile node (third entity) in advance, so that the target entity (fourth entity) performs admission control and/or resource preparation before UE migration, and/or so that the source entity (second entity) determines whether to select the target entity (fourth entity) as a final target of migration according to a result of admission of the target entity (fourth entity), thereby avoiding UE handover failure or migration failure caused by insufficient resources of the target entity (fourth entity), further ensuring continuity of all UE services, and improving user experience.

In the embodiment of the disclosure, the second entity sends node migration request information to the fourth entity. The second and fourth entities may be a core network, a base station, a gNB-CU, a gNB-DU, a gNB-CU-CP or a gNB-CU-UP.

In an exemplary embodiment, the second entity and the fourth entity are base stations and have an IAB function, for example, IAB-donor or IAB-donor-CU-CP, and the third entity in the node migration request information that needs to request migration may be an IAB node, which may be mobile, for example, mobile IAB.

In another exemplary embodiment, the second entity and the fourth entity may be satellites having a base station function or a part of a base station function, and the third entity in the node migration request information that needs to request migration is a satellite having a base station function or a part of a base station function.

It should be appreciated that the above is merely an example, and the second entity, the fourth entity, and the third entity that needs to request migration are not limited thereto.

In an exemplary embodiment, the second entity and the fourth entity are base stations, gNB-CU-CP, or satellites with base station functionality, the node migration request information may be transmitted by an XnAP (Xn Application Protocol, xn interface application protocol) message, which may 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.

In another exemplary embodiment, the second entity is a base station, a gNB-CU-CP, or a satellite with base station functionality, the fourth entity is a core network, such as an AMF (acess and mobility management function, access and mobility management function), the node migration request information may be transmitted by an NGAP (NG Application Protocol ) message, which may be a handover required message (Handover Required message), a migration required message (Migration Required message), an IAB migration required message (IAB Migration Required message), or a group handover required message (Group Handover Required message), etc.

In yet another exemplary embodiment, the second entity is a core network, the fourth entity is a base station, a gNB-CU-CP, or a satellite with base station functionality, the node migration request information may be transmitted by an NGAP message, which may 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.

It should be appreciated that the above is merely an example, and the second and fourth entities, and the message of the node migration request information are not limited thereto.

In some embodiments, the node migration request information of the third entity includes at least one of:

information for indicating a node migration mode;

information for node migration admission control.

In the embodiment of the disclosure, the second entity sends the node migration request information of the third entity to the fourth entity, and may send information for indicating the node migration mode to the fourth entity.

In the embodiment of the disclosure, the second entity sends the node migration request information of the third entity to the fourth entity, and may send the information for node migration admission control to the fourth entity.

In the embodiment of the disclosure, the second entity sends the node migration request information of the third entity to the fourth entity, and may send information for indicating the node migration mode and information for controlling the node migration admission to the fourth entity.

The information for indicating the node migration mode may be implicit or displayed, and the fourth entity may consider or prepare resources for the migrated node according to the information for indicating the node migration mode.

In an exemplary embodiment, the information for indicating the node migration manner may be partial migration, complete migration, or the like; in another exemplary embodiment, the information for indicating the node migration mode may be a function of the node indicating that the migration is specifically required, for example, an IAB-MT, an IAB-DU, an IAB-node, etc.; in yet another exemplary embodiment, the information for indicating the node migration manner is implicitly indicated, for example, when the node migration request information of the third entity includes information related to the IAB-DU, the description is a complete migration, and otherwise, the description is a partial migration. It should be appreciated that the above is merely an example, and the information for indicating the node migration manner is not limited thereto.

Wherein the information for node migration admission control includes information that requires admission control for complete migration (i.e., IAB node migration or complete migration), the fourth entity may consider or based on the information for node migration admission control, perform admission control, and feed back the information for admission control and/or resource preparation to the second entity.

In some embodiments, the fourth entity performs different actions taking into account information indicating the manner in which the node is migrated. For example, if the migration is complete, the fourth entity needs to consider admission control and/or prepare corresponding resources for the migration node (i.e., the third entity) and all UEs under the migration node; and if the migration is partial, the fourth entity only needs to consider partial service requirements in the migration node to perform admission control and/or admit resources.

related information of terminal equipment served by a third entity;

related information of the services supported by the third entity.

In the embodiment of the present disclosure, the second entity sends the node migration request information of the third entity to the fourth entity, and may send the related information of the terminal device served by the third entity to the fourth entity.

In the embodiment of the disclosure, the second entity sends the node migration request information of the third entity to the fourth entity, and may send the related information of the service supported by the third entity to the fourth entity.

In the embodiment of the present disclosure, 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 of the terminal device served by the third entity and related information of the service supported by the third entity.

the number of terminal devices;

the number of data radio bearers DRB;

signaling the number of radio bearers SRBs;

quality of service QoS requirements for each terminal device;

quality of service QoS requirements for all terminal devices;

a core network node connected with the terminal equipment;

packet data unit, PDU, session information for the terminal device.

In the embodiment of the present disclosure, the related information of the terminal device served by the third entity is information related to all terminal devices that need to be migrated or switched to the fourth entity, where the terminal device refers to a terminal device served by the third entity, and the related information of the terminal device served by the third entity may be information such as the number of all terminal devices under the IAB-DU, the DRB (Data Radio Bearer )/SRB (Signalling Radio Bearer, signaling radio bearer) number, the QoS (Quality of Service ) requirement of the whole or each terminal device, or specific information of each terminal device, for example, information such as a core network node to which the terminal device is connected or information related to a PDU (packet data unit) session of the terminal device, and the fourth entity considers or performs admission control and/or resource preparation according to the related information of the terminal device served by the third entity.

In some embodiments, the service profile includes at least one of:

user plane UP service;

control plane CP services;

QoS requirements;

UP traffic and QoS requirements;

CP traffic and QoS requirements.

In some embodiments, the related information of the service supported by the third entity is sent in the first step of migration, for example, in the IAB-MT migration process, so that the fourth entity can perform admission control and/or resource preparation related to the service in advance, thereby improving the success rate of migration and ensuring the service experience of the user.

In the embodiment of the present disclosure, the fourth entity considers or according to the related information of the service supported by the third entity, prepares the resources after the third entity migrates, including but not limited to adding or modifying the BH RLC (BackHaul Radio Link Control, radio link control) channel, IP address and/or BAP (backhaul adaptation protocol, backhaul adaptation protocol layer) configuration after the IAB-node migrates, generates second feedback information including the resource preparation condition, and sends the second feedback information to the second entity.

In some embodiments, the fourth entity sends the second feedback information to the second entity.

In an exemplary embodiment, the second entity and the fourth entity are base stations, gNB-CU-CP, or satellites with base station functionality, the second feedback information may be transmitted by an XnAP message, which may be a handover request acknowledgement message (Handover Request Acknowledge message), a migration request feedback message (Migration Request Response message), an IAB migration feedback message (IAB Migration Response message), an IAB migration failure message (IAB Migration failure message), or a group handover request acknowledgement message (Group Handover Request Acknowledge message), etc.

In another exemplary embodiment, the second entity is a base station, a gNB-CU-CP, or a satellite with base station functionality, the fourth entity is a core network, e.g., an AMF, and the second feedback information may be transmitted by an NGAP message, which may be a handover command message (Handover Command message), a migration command message (Migration Command message), an IAB migration command message (IAB Migration Command message), a group handover command message (Group Handover Command message), or the like.

In yet another exemplary embodiment, the second entity is a core network, the fourth entity is a base station, a gNB-CU-CP, or a satellite with base station functionality, the second feedback information may be transmitted by an NGAP message, which may be a handover request acknowledgement message (Handover Request Acknowledge message), a migration feedback message (Migration Response message), an IAB migration feedback message (IAB Migration Response message), an IAB migration failure message (IAB Migration failure message), or a group handover feedback message (Group Handover Response message), etc. It should be appreciated that the above is merely an example, and the second and fourth entities, and the second feedback information are not limited thereto.

In the embodiment of the present disclosure, the fourth entity sends second feedback information to the second entity, where the second feedback information is generated by the fourth entity according to node migration request information of the third entity, resource status of the fourth entity, admission control policy of the fourth entity, resource preparation situation, and the like, which are sent by the second entity, and the second feedback information may include information related to feedback node migration admission control and/or resource preparation results.

In some embodiments, the second feedback information includes at least one of:

information of admission control results of the terminal equipment;

information of service admission control results;

information of resource preparation.

In the embodiment of the disclosure, the fourth entity may generate the second feedback information and send the second feedback information to the second entity when receiving the node migration request information of the third entity sent by the second entity.

And the fourth entity sends the information of the admission control result of the terminal equipment to the second entity.

And the fourth entity sends the information of the service admission control result to the second entity.

And the fourth entity sends the information of resource preparation to the second entity.

In the embodiment of the present disclosure, information of an admission control result of a terminal device is used to indicate to a second entity, if a node (a third entity) requesting migration migrates to a fourth entity, whether the UE under the third entity is admitted successfully, information related to admission success, and/or information related to admission failure, etc.

admission success information;

admission failure information.

In the embodiment of the present disclosure, the fourth entity sends information of an admission control result of the terminal device to the second entity, and may send admission success information to the second entity.

In the embodiment of the present disclosure, the fourth entity sends information of an admission control result of the terminal device to the second entity, and may send admission failure information to the second entity.

In the embodiment of the present disclosure, the fourth entity sends information of an 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 number of the access terminal devices;

the proportion of the admission terminal devices;

admitting the number of data radio bearers DRB;

the number of the admission signaling radio bearers SRB;

QoS information supported after migration;

maximum transmission bandwidth supported after migration;

information of terminal devices permitted to migrate.

In the embodiment of the disclosure, the admission success information may be an indication, a percentage, a specific number or specific UE information, and the second entity may consider the admission success information to make a decision of migration and/or a decision of migration policy.

In the embodiment of the present disclosure, the fourth entity sends information of an 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 the admission failure, such as a UE ID.

a successful service index is admitted;

traffic index of admission failure.

In the embodiment of the disclosure, the service admission control result indicates to the second entity, if the node requesting migration migrates under the fourth entity, whether the service addition requested by the node requesting migration (the third entity) is successful or not may include, for example, a successfully added service index and/or a failed added service index.

In an embodiment of the present disclosure, the resource preparation information may include BH configuration information, for example, and the second entity may further forward the BH configuration information to the IAB node (third entity) requesting the migration, so that the IAB node (third entity) performing the migration of the IAB-DU, and the resource preparation information may be included in the RRC (radio resource control ) reconfiguration (RRC Reconfiguration) message for transmission.

In the embodiment of the disclosure, the second entity receives the second feedback information, and may perform the decision of migration, policy generation of migration and/or execution of migration according to or in consideration of the second feedback information.

In some embodiments, if all UEs and traffic are admitted successfully, the second entity may proceed with the migration process; if only part of the UE is admitted successfully, the second entity can consider that the admitted part of the UE migrates along with the third entity and continue to execute the migration process, and the UE which is not admitted successfully can be directly switched to other base stations without migrating along with the third entity so as to ensure the continuity of the service; if the second entity receives a plurality of second feedback information from other entities (including the fourth entity), the second entity can select a target entity with successful admission or higher admission success rate or better experience for the UE to migrate, and continue the migration process. Therefore, whether the resources of the target entity are sufficient or not, the second entity can consider or select the optimal target entity or migration strategy to migrate according to the second feedback information, so that migration failure or UE handover failure or service quality degradation is avoided, and user experience is ensured.

In some embodiments, the second entity is a source integrated access and backhaul (IAB-donor) host, the fourth entity is a target IAB host (target IAB-donor) and the third entity is an IAB node.

first, IAB-MT migration;

step two, IAB-DU migration;

and thirdly, migrating the UE under the IAB node.

It should be noted that, in the embodiment of the present disclosure, S91 and S92 may be implemented separately, or may be implemented in combination with any one of the other steps in the embodiment of the present disclosure, for example, in combination with S71 and S72 and/or S81 to S83 in the embodiment of the present disclosure, which is not limited thereto.

In the embodiments provided in the present disclosure, the method provided in the embodiments of the present disclosure is described from the perspective of the network side device and the terminal device, respectively. In order to implement the functions in the method provided by the embodiments of the present disclosure, the network side device and the terminal device may include a hardware structure, a software module, and implement the functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Some of the functions described above may be implemented in a hardware structure, a software module, or a combination of a hardware structure and a software module.

Fig. 10 is a schematic structural diagram of a communication device 1 according to an embodiment of the 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 transmitting module and/or a receiving module, where the transmitting module is configured to implement a transmitting function, the receiving module is configured to implement a receiving function, and the transceiver module may implement the transmitting function and/or the receiving function.

The communication device 1 is a first entity:

the communication device 1 includes: a transceiver module 11 and a processing module 12.

The transceiver module 11 is configured to send migration request information of a third entity to the second entity, where the third entity and the terminal device under the third entity provide network access connection by the first entity.

The transceiver module 11 is further configured to receive the first feedback information sent by the second entity.

In some embodiments, the processing module 12 is configured to perform at least one of the following according to the first feedback information:

judging migration;

generating a migration strategy;

migration is performed.

information for indicating a node migration mode;

information for node migration admission control.

related information of terminal equipment served by a third entity;

related information of the services supported by the third entity.

the number of terminal devices;

the number of data radio bearers DRB;

Signaling the number of radio bearers SRBs;

quality of service QoS requirements for each terminal device;

quality of service QoS requirements for all terminal devices;

a core network node connected with the terminal equipment;

packet data unit, PDU, session information for the terminal device.

In some embodiments, the service profile includes at least one of:

user plane UP service;

control plane CP services;

QoS requirements;

UP traffic and QoS requirements;

CP traffic and QoS requirements.

In some embodiments, the first feedback information includes at least one of:

information of admission control results of the terminal equipment;

information of service admission control results;

information of resource preparation.

admission success information;

admission failure information.

the number of the access terminal devices;

the proportion of the admission terminal devices;

Admitting the number of data radio bearers DRB;

the number of the admission signaling radio bearers SRB;

QoS information supported after migration;

maximum transmission bandwidth supported after migration;

information of terminal devices permitted to migrate.

a successful service index is admitted;

traffic index of admission failure.

In some embodiments, the first entity is a source integrated access and backhaul IAB host, the second entity is a target IAB host, and the third entity is an IAB node.

The communication device 1 is a second entity:

The transceiver module 11 is configured to receive migration request information of a third entity sent by the first entity, where the third entity and a terminal device under the third entity provide network access connection by the first entity.

The transceiver module 11 is further configured to send the first feedback information to the first entity.

In some embodiments, 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.

In some embodiments, the transceiver module 11 is further configured to send node migration request information of the third entity to the fourth entity, where the third entity and the terminal device under the third entity provide the network access connection by the second entity.

The transceiver module 11 is further configured to receive the second feedback information sent by the fourth entity.

In some embodiments, the migration request information and/or the node migration request information of the third entity comprises at least one of:

information for indicating a node migration mode;

information for node migration admission control.

related information of terminal equipment served by a third entity;

related information of the services supported by the third entity.

the number of terminal devices;

the number of data radio bearers DRB;

signaling the number of radio bearers SRBs;

quality of service QoS requirements for each terminal device;

quality of service QoS requirements for all terminal devices;

a core network node connected with the terminal equipment;

packet data unit, PDU, session information for the terminal device.

In some embodiments, the service profile includes at least one of:

user plane UP service;

control plane CP services;

QoS requirements;

UP traffic and QoS requirements;

CP traffic and QoS requirements.

In some embodiments, the first feedback information and/or the second feedback information comprises at least one of:

information of admission control results of the terminal equipment;

information of service admission control results;

information of resource preparation.

admission success information;

admission failure information.

the number of the access terminal devices;

the proportion of the admission terminal devices;

admitting the number of data radio bearers DRB;

the number of the admission signaling radio bearers SRB;

QoS information supported after migration;

maximum transmission bandwidth supported after migration;

information of terminal devices permitted to migrate.

a successful service index is admitted;

traffic index of admission failure.

With respect to the communication apparatus 1 in the above-described embodiment, the specific manner in which the respective modules perform operations has been described in detail in the embodiment concerning the method, and will not be explained in detail here.

The communication device 1 provided in the foregoing embodiments of the present disclosure achieves the same or similar beneficial effects as the migration method provided in some of the foregoing embodiments, and will not be described herein.

Referring to fig. 11, fig. 11 is a schematic structural diagram of another communication device 1000 according to an embodiment of the disclosure. The communication device 1000 may be the first entity, the second entity, a chip system, a processor, or the like that supports the first entity to implement the method, or a chip, a chip system, a processor, or the like that supports the second entity to implement the method. The communication device 1000 may be used to implement the method described in the above method embodiments, and reference may be made in particular to the description of the above method embodiments.

The communications 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. For example, a baseband processor or a central processing unit. The baseband processor may be configured to process communication protocols and communication data, and the central processor may be configured to control communication devices (e.g., the first entity, the second entity, the baseband chip, the terminal device chip, the DU or CU, etc.), execute a computer program, and process data of the computer program.

Optionally, the communication device 1000 may further include one or more memories 1002, on which a computer program 1004 may be stored, where the memory 1002 executes the computer program 1004, so that the communication device 1000 performs the method described in the above method embodiments. Optionally, the memory 1002 may also store data. The communication device 1000 and the memory 1002 may be provided separately or may be integrated.

Optionally, the communication device 1000 may further comprise a transceiver 1005, an antenna 1006. The transceiver 1005 may be referred to as a transceiver unit, a transceiver circuit, or the like, for implementing a transceiver function. The transceiver 1005 may include a receiver, which may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function, and a transmitter; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

Optionally, one or more interface circuits 1007 may also be included in the communications apparatus 1000. 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 method embodiments described above.

The communication device 1000 is a first entity: the processor 1001 is configured to execute S63 in fig. 6; the transceiver 1005 is used to perform S51 and S52 in fig. 5; s61 and S62 in fig. 6.

The communication device 1000 is a second entity: the transceiver 1005 is used to perform S71 and S72 in fig. 7; s81 and S83 in fig. 8; s91 and S92 in fig. 9; the processor 1001 is configured to execute S82 in fig. 8.

In one implementation, a transceiver for implementing the receive and transmit functions may be included in the processor 1001. For example, the transceiver may be a transceiver circuit, or an interface circuit. The transceiver circuitry, interface or interface circuitry for implementing the receive and transmit functions may be separate or may be integrated. The transceiver circuit, interface or interface circuit may be used for reading and writing codes/data, or the transceiver circuit, interface or interface circuit may be used for transmitting or transferring signals.

In one implementation, the processor 1001 may store a computer program 1003, where the computer program 1003 runs on the processor 1001, and may cause the communication device 1000 to execute 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.

In one implementation, the communications apparatus 1000 can include circuitry that can implement the functions of transmitting or receiving or communicating in the foregoing method embodiments. The processors and transceivers described in this disclosure may be implemented on integrated circuits (integrated circuit, ICs), analog ICs, radio frequency integrated circuits RFICs, mixed signal ICs, application specific integrated circuits (application specific integrated circuit, ASIC), printed circuit boards (printed circuit board, PCB), electronic devices, and the like. The processor and transceiver may also be fabricated using a variety of IC process technologies such as complementary metal oxide semiconductor (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 (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

The communication apparatus described in the above embodiment may be the first entity or the second entity, but the scope of the communication apparatus described in the present disclosure is not limited thereto, and the structure of the communication apparatus may not be limited by fig. 11. The communication means may be a stand-alone device or may be part of a larger device. For example, the communication device may be:

(1) A stand-alone integrated circuit IC, or chip, or a system-on-a-chip or subsystem;

(2) A set of one or more ICs, optionally including storage means for storing data, a computer program;

(3) An ASIC, such as a Modem (Modem);

(4) Modules that may be embedded within other devices;

(5) A receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handset, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligent device, and the like;

(6) Others, and so on.

In the case where the communication device may be a chip or a chip system, please refer to fig. 12, which is a block diagram of a chip provided in an embodiment of the disclosure.

Chip 1100 includes processor 1101 and interface 1103. Wherein the number of processors 1101 may be one or more, and the number of interfaces 1103 may be a plurality.

For the case where the chip is used to implement the functionality of the first entity in the embodiments of the present disclosure:

an interface 1103 for receiving the code instruction and transmitting the code instruction to the processor.

A processor 1101 for executing code instructions to perform the migration method as described in some embodiments above.

For the case where the chip is used to implement the functionality of the second entity in the embodiments of the present disclosure:

Optionally, the chip 1100 further comprises a memory 1102, the memory 1102 being used for storing the necessary computer programs and data.

Those of skill in the art will further appreciate that the various illustrative logical blocks (illustrative logical block) and steps (step) described in connection with the embodiments of the disclosure may be implemented by electronic hardware, computer software, or combinations of both. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation is not to be understood as beyond the scope of the embodiments of the present disclosure.

The embodiment of the present disclosure further provides a migration system, where the system includes the communication device as the first entity and the communication device as the second entity in the embodiment of fig. 10, or the system includes the communication device as the first entity and the communication device as the second entity in the embodiment of fig. 11.

The present disclosure also provides a readable storage medium having instructions stored thereon which, when executed by a computer, perform the functions of any of the method embodiments described above.

The present disclosure also provides a computer program product which, when executed by a computer, performs the functions of any of the method embodiments described above.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer programs. When the computer program is loaded and executed on a computer, the flow or functions described in accordance with the embodiments of the present disclosure are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer program may be stored in or transmitted from one computer readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means from one website, computer, server, or data center. 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 an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Those of ordinary skill in the art will appreciate that: the various numbers of first, second, etc. referred to in this disclosure are merely for ease of description and are not intended to limit the scope of embodiments of this disclosure, nor to indicate sequencing.

At least one of the present disclosure may also be described as one or more, a plurality may be two, three, four or more, and the present disclosure is not limited. In the embodiment of the disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "a", "B", "C", and "D", and the technical features described by "first", "second", "third", "a", "B", "C", and "D" are not in sequence or in order of magnitude.

The correspondence relationships shown in the tables in the present disclosure may be configured or predefined. The values of the information in each table are merely examples, and may be configured as other values, and the present disclosure is not limited thereto. In the case of the correspondence between the configuration information and each parameter, it is not necessarily required to configure all the correspondence shown in each table. For example, in the table in the present disclosure, the correspondence shown by some rows may not be configured. For another example, appropriate morphing adjustments, e.g., splitting, merging, etc., may be made based on the tables described above. The names of the parameters indicated in the tables may be other names which are understood by the communication device, and the values or expressions of the parameters may be other values or expressions which are understood by the communication device. When the tables are implemented, other data structures may be used, for example, an array, a queue, a container, a stack, a linear table, a pointer, a linked list, a tree, a graph, a structure, a class, a heap, a hash table, or a hash table.

Predefined in this disclosure may be understood as defining, predefining, storing, pre-negotiating, pre-configuring, curing, or pre-sintering.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

The foregoing is merely specific embodiments of the disclosure, but the protection scope of the disclosure is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the disclosure, and it is intended to cover the scope of the disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims

A migration method, the method performed by a first entity, comprising:

transmitting migration request information of a third entity to a second entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity;

and receiving the first feedback information sent by the second entity.
The method as recited in claim 1, further comprising:

according to the first feedback information, at least one of the following is executed:

performing migration judgment;

executing migration strategy generation;

migration is performed.
The method of claim 1 or 2, wherein the migration request information comprises at least one of:

information for indicating a node migration mode;

information for node migration admission control.
The method of claim 3, wherein the information for node migration admission control comprises at least one of:

the related information of the terminal equipment served by the third entity;

and the related information of the service supported by the third entity.
The method of claim 4, wherein the information regarding the terminal device served by the third entity comprises at least one of:

The number of terminal devices;

the number of data radio bearers DRB;

signaling the number of radio bearers SRBs;

quality of service QoS requirements for each terminal device;

quality of service QoS requirements for all terminal devices;

a core network node connected with the terminal equipment;

packet data unit, PDU, session information for the terminal device.
The method of claim 4, wherein the information related to the services supported by the third entity comprises one or more service configuration items;

the service configuration items comprise service indexes, service configuration files and backhaul BH related configurations.
The method of claim 6, wherein the service profile comprises at least one of:

user plane UP service;

control plane CP services;

QoS requirements;

UP traffic and QoS requirements;

CP traffic and QoS requirements.
The method of claim 1 or 2, wherein the first feedback information comprises at least one of:

information of admission control results of the terminal equipment;

information of service admission control results;

information of resource preparation.
The method of claim 8, wherein the information of the admission control result of the terminal device comprises admission success information, wherein the admission success information comprises at least one of:

The number of the access terminal devices;

the proportion of the admission terminal devices;

admitting the number of data radio bearers DRB;

the number of the admission signaling radio bearers SRB;

QoS information supported after migration;

maximum transmission bandwidth supported after migration;

information of terminal devices permitted to migrate.
The method of claim 8, wherein the resource preparation information comprises: backhaul BH configuration information.
The method according to any of claims 1 to 10, wherein the first entity is a source integrated access and backhaul, IAB, host, the second entity is a target, IAB, host, and the third entity is an IAB node.
A migration method, the method performed by a second entity, comprising:

receiving migration request information of a third entity sent by a first entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity;

and sending first feedback information to the first entity.
The method as recited in claim 12, further comprising:

and executing node migration admission control and/or resource preparation according to the migration request information so as to generate the first feedback information.
The method of claim 12 or 13, further comprising:

sending node migration request information of the third entity to a fourth entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the second entity;

and receiving second feedback information sent by the fourth entity.
The method of claim 14, wherein the migration request information and/or the node migration request information comprises at least one of:

information for indicating a node migration mode;

information for node migration admission control.
The method of claim 15, wherein the information for node migration admission control comprises at least one of:

the related information of the terminal equipment served by the third entity;

and the related information of the service supported by the third entity.
The method of claim 16, wherein the information regarding the terminal device served by the third entity comprises at least one of:

the number of terminal devices;

the number of data radio bearers DRB;

signaling the number of radio bearers SRBs;

quality of service QoS requirements for each terminal device;

Quality of service QoS requirements for all terminal devices;

a core network node connected with the terminal equipment;

packet data unit, PDU, session information for the terminal device.
The method of claim 16, wherein the information related to the services supported by the third entity comprises one or more service configuration items;

the service configuration items comprise service indexes, service configuration files and backhaul BH related configurations.
The method of claim 18, wherein the service profile comprises at least one of:

user plane UP service;

control plane CP services;

QoS requirements;

UP traffic and QoS requirements;

CP traffic and QoS requirements.
The method of claim 14, wherein the first feedback information and/or the second feedback information comprises at least one of:

information of admission control results of the terminal equipment;

information of service admission control results;

information of resource preparation.
The method of claim 20, wherein the information of the admission control result of the terminal device is admission success information, wherein the admission success information comprises at least one of:

the number of the access terminal devices;

The proportion of the admission terminal devices;

admitting the number of data radio bearers DRB;

the number of the admission signaling radio bearers SRB;

QoS information supported after migration;

maximum transmission bandwidth supported after migration;

information of terminal devices permitted to migrate.
The method of claim 20, wherein the resource preparation information comprises: backhaul BH configuration information.
The method according to any of claims 12 to 22, wherein the first entity is a source integrated access and backhaul, IAB, host, the second entity is a target, IAB, host, and the third entity is an IAB node.
A communication device, the device comprising:

the receiving and transmitting module is configured to send migration request information of a third entity to the second entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity;

the transceiver module is further configured to receive first feedback information sent by the second entity.
A communication device, the device comprising:

the receiving and transmitting module is configured to receive migration request information of a third entity sent by a first entity, wherein the third entity and terminal equipment under the third entity provide network access connection by the first entity;

The transceiver module is further configured to send first feedback information to the first entity.
A communication device, characterized in that the device comprises a processor and a memory, the memory having stored therein a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method according to any one of claims 1 to 11, or the processor executing the computer program stored in the memory to cause the device to perform the method according to any one of claims 12 to 23.
A communication device, comprising: a processor and interface circuit;

the interface circuit is used for receiving code instructions and transmitting the code instructions to the processor;

the processor for executing the code instructions to perform the method of any one of claims 1 to 11 or for executing the code instructions to perform the method of any one of claims 12 to 23.
A computer readable storage medium storing instructions which, when executed, cause the method of any one of claims 1 to 11 to be implemented or which, when executed, cause the method of any one of claims 12 to 23 to be implemented.