Relay system information transfer

Abstract

Wireless communication systems, methods, and devices are described. The methods facilitate information transfer between network devices in a relay system. An example wireless communication method includes a network device receiving a first message containing non-user plane (UP) traffic. The method also includes the network device transmitting a second message containing non-UP traffic. Another example wireless communication method includes a network device transmitting signaling radio bearer (SRB) configuration information. The method also includes the network device receiving a radio resource control (RRC) message and a new SRB type associated with the SRB configuration information, where the RRC message contains non-user plane (UP) traffic.

Description

Technical Field

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

[0002] Mobile communication technologies are driving the world toward an increasingly interconnected and networked society. Compared to existing wireless networks, next-generation systems and wireless communication technologies need to support a wider range of use case characteristics and meet more complex, granular access requirements and flexibility.

[0003] Long Term Evolution (LTE) is a wireless communication standard for mobile devices and data terminals developed by the 3rd Generation Partnership Project (3GPP). LTE Advanced (LTE-A) is a wireless communication standard that enhances the LTE standard. The fifth-generation wireless system (5G) iterates and upgrades upon the LTE and LTE-A wireless standards, aiming to achieve higher data rates, a larger number of connections, ultra-low latency, high reliability, and meet the needs of other emerging services. Summary of the Invention

[0004] Techniques for performing information transfer between network devices in a relay system are disclosed. In some embodiments, the network devices include at least one of a donor node, a wireless access and backhaul (WAB) node, or an access and mobility management function (AMF). The disclosed techniques also explicitly specify the content of the transferred information and the type of message used.

[0005] A first exemplary wireless communication method includes: a network device receiving a first message containing non-user plane (UP) traffic. The method further includes: the network device transmitting a second message containing non-UP traffic.

[0006] A second exemplary wireless communication method includes: a network device receiving a first message in a second message, wherein the first message contains non-user plane (UP) traffic. The method further includes: the network device transmitting a third message containing the non-UP traffic.

[0007] A third exemplary wireless communication method includes: a network device transmitting signaling radio bearer (SRB) configuration information. The method further includes: the network device receiving a radio resource control (RRC) message and a new SRB type associated with the SRB configuration information, wherein the RRC message contains non-user plane (UP) traffic.

[0008] A fourth exemplary wireless communication method includes: a network device receiving a Radio Resource Control (RRC) message containing an indication of a Radio Access and Backhaul (WAB) node. The method further includes: the network device transmitting a Next Generation Application Protocol (NGAP) message based on the WAB node indication.

[0009] A fifth exemplary wireless communication method includes: a network device receiving a service request message associated with non-user plane (UP) traffic. The method further includes: the network device transmitting a second message associated with the non-UP traffic based on the service request message.

[0010] Please note that if this patent document discloses a method for transmitting information from a first network device to a second network device, then this patent document also discloses a method for the second network device to receive information from the first network device.

[0011] In yet another exemplary embodiment, an apparatus configured or operable to perform the methods described above is disclosed. The apparatus includes at least one processor configured to implement the methods described above.

[0012] In yet another exemplary embodiment, the above method is implemented in the form of processor-executable code and stored in a non-transitory computer-readable storage medium. When executed by a processor, the code included in the computer-readable storage medium causes the processor to implement the method described in this patent document.

[0013] The above and other aspects and their embodiments are described in more detail in the accompanying drawings, specification and claims. Attached Figure Description

[0014] Figure 1 An exemplary wireless access and backhaul (WAB) architecture is shown.

[0015] Figures 2 to 6 An exemplary flowchart for performing information transmission in a relay system.

[0016] Figure 7 An exemplary block diagram of a hardware platform is shown, which may be part of a network device or a wireless device.

[0017] Figure 8 Exemplary wireless communications including a base station (BS) and a user equipment (UE) based on some implementations of the disclosed technology are shown. Detailed Implementation

[0018] The example headings in the following sections are provided solely for ease of understanding of the disclosed subject matter and do not in any way limit the scope of the claimed subject matter. Therefore, one or more features of one example section may be combined with one or more features of another example section. Furthermore, the term "5G" is used for clarity, but the technology disclosed in this patent document is not limited to 5G technology and can also be applied to wireless systems employing other protocols.

[0019] I. Introduction This patent document describes how to transmit information between network devices in a relay system. The problem addressed in this document is how to support non-user plane (UP) traffic mapping for wireless relay nodes.

[0020] Radio access and backhaul (WAB) architectures (e.g., integrated access and backhaul (IAB) or WAB) support radio access and backhaul via new radio (NR), which enables flexible and very close deployment of NR cells while reducing the need for wired transportation infrastructure.

[0021] Relay nodes (e.g., IAB or WAB nodes) support access and backhaul via NR. The terminating node for NR backhaul on the network side is called the donor node, which represents a next-generation node B (gNB) with additional capabilities to support radio access and backhaul. Backhaul can be performed via single hops or multiple hops. An example of a radio access and backhaul architecture is shown in... Figure 1 As shown in the image. Figure 1 An example of a wireless access and backhaul architecture is shown. Figure 1 In this example, relay node 2 is the parent node of relay node 1, meaning relay node 1 is the child node of relay node 2. Furthermore, relay node 3 is the parent node of relay node 2, meaning relay node 2 is the child node of relay node 3.

[0022] The relay node supports gNB functionality, terminating the NR access interface for User Equipment (UE) and the Xn / NG protocol for the Donor Node / Access and Mobility Management Functions (AMF). In addition to gNB functionality, the relay node also supports a subset of UE functions known as Mobile Terminal Functions (MT), which includes, for example, physical layer, layer 2, Radio Resource Control (RRC), and Non-Access Stratum (NAS) functions, to connect to another relay node or donor node and the core network.

[0023] Please note that in the following embodiments, the step numbers do not imply that these steps must be performed in that order in time.

[0024] II. Example 1 If the WAB node has gNB functionality, traffic needs to be transmitted via one or more backhaul links between the WAB node and the donor node. This traffic includes UP traffic, control plane (CP) traffic (including Xn-Control Plane Interface (Xn-C) and Next Generation Radio Access Network-Control Plane Interface (Ng-C) traffic), or operation, administration, and maintenance (OAM) traffic. For example, UP traffic is routed via one or more Protocol Data Unit (PDU) sessions to the User Plane Function (UPF) of the MT in the WAB donor, and then routed from the MT's UPF to the UE's UPF via Internet Protocol (IP). However, non-UP traffic is not transmitted via PDU sessions. The question is how to transmit CP traffic between the WAB node and the parent / donor node.

[0025] Example 1 provides a solution, for example, for traffic delivery from a WAB node to an AMF / Next Generation Radio Access Network (NGRAN) node.

[0026] Step 1: Uplink (UL) non-UP traffic (e.g., Xn-C, Ng-C, or OAM traffic) is included in an RRC message and sent from the WAB node to the donor node. In some embodiments, the RRC message includes the non-UP traffic type, priority, source node information, and destination node information. Specifically, the non-UP type includes one of the following: NG-C associated with the UE, NG-C associated with a non-UE, Xn-C associated with the UE, Xn-C associated with a non-UE, non-UP traffic, and OAM traffic. The source node information is related to the WAB node and includes one of the following: IP address, gNB identifier (ID), cell ID, Xn Application Protocol (XnAP) UEID, and Next Generation Application Protocol (NGAP) UE ID. The destination node information includes one of the following: IP address, gNB ID, cell ID, and AMF identifier.

[0027] Step 2: The donor node sends the non-UP traffic received from the WAB node to the AMF via NGAP messages; or the donor node sends the non-UP traffic received from the WAB node to the NG RAN node via XnAP messages. NGAP / XnAP messages contain the non-UP traffic type, priority, source node information, and destination node information.

[0028] III. Example 2 If the WAB node has gNB functionality, traffic needs to be transmitted via one or more backhaul links between the WAB node and the donor node. This traffic includes UP traffic, CP traffic (including Xn-C and Ng-C traffic), or OAM traffic. For example, UP traffic is routed via one or more PDU sessions to the UPF of the MT in the WAB donor, and then via IP routing from the MT's UPF to the UE's UPF. However, non-UP traffic is not transmitted via PDU sessions. The challenge lies in how to transmit CP traffic between the WAB node and the parent / donor node.

[0029] Example 2 provides a solution, for example, for traffic from an AMF / NG RAN node to a WAB node.

[0030] Step 1: The AMF contains the first NGAP message or the first XnAP message in the second NGAP message and sends it to the donor node; or the NG-RAN node contains the first XnAP message or the first NGAP message in the second XnAP message and sends it to the donor node or another WAB node (e.g., a child WAB node, a parent WAB node, or an adjacent WAB node).

[0031] The second NGAP / XnAP message contains one of the following: non-UP traffic type, priority, source node information, and destination node information. Specifically, the non-UP type includes one of the following: NG-C associated with the UE, NG-C associated with a non-UE, Xn-C associated with the UE, Xn-C associated with a non-UE, non-UP traffic, and OAM traffic. The source node information is related to the NG-RAN node or AMF and includes one of the following: IP address, gNB ID, cell ID, AMF ID, XnAP UE ID, and NGAP UEID. The destination node information includes one of the following: IP address, gNB ID, and cell ID.

[0032] Step 2: The donor node receives non-UP traffic from the AMF or other NG-RAN nodes or OAM. The donor node includes the non-UP traffic in an RRC message and sends the RRC message to the WAB node. The RRC message contains one of the following: non-UP traffic type, priority, source node information, or destination node information.

[0033] IV. Example 3 If the WAB node has gNB functionality, traffic needs to be transmitted via one or more backhaul links between the WAB node and the donor node. This traffic includes UP traffic, CP traffic (including Xn-C and Ng-C traffic), or OAM traffic. For example, UP traffic is routed via one or more PDU sessions to the UPF of the MT in the WAB donor, and then via IP routing from the MT's UPF to the UE's UPF. However, non-UP traffic is not transmitted via PDU sessions. The challenge lies in how to transmit CP traffic between the WAB node and the parent / donor node.

[0034] Example 3 provides a solution for delivering non-UP traffic and new signaling radio bearer (SRB) types via RRC messaging.

[0035] The difference between Solution 1 and Solution 2 is that in Solution 2, non-UP traffic is delivered via RRC messages along with a new SRB type. In Solution 2, a new SRB type is configured at the WAB node for delivering non-UP traffic through the donor / parent node. The donor / parent node sends SRB configuration information to the WAB node, for example, via RRC or Xn messages. The SRB configuration information includes one of the following: SRB identifier (e.g., 5), priority, Packet Data Convergence Protocol (PDCP) parameters, and non-UP traffic type.

[0036] V. Example 4 Example 4 addresses the problem of how to establish a PDU session / data radio bearer (DRB) for delivering non-UP traffic (e.g., Xn-C, Ng-C, or OAM traffic) to WAB nodes.

[0037] Step 1: MT performs the initial access procedure.

[0038] Step 2: The MT portion of the WAB node sends a service request message to the AMF serving that MT to request the establishment or modification of a PDU session (e.g., for backhaul).

[0039] Specifically, during the service request process, the WAB node includes the WAB node instruction in the RRC message and sends the RRC message to its parent node / donor node.

[0040] Subsequently, the parent / donor node sends the NGAP initial UE message to the AMF. The NGAP message contains one of the following: WAB node indication, non-UP traffic indication, non-UP traffic type, and priority. The non-UP traffic type contains one of the following: UE-associated NG-C, non-UE-associated NG-C, UE-associated Xn-C, non-UE-associated Xn-C, non-UP traffic, and OAM traffic.

[0041] Step 3: AMF initiates subsequent procedures to establish a PDU session / DRB for traffic transfer to the WAB node.

[0042] VI. Example 5 The MT should initiate a service request process to trigger the establishment of a PDU session for delivering Xn-User Plane Interface (Xn-U) / Next Generation Radio Access Network-User Plane Interface (Ng-U) traffic to the WAB node. The challenge lies in how to perform PDU session management for the WAB node used for UP traffic delivery. Example 5 provides a solution.

[0043] Step 1: Trigger the service request process through the UE or network served by the WAB node.

[0044] Step 2: The WAB node serving the UE (e.g., the gNB part of the WAB node) receives the N2 request from the AMF (N2 is the interface between the NGRAN node and the AMF).

[0045] Step 3: The gNB portion of the WAB node delivers the information received in the N2 request message to the MT portion of the WAB node. Subsequently, the MT portion of the WAB node initiates a service request message to the AMF serving that MT to request the establishment / modification of a PDU session for backhaul traffic delivery. This service request message contains one of the following: WAB node indication, priority, traffic type (NG-U traffic, Xn-U traffic, UP traffic, NG-C associated with UE, NG-C associated with non-UE, Xn-C associated with UE, Xn-C associated with non-UE, non-UP traffic, OAM traffic), and traffic quality of service (QoS) information.

[0046] Step 4: The AMF sends a message to the Session Management Function (SMF) containing one of the following: WAB node indication, traffic type (NG-U traffic, Xn-U traffic, UP traffic, NG-C associated with UE, NG-C associated with non-UE, Xn-C associated with UE, Xn-C associated with non-UE, non-UP traffic, OAM traffic), and QoS information for the traffic.

[0047] Figure 2 This is a first exemplary flowchart for performing information transmission in a relay system. Operation 202 includes: the network device receiving a first message containing non-user plane (UP) traffic. Operation 204 includes: the network device transmitting a second message containing non-UP traffic. In some embodiments, the method may be implemented according to embodiment 1. In some embodiments, further steps of the method may be performed based on system performance superior to conventional protocols.

[0048] In some embodiments, the network device is a donor node, and receiving the first message includes receiving a Radio Resource Control (RRC) message from a Radio Access and Backhaul (WAB) node.

[0049] In some embodiments, the first message includes at least one of non-UP traffic type, priority, source node information, or target node information, wherein the non-UP traffic type includes at least one of Next Generation Radio Access Network-Control Plane Interface (NG-C) traffic associated with a User Equipment (UE), NG-C traffic associated with a non-UE, Xn-Control Plane Interface (Xn-C) traffic associated with a UE, Xn-C traffic associated with a non-UE, non-UP traffic, or Operation, Administration, and Maintenance (OAM) traffic, wherein the source node information is related to a Radio Access and Backhaul (WAB) node and includes at least one of Internet Protocol (IP) address, Next Generation Node B (gNB) identifier (ID), cell ID, Xn Application Protocol (XnAP) UE ID, or Next Generation Application Protocol (NGAP) UE ID, and wherein the target node information includes at least one of IP address, gNB ID, cell ID, or Access and Mobility Management Function (AMF) identifier.

[0050] In some embodiments, transmitting the second message includes transmitting a Next Generation Application Protocol (NGAP) message to the Access and Mobility Management Function (AMF) or transmitting an Xn Application Protocol (XnAP) message to a Next Generation Radio Access Network (NG RAN) node.

[0051] In some embodiments, the second message includes at least one of non-UP traffic type, priority, source node information, or target node information.

[0052] Figure 3 This is a second exemplary flowchart for performing information transmission in a relay system. Operation 302 includes: the network device receiving a first message in a second message, wherein the first message contains non-user plane (UP) traffic. Operation 304 includes: the network device transmitting a third message containing non-UP traffic. In some embodiments, the method may be implemented according to embodiment 2. In some embodiments, further steps of the method may be performed based on system performance superior to conventional protocols.

[0053] In some embodiments, the network device is a donor node, and receiving the first message in the second message includes: receiving a first NGAP message or a first Xn Application Protocol (XnAP) message in a second Next Generation Application Protocol (NGAP) message from the Access and Mobility Management Function (AMF).

[0054] In some embodiments, the network device is a donor node, a parent radio access and backhaul (WAB) node, a child WAB node, or a neighboring WAB node, and receiving the first message in the second message includes: receiving the first XnAP message or the first Next Generation Application Protocol (NGAP) message in the second XnAP message from the Next Generation Radio Access Network (NG RAN) node.

[0055] In some embodiments, the second message includes at least one of non-UP traffic type, priority, source node information, or target node information.

[0056] In some embodiments, transmitting a third message includes transmitting a Radio Resource Control (RRC) message to a Radio Access and Backhaul (WAB) node, wherein the RRC message contains at least one of a non-UP traffic type, priority, source node information, or destination node information.

[0057] Figure 4 This is a third exemplary flowchart for performing information transfer in a relay system. Operation 402 includes: the network device transmitting Signaling Radio Bearer (SRB) configuration information. Operation 404 includes: the network device receiving a Radio Resource Control (RRC) message and a new SRB type associated with the SRB configuration information, wherein the RRC message contains non-user plane (UP) traffic. In some embodiments, the method may be implemented according to Embodiment 3. In some embodiments, further steps of the method may be performed based on system performance superior to conventional protocols.

[0058] In some embodiments, the network device is a donor node or a parent node, and transmitting SRB configuration information includes transmitting the SRB configuration information to a Radio Access and Backhaul (WAB) node via an RRC message or an Xn message, wherein the SRB configuration information includes at least one of an SRB identifier, priority, Packet Data Convergence Protocol (PDCP) parameters, or non-UP traffic type.

[0059] Figure 5 This is a fourth exemplary flowchart for performing information transfer in a relay system. Operation 502 includes: the network device receiving a Radio Resource Control (RRC) message containing an indication of a Radio Access and Backhaul (WAB) node. Operation 504 includes: the network device transmitting a Next Generation Application Protocol (NGAP) message based on the WAB node indication. In some embodiments, the method may be implemented according to embodiment 4. In some embodiments, further steps of the method may be performed based on system performance superior to conventional protocols.

[0060] In some embodiments, the network device is a donor node or a parent node, and receiving an RRC message includes receiving the RRC message from a WAB node, and transmitting an NGAP message includes transmitting the NGAP message to an Access and Mobility Management Function (AMF), wherein the NGAP message contains at least one of a WAB node indication, a non-user plane (UP) traffic indication, a non-UP traffic type, or a priority.

[0061] Figure 6 This is a fifth exemplary flowchart for performing information transmission in a relay system. Operation 602 includes: the network device receiving a service request message associated with non-user plane (UP) traffic. Operation 604 includes: the network device transmitting a second message associated with the non-UP traffic based on the service request message. In some embodiments, the method may be implemented according to embodiment 5. In some embodiments, further steps of the method may be performed based on system performance superior to conventional protocols.

[0062] In some embodiments, the network device is an Access and Mobility Management Function (AMF), receiving a service request message includes receiving a service request message from the Mobile Terminal Function (MT) portion of a Radio Access and Backhaul (WAB) node, and transmitting a second message includes transmitting a second message to a Session Management Function (SMF).

[0063] In some embodiments, each of the service request message or the second message includes at least one of the following: a radio access and backhaul (WAB) node indication, quality of service (QoS) information for non-UP traffic, priority, or traffic type, wherein the traffic type includes at least one of the following: next-generation radio access network-user plane interface (NG-U) traffic, Xn-user plane interface (Xn-U) traffic, UP traffic, next-generation radio access network-control plane interface (NG-C) traffic associated with a user equipment (UE), NG-C traffic associated with a non-UE, Xn-control plane interface (Xn-C) traffic associated with a UE, Xn-C traffic associated with a non-UE, non-UP traffic, or operation, administration, and maintenance (OAM) traffic.

[0064] Figure 7 An exemplary block diagram of a hardware platform 700 is shown. This hardware platform may be part of a network device (e.g., a donor node, WAB node, AMF, or SMF) or a wireless device (e.g., a user equipment (UE)). The hardware platform 700 includes at least one processor 710 and a memory 705 storing instructions thereon. When executed by the processor 710, the instructions configure the hardware platform 700 to perform... Figures 1 to 6And the operations described in the various embodiments described in this patent document. Transmitter 715 transmits or sends information or data to another device. For example, a network device transmitter may send a message to a user equipment. Receiver 720 receives information or data transmitted or sent by another device. For example, a user equipment may receive a message from a network device. For example, a UE, wireless device, or network device (as described in this document) may be implemented using hardware platform 700.

[0065] The implementation methods described above are applied to wireless communication. Figure 8 An example of a wireless communication system (e.g., a 5G or NR cellular network) is illustrated, comprising a base station 820 and one or more user equipments (UEs) 811, 812, and 813. In some embodiments, the UE accesses the BS (e.g., the network) using a communication link to the network (sometimes referred to as the uplink, as shown by dashed arrows 831, 832, 833), which subsequently enables subsequent communication from the BS to the UE (e.g., as shown along the direction from the network to the UE, sometimes referred to as the downlink, as shown by arrows 841, 842, 843). In some embodiments, the BS sends information to the UE (sometimes referred to as the downlink, as shown by arrows 841, 842, 843), which subsequently enables subsequent communication from the UE to the BS (e.g., as shown along the direction from the UE to the BS, sometimes referred to as the uplink, as shown by dashed arrows 831, 832, 833). The UE may be, for example, a smartphone, tablet, mobile computer, machine-to-machine (M2M) device, Internet of Things (IoT) device, etc. The UE described in this document can communicatively connect to... Figure 8 The base station 820 is depicted in the image.

[0066] Those skilled in the art will understand that this patent document discloses a method for performing information transmission via network devices (such as donor nodes, WAB nodes, or AMFs), which is beneficial for relay systems. This patent document clearly specifies the content of the transmitted information and the type of message used. This patent document provides an effective and efficient information transmission method for relay systems.

[0067] Some embodiments described herein are described in the general context of a method or process that, in one embodiment, can be implemented by a computer program product contained in a computer-readable medium, including computer-executable instructions, such as program code executed by a computer in a networked environment. The computer-readable medium may 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 may include non-transitory storage media. Generally, a program module may include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular 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 such steps or processes.

[0068] Some embodiments of the disclosed examples may 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). Some implementations may additionally or alternatively include digital signal processors (DSPs), which are special-purpose microprocessors with an architecture optimized for the operational requirements of digital signal processing associated with the disclosed functions of this application. Similarly, various components or sub-components within each module may be implemented using software, hardware, or firmware. Connectivity between modules and / or components within modules may 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.

[0069] While this document contains numerous details, these details should not be construed as limiting the scope of the claimed invention or any potentially claimed scope, 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 in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although features may be described above as functioning in certain combinations, or even initially claimed, 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 order or sequential sequence shown, or requiring all shown operations to achieve the desired result.

[0070] Only a few implementation methods and examples have been described, and other implementations, enhancements and variations may be made based on what is described and shown in this patent document.

Claims

1. A wireless communication method, comprising: The network device receives the first message containing non-user plane (UP) traffic; as well as The network device transmits a second message containing the non-UP traffic.

2. The method of claim 1, wherein the network device is a donor node, and wherein receiving the first message includes: Receive Radio Resource Control (RRC) messages from the Radio Access and Backhaul (WAB) node.

3. The method according to claim 1 or 2, wherein the first message includes at least one of non-UP traffic type, priority, source node information, or target node information, wherein the non-UP traffic type includes at least one of Next Generation Radio Access Network-Control Plane Interface (NG-C) traffic associated with a User Equipment (UE), NG-C traffic associated with a non-UE, Xn-Control Plane Interface (Xn-C) traffic associated with a UE, Xn-C traffic associated with a non-UE, non-UP traffic, or Operation, Administration, and Maintenance (OAM) traffic, wherein the source node information is related to a Radio Access and Backhaul (WAB) node and includes at least one of Internet Protocol (IP) address, Next Generation Node B (gNB) identifier (ID), cell ID, Xn Application Protocol (XnAP) UE ID, or Next Generation Application Protocol (NGAP) UE ID, and wherein the target node information includes at least one of IP address, gNB ID, cell ID, or Access and Mobility Management Function (AMF) identifier.

4. The method according to any one of claims 1 to 3, wherein transmitting the second message comprises: Transmit Next Generation Application Protocol (NGAP) messages to the Access and Mobility Management Function (AMF), or transmit Xn Application Protocol (XnAP) messages to Next Generation Radio Access Network (NG RAN) nodes.

5. The method according to any one of claims 1 to 4, wherein the second message includes at least one of non-UP traffic type, priority, source node information, or target node information.

6. A wireless communication method, comprising: The network device receives the first message in the second message, wherein the first message contains non-user plane (UP) traffic; as well as The network device transmits a third message containing the non-UP traffic.

7. The method of claim 6, wherein the network device is a donor node, and wherein receiving the first message in the second message includes: Receive the first NGAP message or the first Xn Application Protocol (XnAP) message from the second Next Generation Application Protocol (NGAP) message from the Access and Mobility Management Function (AMF).

8. The method of claim 6, wherein the network device is a donor node, a parent Wireless Access and Backhaul (WAB) node, a child WAB node, or a neighboring WAB node, and wherein receiving the first message in the second message includes: Receive the first XnAP message or the first Next Generation Application Protocol (NGAP) message from the second XnAP message from the Next Generation Radio Access Network (NG RAN) node.

9. The method according to any one of claims 6 to 8, wherein the second message includes at least one of non-UP traffic type, priority, source node information, or target node information.

10. The method according to any one of claims 6 to 9, wherein transmitting the third message comprises: A radio resource control (RRC) message is transmitted to a radio access and backhaul (WAB) node, wherein the RRC message contains at least one of a non-UP traffic type, priority, source node information, or destination node information.

11. A wireless communication method, comprising: Network devices transmit signaling radio bearer (SRB) configuration information; as well as The network device receives a Radio Resource Control (RRC) message and a new SRB type associated with the SRB configuration information, wherein the RRC message contains non-user plane (UP) traffic.

12. The method of claim 11, wherein the network device is a donor node or a parent node, wherein transmitting the SRB configuration information includes: The SRB configuration information is transmitted to the Radio Access and Backhaul (WAB) node via an RRC message or an Xn message, wherein the SRB configuration information includes at least one of an SRB identifier, priority, Packet Data Convergence Protocol (PDCP) parameters, or non-UP traffic type.

13. A wireless communication method, comprising: The network device receives a Radio Resource Control (RRC) message containing an indication of the Radio Access and Backhaul (WAB) node; as well as The network device transmits Next Generation Application Protocol (NGAP) messages based on the instructions of the WAB node.

14. The method of claim 13, wherein the network device is a donor node or a parent node, wherein receiving the RRC message includes: Receiving the RRC message from the WAB node, wherein transmitting the NGAP message includes: transmitting the NGAP message to the Access and Mobility Management Function (AMF), and wherein the NGAP message contains at least one of the WAB node indication, non-user plane (UP) traffic indication, non-UP traffic type, or priority.

15. A wireless communication method, comprising: Network devices receive service request messages associated with non-user plane (UP) traffic; as well as The network device transmits a second message associated with the non-UP traffic based on the service request message.

16. The method of claim 15, wherein the network device is an Access and Mobility Management Function (AMF), wherein receiving the service request message includes: Receiving the service request message from the Mobile Terminal Function (MT) portion of the Wireless Access and Backhaul (WAB) node, wherein transmitting the second message includes transmitting the second message to the Session Management Function (SMF).

17. The method of claim 15 or 16, wherein each of the service request message or the second message comprises at least one of the following: a radio access and backhaul (WAB) node indication, quality of service (QoS) information of the non-UP traffic, priority, or traffic type, wherein the traffic type comprises at least one of the following: Next Generation Radio Access Network - User Plane Interface (NG-U) traffic, Xn-User Plane Interface (Xn-U) traffic, UP traffic, Next Generation Radio Access Network - Control Plane Interface (NG-C) traffic associated with a User Equipment (UE), NG-C traffic associated with a non-UE, Xn-Control Plane Interface (Xn-C) traffic associated with a UE, Xn-C traffic associated with a non-UE, non-UP traffic, or Operation, Administration, and Maintenance (OAM) traffic.

18. A wireless communication device, comprising a processor, wherein the processor is configured to implement the method of any one or more of claims 1 to 17.

19. A computer-readable program storage medium having code stored thereon, which, when executed by a processor, causes the processor to perform the method of any one or more of claims 1 to 17.

Images