WO2012175140A1 - Sélection de passerelle pour équilibrer une charge - Google Patents

Sélection de passerelle pour équilibrer une charge Download PDF

Info

Publication number
WO2012175140A1
WO2012175140A1 PCT/EP2011/060598 EP2011060598W WO2012175140A1 WO 2012175140 A1 WO2012175140 A1 WO 2012175140A1 EP 2011060598 W EP2011060598 W EP 2011060598W WO 2012175140 A1 WO2012175140 A1 WO 2012175140A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateways
gateway
load value
network
performance measurements
Prior art date
Application number
PCT/EP2011/060598
Other languages
English (en)
Inventor
Jarno Antero HALME
Risto Antero Kauppinen
Original Assignee
Nokia Siemens 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 Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to PCT/EP2011/060598 priority Critical patent/WO2012175140A1/fr
Publication of WO2012175140A1 publication Critical patent/WO2012175140A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/17—Selecting a data network PoA [Point of Attachment]
    • 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/18—Service support devices; Network management devices

Definitions

  • the present invention relates to load balancing and, in particular, to load balancing in Gateways in a telecommunication network.
  • a Gateway refers to a network entity that interfaces from one network to another or one part of a network to another part of the network. In other words, it acts as a gateway between adjoining or operatively adjoining networks or parts of a network.
  • the mobile network may typically include, in a simplified view, an access network and a core network.
  • the access network enables User Equipment (UE), for example in the mobile domain, a mobile telephone, mobile device, a tablet, and so on, to receive and transmit traffic, e.g. voice traffic, data traffic, multimedia traffic and so on.
  • UE User Equipment
  • the access network in the mobile domain may include various entities including, for example depending on the type of mobile network, Base Transceiver Stations (BTS), Node Bs (NB), Evolved Node Bs (eNB) and so on, to enable the UE to access wirelessly the mobile network.
  • BTS Base Transceiver Stations
  • NB Node Bs
  • eNB Evolved Node Bs
  • the core network may be one or more of a packet switched network, a circuit switched network, Public Switched Telephone Network (PSTN), Wide Area Network (WAN), Local Area Network (LAN), Internet Protocol (IP) network, or any other type of network.
  • PSTN Public Switched Telephone Network
  • WAN Wide Area Network
  • LAN Local Area Network
  • IP Internet Protocol
  • a GW may be located (either virtually or physically) between the access network and the core network where the GW may handle all traffic traversing between UE, via the access network, and the core network. Accordingly, if a GW becomes overloaded with then there will be a significant degradation in quality of service to the UE and therefore the end-users of the mobile network, e.g. the subscribers to a Mobile Network Operator (MNO).
  • MNO Mobile Network Operator
  • Next Generation Mobile Networks which includes the so-called Fourth Generation (4G) networks, for example, Long Term Evolution (LTE) networks
  • 4G Fourth Generation
  • a user equipment session starts when the user equipment connects to the network, for example, via a transceiver, and continues until the user equipment is disconnected from the network.
  • the user equipment may request and/or receive traffic from the core network, e.g. data traffic, multimedia traffic, TV on demand, video streaming, and so on.
  • the increase of user equipment sessions and the increase in traffic from and/or to the user equipment mean that the gateways between the access network and the core network will be substantially more heavily utilised. It would not be feasible for a Network Operator to provision the network with a substantial number of gateways due to the cost and that for periods of time the gateways may not be fully utilised and thus have significant spare capacity.
  • NGMN there is a desire to enable self-organizing functionality, which may be referred to as Self-organizing Networks (SON) due to the size and complexity of NGMNs as manual configuration may not be possible.
  • SON Self-organizing Networks
  • standardised specific use cases for NGMNs will take a substantial amount of time to propose and be accepted and thus, as NGMNs are becoming available for deployment and implementation, there is a need to provide certain functionality prior to standardised solutions are implemented and to efficiently manage gateways in a telecommunication network.
  • the present invention seeks to address, at least in part, some or all of the problems and drawbacks discussed hereinabove.
  • a method comprising the steps of: receiving one or more performance measurements relating one or more gateways; determining a load value for each of the gateways based on the one or more performance measurements relating to each gateway; receiving a request for a gateway from a network entity; identifying an available gateway based on the determined load value for each of the gateways; and transmitting an identification of the identified available gateway to the network entity.
  • the method may be implemented by any entity such as, for example, a network node, server, system, computing device, module, and so on.
  • entity implementing the method may a separate entity, in other words a stand alone entity, or the entity may form part of integrated with another entity, for example, the method may be implemented by a module (where the module may be hardware, software or a combination thereof) that is integrated with a management system of the network.
  • One or more performance measurements are received relating to one or more gateways, wherein a network may include one or more gateways.
  • the gateways may act as a gateway between an access network and a core network.
  • the network may be a mobile network.
  • the performance measurements for one or more of the gateways may be received periodically, for example, every 1 0 seconds, every 30 seconds, every minute, every 5 minutes, every 10 minutes, and so on.
  • the period between receiving consecutive performance measurements may be any period suitable for the size, type and implementation of the network.
  • the method may further comprise requesting the performance measurements from a management system.
  • the request for performance measurements may be performed periodically, for example, every 10 seconds, every 30 seconds, every minute, every 5 minutes and so on.
  • the period for requesting the performance measurements may be any period suitable for the size, type and implementation of the network.
  • the performance measurements may include counter, load, throughput, processor load, capacity and any other Key Performance Indicator (KPI) data for one or more of the gateways. Based on the received performance measurements a load value for each gateway may be determined.
  • KPI Key Performance Indicator
  • the load value determined for each gateway may be a percentage value, a weighting value or any other rating or type of value that may enable an available gateway to be selected or identified based on the determined load values.
  • a request may be received from a network entity for an available gateway.
  • the network entity from which the request may be received may be a Mobility
  • the network entity may request an available gateway to enable a session for User Equipment to be established whilst efficiently balancing the load on each of the gateways to substantially ensure that gateways are not overloaded and that the service provided for the User Equipment session is not degraded.
  • the available gateway may be identified or selected based on the determined load values.
  • the available gateway may be identified or selected by comparing the load values to identify the gateway with the lowest load value or highest load value depending on the scale, type or meaning of the load value determined.
  • the load value may indicate the actual spare capacity or percentage i o spare capacity for each gateway and then the available gateway may be identified or selected by comparing the load values to identify the gateway with the highest spare capacity.
  • the step of identifying the best available gateway may further comprise the step of comparing the load value for each of the gateways to identify the best available gateway, for example, as a gateway having a lowest
  • the load value may be a probability value that may be used as a probability factor in identifying an available gateway.
  • a first gateway (GW1 ) has a determined load value of 44%
  • a second gateway has a determined load value of 31 % probability (which may be based on the performance measurements for GW2, for example, current or
  • GW3 25 predicted spare capacity and load on GW2 and a third gateway (GW3) has a determined load value of 25% probability (which may be based on the
  • the determined load value may define a probability of identifying a gateway and the step of identifying an available gateway may be based on the probability.
  • the load for the network of gateways will be shared and balanced amongst the gateways in the network depending on the determined load values for the gateways.
  • any type and/or scale, (e.g. percentage, absolute value, probability, etc), for the load value determined for each gateway (based on one or more of load, capacity, spare capacity, number of sessions, processor usage, etc), may be implemented to enable the available gateway to be identified or selected.
  • the identification or selection of the available gateway may be further based on actual parameters or predicted/estimated parameters relating to the session to be established, for example, the type of traffic (e.g. multimedia data, video streaming, and so on), the length of time of the session, bandwidth or capacity required, and so on.
  • the identification of an available gateway may be further based on the estimated/predicted or actual parameters indicating the actual or estimated load that may be generated by the new session for a gateway.
  • the method may enable one or more gateways in a network to be efficiently and effectively managed in terms of load balancing across the gateways.
  • a gateway is required for a session establishment for User Equipment an available gateway can be identified and/or selected for that session which effectively and efficiently balances the load between the gateways in the network.
  • the step of determining the load value for each of the gateways may further comprise the step of determining a current load value for each of the gateways.
  • the method may determine the current load of each gateway where the current load is effectively related to the point in time the performance
  • the step of determining the load value for each of the gateways may further comprise the step of determining a predicted load value for each of the gateways. As each set of performance measurements for each gateway are taken at a point in time and the performance measurements are collected and/or received periodically then the method may determine a predicted load value for each of the gateways for the period until the next consecutive set of performance
  • the predicted load value may be determined based on, for example, one or more of the current performance measurements, a series of performance measurements for each gateway (e.g. using historical performance measurements for each gateway),
  • estimated/predicted or actual trends/patterns e.g. time of day
  • the type of sessions each gateway is handling e.g. time of day
  • the step of determining the load value for each of the gateways maybe performed periodically. For example, each time a new set of performance parameters for each of the one or more gateways is received, the load value may be determined.
  • the load values for each gateway may be dynamic or variable and may be determined periodically to ensure that the load balancing between gateways is maintained.
  • the method may further comprise the steps of receiving a list of the one or more gateways; and storing the list of one or more gateways.
  • a list of the one or more gateways in the network may be obtained so that it is known which gateways are in the network. This list of gateways may change depending on new gateways being provisioned, gateways that are faulty, undergoing maintenance, and so on.
  • the list of gateways may be requested from a network entity (e.g. management system, Domain Name Server (DNS), and so on) and the list of gateways received in response to the request, e.g. pulled.
  • DNS Domain Name Server
  • the list of gateways may be received, e.g. pushed, from a network entity when the list of gateways is generated, updated or changed.
  • an apparatus comprising: a first input adapted to receive one or more performance measurements relating one or more gateways; a first processor adapted to determine a load value for each of the gateways based on the one or more performance measurements relating to each gateway; a second input adapted to receive a request for a gateway from a network entity; a second processor adapted to identify an available gateway based on the determined load value for each of the gateways; and an output adapted to transmit an identification of the identified available gateway to the network entity.
  • an apparatus adapted to: receive one or more performance measurements relating one or more gateways; determine a load value for each of the gateways based on the one or more performance measurements relating to each gateway; receive a request for a gateway from a network entity; identify an available gateway based on the determined load value for each of the gateways; and transmit an identification of the identified available gateway to the network entity.
  • the apparatus may be a computing device, e.g. a server, personal computer, and so on.
  • the apparatus may be a module or emulator that is separate to, attached to or integrated with any other computing device, system (e.g. management system), or network.
  • the first processor may be further adapted to determine a current load value for each of the gateways.
  • the first processor may be further adapted to determine a predicted load value for each of the gateways.
  • the first processor may be further adapted to determine the load value for each of the gateways periodically.
  • the second processor may be further adapted to compare the load value for each of the gateways to identify the available gateway.
  • the determined load value may define a probability of identifying a gateway and the second processor may be further adapted to identify the available gateway based on the probability.
  • the apparatus may further comprise a third input adapted to receive a list of the one or more gateways; and a memory adapted to store the list of one or more gateways.
  • the apparatus may be adapted to perform any or all of the functionality of the aspects of the present invention.
  • the apparatus may be adapted or configured using hardware, software or any combination thereof.
  • the first input, second input and third input may be the same input, different inputs or any combination thereof.
  • the first processor and the second processor may be the same processor or different processors.
  • a computer program product comprising computer readable executable code for: receiving one or more performance measurements relating one or more gateways; determining a load value for each of the gateways based on the one or more performance measurements relating to each gateway; receiving a request for a gateway from a network entity; identifying an available gateway based on the determined load value for each of the gateways; and transmitting an identification of the identified available gateway to the network entity.
  • the computer program product may further comprise computer readable executable code for performing any or all of the functions in accordance with the aspects of the invention.
  • Figure 1 shows a simplified block diagram of a mobile network in accordance with many of the embodiments of the present invention.
  • the mobile network 101 shown in Figure 1 relates to a fourth generation (4G), Long Term Evolution (LTE) mobile network which is a Next Generation Mobile Network (NGMN).
  • 4G Long Term Evolution
  • LTE Long Term Evolution
  • NVMN Next Generation Mobile Network
  • many of the embodiments will be described in relation to LTE networks and several nodes or entities may be referred to by the name associated with LTE networks and may include nodes or entities that are relevant to LTE networks.
  • many of the embodiments may be applicable to other mobile networks, e.g. second generation (2G) networks, third generation networks (3G), and so on.
  • different network nodes, entities, systems or servers may implement similar functionality to those described hereinbelow in relation to 4G LTE networks.
  • the physical or virtual location and/or the names of the network nodes, entities, systems or servers may be different in the other mobile networks but the load balancing of many of the embodiments described hereinbelow may be implemented in the other types of networks.
  • FIG. 1 shows a simplified block diagram of a 4G LTE mobile network 1 01 , which comprises an access network 102 and a core network 103.
  • the access network 102 may include, amongst other entities, one or more Evolved Node Bs (eNBs) 104 to enable mobile devices 105, e.g. mobile telephones, tablet devices, notebooks, laptops, and so on, to connect to the LTE mobile network 101 in order to transmit and receive traffic.
  • eNBs may instead be Base Transceiver Stations (BTS), Node Bs (NB), and so on.
  • BTS Base Transceiver Stations
  • NB Node Bs
  • a 4G LTE network may comprise tens, hundreds or even thousands of eNBs 104 in the access network 102 of the mobile network 101 .
  • the eNB 104 may be operatively connected to one or more Mobility Management Entity (MME) 106.
  • MME Mobility Management Entity
  • the MME 106 is an LTE network node that is responsible for various functions, services and processes in the LTE access network 102.
  • the MME 1 06 may be responsible, amongst others, for idle mode User Equipment (UE) 105 tracking, bearer activation/deactivation processes, authenticating the UE 105, and so on.
  • the MME 106 may also serve the purpose of establishing a session, or enabling session establishment, for a UE 105 that is requesting to transmit or receive traffic, e.g. multimedia data traffic, over the LTE mobile network 101 .
  • UE User Equipment
  • the MME 106 may receive a request from eNB 104 to establish a session for UE 105 that is operatively communicating with eNB 1 04.
  • the MME 106 may request a selected Serving Gateway (S-GW) 107 through which the session for UE 105 may be channelled to the core network 103.
  • S-GW Serving Gateway
  • the S-GW 107 acts as a gateway between the access network 102 and the core network 103 and provide various functions and services. For example, the S-GW 107 may route and forward data packets from and to UE1 05, and so on. Thus, given the predicted or expected significant increase in UE 1 05 sessions and traffic over the mobile network 101 that will be routed via the S-GWs 107 then it will be an important factor to be able to manage or select the appropriate S-GW 107 to handle each UE 105 session in order to efficiently manage and control the load balancing so as to not degrade a user's experience and quality of service.
  • the mobile network 101 may be managed by one or more management systems.
  • the mobile network 101 may include a Network Management System (NMS) 108, along with any number of other management systems, such as Element Management Systems (EMS), Charging and Billing Systems, and so on.
  • NMS Network Management System
  • EMS Element Management Systems
  • Charging and Billing Systems and so on.
  • EMS Element Management Systems
  • the NMS 108 may include various functions, services and processes to manage the mobile network 101 as a whole.
  • the NMS 108 may include, amongst others, Performance Management functions/modules, Fault Management functions/modules, Configuration Management functions/modules, and so on.
  • the NMS 108 may be operatively connected to other management systems, e.g. the EMS (not shown) in order to request and/or receive information and or data relating to the operation, maintenance and implementation of the mobile network 101 .
  • the NMS 1 08 may be operatively connected to the S-GWs 107, directly or indirectly via another management system, network entity, network node, or module.
  • the NMS 108 may receive various performance measurements relating to each of the S-GWs 107 in the mobile network 101 .
  • the NMS 1 08 may receive the performance measurements automatically and periodically, for example, every 10 seconds, every 30 seconds, every minute, every 5 minutes and so on.
  • the periodic time period may be set at any time period appropriate for the size and type of network to ensure that the NMS 108 has up-to-date and adequate performance measurements or data for the S-GWs 107 in the mobile network 101 .
  • the NMS 108 may request the performance measurements from the S-GWs 107, or from any other management system, entity, node or module.
  • the performance measurements may include any performance measurements relating to the performance and/or operation of the S-GW 107.
  • the performance measurements may include, for example, counter, load, number of active sessions, processor loads, and/or any other Key Performance Indicators (KPI) relating to each of the S-GWs 107 in the mobile network 101 .
  • the mobile network 101 may further include a Process Automation Engine (PAE) 109.
  • PAE 109 is shown as a separate server or system in the mobile network 101 that is operatively connected to the NMS 108 and the MME 106.
  • the PAE 109 may be part of a management system, e.g. the NMS 108, part of another network entity or node, a module, or any other device or entity that may perform the function of the PAE 109 of many of the embodiments described herein.
  • the PAE 109 may also be operatively connected to a Domain Name Server (DNS) 1 1 1 , where the PAE 109 may request and/or receive a list of the S-GWs 107 deployed or provisioned in the mobile network 101 from the DNS 1 1 1 .
  • DNS Domain Name Server
  • the PAE 109 may request and/or receive the performance measurements for each of the S-GWs 107 in the mobile network 101 .
  • the PAE 109 may receive the performance measurements periodically from the NMS 108, for example, every minute. However, as will be appreciated the period between which the PAE 109 receives the may be set at any period that is suitable or appropriate for the purpose of many of the embodiments.
  • the PAE 109 may receive the performance measurements automatically from the NMS 108 or the PAE 109 may periodically request the performance measurements from the NMS 1 08.
  • the PAE 109 may determine or calculate a load value, for example, a load percentage, a weighting value or any other rating or differentiator value, for each of the S-GWs 107.
  • the load value may be a percentage, a weighting value, an absolute value, and so on.
  • the load value for each S-GW 107 may be determined as the overall load/spare capacity of each S-GWs 107 based on the current performance measurements for each S-GW 107.
  • the load value for each S-GW 107 may be determined as a weighted value or percentage of the load/spare capacity of each S-GW 107 based on the current performance measurements for each S-GW 107 in relation to, or in respect of, the total load/spare capacity in the network of S-GWs 107.
  • the available gateway may be identified or selected by comparing the load values to identify the gateway with the lowest load value or highest load value depending on the scale, type or meaning of the load value determined.
  • the load value may be determined as a probability value that may be used as a probability factor in identifying an available gateway.
  • a first gateway has a determined load value of 44% probability (which may be based on the performance measurements for GW1 , for example, current or predicted spare capacity and/or load on GW1 )
  • a second gateway has a determined load value of 31 % probability (which may be based on the performance measurements for GW2, for example, current or predicted spare capacity and load on GW2)
  • a third gateway has a determined load value of 25% probability (which may be based on the
  • GW1 will be identified 44 times out of 100 requests for a gateway as the available gateway
  • GW2 will be identified 31 times out of 100 requests for a gateway as the available gateway
  • GW3 will be identified 25 times out of 100 requests for a gateway as the available gateway.
  • any type and/or scale, (e.g. percentage, absolute value, probability, etc), for the load value determined for each gateway (based on one or more of load, capacity, spare capacity, number of sessions, processor usage, etc), may be implemented to enable an available gateway to be identified or selected.
  • the load for the network of gateways will be shared and balanced amongst the gateways in the network depending on the determined load values for the gateways.
  • the PAE 109 may further determine or calculate a predicted load value, e.g. load percentage, for each S-GW 107.
  • the predicted load value relates to the expected load of each S-GW 107 for the period between receiving performance
  • the predicted load value may be based on the performance measurements along with historical
  • the PAE 109 is continually or periodically determining or calculating a load value for each of the S-GWs 107 in the mobile network 101 .
  • the PAE 109 may further or alternatively determine or calculate a predicted load value for each of the S-GWs 107 in the mobile network 101 to predict the load of each S-GW 107 for the time period between the periodic determination or calculation of the load value for each S-GW 107.
  • the eNB 104 may interact with the MME 106 in order to enable the session establishment for the UE 105.
  • the MME 106 conventionally or typically may request a selected S-GW 107 from the DNS 1 1 1 and the DNS 1 1 1 would respond to the request with a selected S-GW 107 for the UE 105 session establishment.
  • the DNS 1 1 1 may select a S-GW 107 based on a simple round robin mechanism, in other words, the next S-GW in a list, which is an inefficient mechanism and may cause one or more S-GWs to become overloaded thereby degrading the service provided to the UE 105.
  • the PAE 109 may include a DNS emulator 1 10 to emulate a DNS. Therefore, in many of the embodiments, the MME 106 may now request a selected S-GW 107 from the DNS emulator 1 10.
  • a DNS emulator 1 10 By implementing a DNS emulator 1 10 then little or no changes are required in the present process for the MME 106 to request a gateway which enhances many of the embodiments. However, as will be appreciated, many of the embodiments may be implemented without the DNS emulator 1 10 where the MME 106 is instructed to communicate directly with the PAE 109, the entity performing the function of the PAE 109 and/or the DNS emulator 1 10.
  • the DNS emulator 1 10 On receipt of the request for a S-GW 107 the DNS emulator 1 10 based on either or both of the determined load value and predicted load value for each S-GW 107 in the mobile network 101 may select the best available S-GW 107 to handle the session for the UE 105. The PAE 109 via the DNS emulator 1 10 may then inform or transmit an identification of the selected or identified S-GW 107 to the MME 106 so that the session for the UE 105 can be established using the selected S-GW 107 to handle, amongst other functions, the routing of the data packets between the UE 105 (via eNB 104) and the core network 103.
  • many of the embodiments enable an efficient and effective mechanism for load balancing of gateways in a network.
  • the load from User Equipment sessions may be shared and balanced between the gateways.
  • the gateways may be utilised more efficiently, may prevent gateways becoming overloaded and thereby maintaining a high level of service for the user's of the User Equipment.
  • a fast solution to provide network resource efficient usage in networks may be implemented now as part of a network management solution that also enables multi-vendor support without waiting for a standardised approach to be agreed, and determination of the load values for each gateway may be fine tuned depending on usage of the gateways and gateway vendor specific implementation and characteristics.

Abstract

La présente invention se rapporte à un équilibrage de charge et, en particulier, à un équilibrage de charge dans des passerelles. Dans la présente invention, une ou plusieurs mesures de performance relatives à une ou plusieurs passerelles (107) peuvent être reçues et une valeur de charge peut être déterminée, pour chacune des passerelles (107), sur la base de la ou des mesures de performance relatives à chaque passerelle (107). Une demande pour une passerelle (107) peut être reçue, en provenance d'une entité de réseau (106), et une passerelle (107) disponible peut être identifiée sur la base de la valeur de charge déterminée pour chacune des passerelles (107). Ensuite, une identification de la passerelle (107) disponible identifiée peut être transmise à l'entité de réseau (106).
PCT/EP2011/060598 2011-06-24 2011-06-24 Sélection de passerelle pour équilibrer une charge WO2012175140A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2011/060598 WO2012175140A1 (fr) 2011-06-24 2011-06-24 Sélection de passerelle pour équilibrer une charge

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2011/060598 WO2012175140A1 (fr) 2011-06-24 2011-06-24 Sélection de passerelle pour équilibrer une charge

Publications (1)

Publication Number Publication Date
WO2012175140A1 true WO2012175140A1 (fr) 2012-12-27

Family

ID=44627932

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2011/060598 WO2012175140A1 (fr) 2011-06-24 2011-06-24 Sélection de passerelle pour équilibrer une charge

Country Status (1)

Country Link
WO (1) WO2012175140A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20160147927A (ko) * 2014-04-30 2016-12-23 어펌드 네트웍스, 인크. 모바일 네트워크의 용량 확장 최적화
US9614926B2 (en) 2014-04-29 2017-04-04 International Business Machines Corporation Parallel I/O write processing for use in clustered file systems having cache storage
US9667736B2 (en) 2014-04-29 2017-05-30 International Business Machines Corporation Parallel I/O read processing for use in clustered file systems having cache storage
US10912017B2 (en) * 2015-11-10 2021-02-02 Blackberry Limited Gateway selection controlled by network

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030156537A1 (en) * 2002-02-21 2003-08-21 Said Soulhi Packet data serving node (PDSN) load optimization
EP1587272A1 (fr) * 2004-04-13 2005-10-19 Alcatel Méthode et appareil pour la répartition de charge dans un réseau de communication de données sans fil
WO2007092687A2 (fr) * 2006-02-08 2007-08-16 Motorola, Inc. Régulation de charge dans un système de communication cellulaire
WO2009092440A1 (fr) * 2008-01-23 2009-07-30 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil de mise en commun de ressources de réseau
US20090285179A1 (en) * 2008-05-16 2009-11-19 Bridgewater Systems Corp. Long-Term Evolution (LTE) Packet Data Network Gateway (PDN-GW) Selection
WO2010102127A1 (fr) * 2009-03-04 2010-09-10 Cisco Technology, Inc. Détection de surcharges dans des dispositifs réseau
WO2010132884A1 (fr) * 2009-05-15 2010-11-18 Ciso Technology, Inc. Système et procédé pour un réseau auto-organisateur

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030156537A1 (en) * 2002-02-21 2003-08-21 Said Soulhi Packet data serving node (PDSN) load optimization
EP1587272A1 (fr) * 2004-04-13 2005-10-19 Alcatel Méthode et appareil pour la répartition de charge dans un réseau de communication de données sans fil
WO2007092687A2 (fr) * 2006-02-08 2007-08-16 Motorola, Inc. Régulation de charge dans un système de communication cellulaire
WO2009092440A1 (fr) * 2008-01-23 2009-07-30 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil de mise en commun de ressources de réseau
US20090285179A1 (en) * 2008-05-16 2009-11-19 Bridgewater Systems Corp. Long-Term Evolution (LTE) Packet Data Network Gateway (PDN-GW) Selection
WO2010102127A1 (fr) * 2009-03-04 2010-09-10 Cisco Technology, Inc. Détection de surcharges dans des dispositifs réseau
WO2010132884A1 (fr) * 2009-05-15 2010-11-18 Ciso Technology, Inc. Système et procédé pour un réseau auto-organisateur

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9614926B2 (en) 2014-04-29 2017-04-04 International Business Machines Corporation Parallel I/O write processing for use in clustered file systems having cache storage
US9667736B2 (en) 2014-04-29 2017-05-30 International Business Machines Corporation Parallel I/O read processing for use in clustered file systems having cache storage
US9892130B2 (en) 2014-04-29 2018-02-13 International Business Machines Corporation Parallel I/O read processing for use in clustered file systems having cache storage
US9992274B2 (en) 2014-04-29 2018-06-05 International Business Machines Corporation Parallel I/O write processing for use in clustered file systems having cache storage
US10657108B2 (en) 2014-04-29 2020-05-19 International Business Machines Corporation Parallel I/O read processing for use in clustered file systems having cache storage
KR20160147927A (ko) * 2014-04-30 2016-12-23 어펌드 네트웍스, 인크. 모바일 네트워크의 용량 확장 최적화
EP3138307A4 (fr) * 2014-04-30 2017-12-13 Affirmed Networks Inc. Optimisation d'extension de capacité dans un réseau mobile
KR102178142B1 (ko) 2014-04-30 2020-11-13 마이크로소프트 테크놀로지 라이센싱, 엘엘씨 모바일 네트워크의 용량 확장 최적화
US10912017B2 (en) * 2015-11-10 2021-02-02 Blackberry Limited Gateway selection controlled by network
US11595885B2 (en) 2015-11-10 2023-02-28 Blackberry Limited Gateway selection controlled by network

Similar Documents

Publication Publication Date Title
US11399293B2 (en) System and method of network policy optimization
US11729067B2 (en) Management data analytical KPIS for 5G network traffic and resource
US11323413B2 (en) Methods, systems, and computer readable media for actively discovering and tracking addresses associated with 4G service endpoints
US8452866B2 (en) Network resource management
US11089516B2 (en) Systems and methods for network performance monitoring, event detection, and remediation
GB2587697A (en) Service experience analytics for network slice instance
CN107635015B (zh) 移动终端与服务器端链接的最优路径选择系统及方法
US20200296603A1 (en) Deploying network functions in a communication network based on geo-social network data
US9462049B2 (en) Method and apparatus for providing a centralized subscriber load distribution
US20150121473A1 (en) Method and system for providing multipath tcp proxy services
CN117397230A (zh) 用于在核心网中分发网络功能（nf）高可用性（ha）拓扑信息的方法、系统和计算机可读介质
CN103109502B (zh) 对毫微微小区簇接入进行负载平衡的方法和装置
JP2015023533A (ja) 通信システム
WO2012175140A1 (fr) Sélection de passerelle pour équilibrer une charge
CN106101468B (zh) 传输链路的确定方法及装置
US20200112905A1 (en) Routing optimization based on historical network measures
CN106688256B (zh) 一种背景流量下载方法、设备及系统
CN112470445B (zh) 用于边缘计算拓扑信息开放的方法和设备
JP5894981B2 (ja) 複数基準の選択を有するトポロジサーバを用いて通信アーキテクチャにわたって分散されたノードのネットワークへのアクセス
CN106686034B (zh) Cdn调度增强方法、装置及系统
EP4059209A1 (fr) Procédés, systèmes et supports lisibles par ordinateur pour découvrir et suivre activement des adresses associées à des points d'extrémité de service 4g
US11888598B1 (en) Central routing function (CRF) implementation on a call route
US11825349B2 (en) Methods, systems, and computer readable media for dynamic network function discovery responses
US20240137290A1 (en) Method, apparatus and system for nf selection
KR20210056210A (ko) 무선 통신 시스템의 네트워크 슬라이스에서 데이터 속도 제어를 위한 방법 및 장치

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

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

Country of ref document: EP

Kind code of ref document: A1