System and method for information transmission for relay systems

Abstract

Systems and methods for information transfer for relay systems are provided. A network node of a wireless access and backhaul communication system can receive traffic mapping information. The network node can use the traffic mapping information to perform mapping for one or more packets of non-user plane (UP) traffic.

Description

Technical Field

[0001] The disclosure generally relates to wireless communication, including but not limited to systems and methods for information transmission in relay systems. Background Technology

[0002] Coverage is a fundamental aspect of cellular network deployment. Mobile operators rely on different types of network nodes to provide comprehensive coverage in their deployments. Therefore, new types of network nodes have been considered to increase the flexibility of mobile operators in their network deployments. For example, some systems or architectures introduce integrated access and backhaul (IAB), which can be enhanced in some other systems as a new type of network node that does not require wired backhaul. Another type of network node is the RF repeater, which simply amplifies and forwards any signals it receives. RF repeaters have been widely deployed in 2G, 3G, and 4G mobile communication technologies to supplement the coverage provided by conventional full-stack cells. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more issues existing in the prior art and provide additional features that will become apparent when taken in conjunction with the accompanying drawings and the following detailed description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not as limiting, and that various modifications can be made to the disclosed embodiments without departing from the scope of this disclosure, as will be apparent to those skilled in the art upon reading this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A network node (e.g., a wireless access and backhaul (WAB) node or WAB donor) of a wireless access and backhaul communication system can receive / acquire / obtain service mapping information. The network node can use this service mapping information to perform / initiate / enforce mapping for one or more packets of non-user plane (UP) services.

[0005] In some implementations, non-UP services may include at least one of the following: next-generation control plane interface (NG-C) services, Xn control plane interface (Xn-C) services, and / or operations, administration, and maintenance (OAM) services. In some implementations, service mapping information may be configured by the session management function (SMF) or access management function (AMF), or received from the SMF or AMF.

[0006] In some implementations, service mapping information may include at least one of the following: Quality of Service (QoS) flow identifier (QFI); Protocol Data Unit (PDU) session identifier (ID); non-UP service type; priority; Evolved Radio Access Bearer (E-RAB) ID; Internet Protocol (IP) related information; and / or Data Radio Bearer (DRB) ID. In some implementations, non-UP service type may include at least one of the following: NG-C associated with user equipment (UE); NG-C not associated with UE; Xn-C associated with UE; Xn-C not associated with UE; non-UP service; and / or OAM service.

[0007] In some implementations, IP-related information may include at least one of the following: IP address; differentiated services codepoint (DSCP); and / or flow label. In some implementations, network nodes may use service mapping information to map at least one packet of the one or more packets of non-UP services to at least one of the following: one or more QoS flows; E-RAB; and / or DRB.

[0008] In some implementations, network nodes may send donor node information via Xn Application Protocol (XnAP) messages or Radio Resource Control (RRC) messages. In some implementations, network nodes may send / transmit / provide / forward donor node information via Next Generation Application Protocol (NGAP) messages. In some implementations, donor node information may include at least one of the following: information about the network node; information about the network node's child nodes; information about the network node's parent node; and / or donor node information.

[0009] In some implementations, a network node may send network node information to a donor node and / or a WAB node. A network node may receive a response message from a donor node or a WAB node, the response message including at least one of the following: gNodeB (gNB) identifier (ID); cell ID; IP address; cell radio network temporary identifier (C-RNTI); information about the sub-WAB node; and / or Xn Application Protocol (XnAP) ID.

[0010] In some implementations, network node information may include at least one of the following: IP address; Cell Radio Network Temporary Identifier (C-RNTI); Xn Application Protocol (XnAP) Identifier (ID); child node information; and / or parent node information. In some cases, network node information may include at least one of the following for the network node: gNB ID; cell ID; IP address; child node information; and / or parent node information.

[0011] In some implementations, a network node may send at least one of parent node information and / or child node information to a donor node and / or a WAB node. The network node may receive topology information from the donor node and / or the WAB node, which includes at least one of the following: IP address; and / or next-hop identifier (ID). In some implementations, the next-hop ID may include at least one of the following from at least one of the parent node of the WAB node, and / or the child node of the WAB node, and / or the donor node: gNodeB (gNB) identifier (ID); IP address; Cell Radio Network Temporary Identifier (C-RNTI); and / or Xn Application Protocol (XnAP) ID.

[0012] At least one aspect relates to a system, method, apparatus, or computer-readable medium. Core network functions (e.g., access management function (AMF), session management function (SMF), etc.) can send / provide / transmit / deliver service mapping information to network nodes of a radio access and backhaul communication system. One or more packets of control plane (CP) services can be mapped by the network node using this service mapping information. Attached Figure Description

[0013] Various exemplary embodiments of this solution will be described in detail below with reference to the accompanying drawings or illustrations. These drawings are for illustrative purposes only and depict only exemplary embodiments of the solution to aid the reader's understanding. Therefore, these drawings should not be considered as limitations on the breadth, scope, or applicability of the solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of explanation.

[0014] Figure 1 An example cellular communication network according to an embodiment of the present disclosure is shown, in which the techniques disclosed herein can be implemented; Figure 2 Block diagrams of example base stations and user equipment according to some embodiments of the present disclosure are shown; Figure 3 Example wireless access and backhaul architectures according to some embodiments of this disclosure are shown; and Figure 4 A flowchart illustrating an example method for information transmission in a relay system according to some embodiments of the present disclosure is shown. Detailed Implementation

[0015] 1. Mobile communication technology and environment Figure 1An example wireless communication network and / or system 100 according to an embodiment of this disclosure is illustrated, in which the techniques disclosed herein can be implemented. In the following discussion, wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100". Such an example network 100 includes a base station 102 (hereinafter referred to as "BS 102"; also referred to as a wireless communication node) and a user equipment 104 (hereinafter referred to as "UE 104"; also referred to as a wireless communication device), which can communicate with each other via a communication link 110 (e.g., a wireless communication channel), and a set of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are contained within the corresponding geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0016] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes," which generally practice the methods disclosed herein. According to various embodiments of this solution, such communication nodes may be able to perform wireless and / or wired communication.

[0017] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., Orthogonal Frequency Division Multiplexing (OFDM) / Orthogonal Frequency Division Multiple Access (OFDMA) signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating characteristics, which need not be described in detail herein. In one illustrative embodiment, system 200 may be used in applications such as those described above. Figure 1 In wireless communication environments such as 100, data symbols are transmitted (e.g., sent and received).

[0018] System 200 typically includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes a base station (BS) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with each other as needed via a data communication bus 220. UE 204 includes a user equipment (UE) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for the data transmission described herein.

[0019] As those skilled in the art will understand, system 200 may also include, in addition to Figure 2 Any number of modules other than those shown. Those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described in terms of their functionality. Whether such functionality is implemented in hardware, firmware, or software can depend on the specific application and design constraints imposed on the overall system. Those skilled in the art can implement such functionality appropriately for each specific application, but such implementation decisions should not be construed as limiting the scope of this disclosure.

[0020] According to some embodiments, UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-division duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that the uplink receiver circuitry is coupled to the uplink antenna 232 so that transmissions on the radio transmission link 250 can be received while the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operation of the two transceivers 210 and 230 can be time-coordinated, such that the downlink receiver is coupled to the downlink antenna 212 so that the uplink transmitter is coupled to the uplink antenna 232 while receiving transmissions on the wireless transmission link 250. In some embodiments, there is tight time synchronization with a minimum guard time between changes in the duplex direction.

[0021] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 in a suitable configuration capable of supporting specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to application to specific standards and associated protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0022] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some embodiments, UE 204 may be implemented in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, or a state machine, etc. The processor may also be implemented as a combination of multiple computing devices, such as a combination of a digital signal processor and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors incorporating a digital signal processor core, or any other combination of such configurations.

[0023] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any feasible combination thereof. Memory modules 216 and 234 can be implemented as random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, removable disks, compact optical disc read-only storage (CD-ROM), or any other form of storage medium known in the art. In this respect, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions executed by processor modules 210 and 230, respectively.

[0024] Network communication module 218 broadly represents the hardware, software, firmware, processing logic, and / or other components that enable bidirectional communication between base station 202, base transceiver 210, and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or Global Microwave Access Interoperability (WiMAX) services. In a typical deployment, but without limitation, network communication module 218 provides an 802.3 Ethernet interface, enabling base transceiver 210 to communicate with conventional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and variations thereof, used herein with respect to a specified operation or function, refer to devices, components, circuits, structures, machines, signals, etc., which are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0025] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication devices, wireless communication nodes) for interconnecting and communicating with other systems. The model is divided into seven sub-components or layers, each representing a conceptual set of services provided to the layers above and below it. The OSI model also defines logical networks and efficiently describes computer packet transmission using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Medium Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer is another layer.

[0026] Various exemplary embodiments of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to make and use this solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the exemplary embodiments and applications described and shown herein. Furthermore, the specific order or hierarchy of the steps in the methods disclosed herein is merely an example. Based on design preferences, the specific order or hierarchy of the steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0027] 2. Systems and methods for information transmission in relay systems In some systems, a radio access and backhaul architecture (e.g., Integrated Access and Backhaul (IAB) or Radio Access and Backhaul (WAB)) can be provided to support or allow radio access and backhaul via / through a new radio interface (NR) (e.g., NR technology or features). Supporting radio access and backhaul can, for example, allow / enable flexible and relatively dense deployment of NR cells and reduce / minimize wired transmission infrastructure.

[0028] Relay nodes (such as IAB or WAB nodes) and other compatible nodes can support access and backhaul via NR. The terminating node for NR backhaul on the network side can be referred to as a donor node. A donor node can represent a BS 102 (e.g., gNB, wireless communication node, or transmission and reception point (TRP)) with one or more functions to support or allow radio access and backhaul. Backhaul can be performed via single hops or multiple hops. An example architecture for radio access and backhaul can be combined, but is not limited to, [examples of such architectures]. Figure 3 Describe it.

[0029] Figure 3 An example radio access and backhaul architecture 300 according to some embodiments of the present disclosure is illustrated. This exemplary radio access and backhaul architecture 300 may include at least one UE 104, at least one donor node 302, and relay nodes 304a to 304c (e.g., sometimes referred to as one or more relay nodes 304). This exemplary radio access and backhaul architecture 300 may include, for example, more or fewer components or devices, such as more or fewer relay nodes 304, and is not limited to a combination of... Figure 3The three relay nodes 304 are described. Donor node 302 may correspond to BS 102. Although not explicitly shown, it should be understood that at least donor node 302 can communicate with other devices (e.g., network devices), such as core network functions (e.g., Access Management Function (AMF), Session Management Function (SMF), etc.).

[0030] In this document, for illustrative purposes, relay nodes 304a to 304c may be referred to as relay node 1, relay node 2, and relay node 3, respectively. Relay node 304, which is relatively closer to donor node 302, may be the parent node of relay node 304 that is farther from donor node 302 (or closer to UE 104), or in some arrangements, the reverse. For example, relay node 2 may be the parent node of relay node 1, i.e., relay node 1 may be a child node of relay node 2. Relay node 3 may be the parent node of relay node 2, i.e., relay node 2 may be a child node of relay node 3.

[0031] In various implementations, relay node 304 may include, support, or be configured with gNB functionality (e.g., functionality similar to that of BS 102). For example, gNB functionality may include, but is not limited to, functionality for terminating NR access interfaces to one or more UEs 104, and / or functionality for terminating Xn / Next Generation (NG) protocols to donor node 302 and / or core network functions (e.g., AMF, SMF, etc.). Relay node 304 may include, support, or be configured with a subset of UE functions (e.g., sometimes referred to as mobile terminal (MT)). UE functions may include, for example, at least one of, but not limited to, physical layer functions, layer 2 functions, radio resource control (RRC) functions, and / or non-access stratum (NAS) functions for connecting to another relay node 304, donor node 302, and / or core network, and other functions. In certain scenarios, mapping non-UP services (e.g., control plane (CP) services) to one or more relay nodes 304 within a radio access and backhaul architecture 300 can be challenging. The systems and methods of the technical solutions discussed in this paper can provide features or configurations for supporting (e.g., radio) relay node 304 non-user plane (UP) service mapping.

[0032] Example Implementation Method 1 In some implementations, if a WAB node (e.g., relay node 304) includes gNB functionality, services (e.g., packets or signals) can be transmitted / sent / communicated / forwarded via one or more backhaul links between the WAB node and donor node 302 (e.g., BS 102 or gNB). The service may include at least one of the following: user plane (UP) services; control plane (CP) services (e.g., Xn control plane interface (Xn-C) services and / or next-generation control plane interface (NG-C) services); and / or other types of services such as operation, administration, and maintenance (OAM) services. For example, the service may be routed / transmitted to the user plane function (UPF) of the MT in the WAB donor via one or more Protocol Data Unit (PDU) sessions. Subsequently, the UPF of the MT (e.g., in the WAB donor) may send / forward / transmit the service to the UPF, AMF, and / or other WAB nodes or other WAB donors via Internet Protocol (IP) routing or other routing mechanisms used to route packets to or from one or more devices.

[0033] In some systems, Quality of Service (QoS) flows may not be utilized / used for transmitting control plane signaling (e.g., packets or traffic). Furthermore, in such systems, QoS flow-level QoS parameters may not be configured at the NG RAN node for non-UP services (e.g., CP services, etc.). The system and method of this technical solution can provide features for configuring service mapping for CP services (or other non-UP services) at NG-RAN nodes (e.g., gNBs in relay node 304) and / or donor node 302. In some implementations, donor node 302 may include the functionality of an NG-RAN node and / or a UPF. In some cases, the NG-RAN node may be part of donor node 302.

[0034] To configure service mapping for CP services, donor node 302 (e.g., the UPF of the MT located in donor node 302) can receive / acquire / obtain packets from the AMF of UE 104 in the core network and / or from other NG-RAN nodes or OAM. Donor node 302 can then map the received IP packets to QoS flows according to or based on one or more packet detection rules (PDRs). For example, the PDR may include classifying incoming data packets by the UPF based on a set of packet filters for the downlink (DL) PDR. The PDR may include other criteria or parameters. The UPF can send / transmit PDUs for a PDU session in a tunnel between the core network (e.g., 5GC) and the (radio) access network ((R)AN). The UPF can include at least a QoS Flow Identifier (QFI) in the Next Generation Application Protocol (NGAP) General Packet Radio Service (GPRS) Tunneling Protocol-User Plane (GTP-U) header.

[0035] For example, for packets (e.g., IP packets, such as Xn-C packets) generated by donor node 302, donor node 302 may send / deliver these packets to the UPF of its co-located MT. As discussed herein, the UPF of the MT may, in response to receiving these packets, map the IP packets generated by donor node 302 to a QoS flow.

[0036] Next, in some implementations, the donor node 302 (e.g., a first network node or WAB) can determine the next hop for these packets. The next hop for a packet may refer to the next relay node 304 or network node to which the donor node 302 will send the packet. The determination of the next hop may be described, for example, in conjunction with Example Implementation 4 and / or Example Implementation 5, but is not limited thereto. For non-UP (e.g., CP) services, service mapping information for non-UP services may be configured by core network functions (e.g., SMF and / or AMF) at NG-RAN nodes (e.g., the gNB portion of the WAB node / WAB donor). Non-UP services may include at least one of the following: NG-C signaling / services; Xn-C services; and / or OAM services, etc. The donor node 302 may receive / obtain service mapping information from at least one of the core network functions (e.g., SMF and / or AMF). Service mapping information may include at least one of the following: QoS Flow Identifier (QFI); PDU Session ID; non-UP service type; priority; evolved Radio Access Bearer (E-RAB) ID, etc. Non-UP service types may include at least one of the following, but are not limited to: UE-associated NG-C; non-UE-associated NG-C; UE-associated Xn-C; non-UE-associated Xn-C; non-UP services; and / or OAM services, etc.

[0037] Subsequently, NG-RAN nodes (e.g., the gNB portion of a WAB node / WAB donor) can perform / implement / initiate mapping for PDUs (e.g., packets flowing from QoS to Data Radio Bearers (DRBs) based on, according to, or using service mapping information configured by core network functions (e.g., AMF and / or SMF, etc.).

[0038] Example Implementation Method 2 In some systems, QoS flows may not be used to transmit control plane signaling (e.g., packets or services). Furthermore, in such systems, it may not be necessary to configure QoS flow-level QoS parameters for non-UP services (e.g., CP services, etc.) at NG-RAN nodes (e.g., network nodes, such as at least one of the relay nodes 304). The system and method of this technical solution can provide features for configuring service mapping for CP services (or other non-UP services) at NG-RAN nodes and / or donor nodes 302. In some aspects, the system and method of Example Implementation 2 may be described in conjunction with Example Implementation 1, but are not limited thereto.

[0039] In various implementations, mapping information can be configured at relay node 304 (e.g., IAB node and / or WAB node) and / or donor node 302. While a WAB node may be provided as an example relay node 304, it should be understood that other relay nodes 304, not limited to WAB nodes, may be provided herein. Similarly, for example, while AMD or SMF is provided as an example core network function, it should be understood that other core network functions, not limited to AMF or SMF, may be provided herein.

[0040] WAB nodes and / or donor nodes can obtain / receive mapping configurations (e.g., service mapping information) from AMF and / or SMF (e.g., core network functions). This mapping configuration may include, but is not limited to, at least one of the following: IP-related information; QFI; PDU session ID; E-RAB ID; DRB ID, etc. IP-related information may include, but is not limited to, at least one of the following: IP address; Differentiated Service Code Point (DSCP); and / or flow label. For example, the mapping information can be used to perform mappings from IP, DSCP, and / or flow label to QFI, from QFI to E-RAB and / or DRB, and / or from IP, DSCP, and / or flow label to E-RAB and / or DRB, etc.

[0041] After acquiring the mapping information, donor node 302 can obtain one or more packets from the AMF or other NG-RAN nodes of UE 104 (e.g., the gNB function of at least one of the relay nodes 304). Donor node 302 can determine the next hop (e.g., which WAB node) for forwarding these packets (or for receiving these packets from donor node 302). The determination of the next hop can be described in conjunction with Example Implementation 4 and / or Example Implementation 5, but is not limited thereto. In response to determining the next hop, donor node 302 can map at least one of the one or more IP packets to at least one of the following of the determined WAB node (e.g., the next hop) according to the configured mapping configuration (e.g., service mapping information): QoS flow; E-RAB; and / or DRB, etc.

[0042] For example, for packets generated by donor node 302 (e.g., Xn-C packets), donor node 302 can determine the next hop for receiving these packets. In some cases, for example, the next hop can be determined as relay node 3. In this case, in response to this determination, donor node 302 can map IP packets to the QoS flow, E-RAB, DRB, etc. of relay node 3 according to the configured mapping configuration.

[0043] Example Implementation Method 3 In some systems, core network functions (e.g., AMF and / or SMF) can connect to multiple donor nodes 302 simultaneously. In such systems, determining or identifying which donor node 302 is connected to a specific relay node 304 (e.g., a desired WAB node) can be challenging for the core network functions. The systems and methods discussed herein can provide features or techniques for determining or identifying donor nodes 302 connected to a desired relay node 304, enabling the core network functions to send NG signaling (or other types of signaling) for that relay node 304 to the corresponding donor node 302. In some configurations, for example, these systems and methods can implement these features or techniques for Example Implementation 1 and / or Example Implementation 2.

[0044] For example, relay node 304 (e.g., a WAB node) can send / transmit / provide donor node information to core network functions (e.g., AMF) via Next Generation Application Protocol (NGAP) messages (e.g., NG Establishment Request messages). In some cases, relay node 304 can send donor node information to at least one of the following via Xn messages and / or RRC messages (or other types of messages or signaling): donor node; parent node; child node; neighboring WAB nodes; and / or neighboring donor nodes, etc. Donor node information may include, but is not limited to, at least one of the following: information of network nodes including WAB nodes (e.g., relay node 304); information of donor node 302. The information of relay node 304 and / or donor node 302 may include at least one of the following: gNB ID; cell ID; IP address, etc.

[0045] In various configurations, relay node 304 can communicate with core network functions (e.g., to send donor node information) via a corresponding donor node 302. For example, relay node 304 can send donor node information to core network functions via donor node 302. In some configurations, relay node 304 can send an instruction (or notification) to donor node 302 to cause donor node 302 to send its information (e.g., donor node information) to core network functions. For example, donor node 302 can be an intermediary device between one or more relay nodes 304 and core network functions. Core network functions can store donor node information received / acquired from relay node 304 or donor node 302. Core network functions can, for example, determine the donor node 302 associated with the desired relay node 304 based on the donor node information when sending NG signaling for relay node 304 (e.g., IAB node and / or WAB node).

[0046] Example Implementation Method 4 The systems and methods of this technical solution can provide features or operations that are discussed herein for donor node 302 and / or relay node 304 (e.g., IAB node or WAB node) to determine the next hop (e.g., another relay node 304 or donor node 302) for sending or receiving DL packets, for example, in a single-hop case / scenario. The systems and methods of this technical solution can also provide features or operations that are used by donor node 302 and / or relay node 304 to identify or determine the (co-)location of the MT portion and / or gNB portion of relay node 304 (e.g., performing UE functions or gNB functions respectively).

[0047] Example Configuration 1 of Example Implementation Method 4 In various configurations, relay node 304 may send its information (e.g., relay node information, such as, but not limited to, at least one of the following: IP address; C-RNTI; XnAP ID; parent WAB node information, etc.) to donor node 302 and / or one or more other relay nodes 304 in an XnAP (e.g., Xn Establishment Request) message (or other signaling / message). Relay node 304 may send other information to donor node 302 and / or one or more other relay nodes 304, such as information related to child WAB nodes. Parent relay node information may include at least one of the following: gNB ID; cell ID; and / or IP address, etc.

[0048] Subsequently, donor node 302 or one or more other relay nodes 304 may send its information to relay node 304 in an XnAP message (e.g., a response message). The information from donor node 302 or one or more other relay nodes 304 may include at least one of the following: gNB ID; cell ID; IP address; C-RNTI; XnAP ID; and / or sub-WAB node information; or other types of information.

[0049] Example Configuration 2 of Example Implementation 4 In various configurations, relay node 304 can send its information (e.g., relay node information) to its parent relay node or donor node 302 in an RRC message. This information may include, but is not limited to, at least one of the following: gNB ID; cell ID; IP address; XnAP ID; and / or parent WAB node information.

[0050] Donor node 302 and / or parent relay node may (e.g., in response to receiving the information) send their information to relay node 304 in a response message. In this case, the information sent by donor node 302 and / or parent relay node may include at least one of the following: gNB ID; cell ID; IP address; C-RNTI; XnAP ID; child WAB node information, etc.

[0051] Example Implementation Method 5 The systems and methods of this technical solution can provide features or operations that are discussed herein for donor node 302 and / or relay node 304 (e.g., IAB node or WAB node) to determine the next hop (e.g., another relay node 304 or donor node 302) for sending or receiving DL packets, for example, in multi-hop scenarios. The systems and methods of this technical solution can provide features or operations that are used by donor node 302 and / or relay node 304 to identify or determine the (common) location of the MT portion and / or gNB portion of relay node 304. For example, features or operations of Example Implementation 5 may be added to or replaced by Example Implementation 4 in the description.

[0052] In some configurations, relay node 304 (e.g., WAB node) can send parent node information to donor node 302 and / or child relay nodes via RRC signaling, Xn signaling (e.g., XnAP messages), or other types of signaling. For example, in the example architecture 300, relay node 2 can send information related to relay node 3 to at least one of donor node 302 and / or relay node 1, where relay node 1 is a child relay node of relay node 2.

[0053] In some configurations, relay node 304 can send child node information to its parent relay node and / or donor node 302, and / or send parent node information to its child relay node and / or donor node 302. For example, in the example architecture 300, relay node 2 can send information related to relay node 3 to at least one of donor node 302 and / or relay node 1, or send information related to relay node 1 to at least one of donor node 302 and / or relay node 3. The information of the parent relay node and / or child relay node may include at least one of the following: gNB ID; cell ID; IP address; C-RNTI; XnAP ID, etc.

[0054] Based on the child node information or parent node information of relay node 304, donor node 302 can generate / construct topology information and / or send the topology information to relay node 304 via RRC signaling, Xn signaling, or other types of signaling. For example, the topology information may include at least one of the following: IP address; next-hop ID, etc. The next-hop ID may include, for example, at least one of the following from the parent node of relay node 304, or the child node of relay node 304, or at least the donor node 302: gNodeB (gNB) ID; IP address; C-RNTI; and / or XnAP ID; and other information. In response to receiving the topology information, donor node 302 and / or relay node 304 can determine the next hop for sending services based on the topology information.

[0055] Figure 4 This is a flowchart illustrating an example method 400 for information transmission in a relay system. It can be combined with... Figures 1 to 3 Method 400 is implemented by any one or more of the components and devices detailed herein. In general, in some embodiments, method 400 may be performed by one or more network devices, such as one or more wireless communication devices (e.g., one or more UEs 104), at least one donor node (e.g., a wireless communication node, BS, gNB, or TRP), at least one network node (e.g., an IAB node / IAB donor, a WAB node / WAB donor, etc.), and / or at least one core network function (e.g., SMF, AMF, etc.). Depending on the embodiment, additional, fewer, or different operations may be performed in method 400. At least one aspect of these operations relates to a system, method, apparatus, or computer-readable medium.

[0056] In Operation 402, core network functions (e.g., SMF and / or AMF) may send / transmit / provide / transmit service mapping information to network nodes (e.g., WAB nodes or WAB donors) of the Radio Access and Backhaul (RAB) system. For example, the RAB system may specify... Figure 3 The architecture 300, or can be combined with Figure 3 The architecture described in 300 is not limited to this. In operation 404, the network node can receive / acquire / obtain service mapping information from core network functions. For example, the network node may include or correspond to a WAB node or a WAB donor. The network node may be referred to as the first network node. The network node can communicate with at least one of the following: one or more other network nodes; at least one wireless communication device; or at least one donor node.

[0057] In Operation 406, a network node can perform mapping on one or more packets of non-user plane (UP) services (e.g., PDUs from QoS flows to DRBs) based on or using service mapping information. These packets may include IP packets or are referred to as IP packets. Performing mapping can allow / enable non-UP downlink (DL) service delivery between the network node and other network elements (e.g., AMF, NG-RAN nodes, etc.), and / or allow configuration of parameters for bearers (e.g., DRBs) used for non-UP services.

[0058] In some implementations, non-UP services may include at least one of the following: Next Generation Control Plane Interface (NG-C) services; Xn Control Plane Interface (Xn-C) services; and / or Operation, Administration and Maintenance (OAM) services, etc. In some implementations, for example for non-UP (e.g., CP) services (e.g., NG-C signaling, Xn-C signaling and / or OAM signaling), service mapping information may be configured by the Session Management Function (SMF) or the Access Management Function (AMF), or received from the SMF or AMF.

[0059] In some implementations, service mapping information may include, but is not limited to, at least one of the following: Quality of Service (QoS) Flow Identifier (QFI); Protocol Data Unit (PDU) Session Identifier (ID); Non-UP Service Type; Priority; Evolved Radio Access Bearer (E-RAB) ID; Internet Protocol (IP) related information; and / or Data Radio Bearer (DRB) ID. In some implementations, non-UP service types may include at least one of the following: User Equipment (UE) associated NG-C; Non-UE associated NG-C; UE associated Xn-C; Non-UE associated Xn-C; Non-UP service; and / or OAM service. As some examples, IP related information may include at least one of the following: IP address; Differentiated Service Code Point (DSCP); and / or Flow Label.

[0060] In some implementations, network nodes can use service mapping information to map at least one packet of one or more packets of non-UP services to at least one of the following: one or more QoS flows; E-RAB; and / or DRB. In some implementations, for example, network nodes can send donor node information to donor nodes, parent nodes, child nodes, neighboring WAB nodes, and / or neighboring donor nodes via at least one of other types of messages or signaling such as Xn Application Protocol (XnAP) (e.g., Xn messages) and / or RRC messages. In some implementations, network nodes can send donor node information via Next Generation Application Protocol (NGAP) messages. Sending donor node information allows core network functions (e.g., AMF, SMF, etc.) to identify the donor node to which the network node (e.g., WAB node / WAB donor) is connected, so that the core network function can send NG signaling (or other types of signaling) for the network node to the corresponding donor node (e.g., for forwarding). In some implementations, donor node information may include, but is not limited to, at least one of the following: information about the network node; information about the child nodes of the network node; information about the parent node of the network node; and / or donor node information.

[0061] In some implementations, network nodes can send / provide information to donor nodes and / or WAB nodes (e.g., a second network node). Network nodes can receive response messages (e.g., as a reply to the provided information) from donor nodes or WAB nodes. These response messages may include, but are not limited to, at least one of the following from the donor node or WAB node: gNodeB (gNB) identifier (ID); cell ID; IP address; Cell Radio Network Temporary Identifier (C-RNTI); information about the sub-WAB node; and / or Xn Application Protocol (XnAP) ID.

[0062] In some implementations, network node information may include at least one of the following: IP address; Cell Radio Network Temporary Identifier (C-RNTI); Xn Application Protocol (XnAP) Identifier (ID); child node information; and / or parent node information. In some cases, network node information may include at least one of the following for the network node: gNB ID; cell ID; IP address; child node information; and / or parent node information. Network node information may include other information, not limited to the information discussed herein.

[0063] In some implementations, a network node may send at least one of parent node information and / or child node information to a donor node or a WAB node (e.g., a child node, parent node, or neighbor node). In this case, the WAB node may be a second network node. For example, if the WAB node is a child node of a network node (e.g., a child network node or a child relay node), the network node may send parent node information. In another example, if the WAB node is a parent node of a network node (e.g., a parent network node or a parent relay node), the network node may send child node information.

[0064] Network nodes can receive / acquire topology information from donor nodes or WAB nodes (e.g., as a response to sending at least one of parent node information and / or child node information). This topology information may include, but is not limited to, at least one of the following: IP address; and / or next-hop identifier (ID). In some implementations, the next-hop ID may include, but is not limited to, at least one of the following from at least one of the parent node of the WAB node, and / or the child node of the WAB node, and / or the donor node: gNodeB (gNB) identifier (ID); IP address; Cell Radio Network Temporary Identifier (C-RNTI); and / or Xn Application Protocol (XnAP) ID.

[0065] While various embodiment arrangements of the present solution have been described above, it should be understood that these embodiment arrangements are presented by way of example only and not as a limitation. Similarly, various accompanying drawings may depict exemplary architectures or configurations, provided to enable those skilled in the art to understand exemplary features and functionality of the present solution. However, those skilled in the art will understand that the solution is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one arrangement embodiment may be combined with one or more features of another arrangement embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the illustrative arrangement embodiments described above.

[0066] It should also be understood that any references to elements using identifiers (such as "first" and "second") in this document generally do not restrict the number or order of these elements. Rather, these identifiers are used herein as a convenient means of distinguishing two or more elements or instances of elements. Therefore, a reference to the first element and the second element does not imply that only two elements can be used, or that the first element must precede the second element in some way.

[0067] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0068] Those skilled in the art will also recognize that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, these components, blocks, modules, circuits, and steps have been generally described above in terms of their functions. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not lead to a departure from the scope of this disclosure.

[0069] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or executed by an integrated circuit (IC), which may include: a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communication with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, it may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of multiple computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors incorporating a DSP core, or any other suitable configuration that performs the functions described herein.

[0070] If these functions are implemented in software, they can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. A computer-readable medium can include computer storage media and communication media, with communication media including any medium capable of transferring computer programs or code from one location to another. A storage medium can be any available medium accessible to a computer. For example, but not limited to, such a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and is accessible to a computer.

[0071] In this document, as used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements used to perform the associated functions described herein. Furthermore, for purposes of discussion, various modules are described as discrete modules; however, as will be apparent to those skilled in the art, two or more modules may be combined to form a single module that performs the functions associated with embodiments of this solution.

[0072] Additionally, memory or other storage devices, as well as communication components, may be employed in the arrangement embodiments of this solution. It will be understood that, for clarity, the above description has referenced different functional units and processors in the arrangement embodiments of this solution. However, it will be apparent that any suitable functional distribution can be used among different functional units, processing logic elements, or domains without diminishing the effectiveness of this solution. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to the appropriate means for providing the described functions and do not indicate a strict logical or physical structure or organization.

[0073] Various modifications to the arrangement embodiments described herein will be apparent to those skilled in the art, and the general principles defined herein can be applied to other arrangement embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the arrangement embodiments shown herein, but is intended to be accorded the broadest scope consistent with the inventive features and principles disclosed herein as set forth in the following claims.

Claims

1. A method comprising: Service mapping information is received by network nodes of the wireless access and backhaul communication system; as well as The network node uses the service mapping information to perform mapping on one or more packets of non-user plane (UP) services.

2. The method according to claim 1, wherein, Non-UP services include at least one of the following: Next Generation Control Plane Interface (NG-C) services; Xn Control Plane Interface (Xn-C) services; or Operation, Administration and Maintenance (OAM) services.

3. The method according to claim 1, wherein, The service mapping information is configured by the Session Management Function (SMF) or the Access Management Function (AMF), or received from the SMF or AMF.

4. The method according to claim 1, wherein, The service mapping information includes at least one of the following: Quality of Service (QoS) Flow Identifier (QFI); Protocol Data Unit (PDU) Session Identifier (ID); Non-UP Service Type; Priority; Evolved Radio Access Bearer (E-RAB) ID; Internet Protocol (IP) related information; or Data Radio Bearer (DRB) ID.

5. The method according to claim 4, wherein, The non-UP service type includes at least one of the following: NG-C associated with user equipment (UE); NG-C not associated with UE; Xn-C associated with UE; Xn-C not associated with UE; non-UP service; or OAM service.

6. The method according to claim 4, wherein, The IP-related information includes at least one of the following: IP address; Differentiated Service Code Point (DSCP); or Flow Label.

7. The method according to claim 1, comprising: The network node uses the service mapping information to map at least one of the one or more packets of the non-UP service to at least one of the following: one or more QoS flows; E-RAB; or DRB.

8. The method according to claim 1, comprising: The network node sends donor node information via Xn Application Protocol (XnAP) messages or RRC messages.

9. The method according to claim 1, comprising: The donor node information is sent by the network node via Next Generation Application Protocol (NGAP) messages.

10. The method according to claim 9, wherein, The donor node information includes at least one of the following: information about the network node; information about the child nodes of the network node; information about the parent node of the network node; or information about the donor node.

11. The method according to claim 1, comprising: The network node sends network node information to the donor node or the wireless access and backhaul WAB node. as well as The network node receives a response message from the donor node or the WAB node, the response message including at least one of the following from the donor node or the WAB node: gNodeB (gNB) identifier (ID); cell ID; IP address; cell radio network temporary identifier (C-RNTI); sub-WAB node information; or Xn application protocol (XnAP) ID.

12. The method according to claim 11, wherein: The network node information includes at least one of the following: IP address; Cell Radio Network Temporary Identifier (C-RNTI); Xn Application Protocol (XnAP) Identifier (ID); child node information; or parent node information; or The network node information includes at least one of the following: gNB ID; cell ID; IP address; child node information; or parent node information.

13. The method according to claim 1, comprising: The network node sends at least one of parent node information or child node information to the donor node or WAB node; as well as The network node receives topology information from the donor node or the WAB node, the topology information including at least one of the following: IP address; or next-hop identifier (ID).

14. The method according to claim 13, wherein, The next-hop ID includes at least one of the following from at least one of the parent node of the WAB node, or the child node of the WAB node, or the donor node: gNodeB (gNB) identifier (ID); IP address; Cell Radio Network Temporary Identifier (C-RNTI); or Xn Application Protocol (XnAP) ID.

15. A method comprising: The core network functions send service mapping information to network nodes in the wireless access and backhaul communication systems. In this process, one or more packets of control plane (CP) services are mapped by the network node using the service mapping information.

16. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 1 to 15.

17. An apparatus comprising at least one processor configured to implement the method according to any one of claims 1 to 15.

Images