WO2025156447A1

WO2025156447A1 - Information transfer for relay system and apparatus

Info

Publication number: WO2025156447A1
Application number: PCT/CN2024/086597
Authority: WO
Inventors: Ying Huang; Lin Chen; Weiqiang DU
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2024-04-08
Filing date: 2024-04-08
Publication date: 2025-07-31
Anticipated expiration: 2026-10-08

Abstract

Techniques for traffic transfer in wireless relay systems are disclosed. In an implementation, a method of wireless communication includes receiving, by a first network node, from a second network node, a configuration for a traffic transfer between different nodes in a wireless access and backhaul network; and performing the traffic transfer between the different nodes in the wireless access and backhaul network based on the configuration.

Description

INFORMATION TRANSFER FOR RELAY SYSTEM AND APPARATUS

TECHNICAL FIELD

This patent document is directed generally to wireless communications.

BACKGROUND

Mobile communication technologies are moving the world toward an increasingly connected and networked society. The rapid growth of mobile communications and advances in technology have led to greater demand for capacity and connectivity. Other aspects, such as energy consumption, device cost, spectral efficiency, and latency are also important to meeting the needs of various communication scenarios. Various techniques, including new ways to provide higher quality of service, longer battery life, and improved performance are being discussed.

SUMMARY

This patent document describes, among other things, techniques for traffic transfer in wireless relay systems.

In one aspect, a method of data communication is disclosed. The method includes receiving, by a first network node, from a second network node, a configuration for a traffic transfer between different nodes in a wireless access and backhaul network, and performing the traffic transfer between the different nodes in the wireless access and backhaul network based on the configuration.

In another aspect, a method of data communication is disclosed. The method includes transmitting, by a second network node, from a first network node, a configuration for a traffic transfer between different nodes in a wireless access and backhaul network, and performing the traffic transfer between the different nodes in the wireless access and backhaul network based on the configuration.

In another example aspect, a wireless communication apparatus comprising a processor configured to implement an above-described method is disclosed.

In another example aspect, a computer storage medium having code for implementing an above-described method stored thereon is disclosed.

These, and other, aspects are described in the present document.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 shows an example of a wireless communication system based on some example embodiments of the disclosed technology.

FIG. 2 is a block diagram representation of a portion of an apparatus based on some embodiments of the disclosed technology.

FIG. 3 shows an example of a wireless access and backhaul architecture.

FIG. 4 shows an example of a process for establishing radio bearer in a case where traffic is transferred via radio bearer.

FIG. 5 shows an example of a process for wireless communication based on some example embodiments of the disclosed technology.

FIG. 6 shows another example of a process for wireless communication based on some example embodiments of the disclosed technology.

DETAILED DESCRIPTION

Section headings are used in the present document only for ease of understanding and do not limit scope of the embodiments to the section in which they are described. Furthermore, while embodiments are described with reference to 5G examples, the disclosed techniques may be applied to wireless systems that use protocols other than 5G or 3GPP protocols.

FIG. 1 shows an example of a wireless communication system (e.g., a long term evolution (LTE) , 5G or NR cellular network) that includes a BS 120 and one or more user equipment (UE) 111, 112 and 113. In some embodiments, the uplink transmissions (131, 132, 133) can include uplink control information (UCI) , higher layer signaling (e.g., UE assistance information or UE capability) , or uplink information. In some embodiments, the downlink transmissions (141, 142, 143) can include DCI or high layer signaling or downlink information. The UE may be, for example, a smartphone, a tablet, a mobile computer, a machine to machine (M2M) device, a terminal, a mobile device, an Internet of Things (IoT) device, and so on.

FIG. 2 is a block diagram representation of a portion of an apparatus based on some embodiments of the disclosed technology. An apparatus 205 such as a network device or a base station or a wireless device (or UE) , can include processor electronics 210 such as a microprocessor that implements one or more of the techniques presented in this document. The apparatus 205 can include transceiver electronics 215 to send and/or receive wireless signals over one or more communication interfaces such as antenna (s) 220. The apparatus 205 can include other communication interfaces for transmitting and receiving data. Apparatus 205 can include one or more memories (not explicitly shown) configured to store information such as data and/or instructions. In some implementations, the processor electronics 210 can include at least a portion of the transceiver electronics 215. In some embodiments, at least some of the disclosed techniques, modules or functions are implemented using the apparatus 205.

Wireless access and backhaul architecture such as Integrated Access and Backhaul (IAB) or Wireless Access Backhaul (WAB) supports wireless access and backhauling via NR (New Radio) enabling flexible and dense deployment of NR cells while reducing the need for infrastructure for wired transmission such as wireline transport infrastructure.

FIG. 3 shows an example of a wireless access and backhaul architecture.

A relay node (e.g., IAB or WAB node) can support access and backhauling via NR. A terminating node of NR backhauling on a network side is referred to as a donor node, which represents a gNB with additional functionality to support wireless access and backhaul. Backhauling can occur via a single hop or multiple hops. One example of the wireless access and backhaul architecture is shown in FIG. 3. In FIG. 3, UE connects to the network via a WAB node, and UE traffic between UE’s user plane function (UPF) and UE is transferred via a WAB node, a WAB donor, and optionally an MT (Mobile Terminal) ’s UPF. In another example, the MT’s UPF can be co-located in the WAB donor.

The WAB node supports a gNB functionality to provide NR access to UEs and to terminate the Xn/NG protocol (e.g., interface between NG-RAN nodes) to the donor node, an access and mobility management function (AMF) , and/or a UPF. In addition to the gNB functionality, the relay node also supports a subset of the UE functionality referred to as MT, which includes, e.g., physical layer, layer-2, radio resource control (RRC) and non-access stratum (NAS) functionality to connect to another WAB node or the WAB donor node, and to the core network.

User plane (UP) /control plane (CP) traffic transfer via mapping configuration

Problem: how to perform traffic mapping for WAB node

Solution 1: a mapping configuration is configured at a WAB node for uplink (UL) traffic transfer.

Step 1: a WAB node receives a mapping configuration from WAB donor via RRC or Xn message. Alternatively, a WAB node receives a mapping configuration from an AMF via a next generation application protocol (NGAP) message. Alternatively, a WAB node receives a mapping configuration from a session management function (SMF) . In some implementations, the mapping configuration includes at least one of UE traffic information, MT traffic information, priority, or timer. In some implementations, the UE traffic information or MT traffic information may include at least one of priority, UP traffic type, non-UP traffic type, quality of service (QoS) flow identifier (QFI) , 5G QoS identifier (5QI) , bearer ID, packet data unit (PDU) session ID, differentiated services code point (DSCP) , flow label, source IP address, or target IP address. The source/target IP address can be inner or outer IP address. In some implementations, the bearer ID could be SRB ID, DRB ID, E-RAB ID, or backhaul bearer ID. The non-UP traffic type includes at least one of the following: UE-associated next generation (NG) control plane interface (NG-C) , non-UE-associated NG-C, UE-associated Xn control plane interface (Xn-C) , non-UE-associated Xn-C, non-UP traffic, OAM (Operations, Administration, and Maintenance) traffic. In some implementations, UP traffic type includes at least one of the following: NG user-plane interface (NG-U) traffic, or Xn user plane interface (Xn-U) traffic.

Step 2: a WAB node performs traffic mapping based on the mapping configuration. For example, a WAB node maps UE traffic or CP traffic to MT’s QoS flow/PDU session, or MT’s radio bearer.

Solution 2: the mapping is configured at the MT’s UPF for downlink (DL) traffic transfer.

Step 1: in an implementation, MT’s AMF/SMF obtains UE traffic information from an MT function of a WAB node (WAB-MT) , e.g., via NAS information. The UE traffic information includes at least one of: QFI, 5QI, bearer ID, PDU session ID, DSCP, flow label, source IP address, target IP address. The source/target IP address can be inner or outer IP address. In another implementation, MT’s AMF/SMF obtains UE traffic information from a WAB donor.

Step 2: UE’s AMF/SMF or MT’s AMF/SMF sends the mapping configuration (used for mapping from UE traffic to MT traffic ) to MT’s UPF. The mapping configuration includes: UE traffic info, MT traffic info, priority, timer.

The information associated with UE traffic or MT traffic (e.g., UE traffic information and MT traffic information) includes at least one of: priority, UP traffic type, non-UP traffic type, MT ID, QFI, 5QI, bearer ID, PDU session ID, DSCP, flow label, source IP address, target IP address. The source/target IP address can be inner or outer IP address. The bearer ID may be signaling radio bearer (SRB) ID, data radio bearer (DRB) ID, E-UTRAN radio access bearer (E-RAB) ID, or backhaul bearer ID. In some implementations, the non-UP traffic type may include at least one of the following: UE-associated NG-C, non-UE-associated NG-C, UE-associated Xn-C, non-UE-associated Xn-C, non-UP traffic, OAM traffic. In some implementations, UP traffic type may include at least one of the following: NG-U traffic, Xn-U traffic.

Step 3: MT’s UPF performs traffic mapping for the UE traffic. For example, MT’s UPF maps the DL UE traffic to MT’s QoS flow/PDU session.

Traffic transfer via radio bearer

Problem: If UE traffic or CP traffic is transferred via a radio bearer such as backhaul (BH) radio bearer instead of PDU session, there is no QoS profile at the RAN node side and no QoS rules at the MT side. UE traffic or CP traffic is not transferred via MT’s UPF. The problem is how to perform traffic mapping when traffic is transferred via radio bearer.

Solution 1: For UL

Step 1: a gNB function of a WAB node (WAB-gNB) generates UP or CP packets (e.g., NG or Xn packets) and delivers them to WAB-MT. MT maps UP or CP traffic to MT’s radio bearer based on routing and mapping configuration and sends to WAB donor. The routing and mapping configuration includes traffic information and MT’s radio bearer information. The traffic information includes at least one of: priority, non-UP traffic type, source IP address, target IP address, DSCP, flow labe, QFI, 5QI, PDU session ID, or QoS parameters. MT’s radio bearer information includes at least one of: CP traffic indication, UP traffic indication, backhaul radio bearer indication, radio bearer ID, net hop ID (e.g., MCG, SCG, MN, SN indication) . The bearer ID could be SRB ID, DRB ID, E-RAB ID, or backhaul bearer ID.

In other implementations, before performing the routing and mapping, a WAB node receives the routing and mapping configuration from WAB donor, or from AMF or SMF.

Step 2: WAB donor receives packets from MT via a radio bearer, and determines not to map these packets to an NG-U (user-plane interface) tunnel.

Step 3: WAB donor checks IP address of the received packets and performs routing via internet protocol (IP) .

Solution 2: For DL

Step 1: at least one of AMF, UPF, or gNB sends packets to WAB donor.

Step 2: WAB donor maps the IP traffic to a backhaul radio bearer and sends to a WAB node. WAB donor performs traffic mapping based on a routing and mapping configuration. The routing and mapping configuration includes traffic information and MT’s radio bearer information. The traffic information includes at least one of priority, non-UP traffic type, source IP address, target IP address, DSCP, flow labe, QFI, 5QI, PDU session ID, or QoS parameters. MT’s radio bearer information may include at least one of CP traffic indication, UP traffic indication, backhaul radio bearer indication, radio bearer ID, net hop ID (e.g., master cell group (MCG) , secondary cell group (SCG) , master node (MN) , secondary node (SN) indication) . The bearer ID may be signaling radio bearer (SRB) ID, data radio bearer (DRB) ID, evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) ID, or backhaul bearer ID.

In other implementations, before performing the routing and mapping, WAB donor receives the routing and mapping configuration from the AMF or SMF or OAM or pre-configuration. In other implementations, the WAB donor generates the routing and mapping configuration by itself.

How to establish radio bearer if traffic is transferred via radio bearer

Problem: how to establish radio bearer if traffic is transferred via radio bearer Solution 1:

Step 1: a PDU session establishment procedure for UE is triggered by UE or the network.

Step 2: a gNB part of the WAB node receives QoS profile for UE traffic via next generation application protocol (NGAP) message from UE’s AMF.

Step 3: a WAB node sends UE traffic information to a donor node via RRC or Xn. The UE traffic information includes: (source and/or target) IP address, DSCP/flow label, traffic type, priority, QFI, QoS parameters (5QI, ARP, guaranteed bit rate (GBR) /non-GBR information, etc. )

Step 4: a WAB donor sends a radio bearer configuration and a routing and mapping configuration to a WAB node via RRC or Xn.

The radio bearer configuration includes at least one of: radio bearer ID, backhaul indication, UP indication, CP indication, packet data convergence protocol (PDCP) configuration, radio link control (RLC) configuration, medium access control (MAC) configuration, skip ciphering indication. Skip ciphering indication is used to indicate that the ciphering is not performed at PDCP sublayer for this radio bearer. For example, if ciphering is performed at IP layer via Internet Protocol Security (IPsec) , there is no need to perform ciphering at PDCP layer between WAB-MT and WAB donor when transferring UE traffic or CP traffic.

The routing and mapping configuration includes traffic information and MT’s radio bearer information as explained above.

Solution 2: backhaul radio bearer is established after MT initial access.

Step 1: a WAB node performs initial access procedure and includes the WAB node indication in the RRC message and sends it to donor node.

Step 2: a WAB donor sends radio bearer configuration and routing and mapping configuration to the WAB node via RRC or Xn.

Traffic transfer via QoS flow and/or packet data unit (PDU) session without NG-U tunnel

Problem: If UE traffic or CP traffic is transferred via PDU session/QoS flow without NG-U tunnel, there is no NG-U tunnel for the corresponding PDU session/QoS flow, and UE traffic or CP traffic is not transferred via MT’s UPF. The problem is how to perform traffic mapping when traffic is transferred via QoS flow/PDU session without NG-U tunnel.

Solution 1: For UL

Step 1: WAB-gNB generates UP or CP packets (e.g. NG or Xn packets) and deliver them to WAB-MT.MT maps these packets to MT’s QoS flow, e.g., based on a packet filter set or a configuration from WAB donor, as discussed above. MT maps the corresponding QoS flow to a radio bearer and sends to WAB donor.

Step 2: WAB donor receives packets from MT, and determines not to map these packets to NG-U tunnel.

In some implementations, an indication (e.g., backhaul PDU session indication, no GTP-U tunnel indication, backhaul QoS flow indication) and the corresponding PDU session/QoS flow ID is received by the WAB donor from core network, e.g., AMF or SMF.

Step 3: WAB donor performs routing for the packets and sends them to next hop.

Solution 2: For DL

Step 1: at least one of AMF, UPF, or gNB sends CP or UP packets to a WAB donor.

Step 2: the WAB donor maps these packets to backhaul QoS flow/PDU session (which has no GTP-U tunnel) and sends to a WAB node.

In some implementations, the WAB donor can perform traffic mapping using one of the following options:

Option 1: the WAB donor can perform traffic mapping based on a traffic mapping configuration configured at the WAB donor. The WAB donor receives the traffic mapping configuration from OAM or pre-configuration or a core network, e.g., AMF or SMF.

The mapping configuration includes at least one of UE traffic information, MT traffic information, a priority, or a timer.

The information of UE traffic or MT traffic (e.g., UE traffic information, MT traffic information) may include at least one of priority, UP traffic type, non-UP traffic type, QFI, 5QI, bearer ID, PDU session ID, DSCP, flow label, source IP address, or target IP address. The source/target IP address can be inner or outer IP address. The bearer ID may be SRB ID, DRB ID, E-RAB ID, or backhaul bearer ID. The non-UP traffic type includes at least one of the following: UE-associated NG-C, non-UE-associated NG-C, UE-associated Xn-C, non-UE-associated Xn-C, non-UP traffic, OAM traffic. UP traffic type includes at least one of the following: NG-U traffic, Xn-U traffic.

Option2: WAB donor can perform traffic mapping based on a packet filter set configured by SMF. Routing

Problem: if WAB-MT is dual-connected to two WAB donors connect to different AMFs/UPFs/gNBs, the problem is how a WAB node can determine which donor to forward the UL packets, and how the AMF/gNB/UPF can determine which donor to forward the DL packets.

Solution 1: a WAB node receives the routing configuration from a WAB donor or AMF. The routing configuration includes at least one of the following: IP address of AMF/gNB/UPF, ID of AMF/gNB/UPF, IP address of WAB donor, gNB ID of WAB donor, MCG indication, SCG indication, MN indication, SN indication. The IP address could be inner or outer IP address.

Solution 2: an AMF receives the routing configuration from the WAB donor via an NGAP message.

The routing configuration includes at least one of the following: WAB node information, WAB donor information.

In some implementations, WAB node information includes at least one of the following: gNB ID or cell ID or IP address of WAB node. In some implementations, WAB donor information includes at least one of the following: gNB ID or cell ID or IP address of WAB donor. The IP address may be inner or outer IP address.

Solution 3: UPF receives the routing configuration from AMF or SMF or WAB node or WAB donor. In some implementations, the routing configuration includes at least one of the following: WAB node information, WAB donor information, as discussed above.

IP address allocation

Problem: a WAB node has both the gNB and MT functions. The IP address of an MT part of WAB node is allocated by SMF under the current standard. The problem is how to allocate IP address for the gNB part of a WAB node.

Solution:

Step 1: IP address of the gNB part of the WAB node is allocated by the serving SMF of the MT part of the WAB node. The serving SMF of the MT part of the WAB node sends an IP address of the gNB part of the WAB node to the MT.

Step 2: the MT part of the WAB node delivers the IP address of the gNB part of the WAB node to the gNB part of the WAB node, e.g., co-located WAB-gNB.

Routing at WAB donor when IPsec is used

Problem:

If an Internet Protocol Security (IPsec) is used in NGAP/NG-U between a WAB node and an AMF/UPF, or if the IPsec is used in an XnAP/Xn-U between a WAB node and gNB, and these packets needs to be routed at the WAB donor based on the IP address, then the WAB donor cannot obtain an inner IP address of these packets and performs routing based on the inner IP address. The problem is how to perform routing at a WAB donor when IPsec is used.

Solution:

Option1: a WAB node sends mapping information to a WAB donor via an RRC or Xn message. The mapping information includes at least one of: ID of AMF, ID of gNB, IP address of AMF, IP address of gNB, ID of UPF, IP address of UPF. The IP address can be an inner IP address or an outer IP address.

Option2: an AMF sends IP address information to a WAB donor. The IP address information includes at least one of: IP address of AMF, IP address of UPF, ID of UPF, ID of AMF. The IP address can be an inner IP address or an outer IP address.

Option3: a gNB sends its IP address to a WAB donor. The IP address can be an inner IP address or an outer IP address.

Option 4: a UPF sends its IP address to a WAB donor. The IP address can be an inner IP address or an outer IP address.

In some implementations, the process 500 for wireless communication may include, at 510, receiving, by a first network node, from a second network node, a configuration for a traffic transfer between different nodes in a wireless access and backhaul network, and at 520, performing the traffic transfer between the different nodes in the wireless access and backhaul network based on the configuration.

In some implementations, the process 600 for wireless communication may include, at 610, transmitting, by a second network node, from a first network node, a configuration for a traffic transfer between different nodes in a wireless access and backhaul network, and at 620, performing the traffic transfer between the different nodes in the wireless access and backhaul network based on the configuration.

It will be appreciated that the present document discloses techniques that can be embodied in various embodiments to determine downlink control information in wireless networks. The disclosed and other embodiments, modules and the functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.

A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document) , in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code) . A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit) .

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random-access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

Some embodiments may preferably implement one or more of the following solutions, listed in clause-format. The following clauses are supported and further described in the embodiments above and throughout this document. As used in the clauses below and in the claims, a wireless device may be user equipment, mobile station, or any other wireless terminal including fixed nodes such as base stations. A network device includes a base station including a next generation Node B (gNB) , enhanced Node B (eNB) , or any other device that performs as a base station.

Clause 1. A method of wireless communication, comprising: receiving, by a first network node, from a second network node, a configuration for a traffic transfer between different nodes in a wireless access and backhaul network; and performing the traffic transfer between the different nodes in the wireless access and backhaul network based on the configuration.

Clause 2. The method of clause 1, wherein the first network node includes a wireless access backhaul (WAB) node, and the second network node includes at least one of a WAB donor, an access and mobility management function (AMF) , or a session management function (SMF) .

Clause 3. The method of clause 1, wherein the configuration includes a mapping configuration that includes at least one of a user equipment (UE) traffic information, a mobile terminal (MT) traffic information, a priority, or a timer.

Clause 4. The method of clause 3, wherein the UE traffic information and the MT traffic information includes at least one of a source internet protocol (IP) address, a target IP address, differentiated services code point (DSCP) or flow label, a traffic type, a priority, a quality of service (QoS) flow identifier (QFI) , or a QoS parameter.

Clause 5. The method of clause 1, wherein the first network node is a user plane function (UPF) of a mobile terminal (MT) .

Clause 6. The method of clause 5, wherein the receiving of the configuration includes: receiving, by an access and mobility management function (AMF) or a session management function (SMF) of a mobile terminal (MT) in the first network node, from a wireless access backhaul (WAB) with mobile terminal (MT) function or a WAB donor, a UE traffic information; and transmitting, by the AMF or SMF of the MT or by an AMF or SMF of user equipment (UE) , the configuration to the UPF of the MT.

Clause 7. The method of clause 6, wherein the UE traffic information includes at least one of a source IP address, a target IP address, differentiated services code point (DSCP) or flow label, a traffic type, a priority, a quality of service (QoS) flow identifier (QFI) , or a QoS parameter.

Clause 8. The method of clause 3, wherein the MT traffic information includes at least one of: a control plane (CP) traffic indication, a user plane (UP) traffic indication, a backhaul radio bearer indication, a radio bearer ID, or a net hop ID including at least one of a master cell group (MCG) indication, a secondary cell group (SCG) indication, a master node (MN) indication, or a secondary node (SN) indication.

Clause 9. The method of clause 8, wherein the radio bearer ID includes at least one of a signaling radio bearer (SRB) ID, a data radio bearer (DRB) ID, an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) ID, or a backhaul bearer ID.

Clause 10. The method of any of clauses 1-3, further comprising: transmitting a UE traffic information to the second network node before receiving the configuration.

Clause 11. The method of clause 10, wherein the configuration includes a radio bearer configuration and a mapping configuration.

Clause 12. The method of clause 11, wherein the radio bearer configuration includes at least one of a radio bearer ID, a backhaul indication, a user plane (UP) indication, a control plane (CP) indication, a packet data convergence protocol (PDCP) configuration, a radio link control (RLC) configuration, a medium access control (MAC) configuration, or skip ciphering indication.

Clause 13. The method of clause 11, further comprising, before receiving the radio bearer configuration and the mapping configuration, performing an initial access procedure by sending, to the second network node, a WAB node indication that indicate the first network node is a WAB node.

Clause 14. The method of clause 1, wherein the first network node is a WAB donor of a mobile terminal (MT) , and the second network node includes at least one of an access and mobility management function (AMF) or a session management function (SMF) .

Clause 15. The method of clause 14, wherein the first network node receives an indication and a corresponding PDU session and quality of service (QoS) flow ID from a second network node.

Clause 16. The method of clause 15, wherein the indication includes at least one of a backhaul PDU session indication, an indication that there is no GTP-U tunnel, or a backhaul QoS flow indication.

Clause 17. The method of clause 1, wherein the second network node includes one of a WAB donor and an AMF, and the first network node includes a WAB node configured to receive a routing configuration from the second network node.

Clause 18. The method of clause 17, wherein the routing configuration includes at least one of: an IP address of at least one of AMF, gNB, or UPF; an ID of at least one of AMF, gNB, or UPF, an IP address of the WAB donor; a gNB ID of the WAB donor; a master cell group (MCG) indication; a secondary cell group (SCG) indication; a master node (MN) indication; or a secondary node (SN) indication.

Clause 19. The method of clause 1, wherein the second network node includes a WAB donor, and the first network node includes an AMF, and the first network node receives a routing configuration from the second network node via a next generation application protocol (NGAP) message.

Clause 20. The method of clause 19, wherein the routing configuration includes at least one of: a WAB node information or a WAB donor information.

Clause 21. The method of clause 20, wherein the WAB node information includes at least one of: a gNB ID of the WAB node, a cell ID of the WAB node, or an IP address of the WAB node.

Clause 22. The method of clause 20, wherein the WAB donor information includes at least one of: a gNB ID of the WAB donor, a cell ID of the WAB donor, or an IP address of the WAB donor.

Clause 23. The method of clause 1, wherein the second network node includes one of an AMF, an SMF, a WAB node, or a WAB donor, and the first network node includes an UPF, and the first network node receives a routing configuration from the second network node.

Clause 24. The method of clause 23, wherein the routing configuration includes at least one of: a WAB node information or a WAB donor information.

Clause 25. The method of clause 24, wherein the WAB node information includes at least one of: a gNB ID of the WAB node, a cell ID of the WAB node, or an IP address of the WAB node.

Clause 26. The method of clause 24, wherein the WAB donor information includes at least one of: a gNB ID of the WAB donor, a cell ID of the WAB donor, or an IP address of the WAB donor.

Clause 27. The method of clause 1, wherein the first network node includes a WAB node that has both gNB and MT functions, wherein an internet protocol (IP) address of the gNB function of the WAB node is sent by a serving SMF of the MT function of the WAB node to the MT function of the WAB node.

Clause 28. A method of wireless communication, comprising: transmitting, by a second network node, from a first network node, a configuration for a traffic transfer between different nodes in a wireless access and backhaul network; and performing the traffic transfer between the different nodes in the wireless access and backhaul network based on the configuration.

Clause 29. The method of clause 28, wherein the first network node includes a wireless access backhaul (WAB) node, and the second network node includes at least one of a WAB donor, an access and mobility management function (AMF) , or a session management function (SMF) .

Clause 30. The method of clause 28, wherein the configuration includes a mapping configuration that includes at least one of a user equipment (UE) traffic information, a mobile terminal (MT) traffic information, a priority, or a timer.

Clause 31. The method of clause 30, wherein the UE traffic information and the MT traffic information includes at least one of a source internet protocol (IP) address, a target IP address, differentiated services code point (DSCP) or flow label, a traffic type, a priority, a quality of service (QoS) flow identifier (QFI) , or a QoS parameter.

Clause 32. The method of clause 30, wherein the MT traffic information includes at least one of: a control plane (CP) traffic indication, a user plane (UP) traffic indication, a backhaul radio bearer indication, a radio bearer ID, or a net hop ID including at least one of a master cell group (MCG) indication, a secondary cell group (SCG) indication, a master node (MN) indication, or a secondary node (SN) indication.

Clause 33. The method of clause 32, wherein the radio bearer ID includes at least one of a signaling radio bearer (SRB) ID, a data radio bearer (DRB) ID, an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) ID, or a backhaul bearer ID.

Clause 34. The method of any of clauses 28-30, further comprising: receiving a UE traffic information from the first network node before transmitting the configuration.

Clause 35. The method of clause 34, wherein the configuration includes a radio bearer configuration and a mapping configuration.

Clause 36. The method of clause 35, wherein the radio bearer configuration includes at least one of a radio bearer ID, a backhaul indication, a user plane (UP) indication, a control plane (CP) indication, a packet data convergence protocol (PDCP) configuration, a radio link control (RLC) configuration, a medium access control (MAC) configuration, or skip ciphering indication.

Clause 37. The method of clause 28, wherein the second network node includes one of a WAB donor and an AMF, and the first network node includes a WAB node configured to receive a routing configuration from the second network node.

Clause 38. The method of clause 37, wherein the routing configuration includes at least one of: an IP address of at least one of AMF, gNB, or UPF; an ID of at least one of AMF, gNB, or UPF, an IP address of the WAB donor; a gNB ID of the WAB donor; a master cell group (MCG) indication; a secondary cell group (SCG) indication; a master node (MN) indication; or a secondary node (SN) indication.

Clause 39. The method of clause 28, wherein the second network node includes a WAB donor, and the first network node includes an AMF, and the first network node receives a routing configuration from the second network node via a next generation application protocol (NGAP) message.

Clause 40. The method of clause 39, wherein the routing configuration includes at least one of: a WAB node information or a WAB donor information.

Clause 41. The method of clause 40, wherein the WAB node information includes at least one of: a gNB ID of the WAB node, a cell ID of the WAB node, or an IP address of the WAB node.

Clause 42. The method of clause 40, wherein the WAB donor information includes at least one of: a gNB ID of the WAB donor, a cell ID of the WAB donor, or an IP address of the WAB donor.

Clause 43. The method of clause 28, wherein the second network node includes one of an AMF, an SMF, a WAB node, or a WAB donor, and the first network node includes an UPF, and the first network node receives a routing configuration from the second network node.

Clause 44. The method of clause 43, wherein the routing configuration includes at least one of: a WAB node information or a WAB donor information.

Clause 45. The method of clause 44, wherein the WAB node information includes at least one of: a gNB ID of the WAB node, a cell ID of the WAB node, or an IP address of the WAB node.

Clause 46. The method of clause 44, wherein the WAB donor information includes at least one of: a gNB ID of the WAB donor, a cell ID of the WAB donor, or an IP address of the WAB donor.

Clause 47. An apparatus for wireless communication comprising a processor that is configured to carry out the method of any of clauses 1 to 46.

Clause 48. A non-transitory computer readable medium having code stored thereon, the code when executed by a processor, causing the processor to implement a method recited in any of clauses 1 to 46.

Some of the embodiments described herein are described in the general context of methods or processes, which may be implemented in one embodiment by a computer program product, embodied in a computer-readable medium, including computer-executable instructions, such as program code, executed by computers in networked environments. A computer-readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM) , Random Access Memory (RAM) , compact discs (CDs) , digital versatile discs (DVD) , etc. Therefore, the computer-readable media can include a non-transitory storage media. Generally, program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer-or processor-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.

Some of the disclosed embodiments can be implemented as devices or modules using hardware circuits, software, or combinations thereof. For example, a hardware circuit implementation can include discrete analog and/or digital components that are, for example, integrated as part of a printed circuit board. Alternatively, or additionally, the disclosed components or modules can be implemented as an Application Specific Integrated Circuit (ASIC) and/or as a Field Programmable Gate Array (FPGA) device. Some implementations may additionally or alternatively include a digital signal processor (DSP) that is a specialized microprocessor with an architecture optimized for the operational needs of digital signal processing associated with the disclosed functionalities of this application. Similarly, the various components or sub-components within each module may be implemented in software, hardware or firmware. The connectivity between the modules and/or components within the modules may be provided using any one of the connectivity methods and media that is known in the art, including, but not limited to, communications over the Internet, wired, or wireless networks using the appropriate protocols.

While this document contains many specifics, these should not be construed as limitations on the scope of an invention that is claimed or of what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features that are described in this document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or a variation of a sub-combination. Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results.

Only a few implementations and examples are described and other implementations, enhancements and variations can be made based on what is described and illustrated in this disclosure.

Claims

A method of wireless communication, comprising:

receiving, by a first network node, from a second network node, a configuration for a traffic transfer between different nodes in a wireless access and backhaul network; and

performing the traffic transfer between the different nodes in the wireless access and backhaul network based on the configuration.
The method of claim 1, wherein the first network node includes a wireless access backhaul (WAB) node, and the second network node includes at least one of a WAB donor, an access and mobility management function (AMF) , or a session management function (SMF) .
The method of claim 1, wherein the configuration includes a mapping configuration that includes at least one of a user equipment (UE) traffic information, a mobile terminal (MT) traffic information, a priority, or a timer.
The method of claim 3, wherein the UE traffic information and the MT traffic information includes at least one of a source internet protocol (IP) address, a target IP address, differentiated services code point (DSCP) or flow label, a traffic type, a priority, a quality of service (QoS) flow identifier (QFI) , or a QoS parameter.
The method of claim 1, wherein the first network node is a user plane function (UPF) of a mobile terminal (MT) .
The method of claim 5, wherein the receiving of the configuration includes:

receiving, by an access and mobility management function (AMF) or a session management function (SMF) of a mobile terminal (MT) in the first network node, from a wireless access backhaul (WAB) with mobile terminal (MT) function or a WAB donor, a UE traffic information; and

transmitting, by the AMF or SMF of the MT or by an AMF or SMF of user equipment (UE) , the configuration to the UPF of the MT.
The method of claim 6, wherein the UE traffic information includes at least one of a source IP address, a target IP address, differentiated services code point (DSCP) or flow label, a traffic type, a priority, a quality of service (QoS) flow identifier (QFI) , or a QoS parameter.
The method of claim 3, wherein the MT traffic information includes at least one of: a control plane (CP) traffic indication, a user plane (UP) traffic indication, a backhaul radio bearer indication, a radio bearer ID, or a net hop ID including at least one of a master cell group (MCG) indication, a secondary cell group (SCG) indication, a master node (MN) indication, or a secondary node (SN) indication.
The method of claim 8, wherein the radio bearer ID includes at least one of a signaling radio bearer (SRB) ID, a data radio bearer (DRB) ID, an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) ID, or a backhaul bearer ID.
The method of any of claims 1-3, further comprising:

transmitting a UE traffic information to the second network node before receiving the configuration.
The method of claim 10, wherein the configuration includes a radio bearer configuration and a mapping configuration.
The method of claim 11, wherein the radio bearer configuration includes at least one of a radio bearer ID, a backhaul indication, a user plane (UP) indication, a control plane (CP) indication, a packet data convergence protocol (PDCP) configuration, a radio link control (RLC) configuration, a medium access control (MAC) configuration, or skip ciphering indication.
The method of claim 11, further comprising, before receiving the radio bearer configuration and the mapping configuration, performing an initial access procedure by sending, to the second network node, a WAB node indication that indicate the first network node is a WAB node.
The method of claim 1, wherein the first network node is a WAB donor of a mobile terminal (MT) , and the second network node includes at least one of an access and mobility management function (AMF) or a session management function (SMF) .
The method of claim 14, wherein the first network node receives an indication and a corresponding PDU session and quality of service (QoS) flow ID from a second network node.
The method of claim 15, wherein the indication includes at least one of a backhaul PDU session indication, an indication that there is no GTP-U tunnel, or a backhaul QoS flow indication.
The method of claim 1, wherein the second network node includes one of a WAB donor and an AMF, and the first network node includes a WAB node configured to receive a routing configuration from the second network node.
The method of claim 17, wherein the routing configuration includes at least one of: an IP address of at least one of AMF, gNB, or UPF; an ID of at least one of AMF, gNB, or UPF, an IP address of the WAB donor; a gNB ID of the WAB donor; a master cell group (MCG) indication; a secondary cell group (SCG) indication; a master node (MN) indication; or a secondary node (SN) indication.
The method of claim 1, wherein the second network node includes a WAB donor, and the first network node includes an AMF, and the first network node receives a routing configuration from the second network node via a next generation application protocol (NGAP) message.
The method of claim 19, wherein the routing configuration includes at least one of: a WAB node information or a WAB donor information.
The method of claim 20, wherein the WAB node information includes at least one of: a gNB ID of the WAB node, a cell ID of the WAB node, or an IP address of the WAB node.
The method of claim 20, wherein the WAB donor information includes at least one of: a gNB ID of the WAB donor, a cell ID of the WAB donor, or an IP address of the WAB donor.
The method of claim 1, wherein the second network node includes one of an AMF, an SMF, a WAB node, or a WAB donor, and the first network node includes an UPF, and the first network node receives a routing configuration from the second network node.
The method of claim 23, wherein the routing configuration includes at least one of: a WAB node information or a WAB donor information.
The method of claim 24, wherein the WAB node information includes at least one of: a gNB ID of the WAB node, a cell ID of the WAB node, or an IP address of the WAB node.
The method of claim 24, wherein the WAB donor information includes at least one of: a gNB ID of the WAB donor, a cell ID of the WAB donor, or an IP address of the WAB donor.
The method of claim 1, wherein the first network node includes a WAB node that has both gNB and MT functions, wherein an internet protocol (IP) address of the gNB function of the WAB node is sent by a serving SMF of the MT function of the WAB node to the MT function of the WAB node.
A method of wireless communication, comprising:

transmitting, by a second network node, from a first network node, a configuration for a traffic transfer between different nodes in a wireless access and backhaul network; and

performing the traffic transfer between the different nodes in the wireless access and backhaul network based on the configuration.
The method of claim 28, wherein the first network node includes a wireless access backhaul (WAB) node, and the second network node includes at least one of a WAB donor, an access and mobility management function (AMF) , or a session management function (SMF) .
The method of claim 28, wherein the configuration includes a mapping configuration that includes at least one of a user equipment (UE) traffic information, a mobile terminal (MT) traffic information, a priority, or a timer.
The method of claim 30, wherein the UE traffic information and the MT traffic information includes at least one of a source internet protocol (IP) address, a target IP address, differentiated services code point (DSCP) or flow label, a traffic type, a priority, a quality of service (QoS) flow identifier (QFI) , or a QoS parameter.
The method of claim 30, wherein the MT traffic information includes at least one of: a control plane (CP) traffic indication, a user plane (UP) traffic indication, a backhaul radio bearer indication, a radio bearer ID, or a net hop ID including at least one of a master cell group (MCG) indication, a secondary cell group (SCG) indication, a master node (MN) indication, or a secondary node (SN) indication.
The method of claim 32, wherein the radio bearer ID includes at least one of a signaling radio bearer (SRB) ID, a data radio bearer (DRB) ID, an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) ID, or a backhaul bearer ID.
The method of any of claims 28-30, further comprising:

receiving a UE traffic information from the first network node before transmitting the configuration.
The method of claim 34, wherein the configuration includes a radio bearer configuration and a mapping configuration.
The method of claim 35, wherein the radio bearer configuration includes at least one of a radio bearer ID, a backhaul indication, a user plane (UP) indication, a control plane (CP) indication, a packet data convergence protocol (PDCP) configuration, a radio link control (RLC) configuration, a medium access control (MAC) configuration, or skip ciphering indication.
The method of claim 28, wherein the second network node includes one of a WAB donor and an AMF, and the first network node includes a WAB node configured to receive a routing configuration from the second network node.
The method of claim 37, wherein the routing configuration includes at least one of: an IP address of at least one of AMF, gNB, or UPF; an ID of at least one of AMF, gNB, or UPF, an IP address of the WAB donor; a gNB ID of the WAB donor; a master cell group (MCG) indication; a secondary cell group (SCG) indication; a master node (MN) indication; or a secondary node (SN) indication.
The method of claim 28, wherein the second network node includes a WAB donor, and the first network node includes an AMF, and the first network node receives a routing configuration from the second network node via a next generation application protocol (NGAP) message.
The method of claim 39, wherein the routing configuration includes at least one of: a WAB node information or a WAB donor information.
The method of claim 40, wherein the WAB node information includes at least one of: a gNB ID of the WAB node, a cell ID of the WAB node, or an IP address of the WAB node.
The method of claim 40, wherein the WAB donor information includes at least one of: a gNB ID of the WAB donor, a cell ID of the WAB donor, or an IP address of the WAB donor.
The method of claim 28, wherein the second network node includes one of an AMF, an SMF, a WAB node, or a WAB donor, and the first network node includes an UPF, and the first network node receives a routing configuration from the second network node.
The method of claim 43, wherein the routing configuration includes at least one of: a WAB node information or a WAB donor information.
The method of claim 44, wherein the WAB node information includes at least one of: a gNB ID of the WAB node, a cell ID of the WAB node, or an IP address of the WAB node.
The method of claim 44, wherein the WAB donor information includes at least one of: a gNB ID of the WAB donor, a cell ID of the WAB donor, or an IP address of the WAB donor.
An apparatus for wireless communication comprising a processor that is configured to carry out the method of any of claims 1 to 46.
A non-transitory computer readable medium having code stored thereon, the code when executed by a processor, causing the processor to implement a method recited in any of claims 1 to 46.