WO2018015785A1 - Procédé et appareil de désagrégation de passerelle de réseau - Google Patents

Procédé et appareil de désagrégation de passerelle de réseau Download PDF

Info

Publication number
WO2018015785A1
WO2018015785A1 PCT/IB2016/054274 IB2016054274W WO2018015785A1 WO 2018015785 A1 WO2018015785 A1 WO 2018015785A1 IB 2016054274 W IB2016054274 W IB 2016054274W WO 2018015785 A1 WO2018015785 A1 WO 2018015785A1
Authority
WO
WIPO (PCT)
Prior art keywords
unit instance
network
instance
subscriber
access
Prior art date
Application number
PCT/IB2016/054274
Other languages
English (en)
Inventor
Alexander Bachmutsky
Srinivas Kadaba
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/IB2016/054274 priority Critical patent/WO2018015785A1/fr
Publication of WO2018015785A1 publication Critical patent/WO2018015785A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols

Definitions

  • Embodiments of the invention relate to the field of networking; and more specifically, to a disaggregated network gateway.
  • Network gateways such as the mobile Packet Data Network Gateway (PDN-GW) and the fixed Broadband Network Gateway (BNG) are essential elements of enabling access to both human users and machines in the future Internet of Things (IoT).
  • Service providers e.g., telecommunication service providers, network service providers, Application service providers, storage service providers, Internet service providers, etc.
  • core network e.g., an enterprise network, a packet data network, the Internet, etc.
  • Network gateways are an integral element of service providers' networks and enable subscribers and/or devices to connect to the network using an access technology (for instance LTE in the case of wireless access and DSL/Cable in the case of fixed access), and provide a subscriber management functionality (authentication, authorization, accounting, and the application of policies).
  • Mobile networks e.g., networks that utilize High Speed Packet Access (HSPA) or Long-Term Evolution (LTE)
  • HSPA High Speed Packet Access
  • LTE Long-Term Evolution
  • PDN-GW fixed access networks
  • a common method of implementing network gateways is through a monolithic component that provides access management and subscribers management functionalities combined into one physical component (e.g., one physical network device).
  • one physical component e.g., one physical network device.
  • VAS value added service
  • any information about devices and/or subscribers is internal to the gateway and not exposed to external applications and/or network devices.
  • a value added service suffers from lack of visibility of the information obtained and processed within the network gateway.
  • GPRS General Packet Radio Service
  • GTP General Packet Radio Service Tunneling Protocol
  • PPPoE Point-to-Point Protocol over Ethernet
  • L2TP Layer 2 Tunneling Protocol
  • a value added service application is located north of the network gateway, towards the core network (e.g., the Internet), this application is limited in the sense that it is at best IP flow aware (based on the source and destination address pairs) as the network gateway interfaces with the core network at this point and outputs flows of IP packets.
  • the VAS application would need to go through the entire processing that was performed in the gateway again in order to reach the subscriber information. In some cases, it would be impossible, as the gateway may prevent access to this information due to internal policies.
  • a VAS application which needs to access further details regarding a subscriber or a device of a subscriber needs much integration effort to access the information from the policy and accounting infrastructure of the network gateway.
  • the integration effort is heavy and tedious enough to be a big deterrent, so the providers of such services resign themselves to being only IP flow aware and not truly subscriber or device aware.
  • the embodiments present a disaggregated network gateway enabling the dynamic and flexible incorporation of services at a proper location within the processing flow of traffic in a network gateway without compromising the fundamental structure of the network gateway.
  • the embodiments enable service providers to avail themselves of the rich functionality possible with access to subscriber and device related information available to the network gateway. Further, the embodiments enable independent scalability of different functions performed at the network gateway rendering the network gateway adaptable to a varying number of subscriber/devices serviced as well as an independently varying number of flows handled.
  • the network gateway system includes an access unit instance to receive or forward traffic from one or more user devices, and to determine device information associated with the received or forwarded traffic; a subscriber unit instance to perform at least one of identification, authentication and authorization of a subscriber's session associated with the received or forwarded traffic, and to determine subscriber information associated with the received or forwarded traffic; a network unit instance to receive or forward the received or forwarded traffic towards the core packet data network, and to determine network information associated with the received or forwarded traffic; an application unit instance to process the received or forwarded traffic; a gateway control mechanism to configure and manage the access unit instance, the subscriber unit instance, the application unit instance, and the network unit instance; and an internal communication mechanism to enable each one of the access unit instance, the subscriber unit instance, the application unit instance, and the network unit instance to expose the device information, the subscriber information, the network information, and a result of processing of the received or forwarded traffic at
  • One general aspect includes a method in a network gateway system located between an access network and a core packet data network of a carrier network.
  • the method includes receiving, at an access unit instance, traffic from one or more user device; determining, at the access unit instance, device information associated with the received traffic; performing, at a subscriber unit instance, at least one of identification, authentication and authorization of a subscriber's session associated with the received traffic; determining, at the subscriber unit instance, subscriber information associated with the received traffic; forwarding, from a network unit instance, the received traffic towards the core packet data network; determining, at the network unit instance, network information associated with the received traffic; and exposing the device information, the subscriber information, the network information, and a result of processing of the traffic at an application unit instance to other ones of the access unit instance, the subscriber unit instance, the network unit instance, and the application unit instance, where each one of the access unit instance, the subscriber unit instance, the network unit instance and the application unit instance is separately implemented and separately scalable from the other ones of the access unit
  • One general aspect includes a non-transitory computer readable storage medium that provides instructions, which when executed by one or more processors of a network gateway system located between an access network and a core packet data network of a carrier network, cause the one or more processor(s) to perform operations including: receiving, at an access unit instance, traffic from one or more user device; determining, at the access unit instance, device information associated with the received traffic; performing, at a subscriber unit instance, at least one of identification, authentication and authorization of a subscriber's session associated with the received traffic; determining, at the subscriber unit instance, subscriber information associated with the received traffic; forwarding, from a network unit instance, the received traffic towards the core packet data network; determining, at the network unit instance, network information associated with the received traffic; and exposing the device information, the subscriber information, the network information, and a result of processing of the traffic at an application unit instance to other ones of the access unit instance, the subscriber unit instance, the network unit instance, and the application unit instance, where each one of the access
  • One general aspect includes a method in a network gateway system located between an access network and a core packet data network of a carrier network.
  • the method includes receiving, at a network unit instance, traffic from the core packet data network; determining, at the network unit instance, network information associated with the received traffic; performing, at a subscriber unit instance, at least one of identification, authentication and authorization of a subscriber's session associated with the received traffic; determining, at the subscriber unit instance, subscriber information associated with the received traffic; forwarding, from an access unit instance, the received traffic towards the access network; determining, at the access unit instance, device information associated with the received traffic; and exposing the device information, the subscriber information, the network information, and a result of processing of the traffic at an application unit instance to other ones of the access unit instance, the subscriber unit instance, the network unit instance, and the application unit instance, wherein each one of the access unit instance, the subscriber unit instance, the network unit instance and the application unit instance is separately implemented and separately scalable from the other ones of the access unit instance
  • One general aspect includes a non-transitory computer readable storage medium that provides instructions, which when executed by one or more processors of a network gateway system located between an access network and a core packet data network of a carrier network, cause the one or more processor(s) to perform operations including: receiving, at a network unit instance, traffic from the core packet data network; determining, at the network unit instance, network information associated with the received traffic; performing, at a subscriber unit instance, at least one of identification, authentication and authorization of a subscriber's session associated with the received traffic; determining, at the subscriber unit instance, subscriber information associated with the received traffic; forwarding, from an access unit instance, the received traffic towards the access network; determining, at the access unit instance, device information associated with the received traffic; and exposing the device information, the subscriber information, the network information, and a result of processing of the traffic at an application unit instance to other ones of the access unit instance, the subscriber unit instance, the network unit instance, and the application unit instance, wherein each one of the access unit
  • Figure 1 illustrates a disaggregated network gateway system according to some embodiments.
  • Figure 2 illustrates a block diagram of an exemplary disaggregated network gateway according to some embodiments.
  • FIG. 3 is a diagram of one embodiment of a physical disaggregated network gateway system according to some embodiments.
  • Figure 4 is a diagram of one embodiment of a network device that can implement one or more virtual disaggregated gateway units (DGUs) that can be part of a network gateway system according to some embodiments.
  • DGUs virtual disaggregated gateway units
  • Figure 5 illustrates an exemplary flow diagram of operations performed in a network gateway system located between an access network and a core packet data network of a carrier network when traffic is received from user devices according to some embodiments.
  • Figure 6 illustrates an exemplary flow diagram of operations performed in a network gateway system located between an access network and a core packet data network of a carrier network when traffic is received from the core network according to some embodiments.
  • references in the specification to "one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • Bracketed text and blocks with dashed borders may be used herein to illustrate optional operations that add additional features to embodiments of the invention. However, such notation should not be taken to mean that these are the only options or optional operations, and/or that blocks with solid borders are not optional in certain embodiments of the invention.
  • the terms “coupled” and “connected,” along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other.
  • Coupled is used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, co-operate or interact with each other.
  • Connected is used to indicate the establishment of communication between two or more elements that are coupled with each other.
  • the embodiments present a disaggregated network gateway enabling the dynamic and flexible incorporation of services at a proper location within the processing flow of traffic in a network gateway without compromising the fundamental structure of the network gateway.
  • the embodiments enable service providers to avail themselves of the rich functionality possible with access to subscriber and device related information available to the network gateway. Further, the embodiments enable independent scalability of different functions performed at the network gateway rendering the network gateway adaptable to a varying number of subscriber/devices serviced as well as an independently varying number of flows handled.
  • a disaggregation of network gateways based on the separation of functionalities (access, subscriber, application and network) within the network gateway is proposed. These separate pieces of the gateway are connected via control and data communication channels such that they collectively behave within a disaggregated gateway system in the same manner as a monolithic network gateway.
  • the new disaggregated architecture of the network gateway allows for novel deployment and operational options.
  • a network gateway system located between an access network and a core packet data network of a carrier network comprises an access unit instance to receive traffic from one or more user devices, and to determine device information associated with the received traffic; a subscriber unit instance to perform at least one of identification, authentication and authorization of a subscriber's session associated with the received traffic, and to determine subscriber information associated with the received traffic; a network unit instance to forward the received traffic towards the core packet data network, and to determine network information associated with the received traffic; an application unit instance to process the received traffic; a gateway control mechanism to configure and manage the access unit instance, the subscriber unit instance, the application unit instance, and the network unit instance.
  • the network gateway system further includes an internal communication mechanism to enable each one of the access unit instance, the subscriber unit instance and the network unit instance to expose the device information, the subscriber information, the network information, and a result of the processing of the received traffic at the application unit instance to other ones of the access unit instance, the subscriber unit instance, the network unit instance and the application unit instance.
  • Each one of the access unit instance, the subscriber unit instance, the network unit instance, and the application unit instance is separately implemented and separately scalable from the other units of the network gateway system.
  • Figure 1 illustrates a disaggregated network gateway system according to some embodiments.
  • the network gateway system 100 of Figure 1 forms part of a data plane of a carrier network of a service provider.
  • the carrier network may serve various types of user devices (not shown; such as workstations, laptops, netbooks, tablets, palm tops, mobile phones, smartphones, phablets, multimedia phones, Voice Over Internet Protocol (VOIP) phones, terminals, portable media players, GPS units, wearable devices, gaming systems, set-top boxes, Internet of Things (IoT) devices (e.g., Internet enabled household appliances, wireless or wired sensing devices, smart cars, etc.)).
  • IoT Internet of Things
  • These user devices may be coupled to the network gateway (directly or through other networks such as access networks (e.g., access network 101)) to communicate over the carrier network (e.g., the Internet or virtual private networks (VPNs) overlaid on (e.g., tunneled through) the Internet) with each other (directly or through servers) and/or access content and/or services.
  • networks e.g., access network 101
  • VPNs virtual private networks
  • Such content and/or services are typically provided by one or more servers (not shown) belonging to a service/content provider or one or more end user devices (not shown) participating in a peer-to-peer (P2P) service, and may include, for example, public webpages (e.g., free content, store fronts, search services), private webpages (e.g., username/password accessed webpages providing email services), and/or corporate networks over VPNs.
  • public webpages e.g., free content, store fronts, search services
  • private webpages e.g., username/password accessed webpages providing email services
  • corporate networks e.g., corporate networks over VPNs.
  • end user devices may be coupled (e.g., through customer premise equipment coupled to an access network (wired or wirelessly)) to the network gateway system 100, which is coupled (e.g., through one or more core network devices (NDs) of the core network 103) to other edge NDs, which are coupled to electronic devices acting as servers.
  • the network gateway system 100 receives traffic from a user electronic device and forwards it towards a packet data network enabling users and/or devices to access
  • the network gateway system 100 can receive traffic from the core network 103 to be forwarded towards the user electronic device.
  • the network gateway system 100 includes a gateway control 116, coupled with an access unit 106, a subscriber unit 108, a network unit 110, an internal communication mechanism 112 and one or more application units 114.
  • the gateway control 116 includes a gateway controller 102 and a gateway manager 104.
  • Each one of the access unit 106, the subscriber unit 108, the network unit 110, and the application unit 114 is a self-contained component of the network gateway that can be referred to as a disaggregated gateway unit (DGU) as will be described in further details with reference to Figures 3-4.
  • DGU disaggregated gateway unit
  • While the network gateway system 100 is illustrated including a single one of each DGU, the present embodiments are not so limited. Some embodiments, may include any number of units for each one of the DGU.
  • the gateway control 116 orchestrates and manages the set of components of the network gateway enabling them to collectively operate and to provide coherent gateway functionalities (e.g., providing access and subscriber management functionalities to a carrier network as well as additional services (through the application unit 114) tailored to the needs of the service provider administrating the carrier network or to customers of the services provider).
  • coherent gateway functionalities e.g., providing access and subscriber management functionalities to a carrier network as well as additional services (through the application unit 114) tailored to the needs of the service provider administrating the carrier network or to customers of the services provider).
  • the gateway control 116 includes two separate components : 1) the gateway controller 102, that is used to configure the components of the network gateway system 100 (i.e., configure the access unit 106 to operate according to a set of access network protocols; configure the subscriber unit 108 to process traffic according to a set of subscriber accounts; configure the network unit 110 to operate according to a set of network protocols for interfacing with the core network 103, and configure the application unit 114 according to a desired value added service that is to be offered to the subscribers of a service); and 2) the gateway manager 104 that is used to perform a variety of management tasks.
  • the gateway manager 104 is operative to perform statistics collections (e.g., statistics collection for each one of the disaggregated units, for each flow, per subscriber, etc.); manage the administrative rights corresponding to each component of the network gateway, enabling different
  • FIG. 1 illustrates dashed lines coupling the gateway control 116 with the other units of the network gateway system 100, these lines are representative of control and data communication mechanisms between the gateway control and the units of the network gateway. This communication mechanism is not optional.
  • the access unit 106 handles all operations related to the access network (coupling the user device, or user equipment to the network gateway). For example, the access unit 106 is operative to terminate one or more network protocols between the user device and the network gateway system 100 (e.g., such as the point-to-point protocol over another protocol (PPPoX) (e.g., where X is Ethernet or Asynchronous Transfer Mode (ATM)), Ethernet, 802.1Q Virtual LAN (VLAN), Internet Protocol, or ATM).
  • PPPoX point-to-point protocol over another protocol
  • ATM 802.1Q Virtual LAN
  • ATM Virtual LAN
  • the access unit 106 receives traffic from a single electronic device (not shown; such as end user devices including workstations, laptops, netbooks, tablets, palm tops, mobile phones, smartphones, phablets, multimedia phones, Voice Over Internet Protocol (VOIP) phones, terminals, portable media players, GPS units, wearable devices, gaming systems, set-top boxes, Internet of Things (IoT) devices (e.g., Internet enabled household appliances, wireless or wired sensing devices, etc.)).
  • VOIP Voice Over Internet Protocol
  • IoT Internet of Things
  • the access unit receives traffic from another network device that aggregates traffic from multiple electronic devices (e.g., a home gateway device to which one or more end user devices are coupled, or a gateway located at a manufacturing site to which one or more sensing devices are coupled, etc.).
  • the access unit 106 provides device identification services for the other units of the network gateway system and exposes device information (e.g., Media Access Control (MAC) address of the user device, access technology used to couple to the network gateway system 100, device type and capabilities, etc.) to the other units of the network gateway system.
  • the device information can be delivered to the other units of the network gateway system via a response to an explicit request received from the other unit(s) and transmitted via the internal communication mechanism 112.
  • the device information can be delivered to the other units of the network gateway system as a form of metadata with device identification information correlated to a particular packet or processing stream, and forwarded to the other unit(s) via the internal communication mechanism 112.
  • an access unit 106 may include multiple instances, where each instance handles a different subset of user devices connecting to the network gateway system 100.
  • Subscriber unit 108 includes functionality for authentication, authorization, and accounting (AAA) protocols (e.g., RADIUS (Remote Authentication Dial-In User Service), Diameter, and/or TACACS+ (Terminal Access Controller Access Control System Plus)).
  • AAA authentication, authorization, and accounting
  • Authentication is the process of identifying and verifying a subscriber. For instance, a subscriber might be identified by a combination of a username and a password or through a unique key. Authorization determines what a subscriber can do after being authenticated, such as gaining access to certain electronic device information resources (e.g., through the use of access control policies). Accounting is recording user activity.
  • end user devices may be coupled (e.g., through an access network) through the network gateway system 100 including the subscriber unit 108 (supporting AAA processing). AAA processing is performed to identify for a subscriber the subscriber record stored for that subscriber.
  • a subscriber record includes a set of attributes (e.g., subscriber name, password, authentication information, access control information, rate-limiting information, policing information) used during processing of that subscriber's traffic.
  • the subscriber unit 108 represents end user devices (or sometimes customer premise equipment (CPE) such as a residential gateway (e.g., a router, modem)) using subscriber circuits.
  • CPE customer premise equipment
  • a subscriber circuit uniquely identifies within the subscriber unit 108 a subscriber session and typically exists for the lifetime of the session.
  • a subscriber unit 108 typically allocates a subscriber circuit when the subscriber connects to the network gateway system 100, and correspondingly de-allocates that subscriber circuit when that subscriber disconnects.
  • Each subscriber session represents a distinguishable flow of packets communicated between the network gateway system 100 and an end user device (or sometimes CPE such as a residential gateway or modem) using an access protocol.
  • a subscriber session can be initiated using a variety of mechanisms (e.g., manual provisioning a dynamic host configuration protocol (DHCP), DHCP/client-less internet protocol service (CLIPS) or Media Access Control (MAC) address tracking).
  • DHCP dynamic host configuration protocol
  • CLIPS client-less internet protocol service
  • MAC Media Access Control
  • PPP point-to-point protocol
  • DSL digital subscriber line
  • a username typically is not provided; but in such situations other information (e.g., information that includes the MAC address of the hardware in the end user device (or CPE)) is provided.
  • DHCP and CLIPS captures the MAC addresses and uses these addresses to distinguish subscribers and access their subscriber records.
  • device identification can be performed based on the subscriber identity module (SIM) parameters like the international mobile subscriber identity (IMSI) (for example card of soft SIM (e.g., in IoT).
  • SIM subscriber identity module
  • IMSI international mobile subscriber identity
  • the MAC and IMSI are separable since the SIM card can be inserted into a different device.
  • the subscriber unit 108 performs policy enforcement based on the subscriber records, such that for flows of traffic received at the network gateway system, the subscriber unit identifies the subscriber associated with these flows and performs subscriber-specific policy enforcement (such as bandwidth monitoring/control, access control, etc.).
  • the subscriber unit 108 can also provide subscriber identification services to the other units of the network gateway system 100 by exposing subscriber information (e.g., subscriber name, authentication information, access control information, rate-limiting information, policing information, devices enabled for the subscriber, services enabled for the subscriber, etc.) to the other units of the network gateway system.
  • subscriber information e.g., subscriber name, authentication information, access control information, rate-limiting information, policing information, devices enabled for the subscriber, services enabled for the subscriber, etc.
  • the subscriber information can be delivered to the other units of the network gateway system via a response to an explicit request received from the other unit(s) and transmitted via the internal communication mechanism 112.
  • the subscriber information can be delivered to the other unit(s) of the network gateway system as a form of metadata with subscriber identification information correlated to a particular packet/flow or processing stream, and forwarded to the other unit(s) via the internal communication mechanism 112.
  • a subscriber unit may include multiple instances, where each instance handles a different subset of subscribers connecting to the network gateway system 100.
  • Network unit 110 is the interface that couples the subscriber's traffic with the core packet data network 103.
  • the network unit 110 handles traffic to and from other network devices that are communicatively coupled with the end user device through the core network and the network gateway system 100.
  • Network unit 110 can implement one or more packet network communication protocols enabling the communication of traffic flows to and from the core network 103 (e.g., Internet Protocol Security (IPsec), Secure Sockets Layer (SSL) / Transport Layer Security (TLS), peer-to-peer (P2P), Voice over IP (VoIP) Session Border Controller, Gi/SGi interface in LTE, a VPN connection, etc.).
  • IPsec Internet Protocol Security
  • SSL Secure Sockets Layer
  • TLS Transport Layer Security
  • P2P peer-to-peer
  • VoIP Voice over IP
  • the network unit 110 routes packets to and from the core network 103; it also performs various functions such as IP address/IP prefix allocation.
  • the network unit 110 can also provide network information services to the other units of the network gateway system 100.
  • network information related to the traffic received e.g., flow information, source and destination addresses, network policies, transport protocols, security settings, access control lists (ACL), routing policies, etc.
  • ACL access control lists
  • the network information can be delivered to the other unit(s) of the network gateway system as a form of metadata with network information correlated to a particular packet or processing stream, and forwarded to the other unit(s) via the internal communication mechanism 112.
  • a network unit may include multiple instances, where each instance handles a different subset of traffic flows (e.g., different IP flows) forwarded (to and from the user devices) within the network gateway system 100.
  • the network gateway system 100 further includes an application unit 114, which provides value added services offered by a service provider. These value added services unlock further revenue potential to the service provider. Monitoring temperatures or water leaks, monitoring airplane engines, monitoring or performing remote surgeries, security monitoring services, triggering repair services based on detection of system failures, etc., are examples of value added services that can be offered by service providers to customers of the service.
  • the application unit 114 may use all or some of the device information, subscriber information, network information exposed by the other unit(s) of the network gateway system 100 through the internal communication mechanism 112.
  • a result of processing of data in the application unit 114 can be delivered to and/or used by the other units of the network gateway system, including other application unit(s), to perform and/or update the processing of the traffic at these unit(s).
  • a network unit may include multiple instances, where each instance handles a different subset of traffic flows (e.g., different IP flows) forwarded (to and from the user devices) within the network gateway system 100.
  • the network gateway system 100 further includes the internal communication mechanism 112 that enables communication and data exchanges between the different components of the network gateway system.
  • the internal communication mechanism 112 enables each of the components of the network gateway system 100 to communicate and exchange data with one another.
  • the internal communication mechanism 112 enables the application unit 114 to get access to data and information related to traffic received from or addressed to end user devices as obtained when the traffic is processed within the network gateway system 100.
  • the internal communication mechanism 112 enables an application to gain access to the result of the processing of the traffic at the access unit 106 (e.g., obtain device information), at the subscriber unit 108 (e.g., obtain subscriber information) or at the network unit 110 (e.g., obtain network information), or at another application unit.
  • the access unit 106 e.g., obtain device information
  • the subscriber unit 108 e.g., obtain subscriber information
  • the network unit 110 e.g., obtain network information
  • this architecture provides a service provider with the ability to offer dynamic and adaptable services applications that benefit from the information and data exposed by the various disaggregated elements of the network gateway architecture 100.
  • the internal communication mechanism 112 further enables maintaining the state of each one of the components (the access unit 106, the subscriber unit 108, the network unit 110 and the application unit 114) of the network gateway system 100.
  • the internal communication mechanism enables a flexible and adaptable communication between the components such that traffic received from an end user device through the access network can be processed in the various components of the network gateway in any suitable order desired by a service provider.
  • the current architecture of the gateway system 100 enables a non-pipelined processing of traffic received from an end user device.
  • traffic entering the network gateway may be first processed at the access unit 106 then processed at the network unit 110 while skipping the subscriber unit 108.
  • the application unit 114 can be added at any step within the network gateway system.
  • the internal communication mechanism 112 may be
  • the internal communication mechanism 112 may be implemented as a shared memory system that is accessible by each one of the access unit 106, the subscriber unit 108, the network unit 110 and the application unit 114.
  • the internal communication mechanism 112 may be implemented as a Remote procedure call (RPC) between the different components of the network gateway system.
  • RPC Remote procedure call
  • the internal communication mechanism 112 is implemented as a database infrastructure (be it a database infrastructure distributed over multiple computing devices or implemented on a single computing device) shared between the different components.
  • the internal communication mechanism 112 can be implemented as a service chaining infrastructure such that the components of the network gateway system 100 (i.e., the access unit 106, the subscriber unit 108, the network unit 110 and the application unit 114) are communicatively coupled through a packet network.
  • FIG. 2 illustrates a block diagram of an exemplary disaggregated network gateway system 200 according to one embodiment.
  • the example disaggregated network gateway system 200 includes a set of physical or virtual disaggregated gateway units (DGUs) comprising the access unit instances 106-106N; the application unit instances 114A-L; the subscriber unit instance 108A-M, and the network unit instances 110A-R.
  • the network gateway further includes gateway control 116 (including the gateway controller 102 and the gateway manager 104).
  • Network gateway system 200 is an exemplary embodiment of a disaggregated network gateway system 100 as described with reference to Figure 100.
  • the network gateway system 200 also includes an internal communication mechanism which enables the various instances of the DGUs to communicate with one another.
  • the instances are virtual or physical implementation of the corresponding units illustrated in Figure 1.
  • Any number of DGUs can form the disaggregated network gateway system 200.
  • the network gateway system 200 is coupled with a set of user devices 205 A-N.
  • the example network shows three UEs 205 A, 205B, and 205N connecting (either directly or indirectly) to the network gateway system 200. However, more than three UEs 205 A-N may be connected to the gateway at a given time.
  • the arrows coupling the multiple DGUs illustrate the path that traffic takes within the network gateway system 200 when received at one of the access unit instances 106A-C.
  • each DGU is a separate computing component (physical or virtual), that is independent of the other DGUs, each one may be configured to process traffic according to different configuration parameters (e.g., different access technologies and protocols, various value added applications that can be configured according to the needs of the service provider or to the customers of the service providers).
  • different configuration parameters e.g., different access technologies and protocols, various value added applications that can be configured according to the needs of the service provider or to the customers of the service providers).
  • a disaggregated gateway architecture implements separate components that can be configured according to different technologies and which provides various paths for traffic within the gateway.
  • the access unit instance 106 A is configured to interface and process traffic from wireless/mobile access networks and/or user devices (e.g., GERAN, UTRAN, E-UTRAN, CDMA2000, GSM, UMTS, lxEVDO, LTE, Wi-Fi, WiMAX, etc.); while the access unit instance 106C is configured to interface and process traffic from wired access networks/user devices.
  • wireless/mobile access networks and/or user devices e.g., GERAN, UTRAN, E-UTRAN, CDMA2000, GSM, UMTS, lxEVDO, LTE, Wi-Fi, WiMAX, etc.
  • the access unit instance 106C is configured to interface and process traffic from wired access networks/user devices.
  • traffic that reaches the network gateway system 200 from a user device may follow at least 3 paths within the gateway device.
  • traffic received at the access unit instance 106A is processed and forwarded towards the application unit instance 114A, following its processing at the application unit instance 114A, the traffic is communicated to the subscriber unit instance 108A to be processed. Following the processing of the traffic at the subscriber unit instance 108 A, it is communicated to the network unit instance 11 OA.
  • traffic received at the access unit instance 106C is processed and forwarded towards the subscriber unit instance 108 A to be processed. Following the processing of the traffic at the subscriber unit instance 108 A, it is communicated to the network unit instance 11 OA.
  • the traffic is then communicated to a common subscriber unit instance 108 A to be processed.
  • a service provider may now offer different access technologies to customers of the service while availing the same subscriber unit of process subscriber information.
  • the architecture of the gateway allows a flexible and dynamic configuration of the various components of the network gateway.
  • traffic received at the access unit instance 106B is processed and forwarded towards the subscriber unit instance 108B to be processed. Following the processing of the traffic at the subscriber unit instance 108B, it is communicated to the application unit instance 114B. Following the processing of the traffic at the application unit instance 114B, the traffic is communicated to the network unit instance HOB.
  • traffic received at the network gateway system from the network side may follow at least 3 paths within the gateway device towards the user devices 205 A-N.
  • traffic may reach the network gateway system 200 from the network at the network unit instance 11 OA (for example, the network unit instance may implement an IPv4/MPLS tunnel, while the network unit instance HOB implements an IPv6 tunnel).
  • traffic received at the network unit instance 11 OA is processed and forwarded towards the subscriber instance 108A; following its processing at the subscriber unit instance 108A, the traffic is communicated to the application unit instance 114A, to be processed.
  • the access unit instance 106 A to be forwarded towards one of the user devices 205 A-N.
  • traffic received at the network unit instance 110A is processed and forwarded towards the subscriber instance 108A; following its processing at the subscriber unit instance 108 A, the traffic is communicated to the access unit instance 106C to be forwarded towards one of the user devices 205 A-N.
  • a service provider may now offer different access technologies to customers of the service while availing the same subscriber unit of process subscriber information.
  • the architecture of the gateway allows a flexible and dynamic configuration of the various components of the network gateway.
  • traffic received at the network unit instance 110B is processed and forwarded towards the application unit instance 114B to be processed. Following the processing of the traffic at the application unit instance 114B, it is communicated to the subscriber unit instance 108B. Following the processing of the traffic at the subscriber unit instance 108B, the traffic is communicated to the access unit instance 106B.
  • the disaggregated architecture of the gateway enables a service provider to implement various levels of scalability within the gateway offering support to different types of access technologies and/or network technologies, as well as enabling varying processing paths of data within the gateway.
  • the disaggregation gateway system can support varying scaling possibilities for each unit within the gateway.
  • the access units (and corresponding instances) can be scaled to support millions of end user devices that couple to the gateway.
  • the access units can be distributed close to the end user devices.
  • the network unit (and corresponding instances) can be scaled to support tens or hundreds of flows (as there is a significantly lower number of service providers offering content and services) that are accessed by the end user devices through the gateway system 100.
  • the service provider may implement different applications (within application unit(s) 114) that can use the information output from each one of the access unit instances, the subscriber unit instances and/or the network unit instances.
  • the application unit may now access subscriber information, device information and network information related to traffic processed at the network gateway system 100, which was exposed by the various units through the intra- communication interface, and without significant implementation efforts at the application unit level.
  • An electronic device stores and transmits (internally and/or with other electronic devices over a network) code (which is composed of software instructions and which is sometimes referred to as computer program code or a computer program) and/or data using machine -readable media (also called computer-readable media), such as machine -readable storage media (e.g., magnetic disks, optical disks, read only memory (ROM), flash memory devices, phase change memory) and machine -readable transmission media (also called a carrier) (e.g., electrical, optical, radio, acoustical or other form of propagated signals - such as carrier waves, infrared signals).
  • machine -readable media also called computer-readable media
  • machine -readable storage media e.g., magnetic disks, optical disks, read only memory (ROM), flash memory devices, phase change memory
  • machine -readable transmission media also called a carrier
  • carrier e.g., electrical, optical, radio, acoustical or other form of propagated signals - such as carrier waves, infrared
  • an electronic device typically includes hardware and software, such as a set of one or more processors coupled to one or more machine- readable storage media to store code for execution on the set of processors and/or to store data.
  • an electronic device may include non-volatile memory containing the code since the non-volatile memory can persist code/data even when the electronic device is turned off (when power is removed), and while the electronic device is turned on that part of the code that is to be executed by the processor(s) of that electronic device is typically copied from the slower non-volatile memory into volatile memory (e.g., dynamic random access memory (DRAM), static random access memory (SRAM)) of that electronic device.
  • volatile memory e.g., dynamic random access memory (DRAM), static random access memory (SRAM)
  • Typical electronic devices also include a set or one or more physical network interface(s) to establish network connections (to transmit and/or receive code and/or data using propagating signals) with other electronic devices.
  • network connections to transmit and/or receive code and/or data using propagating signals.
  • One or more parts of an embodiment of the invention may be implemented using different combinations of software, firmware, and/or hardware.
  • a network device is an electronic device that communicatively interconnects other electronic devices on the network (e.g., other network devices, end-user devices).
  • Some network devices are "multiple services network devices" that provide support for multiple networking functions (e.g., routing, bridging, switching, Layer 2 aggregation, session border control, Quality of Service, and/or subscriber management), and/or provide support for multiple application services (e.g., data, voice, and video).
  • FIG. 3 is a diagram of one embodiment of a physical disaggregated network gateway system.
  • the physical (i.e., hardware) gateway system 300 is a network device that can perform some or all of the operations and methods described above for one or more of the embodiments.
  • the physical gateway system 300 can include one or more network interface controllers (NICs; also known as network interface cards) 315, processor(s) (“processor circuitry”) 310, memory 305, and internal communication mechanism 112.
  • NICs network interface controllers
  • the processor(s) 310 may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g. , microprocessor and/or digital signal processor).
  • the processor(s) 310 is configured to execute of the access unit 106, the subscriber unit 108, the network unit 110, and one or more application units 114, to perform some or all of the operations and methods described above for one or more of the embodiments.
  • the various modules of Fig. 3 are shown to be included as part of the processor 310, one having ordinary skill in the art will appreciate that the various modules may be stored separately from the processor 310, for example, in a non-transitory computer readable storage medium.
  • the processor 310 can execute the various modules stored in the non-transitory computer readable medium, to perform some or all of the operations and methods described above. Accordingly, the processor 310 can be configured by execution of various modules to carry out some or all of the functionality disclosed herein. While the processor 110 is shown to include a single one of each of the access unit 106, the subscriber unit 108, the network unit 110, and the application units 114, one having ordinary skill in the art will appreciate that any number per type of unit can be included. Further, as described with reference to Figures 1-2, units of a same type (e.g., access unit, network unit, or subscriber unit) may be implemented to support different technologies (access technologies, network technologies, etc.) within the same network gateway system.
  • a same type e.g., access unit, network unit, or subscriber unit
  • FIG 4 is a diagram of one embodiment of a network device that can implement one or more virtual disaggregated gateway units (DGU) that can be part of a network gateway system (e.g., such as gateway 100, 200). Each one of the DGU, can implement one of an access unit, a subscriber unit, a network unit or an application unit.
  • DGU virtual disaggregated gateway units
  • the network device 400 includes hardware 401 comprising a set of one or more processor(s) 405 (which are often commercial off-the-shelf COTS processors) and NIC(s) 410 (which include physical NIs 415), as well as non-transitory machine readable storage media 420 having stored therein a DGU 4 72.
  • a physical NI 415 is hardware in a network device 400 through which a network connection (e.g., wirelessly through a wireless network interface controller (WNIC) or through plugging in a cable to a physical port connected to a NIC 410) is made.
  • a network connection e.g., wirelessly through a wireless network interface controller (WNIC) or through plugging in a cable to a physical port connected to a NIC 410
  • the processor(s) 405 may execute software to instantiate a hypervisor 470 (sometimes referred to as a virtual machine monitor (VMM)) and one or more virtual entities 440A-Z that are run by the hypervisor 470, which are collectively referred to as software instance(s) 402.
  • a virtual entity 440 is a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine; and applications generally do not know they are running on a virtual entity as opposed to running on a "bare metal" host electronic device, though some systems provide para-virtualization which allows an operating system or application to be aware of the presence of virtualization for optimization purposes.
  • Each of the virtual entities 440A-Z, and that part of the hardware 401 that executes that virtual machine may form a separate virtualized DGU 404A-Z.
  • Each such virtualized DGU can include a DGU manager interface 446A, a DGU controller interface 444A, where the DGU manager interface enables the DGU to communicate with the gateway manager and the gateway controller respectively.
  • the DGU includes an internal communication interface 442A that enables the DGU to communicate with other DGUs of the network gateway system.
  • the DGU further includes a processing module 448A, that performs the operations/services of a particular DGU (e.g., enables an access unit to receive traffic from user devices and expose device information; enables the subscriber unit to perform subscriber identification, authentication and authorization, policy enforcement, as well as exposure of subscriber information; enables the network unit to interface with packet data networks, and expose flow information; and/or enables application units to use the result of the processing of each one of the other processing units to provide value added services to a service provider).
  • DGU instances 450Y-Z represent the DGU manager interface 446, the DGU controller interface 444, the processing module 448, and the internal communication interface 442 included in the respective virtualized DGUs.
  • hypervisor 470 and virtual entities 440A-Z such as virtual machines
  • alternative embodiments may use other techniques (e.g., using operating system level virtualization where, instead of a hypervisor and virtual machines, the kernel of the operating system allows for multiple user space instances (often called software containers, virtualization engines, virtual private servers, or jails) that may execute a virtualized DGU.
  • each type of DGU e.g., an access unit, a network unit, or a subscriber unit
  • the various types of DGUs may be included within the same network device, such as each one is part of a single independent virtual entity, or alternatively as part of the same virtual entity.
  • FIG. 5 illustrates an exemplary flow diagram of operations performed in a network gateway system located between an access network and a core packet data network of a carrier network when traffic is received from one or more user devices.
  • traffic is received at an access unit instance from one or more user device.
  • traffic is received from one or more of the user devices 205A-N at access unit instances (106A-C).
  • an access unit instance e.g., access unit instances 106A, 106B, 106C
  • determines device information associated with the received traffic e.g., MAC address of the device forwarding the traffic, access technology used for coupling the user device to the network gateway system, etc.
  • traffic is processed at the subscriber unit instance, where the processing includes performing at least one of identification, authentication and authorization of a subscriber's session associated with the received traffic.
  • the subscriber unit instance (108 A, 108B) determines subscriber information associated with the received traffic.
  • traffic is forwarded from the network unit instance towards the core packet data network.
  • the network unit instance (110A, HOB) determines network information associated with the received traffic.
  • the device information, the subscriber information, the network information, and a result of the processing of the traffic at an application unit instance is exposed to other ones of the access unit instance (106A, 106B, 106C), the subscriber unit instance (108A, 108B), the network unit instance (110A, HOB), and the application unit instance (114A, 114B).
  • Each one of the access unit instance, the subscriber unit instance and the network unit instance is separately implemented and separately scalable from the other ones of the access unit instance, the subscriber unit instance and the network unit instance.
  • FIG. 6 illustrates an exemplary flow diagram of operations performed in a network gateway system located between an access network and a core packet data network of a carrier network when traffic is received from the core network.
  • traffic is received at a network unit instance from the core network 103.
  • the traffic is received through a packet data network at one of the network unit instances 110A or HOB.
  • each of the network unit instances implements a given packet data network protocol (e.g., IPv4, IP/MPLS, IPv6, etc.) and is operative to receive one or flows destined to one or more user devices 205 A-N.
  • a network unit instance e.g., network unit instances 110A, HOB determines network information associated with the received traffic.
  • traffic is processed at the subscriber unit instance, where the processing includes performing at least one of identification, authentication and authorization of a subscriber's session associated with the received traffic.
  • the subscriber unit instance (108 A, 108B) determines subscriber information associated with the received traffic.
  • traffic is forwarded from the access unit instance towards one or more user devices. For example, traffic is forwarded towards one or more user devices 205 A-N from access unit instances (106A-C) according to a one or more access technologies.
  • the access unit instance determines device information associated with the traffic to be forwarded (e.g., MAC address of the device to which the traffic is to be forwarded, access technology used for coupling the user device to the network gateway system, the device's type and capabilities, etc.).
  • the device information, the subscriber information, the network information, and a result of the processing of the traffic at an application unit instance (114A, 114B) is exposed to other ones of the access unit instance (106A, 106B, 106C), the subscriber unit instance (108A, 108B), the network unit instance (110A, HOB), and the application unit instance (114A, 114B).
  • Each one of the access unit instance, the subscriber unit instance and the network unit instance is separately implemented and separately scalable from the other ones of the access unit instance, the subscriber unit instance and the network unit instance.
  • disaggregated network gateway enables independent scalability of functions (independent scalability of the access unit, the subscriber unit, the network unit and the application unit of the gateway).
  • a disaggregated network gateway enables an easier scalability
  • each instance needs to be deployed while having a centralized subscriber and network unit within the gateway system.
  • the implementation complexity of each instance is smaller, and can be, for example, be easier to virtualize it and may be implemented within a single processing core.
  • a disaggregated gateway system may be built from components/functions provided by different suppliers based on their unique expertise, existing products, roadmap, etc. Further, the DGU instances 450 are more flexible in terms of their location. The various DGUs can be deployed on the same server/network device to distributed cloud infrastructure (for example: access unit instances deployed in a number of micro-DCs closer to the end-user, while subscriber unit can be more centralized).
  • a disaggregated gateway system enables a more flexible infrastructure to develop and deploy Value-Added-Services (VAS) (i.e., applications), which can be inserted between any unit within the gateway.
  • VAS Value-Added-Services
  • VAS may also be deployed after the Network Function, similarly to current deployments of services on Gi interface in mobile networks. Also, we can deploy a number of VAS at different "locations" within the network gateway.
  • the disaggregated gateway system enables the creation of multi-access and multi-tenant deployments more easily, efficiently, and flexibly than in standard network gateway architectures.
  • the flow of traffic within the disaggregated network gateway may be performed in another order than the one depicted in the flow diagram of Figure 5 or Figure 6, and some operations may be skipped without departing from the scope of the present invention.
  • the disaggregated network gateway structure allows for a flexible configuration of flows of operations within the network gateway such as multiple operations can be performed in a different order.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un système de passerelle de réseau désagrégée. Le système de passerelle de réseau comprend une instance d'unité d'accès, une instance d'unité d'abonné, une instance d'unité de réseau, une instance d'unité d'application, un mécanisme de commande de passerelle et un mécanisme de communication interne permettant à chacune des instances parmi l'instance d'unité d'accès, l'instance d'unité d'abonné et l'instance d'unité de réseau d'exposer les informations de dispositif, les informations d'abonné, les informations de réseau, et un résultat du traitement du trafic reçu au niveau de l'instance d'unité d'application à d'autres unités du système de passerelle de réseau. Chaque instance parmi l'instance d'unité d'accès, l'instance d'unité d'abonné, l'instance d'unité de réseau et l'instance d'unité d'application est mise en œuvre séparément et peut être extensible séparément des autres unités du système de passerelle de réseau.
PCT/IB2016/054274 2016-07-18 2016-07-18 Procédé et appareil de désagrégation de passerelle de réseau WO2018015785A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2016/054274 WO2018015785A1 (fr) 2016-07-18 2016-07-18 Procédé et appareil de désagrégation de passerelle de réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2016/054274 WO2018015785A1 (fr) 2016-07-18 2016-07-18 Procédé et appareil de désagrégation de passerelle de réseau

Publications (1)

Publication Number Publication Date
WO2018015785A1 true WO2018015785A1 (fr) 2018-01-25

Family

ID=56550931

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2016/054274 WO2018015785A1 (fr) 2016-07-18 2016-07-18 Procédé et appareil de désagrégation de passerelle de réseau

Country Status (1)

Country Link
WO (1) WO2018015785A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112055851A (zh) * 2018-04-17 2020-12-08 日本电信电话株式会社 仪器控制装置、仪器控制方法以及仪器控制系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150358850A1 (en) * 2014-06-10 2015-12-10 Cisco Technology, Inc. Conveying subscriber information to service chain services using tunnel protocol header encapsulation for mobile network applications in a network environment

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150358850A1 (en) * 2014-06-10 2015-12-10 Cisco Technology, Inc. Conveying subscriber information to service chain services using tunnel protocol header encapsulation for mobile network applications in a network environment

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
KOSTAS PENTIKOUSIS ET AL: "Mobileflow: Toward software-defined mobile networks", IEEE COMMUNICATIONS MAGAZINE, IEEE SERVICE CENTER, PISCATAWAY, US, vol. 51, no. 7, 1 July 2013 (2013-07-01), XP011519224, ISSN: 0163-6804, DOI: 10.1109/MCOM.2013.6553677 *
SUNETH NAMAL ET AL: "Architectural EPC extensions for supporting heterogeneous mobility schemes", 31 January 2013 (2013-01-31), pages 1 - 93, XP055227315, Retrieved from the Internet <URL:http://www.mevico.org/D22.pdf> [retrieved on 20151110] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112055851A (zh) * 2018-04-17 2020-12-08 日本电信电话株式会社 仪器控制装置、仪器控制方法以及仪器控制系统
CN112055851B (zh) * 2018-04-17 2024-05-07 日本电信电话株式会社 仪器控制装置、仪器控制方法以及仪器控制系统

Similar Documents

Publication Publication Date Title
US11973686B1 (en) Virtual performance hub
EP3228053B1 (fr) Sélection de fonction de réseau périphérique (enf) pour une infrastructure de virtualisation de fonction de réseau (nfvi)
US11129023B2 (en) Systems and methods for distributing SD-WAN policies
US9544248B2 (en) Overlay network capable of supporting storage area network (SAN) traffic
US9374267B2 (en) Cloud based customer premises equipment
EP3580897B1 (fr) Procédé et appareil de chaînage de service dynamique avec routage de segment pour bng
US20150350912A1 (en) Residential service delivery based on unique residential apn
US20210091994A1 (en) Network slicing with smart contracts
US20140068703A1 (en) System and method providing policy based data center network automation
US20150327052A1 (en) Techniques for Managing Network Access
US20140105062A1 (en) Feature peer network with scalable state information
EP3732833B1 (fr) Permettre des services d&#39;itinérance à large bande
US11870641B2 (en) Enabling enterprise segmentation with 5G slices in a service provider network
BR112014001861B1 (pt) Método para implementar um protocolo de túnel de serviço geral de rádio por pacotes, e, sistema computacional em nuvem para gerenciar a implementação de um protocolo de túnel de serviço geral de rádio por pacotes
US10819626B2 (en) Method and apparatus for updating multiple multiprotocol label switching (MPLS) bidirectional forwarding detection (BFD) sessions
WO2018150222A1 (fr) Allocation d&#39;adresse de protocole internet (ip) sur des réseaux virtuels de couche 2
WO2018015785A1 (fr) Procédé et appareil de désagrégation de passerelle de réseau
US11540131B2 (en) Customer control of their mobile assets
US20220337679A1 (en) System and method for implementing extension of customer lan at provider network service point
Langenskiöld Network Slicing using Switch Virtualization
FAIZAL Optimization of virtual network quality through protocol analysis

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: 16744540

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16744540

Country of ref document: EP

Kind code of ref document: A1