User plane traffic mapping

Abstract

The exemplary embodiments of this disclosure relate to user plane service mapping. In one aspect, a first network device establishes a Protocol Data Unit (PDU) session using a first User Plane Function (UPF) serving a terminal device connected to the first network device. The first network device determines rules to be used for service detection and mapping at a second UPF based on Transport Network Layer (TNL) information, and the second UPF is used to provide radio access backhaul to the first network device. In this way, user plane service mapping can be improved, particularly the service mapping between the QoS flow of the terminal device and the QoS flow of the mobile terminal of the relay node.

Description

Technical Field

[0001] The exemplary embodiments of this disclosure generally relate to the field of communications, and particularly to terminal devices, network devices, methods, and apparatuses for user plane service mapping, such as service detection and mapping between a quality of service (QoS) flow of a terminal device and a QoS flow of a mobile terminal (MT) of a relay node. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks. Communication devices may be served by application servers.

[0003] Such communication networks operate according to standards such as those provided by 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). An example of such a standard is the so-called 5G (fifth generation) standard provided by 3GPP. Summary of the Invention

[0004] In general, the exemplary embodiments of this disclosure provide a solution for user plane traffic mapping, such as for improving traffic detection and mapping between the QoS flow of a terminal device and the QoS flow of the MT of a relay node.

[0005] In a first aspect, a first network device is provided. The first network device may include at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the first network device to at least: establish a Protocol Data Unit (PDU) session using a first User Plane Function (UPF) serving a terminal device connected to the first network device; and determine, based on Transport Network Layer (TNL) information, rules to be used for traffic detection and mapping at a second UPF, the second UPF being used to provide radio access backhaul to the first network device.

[0006] In a second aspect, a third network device is provided. The third network device may include at least one processor and at least one memory storing instructions for a Session Management Function (SMF), which, when executed by the at least one processor, cause the third network device to at least: receive transport network layer (TNL) information related to downlink user plane traffic of a terminal device connected to a first network device from a user plane function (UPF) serving the terminal device; and send the TNL information to the first network device via an access and mobility management function (AMF) serving the terminal device.

[0007] In a third aspect, a fourth network device is provided. The fourth network device may include at least one processor and at least one memory storing instructions for a first user plane function (UPF), which, when executed by the at least one processor, cause the fourth network device to at least: receive from a session management function (SMF) an indication that a terminal device is communicating with a first network device, the first network device serving as a relay including base station functions and mobile terminals (MTs); determine, based on the indication, transport network layer (TNL) information related to downlink user plane services of the terminal device; and send the TNL information to the SMF.

[0008] In a fourth aspect, a method implemented at a first network device is provided. The method may include: establishing a Protocol Data Unit (PDU) session using a first User Plane Function (UPF) serving a terminal device connected to the first network device; and determining, based on Transport Network Layer (TNL) information, rules to be used for service detection and mapping at a second UPF, which is used to provide radio access backhaul to the first network device.

[0009] In a fifth aspect, a method implemented at a third network device is provided. The method may include: receiving transport network layer (TNL) information related to downlink user plane services of a terminal device connected to a first network device from a user plane function (UPF) serving the terminal device; and sending the TNL information to the first network device via an access and mobility management function (AMF) serving the terminal device.

[0010] In a sixth aspect, a method implemented at a fourth network device is provided. The method may include: receiving from a Session Management Function (SMF) an indication that a terminal device is communicating with a first network device, the first network device serving as a relay including base station functions and a mobile terminal (MT); determining, based on the indication, transport network layer (TNL) information related to downlink user plane services of the terminal device; and sending the TNL information to the SMF.

[0011] In a seventh aspect, an apparatus is provided. The apparatus may include: components for establishing a Protocol Data Unit (PDU) session using a first User Plane Function (UPF) serving a terminal device connected to a first network device; and components for determining, based on Transport Network Layer (TNL) information, rules to be used for service detection and mapping at a second UPF, the second UPF being used to provide radio access backhaul to the first network device.

[0012] In an eighth aspect, an apparatus is provided. The apparatus may include: components for receiving transport network layer (TNL) information related to downlink user plane services of a terminal device connected to a first network device from a user plane function (UPF) serving the terminal device; and components for transmitting the TNL information to the first network device via an access and mobility management function (AMF) serving the terminal device.

[0013] In a ninth aspect, an apparatus is provided. The apparatus may include: components for receiving from a Session Management Function (SMF) an indication that a terminal device is communicating with a first network device, the first network device serving as a relay including base station functions and a mobile terminal (MT); components for determining, based on the indication, transport network layer (TNL) information related to downlink user plane services of the terminal device; and components for sending the TNL information to the SMF.

[0014] In a tenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions that, when executed by a device, cause the device to perform at least any one of the methods according to aspects four through six of this application.

[0015] In an eleventh aspect, a computer program including instructions is provided that, when executed by a device, causes the device to perform at least any one of the methods according to the fourth to sixth aspects of this application.

[0016] In a twelfth aspect, a first network device is provided. The first network device may include: an establishment circuitry for establishing a Protocol Data Unit (PDU) session using a first User Plane Function (UPF) serving a terminal device connected to the first network device; and a determination circuitry for determining rules to be used for service detection and mapping at a second UPF based on Transport Network Layer (TNL) information, wherein the second UPF is used to provide radio access backhaul to the first network device.

[0017] In a thirteenth aspect, a third network device is provided. The third network device may include: a receiving circuit system for receiving transport network layer (TNL) information related to downlink user plane services of a terminal device connected to a first network device from a user plane function (UPF) serving the terminal device; and a transmitting circuit system for transmitting TNL information to the first network device via an access and mobility management function (AMF) serving the terminal device.

[0018] In a fourteenth aspect, a fourth network device is provided. The fourth network device may include: a receiving circuitry for receiving from a Session Management Function (SMF) an indication that a terminal device is communicating with a first network device, the first network device serving as a relay including base station functions and a mobile terminal (MT); a determining circuitry for determining transport network layer (TNL) information related to downlink user plane services of the terminal device based on the indication; and a transmitting circuitry for transmitting the TNL information to the SMF.

[0019] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0020] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:

[0021] Figure 1 The illustration shows an example of a network environment in which some embodiments of the present disclosure may be implemented;

[0022] Figure 2A The illustration shows an example of a network architecture in which some embodiments of the present disclosure may be implemented;

[0023] Figure 2B The figure illustrates a user plane protocol stack for a wireless access backhaul architecture in which some embodiments of the present disclosure may be implemented;

[0024] Figure 3 The illustration shows an example signaling process for improving traffic mapping according to some embodiments of this disclosure;

[0025] Figure 4 The illustration shows an example call flow for improving service detection and mapping according to some embodiments of the present disclosure;

[0026] Figure 5 The illustration shows a flowchart of an example method implemented at a first network device according to some embodiments of the present disclosure;

[0027] Figure 6 The illustration shows a flowchart of an example method implemented at a third network device according to some embodiments of the present disclosure;

[0028] Figure 7 The illustration shows a flowchart of an example method implemented at a fourth network device according to some embodiments of the present disclosure;

[0029] Figure 8 The illustration shows a simplified block diagram of an apparatus suitable for implementing some embodiments of the present disclosure; and

[0030] Figure 9 A block diagram illustrating an example of a computer-readable medium according to some embodiments of the present disclosure is shown.

[0031] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0032] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not constitute any limitation on the scope of this disclosure. This disclosure described herein can be implemented in various other ways besides those described below.

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

[0034] In this disclosure, references to "an embodiment," "embodiment," and "example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will understand that, whether explicitly described or not, combining it with other embodiments to affect such a feature, structure, or characteristic is within the knowledge of those skilled in the art.

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

[0036] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. The singular forms “a,” “an,” and “the” used herein also include the plural forms unless the context clearly indicates otherwise. Further understanding, the terms “includes,” “including,” “has,” “having,” “including,” and / or “including” as used herein specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, “at least one of the following: ” and “<at least one item in a list of two or more elements>” and similar wording (where a list of two or more elements is connected by “and” or “or”) means at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0037] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Pure hardware circuit implementation (such as implementations only in analog and / or digital circuit systems), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and (ii) Any part of a hardware processor (including (multiple) digital signal processors), software, and (multiple) memories that work together to enable a device such as a mobile phone or server to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to function, but may be absent when the software is not required to function.

[0038] The definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit system" also covers only hardware circuitry or a processor (or processors) or a portion of hardware circuitry or a processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0039] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiplexing (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, future fifth-generation (5G) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will naturally be communication technologies and systems that can be used to embody future types of communication technologies and systems. This should not be construed as limiting the scope of this disclosure to the systems described above.

[0040] As used herein, the term "network device" refers to a node in a communication network through which terminal devices access the network and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Header (RH), Remote Radio Header (RRH), relay, low-power nodes (such as femtoseconds, picoseconds), etc., depending on the terminology and technology used.

[0041] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal equipment", "communication equipment", "terminal", "user equipment" and "UE" are used interchangeably.

[0042] As agreed, there are other architectural options to implement the functionality of Vehicular Relay (VMR) as defined in TS 22.261. One such option is the so-called "Velcro" solution. In this solution, the Radio Access Backhaul (WAB) node, acting as a relay node, typically consists of a gNB (5G Node B) and a WAB-MT (WAB Mobile Terminal), which provides radio connectivity for New Radio (NR) backhaul. The gNB in ​​the relay node establishes an N2 interface to the Access and Mobility Management Function (AMF) residing in the 5G Core Network (5GC) and an N3 interface to the User Plane Function (UPF) in the 5GC via Protocol Data Unit (PDU) sessions. That is, the WAB node utilizes next-generation interfaces (e.g., the N2 and N3 interfaces) for both the control plane and the user plane to transparently forward data through the serving network. The WAB node is responsible for transmitting data between the base station and the core network to ensure efficient and reliable communication. This allows for efficient data transmission between the WAB node and the core network (e.g., AMF and User Plane Functions (UPF) for the WAB or UE in 5GC), while providing seamless connectivity for UEs (User Equipment) connected to the WAB node.

[0043] The main principle is that the backhaul BH connection for WAB-gNB is provided by the PDU session established with the serving network for WAB-MT. In other words, the PDU session established with the serving network for WAB-MT provides the WAB-gNB with a new radio (NR) BH connection. The WAB-gNB NG interface (used for both the control plane and user plane) is transparently forwarded through the serving network. When a UE connects to a WAB node, it treats the WAB cell as a normal cell (e.g., a 5G cell), and the UE can establish a PDU session with the UE's next-generation core network (NGCN, also known as 5GC as specified in TS 23.501) (e.g., the UE's UPF) using signaling procedures. That is, a UE connected to a WAB node treats the WAB cell like a normal cell, and the UE can establish a PDU session with the UENGCN through signaling procedures. Therefore, WAB deployment is transparent to the UE and does not require enhancements for ordinary UEs.

[0044] For a UE connected to the WAB, a PDU session is established for the UE. The PDU session can be used to transmit one or more QoS flows. Each QoS flow is identified by a QoS Flow IF (QFI). The PDU session uses a General Packet Radio Service Tunneling Protocol User Plane (GTP-U) tunnel to transmit uplink (UL) Next Generation User Plane (UL NG-U) packets from the gNB to the UPF, and downlink (DL) NG-U packets from the UPF to the gNB. In the DL direction, the UE's UPF sends downlink next generation user plane (DL NG-U) packets with a destination IP address set to the IP address of the WAB-gNB (i.e., the IP address of the co-located WAB-MT). This IP address is known to the WAB's UPF (i.e., the UPF serving the WAB or a part of the UPF serving the WAB, such as the UPF of WAB-MT), and therefore, the IP packets (including DL NG-U packets) are routed to the WAB's UPF. The WAB's UPF performs traffic detection and maps the UE's Quality of Service (QoS) flow in the DL NG-U packets to the appropriate QoS flow in the WAB-MT. Traffic mapping in the UPF is based on rules provided by the SMF. Traffic detection and mapping can be based on at least one of the TNL information, such as information from the IP header. For example, traffic detection and mapping can be based on IP address, DSCP, SPI, or a combination of one or more TNL information.

[0045] However, the WAB's UPF may fail to perform the aforementioned mapping. Since the WAB's UPF cannot decode the encrypted UE's NG-U packets, it knows neither the destination UE nor the QoS flow of the UE's NG-U packets (because the QFI is within the encrypted UE's NG-U packets). The WAB's UPF also does not know which UE's UPF has sent the DL NG-U packets. Therefore, the WAB's UPF may fail to perform correct service detection and mapping. If there is no correct service mapping in the WAB's UPF, the donor may be unable to map the UE's DL NG-U packets to the correct Data Radio Bearer (DRB). A DRB is a radio bearer used to transmit user plane information. In 5G networks, user data is carried in QoS flows, which are mapped to (multiple) DRBs by the Serving Data Adaptation Protocol (SDAP) layer. Without a correct mapping of the UE's DL NG-U packets to the DRBs, the UE's QoS cannot be guaranteed.

[0046] According to some embodiments of this disclosure, a solution is provided for user plane service detection and mapping, particularly for improving service detection and mapping between the QoS flow of a terminal device and the QoS flow of a relay node's MT. In this solution, a first network device (e.g., a relay node) establishes a Protocol Data Unit (PDU) session using a first User Plane Function (UPF) serving a terminal device connected to the first network device; and also determines rules for service detection and mapping at a second UPF based on Transport Network Layer (TNL) information, which is used to provide radio access backhaul to the first network device. The TNL information includes at least information about the transmitter of the DL NG-U packet, such as IP address, port number, and other TNL parameters / information used by the UE's UPF to transmit another DL IP packet containing the UE's DL NG-U packet. The determined rules inform the second UPF (e.g., the UPF serving the first network device) how to map IP packets carrying the UE's DL NG-U packet to a specific QoS flow of the WAB-MT's PDU session. This rule can be used by a second UPF serving the first network device to perform service detection and mapping for wireless access backhaul, and QoS for terminal devices can be guaranteed.

[0047] Figure 1Examples of network environments 100 in which some embodiments of the present disclosure may be implemented are illustrated. In the description of the exemplary embodiments of the present disclosure, network environment 100 may also be referred to as communication system 100 (e.g., part of a communication network). For illustrative purposes only, aspects of the exemplary embodiments will be described in the context of one or more terminal devices and network devices communicating with each other. However, it should be understood that the description herein can be applied to other types of apparatus or other similar apparatuses referenced using other terms.

[0048] The communication system 100 includes a network device 101 (e.g., used as a relay network device) and a plurality of terminal devices 102. The network device 101 can provide services to the terminal devices 102, and the network device 101 and the terminal devices 102 can transmit data and control information to each other. In some embodiments, the network device 101 and the terminal devices 102 can communicate via a direct link / channel. The communication system 100 may also include a network device 103 for communicating with the network device 101, which acts as a relay node. In some embodiments, the network device may be a core network device and includes multiple network functions, such as a first network function NF1, a second network function NF2, a third network function NF3, a fourth network function NF4, and a fifth network function NF5.

[0049] Figure 2A Examples of network architectures in which some embodiments of the present disclosure may be implemented are illustrated. It should be understood that UE 120 may be an example of terminal device 102, and WAB node 110 may be an example of network device 101. Furthermore, the UPF 130 of the UE, the donor 140, and the UPF 150 of the WAB may be examples of network functions.

[0050] like Figure 2AAs shown, the WAB node 110 used as a relay node can be an example of network device 101. The WAB node 110 as a relay node consists of a gNB (5G Node B) 111 and a mobile terminal unit (WAB-MT) 112, with the WAB-MT 112 providing radio connectivity for New Radio (NR) backhaul (BH). The gNB 111 in the relay node establishes N2 and N3 interfaces with the AMF and UPF residing in the 5GC via PDU sessions. PDU sessions established for the WAB-MT 112 to the serving network (e.g., the UPF) provide BH connectivity for the WAB-gNB 111. That is, the WAB-gNB BH (i.e., the NG interface to the NGCN) goes through the PDU sessions established for the WAB-MT. When UE 120 connects to WAB node 110, UE 120 treats the WAB cell as a normal cell (e.g., a 5G cell), and UE 120 can use signaling procedures to establish a PDU session with UE's UPF 130 (e.g., UPF 130 for serving UE 120).

[0051] In the communication system, between WAB node 110 and UE's UPF 130, there are two network devices, such as donor device 140 (e.g., gNB) and WAB 110's UPF 150 (e.g., UPF 150 for serving WAB-MT 112, or WAB's UPF). In the uplink direction, data from UE 120 is sequentially sent to WAB node 110, donor device 140, WAB's UPF 150, and then to UE's UPF 130. In the downlink direction, data from UE's UPF 130 is sequentially sent to WAB's UPF 150, donor device 140, WAB node 110, and then to UE 120.

[0052] Communication in network environment 100 can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as fourth-generation (4G) and fifth-generation (5G), wireless local area network communication protocols such as IEEE 802.11, and / or any other protocols currently known or to be developed in the future. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM), and / or any other technologies currently known or to be developed in the future.

[0053] It should be understood that Figure 1 The number of devices, their connections, and types shown are for illustrative purposes only and do not represent any limitation. Communication system 100 may include any suitable number of devices appropriate for implementing embodiments of this disclosure.

[0054] Figure 2B The illustration shows a user plane protocol stack for a WAB architecture according to some embodiments of this disclosure. For example... Figure 2B As shown, in the downlink direction, the UE's UPF 130 performs packet detection using a packet filter provided by the UE 120, such as identifying relevant QoS flows and adding a QoS Flow Identifier (QFI) to the NG-U General Packet Radio Service Tunneling Protocol User Plane (GTP-U) header. If the WAB node 110 (e.g., gNB) receives the QFI, the WAB 110 serving the UE 120 performs further mapping from the DL NG-U QoS flows to the UE's DRB.

[0055] During the PDU session establishment process for WAB-MT, WAB-MT 112 is assigned an IP address. This IP address is used by the co-located WAB-gNB 111 for the NG control plane / user plane (NG-C / NG-U). For UE 120 connected to WAB 110, UE's UPF 130 sends a DL NG-U packet with a destination IP address set to the IP address of WAB-gNB 111 (i.e., the IP address of co-located WAB-MT 112). This IP address is known to WAB's UPF 150 (e.g., WAB-MT's UPF 150, the UPF 150 used to serve WAB-MT 112), and therefore, the IP packet (including the DL NG-U packet) is routed to WAB's UPF 150. WAB's UPF 150 performs service mapping of the UE's QoS flow in the DL NG-U packet to the appropriate QoS flow of WAB-MT 112.

[0056] Multiple terminal devices 120 can communicate with the same WAB node 110, and multiple UEs 120 connected to the WAB node 110 can use different UPFs 130, thus allowing the NG-U tunnels of UEs 120 to multiplex up to 64 QoS flows. Each QoS flow has its own QoS. NG-U tunnels of UEs 120 from different UPFs 130 can use the same IP address of WAB-MT 112. Multiple NG-U tunnels of UEs 120 (between WAB 110 and the UE's UPF 130) can be multiplexed into a single NG-U tunnel of the WAB (between donor 140 and the WAB's UPF 150). The NG-U tunnels of UEs 120 are encrypted so that only the source node (UE's UPF 130) and the destination node (WAB 110) can decode the GTP-U header. The GTP-U packets of UE 120 are encapsulated within the GTP-U packets of WAB-MT 112 and will be sent to donor 140. Therefore, donor 140 can only see the GTP-U header of the GTP-U packets of WAB-MT 112, and cannot see the internal GTP-U header of the GTP-U packets of UE 120, which is encrypted and encapsulated within the GTP-U packets of WAB-MT 112.

[0057] As described above, for UE 120 connected to WAB 110, UE's UPF 130 sends a DL NG-U packet, where the destination IP address is set to the IP address of WAB-gNB 111 (i.e., the IP address of co-located WAB-MT 112). This IP packet is routed to WAB's UPF 150. WAB's UPF 150 performs service mapping of the IP packet to the appropriate QoS flow for WAB-MT 112. For example, assume WAB-MT 112 has two QoS flows: - QoS flow #1, 5QI=2; and - QoS flow #2, 5QI=3.

[0058] For example, suppose a specific PDU session of UE 120 has 2 QoS flows: - QoS flow #10, 5QI=3; and - QoS flow #11, 5QI=2.

[0059] Ideally, WAB's UPF 150 can perform the following mappings. - For packets associated with UE's QoS flow #10 (5QI=3), map them to WAB's QoS flow #2 (5QI=3). - For packets associated with QoS flow #11 (5QI=2) of the UE, map them to QoS flow #1 (5QI=2) of the WAB.

[0060] In 5G, a "PDU session" can be used to provide end-to-end user plane connectivity between the UE and a specific data network (DN) via a UPF. A PDU session supports one or more QoS flows. There is a one-to-one mapping between QoS flows and QoS profiles, meaning that all packets belonging to a specific QoS flow have the same "5G Quality of Service Identifier" (5QI).

[0061] However, the WAB's UPF 150 may not be able to perform the ideal mapping described above. Since the WAB's UPF 150 cannot decode the encrypted UE's NG-U packets, it knows neither the destination UE nor the QoS flow of the UE's NG-U packets (because QFI is within the encrypted UE's NG-U). Therefore, the WAB's UPF may fail to perform proper traffic detection and mapping. Without proper traffic detection and mapping in the WAB's UPF, the donor may be unable to map the UE's DL NG-U packets to the correct Data Radio Bearer (DRB). The DRB is a radio bearer used to transmit user plane information. In 5G networks, the Data Radio Bearer transmits user data by mapping to QoS flows, and then the QoS flows are mapped to the DRB by the Serving Data Adaptation Protocol (SDAP) layer. Without proper mapping of the UE's DL NG-U packets to the DRB, the UE's QoS cannot be guaranteed.

[0062] In the following text, reference will be made to Figure 3 An example signaling process 300 for improving service detection and mapping is described according to some embodiments of this disclosure.

[0063] In process 300, the first network device 301 sends (310) an indication 201 to the second network device 302 that the terminal device 102 or UE 120 is communicating with the first network device 301, which is acting as a relay including base station functionality. In some embodiments, the first network device 301 may be as follows: Figure 2A and Figure 2B The WAB node 110 shown serves as a relay node, and the second network device 302 may be associated with or serve the UE's Mobility Management Function (AMF), i.e., the UE's AMF. Transmissions from Instruction 201 to the second network device may be performed by several network entities (e.g., donor gNB 140 and WAB's UPF 150) between the first network device 301 (e.g., WAB node 110) and the second network device 302 (e.g., the UE's AMF).

[0064] In some embodiments, an indication 201 indicating that terminal device 102 or UE 120 is communicating with first network device 301 is sent from first network device 301 to second network device 302 by sending a Next Generation Application Protocol (NGAP) message including indication 201 to second network device 302, or by sending indication 201 to second network device 302 during Next Generation (NG) setup. In some embodiments, indication 201 is sent to second network device 302 by gNB (e.g., gNB 111 of WAB node 110).

[0065] Then, the second network device 302 receives (315) indication 201 and sends (320) indication 201 to the third network device 303. Then, the third network device 303 receives (325) indication 201. In some embodiments, the third network device 303 may be a session management function (SMF) serving the terminal device 100, such as the UE's SMF. In some embodiments, indication 201 is sent from the second network device 302 to the third network device 303 by initiating a Protocol Data Unit (PDU) session service operation to the third network device 303 to create or modify the context of the terminal device in the third network device 303.

[0066] Then, the third network device 303 sends (330) indication 201 to the fourth network device 304, and the fourth network device 304 receives (335) indication 201. In some embodiments, the fourth network device 304 may be a User Plane Function (UPF) serving the UE 120, such as the UE's UPF 130. For example, the fourth network device 304 includes a UPF serving a terminal device connected to the first network device. In some embodiments, indication 201 is sent from the third network device 303 to the fourth network device 304 by sending indication 201 to the fourth network device 304 via an N4 session establishment or modification request.

[0067] Upon receiving an indication 201 that UE 120 is communicating with a first network device 301 acting as a relay including base station functions, a fourth network device 304 determines (336) Transport Network Layer (TNL) information 202 related to the User Plane Function (UPF) serving UE 120 (e.g., related to UE's UPF 130). The fourth network device 304 then sends (340) the TNL information 202 to a third network device 303, and the third network device 303 receives (345) the TNL information 202. For example, knowing that the terminal device is accessing via the first network device acting as a relay node, the fourth network device 304 (e.g., UE's UPF) includes additional TNL information in its response to the third network device 303 (e.g., UE's SMF). In some embodiments, the TNL information 202 is sent to the third network device 303 by sending an N4 session establishment response or an N4 session modification response including the TNL information 202.

[0068] In some embodiments, the TNL information includes information for sending downlink (DL) Next Generation User Plane (NG-U) packets. In some embodiments, the TNL information includes: an Internet Protocol (IP) address of the UPF for sending downlink user plane services associated with the terminal device to the first network device; a port number of the UPF for sending downlink user plane services associated with the terminal device to the first network device; an external IP address of the downlink user plane services associated with the terminal device; a Security Parameter Index (SPI) associated with the downlink user plane services; a Differential Service Code Point (DSCP) value to be used by the UPF to send downlink user plane services associated with the terminal device to the first network device; an Internet Protocol Version 6 (IPv6) flow label to be used by the UPF to send downlink user plane services associated with the terminal device to the first network device; or any combination thereof. In some embodiments, a DSCP value and an IPv6 flow label are assigned to each QoS flow of the terminal device.

[0069] Then, the third network device 303 sends (350) TNL information to the second network device 302, and the second network device 302 receives (355) TNL information 202. In some embodiments, the TNL information is sent by sending a transmission message including the TNL information to the second network device 302. In some embodiments, the TNL information is sent by sending an Information Element (IE) including the TNL information to the second network device 302. For example, the IE is associated with the third network device 303 and is transparent to the second network device 302. In some embodiments, the TNL information is included in the following: Next Generation Application Protocol (NGAP) Protocol Data Unit (PDU) Session Resource Establishment Request Transmission IE; PDU Session Resource Modification Request Transmission IE; or any combination thereof.

[0070] Then, the second network device 302 sends (360) TNL information 202 to the first network device 301, and the first network device 301 receives (365) TNL information 202. In some embodiments, TNL information 202 is sent to the first network device 301 by sending a message that includes TNL information related to the third network device in an information element (IE). For example, the message includes a Next Generation Application Protocol (NGAP) Protocol Data Unit (PDU) Session Resource Establishment Request message or a PDU Session Resource Modification Request message. It should be noted that the TNL transmission from the second network device 302 to the first network device 301 may involve several entities in between.

[0071] Upon receiving TNL information, the first network device 301 determines (370) a rule 203 to be used for service detection and mapping based on the TNL information 202. In some embodiments, the rule to be used for service detection and mapping is determined by a gNB included in the first network device 301 (e.g., gNB 111 of WAB), and the determined rule 203 is then sent from the gNB to the MT (e.g., MT 112 of WAD), and then the MT 112 sends (375) the rule 203 to an AMF 306 associated with or serving the first network device 301, such as the AMF of a mobile terminal serving the first network device 201 (i.e., the AMF of WAB-MT). In some embodiments, the TNL information is sent from the gNB to the MT, and the rule 203 is determined at the MT 112, and then the MT 112 sends (375) the rule 203 to an AMF 306 associated with or serving the first network device.

[0072] In some embodiments, the rule may include a Protocol Data Unit (PDU) Session Identifier (ID); a Quality of Service (QoS) Flow ID; the source IP address of the downlink user plane service associated with the terminal device; the source port number of the downlink user plane service associated with the terminal device; the external IP address of the downlink user plane service associated with the terminal device; the SPI associated with the downlink user plane service; the DSCP value of the downlink user plane service associated with the terminal device; the IPv6 Flow Label of the downlink user plane service associated with the terminal device; or any combination thereof.

[0073] AMF 306 sends rule 203 (382) to SMF 307 serving the first network device (e.g., the SMF of WAB-MT). SMF 307 then receives (384) rule 203 and sends it (386) to the fifth network device 305. The fifth network device 305 then receives (388) rule 203. In some embodiments, the fifth network device 305 includes a UPF serving the MT of the first network device 301. For example, WAB-MT sends rules (e.g., QoS rules) to AMF 306 of WAB-MT, and AMF 306 of WAB-MT sends the rules to SMF 307 of WAB-MT, whereby SMF 307 can construct a Packet Detection Rule (PDR). SMF 307 of WAB-MT then sends the rules to the fifth network device 305 (e.g., the UPF of WAB).

[0074] The fourth network device 304 sends (390) downlink data 204, including TNL information and related to the QoS of the terminal device, to the fifth network device 305. That is, the fourth network device 304 sends data to the fifth network device 305 based on the TNL information to perform service detection and mapping. Upon receiving rule 203 and downlink data 204, the fifth network device 305 performs (396) service mapping between the QoS flow of the terminal device (e.g., UE 120) and the QoS service of the MT of the first network device (e.g., MT112 of WAB). In some embodiments, the downlink data 204 including TNL information includes downlink next-generation user plane (DL NG-U) packets, which include TNL information. In some embodiments, service mapping includes mapping the QoS flow of the terminal device associated with the DL NG-U packets to the QoS flow of the MT.

[0075] Through process 300, it can enhance control plane (CP) signaling to provide additional TNL information of the fourth network device 304 to the gNB of the first network device 301. Then, the co-located MT in the first network device 301 or the gNB of the first network device 301 can configure DL packet filters or rules for service detection and mapping based on the TNL information, enabling the fifth network device 305 to appropriately process NG-U services based on these rules, for example, mapping DL NG-U IP packets from terminal devices to the correct QoS flow of the MT of the first network device 301. Compared to the current method of only providing the first network device 301 with the NG-U endpoint in the fourth network device 304 for receiving UL NG-U packets (i.e., only providing the gNB of the first network device 301 with the UL NG-U F-TEID), the additional TNL information provided to the first network device 301 according to this disclosure includes at least the NG-U endpoint in the fourth network device 304 for sending DL NG-U packets.

[0076] By including TNL information in the response information from the fourth network device 304, DL NG-U packets can be sent to the gNB of the first network device 301. Based on the TNL information, the gNB or MT of the first network device 301 can configure DL packet filters or rules for service detection and mapping. The TNL information includes at least the transmitter information of the DL NG-U packet, such as IP address, port number, and other TNL parameters / information used by the UE's UPF to send another DL IP packet containing the UE's DL NG-U packet. UEs connected to the same WAB can use different UPFs. Each UE's UPF can be configured with different policies for setting the TNL information of DL NG-U packets. By knowing the TNL information used for DL ​​NG-U by each transmitter (i.e., the UE's UPF), the determined rules can identify specific NG-U packets from the UE's UPF. The determined rules inform the second UPF (e.g., the UPF serving the first network device, i.e., the fifth network device 305) how to map IP packets carrying the UE's DL NG-U packets to a specific QoS flow of the WAB-MT's PDU session. In this way, the fifth network device 305 can decode the encrypted UE's NG-U packets based on the configured DL packet filters or rules, and the fifth network device 305 can know the destination UE and the QoS flow of the UE's NG-U packets. Therefore, the fifth network device 305 can perform correct service detection and mapping between the QoS of the terminal device and the QoS of the first network device's MT, and the QoS for UE 120 can be guaranteed.

[0077] In the following text, reference will be made to Figure 4Example call flow 400 for improving service detection and mapping according to some embodiments of this disclosure is described. It will be understood that WAB 110 (including WAB gNB 111 and WAB MT 112) may be an example of a first network device 301; UE 120 may be an example of a terminal device; UE's AMF 160 may be an example of a second network device 302; UE's SMF 170 may be an example of a third network device 303; UE's UPF 130 may be an example of a fourth network device 304; and WAB's UPF 150 may be an example of a fifth network device 305.

[0078] like Figure 4 As shown, at 410, WAB-MT 112 is connected to donor 140. WAB-MT 112 establishes PDU session resources via the PDU session establishment procedure defined in the specification (such as TS23.502). Therefore, the DL packet filter provided from UE 120 is provided to the WAB's UPF 150. WAB-MT 112 is assigned an IP address anchored in the WAB's UPF 150, and the IP address is also the address of the WAB-gNB used for the NG control plane / user plane (NG-C / NG-U), and therefore the IP address is known to the WAB's UPF 150.

[0079] For example, a WAB-MT PDU session can include: - QoS flow #1, 5QI=2 (priority=40, packet delay budget (PDB)=150ms); and - QoS flow #2, 5QI=3 (priority=10, PDB=50ms).

[0080] At 420, UE 120 connects to WAB 110 (e.g., WAB gNB 111). UE 120 initiates a PDU session establishment procedure. When WAB 110 sends a Next Generation Application Protocol (NGAP) message (including an encapsulated Non-Access Stratum (NAS) PDU session establishment / modification request), the NGAP message includes a flag indicating that the UE is accessing via the WAB. Alternatively, this indication can be provided to the UE's AMF 160 by WAB 110 during the NG establishment procedure.

[0081] At position 430, UE's AMF 160 initiates a Network Selection Mobile Multimedia Broadcast Service (NSMF) operation to create a UE context in UE's SMF 170. UE's AMF 160 can indicate to UE's SMF 170 that UE 110 is accessing or communicating with WAB 110 via WAB 110. In other words, WAB node 110 indicates to UE's SMF 170 via UE's AMF 160 that UE 120 is accessing via WAB 110.

[0082] At 440, UE's SMF 170 initiates an N4 session establishment / modification request to UE's UPF 130. In this way, UE's SMF 170 notifies UE's UPF 130 that UE is accessing via WAB 110. Then, at 450, UE's UPF 130 confirms this indication by sending an N4 session establishment / modification response to UE's SMF 170. Knowing that UE 120 is accessing via WAB 110, UE's UPF 130 can include additional Transport Network Layer (TNL) information in the N4 session establishment / modification response. That is, TNL information is included in the N4 session establishment / modification response sent at 450. TNL information can refer to information in the network transport layer that provides end-to-end data transmission services. TNL information typically includes source and destination addresses, port numbers, data transmission sequences, and flow control. During network transmission, TNL information is used to identify and route data packets to ensure that data arrives at its correct destination.

[0083] In some embodiments, the additional TNL information includes user plane endpoint information in the terminal device's UPF used to transmit DL NG-U packets, such as GTP-U endpoint information (IP address, port number) used to transmit DL NG-U in the UE's UPF 130. GTP-U endpoint information refers to information related to the GTP-U protocol endpoint, including node identifier, IP address, port number, etc. Each GTP-U endpoint is identified by a TEID (Tunnel Endpoint Identifier), which uniquely identifies the GTP-U tunnel. Furthermore, the GTP-U endpoint needs to know the IP address and port number of its peer node in order to establish and maintain the GTP-U tunnel.

[0084] It should be understood that the current UPF only provides the UL GTP-U endpoint in the UE's UPF 130 for receiving UL NG-U via SMF 170 and AMF 160, and not for sending DL NG-U to gNB 111. That is, the additional TNL information provided to WAB 110 according to this disclosure includes at least the NG-U endpoint in UPF 130 for sending DL NG-U packets. The current standard only provides the NG-U endpoint in UPF 130 to WAB 110 for receiving UL NG-U packets; that is, the UE's SMF 170 provides the UL NG-U F-TEID to gNB 111.

[0085] In some embodiments, when using Internet Protocol Security (IPSec) tunneling mode to protect NG-U packets of an end device, the additional TNL information includes an external Internet Protocol (IP) address. If the IPSec tunnel is used to protect NG-U, the IP address is an external IP address. In some embodiments, the additional TNL information includes the end device's UPF plan for Differentiated Service Code Point (DSCP) information for DL ​​NG-U packets; optionally, this information may be per QoS flow for each UE. In some embodiments, the additional TNL information includes the end device's UPF plan for Internet Protocol Version 6 (IPv6) flow label for DL ​​NG-U packets; optionally, this information may be per QoS flow for each UE.

[0086] At 460, the UE's SMF 170 will include additional TNL information received from the UE's UPF 130. Nsm_ Communication_N1N2 Message Transmission The AMF 160 is sent to the UE to create an SMF context. For example, additional TNL information can be included in the SMF-related IE that is transparent to the AMF 160. For example, additional TNL information can be added to... NGAP PDU Request to establish a resource transfer element (IE) , PDU Session Resource Modification Request Transmitting IEs, or other SMF-related IEs defined in specifications such as TS 38.413.

[0087] At position 470, the UE's AMF 160 sends additional TNL information, including the SMF-related IE, to the WAB-gNB 111. NGAP PDU Session Resource Establishment Request MessageIn other words, the UE's SMF 170 forwards the additional TNL information received from the UE's UPF 130 to the UE's gNB 111 (i.e., WAB 110 in this case) via the UE's AMF 160. Control plane (CP) signaling includes UPF<->SMF signaling and SMF->gNB signaling (i.e., SMF-related IEs as defined in specifications such as TS38.413). The additional TNL information provided to the WAB includes at least the NG-U endpoint in the UPF used to send DL NG-U packets.

[0088] Now, perform the normal PDU session establishment procedure. Establish the UE's PDU session. For example, the UE's PDU session has 2 QoS flows. - QoS flow #10, 5QI=3; and - QoS flow #11, 5QI=2

[0089] WAB-gNB 111 now has the following information for UE PDU sessions, such as: - QoS flow #10, 5QI=3, UPF IP address is 192.168.0.1, DSCP=a, for applicable DL services; and - QoS flow #11, 5QI=2, UPF IP address is 192.168.0.1, DSCP=b, for applicable DL services.

[0090] It should be understood that the IP address of the aforementioned UPF is the IP address of the UE's UPF 130. WAB-gNB 111 can send this new TNL information to WAB-MT 112.

[0091] Based on the received TNL information, WAB-MT 112 or gNB 111 determines to update the rules (or packet filters) for service detection and mapping in the WAB's UPF 150 that will be used for the PDU session. For example, WAB-gNB 111 notifies the co-located WAB-MT 112 of the TNL information received from the UE's UPF 130. In some embodiments, WAB-MT 112 initiates a PDU session modification procedure to update the rules in the WAB's UPF 150. In some embodiments, WAB-MT 112 may initiate a PDU session establishment procedure to establish a new PDU session and provide the rules (packet filters) to be used by the WAB's UPF 150. In some embodiments, WAB-gNB 111 determines the rules to be used for service detection and mapping based on the TNL information. At 480, WAB-MT 112 sends the determined rules to the WAB's UPF 150, for example, via donor 140, the WAB's AMF ( Figure 4(not shown in the image) and WAB's SMF ( Figure 4 (Not shown in the image).

[0092] For example, a rule (group filter) could be as follows: - QoS flow ID#1, remote IP address 192.168.0.1, DSCP=b, for applicable DL services; and - QoS flow ID#2, remote IP address is 192.168.0.1, DSCP=a, for applicable DL services.

[0093] At 490, WAB's UPF 150 can update the current rules used for service detection and mapping to the rules provided by WAB-MT112. At 495, WAB's UPF 150 receives DL NG-U packets from UE's UPF 130, and the final destination of the DL NG-U packets is at the UE. DL NG-U packets are sent from UE's UPF 130 to WAB's UPF 150 using TNL information such as a remote IP address (i.e., the IP address of UE's UPF 130), port number, DSCP, or IPv6 flow label.

[0094] For example, for a UE 120 connected to WAB 110, the UE's UPF 130 sends a DLNG-U packet with a destination IP address set to WAB-gNB 111 (i.e., the IP address of the co-located WAB-MT 112). This IP packet (including the DL NG-U packet) is routed to the WAB's UPF 150. The WAB's UPF 150 now has rules for identifying a specific DL NG-U packet of the UE based on at least one of the following: remote IP address (i.e., the IP address of the UE's UPF 130), port number, DSCP, or IPv6 flow label. Based on the updated rules (packet filter) and the DL NG-U packets received from the UE's UPF 130 via TNL information, the WAB's UPF 150 performs traffic detection and mapping based on the IP header (e.g., source IP address, DSCP, etc.). Therefore, the UPF 150 of WAB can perform service mapping from the QoS flow of UE 120 in the DL NG-U packet to the appropriate QoS flow of WAB-MT 112.

[0095] For example, the UE's NG-U packets will be mapped to the following WAB-MT QoS flows: - For UE's QoS flow #10 (5QI=3), WAB's UPF 150 maps it to WAB's QoS flow #2 (5QI=3); and - For UE's QoS flow #11 (5QI=2), WAB's UPF 150 maps it to WAB's QoS flow #1 (5QI=2).

[0096] Then, the WAB's UPF 150 sends the DL NG-U packets, which encapsulate the UE's DL NG-U packets, to donor 140. Donor 140 performs service mapping by mapping DL packets associated with a specific QoS flow (e.g., QoS flow #2) to a specific DRB and sends it to WAB-MT 112. WAB-MT 112 then forwards the UE's DL NG-U packets to the co-located WAB-gNB 111, and WAB-gNB 111 then further forwards the DL NG-U packets to the UE.

[0097] By calling flow 400, it can enhance control plane (CP) signaling to provide gNB 111 with additional TNL information of the UE's UPF 130. Then, the co-located WAB-MT 112 in WAB node 110 is configured with DL packet filters to be used in the WAB's UPF 150, so the WAB's UPF 150 can appropriately handle NG-U traffic, for example, mapping the UE's DL NG-U IP packets to the correct QoS flow of WAB-MT 112. Compared to the current method of only providing the NG-U endpoint in the UE's UPF 130 for receiving UL NG-U packets to WAB node 110 (e.g., the UE's SMF 170 only provides UL NG-U F-TEID to gNB 111 via the UE's AMF 160), the additional TNL information provided to the WAB node 110 of this disclosure includes at least the NG-U endpoint in the UPF for sending DL NG-U packets.

[0098] By including TNL information in the response information from the UE's UPF 130, DL NG-U packets can be sent to the UE's gNB 111. Based on the TNL information, WAB-MT 112 in WAB node 110 configures DL packet filters or rules to be used for service detection and mapping in the WAB's UPF 150. In this way, the WAB's UPF 150 can decode the encrypted UE's NG-U packets based on the configured DL packet filters or rules, and the WAB's UPF 150 can know the destination UE and the QoS flow of the UE's NG-U packets. Therefore, the WAB's UPF 150 can perform correct service detection and mapping, and the QoS for the UE 120 can be guaranteed.

[0099] Figure 5A flowchart illustrating an example method 500 implemented at a first network device according to some other embodiments of the present disclosure is shown. Reference will be made to this flowchart for discussion purposes. Figure 3 Method 500 is described from the perspective of the first network device 301 (e.g., WAB node 110).

[0100] At block 510, the first network device 301 establishes a Protocol Data Unit (PDU) session using a first User Plane Function (UPF) serving a terminal device connected to the first network device. At block 520, the first network device 301 determines, based on Transport Network Layer (TNL) information, the rules to be used for service detection and mapping at the second UPF, which is used to provide radio access backhaul to the first network device.

[0101] In some embodiments, the first network device 301 determines the rule based on TNL information associated with a first UPF serving the terminal device, wherein the TNL information is received from the Session Management Function (SMF) serving the terminal device.

[0102] In some embodiments, the first network device 301 includes a base station (BS) and a mobile terminal (MT), and the first network device 301 determines the rule by: determining the rule to be used for service detection and mapping at the BS or MT; and sending the rule from the MT to the session management function (SMF) that controls the second UPF via the access and mobility management function (AMF) serving the MT of the first network device.

[0103] In some embodiments, the first network device 301 also sends an indication to the Access and Mobility Management Function (AMF) serving the terminal device that the terminal device is communicating with the first network device, wherein TNL information is determined at the first UPF serving the terminal device based on the indication.

[0104] In some embodiments, the transmission of the instruction and the reception of the TNL information are performed by the BS of the first network device. In some embodiments, the TNL information includes at least one of the following: an Internet Protocol (IP) address of a first UPF for transmitting downlink user plane services associated with the terminal device to the first network device; a port number of the first UPF for transmitting downlink user plane services associated with the terminal device to the first network device; an external IP address of the downlink user plane services associated with the terminal device; a Security Parameter Index (SPI) associated with the downlink user plane services; a Differential Service Code Point (DSCP) value to be transmitted by the first UPF to the first network device for the downlink user plane services associated with the terminal device; or an Internet Protocol Version 6 (IPv6) flow label to be transmitted by the first UPF to the first network device for the downlink user plane services associated with the terminal device.

[0105] In some embodiments, the rule includes at least one of the following: Protocol Data Unit (PDU) Session Identifier (ID); Quality of Service (QoS) Flow ID; Source IP address of the downlink user plane service associated with the terminal device; Source port number of the downlink user plane service associated with the terminal device; External IP address of the downlink user plane service associated with the terminal device; SPI associated with the downlink user plane service; DSCP value of the downlink user plane service associated with the terminal device; or IPv6 Flow Label of the downlink user plane service associated with the terminal device.

[0106] Figure 6 A flowchart illustrating an example method 600 implemented at a third network device according to some other embodiments of the present disclosure is shown. Reference will be made to this flowchart for discussion purposes. Figure 3 Method 600 is described from the perspective of a third network device 303 (e.g., the UE's SMF).

[0107] At box 610, the third network device 303 receives transport network layer (TNL) information related to downlink user plane services of the terminal device from the user plane function (UPF) serving the terminal device connected to the first network device. At box 620, the third network device 303 sends TNL information to the first network device via the access and mobility management function (AMF) serving the terminal device.

[0108] In some embodiments, the third network device 303 also receives from the AMF an indication that the terminal device is communicating with the first network device, which is used as a relay including base station functions; and sends the indication to the UPF to trigger the UPF to send TNL information to the first network device via the AMF.

[0109] In some embodiments, the TNL information includes at least one of the following: an Internet Protocol (IP) address of the UPF used to send downlink user plane services associated with the terminal device to the first network device; a port number of the UPF used to send downlink user plane services associated with the terminal device to the first network device; an external Internet Protocol (IP) address of the downlink user plane services associated with the terminal device; a Security Parameter Index (SPI) associated with the downlink user plane services; a Differential Service Code Point (DSCP) value to be used by the UPF to send downlink user plane services associated with the terminal device to the first network device; or an Internet Protocol Version 6 (IPv6) flow label to be used by the UPF to send downlink user plane services associated with the terminal device to the first network device.

[0110] Figure 7A flowchart illustrating an example method 700 implemented at a fourth network device according to some other embodiments of the present disclosure is shown. Reference will be made to this flowchart for discussion purposes. Figure 3 Method 700 is described from the perspective of the fourth network device 304 (e.g., the UPF of the UE).

[0111] At block 710, the fourth network device 304 receives an indication from the Session Management Function (SMF) that a terminal device is communicating with a first network device, which acts as a relay including base station functions and mobile terminals (MTs). At block 720, the fourth network device 304 determines Transport Network Layer (TNL) information related to the downlink user plane services of the terminal device based on this indication. At block 730, the fourth network device 304 sends the TNL information to the SMF.

[0112] In some embodiments, the fourth network device 304 sends TNL information by sending an N4 session establishment response or an N4 session modification response including TNL information to the SMF.

[0113] In some embodiments, the TNL information includes information that will be used to perform service mapping for sending downlink (DL) next-generation user plane (NG-U) packets to a second UPF serving the MT of the first network device. In some embodiments, the TNL information includes at least one of the following: the Internet Protocol (IP) address of the first UPF used to send downlink user plane services associated with the terminal device to the first network device; the port number of the first UPF used to send downlink user plane services associated with the terminal device to the first network device; the external IP address of the downlink user plane services associated with the terminal device; the Security Parameter Index (SPI) associated with the downlink user plane services; the Differential Service Code Point (DSCP) value to be used by the first UPF to send downlink user plane services associated with the terminal device to the first network device; or the Internet Protocol version 6 (IPv6) flow label to be used by the first UPF to send downlink user plane services associated with the terminal device to the first network device.

[0114] In some embodiments, an apparatus capable of performing method 500 (e.g., a first network device 301) may include components for performing the corresponding steps of method 500. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0115] In some embodiments, the apparatus includes: components for establishing a Protocol Data Unit (PDU) session using a first User Plane Function (UPF) serving a terminal device connected to a first network device; and components for determining, based on Transport Network Layer (TNL) information, rules to be used for traffic detection and mapping at a second UPF, which is used to provide radio access backhaul to the first network device. In some embodiments, the apparatus determines the rules based on TNL information associated with the first UPF serving the terminal device, wherein the TNL information is received from a Session Management Function (SMF) serving the terminal device.

[0116] In some embodiments, the apparatus includes a base station (BS) and a mobile terminal (MT), and the apparatus determines the rule by: determining at the BS or MT the rule to be used for service detection and mapping; and sending the rule from the MT to the session management function (SMF) controlling the second UPF via the access and mobility management function (AMF) of the MT serving the first network device.

[0117] In some embodiments, the apparatus further includes components for sending an indication to the Access and Mobility Management Function (AMF) serving the terminal device that the terminal device is communicating with a first network device, wherein TNL information is determined at the first UPF serving the terminal device based on the indication.

[0118] In some embodiments, the transmission of the instruction and the reception of the TNL information are performed by the BS of the first network device. In some embodiments, the TNL information includes at least one of the following: an Internet Protocol (IP) address of a first UPF for transmitting downlink user plane services associated with the terminal device to the first network device; a port number of the first UPF for transmitting downlink user plane services associated with the terminal device to the first network device; an external IP address of the downlink user plane services associated with the terminal device; a Security Parameter Index (SPI) associated with the downlink user plane services; a Differential Service Code Point (DSCP) value to be transmitted by the first UPF to the first network device for the downlink user plane services associated with the terminal device; or an Internet Protocol Version 6 (IPv6) flow label to be transmitted by the first UPF to the first network device for the downlink user plane services associated with the terminal device.

[0119] In some embodiments, the rule includes at least one of the following: Protocol Data Unit (PDU) Session Identifier (ID); Quality of Service (QoS) Flow ID; Source IP address of the downlink user plane service associated with the terminal device; Source port number of the downlink user plane service associated with the terminal device; External IP address of the downlink user plane service associated with the terminal device; SPI associated with the downlink user plane service; DSCP value of the downlink user plane service associated with the terminal device; or IPv6 Flow Label of the downlink user plane service associated with the terminal device.

[0120] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 500. In some embodiments, the apparatus includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to achieve the performance of the apparatus.

[0121] In some embodiments, an apparatus capable of performing method 600 (e.g., a third network device 303) may include components for performing the corresponding steps of method 600. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0122] In some embodiments, the apparatus includes: components for receiving transport network layer (TNL) information related to downlink user plane services of a terminal device from a user plane function (UPF) serving a terminal device connected to a first network device; and components for sending the TNL information to the first network device via an access and mobility management function (AMF) serving the terminal device.

[0123] In some embodiments, the apparatus further includes components for: receiving from the AMF an indication that the terminal device is communicating with a first network device, the first network device serving as a relay including base station functions; and sending the indication to the UPF to trigger the UPF to send TNL information to the first network device via the AMF.

[0124] In some embodiments, the TNL information includes at least one of the following: an Internet Protocol (IP) address of the UPF used to send downlink user plane services associated with the terminal device to the first network device; a port number of the UPF used to send downlink user plane services associated with the terminal device to the first network device; an external Internet Protocol (IP) address of the downlink user plane services associated with the terminal device; a Security Parameter Index (SPI) associated with the downlink user plane services; a Differential Service Code Point (DSCP) value to be used by the UPF to send downlink user plane services associated with the terminal device to the first network device; or an Internet Protocol Version 6 (IPv6) flow label to be used by the UPF to send downlink user plane services associated with the terminal device to the first network device.

[0125] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 600. In some embodiments, the apparatus includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to achieve the performance of the apparatus.

[0126] In some embodiments, an apparatus capable of performing method 700 (e.g., a fourth network device 304) may include components for performing the corresponding steps of method 700. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0127] In some embodiments, the apparatus includes: components for receiving from a Session Management Function (SMF) an indication that a terminal device is communicating with a first network device, the first network device serving as a relay including base station functions and a mobile terminal (MT); components for determining transport network layer (TNL) information related to downlink user plane services of the terminal device based on the indication; and components for sending the TNL information to the SMF.

[0128] In some embodiments, the device sends TNL information by sending an N4 session establishment response or an N4 session modification response including TNL information to the SMF. In some embodiments, the TNL information includes information that will be used to perform service mapping by sending downlink (DL) next-generation user plane (NG-U) packets to a second UPF serving the MT of the first network device.

[0129] In some embodiments, the TNL information includes at least one of the following: an Internet Protocol (IP) address of a first UPF used to send downlink user plane services associated with a terminal device to a first network device; a port number of the first UPF used to send downlink user plane services associated with a terminal device to the first network device; an external IP address of the downlink user plane services associated with the terminal device; a Security Parameter Index (SPI) associated with the downlink user plane services; a Differential Service Code Point (DSCP) value to be used by the first UPF to send downlink user plane services associated with a terminal device to the first network device; or an Internet Protocol Version 6 (IPv6) flow label to be used by the first UPF to send downlink user plane services associated with a terminal device to the first network device.

[0130] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 700. In some embodiments, the apparatus includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to achieve the performance of the apparatus.

[0131] Figure 8 This is a simplified block diagram of a device 800 suitable for implementing embodiments of the present disclosure. The device 800 can be provided to implement communication devices, such as terminal device 102, network device 101, and network device 103, as... Figure 1 As shown, device 800 includes one or more processors 810, one or more memories 820 coupled to processor 810, and one or more communication modules 840 coupled to processor 810.

[0132] The communication module 840 is used for bidirectional communication. The communication module 840 has at least one antenna to facilitate communication. The communication interface can represent any interface required for communication with other network devices.

[0133] Processor 810 can be of any type suitable for a local technology network, and by way of non-limiting example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 800 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.

[0134] Memory 820 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 824, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 822 and other volatile memories that do not persist during power outages.

[0135] Computer program 830 includes computer-executable instructions that are executed by the associated processor 810. Program 830 may be stored in ROM 820. Processor 810 may perform any suitable actions and processes by loading program 830 into RAM 822.

[0136] The embodiments of this disclosure can be implemented by a program, such that device 800 can execute the reference. Figures 5 to 7 Any process of the methods discussed. Embodiments of this disclosure can also be implemented in hardware or a combination of software and hardware.

[0137] In some embodiments, program 830 may be tangibly contained in a computer-readable medium, which may be included in device 800 (such as memory 820) or other storage device accessible to device 800. Device 800 may load program 830 from the computer-readable medium into RAM 822 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0138] Figure 9 An example of a computer-readable medium 900 in the form of a CD or DVD according to some embodiments of the present disclosure is illustrated. A program 830 is stored on the computer-readable medium. It should be noted that although the computer-readable medium 900 is depicted in the form of a CD or DVD, the computer-readable medium 900 may be any other form suitable for carrying or storing the program 830.

[0139] Generally, the various embodiments of this disclosure can be implemented using hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented using hardware, while others can be implemented using firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented using hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0140] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in a program module, which execute in a device on a target real or virtual processor to perform the above-referenced... Figures 5 to 7 The method described is 500 to 700. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions of a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0141] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0142] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0143] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination of the foregoing. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. The term "non-transient" as used herein is a limitation on the medium itself (i.e., tangible, not signaling), not a limitation on the persistence of data storage (e.g., RAM and ROM).

[0144] Furthermore, although operations are described in a specific order, this should not be construed as requiring the operations to be performed in the specific order shown or sequentially, or to perform all of the shown operations to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0145] Although this disclosure is described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A first network device for communication, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the first network device to perform at least the following: A Protocol Data Unit (PDU) session is established using the first User Plane Function (UPF) serving the terminal device connected to the first network device; as well as Based on the Transport Network Layer (TNL) information, the rules that will be used for service detection and mapping at the second UPF are determined, and the second UPF is used to provide wireless access backhaul to the first network device.

2. The first network device of claim 1, wherein the rule is determined based on the TNL information, the TNL information being associated with the first UPF serving the terminal device, and wherein the TNL information is received from the Session Management Function (SMF) serving the terminal device.

3. The first network device according to claim 1, wherein the first network device comprises a base station (BS) and a mobile terminal (MT), and The rules are determined as follows: At the BS or the MT, the rules that will be used for service detection and mapping are determined; as well as The rules are sent from the MT to the Session Management Function (SMF) that controls the second UPF via the Access and Mobility Management Function (AMF) of the MT serving the first network device.

4. The first network device according to any one of claims 2 to 3, wherein the instructions, when executed by the at least one processor, further cause the first network device to perform: An indication is sent to the Access and Mobility Management Function (AMF) serving the terminal device that the terminal device is communicating with the first network device, wherein the TNL information is determined at the first UPF serving the terminal device based on the indication.

5. The first network device according to claim 4, wherein the indicated transmission and the reception of the TNL information are performed by the BS of the first network device.

6. The first network device according to any one of claims 1 to 5, wherein the TNL information includes at least one of the following: The Internet Protocol (IP) address of the first UPF used to send downlink user plane services related to the terminal device to the first network device; The port number of the first UPF used to send downlink user plane services related to the terminal device to the first network device; The external IP address of the downlink user plane service associated with the terminal device; Index of Security Parameters (SPI) related to downlink user plane services; The first UPF will be used to send the differential service code point (DSCP) value of the downlink user plane service related to the terminal device to the first network device; or The first UPF will be used to send Internet Protocol version 6 (IPv6) flow labels for downlink user plane services related to the terminal device to the first network device.

7. The first network device according to any one of claims 1 to 6, wherein the rule includes at least one of the following: Protocol Data Unit (PDU) Session Identifier (ID); Quality of Service (QoS) Stream ID; The source Internet Protocol (IP) address of the downlink user plane service associated with the terminal device; The source port number of the downlink user plane service associated with the terminal device; The external IP address of the downlink user plane service associated with the terminal device; Index of Security Parameters (SPI) related to downlink user plane services; The differential service code point (DSCP) value of the downlink user plane service associated with the terminal device; or Internet Protocol version 6 (IPv6) flow labels for downlink user plane services associated with the terminal device.

8. A third network device for communication, comprising: At least one processor; as well as At least one memory stores instructions for a Session Management Function (SMF), which, when executed by the at least one processor, cause the third network device to perform at least the following: Receive transport network layer (TNL) information related to the downlink user plane services of the terminal device from the user plane function (UPF) serving the terminal device connected to the first network device; as well as The TNL information is sent to the first network device via the Access and Mobility Management Function (AMF) serving the terminal device.

9. The third network device of claim 8, wherein the instructions, when executed by the at least one processor, further cause the third network device to perform: The terminal device receives an indication from the AMF that it is communicating with a first network device, which acts as a relay including base station functions; and The instruction is sent to the UPF to trigger the UPF to send the TNL information to the first network device via the AMF.

10. The third network device according to claim 8, wherein the TNL information includes at least one of the following: The Internet Protocol (IP) address of the UPF used to send downlink user plane services related to the terminal device to the first network device; The port number of the UPF used to send downlink user plane services related to the terminal device to the first network device; The external Internet Protocol (IP) address of the downlink user plane service associated with the terminal device; Index of Security Parameters (SPI) related to downlink user plane services; The UPF will be used to send the differential service code point (DSCP) value of the downlink user plane service related to the terminal device to the first network device; or The UPF will be used to send Internet Protocol version 6 (IPv6) flow labels for downlink user plane services related to the terminal device to the first network device.

11. A fourth network device for communication, comprising: At least one processor; as well as At least one memory stores instructions for a first user plane function (UPF), which, when executed by the at least one processor, cause the fourth network device to perform at least the following: Receive an indication from the Session Management Function (SMF) that the terminal device is communicating with a first network device, which serves as a relay including base station functions and mobile terminals (MTs); Based on the indication, determine the transport network layer (TNL) information related to the downlink user plane services of the terminal device; as well as Send the TNL information to the SMF.

12. The fourth network device according to claim 11, wherein sending the TNL information includes: Send an N4 session establishment response or an N4 session modification response, including the TNL information, to the SMF.

13. The fourth network device according to claim 11 or 12, wherein the TNL information includes information that will be used to perform service mapping for sending downlink (DL) next-generation user plane (NG-U) packets to a second UPF of the MT serving the first network device.

14. The fourth network device according to any one of claims 11 to 13, wherein the TNL information includes at least one of the following: The Internet Protocol (IP) address of the first UPF used to send downlink user plane services related to the terminal device to the first network device; The port number of the first UPF used to send downlink user plane services related to the terminal device to the first network device; The external IP address of the downlink user plane service associated with the terminal device; Index of Security Parameters (SPI) related to downlink user plane services; The first UPF will be used to send the differential service code point (DSCP) value of the downlink user plane service related to the terminal device to the first network device; or The first UPF will be used to send Internet Protocol version 6 (IPv6) flow labels for downlink user plane services related to the terminal device to the first network device.

15. A method for communication performed by a first network device, comprising: A Protocol Data Unit (PDU) session is established using the first User Plane Function (UPF) serving the terminal device connected to the first network device; as well as Based on the Transport Network Layer (TNL) information, the rules that will be used for service detection and mapping at the second UPF are determined, and the second UPF is used to provide wireless access backhaul to the first network device.

16. The method of claim 15, wherein the rule is determined based on the TNL information, the TNL information being associated with the first UPF serving the terminal device, and wherein the TNL information is received from the Session Management Function (SMF) serving the terminal device.

17. The method of claim 15, wherein the first network device comprises a base station (BS) and a mobile terminal (MT), and The rules are determined as follows: At the BS or the MT, the rules that will be used for service detection and mapping are determined; as well as The rules are sent from the MT to the Session Management Function (SMF) that controls the second UPF via the Access and Mobility Management Function (AMF) of the MT serving the first network device.

18. The method according to any one of claims 16 to 17, further comprising: The first network device sends an indication from the Access and Mobility Management Function (AMF) serving the terminal device that the terminal device is communicating with the first network device, wherein the TNL information is determined at the first UPF serving the terminal device based on the indication.

19. The method of claim 18, wherein the indicated transmission and the reception of the TNL information are performed by the BS of the first network device.

20. The method according to any one of claims 15 to 19, wherein the TNL information comprises at least one of the following: The Internet Protocol (IP) address of the first UPF used to send downlink user plane services related to the terminal device to the first network device; The port number of the first UPF used to send downlink user plane services related to the terminal device to the first network device; The external IP address of the downlink user plane service associated with the terminal device; Index of Security Parameters (SPI) related to downlink user plane services; The first UPF will be used to send the differential service code point (DSCP) value of the downlink user plane service related to the terminal device to the first network device; or The first UPF will be used to send Internet Protocol version 6 (IPv6) flow labels for downlink user plane services related to the terminal device to the first network device.

21. The method according to any one of claims 15 to 20, wherein the rule comprises at least one of the following: Protocol Data Unit (PDU) Session Identifier (ID); Quality of Service (QoS) Stream ID; The source Internet Protocol (IP) address of the downlink user plane service associated with the terminal device; The source port number of the downlink user plane service associated with the terminal device; The external IP address of the downlink user plane service associated with the terminal device; Index of Security Parameters (SPI) related to downlink user plane services; The differential service code point (DSCP) value of the downlink user plane service associated with the terminal device; or Internet Protocol version 6 (IPv6) flow labels for downlink user plane services associated with the terminal device.

22. A method for communication performed by a third network device, comprising: Receive transport network layer (TNL) information related to the downlink user plane services of the terminal device from the user plane function (UPF) serving the terminal device connected to the first network device; as well as The TNL information is sent to the first network device via the Access and Mobility Management Function (AMF) serving the terminal device.

23. The method of claim 22, further comprising: The terminal device receives an indication from the AMF that it is communicating with a first network device, which is used as a relay including base station functions; as well as The instruction is sent to the UPF to trigger the UPF to send the TNL information to the first network device via the AMF.

24. The method of claim 22, wherein the TNL information comprises at least one of the following: The Internet Protocol (IP) address of the UPF used to send downlink user plane services related to the terminal device to the first network device; The port number of the UPF used to send downlink user plane services related to the terminal device to the first network device; The external Internet Protocol (IP) address of the downlink user plane service associated with the terminal device; Index of Security Parameters (SPI) related to downlink user plane services; The UPF will be used to send the differential service code point (DSCP) value of the downlink user plane service related to the terminal device to the first network device; or The UPF will be used to send Internet Protocol version 6 (IPv6) flow labels for downlink user plane services related to the terminal device to the first network device.

25. A method for communication performed by a fourth network device, comprising: Receive an indication from the Session Management Function (SMF) that the terminal device is communicating with a first network device, which serves as a relay including base station functions and mobile terminals (MTs); Based on the indication, determine the transport network layer (TNL) information related to the downlink user plane services of the terminal device; as well as Send the TNL information to the SMF.

26. The method of claim 25, wherein sending the TNL information comprises: Send an N4 session establishment response or an N4 session modification response, including the TNL information, to the SMF.

27. The method of claim 25 or 26, wherein the TNL information includes information that will be used to perform service mapping by sending downlink (DL) next-generation user plane (NG-U) packets to a second UPF of the MT serving the first network device.

28. The method according to any one of claims 25 to 27, wherein the TNL information comprises at least one of the following: The Internet Protocol (IP) address of the first UPF used to send downlink user plane services related to the terminal device to the first network device; The port number of the first UPF used to send downlink user plane services related to the terminal device to the first network device; The external IP address of the downlink user plane service associated with the terminal device; Index of Security Parameters (SPI) related to downlink user plane services; The first UPF will be used to send the differential service code point (DSCP) value of the downlink user plane service related to the terminal device to the first network device; or The first UPF will be used to send Internet Protocol version 6 (IPv6) flow labels for downlink user plane services related to the terminal device to the first network device.

29. An apparatus comprising: Components for establishing Protocol Data Unit (PDU) sessions using a first User Plane Function (UPF) serving a terminal device connected to the first network device; as well as A component for determining, based on Transport Network Layer (TNL) information, the rules to be used for service detection and mapping at the second UPF, which is used to provide radio access backhaul to the first network device.

30. An apparatus comprising: A component for receiving transport network layer (TNL) information related to downlink user plane services of a terminal device connected to a first network device from a user plane function (UPF). as well as Components for sending the TNL information to the first network device via the Access and Mobility Management Function (AMF) serving the terminal device.

31. An apparatus comprising: A component for receiving an indication from a Session Management Function (SMF) that a terminal device is communicating with a first network device, the first network device serving as a relay including base station functions and a mobile terminal (MT); Components for determining transport network layer (TNL) information related to downlink user plane services of the terminal device based on the indication; as well as A component used to send the TNL information to the SMF.

32. A non-transitory computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the method according to any one of claims 15 to 28.

Images