WO2025145587A1 - Systèmes et procédés de transfert d'informations pour systèmes de relais - Google Patents
Systèmes et procédés de transfert d'informations pour systèmes de relais Download PDFInfo
- Publication number
- WO2025145587A1 WO2025145587A1 PCT/CN2024/110026 CN2024110026W WO2025145587A1 WO 2025145587 A1 WO2025145587 A1 WO 2025145587A1 CN 2024110026 W CN2024110026 W CN 2024110026W WO 2025145587 A1 WO2025145587 A1 WO 2025145587A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- wab
- network node
- gnb
- authorization status
- indication
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
Definitions
- the disclosure relates generally to wireless communications, including but not limited to systems and methods for information transfer for relay systems.
- Coverage is a fundamental aspect of cellular network deployments.
- Mobile operators rely on different types of network nodes to offer blanket coverage in their deployments.
- new types of network nodes have been considered to increase the flexibility of mobile operators for their network deployments.
- IAB integrated access and backhaul
- Another type of network node is the RF repeater which simply amplify-and-forward any signal that they receive. RF repeaters have seen a wide range of deployments in 2G, 3G and 4G to supplement the coverage provided by regular full-stack cells.
- example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings.
- example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.
- At least one aspect is directed to a system, method, apparatus, or a computer-readable medium.
- a first component e.g., WAB-MT or WAB-gNB
- WAB-MT or WAB-gNB a network node of a wireless access and backhaul (WAB) communication system
- WAB wireless access and backhaul
- AMF access and mobility management function
- AMF access and mobility management function
- AMF access and mobility management function
- the identity information comprises at least one of: an identity of the network node, an identity of a mobile termination (MT) portion of the network node, and/or an identity of a next generation node B (gNB) portion of the network node.
- the indication can comprise at least one of: an indication of a corresponding procedure to be initiated or requested according to the authorization status information, an indication of completion of a behavior of a next generation node B (gNB) portion of the network node responsive to the authorization status information, an indication that a mobile termination (MT) portion of the network node can be or is to be de-registered, and/or an indication that a protocol data unit (PDU) session of the MT portion can be or is to be released.
- PDU protocol data unit
- the authorization status information can comprise at least one of: an indication for de-registration, an indication for protocol data unit (PDU) session release, an indication for backhaul (BH) PDU session release, and/or a WAB authorization status.
- the WAB authorization status can comprise at least one of: an authorization status of a mobile termination (MT) portion of the network node, an authorization status of a next generation node B (gNB) portion of the network node, and/or an authorization status of the network node.
- MT mobile termination
- gNB next generation node B
- the first component can comprise a mobile termination (MT) portion of the network node; the second component can comprise the MT portion of the network node; and/or the MT portion may send the indication via a de-registration or PDU session release request message.
- the first component comprises a mobile termination (MT) portion of the network node; and/or the second component comprises a next generation node B (gNB) portion of the network node.
- MT mobile termination
- gNB next generation node B
- the authorization status information of the gNB portion can comprise at least one of: a WAB authorization status, an identity of the network node, an identity of a mobile termination (MT) portion of the network node, and/or an identity of a next generation node B (gNB) portion of the network node, an indication of a corresponding procedure to be initiated or requested according to the WAB authorization status, an indication of completion of a behavior of the gNB portion of the network node responsive to the WAB authorization status, an indication that the MT portion of the network node can be or is to be de-registered, and/or an indication that a protocol data unit (PDU) session of the MT portion can be or is to be released.
- a WAB authorization status an identity of the network node
- MT mobile termination
- gNB next generation node B
- a third component of the network node can send the authorization status information to the AMF.
- the third component may comprise a mobile termination (MT) portion of the network node.
- the third component may comprise a next generation node B (gNB) portion of the network node.
- MT mobile termination
- gNB next generation node B
- a communication node that serves or is connected with the network node can send WAB mobility-related information to the network node.
- the communication node can send the WAB mobility-related information to the network node via Xn or radio resource control (RRC) signaling.
- the WAB mobility-related information can comprise at least one of: a transport network layer (TNL) address of the AMF, a TNL address of the gNB portion, an identity of the AMF, an identity of the gNB portion, a cell identifier (ID) , and/or a physical cell ID (PCI) .
- TNL transport network layer
- ID identity of the AMF
- PCI physical cell ID
- the AMF may send WAB mobility-related information to the network node; and/or the AMF may send the WAB mobility-related information to the network node via next generation (NG) or non-access stratum (NAS) signaling.
- NG next generation
- NAS non-access stratum
- a next generation node B (gNB) portion of the network node can send mobility registration update (MRU) -related information to at least one wireless communication device served by the gNB portion.
- the MRU-related information can comprise at least one of: an indication of tracking area change, an indication of MRU, and/or an indication that MRU is required.
- An access and mobility management function can send authorization status information to a first component of a network node of a wireless access and backhaul (WAB) communication system.
- the AMF can receive at least one of identity information and/or an indication associated with the authorization status information from a second component of the network node.
- FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure
- FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure
- FIG. 4 illustrates examples of UE traffic paths before and after mobile terminal (MT) migration, in accordance with some embodiments of the present disclosure.
- FIG. 5 illustrates a flow diagram of an example method for information transfer for relay systems, in accordance with some embodiments of the present disclosure.
- FIG. 1 illustrates an example wireless communication network, and/or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure.
- the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as “network 100.
- NB-IoT narrowband Internet of things
- Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101.
- the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126.
- Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.
- system 200 may further include any number of modules other than the modules shown in Figure 2.
- modules other than the modules shown in Figure 2.
- Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.
- the UE transceiver 230 may be referred to herein as an “uplink” transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232.
- a duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion.
- the BS transceiver 210 may be referred to herein as a “downlink” transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212.
- a downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion.
- the operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.
- the UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme.
- the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
- LTE Long Term Evolution
- 5G 5G
- the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example.
- eNB evolved node B
- the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc.
- PDA personal digital assistant
- the processor modules 214 and 236 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.
- a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like.
- a processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
- the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any practical combination thereof.
- the memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
- memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively.
- the memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230.
- the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively.
- Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.
- the network communication module 218 generally represents the hardware, software, firmware, processing logic, and/or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communication with the base station 202.
- network communication module 218 may be configured to support internet or WiMAX traffic.
- network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network.
- the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) .
- MSC Mobile Switching Center
- the Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems.
- the model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it.
- the OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols.
- the OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model.
- a first layer may be a physical layer.
- a second layer may be a Medium Access Control (MAC) layer.
- MAC Medium Access Control
- a third layer may be a Radio Link Control (RLC) layer.
- a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer.
- PDCP Packet Data Convergence Protocol
- a fifth layer may be a Radio Resource Control (RRC) layer.
- a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.
- NAS Non Access Stratum
- IP Internet Protocol
- the BH PDU session may be released and/or the WAB-MT may be de-registered.
- the de-registration and/or PDU session release procedure can be initiated by the UE 104 or network.
- the systems and methods of the technical solution discussed herein can determine which node decides whether to initiate/perform/execute PDU session release or de-registration procedure and how to perform/execute/initiate the corresponding procedure (e.g., PDU session release and/or de-registration) .
- the WAB-MT can send the WAB authorization status information to the co-located WAB-gNB, in response to receiving the authorization status information from the AMF.
- the WAB-gNB can perform at least one corresponding behavior, e.g., hands over the UE (s) 104 served by the WAB-gNB to one or more other cells. After the WAB-gNB completes the corresponding behavior, the WAB-gNB can inform the co-located WAB-MT of the completion of the corresponding procedures.
- the WAB-MT can send/transfer/forward the WAB authorization status information to the co-located WAB-gNB.
- the WAB-gNB can perform at least one corresponding behavior, e.g., hands over the UE (s) 104 served by the WAB-gNB to one or more other cells in response to receiving the authorization status information from the WAB-MT.
- the WAB-gNB can inform the co-located WAB-MT of the completion of the corresponding procedure.
- the MT e.g., WAB-MT
- the WAB-MT can send an indication to the MT’s AMF.
- the sent indication can be used to indicate at least one of the corresponding procedure is initiated/requested due to or because of the WAB authorization status, the completion of the WAB-gNB behavior due to the WAB authorization status, that the MT can be de-registered, and/or that the PDU session of the MT can be released, among others.
- the MT’s AMF can initiate the de-registration or PDU session release procedure for the WAB-MT according to the indication received from the WAB-MT.
- the MT’s AMF can be responsible for making the decision of whether to perform the PDU session release or de-registration procedure.
- the de-registration or PDU session release procedure can be initiated by MT’s AMF.
- the WAB-gNB e.g., alternatively to the WAB-MT
- the WAB-gNB can inform the completion of the corresponding operation to the MT’s AMF after or in response to the WAB-gNB completing a corresponding operation due to the WAB authorization, e.g., when the WAB-gNB is connected to the MT’s AMF.
- the WAB-MT can send/forward the authorization status information to the co-located WAB-gNB.
- the WAB-gNB can perform the corresponding behavior based on or according to the authorization status information, e.g., hands over the UE (s) 104 served by the WAB-gNB to one or more other cells.
- the WAB-gNB can send information to the MT’s AMF including or indicating at least one of an identity of the WAB node 302, an identity of WAB-MT, an identity of WAB-gNB, and/or an indication to indicate at least one of the completion of the WAB-gNB behavior based on the authorization status information, that the MT can be de-registered, that the PDU session of the MT can be released, etc.
- the identity of WAB-MT may be a 5G-global unique temporary identifier (GUTI) , among others.
- GUI 5G-global unique temporary identifier
- the MT’s AMF can determine whether to initiate de-registration or PDU session release procedure for the WAB-MT.
- the MT’s AMF can initiate the de-registration or PDU session release procedure for the WAB-MT according to the determination.
- the MT can be responsible for making the decision of whether to perform the PDU session release or de-registration procedure.
- the de-registration or PDU session release procedure can be initiated by MT’s AMF.
- the WAB-gNB e.g., alternatively to the WAB-MT
- the AMF can send WAB authorization status to the WAB-MT, e.g., via UE configuration update message.
- the WAB authorization status can include at least one of authorization status of the WAB-MT, authorization status of the WAB-gNB, authorization status of the WAB node 302, etc.
- the MT may determine whether to initiate the de-registration or PDU session release procedure for the WAB-MT.
- the MT may send the authorization status information to the WAB-gNB in response to receiving the authorization status information from the AMF.
- the authorization status information can include at least one of the de-registration indication, PDU session release indication, BH PDU session release indication, WAB authorization status, etc.
- the WAB authorization status can include at least one of authorization status of the WAB-MT, authorization status of the WAB-gNB, and/or authorization status of the WAB node, among others.
- the WAB-gNB can execute/perform the corresponding behavior according to the authorization status, such as handing over the UE (s) 104 served by the WAB-gNB to one or more other cells. After the WAB-gNB completes the corresponding behavior, the WAB-gNB can send information to the MT’s AMF.
- the information (sent from the WAB-gNB to the MT’s AMF) can include at least one of but not limited to the identity of WAB node, identity of WAB-MT, identity of WAB-gNB, and/or an indication to indicate at least one of the corresponding procedure is initiated/requested due to the WAB authorization status, to indicate the completion of the WAB-gNB behavior due to the WAB authorization status, to indicate that the MT can be de-registered, and/or to indicate that the PDU session of the MT can be released, etc.
- the MT’s AMF can initiate the de-registration or PDU session release procedure for the WAB-MT based on the information (or at least a portion/part of the information) from the WAB-gNB.
- the WAB-MT can make the decision (e.g., whether to perform the PDU session release procedure or the de-registration procedure) and initiate the corresponding procedure, with the WAB-MT informing the MT’s AMF.
- the WAB-gNB in response to, subsequent to, or after the WAB-gNB receives/obtains/acquires updated authorization status (e.g., according to the authorization status information) , such as from the operations, administration and maintenance (OAM) traffic, the WAB-gNB can hand over the UE(s) 104 to one or more other cells. After completing the corresponding procedure, the WAB-gNB can inform the WAB-MT of the completion of the corresponding procedure.
- OAM operations, administration and maintenance
- the WAB-MT can receive an indication of the completed corresponding procedure from the WAB-gNB. In response to completing the corresponding procedure, the WAB-MT can determine whether to initiate de-registration or BH PDU session release procedure.
- the WAB-MT e.g., MT portion of the network node
- the WAB-MT can initiate/perform the corresponding procedure (e.g., de-registration or PDU session release procedure) and send the (e.g., WAB) authorization status information to the MT’s AMF, e.g., via a cause value during the de-registration or BH PDU session release procedure.
- the MT’s AMF can make the decision (e.g., whether to initiate the de-registration or PDU session release procedure) and initiate the corresponding procedure, with the WAB-MT informing the AMF.
- the WAB-gNB can hand over the UE (s) 104 to one or more other cells.
- the WAB-gNB can inform the WAB-MT of the completion of the corresponding procedure.
- the WAB-MT can receive the indication that the WAB-gNB completed the corresponding procedure.
- the WAB-MT can send the authorization status information to the MT’s AMF.
- the authorization status information can include at least one of WAB authorization status, identity of WAB node, identity of WAB-MT, identity of WAB-gNB, and/or an indication to indicate at least one of the corresponding procedure is initiated/requested due to the WAB authorization status, the completion of the WAB-gNB behavior due to the WAB authorization status, that the MT can be de-registered, and/or that the PDU session of the MT can be released, etc.
- the MT’s AMF can determine whether to initiate the de-registration or PDU session release procedure for the WAB-MT in response to or after receiving the authorization status information from the WAB-MT.
- the MT’s AMF can initiate the de-registration or PDU session release procedure for the WAB-MT based on the determination.
- the WAB-MT can make the decision and initiate the corresponding procedure, with the WAB-gNB informing the MT’s AMF. For example, after the WAB-gNB obtains the updated authorization status, e.g., from the OAM, the WAB-gNB can hand over the UE (s) 104 to one or more other cells. Subsequent to the WAB-gNB completing/finishing the corresponding procedure, the WAB-gNB can inform the WAB-MT of the completion. The WAB-MT can determine whether to initiate de-registration or BH PDU session release procedure in response to receiving the completion indication.
- the WAB-MT can inform the WAB-gNB of the decision via decision information, e.g., whether to initiate de-registration or BH PDU session release procedure.
- the WAB-gNB can send the authorization status information to the WAB-MT’s AMF.
- the authorization status information can include at least one of identity of WAB node, identity of WAB-MT, identity of WAB-gNB, WAB authorization status, de-registration indication (e.g., an indication of whether to use the de-registration procedure) , and/or PDU session release indication (e.g., an indication of whether to use the PDU session release procedure) , etc.
- the MT’s AMF can initiate the de-registration or PDU session release procedure for the WAB-MT.
- the WAB-MT when the WAB node 302 moves/relocates/repositions, the WAB-MT can be migrated to another donor node.
- the co-located WAB-gNB may connect to another AMF (e.g., AMF serving the UE (s) 104 different from the AMF serving the WAB-MT) .
- AMF serving the UE (s) 104 different from the AMF serving the WAB-MT
- the systems and methods of the technical solution discussed herein can provide features, operations, or techniques for triggering the WAB-gNB to establish next generation (NG) or Xn interface with new AMF (s) .
- the WAB-gNB can be triggered by the BH gNB (e.g., the BS 102, TRP, or wireless communication node) , for instance, to establish the NG/XN interface with one or more new AMFs.
- the BS 102 e.g., gNB, wireless communication node (or communication node) , or TRP
- the WAB node 302 e.g., network node
- the WAB node 302 can send/provide/transmit/communicate/signal WAB mobility-related information to the WAB node, e.g., via Xn and/or RRC message, among other types of signalings or messages.
- the UE’s AMF may be changed (e.g., change to a local AMF when entering a new territory or location) , for instance, based on the current location of the WAB node 302 and/or additional, alternative, or other criteria.
- the TAC of the WAB-gNB may change to trigger the mobility registration update (MRU) procedure of the UE (s) 104 served by the WAB-gNB, such that the UE’s AMF can be re-allocated during the MRU procedure.
- MRU mobility registration update
- the MRU procedure may be initiated when the UE 104 moves/relocates/repositions to a new tracking area (TA) , position, or location outside the UE’s registration area (RA) . In such cases, the MRU procedure may not be initiated when the new TAC of the WAB-gNB is in the UE’s registration area.
- the systems and methods of the technical solution discussed herein can provide features, operations, or techniques for triggering the MRU procedure for the UE (s) 104, e.g., when the new TAC of the WAB-gNB is in the UE’s registration area.
- an AMF can send/transmit/provide/communicate authorization status information to a first component (e.g., MT portion or gNB portion) of a network node (e.g., WAB node or WAB donor) of a WAB communication system.
- the wireless access and backhaul communication system may refer to or be described in conjunction with but not limited to the architecture 300 of FIG. 3, for example.
- the network node may be in communication with at least one of one or more other network nodes, at least one wireless communication device (e.g., UE) , or at least one donor node.
- the first component of the network node can receive/obtain/acquire the authorization status information from the AMF.
- the authorization status information may sometimes be referred to as WAB authorization status information or authorization status-related information.
- the network node can obtain its authorization status from the AMF.
- the identity information can comprise/include at least one of an identity of the network node (e.g., WAB node) , an identity of a mobile termination (MT) portion of the network node (e.g., WAB-MT) , and/or an identity of a next generation node B (gNB) portion of the network node (e.g., WAB-gNB) .
- the identify information can assist the AMF with determining which network node to initiate the de-registration or PDU session release procedure for.
- the indication can comprise at least one of: an indication of a corresponding procedure to be initiated or requested according to the authorization status information, an indication of completion of a behavior of a next generation node B (gNB) portion of the network node responsive to the authorization status information, an indication that a mobile termination (MT) portion of the network node can be or is to be de-registered, and/or an indication that a protocol data unit (PDU) session of the MT portion can be or is to be released.
- the indication of the corresponding procedure to be initiated or requested according to the authorization status information can provide the AMF with the reason or cause value of the procedure.
- the indication of completion of the behavior can indicate to the AMF that the operation of the WAB-gNB has been completed, such that the AMF can initiate the de-registration or PDU session release procedure.
- the indication that the MT portion of the network node can be or is to be de-registered can indicate which procedure is selected by the WAB-node if the WAB-node is responsible for making the decision, or indicate that the operation of the WAB-gNB has completed so that the AMF can initiate the corresponding procedure.
- the authorization status information comprises at least one of: an indication for de-registration, an indication for protocol data unit (PDU) session release, an indication for backhaul (BH) PDU session release, and/or a WAB authorization status.
- the authorization status information can be provided to indicate the authorization status or indicate which procedure to be initiated by the MT, for example.
- the WAB authorization status can comprise at least one of an authorization status of a mobile termination (MT) portion of the network node, an authorization status of a next generation node B (gNB) portion of the network node, and/or an authorization status of the network node.
- MT mobile termination
- gNB next generation node B
- the first component can include a mobile termination (MT) portion of the network node; the second component can include the MT portion of the network node; and/or the MT portion can send the indication via a de-registration or PDU session release request message (e.g., as described in conjunction with at least one of but not limited to example configuration 1 or 3 of example implementation 1) .
- the at least one of: the first component comprises a mobile termination (MT) portion of the network node; and/or the second component comprises a next generation node B (gNB) portion of the network node (e.g., as described in conjunction with at least one of but not limited to example configuration 5 of example implementation 1) .
- gNB next generation node B
- the authorization status information of the gNB portion can comprise at least one of: a WAB authorization status, an identity of the network node, an identity of a mobile termination (MT) portion of the network node, and/or an identity of a next generation node B (gNB) portion of the network node, an indication of a corresponding procedure to be initiated or requested according to the WAB authorization status, an indication of completion of a behavior of the gNB portion of the network node responsive to the WAB authorization status, an indication that the MT portion of the network node can be or is to be de-registered, and/or an indication that a protocol data unit (PDU) session of the MT portion can be or is to be released.
- a WAB authorization status an identity of the network node
- MT mobile termination
- gNB next generation node B
- a third component of the network node may send the authorization status information to the AMF, such as described in conjunction with but not limited to example implementation 2.
- the third component of the network node may include or correspond to a mobile termination (MT) portion of the network node, such as described in conjunction with example configuration 1 or 2 of example implementation 2.
- the third component can comprise or correspond to a next generation node B (gNB) portion of the network node, such as described in conjunction with example configuration 3 or 4 of example implementation 2.
- MT mobile termination
- gNB next generation node B
- the third component can provide the authorization status information to the AMF, for instance, for the AMF to know the authorization status of the WAB-gNB or WAB-MT and/or to indicate the completion of the WAB-gNB operation and/or to indicate which procedure (e.g., de-registration or PDU session release procedure) can be initiated.
- the AMF can know the authorization status of the WAB-gNB or WAB-MT and/or to indicate the completion of the WAB-gNB operation and/or to indicate which procedure (e.g., de-registration or PDU session release procedure) can be initiated.
- any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as “software” or a “software module) , or any combination of these techniques.
- firmware e.g., a digital implementation, an analog implementation, or a combination of the two
- firmware various forms of program or design code incorporating instructions
- software or a “software module”
- a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.
- Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
- a storage media can be any available media that can be accessed by a computer.
- such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
- module refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according to arrangements of the present solution.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
L'invention concerne des systèmes et des procédés de transfert d'informations pour des systèmes de relais. Un premier composant d'un noeud de réseau d'un système de communication WAB (backhaul et accès sans fil) peut recevoir des informations d'état d'autorisation en provenance d'une fonction de gestion de l'accès et de la mobilité (AMF). Un second composant du noeud de réseau peut envoyer des informations d'identité et/ou une indication associée aux informations d'état d'autorisation à l'AMF.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2024/110026 WO2025145587A1 (fr) | 2024-08-06 | 2024-08-06 | Systèmes et procédés de transfert d'informations pour systèmes de relais |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2024/110026 WO2025145587A1 (fr) | 2024-08-06 | 2024-08-06 | Systèmes et procédés de transfert d'informations pour systèmes de relais |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2025145587A1 true WO2025145587A1 (fr) | 2025-07-10 |
Family
ID=96299966
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2024/110026 Pending WO2025145587A1 (fr) | 2024-08-06 | 2024-08-06 | Systèmes et procédés de transfert d'informations pour systèmes de relais |
Country Status (1)
| Country | Link |
|---|---|
| WO (1) | WO2025145587A1 (fr) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20210105622A1 (en) * | 2019-08-26 | 2021-04-08 | Samsung Electronics Co., Ltd. | Method and apparatus for authentication of integrated access and backhaul (iab) node in wireless network |
| CN117178576A (zh) * | 2023-06-21 | 2023-12-05 | 北京小米移动软件有限公司 | 授权方法及其装置 |
-
2024
- 2024-08-06 WO PCT/CN2024/110026 patent/WO2025145587A1/fr active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20210105622A1 (en) * | 2019-08-26 | 2021-04-08 | Samsung Electronics Co., Ltd. | Method and apparatus for authentication of integrated access and backhaul (iab) node in wireless network |
| CN117178576A (zh) * | 2023-06-21 | 2023-12-05 | 北京小米移动软件有限公司 | 授权方法及其装置 |
Non-Patent Citations (1)
| Title |
|---|
| STEVEN XU, NOKIA, NOKIA SHANGHAI BELL: "Discussion on WAB integration and mobility", 3GPP DRAFT; R3-243352; TYPE DISCUSSION; FS_NR_WAB_5GFEMTO, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Fukuoka City, Fukuoka, JP; 20240520 - 20240524, 10 May 2024 (2024-05-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052603723 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20240381223A1 (en) | Systems and methods for mobile node inter-cu migration | |
| US20240187880A1 (en) | Systems and methods for configuration information transfer | |
| US20250016643A1 (en) | Systems and methods for inter-donor migration and apparatus | |
| US20250113263A1 (en) | Inter-donor migration for integrated access and backhaul (iab) nodes | |
| US20250008385A1 (en) | Systems and methods for inter-donor migration and apparatus | |
| CN113261340A (zh) | 传输信息的方法、终端设备、基站和核心网设备 | |
| US20240188157A1 (en) | Systems and methods for establishing shared n3 tunnel | |
| US20240430851A1 (en) | Systems and methods for authorization configuration in device-to-device communications | |
| WO2025145587A1 (fr) | Systèmes et procédés de transfert d'informations pour systèmes de relais | |
| US20240298376A1 (en) | Systems and methods for successful handover reporting | |
| WO2025065621A1 (fr) | Systèmes et procédés de migration inter-donneurs | |
| WO2024026875A1 (fr) | Systèmes et procédés de configuration de multi-rat à double connectivité (mrdc) de véhicule aérien sans pilote (uav) | |
| US20240340632A1 (en) | Systems and methods for identifying subscription-based unmanned aerial vehicle (uav) | |
| AU2021459631B2 (en) | Systems and methods for establishing shared n3 tunnel | |
| WO2025137827A1 (fr) | Systèmes et procédés de transfert d'informations pour systèmes de relais | |
| WO2024230030A1 (fr) | Systèmes et procédés de transfert | |
| WO2024103656A1 (fr) | Procédé de configuration de faisceau et appareil associé | |
| WO2024216823A1 (fr) | Systèmes et procédés de transfert | |
| WO2024169004A1 (fr) | Systèmes et procédés de réactivation d'une session d'unité de données de protocole (pdu) pour remplacement de nom de réseau de données (dnn) | |
| US12501435B2 (en) | Data forwarding for user equipment with data transmission | |
| WO2024065245A1 (fr) | Systèmes et procédés de transfert d'informations dans un système iab et appareil | |
| WO2024026876A1 (fr) | Systèmes et procédés de configuration de service de véhicule aérien sans pilote (uav) entre des systèmes et dans un système avec différentes technologies d'accès radioélectriques (rat) |
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: 24914809 Country of ref document: EP Kind code of ref document: A1 |