WO2024092739A1 - Techniques de transfert d'informations dans un système d'accès et de liaison terrestre intégré - Google Patents

Techniques de transfert d'informations dans un système d'accès et de liaison terrestre intégré Download PDF

Info

Publication number
WO2024092739A1
WO2024092739A1 PCT/CN2022/129971 CN2022129971W WO2024092739A1 WO 2024092739 A1 WO2024092739 A1 WO 2024092739A1 CN 2022129971 W CN2022129971 W CN 2022129971W WO 2024092739 A1 WO2024092739 A1 WO 2024092739A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
migration
mobile network
iab
donor
Prior art date
Application number
PCT/CN2022/129971
Other languages
English (en)
Inventor
Ying Huang
Lin Chen
Original Assignee
Zte Corporation
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 Zte Corporation filed Critical Zte Corporation
Priority to PCT/CN2022/129971 priority Critical patent/WO2024092739A1/fr
Publication of WO2024092739A1 publication Critical patent/WO2024092739A1/fr

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

Definitions

  • This document is directed generally to digital wireless communications.
  • LTE Long-Term Evolution
  • 3GPP 3rd Generation Partnership Project
  • LTE Advanced LTE-A
  • LTE-A LTE Advanced
  • the 5th generation of wireless system advances the LTE and LTE-A wireless standards and is committed to supporting higher data-rates, large number of connections, ultra-low latency, high reliability and other emerging business needs.
  • Techniques are disclosed for transferring information in an integrated access and backhaul system.
  • a first example wireless communication method includes receiving, by a first network device, a migration type information that indicates a type of handover associated with a handover operation of a mobile network device from the first network device to a second network device, where the first network device receives the migration type information from a third network device.
  • the method further comprises sending a first message comprising the migration type information to the second network device.
  • the method further comprises receiving a second message comprising the migration type information from the second network device; and transmitting, by the first network device and in response to the receiving the second message, the migration type information to the mobile network device.
  • the type of handover indicates a sequence of operations associated with the handover operation for the mobile network device and/or a communication device in communication with the mobile network device.
  • the migration type information includes any one or more of: a partial migration, a full migration, a user equipment (UE) migration first that indicates that the handover operation is performed for the communication device before the handover operation for the mobile network device, a mobile termination (MT) migration first that indicates that the handover operation is first performed for the MT in the mobile network device, a distributed unit (DU) migration first that indicates that the handover operation is first performed for the DU in the mobile network device, a DU migration is executed after MT migration that indicates that the handover operation is performed for the DU in the mobile network device after the handover operation is performed for the MT in the mobile network device, a UE migration is executed after MT migration that indicates that the handover operation is performed for the communication device after the handover operation is performed for the MT in the mobile network device, a DU migration is executed before
  • the first network device includes a first Integrated Access and Backhaul (IAB) donor to which the mobile network device is connected before the handover, where the second network device includes a second IAB donor to which the mobile network device will be connected after the handover, and/or where the third network device includes a third IAB donor that has a connection with the mobile network device.
  • the mobile network device includes a mobile Integrated Access and Backhaul (IAB) device.
  • a second example wireless communication method includes transmitting, by a second logical distributed unit (DU) in a mobile network device, information related to a communication device during a handover of the communication device from a first network device to a second network device, where the second logical DU in the mobile network device transmits the information related to the UE to the second network device, where the communication device is in communication with the mobile network device, where the second logical DU is configured to communicate with the second network device, and where the information related to the communication device includes any one or more of: a cell radio network temporary identifier (C-RNTI) allocated by the mobile network device for the communication device, a first C-RNTI allocated by a first logical DU in the mobile network device for the communication device, a second C-RNTI allocated by the second logical DU in the mobile network device for the communication device.
  • the first network device includes a source base station
  • the second network device includes a target base station.
  • the mobile network device includes an Integrated Access and Backhaul (I
  • a third example wireless communication method includes receiving, by a first network device from a mobile network device, an address associated with the mobile network device; and transmitting the address to a second network device.
  • the address includes a downlink (DL) transport network layer (TNL) address for F1 traffic which goes through a donor DU which connects to the second network device.
  • the first network device includes a target base station to which a mobile termination (MT) in the mobile network device is handed over
  • the second network device includes a source base station from which the MT in the mobile network device is handed over.
  • the mobile network device includes an Integrated Access and Backhaul (IAB) device.
  • IAB Integrated Access and Backhaul
  • the above-described methods are embodied in the form of processor-executable code and stored in a non-transitory computer-readable storage medium.
  • the code included in the computer readable storage medium when executed by a processor, causes the processor to implement the methods described in this patent document.
  • a device that is configured or operable to perform the above-described methods is disclosed.
  • FIG. 1 shows an example scenario where a mobile Integrated Access
  • IAB Backhaul
  • FIGS. 2A-2B show example architectures for IAB systems.
  • FIG. 3 shows parent-node and child-node relationship for an IAB-node.
  • FIGS. 4A-4C show example scenarios of the inter-donor mobility of the mobile IAB node.
  • FIG. 5 shows an exemplary block diagram of a hardware platform that may be a part of a network device or a communication device.
  • FIG. 6 shows an example of wireless communication including a base station (BS) and user equipment (UE) based on some implementations of the disclosed technology.
  • BS base station
  • UE user equipment
  • FIG. 7 shows an exemplary flowchart for receiving a migration type information.
  • FIG. 8 shows an exemplary flowchart for transmitting information related to a communication device.
  • FIG. 9 shows an exemplary flowchart for receiving an address associated with a mobile network device.
  • IAB Integrated Access and Backhaul
  • NR new radio
  • Intra-donor centralized unit (CU) migration procedure includes a scenario where both the source and the target parent node are served by the same IAB-donor-CU.
  • an IAB donor CU may not be changed.
  • inter-donor CU migration includes a scenario where a migrating IAB node is static.
  • the IAB Donor CU is changed at least because an IAB mobile termination (MT) may have moved out of a coverage of a source donor CU or the radio link quality deteriorates so that the IAB MT may need to be served by a target donor CU.
  • IAB nodes can be mounted in vehicles and can provide wireless (e.g., 5G) coverage/capacity enhancement to onboard and/or surrounding UEs such as in shown in FIG. 1 where a mobile IAB node is included on or in a train.
  • wireless e.g., 5G
  • IAB can enable wireless relaying in NG-RAN.
  • the relaying node which can be referred to as IAB-node, can support access and backhauling via NR.
  • the terminating node of NR backhauling on network side can be referred to as the IAB-donor, which can represent a gNB with additional functionality to support IAB. Backhauling can occur via a single or via multiple hops.
  • the IAB architecture is shown in FIGS. 2A and 2B.
  • FIG. 2A shows IAB-node using standalone (SA) mode with next generation core network (NGC) .
  • FIG. 2B shows IAB-node using E-UTRA-NR Dual Connectivity (EN-DC) .
  • the IAB-node can support gNB-DU functionality, to terminate the NR access interface to UEs and next-hop IAB-nodes, and to terminate the F1 protocol to the gNB-CU functionality, on the IAB-donor.
  • the gNB-DU functionality on the IAB-node can also be referred to as IAB-DU.
  • DU is an acronym for distributed unit.
  • the IAB-node can also support a subset of the UE functionality referred to as IAB-MT, which includes, e.g., physical layer, layer-2, RRC and NAS functionality to connect to the gNB-DU of another IAB-node or the IAB-donor, to connect to the gNB-CU on the IAB-donor, and to the core network.
  • IAB-MT is an acronym for mobile termination.
  • the IAB-node can access the network using either SA-mode or EN-DC.
  • EN-DC the IAB-node can also connect via E-UTRA to a Master eNB (MeNB) , and the IAB-donor terminates X2-C as secondary gNB (SgNB) .
  • MeNB Master eNB
  • SgNB secondary gNB
  • FIG. 3 shows parent-node and child-node relationship for an IAB-node.
  • All IAB-nodes that are connected to an IAB-donor via one or multiple hops can form a directed acyclic graph (DAG) topology with the IAB-donor at its root as shown in FIG. 3.
  • DAG directed acyclic graph
  • the neighbor node on the IAB-DU’s interface can be referred to as child node and the neighbor node on the IAB-MT’s interface can be referred to as parent node.
  • the direction toward the child node can be further referred to as downstream while the direction toward the parent node can be referred to as upstream.
  • the IAB-donor performs centralized resource, topology and route management for the IAB topology.
  • ⁇ IAB-donor can be a gNB that provides network access to UEs via a network of backhaul and access links.
  • ⁇ IAB-donor-CU can be a gNB-CU of an IAB-donor, terminating the F1 interface towards IAB-nodes and IAB-donor-DU.
  • ⁇ IAB-donor-DU can be the gNB-DU of an IAB-donor, hosting the IAB BAP sublayer, providing wireless backhaul to IAB-nodes.
  • ⁇ IAB-DU can have a gNB-DU functionality supported by the IAB-node to terminate the NR access interface to UEs and next-hop IAB-nodes, and to terminate the F1 protocol to the gNB-CU functionality on the IAB-donor.
  • IAB-MT can have an IAB-node function that terminates the Uu interface to the parent node using the procedures and behaviors specified for UEs unless stated otherwise.
  • IAB-MT function may correspond to an IAB-UE function.
  • ⁇ IAB-node can be a RAN node that supports NR access links to UEs and NR backhaul links to parent nodes and child nodes.
  • the IAB-node may not support backhauling via LTE.
  • Child node can be IAB-DU’s and IAB-donor-DU’s next hop neighbor node; the child node can also be an IAB-node.
  • Parent node can be IAB-MT’s next hop neighbor node; the parent node can be IAB-node or IAB-donor-DU.
  • ⁇ Upstream can describe a direction toward parent node in IAB-topology.
  • ⁇ Downstream can describe a direction toward child node or UE in IAB-topology.
  • FIGS. 4A-4C show example scenarios of the inter-donor mobility of the mobile IAB node.
  • mobile IAB-MT migrates from donor DU1 which belongs to donor CU1 to donor DU2 which belongs to donor CU2.
  • the mobile IAB-DU may maintain its F1 connection with donor CU1 and UE context remains in donor CU1.
  • F1-C/U traffic between donor CU1 and mobile IAB-DU is transmitted via donor DU2.
  • mobile IAB-MT migrates from donor DU2 which belongs to donor CU2 to donor DU3 which belongs to donor CU3.
  • the mobile IAB-DU may maintain its F1 connection with donor CU1 and UE context remains in donor CU1.
  • F1-C/U traffic between donor CU1 and mobile IAB-DU is transmitted via donor DU3.
  • the mobile IAB-DU migrates from donor CU1 to donor CU3. And the UE is handed over from donor CU1 to donor CU3. As shown in FIG. 4C, F1-C/U traffic between donor CU3 and mobile IAB-DU can be transmitted via donor DU3.
  • the F1-terminating donor can include a CU that has F1-C connection with the mobile IAB node, e.g., the CU that serves the mobile IAB-DU.
  • the source donor can be a source CU donor that is connected to the mobile IAB MT before the handover, and the target donor is a target CU donor to which the mobile IAB MT will be connected after the handover is performed.
  • Step 1 optionally, during the inter-donor migration procedure of mobile IAB node (including partial migration or full migration) , if the source donor of the IAB-MT and the F1-terminating donor are different donors, the source donor sends MT handover information to the F1-terminating donor, e.g., after receiving measurement report from the IAB-MT, or after receiving handover request ack message from the target donor of the IAB-MT.
  • the MT handover information includes at least one of the following: MT handover indication, target cell ID, candidate cell ID or candidate cell ID, MT ID allocated by the source donor, MT ID allocated by the target donor (e.g., XnAP ID or BAP address) .
  • the target donor of IAB-MT sends MT handover information to the F1-terminating donor, e.g., after receiving handover request message from the source donor.
  • the IAB node sends MT handover information to the F1-terminating donor, e.g., after receiving RRCreconfiguration message from the source donor.
  • Step 2 Optionally, if the source donor of the IAB-MT and the F1-terminating donor are different donors, F1 terminating donor can determine (e.g., based on whether there is Xn interface or IP connectivity between F1 terminating donor and the target donor) the migration type. And then F1 terminating donor can send the migration type information to the source donor or the target donor.
  • the F1 terminating donor can have a connection with a mobile IAB DU.
  • the migration type information can indicate whether a UE handover is to be performed and/or a sequence of handover involving the UE, mobile IAB node, DU in mobile IAB node, and/or MT in mobile IAB node.
  • the migration type information includes at least one of the following: partial migration, full migration, UE migration first, MT migration first, DU migration first, DU migration is executed after MT migration, UE migration is executed after MT migration, DU migration is executed before MT migration, UE migration is executed before MT migration.
  • the indication related to “UE migration first, ” or “MT migration first, ” or “DU migration first” can indicate that a handover is respectively first performed by UE, or MT, or DU.
  • the indication related to “DU migration is executed after MT migration, ” “UE migration is executed after MT migration, ” “DU migration is executed before MT migration, ” “UE migration is executed before MT migration” respectively indicate that a handover is first preformed by MT and then DU, that a handover is first performed by the MT and then UE, that the handover is first performed by DU and then MT, and the handover is first performed by UE and then MT.
  • a partial migration may include performing a migration of an IAB-MT to a parent node underneath a different IAB-donor-CU while the donor CU serving co-located IAB-DU and served UEs remain unchanged.
  • a full migration may include migrating the IAB-MT, co-located IAB-DU and the served UE (e.g., both RRC and F1 connection) to a target IAB-donor-CU.
  • the F1 terminating donor determines that there is no IP connectivity between F1 terminating donor and the target donor, then the F1 terminating donor determines that DU migration needs to be executed before MT migration and the F1 terminating donor can indicate “DU migration is executed after MT migration” in the migration type information.
  • Step 3 The source donor of the IAB-MT sends the migration type information to the target donor of the IAB-MT, e.g., after the receiving the migration type information from the F1-terminating donor.
  • the source donor could send the migration type information to the target donor via XnAP message, e.g., handover request message.
  • Step 4 The target donor includes the migration type information in the RRCreconfiguration message, and includes the RRCreconfiguration message in XnAP message. And then the target donor sends the XnAP message including the migration type information to the source donor.
  • Step 5 the source donor sends the the RRCreconfiguration message including the migration type information to the IAB-MT.
  • UE context setup and release procedure is used at target and source DU respectively to setup UE context at the target DU and release UE context at the source DU.
  • the source and target DUs of the UE handover procedure are two logical DUs which co-locates in the same mobile IAB node. So it’s not efficient to use UE context setup and release procedure during UE handover procedure.
  • One potential solution is that UE context may be shared between the two logical DUs in the mobile IAB-node. In this way, UE context modification could be used to update UE context at the mobile IAB node, instead of UE context setup/release procedure at source/target logical DU respectively.
  • the technical problem is how to transfer UE information used in the target logical DU (e.g., the logical DU that has F1 connection with the target donor) to the target donor if UE context setup procedure is not used during UE handover procedure.
  • the mobile IAB node is handover from a source DU to a target DU, where a UE is connected to a source logical DU in mobile IAB node before the handover, and the UE is connected to a target logical DU in the mobile IAB node after the handover.
  • Example Solution UE information is sent from the target logical DU in the mobile IAB node to the target donor (e.g., target donor CU) , e.g., via F1AP UE context modification response or IAB UP configuration update response message.
  • the UE information includes at least one of the following: the cell radio network temporary identifier (C-RNTI) allocated by the mobile IAB node for the UE, the old C-RNTI allocated by the source logical DU for the UE, the new C-RNTI allocated by the target logical DU for the UE.
  • the C-RNTI allocated by the mobile IAB node may not be changed and can be used to identify the UE in source logical DU and target logical DU.
  • the old C-RNTI is used to identify the UE in the source logical DU
  • the new C-RNTI is used to identify the UE by the target logical DU.
  • target logical DU in the IAB node needs to setup F1 connection with the target donor before MT migration. So F1 traffic between the target donor and the mobile IAB node needs to be transferred via the source path, e.g., through the source parent DU and the source donor DU.
  • the problem is how to transfer F1 traffic between target CU and the mobile IAB node via source path.
  • a migration of the mobile IAB node is facilitated from a source donor CU to a target donor CU, where the migration of the DU in IAB node is executed before the migration of the MT in the same IAB node.
  • Step 1 F1 terminating donor or source donor of IAB-MT sends DSCP/Flow label to be used for downlink F1 traffic to target donor of IAB-MT.
  • the target donor can set the DSCP/Flow label of F1 traffic according to the DSCP/Flow label information received from the F1 terminating donor or source donor.
  • Step 2 target donor obtain new DL TNL address used by the mobile IAB node via F1AP, e.g., F1 setup, DU configuration update, or IAB UP configuration update response message.
  • F1AP e.g., F1 setup, DU configuration update, or IAB UP configuration update response message.
  • Step 3 the target donor sends new DL TNL address for F1 traffic to source donor via XnAP message to the source donor.
  • the source donor can use the new DL TNL address for DL mapping configuration at the source donor DU.
  • the target donor sends the new DL TNL address for F1 traffic to the F1-terminating donor via XnAP message. And then the F1-terminating donor sends the new DL TNL address to the source donor via XnAP message.
  • FIG. 5 shows an exemplary block diagram of a hardware platform 500 that may be a part of a network device (e.g., base station) or a communication device (e.g., a user equipment (UE) ) .
  • the hardware platform 500 includes at least one processor 510 and a memory 505 having instructions stored thereupon. The instructions upon execution by the processor 510 configure the hardware platform 500 to perform the operations described in FIGS. 1 to 4C and 6 to 9 and in the various embodiments described in this patent document.
  • the transmitter 515 transmits or sends information or data to another device.
  • a network device transmitter can send a message to a user equipment.
  • the receiver 520 receives information or data transmitted or sent by another device.
  • a user equipment can receive a message from a network device.
  • FIG. 6 shows an example of a wireless communication system (e.g., a 5G or NR cellular network) that includes a base station 620 and one or more user equipment (UE) 611, 612 and 613.
  • the UEs access the BS (e.g., the network) using a communication link to the network (sometimes called uplink direction, as depicted by dashed arrows 631, 632, 633) , which then enables subsequent communication (e.g., shown in the direction from the network to the UEs, sometimes called downlink direction, shown by arrows 641, 642, 643) from the BS to the UEs.
  • a wireless communication system e.g., a 5G or NR cellular network
  • the UEs access the BS (e.g., the network) using a communication link to the network (sometimes called uplink direction, as depicted by dashed arrows 631, 632, 633) , which then enables subsequent communication (e.g.,
  • the BS send information to the UEs (sometimes called downlink direction, as depicted by arrows 641, 642, 643) , which then enables subsequent communication (e.g., shown in the direction from the UEs to the BS, sometimes called uplink direction, shown by dashed arrows 631, 632, 633) from the UEs to the BS.
  • the UE may be, for example, a smartphone, a tablet, a mobile computer, a machine to machine (M2M) device, an Internet of Things (IoT) device, and so on.
  • M2M machine to machine
  • IoT Internet of Things
  • FIG. 7 shows an exemplary flowchart for receiving a migration type information.
  • Operation 702 includes receiving, by a first network device, a migration type information that indicates a type of handover associated with a handover operation of a mobile network device from the first network device to a second network device, where the first network device receives the migration type information from a third network device.
  • the method further comprises sending a first message comprising the migration type information to the second network device.
  • the method further comprises receiving a second message comprising the migration type information from the second network device; and transmitting, by the first network device and in response to the receiving the second message, the migration type information to the mobile network device.
  • the type of handover indicates a sequence of operations associated with the handover operation for the mobile network device and/or a communication device in communication with the mobile network device.
  • the migration type information includes any one or more of: a partial migration, a full migration, a user equipment (UE) migration first that indicates that the handover operation is performed for the communication device before the handover operation for the mobile network device, a mobile termination (MT) migration first that indicates that the handover operation is first performed for the MT in the mobile network device, a distributed unit (DU) migration first that indicates that the handover operation is first performed for the DU in the mobile network device, a DU migration is executed after MT migration that indicates that the handover operation is performed for the DU in the mobile network device after the handover operation is performed for the MT in the mobile network device, a UE migration is executed after MT migration that indicates that the handover operation is performed for the communication device after the handover operation is performed for the MT in the mobile network device, a DU migration is executed before
  • the first network device includes a first Integrated Access and Backhaul (IAB) donor to which the mobile network device is connected before the handover, where the second network device includes a second IAB donor to which the mobile network device will be connected after the handover, and/or where the third network device includes a third IAB donor that has a connection with the mobile network device.
  • the mobile network device includes a mobile Integrated Access and Backhaul (IAB) device.
  • FIG. 8 shows an exemplary flowchart for transmitting information related to a communication device.
  • Operation 802 includes transmitting, by a second logical distributed unit (DU) in a mobile network device, information related to a communication device during a handover of the communication device from a first network device to a second network device, where the second logical DU in the mobile network device transmits the information related to the UE to the second network device, where the communication device is in communication with the mobile network device, where the second logical DU is configured to communicate with the second network device, and where the information related to the communication device includes any one or more of: a cell radio network temporary identifier (C-RNTI) allocated by the mobile network device for the communication device, a first C-RNTI allocated by a first logical DU in the mobile network device for the communication device, a second C-RNTI allocated by the second logical DU in the mobile network device for the communication device.
  • the first network device includes a source base station
  • the second network device includes a target base station.
  • FIG. 9 shows an exemplary flowchart for receiving an address associated with a mobile network device.
  • Operation 902 includes receiving, by a first network device from a mobile network device, an address associated with the mobile network device.
  • Operation 904 includes transmitting the address to a second network device.
  • the address includes a downlink (DL) transport network layer (TNL) address for F1 traffic which goes through a donor DU which connects to the second network device.
  • the first network device includes a target base station to which a mobile termination (MT) in the mobile network device is handed over
  • the second network device includes a source base station from which the MT in the mobile network device is handed over.
  • the mobile network device includes an Integrated Access and Backhaul (IAB) device.
  • IAB Integrated Access and Backhaul
  • a computer-readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM) , Random Access Memory (RAM) , compact discs (CDs) , digital versatile discs (DVD) , etc. Therefore, the computer-readable media can include a non-transitory storage media.
  • program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • Computer-or processor-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.
  • a hardware circuit implementation can include discrete analog and/or digital components that are, for example, integrated as part of a printed circuit board.
  • the disclosed components or modules can be implemented as an Application Specific Integrated Circuit (ASIC) and/or as a Field Programmable Gate Array (FPGA) device.
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • DSP digital signal processor
  • the various components or sub-components within each module may be implemented in software, hardware or firmware.
  • the connectivity between the modules and/or components within the modules may be provided using any one of the connectivity methods and media that is known in the art, including, but not limited to, communications over the Internet, wired, or wireless networks using the appropriate protocols.

Landscapes

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

Abstract

L'invention concerne des techniques de transfert d'informations dans un système d'accès et de liaison terrestre intégré. Un procédé de communication sans fil donné à titre d'exemple consiste à recevoir, par un premier dispositif de réseau, des informations de type de migration qui indiquent un type de transfert associé à une opération de transfert d'un dispositif de réseau mobile du premier dispositif réseau à un second dispositif réseau, le premier dispositif réseau recevant les informations de type de migration provenant d'un troisième dispositif réseau.
PCT/CN2022/129971 2022-11-04 2022-11-04 Techniques de transfert d'informations dans un système d'accès et de liaison terrestre intégré WO2024092739A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/129971 WO2024092739A1 (fr) 2022-11-04 2022-11-04 Techniques de transfert d'informations dans un système d'accès et de liaison terrestre intégré

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/129971 WO2024092739A1 (fr) 2022-11-04 2022-11-04 Techniques de transfert d'informations dans un système d'accès et de liaison terrestre intégré

Publications (1)

Publication Number Publication Date
WO2024092739A1 true WO2024092739A1 (fr) 2024-05-10

Family

ID=90929343

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/129971 WO2024092739A1 (fr) 2022-11-04 2022-11-04 Techniques de transfert d'informations dans un système d'accès et de liaison terrestre intégré

Country Status (1)

Country Link
WO (1) WO2024092739A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113940112A (zh) * 2019-03-28 2022-01-14 中兴通讯股份有限公司 用于iab切换的系统和方法
WO2022015230A1 (fr) * 2020-07-17 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Migration inter-cu dans la migration inter-cu de réseau iab dans un réseau iab
CN115053565A (zh) * 2020-02-17 2022-09-13 中兴通讯股份有限公司 自接入回传网络中的宿主间拓扑自适应

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113940112A (zh) * 2019-03-28 2022-01-14 中兴通讯股份有限公司 用于iab切换的系统和方法
CN115053565A (zh) * 2020-02-17 2022-09-13 中兴通讯股份有限公司 自接入回传网络中的宿主间拓扑自适应
WO2022015230A1 (fr) * 2020-07-17 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Migration inter-cu dans la migration inter-cu de réseau iab dans un réseau iab

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SAMSUNG (MODERATOR): "Summary of offline discussion on CB: # 37_IAB_InterDonorMigrationDetails", 3GPP DRAFT; R3-212676, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20210517 - 20210527, 24 May 2021 (2021-05-24), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052013584 *
SAMSUNG: "(TP for IAB BL CR TS38.401) Discussion on inter-donor IAB node migration procedure for Rel-17 eIAB", 3GPP DRAFT; R3-213313, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20210816 - 20210826, 6 August 2021 (2021-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052035237 *

Similar Documents

Publication Publication Date Title
RU2752242C1 (ru) Способы, обеспечивающие возможность двойного подключения для избыточных путей плоскости пользователя, и соответствующие сетевые узлы
KR102615567B1 (ko) 정보 전송 방법 및 디바이스
JP5710753B2 (ja) アドバンストｌｔｅシステムにおける通信のリレー
US20110244851A1 (en) Configuring relay cell identities in cellular networks
US20220263743A1 (en) Selective packet duplication or alternative packet transmission based on survival time
WO2013191505A1 (fr) Procédé et appareil pour la transmission d'une indication dans un système de communications sans fil
US20220141732A1 (en) Method and apparatus for reporting assistant information
US20230354114A1 (en) Systems and methods for iab migration
CN112073163A (zh) 邻小区配置信息传输方法和系统、计算机可读存储介质
JP2023545801A (ja) 信号の送受信方法、装置及び通信システム
WO2016161785A1 (fr) Procédé et appareil de commutation de section de nœud b évolué maître et station de base
CN114339925B (zh) 切换方法、装置、终端设备、网络设备及存储介质
US20230308975A1 (en) Group migration method and apparatus and system
WO2020167188A1 (fr) Entité de protocole pdcp, entité de commande rlc et procédés réalisés dans celles-ci pour fournir une connectivité multiple
WO2024092739A1 (fr) Techniques de transfert d'informations dans un système d'accès et de liaison terrestre intégré
CN109804708B (zh) 控制通信的方法、无线通信设备、接入点和无线通信系统
US20230354106A1 (en) Cu-du communication for multicast with support for switching between unicast and multicast
JP2024517469A (ja) 信号の送受信方法、装置及び通信システム
KR20230070483A (ko) Iab-노드 마이그레이션 방법 및 장치
CN117099404A (zh) 发送和接收信号的方法、装置和通信系统
WO2024031265A1 (fr) Procédé et appareil de migration de noeud d'accès et de liaison terrestre intégrés
WO2023150975A1 (fr) Dispositif donneur d'iab et procédé de transmission et de retour en arrière de la migration
US20230363026A1 (en) Radio access network node, user equipment, and methods thereof
WO2024113620A1 (fr) Génération de clé secrète pré-partagée pour un dispositif de réseau d'accès et de backhaul
WO2022205326A1 (fr) Procédés et systèmes de migration de donneur d'accès et de de liaison terrestre intégré

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

Country of ref document: EP

Kind code of ref document: A1