WO2022082690A1 - 群组切换的方法、装置和系统 - Google Patents

群组切换的方法、装置和系统 Download PDF

Info

Publication number
WO2022082690A1
WO2022082690A1 PCT/CN2020/123024 CN2020123024W WO2022082690A1 WO 2022082690 A1 WO2022082690 A1 WO 2022082690A1 CN 2020123024 W CN2020123024 W CN 2020123024W WO 2022082690 A1 WO2022082690 A1 WO 2022082690A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
iab
iab node
donor device
message
Prior art date
Application number
PCT/CN2020/123024
Other languages
English (en)
French (fr)
Inventor
路杨
李国荣
贾美艺
Original Assignee
富士通株式会社
路杨
李国荣
贾美艺
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 路杨, 李国荣, 贾美艺 filed Critical 富士通株式会社
Priority to CN202080105466.1A priority Critical patent/CN116235543A/zh
Priority to EP20958272.5A priority patent/EP4236451A4/en
Priority to PCT/CN2020/123024 priority patent/WO2022082690A1/zh
Priority to JP2023522551A priority patent/JP2023545809A/ja
Publication of WO2022082690A1 publication Critical patent/WO2022082690A1/zh
Priority to US18/133,746 priority patent/US20230308975A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0009—Control or signalling for completing the hand-off for a plurality of users or terminals, e.g. group communication or moving wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/087—Reselecting an access point between radio units of access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports

Definitions

  • This application relates to the field of communications.
  • Ultra-dense network is one of the goals of 5G. Deploying an NR network that does not require wired backhaul is very important for realizing 5G's ultra-dense network. As 5G millimeter wave reduces the cell coverage, the wireless self-backhaul system also needs to be multi-hop to meet the deployment requirements. 5G's high bandwidth, massive MIMO and beam systems make 5G easier than LTE to develop wireless self-backhaul systems for ultra-dense NR cells, in order to develop this multi-hop system with wireless self-backhaul, 3GPP started IAB in R16 (Integrated access and backhaul, access and backhaul integration) project research and standardization.
  • R16 Integrated access and backhaul, access and backhaul integration
  • Figure 1 is a schematic diagram of the IAB system.
  • the relay node supports both access and backhaul functions, and the wireless transmission link of the relay node is in the time domain,
  • the access link and the backhaul link are multiplexed in the frequency domain or the space domain, and the access link and the backhaul link can use the same or different frequency bands.
  • the relay node refers to an IAB-node (IAB node), which supports both access and backhaul functions.
  • IAB node The last hop access node on the network side is called IAB-donnor (IAB host), which supports the gNB function and supports IAB-node access. All UE data can be sent back to IAB-donor via IAB-node through one or more hops.
  • IAB-node The function of the IAB-node is divided into two parts, one part is the gNB-DU function, called IAB-DU, and the other part is the UE function, called IAB-MT.
  • the IAB-DU realizes the function of the network side device, connects to the downstream child IAB-node (child IAB node), provides NR air interface access to the UE and the downstream child IAB-node, and establishes an F1 connection with the IAB donor-CU.
  • IAB-MT implements some terminal equipment functions and is connected to the upstream parent IAB-node (parent IAB node) or IAB-donor DU.
  • IAB-MT includes physical layer, layer 2, RRC and NAS layer functions, and is also indirectly connected to IAB donor-CU and core network.
  • the IAB-node can access the network in SA mode or EN-DC mode.
  • FIG. 2 is a schematic diagram of an IAB architecture in SA mode.
  • Figure 3 is a schematic diagram of an IAB architecture in EN-DC mode.
  • FIG. 4 is a schematic diagram of a parent node (parent IAB-node) and a child node (child IAB-node).
  • Figure 5 is a schematic diagram of the F1 user plane protocol stack between the IAB-DU and the IAB-donor CU.
  • Figure 6 is a schematic diagram of the F1 control plane protocol stack between the IAB-DU and the IAB-donor CU.
  • the F1 user plane and the F1 control plane are built on the transport (IP) layer between IAB-DU and IAB-donor-CU. and one-hop wired backhaul.
  • the transport (IP) layer is carried on the backhaul adaptation protocol (BAP) sublayer.
  • BAP backhaul adaptation protocol
  • the BAP entity in the IAB-node implements the routing function of the IAB system, and the IAB-donor CU provides the routing table.
  • the BAP PDU is transmitted in the RLC channel of the backhaul link. Multiple RLC channels of the backhaul link can be configured by the IAB-donor to carry services with different priorities and QoS.
  • the BAP entity maps the BAP PDU to different backhaul channels. transmitted on the RLC channel.
  • the IAB-node moves under the same Donor, there is no need to establish a new F1 control plane connection with the donor, which has no effect on the downstream child IAB-node and UE, and the child IAB-node and UE can maintain the connection with the IAB-node.
  • the R17 IAB system will introduce the moving function of the IAB-node under different donors, but in this case, since the IAB-node switches to the new donor, it will have a great impact on the downstream child IAB-node and UE, child IAB-node and UE. A radio link failure will be experienced with the IAB-node.
  • the existing method of moving IAB-node between donors is that when the IAB-node switches to the new donor, the downstream child IAB-node and the UE and the IAB-node experience radio link failure, and then the downstream child IAB-node experiences radio link failure.
  • the IAB-node and the UE themselves initiate an RRC re-establishment process to reconnect to the IAB-node and establish an RRC connection with the new donor. In this way, service communication will be interrupted for a long time.
  • the downstream child IAB-node will also be re-established to a new donor, the UE served by the child IAB-node will also experience wireless link failure, so the UE served by the child IAB-node will also experience wireless link failure. There are longer communication interruptions.
  • embodiments of the present application provide a group switching method, apparatus, and system.
  • a group switching apparatus which is configured in a source Donor device, wherein the apparatus includes:
  • a first receiving unit which receives the measurement report sent by the relocated IAB node
  • a first sending unit which sends a first handover request message to the target Donor device, where the first handover request message includes the context information of the migrated IAB node and the sub-IAB node or UE served by it;
  • a second receiving unit which receives a first response message sent by the target Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node and its served sub-IAB node or UE;
  • a second sending unit which sends the RRC reconfiguration message to the migrated IAB node and its served sub-IAB node or UE.
  • a group switching apparatus which is configured in a source Donor device, wherein the apparatus includes:
  • a first receiving unit which receives the measurement report sent by the relocated IAB node
  • a first sending unit which sends a first handover request message to the target Donor device, where the first handover request message includes the context information of the migrated IAB node and the sub-IAB node or UE served by it;
  • a second receiving unit which receives a first response message sent by the target Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node;
  • a second sending unit which sends the RRC reconfiguration message to the migrating IAB node.
  • a group switching apparatus which is configured on a target Donor device, wherein the apparatus includes:
  • a first receiving unit which receives a first handover request message sent by the source Donor device, where the first handover request message includes the context information of the migrated IAB node and its served sub-IAB node or UE;
  • a first sending unit which sends a first response message to the source Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node and its served sub-IAB node or UE;
  • a first processing unit which establishes a new F1 connection with the migrated IAB node
  • a second receiving unit which receives an RRC reconfiguration complete message sent by the migrated IAB node and its served sub-IAB node or UE.
  • a group switching apparatus which is configured on a target Donor device, wherein the apparatus includes:
  • a first receiving unit which receives a first handover request message sent by the source Donor device, where the first handover request message includes the context information of the migrated IAB node and its served sub-IAB node or UE;
  • a first sending unit which sends a first response message to the source Donor device, where the first response message includes an RRC reconfiguration message for the migrating IAB node;
  • a first processing unit which establishes a new F1 connection with the migrated IAB node
  • a second sending unit which sends an RRC reconfiguration message to the sub-IAB node or UE served by the migrated IAB node through the new F1 connection;
  • a second receiving unit which receives an RRC reconfiguration complete message sent by the migrated IAB node and its served sub-IAB node or UE.
  • a group switching apparatus configured to migrate an IAB node, wherein the apparatus includes:
  • a first sending unit which sends a measurement report to the source Donor device
  • a first receiving unit which receives the RRC reconfiguration message sent by the source Donor device
  • a processing unit that establishes a new F1 connection with the target Donor device
  • a second receiving unit which receives the RRC reconfiguration message for the sub-IAB node or UE served by the migrated IAB node and sent by the source Donor device through the old F1 connection;
  • a second sending unit which sends the RRC reconfiguration message to the sub-IAB node or the UE;
  • a third sending unit which sends an RRC reconfiguration complete message to the target Donor device
  • a fourth sending unit which forwards the RRC reconfiguration complete message sent by the sub-IAB node or the UE to the target Donor device.
  • a group switching method which is configured for migrating an IAB node, wherein the apparatus includes:
  • a first sending unit which sends a measurement report to the source Donor device
  • a first receiving unit which receives the RRC reconfiguration message sent by the source Donor device
  • a processing unit that establishes a new F1 connection with the target Donor device
  • a second receiving unit receiving an RRC reconfiguration message for the sub-IAB node or UE served by the migrated IAB node and sent by the source Donor device through the new F1 connection;
  • a second sending unit which sends the RRC reconfiguration message to the sub-IAB node or the UE;
  • a third sending unit which sends an RRC reconfiguration complete message to the target Donor device
  • a fourth sending unit which forwards the RRC reconfiguration complete message sent by the sub-IAB node or the UE to the target Donor device.
  • a group switching device configured to migrate a sub-IAB node served by an IAB node, wherein the device includes:
  • a first receiving unit which receives the RRC reconfiguration message sent by the source Donor device
  • a processing unit that establishes a new F1 connection with the target Donor device
  • a first sending unit which sends an RRC reconfiguration complete message to the target Donor device.
  • a group switching apparatus which is configured to migrate a terminal device served by an IAB node, wherein the apparatus includes:
  • a receiving unit which receives the RRC reconfiguration message sent by the source Donor device or the target Donor device;
  • a sending unit which sends an RRC reconfiguration complete message to the target Donor device.
  • One of the beneficial effects of the embodiments of the present application is that according to the embodiments of the present application, when the IAB-node moves to the target Donor node, there is no need to re-establish the RRC connection with the CU of the target Donor node through the RRC re-establishment method, which can reduce the Service communication interruption time during the movement of the IAB-node.
  • Fig. 1 is a schematic diagram of the IAB system
  • Fig. 2 is the schematic diagram of the IAB architecture of SA mode
  • Fig. 3 is the schematic diagram of the IAB framework of EN-DC mode
  • Figure 4 is a schematic diagram of a parent node (parent IAB-node) and a child node (child IAB-node);
  • Fig. 5 is the schematic diagram of the F1 user plane protocol stack between IAB-DU and IAB-donor CU;
  • Fig. 6 is the schematic diagram of the F1 control plane protocol stack between IAB-DU and IAB-donor CU;
  • FIG. 7 is a schematic diagram of an implementation scenario of an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a group switching method according to an embodiment of the first aspect of the present application.
  • FIG. 9 is another schematic diagram of a group switching method according to an embodiment of the first aspect of the present application.
  • FIG. 10 is another schematic diagram of the group switching method according to the embodiment of the first aspect of the present application.
  • FIG. 11 is another schematic diagram of a group switching method according to an embodiment of the first aspect of the present application.
  • Fig. 12 is the schematic diagram of the entrance and exit of IAB node
  • FIG. 13 is a schematic diagram of a group switching method according to an embodiment of the second aspect of the present application.
  • FIG. 14 is another schematic diagram of a group switching method according to an embodiment of the second aspect of the present application.
  • 15 is a schematic diagram of a group switching method according to an embodiment of the third aspect of the present application.
  • 16 is another schematic diagram of a group switching method according to an embodiment of the third aspect of the present application.
  • 17 is a flowchart of a scenario of an embodiment of the present application.
  • FIG. 19 is a schematic diagram of a group switching apparatus according to an embodiment of the fourth aspect of the present application.
  • FIG. 20 is another schematic diagram of a group switching apparatus according to an embodiment of the fourth aspect of the present application.
  • FIG. 21 is another schematic diagram of a group switching apparatus according to an embodiment of the fourth aspect of the present application.
  • FIG. 22 is another schematic diagram of a group switching apparatus according to an embodiment of the fourth aspect of the present application.
  • FIG. 23 is a schematic diagram of a group switching apparatus according to an embodiment of the fifth aspect of the present application.
  • FIG. 24 is another schematic diagram of a group switching apparatus according to an embodiment of the fifth aspect of the present application.
  • 25 is a schematic diagram of a group switching apparatus according to an embodiment of the sixth aspect of the present application.
  • 26 is another schematic diagram of a group switching apparatus according to an embodiment of the sixth aspect of the present application.
  • FIG. 27 is a schematic diagram of a communication system according to an embodiment of the seventh aspect of the present application.
  • FIG. 28 is a schematic diagram of an IAB node according to an embodiment of the seventh aspect of the present application.
  • 29 is a schematic diagram of the Donor device according to the embodiment of the seventh aspect of the present application.
  • FIG. 30 is a schematic diagram of a terminal device according to an embodiment of the seventh aspect of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of numelation, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be referred to by these terms restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed items.
  • the terms “comprising”, “including”, “having”, etc. refer to the presence of stated features, elements, elements or components, but do not preclude the presence or addition of one or more other features, elements, elements or components.
  • the term "communication network” or “wireless communication network” may refer to a network that conforms to any of the following communication standards, such as New Radio (NR, New Radio), Long Term Evolution (LTE, Long Term Evolution), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access), etc.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to communication protocols at any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, 6G, etc., and/or other communication protocols currently known or to be developed in the future.
  • 1G generation
  • 2G 2.5G, 2.75G
  • 3G 3G
  • 4G 4.5G
  • future 5G, 6G, etc. and/or other communication protocols currently known or to be developed in the future.
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network devices may include but are not limited to the following devices: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobility management entity (MME, Mobile Management Entity), gateways, servers, radio network controllers (RNC, Radio Network Controller), base station controllers (BSC, Base Station Controller) and so on.
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include a remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low power node (eg femto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low power node eg femto, pico, etc.
  • base station may include some or all of their functions, each base station may provide communication coverage for a particular geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "User Equipment” refers to a device that accesses a communication network through a network device and receives network services, and may also be called “Terminal Equipment” (TE, Terminal Equipment).
  • a terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), a terminal, a user, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, etc. Wait.
  • the terminal device may include but is not limited to the following devices: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • Cellular Phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication device
  • handheld device machine type communication device
  • laptop computer Cordless phones, smartphones, smart watches, digital cameras, and more.
  • the terminal device may also be a machine or device that performs monitoring or measurement, such as but not limited to: Machine Type Communication (MTC, Machine Type Communication) terminals, In-vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • An embodiment of the present application proposes a method for group switching.
  • the method is used in the IAB system, and provides a method for the adaptive change of routing and topology caused by the movement of IAB-node between different donor devices.
  • all sub-IAB-nodes of the IAB-node and the UE perform handover under the control of the network side.
  • the source donor device and the target donor device perform handover preparation for the IAB-node, the UE served by it, the sub-IAB-node, and the UE served by the sub-IAB-node.
  • the UE and the sub-IAB-node, and the UE served by the sub-IAB-node send a reconfiguration message, and these sub-IAB-nodes and the UE transmit the reconfiguration completion message to the CU of the target Donor device through the IAB-node to complete the reconfiguration to the target Donor device.
  • connection it is not necessary to re-establish the RRC connection with the CU of the target Donor device through the RRC re-establishment method.
  • the interruption time of service communication during the movement of the IAB-node can be reduced.
  • FIG. 7 is a schematic diagram of an implementation scenario of an embodiment of the present application.
  • a migrating IAB-node (Migrating IAB-node) 701 may move between multiple Donor devices (IAB donors) 702 and 703 .
  • Both the child IAB node 704 and the UE 705 served by the IAB node 701 perform handover under the control of the network side.
  • FIG. 7 only shows one migrated IAB node 701, one source Donor device 702, one target Donor device 703, one UE 705 served by the migrated IAB node 701, and two child IAB nodes 704, but the present application is not limited to this .
  • the IAB-node is divided into an IAB-DU part and an IAB-MT part.
  • the IAB-DU implements the DU equipment function on the network side. It provides NR air interface access to the UE and MT and establishes an F1 connection with the IAB donor-CU.
  • the IAB-MT implements the terminal equipment function.
  • IAB-node moving between different donor nodes can be divided into three independent processes:
  • the switching of the IAB-MT part means that the PCell serving the IAB-node is switched from the source Donor device to the target Donor device, the IAB-node disconnects the RRC connection with the source Donor device, and establishes an RRC connection with the target Donor device.
  • the handover of the IAB-DU part means that the F1 connection between the IAB-node and the CU is switched from the source Donor device to the target Donor device, and the IAB-node serves as a new serving cell to provide NR air interface access.
  • Scenario 1 The IAB-MT of the Migrating IAB-node (migrating IAB node) and the IAB-MT of the child IAB-node and the UE of the migrating IAB-node service are switched at the same time;
  • the source Donor device sends an RRC reconfiguration message to the migrating IAB-node, sub-IAB-node and UE at the same time;
  • the source Donor or the target Donor sends the message to the child IAB-node and UE. Send an RRC reconfiguration message.
  • the embodiment of the present application provides a group switching method.
  • FIG. 8 is a schematic diagram of a group switching method according to an embodiment of the present application, which is described from the side of the source Donor device in the IAB network. As shown in Figure 8, the method includes:
  • the target Donor device 803 Receive a first response message sent by the target Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node and its served sub-IAB node or UE;
  • FIG. 9 is another schematic diagram of a group switching method according to an embodiment of the present application, which is described from the side of the target Donor device in the IAB network.
  • the method in FIG. 9 corresponds to the method in FIG. 8 .
  • the method includes:
  • FIG. 10 is another schematic diagram of a group switching method according to an embodiment of the present application, which is described from the side of the source Donor device in the IAB network. As shown in Figure 10, the method includes:
  • 1002 Send a first handover request message to the target Donor device, where the first handover request message includes context information of the migrated IAB node and its served sub-IAB node or UE;
  • 1003 Receive a first response message sent by the target Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node;
  • FIG. 11 is another schematic diagram of a group switching method according to an embodiment of the present application, which is described from the side of the target Donor device in the IAB network.
  • the method in FIG. 11 corresponds to the method in FIG. 10 .
  • the method includes:
  • 1102 Send a first response message to the source Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node;
  • FIGS. 8 and 9 correspond to the foregoing scenario 1
  • the methods in FIGS. 10 and 11 correspond to the foregoing scenario 2.
  • the method of this embodiment of the present application when an IAB node moves between different Donor devices, it is not necessary to re-establish an RRC The RRC connection is re-established between the method and the target Donor device, which can reduce the interruption time of service communication during the movement of the IAB node.
  • the context information of the migrated IAB node includes: the IAB-DU context and the IAB-MT context of the migrated IAB node; the context information of the child IAB node includes: the child IAB node IAB-DU context and IAB-MT context.
  • the IAB-DU context of the relocated IAB node includes: the serving cell information of the IAB-DU of the relocated IAB node under the source Donor device.
  • the serving cell information includes at least one of the following: a new wireless cell global identifier (Cell Global Identifier, NR CGI); a new wireless physical cell ID (Physical Cell ID, NR PCI); the public land mobile service served by the IAB-DU Network (Public Land Mobile Network, PLMN); uplink and downlink transmission frequency and bandwidth.
  • a new wireless cell global identifier Cell Global Identifier, NR CGI
  • a new wireless physical cell ID Physical Cell ID
  • PLMN Public Land Mobile Network
  • uplink and downlink transmission frequency and bandwidth uplink and downlink transmission frequency and bandwidth.
  • the IAB-MT context of the above-mentioned migrating IAB node includes BAP configuration information.
  • the BAP configuration information includes a BAP address, a transport layer (IP) address, a default uplink backhaul RLC channel identifier and/or a default uplink BAP route identifier allocated by the source Donor device to the IAB node.
  • the default upstream BAP route identifier refers to a default destination BAP address and a default path identifier.
  • the above-mentioned first handover request message further includes return information configured by the source Donor device for the migrating IAB node or the sub-IAB node.
  • the returned information includes at least one of the following:
  • Figure 12 shows the relationship between the ingress and egress of an IAB node.
  • the returned information includes at least one of the following:
  • the BAP routing identifier used by F1 control plane data or non-F1 data, the BAP address of the next hop node, and the backhaul RLC channel identifier used by F1 control plane data or non-F1 data, the BAP address of the next hop node, and the backhaul RLC channel identifier.
  • the BAP routing identifier includes a destination BAP address and a path ID identifier.
  • An example of a BAP route identification is given below:
  • the above-mentioned first handover request message further includes: topology information, where the topology information includes the topology relationship between the migrated IAB node and the sub-IAB node or UE served by it, or includes the sub-IAB Topological relationship between a node and the child IAB nodes or UEs it serves.
  • the above-mentioned first handover request message further includes: address request information, where the address request information is used to request the target Donor device to allocate a new transport layer (IP) address or BAP address.
  • address request information is used to request the target Donor device to allocate a new transport layer (IP) address or BAP address.
  • the target Donor device in the aforementioned 903 and 1103, establishes a new F1 connection with the migrating IAB node, which may be: the target Donor device receives the F1 establishment request message sent by the migrating IAB node; sends the F1 establishment request message to the migrating IAB node; response message.
  • the target Donor device establishes a new F1 connection with the migration IAB node.
  • the target node may further establish a new F1 connection with the child IAB node. Set up in the same way as before.
  • the present application is not limited to this.
  • the target Donor device can also configure backhaul RLC channel mapping and BAP routing configuration for the migrating IAB node.
  • the BAP routing configuration includes a routing identifier, a corresponding relationship between the routing identifier and the next-hop BAP address.
  • the target Donor device may also send a first indication to the source Donor device message, and the first indication message is used to instruct the source Donor device to send an RRC reconfiguration message to the sub-IAB node or the UE.
  • the context information of the migrated IAB node and the context information of the sub-IAB node or the UE are included in the same Xn message or different Xn messages.
  • the source Donor device first sends an Xn message containing the context information of the migrated IAB node to the target Donor, so that the target Donor first sends an RRC reconfiguration message for the migrated IAB node.
  • the target Donor device may also send a second indication message to the source Donor device.
  • the second indication message instructs the source Donor device to send an Xn message containing the context of the sub-IAB node or UE to the target Donor device, so that the target Donor sends an RRC reconfiguration message for the sub-IAB node or UE.
  • the RRC reconfiguration message for the migrated IAB node and the RRC reconfiguration message for the sub-IAB node or UE are included in the same Xn message or different Xn messages.
  • the target Donor first sends an RRC reconfiguration message for the migrating IAB node, and after the target Donor device receives the RRC reconfiguration complete message sent by the migrating IAB node, or after establishing a new F1 connection with the migrating IAB node, the target Donor The Donor device then sends an Xn message including an RRC reconfiguration message for the sub-IAB node or UE to the source Donor device.
  • the target Donor device may also The child IAB node is configured with BAP routing. Since the child IAB node may not change the backhaul RLC channel mapping after switching to the target Donor, the target Donor device can configure BAP routing configuration only for the child IAB node.
  • the RRC reconfiguration message for the migrated IAB node includes at least one of the following: handover to the default uplink backhaul RLC channel identifier (used for F1 interface control plane or non-F1 data) used by the target Donor device; handover To the default BAP route identifier used by the target Donor device (for F1 control plane data or non-F1 data); switch to the BAP address used by the target Donor device; switch to the transport layer address used by the target Donor device; and switch to the target Donor device The security key configuration used.
  • the default uplink backhaul RLC channel identifier used for F1 interface control plane or non-F1 data
  • the target Donor device for F1 control plane data or non-F1 data
  • switch to the BAP address used by the target Donor device switch to the transport layer address used by the target Donor device
  • switch to the target Donor device The security key configuration used.
  • the RRC reconfiguration message for the migrating IAB node further includes the backhaul RLC channel mapping and BAP routing configuration used by the handover to the target Donor device.
  • the RRC reconfiguration message for the child IAB node includes at least one of the following: switching to the default BAP routing identifier (used for F1 control plane data or non-F1 data) used by the target Donor device; switching to the The BAP address used by the target Donor device; the transport layer address used by the switch to the target Donor device; and the security key configuration used by the switch to the target Donor device.
  • BAP routing identifier used for F1 control plane data or non-F1 data
  • the default uplink backhaul RLC channel identifier for F1 control plane data or non-F1 data may not be changed, and the RRCReconfiguration message does not Must contain the new default upstream backhaul RLC channel.
  • the RRC reconfiguration message for the child IAB node further includes: switching to the BAP routing configuration used by the target Donor device.
  • the backhaul RLC channel mapping includes at least one of the following:
  • the BAP routing configuration includes at least one of the following:
  • the BAP routing identifier includes the destination BAP address and the path ID identifier.
  • the RRC reconfiguration message for the UE includes: switching to the security key configuration used by the target Donor device.
  • FIGS. 8 to 11 only schematically illustrate the embodiments of the present application, but the present application is not limited thereto.
  • the execution order of each operation can be adjusted appropriately, and other operations can be added or some of the operations can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the descriptions in the above-mentioned FIG. 8 to FIG. 11 .
  • the interruption time of service communication during the movement of the IAB node can be reduced.
  • the embodiment of the present application provides a group switching method, which is described from the side of the IAB node migrating in the IAB network.
  • FIG. 13 is a schematic diagram of a group switching method according to an embodiment of the present application.
  • the method is a process of migrating one side of an IAB node corresponding to the methods in FIGS. 8 and 9 , and the content is the same as that in the methods in FIGS. 8 and 9 . The description will not be repeated.
  • the method includes:
  • FIG. 14 is another schematic diagram of a group switching method according to an embodiment of the present application.
  • the method is a process of migrating one side of an IAB node corresponding to the methods in FIG. 10 and FIG. 11 , and the method is the same as that in the methods in FIGS. The content will not be repeated.
  • the method includes:
  • establishing a new F1 connection with the target Donor device may be: sending an F1 establishment request message to the target Donor, requesting to establish a new F1 connection with the target Donor device; then, receiving The F1 establishment response message sent by the target Donor device, thereby establishing a new F1 connection with the target Donor device.
  • the migrating IAB node maintains the old F1 connection with the source Donor device, and if one of the following conditions is satisfied Release the old F1 connection to the source Donor device:
  • the migrating IAB node sends an F1 release request message to the source Donor device to release the old F1 connection with the source Donor device.
  • the migrated IAB node sends the RRC reconfiguration message for the child IAB node or UE received from the old F1 connection to the child The IAB node or the UE.
  • the RRC reconfiguration complete message of the sub-IAB node or the UE is forwarded to the target Donor device. In this way, it can be ensured that the migrating node successfully sends the RRC reconfiguration complete message of the child IAB node or the UE to the target Donor device through the new F1 connection.
  • the migrating IAB node may also receive the backhaul RLC channel configured by the target Donor device Mapping and BAP routing configuration.
  • the RRC reconfiguration message includes one of the following: switching to the default uplink backhaul RLC channel identifier used by the target Donor device; switching to the default BAP routing identifier used by the target Donor device; switching to the target Donor device The BAP address used; the transport layer address used by the switch to the target Donor device; and the security key configuration used by the switch to the target Donor device.
  • the RRC reconfiguration message further includes: the backhaul RLC channel mapping and BAP routing configuration used by the handover to the target Donor device.
  • the migrating IAB node can apply the backhaul RLC channel mapping and BAP routing configuration.
  • FIG. 13 and FIG. 14 only schematically illustrate the embodiments of the present application, but the present application is not limited thereto.
  • the execution order of each operation can be adjusted appropriately, and other operations can be added or some of the operations can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the descriptions in the above-mentioned FIG. 13 and FIG. 14 .
  • the interruption time of service communication during the movement of the IAB node can be reduced.
  • An embodiment of the present application provides a group switching method, which is described from the side of a sub-IAB node served by a migrating IAB node in an IAB network, and the same content as the embodiments of the first aspect and the second aspect will not be repeated. .
  • FIG. 15 is a schematic diagram of a group switching method according to an embodiment of the present application. As shown in FIG. 15 , the method includes:
  • the sub-IAB nodes served by the IAB node can be switched accordingly, and there is no need to re-establish an RRC connection with the target Donor device through the RRC re-establishment method , which can reduce the interruption time of service communication during the movement of the IAB node.
  • establishing a new F1 connection between the child IAB node and the target Donor device may be: the child IAB node sends an F1 establishment request message to the target Donor, requesting to establish a connection between the child IAB node and the target Donor device The F1 connection is received; the F1 establishment response message sent by the target Donor device is received, thereby establishing an F1 connection with the target Donor device.
  • the child IAB node may maintain the old F1 connection with the source Donor device, and under one of the following conditions Release the old F1 connection with the source Donor device when satisfied, for example:
  • the sub-IAB node may send an F1 release request message to the source Donor device to release the connection between the source Donor device and the source Donor device. the old F1 connection.
  • the sub-IAB node may also receive an F1AP (F1 Application Protocol, F1 interface application protocol) message sent by the target Donor device through the new F1 connection, and send the The RRC reconfiguration message is sent to the grandchild IAB node or UE.
  • F1AP F1 Application Protocol, F1 interface application protocol
  • the F1AP message includes an RRC reconfiguration message for the grandchild IAB node or UE served by the child IAB node.
  • the sub-IAB node may also receive the BAP route configured by the target Donor configuration.
  • the content included in the BAP routing configuration reference may be made to the embodiment of the first aspect, which will not be repeated here.
  • the sub-IAB node may also receive an F1AP message sent by the source Donor device through the old F1 connection with the sub-IAB node, and send an RRC reconfiguration message to the serving The grandchild IAB node or UE.
  • the F1AP message includes an RRC reconfiguration message for the grandchild IAB node or UE served by the child IAB node.
  • the child IAB node after 1502, that is, after the establishment of the new F1 connection is completed, the child IAB node sends the RRC reconfiguration message to the serving grandchild IAB node or UE.
  • the RRC reconfiguration complete message of the serving grandchild IAB node or UE is forwarded to the target Donor device. In this way, it can be guaranteed that the child IAB node successfully sends the RRC reconfiguration complete message of the served grandchild IAB node or UE to the target Donor device through the new F1 connection.
  • the RRC reconfiguration message for the above-mentioned sub-IAB node includes one of the following: switching to the default uplink backhaul RLC channel identifier used by the target Donor device; switching to the default BAP routing identifier used by the target Donor device; switching to the BAP address used by the target Donor device; switch to the transport layer address used by the target Donor device; and switch to the security key configuration used by the target Donor device.
  • the RRC reconfiguration message for the above-mentioned sub-IAB node may further include: switching to the BAP routing configuration used by the target Donor device. Therefore, after the child IAB node determines that the migrating IAB node has completed the handover to the target Donor device, and after sending the RRC reconfiguration complete message to the target Donor device, the child IAB node can apply the BAP routing configuration.
  • An embodiment of the present application further provides a method for group switching, which is described from the side of a terminal device serving an IAB node in an IAB network, where the same content as the embodiments of the first aspect and the second aspect will not be repeated. .
  • the RRC reconfiguration message may include: switching to the security key configuration used by the target Donor device.
  • the terminal device served by the IAB node can be switched accordingly, and there is no need to re-establish an RRC connection with the target Donor device through the RRC re-establishment method.
  • the interruption time of service communication during the movement of the IAB node can be reduced.
  • FIG. 15 and FIG. 16 only schematically illustrate the embodiments of the present application, but the present application is not limited thereto.
  • the execution order of each operation can be adjusted appropriately, and other operations can be added or some of the operations can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the descriptions in the above-mentioned FIG. 15 and FIG. 16 .
  • the interruption time of service communication during the movement of the IAB node can be reduced.
  • Fig. 17 is the signaling interaction flow chart corresponding to the aforementioned scenario 1.
  • the IAB-MT of the Migrating IAB-node and the IAB-MT of the sub-IAB-node and the UE serving the migrating IAB-node are switched at the same time.
  • the source Donor can send an RRC reconfiguration message to the migrating IAB-node, the downstream child IAB-node and the UE at the same time.
  • the process includes:
  • the source Donor receives the measurement report sent by the migrating IAB-node, and determines that the migrating IAB-node needs to be switched to the target Donor.
  • the source Donor sends a first handover request message to the target Donor, where the first handover request message includes context information for the migrating IAB-node, the downstream sub-IAB-node, and the UE.
  • the handover preparation information for each IAB-node and UE may be sent through different Xn messages, or may be sent in the same Xn message.
  • the target Donor sends a UE CONTEXT SETUP REQUEST message to the parent IAB-node of the migrating IAB-node under the target Donor to create a context and radio bearer for the migrating IAB-node in the parent IAB-node under the target Donor.
  • the target Donor receives the UE CONTEXT SETUP RESPONSE message sent by the parent IAB-node of the migrating IAB-node under the target Donor.
  • the steps of establishing the IAB-node or UE context and radio bearer in the migrating IAB-node for the child IAB-node or UE can be omitted.
  • the target Donor sends a first response message to the source Donor, where the first response message includes an RRC reconfiguration message for the migrating IAB-node, the sub-IAB-node, and the UE.
  • the RRC reconfiguration message for each IAB-node and UE may be sent through different Xn messages, or may be sent in the same Xn message.
  • the source Donor sends a DL RRC MESSAGE TRANSFER or UE CONTEXT MODIFICATION REQUEST to the parent IAB-node of the migrating IAB-node under the source Donor, which contains the RRCReconfiguration message for the migrating IAB-node.
  • the RRCReconfiguration message for migrating IAB-node includes at least the following configuration information:
  • the RRCReconfiguration message may also include backhaul information used after switching to the target Donor, for example, the backhaul RLC channel mapping information and BAP routing configuration information configured by the target Donor to the migrating IAB-node.
  • the returned RLC channel mapping information is, for example:
  • the BAP routing configuration information is, for example:
  • the source Donor sends an RRCReconfiguration message to the migrating IAB-node. After that, the migrating IAB-node can continue to provide the original air interface access service to the child IAB-node or UE, or it can stop the original air interface access service.
  • the source Donor sends an F1AP message (DL RRC MESSAGE TRANSFER or UE CONTEXT MODIFICATION REQUEST) through the F1 connection with the migrating IAB-node, which contains the RRCReconfiguration message for the child IAB-node or UE.
  • F1AP message DL RRC MESSAGE TRANSFER or UE CONTEXT MODIFICATION REQUEST
  • the RRCReconfiguration message for the child IAB-node includes, for example: switching to the default BAP routing configuration used by the target Donor device (for F1 interface control plane data or non-F1 data); switching to the default BAP routing configuration used by the target Donor device; BAP address; switch to the transport layer (IP) address configuration used by the target Donor device; switch to the security key configuration used by the target Donor.
  • BAP routing configuration used by the target Donor device
  • BAP address for F1 interface control plane data or non-F1 data
  • IP transport layer
  • the default uplink return RLC channel identifier for the F1 interface control plane data or non-F1 data may not be changed, so the RRCReconfiguration message does not necessarily contain The new default uplink backhaul RLC channel identifier.
  • the RRCReconfiguration message for the child IAB-node may also include the BAP routing configuration used after switching to the target Donor.
  • the BAP routing configuration information is, for example:
  • the sub-IAB-node does not necessarily need to change the RLC channel mapping relationship of the F1 interface user plane or the sub-node return data before and after the handover, it is not necessary to reconfigure the RLC channel mapping information.
  • the RRCReconfiguration message for the UE at least includes: switching to the security key configuration used by the target Donor. Because the migrating IAB-node does not necessarily change the PCI (Physical Cell Identity, physical cell identity) and frequency of the serving cell before and after the handover, the target Donor only needs to configure a new security key for the UE.
  • PCI Physical Cell Identity, physical cell identity
  • the Migrating IAB-node forwards the RRCReconfiguration message to the child IAB-node or UE.
  • the aforementioned steps 1706 and 1707 and the aforementioned steps 1708 and 1709 do not have a sequential relationship, for example, the step 1708 may be performed before the step 1706 .
  • Migrating IAB-node uses the configured new transport layer (IP) address to connect to the OAM through the target Donor, download the OAM data, and establish a new SCTP connection with the target Donor.
  • IP transport layer
  • Migrating IAB-node sends an F1AP message (F1 Setup Request message) to the target Donor through the new SCTP connection, and receives the F1 Setup Response sent by the target Donor, thereby establishing a new F1 connection with the target Donor.
  • F1AP message F1 Setup Request message
  • the messages in steps 1710 and 1711 can be forwarded to the target Donor through the old path, that is, the transmission path of the messages in steps 1710 and 1711 It is: migrating IAB-node ⁇ source Donor ⁇ target Donor.
  • the Migrating IAB after the Migrating IAB has established a new F1 connection, it can be used as the IAB-node under the target Donor to provide new air interface access services for the child IAB-node or UE.
  • the child IAB-node uses the configured new transport layer (IP) address to connect to the OAM through the target Donor, download the OAM data, and establish a new SCTP connection with the target Donor.
  • IP transport layer
  • the child IAB-node sends an F1AP message (F1 Setup Request) to the target Donor through the new SCTP connection, and receives the F1 setup response sent by the target Donor, thereby establishing a new F1 connection with the target Donor.
  • F1AP message F1 Setup Request
  • the messages in steps 1712 and 1713 can be forwarded to the target Donor through the original path, that is, the transmission paths of the messages in steps 1712 and 1713 are: child IAB -node ⁇ migrating IAB-node ⁇ source Donor ⁇ target Donor.
  • step 1710 can only be executed after step 1707
  • step 1712 can only be executed after step 1709 is completed.
  • the Migrating IAB-node initiates random access to the parent IAB-node under the target Donor and sends an RRCReconfigurationComplete message.
  • the parent IAB-node under the target Donor puts this message in the F1AP message (UL RRC MESSAGE TRANSFER) and passes it to the target Donor .
  • the migrating IAB-node can send its own signaling or data through the new uplink backhaul RLC channel and the new default BAP path.
  • step 1714 only needs to be executed after step 1707 .
  • the target Donor configures the new backhaul RLC channel mapping and BAP routing configuration for the migrating IAB-node through the F1AP message. Afterwards, the migrating IAB-node can send signaling or data of the served UE and the child IAB-node through the new backhaul RLC channel and the new BAP path.
  • step 1715 is optional.
  • the child IAB-node or UE sends an RRCReconfigurationComplete message to the migrating IAB-node, and the migrating IAB-node puts this message in the F1AP message (UL RRC MESSAGE TRANSFER) and forwards it to the target Donor through the new F1 connection. Afterwards, the child IAB-node can send the signaling or data generated by itself through the new default BAP path.
  • the target Donor configures a new BAP route for the child IAB-node through the F1AP message.
  • the child IAB-node can then send signaling or data of the served UE and the IAB-node (referred to as the grandchild IAB-node) through the new BAP path.
  • step 1717 is optional.
  • steps 1715 and 1717 need to be completed after step 1714, that is, after the target Donor receives the RRCReconfigurationComplete sent by the migrating IAB-node.
  • the migrating IAB-node and the sub-IAB-node and the UE served by the migrating IAB-node perform handover at the same time, and multiple steps can be executed in parallel, so the overall handover process takes a short time.
  • step 1716 should be after step 1711 Execute, or, step 1709 can also be executed after step 1711, that is, after the migrating IAB-node and the target Donor have established a new F1 connection.
  • the sub-IAB-node or UE can send the RRCReconfigurationComplete message after detecting the new PCI of the migrating IAB-node or the cell reference signal of the new frequency, which can ensure a successful handover.
  • Figure 18 is an information exchange flow chart corresponding to the foregoing scenario 2.
  • the sub-IAB-node of the migrating IAB-node service and the UE can be switched after the IAB-DU or IAB-MT of the migrating IAB-node is switched.
  • the source Donor or the target Donor establishes a new F1 connection with the migrating IAB-node, or after the target Donor receives the RRCReconfigurationComplete message sent by the migrating IAB-node, it sends an RRC reconfiguration message to the child IAB-node and the UE.
  • the process includes:
  • the source Donor receives the measurement report sent by the migrating IAB-node MT and determines that the migrating IAB-node needs to be switched to the target Donor.
  • the source Donor sends a first handover request message to the target Donor, where the first handover request message includes context information for the migrating IAB-node, the child IAB-node, and the UE.
  • the context information for each IAB-node and UE may be sent through different Xn messages, or may be sent in the same Xn message.
  • the first handover request in this step may only include the context information for the migrating IAB-node.
  • the target Donor After the target Donor establishes a new F1 connection with the migrating IAB-node, or after the target Donor receives the migrating IAB-node
  • the context information of the child IAB-node and the UE is sent to the target Donor.
  • the target Donor sends a UE CONTEXT SETUP REQUEST message to the parent IAB-node of the migrating IAB-node under the target Donor, creating a context and a radio bearer for the migrating IAB-node in the parent IAB-node under the target Donor.
  • the target Donor receives the UE CONTEXT SETUP RESPONSE message sent by the parent IAB-node under the target Donor.
  • the steps of establishing the IAB-node or UE context and radio bearer in the migrating IAB-node DU for the child IAB-node or UE can be omitted. .
  • the target Donor sends a first response message to the source Donor, where the first response message includes an RRC reconfiguration message for the migrating IAB-node, the sub-IAB-node, and the UE.
  • the RRC reconfiguration message for each IAB-node and UE may be sent through different Xn messages, or may be sent in the same Xn message.
  • the first response message in this step may only include the RRC for the migrating IAB-node Reconfiguration messages (ie handover commands).
  • the source Donor sends an F1AP message (DL RRC MESSAGE TRANSFER or UE CONTEXT MODIFICATION REQUEST) to the parent IAB-node of the migrating IAB-node under the source Donor, which contains an RRCReconfiguration message for the migrating IAB-node.
  • F1AP message DL RRC MESSAGE TRANSFER or UE CONTEXT MODIFICATION REQUEST
  • the RRCReconfiguration message for migrating IAB-node includes:
  • the RRCReconfiguration message can also include the return information used after switching to the target Donor, for example: the return RLC channel mapping information and BAP routing configuration information configured by the target Donor to the migrating IAB-node:
  • the above-mentioned return RLC channel mapping information includes, for example:
  • the above-mentioned BAP routing configuration information includes, for example:
  • the source Donor sends an RRCReconfiguration message to the migrating IAB-node.
  • the Migrating IAB-node needs to continue to provide the original air interface access service to the child IAB-node or UE.
  • Migrating IAB-node uses the configured new transport layer (IP) address to connect to the OAM through the target Donor, download the OAM data, and establish a new SCTP connection with the target Donor.
  • IP transport layer
  • the Migrating IAB-node sends an F1AP message (F1Setup Request) message to the target Donor through the new SCTP connection, and receives the F1 Setup Response message sent by the target Donor to establish a new F1 connection with the target Donor.
  • F1AP message F1Setup Request
  • the messages in steps 1810 and 1811 can be forwarded to the target Donor through the old path, that is, the messages in steps 1810 and 1811
  • the transmission path is: migrating IAB-node ⁇ source Donor ⁇ target Donor.
  • the Migrating IAB-node after the Migrating IAB-node establishes a new F1 connection, it can act as the IAB node under the target Donor, thereby providing new air interface access services to the child IAB-node or UE.
  • Mode 1 The source Donor sends an F1AP message (DL RRC MESSAGE TRANSFER or UE CONTEXT MODIFICATION REQUEST) to the migrating IAB-node through the old F1 connection, which contains the RRCReconfiguration message for the child IAB-node or UE.
  • F1AP message DL RRC MESSAGE TRANSFER or UE CONTEXT MODIFICATION REQUEST
  • Migrating IAB-node forwards RRCReconfiguration message to child IAB-node or UE.
  • This method applies to the scenario where the F1 connection between the migrating IAB-node and the source Donor is still maintained after the new F1 connection is established.
  • Method 1 The target Donor sends a second response message including an RRC Reconfiguration message for the child IAB-node or the served UE to the source Donor, so that the source Donor sends an RRCReconfiguration message for the child IAB-node or the UE.
  • Method 2 The target Donor sends a first indication message to the source Donor to trigger the source Donor to send the RRCReconfiguration message of the sub-IAB-node or the UE.
  • Method 3 The target Donor sends a second indication message to the source Donor to trigger the source Donor to send an Xn message containing the context information of the sub-IAB-node or UE to the target Donor, so that the target Donor sends the target Donor to the source Donor for the sub-IAB-node or UE.
  • the RRC Reconfiguration message of the UE so that the source Donor sends the RRCReconfiguration message of the child IAB-node or the UE.
  • Mode 2 The target Donor sends an F1AP message (DL RRC MESSAGE TRANSFER or UE CONTEXT MODIFICATION REQUEST) to the migrating IAB-node through the new F1 connection, which contains the RRCReconfiguration message for the child IAB-node or UE.
  • F1AP message DL RRC MESSAGE TRANSFER or UE CONTEXT MODIFICATION REQUEST
  • Migrating IAB-node forwards RRCReconfiguration message to child IAB-node or UE.
  • This method applies to the scenario where the old F1 connection between the migrating IAB-node and the source Donor is released immediately after the new F1 connection is established.
  • the RRCReconfiguration message for the child IAB-node includes: switching to the default BAP routing identifier used by the target Donor; switching to the BAP address used by the target Donor; switching to the transport layer used by the target Donor (IP) address configuration; switch to the security key configuration used by the target Donor.
  • IP target Donor
  • the RRCReconfiguration message for the UE at least contains the security key configuration used by the handover to the target Donor. Because the migrating IAB-node does not necessarily change the PCI (Physical Cell Identity, physical cell identity) and frequency of the serving cell before and after the handover, the target Donor only needs to configure a new security key for the UE.
  • PCI Physical Cell Identity, physical cell identity
  • the child IAB-node uses the configured new transport layer (IP) address to connect to the OAM through the target Donor, download the OAM data, and establish a new SCTP connection with the target Donor CU.
  • IP transport layer
  • the child IAB-node sends an F1AP message (F1 Setup Request) to the target Donor through the new SCTP connection, and receives the F1 setup response sent by the target Donor, thereby establishing a new F1 connection with the target Donor.
  • F1AP message F1 Setup Request
  • the messages in steps 1812 and 1813 can be forwarded to the target Donor through the original, that is, the transmission paths of the messages in steps 1812 and 1813 are: IAB-node ⁇ migrating IAB-node ⁇ source Donor ⁇ target Donor.
  • the Migrating IAB after the Migrating IAB has established a new F1 connection, it can be used as the IAB-node under the target Donor, thereby providing new air interface access services for the child IAB-node or UE.
  • the Migrating IAB-node initiates random access to the parent IAB-node under the target Donor and sends the RRCReconfigurationComplete message, and the target parent IAB-node puts this message in the F1AP message (UL RRC MESSAGE TRANSFER) and transmits it to the target Donor. After that, the migrating IAB-node can send its own signaling or data through the new uplink backhaul RLC channel and the new default BAP path.
  • step 1813 only needs to be executed after step 1807 .
  • the target Donor configures the new backhaul RLC channel mapping and BAP routing configuration for the migrating IAB-node through the F1AP message. Afterwards, the migrating IAB-node can send signaling or data of the served UE and the child IAB-node through the new backhaul RLC channel and the new BAP path.
  • step 1814 is optional.
  • the child IAB-node sends an RRCReconfigurationComplete message to the migrating IAB-node, and the migrating IAB-node forwards the message to the target Donor in an F1AP message (UL RRC MESSAGE TRANSFER). Afterwards, the child IAB-node can send the signaling or data generated by itself through the new default BAP path.
  • the target Donor configures a new BAP route for the child IAB-node through the F1AP message. Then the child IAB-node can send signaling or data of the served UE and the grandchild IAB-node through the new BAP path.
  • step 1816 is optional.
  • steps 1814 and 1816 need to be completed after step 1813, that is, after the target Donor receives the RRCReconfigurationComplete sent by the migrating IAB-node.
  • the RRCReconfiguration message is sent to the child IAB-node or UE only after the migrating IAB-node completes the establishment of a new F1 connection with the target Donor. This ensures that the migrating IAB-node sends an RRCReconfigurationComplete message to the child IAB-node or UE after establishing a new F1 connection with the target Donor, so that the migrating IAB-node does not change the PCI and frequency.
  • the old F1 connection between the migrating IAB-node or the sub-IAB-node and the source Donor can still be maintained, and the release conditions are as follows:
  • Condition 1 After sending the RRCReconfiguration message to all sub-IAB-nodes and serving UEs, release the old F1 connection with the source Donor;
  • the source Donor has already sent the F1 message containing the RRCReconfiguration for the downstream sub-IAB-node or UE through the old F1 connection, and there is no need to continue to use the old F1 connection;
  • the child IAB-node or UE may fail to switch or reconfigure, the child IAB-node and the serving UE complete the RRC reconfiguration and then release the original F1 connection, which can ensure that the child IAB-node or UE can be reconfigured when the handover fails. Back to source Donor.
  • Condition 3 Release the original F1 connection after a preset time after the new F1 connection is established, to ensure that the source Donor has completed sending the F1 message including the RRCReconfiguration for the downstream child IAB-node or UE through the old F1 connection. For example, a timer is started, and the original F1 connection is released after the timer expires.
  • the old F1 connection between the migrating IAB-node or child IAB-node and the source Donor may be released immediately after the new F1 connection is established.
  • the migrating IAB-node only needs to maintain one F1 connection and does not need to keep the old F1 connection to the source Donor after the new F1 connection is established.
  • the target Donor can directly send the RRC reconfiguration message for its downstream sub-IAB-node or UE to the migrating IAB-node or sub-IAB-node through the new F1 connection, instead of sending the RRC reconfiguration message to the source Donor, through the original F1
  • the connection sends the RRCReconfiguration message of the child IAB-node or UE. Refer to B of Example 2. In this way, the time for sending the handover command (ie, the RRCReconfiguration message) can be reduced.
  • An embodiment of the present application provides a group switching device.
  • FIG. 19 is a schematic diagram of a group switching apparatus according to an embodiment of the present application.
  • the apparatus may be, for example, a Donor device in an IAB network, such as a Donor device before migrating an IAB node, called a source Donor device, or a Donor device configured in one or some of the components or assemblies in the Donor device.
  • the implementation principle of the apparatus is similar to that of the method in FIG. 8 of the embodiment of the first aspect, and the description of the same content will not be repeated.
  • the group switching apparatus 1900 in this embodiment of the present application includes:
  • the first receiving unit 1901 which receives the measurement report sent by the relocated IAB node;
  • a first sending unit 1902 which sends a first handover request message to the target Donor device, where the first handover request message includes the context information of the migrated IAB node and its served child IAB node or UE;
  • a second receiving unit 1903 which receives a first response message sent by the target Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node and its serving child IAB node or UE;
  • a second sending unit 1904 which sends the RRC reconfiguration message to the migrated IAB node and its served sub-IAB node or UE.
  • the device may be, for example, a Donor device in an IAB network, such as a Donor device after migrating an IAB node after migration, called a target Donor device, or a Donor device configured in one or some of the components or assemblies in the Donor device.
  • the implementation principle of the apparatus is similar to that of the method in FIG. 9 of the embodiment of the first aspect, and the description of the same content will not be repeated.
  • the group switching apparatus 2000 includes:
  • a first receiving unit 2001 which receives a first handover request message sent by a source Donor device, where the first handover request message includes the context information of the migrated IAB node and its served sub-IAB node or UE;
  • a first sending unit 2002 which sends a first response message to the source Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node and its served sub-IAB node or UE;
  • a first processing unit 2003 which establishes a new F1 connection with the migrated IAB node
  • the second receiving unit 2004 is configured to receive the RRC reconfiguration complete message sent by the migrated IAB node and its served sub-IAB node or UE.
  • the device may be, for example, a Donor device in an IAB network, such as a Donor device before the migration of the IAB node, which is called a source Donor device, or a Donor device configured in one or some of the components or assemblies in the Donor device.
  • the implementation principle of the apparatus is similar to that of the method in FIG. 10 of the embodiment of the first aspect, and the description of the same content will not be repeated.
  • the group switching apparatus 2100 includes:
  • the first receiving unit 2101 which receives the measurement report sent by the relocated IAB node;
  • a first sending unit 2102 which sends a first handover request message to the target Donor device, where the first handover request message includes the context information of the migrated IAB node and its served sub-IAB node or UE;
  • a second receiving unit 2103 which receives a first response message sent by the target Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node;
  • a second sending unit 2104 which sends the RRC reconfiguration message to the migrating IAB node.
  • FIG. 22 is a schematic diagram of a group switching apparatus according to an embodiment of the present application.
  • the apparatus may be, for example, a Donor device in an IAB network, such as a Donor device after migrating an IAB node after migration, which is called a target Donor device, or it may be a Donor device configured in one or some of the components or assemblies in the Donor device.
  • the implementation principle of the apparatus is similar to that of the method in FIG. 11 of the embodiment of the first aspect, and the description of the same content will not be repeated.
  • the group switching apparatus 2200 includes:
  • a first receiving unit 2201 which receives a first handover request message sent by a source Donor device, where the first handover request message includes the context information of the migrated IAB node and the sub-IAB node or UE served by it;
  • a first sending unit 2202 which sends a first response message to the source Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node;
  • the first processing unit 2203 which establishes a new F1 connection with the migrated IAB node
  • the second sending unit 2204 sends an RRC reconfiguration message to the sub-IAB node or UE served by the migrated IAB node through the new F1 connection;
  • the second receiving unit 2205 is configured to receive the RRC reconfiguration complete message sent by the migrated IAB node and its served sub-IAB node or UE.
  • the context information of the migrated IAB node includes: the IAB-DU context and the IAB-MT context of the migrated IAB node; the context information of the child IAB node includes: the IAB of the child IAB node - DU context and IAB-MT context.
  • the IAB-DU context of the relocated IAB node includes: serving cell information of the IAB-DU of the relocated IAB node under the source Donor device.
  • the serving cell information includes at least one of the following: a new wireless cell global identifier (Cell Global Identifier, NR CGI); a new wireless physical cell ID (Physical Cell ID, NR PCI); Land mobile network (Public Land Mobile Network, PLMN); uplink and downlink transmission frequency and bandwidth.
  • the IAB-MT context of the migrated IAB node includes BAP configuration information; wherein the BAP configuration information includes a BAP address and a transport layer (IP) address allocated by the source Donor device for the IAB node , a default uplink backhaul RLC channel identifier and/or a default uplink BAP routing identifier; wherein the default uplink BAP routing identifier refers to a default destination BAP address and a default path identifier.
  • IP transport layer
  • the first handover request message further includes return information configured by the source Donor device for the migrating IAB node or the sub-IAB node.
  • the returned information includes at least one of the following:
  • the returned information includes:
  • the BAP routing identifier used by the DRB of the UE served by the relocated IAB node or the sub-IAB node, the BAP address of the next hop node, and the backhaul RLC channel identifier;
  • the BAP routing identifier used by F1 control plane data or non-F1 data, the BAP address of the next hop node, and the return RLC channel identifier used by F1 control plane data or non-F1 data, the BAP address of the next hop node, and the return RLC channel identifier.
  • the BAP routing identifier includes a destination BAP address and a path ID identifier.
  • the first handover request message further includes: topology information, where the topology information includes a topology relationship between the migrated IAB node and its served sub-IAB node or UE, Or it includes the topological relationship between the sub-IAB node and the sub-IAB node or UE it serves.
  • the first handover request message further includes: address request information, where the address request information is used to request the target Donor device to be the migrated IAB node or the child
  • the IAB node assigns a new transport layer (IP) address or BAP address.
  • IP transport layer
  • establishing a new F1 connection with the migrating IAB node includes: receiving an F1 establishment request message sent by the migrating IAB node; and sending an F1 establishment response message to the migrating IAB node.
  • the apparatus 2000/2200 further includes:
  • the second processing unit 2005/2206 establishes a new F1 connection with the child IAB node.
  • the apparatus 2000/2200 further includes:
  • the first configuration unit 2006/2207 after the target Donor device receives the RRC reconfiguration complete message sent by the migrating IAB node, configures backhaul RLC channel mapping and BAP routing configuration for the migrating IAB node.
  • the apparatus 2000 further includes:
  • the context information of the migrated IAB node and the context information of the child IAB node or the UE are included in the same Xn message or different Xn messages.
  • the apparatus 2000/2200 further includes:
  • the third sending unit 2008/2208 after the target Donor device receives the RRC reconfiguration complete message sent by the migrating IAB node, or after establishing a new F1 connection with the migrating IAB node, sends the source Donor device to the source Donor device.
  • the RRC reconfiguration message for the migrated IAB node and the RRC reconfiguration message for the sub-IAB node or the UE are included in the same Xn message or different Xn messages.
  • the apparatus 2000/2200 further includes:
  • the fourth sending unit 2009/2209 after the target Donor device receives the RRC reconfiguration complete message sent by the migrating IAB node, or after establishing a new F1 connection with the migrating IAB node, sends a message to the source Donor device An Xn message containing an RRC reconfiguration message for the child IAB node or the UE is sent.
  • the apparatus 2000/2200 further includes:
  • the second configuration unit 2010/2210 after the target Donor device receives the RRC reconfiguration complete message sent by the migrating IAB node and the RRC reconfiguration complete message sent by the child IAB node, it is the child IAB node.
  • Configure BAP routing configuration After the target Donor device receives the RRC reconfiguration complete message sent by the migrating IAB node and the RRC reconfiguration complete message sent by the child IAB node, it is the child IAB node.
  • the RRC reconfiguration message for the migrated IAB node includes at least one of the following: switching to a default uplink backhaul RLC channel identifier used by the target Donor device; switching to a default uplink backhaul RLC channel identifier used by the target Donor device; Default BAP routing configuration; switch to the BAP address used by the target Donor device; switch to the transport layer address used by the target Donor device; and switch to the security key configuration used by the target Donor device.
  • the RRC reconfiguration message for the migrating IAB node further includes: switching to the backhaul RLC channel mapping and BAP routing configuration used by the target Donor device.
  • the RRC reconfiguration message for the sub-IAB node includes at least one of the following: switching to the default BAP routing identifier used by the target Donor device; switching to the BAP address used by the target Donor device; switching to The transport layer address used by the target Donor device; and the security key configuration used by the handover to the target Donor device.
  • the RRC reconfiguration message for the sub-IAB node further includes: switching to the BAP routing configuration used by the target Donor device.
  • the RRC reconfiguration message for the UE includes: switching to the security key configuration used by the target Donor device.
  • the group switching apparatus 1900/2000/2100/2200 in this embodiment of the present application may further include other components or modules.
  • specific content of these components or modules reference may be made to the related art.
  • FIG. 19 to FIG. 22 only exemplarily show the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used .
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
  • the interruption time of service communication during the movement of the IAB node can be reduced.
  • An embodiment of the present application provides a group switching device.
  • the device may be, for example, an IAB node to be migrated in an IAB network, referred to as a migration IAB node, or may be one or some components configured in the migrated IAB node or components.
  • FIG. 23 is a schematic diagram of a group switching apparatus according to an embodiment of the present application.
  • the principle of the apparatus for solving problems is similar to that of the method in FIG. 13 of the embodiment of the second aspect.
  • the group switching apparatus 2300 in this embodiment of the present application includes:
  • the first sending unit 2301 which sends a measurement report to the source Donor device
  • a first receiving unit 2302 which receives the RRC reconfiguration message sent by the source Donor device
  • Processing unit 2303 which establishes a new F1 connection with the target Donor device
  • a second receiving unit 2304 which receives the RRC reconfiguration message for the child IAB node or UE served by the migrated IAB node and sent by the source Donor device through the old F1 connection;
  • a second sending unit 2305 which sends the RRC reconfiguration message to the sub-IAB node or the UE;
  • a third sending unit 2306 which sends an RRC reconfiguration complete message to the target Donor device
  • the fourth sending unit 2307 which forwards the RRC reconfiguration complete message sent by the sub-IAB node or the UE to the target Donor device.
  • FIG. 24 is a schematic diagram of a group switching apparatus according to an embodiment of the present application.
  • the principle of the apparatus for solving problems is similar to that of the method in FIG. 14 of the embodiment of the second aspect.
  • the group switching apparatus 2400 in this embodiment of the present application includes:
  • a first sending unit 2401 which sends a measurement report to the source Donor device
  • the first receiving unit 2402 which receives the RRC reconfiguration message sent by the source Donor device;
  • Processing unit 2403 which establishes a new F1 connection with the target Donor device
  • a second receiving unit 2404 which receives the RRC reconfiguration message sent by the target Donor device through the new F1 connection for the sub-IAB node or UE served by the migrated IAB node;
  • a second sending unit 2405 which sends the RRC reconfiguration message to the sub-IAB node or the UE;
  • a third sending unit 2406 which sends an RRC reconfiguration complete message to the target Donor device
  • Fourth sending unit 2407 it forwards the RRC reconfiguration complete message sent by the sub-IAB node or the UE to the target Donor device.
  • the processing unit 2303/2403 establishes a new F1 connection with the target Donor device, including:
  • the F1 establishment response message sent by the target Donor device is received, thereby establishing a new F1 connection with the target Donor device.
  • the processing unit 2303/2403 maintains the old F1 connection with the source Donor device, and releases the connection with the source if one of the following conditions is satisfied Old F1 connection between Donor devices:
  • the processing unit 2303/2403 sends an F1 release request message to the source Donor device to release the old F1 connection with the source Donor device.
  • the processing unit 2303/2403 sends the RRC reconfiguration message of the sub-IAB node or the UE to the sub-IAB node or the UE; Alternatively, after the establishment of the new F1 connection is completed, the RRC reconfiguration complete message sent by the sub-IAB node or the UE is forwarded to the target Donor device.
  • the apparatus 2300/2400 further comprises:
  • the RRC reconfiguration message for the migrated IAB node includes one of the following:
  • the RRC reconfiguration message further includes: switching to the backhaul RLC channel mapping and BAP routing configuration used by the target Donor device.
  • the processing unit 2303/2403 may apply the backhaul RLC channel mapping and BAP routing configuration.
  • the resource allocation apparatus 2300/2400 in this embodiment of the present application may further include other components or modules, and for the specific content of these components or modules, reference may be made to the related art.
  • FIG. 23 and FIG. 24 only exemplarily show the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used .
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
  • the interruption time of service communication during the movement of the IAB node can be reduced.
  • An embodiment of the present application provides a group switching device.
  • FIG. 25 is a schematic diagram of a group switching device according to an embodiment of the present application.
  • the device may be a sub-IAB node served by a migrating IAB node in an IAB network, or may be some or some components configured in the sub-IAB node.
  • the principle of the device for solving the problem is similar to the method in FIG. 15 of the embodiment of the third aspect, and the specific implementation can refer to the method in FIG. 15 , and the same content will not be repeated.
  • the group switching apparatus 2500 according to the embodiment of the present application includes:
  • the first receiving unit 2501 which receives the RRC reconfiguration message sent by the source Donor device or the target Donor device;
  • the processing unit 2502 establishes a new F1 connection with the target Donor device
  • the first sending unit 2503 which sends an RRC reconfiguration complete message to the target Donor device.
  • a new F1 connection is established between the processing unit 2502 and the target Donor device, including:
  • the F1 establishment response message sent by the target Donor device is received, thereby establishing an F1 connection with the target Donor device.
  • the processing unit 2502 maintains the old F1 connection with the source Donor device, and releases the connection with the source Donor device if one of the following conditions is satisfied Old F1 connection between:
  • the processing unit 2502 sends an F1 release request message to the source Donor device to release the old F1 connection with the source Donor device.
  • the apparatus 2500 further includes:
  • a second receiving unit 2504 which receives an F1AP message sent by the target Donor device through the new F1 connection, wherein the F1AP message includes an RRC reconfiguration message for a grandson IAB node or UE served by the sub IAB node;
  • the apparatus 2500 further includes:
  • the third receiving unit 2506 receives the BAP routing configuration configured by the target Donor after the first sending unit 2503 sends the RRC reconfiguration complete message to the target Donor device.
  • the apparatus 2500 further includes:
  • the fourth receiving unit 2507 which receives the F1AP message sent by the source Donor device through the old F1 connection with the child IAB node, wherein the F1AP message includes the grandchild IAB node or the child IAB node serving the child IAB node.
  • UE's RRC reconfiguration message
  • a third sending unit 2508, which sends the RRC reconfiguration message to the grandchild IAB node or the UE, and forwards the RRC reconfiguration complete message sent by the grandchild IAB node or the UE to the target Donor device.
  • the third sending unit 2508 sends the RRC reconfiguration message of the grandchild IAB node or UE to the serving grandchild IAB node or UE, or in the new F1 After the connection establishment is completed, the RRC reconfiguration complete message of the serving grandchild IAB node or UE is sent to the target Donor device.
  • the above-mentioned RRC reconfiguration message for the sub-IAB node includes one of the following:
  • the RRC reconfiguration message further includes: switching to the BAP routing configuration used by the target Donor device.
  • the processing unit 2502 after determining that the migrating IAB node has completed the handover to the target Donor device, and after sending the RRC reconfiguration complete message to the target Donor device, applies the BAP routing configuration .
  • FIG. 26 is a schematic diagram of a group switching apparatus according to an embodiment of the present application.
  • the apparatus may be a UE served by a migrating IAB node in an IAB network, or may be some or some components or components configured in the UE.
  • the principle of the device for solving the problem is similar to that of the method in FIG. 16 in the embodiment of the third aspect, and the specific implementation can refer to the method in FIG. 16 , and the same content will not be repeated.
  • the group switching apparatus 2600 includes:
  • a receiving unit 2601 which receives the RRC reconfiguration message sent by the source Donor device or the target Donor device;
  • a sending unit 2602 which sends an RRC reconfiguration complete message to the target Donor device.
  • the RRC reconfiguration message includes switching to the security key configuration used by the target Donor device.
  • the interruption time of service communication during the movement of the IAB node can be reduced.
  • FIG. 27 is a schematic diagram of the communication system 2700.
  • the communication system 2700 includes Donor devices 2701 and 2702, IAB nodes 2703 and 2704, and a terminal device 2705, wherein , the IAB node 2703 is the migrating IAB node, the Donor device 2701 is the source Donor device of the IAB node 2703, the Donor device 2702 is the target Donor device of the IAB node 2703, the IAB node 2704 and the terminal device 2705 are provided by the IAB node 2703.
  • Node 2704 is a child IAB node of IAB node 2703.
  • FIG. 27 only takes two Donro devices, two IAB nodes, and one terminal device as examples for description, but the embodiment of the present application is not limited to this.
  • the network architecture of the Donro device, the IAB node and the terminal device reference may be made to related technologies, and the description is omitted here.
  • the Donor device 2701 is configured to perform the methods shown in FIGS. 8 and 10 and may include the apparatus of FIGS. 19 and 21 .
  • Donor device 2702 is configured to perform the methods shown in FIGS. 9 and 11 , and may include the apparatus of FIGS. 20 and 22 .
  • the IAB node 2703 is configured to perform the methods shown in FIGS. 13 and 14 and may include the apparatus of FIGS. 23 and 23 .
  • the IAB node 2704 configured to perform the method shown in FIG. 15 may include the apparatus of FIG. 25 .
  • the terminal device 2705 is configured to perform the method shown in FIG. 16 and may include the apparatus of FIG. 26 .
  • the IAB nodes 2703 and 2704, and the terminal device 2705 please refer to the embodiments of the first aspect to the sixth aspect, and the description is omitted here.
  • the embodiment of the present application also provides an IAB node.
  • FIG. 28 is a schematic diagram of an IAB node according to an embodiment of the present application.
  • the IAB node 2800 may include a processor 2801 and a memory 2802 ; the memory 2802 stores data and programs, and is coupled to the processor 2801 .
  • this figure is exemplary; other types of structures may be used in addition to or in place of this structure to implement telecommunication functions or other functions.
  • the processor 2801 may be configured to execute a program to implement the method as described in the embodiment of FIG. 13 or FIG. 14 of the second aspect or the embodiment of FIG. 15 of the third aspect.
  • the IAB node 2800 may further include: a communication module 2803 , an input unit 2804 , a display 2805 , and a power supply 2806 .
  • the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the IAB node 2800 does not necessarily include all the components shown in FIG. 28 , and the above components are not required; in addition, the IAB node 2800 may also include components not shown in FIG. 28 . There is technology.
  • the embodiment of the present application also provides a Donor device.
  • FIG. 29 is a schematic diagram of a Donor device according to an embodiment of the present application.
  • the Donor device 2900 may include: a processor (eg, a central processing unit CPU) 2901 and a memory 2902 ; the memory 2902 is coupled to the processor 2901 .
  • the memory 2902 can store various data; in addition, it also stores information processing programs, and the programs are executed under the control of the central processing unit 2901 .
  • the processor 2901 may be configured to execute a program to implement the method as described in the embodiment of FIG. 8 or FIG. 9 or FIG. 10 or FIG. 11 of the first aspect.
  • the Donor device 2900 may further include: a transceiver 2903, an antenna 2904, etc.; wherein, the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the Donor device 2900 does not necessarily include all the components shown in FIG. 29 ; in addition, the Donor device 2900 may also include components not shown in FIG. 29 , and reference may be made to the prior art.
  • the embodiments of the present application also provide a terminal device.
  • FIG. 30 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 2800 may include a processor 2801 and a memory 3002 ; the memory 3002 stores data and programs, and is coupled to the processor 3001 .
  • this figure is exemplary; other types of structures may be used in addition to or in place of this structure to implement telecommunication functions or other functions.
  • the processor 3001 may be configured to execute a program to implement the method as described in the embodiment of FIG. 16 of the third aspect.
  • the terminal device 3000 may further include: a communication module 3003 , an input unit 3004 , a display 3005 , and a power supply 3006 .
  • the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the terminal device 3000 does not necessarily include all the components shown in FIG. 30 , and the above components are not required; in addition, the terminal device 3000 may also include components not shown in FIG. 30 . There is technology.
  • the embodiment of the present application also provides a computer-readable program, wherein when the program is executed in an IAB node, the program causes a computer to execute the embodiment of FIG. 15 of the second aspect or the third aspect in the IAB node the method described.
  • the embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer to execute the method described in the embodiment of FIG. 15 in the second aspect or the third aspect in an IAB node.
  • the embodiments of the present application further provide a computer-readable program, wherein when the program is executed in a Donor device, the program causes a computer to execute the method described in the embodiment of the first aspect in the Donor device.
  • the embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer to execute the method described in the embodiment of the first aspect in a Donor device.
  • the embodiment of the present application further provides a computer-readable program, wherein when the program is executed in a terminal device, the program causes a computer to execute the method described in the embodiment of FIG. 16 in the third aspect in the terminal device .
  • the embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer to execute the method described in the embodiment of FIG. 16 of the third aspect in a Donor device.
  • the apparatuses and methods above in the present application may be implemented by hardware, or may be implemented by hardware combined with software.
  • the present application relates to a computer-readable program that, when executed by logic components, enables the logic components to implement the above-described apparatus or constituent components, or causes the logic components to implement the above-described various methods or steps.
  • Logic components such as field programmable logic components, microprocessors, processors used in computers, and the like.
  • the present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, and the like.
  • the method/apparatus described in conjunction with the embodiments of this application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in the figures may correspond to either software modules or hardware modules of the computer program flow.
  • These software modules may respectively correspond to the various steps shown in the figure.
  • These hardware modules can be implemented by, for example, solidifying these software modules using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
  • a storage medium can be coupled to the processor, such that the processor can read information from, and write information to, the storage medium; or the storage medium can be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • the functional blocks and/or one or more combinations of the functional blocks described in the figures can be implemented as a general-purpose processor, a digital signal processor (DSP) for performing the functions described in this application ), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described with respect to the figures can also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors processor, one or more microprocessors in communication with the DSP, or any other such configuration.
  • a group switching method the method is applied to a source Donor device, wherein the method comprises:
  • the target Donor device Send a first handover request message to the target Donor device, where the first handover request message includes the context information of the migrated IAB node and its served sub-IAB node or UE;
  • the target Donor device receiving a first response message sent by the target Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node and its served sub-IAB node or UE;
  • the RRC reconfiguration message is sent to the migrating IAB node and its serving child IAB node or UE.
  • a group switching method the method is applied to a source Donor device, wherein the method comprises:
  • the target Donor device Send a first handover request message to the target Donor device, where the first handover request message includes the context information of the migrated IAB node and its served sub-IAB node or UE;
  • the target Donor device receiving a first response message sent by the target Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node;
  • the RRC reconfiguration message is sent to the migrating IAB node.
  • a group switching method the method is applied to a target Donor device, wherein the method comprises:
  • the source Donor device receiving a first handover request message sent by the source Donor device, where the first handover request message includes the context information of the migrated IAB node and its served sub-IAB node or UE;
  • the source Donor device sending a first response message to the source Donor device, where the first response message includes an RRC reconfiguration message for the migrated IAB node and its served sub-IAB node or UE;
  • a group switching method the method is applied to a target Donor device, wherein the method comprises:
  • the source Donor device receiving a first handover request message sent by the source Donor device, where the first handover request message includes the context information of the migrated IAB node and its served sub-IAB node or UE;
  • the context information of the migrated IAB node includes: the IAB-DU context and the IAB-MT context of the migrated IAB node;
  • the context information of the sub-IAB node includes: the IAB-DU context and the IAB-MT context of the sub-IAB node.
  • serving cell information includes at least one of the following:
  • Cell Global Identifier Cell Global Identifier, NR CGI
  • the public land mobile network (Public Land Mobile Network, PLMN) served by the IAB-DU;
  • the IAB-MT context of the migrated IAB node includes BAP configuration information; wherein the BAP configuration information includes a BAP address allocated by the source Donor device to the IAB node , a transport layer (IP) address, a default uplink backhaul RLC channel identifier and/or a default uplink BAP routing identifier; wherein the default uplink BAP routing identifier refers to a default destination BAP address and a default path identifier.
  • the BAP configuration information includes a BAP address allocated by the source Donor device to the IAB node , a transport layer (IP) address, a default uplink backhaul RLC channel identifier and/or a default uplink BAP routing identifier; wherein the default uplink BAP routing identifier refers to a default destination BAP address and a default path identifier.
  • IP transport layer
  • the BAP routing identifier used by the DRB of the UE served by the relocated IAB node or the sub-IAB node, the BAP address of the next hop node, and the backhaul RLC channel identifier;
  • the BAP routing identifier used by F1 control plane data or non-F1 data, the BAP address of the next hop node, and the return RLC channel identifier used by F1 control plane data or non-F1 data, the BAP address of the next hop node, and the return RLC channel identifier.
  • the first handover request message further includes topology information
  • the topology information includes the relationship between the migrating IAB node and its served sub-IAB node or UE. the topology relationship, or the topology relationship between the child IAB node and its serving grandchild IAB node or UE.
  • the first handover request message further comprises: address request information, where the address request information is used to request the target Donor device to be the migration IAB
  • the node or the child IAB node assigns a new transport layer (IP) address or BAP address.
  • IP transport layer
  • An F1 setup response message is sent to the migrating IAB node.
  • a new F1 connection is established with the child IAB node.
  • the target Donor device After receiving the RRC reconfiguration complete message sent by the migrating IAB node, the target Donor device configures backhaul RLC channel mapping and BAP routing configuration for the migrating IAB node.
  • the target Donor device After the target Donor device receives the RRC reconfiguration complete message sent by the migrating IAB node, or after establishing a new F1 connection with the migrating IAB node, it sends a first indication message to the source Donor device; The first indication message is used to instruct the source Donor device to send an RRC reconfiguration message to the sub-IAB node or the UE.
  • the target Donor device After the target Donor device receives the RRC reconfiguration complete message sent by the migrating IAB node, or after establishing a new F1 connection with the migrating IAB node, it sends a second indication message to the source Donor device; The second indication message is used to instruct the source Donor device to send an Xn message including the context of the sub-IAB node or the UE to the target Donor device.
  • the target Donor device After the target Donor device receives the RRC reconfiguration complete message sent by the migrating IAB node, or after establishing a new F1 connection with the migrating IAB node, it sends a message to the source Donor device that includes information about the child IAB node or The Xn message of the UE's RRC reconfiguration message.
  • the target Donor device After receiving the RRC reconfiguration complete message sent by the relocated IAB node and the RRC reconfiguration complete message sent by the child IAB node, the target Donor device configures the BAP routing configuration for the child IAB node.
  • the RRC reconfiguration complete message sent by the sub-IAB node or the UE is forwarded to the target Donor device.
  • the RRC reconfiguration complete message sent by the sub-IAB node or the UE is forwarded to the target Donor device.
  • the F1 establishment response message sent by the target Donor device is received, thereby establishing a new F1 connection with the target Donor device.
  • RRC reconfiguration message further comprises: switching to the backhaul RLC channel mapping and BAP routing configuration used by the target Donor device.
  • the backhaul RLC channel mapping and BAP routing configuration are applied.
  • the F1 establishment response message sent by the target Donor device is received, thereby establishing an F1 connection with the target Donor device.
  • the target Donor device receiving an F1AP message sent by the target Donor device through the new F1 connection, wherein the F1AP message includes an RRC reconfiguration message for a grand-child IAB node or UE served by the child IAB node;
  • the RRC reconfiguration message is sent to the grandchild IAB node or UE.
  • the F1AP message includes an RRC reconfiguration message for the grandchild IAB node or UE served by the child IAB node;
  • the RRC reconfiguration complete message sent by the grandchild IAB node or the UE is forwarded to the target Donor device.
  • the BAP routing configuration is applied.
  • a Donor device comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the method according to any one of appendixes 1 to 28 .
  • An IAB node comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the method according to any one of appendixes 29 to 49 .
  • a terminal device comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the method as described in appendix 50 or 51.
  • a communication system comprising a Donor device, an IAB node, and a terminal device, wherein the Donor device is configured to execute the method described in any one of the appendices 1 to 28, and the IAB node is configured to execute the appendix The method described in any one of 29 to 49, wherein the terminal device is configured to execute the method described in appendix 50 or 51.

Landscapes

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

Abstract

本申请实施例提供了一种群组切换方法、装置和系统，一种群组切换方法包括：接收迁移IAB节点发送的测量报告；向目标Donor设备发送第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；接收所述目标Donor设备发送的第一响应消息，所述第一响应消息包含针对所述迁移IAB节点及其服务的子IAB节点或UE的RRC重配置消息；向所述迁移IAB节点及其服务的子IAB节点或UE发送所述RRC重配置消息。

Description

群组切换的方法、装置和系统 技术领域
本申请涉及通信领域。
背景技术
未来无缝的蜂窝网络部署需要非常灵活和超密集的NR小区部署，超密集网络是5G的目标之一，部署一个无需有线回传的NR网络对于实现5G的超密集网络非常重要。由于5G毫米波使小区覆盖范围缩小，无线自回传系统还需要是多跳的才能满足部署需求。5G的高带宽、大规模MIMO和波束系统使5G比LTE更容易开发超密集NR小区的无线自回传系统，为了开发这种带有无线自回传的多跳系统，3GPP在R16开始了IAB(Integrated access and backhaul，接入回传一体化)项目的研究和标准化。
图1是IAB系统的一个示意图，如图1所示，在IAB系统中，中继节点同时支持接入(access)和回传(backhaul)功能，中继节点的无线传输链路在时域、频域或空域上复用接入链路(access link)和回传链路(backhaul link)，接入链路和回传链路可以使用相同或不同的频段。
在IAB网络架构如下，中继节点指的是IAB-node(IAB节点)，其同时支持接入和回传功能。网络侧最后一跳接入节点称为IAB-donnor(IAB宿主)，其支持gNB功能并支持IAB-node接入。所有的UE数据可以通过一跳或多跳经IAB-node回传到IAB-donor。IAB-node的功能分为两部分，一部分是gNB-DU功能，称作IAB-DU，另一部分是UE功能，称作IAB-MT。IAB-DU实现网络侧设备功能，连接到下游的child IAB-node(子IAB节点)，对UE以及下游child IAB-node提供NR空口接入并与IAB donor-CU之间建立有F1连接。IAB-MT实现部分终端设备功能，连接到上游的parent IAB-node(父IAB节点)或IAB-donor DU，IAB-MT包括物理层、层二、RRC和NAS层功能，还间接的连接到IAB donor-CU以及核心网。IAB-node可以通过SA模式或EN-DC模式接入网络。图2是SA模式的IAB架构的示意图。图3是EN-DC模式的IAB架构的示意图。图4是父节点(parent IAB-node)和子节点(child IAB-node)的示意图。
图5是IAB-DU和IAB-donor CU之间的F1用户面协议栈的示意图。图6是 IAB-DU和IAB-donor CU之间的F1控制面协议栈的示意图。
如图5和图6所示，F1用户面和F1控制面是建立在IAB-DU和IAB-donor-CU之间的传输(IP)层之上，图5和图6中经过两跳无线回传和一跳有线回传。在回传链路上，传输(IP)层承载在回传自适应协议(BAP)子层上，IAB-node中的BAP实体实现IAB系统的路由功能，由IAB-donor CU提供路由表。BAP PDU在回传链路的RLC信道中传输，回传链路的多个RLC信道可以被IAB-donor配置为承载不同的优先级和QoS的业务，由BAP实体将BAP PDU映射到不同的回传RLC信道上。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人发现，R16IAB系统已经支持了IAB-node在同一个donor下的不同DU之间移动时引起的拓扑和路由的自适应改变。IAB-node在同一个Donor下移动时，无需与donor建立新的F1控制面连接，对下游child IAB-node和UE没有影响，child IAB-node和UE可以保持与IAB-node的连接。R17 IAB系统将引入IAB-node在不同donor下的移动功能，但是这种情况下由于IAB-node切换到新的donor，对下游child IAB-node和UE有很大影响，child IAB-node和UE与IAB-node之间会经历无线链路失败。
例如，现有的Donor之间的IAB-node移动的方法是当IAB-node切换到新的donor下时，下游child IAB-node和UE与IAB-node之间经历无线链路失败，然后下游child IAB-node和UE自己发起RRC重建立过程重新连接到IAB-node并与新的donor之间建立RRC连接。这样，会导致较长时间的业务通信中断，由于下游child IAB-node也要重建立到新的donor，child IAB-node服务的UE也会经历无线链路失败，所以child IAB-node服务的UE有更长时间的通信中断。
为了解决上述问题的至少一种或其它类似问题，本申请实施例提供了一种群组切换的方法、装置和系统。
根据本申请实施例的一方面，提供一种群组切换装置，配置于源Donor设备，其中，所述装置包括：
第一接收单元，其接收迁移IAB节点发送的测量报告；
第一发送单元，其向目标Donor设备发送第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
第二接收单元，其接收所述目标Donor设备发送的第一响应消息，所述第一响应消息包含针对所述迁移IAB节点及其服务的子IAB节点或UE的RRC重配置消息；
第二发送单元，其向所述迁移IAB节点及其服务的子IAB节点或UE发送所述RRC重配置消息。
根据本申请实施例的一方面，提供一种群组切换装置，配置于源Donor设备，其中，所述装置包括：
第一接收单元，其接收迁移IAB节点发送的测量报告；
第一发送单元，其向目标Donor设备发送第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
第二接收单元，其接收所述目标Donor设备发送的第一响应消息，所述第一响应消息包含针对所述迁移IAB节点的RRC重配置消息；
第二发送单元，其向所述迁移IAB节点发送所述RRC重配置消息。
根据本申请实施例的一方面，提供一种群组切换装置，配置于目标Donor设备，其中，所述装置包括：
第一接收单元，其接收源Donor设备发送的第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
第一发送单元，其向所述源Donor设备发送第一响应消息，所述第一响应消息包含针对所述迁移IAB节点及其服务的子IAB节点或UE的RRC重配置消息；
第一处理单元，其与所述迁移IAB节点建立新F1连接；
第二接收单元，其接收所述迁移IAB节点及其服务的子IAB节点或UE发送的RRC重配置完成消息。
根据本申请实施例的一方面，提供一种群组切换装置，配置于目标Donor设备，其中，所述装置包括：
第一接收单元，其接收源Donor设备发送的第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
第一发送单元，其向所述源Donor设备发送第一响应消息，所述第一响应消息包 含针对所述迁移IAB节点的RRC重配置消息；
第一处理单元，其与所述迁移IAB节点建立新F1连接；
第二发送单元，其通过所述新F1连接向所述迁移IAB节点服务的子IAB节点或UE发送RRC重配置消息；
第二接收单元，其接收所述迁移IAB节点及其服务的子IAB节点或UE发送的RRC重配置完成消息。
根据本申请实施例的一方面，提供一种群组切换装置，配置于迁移IAB节点，其中，所述装置包括：
第一发送单元，其向源Donor设备发送测量报告；
第一接收单元，其接收所述源Donor设备发送的RRC重配置消息；
处理单元，其与目标Donor设备建立新F1连接；
第二接收单元，其接收所述源Donor设备通过旧F1连接发送的针对所述迁移IAB节点服务的子IAB节点或UE的RRC重配置消息；
第二发送单元，其将所述RRC重配置消息发送给所述子IAB节点或所述UE；
第三发送单元，其向所述目标Donor设备发送RRC重配置完成消息；
第四发送单元，其向所述目标Donor设备转发所述子IAB节点或所述UE发送的RRC重配置完成消息。
根据本申请实施例的一方面，提供一种群组切换方法，配置于迁移IAB节点，其中，所述装置包括：
第一发送单元，其向源Donor设备发送测量报告；
第一接收单元，其接收所述源Donor设备发送的RRC重配置消息；
处理单元，其与目标Donor设备建立新F1连接；
第二接收单元，接收所述源Donor设备通过所述新F1连接发送的针对所述迁移IAB节点服务的子IAB节点或UE的RRC重配置消息；
第二发送单元，其将所述RRC重配置消息发送给所述子IAB节点或所述UE；
第三发送单元，其向所述目标Donor设备发送RRC重配置完成消息；
第四发送单元，其向所述目标Donor设备转发所述子IAB节点或所述UE发送的RRC重配置完成消息。
根据本申请实施例的一方面，提供一种群组切换装置，配置于迁移IAB节点服 务的子IAB节点，其中，所述装置包括：
第一接收单元，其接收源Donor设备发送的RRC重配置消息；
处理单元，其与目标Donor设备之间建立新F1连接；
第一发送单元，其向所述目标Donor设备发送RRC重配置完成消息。
根据本申请实施例的一方面，提供一种群组切换装置，配置于迁移IAB节点服务的终端设备，其中，所述装置包括：
接收单元，其接收源Donor设备或目标Donor设备发送的RRC重配置消息；
发送单元，其向所述目标Donor设备发送RRC重配置完成消息。
本申请实施例的有益效果之一在于：根据本申请实施例，当IAB-node移动到目标Donor节点时，无需通过RRC重建立方式与目标Donor节点的CU之间重新建立RRC连接，可减小在IAB-node移动过程中的业务通信中断时间。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是IAB系统的一个示意图；
图2是SA模式的IAB架构的示意图；
图3是EN-DC模式的IAB架构的示意图；
图4是父节点(parent IAB-node)和子节点(child IAB-node)的示意图；
图5是IAB-DU和IAB-donor CU之间的F1用户面协议栈的示意图；
图6是IAB-DU和IAB-donor CU之间的F1控制面协议栈的示意图；
图7是本申请实施例的实施场景的一个示意图；
图8是本申请第一方面的实施例的群组切换方法的一个示意图；
图9是本申请第一方面的实施例的群组切换方法的另一个示意图；
图10是本申请第一方面的实施例的群组切换方法的再一个示意图；
图11是本申请第一方面的实施例的群组切换方法的又一个示意图；
图12是IAB节点的入口和出口的示意图；
图13是本申请第二方面的实施例的群组切换方法的一个示意图；
图14是本申请第二方面的实施例的群组切换方法的另一个示意图；
图15是本申请第三方面的实施例的群组切换方法的一个示意图；
图16是本申请第三方面的实施例的群组切换方法的另一个示意图；
图17是本申请实施例的一个场景的流程图；
图18是本申请实施例的另一个场景的流程图；
图19是本申请第四方面的实施例的群组切换装置的一个示意图；
图20是本申请第四方面的实施例的群组切换装置的另一个示意图；
图21是本申请第四方面的实施例的群组切换装置的再一个示意图；
图22是本申请第四方面的实施例的群组切换装置的又一个示意图；
图23是本申请第五方面的实施例的群组切换装置的一个示意图；
图24是本申请第五方面的实施例的群组切换装置的另一个示意图；
图25是本申请第六方面的实施例的群组切换装置的一个示意图；
图26是本申请第六方面的实施例的群组切换装置的另一个示意图；
图27是本申请第七方面的实施例的通信系统的一个示意图；
图28是本申请第七方面的实施例的IAB节点的一个示意图；
图29是本申请第七方面的实施例的Donor设备的一个示意图；
图30是本申请第七方面的实施例的终端设备的一个示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、6G等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC， Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
本申请实施例提出了一种群组切换的方法。该方法用于IAB系统，提供了一种IAB-node在不同的donor设备之间移动引起的路由和拓扑的自适应改变的方法。在本申请实施例中，当IAB-node移动到目标Donor设备时，IAB-node的所有子IAB-node和UE都在网络侧的控制下进行切换。源donor设备与目标donor设备之间对IAB-node、其服务的UE和子IAB-node、以及该子IAB-node服务的UE进行切换准备，源donor设备的CU向该IAB-node、其服务的UE和子IAB-node、以及该子IAB-node服务的UE发送重配置消息，这些子IAB-node和UE通过IAB-node将重配置完成消息传递给目标Donor设备的CU以完成到目标Donor设备的连接，无需通过RRC重建立方式与目标Donor设备的CU之间重新建立RRC连接。可减小在IAB-node移动过程中 的业务通信中断时间。
图7是本申请实施例的实施场景的一个示意图，如图7所示，一个迁移IAB节点(Migrating IAB-node)701可能在多个Donor设备(IAB donor)702、703之间移动，该迁移IAB节点701服务的子IAB节点704和UE 705都在网络侧的控制下进行切换。为了方便说明，图7仅示出了一个迁移IAB节点701、一个源Donor设备702、一个目标Donor设备703、迁移IAB节点701服务的一个UE 705和两个子IAB节点704，但本申请不限于此。
在本申请实施例中，由于IAB-node分为IAB-DU部分和IAB-MT部分。IAB-DU实现网络侧DU设备功能，要向UE和MT提供NR空口接入并与IAB donor-CU之间建立F1连接，IAB-MT实现终端设备功能。
IAB-node在不同的donor节点之间移动的流程可以分成三个独立的过程：
1.IAB-node的IAB-MT部分的切换；
2.IAB-node的IAB-DU部分的切换；
3.IAB-node服务的UE的切换。
其中，IAB-MT部分的切换是指，服务IAB-node的PCell从源Donor设备换到目标Donor设备，IAB-node断开与源Donor设备的RRC连接，建立与目标Donor设备的RRC连接。IAB-DU部分的切换是指，IAB-node与CU的F1连接从源Donor设备换到目标Donor设备，IAB-node作为新的服务小区提供NR空口接入。
在本申请实施例中，主要考虑了以下两种实施场景：
场景一：Migrating IAB-node(迁移IAB节点)的IAB-MT和子IAB-node的IAB-MT及migrating IAB-node服务的UE同时进行切换；
在该场景下，源Donor设备同时向migrating IAB-node、子IAB-node及UE发送RRC重配置消息；
场景二：子IAB-node的IAB-MT及migrating IAB-node服务的UE在migrating IAB-node的IAB-DU或IAB-MT切换之后切换；
在该场景下，源Donor设备或目标Donor设备在目标Donor与migrating IAB-node建立F1连接后，或者在目标Donor收到migrating IAB-node的RRC重配置完成消息之后，向子IAB-node及UE发送RRC重配置消息。
下面结合附图对本申请的各种实施方式进行说明。这些实施方式只是示例性的， 不是对本申请的限制。
第一方面的实施例
本申请实施例提供一种群组切换方法。
图8是本申请实施例的群组切换方法的一个示意图，从IAB网络中源Donor设备的一侧进行说明。如图8所示，该方法包括：
801：接收迁移IAB节点发送的测量报告；
802：向目标Donor设备发送第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
803：接收所述目标Donor设备发送的第一响应消息，所述第一响应消息包含针对所述迁移IAB节点及其服务的子IAB节点或UE的RRC重配置消息；
804：向所述迁移IAB节点及其服务的子IAB节点或UE发送所述RRC重配置消息。
图9是本申请实施例的群组切换方法的另一个示意图，从IAB网络中目标Donor设备的一侧进行说明，图9的方法与图8的方法对应。如图9所示，该方法包括：
901：接收源Donor设备发送的第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
902：向所述源Donor设备发送第一响应消息，所述第一响应消息包含针对所述迁移IAB节点及其服务的子IAB节点或UE的RRC重配置消息；
903：与所述迁移IAB节点建立新F1连接；
904：接收所述迁移IAB节点及其服务的子IAB节点或UE发送的RRC重配置完成消息。
图10是本申请实施例的群组切换方法的再一个示意图，从IAB网络中源Donor设备的一侧进行说明。如图10所示，该方法包括：
1001：接收迁移IAB节点发送的测量报告；
1002：向目标Donor设备发送第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
1003：接收所述目标Donor设备发送的第一响应消息，所述第一响应消息包含针对所述迁移IAB节点的RRC重配置消息；
1004：向所述迁移IAB节点发送所述RRC重配置消息。
图11是本申请实施例的群组切换方法的又一个示意图，从IAB网络中目标Donor设备的一侧进行说明，图11的方法与图10的方法对应。如图11所示，该方法包括：
1101：接收源Donor设备发送的第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
1102：向所述源Donor设备发送第一响应消息，所述第一响应消息包含针对所述迁移IAB节点的RRC重配置消息；
1103：与所述迁移IAB节点建立新F1连接；
1104：通过所述新F1连接向所述迁移IAB节点服务的子IAB节点或UE发送RRC重配置消息；
1105：接收所述迁移IAB节点及其服务的子IAB节点或UE发送的RRC重配置完成消息。
图8和图9的方法对应前述场景一，图10和图11的方法对应前述场景二，根据本申请实施例的方法，当一个IAB节点在不同的Donor设备间移动时，无需通过RRC重建立方式与目标Donor设备之间重新建立RRC连接，可减小在IAB节点移动过程中的业务通信中断时间。
在本申请实施例中，在一些实施例中，迁移IAB节点的上下文信息包括：所述迁移IAB节点的IAB-DU上下文和IAB-MT上下文；子IAB节点的上下文信息包括：所述子IAB节点的IAB-DU上下文和IAB-MT上下文。
在一些实施例中，上述迁移IAB节点的IAB-DU上下文包括：所述迁移IAB节点的IAB-DU在所述源Donor设备下的服务小区信息。这里，服务小区信息包括以下至少之一：新无线小区全球标识符(Cell Global Identifier，NR CGI)；新无线物理小区标识(Physical Cell ID，NR PCI)；所述IAB-DU服务的公共陆地移动网(Public Land Mobile Network，PLMN)；上下行传输频点和带宽。本申请不限于此。
在一些实施例中，上述迁移IAB节点的IAB-MT上下文包括BAP配置信息。该BAP配置信息包括所述源Donor设备为IAB节点分配的BAP地址、传输层(IP)地址、默认上行回传RLC信道标识和/或默认上行BAP路由标识。该默认上行BAP路由标识是指默认目的BAP地址和默认路径标识。
在本申请实施例中，在一些实施例中，上述第一切换请求消息还包含源Donor 设备为迁移IAB节点或子IAB节点配置的回传信息。
在一些实施例中，所述回传信息至少包括以下之一：
上一跳节点的BAP地址和入口回传RLC信道的标识与下一跳节点的BAP地址和出口回传RLC信道的标识之间的对应关系；
源Donro设备为迁移IAB节点或子IAB节点配置的BAP路由标识和下一跳节点的BAP地址的对应关系。
图12示出了IAB节点的入口和出口之间的关系。
在一些实施例中，所述回传信息至少包括以下之一：
迁移IAB节点或子IAB节点所服务的UE的DRB使用的BAP路由标识、下一跳节点的BAP地址和回传RLC信道标识；
F1控制面数据或非F1数据使用的BAP路由标识、下一跳节点的BAP地址和回传RLC信道标识。
在上述实施例中，所述BAP路由标识包括目的BAP地址和路径ID标识。下面给出了BAP路由标识的一个示例：
Figure PCTCN2020123024-appb-000001
在本申请实施例中，在一些实施例中，上述第一切换请求消息还包含：拓扑信息，该拓扑信息包括迁移IAB节点与其服务的子IAB节点或UE之间的拓扑关系，或者包括子IAB节点与其服务的子IAB节点或UE之间的拓扑关系。
在本申请实施例中，在一些实施例中，上述第一切换请求消息还包括：地址请求信息，该地址请求信息用于请求目标Donor设备为迁移IAB节点或子IAB节点分配新的传输层(IP)地址或BAP地址。
在本申请实施例中，在前述903和1103中，目标Donor设备与迁移IAB节点建立新F1连接，可以是：目标Donor设备接收迁移IAB节点发送的F1建立请求消息；向迁移IAB节点发送F1建立响应消息。由此，目标Donor设备与迁移IAB节点建立起新的F1连接。
在本申请实施例中，在一些实施例中，目标节点还可以与子IAB节点之间建立新F1连接。建立的方式与前述相同。本申请不限于此。
在本申请实施例中，在目标Donor设备接收到迁移IAB节点发送的RRC重配置完成消息后，该目标Donor设备还可以为迁移IAB节点配置回传RLC信道映射和 BAP路由配置。在一些实施例中，BAP路由配置包括路由标识、路由标识和下一跳BAP地址的对应关系。
在本申请实施例中，在目标Donor设备接收到迁移IAB节点发送的RRC重配置完成消息后，或与迁移IAB节点建立新F1连接后，该目标Donor设备还可以向源Donor设备发送第一指示消息，通过该第一指示消息来指示源Donor设备向子IAB节点或UE发送RRC重配置消息。
在本申请实施例中，上述迁移IAB节点的上下文信息和上述子IAB节点或上述UE的上下文信息包含于相同的Xn消息或不同的Xn消息。
在一些实施例中，源Donor设备首先向目标Donor发送包含迁移IAB节点的上下文信息的Xn消息，使目标Donor首先发送针对迁移IAB节点的RRC重配置消息。在所述目标Donor设备接收到迁移IAB节点发送的RRC重配置完成消息后，或与迁移IAB节点建立新F1连接后，该目标Donor设备还可以向源Donor设备发送第二指示消息。通过该第二指示消息指示源Donor设备向目标Donor设备发送包含子IAB节点或UE的上下文的Xn消息，从而使目标Donor发送针对子IAB节点或UE的RRC重配置消息。
在本申请实施例中，针对所述迁移IAB节点的RRC重配置消息和针对子IAB节点或UE的RRC重配置消息包含于相同的Xn消息或不同的Xn消息。
在一些实施例中，目标Donor首先发送针对迁移IAB节点的RRC重配置消息，在目标Donor设备接收到迁移IAB节点发送的RRC重配置完成消息后，或与迁移IAB节点建立新F1连接后，目标Donor设备再向源Donor设备发送包含针对子IAB节点或UE的RRC重配置消息的Xn消息。
在本申请实施例中，在一些实施例中，在目标Donor设备接收到迁移IAB节点发送的RRC重配置完成消息以及子IAB节点发送的RRC重配置完成消息后，该目标Donor设备还可以为该子IAB节点配置BAP路由，由于子IAB节点在切换到目标Donor后可能不改变回传RLC信道映射，所以目标Donor设备可以仅为子IAB节点配置BAP路由配置。
在本申请实施例中，针对迁移IAB节点的RRC重配置消息至少包括以下之一：切换到目标Donor设备使用的默认上行回传RLC信道标识(用于F1接口控制面或非F1数据)；切换到目标Donor设备使用的默认BAP路由标识(用于F1控制面数据或非 F1数据)；切换到目标Donor设备使用的BAP地址；切换到目标Donor设备使用的传输层地址；以及切换到目标Donor设备使用的安全密钥配置。
在一些实施例中，针对迁移IAB节点的RRC重配置消息还包括：切换到目标Donor设备使用的回传RLC信道映射和BAP路由配置。
在本申请实施例中，针对子IAB节点的RRC重配置消息包括以下至少之一：切换到目标Donor设备使用的默认BAP路由标识(用于F1控制面数据或非F1数据)；切换到所述目标Donor设备使用的BAP地址；切换到目标Donor设备使用的传输层地址；以及切换到目标Donor设备使用的安全密钥配置。
在上述实施例中，因为子IAB-node在切换后仍然是连接到migrating IAB-node DU，所以可能不会改变针对F1控制面数据或非F1数据的默认上行回传RLC信道标识，RRCReconfiguration消息不一定包含新的默认上行回传RLC信道。
在一些实施例中，针对子IAB节点的RRC重配置消息还包括：切换到所述目标Donor设备使用的BAP路由配置。
其中，在上述实施例中，回传RLC信道映射至少包括以下之一：
上一跳节点的BAP地址和入口回传RLC信道的标识与下一跳节点的BAP地址和出口回传RLC信道的标识之间的对应关系；
迁移IAB节点所服务的UE的DRB使用的回传RLC信道标识。
其中，在上述实施例中，BAP路由配置至少包括以下之一：
BAP路由标识与下一跳节点的BAP地址的对应关系；
迁移IAB节点所服务的UE的DRB使用的BAP路由标识和下一跳节点的BAP地址。
在上述实施例中，BAP路由标识包括目的BAP地址和路径ID标识。
在本申请实施例中，在一些实施例中，针对所述UE的RRC重配置消息包括：切换到所述目标Donor设备使用的安全密钥配置。
值得注意的是，以上图8至图11仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作，或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图8至图11的记载。
根据本申请实施例的方法，如前所述，可减小在IAB节点移动过程中的业务通 信中断时间。
第二方面的实施例
本申请实施例提供一种群组切换方法，从IAB网络中的迁移IAB节点的一侧进行说明。
图13是本申请实施例的群组切换方法的一个示意图，该方法是与图8和图9的方法对应的迁移IAB节点的一侧的处理，其中与图8和图9的方法相同的内容不再重复说明。如图13所示，该方法包括：
1301：向源Donor设备发送测量报告；
1302：接收源Donor设备发送的RRC重配置消息；
1303：与目标Donor设备建立新F1连接；
1304：接收源Donor设备通过旧F1连接发送的针对该迁移IAB节点服务的子IAB节点或UE的RRC重配置消息；
1305：将该RRC重配置消息发送给子IAB节点或所述UE；
1306：向目标Donor设备发送RRC重配置完成消息；
1307：向所述目标Donor设备转发所述子IAB节点或所述UE发送的RRC重配置完成消息。
图14是本申请实施例的群组切换方法的另一个示意图，该方法是与图10和图11的方法对应的迁移IAB节点的一侧的处理，其中与图10和图11的方法相同的内容不再重复说明。如图14所示，该方法包括：
1401：向源Donor设备发送测量报告；
1402：接收源Donor设备发送的RRC重配置消息；
1403：与目标Donor设备建立新F1连接；
1404：接收目标Donor设备通过所述新F1连接发送的针对迁移IAB节点服务的子IAB节点或UE的RRC重配置消息；
1405：将该RRC重配置消息发送给上述子IAB节点或所述UE；
1406：向目标Donor设备发送RRC重配置完成消息；
1407：向所述目标Donor设备转发所述子IAB节点或所述UE发送的RRC重配置完成消息。
根据本申请实施例的方法，当一个IAB节点在不同的Donor设备间移动时，无需通过RRC重建立方式与目标Donor设备之间重新建立RRC连接，可减小在IAB节点移动过程中的业务通信中断时间。
在本申请实施例中，在1305和1403中，与目标Donor设备建立新F1连接，可以是：向目标Donor发送F1建立请求消息，请求建立与目标Donor设备之间的新F1连接；然后，接收目标Donor设备发送的F1建立响应消息，由此建立起与目标Donor设备之间的新F1连接。
在一些实施例中，在1305或1403之后，也即，在上述新F1连接建立完成之后，该迁移IAB节点保持与源Donor设备之间的旧F1连接，并且在以下条件之一满足的情况下释放与源Donor设备之间的旧F1连接：
向迁移IAB节点服务的子IAB节点或UE发送完RRC重配置消息后；
收到迁移IAB节点服务的子IAB节点或UE发送的RRC重配置完成消息后；
与目标Donor设备之间的新F1连接建立完成的预定时间之后。
在一些实施例中，在1305或1403之后，也即，在新F1连接建立完成之后，该迁移IAB节点向源Donor设备发送F1释放请求消息，释放与源Donor设备之间的旧F1连接。
在一些实施例中，在1305之后，也即在所述新F1连接建立完成之后，该迁移IAB节点再将从旧F1连接收到的针对子IAB节点或UE的RRC重配置消息发送给该子IAB节点或该UE。或者，在新F1连接建立完成之后，再将子IAB节点或UE的RRC重配置完成消息转发给目标Donor设备。这样，可以保证迁移节点通过该新F1连接将子IAB节点或UE的RRC重配置完成消息成功地发送给目标Donor设备。
在一些实施例中，在1306或1406之后，也即，在该迁移IAB节点向目标Donor设备发送所述RRC重配置完成消息后，该迁移IAB节点还可以接收目标Donor设备配置的回传RLC信道映射和BAP路由配置。
在本申请实施例中，所述RRC重配置消息包括以下之一：切换到目标Donor设备使用的默认上行回传RLC信道标识；切换到目标Donor设备使用的默认BAP路由标识；切换到目标Donor设备使用的BAP地址；切换到目标Donor设备使用的传输层地址；以及切换到目标Donor设备使用的安全密钥配置。
在一些实施例中，所述RRC重配置消息还包括：切换到目标Donor设备使用的 回传RLC信道映射和BAP路由配置。由此，在1306或1406之后，也即，在该迁移IAB节点向目标Donor设备发送RRC重配置完成消息后，该迁移IAB节点可以应用该回传RLC信道映射和BAP路由配置。
在以上实施例中，对回传RLC信道映射和BAP路由配置的解释可参考第一方面的实施例，此处不再赘述。
值得注意的是，以上图13和图14仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作，或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图13和图14的记载。
根据本申请实施例的方法，如前所述，可减小在IAB节点移动过程中的业务通信中断时间。
第三方面的实施例
本申请实施例提供一种群组切换方法，从IAB网络中的迁移IAB节点服务的子IAB节点的一侧进行说明，其中与第一方面和第二方面的实施例相同的内容不再重复说明。
图15是本申请实施例的群组切换方法的一个示意图，如图15所示，该方法包括：
1501：接收源Donor设备或目标Donor设备发送的RRC重配置消息；
1502：与目标Donor设备之间建立新F1连接；
1503：向目标Donor设备发送RRC重配置完成消息。
根据本申请实施例的方法，当一个IAB节点在不同的Donor设备间移动时，该IAB节点服务的子IAB节点可以随之切换，无需通过RRC重建立方式与目标Donor设备之间重新建立RRC连接，可减小在IAB节点移动过程中的业务通信中断时间。
在本申请实施例中，在1502中，该子IAB节点与目标Donor设备之间建立新F1连接，可以是：该子IAB节点向目标Donor发送F1建立请求消息，请求建立与目标Donor设备之间的F1连接；接收目标Donor设备发送的F1建立响应消息，由此建立起与目标Donor设备之间的F1连接。
在本申请实施例中，在一些实施例中，在1502之后，也即，在新F1连接建立起来之后，该子IAB节点可以保持与源Donor设备之间的旧F1连接，并且在以下条件 之一满足的情况下释放与源Donor设备之间的旧F1连接，例如是：
向其所服务的孙IAB节点或UE发送完RRC重配置消息后；或，
收到其所服务的孙IAB节点或UE发送RRC重配置完成消息后；或，
与目标Donor设备之间的新F1连接建立后的预定时间之后。
在本申请实施例中，在一些实施例中，在1502之后，也即，在新F1连接建立起来之后，该子IAB节点可以向源Donor设备发送F1释放请求消息，释放与源Donor设备之间的旧F1连接。
在本申请实施例中，在一些实施例中，该子IAB节点还可以接收所述目标Donor设备通过所述新F1连接发送的F1AP(F1 Application Protocol，F1接口应用协议)消息，并将所述RRC重配置消息发送给所述孙IAB节点或UE。其中，所述F1AP消息包含针对所述子IAB节点服务的孙IAB节点或UE的RRC重配置消息。
在本申请实施例中，在一些实施例中，在1503之后，也即，在该子IAB节点向目标Donor设备发送RRC重配置完成消息后，该子IAB节点还可以接收目标Donor配置的BAP路由配置。其中，BAP路由配置中包括的内容可参考第一方面的实施例，此处不再赘述。
在本申请实施例中，在一些实施例中，该子IAB节点还可以接收源Donor设备通过与该子IAB节点之间的旧F1连接发送的F1AP消息，并将RRC重配置消息发送给所服务的孙IAB节点或UE。其中，F1AP消息中包含针对该子IAB节点服务的孙IAB节点或UE的RRC重配置消息。
在上述实施例中，在1502之后，也即，在新F1连接建立完成之后，该子IAB节点再将RRC重配置消息发送给服务的孙IAB节点或UE。或者，在新F1连接建立完成之后，再将服务的孙IAB节点或UE的RRC重配置完成消息转发给目标Donor设备。这样，可以保证该子IAB节点通过新F1连接将所服务的孙IAB节点或UE的RRC重配置完成消息成功地发送给目标Donor设备。
在本申请实施例中，针对上述子IAB节点的RRC重配置消息包括以下之一：切换到目标Donor设备使用的默认上行回传RLC信道标识；切换到目标Donor设备使用的默认BAP路由标识；切换到目标Donor设备使用的BAP地址；切换到目标Donor设备使用的传输层地址；以及切换到目标Donor设备使用的安全密钥配置。
在一些实施例中，针对上述子IAB节点的RRC重配置消息还可以包括：切换到 所述目标Donor设备使用的BAP路由配置。由此，在该子IAB节点确定迁移IAB节点完成切换到目标Donor设备后，并且在向目标Donor设备发送所述RRC重配置完成消息后，该子IAB节点可以应用该BAP路由配置。
本申请实施例还提供一种群组切换方法，从IAB网络中的迁移IAB节点服务的终端设备的一侧进行说明，其中与第一方面和第二方面的实施例相同的内容不再重复说明。
1601：接收源Donor设备或目标Donor设备发送的RRC重配置消息；
1602：向目标Donor设备发送RRC重配置完成消息。
在本申请实施例中，该RRC重配置消息可以包括：切换到所述目标Donor设备使用的安全密钥配置。
根据本申请实施例的方法，当一个IAB节点在不同的Donor设备间移动时，该IAB节点服务的终端设备可以随之切换，无需通过RRC重建立方式与目标Donor设备之间重新建立RRC连接，可减小在IAB节点移动过程中的业务通信中断时间。
值得注意的是，以上图15和图16仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作，或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图15和图16的记载。
根据本申请实施例的方法，如前所述，可减小在IAB节点移动过程中的业务通信中断时间。
以上通过第一方面至第三方面的实施例对本申请实施例的群组切换方法做了说明。为了使本申请实施例的方法更加清楚易懂，下面对应前述两个场景通过信息交互的流程对本申请实施例的方法进行说明。
图17是对应前述场景一的信令交互流程图，在该场景中，Migrating IAB-node的IAB-MT和子IAB-node的IAB-MT及migrating IAB-node服务的UE同时进行切换。源Donor可以同时向migrating IAB-node，下游子IAB-node及UE发送RRC重配置消息。
如图17所示，该流程包括：
1701：源Donor接收migrating IAB-node发送的测量报告，确定需要将migrating  IAB-node切换到目标Donor。
1702：源Donor向目标Donor发送第一切换请求消息，第一切换请求消息中包括对migrating IAB-node、下游子IAB-node及UE的上下文信息。
其中，对每个IAB-node和UE的切换准备信息可以通过不同的Xn消息发送，也可以在同一条Xn消息中发送。
1703：目标Donor向目标Donor下的migrating IAB-node的父IAB-node发送UE CONTEXT SETUP REQUEST消息，为migrating IAB-node在目标Donor下的父IAB-node中创建上下文和无线承载。
1704：目标Donor接收目标Donor下的migrating IAB-node的父IAB-node发送的UE CONTEXT SETUP RESPONSE消息。
其中，由于子IAB-node或UE在切换后仍然是连接到migrating IAB-node，所以为子IAB-node或UE在migrating IAB-node中建立IAB-node或UE上下文和无线承载的步骤可以省略。
1705：目标Donor向源Donor发送第一响应消息，第一响应消息中包括对migrating IAB-node、子IAB-node及UE的RRC重配置消息。
其中，对每个IAB-node和UE的RRC重配置消息可以通过不同的Xn消息发送，也可以在同一条Xn消息中发送。
1706：源Donor向源Donor下的migrating IAB-node的父IAB-node发送DL RRC MESSAGE TRANSFER或UE CONTEXT MODIFICATION REQUEST，其中包含针对migrating IAB-node的RRCReconfiguration消息。
其中，针对migrating IAB-node的RRCReconfiguration消息里至少包括以下配置信息：
切换到目标Donor使用的新的默认上行回传RLC信道标识(用于F1接口控制面和非F1数据)；
切换到目标Donor使用的新的默认上行BAP路由标识(用于F1接口控制面和非F1数据)；
切换到目标Donor使用的新的传输层(IP)地址配置；
切换到目标Donor使用的新的安全密钥配置。
其中，为了不影响正在传输的业务，RRCReconfiguration消息里还可以包括切换 到目标Donor后使用的回传信息，例如，目标Donor给migrating IAB-node配置的回传RLC信道映射信息和BAP路由配置信息。
其中，回传RLC信道映射信息例如为：
上一跳节点的BAP地址和入口回传RLC信道的标识与下一跳节点的BAP地址和出口回传RLC信道的标识之间的对应关系；
migrating IAB-node所服务的UE的DRB使用的回传RLC信道标识。
其中，BAP路由配置信息例如为：
BAP路由标识与下一跳节点的BAP地址的对应关系；
migrating IAB-node所服务的UE的DRB使用的BAP路由标识和下一跳节点的BAP地址。
1707：源Donor向migrating IAB-node发送RRCReconfiguration消息。此后，migrating IAB-node可以继续向子IAB-node或UE提供原空口接入服务，也可以停止原空口接入服务。
1708：源Donor通过与migrating IAB-node的F1连接发送F1AP消息(DL RRC MESSAGE TRANSFER或UE CONTEXT MODIFICATION REQUEST)，其中包含针对子IAB-node或UE的RRCReconfiguration消息。
其中，针对子IAB-node的RRCReconfiguration消息里例如包括：切换到所述目标Donor设备使用的默认BAP路由配置(用于F1接口控制面数据或非F1数据)；切换到所述目标Donor设备使用的BAP地址；切换到所述目标Donor设备使用的传输层(IP)地址配置；切换到目标Donor使用的安全密钥配置。
其中，因为子IAB-node在切换后仍然是连接到migrating IAB-node DU，所以可能不会改变针对F1接口控制面数据或非F1数据的默认上行回传RLC信道标识，所以RRCReconfiguration消息不一定包含新的默认上行回传RLC信道标识。
同样的，为了不影响正在传输的业务，针对子IAB-node的RRCReconfiguration消息里还可以包含切换到目标Donor后使用的BAP路由配置。
其中，BAP路由配置信息例如为：
BAP路由标识与下一跳节点的BAP地址的对应关系；
迁移IAB节点所服务的UE的DRB使用的BAP路由标识和下一跳节点的BAP地址。
其中，因为子IAB-node在切换前后不一定需要改变F1接口用户面或子节点回传数据的RLC信道映射关系，所以不需要重新配置RLC信道映射信息。
此外，针对UE的RRCReconfiguration消息至少包含：切换到目标Donor使用的安全密钥配置。因为迁移IAB-node在切换前后不一定改变服务小区的PCI(Physical Cell Identity，物理小区标识)和频点，目标Donor对于UE只需配置新的安全密钥。
1709：Migrating IAB-node向子IAB-node或UE转发RRCReconfiguration消息。
前述步骤1706和1707与前述步骤1708和1709之间没有先后关系，例如，步骤1708可以在步骤1706之前执行。
1710：Migrating IAB-node使用配置的新的传输层(IP)地址通过目标Donor连接到OAM，下载OAM数据，与目标Donor建立新的SCTP连接。
1711：Migrating IAB-node通过新的SCTP连接向目标Donor发送F1AP消息(F1 Setup Request消息)，并接收目标Donor发送的F1 Setup Response，从而与目标Donor建立新的F1连接。
其中，如果migrating IAB-node未接入目标Donor下的父IAB-node，步骤1710和1711的消息可以通过原路径(old path)转发给目标Donor，也即，步骤1710和1711的消息的传输路径为：migrating IAB-node→源Donor→目标Donor。
在上述例子中，Migrating IAB建立完新F1连接可作为目标Donor下的IAB-node从而为子IAB-node或UE提供新的空口接入服务。
1712：子IAB-node使用配置的新的传输层(IP)地址通过目标Donor连接到OAM，下载OAM数据，与目标Donor建立新的SCTP连接。
1713：子IAB-node通过新的SCTP连接向目标Donor发送F1AP消息(F1 Setup Request)，接收目标Donor发送的F1 setup response，从而与目标Donor建立新的F1连接。
其中，如果migrating IAB-node此时还未接入目标父IAB-node，步骤1712、1713的消息可以通过原路径转发给目标Donor，也即，步骤1712和1713的消息的传输路径为：子IAB-node→migrating IAB-node→源Donor→目标Donor。
在上述例子中，步骤1710和1711和步骤1712和1713之间没有先后关系，例如，步骤1710可以只要在步骤1707之后执行即可，步骤1712只要在步骤1709完成后执行即可。
1714：Migrating IAB-node向目标Donor下的父IAB-node发起随机接入并发送RRCReconfigurationComplete消息，目标Donor下的父IAB-node将这个消息放在F1AP消息(UL RRC MESSAGE TRANSFER)中传递给目标Donor。之后migrating IAB-node可以通过新的上行回传RLC信道和新默认BAP路径发送自己产生的信令或数据。
在上述例子中，步骤1714只要在步骤1707之后执行即可。
1715：目标Donor为migrating IAB-node通过F1AP消息配置新的回传RLC信道映射和BAP路由配置。之后migrating IAB-node可以通过新的回传RLC信道和新BAP路径发送所服务的UE和子IAB-node的信令或数据。
其中，如果上述步骤1706中针对migrating IAB-node的RRCReconfiguration消息包含新的回传RLC信道映射和BAP路由配置，则步骤1715是可选的。
1716：子IAB-node或UE向migrating IAB-node发送RRCReconfigurationComplete消息，migrating IAB-node将这个消息放在F1AP消息(UL RRC MESSAGE TRANSFER)中通过新F1连接转发给目标Donor。之后子IAB-node可以通过新默认BAP路径发送自己产生的信令或数据。
1717：目标Donor通过F1AP消息为子IAB-node配置新的BAP路由。之后子IAB-node可以通过新BAP路径发送所服务的UE和IAB-node(称为孙IAB-node)的信令或数据。
其中，如果上述步骤1708中针对migrating IAB-node的RRCReconfiguration消息包括新BAP路由配置，则步骤1717是可选的。
在上述例子中，步骤1715和1717需要在步骤1714之后完成，即目标Donor收到migrating IAB-node发送的RRCReconfigurationComplete之后。
在图17的示例中，Migrating IAB-node和子IAB-node及migrating IAB-node服务的UE同时进行切换，多个步骤可以并行执行，所以整体切换流程花费的时间较短。
值得注意的是，在上述例子中，如果Migrating IAB-node切换到目标Donor后不改变PCI和频率，为将子IAB-node或UE的RRCReconfigurationComplete消息成功发给目标Donor，步骤1716要在步骤1711之后执行，或者，也可以使步骤1709在步骤1711之后执行，即在migrating IAB-node与目标Donor建立完成新的F1连接之后。
另外，如果Migrating IAB-node切换到目标Donor后改变了PCI或频率，migrating  IAB-node与目标Donor建立完成新的F1连接之后作为目标Donor下的DU提供新的空口接入服务，应用新PCI或频率，这样，子IAB-node或UE可以在检测到migrating IAB-node的新PCI或新频率的小区参考信号之后，发送RRCReconfigurationComplete消息，可保证成功切换。
图18是对应前述场景二的信息交互流程图，在该场景中，migrating IAB-node服务的子IAB-node和UE在migrating IAB-node的IAB-DU或IAB-MT切换之后才能进行切换。源Donor或目标Donor在目标Donor与migrating IAB-node建立新F1连接后，或在目标Donor收到migrating IAB-node发送的RRCReconfigurationComplete消息后，向子IAB-node及UE发送RRC重配置消息。
如图18所示，该流程包括：
1801：源Donor接收migrating IAB-node MT发送的测量报告，确定需要将migrating IAB-node切换到目标Donor。
1802：源Donor向目标Donor发送第一切换请求消息，第一切换请求消息中包括对migrating IAB-node、子IAB-node及UE的上下文信息。
其中，对每个IAB-node和UE的上下文信息可以通过不同的Xn消息发送，也可以在同一条Xn消息中发送。
在本实施例中，这一步骤的第一切换请求可以只包含针对migrating IAB-node的上下文信息，在目标Donor与migrating IAB-node建立新F1连接后，或在目标Donor收到migrating IAB-node发送的RRCReconfigurationComplete消息后再向目标Donor发送子IAB-node及UE的上下文信息。
1803：目标Donor向目标Donor下的migrating IAB-node的父IAB-node发送UE CONTEXT SETUP REQUEST消息，为migrating IAB-node在目标Donor下的父IAB-node中创建上下文和无线承载。
1804：目标Donor接收目标Donor下的父IAB-node发送的UE CONTEXT SETUP RESPONSE消息。
其中，由于子IAB-node或UE在切换后仍然是连接到migrating IAB-node，所以为子IAB-node或UE在migrating IAB-node DU中建立IAB-node或UE上下文和无线承载的步骤可以省略。
1805：目标Donor向源Donor发送第一响应消息，第一响应消息中包括对migrating  IAB-node、子IAB-node和UE的RRC重配置消息。
其中，对每个IAB-node和UE的RRC重配置消息可以通过不同的Xn消息发送，也可以在同一条Xn消息中发送。
在本实施例中，如果目标Donor通过与migrating node之间的新F1连接发送针对子IAB-node或UE的RRCReconfiguration消息，则这一步骤的第一响应消息可以只包括针对migrating IAB-node的RRC重配置消息(即切换命令)。
1806：源Donor向源Donor下的migrating IAB-node的父IAB-node发送F1AP消息(DL RRC MESSAGE TRANSFER或UE CONTEXT MODIFICATION REQUEST)，其中包含针对migrating IAB-node的RRCReconfiguration消息。
其中，针对migrating IAB-node的RRCReconfiguration消息里包括：
切换到目标Donor使用的新的默认上行回传RLC信道标识(用于F1控制面数据和非F1数据)；
切换到目标Donor使用的新的默认上行BAP路由标识(用于F1控制面数据和非F1数据)；
切换到目标Donor使用的新的传输层(IP)地址配置；
切换到目标Donor使用的新的安全密钥配置；
其中，为了不影响正在传输的业务，RRCReconfiguration消息里还可以包括切换到目标Donor后使用的回传信息，例如：目标Donor给migrating IAB-node配置的回传RLC信道映射信息和BAP路由配置信息：
其中，上述回传RLC信道映射信息例如包括：
上一跳节点的BAP地址和入口回传RLC信道的标识与下一跳节点的BAP地址和出口回传RLC信道的标识之间的对应关系；
migratingIAB-node所服务的UE的DRB使用的回传RLC信道标识。
其中，上述BAP路由配置信息例如包括：
BAP路由标识与下一跳节点的BAP地址的对应关系；
migratingIAB-node所服务的UE的DRB使用的BAP路由标识和下一跳节点的BAP地址。
1807：源Donor向migrating IAB-node发送RRCReconfiguration消息。此外，由于要向子IAB-node或UE发送RRCReconfiguration消息，Migrating IAB-node需要继 续向子IAB-node或UE提供原空口接入服务。
1808：Migrating IAB-node使用配置的新的传输层(IP)地址通过目标Donor连接到OAM，下载OAM数据，与目标Donor建立新的SCTP连接。
1809：Migrating IAB-node通过新的SCTP连接向目标Donor发送F1AP消息(F1Setup Request)消息，并接收目标Donor发送的F1 Setup Response消息，与目标Donor建立新的F1连接。
其中，如果migrating IAB-node还未接入目标Donro下的父IAB-node，所以步骤1810和1811的消息可以是通过原路径(old path)转发给目标Donor，也即，步骤1810和1811的消息的传输路径为：migrating IAB-node→源Donor→目标Donor。
在这个例子中，Migrating IAB-node建立完新F1连接可作为目标Donor下的IAB节点，从而向子IAB-node或UE提供新的空口接入服务。
1810：在目标Donor与migrating IAB-node建立新F1连接后，有两种方式发送子IAB-node或UE的RRCReconfiguration消息：
方式一(A)：源Donor通过旧F1连接向migrating IAB-node发送F1AP消息(DL RRC MESSAGE TRANSFER或UE CONTEXT MODIFICATION REQUEST)，其中包含针对子IAB-node或UE的RRCReconfiguration消息。Migrating IAB-node向子IAB-node或UE转发RRCReconfiguration消息。
此方式应用在新F1连接建立之后依然保持migrating IAB-node与源Donor之间的F1连接的场景，例如可有三种实现方法：
方法一：目标Donor向源Donor发送包含针对子IAB-node或所服务UE的RRC重配置消息的第二响应消息，以使源Donor发送针对子IAB-node或UE的RRCReconfiguration消息。
方法二：目标Donor向源Donor发送第一指示消息，以触发源Donor发送子IAB-node或UE的RRCReconfiguration消息。
方法三：目标Donor向源Donor发送第二指示消息，以触发源Donor向目标Donor发送包含子IAB-node或UE的上下文信息的Xn消息，以使目标Donor向源Donor发送针对子IAB-node或UE的RRC重配置消息，从而使源Donor发送子IAB-node或UE的RRCReconfiguration消息。
方式二(B)：目标Donor通过新F1连接向migrating IAB-node发送F1AP消息(DL  RRC MESSAGE TRANSFER或UE CONTEXT MODIFICATION REQUEST)，其中包含针对子IAB-node或UE的RRCReconfiguration消息。Migrating IAB-node向子IAB-node或UE转发RRCReconfiguration消息。
此方式应用在新F1连接建立后立即释放migrating IAB-node与源Donor之间的旧F1连接的场景。
在上述例子中，针对子IAB-node的RRCReconfiguration消息里包括：切换到所述目标Donor设备使用的默认BAP路由标识；切换到所述目标Donor设备使用的BAP地址；切换到目标Donor使用的传输层(IP)地址配置；切换到目标Donor使用的安全密钥配置。
在上述例子中，针对UE的RRCReconfiguration消息至少包含切换到目标Donor使用的安全密钥配置。因为迁移IAB-node在切换前后不一定改变服务小区的PCI(Physical Cell Identity，物理小区标识)和频点，目标Donor对于UE只需配置新的安全密钥。
1811：子IAB-node使用配置的新的传输层(IP)地址通过目标Donor连接到OAM，下载OAM数据，与目标Donor CU建立新的SCTP连接。
1812：子IAB-node通过新的SCTP连接向目标Donor发送F1AP消息(F1 Setup Request)，并接收目标Donor发送的F1 setup response，从而与目标Donor建立新的F1连接。
其中，如果migrating IAB-node还未接入目标Donor下的父IAB-node，步骤1812和1813的消息可以是通过原转发给目标Donor，也即，步骤1812和1813的消息的传输路径为：子IAB-node→migrating IAB-node→源Donor→目标Donor。
在上述例子中，Migrating IAB建立完新F1连接可作为目标Donor下的IAB-node，从而为子IAB-node或UE提供新的空口接入服务。
1813：Migrating IAB-node向目标Donor下的父IAB-node发起随机接入并发送RRCReconfigurationComplete消息，目标父IAB-node将这个消息放在F1AP消息(UL RRC MESSAGE TRANSFER)中传递给目标Donor。之后migrating IAB-node可以通过新的上行回传RLC信道和新默认BAP路径发送自己产生的信令或数据。
在上述例子中，步骤1813只要在步骤1807之后执行即可。
1814：目标Donor为migrating IAB-node通过F1AP消息配置新的回传RLC信道 映射和BAP路由配置。之后migrating IAB-node可以通过新的回传RLC信道和新BAP路径发送所服务的UE和子IAB-node的信令或数据。
其中，如果步骤1806中针对migrating IAB-node的RRCReconfiguration消息包含新的回传RLC信道映射和BAP路由配置，则上述步骤1814是可选的。
1815：子IAB-node向migrating IAB-node发送RRCReconfigurationComplete消息，migrating IAB-node将这个消息放在F1AP消息(UL RRC MESSAGE TRANSFER)中转发给目标Donor。之后子IAB-node可以通过新默认BAP路径发送自己产生的信令或数据。
1816：目标Donor通过F1AP消息为子IAB-node配置新的BAP路由。之后子IAB-node可以通过新BAP路径发送所服务的UE和孙IAB-node的信令或数据。
其中，如果上述步骤1810中针对migrating IAB-node的RRCReconfiguration消息包括新BAP路由配置，则步骤1816是可选的。
在上述例子中，步骤1814和1816需要在步骤1813之后完成，即在目标Donor收到migrating IAB-node发送的RRCReconfigurationComplete之后执行。
在图18的示例中，migrating IAB-node与目标Donor建立完成新的F1连接之后，才向子IAB-node或UE发送RRCReconfiguration消息。这样可保证migrating IAB-node与目标Donor建立完成新的F1连接之后向子IAB-node或UE发送RRCReconfigurationComplete消息，从而在migrating IAB-node不改变PCI和频点的场景下也可以保证切换成功。
在上述图17和图18的示例中，还涉及释放migrating IAB-node或子IAB-node与源Donor之间的旧F1连接。
在一些实施例中，可以在新F1连接建立之后依然保持migrating IAB-node或子IAB-node与源Donor之间的旧F1连接，释放条件有如下几种：
条件一：向所有子IAB-node及服务的UE发送完RRCReconfiguration消息后，释放与源Donor之间的旧F1连接；
其中，源Donor已将包含针对下游子IAB-node或UE的RRCReconfiguration的F1消息通过旧F1连接发送完成，无需继续使用旧F1连接；
条件二：收到所有子IAB-node及服务的UE发送的RRCReconfigurationComplete后，释放与源Donor之间的旧F1连接；
其中，由于子IAB-node或UE可能会切换或重配置失败，子IAB-node及服务的UE完成RRC重配置后再释放原F1连接，这样可以保证切换失败时子IAB-node或UE可以重新回到源Donor。
条件三：新F1连接建立后的预设时间之后释放原F1连接，以保证源Donor已将包含针对下游子IAB-node或UE的RRCReconfiguration的F1消息通过旧F1连接发送完成。例如启动一个定时器，在该定时器超时后释放原F1连接。
在一些实施例中，可以在新F1连接建立后立即释放migrating IAB-node或子IAB-node与源Donor之间的旧F1连接。
在这种情况下，migrating IAB-node只需维持一个F1连接，在新F1连接建立后无需保留与源Donor的旧F1连接。目标Donor可以直接通过新F1连接向migrating IAB-node或子IAB-node发送针对其下游子IAB-node或UE的RRC重配置消息，而不用将RRC重配置消息发给源Donor，通过原有F1连接发送子IAB-node或UE的RRCReconfiguration消息。参考实施例二的B。这样可以减少切换命令(也即RRCReconfiguration消息)的发送的时间。
第四方面的实施例
本申请实施例提供一种群组切换装置。
图19是本申请实施例的群组切换装置的一个示意图，该装置例如可以是IAB网络中的Donor设备，例如迁移IAB节点在迁移前的Donor设备，称为源Donor设备，也可以是配置于该Donor设备中的某个或某些部件或者组件。该装置的实施原理与第一方面的实施例的图8的方法类似，内容相同之处不再重复说明。如图19所示，本申请实施例的群组切换装置1900包括：
第一接收单元1901，其接收迁移IAB节点发送的测量报告；
第一发送单元1902，其向目标Donor设备发送第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
第二接收单元1903，其接收所述目标Donor设备发送的第一响应消息，所述第一响应消息包含针对所述迁移IAB节点及其服务的子IAB节点或UE的RRC重配置消息；
第二发送单元1904，其向所述迁移IAB节点及其服务的子IAB节点或UE发送 所述RRC重配置消息。
图20是本申请实施例的群组切换装置的一个示意图，该装置例如可以是IAB网络中的Donor设备，例如迁移IAB节点在迁移后的Donor设备，称为目标Donor设备，也可以是配置于该Donor设备中的某个或某些部件或者组件。该装置的实施原理与第一方面的实施例的图9的方法类似，内容相同之处不再重复说明。如图20所示，本申请实施例的群组切换装置2000包括：
第一接收单元2001，其接收源Donor设备发送的第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
第一发送单元2002，其向所述源Donor设备发送第一响应消息，所述第一响应消息包含针对所述迁移IAB节点及其服务的子IAB节点或UE的RRC重配置消息；
第一处理单元2003，其与所述迁移IAB节点建立新F1连接；
第二接收单元2004，其接收所述迁移IAB节点及其服务的子IAB节点或UE发送的RRC重配置完成消息。
图21是本申请实施例的群组切换装置的一个示意图，该装置例如可以是IAB网络中的Donor设备，例如迁移IAB节点在迁移前的Donor设备，称为源Donor设备，也可以是配置于该Donor设备中的某个或某些部件或者组件。该装置的实施原理与第一方面的实施例的图10的方法类似，内容相同之处不再重复说明。如图21所示，本申请实施例的群组切换装置2100包括：
第一接收单元2101，其接收迁移IAB节点发送的测量报告；
第一发送单元2102，其向目标Donor设备发送第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
第二接收单元2103，其接收所述目标Donor设备发送的第一响应消息，所述第一响应消息包含针对所述迁移IAB节点的RRC重配置消息；
第二发送单元2104，其向所述迁移IAB节点发送所述RRC重配置消息。
图22是本申请实施例的群组切换装置的一个示意图，该装置例如可以是IAB网络中的Donor设备，例如迁移IAB节点在迁移后的Donor设备，称为目标Donor设备，也可以是配置于该Donor设备中的某个或某些部件或者组件。该装置的实施原理与第一方面的实施例的图11的方法类似，内容相同之处不再重复说明。如图22所示，本申请实施例的群组切换装置2200包括：
第一接收单元2201，其接收源Donor设备发送的第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
第一发送单元2202，其向所述源Donor设备发送第一响应消息，所述第一响应消息包含针对所述迁移IAB节点的RRC重配置消息；
第一处理单元2203，其与所述迁移IAB节点建立新F1连接；
第二发送单元2204，通过所述新F1连接向所述迁移IAB节点服务的子IAB节点或UE发送RRC重配置消息；
第二接收单元2205，其接收所述迁移IAB节点及其服务的子IAB节点或UE发送的RRC重配置完成消息。
在本申请实施例中，所述迁移IAB节点的上下文信息包括：所述迁移IAB节点的IAB-DU上下文和IAB-MT上下文；所述子IAB节点的上下文信息包括：所述子IAB节点的IAB-DU上下文和IAB-MT上下文。
在一些实施例中，所述迁移IAB节点的IAB-DU上下文包括：所述迁移IAB节点的IAB-DU在所述源Donor设备下的服务小区信息。其中，所述服务小区信息包括以下至少之一：新无线小区全球标识符(Cell Global Identifier，NR CGI)；新无线物理小区标识(Physical Cell ID，NR PCI)；所述IAB-DU服务的公共陆地移动网(Public Land Mobile Network，PLMN)；上下行传输频点和带宽。
在一些实施例中，所述迁移IAB节点的IAB-MT上下文包括BAP配置信息；其中，所述BAP配置信息包括所述源Donor设备为所述IAB节点分配的BAP地址、传输层(IP)地址、默认上行回传RLC信道标识和/或默认上行BAP路由标识；其中，所述默认上行BAP路由标识是指默认目的BAP地址与默认路径标识。
在本申请实施例中，在一些实施例中，所述第一切换请求消息还包含源Donor设备为迁移IAB节点或子IAB节点配置的回传信息。
在一些实施例中，所述回传信息至少包括以下之一：
上一跳节点的BAP地址和入口回传RLC信道的标识、与下一跳节点的BAP地址和出口回传RLC信道的标识之间的对应关系；
源Donor设备为迁移IAB节点或子IAB节点配置的BAP路由标识和下一跳节点的BAP地址的对应关系。
在一些实施例中，所述回传信息包括：
所述迁移IAB节点或所述子IAB节点所服务的UE的DRB使用的BAP路由标识、下一跳节点的BAP地址以及回传RLC信道标识；以及，
F1控制面数据或非F1数据使用的BAP路由标识、下一跳节点的BAP地址以及回传RLC信道标识。
在上述实施例中，所述BAP路由标识包括目的BAP地址和路径ID标识。
在本申请实施例中，在一些实施例中，所述第一切换请求消息还包含：拓扑信息，所述拓扑信息包括所述迁移IAB节点与其服务的子IAB节点或UE之间的拓扑关系，或者包括所述子IAB节点与其服务的子IAB节点或UE之间的拓扑关系。
在本申请实施例中，在一些实施例中，所述第一切换请求消息还包括：地址请求信息，所述地址请求信息用于请求所述目标Donor设备为所述迁移IAB节点或所述子IAB节点分配新的传输层(IP)地址或BAP地址。
在上述实施例中，与所述迁移IAB节点建立新F1连接，包括：接收所述迁移IAB节点发送的F1建立请求消息；向所述迁移IAB节点发送F1建立响应消息。
在本申请实施例中，在一些实施例中，如图20和图22所示，所述装置2000/2200还包括：
第二处理单元2005/2206，其与所述子IAB节点之间建立新F1连接。
在本申请实施例中，在一些实施例中，如图20和图22所示，所述装置2000/2200还包括：
第一配置单元2006/2207，其在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息后，为所述迁移IAB节点配置回传RLC信道映射和BAP路由配置。
在本申请实施例中，在一些实施例中，如图20所示，所述装置2000还包括：
第二发送单元2007，其在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息后，或与所述迁移IAB节点建立新F1连接后，向所述源Donor设备发送第一指示消息；其中，所述第一指示消息用于指示所述源Donor设备向所述子IAB节点或所述UE发送RRC重配置消息。
在本申请实施例中，所述迁移IAB节点的上下文信息和所述子IAB节点或所述UE的上下文信息包含于相同的Xn消息或不同的Xn消息。
在上述实施例中，如图20和图22所示，该装置2000/2200还包括：
第三发送单元2008/2208，其在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息后，或与所述迁移IAB节点建立新F1连接后，向所述源Donor设备发送第二指示消息；其中，所述第二指示消息用于指示所述源Donor设备向所述目标Donor设备发送包含所述子IAB节点或所述UE的上下文的Xn消息。
在本申请实施例中，针对所述迁移IAB节点的RRC重配置消息和针对所述子IAB节点或所述UE的RRC重配置消息包含于相同的Xn消息或不同的Xn消息。
在上述实施例中，如图20和图22所示，该装置2000/2200还包括：
第四发送单元2009/2209，其在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息后，或与所述迁移IAB节点建立新F1连接后，向所述源Donor设备发送包含针对所述子IAB节点或所述UE的RRC重配置消息的Xn消息。
在本申请实施例中，如图20和图22所示，该装置2000/2200还包括：
第二配置单元2010/2210，其在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息以及所述子IAB节点发送的RRC重配置完成消息后，为所述子IAB节点配置BAP路由配置。
在本申请实施例中，针对所述迁移IAB节点的RRC重配置消息包括以下至少之一：切换到所述目标Donor设备使用的默认上行回传RLC信道标识；切换到所述目标Donor设备使用的默认BAP路由配置；切换到所述目标Donor设备使用的BAP地址；切换到所述目标Donor设备使用的传输层地址；以及切换到所述目标Donor设备使用的安全密钥配置。
在一些实施例中，针对所述迁移IAB节点的RRC重配置消息还包括：切换到所述目标Donor设备使用的回传RLC信道映射和BAP路由配置。
在本申请实施例中，针对所述子IAB节点的RRC重配置消息包括以下至少之一：切换到目标Donor设备使用的默认BAP路由标识；切换到所述目标Donor设备使用的BAP地址；切换到所述目标Donor设备使用的传输层地址；以及切换到所述目标Donor设备使用的安全密钥配置。
在一些实施例中，所述针对所述子IAB节点的RRC重配置消息还包括：切换到所述目标Donor设备使用的BAP路由配置。
在本申请实施例中，在一些实施例中，针对所述UE的RRC重配置消息包括：切换到所述目标Donor设备使用的安全密钥配置。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的群组切换装置1900/2000/2100/2200还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图19至图22中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
根据本申请实施例，如前所述，可减小在IAB节点移动过程中的业务通信中断时间。
第五方面的实施例
本申请实施例提供一种群组切换装置，该装置例如可以是IAB网络中的待迁移的IAB节点，称为迁移IAB节点，也可以是配置于该迁移IAB节点的某个或某些部件或者组件。
图23是本申请实施例的群组切换装置的一个示意图，该装置解决问题的原理与第二方面的实施例的图13的方法类似，其具体的实施可以参考图13的方法，内容相同之处不再重复说明。如图23所示，本申请实施例的群组切换装置2300包括：
第一发送单元2301，其向源Donor设备发送测量报告；
第一接收单元2302，其接收所述源Donor设备发送的RRC重配置消息；
处理单元2303，其与目标Donor设备建立新F1连接；
第二接收单元2304，其接收所述源Donor设备通过旧F1连接发送的针对所述迁移IAB节点服务的子IAB节点或UE的RRC重配置消息；
第二发送单元2305，其将所述RRC重配置消息发送给所述子IAB节点或所述UE；
第三发送单元2306，其向所述目标Donor设备发送RRC重配置完成消息；
第四发送单元2307，其向所述目标Donor设备转发所述子IAB节点或所述UE发送的RRC重配置完成消息。
图24是本申请实施例的群组切换装置的一个示意图，该装置解决问题的原理与第二方面的实施例的图14的方法类似，其具体的实施可以参考图14的方法，内容相 同之处不再重复说明。如图24所示，本申请实施例的群组切换装置2400包括：
第一发送单元2401，其向源Donor设备发送测量报告；
第一接收单元2402，其接收所述源Donor设备发送的RRC重配置消息；
处理单元2403，其与目标Donor设备建立新F1连接；
第二接收单元2404，其接收所述目标Donor设备通过所述新F1连接发送的针对所述迁移IAB节点服务的子IAB节点或UE的RRC重配置消息；
第二发送单元2405，其将所述RRC重配置消息发送给所述子IAB节点或所述UE；
第三发送单元2406，其向所述目标Donor设备发送RRC重配置完成消息；
第四发送单元2407：其向所述目标Donor设备转发所述子IAB节点或所述UE发送的RRC重配置完成消息。
在一些实施例中，处理单元2303/2403与目标Donor设备建立新F1连接，包括：
向所述目标Donor发送F1建立请求消息，请求建立与所述目标Donor设备之间的新F1连接；
接收所述目标Donor设备发送的F1建立响应消息，由此建立起与所述目标Donor设备之间的新F1连接。
在一些实施例中，在所述新F1连接建立完成后，处理单元2303/2403保持与所述源Donor设备之间的旧F1连接，并且在以下条件之一满足的情况下释放与所述源Donor设备之间的旧F1连接：
向所述迁移IAB节点服务的子IAB节点或UE发送完RRC重配置消息后；
收到所述迁移IAB节点服务的子IAB节点或UE发送的RRC重配置完成消息后；
与所述目标Donor设备之间的新F1连接建立完成的预定时间之后。
在一些实施例中，在所述新F1连接完成建立后，处理单元2303/2403向所述源Donor设备发送F1释放请求消息，释放与所述源Donor设备之间的旧F1连接。
在一些实施例中，在所述新F1连接建立完成之后，处理单元2303/2403将所述子IAB节点或所述UE的所述RRC重配置消息发送给所述子IAB节点或所述UE；或者，在所述新F1连接建立完成之后，向所述目标Donor设备转发所述子IAB节点或所述UE发送的RRC重配置完成消息。
在一些实施例中，如图23和图24所示，所述装置2300/2400还包括：
第三接收单元2308/2408，其在第三发送单元2306/2406向所述目标Donor设备发送所述RRC重配置完成消息后，接收所述目标Donor设备配置的回传RLC信道映射和BAP路由配置。
在一些实施例中，所述针对迁移IAB节点的RRC重配置消息包括以下之一：
切换到所述目标Donor设备使用的默认上行回传RLC信道标识；
切换到所述目标Donor设备使用的默认BAP路由标识；
切换到所述目标Donor设备使用的BAP地址；
切换到所述目标Donor设备使用的传输层地址；以及
切换到所述目标Donor设备使用的安全密钥配置。
在一些实施例中，所述RRC重配置消息还包括：切换到所述目标Donor设备使用的回传RLC信道映射和BAP路由配置。
在一些实施例中，在第三发送单元2306/2406向所述目标Donor设备发送所述RRC重配置完成消息后，处理单元2303/2403可以应用所述回传RLC信道映射和BAP路由配置。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的资源分配装置2300/2400还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图23和图24中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
根据本申请实施例，如前所述，可减小在IAB节点移动过程中的业务通信中断时间。
第六方面的实施例
本申请实施例提供一种群组切换装置。
图25是本申请实施例的群组切换装置的一个示意图，该装置例如可以是IAB网络中的迁移IAB节点服务的子IAB节点，也可以是配置于该子IAB节点的某个或某些部件或者组件，该装置解决问题的原理与第三方面的实施例的图15的方法类似， 其具体的实施可以参考图15的方法，内容相同之处不再重复说明。如图25所示，本申请实施例的群组切换装置2500包括：
第一接收单元2501，其接收源Donor设备或目标Donor设备发送的RRC重配置消息；
处理单元2502，其与目标Donor设备之间建立新F1连接；
第一发送单元2503，其向所述目标Donor设备发送RRC重配置完成消息。
在一些实施例中，处理单元2502与目标Donor设备之间建立新F1连接，包括：
向所述目标Donor发送F1建立请求消息，请求建立与所述目标Donor设备之间的F1连接；
接收所述目标Donor设备发送的F1建立响应消息，由此建立起与所述目标Donor设备之间的F1连接。
在一些实施例中，在所述新F1连接建立起来之后，处理单元2502保持与所述源Donor设备之间的旧F1连接，并且在以下条件之一满足的情况下释放与所述源Donor设备之间的旧F1连接：
向所述子IAB节点服务的孙IAB节点或UE发送完RRC重配置消息后；
收到所述子IAB节点服务的孙IAB节点或UE发送的RRC重配置完成消息后；
与所述目标Donor设备之间的新F1连接建立后的预定时间之后。
在一些实施例中，在所述新F1连接建立起来之后，处理单元2502向所述源Donor设备发送F1释放请求消息，释放与所述源Donor设备之间的旧F1连接。
在一些实施例中，如图25所示，所述装置2500还包括：
第二接收单元2504，其接收所述目标Donor设备通过所述新F1连接发送的F1AP消息，其中，所述F1AP消息包含针对所述子IAB节点服务的孙IAB节点或UE的RRC重配置消息；
第二发送单元2505，其将所述RRC重配置消息发送给所述孙IAB节点或UE。
在一些实施例中，如图25所示，所述装置2500还包括：
第三接收单元2506，其在第一发送单元2503向所述目标Donor设备发送所述RRC重配置完成消息后，接收所述目标Donor配置的BAP路由配置。
在一些实施例中，如图25所示，所述装置2500还包括：
第四接收单元2507，其接收所述源Donor设备通过与所述子IAB节点之间的旧 F1连接发送的F1AP消息，其中，所述F1AP消息包含针对所述子IAB节点服务的孙IAB节点或UE的RRC重配置消息；
第三发送单元2508，其将所述RRC重配置消息发送给所述孙IAB节点或UE，并向所述目标Donor设备转发所述孙IAB节点或所述UE发送的RRC重配置完成消息。
在一些实施例中，在所述新F1连接建立完成之后，所述第三发送单元2508将所述孙IAB节点或UE的RRC重配置消息发送给服务的孙IAB节点或UE，或者在新F1连接建立完成之后，将服务的孙IAB节点或UE的RRC重配置完成消息发送给所述目标Donor设备。
在一些实施例中，上述针对子IAB节点的RRC重配置消息包括以下之一：
切换到所述目标Donor设备使用的默认BAP路由标识；
切换到所述目标Donor设备使用的BAP地址；
切换到所述目标Donor设备使用的传输层地址；以及
切换到所述目标Donor设备使用的安全密钥配置。
在一些实施例中，所述RRC重配置消息还包括：切换到所述目标Donor设备使用的BAP路由配置。
在一些实施例中，在确定所述迁移IAB节点完成切换到所述目标Donor设备后，并且在向所述目标Donor设备发送所述RRC重配置完成消息后，处理单元2502应用所述BAP路由配置。
图26是本申请实施例的群组切换装置的一个示意图，该装置例如可以是IAB网络中的迁移IAB节点服务的UE，也可以是配置于该UE的某个或某些部件或者组件，该装置解决问题的原理与第三方面的实施例的图16的方法类似，其具体的实施可以参考图16的方法，内容相同之处不再重复说明。如图26所示，本申请实施例的群组切换装置2600包括：
接收单元2601，其接收源Donor设备或目标Donor设备发送的RRC重配置消息；
发送单元2602，其向所述目标Donor设备发送RRC重配置完成消息。
在一些实施例中，所述RRC重配置消息包括：切换到所述目标Donor设备使用的安全密钥配置。
根据本申请实施例，如前所述，可减小在IAB节点移动过程中的业务通信中断 时间。
第七方面的实施例
本申请实施例提供了一种通信系统，图27是该通信系统2700的示意图，如图27所示，该通信系统2700包括Donor设备2701和2702、IAB节点2703和2704，以及终端设备2705，其中，IAB节点2703为迁移IAB节点，Donor设备2701作为IAB节点2703的源Donor设备，Donor设备2702作为IAB节点2703的目标Donor设备，IAB节点2704和终端设备2705由IAB节点2703提供服务，即，IAB节点2704是IAB节点2703的子IAB节点。
为简单起见，图27仅以两个Donro设备、两个IAB节点、一个终端设备为例进行说明，但本申请实施例不限于此。关于Donro设备、IAB节点以及该终端设备的网络架构可以参考相关技术，此处省略说明。
在一些实施例中，Donor设备2701被配置为执行图8和图10所示的方法，可以包含图19和图21的装置。在一些实施例中，Donor设备2702被配置为执行图9和图11所示的方法，可以包含图20和图22的装置。在一些实施例中，IAB节点2703被配置为执行图13和图14所示的方法，可以包括图23和图23的装置。在一些实施例中，IAB节点2704被配置为执行图15所示的方法，可以包括图25的装置。在一些实施例中，终端设备2705被配置为执行图16所示的方法，可以包括图26的装置。关于Donor设备2701和2702、IAB节点2703和2704，以及终端设备2705的相关内容请参见第一方面至第六方面的实施例，此处省略说明。
本申请实施例还提供一种IAB节点。
图28是本申请实施例的IAB节点的示意图。如图28所示，该IAB节点2800可以包括处理器2801和存储器2802；存储器2802存储有数据和程序，并耦合到处理器2801。值得注意的是，该图是示例性的；还可以使用其它类型的结构，来补充或代替该结构，以实现电信功能或其它功能。
例如，处理器2801可以被配置为执行程序而实现如第二方面的图13或图14的实施例或第三方面的图15的实施例所述的方法。
如图28所示，该IAB节点2800还可以包括：通信模块2803、输入单元2804、显示器2805、电源2806。其中，上述部件的功能与现有技术类似，此处不再赘述。 值得注意的是，IAB节点2800也并不是必须要包括图28中所示的所有部件，上述部件并不是必需的；此外，IAB节点2800还可以包括图28中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种Donor设备。
图29是本申请实施例的Donor设备的示意图。如图29所示，Donor设备2900可以包括：处理器(例如中央处理器CPU)2901和存储器2902；存储器2902耦合到处理器2901。其中该存储器2902可存储各种数据；此外还存储信息处理的程序，并且在中央处理器2901的控制下执行该程序。
例如，处理器2901可以被配置为执行程序而实现如第一方面的图8或图9或图10或图11的实施例所述的方法。
此外，如图29所示，Donor设备2900还可以包括：收发机2903和天线2904等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，Donor设备2900也并不是必须要包括图29中所示的所有部件；此外，Donor设备2900还可以包括图29中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种终端设备。
图30是本申请实施例的终端设备的示意图。如图30所示，该终端设备2800可以包括处理器2801和存储器3002；存储器3002存储有数据和程序，并耦合到处理器3001。值得注意的是，该图是示例性的；还可以使用其它类型的结构，来补充或代替该结构，以实现电信功能或其它功能。
例如，处理器3001可以被配置为执行程序而实现如第三方面的图16的实施例所述的方法。
如图30所示，该终端设备3000还可以包括：通信模块3003、输入单元3004、显示器3005、电源3006。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备3000也并不是必须要包括图30中所示的所有部件，上述部件并不是必需的；此外，终端设备3000还可以包括图30中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机可读程序，其中当在IAB节点中执行所述程序时，所述程序使得计算机在所述IAB节点中执行第二方面或第三方面的图15的实施例所述的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在IAB节点中执行第二方面或第三方面的图15的实施例所述的方法。
本申请实施例还提供一种计算机可读程序，其中当在Donor设备中执行所述程序时，所述程序使得计算机在所述Donor设备中执行第一方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在Donor设备中执行第一方面的实施例所述的方法。
本申请实施例还提供一种计算机可读程序，其中当在终端设备中执行所述程序时，所述程序使得计算机在所述终端设备中执行第三方面的图16的实施例所述的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在Donor设备中执行第三方面的图16的实施例所述的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于本实施例公开的上述实施方式，还公开了如下的附记：
1.一种群组切换方法，所述方法应用于源Donor设备，其中，所述方法包括：
接收迁移IAB节点发送的测量报告；
向目标Donor设备发送第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
接收所述目标Donor设备发送的第一响应消息，所述第一响应消息包含针对所述迁移IAB节点及其服务的子IAB节点或UE的RRC重配置消息；
向所述迁移IAB节点及其服务的子IAB节点或UE发送所述RRC重配置消息。
2.一种群组切换方法，所述方法应用于源Donor设备，其中，所述方法包括：
接收迁移IAB节点发送的测量报告；
向目标Donor设备发送第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
接收所述目标Donor设备发送的第一响应消息，所述第一响应消息包含针对所述迁移IAB节点的RRC重配置消息；
向所述迁移IAB节点发送所述RRC重配置消息。
3.一种群组切换方法，所述方法应用于目标Donor设备，其中，所述方法包括：
接收源Donor设备发送的第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
向所述源Donor设备发送第一响应消息，所述第一响应消息包含针对所述迁移IAB节点及其服务的子IAB节点或UE的RRC重配置消息；
与所述迁移IAB节点建立新F1连接；
接收所述迁移IAB节点及其服务的子IAB节点或UE发送的RRC重配置完成消息。
4.一种群组切换方法，所述方法应用于目标Donor设备，其中，所述方法包括：
接收源Donor设备发送的第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
向所述源Donor设备发送第一响应消息，所述第一响应消息包含针对所述迁移IAB节点的RRC重配置消息；
与所述迁移IAB节点建立新F1连接；
通过所述新F1连接向所述迁移IAB节点服务的子IAB节点或UE发送RRC重配置消息；
接收所述迁移IAB节点及其服务的子IAB节点或UE发送的RRC重配置完成消息。
5.根据附记1至4任一项所述的方法，其中，
所述迁移IAB节点的上下文信息包括：所述迁移IAB节点的IAB-DU上下文和IAB-MT上下文；
所述子IAB节点的上下文信息包括：所述子IAB节点的IAB-DU上下文和IAB-MT上下文。
6.根据附记5所述的方法，其中，所述迁移IAB节点的IAB-DU上下文包括：所述迁移IAB节点的IAB-DU在所述源Donor设备下的服务小区信息。
7.根据附记6所述的方法，其中，所述服务小区信息包括以下至少之一：
新无线小区全球标识符(Cell Global Identifier，NR CGI)；
新无线物理小区标识(Physical Cell ID，NR PCI)；
所述IAB-DU服务的公共陆地移动网(Public Land Mobile Network，PLMN)；
上下行传输频点和带宽。
8.根据附记5所述的方法，其中，所述迁移IAB节点的IAB-MT上下文包括BAP配置信息；其中，所述BAP配置信息包括所述源Donor设备为所述IAB节点分 配的BAP地址、传输层(IP)地址、默认上行回传RLC信道标识和/或默认上行BAP路由标识；其中，所述默认上行BAP路由标识是指默认目的BAP地址和默认路径标识。
9.根据附记1至4任一项所述的方法，其中，所述第一切换请求消息还包含回传信息。
10.根据附记9所述的方法，其中，所述回传信息包括以下至少之一：
上一跳节点的BAP地址和入口回传RLC信道的标识、与下一跳节点的BAP地址和出口回传RLC信道的标识之间的对应关系；
源Donor设备为迁移IAB节点或子IAB节点配置的BAP路由标识和下一跳节点的BAP地址的对应关系。
11.根据附记9所述的方法，其中，所述回传信息包括以下至少之一：
所述迁移IAB节点或所述子IAB节点所服务的UE的DRB使用的BAP路由标识、下一跳节点的BAP地址以及回传RLC信道标识；以及，
F1控制面数据或非F1数据使用的BAP路由标识、下一跳节点的BAP地址以及回传RLC信道标识。
12.根据附记10或11所述的方法，其中，所述BAP路由标识包括目的BAP地址和路径标识。
13.根据附记1至4任一项所述的方法，其中，所述第一切换请求消息还包含拓扑信息，所述拓扑信息包括所述迁移IAB节点与其服务的子IAB节点或UE之间的拓扑关系，或者包括所述子IAB节点与其服务的孙IAB节点或UE之间的拓扑关系。
14.根据附记1至4任一项所述的方法，其中，所述第一切换请求消息还包括：地址请求信息，所述地址请求信息用于请求所述目标Donor设备为所述迁移IAB节点或所述子IAB节点分配新的传输层(IP)地址或BAP地址。
15.根据附记3或4所述的方法，其中，与所述迁移IAB节点建立新F1连接，包括：
接收所述迁移IAB节点发送的F1建立请求消息；
向所述迁移IAB节点发送F1建立响应消息。
16.根据附记3或4所述的方法，其中，所述方法还包括：
与所述子IAB节点之间建立新F1连接。
17.根据附记3或4所述的方法，其中，所述方法还包括：
在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息后，为所述迁移IAB节点配置回传RLC信道映射和BAP路由配置。
18.根据附记3所述的方法，其中，所述方法还包括：
在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息后，或与所述迁移IAB节点建立新F1连接后，向所述源Donor设备发送第一指示消息；其中，所述第一指示消息用于指示所述源Donor设备向所述子IAB节点或所述UE发送RRC重配置消息。
19.根据附记1至4任一项所述的方法，其中，所述迁移IAB节点的上下文信息和所述子IAB节点或所述UE的上下文信息包含于相同的Xn消息或不同的Xn消息。
20.根据附记19所述的方法，其中，所述方法还包括：
在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息后，或与所述迁移IAB节点建立新F1连接后，向所述源Donor设备发送第二指示消息；其中，所述第二指示消息用于指示所述源Donor设备向所述目标Donor设备发送包含所述子IAB节点或所述UE的上下文的Xn消息。
21.根据附记1或3所述的方法，其中，针对所述迁移IAB节点的RRC重配置消息和针对所述子IAB节点或所述UE的RRC重配置消息包含于相同的Xn消息或不同的Xn消息。
22.根据附记21所述的方法，其中，所述方法还包括：
在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息后，或与所述迁移IAB节点建立新F1连接后，向所述源Donor设备发送包含针对所述子IAB节点或所述UE的RRC重配置消息的Xn消息。
23.根据附记3或4所述的方法，其中，所述方法还包括：
在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息以及所述子IAB节点发送的RRC重配置完成消息后，为所述子IAB节点配置BAP路由配置。
24.根据附记1至4任一项所述的方法，其中，针对所述迁移IAB节点的RRC重配置消息包括以下至少之一：
切换到所述目标Donor设备使用的默认上行回传RLC信道标识；
切换到所述目标Donor设备使用的默认BAP路由标识；
切换到所述目标Donor设备使用的BAP地址；
切换到所述目标Donor设备使用的传输层地址；以及
切换到所述目标Donor设备使用的安全密钥配置。
25.根据附记24所述的方法，其中，针对所述迁移IAB节点的RRC重配置消息还包括：切换到所述目标Donor设备使用的回传RLC信道映射和BAP路由配置。
26.根据附记1、3或4任一项所述的方法，其中，针对所述子IAB节点的RRC重配置消息包括以下至少之一：
切换到目标Donor设备使用的默认BAP路由标识；
切换到所述目标Donor设备使用的BAP地址；
切换到所述目标Donor设备使用的传输层地址；以及
切换到所述目标Donor设备使用的安全密钥配置。
27.根据附记26所述的方法，其中，所述针对所述子IAB节点的RRC重配置消息还包括：切换到所述目标Donor设备使用的BAP路由配置。
28.根据附记1或3或4所述的方法，其中，针对所述UE的RRC重配置消息包括：
切换到所述目标Donor设备使用的安全密钥配置。
29.一种群组切换方法，应用于迁移IAB节点，其中，所述方法包括：
向源Donor设备发送测量报告；
接收所述源Donor设备发送的RRC重配置消息；
与目标Donor设备建立新F1连接；
接收所述源Donor设备通过旧F1连接发送的针对所述迁移IAB节点服务的子IAB节点或UE的RRC重配置消息；
将所述RRC重配置消息发送给所述子IAB节点或所述UE；向所述目标Donor设备发送RRC重配置完成消息；
向所述目标Donor设备转发所述子IAB节点或所述UE发送的RRC重配置完成消息。
30.一种群组切换方法，应用于迁移IAB节点，其中，所述方法包括：
向源Donor设备发送测量报告；
接收所述源Donor设备发送的RRC重配置消息；
与目标Donor设备建立新F1连接；
接收所述目标Donor设备通过所述新F1连接发送的针对所述迁移IAB节点服务的子IAB节点或UE的RRC重配置消息；
将所述RRC重配置消息发送给所述子IAB节点或所述UE；
向所述目标Donor设备发送RRC重配置完成消息；
向所述目标Donor设备转发所述子IAB节点或所述UE发送的RRC重配置完成消息。
31.根据附记29或30所述的方法，其中，与目标Donor设备建立新F1连接，包括：
向所述目标Donor发送F1建立请求消息，请求建立与所述目标Donor设备之间的新F1连接；
接收所述目标Donor设备发送的F1建立响应消息，由此建立起与所述目标Donor设备之间的新F1连接。
32.根据附记29或30所述的方法，其中，在所述新F1连接建立完成后，保持与所述源Donor设备之间的旧F1连接，并且在以下条件之一满足的情况下释放与所述源Donor设备之间的旧F1连接：
向所述迁移IAB节点服务的子IAB节点或UE发送完RRC重配置消息后；
收到所述迁移IAB节点服务的子IAB节点或UE发送的RRC重配置完成消息后；
与所述目标Donor设备之间的新F1连接建立完成的预定时间之后。
33.根据附记29或30所述的方法，其中，在所述新F1连接建立完成后，向所述源Donor设备发送F1释放请求消息，释放与所述源Donor设备之间的旧F1连接。
34.根据附记29所述的方法，其中，在所述新F1连接建立完成之后，将所述子IAB节点或所述UE的RRC重配置消息发送给所述子IAB节点或所述UE；或者，在所述新F1连接建立完成之后，向所述目标Donor设备转发所述子IAB节点或所述UE发送的RRC重配置完成消息。
35.根据附记29或30所述的方法，其中，所述方法还包括：
在向所述目标Donor设备发送所述RRC重配置完成消息后，接收所述目标Donor 设备配置的回传RLC信道映射和BAP路由配置。
36.根据附记29或30所述的方法，其中，所述针对迁移IAB节点的RRC重配置消息包括以下之一：
切换到所述目标Donor设备使用的默认上行回传RLC信道标识；
切换到所述目标Donor设备使用的默认BAP路由标识；
切换到所述目标Donor设备使用的BAP地址；
切换到所述目标Donor设备使用的传输层地址；以及
切换到所述目标Donor设备使用的安全密钥配置。
37.根据附记36所述的方法，其中，所述RRC重配置消息还包括：切换到所述目标Donor设备使用的回传RLC信道映射和BAP路由配置。
38.根据附记37所述的方法，所述方法还包括：
在向所述目标Donor设备发送所述RRC重配置完成消息后，应用所述回传RLC信道映射和BAP路由配置。
39.一种群组切换方法，应用于迁移IAB节点服务的子IAB节点，其中，所述方法包括：
接收源Donor设备或目标Donor设备发送的RRC重配置消息；
与目标Donor设备之间建立新F1连接；
向所述目标Donor设备发送RRC重配置完成消息。
40.根据附记39所述的方法，与目标Donor设备之间建立新F1连接，包括：
向所述目标Donor发送F1建立请求消息，请求建立与所述目标Donor设备之间的F1连接；
接收所述目标Donor设备发送的F1建立响应消息，由此建立起与所述目标Donor设备之间的F1连接。
41.根据附记39所述的方法，其中，在所述新F1连接建立起来之后，保持与所述源Donor设备之间的旧F1连接，并且在以下条件之一满足的情况下释放与所述源Donor设备之间的旧F1连接：
向所述子IAB节点服务的孙IAB节点或UE发送完RRC重配置消息后；
收到所述子IAB节点服务的孙IAB节点或UE发送的RRC重配置完成消息后；
与所述目标Donor设备之间的新F1连接建立后的预定时间之后。
42.根据附记39所述的方法，其中，在所述新F1连接建立起来之后，向所述源Donor设备发送F1释放请求消息，释放与所述源Donor设备之间的旧F1连接。
43.根据附记39所述的方法，其中，所述方法还包括：
接收所述目标Donor设备通过所述新F1连接发送的F1AP消息，其中，所述F1AP消息包含针对所述子IAB节点服务的孙IAB节点或UE的RRC重配置消息；
将所述RRC重配置消息发送给所述孙IAB节点或UE。
44.根据附记39所述的方法，其中，所述方法还包括：
在向所述目标Donor设备发送所述RRC重配置完成消息后，接收所述目标Donor配置的BAP路由配置。
45.根据附记39所述的方法，其中，所述方法还包括：
接收所述源Donor设备通过与所述子IAB节点之间的旧F1连接发送的F1AP消息，其中，所述F1AP消息包含针对所述子IAB节点服务的孙IAB节点或UE的RRC重配置消息；
将所述RRC重配置消息发送给所述孙IAB节点或UE；
向所述目标Donor设备转发所述孙IAB节点或所述UE发送的RRC重配置完成消息。
46.根据附记45所述的方法，其中，在所述新F1连接建立完成之后，将所述孙IAB节点或UE的RRC重配置消息发送给服务的所述孙IAB节点或UE；或者，在所述新F1连接建立完成之后，向所述目标Donor转发所述孙IAB节点或所述UE发送的RRC重配置完成消息。
47.根据附记39所述的方法，其中，所述针对子IAB节点的RRC重配置消息包括以下之一：
切换到所述目标Donor设备使用的默认BAP路由标识；
切换到所述目标Donor设备使用的BAP地址；
切换到所述目标Donor设备使用的传输层地址；以及
切换到所述目标Donor设备使用的安全密钥配置。
48.根据附记47所述的方法，其中，所述RRC重配置消息还包括：切换到所述目标Donor设备使用的BAP路由配置。
49.根据附记48所述的方法，所述方法还包括：
确定所述迁移IAB节点完成切换到所述目标Donor设备后，并且在向所述目标Donor设备发送所述RRC重配置完成消息后，应用所述BAP路由配置。
50.一种群组切换方法，应用于迁移IAB节点服务的终端设备，其中，所述方法包括：
接收源Donor设备或目标Donor设备发送的RRC重配置消息；
向所述目标Donor设备发送RRC重配置完成消息。
51.根据附记50所述的方法，其中，所述RRC重配置消息包括：切换到所述目标Donor设备使用的安全密钥配置。
52.一种Donor设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记1至28任一项所述的方法。
53.一种IAB节点，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记29至49任一项所述的方法。
54.一种终端设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记50或51所述的方法。
55.一种通信系统，包括Donor设备、IAB节点以及终端设备，其中，所述Donor设备被配置为执行附记1至28任一项所述的方法，所述IAB节点被配置为执行附记29至49任一项所述的方法，所述终端设备被配置为执行附记50或51所述的方法。

Claims (20)

  1. 一种群组切换装置，所述装置配置于源Donor设备，其中，所述装置包括：
    第一接收单元，其接收迁移IAB节点发送的测量报告；
    第一发送单元，其向目标Donor设备发送第一切换请求消息，所述第一切换请求消息包含所述迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
    第二接收单元，其接收所述目标Donor设备发送的第一响应消息，所述第一响应消息包含针对所述迁移IAB节点及其服务的子IAB节点或UE的RRC重配置消息；
    第二发送单元，其向所述迁移IAB节点及其服务的子IAB节点或UE发送所述RRC重配置消息。
  2. 根据权利要求1所述的装置，其中，所述第一切换请求消息还包含回传信息。
  3. 根据权利要求2所述的装置，其中，所述回传信息包括以下至少之一：
    上一跳节点的BAP地址和入口回传RLC信道的标识、与下一跳节点的BAP地址和出口回传RLC信道的标识之间的对应关系；
    源Donor设备为迁移IAB节点或子IAB节点配置的BAP路由标识和下一跳节点的BAP地址的对应关系。
  4. 根据权利要求2所述的装置，其中，所述回传信息包括以下至少之一：
    所述迁移IAB节点或所述子IAB节点所服务的UE的DRB使用的BAP路由标识、下一跳节点的BAP地址以及回传RLC信道标识；以及，
    F1控制面数据或非F1数据使用的BAP路由标识、下一跳节点的BAP地址以及回传RLC信道标识。
  5. 根据权利要求1所述的装置，其中，所述第一切换请求消息还包含拓扑信息，所述拓扑信息包括所述迁移IAB节点与其服务的子IAB节点或UE之间的拓扑关系，或者包括所述子IAB节点与其服务的孙IAB节点或UE之间的拓扑关系。
  6. 根据权利要求1所述的装置，其中，所述迁移IAB节点的上下文信息和所述子IAB节点或所述UE的上下文信息包含于相同的Xn消息或不同的Xn消息。
  7. 一种群组切换装置，所述装置配置于目标Donor设备，其中，所述装置包括：
    第一接收单元，其接收源Donor设备发送的第一切换请求消息，所述第一切换请求消息包含迁移IAB节点及其服务的子IAB节点或UE的上下文信息；
    第一发送单元，其向所述源Donor设备发送第一响应消息，所述第一响应消息包含针对所述迁移IAB节点及其服务的子IAB节点或UE的RRC重配置消息；
    第一处理单元，其与所述迁移IAB节点建立新F1连接；
    第二接收单元，其接收所述迁移IAB节点及其服务的子IAB节点或UE发送的RRC重配置完成消息。
  8. 根据权利要求7所述的装置，其中，所述装置还包括：
    第一配置单元，其在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息后，为所述迁移IAB节点配置回传RLC信道映射和BAP路由配置。
  9. 根据权利要求7所述的装置，其中，针对所述迁移IAB节点的RRC重配置消息和针对所述子IAB节点或所述UE的RRC重配置消息包含于相同的Xn消息或不同的Xn消息。
  10. 根据权利要求9所述的装置，其中，所述装置还包括：
    第四发送单元，其在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息后，或与所述迁移IAB节点建立新F1连接后，向所述源Donor设备发送包含针对所述子IAB节点或所述UE的RRC重配置消息的Xn消息。
  11. 根据权利要求7所述的装置，其中，所述装置还包括：
    第二配置单元，其在所述目标Donor设备接收到所述迁移IAB节点发送的RRC重配置完成消息以及所述子IAB节点发送的RRC重配置完成消息后，为所述子IAB节点配置BAP路由配置。
  12. 根据权利要求7所述的装置，其中，针对所述迁移IAB节点的RRC重配置消息包括以下至少之一：
    切换到所述目标Donor设备使用的默认上行回传RLC信道标识；
    切换到所述目标Donor设备使用的默认BAP路由标识；
    切换到所述目标Donor设备使用的BAP地址；
    切换到所述目标Donor设备使用的传输层地址；以及
    切换到所述目标Donor设备使用的安全密钥配置。
  13. 根据权利要求12所述的装置，其中，针对所述迁移IAB节点的RRC重配置消息还包括：切换到所述目标Donor设备使用的回传RLC信道映射和BAP路由配置。
  14. 根据权利要求7所述的装置，其中，针对所述子IAB节点的RRC重配置消息包括以下至少之一：
    切换到目标Donor设备使用的默认BAP路由标识；
    切换到所述目标Donor设备使用的BAP地址；
    切换到所述目标Donor设备使用的传输层地址；以及
    切换到所述目标Donor设备使用的安全密钥配置。
  15. 根据权利要求14所述的装置，其中，所述针对所述子IAB节点的RRC重配置消息还包括：切换到所述目标Donor设备使用的BAP路由配置。
  16. 一种群组切换装置，配置于迁移IAB节点，其中，所述装置包括：
    第一发送单元，其向源Donor设备发送测量报告；
    第一接收单元，其接收所述源Donor设备发送的RRC重配置消息；
    处理单元，其与目标Donor设备建立新F1连接；
    第二接收单元，其接收所述源Donor设备通过旧F1连接发送的针对所述迁移IAB节点服务的子IAB节点或UE的RRC重配置消息；
    第二发送单元，其将所述RRC重配置消息发送给所述子IAB节点或所述UE；向所述目标Donor设备发送RRC重配置完成消息；
    第三发送单元，其向所述目标Donor设备转发所述子IAB节点或所述UE发送的RRC重配置完成消息。
  17. 根据权利要求16所述的装置，其中，在所述新F1连接建立完成后，保持与所述源Donor设备之间的旧F1连接，并且在以下条件之一满足的情况下释放与所述源Donor设备之间的旧F1连接：
    向所述迁移IAB节点服务的子IAB节点或UE发送完RRC重配置消息后；
    收到所述迁移IAB节点服务的子IAB节点或UE发送的RRC重配置完成消息后；
    与所述目标Donor设备之间的新F1连接建立完成的预定时间之后。
  18. 根据权利要求16所述的装置，其中，在所述新F1连接建立完成后，所述处理单元向所述源Donor设备发送F1释放请求消息，释放与所述源Donor设备之间的旧F1连接。
  19. 根据权利要求16所述的装置，其中，所述针对迁移IAB节点的RRC重配置消息包括以下之一：
    切换到所述目标Donor设备使用的默认上行回传RLC信道标识；
    切换到所述目标Donor设备使用的默认BAP路由标识；
    切换到所述目标Donor设备使用的BAP地址；
    切换到所述目标Donor设备使用的传输层地址；以及
    切换到所述目标Donor设备使用的安全密钥配置；
    其中，所述RRC重配置消息还包括：切换到所述目标Donor设备使用的回传RLC信道映射和BAP路由配置。
  20. 根据权利要求19所述的装置，其中，在所述第三发送单元向所述目标Donor设备发送所述RRC重配置完成消息后，应用所述回传RLC信道映射和BAP路由配置。
PCT/CN2020/123024 2020-10-22 2020-10-22 群组切换的方法、装置和系统 WO2022082690A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN202080105466.1A CN116235543A (zh) 2020-10-22 2020-10-22 群组切换的方法、装置和系统
EP20958272.5A EP4236451A4 (en) 2020-10-22 2020-10-22 GROUP SWITCHING METHOD, APPARATUS AND SYSTEM
PCT/CN2020/123024 WO2022082690A1 (zh) 2020-10-22 2020-10-22 群组切换的方法、装置和系统
JP2023522551A JP2023545809A (ja) 2020-10-22 2020-10-22 グループ移行方法、装置及びシステム
US18/133,746 US20230308975A1 (en) 2020-10-22 2023-04-12 Group migration method and apparatus and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/123024 WO2022082690A1 (zh) 2020-10-22 2020-10-22 群组切换的方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/133,746 Continuation US20230308975A1 (en) 2020-10-22 2023-04-12 Group migration method and apparatus and system

Publications (1)

Publication Number Publication Date
WO2022082690A1 true WO2022082690A1 (zh) 2022-04-28

Family

ID=81291165

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123024 WO2022082690A1 (zh) 2020-10-22 2020-10-22 群组切换的方法、装置和系统

Country Status (5)

Country Link
US (1) US20230308975A1 (zh)
EP (1) EP4236451A4 (zh)
JP (1) JP2023545809A (zh)
CN (1) CN116235543A (zh)
WO (1) WO2022082690A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019246446A1 (en) * 2018-06-21 2019-12-26 Google Llc Maintaining communication and signaling interfaces through a donor base station handover
CN110636570A (zh) * 2018-06-25 2019-12-31 中兴通讯股份有限公司 Iab网络中iab节点信息的处理方法及装置
CN110830979A (zh) * 2018-08-09 2020-02-21 中兴通讯股份有限公司 信息传输方法及装置
CN111093286A (zh) * 2019-08-15 2020-05-01 中兴通讯股份有限公司 连接建立方法、装置、集合接入回传节点及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019246446A1 (en) * 2018-06-21 2019-12-26 Google Llc Maintaining communication and signaling interfaces through a donor base station handover
CN110636570A (zh) * 2018-06-25 2019-12-31 中兴通讯股份有限公司 Iab网络中iab节点信息的处理方法及装置
CN110830979A (zh) * 2018-08-09 2020-02-21 中兴通讯股份有限公司 信息传输方法及装置
CN111093286A (zh) * 2019-08-15 2020-05-01 中兴通讯股份有限公司 连接建立方法、装置、集合接入回传节点及存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Remaining IP transport issues for IAB", 3GPP DRAFT; R3-200417, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Electronic Meeting; 20200224 - 20200306, 14 February 2020 (2020-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051854092 *
See also references of EP4236451A4 *

Also Published As

Publication number Publication date
US20230308975A1 (en) 2023-09-28
JP2023545809A (ja) 2023-10-31
CN116235543A (zh) 2023-06-06
EP4236451A4 (en) 2023-12-06
EP4236451A1 (en) 2023-08-30

Similar Documents

Publication Publication Date Title
US11546811B2 (en) Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
ES2886519T3 (es) Procedimientos y aparatos para realizar un traspaso para un UE
US9955513B2 (en) Radio communication system and control method
WO2016161785A1 (zh) 跨MeNB切换方法、装置及基站
US20230254729A1 (en) Migration method and apparatus for iab-node
WO2024031289A1 (zh) 网络节点的通信方法、移动节点的通信方法、移动节点和宿主设备
WO2022082690A1 (zh) 群组切换的方法、装置和系统
JP2024502623A (ja) Ｉａｂの通信方法及び装置
WO2022233008A1 (zh) 消息发送方法、装置和系统
WO2023197184A1 (zh) Iab宿主设备以及传输地址配置方法
WO2022151298A1 (zh) 群组迁移方法、装置和系统
WO2022205252A1 (zh) 发送和接收信号的方法、装置和通信系统
WO2023010367A1 (zh) 终端设备的转移方法、装置和系统
WO2024026803A1 (zh) 移动节点的配置方法和宿主设备
WO2023010364A1 (zh) 集成的接入和回传的通信装置以及方法
WO2023150975A1 (zh) Iab宿主设备以及传输迁移回退方法
WO2023197185A1 (zh) Iab节点设备、iab宿主设备以及传输地址确定方法
WO2023130232A1 (zh) Iab节点设备、iab宿主设备以及路径迁移方法
WO2023130231A1 (zh) Iab节点设备、iab宿主设备以及拓扑退行方法
WO2024026804A1 (zh) 移动节点的配置方法、移动节点和宿主设备
WO2022205251A1 (zh) 信息收发方法，数据发送方法以及装置
WO2022205485A1 (zh) 信息收发方法以及装置
JP2024517469A (ja) 信号の送受信方法、装置及び通信システム
WO2015042883A1 (zh) 上行业务传输方法、下行业务传输方法和设备

Legal Events

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

Ref document number: 20958272

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023522551

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020958272

Country of ref document: EP

Effective date: 20230522