[go: up one dir, main page]

WO2025166586A1 - Migration mobile d'accès intégré et de liaison terrestre (iab) - Google Patents

Migration mobile d'accès intégré et de liaison terrestre (iab)

Info

Publication number
WO2025166586A1
WO2025166586A1 PCT/CN2024/076468 CN2024076468W WO2025166586A1 WO 2025166586 A1 WO2025166586 A1 WO 2025166586A1 CN 2024076468 W CN2024076468 W CN 2024076468W WO 2025166586 A1 WO2025166586 A1 WO 2025166586A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
handover
message
system information
mobile
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/CN2024/076468
Other languages
English (en)
Inventor
Andrew LAPPALAINEN
Ilkka Antero Keskitalo
Xiang Xu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
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 Nokia Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to PCT/CN2024/076468 priority Critical patent/WO2025166586A1/fr
Priority to CN202411769975.0A priority patent/CN120456152A/zh
Publication of WO2025166586A1 publication Critical patent/WO2025166586A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points

Definitions

  • Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium of mobile integrated access and backhaul (IAB) migration.
  • IAB mobile integrated access and backhaul
  • IAB integrated access and backhaul
  • NG next generation
  • RAN radio access network
  • IAB-node supports access and backhauling via NR.
  • the terminating node of NR backhauling on network side is referred to as the IAB-donor, which represents a network node such as an NR NB (also referred to as a gNB) with additional functionality to support IAB.
  • Backhauling may occur via a single or via multiple hops.
  • mIAB mobile IAB
  • Mobile IAB-node is a RAN node that provides NR access links to user equipment (UE) and an NR backhaul link to a parent node, and that may conduct physical mobility across the RAN area.
  • the mobile IAB-node includes a mobile IAB mobile termination (IAB-MT) and a mobile IAB distributed unit (IAB-DU) .
  • Mobile IAB may support the same or similar functionality as IAB unless explicitly specified.
  • the mobile IAB-MT may perform a mobile IAB-MT migration procedure.
  • a first apparatus comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: receive, from a second apparatus, a request for handover of a third apparatus from the second apparatus to the first apparatus; determine, based on a type of the third apparatus, that system information is unrequired for the handover of the third apparatus; and transmit a message to the third apparatus via the second apparatus, the message including identity information of the first apparatus and excluding the system information.
  • a third apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the third apparatus at least to: receive, from a first apparatus via a second apparatus, a message for handover of the third apparatus from the second apparatus to the first apparatus, wherein system information is unrequired for the handover of the third apparatus and the message includes identity information of the first apparatus and excludes the system information; and initiate a handover execution to the first apparatus based on the message.
  • a method comprises: receiving, at a third apparatus from a first apparatus via a second apparatus, a message for handover of the third apparatus from the second apparatus to the first apparatus, wherein system information is unrequired for the handover of the third apparatus and the message includes identity information of the first apparatus and excludes the system information; and initiating a handover execution to the first apparatus based on the message.
  • a first apparatus comprises means for receiving, from a second apparatus, a request for handover of a third apparatus from the second apparatus to the first apparatus; means for determining, based on a type of the third apparatus, that system information is unrequired for the handover of the third apparatus; and means for transmitting a message to the third apparatus via the second apparatus, the message including identity information of the first apparatus and excluding the system information.
  • a third apparatus comprises means for receiving, from a first apparatus via a second apparatus, a message for handover of the third apparatus from the second apparatus to the first apparatus, wherein system information is unrequired for the handover of the third apparatus and the message includes identity information of the first apparatus and excludes the system information; and initiating a handover execution to the first apparatus based on the message.
  • a computer readable medium comprises instructions stored thereon for causing an apparatus to perform the method according to the third aspect or the fourth aspect.
  • FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented
  • FIG. 2A illustrates an example signaling flow of mobile IAB migration
  • FIG. 2B illustrates another example signaling flow of mobile IAB migration
  • FIG. 3 illustrates a signaling flow of a handover procedure according to some example embodiments of the present disclosure
  • FIG. 4A illustrates a signaling flow of mobile IAB migration according to some example embodiments of the present disclosure
  • FIG. 4B illustrates another signaling flow of mobile IAB migration according to some example embodiments of the present disclosure
  • FIG. 5 illustrates a flowchart of a method implemented at a first apparatus according to some example embodiments of the present disclosure
  • FIG. 6 illustrates a flowchart of a method implemented at a third apparatus according to some example embodiments of the present disclosure
  • FIG. 7 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure.
  • FIG. 8 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first, ” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • performing a step “in response to A” does not indicate that the step has to be performed immediately after “A” occurs and one or more intervening steps may be included.
  • circuitry may refer to one or more or all of the following:
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • suitable generation communication protocols including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system
  • the term “network device” or “network access device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio head (RH) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth,
  • radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node.
  • An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.
  • IAB-MT Mobile Terminal
  • terminal device refers to any end device that may be capable of wireless communication.
  • a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • UE user equipment
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/
  • the terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node) .
  • MT Mobile Termination
  • IAB node e.g., a relay node
  • the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
  • resource may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like.
  • a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
  • the mobile IAB-MT may perform the mobile IAB-MT migration procedures via Xn handover and/or via NG handover.
  • the mobile IAB-MT may also perform the mobile IAB-node recovery procedures.
  • the mobile IAB-node may perform the mobile IAB-DU migration procedure, where a new logical mobile IAB-DU is established on the mobile IAB-node and the initial logical mobile IAB-DU is released some time later.
  • the UEs connected via the mobile IAB-node are handed over from the initial logical mobile IAB-DU, referred to as the source logical mobile IAB-DU, to the new logical mobile IAB-DU, referred to as the target logical mobile IAB-DU.
  • the details of the mobile IAB-DU migration may be defined in a standard such as the technical specification (TS) 38.401.
  • Enhancements related to backhaul adaptation protocol (BAP) for mobile IAB-DU migration may be defined in a standard such as the technical specification (TS) 38.340.
  • FIG. 1 illustrates an example communication environment 100 in which example embodiments of the present disclosure can be implemented.
  • a mobile IAB 110 includes an IAB-DU 112 (also referred to as mobile IAB-DU) and an IAB-MT 114 (also referred to as mobile IAB-MT) .
  • the mobile IAB 110 may also be referred to as a mobile IAB node.
  • the IAB-DU supports the gNB-DU functionality, to terminate the NR access interface to terminal devices or UEs and next-hop IAB-nodes, and to terminate F1 protocol to the gNB-CU functionality, on the IAB-donor.
  • the IAB-MT 114 may include a subset of the UE functionality, which includes for example physical layer, layer-2, RRC and non-access stratum (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.
  • NAS non-access stratum
  • the mobile IAB 110 is connected to a source network node 120 (also referred to as a source network device or a source gNB) .
  • a source network node 120 also referred to as a source network device or a source gNB
  • the IAB-MT 114 is connected to the source network node 120.
  • the source network node 120 may be the terminating node of NR backhauling on network side, which may be a gNB with additional functionality to support IAB.
  • the source network node 120 may be referred to as a source radio resource control (RRC) -terminating IAB-donor-central unit (CU) .
  • RRC source radio resource control
  • the mobile IAB 110 may be handed over to a target network node 130 (also referred to as a target network device or target gNB) from the source network node 120.
  • the target network node 130 may also be referred to as a target RRC-terminating IAB-donor-CU.
  • the mobile IAB 110 may be connected to a donor CU 150 such as an F1-terminating IAB-donor-CU.
  • the mobile IAB-DU 112 co-located with the mobile IAB-MT 114 is connected to the donor CU 150 (that is, the F1-terminating IAB-donor-CU) .
  • the F1-terminating IAB-donor-CU may be the source RRC-terminating IAB-donor-CU, or the target RRC-terminating IAB-donor-CU, or any other suitable different donor CU.
  • a terminal device 140 communicates with the mobile IAB 110.
  • the terminal device 110 may get access to the network such as get the NR access links from the mobile IAB 110.
  • the network such as the core network may provide service to the terminal device 140 via the mobile IAB 110.
  • the communication environment 100 may include any suitable number of apparatuses configured to implementing example embodiments of the present disclosure.
  • Communications in the communication environment 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , the fifth generation (5G) , the sixth generation (6G) , and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • s cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , the fifth generation (5G) , the sixth generation (6G) , and the like
  • wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and/or any other technologies currently known or to be developed in the future.
  • CDMA Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • MIMO Multiple-Input Multiple-Output
  • OFDM Orthogonal Frequency Division Multiple
  • DFT-s-OFDM Discrete Fourier Transform spread OFDM
  • the mobile IAB node may perform a mobile IAB migration procedure.
  • the mobile IAB-DU may pass to the F1-terminating IAB-donor-CU via F1 application protocol (F1AP) the gNB identifier (ID) of the target RRC-terminating IAB-donor-CU and the mobile IAB node’s BAP address allocated by the target RRC-terminating IAB-donor-CU.
  • F1AP F1 application protocol
  • ID gNB identifier
  • each logical mobile IAB-DU passes this information to its respective F1-terminating IAB-donor-CU.
  • the target cell supporting mobile IAB access should broadcast gNB-ID-Length in system information block one (SIB1) .
  • SIB1 system information block one
  • the mobile IAB-MT may be able to decode this information.
  • the IAB-MT Upon acquiring the relevant information from SIB1, the IAB-MT signals the gNB ID (and public land mobile network (PLMN) ID) to the IAB-DU, which the IAB-DU signals to its respective F1-terminating IAB-donor-CU within the RRC Terminating IAB-Donor-Related Info information element (IE) of the GNB-CU CONFIGURATION UPDATE message.
  • PLMN public land mobile network
  • IAB-MT decodes the PLMN ID, cell ID, and gNB-ID-Length from the SIB1 of the neighbour cells (including the target cell) that triggered the mobility event.
  • the IAB-MT may decode the PLMN ID and gNB ID from PLMN-IdentityInfoList IE and a non-public network (NPN) -IdentityInfoList IE.
  • PLMN-IdentityInfoList IE PLMN-IdentityInfoList IE
  • NPN non-public network
  • FIG. 2A illustrates an example signaling flow 200 of mobile IAB migration.
  • the signaling flow 200 involves a mobile IAB 201, a source gNB 205, a target gNB 207 and a F1-terminating donor CU 209.
  • the mobile IAB 201 includes an IAB-DU 202 and an IAB-MT 204.
  • the target gNB 207 may transmit SSB and SIB1 to the IAB-MT 204.
  • the source gNB 205 may transmit a measurement configuration to the IAB-MT 204.
  • the IAB-MT may detect an event such as a target cell being better than the serving cell or a mobility event. The event may trigger the mobile IAB mobility, such as the IAB-MT 204 mobility.
  • the target gNB 207 transmits SIB1 to the IAB-MT 204.
  • a delay for SIB reception and decoding may occur.
  • this requirement for the IAB-MT 204 to decode SIB1 from cells would introduce delays based on the synchronization signal block (SSB) periodicity and SIB1 scheduling, which increases the risk for handover failure at the IAB-MT 204 (especially in high-speed mobility scenarios) and could slow down the migration procedure.
  • time spent decoding the SIB1 of the neighbouring cells causes interruptions to the mobile IAB-MT 204's backhaul, which could negatively impact the on-board UEs.
  • SSB synchronization signal block
  • the IAB-MT 204 may transmit the measurement report to the source gNB 205.
  • the source gNB 205 may transmit the handover request to the target gNB 207.
  • the target gNB 207 may respond with a handover request ACK (such as HandoverCommand) to the source gNB 205.
  • the source gNB 205 may transmit an RRCReconfiguration such as reconfigurationWithSync to the IAB-MT 204.
  • the IAB-MT 204 may transmit the target cell PLMN-ID and the gNB-ID to the IAB-DU 202.
  • An access procedure may be performed by the IAB-MT 204 and the target gNB 207.
  • the handover procedure may be completed.
  • the IAB-DU 202 may update the gNB-DU configuration including the PLMN-ID and the gNB-ID to the F1-terminating donor-CU 209.
  • An IAB transport migration management procedure is then performed.
  • FIG. 2B illustrates another example signaling flow 250 of mobile IAB migration.
  • the signaling flow 250 involves the mobile IAB 201, the source gNB 205, the target gNB 207 and the F1-terminating donor CU 209.
  • the mobile IAB 201 includes an IAB DU 202 and an IAB MT 204.
  • dedicatedSIB1-Delivery is included in the handover request acknowledgement (ACK) or the HandoverCommand from the target gNB 207 to the source gNB 205.
  • ACK handover request acknowledgement
  • HandoverCommand from the target gNB 207 to the source gNB 205.
  • the dedicatedSIB1-Delivery includes the PLMN-ID, the cellIdentity and gNB-ID-Length.
  • the dedicatedSIB1-Delivery may be transmitted from the source gNB 205 to the mobile IAB-MT 204 via the RRCReconfiguration such as reconfigurationWithSync.
  • a second apparatus transmits, to a first apparatus (for example, a target gNB) , a request for handover of a third apparatus (for example, a mobile IAB) from the second apparatus to the first apparatus.
  • the first apparatus determines that system information is unrequired for the handover of the third apparatus based on a type of the third apparatus.
  • the type of the third apparatus may be the mobile IAB.
  • the first apparatus transmits a message to the third apparatus via the second apparatus.
  • the message includes identity information of the first apparatus and excludes the system information.
  • the message may include global gNB ID of the first apparatus. In this way, the identity information of the first apparatus can be informed to the third apparatus without transmitting the system information such as SIB1. Signaling overhead can thus be reduced.
  • time delay for decoding the system information can be reduced.
  • FIG. 3 illustrates a signaling flow 300 of a handover procedure for the mobile IAB migration according to some example embodiments of the present disclosure.
  • the signaling flow 300 involves a first apparatus 310, a second apparatus 320 and a third apparatus 330.
  • the first apparatus 310 may be a first network node or network device such as the target network node 130 in FIG. 1.
  • the second apparatus 320 may be a second network node or network device such as the source network node 120 in FIG. 1.
  • the third apparatus 330 may be implemented as the mobile IAB 110 in FIG. 1.
  • the third apparatus 330 may be in a connected mode with the second apparatus 320.
  • the first apparatus 310 may be a target network node such as a target RRC-terminating IAB-donor-CU
  • the second apparatus 320 may be a source network node such as a source RRC-terminating IAB-donor-CU.
  • the second apparatus 320 transmits (335) , to the first apparatus 310, a request for handover (HO) of the third apparatus 330 from the second apparatus 320 to the first apparatus 310.
  • the first apparatus 310 receives (340) the request.
  • the first apparatus 310 determines (350) , based on a type of the third apparatus 330, that system information is unrequired for the handover of the third apparatus 330.
  • the system information may include SIB1 such as dedicated SIB1-Delivery.
  • the type of the third apparatus 330 is a mobile IAB or a mobile IAB-MT
  • the first apparatus 310 may determine (350) that the system information is unrequired. If the third apparatus 330 is UE or other terminal device or network node, the first apparatus 310 may determine that the system information is required.
  • the request for the handover may indicate the type of the third apparatus 330.
  • the first apparatus 310 may determine whether the system information is required or unrequired for the handover based on the request for the handover.
  • the conditions such as the type of the third apparatus 330 being the mobile IAB are only for the purpose of illustration, without suggesting any limitation.
  • the first apparatus 310 may determine that the system information is unrequired, as well.
  • the applicable type is not limited to the mobile IAB.
  • the first apparatus 310 may determine (350) that the system information is unrequired. If the type of the third apparatus 330 is a mobile IAB but the first apparatus 310 does not support the mobile IAB, the first apparatus 310 may determine that the system information is required. That is, the determination of whether or not the system information is required may in an embodiment be based also on the capabilities of the first apparatus 310.
  • the first apparatus 310 transmits (360) a message to the third apparatus 330 via the second apparatus 320.
  • the message includes identity information of the first apparatus 310 and excludes the system information.
  • the first apparatus 310 transmits (360) the message to the second apparatus 320.
  • the second apparatus 320 transmits or forwards (370) the message to the third apparatus 330.
  • the third apparatus 330 receives (380) the message.
  • the message may be an RRC container or any other suitable message or IE.
  • the first apparatus 310 may transmit (360) the message to the IAB-MT of the mobile IAB via the second apparatus 320.
  • the system information such as SIB1 or dedicated SIB1-Delivery needs not to be signaled for the handover of the third apparatus 330.
  • the signaling overhead and the time delay for decoding the system information can be reduced.
  • the handover interruption due to the decoding of SIB1 and the signaling overhead can be reduced.
  • the message may include a RRC reconfiguration message.
  • the RRC reconfiguration message includes a handover command for the handover.
  • the message may include a handover command for the handover.
  • the message may include an ACK of the request for the handover.
  • the identity information of the first apparatus 310 may further include a PLMN ID.
  • a global identifier of the first apparatus 310 may be informed to the third apparatus 330.
  • the global identifier of the first apparatus 310 may be the global gNB ID of the RRC terminating IAB-Donor related information, which is composed of a PLMN ID and a gNB ID.
  • the global gNB ID of the RRC Terminating IAB-Donor related info IE may be composed of a PLMN-ID and gNB-ID.
  • the third apparatus 330 may obtain the identity information of the first apparatus 310 based on the message without receiving broadcasted system information over a radio interface from the first apparatus 310.
  • the IAB-MT of the mobile IAB obtains/receives the identity information of the first apparatus 310.
  • the identity information of the first apparatus 310 may be transferred to a fourth apparatus by the third apparatus 330.
  • the IAB-DU may transmit the identity information of the first apparatus 310 to the fourth apparatus.
  • the fourth apparatus may be an F1-terminating CU of the third apparatus 330.
  • the third apparatus 330 may perform cell measurements based on the identity information of the first apparatus 110. In addition, in some example embodiments, the third apparatus 330 initiates a handover execution to the first apparatus 310 based on the message. For example, the handover execution may be initiated based on the identity information of the first apparatus 310.
  • FIG. 4A illustrates a signaling flow 400 of mobile IAB migration according to some example embodiments of the present disclosure.
  • the signaling flow 400 involves a mobile IAB 401, a source gNB 405 (such as a source RRC-terminating IAB-donor CU) , a target gNB 407 (such as a target RRC-terminating IAB-donor CU) and an F1-terminating donor CU 409.
  • the mobile IAB 401 includes an IAB-DU 402 and an IAB-MT 404.
  • the mobile IAB 401 may be the mobile IAB 110 in FIG. 1
  • the source gNB 405 may be the source network node 120 in FIG.
  • the target gNB 407 may be the target network node 130 in FIG.
  • the F1-terminating donor CU 409 may be the donor CU 150 in FIG. 1.
  • the F1-terminating donor CU 409 may or may not be the same as the source RRC-terminating IAB-donor CU.
  • the signaling flow 400 shows the steps involved in signaling the global gNB-ID of the target RRC-terminating IAB-donor CU (that is, the target gNB 407) to the mobile IAB-MT 404.
  • the mobile IAB-MT 404 receives a measurement configuration from its source gNB 405.
  • the mobile IAB-MT 404 may trigger a measurement report based on the measurement configuration.
  • the IAB-MT 404 detects a measurement event, which it reports to the source gNB.
  • the measurement event may be that a target cell is better than the serving cell (that is, the source cell) .
  • the source gNB 405 may determine that the mobile IAB-MT 404 should be handed over to the target gNB 407 (that it, the target RRC-terminating IAB-donor-CU) and sends a handover request to the target gNB 407. For example, the source gNB 405 transmits (410) an XnAP HANDOVER REQUEST to the target gNB 407. The target gNB 407 receives (415) the HANDOVER REQUEST.
  • the HANDOVER REQUEST includes the indication that the moving node is an IAB-node as well as a mobile IAB authorization status, from which the target gNB 407 may know that the handover is associated with a mobile IAB node.
  • the target gNB 407 may acknowledge the handover request and include the handover command to be sent to the mobile IAB-MT 404.
  • the handover command may include the target global gNB ID information.
  • the target gNB 407 responds (420) with XnAP HANDOVER REQUEST ACK, which contains the HandoverCommand with the RRCReconfiguration for the target cell.
  • the source gNB 405 receives (425) the HANDOVER REQUEST ACK. Included with the RRCReconfiguration of the HandoverCommand may be the PLMN-ID, cellIdentity, and gNB-ID-Length of the target cell, while dedicated SIB1 is excluded from this message.
  • the source gNB 405 may send the handover command to the IAB-MT 404 (for example, via RRC reconfiguration with sync) , including the target gNB-ID information.
  • the source gNB 405 sends (430) the IAB-MT 404 the RRCReconfiguration for the target cell (i.e. reconfigurationWithSync) .
  • the IAB-MT 404 receives (435) the RRCReconfiguration. Included with the configuration is the PLMN-ID, cellIdentity, and gNB-ID-Length of the target cell, while dedicated SIB1 is excluded from this message.
  • the IAM-MT 404 may decode the received information and derive gNB-ID of the target node.
  • the IAB-MT 404 may also be handed over to the target gNB 407 via N2-based handover.
  • the handover signaling is NG application protocol (NGAP) signaling.
  • NGAP NG application protocol
  • the required change is also similar, and the HandoverCommand is transferred to source gNB 405 via NGAP signaling.
  • the mobile IAB-MT 404 informs the IAB-DU 402 of the target gNB-ID information, which the IAB-DU 402 signals to its F1-terminating IAB-donor CU 409 within the RRC terminating IAB-Donor Related Info IE of the GNB-CU CONFIGURATION UPDATE message.
  • the mobile IAB-MT 404 decodes the gNB-ID of the target gNB 407 based on the cellIdentity and gNB-ID-Length fields and forwards the PLMN-ID and gNB-ID to the IAB-DU 402.
  • the IAB-MT 404 accesses the target cell, and handover procedure is completed.
  • the IAB-DU 402 sends the target gNB-ID to its F1-terminating donor CU 409 as part of the RRC Terminating IAB-Donor Related Info IE of the GNB-DU CONFIGURATION UPDATE command. Knowing the target gNB-ID, the F1-terminating IAB-donor-CU 409 may initiate the transport migration management procedure with the target RRC-terminating donor CU. For example, the F1-terminating donor CU 409 initiates IAB TRANSPORT MANAGEMENT procedure with the target gNB 407.
  • the global gNB-ID information of the target RRC-terminating IAB-donor CU is signaled to the mobile IAB-MT during the handover procedure. It is beneficial to directly signal only the relevant information needed for determining the global gNB-ID of the target RRC-terminating IAB-donor CU (i.e., without extra overhead) without requiring the IAB-MT to spend time decoding the SIB1 of neighboring cells.
  • FIG. 4B illustrates another signaling flow 450 of mobile IAB migration according to some example embodiments of the present disclosure.
  • the signaling flow 450 involves the mobile IAB 401, the source gNB 405 (such as a source RRC-terminating IAB-donor CU) , the target gNB 407 (such as a target RRC-terminating IAB-donor CU) and the F1-terminating donor CU 409.
  • the mobile IAB 401 includes an IAB-DU 402 and an IAB-MT 404.
  • the mobile IAB 401 may be the mobile IAB 110 in FIG. 1
  • the source gNB 405 may be the source network node 120 in FIG.
  • the target gNB 407 may be the target network node 130 in FIG.
  • the F1-terminating donor CU 409 may be the donor CU 150 in FIG. 1.
  • the F1-terminating donor CU 409 may or may not be the same as the source RRC-terminating IAB-donor CU.
  • the mobile IAB-MT 404 receives a measurement configuration from its source gNB 405.
  • the mobile IAB-MT 404 may trigger a measurement report based on the measurement configuration.
  • the IAB-MT 404 detects a measurement event, which it reports to the source gNB.
  • the measurement event may be a target cell better than the serving cell.
  • the source gNB 405 may determine that the mobile IAB-MT 404 should be handed over to the target gNB 407 (that it, the target RRC-terminating IAB-donor-CU) and sends a handover request to the target gNB 407. For example, the source gNB 405 transmits (410) an XnAP HANDOVER REQUEST to the target gNB 407. The target gNB 407 receives (415) the HANDOVER REQUEST.
  • the HANDOVER REQUEST includes the indication that the moving node is an IAB-node as well as a mobile IAB authorization status, from which the target gNB 407 may know that the handover is associated with a mobile IAB node.
  • the target gNB 407 may acknowledge the handover request and include the handover command to be sent to the mobile IAB-MT 404.
  • the handover command may include the target global gNB ID information.
  • the target gNB 407 responds (460) with XnAP HANDOVER REQUEST ACK, which contains the HandoverCommand with the RRCReconfiguration for the target cell.
  • the source gNB 405 received (465) the HANDOVER REQUEST ACK. Included with the RRCReconfiguration of the HandoverCommand is the PLMN-ID and gNB-ID, while dedicated SIB1 is excluded from this message.
  • the source gNB 405 may send the handover command to the IAB-MT 404 (for example, via RRC reconfiguration with sync) , including the target gNB-ID information.
  • the source gNB 405 sends (470) the IAB-MT 404 the RRCReconfiguration for the target cell (i.e. reconfigurationWithSync) .
  • the IAB MT 404 receives (475) the RRCReconfiguration. Included with the configuration is the PLMN-ID and gNB-ID of the target gNB 407, while dedicated SIB1 is excluded from this message.
  • the IAB-MT 404 may also be handed over to the target gNB 407 via N2-based handover.
  • the handover signaling is NGAP signaling.
  • the required change is also similar, and the HandoverCommand is transferred to source gNB 405 via NGAP signaling.
  • the mobile IAB-MT 404 forwards the PLMN-ID and gNB-ID to the IAB-DU 402.
  • the IAB-MT 404 accesses the target cell, and handover procedure is completed.
  • the IAB-DU 402 sends the target gNB-ID to its F1-terminating donor CU 409 as part of the RRC Terminating IAB-Donor Related Info IE of the GNB-DU CONFIGURATION UPDATE command. Knowing the target gNB-ID, the F1-terminating IAB-donor-CU 409 may initiate the transport migration management procedure with the target RRC-terminating donor CU. For example, the F1-terminating donor CU 409 initiates IAB TRANSPORT MANAGEMENT procedure with the target gNB 407.
  • the gNB-ID is signalled to the mobile IAB-MT 404 directly during the handover procedure, avoiding the need to decode the gNB-ID using the cellIdentity and gNB-ID-Length fields.
  • the extra signaling overhead and the time for decoding are reduced.
  • the dedicated SIB1 delivery is a complete SIB1 information (acopy of existing SIB1, OCTET STRING) , it includes lots of redundant/unnecessary information to be signalled to the mobile IAB-MT.
  • embodiments of the present disclosure uses a new IE in HANDOVER REQUEST ACK and RRCReconfiguration (ReconfigurationWithSync) carrying only the (gNB-ID and PLMN-ID) needed to be sent to the F1-terminating donor CU for the Transport Migration Management purposes.
  • the new IE may be mandatory in the HANDOVER REQUEST ACK (or handover command) message when the target knows that the migrating node is a mobile IAB-node, and when the target gNB supports mobile IAB. This removes the ambiguity whether IAB-MT should receive and decode SIB1 broadcasted by the target gNB or could it assume SIB1 to be provided with the handover signalling. If the SIB1 is known to be included in the handover signalling, the mobile IAB-MT does not have to receive system information over the air from the target cell which enables optimized behavior for IAB-MT measurements and backhaul link performance.
  • the small IE should be sent.
  • the small IE may include the gNB information relevant for the mobile IAB migration or mobility handling.
  • the small IE does not need to be transmitted:
  • the small IE may also be applied. It is also to be understood that the example small IE, the format or content of the small IE, and the message carrying the small IE are only for the purpose of illustration. Any suitable message or signaling for the handover procedure can be applied for carrying the IE. Scope of embodiments of the present disclosure is not limited here.
  • Example embodiments regarding the gNB identity information transmission without signaling the system information for the mobile IAB migration have been described. It is to be understood that the signaling flows 300, 400 and 450 may be applied separately, or in any combination. Scope of the present disclosure is not limited in this regard. With these signaling flows, the signaling overhead and time delay for decoding the system information can be reduced. In addition, it can optimize the performance on the backhaul link as there may be no interruption due to receiving the system information and decoding of the system information.
  • FIG. 5 shows a flowchart of an example method 500 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 500 will be described from the perspective of the first apparatus 310 in FIG. 3.
  • the first apparatus 310 receives, from a second apparatus, a request for handover of a third apparatus from the second apparatus to the first apparatus 310.
  • the first apparatus 310 determines, based on a type of the third apparatus, that system information is unrequired for the handover of the third apparatus.
  • the first apparatus 310 transmits a message to the third apparatus via the second apparatus, the message including identity information of the first apparatus 310 and excluding the system information.
  • the identity information of the first apparatus 310 comprises an identifier of the first apparatus 310.
  • the identity information of the first apparatus 310 comprises a cell identity associated with the first apparatus 310 and a length of an identifier of the first apparatus 310.
  • the identity information further comprises a public land mobile network identifier.
  • the first apparatus 310 may determine, based on that the type of the third apparatus being a mobile IAB and that the first apparatus 310 supports the handover for the mobile IAB, that the system information is unrequired for the handover of the third apparatus.
  • the request indicates the type of the third apparatus.
  • the message comprises at least one of: a radio resource control reconfiguration message comprising a handover command for the handover, a handover command for the handover, or an acknowledgement of the request.
  • FIG. 6 shows a flowchart of an example method 600 implemented at a third apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 600 will be described from the perspective of the third apparatus 330 in FIG. 3.
  • the third apparatus 330 receives, from a first apparatus via a second apparatus, a message for handover of the third apparatus from the second apparatus to the first apparatus.
  • System information is unrequired for the handover of the third apparatus.
  • the message includes identity information of the first apparatus and excludes the system information.
  • the third apparatus 330 initiates a handover execution to the first apparatus based on the message.
  • the third apparatus 330 may obtain the identity information of the first apparatus without receiving broadcasted system information over a radio interface from the first apparatus.
  • the third apparatus 330 may transfer the identity information of the first apparatus to a fourth apparatus.
  • the first apparatus comprises a target RRC-terminating IAB donor-CU
  • the second apparatus comprises a source RRC-terminating IAB donor-CU
  • the third apparatus comprises a mobile IAB
  • the fourth apparatus comprises a F1-terminating donor CU of the mobile IAB.
  • a first apparatus capable of performing any of the method 500 may comprise means for performing the respective operations of the method 500.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the first apparatus may be implemented as or included in the first apparatus 310 in FIG. 3.
  • the first apparatus comprises means for receiving, from a second apparatus, request for handover of a third apparatus from the second apparatus to the first apparatus; means for determining, based on a type of the third apparatus, that system information is unrequired for the handover of the third apparatus; and means for transmitting a message to the second apparatus, the message including identity information of the first apparatus and excluding the system information.
  • the first apparatus further comprises means for performing other operations in some example embodiments of the method 500 or the first apparatus 310.
  • the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the first apparatus.
  • a third apparatus capable of performing any of the method 600 may comprise means for performing the respective operations of the method 600.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the third apparatus may be implemented as or included in the third apparatus 330 in FIG. 3.
  • the third apparatus comprises means for receiving, from a first apparatus via a second apparatus, a message for handover of the third apparatus from the second apparatus to the first apparatus, wherein system information is unrequired for the handover of the third apparatus and the message includes identity information of the first apparatus and excludes the system information; and means for initiating a handover execution to the first apparatus based on the message.
  • the third apparatus further comprises means for performing other operations in some example embodiments of the method 600 or the third apparatus 330.
  • the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the third apparatus.
  • FIG. 7 is a simplified block diagram of a device 700 that is suitable for implementing example embodiments of the present disclosure.
  • the device 700 may be provided to implement a communication device, for example, the mobile IAB 110, the source network node 120, the target network node 130, the terminal device 140 and/or the donor CU 150 as shown in FIG. 1.
  • the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.
  • the communication module 740 is for bidirectional communications.
  • the communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices.
  • the communication interfaces may represent any interface that is necessary for communication with other network elements.
  • the communication module 740 may include at least one antenna.
  • the processor 710 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 700 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the memory 720 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 724, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and/or optical storage.
  • Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 722 and other volatile memories that will not last in the power-down duration.
  • a computer program 730 includes computer executable instructions that are executed by the associated processor 710.
  • the instructions of the program 730 may include instructions for performing operations/acts of some example embodiments of the present disclosure.
  • the program 730 may be stored in the memory, e.g., the ROM 724.
  • the processor 710 may perform any suitable actions and processing by loading the program 730 into the RAM 722.
  • the example embodiments of the present disclosure may be implemented by means of the program 730 so that the device 700 may perform any process of the disclosure as discussed with reference to FIG. 3 to FIG. 6.
  • the example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the program 730 may be tangibly contained in a computer readable medium which may be included in the device 700 (such as in the memory 720) or other storage devices that are accessible by the device 700.
  • the device 700 may load the program 730 from the computer readable medium to the RAM 722 for execution.
  • the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • the term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
  • FIG. 8 shows an example of the computer readable medium 800 which may be in form of CD, DVD or other optical storage disk.
  • the computer readable medium 800 has the program 730 stored thereon.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium.
  • the computer program product includes computer- executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages.
  • the program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable medium, and the like.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Landscapes

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

Abstract

Les modes de réalisation donnés à titre d'exemple de la présente divulgation se rapportent à des procédés, à des dispositifs, à des appareils et à un support de stockage lisible par ordinateur de migration mobile d'accès intégré et de liaison terrestre (IAB). Dans un procédé, un premier appareil reçoit en provenance d'un deuxième appareil une demande de transfert intercellulaire d'un troisième appareil, du deuxième appareil vers le premier appareil. Le premier appareil détermine, sur la base du type du troisième appareil, que des informations système ne sont pas nécessaires pour le transfert intercellulaire du troisième appareil. Le premier appareil transmet un message au troisième appareil par l'intermédiaire du deuxième appareil, le message comprenant des informations d'identité du premier appareil et excluant les informations système.
PCT/CN2024/076468 2024-02-06 2024-02-06 Migration mobile d'accès intégré et de liaison terrestre (iab) Pending WO2025166586A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2024/076468 WO2025166586A1 (fr) 2024-02-06 2024-02-06 Migration mobile d'accès intégré et de liaison terrestre (iab)
CN202411769975.0A CN120456152A (zh) 2024-02-06 2024-12-04 移动集成接入和回程（iab）迁移

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/076468 WO2025166586A1 (fr) 2024-02-06 2024-02-06 Migration mobile d'accès intégré et de liaison terrestre (iab)

Publications (1)

Publication Number Publication Date
WO2025166586A1 true WO2025166586A1 (fr) 2025-08-14

Family

ID=96604622

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/076468 Pending WO2025166586A1 (fr) 2024-02-06 2024-02-06 Migration mobile d'accès intégré et de liaison terrestre (iab)

Country Status (2)

Country Link
CN (1) CN120456152A (fr)
WO (1) WO2025166586A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020030146A1 (fr) * 2018-08-09 2020-02-13 中兴通讯股份有限公司 Procédé et appareil d'accès à un réseau, dispositif de réseau, et support de stockage lisible par ordinateur
WO2022061780A1 (fr) * 2020-09-25 2022-03-31 Nokia Shanghai Bell Co., Ltd. Procédés, appareils et supports lisibles par ordinateur pour communication par liaison terrestre et accès intégré
US20220225392A1 (en) * 2021-01-12 2022-07-14 Lg Electronics Inc. Method and apparatus for transmitting/receiving wireless signal in wireless communication system
CN115280842A (zh) * 2020-03-13 2022-11-01 中兴通讯股份有限公司 用于在施主间迁移期间更新数据传输的方法和设备
CN116671246A (zh) * 2020-10-22 2023-08-29 谷歌有限责任公司 管理集成接入和回程移动性
US20240032129A1 (en) * 2021-03-29 2024-01-25 Kyocera Corporation Communication control method

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020030146A1 (fr) * 2018-08-09 2020-02-13 中兴通讯股份有限公司 Procédé et appareil d'accès à un réseau, dispositif de réseau, et support de stockage lisible par ordinateur
CN115280842A (zh) * 2020-03-13 2022-11-01 中兴通讯股份有限公司 用于在施主间迁移期间更新数据传输的方法和设备
WO2022061780A1 (fr) * 2020-09-25 2022-03-31 Nokia Shanghai Bell Co., Ltd. Procédés, appareils et supports lisibles par ordinateur pour communication par liaison terrestre et accès intégré
CN116671246A (zh) * 2020-10-22 2023-08-29 谷歌有限责任公司 管理集成接入和回程移动性
US20220225392A1 (en) * 2021-01-12 2022-07-14 Lg Electronics Inc. Method and apparatus for transmitting/receiving wireless signal in wireless communication system
US20240032129A1 (en) * 2021-03-29 2024-01-25 Kyocera Corporation Communication control method

Also Published As

Publication number Publication date
CN120456152A (zh) 2025-08-08

Similar Documents

Publication Publication Date Title
US20230145711A1 (en) Signaling Reduction at Handover of an IAB Node
WO2024093081A1 (fr) Dispositifs terminaux, dispositif de réseau et procédés pour des communications multi-trajets
WO2025166586A1 (fr) Migration mobile d'accès intégré et de liaison terrestre (iab)
WO2022027389A1 (fr) Mécanisme de gestion d'identité de cellule
US12127051B2 (en) Device, method, apparatus and computer readable medium for inter-master node handover
WO2022140938A1 (fr) Procédés, dispositifs et support lisible par ordinateur de communication
US20240107390A1 (en) Configuration of successful primary secondary cell change report
US20250056250A1 (en) Master node centric reference configuration generation
US20240163743A1 (en) Successful primary secondary cell changes
WO2024077470A1 (fr) Améliorations de transfert
US12507313B2 (en) Mobile terminated small data transmission bearer handling
US20250056339A1 (en) Methods, devices, apparatuses and medium for measurement-based tci state activation
WO2024227300A1 (fr) Achèvement d'une procédure de strate de non-accès dans une architecture stockage et transmission
WO2025076785A1 (fr) Création de rapport de qualité d'expérience avec des informations de transfert
WO2024207145A1 (fr) Optimisation dans un réseau d'accès et de liaison terrestre intégré
WO2024212064A1 (fr) Rapport de csi pour activation de cellule
WO2025097319A1 (fr) Fourniture de ressource préconfigurée pour une cellule cible dans un réseau non terrestre
US20250365806A1 (en) Mobile terminated small data transmission bearer handling
WO2025199930A1 (fr) Fourniture d'informations de relations de voisinage
US20250063459A1 (en) Handling conditional handover
WO2025030345A1 (fr) Mécanisme de sélection d'un dispositif de réseau non terrestre
WO2024093133A1 (fr) Dispositifs terminaux, dispositif de réseau et procédés pour des communications multi-trajets
WO2025073095A1 (fr) Indication précoce de capacités réduites
WO2025060001A1 (fr) Transfert intercellulaire dans un scénario lorsque à la fois une unité distribuée source et une unité distribuée cible sont co-localisées
US20250056358A1 (en) Conditional cell change

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

Country of ref document: EP

Kind code of ref document: A1