Relay system and device information forwarding

Abstract

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

Description

Technical Field

[0001] This patent document generally relates to wireless communication. Background Technology

[0002] Mobile communication technology is driving the world towards an increasingly interconnected and networked society. The rapid growth and technological advancements in mobile communications have led to greater demands for capacity and connectivity. Other factors, such as energy consumption, device cost, spectrum efficiency, and latency, are also important for meeting the needs of various communication scenarios. Various technologies are being discussed, including new methods to provide higher service quality, longer battery life, and improved performance. Summary of the Invention

[0003] Among other things, the patent document describes a technique for service forwarding in a wireless relay system.

[0004] In one aspect, a method for data communication is disclosed. The method includes: a first network node receiving from a second network node a configuration for service forwarding between different nodes in a radio access and backhaul network; and performing service forwarding between different nodes in the radio access and backhaul network based on the configuration.

[0005] In another aspect, a method for data communication is disclosed. The method includes: sending a configuration for service forwarding between different nodes in a radio access and backhaul network from a second network node to a first network node, and performing service forwarding between different nodes in the radio access and backhaul network based on the configuration.

[0006] In another example aspect, a wireless communication device is disclosed, which includes a processor configured to implement the methods described above.

[0007] In another example, a computer storage medium is disclosed on which code for implementing the above methods is stored.

[0008] These and other aspects are described in this patent document. Attached Figure Description

[0009] Figure 1 Examples of wireless communication systems based on some exemplary embodiments of the disclosed technology are shown.

[0010] Figure 2 This is a block diagram representation of a portion of an apparatus based on some embodiments of the disclosed technology.

[0011] Figure 3 An example of a wireless access and backhaul architecture is shown.

[0012] Figure 4 An example of the process for establishing a radio bearer when forwarding services via a radio bearer is shown.

[0013] Figure 5 Another example of a wireless communication process based on some example embodiments of the disclosed technology is shown.

[0014] Figure 6 Another example of a wireless communication process based on some example embodiments of the disclosed technology is shown. Detailed Implementation

[0015] The section headings used in this document are for ease of understanding only and do not limit the scope of the embodiments to the sections describing them. Furthermore, while embodiments are described with reference to 5G examples, the disclosed techniques can be applied to wireless systems using protocols other than 5G or 3GPP protocols.

[0016] Figure 1 An example of a wireless communication system (e.g., a Long Term Evolution (LTE), 5G, or NR cellular network) including a BS 120 and one or more user equipment (UE) devices 111, 112, and 113 is shown. In some embodiments, uplink transmissions (131, 132, 133) may include uplink control information (UCI), higher-layer signaling (e.g., UE assistance information or UE capabilities), or uplink information. In some embodiments, downlink transmissions (141, 142, 143) may include DCI or higher-layer signaling or downlink information. The UE may be, for example, a smartphone, tablet, mobile computer, machine-to-machine (M2M) device, terminal, mobile device, Internet of Things (IoT) device, etc.

[0017] Figure 2 This is a block diagram representation of a portion of an apparatus based on some embodiments of the disclosed technology. Apparatus 205, such as a network device, base station, or wireless device (or UE), may include processor electronics 210, such as a microprocessor implementing one or more technologies proposed in this document. Apparatus 205 may include transceiver electronics 215 for transmitting and / or receiving wireless signals via one or more communication interfaces, such as antenna 220. Apparatus 205 may include other communication interfaces for transmitting and receiving data. Apparatus 205 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some implementations, processor electronics 210 may include at least a portion of transceiver electronics 215. In some embodiments, apparatus 205 is used to implement at least some of the disclosed technologies, modules, or functions.

[0018] Radio access and backhaul architectures, such as Integrated Access and Backhaul (IAB) or Radio Access Backhaul (WAB), support radio access and backhaul via NR (New Radio), enabling flexible and dense deployment of NR cells while reducing the need for wired transmission infrastructure.

[0019] Figure 3 An example of a wireless access and backhaul architecture is shown.

[0020] Relay nodes (e.g., IAB or WAB nodes) can support access and backhaul via NR. The terminating node of the network-side NR backhaul is called the donor node, which represents a gNB with additional capabilities to support radio access and backhaul. Backhaul can occur via single hops or multiple hops. Figure 3 An example of a wireless access and backhaul architecture is shown in the diagram. Figure 3 In this configuration, the UE connects to the network via the WAB node. UE services between the UE and its users' plane functions (UPF) are forwarded via the UPF of the WAB node, the WAB donor node, and the optional MT (Mobile Terminal). In another example, the MT's UPF can be co-located with the WAB donor node.

[0021] WAB nodes support gNB functionality to provide NR access to UEs and terminate Xn / NG protocols (e.g., interfaces between NG-RAN nodes) for donor nodes, Access and Mobility Management Functions (AMF), and / or UPF. In addition to gNB functionality, relay nodes also support a subset of UE functions known as MT, including, for example, physical layer, Layer 2, Radio Resource Control (RRC), and Non-Access Stratum (NAS) functions, to connect to another WAB node or WAB donor node, and to connect to the core network.

[0022] User plane (UP) / control plane (CP) service forwarding via mapping configuration Question: How to perform business mapping on WAB nodes? Solution 1: Configure mapping at the WAB node for uplink (UL) service forwarding.

[0023] Step 1: The WAB node receives the mapping configuration from the WAB donor node via RRC or Xn messages. Alternatively, the WAB node receives the mapping configuration from the AMF via Next Generation Application Protocol (NGAP) messages. Alternatively, the WAB node receives the mapping configuration from the Session Management Function (SMF). In some implementations, the mapping configuration includes at least one of UE service information, MT service information, priority, or timer. In some implementations, the UE service information or MT service information may include at least one of priority, UP service type, non-UP service 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 destination IP address. The source / destination IP address can be an internal or external IP address. In some implementations, the bearer ID can be an SRB ID, DRB ID, E-RAB ID, or backhaul bearer ID. Non-UP service types include at least one of the following: UE-related Next Generation (NG) Control Plane Interface (NG-C), non-UE-related NG-C, UE-related Xn Control Plane Interface (Xn-C), non-UE-related Xn-C, non-UP services, and OAM (Operation, Administration, and Maintenance) services. In some implementations, UP service types include at least one of the following: NG User Plane Interface (NG-U) services or Xn User Plane Interface (Xn-U) services.

[0024] Step 2: The WAB node performs service mapping according to the mapping configuration. For example, the WAB node maps UE services or CP services to MT's QoS stream / PDU session or MT's radio bearer.

[0025] Solution 2: Configure a mapping at the UPF of the MT for downlink (DL) service forwarding.

[0026] Step 1: In one implementation, the MT's AMF / SMF obtains UE service information from the MT function of the WAB node (WAB-MT), for example via NAS information. UE service information includes at least one of QFI, 5QI, bearer ID, PDU session ID, DSCP, flow label, source IP address, and destination IP address. The source / destination IP address can be an internal or external IP address. In another implementation, the MT's AMF / SMF obtains UE service information from the WAB donor node.

[0027] Step 2: The UE's AMF / SMF or the MT's AMF / SMF sends the mapping configuration (used to map UE services to MT services) to the MT's UPF. The mapping configuration includes: UE service information, MT service information, priority, and timers.

[0028] Information related to UE services or MT services (e.g., UE service information and MT service information) includes at least one of the following: priority, UP service type, non-UP service type, MT ID, QFI, 5QI, bearer ID, PDU session ID, DSCP, flow label, source IP address, and destination IP address. The source / destination IP address can be an internal or external IP address. The bearer ID can be a signaling radio bearer (SRB) ID, a data radio bearer (DRB) ID, an E-UTRAN radio access bearer (E-RAB) ID, or a backhaul bearer ID. In some implementations, non-UP service types may include at least one of the following: UE-related NG-C, non-UE-related NG-C, UE-related Xn-C, non-UE-related Xn-C, non-UP service, and OAM service. In some implementations, UP service types may include at least one of the following: NG-U service and Xn-U service.

[0029] Step 3: The MT's UPF performs service mapping for the UE services. For example, the MT's UPF maps DL UE services to the MT's QoS stream / PDU session.

[0030] Service forwarding via radio bearer Problem: If UE or CP services are forwarded via a radio bearer, such as a backhaul (BH) radio bearer, instead of a PDU session, there is no QoS profile at the RAN node and no QoS rules at the MT. UE or CP services are not forwarded via the MT's UPF. The question is how to perform service mapping when services are forwarded via radio bearers.

[0031] Solution 1: Applicable to UL Step 1: The gNB function of the WAB node (WAB-gNB) generates UP or CP packets (e.g., NG or Xn packets) and delivers them to the WAB-MT. The MT maps the UP or CP service to its radio bearer according to the routing and mapping configuration and sends it to the WAB donor node. The routing and mapping configuration includes service information and the MT's radio bearer information. Service information includes at least one of priority, non-UP service type, source IP address, destination IP address, DSCP, flow label, QFI, 5QI, PDU session ID, or QoS parameters. The MT's radio bearer information includes at least one of CP service indication, UP service indication, backhaul radio bearer indication, radio bearer ID, and network hop ID (e.g., MCG, SCG, MN, SN indication). The bearer ID can be SRB ID, DRBID, E-RAB ID, or backhaul bearer ID.

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

[0033] Step 2: The WAB donor node receives data packets from the MT via radio bearer and determines not to map these data packets to the NG-U (User Plane Interface) tunnel.

[0034] Step 3: The WAB donor node checks the IP address of the received data packet and routes it via Internet Protocol (IP).

[0035] Solution 2: Applicable to DL Step 1: At least one of AMF, UPF, or gNB sends a data packet to the WAB donor node.

[0036] Step 2: The WAB donor node maps IP services to backhaul radio bearers and sends the mappings to the WAB node. The WAB donor node performs service mapping based on the routing and mapping configuration. The routing and mapping configuration includes service information and MT radio bearer information. Service information includes at least one of priority, non-UP service type, source IP address, destination IP address, DSCP, flow label, QFI, 5QI, PDU session ID, or QoS parameters. MT radio bearer information may include at least one of CP service indication, UP service indication, backhaul radio bearer indication, radio bearer ID, and network hop ID (e.g., primary cell group (MCG), secondary cell group (SCG), primary node (MN), secondary node (SN) indication). Bearer ID may be 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.

[0037] In other implementations, the WAB donor node receives route and mapping configurations from AMF, SMF, OAM, or pre-configured sources before performing routing and mapping. In other implementations, the WAB donor node generates the route and mapping configurations itself.

[0038] If the service is conducted via radio bearer, how should the radio bearer be established? Question: If the service is transmitted via radio bearer, how is the radio bearer established? Solution 1: Step 1: The UE's PDU session establishment process is triggered by the UE or the network.

[0039] Step 2: The gNB portion of the WAB node receives the QoS profile of the UE service from the UE's AMF via Next Generation Application Protocol (NGAP) messages.

[0040] Step 3: The WAB node sends UE service information to the donor node via RRC or Xn. UE service information includes: (source and / or destination) IP address, DSCP / flow label, service type, priority, QFI, QoS parameters (5QI, ARP, Guaranteed Bit Rate (GBR) / non-GBR information, etc.). Step 4: The WAB donor node sends the radio bearer configuration and route mapping configuration to the WAB node via RRC or Xn.

[0041] The radio bearer configuration includes at least one of the following: radio bearer ID, backhaul indication, UP indication, CP indication, Packet Data Convergence Protocol (PDCP) configuration, Radio Link Control (RLC) configuration, Media Access Control (MAC) configuration, and skip encryption indication. The skip encryption indication is used to indicate that encryption is not performed on the radio bearer at the PDCP sublayer. For example, if encryption is performed at the IP layer via Internet Protocol Security (IPsec), then encryption is not required at the PDCP layer between the WAB-MT and the WAB donor node when forwarding UE or CP services.

[0042] As mentioned above, the routing and mapping configuration includes service information and radio bearer information for the MT.

[0043] Figure 4 An example of the process for establishing a radio bearer is shown when a service is forwarded via a radio bearer.

[0044] Solution 2: Establish a backhaul radio bearer after the initial MT access.

[0045] Step 1: The WAB node performs the initial access procedure and sends the WAB node indication in an RRC message to the donor node.

[0046] Step 2: The WAB donor node sends the radio bearer configuration and route mapping configuration to the WAB node via RRC or Xn.

[0047] Traffic forwarding is performed via QoS streams and / or Packet Data Unit (PDU) sessions, without NG-U tunnels. Problem: If UE or CP services are forwarded via PDU sessions / QoS flows without NG-U tunnels, then the corresponding PDU sessions / GOS flows also lack NG-U tunnels, and UE or CP services will not be forwarded via MT's UPF. The question is how to perform service mapping when services are forwarded via QoS flows / PDU sessions without NG-U tunnels.

[0048] Solution 1: Applicable to UL Step 1: The WAB-gNB generates UP or CP packets (e.g., NG or Xn packets) and delivers them to the WAB-MT. The MT maps these packets to its QoS flow, for example, based on packet filter settings or configuration from the WAB donor node, as described above. The MT maps the corresponding QoS flow to a radio bearer and sends it to the WAB donor node.

[0049] Step 2: The WAB donor node receives data packets from the MT and determines not to map these data packets to the NG-U tunnel.

[0050] In some implementations, the WAB donor node receives indications (e.g., backhaul PDU session indication, no GTP-U tunnel indication, backhaul QoS flow indication) and the corresponding PDU session / QoS flow ID from the core network (e.g., AMF or SMF).

[0051] Step 3: The WAB donor node performs routing for the packet and sends it to the next hop.

[0052] Solution 2: Applicable to DL Step 1: At least one of AMF, UPF, or gNB sends a CP or UP packet to the WAB donor node.

[0053] Step 2: The WAB donor node maps these packets to a backhaul QoS stream / PDU session (which does not have a GTP-U tunnel) and sends it to the WAB node.

[0054] In some implementations, the WAB donor node can perform business mapping using one of the following options: Option 1: The WAB donor node can perform service mapping based on the service mapping configuration configured at the WAB donor node. The WAB donor node receives the service mapping configuration from OAM or a pre-configured core network (e.g., AMF or SMF).

[0055] The mapping configuration includes at least one of UE service information, MT service information, priority, or timer.

[0056] Information about UE services or MT services (e.g., UE service information, MT service information) may include priority, UP service type, non-UP service type, and at least one of QFI, 5QI, bearer ID, PDU session ID, DSCP, flow label, source IP address, or destination IP address. The source / destination IP address can be an internal or external IP address. The bearer ID can be an SRB ID, DRB ID, E-RAB ID, or backhaul bearer ID. Non-UP service types include at least one of the following: UE-related NG-C, non-UE-related NG-C, UE-related Xn-C, non-UI-related Xn-C, non-UP services, and OAM services. UP service types include at least one of the following: NG-U services and Xn-U services.

[0057] Option 2: The WAB donor node can perform service mapping based on the packet filter settings configured by SMF.

[0058] routing Problem: If WAB-MT is dual-connected to two WAB donor nodes and connected to different AMF / UPF / gNB, the problem is how the WAB node determines the donor node for forwarding UL packets, and how the AMF / gNB / UPF determines the donor node for forwarding DL packets.

[0059] Solution 1: The WAB node receives routing configuration from the WAB donor node or AMF. The routing configuration includes at least one of the following: the IP address of the AMF / gNB / UPF, the ID of the AMF / gNB / UPF, the IP address of the WAB donor node, and the gNBID, MCG indication, SCG indication, MN indication, and SN indication of the WAB donor node. The IP address can be an internal or external IP address.

[0060] Solution 2: AMF receives routing configuration from the WAB donor node via NGAP messages.

[0061] The routing configuration includes at least one of the following: WAB node information and WAB donor node information.

[0062] In some implementations, WAB node information includes at least one of the following: the WAB node's gNB ID, cell ID, or IP address. In some implementations, WAB donor node information includes at least one of the following: the WAB donor node's gNB ID, cell ID, or IP address. The IP address can be an internal or external IP address.

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

[0064] IP address allocation Problem: A WAB node has both gNB and MT functions. The IP addresses for the MT portion of the WAB node are assigned by SMF under the current standard. The question is how to assign IP addresses to the gNB portion of the WAB node.

[0065] Solution: Step 1: The IP address of the gNB portion of the WAB node is assigned by the SMF service of the MT portion of the WAB node. The SMF service of the MT portion of the WAB node sends the IP address of the gNB portion of the WAB node to the MT.

[0066] 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, for example, by co-configuring WAB-gNB.

[0067] When using IPsec, routing is performed at the WAB donor node. question: If Internet Protocol Security (IPsec) is used in NGAP / NG-U between the WAB node and AMF / UPF, or if IPsec is used in XnAP / Xn-U between the WAB node and gNB, and these packets need to be routed at the WAB donor node based on IP address, the WAB donor node cannot obtain the internal IP address of these packets and cannot perform routing based on the internal IP address. The problem is how to perform routing at the WAB donor node when using IPsec.

[0068] Solution: Option 1: The WAB node sends mapping information to the WAB donor node via RRC or Xn messages. The mapping information includes at least one of the following: AMF ID, gNB ID, AMF IP address, gNB IP address, UPF ID, and UPF IP address. The IP addresses can be internal or external IP addresses.

[0069] Option 2: The AMF sends IP address information to the WAB donor node. The IP address information includes at least one of the following: the AMF's IP address, the UPF's IP address, the UPF's ID, and the AMF's ID. The IP address can be an internal or external IP address.

[0070] Option 3: The gNB sends its IP address to the WAB donor node. This IP address can be an internal or external IP address.

[0071] Option 4: The UPF sends its IP address to the WAB donor node. This IP address can be an internal or external IP address.

[0072] Figure 5 Examples of wireless communication processes based on some exemplary embodiments of the disclosed technology are shown.

[0073] In some implementations, the process 500 for wireless communication may include: at 510, a first network node receiving from a second network node a configuration for service forwarding between different nodes in the wireless access and backhaul network, and at 520, performing service forwarding between different nodes in the wireless access and backhaul network based on the configuration.

[0074] Figure 6 Another example of a wireless communication process based on some example embodiments of the disclosed technology is shown.

[0075] In some implementations, the process 600 for wireless communication may include: at 610, a second network node sending a configuration for service forwarding between different nodes in the wireless access and backhaul network to a first network node, and at 620, performing service forwarding between different nodes in the wireless access and backhaul network based on the configuration.

[0076] It should be understood that this document discloses techniques that can be implemented in various embodiments to determine downlink control information in a wireless network. The disclosed embodiments and other embodiments, modules, and functional operations described in this document can be implemented in digital electronic circuits, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in a combination 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 computer program instruction modules encoded on a computer-readable medium for execution by or control of the operation of a data processing apparatus. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a storage device, a composition of substances affecting machine-readable propagation signals, or one or more of these. The term "data processing apparatus" includes all means, devices, and machines for processing data, such as a programmable processor, a computer, or a plurality of processors or computers. In addition to hardware, the apparatus may also include code that creates an execution environment for the computer program in question, for example, code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of these. A propagation signal is a man-made signal, such as a machine-generated electrical, optical, or electromagnetic signal, which is generated to encode information for transmission to a suitable receiver device.

[0077] Computer programs (also known as programs, software, software applications, scripts, or code) can be written in any programming language, including compiled or interpreted languages, and can be deployed in any form, including as standalone programs or as modules, components, subroutines, or other units suited to a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored as part of a file containing other programs or data (e.g., one or more scripts stored in a markup language document), or as a single file dedicated to the program in question, or as multiple coordinating files (e.g., a file storing one or more modules, subroutines, or code sections). Computer programs can be deployed to execute on a single computer, located at a site, or distributed across multiple sites and interconnected via a communication network.

[0078] The processes and logic flows described in this document can be executed by one or more programmable processors, which execute one or more computer programs to perform functions by manipulating input data and generating outputs. The processes and logic flows can also be executed by dedicated logic circuits, and the devices can be implemented as dedicated logic circuits, such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits).

[0079] For example, processors suitable for executing computer programs include general-purpose and special-purpose microprocessors, as well as any one or more processors in any type of digital computer. Typically, a processor receives instructions and data from read-only memory or random access memory, or both. The basic components of a computer are a processor for executing instructions and one or more storage devices for storing instructions and data. Typically, a computer will also include, or be operatively coupled to, receiving data from or forwarding data to one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or both. However, a computer does not need to have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices, such as semiconductor storage devices like EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROMs and DVD-ROMs. The processor and memory may be supplemented or integrated within dedicated logic circuitry.

[0080] Some embodiments may preferably implement one or more of the following solutions listed in the terms format. The following terms are supported and further described in the above embodiments and in this document. As used in the following terms and claims, a wireless device may be a user equipment, a mobile station, or any other wireless terminal including a fixed node such as a base station. Network devices include base stations, which include next-generation node B (gNB), enhanced node B (eNB), or any other device performing as a base station.

[0081] Clause 1. A method for wireless communication, comprising: receiving, by a first network node, a configuration for service forwarding between different nodes in a wireless access and backhaul network from a second network node; and performing service forwarding between different nodes in the wireless access and backhaul network based on said configuration.

[0082] The methods of Clause 2 and Clause 1, wherein the first network node includes a Radio Access Backhaul (WAB) node and the second network node includes at least one of a WAB donor node, an Access and Mobility Management Function (AMF), or a Session Management Function (SMF).

[0083] The methods of Clause 3 and Clause 1, wherein the configuration includes a mapping configuration, the mapping configuration including at least one of user equipment (UE) service information, mobile terminal (MT) service information, priority, or timer.

[0084] The methods in Clauses 4 and 3, wherein the UE service information and MT service information include at least one of the following: source Internet Protocol (IP) address, destination IP address, differentiated service code point (DSCP) or flow label, service type, priority, quality of service (QoS) flow identifier (QFI) or QoS parameter.

[0085] The method of Clause 5 and Clause 1, wherein the first network node is the User Plane Function (UPF) of the mobile terminal (MT).

[0086] The methods of Clause 6 and Clause 5, wherein receiving the configuration includes: receiving UE service information from a Radio Access Backhaul (WAB) or WAB donor node with mobile terminal (MT) functionality by the Access and Mobility Management Function (AMF) or Session Management Function (SMF) of the mobile terminal (MT) in the first network node; and sending the configuration to the UPF of the MT by the AMF or SMF of the MT or by the AMF or SMF of the user equipment (UE).

[0087] The methods in Clauses 7 and 6, wherein the UE service information includes at least one of the following: source IP address, destination IP address, differentiated service code point (DSCP) or flow label, service type, priority, quality of service (QoS) flow identifier (QFI) or QoS parameter.

[0088] The methods of Clause 8 and Clause 3, wherein the MT service information includes at least one of Control Plane (CP) service indication, User Plane (UP) service indication, Backhaul radio bearer indication, Radio Bearer ID or Network Jump ID, wherein the Network Jump ID includes at least one of Primary Cell Group (MCG) indication, Secondary Cell Group (SCG) indication, Primary Node (MN) indication or Secondary Node (SN) indication.

[0089] The methods of Clauses 9 and 8, wherein the radio bearer ID includes at least one of the following: 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.

[0090] The method of any one of Clause 10 or Clauses 1-3 further includes: sending UE service information to the second network node before receiving the configuration.

[0091] The methods of Clause 11 and Clause 10, wherein the configuration includes radio bearer configuration and mapping configuration.

[0092] The methods of Clause 12 and Clause 11, wherein the radio bearer configuration includes at least one of radio bearer ID, return indication, user plane (UP) indication, control plane (CP) indication, packet data convergence protocol (PDCP) configuration, radio link control (RLC) configuration, media access control (MAC) configuration, or skip encryption indication.

[0093] The methods of Clauses 13 and 11 further include performing an initial access procedure by sending a WAB node indication to a second network node indicating that the first network node is a WAB node, prior to receiving the radio bearer configuration and mapping configuration.

[0094] The method of Clause 14 and Clause 1, wherein the first network node is a WAB donor node of the 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).

[0095] The methods of Clauses 15 and 14, wherein the first network node receives an indication from the second network node and the corresponding PDU session and Quality of Service (QoS) flow ID.

[0096] The methods of Clause 16 and Clause 15, wherein the indication includes at least one of a backhaul PDU session indication, an indication of not having a GTP-U tunnel, or a backhaul QoS flow indication.

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

[0098] The methods of Clauses 18 and 17, wherein the routing configuration includes at least one of the following: the IP address of at least one of AMF, gNB or UPF; the ID of at least one of AMF, gNB or UPF; the IP address of the WAB donor node; the gNBID of the WAB donor node; the primary cell group (MCG) indication; the secondary cell group (SCG) indication; the primary node (MN) indication; or the secondary node (SN) indication.

[0099] The method of Clause 19 and Clause 1, wherein the second network node includes a WAB donor node, the first network node includes an AMF, and the first network node receives routing configuration from the second network node via a Next Generation Application Protocol (NGAP) message.

[0100] The methods of Clauses 20 and 19, wherein the routing configuration includes at least one of WAB node information or WAB donor node information.

[0101] The methods of Clauses 21 and 20, wherein the WAB node information includes at least one of the WAB node's gNB ID, the WAB node's cell ID, or the WAB node's IP address.

[0102] The methods of Clauses 22 and 20, wherein the WAB donor node information includes at least one of the following: the gNB ID of the WAB donor node, the cell ID of the WAB donor node, or the IP address of the WAB donor node.

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

[0104] The methods of Clauses 24 and 23, wherein the routing configuration includes at least one of WAB node information or WAB donor node information.

[0105] The methods in Clauses 25 and 24, wherein the WAB node information includes at least one of the WAB node's gNB ID, the WAB node's cell ID, or the WAB node's IP address.

[0106] The methods in Clauses 26 and 24, wherein the WAB donor node information includes at least one of the following: the gNB ID of the WAB donor node, the cell ID of the WAB donor node, or the IP address of the WAB donor node.

[0107] The method of Clause 27 and Clause 1, wherein the first network node includes a WAB node having gNB and MT functions, wherein the Internet Protocol (IP) address of the gNB function of the WAB node is sent to the MT function of the WAB node by the service SMF of the MT function of the WAB node.

[0108] Clause 28. A method for wireless communication, comprising: sending a configuration for service forwarding between different nodes in a radio access and backhaul network from a second network node to a first network node; and performing service forwarding between different nodes in the radio access and backhaul network based on the configuration.

[0109] The methods of Clauses 29 and 28, wherein the first network node includes a Radio Access Backhaul (WAB) node and the second network node includes at least one of a WAB donor node, an Access and Mobility Management Function (AMF), or a Session Management Function (SMF).

[0110] The methods of Clauses 30 and 28, wherein the configuration includes a mapping configuration, the mapping configuration including at least one of user equipment (UE) service information, mobile terminal (MT) service information, priority, or timer.

[0111] The methods of Clauses 31 and 30, wherein the UE service information and the MT service information include at least one of the following: source Internet Protocol (IP) address, destination IP address, differentiated service code point (DSCP) or flow label, service type, priority, quality of service (QoS) flow identifier (QFI) or QoS parameter.

[0112] The methods of Clauses 32 and 30, wherein the MT service information includes at least one of Control Plane (CP) service indication, User Plane (UP) service indication, Backhaul radio bearer indication, Radio Bearer ID or Network Jump ID, and the Network Jump ID includes at least one of Primary Cell Group (MCG) indication, Secondary Cell Group (SCG) indication, Primary Node (MN) indication or Secondary Node (SN) indication.

[0113] The methods of Clauses 33 and 32, wherein the radio bearer ID includes at least one of the following: 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.

[0114] The method of any one of Clauses 34 and Clauses 28-30 further includes: receiving UE service information from the first network node before sending the configuration.

[0115] The methods of Clauses 35 and 34, wherein the configuration includes radio bearer configuration and mapping configuration.

[0116] The methods of Clauses 36 and 35, wherein the radio bearer configuration includes at least one of radio bearer ID, return indication, user plane (UP) indication, control plane (CP) indication, packet data convergence protocol (PDCP) configuration, radio link control (RLC) configuration, media access control (MAC) configuration, or skip encryption indication.

[0117] The methods of Clauses 37 and 28, wherein the second network node includes one of a WAB donor node and an AMF, and the first network node includes a WAB node configured to receive routing configuration from the second network node.

[0118] The methods of Clauses 38 and 37, wherein the routing configuration includes at least one of the following: the IP address of at least one of AMF, gNB or UPF; the ID of at least one of AMF, gNB or UPF; the IP address of the WAB donor node; the gNBID of the WAB donor node; the primary cell group (MCG) indication; the secondary cell group (SCG) indication; the primary node (MN) indication; or the secondary node (SN) indication.

[0119] The methods of Clauses 39 and 28, wherein the second network node includes a WAB donor node, the first network node includes an AMF, and the first network node receives routing configuration from the second network node via Next Generation Application Protocol (NGAP) messages.

[0120] The methods of Clauses 40 and 39, wherein the routing configuration includes at least one of WAB node information or WAB donor node information.

[0121] The methods in Clauses 41 and 40, wherein the WAB node information includes at least one of the WAB node's gNB ID, the WAB node's cell ID, or the WAB node's IP address.

[0122] The methods of Clauses 42 and 40, wherein the WAB donor node information includes at least one of the following: the gNB ID of the WAB donor node, the cell ID of the WAB donor node, or the IP address of the WAB donor node.

[0123] The methods of Clauses 43 and 28, wherein the second network node includes one of AMF, SMF, WAB node or WAB donor node, the first network node includes UPF, and the first network node receives routing configuration from the second network node.

[0124] The methods of Clauses 44 and 43, wherein the routing configuration includes at least one of WAB node information or WAB donor node information.

[0125] The methods in Clauses 45 and 44, wherein the WAB node information includes at least one of the WAB node's gNB ID, the WAB node's cell ID, or the WAB node's IP address.

[0126] The methods in Clauses 46 and 44, wherein the WAB donor node information includes at least one of the following: the gNB ID of the WAB donor node, the cell ID of the WAB donor node, or the IP address of the WAB donor node.

[0127] Clause 47. An apparatus for wireless communication, comprising a processor configured to perform the method of any one of Clauses 1 to 46.

[0128] Clause 48. A non-transitory computer-readable medium having code stored thereon that, when executed by a processor, causes the processor to implement the methods of any one of Clauses 1 to 46.

[0129] Some embodiments described herein are set within a general context of methods or processes. In one embodiment, these methods or processes can be implemented by a computer program product contained in a computer-readable medium, including computer-executable instructions, such as program code, that are executed by a computer in a networked environment. The computer-readable medium can include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), optical disc (CD), digital versatile optical disc (DVD), etc. Therefore, the computer-readable medium can include non-transitory storage media. Typically, program modules can include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents examples of corresponding actions for implementing the functionality described in these steps or processes.

[0130] Some of the disclosed embodiments can be implemented as devices or modules using hardware circuitry, software, or a combination thereof. For example, hardware circuitry implementations may include discrete analog and / or digital components, such as those integrated as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs) devices. Some implementations may additionally or alternatively include a digital signal processor (DSP), which is a special-purpose microprocessor with an architecture optimized for the operational requirements of digital signal processing related to the disclosed functions of this application. Similarly, various components or sub-components within each module can be implemented using software, hardware, or firmware. Connectivity between modules and / or components within modules can be provided using any of the connection methods and media known in the art, including but not limited to communication over the Internet, wired, or wireless networks using appropriate protocols.

[0131] While this document contains numerous details, these details should not be construed as limiting the scope of the claimed invention or any potentially claimed content, but rather as descriptions of features specific to particular embodiments. Certain features described in this document within the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described within the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although the foregoing features may be described as functioning in certain combinations, or even originally claimed in this way, in some cases one or more features from the claimed combination may be removed, and the claimed combination may refer to a sub-combination or a variation of the sub-combination. Similarly, although operations are depicted in a specific order in the drawings, this should not be construed as requiring these operations to be performed in the specific sequence or order shown, or requiring all of the shown operations to achieve the desired result.

[0132] Only a few implementations and examples are described, and other implementations, enhancements and variations may be made based on what is described and shown in this disclosure.

Claims

1. A method for wireless communication, comprising: The first network node receives configuration from the second network node for service forwarding between different nodes in the wireless access and backhaul network; as well as Based on the configuration, the service forwarding is performed between different nodes in the wireless access and backhaul network.

2. The method according to claim 1, wherein, The first network node includes a Radio Access Backhaul (WAB) node, and the second network node includes at least one of a WAB donor node, an Access and Mobility Management Function (AMF), or a Session Management Function (SMF).

3. The method according to claim 1, wherein, The configuration includes a mapping configuration, which includes at least one of user equipment (UE) service information, mobile terminal (MT) service information, priority, or timer.

4. The method according to claim 3, wherein, The UE service information and the MT service information include at least one of the following: source Internet Protocol (IP) address, destination IP address, differentiated service code point (DSCP) or flow label, service type, priority, quality of service (QoS) flow identifier (QFI) or QoS parameter.

5. The method according to claim 1, wherein, The first network node is the user plane function (UPF) of the mobile terminal (MT).

6. The method according to claim 5, wherein, Receiving the configuration includes: The UE service information is received from the Radio Access Backhaul (WAB) or WAB donor node with mobile terminal (MT) functionality by the Access and Mobility Management Function (AMF) or Session Management Function (SMF) of the mobile terminal (MT) in the first network node; and The configuration is sent from the AMF or SMF of the MT or from the AMF or SMF of the user equipment (UE) to the UPF of the MT.

7. The method according to claim 6, wherein, The UE service information includes at least one of the following: source IP address, destination IP address, differentiated service code point (DSCP) or flow label, service type, priority, quality of service (QoS) flow identifier (QFI) or QoS parameter.

8. The method according to claim 3, wherein, The MT service information includes at least one of control plane (CP) service indication, user plane (UP) service indication, backhaul radio bearer indication, radio bearer ID, or network hop ID. The network hop ID includes at least one of primary cell group (MCG) indication, secondary cell group (SCG) indication, primary node (MN) indication, or secondary node (SN) indication.

9. The method according to claim 8, wherein, The radio bearer ID includes at least one of the following: 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.

10. The method according to any one of claims 1 to 3, further comprising: Before receiving the configuration, UE service information is sent to the second network node.

11. The method according to claim 10, wherein, The configuration includes radio bearer configuration and mapping configuration.

12. The method according to claim 11, wherein, The radio bearer configuration includes at least one of the following: radio bearer ID, return indication, user plane (UP) indication, control plane (CP) indication, packet data convergence protocol (PDCP) configuration, radio link control (RLC) configuration, media access control (MAC) configuration, or skip encryption indication.

13. The method of claim 11, further comprising: Before receiving the radio bearer configuration and the mapping configuration, the initial access procedure is performed by sending a WAB node indication to the second network node, indicating that the first network node is a WAB node.

14. The method according to claim 1, wherein, The first network node is a WAB donor node for 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).

15. The method according to claim 14, wherein, The first network node receives an indication and the corresponding PDU session and Quality of Service (QoS) flow ID from the second network node.

16. The method according to claim 15, wherein, The indication includes at least one of a backhaul PDU session indication, an indication of not having a GTP-U tunnel, or a backhaul QoS flow indication.

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

18. The method according to claim 17, wherein, The routing configuration includes at least one of the following: the IP address of at least one of AMF, gNB, or UPF; the ID of at least one of AMF, gNB, or UPF; the IP address of the WAB donor node; the gNB ID of the WAB donor node; the primary cell group (MCG) indication; the secondary cell group (SCG) indication; the primary node (MN) indication; or the secondary node (SN) indication.

19. The method according to claim 1, wherein, The second network node includes a WAB donor node, the first network node includes an AMF, and the first network node receives routing configuration from the second network node via Next Generation Application Protocol (NGAP) messages.

20. The method according to claim 19, wherein, The routing configuration includes at least one of WAB node information or WAB donor node information.

21. The method according to claim 20, wherein, The WAB node information includes at least one of the following: the gNB ID of the WAB node, the cell ID of the WAB node, or the IP address of the WAB node.

22. The method according to claim 20, wherein, The WAB donor node information includes at least one of the following: the gNB ID of the WAB donor node, the cell ID of the WAB donor node, or the IP address of the WAB donor node.

23. The method according to claim 1, wherein, The second network node includes one of AMF, SMF, WAB node or WAB donor node, the first network node includes UPF, and the first network node receives routing configuration from the second network node.

24. The method according to claim 23, wherein, The routing configuration includes at least one of WAB node information or WAB donor node information.

25. The method according to claim 24, wherein, The WAB node information includes at least one of the following: the gNB ID of the WAB node, the cell ID of the WAB node, or the IP address of the WAB node.

26. The method according to claim 24, wherein, The WAB donor node information includes at least one of the following: the gNB ID of the WAB donor node, the cell ID of the WAB donor node, or the IP address of the WAB donor node.

27. The method according to claim 1, wherein, The first network node includes a WAB node with gNB and MT functions, wherein the Internet Protocol (IP) address of the gNB function of the WAB node is sent to the MT function of the WAB node by the service SMF of the MT function of the WAB node.

28. A method for wireless communication, comprising: The second network node sends the configuration for service forwarding between different nodes in the wireless access and backhaul network to the first network node; as well as Based on the configuration, the service forwarding is performed between different nodes in the wireless access and backhaul network.

29. The method according to claim 28, wherein, The first network node includes a Radio Access Backhaul (WAB) node, and the second network node includes at least one of a WAB donor node, an Access and Mobility Management Function (AMF), or a Session Management Function (SMF).

30. The method according to claim 28, wherein, The configuration includes a mapping configuration, which includes at least one of user equipment (UE) service information, mobile terminal (MT) service information, priority, or timer.

31. The method according to claim 30, wherein, The UE service information and the MT service information include at least one of the following: source Internet Protocol (IP) address, destination IP address, differentiated service code point (DSCP) or flow label, service type, priority, quality of service (QoS) flow identifier (QFI) or QoS parameter.

32. The method according to claim 30, wherein, The MT service information includes at least one of control plane (CP) service indication, user plane (UP) service indication, backhaul radio bearer indication, radio bearer ID, or network hop ID. The network hop ID includes at least one of primary cell group (MCG) indication, secondary cell group (SCG) indication, primary node (MN) indication, or secondary node (SN) indication.

33. The method according to claim 32, wherein, The radio bearer ID includes at least one of the following: 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.

34. The method according to any one of claims 28 to 30, further comprising: Before sending the configuration, UE service information is received from the first network node.

35. The method according to claim 34, wherein, The configuration includes radio bearer configuration and mapping configuration.

36. The method according to claim 35, wherein, The radio bearer configuration includes at least one of the following: radio bearer ID, return indication, user plane (UP) indication, control plane (CP) indication, packet data convergence protocol (PDCP) configuration, radio link control (RLC) configuration, media access control (MAC) configuration, or skip encryption indication.

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

38. The method according to claim 37, wherein, The routing configuration includes at least one of the following: the IP address of at least one of AMF, gNB, or UPF; the ID of at least one of AMF, gNB, or UPF; the IP address of the WAB donor node; the gNB ID of the WAB donor node; the primary cell group (MCG) indication; the secondary cell group (SCG) indication; the primary node (MN) indication; or the secondary node (SN) indication.

39. The method according to claim 28, wherein, The second network node includes a WAB donor node, the first network node includes an AMF, and the first network node receives routing configuration from the second network node via Next Generation Application Protocol (NGAP) messages.

40. The method according to claim 39, wherein, The routing configuration includes at least one of WAB node information or WAB donor node information.

41. The method according to claim 40, wherein, The WAB node information includes at least one of the following: the gNB ID of the WAB node, the cell ID of the WAB node, or the IP address of the WAB node.

42. The method according to claim 40, wherein, The WAB donor node information includes at least one of the following: the gNB ID of the WAB donor node, the cell ID of the WAB donor node, or the IP address of the WAB donor node.

43. The method according to claim 28, wherein, The second network node includes one of AMF, SMF, WAB node or WAB donor node, the first network node includes UPF, and the first network node receives routing configuration from the second network node.

44. The method according to claim 43, wherein, The routing configuration includes at least one of WAB node information or WAB donor node information.

45. The method according to claim 44, wherein, The WAB node information includes at least one of the following: the gNB ID of the WAB node, the cell ID of the WAB node, or the IP address of the WAB node.

46. ​​The method of claim 44, wherein, The WAB donor node information includes at least one of the following: the gNB ID of the WAB donor node, the cell ID of the WAB donor node, or the IP address of the WAB donor node.

47. An apparatus for wireless communication, comprising a processor configured to perform the method of any one of claims 1 to 46.

48. A non-transitory computer-readable medium having code stored thereon, which, when executed by a processor, causes the processor to implement the method of any one of claims 1 to 46.

Images