WO2024169800A1

WO2024169800A1 - Pdu session establishment

Info

Publication number: WO2024169800A1
Application number: PCT/CN2024/076445
Authority: WO
Inventors: Haiyan Luo; Mingzeng Dai; Yibin ZHUO; Lianhai WU
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2024-02-06
Filing date: 2024-02-06
Publication date: 2024-08-22
Anticipated expiration: 2026-08-06

Abstract

Various aspects of the present disclosure relate to protocol data unit (PDU) session establishment. In an aspect, an AMF receives a PDU session establishment request message in a NAS message from a MWAB-UE, the MWAB-UE and a MWAB-gNB are collocated to compose a MWAB node. The AMF transmits the PDU session establishment request message to a SMF. In case of receiving a PDU session establishment accept message from the SMF, the AMF then transmits the PDU session establishment accept message for the MWAB-UE to the MWAB-UE. The AMF further preserves a first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE, and the second information of MWAB-gNB is indicated by the PDU session establishment request message or the PDU session establishment accept message. In this way, a PDU session establishment is performed between MWAB-UE and a MWAB-UE-UPF.

Description

PDU SESSION ESTABLISHMENT

The present disclosure relates to wireless communications, and more specifically to protocol data unit (PDU) session establishment.

BACKGROUND

A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .

In 3GPP Rel-18, service&system aspects2 (SA2) conducted a study followed by a work item on vehicle-mounted relays (VMR) . During the study, it was agreed to limit the scope of the work to the integrated access and backhaul (IAB) architecture, whereby the IAB node consist of an IAB-mobile terminal (MT) and an IAB-distributed unit (DU) , with the IAB-DU establishing an F1 interface with a donor centralized unit (CU) over a wireless link. However, there are other architecture options to achieve the functionality of VMR.

SUMMARY

The present disclosure relates to methods, apparatuses, and systems that support PDU session establishment, especially, PDU session establishment for a mobile gNB with wireless access backhauling (MWAB) node.

Some implementations of the method and devices described herein include, receiving, from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , a protocol data unit (PDU) session establishment request message in a non-access stratum (NAS) message, wherein the MWAB-UE and a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node; transmitting, to a session management function (SMF) , the PDU session establishment request message; and transmitting, to the MWAB-UE, a PDU session establishment accept message for the MWAB-UE in case of receiving the PDU session establishment accept message from the SMF; further include preserving, a first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE, wherein the second information of MWAB-gNB is indicated by the PDU session establishment request message or the PDU session establishment accept message. In this way, the PDU session establishment is perform between MWAB-UE and a MWAB-UE-UPF.

Some implementations of the method and apparatuses described herein may further include receiving, from the SMF, the second information of the MWAB-gNB along with the PDU session establishment accept message.

Some implementations of the method and apparatuses described herein may further include transmitting, to the MWAB-gNB, the IP address of the AMF in case of receiving an indication of the MWAB node in an initial UE message.

Some implementations of the method and apparatuses described herein may further include transmitting, to the MWAB-UE, an indication of establishing the PDU session for N2 interface in case of receiving an indication of the MWAB node in an initial UE message.

Some implementations of the method and apparatuses described herein may further include preserving a second mapping between the second information of the MWAB-gNB and information of a user plane function for the MWAB-UE (MWAB-UE-UPF) in case of receiving an NG setup request message originated from the MWAB-gNB via the MWAB-UE-UPF.

Some implementations of the method and apparatuses described herein may further include generating a NG setup response message for the MWAB-gNB; and transmitting, to the MWAB-UE-UPF, the NG setup response message based on the second mapping.

Some implementations of the method and apparatuses described herein may further include transmitting the PDU session establishment request message by: transmitting, to the SMF, the IP address of the AMF along with the PDU session establishment request message.

In some implementations of the method and apparatuses described herein, the second information of MWAB-gNB being indicated by the PDU session establishment request message may comprise one of the following: the PDU session establishment request message comprises the second information of the MWAB-gNB; or the PDU session establishment request message is transmitted with the second information of the MWAB-gNB.

In some implementations of the method and apparatuses described herein, the NAS message may further comprise an indication of establishing the PDU session for N2 interface.

In some implementations of the method and apparatuses described herein, the second information of the MWAB-gNB may comprise one of; an identity of the MWAB-gNB; an IP address of the MWAB-gNB; or the identity of the MWAB-gNB and the IP address of the MWAB-gNB; or the information of the MWAB-UE-UPF may comprise an IP address of the MWAB-UE-UPF.

Some implementations of the method and devices described herein include, receiving, from an access and mobility management function (AMF) , a protocol data unit (PDU) session establishment request message originated from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , wherein the PDU session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) , and wherein the MWAB-UE and the MWAB-gNB are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node; generating a PDU session establishment accept message for the MWAB-UE; and transmitting, to the MWAB-UE via the AMF, the PDU session establishment accept message.

Some implementations of the method and apparatuses described herein may further include receiving the PDU session establishment request message by: receiving, from the AMF, an IP address of the AMF along with the PDU session establishment request message.

Some implementations of the method and apparatuses described herein may further include configuring a user plane function (UPF) for the MWAB-UE (MWAB-UE-UPF) with a packet filter set comprising an IP address of the AMF and an IP address of the MWAB-gNB.

Some implementations of the method and apparatuses described herein may further include allocating the IP address of the MWAB-gNB based on one of the indication of requesting the IP address of the MWAB-gNB, or the IP address of the AMF.

Some implementations of the method and apparatuses described herein may further include determining the IP address of the AMF as a source IP address and the IP address of the MWAB-gNB as a destination IP address for a downlink (DL) in the packet filter set; or determining the IP address of the MWAB-gNB as a source IP address and the IP address of the AMF as a destination IP address for an uplink (UL) in the packet filter set.

Some implementations of the method and apparatuses described herein may further include transmitting the PDU session establishment accept message by: transmitting second information of the MWAB-gNB along with the PDU session establishment accept message to the AMF.

In some implementations of the method and apparatuses described herein, the first information of MWAB-gNB may comprise one of the following: an Internet protocol (IP) address of the MWAB-gNB, or an indication for requesting the IP address of the MWAB-gNB.

In some implementations of the method and apparatuses described herein, the PDU session establishment accept message may comprise one of: an IP address of the AMF; the IP address of the AMF and an IP address of the MWAB-gNB.

In some implementations of the method and apparatuses described herein, the second information of the MWAB-gNB may comprise one of the following: an identity of the MWAB-gNB; an IP address of the MWAB-gNB; or the identity of the MWAB-gNB and the IP address of the MWAB-gNB.

Some implementations of the method and devices described herein include, transmitting, to a session management function (SMF) , a protocol data unit (PDU) session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) via an access and mobility management function (AMF) ; and receiving, from the SMF, a PDU session establishment accept message.

Some implementations of the method and apparatuses described herein may further include transmitting, to the WMAB-gNB, the IP address of the AMF in the case that the PDU session establishment accept message comprises the IP address of the AMF; and transmitting, to the MWAB-gNB, the IP address of the AMF and the IP address of the MWAB-gNB in the case that the PDU session establishment accept message comprises the IP address of the AMF and the IP address of the MWAB-gNB.

In some implementations of the method and apparatuses described herein, the first information of the MWAB-gNB may comprise one of the following: an Internet protocol (IP) address of the MWAB-gNB, or an indication for requesting the IP address of the MWAB-gNB.

Some implementations of the method and apparatuses described herein may further include transmitting, to the AMF, one of the following along with the PDU session establishment request message: second information of MWAB-gNB, or an indication of establishing the PDU session for N2 interface.

In some implementations of the method and apparatuses described herein, the second information of MWAB-gNB may comprise one of: an identity of the MWAB-gNB; an IP address of the MWAB-gNB; or the identity of the MWAB-gNB and the IP address of the MWAB-gNB.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example of a wireless communications system that supports PDU session establishment in accordance with aspects of the present disclosure.

FIG. 1B illustrates an example of a MWAB node associated with aspects of the present disclosure.

FIG. 1C illustrates example connections for MWAB node associated with aspects of the present disclosure.

FIG. 1D illustrates an example of MWAB network associated with aspects of the present disclosure.

FIG. 2 illustrates an example signaling chart illustrating an example process in accordance with aspects of the present disclosure.

FIG. 3 illustrates protocol stacks for MWAB node in accordance with aspects of the present disclosure.

FIG. 4 illustrates an example process in accordance with aspects of the present disclosure.

FIG. 5 illustrates another example process in accordance with aspects of the present disclosure.

FIG. 6 illustrates an example NG setup procedure in accordance with aspects of the present disclosure.

FIG. 7 illustrates yet another example process in accordance with aspects of the present disclosure.

FIGS. 8 through 10 illustrates an example of a device that support PDU session establishment in accordance with aspects of the present disclosure.

FIGS. 11 through 13 illustrates an example of a processor that support PDU session establishment in accordance with aspects of the present disclosure.

FIG. 14 illustrates a flowchart of a method that supports PDU session establishment in accordance with aspects of the present disclosure.

FIG. 15 illustrates a flowchart of a method that supports PDU session establishment in accordance with aspects of the present disclosure.

FIG. 16 illustrates a flowchart of a method that supports PDU session establishment in accordance with aspects of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar elements.

DETAILED DESCRIPTION

Principles of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein may be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first” and “second” or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

As used herein, the term “communication network” refers to a network following any suitable communication standards, such as, 5G new radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) , and so on. Further, the communications between a user equipment and a network device in the communication network may be performed according to any suitable generation communication protocols, including but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will also be future type communication technologies and systems in which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned systems.

As used herein, the term “network device” generally refers to a node in a communication network via which a user equipment can access the communication network and receive services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , a radio access network (RAN) node, an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , an infrastructure device for a V2X (vehicle-to-everything) communication, a transmission and reception point (TRP) , a reception point (RP) , a remote radio head (RRH) , a relay, an integrated access and backhaul (IAB) node, a low power node such as a femto BS, a pico BS, and so forth, depending on the applied terminology and technology. The network device may further refer to a network function (NF) in the core network, for example, a SMF, an AMF, a PCF, a UPF or devices with same function in future network architectures, and so forth.

As used herein, the term “user equipment (UE) ” generally refers to any end device that may be capable of wireless communications. By way of example rather than a limitation, a user equipment may also be referred to as a mobile termination (MT) . Besides, a user equipment may also be referred to as a communication device, a terminal device, an end user device, a subscriber station (SS) , an unmanned aerial vehicle (UAV) , a portable subscriber station, a mobile station (MS) , or an access terminal (AT) . The user equipment may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable user equipment, a personal digital assistant (PDA) , a portable computer, a desktop computer, an image capture user equipment such as a digital camera, a gaming user equipment, a music storage and playback appliance, a vehicle-mounted wireless user equipment, a wireless endpoint, a mobile station, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , a USB dongle, a smart device, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device (for example, a remote surgery device) , an industrial device (for example, a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms: “user equipment, ” “communication device, ” “terminal, ” “mobile terminal, ” “user equipment” and “UE, ” may be used interchangeably.

FIG. 1A illustrates an example of a wireless communications system 100 that supports data collection in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.

The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1A. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1A. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.

A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) . In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .

In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.

An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) . In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .

Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.

Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs) . In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .

A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .

In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.

There are some architecture options to achieve the functionality of VMR as defined in TS 22.261, for instance the so-called “Velcro” solution whereby the relay node consists of a UE co-located with a full gNB, with the gNB in the relay establishing N2 and N3 interface to an access and mobility management function (AMF) residing in the 5G Core (5GC) over a PDU session. This architecture option which has not yet been studied by SA2 may be better suited to certain deployment scenarios for vehicle-mounted relays, for instance using the VMR where IAB is not widely supported, or the scenario in which the relay process local traffic in the vehicle to provide on board services with low latency.

It has been defined that the wireless backhaul node comprises a MT part and a full gNB part, which is called as MWAB node instead. The MWAB node can also be called VMR node or WAB node. The MT part can be called UE component of the MWAB (MWAB-UE) . In the following description, the terms: “MWAB-UE” “MWAB-MT” and “MT” may be used interchangeably. The full gNB part can be called gNB component of the MWAB (MWAB-gNB) . FIG. 1B illustrates an example of a MWAB node associated with aspects of the present disclosure. When the MWAB node connects to its parent node, it can be regarded as the user equipment, that is, the role of the MT. When the MWAB node provides service for its child node (the child node may be another MWAB node, or an ordinary UE) , it can be regarded as a network device, that is, it acts as a gNB.

FIG. 1C illustrates example connections for MWAB node associated with aspects of the present disclosure. A UE connects to the gNB of MWAB node and establish an PDU session with the 5GC/NGC serving the UE. There’s a NG (e.g., N2/N3) interface between MWAB-gNB and the 5GC/NGC serving the UE. There’s a backhauling (BH) PDU session between MWAB-UE and BH 5GC (e.g., WMAB-UE-UPF) , which is used to support the overlaid N2 interface between MWAB-gNB and AMF.

FIG. 1D illustrates an example of an MWAB network 100D associated with aspects of the present disclosure. In the MWAB network, a relay node (RN) or MWAB node or a wireless backhaul node/device can provide wireless access services for UEs. That is, UE can connect to an MWAB-donor relayed by one or more MWAB nodes. It is to be understood that the number of MWAB nodes is only for the purpose of illustration without suggesting any limitations. Although not shown, it would be appreciated that there may be multiple hops between the UE and the MWAB-donor, and one or more MWAB nodes may be located between the UE and the MWAB-donor.

The MWAB-donor can be an access network element with a complete base station function, or it can be an access network element with a separate form of the CU and the DU. The MWAB-donor is connected to the core network (for example, connects to the 5G core network, 5GC) , and provide the wireless backhaul function for the MWAB node. In addition, the CU of the MWAB-donor is referred as MWAB-donor-CU (or directly referred as CU) , and the DU of the MWAB-donor is referred as MWAB-donor-DU. The MWAB-donor-CU may also be separated into the control plane (CP) and the user plane (UP) . For example, a CU can be composed of one CU-CP and one (or more) CU-UPs. The MWAB-donor may also be called a donor node or a donor base station (Donor gNodeB, DgNB) . In addition, the wireless link between MWAB-donor and MWAB node, or the wireless link between different MWAB nodes is called backhaul link.

In the 5G standard, considering the small coverage of the high frequency band, in order to ensure the coverage performance of the network, multi-hop networking may be adopted in the MWAB network. Taking into account the requirements of service transmission reliability, MWAB nodes can support dual connectivity (DC) or multi- connectivity to improve the reliability of transmission, so as to deal with abnormal situations that may occur on the backhaul link, such as radio link failure (RLF) or blockage and load fluctuations, etc.

The MWAB network supports multi-hop and dual-connection networking, so there may be multiple transmission paths between the UE and the MWAB-donor. On a transmission path, it contains multiple nodes, such as UE, one or more MWAB nodes, and MWAB-donor (if the MWAB-donor is in the form of separate CU and DU, it also contains the MWAB-donor-DU and MWAB-donor-CU) , each MWAB node treats the neighboring node that provides backhaul services for it as a parent (MWAB) node, and accordingly, each MWAB node can be regarded as a child (MWAB) node of its parent node.

In addition, a MWAB node may also be a “mobile base station relay” , which is a mobile base station acting as a relay between a UE and the 5G network, i.e., providing a NR access link to UEs and connected wirelessly (using NR) through a donor NG-RAN to the 5G Core. Such mobile base station relay is assumed to be mounted on a moving vehicle and serve UEs that can be located inside or outside the vehicle (or entering/leaving the vehicle) .

In view of the above discussions, some embodiments of the present disclosure provide a solution for PDU session establishment between MWAB-UE and MWAB-UE-UPF to work as the backhaul link in order to support N2 interface between MWAB-gNB and AMF. In one aspect of the solution of the present disclosure, an AMF receives a PDU session establishment request message in a NAS message from a MWAB-UE, the MWAB-UE and a MWAB-gNB are collocated to compose a MWAB node. The AMF transmits the PDU session establishment request message to a SMF. In case of receiving a PDU session establishment accept message from the SMF, the AMF then transmits the PDU session establishment accept message for the MWAB-UE to the MWAB-UE. The AMF further preserves a first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE, and the second information of MWAB-gNB is indicated by the PDU session establishment request message or the PDU session establishment accept message. In this way, a PDU session establishment is performed between MWAB-UE and a MWAB-UE-UPF. Principles and implementations of embodiments of the present disclosure will be described in detail below with reference to FIGS. 2-15.

FIG. 2 illustrates a signaling chart illustrating an example process 200 in accordance with aspects of the present disclosure. The process 200 may involve MWAB node 201, AMF 202, and SMF 203. A MWAB-UE and a MWAB-gNB are collocated to compose the MWAB node 201, and the MWAB node 201 in FIG. 2 may be an example of network entity 102 or UE 104 in FIG. 1A. The AMF 202 in FIG. 2 may be an example of core network 106 in FIG. 1A. The SMF 203 in FIG. 2 may be an example of core network 106 in FIG. 1A. It would be appreciated that although the process 200 is applied to in the communication environment 100A of FIG. 1A, this process may be likewise applied to other communication scenarios with similar issues.

In the process 200, the MWAB-UE of the MWAB node 201 transmits 205 a PDU session establishment request message to the SMF 203 via the AMF 202. The PDU session establishment request message 210 indicates (or is associated with) first information of the MWAB-gNB of the MWAB node 201.

FIG. 3 illustrates protocol stacks for MWAB node in accordance with aspects of the present disclosure. As shown in FIG. 3, the BH PDU session#1 between the UE of MWAB node (called MWAB-UE) and MWAB-UE-UPF is the backhaul PDU session mentioned above. MWAB-UE-UPF means the UPF for BH PDU session#1 of MWAB-UE.The gNB of MWAB node (called MWAB-gNB) establishes N2 interface with AMF. The N2 message or signalling transfer via the BH PDU session#1 between the MWAB-UE and MWAB-UE-UPF.

Alternatively or additionally, the first information of the MWAB-gNB may comprise an Internet protocol (IP) address of the MWAB-gNB, or an indication for requesting the IP address of the MWAB-gNB. In other words, the MWAB node 201 may obtain the IP address of the MWAB-gNB before the PDU session establishment or the indication for requesting the IP address of the MWAB-gNB via the PDU session establishment procedure.

In an example, the MWAB node 201 obtains the IP address of the MWAB-gNB from 5GC or operations administration and maintenance (OAM) . For example, upon receiving wab-NodeIndication in the initial UE message, the AMF 202 may provide an IP address of the MWAB-gNB (or the IP address of the MWAB-gNB and the IP address of the AMF 202) to MWAB-UE. E. g., the IP address of MWAB-gNB (or the IP address of the MWAB and the IP address of the AMF 202) may be piggyback via initial context setup request towards BH gNB (also refer as MWAB-donor) . BH gNB provides the IP address of MWAB-gNB (or the IP address of the MWAB and the IP address of the AMF 202) to MWAB-UE. In this way, the AMF 202 may preserve a first mapping between second information (e.g., the IP address of MWAB-gNB) of the MWAB-gNB and an identity of the MWAB-UE. Besides, the AMF 202 may also receive the identity of MWAB-gNB in the initial UE message, the AMF 202 preserves a first mapping between second information (e.g., the identity of MWAB-gNB) of the MWAB-gNB and an identity of the MWAB-UE. The IP address may be allocated by AMF 202, or AMF 202 requests the IP address from dynamic host configuration protocol (DHCP) server or SMF etc. Alternatively, MWAB-gNB may trigger MWAB-UE to establish a PDU session to transfer message or signalling or data between MWAB-gNB and OAM. For example, MWAB-gNB may provide the IP address of OAM to MWAB-UE. Alternatively, it is assumed that MWAB-UE is preconfigured with the IP address of OAM and it triggers PDU session establishment for transfer message or signalling or data between MWAB-gNB and OAM. After the PDU session establishment, OAM provides the IP address of MWAB-gNB and optionally the IP address of AMF via the PDU session towards MWAB-UE. For all the above solutions, MWAB-UE forwards the IP address of MWAB-gNB (or the IP address of the MWAB and the IP address of the AMF 202) to MWAB-gNB.

Additionally, the PDU session establishment request message 210 indicates first information of the MWAB-gNB of the MWAB node 201 may refer the PDU session establishment request message 210 comprises the first information of the MWAB-gNB.

In some embodiments, the MWAB-UE of the MWAB node 201 may transmit second information of MWAB-gNB, an indication of establishing the PDU session for N2 interface, or a combination of second information of MWAB-gNB and an indication of establishing the PDU session for N2 interface along with the PDU session establishment request message to the AMF 202. The PDU session between WMAB-UE and WMAB-UE-UPF provides the backhaul link to support the N2 interface.

Additionally, the second information of the MWAB-gNB may comprise an identity of the MWAB-gNB, an IP address of the MWAB-gNB, or the identity of the MWAB-gNB and the IP address of the MWAB-gNB. The identity (ID) of the MWAB-gNB may be Global RAN node ID or Global gNB ID. Global gNB ID contains both public land mobile network (PLMN) identity and gNB ID. It is to be understood that the first information of the MWAB-gNB is comprised in the PDU session establishment request message, and the second information of the MWAB-gNB may be transmitted along with or comprised in the PDU session establishment request message. In addition, the first information of the MWAB-gNB may be obtained by the SMF 203, and the second information of the MWAB-gNB may be obtained by the AMF 202.

For example, MWAB-UE sends the second information of the MWAB-gNB and the PDU session establishment request message indicating the IP address of the MWAB-gNB in the NAS message towards AMF 202. Optionally, there may be an indication of BH PDU session for MWAB node, or an indication of BH PDU session for N2 interface or an indication of BH PDU session for next generation (NG) control plane (NG-C) interface in the NAS message. Alternatively, the existence of IP address of the MWAB-gNB implies the BH PDU session for MWAB node (or for N2 interface or for NG-C interface) .

Correspondingly, the AMF 202 receives 215 the PDU session establishment request message 210 and optionally the second information of the MWAB-gNB from the MWAB node 201 in a NAS message. In addition, the NAS message may further comprise an indication of BH PDU session for MWAB node, or an indication of BH PDU session for N2 interface or an indication of BH PDU session for NG-C. The following steps take the indication of BH PDU session for N2 interface as an example.

In some embodiments, if the AMF 202 receives an indication of the MWAB node in an initial UE message, the AMF 202 may transmit an indication of establishing the PDU session for N2 interface to the MWAB-UE of the MWAB node 201. For example, the indication of the MWAB node may be the wab-NodeIndication. The AMF 202 may provide the indication of establishing the PDU session for N2 interface in NAS message for the MWAB-UE of the MWAB node 201 contained in initial context setup request upon receiving wab-NodeIndication in the Initial UE message.

Continuing with reference to FIG. 2, the AMF 202 further preserves a first mapping between the second information of the MWAB-gNB and an identity of the MWAB-UE. The identity of the MWAB-UE may comprise the subscription permanent identifier (SUPI) , subscription concealed identifier (SUCI) , 5G S-temporary mobile subscription identifier (5G-S-TMSI) , 5G globally unique temporary identifier (5G-GUTI) , generic public subscription identifier (GPSI) , etc. The second information of the MWAB-gNB is indicated by the PDU session establishment request message or the PDU session establishment accept message.

In some embodiments, the second information of the MWAB-gNB being indicated by the PDU session establishment request message may refer the PDU session establishment request message comprises the second information of the MWAB-gNB. Alternatively, the second information of the MWAB-gNB is indicated by the PDU session establishment request message may refer the PDU session establishment request message is transmitted with the second information of the MWAB-gNB.

In some embodiments, the second information of MWAB-gNB being indicated by the PDU session establishment accept message may refer the AMF 202 receives the second information of the MWAB-gNB along with the PDU session establishment accept message 245 from the SMF 203.

In some embodiments, the AMF 202 may preserve 218 the first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE after receiving the PDU session establishment request message 210 and the second information of the MWAB-gNB from the MWAB-UE of the MWAB node. In some embodiments, the AMF 202 may preserve 252 the first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE after receiving the PDU session establishment accept message 245 and the second information of the MWAB-gNB from the SMF 203. In this way, the AMF 202 knows the binding relationship between the MWAB-gNB and the MWAB-UE. If the AMF 202 preserves the first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE before, then step 218 or 252 can be omitted.

Upon receiving the MWAB-Node indication in initial UE message, the AMF 202 may select a SMF which supports special handling for MWAB node. The AMF 202 transmits 220 the PDU session establishment request message 225 to the SMF 203. The PDU session establishment request message 225 indicates first information of the MWAB-gNB of the MWAB node 201. Alternatively or additionally, the AMF 202 may transmit the IP address of the AMF 202 along with the PDU session establishment request 225 message to the SMF 203. If AMF 202 uses the same IP address of the AMF 202 to communicate with both MWAB-gNB and SMF 203, and AMF 202 provides IP address of AMF 202 before, then there may be no IP address of AMF here. Otherwise, AMF 202 may provide the IP address of the AMF used for N2/NG-C signaling exchange with MWAB-gNB. Alternatively or additionally, if the AMF 202 provides the IP address of MWAB-gNB (or both the IP address of MWAB-gNB and the IP address of AMF) , AMF 202 may transmit the IP address of MWAB-gNB (or both the IP address of MWAB-gNB and the IP address of AMF) along with the PDU session establishment request 225 message to the SMF 203. In this case, the PDU session establishment request message 210 does not include either the IP address of MWAB-gNB, or the indication of indication of requesting the IP address of the MWAB-gNB. Upon receiving the PDU session establishment request with IP address of MWAB-gNB and optionally the indication of establishing the PDU session for N2 interface, the SMF 203 knows that the PDU session is a BH PDU session established for N2/NG-C message exchange between MWAB-gNB and AMF 202.

Continuing with reference to FIG. 2, the SMF 203 receives 230 the PDU session establishment request message 225 from the AMF 202. Additionally, the SMF 203 may receive the IP address of the AMF 202 (or both the IP address of MWAB-gNB and the IP address of AMF) along with the PDU session establishment request message 225 from the AMF 202. Upon receiving the PDU session establishment request together with the IP address of the AMF, the SMF 203 knows that the PDU session is a BH PDU session established for N2/NG-C message exchange between MWAB-gNB and AMF 202.

After receiving 230 the PDU session establishment request message 225 originated from the MWAB-UE of the MWAB node 201, the SMF 203 generates 235 a PDU session establishment accept message 245 for the MWAB-UE of the MWAB node 201. In some embodiments, the PDU session establishment accept message 245 may comprise the IP address of the AMF 202 or (the IP address of the AMF and an IP address of the MWAB-gNB) .

In some embodiments, if the first information of the MWAB-gNB comprises the indication for requesting the IP address of the MWAB-gNB, the SMF 203 may allocate the IP address of the MWAB-gNB based on the indication of requesting the IP address of the MWAB-gNB, the IP address of the AMF provided by the AMF 202, or a combination of the above-mentioned items.

For instance, upon receiving the PDU session establishment request with the indication of requesting the IP address of the MWAB-gNB or the IP address of the AMF provided by AMF 202, the SMF 203 knows that the PDU session is a BH PDU session established for N2/NG-C message exchange between MWAB-gNB and AMF 202. SMF 203 allocates the IP address of the MWAB-gNB either upon the IP address of the AMF provided by AMF 202 or the request for IP address of the MWAB-gNB contained in PDU session establishment request message. SMF 203 may allocate the IP address of the MWAB-gNB by itself, or request UPF to provide the IP address of the MWAB-gNB.

In an example, the MWAB-UE sends the PDU session establishment request message to SMF 203 via AMF 202, which contains an indication of request for the IP address of the MWAB-gNB (or indication of BH PDU session for N2/NG-C etc. ) . The SMF 203 obtains the IP address of the AMF 202 by itself. SMF allocates the IP address of the MWAB-gNB based on the indication of requesting the IP address of the MWAB-gNB.

In another example, the MWAB-UE sends PDU session establishment request message and an indication of BH PDU session for N2/NG-C to AMF 202. If AMF 202 uses the same IP address when communicating with SMF 203 and the MWAB-gNB, then AMF 202 does not provide the IP address of the AMF 202. The AMF 202 provides SMF PDU session establishment request message to SMF 203, which contains the indication of requesting the IP address of the MWAB-gNB. SMF 203 obtains the IP address of the AMF 202 by itself. SMF 203 allocates the IP address of the MWAB-gNB based on the indication of requesting the IP address of the MWAB-gNB.

In yet another example, based on the second information, AMF 202 may provide PDU session establishment request message together with the IP address of the AMF 202 to SMF 203. If AMF 202 uses different IP addresses when communicating with SMF 203 and MWAB-gNB, AMF 202 provides SMF 203 with the PDU session establishment request message and the IP address of the AMF 202 to SMF 203. The PDU session establishment request message includes the indication of requesting the IP address of the MWAB-gNB. The SMF 203 allocates the IP address of the MWAB-gNB based on the indication of requesting the IP address of the MWAB-gNB. Alternatively, upon receiving the IP address of the AMF 202 from AMF 202, SMF 203 allocates the IP address of the MWAB-gNB.

In yet another example, AMF 202 may provide PDU session establishment request message together with the IP address of MWAB-gNB and optionally IP address of the AMF 202) to SMF 203. In this case, the SMF 203 is able to know both the IP address of MWAB-gNB and the IP address of the AMF 202.

In some embodiments, the SMF 203 may configure a MWAB-UE-UPF with a packet filter set comprising the IP address of the AMF 202 and the IP address of the MWAB-gNB. For example, the SMF 203 may send N4 session establishment request (or N4 PDU session modification request) message towards UPF (or called MWAB-UE-UPF) , which contains the packet filter set with the IP address of the AMF and the IP address of the MWAB-gNB. Besides, N4 session establishment request (or N4 PDU session modification request) message contains a QFI and the associated packet filter set. By IP filtering for the DL PDU from application server, UPF is able to mark the DL PDU with the corresponding QFI based on the packet filter set.

Alternatively or additionally, the SMF 203 may determine the IP address of the AMF 202 as a source IP address and the IP address of the MWAB-gNB as a destination IP address for a DL in the packet filter set. Alternatively, the SMF 203 may determine the IP address of the MWAB-gNB as a source IP address and the IP address of the AMF as a destination IP address for an UL in the packet filter set. Generally, server IP address is the source IP address for DL and destination IP address for UL. UE IP address is the destination IP address for DL and source IP address for UL. Therefore, the IP address of the AMF and IP address of the MWAB-gNB can be regarded as server IP address and UE IP address respectively.

Continuing with reference to FIG. 2, the SMF 203 transmits 240 the PDU session establishment accept message 245 to the MWAB-UE of the MWAB node 201 via the AMF 202. For instance, the SMF 203 provides the PDU session establishment accept message and user plane (UP) transport layer information (with IP address of the UPF and GTP-Tunnel endpoint (TE) ID) to RAN node (e.g., BH gNB or MWAB donor) via AMF 202. The PDU session establishment accept message may include the IP address of the AMF 202. For example, if AMF 202 provides the IP address of the AMF 202 before, then SMF 203 includes the IP address of the AMF 202 in the message. Otherwise, the SMF 203 may provide the IP address of the AMF based on specification. In addition, the SMF 203 may provide the quality of service (QoS) parameters for the QoS flow which is used for transferring the N2/NG-C message via BH PDU session#1. It is assumed that SMF is pre-configured with QoS parameters for transferring N2/NG-C message via BH PDU session#1. SMF 203 may also include QoS rule in the PDU session establishment accept message towards MWAB-UE, which contains the mapping of packet filter set and QoS flow identifier (QFI) of the QoS flow. The packet filter set contains the IP address of the AMF and the IP address of the MWAB-gNB.

Additionally, the SMF 203 may transmit second information of the MWAB-gNB along with the PDU session establishment accept message 245 to the AMF 202. Correspondingly, in case of receiving 250 the PDU session establishment accept message 245 from the SMF 203, the AMF 202 transmits 255 the PDU session establishment accept message 260 to the MWAB-UE of the MWAB node 201. Correspondingly, the MWAB-UE of the MWAB node 201 receives 265 the PDU session establishment accept message 260 from the SMF 203.

Alternatively or additionally, if the AMF 202 receives an indication of the MWAB node in an initial UE message, the AMF 202 may transmit the IP address of the AMF 202 to the MWAB-gNB of the MWAB node 201. For example, the AMF 202 may provide the IP address of itself (or called IP address of the AMF) to MWAB-gNB upon receiving wab-NodeIndication in the initial UE message. AMF 202 may send the IP address of the AMF 202 to a RAN node (e.g., BH gNB or MWAB donor) via an initial context setup request. The RAN node transmits the IP address of the AMF 202 to the MWAB-UE of the MWAB node 201, and the MWAB-UE forwards it to the MWAB-gNB of the MWAB node 201.

In some embodiments, if the PDU session establishment accept message comprises the IP address of the AMF 202, the MWAB-UE of the MWAB node 201 may transmit the IP address of the AMF 202 to the WMAB-gNB of the MWAB node 201. In some embodiments, if the PDU session establishment accept message comprises the IP address of the AMF 202 and the IP address of the MWAB-gNB, the MWAB-UE of the MWAB node 201 may transmit the IP address of the AMF and the IP address of the MWAB-gNB to the WMAB-gNB of the MWAB node 201.

Alternatively or additionally, if the AMF 202 receives an NG setup request message originated from the MWAB-gNB via a user plane function (UPF) for the MWAB-UE (MWAB-UE-UPF) , the AMF 202 may preserve a second mapping between the second information of the MWAB-gNB and information of the MWAB-UE-UPF. Additionally, the information of the MWAB-UE-UPF may comprise an IP address of the MWAB-UE-UPF.

In an example, upon receiving the NG setup request message from MWAB-UE-UPF, the AMF 202 obtains the ID of the MWAB-gNB contained in the NG setup request message. Besides, the AMF 202 obtains the IP address of the MWAB-gNB from the IP header of the NG setup request message. The AMF 202 also obtains the IP address of the MWAB-UE-UPF either from IPv6 extension header or IP in IP technology which encapsulates the NG setup request message. In this way, the AMF 202 preserves the mapping#2 of WAB-gNB information (e.g., the ID of the MWAB-gNB and/or the IP address of the MWAB-gNB) and information of the MWAB-UE-UPF (e.g., IP address of the MWAB-UE-UPF) .

In addition, the AMF 202 may generate a NG setup response message for the MWAB-gNB. Based on the second mapping, the AMF 202 may transmit the NG setup response message to the MWAB-UE-UPF.

FIG. 4 illustrates an example process 400 in accordance with aspects of the present disclosure. The process 400 may involve a gNB 401, a MT 402, a RAN node 403 (e.g., BH gNB, MWAB donor) , an AMF 404, a SMF 405, and a UPF 406 (e.g., MWAB-UE-UPF) . The gNB 401 in FIG. 4 may be an example of MWAB-gNB of the MWAB node 201 in FIG. 2. The MT 402 in FIG. 4 may be an example of the MWAB-UE of the MWAB node 201 in FIG. 2. The AMF 404 in FIG. 4 may be an example of the AMF 202 in FIG. 2. The SMF 405 may be an example of SMF 203 in FIG. 2. It is understood that the process 400 can be considered as a more specific example of the process 200 in FIG. 2.

At 410, the MT 402 sends a MSG5 to RAN node 403 (e.g., BH gNB, MWAB donor) with wab-NodeIndication. The MT 402 sends the MSG5 with RRCSetupComplete message towards the RAN node 403. The wab-NodeIndication may be contained in the RRCSetupComplete message. In addition, the MT 402 may include NAS message in RRCSetupComplete message. The NAS message can be a registration request or a service request message, which contains an ID of the MT 401. The ID of the MT 401 may comprise SUCI, SUPI, 5G-S-TMSI, 5G-GUTI, GPSI etc. Besides, the MT 402 may also include the identity of MWAB-gNB in MSG5.

Upon receiving the MWAB-Node indication in MSG5, RAN node 403 may select AMF which supports special handling for MWAB node. E. g., RAN node 403 may be pre-configured by OAM or PLMN or an operator with the MWAB node handling capability of AMF. Alternatively, if MWAB-gNB connects OAM via BH PDU session between MWAB-UE and MWAB-UE-UPF and obtains a configuration from OAM, e.g., the gNB IP address, the AMF information (e.g., the identity or IP address of AMF) , etc. If the AMF information is provided to MWAB-UE/MWAB-gNB, MWAB-UE may provide the AMF information to RAN node 403. RAN node 403 checks whether the previously selected AMF matches the AMF information provided by MWAB-UE. If not, RAN node 403 may request connection with the AMF based on the AMF information, e.g., by sending the initial UE message for the MWAB-UE. RAN node 403 may also release the N2 connection with the previous selected AMF.

At 415, RAN node 403 sends the initial UE message towards AMF 404, which contains the wab-NodeIndication and optionally the identity of MWAB-gNB. RAN node 403 selects AMF. At 420, the gNB 401 obtains the IP address (or called gNB IP address) from 5GC or OAM. For example, upon receiving wab-NodeIndication in the Initial UE message, AMF 404 may allocate an IP address to the gNB 401 after N2 interface setup between gNB 401 and AMF 404. In addition, AMF 404 may also provide the IP address of itself (or called AMF IP address) to gNB 401 upon receiving wab-NodeIndication in the initial UE message. In this way, the AMF 202 may preserve the first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE.

At 425, AMF 404 may provide an indication of establishing PDU session for N2 or NG-C towards MT 401. At 430, MT 402 triggers BH PDU session#1 establishment for N2/NG-C between gNB 401 and AMF 404. At 435, AMF 404 preserves the mapping#1 of gNB information (e.g., gNB ID or gNB IP address) and MT ID (e.g., SUPI) . If the AMF 202 preserves the first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE before (e.g., at 415) , then step 435 can be omitted.

At 440, AMF 404 sends PDU session establishment request (with gNB IP address) message and optionally AMF IP address towards SMF 405. At 445, SMF 405 sets AMF IP address as source IP address for DL (or destination IP address for UL) and gNB IP address as destination IP address for DL (or source IP address for UL) in the packet filter set.

At 450, SMF 405 sends N4 session establishment request (or N4 PDU Session modification request) message towards UPF 406 (or called MT-UPF or MWAB-UE-UPF) , which contains the packet filter set with AMF IP address and gNB IP address. At 455, UPF 406 responds SMF 405 with N4 PDU session establishment/modification response message with UPF side up transport layer information for the BH PDU session#1, which includes the endpoint IP address (e.g., UPF IP address) and GTP-Tunnel endpoint (TE) ID.

At 465, SMF 405 provides PDU session establishment accept message and up transport Layer information (with UPF IP address and TEID) to RAN node 403 via AMF 404. The PDU session establishment accept message may include AMF IP address. SMF 405 may also send N2 SM message towards RAN node 403 at 450, e.g., PDU session resource setup request transfer, together with the PDU session establishment accept message for the MT 402. Then, RAN node 403 will response to SMF 405 with gNB side up transport layer information for the BH PDU session#1. Then SMF 405 will forward the gNB side up transport layer information for the BH PDU session#1 to UPF 406.

At 470, RAN node 403 forwards the PDU session establishment accept message to the MT 402. Additionally, the AMF IP address may be forwarded with the PDU session establishment accept message. Besides, RAN node 403 also configures the MT 402 with the mapping of QFI and DRB. At 475, if AMF IP address is contained in PDU session establishment accept message, then MT 402 forwards the AMF IP address to gNB 401.

In general, the MT 402, i.e., the WAB-MT, MWAB-MT or MWAB-UE, obtains gNB IP address before BH PDU session#1 establishment. The MT 402 (e.g., MWAB-MT) sends PDU session establishment request (with gNB IP address) message and MWAB-gNB information (e.g., gNB ID or gNB IP address) in the NAS message towards AMF 404. AMF 404 preserves the mapping#1 of MWAB-gNB information (e.g., gNB ID or gNB IP address) and MWAB-MT ID (e.g., SUPI) . AMF 404 sends PDU session establishment request (with gNB IP address) message and optionally AMF IP address towards SMF 405. SMF 405 sets AMF IP address as source IP address for DL (or destination IP address for UL) and gNB IP address as destination IP address for DL (or source IP address for UL) in the packet filter set. SMF 405 sends N4 session establishment request (or N4 PDU session modification request) message towards UPF (or called MT-UPF, or MWAB-UE-UPF) , which contains the packet filter set with AMF IP address and gNB IP address. SMF 405 provides PDU session establishment accept message and UP Transport Layer Information (with UPF IP address and TEID) to RAN node 403 via AMF 404. The PDU session establishment accept message may include AMF IP address. If AMF IP address is contained in PDU session establishment accept message, then the MT 402 (e.g., MWAB-MT) forwards the AMF IP address to the gNB 401 (e.g., MWAB-gNB) . AMF 404 may also provide the IP address of itself (or called AMF IP address) to the gNB 401 (e.g., MWAB-gNB) upon receiving wab-NodeIndication in the initial UE message. AMF 404 may provide an indication of establishing PDU session for N2 (or NG-C) towards the MT 402 (e.g., MWAB-MT) upon receiving wab-NodeIndication in the Initial UE message.

FIG. 5 illustrates another example process 500 in accordance with aspects of the present disclosure. The process 500 may involve a gNB 501, a MT 502, a RAN node 503, an AMF 504, a SMF 505, and a UPF 506. The gNB 501 in FIG. 5 may be an example of MWAB-gNB of the MWAB node 201 in FIG. 2. The MT 502 in FIG. 5 may be an example of the MWAB-UE of the MWAB node 201 in FIG. 2. The AMF 504 in FIG. 5 may be an example of the AMF 202 in FIG. 2. The SMF 505 may be an example of SMF 203 in FIG. 2. It is understood that the process 500 can be considered as a more specific example of the process 200 in FIG. 2.

At 510, MT 502 triggers BH PDU session#1 establishment for N2/NG-C between gNB 501 and AMF 504. For example, MT 502 sends PDU session establishment request message and optionally an indication of BH PDU Session for N2/NG-C in the NAS message towards AMF 504. The PDU session establishment request may include an indication of requesting for gNB IP address or indication of BH PDU session for N2/NG-C, etc.

At 515, AMF 504 sends PDU session establishment request message towards SMF 505. If indication of BH PDU Session for N2/NG-C is contained in the NAS message from MT 502, AMF 504 may also provide AMF IP address towards SMF 505. At 520, upon receiving the PDU session establishment request with the indication of requesting gNB IP address or from the AMF IP address provided by AMF 504, SMF 505 knows that the PDU session is a BH PDU session established for NG-C message exchange between gNB 501 and AMF 504. SMF 505 allocates gNB IP address either upon AMF IP address provided by AMF 504 or the request for gNB IP address contained in PDU session establishment request message. SMF 505 sets AMF IP address as source IP address for DL (or destination IP address for UL) and gNB IP address as destination IP address for DL (or source IP address for UL) in the packet filter set. SMF 505 may allocate gNB IP address by itself, or request UPF 506 to provide gNB IP address.

At 525, SMF 505 sends N4 session establishment request (or N4 PDU session modification request) message towards UPF 506 (or called MWAB-UE-UPF) , which contains the packet filter set with AMF IP address and gNB IP address. At 530, UPF 506 responds SMF 505 with N4 PDU session establishment/modification response message with UPF side up transport layer information for the BH PDU session#1, which includes the endpoint IP address (e.g., UPF IP address) and GTP-Tunnel endpoint (TE) ID.

At 535, SMF 505 provides PDU session establishment accept message and gNB IP address to AMF, where PDU session establishment accept message contains both gNB IP address and AMF IP address. For example, the SMF 505 may provide the quality of service (QoS) parameters for the QoS flow which is used for transferring the N2/NG-C message via BH PDU session#1. SMF 505 includes QoS rule in the PDU session establishment accept message towards MT 502, which contains the mapping of packet filter set and QFI for the QoS flow. The packet filter set contains the AMF IP address and gNB IP address. Alternatively, SMF 505 may provide gNB IP address and AMF IP address in a separate message to MT 502. Besides, SMF 505 also provide up transport layer information with UPF IP address and TEID to AMF 504.

At 540, AMF 504 preserves the mapping#1 of gNB information (e.g., gNB ID or gNB IP address) and ID of MT (e.g., SUPI) . In this way, AMF knows the binding relationship between gNB 501 and MT 502. If the AMF 202 preserves the first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE before (e.g., at 415) , then 540 can be omitted. At 545, AMF 504 provides PDU session establishment accept message to RAN node 503. At 550, RAN node 503 forwards the PDU session establishment accept message to MT 502. Besides, RAN node 503 also configures MT 502 with the mapping of QFI and DRB. At 555, MT 502 forwards the gNB IP address and AMF IP address to gNB 501.

In general, MT 502 obtains gNB IP address via BH PDU session#1 establishment. MT 502 sends PDU session establishment request message and optionally an indication of BH PDU session for N2/NG-C in the NAS message towards AMF 504. The PDU session establishment request may include request for gNB IP address, or indication of BH PDU session for N2/NG-C etc. If indication of BH PDU session for N2/NG-C is contained in the NAS message from MT 502, AMF 504 may also provide AMF IP address towards SMF 505. SMF 505 allocates gNB IP address either upon AMF IP address provided by AMF 504 or the request for gNB IP address contained in PDU session establishment request message. SMF 505 sets AMF IP address as source IP address for DL (or destination IP address for UL) and gNB IP address as destination IP address for DL (or source IP address for UL) in the packet filter set. SMF 505 provides PDU session establishment accept message and gNB IP address to AMF 504, where PDU session establishment accept message contains both gNB IP address and AMF IP address. AMF 504 preserves the mapping#1 of WAB-gNB information (e.g., gNB ID or gNB IP address) and WAB-MT ID (e.g., SUPI) . AMF 504 forwards PDU session establishment accept message (with gNB IP address and AMF IP address) to MT 502. MT 502 forwards the gNB IP address and AMF IP address to gNB 501.

FIG. 6 illustrates an example NG setup procedure in accordance with aspects of the present disclosure. The process 600 may involve a gNB 601, a MT 602, a RAN node 603 (e.g., BH gNB, MWAB donor) , an AMF 604, a SMF 605, and a MT-UPF (e.g., MWAB-UE-UPF) 606. The gNB 601 in FIG. 6 may be an example of MWAB-gNB of the MWAB node 201 in FIG. 2. The MT 602 in FIG. 6 may be an example of the MWAB-UE of the MWAB node 201 in FIG. 2. The AMF 604 in FIG. 6 may be an example of the AMF 202 in FIG. 2. The SMF 605 may be an example of SMF 203 in FIG. 2. It is understood that the process 600 can be considered as a more specific example of the process 200 in FIG. 2.

As shown FIG. 3, there is stream control transmission protocol/IP (SCTP/IP connection between connection between WAB-gNB and AMF. It is assumed that WAB-gNB and AMF setup SCTP/IP connection before NG interface setup. That is, the N2/NG-C message is encapsulated in IP packet.

At 610, the gNB 601 generates NG setup request message and sends it to MT 602. In addition, gNB 601 may also provide an indication of N2/NG-C message to MT 602 together with the NG setup request message. MT 602 maps the NG setup request message into the BH PDU session#1, which is established for NG-C.

At 615, MT 602 obtains the source and destination IP address (e.g., gNB IP address and AMF IP address) of the NG setup request message. MT 602 determines the QFI based on the source and destination IP address according to the QoS rule. Then MT 602 maps the QFI to DRB based on the configuration from RAN node 603.

At 620, MT 602 forwards the NG setup request message towards RAN node 603 via the DRB. RAN node 603 determines the BH PDU session#1 based on the DRB ID. At 625, RAN node 602 forwards the NG setup request message to MT-UPF 606 via BH PDU session#1. At 630, after receiving the NG setup request message, MT-UPF 606 forwards the NG setup request message towards AMF 604 based on the destination IP address (i.e., AMF IP address) .

At 635, upon receiving the NG setup request message from MT-UPF 606, AMF 604 obtains gNB ID contained in the NG setup request message. Besides, AMF 604 obtains the gNB IP address from the IP header of the NG setup request message. AMF 604 also obtains MT-UPF IP address either from IPv6 extension header or IP in IP technology which encapsulates the NG setup request message. In this way, AMF 604 preserves the mapping#2 of WAB-gNB information (e.g., gNB ID and/or gNB IP address) and MT-UPF information (e.g., MT-UPF IP address) .

At 640, AMF 604 generates NG setup response message and forwards it to MT-UPF 606 based on the mapping#2 of WAB-gNB information and MT-UPF information. At 645, upon receiving the NG setup response message from AMF 604, MT-UPF 606 performs IP filtering. For example, MT-UPF 606 determines both BH PDU session#1 and QFI based on the packet filter set, which contains the source IP address (i.e., AMF IP address) and destination IP address (i.e., gNB IP address) .

At 650, MT-UPF 606 forwards the NG setup response message towards RAN node 603 via the BH PDU session#1. That is, MT-UPF 606 encapsulates the NG setup response message with GTP-U header, which contains QFI. Besides, GTP-U header also contains the TEID allocated by RAN node 603 for the BH PDU session#1.

At 655, upon receiving the NG setup response message, RAN node 603 determines the MT 602 based on the BH PDU session#1 and determines the DRB based on QFI contained in the GTP-U header. RAN node 603 sends the NG setup response message to MT 602 via the DRB.

At 660, upon receiving the NG setup response message, MT 602 checks the destination IP address. At 665, if the destination IP address is gNB IP address, MT 602 forwards the NG setup response message to gNB 601.

FIG. 7 illustrates yet another example process in accordance with aspects of the present disclosure. The process 700 may involve a MWAB-gNB 701, a MWAB-UE 702, a BH gNB 703, an AMF 704, a SMF 705, and a MWAB-UE-UPF 706. The MWAB-gNB 701 in FIG. 7 may be an example of MWAB-gNB of the MWAB node 201 in FIG. 2. The MWAB-UE 702 in FIG. 7 may be an example of the MWAB-UE of the MWAB node 201 in FIG. 2. The AMF 704 in FIG. 7 may be an example of the AMF 202 in FIG. 2. The SMF 705 may be an example of SMF 203 in FIG. 2. The MWAB-UE 702 and MWAB-gNB 701 are collocated to compose a MWAB node. It is understood that the process 700 can be considered as a more specific example of the process 200 in FIG. 2.

At 710, MWAB-UE 702 includes a MWAB-Node indication and optionally the identity of MWAB-gNB in MSG5 towards BH gNB 703. At 715, upon receiving the MWAB-Node indication in MSG5, BH gNB 703 selects a AMF which supports special handling for the MWAB node. At 720, BH gNB 703 sends a N2 message (e.g., initial UE message) towards the selected AMF 704, which includes the MWAB-Node indication and optionally the identity of MWAB-gNB.

At 725, upon receiving the MWAB-Node indication in the N2 Message, AMF 704 may provide an gNB IP address and an AMF IP address to MWAB-UE 702 via BH gNB 703. For example, AMF 704 may provide the gNB IP address and the AMF IP address in a registration accept message for MWAB-UE 702.

At 730, MWAB-UE 702 forwards the gNB IP address and AMF IP address to MWAB-gNB. It is to be understood that, similar as the IAB, MWAB-gNB 701 may obtain both gNB IP address and AMF IP address from OAM after MWAB-UE 702 established a PDU session towards the OAM. The AMF 202 may preserve the first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE.

At 735, MWAB-UE 702 sends PDU session establishment request message together with MWAB-gNB information to AMF 704 via BH gNB 701, and the PDU session establishment request message may include gNB IP address. At 740, upon receiving MWAB-gNB information from MWAB-UE 702, AMF 704 preserves the first mapping of MWAB-gNB 701 and MWAB-UE 702. If the AMF 202 preserves the first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE before (e.g., at 720) , then 740 can be omitted.

At 745, AMF 704 selects a SMF which supports special handling for the MWAB node. AMF 704 sends Nsmf_PDUSession_CreateSMContext Request towards SMF 705, which includes SUPI and PDU session establishment request message. Optionally, AMF may also include gNB IP address and optionally the AMF IP address in the Nsmf_PDUSession_CreateSMContext Request towards SMF 705.

At 750, upon receiving the PDU session establishment request message from MWAB-UE 702, SMF 705 obtains gNB IP address. Alternatively, SMF 705 obtains gNB IP address contained in Nsmf_PDUSession_CreateSMContext Request from AMF 704. SMF may obtain AMF IP address from the IP header which encapsulates the message from AMF, or obtain AMF IP address directly provided by AMF 704 in Nsmf_PDUSession_CreateSMContext Request. SMF 705 sets AMF IP address and gNB IP address as source/destination IP address in the packet filter set. It is assumed that SMF 705 is pre-configured with QoS parameters for transferring N2 message via a BH PDU session.

At 755, SMF 705 triggers N4 session establishment procedure towards MWAB-UE-UPF 706. MWAB-UE-UPF 706 obtains the packet filter set which contains AMF IP address and gNB IP address. At 760, SMF 705 sends N2 PDU session request message towards NG-RAN via AMF 704, which includes a NAS message (i.e., PDU session establishment accept) for MWAB-UE 702. At 765, BH gNB 703 triggers AN-specific resource setup towards MWAB-UE 702, which contains PDU session establishment accept message from SMF.

FIG. 8 illustrates an example of a device 800 that supports PDU session establishment in accordance with aspects of the present disclosure. The device 800 may be an example of a core network 106 as described herein. The device 800 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 800 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 802, a memory 804, a transceiver 806, and, optionally, an I/O controller 808. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 802, the memory 804, the transceiver 806, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 802, the memory 804, the transceiver 806, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

In some implementations, the processor 802, the memory 804, the transceiver 806, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 802 and the memory 804 coupled with the processor 802 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 802, instructions stored in the memory 804) .

For example, the processor 802 may support wireless communication at the device 800 in accordance with examples as disclosed herein. The processor 802 may be configured to operable to support a means for receiving, from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , a protocol data unit (PDU) session establishment request message in a non-access stratum (NAS) message, wherein the MWAB-UE and a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node; means for transmitting, to a session management function (SMF) , the PDU session establishment request message; and means for transmitting, to the MWAB-UE, a PDU session establishment accept message for the MWAB-UE in case of receiving the PDU session establishment accept message from the SMF; a means for preserving, a first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE, wherein the second information of MWAB-gNB is indicated by the PDU session establishment request message or the PDU session establishment accept message. The processor 802 may be configured to operable to support other means for other implementations of method 1400.

The processor 802 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 802 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 802. The processor 802 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 804) to cause the device 800 to perform various functions of the present disclosure.

The memory 804 may include random access memory (RAM) and read-only memory (ROM) . The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 802 cause the device 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 802 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 804 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The I/O controller 808 may manage input and output signals for the device 800. The I/O controller 808 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 808 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 808 may utilize an operating system such as or another known operating system. In some implementations, the I/O controller 808 may be implemented as part of a processor, such as the processor 806. In some implementations, a user may interact with the device 800 via the I/O controller 808 or via hardware components controlled by the I/O controller 808.

In some implementations, the device 800 may include a single antenna 810. However, in some other implementations, the device 800 may have more than one antenna 810 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 806 may communicate bi-directionally, via the one or more antennas 810, wired, or wireless links as described herein. For example, the transceiver 806 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 806 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 810 for transmission, and to demodulate packets received from the one or more antennas 810. The transceiver 806 may include one or more transmit chains, one or more receive chains, or a combination thereof.

A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 810 for transmitting the amplified signal into the air or wireless medium.

A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 810 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

FIG. 9 illustrates an example of a device 900 that supports PDU session establishment in accordance with aspects of the present disclosure. The device 900 may be an example of a core network 106 as described herein. The device 900 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 900 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 902, a memory 904, a transceiver 906, and, optionally, an I/O controller 908. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 902, the memory 904, the transceiver 906, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 902, the memory 904, the transceiver 906, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

In some implementations, the processor 902, the memory 904, the transceiver 906, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904) .

For example, the processor 902 may support wireless communication at the device 900 in accordance with examples as disclosed herein. The processor 902 may be configured to operable to support a means for receiving, from an access and mobility management function (AMF) , a protocol data unit (PDU) session establishment request message originated from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , wherein the PDU session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) , and wherein the MWAB-UE and the MWAB-gNB are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node; means for generating a PDU session establishment accept message for the MWAB-UE; and means for transmitting, to the MWAB-UE via the AMF, the PDU session establishment accept message. The processor 902 may be configured to operable to support other means for other implementations of method 1500.

The processor 902 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 902 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 904) to cause the device 900 to perform various functions of the present disclosure.

The memory 904 may include random access memory (RAM) and read-only memory (ROM) . The memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 902 cause the device 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 902 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 904 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The I/O controller 908 may manage input and output signals for the device 900. The I/O controller 908 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 908 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 908 may utilize an operating system such as or another known operating system. In some implementations, the I/O controller 908 may be implemented as part of a processor, such as the processor 906. In some implementations, a user may interact with the device 900 via the I/O controller 908 or via hardware components controlled by the I/O controller 908.

In some implementations, the device 900 may include a single antenna 910. However, in some other implementations, the device 900 may have more than one antenna 910 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 906 may communicate bi-directionally, via the one or more antennas 910, wired, or wireless links as described herein. For example, the transceiver 906 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 906 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 910 for transmission, and to demodulate packets received from the one or more antennas 910. The transceiver 906 may include one or more transmit chains, one or more receive chains, or a combination thereof.

A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 910 for transmitting the amplified signal into the air or wireless medium.

A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 910 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

FIG. 10 illustrates an example of a device 1000 that supports PDU session establishment in accordance with aspects of the present disclosure. The device 1000 may be an example of a network entity 102 or a UE 104 as described herein. The device 1000 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 1000 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 1002, a memory 1004, a transceiver 1006, and, optionally, an I/O controller 1008. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 1002, the memory 1004, the transceiver 1006, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 1002, the memory 1004, the transceiver 1006, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

In some implementations, the processor 1002, the memory 1004, the transceiver 1006, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004) .

For example, the processor 1002 may support wireless communication at the device 1000 in accordance with examples as disclosed herein. The processor 1002 may be configured to operable to support a means for transmitting, to a session management function (SMF) , a protocol data unit (PDU) session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) via an access and mobility management function (AMF) ; and means for receiving, from the SMF, a PDU session establishment accept message. The processor 1002 may be configured to operable to support other means for other implementations of method 1600.

The processor 1002 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 1002 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 1002. The processor 1002 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1004) to cause the device

1000 to perform various functions of the present disclosure.

The memory 1004 may include random access memory (RAM) and read-only memory (ROM) . The memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1002 cause the device 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 1002 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 1004 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The I/O controller 1008 may manage input and output signals for the device 1000. The I/O controller 1008 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 1008 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 1008 may utilize an operating system such as or another known operating system. In some implementations, the I/O controller 1008 may be implemented as part of a processor, such as the processor 1006. In some implementations, a user may interact with the device 1000 via the I/O controller 1008 or via hardware components controlled by the I/O controller 1008.

In some implementations, the device 1000 may include a single antenna 1010. However, in some other implementations, the device 1000 may have more than one antenna 1010 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1006 may communicate bi-directionally, via the one or more antennas 1010, wired, or wireless links as described herein. For example, the transceiver 1006 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1006 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1010 for transmission, and to demodulate packets received from the one or more antennas 1010. The transceiver 1006 may include one or more transmit chains, one or more receive chains, or a combination thereof.

A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 1010 for transmitting the amplified signal into the air or wireless medium.

A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 1010 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

FIG. 11 illustrates an example of a processor 1100 that supports PDU session establishment in accordance with aspects of the present disclosure. The processor 1100 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1100 may include a controller 1102 configured to perform various operations in accordance with examples as described herein. The processor 1100 may optionally include at least one memory 1104. Additionally, or alternatively, the processor 1100 may optionally include one or more arithmetic-logic units (ALUs) 1100. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 1100 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1100) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .

The controller 1102 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein. For example, the controller 1102 may operate as a control unit of the processor 1100, generating control signals that manage the operation of various components of the processor 1100. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

The controller 1102 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1104 and determine subsequent instruction (s) to be executed to cause the processor 1100 to support various operations in accordance with examples as described herein. The controller 1102 may be configured to track memory address of instructions associated with the memory 1104. The controller 1102 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1102 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1102 may be configured to manage flow of data within the processor 1100. The controller 1102 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1100.

The memory 1104 may include one or more caches (e.g., memory local to or included in the processor 1100 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 1104 may reside within or on a processor chipset (e.g., local to the processor 1100) . In some other implementations, the memory 1104 may reside external to the processor chipset (e.g., remote to the processor 1100) .

The memory 1104 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1100, cause the processor 1100 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1102 and/or the processor 1100 may be configured to execute computer-readable instructions stored in the memory 1104 to cause the processor 1100 to perform various functions (e.g., functions or tasks supporting transmit power prioritization) . For example, the processor 1100 and/or the controller 1102 may be coupled with or to the memory 1104, the processor 1100, the controller 1102, and the memory 1104 may be configured to perform various functions described herein. In some examples, the processor 1100 may include multiple processors and the memory 1104 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

The one or more ALUs 1100 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 1100 may reside within or on a processor chipset (e.g., the processor 1100) . In some other implementations, the one or more ALUs 1100 may reside external to the processor chipset (e.g., the processor 1100) . One or more ALUs 1100 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1100 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1100 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1100 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1100 to handle conditional operations, comparisons, and bitwise operations.

The processor 1100 may support wireless communication in accordance with examples as disclosed herein. The processor 1102 may be configured to or operable to support a means for a means for receiving, from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , a protocol data unit (PDU) session establishment request message in a non-access stratum (NAS) message, wherein the MWAB-UE and a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node; means for transmitting, to a session management function (SMF) , the PDU session establishment request message; and means for transmitting, to the MWAB-UE, a PDU session establishment accept message for the MWAB-UE in case of receiving the PDU session establishment accept message from the SMF; wherein the apparatus is further caused to preserve, a first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE, wherein the second information of MWAB-gNB is indicated by the PDU session establishment request message or the PDU session establishment accept message. The processor 1100 may be configured to or operable to support other means for other implementations of method 1400.

FIG. 12 illustrates an example of a processor 1200 that supports PDU session establishment in accordance with aspects of the present disclosure. The processor 1200 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1200 may include a controller 1202 configured to perform various operations in accordance with examples as described herein. The processor 1200 may optionally include at least one memory 1204. Additionally, or alternatively, the processor 1200 may optionally include one or more arithmetic-logic units (ALUs) 1200. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 1200 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1200) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .

The controller 1202 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1200 to cause the processor 1200 to support various operations in accordance with examples as described herein. For example, the controller 1202 may operate as a control unit of the processor 1200, generating control signals that manage the operation of various components of the processor 1200. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

The controller 1202 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1204 and determine subsequent instruction (s) to be executed to cause the processor 1200 to support various operations in accordance with examples as described herein. The controller 1202 may be configured to track memory address of instructions associated with the memory 1204. The controller 1202 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1202 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1200 to cause the processor 1200 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1202 may be configured to manage flow of data within the processor 1200. The controller 1202 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1200.

The memory 1204 may include one or more caches (e.g., memory local to or included in the processor 1200 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 1204 may reside within or on a processor chipset (e.g., local to the processor 1200) . In some other implementations, the memory 1204 may reside external to the processor chipset (e.g., remote to the processor 1200) .

The memory 1204 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1200, cause the processor 1200 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1202 and/or the processor 1200 may be configured to execute computer-readable instructions stored in the memory 1204 to cause the processor 1200 to perform various functions (e.g., functions or tasks supporting transmit power prioritization) . For example, the processor 1200 and/or the controller 1202 may be coupled with or to the memory 1204, the processor 1200, the controller 1202, and the memory 1204 may be configured to perform various functions described herein. In some examples, the processor 1200 may include multiple processors and the memory 1204 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

The one or more ALUs 1200 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 1200 may reside within or on a processor chipset (e.g., the processor 1200) . In some other implementations, the one or more ALUs 1200 may reside external to the processor chipset (e.g., the processor 1200) . One or more ALUs 1200 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1200 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1200 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1200 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1200 to handle conditional operations, comparisons, and bitwise operations.

The processor 1200 may support wireless communication in accordance with examples as disclosed herein. The processor 1202 may be configured to or operable to support a means for receiving, from an access and mobility management function (AMF) , a protocol data unit (PDU) session establishment request message originated from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , wherein the PDU session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) , and wherein the MWAB-UE and the MWAB-gNB are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node; means for generating a PDU session establishment accept message for the MWAB-UE; and means for transmitting, to the MWAB-UE via the AMF, the PDU session establishment accept message.. The processor 1200 may be configured to or operable to support other means for other implementations of method 1500.

FIG. 13 illustrates an example of a processor 1300 that supports PDU session establishment in accordance with aspects of the present disclosure. The processor 1300 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1300 may include a controller 1302 configured to perform various operations in accordance with examples as described herein. The processor 1300 may optionally include at least one memory 1304. Additionally, or alternatively, the processor 1300 may optionally include one or more arithmetic-logic units (ALUs) 1300. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 1300 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1300) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .

The controller 1302 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1300 to cause the processor 1300 to support various operations in accordance with examples as described herein. For example, the controller 1302 may operate as a control unit of the processor 1300, generating control signals that manage the operation of various components of the processor 1300. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

The controller 1302 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1304 and determine subsequent instruction (s) to be executed to cause the processor 1300 to support various operations in accordance with examples as described herein. The controller 1302 may be configured to track memory address of instructions associated with the memory 1304. The controller 1302 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1302 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1300 to cause the processor 1300 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1302 may be configured to manage flow of data within the processor 1300. The controller 1302 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1300.

The memory 1304 may include one or more caches (e.g., memory local to or included in the processor 1300 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 1304 may reside within or on a processor chipset (e.g., local to the processor 1300) . In some other implementations, the memory 1304 may reside external to the processor chipset (e.g., remote to the processor 1300) .

The memory 1304 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1300, cause the processor 1300 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1302 and/or the processor 1300 may be configured to execute computer-readable instructions stored in the memory 1304 to cause the processor 1300 to perform various functions (e.g., functions or tasks supporting transmit power prioritization) . For example, the processor 1300 and/or the controller 1302 may be coupled with or to the memory 1304, the processor 1300, the controller 1302, and the memory 1304 may be configured to perform various functions described herein. In some examples, the processor 1300 may include multiple processors and the memory 1304 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

The one or more ALUs 1300 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 1300 may reside within or on a processor chipset (e.g., the processor 1300) . In some other implementations, the one or more ALUs 1300 may reside external to the processor chipset (e.g., the processor 1300) . One or more ALUs 1300 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1300 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1300 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1300 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1300 to handle conditional operations, comparisons, and bitwise operations.

The processor 1300 may support wireless communication in accordance with examples as disclosed herein. The processor 1302 may be configured to or operable to support a means for transmitting, to a session management function (SMF) , a protocol data unit (PDU) session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) via an access and mobility management function (AMF) ; and means for receiving, from the SMF, a PDU session establishment accept message. The processor 1300 may be configured to or operable to support other means for other implementations of method 1600.

FIG. 14 illustrates a flowchart of a method 1400 that supports PDU session establishment in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by a device or its components as described herein. For example, the operations of the method 1400 may be performed by a core network 116 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1405, the method may include receiving, from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , a protocol data unit (PDU) session establishment request message in a non-access stratum (NAS) message, wherein the MWAB-UE and a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node. The operations of 1405 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1405 may be performed by a device as described with reference to FIG. 1A.

At 1411, the method may include transmitting, to a session management function (SMF) , the PDU session establishment request message. The operations of 1411 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 140 may be performed by a device as described with reference to FIG. 1A.

At 1415, the method may include transmitting, to the MWAB-UE, a PDU session establishment accept message for the MWAB-UE in case of receiving the PDU session establishment accept message from the SMF. The method may include preserving, a first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE, wherein the second information of MWAB-gNB is indicated by the PDU session establishment request message or the PDU session establishment accept message. The operations of 1415 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1415 may be performed by a device as described with reference to FIG. 1A.

In some embodiment, the second information of MWAB-gNB being indicated by the PDU session establishment request message may comprise one of the following: the PDU session establishment request message comprises the second information of the MWAB-gNB; or the PDU session establishment request message is transmitted with the second information of the MWAB-gNB. In some embodiment, the NAS message may further comprise an indication of establishing the PDU session for N2 interface.

In some embodiment, the second information of the MWAB-gNB being indicated by the PDU session establishment accept message may comprise: receiving, from the SMF, the second information of the MWAB-gNB along with the PDU session establishment accept message.

In some embodiment, transmitting the PDU session establishment request message may comprise: transmitting, to the SMF, the IP address of the AMF along with the PDU session establishment request message.

In some embodiment, the method may further include transmitting, to the MWAB-gNB, the IP address of the AMF in case of receiving an indication of the MWAB node in an initial UE message.

In some embodiment, the method may further include preserving a second mapping between the second information of the MWAB-gNB and information of a user plane function for the MWAB-UE (MWAB-UE-UPF) in case of receiving an NG setup request message originated from the MWAB-gNB via the MWAB-UE-UPF.

In some embodiment, the method may further include generating a NG setup response message for the MWAB-gNB; and transmitting, to the MWAB-UE-UPF, the NG setup response message based on the second mapping.

In some embodiment, the second information of the MWAB-gNB may comprise one of; an identity of the MWAB-gNB; an IP address of the MWAB-gNB; or the identity of the MWAB-gNB and the IP address of the MWAB-gNB; or the information of the MWAB-UE-UPF may comprise an IP address of the MWAB-UE-UPF.

FIG. 15 illustrates a flowchart of a method 1500 that supports PDU session establishment in accordance with aspects of the present disclosure. The operations of the method 1500 may be implemented by a device or its components as described herein. For example, the operations of the method 1500 may be performed by a UE 114 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1505, the method may include receiving, from an access and mobility management function (AMF) , a protocol data unit (PDU) session establishment request message originated from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , wherein the PDU session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) , and wherein the MWAB-UE and the MWAB-gNB are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node. The operations of 1505 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1505 may be performed by a device as described with reference to FIG. 1A.

At 1511, the method may include generating a PDU session establishment accept message for the MWAB-UE. The operations of 1511 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1511 may be performed by a device as described with reference to FIG. 1A.

At 1515, the method may include transmitting, to the MWAB-UE via the AMF, the PDU session establishment accept message. The operations of 1515 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1515 may be performed by a device as described with reference to FIG. 1A.

In some embodiment, the first information of the MWAB-gNB may comprise one of the following: an Internet protocol (IP) address of the MWAB-gNB, or an indication for requesting the IP address of the MWAB-gNB.

In some embodiment, receiving the PDU session establishment request message may comprise receiving, from the AMF, an IP address of the AMF along with the PDU session establishment request message.

In some embodiment, the method may further include configuring a user plane function (UPF) for the MWAB-UE (MWAB-UE-UPF) with a packet filter set comprising an IP address of the AMF and an IP address of the MWAB-gNB.

In some embodiment, the method may further include allocating the IP address of the MWAB-gNB based on one of the indication of requesting the IP address of the MWAB-gNB, or the IP address of the AMF.

In some embodiment, the method may further include determining the IP address of the AMF as a source IP address and the IP address of the MWAB-gNB as a destination IP address for a downlink (DL) in the packet filter set; or determining the IP address of the MWAB-gNB as a source IP address and the IP address of the AMF as a destination IP address for an uplink (UL) in the packet filter set.

In some embodiment, the PDU session establishment accept message may comprise one of: an IP address of the AMF; the IP address of the AMF and an IP address of the MWAB-gNB.

In some embodiment, transmitting the PDU session establishment accept message may comprises transmitting second information of the MWAB-gNB along with the PDU session establishment accept message to the AMF.

In some embodiment, the second information of the MWAB-gNB may comprise one of the following: an identity of the MWAB-gNB; an IP address of the MWAB-gNB; or the identity of the MWAB-gNB and the IP address of the MWAB-gNB.

FIG. 16 illustrates a flowchart of a method 1600 that supports PDU session establishment in accordance with aspects of the present disclosure. The operations of the method 1600 may be implemented by a device or its components as described herein. For example, the operations of the method 1600 may be performed by a UE 114 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1605, the method may include transmitting, to a session management function (SMF) , a protocol data unit (PDU) session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) via an access and mobility management function (AMF) . The operations of 1605 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1605 may be performed by a device as described with reference to FIG. 1A.

At 1611, the method may include receiving, from the SMF, a PDU session establishment accept message. The operations of 1611 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1611 may be performed by a device as described with reference to FIG. 1A.

In some embodiment, the MWAB-UE may further transmit, to the AMF, one of the following along with the PDU session establishment request message: second information of MWAB-gNB, or an indication of establishing the PDU session for N2 interface.

In some embodiment, the second information of MWAB-gNB may comprise one of: an identity of the MWAB-gNB; an IP address of the MWAB-gNB; or the identity of the MWAB-gNB and the IP address of the MWAB-gNB.

In some embodiment, the MWAB-UE may transmit, to the WMAB-gNB, the IP address of the AMF in the case that the PDU session establishment accept message comprises the IP address of the AMF; and transmit, to the MWAB-gNB, the IP address of the AMF and the IP address of the MWAB-gNB in the case that the PDU session establishment accept message comprises the IP address of the AMF and the IP address of the MWAB-gNB.

It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

An apparatus for performing an access and mobility management function (AMF) , the apparatus comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the apparatus to:

receive, from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , a protocol data unit (PDU) session establishment request message in a non-access stratum (NAS) message, wherein the MWAB-UE and a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node;

transmit, to a session management function (SMF) , the PDU session establishment request message; and

transmit, to the MWAB-UE, a PDU session establishment accept message for the MWAB-UE in case of receiving the PDU session establishment accept message from the SMF;

wherein the apparatus is further caused to preserve a first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE, wherein the second information of the MWAB-gNB is indicated by the PDU session establishment request message or the PDU session establishment accept message.
The apparatus of claim 1, the second information of the MWAB-gNB being indicated by the PDU session establishment request message comprises one of the following:

the PDU session establishment request message comprises the second information of the MWAB-gNB; or

the PDU session establishment request message is transmitted with the second information of the MWAB-gNB.
The apparatus of claim 1, wherein the NAS message further comprises an indication of establishing the PDU session for N2 interface.
The apparatus of claim 1, the second information of MWAB-gNB being indicated by the PDU session establishment accept message comprises:

receiving, from the SMF, the second information of the MWAB-gNB along with the PDU session establishment accept message.
The apparatus of claim 1, wherein the apparatus is further caused to:

transmit, to the MWAB-gNB, the IP address of the AMF in case of receiving an indication of the MWAB node in an initial UE message.
The apparatus of any of claim 1, wherein the apparatus is further caused to:

preserve a second mapping between the second information of the MWAB-gNB and information of a user plane function for the MWAB-UE (MWAB-UE-UPF) in case of receiving an NG setup request message originated from the MWAB-gNB via the MWAB-UE-UPF.
The apparatus of claim 6, wherein the apparatus is further caused to:

generate a NG setup response message for the MWAB-gNB; and

transmit, to the MWAB-UE-UPF, the NG setup response message based on the second mapping.
The apparatus of any of claims 1-7, wherein one of the following:

the second information of the MWAB-gNB comprises one of: an identity of the MWAB-gNB; an IP address of the MWAB-gNB; or the identity of the MWAB-gNB and the IP address of the MWAB-gNB; or

the information of the MWAB-UE-UPF comprises an IP address of the MWAB-UE-UPF.
An apparatus for performing a session management function (SMF) , the apparatus comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the apparatus to:

receive, from an access and mobility management function (AMF) , a protocol data unit (PDU) session establishment request message originated from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , wherein the PDU session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) , and wherein the MWAB-UE and the MWAB-gNB are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node;

generate a PDU session establishment accept message for the MWAB-UE; and

transmit, to the MWAB-UE via the AMF, the PDU session establishment accept message.
The apparatus of claim 9, wherein the first information of the MWAB-gNB comprises one of the following:

an Internet protocol (IP) address of the MWAB-gNB, or

an indication for requesting the IP address of the MWAB-gNB.
The apparatus of claim 9, wherein the apparatus is further caused to:

configure a user plane function (UPF) for the MWAB-UE (MWAB-UE-UPF) with a packet filter set comprising an IP address of the AMF and an IP address of the MWAB-gNB.
The apparatus of any of claims 9-11, wherein the apparatus is caused to transmit the PDU session establishment accept message by:

transmitting second information of the MWAB-gNB along with the PDU session establishment accept message to the AMF.
The apparatus of claim 12, wherein the second information of the MWAB-gNB comprises one of the following:

an identity of the MWAB-gNB;

an IP address of the MWAB-gNB; or

the identity of the MWAB-gNB and the IP address of the MWAB-gNB.
A mobile next generation node B (gNB) with wireless access backhauling (MWAB) node comprising:

a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) ; and

a user equipment (UE) component of a mobile gNB with wireless access backhauling (MWAB-UE) ,

wherein the MWAB-UE is configured to:

transmit, to a session management function (SMF) , a protocol data unit (PDU) session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) via an access and mobility management function (AMF) ; and

receive, from the SMF, a PDU session establishment accept message.
The MWAB node of claim 14, wherein the first information of the MWAB-gNB comprises one of the following:

an Internet protocol (IP) address of the MWAB-gNB, or

an indication for requesting the IP address of the MWAB-gNB.
The MWAB node of claim 14, wherein the MWAB-UE is further configured to:

transmit, to the AMF, one of the following along with the PDU session establishment request message: second information of MWAB-gNB, or an indication of establishing the PDU session for N2 interface.
The MWAB node of claim 16, wherein the second information of MWAB-gNB comprises one of:

an identity of the MWAB-gNB;

an IP address of the MWAB-gNB; or

the identity of the MWAB-gNB and the IP address of the MWAB-gNB.
A method for performing an access and mobility management function (AMF) , the method comprising the steps of:

receiving, from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , a protocol data unit (PDU) session establishment request message in a non-access stratum (NAS) message, wherein the MWAB-UE and a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node;

transmitting, to a session management function (SMF) , the PDU session establishment request message; and

transmitting, to the MWAB-UE, a PDU session establishment accept message for the MWAB-UE in case of receiving the PDU session establishment accept message from the SMF;

wherein the method comprising the steps of preserving, a first mapping between second information of the MWAB-gNB and an identity of the MWAB-UE, wherein the second information of MWAB-gNB is indicated by the PDU session establishment request message or the PDU session establishment accept message.
A method for performing a session management function (SMF) , the method comprising the steps of:

receiving, from an access and mobility management function (AMF) , a protocol data unit (PDU) session establishment request message originated from a user equipment (UE) component of a mobile next generation node B (gNB) with wireless access backhauling (MWAB-UE) , wherein the PDU session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) , and wherein the MWAB-UE and the MWAB-gNB are collocated to compose a mobile gNB with wireless access backhauling (MWAB) node;

generating a PDU session establishment accept message for the MWAB-UE; and

transmitting, to the MWAB-UE via the AMF, the PDU session establishment accept message.
A method for performing a mobile next generation node B (gNB) with wireless access backhauling (MWAB) node, the method comprising the steps of:

transmitting, to a session management function (SMF) , a protocol data unit (PDU) session establishment request message indicating first information of a gNB component of the mobile gNB with wireless access backhauling (MWAB-gNB) via an access and mobility management function (AMF) ; and

receiving, from the SMF, a PDU session establishment accept message.