EP3567912B1 - Fourniture de fonction de données dans un noeud de passerelle d'accès - Google Patents

Fourniture de fonction de données dans un noeud de passerelle d'accès Download PDF

Info

Publication number
EP3567912B1
EP3567912B1 EP19183947.1A EP19183947A EP3567912B1 EP 3567912 B1 EP3567912 B1 EP 3567912B1 EP 19183947 A EP19183947 A EP 19183947A EP 3567912 B1 EP3567912 B1 EP 3567912B1
Authority
EP
European Patent Office
Prior art keywords
data
sdf
list
gateway
node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP19183947.1A
Other languages
German (de)
English (en)
Other versions
EP3567912A1 (fr
Inventor
Stewart H. Maxwell
Wesley R. Erhart
Srinivas Eswara
Anthony D. Bennett
Eric C. Corum
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Inc
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 Apple Inc filed Critical Apple Inc
Publication of EP3567912A1 publication Critical patent/EP3567912A1/fr
Application granted granted Critical
Publication of EP3567912B1 publication Critical patent/EP3567912B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • 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/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/082—Load balancing or load distribution among bearers or channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/29—Control channels or signalling for resource management between an access point and the access point controlling device
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer

Definitions

  • Mobile or wireless communications networks are capable of carrying both circuit-switched and packet-switched traffic (e.g., voice traffic, data traffic, etc.) between mobile stations and other endpoints, which can be another mobile station or an endpoint connected to a network such as a public-switched telephone network (PSTN) or a packet data network (e.g ., local area networks, the Internet, and so forth).
  • PSTN public-switched telephone network
  • packet data network e.g ., local area networks, the Internet, and so forth.
  • Examples of wireless communications networks that support communication of packet-switched traffic include those that operate according to the GSM (Global System for Mobile) or UMTS (Universal Mobile Telecommunications System) standards, as defined by the Third Generation Partnership Project (3GPP).
  • GSM Global System for Mobile
  • UMTS Universal Mobile Telecommunications System
  • US 2004/053607 A1 discloses a communication system supporting wireless communication of packet data and method and arrangement relating thereto.
  • US 2003/058874 A1 discloses a system and method directed to providing a Mobile Edge Service (MES) in a mobile network.
  • MES Mobile Edge Service
  • a data function is provided in an access gateway node (e.g., a GGSN) of a wireless core network, where the data function is controlled by a control function in a separate control node (e.g., an SGSN).
  • an access gateway node e.g., a GGSN
  • a separate control node e.g., an SGSN
  • Fig. 1 shows an example arrangement of a wireless communications network, according to some embodiments.
  • the wireless communications network depicted in Fig. 1 is a GSM (Global System for Mobile) or LTMTS (Universal Mobile Telecommunications System) wireless communications network.
  • the GSM/UMTS wireless communications network includes a GPRS (General Packet Radio Service) core network 100 that includes a 2G (Second Generation) radio access network 102 for communicating wirelessly with mobile stations 104.
  • the core network 100 also includes Serving GPRS Support Nodes (SGSNs) 106 and Gateway GPRS Support Nodes (GGSNs) 108. Each SGSN 106 is coupled between a radio access network 102 and a GGSN 108.
  • SGSNs Serving GPRS Support Nodes
  • GGSNs Gateway GPRS Support Nodes
  • Each GGSN 108 is effectively a gateway between the core network 100 and an external data network 110, such as the Internet or some other type of network.
  • the external data network 110 can be a packet data network that performs packet-switched communications, such as Internet Protocol (IP) communications.
  • IP Internet Protocol
  • IETF Internet Engineering Task Force
  • RFC Request for Comments
  • IP Internet Protocol
  • RFC 2460 entitled “Internet Protocol, Version 6, IPv6 Specification,” dated December 1998 .
  • the data plane resources can then be distributed across all the GGSNs in the network. This is contrasted with conventional arrangements in which the SGSN data plane resources completely reside in the SGSN, in which case the SGSN's data plane resources are typically engineered with the capacity to handle the sum of all possible subscriber traffic from the radio network resources connected to that SGSN. In many cases, the resources of the SGSN's data plane are not used at full capacity most of the time.
  • the arrangement of Fig. 1 provides a many-to-many relationship between the SGSNs 106 and SDFs in corresponding GGSNs 108.
  • This many-to-many relationship allows balancing of the traffic load across the GGSNs 108 in the wireless communications network. Load balancing can be performed according to an algorithm described below.
  • the SCF in the SGSN continues to control a corresponding SDF in the GGSN.
  • a benefit offered by providing the SCF in the SGSN is that the manner in which billing, lawful interception, and other SGSN tasks are performed do not have to be changed.
  • GGSNs 108 can be used in roaming scenarios.
  • the GGSN can appear to be an SGSN to another GGSN outside the wireless communications network, which is used to provide service to mobile stations from other networks that roam into a network that deploys SDFs in GGSNs.
  • the main difference between the 2G and 3G scenarios is that data paths for subscriber traffic are established directly from a 3G radio access network 202 to respective SDF 112 in the GGSNs 108, whereas for the 2G scenario, subscriber traffic passes through layers of a protocol stack in the SGSN 106 to a corresponding SDF 112.
  • the GGSN 108 also includes a GGSN control plane 308 and a GGSN data plane 310.
  • the GGSN control plane 308 and data plane 310 are unmodified from conventional GGSN control and data planes.
  • subscriber data traffic from the radio access network 202 is communicated to the SDF over link 305 (through a GTP-U tunnel), with the SDF 112 passing the subscriber data traffic to the GGSN data plane 310.
  • the GGSN data plane 310 then detunnels the subscriber data traffic from the SDF 112 to transmit data packets (e.g., IP packets) containing the subscriber data traffic to the external data network 110 over a Gi interface 312.
  • data packets e.g., IP packets
  • the GGSN 316 can either be a normal GGSN (a GGSN without an SGSN SDF deployed in the GGSN) or a DT-GGSN. Subscriber data traffic is carried in a GTP-U tunnel between the SDF 112 and the GGSN 316. From the perspective of the GGSN 316, the SDF 112 in the GGSN 108 appears to be an SDF 112 located in an SGSN.
  • the ability to appear as an SGSN to another GGSN allows a DT-GGSN to enable support for (1) roaming mobile stations that have to access an external data network through a GGSN in the mobile stations' home network, and (2) a wireless communications network that has different types of GGSNs (DT-GGSNs and normal GGSNs).
  • the SGSN protocol stack that is normally deployed within the SGSN is divided into two parts, where one part (402) is deployed in the SGSN 106 and another part (406) is deployed in the SDF 112 in the GGSN 108.
  • BSSGP is described in 3GPP TS 48.018.
  • An LLC layer in the protocol stack 402, 406 is divided into two parts, including an LLC upper part and an LLC lower part.
  • the LLC lower part includes an LLC multiplex procedure 410 that is provided in the SGSN 106.
  • the LLC multiplex procedure 410 routes LLC frames to either the SCF 302 or the SDF 112 based on a service access point identifier (SAPI) contained in the LLC frame.
  • SAPI service access point identifier
  • the LLC layer performs the following example tasks: providing a logical link between the mobile station and the SGSN for end-to-end data exchange, provides user identity protection, provides priority handling of certain packets, provides flow control, provides error detection, and performs ciphering. Additional details of tasks performed by the LLC layer can be found in 3GPP TS 44.064.
  • the SAPIs associated with GPRS mobility management and short messaging are considered to be SAPIs for control-related LLC frames.
  • the remaining SAPIs are used to identify LLC frames containing subscriber data traffic. Since ciphering is the most intensive task performed by the LLC layer of an SGSN, it is useful to locate the ciphering task for subscriber data traffic in the GGSN rather than in the SGSN.
  • the SGSN is able to select an SDF that is not overloaded.
  • an SDF that is not overloaded is also referred to as an SDF that is normally loaded. If no SDF of GGSNs servicing the requested APN meets this condition, the SGSN can select a non-overloaded SDF that is resident on another GGSN.
  • the control protocol (referred to as a Monitor Communication Protocol or MCP in one example implementation) between the SGSN and SDFs includes notification of SDF loading in terms of percentage of maximum number of sessions and remaining committed bit rate.
  • the remaining committed bit rate is the amount of bandwidth remaining once the SDF satisfies its guaranteed bit rate commitments.
  • an SDF is considered overloaded when its maximum number of sessions is exceeded or its remaining committed bit rate is zero. Every message (including heartbeat messages) sent from the SDF to an SGSN contains this information.
  • Each SGSN stores the current loading of each SDF so that the SGSN can select a non-overloaded SDF during an SDF selection phase.
  • each SGSN 106 can provide billing services as provided by a normal SGSN.
  • the SGSN 106 instructs the selected SDF with the bearer path billing requirements (e.g., triggers based on time or volume of data).
  • the SDF sends relevant billing information to the SGSN 106 controlling the connection.
  • the SGSN 106 then bills the user in the same manner as a normal SGSN.
  • the SGSN selects (at 504) an SDF from among a pool of SDFs (which pool of SDFs was retrieved from the SDF directory 114).
  • the SGSN then sends (at 506) an Initial Session Setup message (containing a session identifier or ID to identify the requested session) to the selected SDF in the GGSN.
  • the Initial Session Setup message is sent to perform initial session setup between the SGSN and the SDF.
  • the SDF allocates (at 508) a TEID (Tunnel Endpoint Identifier) of the GGSN.
  • the TEID is an identifier used with GTP-U to tunnel subscriber data traffic between the GGSN and SGSN or between the GGSN and a 3G radio access network.
  • Two TEIDs (of the two endpoints) are used to define a tunnel-the TEID of the GGSN is one of the two TEIDs.
  • Other resources are also allocated at 508.
  • the SDF sends (at 510) an acknowledgment (Ack) message to the SGSN that contains the session ID and the TEID (Tunnel Endpoint Identifier) of the GGSN.
  • the SGSN After receiving the Ack message, the SGSN next sends (at 512) a Create PDP Context Request message (a message used to continue the creation of the requested PDP context) to the Gn interface of the GGSN.
  • the Gn interface is the interface between the SGSN and the GGSN.
  • the GGSN responds (at 514) with a Create PDP Context Response message.
  • the SGSN Upon receipt of the Create PDP Context Response message, the SGSN proceeds to perform (516) radio access bearer setup (if a 3G radio access network is used) or to perform (at 518) a packet flow context procedure (if a 2G radio access network is used).
  • the procedure performed at 516 or 518 ensures that resources are established in the radio access network for wireless communications with the mobile station for the requested session.
  • the mobile station sends (at 526) a Deactivate PDP Context Request message to the SGSN, which in response sends (at 528) a Delete PDP Context Request message to the Gn interface of the GGSN.
  • the GGSN then responds (at 530) with a Delete PDP Context Response message to the SGSN.
  • the SGSN in turn sends (at 532) a Deactivate PDP Context Accept message to the mobile station to indicate that the PDP context has been deactivated.
  • the mobile station performs (at 534) radio access bearer release (if a 3G radio access network is used) or performs (at 536) packet flow context release (if a 3G radio access network is used).
  • the SGSN also sends (at 538) a Deactivate Session message to the SDF, which message contains the session ID, for deactivate the session between the SGSN and the SDF.
  • the SDF sends (at 540) an Ack message to the SGSN.
  • Fig. 6 is a flow diagram of a process performed by an SCF in an SGSN.
  • the SGSN sends (at 602) a query to the SDF directory 114 to retrieve a list of SDF addresses indexed by GGSN identifiers (GGSN IDs).
  • This query can be submitted periodically, in response to predefined events, or in response to some other stimulus.
  • the SGSN next receives (at 604) a list of SDF addresses (indexed according to GGSN IDs) from the SDF directory 114, which list is transmitted by the SDF directory 114 in response to the query.
  • the list of SDF addresses indexed by GGSN IDs is then stored in the SGSN.
  • the SGSN then starts up (at 606) an MCP (Monitor Communication Protocol) link with each of the SDFs in the list.
  • MCP is an example protocol for communications between an SCF and an SDF-other protocols can be used in other implementations.
  • the MCP provides for heartbeat messages between each pair of an SGSN (SCF) and an SDF.
  • MCP also provides messages to report packet loss, SDF operational status changes, and SDF load status.
  • load status is communicated in each message sent from the SDF to the SGSN (including heartbeat messages) in terms of percentage of maximum number of sessions and remaining committed bit rate.
  • the SDF also reports its state to an SGSN.
  • the SDF can be in a locked state or unlocked state. If the SDF is in a locked state, the SGSN does not select that SDF for new PDP Context. However, if the SDF is in the unlocked state, then that SDF can be used for new PDP Context.
  • the SGSN examines (at 612) the first DT-GGSN in the list of DT-GGSNs and GGSNs. The SGSN determines (at 614) if this DT-GGSN has a normally loaded SDF (which is an SDF that is not overloaded). Note that the SGSN is continually receiving messages from SDFs regarding their load status. The load status information of the SDFs are maintained by the SGSN so that the SGSN can perform the determination at 614.
  • the SGSN determines (at 614) that the first DT-GGSN in the list does not have a normally loaded SDF (in other words, all SDFs in the DT-GGSN are overloaded), the SGSN determines whether there is another DT-GGSN in the list for the APN. If so, this other DT-GGSN is selected, and the determination at 614 and subsequent acts are performed.
  • a normally loaded SDF in other words, all SDFs in the DT-GGSN are overloaded
  • the SGSN selects (at 632) a normally loaded SDF on any DT-GGSN, regardless of the APN received in the Activate PDP Context Request message. Because a DT-GGSN that does not serve the APN is being used in this scenario, the connection has to go back through a normal GGSN that does serve the APN. Such a GGSN would be the GGSN 316 shown in Fig. 3 or 4 . This GGSN is selected from the DNS response list (received at 610), which means that the selected GGSN serves the APN of the Activate PDP Context Request message. The address of the GGSN is included in the Initial Session Setup message, and control proceeds to act 618 in Fig. 6 .
  • the SDF checks (at 712) for an incoming message. If the incoming message is the Initial Session Setup message, the SDF receives (at 714) the Initial Session Setup message and allocates (at 716) session resources. Also, the SDF sends an Ack message to the DT-SGSN.
  • the incoming message is a Final Session Setup message
  • the Final Session Setup message including the session ID is received (at 718) from the DT-SGSN.
  • the SDF then completes (at 720) the setup of the indicated session and sends the corresponding Ack message.
  • the SDF receives (at 722) the LOCK command to cause the SDF to be placed in the locked state.
  • the locked status is then sent (at 724) on all MCP links to corresponding DT-SGSNs.
  • the SDF sends (at 726) a Deregistration message to the SDF directory to deregister the SDF in the SDF directory.
  • the SDF takes down (at 728) the indicated session. If any active session remains, the SDF returns to wait for further Deactivate Session messages from corresponding DT-SGSNs.
  • Fig. 8 shows the flow diagram of tasks performed by the SDF directory 114.
  • the SDF directory waits (at 802) for an incoming message.
  • the SDF detects (at 804) the incoming message type. If the incoming message is a query, the SDF directory sends (at 806) a response to the requested DT-SGSN, which response includes identifiers and addresses of SDFs that are indexed to DT-GGSN IDs.
  • each SDF in the SDF directory is associated with a timer. If the timer expires (as detected at 808), the corresponding SDF identifier is removed from the directory (along with the timer). If the timer has not expired, the SDF directory waits for the next incoming message (at 812).
  • a Deregistration message sent by an SDF and received by the SDF directory (“Deregistration" path from the decision diamond 804) also causes the corresponding directory record and timer to be removed (at 810). If the incoming message type is a Registration message ("Registration" path from the decision diamond 804), then the corresponding SDF ID, SDF address, and DT-GGSN ID are stored in a record of the directory. The timer is then started for the new SDF record (at 816).
  • the instructions of the software are loaded or transported to each entity in one of many different ways. For example, code segments including instructions stored on floppy disks, CD or DVD media, a hard disk, or transported through a network interface card, modem, or other interface device are loaded into the entity and executed as corresponding software routines or modules.
  • data signals that are embodied in carrier waves (transmitted over telephone lines, network lines, wireless links, cables, and the like) communicate the code segments, including instructions, to the entity.
  • carrier waves are in the form of electrical, optical, acoustical, electromagnetic, or other types of signals.

Claims (10)

  1. Un procédé de mise en oeuvre d'un noeud de contrôle (106) apte à assurer une gestion de la mobilité dans un réseau sans fil, le procédé comprenant :
    la récupération, depuis un répertoire (114), d'une liste de fonctions de données (112) corrélées à des noeuds passerelles correspondants (108), chaque noeud passerelle (108) comprenant au moins une fonction de données (112) pour le routage de paquets contenant des données de trafic entre un réseau d'accès radio (202) et un réseau de données externe (110), le répertoire (114) étant implémenté dans un noeud distinct des noeuds passerelles (108) et distinct de noeuds de contrôle (106) aptes à assurer une gestion de la mobilité dans le réseau sans fil ;
    la réception, en provenance d'une station mobile (104), d'un message requérant l'activation d'une connexion, la station mobile (104) étant connectée sans fil au réseau d'accès radio (202) ;
    en réponse au message reçu, la sélection, en fonction de la liste récupérée de fonctions de données (112), d'un premier et d'un second noeud passerelle (108) couplés entre le réseau d'accès radio (202) et le réseau de données externe (110) s'il n'y a pas de fonctions de données (112) de la liste récupérée de fonctions de données qui desservent un nom de point d'accès particulier, APN, et sont normalement chargées ; et
    l'envoi, au premier et au second noeud passerelle sélectionnés (108), de commandes pour l'établissement d'une session entre le noeud de contrôle (106) et le premier et le second noeud passerelle sélectionnés (108), et pour l'établissement d'un chemin de données entre le réseau d'accès radio (202) et le premier et le second noeud passerelle sélectionnés (108), le chemin de données contournant le noeud de contrôle (106).
  2. Un procédé selon la revendication 1, dans lequel le premier et le second noeud passerelle (108) comprennent au moins une parmi les plusieurs fonctions de données (112), en plus d'un plan de contrôle et d'un plan de données.
  3. Un procédé selon la revendication 1, dans lequel :
    l'étape de réception d'un message en provenance d'une station mobile (104) comprend la réception d'un message qui contient un nom de point d'accès ;
    le procédé comprend en outre l'envoi d'une interrogation de serveur de noms de domaine, comprenant le nom de point d'accès, pour la récupération d'une liste d'au moins un noeud passerelle (108) desservant un point d'accès identifié par le nom de point d'accès ; et
    l'étape de sélection d'un premier et d'un second noeud passerelle (108) comprend la sélection de l'une des plusieurs fonctions de données (112) qui résident dans l'au moins un noeud passerelle (108) identifié dans la liste.
  4. Un procédé selon la revendication 3, comprenant en outre, en réponse à la détermination qu'aucune des fonctions de données (112) résidant dans l'au moins un noeud passerelle (108) identifié dans la liste n'est surchargée, la sélection d'une fonction de données (112) venant d'un autre noeud passerelle qui n'est pas dans la liste.
  5. Un noeud de contrôle (106) pour opérer une gestion de la mobilité dans un réseau sans fil, comprenant :
    une fonction d'interrogation de répertoire, configurée pour la récupération, depuis un répertoire (114), d'une liste de fonctions de données (112) corrélées à des noeuds passerelles correspondants (108), chaque noeud passerelle (108) comprenant au moins une fonction de données (112) pour le routage de paquets contenant des données de trafic entre un réseau d'accès radio (202) et un réseau de données externe (110), le répertoire (114) étant implémenté dans un noeud distinct des noeuds passerelles (108) et distinct de noeuds de contrôle (106) aptes à assurer une gestion de la mobilité dans le réseau sans fil ;
    au moins un port pouvant être mis en oeuvre pour la réception d'un message provenant d'une station mobile (104) requérant l'activation d'une connexion, la station mobile (104) étant connectée sans fil au réseau d'accès radio (202) ;
    un sélecteur de fonction de données pouvant être mis en oeuvre pour la sélection, en réponse au message reçu, en fonction de la liste récupérée de fonctions de données (112), d'un premier et d'un second noeud passerelle (108) couplés entre le réseau d'accès radio (202) et le réseau de données externe (110) s'il n'y a pas de fonctions de données (112) de la liste récupérée de fonctions de données qui desservent un nom de point d'accès particulier, APN, et sont normalement chargées ; et
    au moins un générateur de messages pouvant être mis en oeuvre pour la génération et l'envoi, au premier et au second noeud passerelle sélectionnés (108), de commandes pour l'établissement d'une session entre le noeud de contrôle (106) et le premier et le second noeud passerelle sélectionnés (108), et pour l'établissement d'un chemin de données entre le réseau d'accès radio (202) et le premier et le second noeud passerelle sélectionnés (108), le chemin de données contournant le noeud de contrôle (106).
  6. Un noeud de contrôle (106) selon la revendication 5, dans lequel :
    le port peut être mis en oeuvre pour la réception d'un message provenant d'une station mobile (104) comprenant un nom de point d'accès ;
    la fonction d'interrogation de répertoire peut être mise en oeuvre pour l'envoi d'une interrogation de serveur de noms de domaine, comprenant le nom de point d'accès,
    pour la récupération d'une liste d'au moins un noeud passerelle (108) desservant un point d'accès identifié par le nom de point d'accès ; et
    le sélecteur de fonction de données peut être mis en oeuvre pour la sélection de l'une des plusieurs fonctions de données (112) qui résident dans l'au moins un noeud passerelle (108) identifié dans la liste.
  7. Un noeud de contrôle (106) selon la revendication 6, dans lequel la sélection de fonction de données peut être mise en oeuvre pour, en réponse à la détermination qu'aucune des fonctions de données (112) résidant dans l'au moins un noeud passerelle (108) identifié dans la liste n'est surchargée, la sélection d'une fonction de données (112) venant d'un autre noeud passerelle qui n'est pas dans la liste.
  8. Un article comprenant un support de stockage lisible par machine contenant des instructions qui, lorsqu'elles sont exécutées, peuvent être mises en œuvre pour faire en sorte qu'un noeud de contrôle (106) d'un réseau sans fil :
    récupère, depuis un répertoire (114), une liste de fonctions de données (112) corrélées à des noeuds passerelles correspondants (108), chaque noeud passerelle (108) comprenant au moins une fonction de données (112) pour le routage de paquets contenant des données de trafic entre un réseau d'accès radio (202) et un réseau de données externe (110), le répertoire (114) étant implémenté dans un noeud distinct du noeud de contrôle (106) et de chacun des noeuds passerelles (108) ;
    reçoive, en provenance d'une station mobile (104), un message requérant l'activation d'une connexion, la station mobile (104) étant connectée sans fil au réseau d'accès radio (202) ;
    en réponse au message reçu, sélectionne, en fonction de la liste récupérée de fonctions de données (112), un premier et d'un second noeud passerelle (108) couplés entre le réseau d'accès radio (202) et le réseau de données externe (110) ; et
    envoie, au premier et au second noeud passerelle sélectionnés (108), des commandes pour l'établissement d'une session entre le noeud de contrôle (106) et le premier et le second noeud passerelle sélectionnés (108), et pour l'établissement d'un chemin de données entre le réseau d'accès radio (202) et le premier et le second noeud passerelle sélectionnés (108), le chemin de données contournant le noeud de contrôle (106).
  9. Un article selon la revendication 8, dans lequel :
    les instructions pour la réception d'un message en provenance d'une station mobile (104) comprennent des instructions pour la réception d'un message qui contient un nom de point d'accès ;
    les instructions comprennent en outre des instructions pour l'envoi d'une interrogation de serveur de noms de domaine, comprenant le nom de point d'accès,
    pour la récupération d'une liste d'au moins un noeud passerelle (108) desservant un point d'accès identifié par le nom de point d'accès ; et
    les instructions pour la sélection d'un premier et d'un second noeud passerelle (108) comprennent des instructions pour la sélection de l'une des plusieurs fonctions de données (112) qui résident dans l'au moins un noeud passerelle (108) identifié dans la liste.
  10. Un article selon la revendication 9, comprenant en outre des instructions pour la sélection d'une fonction de données (112) venant d'un autre noeud passerelle qui n'est pas dans la liste, en réponse à la détermination qu'aucune des fonctions de données (112) résidant dans l'au moins un noeud passerelle (108) identifié dans la liste n'est surchargée.
EP19183947.1A 2005-06-07 2006-06-07 Fourniture de fonction de données dans un noeud de passerelle d'accès Active EP3567912B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US68798905P 2005-06-07 2005-06-07
EP06772354.4A EP1889494B1 (fr) 2005-06-07 2006-06-07 Fourniture de fonction de données dans un noeud de passerelle d'accès
PCT/US2006/022003 WO2006133232A2 (fr) 2005-06-07 2006-06-07 Fourniture de fonction de donnees dans un noeud de passerelle d'acces

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
EP06772354.4A Division EP1889494B1 (fr) 2005-06-07 2006-06-07 Fourniture de fonction de données dans un noeud de passerelle d'accès
EP06772354.4A Division-Into EP1889494B1 (fr) 2005-06-07 2006-06-07 Fourniture de fonction de données dans un noeud de passerelle d'accès

Publications (2)

Publication Number Publication Date
EP3567912A1 EP3567912A1 (fr) 2019-11-13
EP3567912B1 true EP3567912B1 (fr) 2023-08-09

Family

ID=37499066

Family Applications (2)

Application Number Title Priority Date Filing Date
EP06772354.4A Active EP1889494B1 (fr) 2005-06-07 2006-06-07 Fourniture de fonction de données dans un noeud de passerelle d'accès
EP19183947.1A Active EP3567912B1 (fr) 2005-06-07 2006-06-07 Fourniture de fonction de données dans un noeud de passerelle d'accès

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP06772354.4A Active EP1889494B1 (fr) 2005-06-07 2006-06-07 Fourniture de fonction de données dans un noeud de passerelle d'accès

Country Status (4)

Country Link
US (7) US7869393B2 (fr)
EP (2) EP1889494B1 (fr)
CN (1) CN101502166B (fr)
WO (1) WO2006133232A2 (fr)

Families Citing this family (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7894807B1 (en) * 2005-03-30 2011-02-22 Openwave Systems Inc. System and method for routing a wireless connection in a hybrid network
EP1889494B1 (fr) 2005-06-07 2019-12-18 Apple Inc. Fourniture de fonction de données dans un noeud de passerelle d'accès
CN101128041B (zh) * 2006-08-15 2010-05-12 华为技术有限公司 接入网和核心网间下行数据隧道失效后的处理方法和系统
US8406764B1 (en) 2006-08-25 2013-03-26 Apple Inc. Bicasting traffic data during a handover
US8095175B2 (en) * 2006-10-26 2012-01-10 Mcmaster University WLAN-to-WWAN handover methods and apparatus using a WLAN support node having a WWAN interface
JP4858407B2 (ja) * 2006-11-27 2012-01-18 ブラザー工業株式会社 画像読取装置
CN101563948B (zh) * 2006-12-21 2012-09-05 艾利森电话股份有限公司 涉及与通信网络中的移交有关的直接隧道的设备和方法
US9300487B1 (en) 2007-02-06 2016-03-29 Apple Inc. Re-establishing a direct tunnel between an access node and a gateway router
KR101402455B1 (ko) * 2007-04-13 2014-06-03 텔레폰악티에볼라겟엘엠에릭슨(펍) 통신 네트워크에서의 장치 간의 정보의 통신
KR100960115B1 (ko) * 2007-11-29 2010-05-27 한국전자통신연구원 이동통신 시스템 및 그 터널관리방법
US20100296453A1 (en) * 2008-01-28 2010-11-25 Nokia Siemens Networks Oy Apparatus and method comprising at least one resource record
US8185628B2 (en) * 2008-03-07 2012-05-22 At&T Mobility Ii Llc Enhanced policy capabilities for mobile data services
JP5587884B2 (ja) 2008-08-06 2014-09-10 モービック・ネットワークス 無線アクセスネットワーク（ｒａｎ）におけるコンテンツのキャッシング
WO2010057529A1 (fr) * 2008-11-20 2010-05-27 Nokia Siemens Networks Oy Procédé et dispositif d'attribution de trafic à un tunnel direct, produit programme d'ordinateur et support lisible par ordinateur
CN102273149A (zh) * 2008-12-23 2011-12-07 莫维克网络公司 一种利用多层协议的透明代理设备
WO2010088490A1 (fr) * 2009-01-30 2010-08-05 Movik Networks Programmateur de réseau de transport sensible à l'application, à l'utilisation et à la liaison radio
JP5426017B2 (ja) 2009-05-06 2014-02-26 テレフオンアクチーボラゲット エル エム エリクソン（パブル） モバイル・ブロードバンド・デバイス用の専用ゲートウェイ
EP2449824B1 (fr) * 2009-06-30 2016-10-05 Telefonaktiebolaget LM Ericsson (publ) Traitement d'informations de capacité d'accès dans un réseau mobile
EP2465274A1 (fr) * 2009-08-13 2012-06-20 NEC Europe Ltd. Système et procédé permettant de supporter une connectivité ip locale pour un noeud b évolué
CN102511035A (zh) * 2009-11-09 2012-06-20 莫维克网络公司 用于umts/hspa网络中改善的ran效率的突发分组调度器
CN102598628A (zh) * 2010-03-15 2012-07-18 莫维克网络公司 用于多媒体传送的自适应分块和内容感知同步设备及方法
CN102223680B (zh) * 2010-04-16 2013-08-07 华为技术有限公司 流量控制方法、设备及系统
US8799480B2 (en) 2010-07-19 2014-08-05 Movik Networks Content pre-fetching and CDN assist methods in a wireless mobile network
US8565076B2 (en) 2010-09-24 2013-10-22 Movik Networks Destination learning and mobility detection in transit network device in LTE and UMTS radio access networks
US8559299B2 (en) * 2010-11-30 2013-10-15 Telefonaktiebolaget L M Ericsson (Publ) Mobile gateways in pool for session resilience
US8509169B2 (en) * 2010-12-13 2013-08-13 At&T Intellectual Property I, L.P. Methods and apparatus to configure virtual private mobile networks
US9432258B2 (en) 2011-06-06 2016-08-30 At&T Intellectual Property I, L.P. Methods and apparatus to configure virtual private mobile networks to reduce latency
US9386035B2 (en) 2011-06-21 2016-07-05 At&T Intellectual Property I, L.P. Methods and apparatus to configure virtual private mobile networks for security
US10044678B2 (en) 2011-08-31 2018-08-07 At&T Intellectual Property I, L.P. Methods and apparatus to configure virtual private mobile networks with virtual private networks
US8676954B2 (en) * 2011-12-06 2014-03-18 Kaseya International Limited Method and apparatus of performing simultaneous multi-agent access for command execution through a single client
US11082492B2 (en) * 2018-01-10 2021-08-03 EMC IP Holding Company LLC System and method for dynamic backup sessions
CN109089267B (zh) * 2018-08-17 2021-08-20 西安电子科技大学 一种高低频协同组网系统及方法

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5819178A (en) 1996-01-05 1998-10-06 Northern Telecom Limited Methods and apparatus for accessing subscriber information in interconnected wireless telecommunications networks
US6842430B1 (en) * 1996-10-16 2005-01-11 Koninklijke Philips Electronics N.V. Method for configuring and routing data within a wireless multihop network and a wireless network for implementing the same
US6104929A (en) * 1997-06-20 2000-08-15 Telefonaktiebolaget Lm Ericsson Data packet radio service with enhanced mobility management
FI108601B (fi) * 1999-01-05 2002-02-15 Nokia Corp QoS-kartoitustiedon välitys pakettiradioverkossa
US20020028656A1 (en) 2000-02-02 2002-03-07 Yechiam Yemini Method and apparatus for providing forwarding and replication services on a dynamically addressed network
CN1119891C (zh) * 2000-06-30 2003-08-27 华为技术有限公司 具有智能业务交换功能的通用分组无线业务网络系统
EP1182894B1 (fr) * 2000-08-21 2004-05-12 Siemens Aktiengesellschaft Optimisation du traitement et du transport de données en paquets pour un système radio mobile GSM/UMTS à transport séparé pour données et gestion
SE518479C2 (sv) * 2000-10-13 2002-10-15 Ericsson Telefon Ab L M Kommunikationssystem som stödjer trådlös kommunikation av paketdata och förfarande och anordning relaterande därtill
FI110561B (fi) * 2000-12-18 2003-02-14 Nokia Corp IP-pohjainen puheviestintä matkaviestinjärjestelmässä
WO2002052869A2 (fr) * 2000-12-27 2002-07-04 Cellglide Technologies Corp. Attribution de ressources dans des reseaux de telephonie cellulaire
US7076254B2 (en) * 2001-04-25 2006-07-11 Nokia Corporation Telecommunication network having at least two network entities, and communication method
US6545992B2 (en) * 2001-04-30 2003-04-08 Winphoria Networks, Inc. System and method of selecting GGSN in a mobile communications network
US6795701B1 (en) * 2002-05-31 2004-09-21 Transat Technologies, Inc. Adaptable radio link for wireless communication networks
KR100389819B1 (ko) * 2001-07-09 2003-07-02 삼성전자주식회사 부호분할다중접속 이동통신시스템에서 패킷 데이터 전송방법
WO2003026319A2 (fr) 2001-09-21 2003-03-27 Nokia Corporation Systeme et procede d'activation de services du cote mobile
US20030117948A1 (en) 2001-12-26 2003-06-26 Ton Bobby That Dao Method and gateway GPRS support node (GGSN) for control plane redundancy
TW552815B (en) * 2002-03-05 2003-09-11 Ind Tech Res Inst Reallocation method for a distributed GGSN system
US7457275B2 (en) * 2002-04-09 2008-11-25 Jianguo Zhao Method for implementing Iu-Flex based MBMS
MXPA04012156A (es) * 2002-06-06 2005-04-19 Thomson Licensing Sa Red de area local inalambrica (wlan) como un modo de soporte logico para un acoplamiento hibrido en un interfuncionamiento etnre una red local inalambrica (wlan) y un sistema de comunicaciones moviles.
US7529372B2 (en) * 2002-09-25 2009-05-05 Intellon Corporation Method for setting an encryption key for logical network separation
TW569603B (en) 2002-10-01 2004-01-01 Quanta Comp Inc Serving radio network controller relocation in radio telecommunication system
KR100569801B1 (ko) * 2002-12-23 2006-04-10 한국전자통신연구원 다중 패킷 관문 교환장치를 갖는 범용 패킷 무선 서비스 시스템, 및 패킷 관문 교환장치 선택 방법
CN1317869C (zh) * 2003-11-28 2007-05-23 华为技术有限公司 一种对移动台的数据业务漫游计费的实现方法
KR20050054663A (ko) * 2003-12-05 2005-06-10 한국전자통신연구원 무선 패킷 서비스 망에서의 부하 분산 방법 및 이를이용한 호 설정 방법
KR20050103065A (ko) * 2004-04-24 2005-10-27 삼성전자주식회사 Ｕｍｔｓ 망에서의 통합된 ｓｇｓｎ 및 ｇｇｓｎ에서의터널 설정 방법 및 장치
FI20045345A0 (fi) 2004-09-17 2004-09-17 Nokia Corp Tiedonsiirtomenetelmä ja verkkoelementti
EP1889494B1 (fr) 2005-06-07 2019-12-18 Apple Inc. Fourniture de fonction de données dans un noeud de passerelle d'accès
US7536187B2 (en) 2005-08-23 2009-05-19 Cisco Technology, Inc. Supporting communication sessions at a mobile node
US20070213057A1 (en) * 2006-03-08 2007-09-13 Interdigital Technology Corporation Method and apparatus for supporting routing area update procedures in a single tunnel gprs-based wireless communication system

Also Published As

Publication number Publication date
US7869393B2 (en) 2011-01-11
US9019891B2 (en) 2015-04-28
US20100284343A1 (en) 2010-11-11
CN101502166B (zh) 2012-08-22
WO2006133232A3 (fr) 2009-04-23
US20110080832A1 (en) 2011-04-07
EP1889494B1 (fr) 2019-12-18
US9504043B2 (en) 2016-11-22
US20150055595A1 (en) 2015-02-26
US20190029010A1 (en) 2019-01-24
US10575309B2 (en) 2020-02-25
CN101502166A (zh) 2009-08-05
US20150016405A1 (en) 2015-01-15
US8599752B2 (en) 2013-12-03
WO2006133232A2 (fr) 2006-12-14
US9504044B2 (en) 2016-11-22
EP1889494A2 (fr) 2008-02-20
EP1889494A4 (fr) 2011-12-14
US20150230232A1 (en) 2015-08-13
US20060274688A1 (en) 2006-12-07
EP3567912A1 (fr) 2019-11-13
US10039109B2 (en) 2018-07-31

Similar Documents

Publication Publication Date Title
US10575309B2 (en) Providing a data function in an access gateway node
US11632705B2 (en) Device configuration for time sensitive network bridge
US20220124870A1 (en) Network Initiated UPF Sessions Transfer
US11178725B2 (en) Multi access packet/protocol data unit session
CN113194513B (zh) 用于会话管理的方法、装置和系统
US20210274575A1 (en) Application Triggering for a Wireless Device
EP2950583B1 (fr) Utilisation d'un nom de point d'accès pour sélectionner un noeud passerelle d'accès
JP2006516845A (ja) 移動インターネットプロトコルネットワークにおけるパケットデータ提供ノード選出の制御システムおよび方法
JP2007534195A (ja) パケットデータ通信
CN102668685A (zh) 针对改进服务质量处理的电信方法、协议和设备
US20050143087A1 (en) Dynamic selection of a packet data serving node
JP2011509611A (ja) 通信ネットワークにおいて、ルートを最適化するためのテクニック
WO2018206101A1 (fr) Critères de sélection en vue de destinations de données (non ip)

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20190702

AC Divisional application: reference to earlier application

Ref document number: 1889494

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20210208

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20230323

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230523

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AC Divisional application: reference to earlier application

Ref document number: 1889494

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602006060479

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20230809

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1598922

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230809

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231110

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231209

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231211

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231209

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231110

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230809