In-vehicle relay using protocol data unit (PDU) sessions

Abstract

The invention discloses a method. The method comprises the following steps of: establishing a protocol data unit (PDU) session by vehicle-mounted relay user equipment (VMR-UE) and a core network subscribed by the VMR-UE; and transmitting, to a core network, an indication of the PDU session for at least one of an interface control message of an in-vehicle relay network node (VMR-NN) installed in the vehicle with the VMR-UE, user plane (UP) traffic for the at least one second UE connected to the VMR-NN, or control plane (CP) traffic for the at least one second UE connected to the VMR-NN.

Description

Technical Field

[0001] Various example embodiments relate generally to wireless networks, and more particularly to extending wireless networks using vehicle-mounted relays. Background Art

[0002] Wireless networks offer significant advantages for user mobility. The ability for users to stay connected while on the move provides advantages not only to the user, but also to society as a whole, with increased efficiency and productivity. As user expectations for connection reliability, processing power, data speeds, and device battery life increase, wireless network technology must keep pace with such expectations. As a result, there is a continued interest in improving wireless network technology. Summary of the invention

[0003] In one aspect of the present disclosure, a method includes: establishing, by a vehicle relay user equipment (VMR-UE), a protocol data unit (PDU) session with a core network to which the VMR-UE is subscribed; and sending to the core network an indication that the PDU session is used for at least one of the following items: an interface control message of a vehicle relay network node (VMR-NN) installed in a vehicle together with the VMR-UE, a user plane (UP) service for at least one second UE connected to the VMR-NN, or a control plane (CP) service for at least one second UE connected to the VMR-NN.

[0004] In one aspect of the method, sending the indication may include sending an indication of an interface control message of the PDU session for the VMR-NN.

[0005] In one aspect of the method, the method may further include: receiving an interface control message from the VMR-NN; and sending the interface control message as an application payload of the VMR-UE through the PDU session.

[0006] In one aspect of the method, sending the interface control message may include sending the interface control message using an identifier parameter of the VMR-NN.

[0007] In one aspect of the method, establishing a PDU session with a core network may include receiving an uplink (UL) quality of service (QoS) rule from a session management function (SMF) of the core network, the UL QoS rule being configured to detect an interface control message of the VMR-NN.

[0008] In one aspect of the method, the method may further include: receiving, by the VMR-UE, an interface control message response from the core network through the PDU session; and sending, by the VMR-UE, an interface control message response to the VMR-NN.

[0009] In one aspect of the method, the method may also include: receiving, by the VMR-UE from the VMR-NN, at least one registration request for at least one second UE to register with an access and mobility management function (AMF); and sending, by the VMR-UE through a PDU session, at least one registration request for at least one second UE.

[0010] In one aspect of the method, the method may also include receiving, by the VMR-UE, PDU session resource establishment information provided by a session management function (SMF) from the core network through the PDU session, wherein the PDU session resource establishment information is configured to enable at least one second UE to establish a PDU session with a user plane function (UPF) for at least one second UE.

[0011] In one aspect of the method, the method may also include: the VMR-UE receives the following instructions from the VMR-NN: establishing a second PDU session with the core network for at least one of the UP services of at least one second UE or the CP services of at least one second UE; establishing a second PDU session with the core network, wherein the second PDU session is different from the PDU session of the interface control message of the VMR-NN; and sending the following indication to the core network: the second PDU session is used for at least one of the UP services or CP services of at least one second UE.

[0012] In one aspect of the method, the method may also include: receiving at least one item of UP data of at least one second UE or CP data of at least one second UE from the VMR-NN; and sending at least one item of UP data of at least one second UE or CP data of at least one second UE to the core network through a second PDU session.

[0013] In one aspect of the method, receiving at least one of UP data of at least one second UE or CP data of at least one second UE may include receiving a General Packet Radio Service Tunneling Protocol (GTP) encapsulated application payload including at least one of UP data of at least one second UE or CP data of at least one second UE. Sending at least one of UP data or CP data of at least one second UE may include sending a GTP encapsulated application payload including at least one of UP data or CP data of at least one second UE to the core network through a second PDU session.

[0014] In one aspect of the method, the method may further include: receiving, by the VMR-UE, application data for at least one second UE from the core network through the second PDU session; and sending the application data for the at least one second UE to the VMR-NN.

[0015] In one aspect of the method, receiving application data for at least one second UE may include receiving a General Packet Radio Service Tunneling Protocol (GTP) encapsulated application payload including application data for at least one second UE. Sending application data for at least one second UE may include sending a GTP encapsulated application payload including application data for at least one second UE.

[0016] According to various aspects of the present disclosure, a user equipment includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, causes the user equipment to at least perform any one of the aforementioned methods.

[0017] According to various aspects of the present disclosure, a method includes: establishing, by at least one component of a core network, a protocol data unit (PDU) session with a vehicle relay user equipment (VMR-UE) subscribed to the core network; and receiving, from the VMR-UE, an indication that the PDU session is used for at least one of the following items: an interface control message of a vehicle relay network node (VMR-NN) installed in a vehicle together with the VMR-UE, a user plane (UP) service of at least one second UE connected to the VMR-NN, or a control plane (CP) service of at least one second UE connected to the VMR-NN.

[0018] In one aspect of the method, receiving the indication may include receiving an indication of an interface control message for the VMR-NN that the PDU session is used.

[0019] In one aspect of the method, the method may further include: receiving an application payload of the VMR-UE from the VMR-UE through the PDU session, the application payload of the VMR-UE including an interface control message of the VMR-NN.

[0020] In one aspect of the method, the interface control message of the VMR-NN received from the VMR-UE may include an identifier parameter of the VMR-NN.

[0021] In one aspect of the method, the method may also include: configuring, by a session management function (SMF) of at least one component of the core network, an uplink (UL) quality of service (QoS) rule, the UL QoS rule being configured for detecting an interface control message of the VMR-NN; and sending the UL QoS rule to the VMR-UE for the VMR-UE to use for detecting the interface control message of the VMR-NN.

[0022] In one aspect of the method, the configuration of the UL QoS rules may be based on at least one of: an identifier parameter of the VMR-NN, or an identifier parameter of an Access and Mobility Management Function (AMF) for the VMR-NN.

[0023] In one aspect of the method, the method may also include: obtaining at least one of the following items from at least one of: a unified data management (UDM) session management (SM) subscription for the VMR-UE; a local configuration of the SMF; or a policy control function (PCF) policy for the VMR-UE: an identifier parameter of the VMR-NN; or an identifier parameter of the AMF for the VMR-NN.

[0024] In one aspect of the method, the method may further include: receiving at least one of the following items from the VMR-UE during establishment of the PDU session: an identifier parameter of the VMR-NN, or an identifier parameter of the AMF for the VMR-NN.

[0025] In one aspect of the method, the method may also include: configuring a packet detection rule (PDR) and a forwarding action rule (FAR) to a user plane function (UPF) by a session management function (SMF) of at least one component of the core network, the PDR and the FAR being configured to detect packets and forward packets to the AMF of the VMR-NN, wherein the packet includes a destination address set to the address of the access and mobility management function (AMF) of the VMR-NN.

[0026] In one aspect of the method, the method may also include: a session management function (SMF) of at least one component of the core network configuring a packet detection rule (PDR) and a forwarding action rule (FAR) to a user plane function (UPF), the PDR and the FAR being configured to detect packets including a source address and forward packets including the source address, the source address being set to the address of the AMF for the VMR-NN and being mapped to a packet forwarding control protocol (PFCP) session.

[0027] In one aspect of the method, the method may also include: receiving a message from an access and mobility management function (AMF) of the VMR-NN by a user plane function (UPF) of at least one component of the core network; and generating a general packet radio service tunneling protocol (GTP) encapsulation message based on the message from the AMF for the VMR-NN.

[0028] In one aspect of the method, the method may further include receiving, from the VMR-UE through the PDU session, at least one registration request for at least one second UE to register with an access and mobility management function (AMF) for at least one second UE.

[0029] In one aspect of the method, the method may also include: selecting, by the AMF for at least one second UE, a session management function (SMF) for at least one second UE.

[0030] In one aspect of the method, the method may also include: sending PDU session resource establishment information by the SMF for at least one second UE through the PDU session, and the PDU session resource establishment information is configured to enable at least one second UE and a user plane function (UPF) for at least one second UE to establish a PDU session.

[0031] In one aspect of the method, the method may also include: establishing a second PDU session with the VMR-UE, wherein the second PDU session is different from the PDU session of the interface control message of the VMR-NN; and receiving the following indication from the VMR-UE: the second PDU session is used for at least one of the UP service of at least one second UE or the CP service of at least one second UE.

[0032] In one aspect of the method, the method may also include: configuring, by a session management function (SMF) of the VMR-UE, a user plane function (UPF) for the VMR-UE, at least one of the following items: a packet detection rule (PDR) and a forwarding action rule (FAR) configured to detect and forward uplink packets including a destination IP address set to the IP address of the UPF for at least one second UE, or a PDR and a FAR configured to detect and forward downlink packets including a source address set to the address of the UPF for at least one second UE.

[0033] In one aspect of the method, the PDR and FAR are configured to detect and forward packets to an intermediate data network (DN), wherein the intermediate DN is a service chain or forwarding DN configured to forward packets to a UPF for at least one second UE.

[0034] In one aspect of the method, the method may also include: configuring, by the SMF for at least one second UE, to the UPF for at least one second UE, at least one of the following items: a packet detection rule (PDR) and a forwarding action rule (FAR) configured to detect and forward uplink packets including a destination address set to the address of the UPF for at least one second UE, or a PDR and a FAR configured to detect and forward downlink packets including a source address set to the address of an application server.

[0035] In one aspect of the method, the method may also include: receiving, by a user plane function (UPF) for the VMR-UE, at least one item of UP data or CP data of at least one second UE from the VMR-UE through a second PDU session; and forwarding, by the UPF for the VMR-UE, at least one item of UP data of at least one second UE or CP data of at least one second UE.

[0036] In one aspect of the method, forwarding at least one item of UP data or CP data of at least one second UE may include: forwarding at least one item of UP data or CP data by the VMR-UE to an intermediate data network (DN), wherein the intermediate DN is a service chain or forwarding DN configured to forward at least one item of UP data or CP data of at least one second UE to a UPF for at least one second UE.

[0037] In one aspect of the method, forwarding at least one of UP data of at least one second UE or CP data of at least one second UE may include: forwarding at least one of the UP data or CP data to the UPF for at least one second UE using IP forwarding via the N6 interface by the UPF for the VMR-UE.

[0038] In one aspect of the method, the UPF for the VMR-UE is also the UPF for at least one second UE, wherein forwarding at least one of the UP data or CP data of the at least one second UE includes forwarding at least one of the UP data or CP data to the virtual internal port by the UPF for the VMR-UE before forwarding at N6.

[0039] In one aspect of the method, the method may further include: receiving, by the UPF for the VMR-UE, application data of at least one second UE; and sending the application data of the at least one second UE to the VMR-UE through the second PDU session.

[0040] According to various aspects of the present disclosure, a user equipment includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, causes the user equipment to at least perform any one of the aforementioned methods.

[0041] According to some aspects, the subject matter of the independent claims is provided. Some further aspects are defined in the dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Some example embodiments will now be described with reference to the accompanying drawings.

[0043] Figure 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment device (UE) according to one illustrative aspect of the present disclosure;

[0044] Figure 2 is a diagram of example components of a network system according to one illustrative aspect of the present disclosure;

[0045] Figure 3 is a diagram of an example wireless system including a vehicle-mounted relay according to one illustrative aspect of the present disclosure;

[0046] Figure 4 According to an illustrative aspect of the present disclosure Figure 3 A diagram of an example interaction of a wireless system;

[0047] Figure 5 is a diagram of example signals and operations of a network system including an onboard relay according to one illustrative aspect of the present disclosure;

[0048] Figure 6 is a diagram of another example of signals and operations of a network system including an onboard relay according to one illustrative aspect of the present disclosure;

[0049] Figure 7 According to an illustrative aspect of the present disclosure Figure 3 A diagram of an example interaction of a wireless system of FIG. 1 ; and

[0050] Figure 8 is a diagram of an example embodiment of components of a UE or network device according to one illustrative aspect of the present disclosure. DETAILED DESCRIPTION

[0051] In the following description, certain specific details are set forth in order to provide a thorough understanding of the disclosed aspects. However, one skilled in the relevant art will recognize that the various aspects may be practiced without one or more of these specific details or using other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers are not shown or described in detail to avoid unnecessarily obscuring the description of the various aspects.

[0052] In this specification, reference to "one aspect" or "an aspect" indicates that a particular feature, structure, or characteristic described in connection with that aspect is included in at least one aspect. Thus, the appearance of the phrase "in one aspect" or "in an aspect" in various places in this specification does not necessarily refer to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0053] The embodiments described in the present disclosure may be implemented in wireless network devices, such as, but not limited to, devices utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System (UMTS, 3G) based on basic Wideband Code Division Multiple Access (W-CDMA), High Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE, Enhanced LTE (eLTE), 5G New Radio (5GNR), Advanced 5G, 6G (and beyond), and 802.11ax (Wi-Fi 6), as well as other wireless network systems. The term "eLTE" herein refers to LTE evolution connected to a 5G core. LTE is also known as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN).

[0054] The present disclosure may use the term "serving network device" to refer to a network node or network apparatus (or a portion thereof) that serves a UE. As used herein, the terms "send to," "receive from," and "cooperate with" (and variations thereof) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term "acquire" (and variations thereof) includes first acquiring or reacquiring after a first acquisition. The term "connect" may refer to a physical connection or a logical connection.

[0055] As used herein, the term "device" refers to and includes a physical implementation, which may include one housing and / or components, or may include more than one housing and / or components. In the case of more than one housing and / or components, the multiple housings and / or components of the device may be juxtaposed or geographically separated.

[0056] The present disclosure uses 5G NR as an example of a wireless network, and may use a smartphone as an example of a UE. It should be understood that these examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment devices.

[0057] Figure 11 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment device (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network devices 130 (e.g., test equipment). The network node 120 will be described in more detail below. As used herein, the term "network device" may refer to any component of the network system 100, such as a server 110, a network node 120, a network device 130, any (multiple) components of the above, and / or any other (multiple) components of the network system 100. Examples of network devices include, but are not limited to, devices that implement various aspects of 5G NR, etc. The present disclosure describes embodiments related to 5G NR and embodiments involving various aspects defined by the Third Generation Partnership Project (3GPP). However, it is contemplated that embodiments related to other wireless network technologies are also included within the scope of the present disclosure.

[0058] The following description provides further details of an example of a network node. In a 5G NR network, a gNodeB (also referred to as a gNB) may include, for example, a node that provides NR user plane and control plane protocol terminations towards the UE and is connected to the 5G Core (5GC) via an NG interface, for example in accordance with 3GPP TS 38.300 V16.6.0 (2021-06) Section 3.2, which is incorporated herein by reference.

[0059] The gNB supports various protocol layers, such as Layer 1 (L1) (ie, physical layer), Layer 2 (L2), and Layer 3 (L3).

[0060] NR’s Layer 2 (L2) is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), where for example:

[0061] ○The physical layer provides the transport channel to the MAC sublayer;

[0062] ○The MAC sublayer provides logical channels to the RLC sublayer;

[0063] ○ The RLC sublayer provides RLC channels to the PDCP sublayer;

[0064] ○ The PDCP sublayer provides radio bearer to the SDAP sublayer;

[0065] ○The SDAP sublayer provides Quality of Service (QoS) flows to 5GC;

[0066] o Control channels include the Broadcast Control Channel (BCCH) and the Physical Control Channel (PCCH).

[0067] Layer 3 (L3) includes, for example, Radio Resource Control (RRC) in accordance with Section 6 of 3GPP TS 38.300 V16.6.0 (2021-06), which is incorporated herein by reference.

[0068] The gNB Central Unit (gNB-CU) includes, for example, a logical node that hosts, for example, the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP) and Packet Data Convergence Protocol (PDCP) protocols of the gNB, or the RRC and PDCP protocols of the en-gNB, which controls the operation of one or more gNB Distributed Units (gNB-DUs). The gNB-CU terminates the F1 interface connected to the gNB-DU. The gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0069] The gNB distributed unit (gNB-DU) includes logical nodes such as hosting the radio link control (RLC), media access control (MAC) and physical (PHY) layers of, for example, a gNB or en-gNB, and its operation is controlled in part by the gNB-CU. One gNB-DU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. The gNB-DU may also be referred to as DU or distributed unit in this article.

[0070] As used herein, the term "network node" may refer to any one of a gNB, a gNB-CU or a gNB-DU, or any combination thereof. A RAN (Radio Access Network) node or a network node (such as, for example, a gNB, a gNB-CU or a gNB-DU, or a portion thereof) may be implemented using, for example, a device having at least one processor and / or at least one memory having processor-readable instructions ("program") configured to support and / or provision and / or process CU and / or DU related functions and / or features, and / or at least one protocol (sub) layer of a RAN (Radio Access Network), such as Layer 2 and / or Layer 3. There may be different functional splits between central and distributed units.

[0071] For example, the gNB-CU and gNB-DU components may be co-located or physically separated. The gNB-DU may be even further split into two parts, for example, one part including a processing device and the other including an antenna. The central unit (CU) may also be referred to as a baseband unit / radio equipment controller / cloud RAN / virtual RAN (BBU / REC / C-RAN / V-RAN), an open RAN (O-RAN) or a portion thereof. The distributed unit (DU) may also be referred to as a remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU) or a portion thereof. Hereinafter, in various example embodiments of the present disclosure, a network node supporting at least one of a central unit function or a layer 3 protocol of a radio access network may be, for example, a gNB-CU. Similarly, a network node supporting at least one of a distributed unit function or a layer 2 protocol of a radio access network may be, for example, a gNB-DU.

[0072] A gNB-CU may support one or more gNB-DUs. A gNB-DU may support one or more cells and may therefore support a serving cell for a user equipment device (UE) or a candidate cell for procedures such as handover, dual connectivity and / or carrier aggregation.

[0073] The user equipment device (UE) 150 may be or include a wireless or mobile device, a device having a radio interface for interacting with a RAN (Radio Access Network), a smartphone, a vehicle-mounted device, an IoT device or an M2M device, and other types of user equipment. Such a UE 150 may include: at least one processor; and at least one memory including program code; wherein the at least one memory and the computer program code are configured to cause the device to perform at least certain operations together with the at least one processor, such as, for example, an RRC connection with a RAN. Examples of components of the UE will be combined with Figure 6 In an embodiment, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be sent to the RAN via the radio (e.g., to reach and communicate with a serving cell). In an embodiment, the UE 150 may generate and send and receive an RRC message containing one or more RRC PDUs (protocol data units). Those skilled in the art will understand the RRC protocol and other processes that the UE may perform.

[0074] Continue to refer Figure 1In the example of a 5G NR network, the network system 100 provides one or more cells that define a coverage area of ​​the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network, or may include any other device configured to control radio communications and manage radio resources within a cell. As used herein, the term "resource" may refer to radio resources, such as resource blocks (RBs), physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. In an embodiment, the network node 120 may be referred to as a base station.

[0075] Figure 1 An example is provided and is only used to illustrate the network system 100 and the UE 150. Those skilled in the art will appreciate that the network system 100 includes Figure 1 Components not shown, and it will be understood that other user equipment devices may communicate with the network system 100.

[0076] Figure 2 yes Figure 1 A 5G NR network may be described as an example of a network system 100, and aspects described below should also be applicable to other types of network systems. The network system may be based on Figure 1 The signals and connections shown are operated so that the UE 150 communicates with the network system 100 through the radio access network 225. In addition, as shown and described herein, the network system can be divided into user plane components and functions and control plane components and functions. Unless otherwise specified, the terms "component", "function" and "service" are used interchangeably herein, and they may refer to instructions executed by one or more processors and implemented by them.

[0077] The following describes example functions of the components. The example functions are illustrative only, and it should be understood that the components described herein may perform other operations and functions. In addition, the connections between components may be virtual connections based on service interfaces, so that any component may communicate with any other component. In this way, any component may act as a service "producer" for any other component (which is a service "consumer") to provide services for network functions.

[0078] For example, a core network 210 is described in the control plane of the network system. The core network 210 includes an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SMF) 213. The core network 210 also includes a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a unified data repository (UDR) 224.

[0079] Additional components and functions of the core network 210 include an application function (AF) 218 ​​, a policy control function (PCF) 219 , a network data analysis function (NWDAF) 220 , an analysis data repository function (ADRF) 221 , a management data analysis function (MDAF) 222 , and an operation and management function (OAM) 223 .

[0080] The user plane includes UE 150, radio access network (RAN) 225, user plane function (UPF) 226, and data network (DN) 227. RAN 225 may include a combination of Figure 1 The RAN 225 may include one or more components such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides a connection for data sent through the RAN 225. For example, the DN 226 identifies services from a service provider, Internet access, and third-party services.

[0081] AMF 212 handles connection and mobility tasks. AUSF 211 receives authentication requests from AMF 212 and interacts with UDM 217 to authenticate and verify network responses to determine successful authentication. SMF 213 performs protocol data unit (PDU) session management and manages session context with UPF 226.

[0082] NSSF 214 may select a network slice instance (NSI) and determine allowed network slice selection assistance information (NSSAI). This selection and determination is used to set up AMF 212 to provide services to UE 150. NEF 215 ensures third-party access to network services to create specialized network services. NRF 216 acts as a repository for storing network functions to allow these functions to register and discover each other.

[0083] UDM 217 generates authentication vectors for use by AUSF 211 and ADM 212, and provides user identification processing. UDM 217 can be connected to UDR 224, which stores data related to authentication, applications, etc. AF 218 provides application services (e.g., streaming services, etc.) to users. PCF 219 provides policy control functions. For example, PCF 219 can assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functions.

[0084] NWDAF 220 collects data (e.g., from UE 150 and network systems) to perform network analysis and provide insights into functions that utilize analysis when providing services. ADRF 221 allows consumers to store, retrieve, and remove data and analysis. MDAF 222 provides additional data analysis services for network functions. OAM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0085] Figure 2 These are merely examples of components of a network system, and variations are considered to be within the scope of the present disclosure. In an embodiment, a network system may include Figure 2 In an embodiment, the network system may not include other components not shown. Figure 2 In an embodiment, these components and connections can be used with Figure 2 Such and other embodiments are considered to be within the scope of the present disclosure.

[0086] An example of a wireless system with a vehicle-mounted relay will be described below. In order to extend the coverage of a wireless network, it is proposed to use a so-called vehicle-mounted relay (VMR). A VMR refers to a base station that will be installed on a vehicle and will therefore have a wireless connection as a backhaul connection.

[0087] In 3GPP Release 18, a study was conducted and then a work item on VMR. During the study, it was agreed that the scope of the work would be limited to the IAB (Integrated Access and Backhaul) architecture.

[0088] IAB leverages the spectral efficiency of New Radio and the greater capacity provided by the higher frequency bands available in 5G to provide an alternative to optical cell site backhaul. This alleviates one of the main issues surrounding 5G deployments and can be used as a short-term replacement for fiber or as a permanent option for more isolated antennas or antennas without right-of-way access. IAB allows multi-hop backhaul using the same frequency used for user equipment (UE) access or using different dedicated frequencies.

[0089] The Integrated Access and Backhaul specification defines two types of antenna systems: IAB Nodes and IAB Donors. IAB Donors terminate backhaul traffic from distributed IAB Nodes. These nodes can be backhaul endpoints or relays between these endpoints and the Donor. Both IAB Donors and Nodes serve mobile UEs in the usual way.

[0090] IAB requires a decomposed radio access network (RAN) model that decouples the distributed unit (DU) from the central unit (CU). The DU exists only in the IAB node, while the donor system also includes the CU. A single IAB system, defined in the standard as including the CU and DU, one or more IAB nodes, and the IAB donor are considered as a single gNB. This approach also ensures that the backhaul is isolated within the topology constraints, so routing changes or problems do not propagate to the 5GC or other neighboring gNBs.

[0091] However, there are some limitations to consider when using the IAB concept as a basis for VMR. For example, the approach is not flexible enough because the UE always needs a donor gNB in ​​order to become a VMR node. In addition, both the mobile IAB and the gNB donor node should be configured with Backhaul Adaptation Protocol (BAP) layer support. This can be a limitation for UE vendors / manufacturers. In addition, operators must deploy / upgrade all gNBs with donor functionality in the Public Land Mobile Network (PLMN) to provide seamless VMR functionality, which is not feasible in all deployment scenarios.

[0092] Due to the above mentioned limitations, alternative methods have been considered. One of these methods is the so called "Velcro" system. Figure 3 A diagram illustrating an example of a wireless system including a Velcro architecture is shown.

[0093] Typically, in a Velcro-based VMR architecture, the relay node includes a UE collocated with a full gNB, and the gNB in ​​the relay establishes N2 and N3 interfaces with the AMF residing in the core network through a PDU session established with the PLMN for the VMR-UE. With this approach, some of the above-mentioned problems can be overcome so that it does not require a donor gNB, and the existing stack can be reused without major changes, etc. That is, the Velcro architecture includes a full gNB to provide connectivity for the UE, where this full (VMR-)gNB builds an entity together with the (VMR-)UE connected to other "normal" gNBs for backhaul connectivity.

[0094] Reference numeral 10 denotes one or more UEs, which may be referred to as "remote UEs", i.e., UEs connected to the VMR. For convenience, one or more remote UEs 10 may be simply referred to as UE 10. Any description involving UE 10 should be deemed to also involve one or more UEs 10.

[0095] Reference numeral 20 denotes a VMR. Reference numeral 23 denotes a VMR network node VMR-NN (e.g., gNB), via which the UE 10 can access the PLMN-A. The VMR-UE 25 is connected to the PLMN-A for the backhaul connection of the VMR gNB 23.

[0096] Reference numeral 30 denotes PLMN-A, i.e., the network of the VMR-UE 25. The PLMN-A 30 includes RAN elements and the like such as a network node 31 (e.g., gNB) for connection to the VMR-UE 25 and a core network portion such as an AMF 32 representing a communication network control element or function of the 5GC. AMF 32 is a control plane function within 5GC and performs, for example, registration management (e.g., allowing UE (e.g., 25) to register / deregister with the 5G system, where AMF 32 interacts with other network functions during the registration process), connection management (establishing and releasing control plane signaling connections between UE (e.g., 25) and AMF 32, NAS messages to be exchanged between UE (e.g., 25) and AMF 32, NAS signaling procedures for registration, authentication, service request and identity request), reachability management (by storing location information as part of the UE context, which includes the registration area (tracking area or tracking area list) in which the UE is registered), and mobility management (keeping knowledge of the UE's location in the network, the UE performs registration updates periodically after initial registration and updates due to mobility, for example, if it moves out of the currently registered tracking area or tracking area list). AMF 32 is connected to SMF 34, which is responsible for interacting with the decoupled data plane, creating, updating and removing protocol data unit (PDU) sessions, and managing session contexts with UPF 33. The UPF is denoted by reference numeral 33 and is part of the control method that splits control and user data. The UPF is responsible for RAN / data network interconnection, packet inspection and application detection, packet routing and data forwarding, and QoS management and usage reporting.

[0097] As described above, the VMR-UE 25 provides a backhaul connection via the PLMN-A 30 by using the air interface of the VMR-NN 23 (see arrow).

[0098] However, in this case, it must be clarified how to make the Velcro architecture usable for VMR systems. Specifically, for example, it must be defined how the VMR-gNB configuration works (e.g., the transmission of non-UE related data / interface control data to and from the respective wireless networks involved). In addition, how UE related data transmission works (e.g., for UE user plane and / or control plane data) will also be defined.

[0099] In order to find a solution to the above points, the following scenario can also be considered, in which the UE 10 and the VMR-NN 23 on one side and the VMR-UE 25 on the other side do not use the same PLMN for the backhaul connection. That is, the UE 10 comes from, for example, PLMN B and is communicating with the VMR-NN 23 via this PLMN B. However, the corresponding collocated VMR-UE 25 that establishes the backhaul connection for the VMR-NN 23 comes from PLMN-A (and is connected to this PLMN-A 30). This situation is a valid and even possible use case, because the VMR-NN 23 can provide services for more than one PLMN. Specifically, in the VMR scenario, these VMR-NNs 23 can, for example, be deployed as shared gNBs to provide services for PLMN-A, PLMN-B, PLMN-C, etc., so as to be able to provide services to any UE of any PLMN.

[0100] That is, when a VMR system with the above method is adopted, it should be clarified how to establish a connection from the VMR-NN and how to establish a connection from a remote UE connected to the VMR-NN when the corresponding collocated VMR-UE is usually connected to the PLMN-A via a traditional PDU session. In addition, according to an example of an embodiment, a mechanism is proposed that allows configuration and use of VMR-based communications, wherein a VMR base station can be shared between multiple communication networks, i.e., multiple operator networks such as different PLMNs.

[0101] In the following, different examples of the embodiment will be described to illustrate the processing of the control process in a wireless network that allows VMR-based communication. To this end, as an example of a wireless network to which the example of the embodiment can be applied, a communication network architecture based on the 3GPP standard, such as 5G NR, is used without limiting the present disclosure to such an architecture. It will be clear to those skilled in the art that the example of the embodiment can also be applied to other types of wireless networks, such as Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), Personal Communications Service (PCS), Wideband Code Division Multiple Access (WCDMA), systems using Ultra Wideband (UWB) technology, mobile ad hoc networks (MANET), etc. In addition, without loss of generality, the description of some examples of the embodiments is related to mobile communication networks, but the principles described herein can also be extended and applied to any other type of network, such as a wired communication network.

[0102] The general functions and interconnections of the above elements and functions (which also depend on the actual network type) are understandable to those skilled in the art and are described in the corresponding specifications, so their detailed description is omitted here. However, it should be noted that in addition to those described in detail below, several additional network elements and signaling links may be used to communicate with elements, functions or applications (such as communication endpoints, communication network control elements (such as servers, gateways, radio network controllers) and other elements of the same or other communication networks).

[0103] The communication network architecture considered in the example of the embodiment may also be able to communicate with other networks (such as the public switched telephone network or the Internet) and with individual devices or groups of devices that are not considered to be part of the network (such as monitoring devices, such as cameras, sensors, sensor arrays, etc.). The communication network may also be able to support cloud services for virtual network elements or their functions, where it should be noted that the virtual network part of the telecommunications network may also be provided by non-cloud resources, such as internal networks, etc. It should be understood that the network elements of the access system, core network, etc., and / or the corresponding functions may be implemented using any node, host, server, access node or entity, etc. suitable for such purpose. In general, the network functions may be implemented as network elements on dedicated hardware, software instances running on dedicated hardware, or virtualized functions instantiated on an appropriate platform (e.g., cloud infrastructure).

[0104] Usually, reference Figure 4 According to an example of an embodiment, in a first stage, the VMR-UE 25 creates one or more PDU sessions 405 to its own network (i.e., PLMN-A 30). The VMR-NN 23 and / or the remote UE 10 can then access the network through the one or more PDU sessions 405 using the application stack of the VMR-UE 10. For example, a PDU session represents a data path between the VMR-UE 25 and the core network of the PLMN-A 30, and represents a logical connection between the VMR-UE 25 and a data network (DN) such as the Internet or a private network. Examples of data networks are as follows: Figure 4As shown, it includes a control plane DN 410, a user plane DN 420 and an application DN 430. A PDU session is generally used to carry user data and can support different types of services, such as voice, video and data. For example, PDU session establishment is initiated by issuing a request to the core network (e.g., 5G CN). The request includes information about the type of service and the type of business that the UE wants to use. After the PDU session is established, the VMR-UE 25 can use it to send and receive data. The 5G CN manages the resources used by the PDU session to ensure that the network is used efficiently and that the VMR-UE 25 receives appropriate quality of service ("QoS"). Those skilled in the art will understand that a PDU session involves Figure 4 Various aspects not shown in the PDU session, such as one or more data radio bearers ("DRBs"), one or more F1-U tunnels, N3 tunnels, one or more QoS flows and tunnel endpoint identifiers ("TEIDs"), etc. Those skilled in the art will understand such aspects of the PDU session.

[0105] According to aspects of the present disclosure, the VMR-UE 25 may establish one or more PDU sessions to carry data (e.g., control plane ("C-plane") data, user plane ("U-plane") data, interface control messages, signaling, etc.) from the VMR-NN 23 and / or from the remote UE 10 as application layer payloads on the PDU session(s) 405 for the VMR-UE. The PDU session(s) 405 may also carry the VMR-UE's own user plane data. In various embodiments, a separate PDU session 405 may carry the following as application payloads: (a) interface control messages of the VMR-NN, (b) control plane / user plane data of one or more remote UEs, and (c) the VMR-UE's own user plane data. For example, a first PDU session may carry (a) interface control messages of the VMR-NN, a second PDU session may carry (b) control plane / user plane data of one or more remote UEs, and a third PDU session may carry (c) the VMR-UE's own user plane data. In various embodiments, a single PDU session may carry (a) and (b), while a separate PDU session may carry (c). In various embodiments, a single PDU session may carry all of (a), (b), and (c). In various embodiments, a separate PDU session may carry control plane data for a remote UE and user plane data for a remote UE. Other implementations of PDU sessions for carrying various data are possible and are considered to be within the scope of the present disclosure.

[0106] exist Figure 4In the figure, lines and arrows represent communication connections between devices or components, which can be logical connections and / or physical connections. The connection between the VMR-NN and the VMR-UE can be any type of connection, such as a logical connection or a physical connection (wired or wireless). As an example of a logical connection, the VMR-NN can be implemented as application software in the VMR-UE. Figure 5 and Figure 6 Describes the various communications between devices and components in more detail.

[0107] Figure 4 This is illustrative only, and variations are considered to be within the scope of the present disclosure. In an embodiment, one may include Figure 4 Other devices, components and communications not shown in the figure. In an embodiment, it may not include Figure 4 All devices, components and communications shown. In an embodiment, the devices, components and communications can be Figure 4 Such and other embodiments are considered to be within the scope of the present disclosure.

[0108] Figure 5 yes Figure 4 FIGURE 1 is a diagram of example signals and operations of a system for VMR-NN to send interface control messages to a wireless network and receive interface control messages from a wireless network. The following paragraphs will describe various signals and operations. It should be understood that the described signals may have associated operations, and the described operations may have associated signals. Therefore, the described signals may also involve operations, and the described operations may also involve signals. In addition, Figure 5 The signals between various systems, devices, and components and the operations performed by them will be described, such as Figure 5 Those shown at the top of Figure 4 Specifically, the systems, devices, and components include a VMR-NN, a VMR-UE, a radio access network (RAN) (e.g., a gNB), a session management function (SMF) for the VMR-UE, a user plane function (UPF) for the VMR-UE, and an access and mobility management function (AMF) 32 for the VMR-UE. The systems, devices, and components are illustrative, and it is contemplated that other devices and components (such as those in combination with Figure 1 and Figure 2 Those shown or described) may be involved in a signal or may perform an operation.

[0109] At operation 510, the VMR-UE registers with its core network and establishes a PDU session (e.g., Figure 4405 in). The VMR-UE sends an indication to the core network that the PDU session is used to carry the interface control message of the VMR-NN, and the core network receives the indication from the VMR-UE. The interface control message is used by the VMR-NN to establish and configure the VMR-NN. In various embodiments, the interface control message of the VMR-NN may include one or more of the following: control plane message, NGSetup, RAN configuration update, AMF configuration update, NG reset, error indication, AMF status indication and / or overload indication, and other messages that will be recognized by those skilled in the art. The interface control message of the VMR-NN can be carried on the PDU session as an application payload of the VMR-UE, which will be described in more detail below.

[0110] Since the VMR-UE will have its own application data, various components of the VMR-UE may need to distinguish between application data from / for the VMR-UE and from / for the VMR-NN. In the uplink direction, application data from the VMR-UE will include an identifier parameter value of the VMR-UE (e.g., the IP address of the VMR-UE), and application data from the VMR-NN will include an identifier parameter value of the VMR-NN (e.g., the IP address of the VMR-NN). The SMF for the VMR-UE may configure an uplink (UL) QoS rule for application packet detection at the VMR-UE in such a way that the VMR-UE will use the identifier parameter value of the VMR-NN (e.g., the IP address of the VMR-NN) to send the application data of the VMR-NN using the PDU session for the VMR-UE.

[0111] In various embodiments, UL QoS rules may be supplied by the SMF during PDU session establishment for the VMR-UE.

[0112] In various embodiments, the identifier parameter (eg, IP address / prefix and / or frame route) value may be obtained based on session management (SM) subscription information of the UDM for the VMR-UE or based on local configuration of the SMF.

[0113] In various embodiments, the identifier parameter value may be obtained by receiving an identifier parameter value of the VMR-NN (e.g., the IP address of the VMR-NN) and / or an identifier parameter value of the AMF of the VMR-NN (e.g., the IP address) from the VMR-UE during PDU session establishment.

[0114] In various embodiments, the identifier parameter value may be obtained based on a Policy Control Function (PCF) policy for the VMR-UE, which PCF policy provides a predefined identifier parameter value of the AMF and VMR-NN (eg, the IP address of the VMR-NN) in the session management policy.

[0115] At operation 520, the SMF for the VMR-UE configures the UPF for the VMR-UE with a packet detection rule (PDR) for detecting VMR related packets and a forwarding action rule (FAR) for forwarding VMR related packets to the AMF for the UE. The PDR / FAR may be configured via a packet forwarding control protocol (PFCP) association establishment or modification.

[0116] In various embodiments, the UPF for the VMR-UE may be configured to forward uplink packets to the AMF of the VMR-NN, where the destination address (e.g., IP address) is set to the address (e.g., IP address) of the AMF.

[0117] In various embodiments, the UPF for the VMR-UE may be configured to forward downlink packets from the AMF of the VMR-NN, for which packets the source address (e.g., IP address) is mapped to a specific PFCP session to identify the PDU binding.

[0118] In various embodiments, the PDR and FAR used to detect and forward packets from the VMR-NN may have the following parameters as will be appreciated by those skilled in the art.

[0119]

[0120]

[0121] At operation 530, the VMR-NN transmits an interface control message to the VMR-UE as application data for the VMR-UE, and the VMR-UE receives the interface control message from the VMR-NN.

[0122] At operation 540, the VMR-UE sends an interface control message as an application payload to the RAN through the PDU session, and the RAN receives the interface control message / application payload from the VMR-UE. Those skilled in the art will appreciate that the interface control message / application payload is sent in a data radio bearer (DRB), and the VMR-UE will identify the DRB for sending the interface control message or application payload based on the QFI associated with different QoS flows.

[0123] At operation 550, the RAN sends an interface control message / application payload to the UPF for the VMR-UE through the F1-U tunnel and N3 tunnel that conform to the General Packet Radio Service Tunneling Protocol (GTP), which may be referred to as a GTP tunnel in this article. It will be appreciated by those skilled in the art that the RAN (e.g., GNB-DU) encodes the application payload with the GTP header. The UPF for the VMR-UE receives the GTP encapsulated application payload from the RAN.

[0124] At operation 560, the UPF for VMR-UE removes the GTP header from the GTP encapsulated application payload and sends the application payload containing the interface control message of VMR-NN to the AMF. The AMF for VMR-UE receives the application payload from the UPF of VMR-NN (which may be the same as the UPF for VMR-UE), performs operations related to the interface control message, and provides an interface control message response. For example, if the interface control message is a NG setup message, the AMF for VMR-UE may provide an NG setup response.

[0125] At operation 570, the AMF for the VMR-UE sends an interface control message response to the UPF for the VMR-UE, and the UPF for the VMR-NN receives the interface control message response.

[0126] At operation 580, the UPF for the VMR-UE sends an interface control message response to the RAN through the PDU session and the GTP tunnel. The UPF for the VMR-UE identifies the PDU session based on the PDR configured by the SMF for the VMR-UE, and encapsulates the interface control message response in the GTP header based on the FAR configured by the SMF. The RAN receives the GTP encapsulated interface control message response from the UPF of the VMR-NN.

[0127] At operation 590, the RAN removes the GTP header from the GTP encapsulated interface control message response and sends the interface control message response to the VMR-UE via the DRB. The RAN may identify the DRB based on a tunnel endpoint identifier (TEID) and may use a QoS flow identifier ("QFI") to identify a QoS flow within the DRB. Those skilled in the art will understand how to implement TEID and QFI for a PDU session. The VMR-UE receives the interface control message response from the RAN.

[0128] At operation 595, the VMR-UE transmits an interface control message response to the VMR-NN, and the VMR-NN receives the interface control message response from the VMR-UE.

[0129] Therefore, in the manner described above, VMR-NN can be deployed without the wireless system needing to support IAB.

[0130] Figure 5 The signals and operations are illustrative only, and variations are considered to be within the scope of the present disclosure. In an embodiment, the signals and operations may include Figure 5 Other signals and operations not shown in the figure. In an embodiment, the signals and operations may not include Figure 5 In an embodiment, these signals and operations can be used in conjunction with Figure 5 Such and other embodiments are considered to be within the scope of the present disclosure.

[0131] Figure 6 yes Figure 4 FIG. 1 is a diagram of example signals and operations of a system for transmitting data to and receiving data from a wireless network (e.g., to a data network) for one or more remote UEs connected to a VMR-NN. The following paragraphs will describe various signals and operations. It should be understood that the described signals may have associated operations, and the described operations may have associated signals. Therefore, the described signals may also involve operations, and the described operations may also involve signals.

[0132] also, Figure 6 The signals between various systems, devices, and components and the operations performed by them will be described, such as Figure 6 Those shown at the top of Figure 4 Those shown. Specifically, the systems, devices and components include a remote UE, a VMR-NN, a VMR-UE, a radio access network (RAN) (e.g., a gNB), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a service chain or forwarding data network (DN), and an application DN. In various embodiments, the remote UE and the VMR-UE may have different SMFs, UPFs and AMFs. The following paragraphs will refer to network functions for remote UEs and network functions for VMR-UEs respectively, but it should be understood that the described network functions can serve both remote UEs and VMR-UEs. For clarity, each of the SMF, UPF and AMF is referred to in Figure 6 is shown by a single block. Figure 6 The systems, devices, and components shown at the top of are illustrative, and it is contemplated that other devices and components (such as those in combination with Figure 1 and Figure 2 Those shown or described) may be involved in a signal or may perform an operation.

[0133] As noted above, the following description will refer to a remote UE, but it is intended that any description referring to a remote UE be deemed that the description also refers to more than one remote UE.

[0134] Prior to operation 610, the VMR-UE has established a PDU session with the core network in the manner described at operation 510. Therefore, there is a first PDU session for transmitting interface control messages of the VMR-NN. As described below, the first PDU session may also be used for non-access stratum (NAS) signaling of the remote UE towards the AMF of the remote UE.

[0135] The remote UE sends a registration request to register with its core network at operation 610. The remote UE sends the registration request to the VMR-NN, and the VMR-NN receives the registration request from the remote UE.

[0136] At operations 612-616, the operation is performed for Figure 5 The operation 530-595 is performed in the manner described in the first PDU session, wherein the application payload is sent to the core network through the first PDU session, and the response from the core network is received through the first PDU session. The first PDU session is established between the VMR-UE and the UPF for the VMR-UE. However, the UPF for the VMR-UE then sends the registration request to the AMF for the remote UE, which AMF may be the same as or different from the AMF for the VMR-UE.

[0137] Specifically, at operation 612, the application payload includes a registration request for the remote UE, and the response from the core network may be a confirmation that the remote UE has been registered.

[0138] At operation 614, the remote UE sends a request to establish a PDU session. The application payload includes the remote UE's request to establish a PDU session, and at operation 616, the response includes PDU resource establishment information. The PDU resource establishment information can be provided by the SMF for the remote UE, which can be the same as or different from the SMF for the VMR-UE. The PDU resource establishment information can include, for example, GTP TEID information and other possible information. The PDU resource establishment information enables the remote UE to establish a PDU session between the remote UE and the UPF for the remote UE and to establish a GTP tunnel between the VMR-NN and the UPF for the remote UE. However, as described below, the PDU session between the remote UE and the UPF for the remote UE operates on a second PDU session between the VMR-UE and the UPF for the VMR-UE.

[0139] At operation 618, the VMR-NN requests the VMR-UE to establish a second PDU session different from the first PDU session, and the operation is similar to Figure 5Operation 510. The VMR-UE establishes a second PDU session with the UPF for the VMR-UE and indicates to the core network that the PDU session is for data of the remote UE (e.g., control plane data and / or user plane data). After operation 618, the VMR-UE will have two PDU sessions. The interface control message for the VMR-NN indicates the first PDU session and the second PDU session for the data of the remote UE.

[0140] At operation 620, for the second PDU session, the SMF for the VMR-UE configures the UPF for the VMR-UE with a packet detection rule (PDR) for detecting packets of the remote UE and a forwarding action rule (FAR) for forwarding packets of the remote UE. As described below, the UPF for the VMR-UE may forward the packets of the remote UE to the UPF for the remote UE toward one or more data networks.

[0141] In various embodiments, the UPF for the VMR-UE is provided with a PDR with a PDU layer identifier parameter value of the remote UE (e.g., the IP address of the VMR-NN) to detect and map received GTP encapsulated packets for N6 forwarding to a service chain or forwarding DN or another intermediate DN. Such a DN is capable of performing routing based on the destination address (e.g., IP address). The intermediate DN can use the supplied FAR rules to forward the packet to the UPF for the remote UE.

[0142] In various embodiments, the SMF for the remote UE configures the UPF for the remote UE to identify an identifier parameter value of the remote UE (e.g., the remote UE IP address) and / or identify an application DN address of the remote UE (e.g., the DN IP address) to perform N6 forwarding.

[0143] In various embodiments, similar methods may be applied by the remote UE's SMF and / or the VMR-UE's SMF to configure their corresponding UPFs to forward downlink (DL) traffic to the remote UE using the following PDR and FAR parameters, as will be understood by those skilled in the art.

[0144]

[0145]

[0146]

[0147] The following operations 622-638 describe the transmission of uplink application packets from the remote UE to the application DN.

[0148] At operation 622, the remote UE sends an application payload of the application DN of the remote UE to the VMR-NN, and the VMR-NN receives the application payload from the remote UE. Because the remote UE sends the application payload through its PDU session, the transmission is performed through the data radio bearer of the PDU session of the remote UE.

[0149] At operation 624, the VMR-NN encodes the application payload with the GTP header based on the information in the PDU setup information received at operation 616, thereby implementing a GTP tunnel for the PDU session of the remote UE. The VMR-NN sends the GTP encapsulated application payload to the VMR-UE through the GTP tunnel, and the VMR-UE receives the GTP encapsulated application payload from the VMR-UE.

[0150] At operation 626, the VMR-UE identifies an uplink QoS rule for sending the GTP encapsulated application payload via a second PDU session of the VMR-UE. Those skilled in the art will appreciate that the second PDU session includes a QoS flow in the DRB. The uplink QoS rule applies to the QoS flow, which will be appreciated by those skilled in the art.

[0151] At operation 628, the VMR-UE transmits the GTP encapsulated application payload to the RAN through the DRB of the second PDU session of the VMR-UE as an application payload, and the RAN receives the application payload from the VMR-UE.

[0152] At operation 630, the RAN encodes the GTP encapsulated application payload (from operation 624) with the GTP header of the GTP tunnel of the second PDU session of the VMR-UE. The RAN provides the GTP encapsulated application payload twice. The RAN sends the GTP encapsulated application payload twice for the second PDU session to the UPF for the VMR-UE through the GTP tunnel, and the UPF of the VMR-UE receives the GTP encapsulated application payload twice.

[0153] At operation 632, the UPF for VMR-UE removes the GTP header of the second PDU session from the two GTP encapsulated application payloads and forwards the GTP encapsulated application payloads. The UPF for VMR-UE can forward in three ways.

[0154] In the first approach, the UPF for the VMR-UE can forward the GTP encapsulated application payload to an intermediate DN, such as a service chain or forwarding DN or an IP router. The intermediate DN can then forward the GTP encapsulated application payload to the UPF for the remote UE.

[0155] In the second approach, the UPF for the VMR-UE may forward the GTP encapsulated application payload directly to the UPF for the remote UE, for example, using normal IP forwarding over N6, where the VMR-UE sends the payload on the N6 interface and the UPF for the remote UE receives the payload over its N6 interface.

[0156] In a third approach, if the UPF for the VMR-UE and the UPF for the remote UE are the same UPF, the UPF for the VMR-UE can forward the GTP encapsulated application payload to the virtual internal port. Examples of parameters for virtual internal port forwarding are as follows, which will be recognized by those skilled in the art.

[0157]

[0158]

[0159]

[0160] The flow chart proceeds based on the following assumption: the UPF for the VMR-UE forwards the GTP encapsulated application payload to the service chain or forwarding DN. At operation 634, the UPF for the VMR-UE sends the GTP encapsulated application payload to the service chain or forwarding DN, and the service chain or forwarding DN receives the GTP encapsulated application payload from the UPF for the VMR-UE.

[0161] At operation 636, the service chain or forwarding DN sends the GTP encapsulated application payload to the UPF for the remote UE, and the UPF for the remote UE receives the GTP encapsulated application payload from the service chain or forwarding DN.

[0162] At operation 638, the UPF for the remote UE removes the GTP header (provided in operation 624) from the GTP encapsulated application payload. The UPF for the remote UE sends the application payload to the application DN, and the application DN receives the application payload from the UPF for the remote UE.

[0163] The following operations 640-650 describe the transmission of downlink application packets from the application DN to the remote UE.

[0164] At operation 640, the application DN sends application data of the remote UE to the UPF for the remote UE, and the UPF for the remote UE receives the application data from the application DN.

[0165] At operation 642, the UPF for the remote UE encodes the application data with a GTP header to provide GTP encapsulated application data. The UPF for the remote UE sends the GTP encapsulated application data to the service chaining and forwarding DN, and the service chaining and forwarding DN receives the GTP encapsulated application data from the UPF for the remote UE.

[0166] At operation 644, the service chain and forwarding DN sends the GTP encapsulated application data to the UPF for the VMR-UE, and the UPF for the VMR-UE receives the GTP encapsulated application data from the service chain and forwarding DN. The UPF for the VMR-UE adds a GTP header to the GTP tunnel of the second PDU session of the VMR-UE to provide the GTP encapsulated application data twice.

[0167] At operation 646, the UPF for the VMR-UE sends the GTP encapsulated application data twice to the RAN through the second PDU session of the VMR-UE. The UPF of the VMR-UE identifies the second PDU session based on the PDR configured by the SMF for the VMR-UE. The RAN receives the GTP encapsulated application data twice from the UPF for the VMR-UE.

[0168] At operation 648, the RAN removes the GTP header of the second PDU session from the two GTP encapsulated application data and sends the GTP encapsulated application data to the VMR-UE through the DRB. The RAN can identify the DRB based on the tunnel endpoint identifier (TEID) and can use the QoS flow identifier ("QFI") to identify the QoS flow within the DRB. The VMR-UE receives the GTP encapsulated application data from the RAN. Then, the VMR-UE sends the GTP encapsulated application data to the VMR-NN, and the VMR-NN receives the GTP encapsulated application data from the VMR-UE.

[0169] The VMR-NN removes the GTP header of the PDU session of the remote UE from the GTP encapsulated application data at operation 650. The VMR-NN sends the application data to the remote UE, and the remote UE receives the application data.

[0170] Thus, in the manner described above, application data to and from a remote UE may be transmitted in a VMR system without supporting IAB.

[0171] Figure 6 The signals and operations are illustrative only, and variations are considered to be within the scope of the present disclosure. In an embodiment, the signals and operations may include Figure 6 Other signals and operations not shown in the figure. In an embodiment, the signals and operations may not include Figure 6 In an embodiment, these signals and operations can be used in conjunction with Figure 6Such and other embodiments are considered to be within the scope of the present disclosure.

[0172] Figure 4-Figure 6 An example is shown in which the VMR-UE, VMR-NN, and remote UE all subscribe to the same PLMN (eg, PLMN-A). Figure 7 An example is shown in which the VMR-NN and / or the remote UE subscribe to different PLMNs (e.g., PLMN-B). Figure 7 In the example, PLMN-B 730 includes AMF 732, UPF 733 and SMF 734. Figure 7 The signals and operations of the example are similar to Figure 5 Signals and operations, where the UPF for the VMR-UE forwards data to another UPF. In the case where PLMN-B is the H-PLMN of the VMR-NN, the VMR-NN interface control message will be routed to the AMF in PLMN-B through the UPF in PLMN-B. In the case where PLMN-B is the H-PLMN of the remote UE, the application data for the remote UE will be routed to various data networks through the UPF in PLMN-B. PLMN-A and PLMN-B UPF to UPF packet forwarding can be based on public IP routing, forwarding based on an intermediate DN common to both PLMN-A and PLMN-B, and / or based on a service agreement that utilizes point-to-point (PtP) based packet forwarding. In this case, if the operator of PLMN-B wants to serve the remote UE in PLMN-B, the SMF and UDM in the H-PLMN of the VMR-UE (i.e., PLMN-A) will know the arrangement through local configuration and / or session management (SM) subscription.

[0173] Reference now Figure 8 , Figure 8 A block diagram of example components of a UE or network device is shown. The device includes an electronic storage device 810, a processor 820, a memory 850, and a network interface 840. The various components can be communicatively coupled to each other. The processor 820 can be and can include any type of processor, such as a single-core central processing unit (CPU), a multi-core CPU, a microprocessor, a digital signal processor (DSP), a system on a chip (SoC), or any other type of processor. The memory 850 can be a volatile type of memory, such as RAM, or a non-volatile type of memory, such as NAND flash memory. The memory 850 includes processor-readable instructions that are executable by the processor 820 to cause the device to perform various operations, including the operations described herein, such as Figure 5 and Figure 6 operation.

[0174] Electronic storage 810 may be and include any type of electronic storage for storing data, such as a hard drive, a solid state drive, and / or an optical disk, among other types of electronic storage. Electronic storage 810 stores processor-readable instructions for causing the device to perform its operations, and stores data associated with such operations, such as storing data related to the 5G NR standard and other data. Network interface 840 may implement wireless network technologies, such as 5G NR and / or other wireless network technologies.

[0175] Figure 8 The components shown are examples only, and those skilled in the art will appreciate that the device includes other components not shown, and may include multiples of any of the components shown. Such and other embodiments are considered to be within the scope of the present disclosure.

[0176] Additional embodiments of the present disclosure include the following examples.

[0177] Example 1.1. A user device comprising:

[0178] A component for establishing a protocol data unit (PDU) session between a vehicle-mounted relay user equipment (VMR-UE) and a core network subscribed by the VMR-UE; and

[0179] means for sending to the core network an indication that the PDU session is used for at least one of:

[0180] interface control messages of a vehicle relay network node (VMR-NN) installed in a vehicle together with the VMR-UE;

[0181] A user plane (UP) of at least one second UE connected to the VMR-NN

[0182] business; or

[0183] Control plane (CP) traffic of the at least one second UE connected to the VMR-NN.

[0184] Example 1.2. The user equipment of Example 1.1, wherein the means for sending the indication comprises means for sending the indication that the PDU session is for the interface control message of the VMR-NN.

[0185] Example 1.3. The user equipment according to Example 1.2 further includes:

[0186] means for receiving an interface control message from said VMR-NN; and

[0187] means for sending the interface control message as an application payload of the VMR-UE through the PDU session.

[0188] Example 1.4. The user equipment of Example 1.3, wherein the means for sending the interface control message comprises means for sending the interface control message using an identifier parameter of the VMR-NN.

[0189] Example 1.5. The user equipment according to any one of Examples 1.1 to 1.4, wherein the establishing the PDU session with the core network comprises:

[0190] Means for receiving uplink (UL) quality of service (QoS) rules from a session management function (SMF) of the core network, the UL QoS rules being configured for detecting the interface control message of the VMR-NN.

[0191] Example 1.6. The user equipment according to any one of Examples 1.1 to 1.5, further comprising:

[0192] means for receiving, by the VMR-UE, an interface control message response from the core network via the PDU session; and

[0193] A component for sending the interface control message response from the VMR-UE to the VMR-NN.

[0194] Example 1.7. The user equipment of Example 1.2 further includes:

[0195] means for receiving, by the VMR-UE from the VMR-NN, at least one registration request for registering the at least one second UE with an Access and Mobility Management Function (AMF); and

[0196] means for sending, by the VMR-UE over the PDU session, the at least one registration request for the at least one second UE.

[0197] Example 1.8. The user equipment of Example 1.7 further comprising:

[0198] A component for receiving, by the VMR-UE through the PDU session, PDU session resource establishment information provided by a session management function (SMF) from the core network, wherein the PDU session resource establishment information is configured to enable the at least one second UE to establish a PDU session with a user plane function (UPF) for the at least one second UE.

[0199] Example 1.9. The user equipment according to Example 1.7 or Example 1.8, further comprising:

[0200] a component configured to receive, by the VMR-UE, from the VMR-NN, the following instruction: a component for establishing a second PDU session with the core network for at least one of the UP service of the at least one second UE or the CP service of the at least one second UE;

[0201] means for establishing the second PDU session with the core network, the second PDU session being different from the PDU session of the interface control message of the VMR-NN; and

[0202] A component used to send the following indication to the core network: the second PDU session is used for at least one of the UP service or the CP service of the at least one second UE.

[0203] Example 1.10. The user equipment of Example 1.9, further comprising:

[0204] means for receiving at least one of UP data of the at least one second UE or CP data of the at least one second UE from the VMR-NN; and

[0205] A component for sending at least one of the UP data of the at least one second UE or the CP data of the at least one second UE to the core network through the second PDU session.

[0206] Example 1.11. The user equipment according to Example 1.10,

[0207] wherein the receiving of at least one of the UP data of the at least one second UE or the CP data of the at least one second UE comprises receiving a General Packet Radio Service Tunneling Protocol (GTP) encapsulated application payload including the at least one of the UP data of the at least one second UE or the CP data of the at least one second UE, and

[0208] Wherein, sending at least one of the UP data or the CP data of the at least one second UE includes sending the GTP encapsulated application payload including the at least one of the UP data or the CP data of the at least one second UE to the core network through the second PDU session.

[0209] Example 1.12. A user device according to any one of Examples 1.9 to 1.11, further comprising:

[0210] means for receiving, by the VMR-UE, application data for the at least one second UE from the core network via the second PDU session; and

[0211] means for sending the application data for the at least one second UE to the VMR-NN.

[0212] Example 1.13. The user equipment according to Example 1.12,

[0213] wherein the receiving the application data for the at least one second UE comprises receiving a General Packet Radio Service Tunneling Protocol (GTP) encapsulated application payload comprising the application data for the at least one second UE, and

[0214] Wherein the sending of the application data for the at least one second UE comprises sending the GTP encapsulated application payload comprising the application data for the at least one second UE.

[0215] Example 2.1. An apparatus comprising:

[0216] means for establishing, by at least one component of a core network, a protocol data unit (PDU) session with a vehicle-relay user equipment (VMR-UE) subscribed to the core network; and

[0217] means for receiving, from the VMR-UE, an indication that the PDU session is for at least one of:

[0218] interface control messages of a vehicle relay network node (VMR-NN) installed in a vehicle together with the VMR-UE;

[0219] A user plane (UP) of at least one second UE connected to the VMR-NN

[0220] business; or

[0221] Control plane (CP) traffic of the at least one second UE connected to the VMR-NN.

[0222] Example 2.2. The apparatus of Example 2.1, wherein the means for receiving the indication comprises means for receiving the indication that the PDU session is for the interface control message of the VMR-NN.

[0223] Example 2.3. The apparatus of Example 2.2 further includes:

[0224] means for receiving an application payload of the VMR-UE from the VMR-UE through the PDU session, the application payload of the VMR-UE comprising an interface control message of the VMR-NN.

[0225] Example 2.4. The apparatus of Example 3, wherein the interface control message of the VMR-NN received from the VMR-UE includes an identifier parameter of the VMR-NN.

[0226] Example 2.5. The apparatus according to any one of Examples 2.1 to 2.4, further comprising:

[0227] means for configuring an uplink (UL) quality of service (QoS) rule for a session management function (SMF) of the at least one component of the core network, the UL QoS rule being configured for detecting the interface control message of the VMR-NN; and

[0228] means for sending the UL QoS rule to the VMR-UE for use by the VMR-UE in detecting the interface control message of the VMR-NN.

[0229] Example 2.6. The apparatus of Example 2.5, wherein the configuration of the UL QoS rule is based on at least one of:

[0230] an identifier parameter of the VMR-NN, or

[0231] Identifier parameter of the Access and Mobility Management Function (AMF) of the VMR-NN.

[0232] Example 2.7. The apparatus of Example 2.6 further comprising:

[0233] For at least one of the following:

[0234] a unified data management (UDM) session management (SM) subscription for the VMR-UE;

[0235] local configuration of the SMF; or

[0236] a Policy Control Function (PCF) policy for the VMR-UE;

[0237] Gets a component that is at least one of the following:

[0238] the identifier parameter of the VMR-NN; or

[0239] The identifier parameter of the AMF for the VMR-NN.

[0240] Example 2.8. The apparatus of Example 2.6 further comprising:

[0241] means for receiving, during said establishing said PDU session, from said VMR-UE at least one of:

[0242] the identifier parameter of the VMR-NN, or

[0243] The identifier parameter of the AMF of the VMR-NN.

[0244] Example 2.9. The apparatus according to any one of Examples 2.1 to 2.8, further comprising:

[0245] means for configuring, by a session management function (SMF) of said at least one component of said core network, a packet detection rule (PDR) and a forwarding action rule (FAR) to a user plane function (UPF), said PDR and said FAR being configured to detect packets and forward packets to said AMF of said VMR-NN,

[0246] Wherein the packet comprises a destination address set to the address of an Access and Mobility Management Function (AMF) of the VMR-NN.

[0247] Example 2.10. The apparatus of any one of Examples 2.1 to 2.9, further comprising:

[0248] A component for configuring a packet detection rule (PDR) and a forwarding action rule (FAR) to a user plane function (UPF) by the session management function (SMF) of at least one component of the core network, the PDR and the FAR being configured to detect a packet including a source address and forward a packet including the source address, wherein the source address is set to the address of the AMF of the VMR-NN and is mapped to a packet forwarding control protocol (PFCP) session.

[0249] Example 2.11. The apparatus of any one of Examples 2.1 to 2.10, further comprising:

[0250] means for receiving, by a User Plane Function (UPF) of the at least one component of the core network, a message from an Access and Mobility Management Function (AMF) of the VMR-NN; and

[0251] Means for generating a General Packet Radio Service Tunneling Protocol (GTP) encapsulated message based on the message from the AMF of the VMR-NN.

[0252] Example 2.12. The apparatus of Example 2.2 further includes:

[0253] means for receiving, from the VMR-UE over the PDU session, at least one registration request for the at least one second UE to register with an access and mobility management function (AMF) for the at least one second UE.

[0254] Example 2.13. The apparatus of Example 2.12 further comprising:

[0255] means for selecting, by the AMF for the at least one second UE, a session management function (SMF) of the at least one second UE.

[0256] Example 2.14. The apparatus of Example 2.13 further comprising:

[0257] A component for sending PDU session resource establishment information through the PDU session by the SMF for the at least one second UE, wherein the PDU session resource establishment information is configured to enable the at least one second UE and the user plane function (UPF) for the at least one second UE to establish a PDU session.

[0258] Example 2.15. The apparatus of Example 2.2 further comprising:

[0259] means for establishing a second PDU session with the VMR-UE, the second PDU session being different from the PDU session of the interface control message of the VMR-NN; and

[0260] Means for receiving an indication from the VMR-UE that the second PDU session is for at least one of the UP service of the at least one second UE or the CP service of the at least one second UE.

[0261] Example 2.16. The apparatus of Example 2.15, further comprising:

[0262] means for configuring, by a session management function (SMF) for the VMR-UE, a user plane function (UPF) for the VMR-UE, the UPF having at least one of the following:

[0263] Packet detection rules (PDR) and forwarding action rules (FAR) configured to detect and forward uplink packets including a destination IP address set to the IP address of the UPF for the at least one second UE, or

[0264] The PDR and FAR are configured to detect and forward downlink packets including a source address set to the address of the UPF for the at least one second UE.

[0265] Example 2.17. An apparatus according to Example 2.16, wherein the PDR and FAR are configured to detect and forward the packet to an intermediate data network (DN), the intermediate DN being a service chain or forwarding DN configured to forward the packet to the UPF for the at least one second UE.

[0266] Example 2.18. The apparatus of any one of Examples 2.15 to 2.17 further includes:

[0267] means for configuring, by the SMF for the at least one second UE, the UPF for the at least one second UE, the UPF having at least one of the following:

[0268] packet detection rules (PDR) and forwarding action rules (FAR) configured to detect and forward uplink packets comprising a destination address set to the address of the UPF for the at least one second UE, or

[0269] The PDR and the FAR are configured to detect and forward downlink packets including a source address set to an address of an application server.

[0270] Example 2.19. The apparatus of Example 2.15 further comprising:

[0271] means for receiving, by a user plane function (UPF) for the VMR-UE, at least one of UP data or CP data of the at least one second UE from the VMR-UE through the second PDU session; and

[0272] Means for forwarding, by the UPF for the VMR-UE, at least one of the UP data of the at least one second UE or the CP data of the at least one second UE.

[0273] Example 2.20. The apparatus of Example 2.19, wherein the forwarding of the at least one of the UP data or the CP data of the at least one second UE comprises:

[0274] A component for forwarding at least one of the UP data or the CP data by the VMR-UE to an intermediate data network (DN), wherein the intermediate DN is a service chain or forwarding DN configured to forward at least one of the UP data or the CP data of the at least one second UE to the UPF for the at least one second UE.

[0275] Example 2.21. The apparatus of Example 2.19, wherein the forwarding of the at least one of the UP data of the at least one second UE or the CP data of the at least one second UE comprises:

[0276] Means for forwarding, by the UPF for the VMR-UE using IP forwarding over an N6 interface, at least one of the UP data or the CP data to the UPF for the at least one second UE.

[0277] Example 2.22. The apparatus of Example 2.19, wherein the UPF for the VMR-UE is also the UPF for the at least one second UE,

[0278] The means for forwarding at least one of the UP data or the CP data of the at least one second UE includes a means for forwarding the at least one of the UP data or the CP data to a virtual internal port by the UPF for the VMR-UE before N6 forwarding.

[0279] Example 2.23. The apparatus of any one of Examples 2.15 to 2.22 further includes:

[0280] means for receiving, by the UPF for the VMR-UE, application data for the at least one second UE;

[0281] means for sending the application data for the at least one second UE to the VMR-UE over the second PDU session.

[0282] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For example, although some embodiments herein are described as separate embodiments, each embodiment herein may be combined with one or more other embodiments herein. The specific structural and functional details disclosed herein should not be interpreted as limitations, but as the basis for the claims, and as a representative basis for teaching those skilled in the art to use the present disclosure in various ways in almost any appropriately detailed structure. Throughout the description of the drawings, the same reference numerals may refer to similar or identical elements.

[0283] According to the present disclosure, the phrases "in one aspect", "in various aspects", "in various aspects", "in some aspects" or "in other aspects" may each refer to one or more of the same or different aspects. The phrase "plurality" may refer to two or more.

[0284] According to the present disclosure, the phrases "in one embodiment," "in an embodiment," "in various embodiments," "in some embodiments," or "in other embodiments" may each refer to one or more of the same or different embodiments. A phrase of the form "A or B" means "(A), (B), or (A and B)." A phrase of the form "at least one of A, B, or C" means "(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).

[0285] Any of the methods, programs, algorithms or codes described herein can be converted into a programming language or a computer program, or represented by it. The terms "programming language" and "computer program" used herein each include any language for specifying computer instructions, and include (but are not limited to) the following languages ​​and their derivatives: assembly language, Basic, batch files, BCPL, C, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command language, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, the metalanguage of the program itself, and all first, second, third, fourth, fifth or subsequent generations of computer languages. Databases and other data patterns, and any other metalanguages ​​are also included. There is no difference in the language of interpretation, compilation or simultaneous use of compilation and interpretation methods. There is no difference between the compiled version of the program and the source version. Therefore, if a programming language can exist in more than one state (such as source, compilation, object or link), a reference to a program is a reference to any and all such states. A reference to a program can include actual instructions and / or the intention of these instructions.

[0286] Although various aspects of the present disclosure are shown in the accompanying drawings, it is not intended that the present disclosure is limited thereto, as the scope of the present disclosure should be as broad as possible and the specification should be read in the same manner. Therefore, the above description should not be interpreted as limiting, but only as an example of specific aspects. Those skilled in the art will be able to envision other modifications within the scope and spirit of the appended claims.

Claims

1. A method for communication, comprising: A protocol data unit (PDU) session is established by a vehicle-mounted relay user equipment (VMR-UE) and a core network subscribed by the VMR-UE; as well as Sending to the core network an indication that the PDU session is used for at least one of the following: interface control messages of a vehicle relay network node (VMR-NN) installed in a vehicle together with the VMR-UE; User Plane (UP) traffic of at least one second UE connected to the VMR-NN; or Control plane (CP) traffic of the at least one second UE connected to the VMR-NN.

2. The method according to claim 1, Wherein sending the indication comprises sending the indication of the interface control message of the PDU session for the VMR-NN, and the method further comprises: receiving an interface control message from the VMR-NN; as well as The interface control message is sent as an application payload of the VMR-UE through the PDU session.

3. The method according to claim 2, wherein sending the interface control message comprises: The interface control message is sent using an identifier parameter of the VMR-NN.

4. The method according to any one of claims 1 to 3, wherein establishing the PDU session with the core network comprises: An uplink (UL) quality of service (QoS) rule is received from a session management function (SMF) of the core network, the UL QoS rule being configured for detecting the interface control message of the VMR-NN.

5. The method according to any one of claims 1 to 4, further comprising: The VMR-UE receives an interface control message response from the core network through the PDU session; as well as The VMR-UE sends the interface control message response to the VMR-NN.

6. The method according to claim 2, further comprising: receiving, by the VMR-UE from the VMR-NN, at least one registration request for registering the at least one second UE with an access and mobility management function (AMF); as well as The at least one registration request for the at least one second UE is sent by the VMR-UE through the PDU session.

7. The method according to claim 6, further comprising: The VMR-UE receives PDU session resource establishment information provided by a session management function (SMF) from the core network through the PDU session, wherein the PDU session resource establishment information is configured to enable the at least one second UE to establish a PDU session with a user plane function (UPF) for the at least one second UE.

8. The method according to claim 6 or claim 7, further comprising: The VMR-UE receives the following instruction from the VMR-NN: establishing a second PDU session with the core network for at least one of the UP service of the at least one second UE or the CP service of the at least one second UE; establishing the second PDU session with the core network, the second PDU session being different from the PDU session used for the interface control message of the VMR-NN; as well as The following indication is sent to the core network: the second PDU session is used for at least one of the UP service or the CP service of the at least one second UE.

9. The method according to claim 8, further comprising: receiving at least one of UP data of the at least one second UE or CP data of the at least one second UE from the VMR-NN; as well as At least one of the UP data of the at least one second UE or the CP data of the at least one second UE is sent to the core network through the second PDU session.

10. The method according to claim 9, The receiving at least one of the UP data of the at least one second UE or the CP data of the at least one second UE comprises: receiving a general packet radio service tunneling protocol (GTP) encapsulated application payload including at least one of the UP data of the at least one second UE or the CP data of the at least one second UE, and Sending at least one of the UP data or the CP data of the at least one second UE includes: sending the GTP encapsulated application payload including the at least one of the UP data or the CP data of the at least one second UE to the core network through the second PDU session.

11. The method according to any one of claims 8 to 10, further comprising: receiving, by the VMR-UE through the second PDU session, application data for the at least one second UE from the core network; as well as The application data for the at least one second UE is sent to the VMR-NN.

12. The method according to claim 11, Wherein receiving the application data for the at least one second UE comprises: receiving a general packet radio service tunneling protocol (GTP) encapsulated application payload including said application data for said at least one second UE, and Wherein sending the application data for the at least one second UE comprises: sending the GTP encapsulated application payload including the application data for the at least one second UE.

13. A user equipment, comprising: at least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the user equipment to at least perform the method according to any one of claims 1 to 12.

14. A method for communication, comprising: Establishing, by at least one component of the core network, a protocol data unit (PDU) session with a vehicle-relay user equipment (VMR-UE) subscribed to the core network; as well as receiving, from the VMR-UE, an indication that the PDU session is for at least one of: interface control messages of a vehicle relay network node (VMR-NN) installed in a vehicle together with the VMR-UE; User Plane (UP) traffic of at least one second UE connected to the VMR-NN; or Control plane (CP) traffic of the at least one second UE connected to the VMR-NN.

15. The method of claim 14, wherein receiving the indication comprises receiving the indication that the PDU session is for the interface control message of the VMR-NN, the method further comprising: An application payload of the VMR-UE is received from the VMR-UE through the PDU session, wherein the application payload of the VMR-UE includes an interface control message of the VMR-NN.

16. The method according to claim 15, wherein the interface control message of the VMR-NN received from the VMR-UE comprises: Identifier parameter of the VMR-NN.

17. The method according to any one of claims 14 to 16, further comprising: configuring, by a session management function (SMF) of the at least one component of the core network, an uplink (UL) quality of service (QoS) rule, the UL QoS rule being configured for detecting the interface control message of the VMR-NN; as well as The UL QoS rule is sent to the VMR-UE, so that the VMR-UE can detect the interface control message of the VMR-NN.

18. The method of claim 17, wherein the configuration of the UL QoS rule is based on at least one of: an identifier parameter of the VMR-NN; or Identifier parameter for the Access and Mobility Management Function (AMF) of the VMR-NN.

19. The method according to claim 18, further comprising: At least one of the following: a unified data management (UDM) session management (SM) subscription for the VMR-UE; local configuration of the SMF; or a Policy Control Function (PCF) policy for the VMR-UE; Get at least one of the following: the identifier parameter of the VMR-NN; or The identifier parameter of the AMF for the VMR-NN.

20. The method according to claim 19, further comprising: During establishment of the PDU session, at least one of the following is received from the VMR-UE: the identifier parameter of the VMR-NN; or The identifier parameter of the AMF for the VMR-NN.

21. The method according to any one of claims 14 to 20, further comprising: configuring, by a session management function (SMF) of the at least one component of the core network, a packet detection rule (PDR) and a forwarding action rule (FAR) to a user plane function (UPF), the PDR and the FAR being configured to detect packets and forward packets to the AMF of the VMR-NN, The packet includes a destination address, which is set to an address of an access and mobility management function (AMF) for the VMR-NN.

Images