US20080112396A1 - Method and system for modifying the contents of a database of a communication network, and communication network - Google Patents
Method and system for modifying the contents of a database of a communication network, and communication network Download PDFInfo
- Publication number
- US20080112396A1 US20080112396A1 US12/007,649 US764908A US2008112396A1 US 20080112396 A1 US20080112396 A1 US 20080112396A1 US 764908 A US764908 A US 764908A US 2008112396 A1 US2008112396 A1 US 2008112396A1
- Authority
- US
- United States
- Prior art keywords
- network element
- connection information
- support node
- information sets
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/22—Manipulation of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5076—Update or notification mechanisms, e.g. DynDNS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5084—Providing for device mobility
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/14—Backbone network devices
-
- 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
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/24—Interfaces between hierarchically similar devices between backbone network devices
Definitions
- the present invention relates to a method and system for modifying the contents of a database of a communication network, and to a communication network comprising a database which may be updated in a simplified manner.
- a connection between two entities may be performed using one or more intermediate network elements.
- the connection may be handed over to another network element such as another support node, switching centre, base station, or the like.
- the connection parameters may also be changed in consideration of other parameters such as changing quality of service (QoS) caused e.g. by noise sources of changing strength.
- QoS quality of service
- the connection e.g. a PDP context, may be used to carry data traffic.
- a call is just one example of possible applications.
- Other examples of connections are web surfing (http), remote connections (telnet), file transfers (ftp), etc.
- a new network element may send its address to a co-operating network element for informing this element on the necessity of addressing any subsequent traffic to the new network element.
- a packet-switched network such as a GPRS (General Packet Radio Service) or UMTS (Universal Mobile Telecommunications System) network
- parameter tables defining the handling of the packet transmission.
- These parameter tables may contain data fields defining the supported PDP (Packet Data Protocol) type such as X. 25, PPP, or IP, a PDP address to which the connection is to be directed, and further data such as QoS profile subscribed, access point name (APN) describing the access point to an external packet data network, and the like.
- PDP Packet Data Protocol
- PPP Packet Data Protocol
- IP IP
- Such parameter tables may e.g. be represented by PDP contexts.
- PDP contexts When handling a packet-switched communication, multiple PDP contexts may be activated, e.g. to support multimedia. In such a case, several PDP contexts will have to be updated when handing over the connections from one network element such as an old serving support node (e.g. a SGSN, i.e. a Serving GPRS Support Node) to another network element, for instance, a new serving support node (e.g. a new SGSN). In such a case, the updating of the PDP contexts is performed one by one by sending messages to a network element containing the parameter tables including addresses of the network elements.
- an old serving support node e.g. a SGSN, i.e. a Serving GPRS Support Node
- a new serving support node e.g. a new SGSN
- Such a network element may be, in a GPRS or UMTS network, for instance a GGSN (Gateway GPRS Support Node).
- the network element acknowledges the update requests by sending response messages.
- the number of required messages to be sent on the interfaces between these network elements is therefore equal to twice the number of PDP contexts in case of multiple PDP contexts.
- An object of the present invention is to provide a method for modifying the contents of a database of a communication network which method requires only a small number of messages.
- the invention provides a method and system which may perform update procedures requiring only a small number of messages to be transmitted and/or returned. This reduced number of messages not only reduces the necessary processing load for processing messages but also reduces the signalling load of the network.
- the updating of two or more connection information sets can be performed using only one or a few messages to a network element containing, or co-operating with, a connection handling database, the total number of necessary messages being smaller than twice the number of connection information sets to be updated.
- a single updating message is sent to a network element, and, if at all, only one response message confirming the updating is returned.
- the database preferably stores information on logical tunnels or connections.
- the claimed structure therefore drastically reduces the overhead on the interfaces transmitting the messages, such as the Gn and Gp interfaces in a packet-switched network such as GPRS or UMTS. Likewise, the processing load of the message sending and receiving is decreased.
- connection information sets may comprise information sets of any kind which include one or more addresses of a network element necessary for directing the traffic on the connections.
- connection information sets are PDP contexts wherein at least two PDP contexts are active or at least provided for handling data transmission.
- PDP contexts may be called primary and secondary PDP contexts.
- the first PDP context with a PDP address is called a primary PDP context.
- the next one (s) with the same PDP address is/are called secondary PDP context (s).
- these PDP contexts are updated with only one message from a serving support node to a gateway support node such as from an SGSN to a GGSN.
- the gateway support node acknowledges with only one message to the serving support node.
- the serving support node such as the SGSN
- the gateway support node such as the GGSN
- this changed information can likewise be included in the one message sent to the gateway support node. This information may also be included in the one response message returned from the gateway support node to the new serving support node.
- the invention therefore generally provides a method and system for modifying the contents of a database of a communication network, said database being provided in or for at least one first network element and containing connection information sets for at least one user equipment, the connection information sets including one or more addresses of a second network element, the first network element being adapted to provide connections to and/or from the user equipment, and/or transmit data to and/or from the user equipment, using one or more of the addresses of the second network element included in the connection information sets, wherein, when a connection is to be continued using another, third network element, or using different connection information, a message containing change information is sent to the first network element which, when not refusing this request or update, in response thereto changes the address or addresses contained in the connection information sets.
- the connection information sets preferably comprise or are s active PDP contexts.
- the first network element may be a Gateway GPRS Support Node (GGSN).
- the second and/or third network elements preferably is/are serving support nodes of the communication network.
- the second and/or third network elements may also be RNCs (Radio Network Controllers). A connection may then be changed from one RNC to another RNC.
- RNCs Radio Network Controllers
- the message containing change information may be an “Update PDP Context” message.
- the change information indicates addresses of a further serving support node of the communication network selected for handling the subsequent connection between the first network element and the user equipment.
- the change information may additionally or alternatively indicate Tunnel Endpoint Identifiers (TEIDs).
- the change information will preferably be sent from a serving support node to the first network element when this serving support node is selected for taking over the handling of the connection.
- the communication network is preferably implemented as a GPRS or UMTS network.
- the serving support node may then be a Serving GPRS Support Node (SGSN).
- SGSN Serving GPRS Support Node
- the user equipment may preferably be a mobile station.
- connection information sets may contain further data such as APNs (Access Point Name), TEIDs (two kinds), SGSN addresses (for signalling and user traffic), negotiated QoSs (QoS means Quality of Service), NSAPI etc.
- APNs Access Point Name
- TEIDs two kinds
- SGSN addresses for signalling and user traffic
- QoSs QoS means Quality of Service
- NSAPI NSAPI
- FIG. 1 shows a schematic structure of a basic configuration of one embodiment of the invention
- FIG. 2 illustrates the message flow and method steps performed in an embodiment of the invention
- FIG. 3 shows an embodiment of an updating method performed in a gateway support node
- FIG. 4 illustrates some details of the contents of the messages transmitted in an embodiment of the invention.
- FIG. 1 shows a basic structure of a network 1 representing or incorporating an embodiment of the invention.
- the network 1 is implemented as a GPRS or UMTS system but may also be a packet-switched or circuit-switched network of any other types such as a GSM (Global System for Mobile Telecommunications) or data network, or the like.
- GSM Global System for Mobile Telecommunications
- the network 1 shown in FIG. 1 comprises or communicates with a plurality of mobile stations MS 2 (only one MS is shown).
- the network 1 furthermore comprises a plurality of network elements 3 to 5 which are support nodes (SN) for handling connections to and/or from the mobile stations MS 2 to other terminal equipments such as mobile stations, communication centers, databases and the like.
- the support nodes 3 to 5 are GPRS Support Nodes (GSNs) wherein the support node 3 serves as a Serving GPRS Support Node (SGSN) which handles the connection between the MS 2 and the support node 4 which here provides the function of a Gateway GPRS Support Node (GGSN).
- GSNs GPRS Support Nodes
- SGSN Serving GPRS Support Node
- GGSN Gateway GPRS Support Node
- the GGSN 4 contains', or cooperates with a database 6 storing a plurality of connection information sets such as active PDP contexts for the MS (s) 2 .
- the GGSN 4 may handle a connection to another network (not shown) in which another terminal equipment such as a call originating or terminating equipment may be located.
- the support node 5 may provide the function of an SGSN when e.g. the mobile station 2 is present in the geographical area covered by this support node.
- the support node 5 is assumed to have previously handled the connection to and from the mobile station 2 , and the connection handling has been transferred from SGSN 5 to SGSN 3 because of movement of the mobile station 2 (or because of any other reason) into an area which is covered by SGSN 3 .
- All network elements 2 to 5 shown in FIG. 1 are able to communicate with each other as necessary, as indicated by the double-headed arrows shown between the individual components.
- FIG. 2 shows an embodiment of the message flow between the components 2 to 5 of the network 1 shown in FIG. 1 , i.e. some of the method steps performed in accordance with the present invention.
- FIG. 2 shows an embodiment wherein a routing area update is performed because of movement of the mobile station 2 to another location which is better covered by the SGSN 3 (the new SGSN) than by SGSN 5 which previously handled the connection (the old SGSN).
- step 1 the MS 2 sends a “Routing Area Update Request” to the new SGSN 3 .
- This request may contain information defining the old routing area identity (RAI), the old packet temporary mobile subscriber identity (P-TMSI) and the update type. This request is known and described e.g. in the 3GPP TS 23.060.
- the new SGSN 3 sends, as step 2 .), an “SGSN Context Request” to the old SGSN 5 to get the MM (Mobility Management) and PDP (Packet Data Protocol) contexts for the MS 2 .
- the old SGSN 5 may validate the old P-TMSI, and responds, in a step 3 .), with an “SGSN Context Response”.
- step 4 . the new SGSN 3 sends an “Update PDP Context Request” to the GGSN (s) 4 concerned.
- This “Update PDP Context Request” is a request for updating several PDP contexts, and specifies, as shown in the brackets of step 4 .), the new SGSN address(es) and the new TEID (s) (Tunnel Endpoint Identifier (s)). Instead of one or more TEIDs, the “Update PDP Context Request” may also specify one or more TIDs (Tunnel Identifiers).
- the GGSN 4 updates, in its database 6 , the one or more new SGSN addresses and one or more new TEIDs received in step 4 .), in all of the PDP context fields (primary and secondary PDP context fields) indicated by the message of step 4 .) and activated for the MS 2 , by replacing the previous SGSN address(es) and previous TEID (s) by the new SGSN address(es) and new TEID (s), but maintains all other information contained in the multiple PDP contexts activated for that MS 2 , such as the PDP type, PDP address, access point name (APN) and protocol configuration options parameters.
- PDP context fields primary and secondary PDP context fields
- the GGSN 4 After updating of all the PDP context fields for the MS 2 in step 5 .), the GGSN 4 returns, in step 6 .), an “Update PDP Context Response” message to the new SGSN 3 .
- the new SGSN 3 may perform other steps not shown in FIG. 2 , such as sending a message to the Home Location Register (HLR) informing it of the change of the SGSN.
- HLR Home Location Register
- the new SGSN 3 validates the presence of the mobile station 2 in the new routing area. If all checks are successful, the new SGSN 3 constructs MM and PDP contexts for the mobile station 2 , and a logical link is established between the new SGSN 3 and the MS 2 . The new SGSN 3 responds to the MS 2 with a “Routing Area Update Accept” message indicating the new P-TMSI, and the like. This message is sent in step 7 .) of FIG. 2 . In step 8 .), the MS 2 acknowledges the new P-TMSI with a “Routing Area Update Complete” message.
- the TEID in the header of an Update PDP Context Request message indicates which PDP context the signalling affects.
- SGSN Address For every PDP context, two SGSN addresses are needed (in the Update PDP Context Request message): SGSN Address for Signalling and SGSN Address for User traffic. If the addresses are the same for all the PDP contexts in question, it is enough to send the addresses only once.
- GGSN addresses For every PDP context, two GGSN addresses are needed: GGSN Address for Signalling and GGSN Address for User traffic (in the Update PDP Context Response message).
- NSAPI for every PDP context is needed to identify the PDP context in question.
- the PDP contexts may use the same TEID Signalling but TEID Data is different for every PDP context.
- the SGSN When the SGSN is changing, it is important to send the new information (SGSN address(es) for Signalling, SGSN Address(es) for User traffic, TEID Signalling, TEID Data per NSAPI) from the SGSN to the GGSN.
- the GGSN needs to send the new information (GGSN address(es) for Signalling, GGSN Address(es) for User traffic, TEID Signalling, TEID Data per NSAPI) only if the information changes.
- FIG. 3 shows an updating method carried out by the GGSN 4 .
- the GGSN 4 receives an “Update PDP Context Request” which defines one or more new SGSN addresses and one or more new TEIDs (or TIDs).
- This “Update PDP Context Request” is sent from the new SGSN 3 in step 4 .) of FIG. 2 .
- the GGSN 4 is adapted to perform the steps S 2 to S 4 shown in FIG. 3 as response to the receipt of the “Update PDP Context Request” message.
- step S 2 the GGSN 4 selects, from the database 6 , a first PDP context field activated for the MS 2 (the identity thereof is indicated in the update PDP context request of step S 1 so as to inform the GGSN 4 on the identity of the MS 2 ).
- the GGSN replaces the previously stored SGSN address or addresses (for signalling and/or for user traffic) with the SGSN address(es) indicated in the message sent in step 4 .) of FIG. 2 , and by replacing the previously stored TEIDs (Tunnel Endpoint Identifier Data and/or Tunnel Endpoint Identifier Signalling) by the new TEIDs indicated in the message of step 4 .) of FIG. 2 .
- the GGSN 4 After updating the first PDP context field activated for the MS 2 , the GGSN 4 proceeds to step S 3 wherein the GGSN checks whether its PDP context fields database 6 contains a further PDP context field for that MS 2 . If the answer is yes, the GGSN performs step S 4 and selects the next PDP context field for that MS 2 . The process then goes back to step S 2 , wherein the selected next PDP context field for that MS 2 is updated by updating the SGSN address (es) and TEID (s).
- step S 3 is again carried out and, if present, a next PDP context field for that MS 2 is selected in step S 4 , and step S 2 is performed again.
- step S 3 is “NO” whereupon the updating process ends (step S 5 ).
- FIG. 4 illustrates the contents of the messages transmitted when performing a change of the. SGSNs, in more detail.
- the shown steps essentially correspond to steps 3 .), 4 .), and 6 .) of FIG. 2 .
- the invention has been described by referring to multiple PDP contexts activated for the MS 2 which represent a plurality of connection information sets.
- the invention is also applicable with regard to other types of connection information sets wherein two or more connection information sets are stored for handling a communication to and from an entity such as a user equipment.
- the invention is not only applicable to packet-switched networks such as GPRS or UMTS, but can also be incorporated in other types of networks.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Telephonic Communication Services (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Transition And Organic Metals Composition Catalysts For Addition Polymerization (AREA)
Abstract
A communication network, system and method are provided in which at least one database is provided in or for a first network element and contains connection information sets for the user equipment, the connection information sets including an address of a second network element, and the connection information sets corresponding to active or activated connections. The first network element provides connections, to and/or from user equipment, and/or transmits data to and/or from the user equipment, using one or more of the addresses of the second network element included in the connection information sets. The communication network, system, and method are also configured to send, when the connection is to be continued using another network element or using different connection information, a message containing change information to the first network element which is configured to change, in response to this message, the address contained in at least two connection information sets.
Description
- This is a continuation application of U.S. patent application Ser. No. 10/275,118, filed on Apr. 29, 2003. The disclosure of the prior application is hereby incorporated by reference in its entirety.
- The present invention relates to a method and system for modifying the contents of a database of a communication network, and to a communication network comprising a database which may be updated in a simplified manner.
- When handling a connection in a communication network, there is sometimes the need of actualizing the connection parameters in order to compensate, or take account of, changed conditions.
- For instance, in a mobile communication, a connection between two entities (e.g. a call originating entity and a call terminating entity) may be performed using one or more intermediate network elements. When the entity, or any network element involved in providing the connection, is moving, the connection may be handed over to another network element such as another support node, switching centre, base station, or the like. The connection parameters may also be changed in consideration of other parameters such as changing quality of service (QoS) caused e.g. by noise sources of changing strength. The connection, e.g. a PDP context, may be used to carry data traffic. A call is just one example of possible applications. Other examples of connections are web surfing (http), remote connections (telnet), file transfers (ftp), etc.
- When the connection is handed over to another network element, one or more of the network elements involved in handling the connection must be informed on this change. For example, a new network element may send its address to a co-operating network element for informing this element on the necessity of addressing any subsequent traffic to the new network element.
- In a packet-switched network such as a GPRS (General Packet Radio Service) or UMTS (Universal Mobile Telecommunications System) network, there may be provided parameter tables defining the handling of the packet transmission. These parameter tables may contain data fields defining the supported PDP (Packet Data Protocol) type such as X. 25, PPP, or IP, a PDP address to which the connection is to be directed, and further data such as QoS profile subscribed, access point name (APN) describing the access point to an external packet data network, and the like.
- Such parameter tables may e.g. be represented by PDP contexts.
- When handling a packet-switched communication, multiple PDP contexts may be activated, e.g. to support multimedia. In such a case, several PDP contexts will have to be updated when handing over the connections from one network element such as an old serving support node (e.g. a SGSN, i.e. a Serving GPRS Support Node) to another network element, for instance, a new serving support node (e.g. a new SGSN). In such a case, the updating of the PDP contexts is performed one by one by sending messages to a network element containing the parameter tables including addresses of the network elements. Such a network element may be, in a GPRS or UMTS network, for instance a GGSN (Gateway GPRS Support Node). The network element acknowledges the update requests by sending response messages. The number of required messages to be sent on the interfaces between these network elements is therefore equal to twice the number of PDP contexts in case of multiple PDP contexts.
- A similar situation will occur when parameter tables of other nature are updated one by one for adapting the system to changed conditions.
- An object of the present invention is to provide a method for modifying the contents of a database of a communication network which method requires only a small number of messages.
- The invention provides a method and system which may perform update procedures requiring only a small number of messages to be transmitted and/or returned. This reduced number of messages not only reduces the necessary processing load for processing messages but also reduces the signalling load of the network.
- According to the invention, the updating of two or more connection information sets can be performed using only one or a few messages to a network element containing, or co-operating with, a connection handling database, the total number of necessary messages being smaller than twice the number of connection information sets to be updated. In a preferred case, only a single updating message is sent to a network element, and, if at all, only one response message confirming the updating is returned.
- The database preferably stores information on logical tunnels or connections. The claimed structure therefore drastically reduces the overhead on the interfaces transmitting the messages, such as the Gn and Gp interfaces in a packet-switched network such as GPRS or UMTS. Likewise, the processing load of the message sending and receiving is decreased.
- The connection information sets may comprise information sets of any kind which include one or more addresses of a network element necessary for directing the traffic on the connections.
- In a preferred embodiment the connection information sets are PDP contexts wherein at least two PDP contexts are active or at least provided for handling data transmission. Such a provision or activation of multiple PDP contexts is useful under several conditions such as supporting multimedia transmission. Such PDP contexts may be called primary and secondary PDP contexts. The first PDP context with a PDP address is called a primary PDP context. The next one (s) with the same PDP address is/are called secondary PDP context (s).
- In a preferred embodiment, these PDP contexts are updated with only one message from a serving support node to a gateway support node such as from an SGSN to a GGSN. The gateway support node acknowledges with only one message to the serving support node.
- When for instance changing the serving support node (such as the SGSN) because of a movement of one or more components involved in handling a connection, and/or because of other reason, only the address or addresses of that component (e.g. the serving support node address for signalling and/or the serving support node address for user traffic) will change. It will then be enough to send only the new serving support node address(es) to the gateway support node (such as the GGSN). In case further information should likewise change such as TEIDs Tunnel Endpoint Identifier Data and/or Tunnel Endpoint Identifier Signalling) or TIDs (Tunnel Identifiers), this changed information can likewise be included in the one message sent to the gateway support node. This information may also be included in the one response message returned from the gateway support node to the new serving support node.
- The invention therefore generally provides a method and system for modifying the contents of a database of a communication network, said database being provided in or for at least one first network element and containing connection information sets for at least one user equipment, the connection information sets including one or more addresses of a second network element, the first network element being adapted to provide connections to and/or from the user equipment, and/or transmit data to and/or from the user equipment, using one or more of the addresses of the second network element included in the connection information sets, wherein, when a connection is to be continued using another, third network element, or using different connection information, a message containing change information is sent to the first network element which, when not refusing this request or update, in response thereto changes the address or addresses contained in the connection information sets. The connection information sets preferably comprise or are s active PDP contexts. The first network element may be a Gateway GPRS Support Node (GGSN). The second and/or third network elements preferably is/are serving support nodes of the communication network.
- The second and/or third network elements may also be RNCs (Radio Network Controllers). A connection may then be changed from one RNC to another RNC.
- The message containing change information may be an “Update PDP Context” message.
- In a preferred embodiment, the change information indicates addresses of a further serving support node of the communication network selected for handling the subsequent connection between the first network element and the user equipment. The change information may additionally or alternatively indicate Tunnel Endpoint Identifiers (TEIDs).
- The change information will preferably be sent from a serving support node to the first network element when this serving support node is selected for taking over the handling of the connection.
- The communication network is preferably implemented as a GPRS or UMTS network. The serving support node may then be a Serving GPRS Support Node (SGSN).
- The user equipment may preferably be a mobile station.
- The connection information sets may contain further data such as APNs (Access Point Name), TEIDs (two kinds), SGSN addresses (for signalling and user traffic), negotiated QoSs (QoS means Quality of Service), NSAPI etc.
-
FIG. 1 shows a schematic structure of a basic configuration of one embodiment of the invention; -
FIG. 2 illustrates the message flow and method steps performed in an embodiment of the invention; -
FIG. 3 shows an embodiment of an updating method performed in a gateway support node; and -
FIG. 4 illustrates some details of the contents of the messages transmitted in an embodiment of the invention. -
FIG. 1 shows a basic structure of anetwork 1 representing or incorporating an embodiment of the invention. In the present example, thenetwork 1 is implemented as a GPRS or UMTS system but may also be a packet-switched or circuit-switched network of any other types such as a GSM (Global System for Mobile Telecommunications) or data network, or the like. - The
network 1 shown inFIG. 1 comprises or communicates with a plurality of mobile stations MS 2 (only one MS is shown). Thenetwork 1 furthermore comprises a plurality ofnetwork elements 3 to 5 which are support nodes (SN) for handling connections to and/or from themobile stations MS 2 to other terminal equipments such as mobile stations, communication centers, databases and the like. In the shown example, thesupport nodes 3 to 5 are GPRS Support Nodes (GSNs) wherein thesupport node 3 serves as a Serving GPRS Support Node (SGSN) which handles the connection between theMS 2 and thesupport node 4 which here provides the function of a Gateway GPRS Support Node (GGSN). - The basic structure of a network of such a type is known and will therefore not be described here in detail. The
GGSN 4 contains', or cooperates with adatabase 6 storing a plurality of connection information sets such as active PDP contexts for the MS (s) 2. - The
GGSN 4 may handle a connection to another network (not shown) in which another terminal equipment such as a call originating or terminating equipment may be located. - The
support node 5 may provide the function of an SGSN when e.g. themobile station 2 is present in the geographical area covered by this support node. In the present example, thesupport node 5 is assumed to have previously handled the connection to and from themobile station 2, and the connection handling has been transferred fromSGSN 5 toSGSN 3 because of movement of the mobile station 2 (or because of any other reason) into an area which is covered bySGSN 3. - All
network elements 2 to 5 shown inFIG. 1 are able to communicate with each other as necessary, as indicated by the double-headed arrows shown between the individual components. -
FIG. 2 shows an embodiment of the message flow between thecomponents 2 to 5 of thenetwork 1 shown inFIG. 1 , i.e. some of the method steps performed in accordance with the present invention.FIG. 2 shows an embodiment wherein a routing area update is performed because of movement of themobile station 2 to another location which is better covered by the SGSN 3 (the new SGSN) than bySGSN 5 which previously handled the connection (the old SGSN). - In
step 1.), theMS 2 sends a “Routing Area Update Request” to thenew SGSN 3. This request may contain information defining the old routing area identity (RAI), the old packet temporary mobile subscriber identity (P-TMSI) and the update type. This request is known and described e.g. in the 3GPP TS 23.060. - The
new SGSN 3 sends, asstep 2.), an “SGSN Context Request” to theold SGSN 5 to get the MM (Mobility Management) and PDP (Packet Data Protocol) contexts for theMS 2. Theold SGSN 5 may validate the old P-TMSI, and responds, in astep 3.), with an “SGSN Context Response”. - In
step 4.), thenew SGSN 3 sends an “Update PDP Context Request” to the GGSN (s) 4 concerned. This “Update PDP Context Request” is a request for updating several PDP contexts, and specifies, as shown in the brackets ofstep 4.), the new SGSN address(es) and the new TEID (s) (Tunnel Endpoint Identifier (s)). Instead of one or more TEIDs, the “Update PDP Context Request” may also specify one or more TIDs (Tunnel Identifiers). - In
step 5.), theGGSN 4 updates, in itsdatabase 6, the one or more new SGSN addresses and one or more new TEIDs received instep 4.), in all of the PDP context fields (primary and secondary PDP context fields) indicated by the message ofstep 4.) and activated for theMS 2, by replacing the previous SGSN address(es) and previous TEID (s) by the new SGSN address(es) and new TEID (s), but maintains all other information contained in the multiple PDP contexts activated for thatMS 2, such as the PDP type, PDP address, access point name (APN) and protocol configuration options parameters. - For updating all PDP contexts activated for a
mobile station 2, it is therefore sufficient to send only one request such as “Update PDP Context Request” from thenetwork element 3 to thenetwork element 4. - After updating of all the PDP context fields for the
MS 2 instep 5.), theGGSN 4 returns, instep 6.), an “Update PDP Context Response” message to thenew SGSN 3. - The
new SGSN 3 may perform other steps not shown inFIG. 2 , such as sending a message to the Home Location Register (HLR) informing it of the change of the SGSN. - The
new SGSN 3 validates the presence of themobile station 2 in the new routing area. If all checks are successful, thenew SGSN 3 constructs MM and PDP contexts for themobile station 2, and a logical link is established between thenew SGSN 3 and theMS 2. Thenew SGSN 3 responds to theMS 2 with a “Routing Area Update Accept” message indicating the new P-TMSI, and the like. This message is sent instep 7.) ofFIG. 2 . Instep 8.), theMS 2 acknowledges the new P-TMSI with a “Routing Area Update Complete” message. - Generally, the TEID in the header of an Update PDP Context Request message indicates which PDP context the signalling affects. Here, it is proposed to set the TEID according to the TEID of the primary PDP context.
- For every PDP context, two SGSN addresses are needed (in the Update PDP Context Request message): SGSN Address for Signalling and SGSN Address for User traffic. If the addresses are the same for all the PDP contexts in question, it is enough to send the addresses only once.
- The same applies to GGSN addresses. For every PDP context, two GGSN addresses are needed: GGSN Address for Signalling and GGSN Address for User traffic (in the Update PDP Context Response message).
- In the Update PDP Context Request message, NSAPI for every PDP context is needed to identify the PDP context in question. The PDP contexts may use the same TEID Signalling but TEID Data is different for every PDP context.
- When the SGSN is changing, it is important to send the new information (SGSN address(es) for Signalling, SGSN Address(es) for User traffic, TEID Signalling, TEID Data per NSAPI) from the SGSN to the GGSN. The GGSN needs to send the new information (GGSN address(es) for Signalling, GGSN Address(es) for User traffic, TEID Signalling, TEID Data per NSAPI) only if the information changes.
-
FIG. 3 shows an updating method carried out by theGGSN 4. In step S1, theGGSN 4 receives an “Update PDP Context Request” which defines one or more new SGSN addresses and one or more new TEIDs (or TIDs). This “Update PDP Context Request” is sent from thenew SGSN 3 instep 4.) ofFIG. 2 . TheGGSN 4 is adapted to perform the steps S2 to S4 shown inFIG. 3 as response to the receipt of the “Update PDP Context Request” message. In step S2, theGGSN 4 selects, from thedatabase 6, a first PDP context field activated for the MS 2 (the identity thereof is indicated in the update PDP context request of step S1 so as to inform theGGSN 4 on the identity of the MS 2). For performing the updating of step S2, the GGSN replaces the previously stored SGSN address or addresses (for signalling and/or for user traffic) with the SGSN address(es) indicated in the message sent instep 4.) ofFIG. 2 , and by replacing the previously stored TEIDs (Tunnel Endpoint Identifier Data and/or Tunnel Endpoint Identifier Signalling) by the new TEIDs indicated in the message ofstep 4.) ofFIG. 2 . - After updating the first PDP context field activated for the
MS 2, theGGSN 4 proceeds to step S3 wherein the GGSN checks whether its PDP context fieldsdatabase 6 contains a further PDP context field for thatMS 2. If the answer is yes, the GGSN performs step S4 and selects the next PDP context field for thatMS 2. The process then goes back to step S2, wherein the selected next PDP context field for thatMS 2 is updated by updating the SGSN address (es) and TEID (s). - Thereafter, step S3 is again carried out and, if present, a next PDP context field for that
MS 2 is selected in step S4, and step S2 is performed again. When all PDP context fields for theMS 2 in question have been updated, the answer of step S3 is “NO” whereupon the updating process ends (step S5). -
FIG. 4 illustrates the contents of the messages transmitted when performing a change of the. SGSNs, in more detail. The shown steps essentially correspond tosteps 3.), 4.), and 6.) ofFIG. 2 . - In the above embodiments, the invention has been described by referring to multiple PDP contexts activated for the
MS 2 which represent a plurality of connection information sets. The invention is also applicable with regard to other types of connection information sets wherein two or more connection information sets are stored for handling a communication to and from an entity such as a user equipment. Furthermore, the invention is not only applicable to packet-switched networks such as GPRS or UMTS, but can also be incorporated in other types of networks.
Claims (27)
1. A method for modifying the contents of a database of a communication network, the method comprising:
configuring said database to be in or for at least one first network element and containing connection information sets for at least one user equipment;
configuring the connection information sets to include one or more addresses of a second network element, and the connection information sets to correspond to active or activated connections;
configuring the first network element to provide connections to and/or from the user equipment, and/or transmit data to and/or from the user equipment, using one or more of the addresses of the second network element included in the connection information sets;
when the connection is to be continued using another network element, third network element, or using different connection information, sending a message containing change information to the first network element; and
configuring the first network element to change, in response to this message, the address or addresses contained in at least two connection information sets, wherein the connection information sets are active packet data protocol contexts.
2. The method according to claim 1 , wherein the connection information sets contain information which defines parameters for the connection.
3. The method according to claim 1 , wherein the first network element is a gateway general packet radio service support node.
4. The method according to claim 1 , wherein the second and/or third network elements is/are serving support nodes of the communication network.
5. The method according to claim 1 , wherein the second and/or third network elements is/are radio network controllers of the communication network.
6. The method according to claim 1 , wherein
the change information indicates addresses of a further serving support node of the communication network selected for handling the subsequent connection between the first network element and the user equipment.
7. The method according to claim 1 , wherein
the change information indicates tunnel endpoint identifiers or tunnel identifiers.
8. The method according to claim 1 , wherein
the change information is sent from a serving support node to the first network element when this serving support node is selected for taking over the handling of the connection.
9. The method according to claim 8 , wherein the serving support node is a serving gateway general packet radio service support node.
10. The method according to claim 1 , wherein the communication network is a general packet radio service or a universal mobile telecommunications system network.
11. A system for modifying the contents of a database of a communication network, the system comprising:
a first network element;
a second network element; and
a user equipment, wherein said database is provided in or for the first network element and contains connection information sets for the user equipment, the connection information sets including one or more addresses of the second network element, and the connection information sets corresponding to active or activated connections, wherein the first network element is configured to provide connections to and/or from the user equipment, and/or transmit data to and/or from the user equipment, using one or more of the addresses of the second network element included in the connection information sets, wherein, when the connection is to be continued using another network element, third network element, or using different connection information, the system is configured to send a message containing change information to the first network element which is configured to change, in response to this message, the address or addresses contained in at least two connection information sets, and wherein the connection information sets are active packet data protocol contexts.
12. The system according to claim 11 , wherein the connection information sets contain information defining parameters for the connection.
13. The system according to claim 11 , wherein the connection information sets are active-packet data protocol contexts.
14. The system according to claim 11 , wherein the first network element is a gateway general packet radio service support node.
15. The system according to claim 11 , wherein the second and/or third network elements is/are serving support nodes of the communication network.
16. The system according to claim 11 , wherein the change information indicates addresses of a further serving support node of the communication network selected for handling the subsequent connection between the first network element and the user equipment.
17. The system according to claim 11 , wherein the change information indicates tunnel endpoint identifiers or tunnel identifiers.
18. The system according to claim 11 , wherein, when a serving support node is selected for taking over the handling of the connection, this serving support node is configured to send the change information to the first network element.
19. The system according to claim 18 , wherein the serving support node is a serving general packet radio service support node.
20. The system according to claim 11 , wherein the communication network is a general packet radio service or a universal mobile telecommunications system network.
21. A communication network having several network elements, comprising:
a first network element;
a second network element; and
a user equipment, wherein at least one database is provided in or for the first network element and contains connection information sets for the user equipment, the connection information sets including one or more addresses of the second network element, and the connection information sets corresponding to active or activated connections, wherein the first network element is configured to provide connections, to and/or from the user equipment, and/or transmit data to and/or from the user equipment, using one or more of the addresses of the second network element included in the connection information sets, wherein the communication network is configured to send, when the connection is to be continued using another network element, third network element, or using different connection information, a message containing change information to the first network element which is configured to change, in response to this message, the address or addresses contained in at least two connection information sets, and wherein the connection information sets are active packet data protocol contexts.
22. The network according to claim 21 , wherein the communication network is a general packet radio service or a universal mobile telecommunications system network.
23. A serving general packet radio service support node configured to modify contents of a database provided in or for the serving support node, said database comprising connection information sets for a user equipment, the connection information sets comprising one or more addresses of a network element, and the connection information sets corresponding to active or activated connections, wherein the serving support node is configured to provide connections to and/or from the user equipment, and/or transmit data to and/or from the user equipment, using one or more of the addresses of the network element included in the connection information sets, wherein, when the connection is to be continued using another network element, or using different connection information, the serving support node is configured to receive a message comprising change information and the serving support node is configured to change, in response to this message, the address or addresses contained in at least two connection information sets, and wherein the connection information sets are active packet data protocol contexts.
24. A gateway general packet radio service support node configured to modify contents of a database provided in or for the gateway support node, said database comprising connection information sets for a user equipment, the connection information sets including one or more addresses of a network element, and the connection information sets corresponding to active or activated connections, wherein the gateway support node is configured to provide connections to and/or from the user equipment, and/or transmit data to and/or from the user equipment, using one or more of the addresses of the network element included in the connection information sets, wherein, when the connection is to be continued using another network element, or using different connection information, the gateway support node is configured to receive a message containing change information, the gateway support node is configured to change, in response to this message, the address or addresses contained in at least two connection information sets, and wherein the connection information sets are active packet data protocol contexts.
25. The method according to claim 1 , further comprising:
providing at least two packet data protocol contexts as active packet data protocol contexts which are updated with only one message from a serving support node to a gateway support node.
26. The system according to claim 11 , wherein at least two packet data protocol contexts are active packet data protocol contexts which are updated with only one message from a serving support node to a gateway support node.
27. The network according to claim 22 , wherein at least two packet data protocol contexts are active packet data protocol contexts which are updated with only one message from a serving support node to a gateway support node.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/007,649 US20080112396A1 (en) | 2000-05-08 | 2008-01-14 | Method and system for modifying the contents of a database of a communication network, and communication network |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2000/004118 WO2001086991A1 (en) | 2000-05-08 | 2000-05-08 | Method and system for modifying the contents of a database of a communication network, and communication network |
US27511803A | 2003-04-29 | 2003-04-29 | |
US12/007,649 US20080112396A1 (en) | 2000-05-08 | 2008-01-14 | Method and system for modifying the contents of a database of a communication network, and communication network |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2000/004118 Continuation WO2001086991A1 (en) | 2000-05-08 | 2000-05-08 | Method and system for modifying the contents of a database of a communication network, and communication network |
US27511803A Continuation | 2000-05-08 | 2003-04-29 |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080112396A1 true US20080112396A1 (en) | 2008-05-15 |
Family
ID=8163933
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/275,118 Expired - Lifetime US7333473B1 (en) | 2000-05-08 | 2000-05-08 | Method and system for modifying the contents of a database of a communication network, and communication network |
US12/007,649 Abandoned US20080112396A1 (en) | 2000-05-08 | 2008-01-14 | Method and system for modifying the contents of a database of a communication network, and communication network |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/275,118 Expired - Lifetime US7333473B1 (en) | 2000-05-08 | 2000-05-08 | Method and system for modifying the contents of a database of a communication network, and communication network |
Country Status (7)
Country | Link |
---|---|
US (2) | US7333473B1 (en) |
EP (1) | EP1282992B1 (en) |
AT (1) | ATE413075T1 (en) |
AU (1) | AU2000245634A1 (en) |
DE (1) | DE60040688D1 (en) |
ES (1) | ES2315229T3 (en) |
WO (1) | WO2001086991A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8855071B1 (en) * | 2012-01-04 | 2014-10-07 | Juniper Networks, Inc. | Handling errors in subscriber session management within mobile networks |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7333473B1 (en) * | 2000-05-08 | 2008-02-19 | Nokia Corporation | Method and system for modifying the contents of a database of a communication network, and communication network |
CN101128043B (en) | 2006-08-15 | 2011-02-02 | 华为技术有限公司 | Data processing method for switching between systems or change |
CA2664671C (en) * | 2007-03-12 | 2014-07-08 | Nec Corporation | Mobile communication system and communication control method |
US9769287B2 (en) * | 2010-05-10 | 2017-09-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Reducing protocol overhead in single-block packet access procedures |
US10411954B2 (en) * | 2015-10-13 | 2019-09-10 | International Business Machines Corporation | Pattern based network configuration |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6496690B1 (en) * | 1999-05-07 | 2002-12-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Prepaid subscriber service for packet-switched and circuit-switched radio telecommunications networks |
US7333473B1 (en) * | 2000-05-08 | 2008-02-19 | Nokia Corporation | Method and system for modifying the contents of a database of a communication network, and communication network |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2307828A (en) * | 1995-12-01 | 1997-06-04 | Northern Telecom Ltd | Providing Packet Data to a Mobile Communications System |
US6091952A (en) | 1996-08-30 | 2000-07-18 | Nortel Networks Corporation | Distributed subscriber data management in wireless networks from a central perspective |
WO1998059505A1 (en) * | 1997-06-20 | 1998-12-30 | Telefonaktiebolaget Lm Ericsson (Publ) | Data packet radio service with enhanced mobility management |
US6104929A (en) * | 1997-06-20 | 2000-08-15 | Telefonaktiebolaget Lm Ericsson | Data packet radio service with enhanced mobility management |
FI105309B (en) * | 1997-06-24 | 2000-07-14 | Nokia Mobile Phones Ltd | Mobile communication systems |
JP2001515314A (en) * | 1997-09-04 | 2001-09-18 | ブリティッシュ・テレコミュニケーションズ・パブリック・リミテッド・カンパニー | Telecommunications system |
US6137783A (en) * | 1997-12-02 | 2000-10-24 | Ericsson Inc | System and method for reduced network information handovers |
DE19849578A1 (en) * | 1998-10-27 | 2000-01-13 | Siemens Ag | Method and cellular network for handling a packet data service |
US6230005B1 (en) * | 1998-10-01 | 2001-05-08 | Nokia Telecommunications, Oy | Method and apparatus for providing overlay to support third generation cellular services |
US6480476B1 (en) * | 1998-10-15 | 2002-11-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Variable sleep mode for mobile stations in a mobile communications |
US6466556B1 (en) * | 1999-07-23 | 2002-10-15 | Nortel Networks Limited | Method of accomplishing handover of packet data flows in a wireless telecommunications system |
-
2000
- 2000-05-08 US US10/275,118 patent/US7333473B1/en not_active Expired - Lifetime
- 2000-05-08 ES ES00927166T patent/ES2315229T3/en not_active Expired - Lifetime
- 2000-05-08 DE DE60040688T patent/DE60040688D1/en not_active Expired - Lifetime
- 2000-05-08 EP EP00927166A patent/EP1282992B1/en not_active Expired - Lifetime
- 2000-05-08 AU AU2000245634A patent/AU2000245634A1/en not_active Abandoned
- 2000-05-08 AT AT00927166T patent/ATE413075T1/en not_active IP Right Cessation
- 2000-05-08 WO PCT/EP2000/004118 patent/WO2001086991A1/en active Application Filing
-
2008
- 2008-01-14 US US12/007,649 patent/US20080112396A1/en not_active Abandoned
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6496690B1 (en) * | 1999-05-07 | 2002-12-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Prepaid subscriber service for packet-switched and circuit-switched radio telecommunications networks |
US7333473B1 (en) * | 2000-05-08 | 2008-02-19 | Nokia Corporation | Method and system for modifying the contents of a database of a communication network, and communication network |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8855071B1 (en) * | 2012-01-04 | 2014-10-07 | Juniper Networks, Inc. | Handling errors in subscriber session management within mobile networks |
Also Published As
Publication number | Publication date |
---|---|
ATE413075T1 (en) | 2008-11-15 |
EP1282992A1 (en) | 2003-02-12 |
ES2315229T3 (en) | 2009-04-01 |
AU2000245634A1 (en) | 2001-11-20 |
EP1282992B1 (en) | 2008-10-29 |
WO2001086991A1 (en) | 2001-11-15 |
DE60040688D1 (en) | 2008-12-11 |
US7333473B1 (en) | 2008-02-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7979070B2 (en) | Mobile equipment for sending an attach request to a network | |
EP1192819B1 (en) | Method and device for performing a packet data communication | |
EP0992170B1 (en) | Method of operating a dual mode mobile telephone | |
AU2004214311B2 (en) | Routing procedure for a commnication system | |
US6879834B2 (en) | Method and system for limiting quality of service of data transmission | |
EP1292869B1 (en) | Changing a first subscriber identifier to a second identifier | |
CN101978716B (en) | For the method that optimizing user equipment PDN (packet data network) connects | |
EP1325596B1 (en) | Communication system supporting wireless communication of packet data and method and arrangement relating thereto | |
US6219548B1 (en) | Support for transfer of neighboring cell information between MSC areas for VGCS/VBS calls | |
US20080112396A1 (en) | Method and system for modifying the contents of a database of a communication network, and communication network | |
EP1599010A1 (en) | Protocol conversion device and method | |
CN101658053B (en) | Communication of information between devices in communication networks | |
JP2002543677A (en) | Virtual numbering plan for interworking between heterogeneous networks | |
US20070249357A1 (en) | Method for Switching Between Two Telephone Services | |
CN101277470B (en) | Method and system for obtaining IP-CAN bearing | |
CN100486381C (en) | Method for GGSN in packet domain to obtain information of starting up single tunnel by SGSN | |
CN100515132C (en) | Method and system for roaming between mobile network and wireless network | |
US20050099990A1 (en) | Logical connection modification | |
EP1655886B1 (en) | A method for processing a request to create the packet data protocol context | |
JP4142459B2 (en) | Wireless communication system, wireless communication method, wireless control device, and local exchange |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |