User equipment virtual network group management

Abstract

Various example embodiments described relate to devices, methods, apparatus, and computer-readable storage media for user equipment (UE) virtual network group management. For example, the method may include determining, at a session management function (SMF), that there is a request associated with session management, the request indicating a shared router group identifier, where a terminal device router belongs to a virtual network, and one or more terminal device routers belonging to the virtual network share the same shared router group identifier; and sending a request associated with a packet forwarding control protocol (PFCP) session to a user plane function (UPF), the request indicating at least the shared router group identifier.

Description

TECHNICAL FIELD

[0001] Various example embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly to devices, methods, apparatuses, and computer-readable storage media related to user equipment (UE) virtual network group management. BACKGROUND

[0002] Examples of mobile or wireless telecommunications systems can include the Universal Mobile Telecommunication System (UMTS) Terrestrial Radio Access Network (UTRAN), the evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), Multifire technology, LTE-sequent enhancements, the fifth generation mobile communication technology (5G) radio access technology or 5G New Radio (NR) access technology and / or 5G-Advanced. The 5G wireless system refers to the next generation (NG) radio systems and network architecture. The 5G network technology is mainly based on NR technology, but 5G (or NG) networks can also be built on E-UTRAN radios. It is estimated that NR can provide bitrates of the order of 10-20 Gbit / s or higher and can support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine type communication (mMTC). NR is expected to provide extremely wide bandwidth and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things, IoT. SUMMARY

[0003] Some example embodiments of the present disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the various example embodiments, nor are they intended to limit the scope of the disclosure in any way. Other features, aspects, and elements can become apparent with respect to the disclosure.

[0004] In a first aspect, an apparatus is provided. The apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to determine that there is a request associated with session management, the request indicating a shared router group identification, wherein a terminal device router belongs to a virtual network, and one or more terminal device routers belonging to the virtual network share a same shared router group identification; and send, to a user plane function (UPF), a request associated with a packet forwarding control protocol (PFCP) session, the request indicating at least the shared router group identification.

[0005] In a second aspect, an apparatus is provided. The apparatus includes at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: receive from a Session Management Function (SMF) a request associated with a Packet Forwarding Control Protocol (PFCP) session, the request indicating at least a shared router group identifier associated with an end-device router, wherein the end-device router belongs to a virtual network, and one or more end-device routers belonging to the virtual network share the same shared router group identifier; and perform operations associated with the PFCP session at least based on the shared router group identifier.

[0006] In a third aspect, an apparatus is provided. The apparatus includes at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: send a request associated with session management to an SMF, the request indicating a shared router group identifier, wherein the apparatus belongs to a virtual network, and one or more devices belonging to the virtual network share the same shared router group identifier.

[0007] In a fourth aspect, a method is provided. The method includes: determining at the SMF that a request associated with session management exists, the request indicating a shared router group identifier, wherein the end-device routers belong to a virtual network, and one or more end-device routers belonging to the virtual network share the same shared router group identifier; and sending to the UPF a request associated with a PFCP session, the request indicating at least the shared router group identifier.

[0008] In a fifth aspect, a method is provided. The method includes: receiving, at a UPF, a request associated with a Packet Forwarding Control Protocol (PFCP) session from an SMF, the request indicating at least a shared router group identifier associated with an end-device router, wherein the end-device router belongs to a virtual network, and one or more end-device routers belonging to the virtual network share the same shared router group identifier; and performing operations associated with the PFCP session at least based on the shared router group identifier.

[0009] In a sixth aspect, a method is provided. The method includes: sending a session management-related request from an end-device router to an SMF, the request indicating a shared router group identifier, wherein the device belongs to a virtual network, and one or more devices belonging to the virtual network share the same shared router group identifier.

[0010] In a seventh aspect, an apparatus is provided, comprising: components for determining the existence of a request associated with session management, the request indicating a shared router group identifier, wherein the terminal device routers belong to a virtual network, and one or more terminal device routers belonging to the virtual network share the same shared router group identifier; and components for sending a request associated with a Packet Forwarding Control Protocol (PFCP) session to a User Plane Function (UPF), the request indicating at least the shared router group identifier.

[0011] In an eighth aspect, an apparatus is provided, comprising: components for receiving from a Session Management Function (SMF) a request associated with a Packet Forwarding Control Protocol (PFCP) session, the request indicating at least a shared router group identifier associated with an end-device router, wherein the end-device router belongs to a virtual network, and one or more end-device routers belonging to the virtual network share the same shared router group identifier; and components for performing operations associated with the PFCP session at least based on the shared router group identifier.

[0012] In a ninth aspect, an apparatus is provided, comprising: a component for sending a session management-related request to a session management function (SMF), the request indicating a shared router group identifier, wherein the apparatus belongs to a virtual network, and one or more apparatuses belonging to the virtual network share the same shared router group identifier.

[0013] In a tenth aspect, a computer-readable medium having a computer program stored thereon is provided, which, when executed by at least one processor of the device, causes the device to perform the method according to the fourth, fifth, or sixth aspect. Attached Figure Description

[0014] Some exemplary embodiments of this disclosure will now be described with reference to the accompanying drawings.

[0015] Figure 1 An example environment in which example embodiments of this disclosure may be implemented is shown; Figure 2 A signaling diagram illustrating examples of processes according to some exemplary embodiments of the present disclosure is shown; Figure 3 Examples of session management subscription models for a UE according to some example embodiments of this disclosure are shown; Figure 4 Examples of implementations of the 2-step Packet Detection (PDR) rule and Forwarding Action (FAR) rule according to some exemplary embodiments of the present disclosure are shown; Figure 5 A flowchart is shown illustrating an example method for managing a UE virtual network group according to some example embodiments of this disclosure; Figure 6 A flowchart is shown illustrating an example method for managing a UE virtual network group according to some example embodiments of this disclosure; Figure 7 A flowchart is shown illustrating an example method for managing a UE virtual network group according to some example embodiments of this disclosure; Figure 8 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 9 A block diagram of an example computer-readable medium according to some embodiments of the present disclosure is shown.

[0016] In all the accompanying drawings, the same or similar reference numerals may denote the same or similar elements. Detailed Implementation

[0017] Various exemplary embodiments of this disclosure are further described. It should be understood that these exemplary embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any specific limitation on the scope of this disclosure. The exemplary embodiments described herein can be implemented in various ways other than those described below.

[0018] The terminology used herein is generally provided for the purpose of describing certain exemplary embodiments only and is not intended to be limiting. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein may have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0019] References to “an embodiment,” “an embodiment,” “an example embodiment,” “some example embodiments,” “certain example embodiments,” “various example embodiments,” etc., in this disclosure indicate that the described one or more reference embodiments may include one or more specific features, structures, or characteristics. However, each embodiment or example embodiment described herein need not necessarily include one or more specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment or the same example embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment or example embodiment, it is believed that combining such a feature, structure, or characteristic with any other embodiment or example embodiment described herein is within the knowledge of those skilled in the art, whether or not such combination is explicitly described.

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

[0021] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements is connected by “and” or “or”, means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0022] As used herein, unless explicitly stated otherwise, the execution of step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and one or more intervention steps may be included between “A” and the step.

[0023] As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms “comprising,” “including,” “having,” “having,” “containing,” and / or “including” as used herein specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0024] As used herein, the term "circuit system" may refer to one or more of the following example embodiments: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuits only), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of analog and / or digital hardware circuitry with software / firmware, and (ii) Any part of a hardware processor having software (including digital signal processor(s) working together to enable a device (such as a mobile phone or server) to perform various functions), software, and memory), and (c) One or more hardware circuits and / or one or more processors, such as one or more microprocessors or a portion thereof, that require software (e.g., firmware) to operate, but the software may not be present when operation is not required.

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

[0026] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), Enhanced Machine-Type Communication (eMTC), etc. Furthermore, communication between terminal devices and network nodes in a communication network can be performed according to any suitable generated communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), sixth-generation (6G) communication protocols and / or any other currently known or future-developed protocols. The exemplary embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development in communications, future types of communication technologies and systems that can implement this disclosure will also exist. The scope of this disclosure should not be limited to only the aforementioned communication technologies and systems.

[0027] As used herein, the terms "network node," "radio network node," and / or "radio access network node" refer to a node in a communication network through which terminal devices access the network and receive services. A network node can refer to a base station (BS / BTS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Remote Radio Head (RRH), a repeater, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femtosecond or picosecond), a non-terrestrial network (NTN) or non-terrestrial network node (such as a satellite network node, a low Earth orbit (LEO) satellite, and a geostationary Earth orbit (GEO) satellite), a spacecraft network node, etc., depending on the terminology and technology applied. In some example embodiments, the LEO split architecture includes a centralized unit (CU) and a distributed unit (DU). In some other example embodiments, a portion or all of the radio access network nodes may be embedded on an airborne or space-based NTN vehicle.

[0028] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), an IP host connected to a UE acting as a router, a user station (SS), a portable user station, a mobile station (MS), or an access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and return devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Terminal devices may also correspond to the mobile terminal (MT) portion of an IAB node (e.g., a relay node). As used herein, the terms “terminal device,” “communication device,” “terminal,” “user equipment,” and “UE” are used interchangeably.

[0029] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network node, including resources in the time domain, frequency domain, spatial domain, code domain, or any other resources used to implement communication. Resources in both the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other fields.

[0030] In industrial applications, there may be devices that lack the ability to access 5G networks. Such devices can be configured to use a 5G UE as an access router to access 5G services and applications.

[0031] Some industrial applications may be time-sensitive. Relying on a UE to act as a router carries a certain degree of risk, which can lead to a single point of failure. UE-router failures can be caused by various factors, such as UE power failures, connectivity failures from the UE to the radio access network (RAN), line-of-sight (LOS) issues, overload conditions, etc. In the following, various exemplary embodiments of this disclosure are further explained with reference to mobile communication devices capable of communicating via wireless cellular systems and mobile communication systems serving such mobile communication devices. Before further detailing the various exemplary embodiments, refer to... Figure 1 Briefly explain some general aspects of wireless communication systems, their access systems, and mobile communication devices to aid in understanding the technology underlying the described examples.

[0032] Figure 1 An example communication network 100 in which exemplary embodiments of the present disclosure can be implemented is shown. For example... Figure 1 As shown, the communication network 100 may include terminal devices 130-1 and 130-2. Terminal devices 130-1 and 130-2 may be connected to one or more devices 140-1, 140-2, 140-3, and 140-4. Devices 140-1, 140-2, 140-3, and 140-4 may be configured not to have the capability to access a 5G system (5GS). For example, as shown, devices 140-1, 140-2, 140-3, and 140-4 may connect to terminal devices 130-1 and / or 130-2 via a network, such as an IP network, subnet, etc., to access 5GS. That is, terminal devices 130-1 and / or 130-2 may act as routers for devices 140-1, 140-2, 140-3, and 140-4.

[0033] In the following text, devices 140-1, 140-2, 140-3 and / or 140-4 may also be collectively referred to as device 140 (more generally) which does not have the common capability to access 5G, and terminal devices 130-1 and 130-2 may also be referred to as terminal device routers 130-1 and 130-2, or terminal device router 130 (more generally).

[0034] The communication network 100 may include a core network (CN) 103, which may include, for example, one or more network functions (NFs) to support user plane (UP) functions, such as User Plane Function (UPF) 120. UPF 120 may be configured to forward traffic transmitted between RAN 102 and one or more devices 140 behind the terminal equipment router 130. The forwarding path between UPF 120 and RAN 102 may be referred to as the N3 path.

[0035] CN 103 may also include a Session Management Element (SMF) 110 configured to implement session management functions within CN 103. SMF 110 is also configured to interact with the decoupled data plane, create, update, and remove Protocol Data Unit (PDU) sessions, and manage session contexts with UPF 120. Each of SMF 110 and UPF 120 may be implemented by one or more physical devices, apparatuses, or servers.

[0036] In addition, CN 103 may also include other NFs, such as Access and Mobility Management Function (AMF) 150, which can be configured to provide various functions related to security, access management, and authorization. For example, AMF 150 can be configured to receive new session management requests from End-Equipment Router 130 and / or RAN 102 and forward the session management requests to SMF 110. CN 103 may also include Data Network (DN) 160. The forwarding path between UPF 120 and DN 160 may be referred to as the N6 path.

[0037] It should be understood that Figure 1 The number of network nodes and terminal devices depicted is provided for illustrative purposes and does not impose any limitations. The communication network 100 may include any suitable number of network nodes and terminal devices.

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

[0039] As mentioned above, a UE can be used as a router for devices that do not have 5GS access capabilities. In this case, if reliance on a single UE is necessary due to potential faults such as UE power failure, UE-RAN connection failure, line-of-sight issues, or overload conditions, the data transmission requirements of industrial applications may not be met.

[0040] The network behind the UE can only be manually configured via frame routing or by a prefix delegated to the UE by Internet Protocol version 6 (IPv6) prefixes. Frame routing features allow the 5G core network (5GC) to identify the host device subnets existing behind the UE. Similarly, IPv6 prefixes represent the IPv6 prefixes existing on the devices behind the UE.

[0041] The controller can be implemented as a software-defined networking (SDN) controller. The controller can be configured to collect routing or path information to understand the network topology and manage flow control. For example, the controller could reside in 5GC (e.g., Figure 1 The controller uses various downlink (DL) routes in CN 130 to reach (multiple) devices behind the UE acting as a router. In the case of multiple UE-routers, the controller should collect all available routing information and then select routes from the collected information based on various network and device conditions.

[0042] For example, based on the aforementioned support for SMF and UPF, 5GC can determine the UEs to which packets should be forwarded. For reliability reasons, multiple identical devices behind a UE can be in the same subnet, which can be reached via multiple UEs.

[0043] exist Figure 1 In CN 130, SMF 110 can, for example, be configured to control the forwarding of user plane packets for uplink (UL) and DL services detected by Packet Detection Rules (PDR) by providing forwarding action rules (FAR) with instructions to UPF 120. UPF 120 can forward received DL / UL IP packets to / from Protocol Data Unit (PDU) sessions based on the IP address / prefix provided to UE 130, the IPv6 prefix delegated to UE 130, or the frame route associated with UE 130. SMF 110 can be configured to establish and update packet processing rules (PDR, FAR, etc.) applied at UPF 120 via N4 session signaling.

[0044] Packet forwarding in the 5GC is managed by the Packet Forwarding Control Protocol (PFCP). The SMF 110 can be configured to control packet processing in the UPF 120 by establishing, modifying, or deleting PFCP session contexts via the N4 interface between the SMF 110 and the UPF 120. A PFCP session context corresponds to a single PDU session and includes a PDR. In addition to one or more FARs, the PDR should contain packet detection information (e.g., one or more matching fields that match an upcoming packet).

[0045] Currently, different PDRs for different PFCP sessions may not overlap. For example, any incoming user plane packet may only match the PDR of a single PFCP session and be forwarded via a single PDU session. In multicast / broadcast traffic, the UPF 120 continues to search for other PDRs in other PFCP sessions that match the packet, which are taken into account as exceptions. When forwarding packets to the subnet behind the UE, the current packet processing flow of 5GC restricts the use of multiple PDU sessions associated with the same group of UEs serving the IP hosts behind the UE subnet.

[0046] When two or more UEs act as routers for the same group(s) of devices, they will be mapped to the same frame route or IPv6 prefix in the UPF. As an example, Figure 1 Terminal device routers 130-1 and 130-2 can be configured to act as routers for device groups 140-1, 140-2, 140-3, and 140-4. If they are connected to the same UPF, it will create overlapping packet detection rules with (multiple) identical subnets (e.g., (multiple) frame routes or (multiple) IPv6 prefix entries). The UPF may not know which DL tunnel to use to reach (multiple) devices behind the UE through the subnet filter.

[0047] In this context, to address the aforementioned issues (multiple), a set of terminal device routers (e.g., Figure 1 Terminal device routers 130-1 and 130-2 are providing IP path management and IP packet forwarding support to the IP hosts behind these terminal device routers. Similarly, another group of terminal device routers ( Figure 1 (Not shown in the diagram) can also be configured to provide IP path management and IP packet forwarding support to IP hosts behind these terminal device routers. This means that logically, a group of terminal device routers is providing service redirection support to the same group of IP hosts. In various example embodiments of this disclosure, each group of terminal device routers providing service redirection support to the same group of IP hosts can be grouped to form a UE Virtual Network (UVN).

[0048] In this context, the research on how 5GS can create and maintain one or more UVNs based on local configuration, session management subscriptions or service requirements, and how to facilitate data forwarding within the maintained UVNs is a topic for further discussion.

[0049] Various exemplary evolutions of this disclosure present example solutions for UE virtual network group management. As a non-limiting and illustrative example, the SMF can be configured to determine, during the establishment or modification of session management of an end-device router, the existence of a request associated with session management that indicates a shared router group identifier, wherein the end-device router belongs to the UVN, and one or more end-device routers belonging to the UVN share the same shared router group identifier.

[0050] Based on this, UVN internal interfaces can be dynamically created within the UPF based on subscription or local configuration. UVN internal interfaces can be implemented as virtual interfaces within the UPF and used to collect upcoming packets from N6. UVN internal interfaces can be used to avoid PDR overlap at the N6 interface. When multiple packets are received, various FAR rules and their weights, replication, and activation / standby states can be associated with the UVN internal interface. Multiple UVN internal interfaces can be created within the UPF to support multiple subnets, or even to apply different routing rules to different prefixes / subnets behind the UE, by adding a unique UVN group suffix to the UVN internal interface name.

[0051] Furthermore, the SMF can dynamically provide instructions to the UPF regarding path selection based on path latency, packet replication, or load balancing requirements. The path selection decision process, based on path availability, packet replication requirements, and load balancing among multiple N3 paths, is performed by the Policy Control Function (PCF) / SMF and UPF. This can be based on various information, such as application policy requirements for packet replication of critical services, load balancing among paths based on path load and capacity, and / or priority-based path selection based on configured / defined policies.

[0052] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0053] Now for reference Figure 2 This illustrates signaling diagram 200 for communication according to some example embodiments of the present disclosure. Figure 2 As shown, signaling diagram 200 relates to SMF 110 and UPF 120. For discussion purposes, refer to... Figure 1 To describe signaling diagram 200.

[0054] like Figure 2As shown, SMF 110 can prepare a (202) PFCP session request. Prior to this, SMF 110 may receive a session management subscription request from an end-device router (e.g., end-device router 130-1) via AMF. The session management subscription request may include a request to subscribe to a shared router group identifier (e.g., sharedRouterGroupDataID), which may be indicated, for example, in session management subscription data (e.g., SM_Sub_Data). The shared router group identifier may indicate that end-device router 130-1 belongs to a virtual network of end-device routers (e.g., UVNs). As described above, each group of end-device routers providing service redirection support for the same group of IP hosts can be grouped to form a UVN. One or more end-device routers belonging to a UVN may share the same shared router group identifier. For example, if end-device router 130-2 also belongs to the UVN, then end-device router 130-2 may share the shared router group identifier (e.g., the same as the shared router group identifier of end-device router 130-1).

[0055] In various example embodiments of this disclosure, if a terminal device is to act as a router for an end-user device or device group lacking 5GS access capability, it will have subscription information in the 5GS, which can be controlled by the network operator to add the terminal device as a router device in the network. If the network operator wishes to add more terminal device routers serving the same device group, the terminal device routers must share a common identifier to identify them as packet routers, which may be referred to as a shared router group identifier (e.g., sharedRouterGroupDataID as described above). The shared router group identifier can be considered as part of the session management subscription data.

[0056] Figure 3 Examples of session management subscription models for a UE according to some exemplary embodiments of this disclosure are shown. For example... Figure 3 As shown, when SMF 110 receives Session Management Subscription Data 310 (e.g., SM_subs_Data) from End Device Router 130-1, SMF 110 can be configured to identify whether End Device Router 130-1 is acting as a router, and also to identify which End Device Router group it belongs to (e.g., based on the field of Shared Router Group ID 301 indicated in Session Management Subscription Data 310).

[0057] This helps SMF 130 select UPF 120 based on the identifier of the router group (e.g., UVN). For example, if SMF 110 receives Session Management Subscription Data 311 from end device router 130-2, which indicates the same shared router group ID as device router 130-1 (indicated by the field of shared router group ID 312 indicated in Session Management Subscription Data 311), then SMF 110 can recognize that end device routers 130-1 and 130-2 belong to the same UVN.

[0058] A group of terminal devices belonging to the same group identifier can be served by UPF 120 (e.g., the same UPF). Then, the UPF selection during a PDU session management procedure can be based on the shared router group identifier.

[0059] like Figure 3 As shown, the shared router group ID 301 can be mapped to shared data 320, which includes a field called “SharedRouterGroupDatas” 303. “SharedRouterGroupDatas” 303 indicates that shared data 320 can be associated with data from the shared router group. Shared data 320 can be mapped to router group data 330, which includes a field called “FramedRoute” 304 and can be configured to point to “FrameRouteInfo” 340.

[0060] Return to reference Figure 2 After determining and preparing the PFCP session request, SMF 110 can send a (204) request associated with the PFCP session to UPF 120. The request for the associated PFCP session can indicate a shared router group identifier, which is obtained from session management subscription data from the end device router. If the shared router group identifier is new, the request associated with the PFCP session can instruct UPF 120 to create a virtual interface (which may also be referred to as an internal UVN virtual interface or a UVN virtual interface) for the UVN associated with the shared router group identifier at UPF 120.

[0061] In addition, requests associated with a PFCP session can instruct the UPF 120 to create PDRs and FARs for both packets that are coming on the N6 path (e.g., from the DN) and packets that are received at the UVN virtual interface.

[0062] Based on a request associated with a PFCP session, the UPF 120 can (206) create an internal virtual interface of the UVN with an active forwarding path and install (multiple) UE IP-based FARs at the N6 path (e.g., the UE behind the router).

[0063] Another end-device router (e.g., end-device router 130-2) can be configured to create a PDU session and a PDU session request including a shared router group identifier. If SMF 120 determines that a UVN virtual interface for a UVN associated with that shared router group identifier has already been created at UPF 120 (e.g., the shared router group identifier is the same as the shared router group identifier included in the PDU session request from end-device router 130-1, and a PFCP session for end-device router 130-1 has previously been created between SMF and UPF), then SMF 110 can send a (204) request to UPF 120 to establish or modify a PFCP session, indicating that one or more FARs should be added for a new N3 path associated with the same UVN virtual interface (e.g., already created at UPF 120). In this case, an N6PDR may not be added.

[0064] Then, UPF 120 can add (208) new FARs for the new N3 path associated with the UVN virtual interface.

[0065] It should be understood that if SMF 110 receives a session management request that includes a new shared router group identifier, SMF 110 may, for example, instruct UPF 120 to create a new UVN virtual interface for the UVN associated with the new shared router group identifier via a PFCP session establishment or modification request.

[0066] In some example implementations, PFCP sessions between UPF 120 and SMF 110 for multiple PDUs have different PFCP session IDs, but may include the same router group ID that will be considered as a UVN group creation, modification or deletion.

[0067] In addition, UPF 120 can be configured to perform (210) FAR selection for data packet forwarding.

[0068] For example, the UPF 120 may always have at least one FAR present at the virtual interface inside the UVN to forward packets on the N3 path (e.g., at least one PDU of a UE acting as a router in the UE is active).

[0069] Each FAR can be associated with a priority. The UPF 120 can perform FAR selection based on the corresponding priority of the FAR.

[0070] In some example implementations, IP path selection for data forwarding within IP paths (FARs) associated with the same internal virtual interface of the UVN can be performed based on the priority assigned to the respective FAR.

[0071] In some example implementations, priority allocation can be performed based on various aspects, such as a) shortest path; b) quality of service (QoS) monitoring latency results; c) service awareness; and / or d) current load on the IP path.

[0072] Furthermore, the UPF 120 can be configured to store the state of each FAR based on GTP loopback or QoS path monitoring mechanisms. If the SMF 110 allows, the UPF 120 can also be configured to adjust the priority of FARs based on the above results.

[0073] For example, the UPF 120 can be configured to reorder priorities based on QoS monitoring latency results; for example, the UPF120 can select a faster path for data packet forwarding.

[0074] In addition, depending on the service type, multiple IP paths can also have the same priority to enable grouped replication (duplication) functionality.

[0075] Return to reference Figure 2 You can refer to this. Figure 1 The PDR / FAR installation based on the UVN virtual interface proposed in this disclosure is further described.

[0076] When a packet matches a packet detection rule on N6, the UPF can forward the packet to the end-device router group specific to the matching packet filter. When the packet arrives at the UVN virtual interface specific to that router group, the UVN virtual interface can have multiple FARs pointing to an N3 tunnel toward a specific end-device router. For example, if end-device routers 130-1 and 130-2 share the same end-device router group identifier when a packet arrives at this UVN virtual interface specific to that router group, it can have one FAR pointing to an N3 tunnel toward end-device router 130-1 and another FAR pointing to an N3 tunnel toward end-device router 130-2.

[0077] When multiple FAR rules are installed at the UVN virtual interface, the SMF 110 can instruct the UPF 120 to select and use FARs based on application awareness, load balancing, packet replication, path priority, path latency, etc. Furthermore, depending on the network operator's environment and application requirements, the PCF / SMF can determine path selection based on static or dynamic policies.

[0078] In some example implementations, forwarding packets for PDR / FAR rules can carry various instruction parameters, such as packet replication (where packets are replicated and sent on all FARs associated with the PDR), FAR priority (where packets are sent only on the highest priority FAR), and FAR load balancing (where packets are sent based on the weights assigned to each FAR).

[0079] Among the various examples disclosed herein, a mechanism is proposed in which 5GS creates and maintains “UE virtual network groups” that logically group a group of UEs that act as routers behind an IP subnet and serve as the same group of IP hosts.

[0080] A UVN group can, for example, represent a dedicated internal virtual interface within a UPF 120 that is mapped to a specific router group. For instance, end-device routers with the same router group identifier serve the same group(s) of devices behind them. This interface can also act as a forwarding interface for an N6 PDR / FAR. It can also act as a receiving interface to bind to multiple FARs with the same subnet / prefix facing different N3 (access) tunnels.

[0081] In this example embodiment, UVN groups can be dynamically created or maintained when a new end-device router joins or leaves the group, triggered by subscription, local configuration, or AF requests. Therefore, the internal virtual interface associated with this UVN is dynamically created or maintained, taking into account public IP traffic utilization.

[0082] In this context, a two-step PDR / FAR rule is introduced. When the terminal device router joins the UVN, the UPF 120 can bind the N3 tunnel (FAR) to the same PDR as the upcoming interface of the UE's virtual network group interface.

[0083] Figure 4An example of implanting a 2-step PDR / FAR rule according to some example embodiments of this disclosure is shown. When packet 401 arrives, in N6 processing, PDR 410 installed in the UPF (e.g., the destination IP address is set to the UE IP address or the IP address of a host behind the UE) can be directed to FAR 420, which sends the packet to a UVN internal interface (e.g., by setting the destination interface to "UVN Group ID #1"). Then, in N3 processing, PDR 430 installed at the UPF UVN internal interface (e.g., the source interface is set to "UVN Group ID #1") detects the packet, finds FAR 440, and forwards it to the correct N3 path. Based on various example embodiments of this disclosure, UPF 120 can perform FAR selection based on the UVN internal interface, which can be based on different criteria, such as packet replication, N3 path priority, and / or dynamic latency.

[0084] Furthermore, PFCP N4 sessions can be created, deleted, or modified at the UPF 120. For example, if the SMF 110 sends a PFCP session establishment / deletion request to the UPF 120, the UPF 120 can check if any sessions exist within the router group identifier (e.g., a shared router group identifier). If they exist, the UPF 120 can add or remove an N3 PDR to an existing router interface. If they do not exist, the UPF 120 can create a unique virtual interface for the UVN for the PFCP session request and create the PDR and FAR.

[0085] SMF 110 can also send a PFCP session modification request to UPF 120, which can indicate the old router group identifier and the new router group identifier. UPF 120 can check if any sessions exist within the old router group identifier. If they do, UPF 120 can delete the N3 PDR associated with that old router group identifier and associate the N6 PDR with the interface corresponding to the new router group identifier.

[0086] If no session exists, the UPF 120 can check if any sessions exist within the new router group identifier. If a session exists within the new router group identifier, the UPF 120 can add the N3 PDR and N6 PDR to the new router group identifier. If no session exists within the new router group identifier, the UPF 120 can create a unique virtual interface for the UVN for PFCP session modification requests and create the PDR and FAR.

[0087] Therefore, various example implementations can allow the dynamic creation of UVN internal interfaces within a UPF based on subscription or local configuration. Multiple UVN internal interfaces can be created within a UPF by adding a unique UVN group suffix to the UVN internal interface name. Because the UVN group identifier is subscription-driven, multiple SMFs can manage the same UVN group.

[0088] Figure 5 A flowchart is shown of an example method 500 for UE virtual network group management according to some example embodiments of the present disclosure. Method 500 can be implemented by an apparatus. The apparatus can be configured as... Figure 1 The operation of the SMF 110. For example, the device can be configured to perform one or more functions of the SMF 110. For the purposes of discussion, reference will be made to... Figure 1 Description method 500.

[0089] At 510, a request associated with session management is identified, indicating a shared router group identifier, wherein the terminal device routers belong to a virtual network, and one or more terminal device routers belonging to the virtual network share the same shared router group identifier. At position 520, a request associated with the Packet Forwarding Control Protocol (PFCP) session is sent to UPF 120, the request indicating at least the shared router group identifier.

[0090] In some example embodiments, the request associated with the PFCP session instructs the UPF to perform the following: create an interface at the UPF for the virtual network associated with the shared router group identifier; install Packet Detection Rules (PDR) and Forwarding Action Rules (FAR) for packets received at the N6 path; and associate the PDR and FAR with the virtual network interface.

[0091] In some example embodiments, if it is determined that a request associated with another session management of another end device router is triggered and the subscription data associated with the other session management indicates a shared router group identifier, the device may send a request associated with another PFCP session to the UPF, wherein the UPF is instructed to perform: adding another FAR for packets at another N3 path associated with another end device router; and associating the other FAR with a virtual network interface.

[0092] In some example embodiments, the PFCP session between the terminal device router and the UPF for packets associated with the terminal device router, and another PFCP session between the device and the UPF for packets associated with the other terminal device router, have different PFCP session identifiers.

[0093] In some example embodiments, the request associated with the PFCP session instructs the UPF to remove the PDR at the N3 path associated with the PFCP session of the terminal device router.

[0094] In some example embodiments, the request associated with the PFCP session instructs the UPF to remove the PDR at both the N6 path and the N3 path associated with the PFCP session of the terminal device router and / or associate the PDR at both the N6 path and the N3 path associated with the PFCP session with another virtual network associated with another shared router group identifier.

[0095] In some example embodiments, requests associated with a PFCP session include: requests to establish a PFCP session, requests to modify a PFCP session, or requests to delete a PFCP session.

[0096] Figure 6 A flowchart of an example method 600 for UE virtual network group management according to some example embodiments of the present disclosure is shown. Method 600 can be implemented by an apparatus. The apparatus can be configured as... Figure 1 The device operates using a UPF 120. For example, the device can be configured to perform one or more functions of the UPF 120. For discussion purposes, see references. Figure 1 Description method 600.

[0097] At 610, the device receives from SMF 110 a request associated with a Packet Forwarding Control Protocol (PFCP) session, the request indicating at least a shared router group identifier associated with an end device router, wherein the end device router belongs to a virtual network, and one or more end device routers belonging to the virtual network share the same shared router group identifier.

[0098] At 620, the device performs operations associated with the PFCP session based at least on the shared router group identifier.

[0099] In some example embodiments, the apparatus may perform the following based on a request associated with a PFCP session: creating an interface for a virtual network associated with a shared router group identifier, installing packet detection rules (PDR) and forwarding action rules (FAR) for packets at both the N3 and N6 paths associated with the end device router, and associating the created PDR and FAR with the virtual network.

[0100] In some example embodiments, the device may receive a request associated with another PFCP session, which is associated with another end-device router sharing the same shared router group identifier; and based on the request associated with the other PFCP session, perform: adding another FAR for packets at another N3 path associated with the other end-device router; and associating the other FAR with the virtual network.

[0101] In some example embodiments, the device may delete the PDR at the N3 path associated with the PFCP session of the terminal device router based on a request associated with the PFCP session.

[0102] In some example embodiments, the apparatus may, based on a request associated with a PFCP session, remove the PDR at both the N3 and N6 paths associated with the PFCP session of the end device router; and / or associate the PDR at the N3 and N6 paths associated with the PFCP session with another virtual network associated with another shared router group identifier.

[0103] In some example embodiments, requests associated with a PFCP session include: requests to establish a PFCP session, requests to modify a PFCP session, or requests to delete a PFCP session.

[0104] In some example embodiments, if it is determined that a data packet associated with a shared router group identifier is about to arrive, the device may determine the FAR at the N6 path based on the PDR corresponding to the data packet at the N6 path; based on the FAR at the N6 path, cause the data packet to be delivered to the interface for the virtual network associated with the shared router group identifier; and route the data packet based on the PDR and FAR at the N3 path.

[0105] In some example embodiments, at least one of the FAR for the packet at the N3 path associated with the terminal device router and the other FAR for the packet at another N3 path associated with the other terminal device router is active.

[0106] In some example embodiments, the device can monitor the status of one FAR and another FAR based on the General Packet Radio Service Tunneling Protocol - Echo or Quality-of-Service path monitoring.

[0107] In some example embodiments, the device can perform FAR selection for data forwarding from the FAR and the other FAR associated with the interface for the virtual network based on the priority assigned to the FAR and the other FAR.

[0108] In some example embodiments, the priority for the FAR and the other FAR is assigned based on at least one of the following: the corresponding distance of the path associated with the FAR and the other FAR; and the corresponding QoS monitoring latency result associated with the FAR and the other FAR.

[0109] In some example embodiments, the assigned priorities of the FAR and the other FAR are rearranged based at least on the corresponding QoS monitoring latency results associated with the FAR and the other FAR; and the data forwarding is performed based on the rearranged priorities of the FAR and the other FAR.

[0110] In some example embodiments, the apparatus may perform FAR selection for data forwarding from the FAR and the other FAR associated with the interface for the virtual network based on at least one of the following: service-aware capabilities associated with the FAR and the other FAR; or load conditions associated with the FAR and the other FAR; or packet replication requirements.

[0111] Figure 7 A flowchart of an example method 700 for UE virtual network group management according to some example embodiments of the present disclosure is shown. Method 700 can be implemented by an apparatus. The apparatus can be configured as... Figure 1 The terminal device router 130 operates. For example, the device can be configured to perform one or more functions of the terminal device router 130. For discussion purposes, see references to... Figure 1 Description method 700.

[0112] At 710, the device provides a session management-related request to SMF 110, the request indicating a shared router group identifier, wherein the device belongs to a virtual network, and one or more devices belonging to the virtual network share the same shared router group identifier.

[0113] In some example implementations, requests associated with session management include: requests to establish a session, requests to modify a PFCP session, or requests to delete a PFCP session.

[0114] In some example embodiments, the apparatus configured to perform method 500 may include components for performing corresponding steps of method 500. The apparatus may be configured as...Figure 1 The device can be configured to perform one or more functions of the SMF 100. It can be implemented in any suitable form; for example, it can be implemented in a circuit or software module.

[0115] In some example embodiments, the apparatus includes: components for determining the existence of a request associated with session management, the request indicating a shared router group identifier, wherein the terminal device routers belong to a virtual network and one or more terminal device routers belonging to the virtual network share the same shared router group identifier; and components for sending a request associated with a Packet Forwarding Control Protocol (PFCP) session to the User Plane Function (UPF), the request indicating at least the shared router group identifier.

[0116] In some example embodiments, the request associated with the PFCP session instructs the UPF to perform at least one of the following: create an interface at the UPF for the virtual network associated with the shared router group identifier; install packet detection rules (PDR) and forwarding action rules (FAR) for DL ​​packets at the N3 and N6 paths associated with the PDCP session of the end device router; and associate the created PDR and FAR with the virtual network.

[0117] In some example embodiments, the apparatus may further include a component for sending a request associated with another PFCP session to the UPF if it is determined that an interface for the virtual network associated with the shared router group identifier exists, the request instructing the UPF to perform at least one of the following: adding another FAR for a packet at another N3 path associated with another end device router; or associating the other FAR with the virtual network.

[0118] In some example embodiments, the PFCP session between the device and the UPF for packets associated with the terminal device router, and another PFCP session between the device and the UPF for packets associated with the other terminal device router, have different PFCP session identifiers.

[0119] In some example embodiments, the request associated with the PFCP session instructs the UPF to remove the PDR at the N3 path associated with the PFCP session of the terminal device router.

[0120] In some example embodiments, a request associated with a PFCP session indicates the removal of the PDR at both the N3 path and the N6 path associated with the PFCP session of the terminal device router; and / or the association of the PDR at both the N3 path and the N6 path associated with the PFCP session to another virtual network associated with another shared router group identifier.

[0121] In some example embodiments, requests associated with a PFCP session include: requests to establish a PFCP session, requests to modify a PFCP session, or requests to delete a PFCP session.

[0122] In some example embodiments, the apparatus configured to perform method 600 may include components for performing corresponding steps of method 600. The apparatus may be configured as... Figure 1 The device operates using the UPF 120. For example, the device can be configured to perform one or more functions of the UPF 120. The device can be implemented in any suitable form. For example, the device can be implemented in a circuit or software module.

[0123] In some example embodiments, the apparatus includes: components for receiving a request associated with a Packet Forwarding Control Protocol (PFCP) session from a Session Management Function (SMF), the request indicating at least a shared router group identifier associated with an end device router, wherein the end device router belongs to a virtual network, and one or more end device routers belonging to the virtual network share the same shared router group identifier; and components for performing operations associated with the PFCP session at least based on the shared router group identifier.

[0124] In some example embodiments, the components for performing operations associated with a PFCP session may include components for performing at least one of the following based on a request associated with the PFCP session: creating an interface for the virtual network associated with the shared router group identifier, installing packet detection rules (PDR) and forwarding action rules (FAR) for DL ​​packets at both the N3 and N6 paths associated with the PFCP session of the terminal device router, or associating the created PDR and FAR with the virtual network.

[0125] In some example embodiments, the apparatus may further include: components for receiving a request associated with another PFCP session of another end device router sharing the shared router group identifier; and components for performing at least one of the following based on the request associated with the other PFCP session: adding another FAR for a packet at another N3 path associated with the other PFCP session of the other end device router; or associating the other FAR with a created PDR of the virtual network.

[0126] In some example embodiments, at least one of the FAR for the packet at the N3 path associated with the terminal device router and the other FAR for the packet at another N3 path associated with the other terminal device router is active.

[0127] In some example embodiments, the apparatus may further include: components for deleting the PDR at both the N3 path and the N6 path associated with the PFCP session of the terminal device router based on the request associated with the PFCP session; and / or components for associating the PDR at both the N3 path and the N6 path associated with the PFCP session to another virtual network associated with another shared router group identifier.

[0128] In some example embodiments, requests associated with a PFCP session include: requests to establish a PFCP session, requests to modify a PFCP session, or requests to delete a PFCP session.

[0129] In some example embodiments, the apparatus may further include components for determining the FAR at the N6 path based on the PDR corresponding to the data packet at the N6 path if it is determined that a data packet associated with the shared router group identifier is imminent; components for causing the data packet to be delivered to the interface for the virtual network associated with the shared router group identifier based on the FAR at the N6 path; and components for routing the data packet based on the PDR and FAR at the N3 path.

[0130] In some example embodiments, the apparatus may also include components for monitoring the status of the FAR and the other FAR based on quality of service path monitoring.

[0131] In some example embodiments, the apparatus may further include components for performing FAR selection for data forwarding from the FAR and the other FAR associated with the interface for the virtual network, based on the priority assigned to the FAR and the other FAR.

[0132] In some example embodiments, the priority for the FAR and the other FAR is assigned based on at least one of the following: the corresponding distance of the path associated with the FAR and the other FAR; or the corresponding QoS monitoring latency result associated with the FAR and the other FAR.

[0133] In some example embodiments, the apparatus may further include components for performing FAR selection for data forwarding from the FAR and the other FAR associated with the interface for the virtual network based on at least one of the following: service-aware capabilities associated with the FAR and the other FAR; or corresponding load conditions associated with the FAR and the other FAR; or packet duplication requirements.

[0134] In some example embodiments, the apparatus may further include: components for rearranging the assigned priorities of the FAR and the other FAR based at least on the corresponding QoS monitoring latency results associated with the FAR and the other FAR; and components for performing the data forwarding based on the rearranged priorities of the FAR and the other FAR.

[0135] In some example embodiments, the apparatus configured to perform method 700 may include components for performing corresponding steps of method 700. The apparatus may be configured to operate as a terminal device router 130. For example, the apparatus may be configured to perform one or more functions of the terminal device router 130. The apparatus may be implemented in any suitable form. For example, the apparatus may be implemented in a circuit or software module.

[0136] In some example embodiments, the apparatus includes components for sending a session management-related request to a Session Management Function (SMF), the request indicating a shared router group identifier, wherein the apparatus belongs to a virtual network, and one or more devices belonging to the virtual network share the same shared router group identifier.

[0137] In some example implementations, requests associated with session management include: requests to establish a session, requests to modify a PFCP session, or requests to delete a PFCP session.

[0138] Figure 8 This is a simplified block diagram of a device 800 that can implement one or more exemplary embodiments of the present disclosure. Device 800 can be configured as a communication device (e.g., SMF 110, UPF 120, or terminal device router 130, such as...) Figure 1 Perform the operation as shown in the image. Figure 8As shown, device 800 includes one or more processors 810, one or more memories 820 coupled to processor 810, and one or more communication modules 840 coupled to processor 810.

[0139] Communication module 840 is used for bidirectional communication. Communication module 840 has one or more communication interfaces to facilitate communication with one or more other modules or devices. A communication interface can represent any interface used for communicating with other network elements. In some example embodiments, communication module 840 may include at least one antenna.

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

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

[0142] Computer program 830 includes computer-executable instructions that are executed by processor 810. The instructions of program 830 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 830 may be stored in memory (e.g., ROM 824). Processor 810 can perform any suitable actions and processes by loading program 830 into RAM 822.

[0143] Example embodiments of this disclosure can be implemented via program 830, such that device 800 can be configured to perform as described in the reference. Figures 2 to 7 Any process discussed in this disclosure. Various exemplary embodiments of this disclosure can also be implemented by hardware or by a combination of software and hardware.

[0144] In some example embodiments, program 830 may be tangibly contained in a computer-readable medium, which may be included in device 800 (such as memory 820) or other storage device accessible to device 800. Device 800 may load program 830 from the computer-readable medium into RAM 822 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation of the medium itself (e.g., tangible, not tactile), rather than a limitation of the persistence of data storage (e.g., RAM vs. ROM).

[0145] Figure 9 An example of a computer-readable medium 900 is shown, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 900 has a program 830 stored thereon.

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

[0147] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions that execute in a device on a target physical or virtual processor, such as those included in a program module, to perform any of the methods described above. A program module may include routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

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

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

[0150] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0151] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or requiring that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specific to particular example embodiments. Unless explicitly stated otherwise, certain features described in the context of a single example embodiment may also be implemented in combination in a single example embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single example embodiment may also be implemented individually or in any suitable sub-combination in multiple example embodiments.

[0152] Although various exemplary embodiments of this disclosure have been described in language specific to structural features and / or methodological actions, it should be understood that the various exemplary embodiments of this disclosure are not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described herein are disclosed as exemplary forms for implementing the various exemplary embodiments of this disclosure.

Claims

1. An apparatus comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions causing the device to at least: A request associated with session management is identified, the request indicating a shared router group identifier, wherein the terminal device routers belong to a virtual network, and one or more terminal device routers belonging to the virtual network share the same shared router group identifier; as well as Send a request associated with a Packet Forwarding Control Protocol (PFCP) session to the User Plane Function (UPF), the request indicating at least the shared router group identifier.

2. The apparatus of claim 1, wherein the request associated with the PFCP session instructs the UPF to perform at least one of the following: At the UPF, an interface is created for the virtual network associated with the shared router group identifier. For DL ​​packets at both the N6 path and N3 path associated with the PFCP session of the terminal device router, install Packet Inspection Rules (PDR) and Forwarding Action Rules (FAR), or Associate the created PDR and FAR with the virtual network.

3. The apparatus of claim 2, wherein the apparatus causes: If it is determined that an interface exists for the virtual network associated with the shared router group identifier, a request associated with another PFCP session is sent to the UPF, the request instructing the UPF to perform at least one of the following: Add another FAR to the virtual network for packets at another N3 path associated with another terminal device router.

4. The apparatus of claim 3, wherein the PFCP session between the apparatus and the UPF for packets associated with the terminal device router, and another PFCP session between the apparatus and the UPF for packets associated with the other terminal device router, have different PFCP session identifiers.

5. The apparatus of claim 2, wherein the request associated with the PFCP session instructs the UPF to remove the PDR at the N3 path associated with the PFCP session of the terminal device router.

6. The apparatus of claim 2, wherein the request associated with the PFCP session instructs the UPF to perform at least one of the following: Delete the PDR at both the N3 path and the N6 path associated with the PFCP session of the terminal device router; or The PDR at both the N3 path and the N6 path associated with the PFCP session will be associated with another virtual network associated with another shared router group identifier.

7. The apparatus according to any one of claims 1-6, wherein the request associated with the PFCP session comprises: The request used to establish the PFCP session, Requests used to modify the PFCP session, or A request to delete the PFCP session.

8. An apparatus comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions causing the device to at least: The Session Management Function (SMF) receives a request associated with a Packet Forwarding Control Protocol (PFCP) session, the request indicating at least a shared router group identifier associated with an end device router, wherein the end device router belongs to a virtual network, and one or more end device routers belonging to the virtual network share the same shared router group identifier. as well as The operation associated with the PFCP session is performed based on the shared router group identifier.

9. The apparatus of claim 8, wherein the apparatus causes: Perform at least one of the following based on the request associated with the PFCP session: Create an interface for the virtual network associated with the shared router group identifier. For DL ​​packets at both the N3 and N6 paths associated with the PFCP session of the terminal device router, install Packet Inspection Rule (PDR) and Forwarding Action Rule (FAR), or Associate the created PDR and FAR with the virtual network.

10. The apparatus of claim 9, wherein the apparatus causes: Receive a request associated with another PFCP session of another terminal device router sharing the shared router group identifier; and Perform at least one of the following based on the request associated with the other PFCP session: Add another FAR for packets at another N3 path associated with the other PFCP session of the other terminal device router; or Associate the other FAR with the PDR created in the virtual network.

11. The apparatus of claim 10, wherein at least one of the FAR for the packet at the N3 path associated with the terminal device router and the other FAR for the packet at another N3 path associated with the other terminal device router is active.

12. The apparatus of claim 9, wherein the apparatus causes: Based on the request associated with the PFCP session, the PDR at the N3 path associated with the PFCP session of the terminal device router is deleted.

13. The apparatus of claim 9, wherein the apparatus causes: Based on the request associated with the PFCP session, delete the PDR at both the N3 path and the N6 path associated with the PFCP session of the terminal device router; and / or The PDR at both the N3 path and the N6 path associated with the PFCP session is associated with another virtual network associated with another shared router group identifier.

14. The apparatus according to any one of claims 8-13, wherein the request associated with the PFCP session comprises: The request used to establish the PFCP session, Requests used to modify the PFCP session, or A request to delete the PFCP session.

15. The apparatus of claim 8, wherein the apparatus causes: If it is determined that a data packet associated with the shared router group identifier is about to arrive, the FAR at the N6 path is determined based on the PDR corresponding to the data packet at the N6 path; Based on the FAR at the N6 path, the data packets will be delivered to the interface for the virtual network associated with the shared router group identifier; as well as The data packets are routed based on the PDR and FAR at the N3 path.

16. The apparatus of claim 10, wherein the apparatus causes: Based on service quality path monitoring, the status of the FAR and the other FAR is monitored.

17. The apparatus of claim 10, wherein the apparatus causes: Based on the priority assigned to the FAR and the other FAR, FAR selection for data forwarding is performed from the FAR and the other FAR associated with the interface for the virtual network.

18. The apparatus of claim 17, wherein the priority for the FAR and the other FAR is assigned based on at least one of the following: The corresponding distances of the paths associated with the FAR and the other FAR; The corresponding QoS monitoring delay results associated with the FAR and the other FAR.

19. The apparatus of claim 10, wherein the apparatus causes: A FAR selection for data forwarding is performed from the FAR and the other FAR associated with the interface for the virtual network based on at least one of the following: The corresponding service-aware capabilities associated with the FAR and the other FAR; or The corresponding load conditions associated with the FAR and the other FAR; or Requirements for grouped replication.

20. The apparatus of claim 17, wherein the apparatus causes: Based at least on the corresponding QoS monitoring latency results associated with the FAR and the other FAR, the assigned priorities of the FAR and the other FAR are rearranged; and The data forwarding is performed based on the rearranged priorities of the FAR and the other FAR.

21. An apparatus comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions causing the device to at least: Send a session management-related request to the Session Management Function (SMF), the request indicating a shared router group identifier, wherein the device belongs to a virtual network, and one or more devices belonging to the virtual network share the same shared router group identifier.

22. The apparatus of claim 21, wherein the request associated with the session management includes: Requests used to establish a Packet Forwarding Control Protocol (PFCP) session. Requests used to modify the PFCP session, or A request to delete the PFCP session.

23. A method comprising: There is a session management-related request at the Session Management Function (SMF) indicating a shared router group identifier, wherein the terminal device routers belong to a virtual network, and one or more terminal device routers belonging to the virtual network share the same shared router group identifier; as well as Send a request associated with a Packet Forwarding Control Protocol (PFCP) session to the User Plane Function (UPF), the request indicating at least the shared router group identifier.

24. A method comprising: At the User Plane Function (UPF), a request associated with a Packet Forwarding Control Protocol (PFCP) session is received from the Session Management Function (SMF). The request at least indicates a shared router group identifier associated with an end device router, wherein the end device router belongs to a virtual network, and one or more end device routers belonging to the virtual network share the same shared router group identifier. as well as The operations associated with the PFCP session are performed at least based on the shared router group identifier.

25. A method comprising: From the terminal device router, a request associated with session management is sent to the Session Management Function (SMF). The request indicates a shared router group identifier, wherein the device belongs to a virtual network, and one or more devices belonging to the virtual network share the same shared router group identifier.

26. An apparatus comprising: A component for determining the existence of a request associated with session management, the request indicating a shared router group identifier, wherein the terminal device routers belong to a virtual network, and one or more terminal device routers belonging to the virtual network share the same shared router group identifier; as well as A component for sending a request associated with a Packet Forwarding Control Protocol (PFCP) session to the User Plane Function (UPF), the request indicating at least the shared router group identifier.

27. An apparatus comprising: A component for receiving a request associated with a Packet Forwarding Control Protocol (PFCP) session from a Session Management Function (SMF), the request indicating at least a shared router group identifier associated with an end device router, wherein the end device router belongs to a virtual network, and one or more end device routers belonging to the virtual network share the same shared router group identifier; as well as A component for performing operations associated with the PFCP session based at least on the shared router group identifier.

28. An apparatus comprising: A component for sending a session management-related request to the Session Management Function (SMF), the request indicating a shared router group identifier, wherein the device belongs to a virtual network, and one or more devices belonging to the virtual network share the same shared router group identifier.

29. A computer-readable medium comprising instructions that, when executed by a device, cause the device to perform at least the method of claim 23, the method of claim 24, or the method of claim 25.

Images