[go: up one dir, main page]

WO2025137827A1 - 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 PDF

Info

Publication number
WO2025137827A1
WO2025137827A1 PCT/CN2023/141591 CN2023141591W WO2025137827A1 WO 2025137827 A1 WO2025137827 A1 WO 2025137827A1 CN 2023141591 W CN2023141591 W CN 2023141591W WO 2025137827 A1 WO2025137827 A1 WO 2025137827A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
information
traffic
donor
network
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/CN2023/141591
Other languages
English (en)
Inventor
Ying Huang
Lin Chen
Tao Qi
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.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to PCT/CN2023/141591 priority Critical patent/WO2025137827A1/fr
Publication of WO2025137827A1 publication Critical patent/WO2025137827A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations

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 network node e.g., wireless access and backhaul (WAB) node or WAB donor
  • WAB wireless access and backhaul
  • the network node can perform/initiate/execute mapping of one or more packets of non-user plane (UP) traffic, using the traffic mapping information.
  • UP non-user plane
  • non-UP traffic can comprise at least one of: next generation control plane interface (NG-C) traffic, Xn control plane interface (Xn-C) traffic, and/or operations, administration and maintenance (OAM) traffic.
  • N-C next generation control plane interface
  • Xn-C Xn control plane interface
  • OAM operations, administration and maintenance
  • the traffic mapping information can be configured by or received from a session management function (SMF) or access management function (AMF) .
  • SMF session management function
  • AMF access management function
  • the traffic mapping information can comprise at least one of: a quality of service (QoS) flow identifier (QFI) , a protocol data unit (PDU) session identifier (ID) , a non-UP traffic type, a priority, an evolved radio access bearer (E-RAB) ID, internet protocol (IP) related information, and/or a data radio bearer (DRB) ID.
  • QoS quality of service
  • PDU protocol data unit
  • ID session identifier
  • non-UP traffic type can comprise at least one of: user equipment (UE) associated NG-C, non-UE-associated NG-C, UE-associated Xn-C, non-UE-associated Xn-C, non-UP traffic, and/or OAM traffic.
  • UE user equipment
  • the IP related information can include at least one of: an IP address, a differentiated services codepoint (DSCP) , and/or a flow label.
  • the network node can perform mapping of at least one of: the one or more packets of non-UP traffic, to at least one of: one or more QoS flows, an E-RAB, and/or a DRB, using the traffic mapping information.
  • the network node can send donor node information via an Xn application protocol (XnAP) or RRC message.
  • XnAP Xn application protocol
  • the network node may send/transmit/provide/forward donor node information via a next generation application protocol (NGAP) message.
  • NGAP next generation application protocol
  • the donor node information can comprise at least one of: information of the network node, information of a child node of the network node, information of a parent node of the network node, and/or information of a donor node.
  • the network node may send network node information to a donor node and/or a WAB node.
  • the network node can receive a response message comprising at least one of: a gNodeB (gNB) identifier (ID) , a cell ID, an IP address, a cell radio network temporary identifier (C-RNTI) , an information of a child WAB node, and/or an Xn application protocol (XnAP) ID, of the donor node or the WAB node, from the donor node or the WAB node.
  • gNB gNodeB
  • ID gNodeB
  • C-RNTI cell radio network temporary identifier
  • XnAP Xn application protocol
  • the network node information can comprise at least one of: an IP address, a cell radio network temporary identifier (C-RNTI) , a Xn application protocol (XnAP) identifier (ID) , information of a child node, and/or information of a parent node.
  • the network node information can comprise at least one of: a gNB ID, a cell ID, an IP address, information of a child node, and/or information of a parent node, of the network node.
  • the network node can send at least one of parent node information and/or child node information, to a donor node and/or a WAB node.
  • the network node may receive topology information comprising at least one of: an IP address, and/or a next hop identifier (ID) from the donor node and/or the WAB node.
  • ID next hop identifier
  • the next hop ID can comprise at least one of: a gNodeB (gNB) identifier (ID) , the IP address, a cell radio network temporary identifier (C-RNTI) , and/or an Xn application protocol (XnAP) ID, of at least one of a parent node and/or a child node of the WAB node, and/or the donor node.
  • gNB gNodeB
  • ID gNodeB
  • C-RNTI cell radio network temporary identifier
  • XnAP Xn application protocol
  • At least one aspect is directed to a system, method, apparatus, or a computer-readable medium.
  • a core network function e.g., access management function (AMF) , session management function (SMF) , etc.
  • AMF access management function
  • SMF session management function
  • CP control plane
  • 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 a flow diagram of an example method for information transfer for relay systems, in accordance with some embodiments of the present disclosure.
  • 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.
  • the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104.
  • the BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively.
  • Each radio frame 118/124 may be further divided into sub-frames 120/127 which may include data symbols 122/128.
  • the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.
  • FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution.
  • the system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein.
  • system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of FIG. 1, as described above.
  • 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 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 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
  • a wireless access and backhaul architecture e.g., integrated access and backhaul (IAB) or wireless access and backhaul (WAB)
  • IAB integrated access and backhaul
  • WAB wireless access and backhaul
  • NR new radio
  • Supporting the wireless access and backhauling can allow/enable flexible and relatively dense deployment of NR cells, and reduce/minimize wireline transport infrastructure, for example.
  • a relay node such as an IAB node or WAB node, among other types of compatible nodes, can support access and backhauling via NR.
  • the terminating node of NR backhauling on the network side can be referred to as a donor node.
  • the donor node can represent a BS 102 (e.g., gNB, wireless communication node, or transmission and reception point (TRP) ) with one or more functionalities to support or allow wireless access and backhaul.
  • Backhauling can occur via a single hop or multiple hops.
  • An example architecture of the wireless access and backhaul can be described in conjunction with but not limited to FIG. 3.
  • FIG. 3 illustrates an example wireless access and backhaul architecture 300, in accordance with some embodiments of the present disclosure.
  • the exemplary wireless access and backhaul architecture 300 can include at least one UE 104, at least one donor node 302, and relay nodes 304a-c (e.g., sometimes referred to as relay node (s) 304) .
  • the exemplary wireless access and backhaul architecture 300 can include more or fewer components or devices, such as more or fewer relay nodes 304, not limited to three relay nodes 304, as described in conjunction with FIG. 3, for example.
  • the donor node 302 can correspond to the BS 102.
  • the donor node 302 can be in communication with other devices (e.g., network devices) , such as a core network function (e.g., access management function (AMF) , session management function (SMF) , etc. ) .
  • a core network function e.g., access management function (AMF) , session management function (SMF) , etc.
  • the relay nodes 304a-c can be referred to as relay node 1, relay node 2, and relay node 3, respectively, for purposes of examples herein.
  • the relay nodes 304 that are relatively closer to the donor node 302 can be the parent of the relay nodes 304 further from the donor node 302 (or closer to the UE 104) , or vice versa in some arrangements.
  • the relay node 2 can be the parent node of relay node 1, e.g., relay node 1 can be the child node of relay node 2.
  • the relay node 3 can be the parent node of relay node 2, e.g., relay node 2 can be the child node of relay node 3.
  • the relay node 304 can include, support, or be configured with gNB functionality (e.g., functionalities similar to the BS 102) .
  • the gNB functionality can include at least one of but is not limited to a function to terminate the NR access interface to one or more UEs 104 and/or a function to terminate the Xn/next generation (NG) protocol to the donor node 302 and/or the core network function (e.g., AMF, SMF, etc. ) .
  • the relay node 304 can include, support, or be configured with a subset of the UE functionality (e.g., sometimes referred to as MT) .
  • the UE functionality can include at least one of but is not limited to physical layer, layer-2, radio resource control (RRC) , and/or non access stratum (NAS) functionality to connect to another relay node 304, the donor node 302, and/or to the core network, among other functionalities, for example.
  • RRC radio resource control
  • NAS non access stratum
  • CP control plane
  • the systems and methods of the technical solution discussed herein can provide features or configurations for supporting non-user plane (UP) traffic mapping for the (e.g., wireless) relay nodes 304.
  • UP non-user plane
  • the traffic (e.g., packets or signals) may be transferred/sent/communicated/forwarded via one or multiple backhaul links between the WAB node and the donor node 302 (e.g., the BS 102 or gNB) .
  • the traffic can include at least one of user plane (UP) traffic, control plane (CP) traffic (e.g., Xn control plane interface (Xn-C) traffic and/or next generation control plane interface (NG-C) traffic) , and/or operations, administration and maintenance (OAM) traffic, among other types of traffic.
  • UP user plane
  • CP control plane
  • Xn-C control plane interface
  • N-C next generation control plane interface
  • OAM operations, administration and maintenance
  • the traffic can be routed/transferred via one or multiple protocol data unit (PDU) sessions to the user plane function (UPF) of the MT in the WAB donor.
  • PDU protocol data unit
  • UPF user plane function
  • the UPF of the MT e.g., in the WAB donor
  • IP internet protocol
  • quality of service (QoS) flow may not be utilized/used for transferring the control plane signaling (e.g., packets or traffic) .
  • QoS Flow level QoS parameters configured for non-UP traffic (e.g., CP traffic, etc. ) at NG RAN node.
  • the systems and methods of the technical solution can provide features for configuring the traffic mapping for CP traffic (or other non-UP traffic) at the NG-RAN node (e.g., the gNB in the relay node 304) and/or the donor node 302.
  • the donor node 302 can include the functionality of the NG-RAN node and/or UPF.
  • the NG-RAN node may be a part of the donor node 302.
  • the donor node 302 can receive/obtain/acquire packets from the AMF of the UE 104 in the core network and/or from other NG-RAN nodes or OAMs. Then, the donor node 302 can map the received IP packets to the QoS flows according to or based on one or more packet detection rules (PDRs) .
  • PDRs packet detection rules
  • the PDR can include classifying incoming data packets by the UPF based on packet filter sets of the downlink (DL) PDRs.
  • the PDR can include other criteria or parameters.
  • the UPF can send/transmit the PDUs of the PDU session in a tunnel between a core network (e.g., 5GC) and the (radio) access network ( (R) AN) .
  • the UPF may include at least a QoS flow identifier (QFI) in the next generation application protocol (NGAP) general packet radio service (GPRS) tunneling protocol-user plane (GTP-U) header.
  • NGAP next generation application protocol
  • GPRS general packet radio service tunneling protocol-user plane
  • the donor node 302 can send/deliver the packets to its co-located MT’s UPF.
  • the MT’s UPF can map the IP packets generated by the donor node 302 to QoS flows as discussed herein.
  • the donor node 302 (e.g., a first network node or WAB) can determine the next hop for the packets.
  • the next hop for the packets can refer to the next relay node 304 or network node for the donor node 302 to transmit the packets.
  • the determination of the next hop can be described in conjunction with but not limited to exemplary implementations 4 and/or 5, for example.
  • traffic mapping information used for non-UP traffic can be configured by the core network function (e.g., SMF and/or AMF) at NG-RAN node (e.g., the gNB portion of the WAB node/WAB donor) .
  • the non-UP traffic can include at least one of NG-C signaling/traffic, Xn-C traffic, and/or OAM traffic, among others.
  • the donor node 302 can receive/obtain the traffic mapping information from at least one of the core network functions (e.g., SMF and/or AMF) .
  • the traffic mapping information can include at least one of QoS flow identifier (QFI) , PDU session ID, non-UP traffic type, priority, evolved radio access bearer (E-RAB) ID, etc.
  • the non-UP traffic type can include at least one of but not limited to UE-associated NG-C, non-UE-associated NG-C, UE-associated Xn-C, non-UE-associated Xn-C, non-UP traffic, and/or OAM traffic, to name a few.
  • the NG-RAN node e.g., the gNB portion of the WAB node/WAB donor
  • the NG-RAN node can perform/execute/initiate mapping for the PDUs (e.g., packets from QoS Flows to data radio bearer DRB) based on, according to, or using the traffic mapping information configured by the core network function (e.g., AMF and/or SMF, etc. ) .
  • the core network function e.g., AMF and/or SMF, etc.
  • the QoS flow may not be used for transferring the control plane signaling (e.g., packets or traffic) .
  • the systems and methods of the technical solution can provide features for configuring the traffic mapping for CP traffic (or other non-UP traffics) at the NG-RAN node and/or the donor node 302.
  • the systems and methods of exemplary implementation 2 can be described in conjunction with but not limited to the exemplary implementation 1.
  • the mapping information can be configured at the relay node 304 (e.g., IAB node and/or WAB node) and/or the donor node 302.
  • the WAB node may be provided as an example relay node 304, it should be understood that other relay nodes 304 can be provided herein, not limited to the WAB node.
  • the AMD or the SMF is provided as an example core network function, it should be understood that other core network functions not limited to the AMF or the SMF can be provided herein, for example.
  • the WAB node and/or the donor node can obtain/receive mapping configuration (e.g., traffic mapping information) from the AMF and/or SMF (e.g., the core network function) .
  • the mapping configuration can include at least one of but is not limited to IP related information, QFI, PDU session ID, E-RAB ID, DRB ID, etc.
  • the IP related information can include at least one of but not limited to an IP address, a differentiated services codepoint (DSCP) , and/or a flow label.
  • DSCP differentiated services codepoint
  • the mapping information may be used to perform a mapping from IP, DSCP, and/or flow label to the QFI, from QFI to E-RAB and/or DRB, and/or from the IP, DSCP, and/or flow label to E-RAB and/or DRB, among others.
  • the donor node 302 can obtain one or more packets from the AMF of the UE 104 or other NG-RAN nodes (e.g., the gNB functionality of at least one of the relay nodes 304) .
  • the donor node 302 can determine the next hop (e.g., which of the WAB nodes) to forward the packets (or to receive the packets from the donor node 302) .
  • the determination of the next hop can be described in conjunction with but not limited to exemplary implementation 4 and/or 5, for example.
  • the donor node 302 can map at least one of one or more IP packets to at least one of the QoS flows, E-RAB, and/or DRB, etc., of the determined WAB node (e.g., the next hop) according to the configured mapping configuration (e.g., traffic mapping information) .
  • the configured mapping configuration e.g., traffic mapping information
  • the donor node 302 can determine the next hop for receiving the packets.
  • the next hop may be determined as the relay node 3, for example.
  • the donor node 302 in response to the determination, can map the IP packets to QoS flows, E-RAB, DRB, etc., of the relay node 3 according to the configured mapping configuration.
  • the core network function (e.g., AMF and/or SMF) may be connected to multiple donor nodes 302 simultaneously.
  • the systems and methods of the technical solution discussed herein can provide features or techniques for determining or identifying the donor node 302 that is connected to the desired relay node 304, such that the core network function can send the NG signaling (or other types of signalings) for the relay node 304 to the corresponding donor node 302.
  • the systems and methods can perform these features or techniques for the exemplary implementations 1 and/or 2, for example.
  • the relay node 304 can send/transmit/provide donor node information via a next generation application protocol (NGAP) message (e.g. NG setup request message) to the core network function (e.g., AMF) .
  • NGAP next generation application protocol
  • the relay node 304 may send the donor node information via at least one of an Xn message and/or an RRC message (or other types of messages or signalings) to at least one of the donor node, the parent node, the child node, the neighboring WAB node, and/or the neighboring donor node, among others.
  • the donor node information can include at least one of but not limited to information of the network node (e.g., relay node 304) including the WAB node, information of the donor node 302.
  • the information of the relay node 304 and/or the donor node 302 can include at least one of gNB ID, cell ID, IP address, etc.
  • the relay node 304 can communicate with the core network function (e.g., for sending the donor node information) via the corresponding donor node 302. For example, the relay node 304 can send the donor node information to the core network function via the donor node 302. In some configurations, the relay node 304 may send an indication to (or notify) the donor node 302 to send its information (e.g., the donor node information) to the core network function.
  • the donor node 302 can be an intermediary device between the one or more relay nodes 304 and the core network function, for example.
  • the core network function can store the donor node information received/obtained from the relay node 304 or the donor node 302.
  • the core network function can determine the donor node 302 associated with the desired relay node 304 according to the donor node information, e.g., when sending NG signaling for the relay node 304 (e.g., IAB node and/or WAB node) .
  • the donor node information e.g., when sending NG signaling for the relay node 304 (e.g., IAB node and/or WAB node) .
  • the systems and methods of the technical solution can provide features or operations discussed herein for the donor node 302 and/or the relay node 304 (e.g., IAB node or WAB node) to determine the next hop (e.g., another relay node 304 or donor node 302) for sending or to receive the DL packets, such as for a one-hop case/scenario.
  • the systems and methods of the technical solution can provide features or operations for the donor node 302 and/or the relay node 304 to identify or determine the (co-) location of the MT and/or gNB parts (e.g., to perform UE functionalities or gNB functionalities, respectively) of the relay node 304.
  • the relay node 304 can send its information (e.g., the relay node information, such as at least one of but not limited to IP address, C-RNTI, XnAP ID, parent WAB node information, etc. ) in the XnAP (e.g., Xn setup request) message (or other signalings/messages) to the donor node 302 and/or one or more other relay nodes 304.
  • the relay node 304 can send other information, such as information related to the child WAB node, etc., to the donor node 302 and/or the one or more other relay nodes 304.
  • the parent relay node information may include at least one of gNB ID, cell ID, and/or IP address, among others.
  • the donor node 302 or the one or more other relay nodes 304 may send its information in the XnAP message (e.g., response message) to the relay node 304.
  • the information from the donor node 302 or the one or more other relay nodes 304 may include at least one of gNB ID, cell ID, IP address, C-RNTI, XnAP ID, and/or child WAB node information, or other types of information.
  • the systems and methods of the technical solution can provide features or operations discussed herein for the donor node 302 and/or the relay node 304 (e.g., IAB node or WAB node) to determine the next hop (e.g., another relay node 304 or donor node 302) for sending or to receive the DL packets, such as for a multi-hop case/scenario.
  • the systems and methods of the technical solution can provide features or operations for the donor node 302 and/or the relay node 304 to identify or determine the (co-) location of the MT and/or gNB parts of the relay node 304.
  • the features or operations of the exemplary implementation 5 may be described additionally or alternatively to the exemplary implementation 4, for example.
  • the relay node 304 may send the parent node information to the donor node 302 and/or the child relay node via RRC signaling, Xn signaling (e.g., XnAP message) , or other types of signalings.
  • relay node 2 may send information related to relay node 3 to at least one of the donor node 302 and/or relay node 1, which is the child relay node of relay node 2.
  • the relay node 304 may send the child node information to the parent relay node and/or the donor node 302 and/or send the parent node information to the child relay node and/or the donor node 302.
  • relay node 2 may send information related to relay node 3 to at least one of the donor node 302 and/or relay node 1 or send information related to relay node 1 to at least one of the donor node 302 and/or relay node 3.
  • the information of the parent relay node and/or the child relay node can include at least one of gNB ID, cell ID, IP address, C-RNTI, XnAP ID, etc.
  • non-UP traffic can include at least one of: next generation control plane interface (NG-C) traffic, Xn control plane interface (Xn-C) traffic, and/or operations, administration and maintenance (OAM) traffic, among others.
  • NG-C next generation control plane interface
  • Xn-C Xn control plane interface
  • OAM operations, administration and maintenance
  • the traffic mapping information can be configured by or received from a session management function (SMF) or access management function (AMF) .
  • SMF session management function
  • AMF access management function
  • the network node can perform mapping of at least one of: the one or more packets of non-UP traffic, to at least one of: one or more QoS flows, an E-RAB, and/or a DRB, using the traffic mapping information.
  • the network node can send donor node information via at least one of an Xn application protocol (XnAP) (e.g., Xn message) and/or RRC message, among other types of messages or signalings, to the donor node, the parent node, the child node, the neighboring WAB node, and/or the neighboring donor node, for example.
  • XnAP Xn application protocol
  • RRC Radio Resource Control
  • the network node can send at least one of parent node information and/or child node information, to a donor node or a WAB node (e.g., child node, parent node, or neighbor node) .
  • the WAB node may be a second network node.
  • the network node can send the parent node information if the WAB node is a child node (e.g., child network node or child relay node) of the network node.
  • the network node can send the child node information if the WAB node is a parent node (e.g., parent network node or parent relay node) of the network node.
  • any reference to an element herein using a designation such as “first, ” “second, ” and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • 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 arrangements of the present solution.
  • memory or other storage may be employed in arrangements of the present solution.
  • memory or other storage may be employed in arrangements of the present solution.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
  • references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

  • Engineering & Computer Science (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 nœud de réseau d'un système de communication d'accès et de liaison terrestre sans fil peut recevoir des informations de mise en correspondance de trafic. Le nœud de réseau peut effectuer une mise en correspondance d'un ou de plusieurs paquets de trafic de non-UP (plan d'utilisateur), à l'aide des informations de mise en correspondance de trafic.
PCT/CN2023/141591 2023-12-25 2023-12-25 Systèmes et procédés de transfert d'informations pour systèmes de relais Pending WO2025137827A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/141591 WO2025137827A1 (fr) 2023-12-25 2023-12-25 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/CN2023/141591 WO2025137827A1 (fr) 2023-12-25 2023-12-25 Systèmes et procédés de transfert d'informations pour systèmes de relais

Publications (1)

Publication Number Publication Date
WO2025137827A1 true WO2025137827A1 (fr) 2025-07-03

Family

ID=96216277

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/141591 Pending WO2025137827A1 (fr) 2023-12-25 2023-12-25 Systèmes et procédés de transfert d'informations pour systèmes de relais

Country Status (1)

Country Link
WO (1) WO2025137827A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113728720A (zh) * 2018-11-01 2021-11-30 中兴通讯股份有限公司 用于集成接入和回程链路的承载映射
US20220248495A1 (en) * 2019-05-02 2022-08-04 Telefonaktiebolaget Lm Ericsson (Publ) Bearer mapping in iab nodes
US20220264602A1 (en) * 2019-11-07 2022-08-18 Huawei Technologies Co., Ltd. Communication method and apparatus
US20220377595A1 (en) * 2019-07-09 2022-11-24 Telefonaktiebolaget Lm Ericsson (Publ) Mapping Information for Integrated Access and Backhaul

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113728720A (zh) * 2018-11-01 2021-11-30 中兴通讯股份有限公司 用于集成接入和回程链路的承载映射
US20220248495A1 (en) * 2019-05-02 2022-08-04 Telefonaktiebolaget Lm Ericsson (Publ) Bearer mapping in iab nodes
US20220377595A1 (en) * 2019-07-09 2022-11-24 Telefonaktiebolaget Lm Ericsson (Publ) Mapping Information for Integrated Access and Backhaul
US20220264602A1 (en) * 2019-11-07 2022-08-18 Huawei Technologies Co., Ltd. Communication method and apparatus

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Bearer mapping for control plane signalling", 3GPP DRAFT; R2-1905105 BEARER MAPPING FOR CONTROL PLANE SIGNALLING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Xi’an, China; 20190408 - 20190412, 6 April 2019 (2019-04-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051702382 *
ZTE: "Consideration on control plane bearer mapping", 3GPP DRAFT; R2-1906553 DISCUSSION ON CONTROL PLANE BEARER MAPPING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051730014 *

Similar Documents

Publication Publication Date Title
US20150016330A1 (en) Multi-directional relay architecture and apparatus and methods of operation useful in conjunction therewith
US20240187880A1 (en) Systems and methods for configuration information transfer
US20250106105A1 (en) Configuring for mobile relay nodes with user plane functions
US20250016643A1 (en) Systems and methods for inter-donor migration and apparatus
US20250113263A1 (en) Inter-donor migration for integrated access and backhaul (iab) nodes
US20250280350A1 (en) Systems and methods for device-to-device relay communications
US20250008385A1 (en) Systems and methods for inter-donor migration and apparatus
EP4462862A1 (fr) Dispositif de noeud iab, dispositif donneur iab et procédé de régression topologique
US20240397376A1 (en) Systems and methods for traffic transmission in iab network
US20240188157A1 (en) Systems and methods for establishing shared n3 tunnel
US12501435B2 (en) Data forwarding for user equipment with data transmission
WO2025137827A1 (fr) Systèmes et procédés de transfert d'informations pour systèmes de relais
WO2024065245A1 (fr) Systèmes et procédés de transfert d'informations dans un système iab et appareil
US20240188165A1 (en) Systems and methods for information transfer
WO2025065621A1 (fr) Systèmes et procédés de migration inter-donneurs
US12316453B2 (en) Controlling uplink duplication in packet data convergence protocol layer
WO2025145587A1 (fr) Systèmes et procédés de transfert d'informations pour systèmes de relais
US20250254599A1 (en) Systems and methods for device-to-device communications
KR20240129057A (ko) Iab 도너 디바이스 및 전송 마이그레이션 관리 방법
CN118575576A (zh) Iab宿主设备以及传输迁移管理方法
CN118975317A (zh) Iab宿主设备以及传输地址配置方法

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

Country of ref document: EP

Kind code of ref document: A1