WO2025030516A1 - Gestion de groupe de réseaux virtuels d'équipement utilisateur - Google Patents

Gestion de groupe de réseaux virtuels d'équipement utilisateur Download PDF

Info

Publication number
WO2025030516A1
WO2025030516A1 PCT/CN2023/112325 CN2023112325W WO2025030516A1 WO 2025030516 A1 WO2025030516 A1 WO 2025030516A1 CN 2023112325 W CN2023112325 W CN 2023112325W WO 2025030516 A1 WO2025030516 A1 WO 2025030516A1
Authority
WO
WIPO (PCT)
Prior art keywords
far
terminal device
session
router
virtual network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/112325
Other languages
English (en)
Inventor
Saubhagya Baliarsingh
Gayathri TADAS
Hua Chao
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to CN202380101329.4A priority Critical patent/CN121753367A/zh
Priority to PCT/CN2023/112325 priority patent/WO2025030516A1/fr
Publication of WO2025030516A1 publication Critical patent/WO2025030516A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • Various example embodiments of this subject disclosure generally relate to the field of telecommunication, and more particularly to devices, methods, apparatuses and computer readable storage media relating to user equipment (UE) virtual network group management.
  • UE user equipment
  • Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) , LTE Evolved UTRAN (E-UTRAN) , LTE-Advanced (LTE-A) , MulteFire, LTE-A Pro, Fifth Generation Mobile Communication Technology (5G) radio access technology or 5G New Radio (NR) access technology, and/or 5G-Advanced.
  • UMTS Universal Mobile Telecommunications System
  • E-UTRAN LTE Evolved UTRAN
  • LTE-A LTE-Advanced
  • MulteFire LTE-A Pro
  • LTE-A Pro Fifth Generation Mobile Communication Technology
  • 5G wireless systems refer to the next generation (NG) of radio systems and network architecture.
  • 5G network technology is mostly based on NR technology, but the 5G (or NG) network can also build on E-UTRAN radio.
  • NR may provide bitrates on the order of 10-20 Gbit/s or higher, and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC) .
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency communication
  • mMTC massive machine-type communication
  • NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivity and massive networking to support the IoT.
  • an apparatus comprising 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 indicating a shared router group identity, wherein the 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 identity; and transmit, to a user plane function (UPF) , a request associated with a packet forwarding control protocol (PFCP) session at least indicating the shared router group identity.
  • UPF user plane function
  • an apparatus comprising 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: receive, from a session management function (SMF) , a request associated with a PFCP session at least indicating a shared router group identity associated with a terminal device router, wherein the 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 identity; and perform an operation associated with the PFCP session at least based on the shared router group identity.
  • SMF session management function
  • an apparatus comprising 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: transmit, to SMF, a request associated with session management indicating a shared router group identity, wherein the apparatus belongs to a virtual network and one or more apparatuses belonging to the virtual network share a same shared router group identity.
  • a method comprises determining, at a SMF, that there is a request associated with session management indicating a shared router group identity, wherein the 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 identity; and transmitting, to a UPF, a request associated with a PFCP session at least indicating the shared router group identity.
  • a method comprises receiving, at a UPF and from a SMF, a request associated with a PFCP session at least indicating a shared router group identity associated with a terminal device router, wherein the 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 identity; and performing an operation associated with the PFCP session at least based on the shared router group identity.
  • a method comprises transmitting, from a terminal device router and to an SMF, a request associated with session management indicating a shared router group identity, wherein the 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 identity.
  • an apparatus comprising means for determining that there is a request associated with session management indicating a shared router group identity, wherein the 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 identity; and means for transmitting, to a UPF, a request associated with a PFCP session at least indicating the shared router group identity.
  • an apparatus comprising means for receiving from a SMF, a request associated with a PFCP session at least indicating a shared router group identity associated with a terminal device router, wherein the 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 identity; and means for performing an operation associated with the PFCP session at least based on the shared router group identity.
  • an apparatus comprising means for transmitting, to a SMF, a request associated with session management indicating a shared router group identity, wherein the apparatus belongs to a virtual network and one or more apparatuses belonging to the virtual network share a same shared router group identity.
  • a computer readable medium having a computer program stored thereon which, when executed by at least one processor of an apparatus, causes the apparatus to carry out the method according to the fourth aspect, the fifth aspect or the sixth aspect.
  • FIG. 1 illustrates an example environment in which example embodiments of the subject disclosure may be implemented
  • FIG. 2 shows a signaling chart illustrating an example of a process according to some example embodiments of the subject disclosure
  • FIG. 3 shows an example of a UE’s session management subscription model according to some example embodiments of the subject disclosure
  • FIG. 4 shows an example of an implementation of a 2-step Packet Detection Rule (PDR) and Forwarding Action Rule (FAR) rule according to some example embodiments of the subject disclosure
  • FIG. 5 shows a flowchart of an example method of a UE virtual network group management according to some example embodiments of the subject disclosure
  • FIG. 6 shows a flowchart of an example method of a UE virtual network group management according to some example embodiments of the subject disclosure
  • FIG. 7 shows a flowchart of an example method of a UE virtual network group management according to some example embodiments of the subject disclosure
  • FIG. 8 shows a simplified block diagram of a device that is suitable for implementing example embodiments of the subject disclosure.
  • FIG. 9 shows a block diagram of an example computer readable medium in accordance with some embodiments of the subject disclosure.
  • references in the subject disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” “some example embodiments, ” “certain example embodiments, ” “various example embodiments, ” and the like indicate that the referenced embodiment (s) described may include particular feature (s) , structure (s) , or characteristic (s) , but it is not necessary that every embodiment or example embodiment described herein includes the particular feature (s) , structure (s) , or characteristic (s) . Moreover, such phrases are not necessarily referring to the same embodiment or same example embodiment.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and one or more intervening steps may be included between “A” and the step.
  • circuitry may refer to one or more or all of the following example embodiments:
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network node, or other computing or network node.
  • the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) , an Enhanced Machine type communication (eMTC) and so on.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • eMTC Enhanced Machine type communication
  • the communications between a terminal device and a network node in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , the sixth generation (6G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Exampel embodiments of the subject disclosure may be applied in various communication systems. Given the rapid development in communications, there will also be future type communication technologies and systems with which the subject disclosure may be embodied. It should not be seen as limiting the scope of the subject disclosure to only the aforementioned communication technologies and systems.
  • the terms “network node” , “radio network node” and/or “radio access network node” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom.
  • the network node may refer to a base station (BS/BTS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network node such as a satellite network node, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite
  • low earth orbit (RAN) split architecture includes a Centralized Unit (CU) and a Distributed Unit (DU) .
  • CU Centralized Unit
  • DU Distributed Unit
  • part of the radio access network node or full of the radio access network node may embark on an airborne or space-borne NTN vehicle.
  • terminal device refers to any end device that may be capable of wireless communication.
  • a terminal device may also be referred to as a communication device, user equipment (UE) , an IP host connected to UE acting as a router, a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • UE user equipment
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and
  • the terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node) .
  • MT Mobile Termination
  • IAB node e.g., a relay node
  • the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
  • resource may refer to any resource for performing communication, for example, a communication between a terminal device and a network node, such as a resource in the time domain, a resource in the frequency domain, a resource in the space domain, a resource in the code domain, or any other resource enabling communication, and the like.
  • a resource in both the frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the subject disclosure are equally applicable to other resources in other domains.
  • Such device may be configured to use a 5G UE as an access router to access 5G services and applications.
  • Certain industrial applications can be time-sensitive. Relying on one UE acting as the router has a certain degree of risk associated therewith, which may lead to single point of failure. Failure at a UE-router could be due to various reasons, such as UE power failure (s) , connectivity failure (s) from the UE to the radio access network (RAN) , line of sight (LOS) problem (s) , overload condition (s) , etc.
  • UE power failure s
  • RAN radio access network
  • LOS line of sight
  • s overload condition
  • various example embodiments of the subject disclosure are further explained with reference to mobile communication devices capable of communication via a wireless cellular system and mobile communication systems serving such mobile communication devices.
  • FIG. 1 shows an example communication network 100 in which example embodiments of the subject disclosure may be implemented.
  • communication network 100 may comprise terminal devices 130-1 and 130-2.
  • Terminal devices 130-1 and 130-2 may connect with 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 without the capability to access the 5G System (5GS) .
  • devices 140-1, 140-2, 140-3 and 140-4 may connect to terminal device 130-1 and/or 130-2 via a network, such as an IP network, a subnetwork, etc., to access the 5GS. That is, terminal device 130-1 and/or 130-2 may act as a router for devices 140-1, 140-2, 140-3 and 140-4.
  • a network such as an IP network, a subnetwork, etc.
  • devices 140-1, 140-2, 140-3 and/or 140-4 may also be referred to as device 140 (more generally) without the capability to access the 5G collectively, whereas terminal devices 130-1 and 130-2 may also be referred to as terminal device routers 130-1 and 130-2, respectively, or a terminal device router 130 (more generally) .
  • Communication network 100 may comprise a core network (CN) 103, which may, for example, comprise one or more network functions (NF) to support a user plane (UP) function, such as User Plane Function (UPF) 120.
  • CN core network
  • NF network functions
  • UPF User Plane Function
  • UPF 120 may be configured to forward traffic communicated between RAN 102 and one or more devices 140 behind the terminal device router 130.
  • the forwarding path between UPF 120 and RAN 102 may be referred to as an N3 path.
  • CN 103 may also include a Session Management Element (SMF) 110 configured to implement a session management function in CN 103.
  • SMF 110 is further configured to interact with the decoupled data plane, create, update, and remove Protocol Data Unit (PDU) sessions, and manage session context with UPF 120.
  • PDU Protocol Data Unit
  • Each of SMF 110 and UPF 120 can be implemented by one or more physical devices, apparatus or servers.
  • CN 103 may also include other NFs, such as an Access and Mobility Management function (AMF) 150
  • AMF 150 may be configured to provide various functions relating to security and access management and authorization.
  • AMF 150 may be configured to receive a new session management request from terminal device router 130 and/or RAN 102 and forward the session management request to SMF 110.
  • CN 103 may further comprise a data network (DN) 160.
  • DN data network
  • the forwarding path between UPF 120 and DN 160 may be referred to as an N6 path.
  • Communication network 100 may include any suitable number of network nodes and terminal devices.
  • Communications in communication network 100 may be implemented according to any proper communication protocol (s) , including, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , 5G, the sixth generation (6G) , and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • s including, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , 5G, the sixth generation (6G) , and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • IEEE Institute for Electrical and Electronics Engineers
  • the communication may utilize any proper wireless communication technology, includes 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 (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and/or any other technologies currently known or to be developed in the future.
  • CDMA Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • TDMA Time Division Multiple Access
  • MIMO Multiple-Input Multiple-Output
  • OFDM Orthogonal Frequency Division Multiple
  • DFT-s-OFDM Discrete Fourier Transform spread OFDM
  • a UE may be used as a router for devices, which do not have 5GS access capability.
  • data transmission requirements for an industrial application may not be satisfied if it relies on only one UE due to the possibility of failure, such as UE power failure (s) , UE-RAN connectivity failure (s) , line of sight problem (s) , overload condition (s) , and so on.
  • failure such as UE power failure (s) , UE-RAN connectivity failure (s) , line of sight problem (s) , overload condition (s) , and so on.
  • the network behind the UE can only be manually configured via framed routes or prefixes delegated to the UE by the Internet Protocol Version 6 (IPv6) prefix delegation.
  • IPv6 Internet Protocol Version 6
  • the framed route feature allows the 5G Core (5GC) to identify the host device subnet present behind UE.
  • the IPv6 prefix represents the IPv6 prefix of the device (s) present behind UE.
  • a controller may be implemented as a software defined networking (SDN) controller.
  • the controller may be configured to collect route or path information to understand network topology and manage flow control.
  • the controller may, for example, consider various downlink (DL) routes present in the 5GC (e.g., CN 130 of FIG. 1) to reach device (s) behind UE that is/are acting as a router. In the case of multiple UE-routers, the controller should collect all the available routing information and then select a route from the collected information based on various network and device conditions.
  • DL downlink
  • the 5GC can determine UEs to be used to forward packets to these devices, based on above-stated support of SMF and UPF. For reliability reasons, the same device (s) behind the UEs can be in the same sub-network, which is reachable via multiple UEs.
  • the SMF 110 may, for example, be configured to control user plane packet forwarding for uplink (UL) and DL traffic detected by a Packet Detection Rule (PDR) by providing a Forwarding Action Rule (FAR) with instructions to UPF 120.
  • UPF 120 can forward the received DL/UL IP packets to/from Protocol Data Unit (PDU) session (s) based on the IP address/prefix provided to UE 130 or an IPv6 Prefix delegated to UE 130 or framed routes associated with UE 130.
  • SMF 110 may be configured to establishe and update the packet processing rules (PDR, FAR, etc. ) applied at UPF 120 via N4 session signalling.
  • Packet forwarding in the 5GC is governed by the Packet Forwarding Control Protocol (PFCP) .
  • SMF 110 may be configured to control packet processing in UPF 120 by establishing, modifying, or deleting PFCP session contexts via the N4 interface between SMF 110 and UPF 120.
  • a PFCP session context corresponds to an individual PDU session and includes PDRs.
  • a PDR shall contain packet detection information (e.g., one or more match fields against which incoming packets are matched) , in addition to one or more FARs, etc.
  • any incoming user plane packet may only match PDRs of a single PFCP session and be forwarded via a single PDU session.
  • An exception is considered for multicast/broadcast traffic, in which UPF 120 continues to look-up other PDRs of the other PFCP sessions matching the packet.
  • the current packet processing flow of the 5GC limits the use of multiple PDU sessions associated with the same set of UEs serving IP hosts behind the UE subnetwork, when forwarding packets to a subnetwork behind UEs.
  • terminal device routers 130-1 and 130-2 of FIG. 1 may be configured to act as a router for a set of devices 140-1, 140-2, 140-3 and 140-4. If they are connected to the same UPF, it will create an overlapping packet detection rule with the same subnet (s) (e.g., framed-route (s) or IPv6 prefix (es) entry) .
  • the UPF may not know which DL tunnel to use these subnet filters for reaching the device (s) behind the UE.
  • one group of terminal device routers (e.g., terminal device routers 130-1 and 130-2 of FIG. 1) is providing IP path management and IP packet forwarding support to IP hosts behind these terminal device routers.
  • another set of terminal device routers (not shown in FIG. 1) may also be configured to provide IP path management and IP packet forwarding support to IP hosts behind these terminal device routers. It means that logically a group of terminal device routers is providing traffic steering support for the same set of IP hosts.
  • each group of terminal device routers providing traffic steering support for the same set of IP hosts may grouped to form one UE Virtual Network (UVN) .
  • UVN UE Virtual Network
  • the SMF may, during establishment or modification of session management for a terminal device router, be configured to determine that there is a request, associated with session management, that indicates a shared router group identity, where the terminal device router belongs to a UVN and one or more terminal device routers belonging to the UVN share a same shared router group identity.
  • a UVN internal interface may be created dynamically within a UPF, based on subscription or local configuration.
  • a UVN internal interface may be implemented as a virtual interface in the UPF and used to collect incoming packets from the N6.
  • the UVN internal interface may used to avoid PDR overlapping at the N6 interface.
  • Various FAR rules with their weightage, replication, and active/standby status can be associated with the UVN internal interface when packet (s) are received.
  • Multiple UVN internal interfaces can be created within a UPF by adding a unique UVN group suffix to the UVN internal interface name to support multiple subnets or even apply different routing rules for different prefixes/subnet behind the UE.
  • the SMF may provide instruction to the UPF on path selection based on path delay, packet duplication, or load balancing requirements, dynamically.
  • the decision process for path selection based on path availability, packet duplication requirement, and load balancing between multiple N3 paths is performed by a policy control function (PCF) /SMF and UPF. This may be based on various information, e.g., application policy requirement for packet duplication for critical service, load balancing between paths based on load and capacity of the path and/or path selection based on priority value based on configured/defined policy.
  • PCF policy control function
  • FIG. 2 shows signaling chart 200 for communication according to some example embodiments of the subject disclosure.
  • signaling chart 200 involves SMF 110 and UPF 120.
  • FIG. 1 shows signaling chart 200.
  • SMF 110 may prepare (202) a PFCP session request. Before that, SMF 110 may, for example, receive a session management subscription request from a terminal device router (e.g., terminal device router 130-1) via an AMF.
  • the session management subscription request may comprise a request for a subscription of a shared router group identity (e.g., sharedRouterGroupDataID) , which may, for example, be indicated in session management subscription data (e.g., SM_Subs_Data) .
  • the shared router group identity may indicate that the terminal device router 130-1 belongs to a virtual network of terminal device routers (e.g., a UVN) .
  • each group of terminal device routers providing traffic steering support for the same set of IP hosts may be grouped to form one UVN.
  • One or more terminal device routers belonging to the UVN may share the same share router group identity. For example, if terminal device router 130-2 also belongs to this UVN, then terminal device router 130-2 may share a share router group identity (e.g., same as that of terminal device router 130-1) .
  • a terminal device if a terminal device is going to act as a router for an end-user device or set of devices that lack capability to access the 5GS, it is to have subscription information in 5GS, which can be controlled by a network operator to add this terminal device as a router device in the network. If the network operator wishes to add more terminal device routers serving the same device set then the terminal device routers must share the common identifier to identify them as a grouped router, which may be referred to as the share router group identity (e.g., sharedRouterGroupDataID as described above) .
  • the shared router group identity may be considered part of the session management subscription data.
  • FIG. 3 shows an example of UE’s session management subscription model according to some example embodiments of the subject disclosure.
  • SMF 110 may be configured to recognize if the terminal device router 130-1 is acting a router and also recognize which terminal device router group it belongs to (e.g., based on the field of the shared router group ID 301 indicated in session management subscription data 310) .
  • a group of terminal devices belonging to the same group identity can be served by UPF 120 (e.g., the same UPF) . Then, UPF selection during one PDU session management procedure may be based on the shared router group identity.
  • shared router group ID 301 may be mapped to shared data 320 comprising a field called “SharedRouterGroupDatas” 303.
  • “SharedRouterGroupDatas” 303 may indicate that shared data 320 may be associated with the data of the shared router group.
  • Shared data 320 may be mapped to router group data 330 comprising a field called “FramedRoute” 304, which may be configured to point to a “FrameRouteInfo” 340.
  • SMF 110 may, after determining and preparing the PFCP session request, transmit (204) a request associated with a PFCP session to UPF 120.
  • the request for the associated PFCP session may indicate the shared router group identity, which was obtained from session management subscription data from a terminal device router. If the shared router group identity is new, the request for the associated with PFCP session may indicate UPF 120 is to create a virtual interface for a UVN associated with the shared router group identity at UPF 120 (which may also be called a UVN internal virtual interface or a UVN virtual interface) .
  • the request associated with the PFCP session may also indicate UPF 120 is to create PDRs and FARs for both incoming packets at the N6 path (e.g., from the DN) and for packets received at the UVN virtual interface.
  • UPF 120 may (206) create a UVN internal virtual interface with an active forwarding path and install UE IP based FAR (s) at the N6 path (e.g., the UE behind routers) .
  • a further terminal device router may be configured to create PDU session and the PDU session request that includes a shared router group identity. If the SMF 120 determines that a UVN virtual interface for a UVN associated with this shared router group identity has already been created at the UPF 120 (e.g., this shared router group identity is same as the shared router group identity included in the PDU Session request from the terminal device router 130-1 and a PFCP session for the terminal device router 130-1 has been created before between SMF and UPF) , the SMF 110 may transmit (204) a request for an establishment or modification of a PFCP session to the UPF 120 indicating that one more FAR should be added for a new N3 path associated with the same UVN virtual interface (e.g., that has been created at the UPF 120) . In this case, the N6 PDR may not be added.
  • UPF 120 may add (208) a new FAR for the new N3 path associated with the UVN virtual interface.
  • SMF 110 may indicate, for example, via a PFCP session establishment or modification request, UPF 120 is to create a new UVN virtual interface for a UVN associated with this new shared router group identify.
  • the PFCP sessions between SMF 110 and UPF 120 for multiple PDUs have different PFCP session IDs, but may include the same router group ID to be treated as UVN group creation, modification, or deletion.
  • UPF 120 may be configured to perform (210) FAR selection for data packet forwarding.
  • UPF 120 may always have at least one FAR present at UVN internal virtual interface to forward packets on an N3 path (e.g., at least one PDU for one of the UE acting as the router is active) .
  • Each FAR may be associated with a priority.
  • UPF 120 may perform FAR selection based on the respective priorities of the FARs.
  • IP path selection for data forwarding, among the IP paths (FARs) associated with the same UVN internal virtual interface may be performed based on the priorities assigned for respective FARs.
  • priority assignment may be performed depending on various aspects, such as a) shortest path; b) quality of service (QoS) monitoring delay result; c) service awareness; and/or d) current load situation on an IP Path.
  • QoS quality of service
  • UPF 120 may be configured to store the status of each FAR based on GTP-echo or QoS path monitoring mechanisms. UPF 120 may further be configured to shuffle the priority of FAR based on the above results if allowed by SMF 110.
  • UPF 120 may be configured to rearrange priority based on QoS monitoring delay result; for instance, a faster path may be chosen by UPF 120 for the data packet forwarding.
  • multiple IP Paths may also have the same priority level to achieve packet replication (duplication) functionality.
  • UVN virtual interface may have multiple FARs pointing towards N3 tunnel towards specific terminal device router. For example, if terminal device routers 130-1 and 130-2 share the same terminal device router group identity when a packet reaches this UVN virtual interface specific to this router group, it may have a FAR pointing towards the N3 tunnel towards terminal device router 130-1 and a further FAR pointing towards the N3 tunnel towards terminal device router 130-2.
  • the SMF 110 may instruct UPF 120 to select and use FAR-based on application awareness, load balancing, packet duplication, path priority, path delay, etc. Furthermore, how a PCF/SMF determines path selection can be based on static or dynamic policy, in view of the network operator’s environment and application demand.
  • a forwarded packet of the PDR/FAR rule may carry various instruction parameters, such as packet duplication (where the packet is duplicated and sent over all the FARs associated with the PDR) , a FAR priority (where the packet is sent only on the highest priority FAR) , a FAR load balancing (where packets are sent based on the weight assigned to each FAR) .
  • packet duplication where the packet is duplicated and sent over all the FARs associated with the PDR
  • FAR priority where the packet is sent only on the highest priority FAR
  • FAR load balancing where packets are sent based on the weight assigned to each FAR
  • a mechanism is proposed by which the 5GS creates and maintains a “UE virtual network group” that logically groups a set of UEs acting as routers for the same set of IP hosts behind an IP subnetwork.
  • the UVN group may, for example, represent a dedicated internal virtual interface within UPF 120, which is mapped to one certain router group. For example, terminal device routers with the same router group identity serve the same set of device (s) behind it.
  • This interface may be used as a forwarding interface for N6 PDRs/FARs. This interface may also act as receiving interface to bind to multiple FARs with the same subnet/prefix towards different N3 (access) tunnels.
  • the UVN group can be dynamically created or maintained upon a new terminal device router joining or a terminal device router leaving the group, which may be triggered by subscription, local configuration, or AF’s request. Therefore, the internal virtual interface associated with the UVN is created or maintained dynamically with consideration of public IP traffic utilization.
  • UPF 120 may bind the N3 tunnel (FAR) to the same PDR as an incoming port for UE virtual network group interface.
  • FIG. 4 shows an example of an implantation of a 2-step PDR/FAR rule according to some example embodiments of the subject disclosure.
  • PDR 410 installed in UPF e.g., destination IP address is set to UE IP address or IP address of a host behind the UE
  • FAR 420 sending packets to a certain UVN internal interface (e.g., by setting destination interface as “UVN group ID#1” ) .
  • PDR 430 installed at the UPF UVN internal interface e.g., source interface is set to “UVN group ID#1”
  • UPF 120 may perform a FAR selection based on the UVN internal interface, which can be based on different criteria, such as packet duplication, priority of N3 path, and/or dynamic delay.
  • the PFCP N4 session may be created, deleted or modified at UPF 120.
  • UPF 120 may check if any session is present within a router group identity (e.g., the shared router group identity) . If present, UPF 120 may add or delete N3 PDR into existing router interfaces. If not present, UPF 120 may create a unique virtual interface for the UVN for PFCP session requests and create PDR and FAR.
  • SMF 110 may transmit to UPF 120 a PFCP session modification request, which may indicate an old router group identity and a new one.
  • UPF 120 may check if any session is present within the old router group identity. If present, UPF 120 may delete the N3 PDR associated with this old router group identity and cause the N6 PDR to be associated with an interface corresponding to the new router group identity.
  • UPF 120 may check if any session is present within the new router group identity. If a session is present within the new router group identity, the UPF 120 may add N3 PDR and N6 PDR to the new router group identity. And if a session is not present within the new router group identity, UPF 120 may create a unique virtual interface for the UVN for PFCP session modification request and create PDR and FAR.
  • UVN internal interface may be created dynamically 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. Since the UVN group identifier is subscription-driven, multiple SMFs can manage the same UVN group.
  • FIG. 5 shows a flowchart of an example method 500 of UE virtual network group management according to some example embodiments of the subject disclosure.
  • Method 500 may be implemented by an apparatus.
  • the apparatus may be configured to operate as SMF 110 of FIG. 1.
  • the apparatus may be configured to perform one or more functions of SMF 110.
  • method 500 will be described with reference to FIG. 1.
  • the apparatus determines that there is a request associated with session management indicating a shared router group identity, wherein the 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 identity.
  • the apparatus transmits, to UPF 120, a request associated with a PFCP session, at least indicating the shared router group identity.
  • the request associated with a PFCP session indicates the UPF is to perform: creating, at the UPF, an interface for the virtual network associated with the shared router group identity, installing a packet detection rule, PDR, and a forwarding action rule, FAR, for packets received at an N6 path; and causing the PDR and FAR to be associated with the virtual network interface.
  • the apparatus may transmit, to the UPF, a request associated with a further PFCP session that indicates the UPF is to perform: adding a further FAR for packets at a further N3 path associated with the further terminal device router; and causing the further FAR to be associated with the virtual network interface.
  • the PFCP session, between the terminal device router and the UPF, for packets associated with the terminal device router, and the further PFCP session, between the apparatus and the UPF, for packets associated with the further terminal device router have different PFCP session identities.
  • the request associated with the PFCP session indicates the UPF is to delete the PDR at the N3 path associated with the PFCP session of the terminal device router.
  • the request may be associated with the modification or deletion of a PFCP session.
  • the request associated with the PFCP session indicates the UPF is to delete the PDR at both the N6 path and at N3 path associated with the PFCP session of the terminal device router; and/or associate the PDR at both the N6 path and N3 path associated with the PFCP session to a further virtual network associated with a further shared router group identity.
  • the request associated with the PFCP session comprises: a request for establishing the PFCP session, a request for modifying the PFCP session, or a request for deleting the PFCP session.
  • FIG. 6 shows a flowchart of an example method 600 of UE virtual network group management according to some example embodiments of the subject disclosure.
  • Method 600 may be implemented by an apparatus.
  • the apparatus may be configured to operate as UPF 120 of FIG. 1.
  • the apparatus may be configured to perform one or more functions of UPF 120.
  • method 600 with be described with reference to FIG. 1.
  • the apparatus receives, from SMF 110, a request associated with a PFCP session at least indicating a shared router group identity associated with a terminal device router, wherein the 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 identity.
  • the apparatus performs an operation associated with the PFCP session at least based on the shared router group identity.
  • the apparatus may perform, based on the request associated with the PFCP session: creating an interface for the virtual network associated with the shared router group identity, installing a packet detection rule, PDR, and a forwarding action rule, FAR, for both packets at a N6 path and at a N3 path associated with the terminal device router, and causing the created PDR and FAR to be associated with the virtual network.
  • the apparatus may receive a request associated with a further PFCP session associated with a further terminal device router sharing the same shared router group identity; and perform, based on the request associated with a further PFCP session: adding a further FAR for packets at a further N3 path associated the further terminal device router; and causing the further FAR to be associated with the virtual network.
  • the apparatus may delete, 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.
  • the apparatus may, based on the request associated with the PFCP session, delete the PDR at both the N6 path and at the N3 path associated with the PFCP session of the terminal device router; and/or associate the PDR at both N6 path and at N3 path associated with the PFCP session to a further virtual network associated with a further shared router group identity.
  • the request associated with the PFCP session comprises: a request for establishing the PFCP session, a request for modifying the PFCP session, or a request for deleting the PFCP session.
  • the apparatus may determine a FAR at the N6 path based on a PDR corresponding to the data packet at the N6 path; cause, based on the FAR at N6 path, the data packet to be delivered to the interface for the virtual network associated with the shared router group identity; and route the data packet based on the PDR and FAR at N3 path.
  • At least one of the FAR for the packets at the N3 path associated with the terminal device router, and the further FAR for the packets at a further N3 path associated with the further terminal device router, is active.
  • the apparatus may monitor the status of the FAR and the further FAR, based on a General Packet Radio Service Tunnelling Protocol-echo or a Quality-of-Service path monitoring.
  • the apparatus may perform a FAR selection for data forwarding from the FAR and the further FAR associated with the interface for the virtual network based on priorities assigned for the FAR and the further FAR.
  • the priorities are assigned for the FAR and the further FAR based on at least one of the following: the respective distances of paths associated with the FAR or the further FAR or respective QoS monitoring delay results associated with the FAR and the further FAR.
  • the apparatus may rearrange the assigned priorities of the FAR and the further FAR, at least based on the respective QoS monitoring delay results associated with the FAR and the further FAR; and perform the data forwarding based on the rearranged priorities of the FAR and the further FAR.
  • the apparatus may perform a FAR selection for data forwarding from the FAR and the further FAR, associated with the interface for the virtual network, based on at least one of the following: the respective capabilities of a service awareness associated with the FAR and the further FAR; or respective load situation associated with the FAR and the further FAR; or a requirement of packet duplication.
  • FIG. 7 shows a flowchart of an example method 700 of UE virtual network group management according to some example embodiments of the subject disclosure.
  • the method 700 may be implemented by an apparatus.
  • the apparatus may be configured to operate as terminal device router 130 of FIG. 1.
  • the apparatus may be configured to perform one or more functions of terminal device router 130.
  • method 700 with be described with reference to FIG. 1.
  • apparatus provides, to SMF 110, a request associated with session management indicating a shared router group identity, wherein the apparatus belongs to a virtual network and one or more terminal device routers belonging to the virtual network share a same shared router group identity.
  • the request associated with the session management comprises: a request for establishing a session, a request for modifying the PFCP session, or a request for deleting the PFCP session.
  • an apparatus configured to perform method 500 may include means for performing the respective steps of the method 500.
  • the apparatus may be configured to operate as SMF 110 of FIG. 1.
  • the apparatus may be configured to perform one or more functions of SMF 100.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for, determining that there is a request associated with session management indicating a shared router group identity, wherein the 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 identity; and means for transmitting, to a UPF, a request associated with a PFCP session at least indicating the shared router group identity.
  • the request associated with the PFCP session indicates the UPF is to perform at least one of the following: creating, at the UPF, an interface for the virtual network associated with the shared router group identity, installing a packet detection rule, PDR and a forwarding action rule, FAR, for DL packets at both N6 path and at N3 path associated with the PFCP session of the terminal device router, or associating the created PDR and FAR to the virtual network.
  • the apparatus may further comprise means for, in accordance with a determination that the interface for the virtual network associated with the shared router group identity exist, transmit, to the UPF, a request, associated with a further PFCP session, that indicates the UPF is to perform at least one of the following: adding a further FAR for packets at a further N3 path associated with the further terminal device router; or associating the further FAR to the virtual network.
  • the PFCP session between the apparatus and the UPF for packets associated with the terminal device router and the further PFCP session between the apparatus and the UPF for packets associated with the further terminal device router have different PFCP session identities.
  • the request associated with the PFCP session indicates the UPF is to delete the PDR at the N3 path associated with the PFCP session of the terminal device router.
  • the request, associated with the PFCP session indicates the UPF is to delete the PDR at both the N6 path and at the N3 path associated with the PFCP session of the terminal device router; and/or associate the PDR at both N6 path and at N3 path associated with the PFCP session to a further virtual network associated with a further shared router group identity.
  • the request associated with the PFCP session comprises: a request for establishing the PFCP session, a request for modifying the PFCP session, or a request for deleting the PFCP session.
  • an apparatus configured to perform method 600 may include means for performing the respective steps of the method 600.
  • the apparatus may be configured to operate as UPF 120 of FIG. 1.
  • the apparatus may be configured to perform one or more functions of UPF 120.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for receiving from a SMF, a request associated with a PFCP session at least indicating a shared router group identity associated with a terminal device router, wherein the 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 identity; and means for performing an operation associated with the PFCP session at least based on the shared router group identity.
  • the means for performing the operation associated with the PFCP session may comprise means for performing, based on the request associated with the PFCP session, at least one of the following: creating an interface for the virtual network associated with the shared router group identity, installing a PDR and a FAR for both packets at a N6 path and at a N3 path associated with the PFCP session of the terminal device router, or associating the created PDR and FAR to the virtual network.
  • the apparatus may further comprise means for receiving, a request associated with a further PFCP session of a further terminal device router sharing the shared router group identity; and means for performing, based on the request associated with the further PFCP session, at least one of the following: adding a further FAR for packets at a further N3 path associated the further PFCP session of the further terminal device router; or associating the further FAR to the created PDR of the virtual network.
  • At least one of the FAR for the packets at the N3 path associated with the terminal device router and the further FAR for the packets at a further N3 path associated with the further terminal device router is active.
  • the apparatus may further comprise means for, based on the request associated with the PFCP session, deleting the PDR at both N6 path and at N3 path associated with the PFCP session of the terminal device router; and/or means for associating the PDR at both N6 path and at N3 path associated with the PFCP session to a further virtual network associated with a further shared router group identity.
  • the request associated with the PFCP session comprises: a request for establishing the PFCP session, a request for modifying the PFCP session, or a request for deleting the PFCP session.
  • the apparatus may further comprise means for, in accordance with a determination that a data packet associated with the shared router group identity is incoming, determining a FAR at N6 path based on a PDR corresponding to the data packet at N6 path; means for causing, based on the FAR at N6 path, the data packet to be delivered to the interface for the virtual network associated with the shared router group identity; and means for routing the data packet based on the PDR and FAR at N3 path.
  • the apparatus may further comprise means for monitoring the status of the FAR and the further FAR based on a Quality-of-Service path monitoring.
  • the apparatus may further comprise means for performing a FAR selection for data forwarding from the FAR and the further FAR, associated with the interface for the virtual network, based on priorities assigned for the FAR and the further FAR.
  • the priorities are assigned for the FAR and the further FAR based on at least one of the following: the respective distances of paths associated with the FAR and the further FAR; or respective QoS monitoring delay results associated with the FAR and the further FAR.
  • the apparatus may further comprise means for performing a FAR selection for data forwarding from the FAR and the further FAR, associated with the interface for the virtual network, based on at least one of the following: the respective capabilities of a service awareness associated with the FAR and the further FAR; or respective load situation associated with the FAR and the further FAR; or a requirement of packet duplication.
  • the apparatus may further comprise means for rearranging the assigned priorities of the FAR and the further FAR at least based on the respective QoS monitoring delay results associated with the FAR and the further FAR; and means for performing the data forwarding based on the rearranged priorities of the FAR and the further FAR.
  • an apparatus configured to perform method 700 may include means for performing the respective steps of method 700.
  • the apparatus may be configured to operate as terminal device router 130.
  • the apparatus may be configured to perform one or more functions of terminal device router 130.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for transmitting, to a SMF, a request associated with session management indicating a shared router group identity, wherein the apparatus belongs to a virtual network and one or more apparatuses belonging to the virtual network share a same shared router group identity.
  • the request associated with the session management comprises: a request for establishing a session, a request for modifying the PFCP session, or a request for deleting the PFCP session.
  • FIG. 8 is a simplified block diagram of device 800 that may implement one or more example embodiments of the subject disclosure.
  • Device 800 may be configured to operate as a communication device (e.g., SMF 110, UPF 120 or terminal device router 130, as shown in FIG. 1) .
  • 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.
  • Communication module 840 is for bidirectional communications.
  • Communication module 840 has one or more communication interfaces to facilitate communication with one or more other modules or devices.
  • the communication interfaces may represent any interface that is utilized for communication with other network elements.
  • communication module 840 may include at least one antenna.
  • Processor 810 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting and illustrative examples.
  • Device 800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • Memory 820 may include one or more non-volatile memories and one or more volatile memories.
  • Examples of the non-volatile memories include, but are not limited to, Read Only Memory (ROM) 824, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and/or optical storage.
  • Examples of the volatile memories include, but are not limited to, random access memory (RAM) 822 and other volatile memories that will not last in the power-down duration.
  • Computer program 830 includes computer executable instructions that are executed by processor 810.
  • the instructions of program 830 may include instructions for performing operations/acts of some example embodiments of the subject disclosure.
  • Program 830 may be stored in the memory, e.g., ROM 824.
  • Processor 810 may perform any suitable actions and processing by loading program 830 into RAM 822.
  • the example embodiments of the subject disclosure may be implemented by means of program 830 so that device 800 may be configured to perform any process of the disclosure as discussed with reference to FIG. 2 to FIG. 7.
  • the various example embodiments of the subject disclosure may also be implemented by hardware or by a combination of software and hardware.
  • program 830 may be tangibly contained in a computer readable medium which may be included in device 800 (such as, in the memory 820) or other storage devices that are accessible by device 800.
  • Device 800 may load program 830 from the computer readable medium to RAM 822 for execution.
  • the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • the term “non-transitory, ” as used herein, is a limitation of the medium itself (e.g., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs.ROM) .
  • FIG. 9 shows an example of computer readable medium 900 which may be in form of CD, DVD or other optical storage disk.
  • the computer readable medium 900 has the program 830 stored thereon.
  • Various example embodiments of the subject disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the subject disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting and illustrative examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • Some example embodiments of the subject 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, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above.
  • Program modules may include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the subject 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 the program code, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable medium, and the like.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Divers modes de réalisation donnés à titre d'exemple de la présente invention se rapportent à des dispositifs, à des procédés, à des appareils et à des supports de stockage lisibles par ordinateur d'une gestion de groupe de réseaux virtuels d'équipement utilisateur (UE). Par exemple, le procédé peut consister à déterminer, au niveau d'une fonction de gestion de session (SMF), qu'il existe une demande associée à une gestion de session indiquant une identité de groupe de routeurs partagés, le routeur de dispositif terminal appartenant à un réseau virtuel et un ou plusieurs routeurs de dispositif terminal appartenant au réseau virtuel partageant une même identité de groupe de routeurs partagés ; et à transmettre, à une fonction de plan utilisateur (UPF), une demande associée à une session de protocole de commande de transfert de paquets (PFCP) indiquant au moins l'identité de groupe de routeurs partagés.
PCT/CN2023/112325 2023-08-10 2023-08-10 Gestion de groupe de réseaux virtuels d'équipement utilisateur Pending WO2025030516A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202380101329.4A CN121753367A (zh) 2023-08-10 2023-08-10 用户设备虚拟网络组管理
PCT/CN2023/112325 WO2025030516A1 (fr) 2023-08-10 2023-08-10 Gestion de groupe de réseaux virtuels d'équipement utilisateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/112325 WO2025030516A1 (fr) 2023-08-10 2023-08-10 Gestion de groupe de réseaux virtuels d'équipement utilisateur

Publications (1)

Publication Number Publication Date
WO2025030516A1 true WO2025030516A1 (fr) 2025-02-13

Family

ID=94533327

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/112325 Pending WO2025030516A1 (fr) 2023-08-10 2023-08-10 Gestion de groupe de réseaux virtuels d'équipement utilisateur

Country Status (2)

Country Link
CN (1) CN121753367A (fr)
WO (1) WO2025030516A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220022092A1 (en) * 2018-12-12 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Policy node, user plane node, control plane node and methods therein for handling quality of service in a wireless communications network
US20220132623A1 (en) * 2019-02-14 2022-04-28 Telefonaktiebolaget Lm Ericsson (Publ) Enhanced up function requested pfcp association release
CN115835259A (zh) * 2022-09-22 2023-03-21 阿里巴巴（中国）有限公司 用户面功能upf设备、报文处理方法及设备
US20230164641A1 (en) * 2020-04-02 2023-05-25 Interdigital Patent Holdings, Inc. Extended 5g local area network interworking with a home network and change of access network for 5g lan connected devices
CN116419423A (zh) * 2021-12-31 2023-07-11 中国移动通信有限公司研究院 一种数据传输方法、装置及设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220022092A1 (en) * 2018-12-12 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Policy node, user plane node, control plane node and methods therein for handling quality of service in a wireless communications network
US20220132623A1 (en) * 2019-02-14 2022-04-28 Telefonaktiebolaget Lm Ericsson (Publ) Enhanced up function requested pfcp association release
US20230164641A1 (en) * 2020-04-02 2023-05-25 Interdigital Patent Holdings, Inc. Extended 5g local area network interworking with a home network and change of access network for 5g lan connected devices
CN116419423A (zh) * 2021-12-31 2023-07-11 中国移动通信有限公司研究院 一种数据传输方法、装置及设备
CN115835259A (zh) * 2022-09-22 2023-03-21 阿里巴巴（中国）有限公司 用户面功能upf设备、报文处理方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Legal Interception support for 5GC SMF/UPF", 3GPP DRAFT; C4-190024_29244_LI, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG4, no. Montreal, CA; 20190301, 15 February 2019 (2019-02-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051598539 *

Also Published As

Publication number Publication date
CN121753367A (zh) 2026-03-27

Similar Documents

Publication Publication Date Title
CN112055959B (zh) 用于通信的方法、装置和介质
US20260039598A1 (en) Methods and apparatus for session steering to application servers
US11611475B2 (en) Association of 3GPP (Third Generation Partnership Project) UPF (User Plane Function) and edge computing application server
WO2024144154A1 (fr) Procédé et appareil de configuration de politique de délestage pour service de bord de vplmn dans un système de communication mobile
CN117354966A (zh) 一种被用于无线通信中的方法和装置
WO2022027478A1 (fr) Procédé et appareil de transfert
CN117917908A (zh) 用于前传的链路聚合
WO2022021239A1 (fr) Notification de réseau concernant le résultat d'authentification et d'autorisation d'un dispositif terminal
WO2025030516A1 (fr) Gestion de groupe de réseaux virtuels d'équipement utilisateur
WO2023212872A1 (fr) Gestion d'interface ip externe dans un nœud de routeur ip 5gs
EP4586582A1 (fr) Commande de politique pour entités de plan de commande
WO2024221305A1 (fr) Traitement de sessions pdu ancré à une upf
US20250175424A1 (en) Ip routing and forwarding operation and management of ip router node
WO2025030344A1 (fr) Mise en vigueur d'isolement pour orientation de trafic d'application
CN116547932A (zh) 用于iab通信的设备、方法、装置和计算机可读介质
WO2024239203A1 (fr) Routeur virtuel dans un système de communication
CN121126352B (zh) 通信方法及通信装置
WO2026031014A1 (fr) Procédés et appareil pour la suppression d'instances d'interface
WO2025091440A1 (fr) Notification de rejet
WO2024243782A1 (fr) Mécanisme de détermination de ressources informatiques périphériques et réseau pour application
WO2025211763A1 (fr) Procédé et appareil d'établissement de session sur la base de données d'utilisateur dans un système de communication sans fil
WO2024098177A1 (fr) Procédure d'authentification pour tranche de réseau
WO2024243828A1 (fr) Adressage et routage de services sensibles au calcul
CN121058262A (zh) 无线电接入网中的协调
WO2023283878A1 (fr) Amélioration de modèle entièrement distribué de tsn

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23948088

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202647026418

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202647026418

Country of ref document: IN