EP1867136A2 - Telecommunications system and method - Google Patents
Telecommunications system and methodInfo
- Publication number
- EP1867136A2 EP1867136A2 EP06794538A EP06794538A EP1867136A2 EP 1867136 A2 EP1867136 A2 EP 1867136A2 EP 06794538 A EP06794538 A EP 06794538A EP 06794538 A EP06794538 A EP 06794538A EP 1867136 A2 EP1867136 A2 EP 1867136A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- mobile
- user equipment
- access network
- internet protocol
- communications session
- 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.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
- H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0029—Provisions for intelligent networking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5029—Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1016—IP multimedia subsystem [IMS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
-
- 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/04—Registration at HLR or HSS [Home Subscriber Server]
-
- 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
- H04W8/10—Mobility data transfer between location register and external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/08—Upper layer protocols
- H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
Definitions
- the present invention relates to telecommunications systems and methods for providing internet protocol multi-media services to mobile user equipment.
- the present invention also relates to a computer program for providing internet protocol multi-media services to mobile user equipment.
- Mobile communications systems such as those provide by mobile radio networks allow a mobile communications device such as, for example, a mobile telephone or portal personal computer (herein after referred to generally as a mobile user equipment) to move within a coverage area of the mobile radio network whilst still supporting a communications service to the mobile user equipment.
- a mobile communications device such as, for example, a mobile telephone or portal personal computer (herein after referred to generally as a mobile user equipment)
- the mobile user equipment can roam between different mobile access networks.
- the mobile user equipment may roam from a home mobile access network, via which the mobile user equipment usually communicates to a visited mobile access network.
- the user of the mobile user equipment subscribes to an operator of its home mobile access network.
- Communications sessions can be controlled by control functions which are associated with the mobile user equipment's home mobile access network or with a visited mobile access network.
- the controlling function in the home mobile access network provides the home mobile access network with the capability to monitor and control media sessions in a visited network, and in particular to apply charges to a user, and to allocate and control bandwidth and Quality of Service.
- the controlling function typically does not allow the visited mobile access network to monitor and control the media sessions in this way.
- a telecommunications system for providing internet protocol rnulti-media services in accordance with a service level agreement specifying conditions for a communications session in which internet protocol data is communicated to and from a mobile user equipment.
- the system comprises an internet protocol multi-media sub-system operable to provide the internet protocol multi-media communications session to the mobile user equipment, a mobile access network for providing a mobile communications facility to the mobile user equipment for the internet protocol multimedia communications session, and a signal transfer point.
- the signal transfer point is operable to receive signalling data messages communicated to and from the mobile access network for providing the internet protocol multi-media communications session, to receive subscriber data of the mobile user equipment from the home location register of the mobile user equipment as part of a communications session establishment procedure, the subscriber data including data representing the service, level agreement for providing the multi-media communications session, and to set triggering conditions, based on the subscriber data, in the mobile access network in accordance with the service level agreement.
- the system also comprises a local access control function operable in response to reporting messages received from the mobile access network generated by the mobile access network when the triggering conditions are satisfied to determine whether the mobile user equipment is communicating in accordance with the service level agreement, and to control the multimedia communications session in accordance with the service level agreement.
- the triggering conditions may be set by adapting the subscriber data, which may be communicated to the mobile access network from the home location register during a communications session establishment procedure.
- the mobile network may include a service support node and a gateway support node, and the triggering conditions may be set either in the service support node or, assuming it has the required functionality, the gateway support node. In either case, little or no change to the service support node or gateway support node may be required, because these nodes traditionally perform the monitoring and policy enforcement functions in response to home network policy decisions.
- One, or more than one triggering condition may be set in the mobile access network, so that control of the session by the local access control function can be enabled for a plurality of parameters.
- the mobile access network is the mobile user equipment's home network, in which case the signal transfer point and the local access function are part of the home mobile access network of the user equipment. Inserting triggering information into subscriber data from the home location register may in some cases be preferable to the conventional approach of storing the triggering information in the home location register (HLR). For instance, if there are a large number of subscribers with triggering information stored in the HLR, but it is necessary to migrate subscribers to start running a new version of an application, say on a different local access control function, then providing for alteration of the routing will allow for a smooth change over of services. It also becomes possible to monitor a total amount of traffic communicated using a mobile access network.
- HLR home location register
- a total amount of data communicated on that GPRS network can be determined. This could be done for all subscribers and could be done regardless of whether other Intelligent Network (IN) services were running.
- Another example application of the present technique is to amend the triggering information for all users, so that all users are awarded free data calls at predetermined times, for instance as a free promotion to offer free late night data when the network is quiet.
- the user equipment may be currently attached to a visited network, in which case the mobile access network, the signal transfer point and the local access control function are part of the visited network to which the user equipment is currently roaming from its home network.
- the home location register will in this case be in the home network of the user equipment.
- a user is roaming to a visited network, it is the user's home network which provides session control functions.
- it is the visited mobile access network which provides session control, regardless of whether the user's home mobile access network has determined that it wishes to trigger service control.
- the subscriber data may or may not include triggering information prior to being received by the signal transfer point in a visited mobile access network. If triggering information was not previously present, it is inserted by the signal transfer point to set triggering conditions in the mobile access network to enable message reporting to a local access control function within the visited network. Alternatively, if triggering information already existed in the subscriber data received by the signal transfer point, the triggering information will be modified to set triggering conditions in the mobile access network to enable message reporting to a local access control function within the visited network in addition to message reporting to a home access control function within the home network of the user equipment.
- the STP may be a function integrated into another physical network node, such as an MSC, or a physical entity in its own right.
- IP (Internet Protocol) Multimedia Subsystems are an example of a telecommunications system, which can be used to control multi-media sessions between parties for applications such as voice, video, messaging, presence and games.
- the 3GPP (3 rd Generation Partnership Project) has defined an DvIS, which is described in detail in 3GPP specifications such as 24.228 - 3GPP.
- DvIS 3 rd Generation Partnership Project
- media sessions can be controlled by CAMEL (Customized Applications for Mobile network Enhanced Logic) which is a mobile network architecture providing IN (Intelligent Network) services.
- CAMEL Customerized Applications for Mobile network Enhanced Logic
- the CAMEL architecture provides remote control functions and switching functions and supports roaming into a visited mobile access network.
- a controlling function referred to as a service control point (SCP) in a home mobile access network interacts with a switching function, referred to as a signal transfer point (STP), in a visited network.
- SCP service control point
- STP signal transfer point
- the triggering information may be CAMEL subscription information comprising a Global Title and a Service Key.
- the Global Title and the Service Key can be adapted by the signal transfer point to route reporting messages from the mobile access network to the local access control function.
- the triggering conditions may include the expiry of a predetermined session duration or the transfer of a predetermined volume of data. It is also possible to set triggering conditions to monitor the quality of service experienced by the user equipment, and to apply charges to the user equipment in respect of multi-media services used.
- Embodiments of the invention are arranged to be separate to the SIP session control that can be carried out in a CAMEL Service Control Function (SCF) as defined in 23.228 - 3GPP and may apply to the control of data flow associated with IMS across various access solutions defined by 3GPP, such as UMTS (Universal Mobile Telecommunications System) and GPRS (General Packet Radio Service).
- SCF CAMEL Service Control Function
- Figure 1 is a schematic illustration of a network architecture providing IMS services
- Figure 2 is a schematic illustration of a CAMEL attachment and data control procedure for a subscriber in their home network according to a first embodiment of the invention
- Figure 3 is a schematic illustration of a first CAMEL attachment and data control procedure for a subscriber roaming from their home network to a visited network according to a second embodiment of the invention
- Figure 4 is a schematic illustration of Global Title and Service Key adaptation for the attachment and data control procedure of Figure 3;
- Figure 5 is a schematic illustration of a second CAMEL attachment and data control procedure for a subscriber roaming from their home network to a visited network according to a third embodiment of the invention
- Figure 6 is a schematic illustration of the steps involved in setting and triggering CAMEL conditions in the procedure of Figures 3 and 4;
- Figure 7 is a schematic illustration of illustrates an example message flow between the SGSN, the STP, a home SCP and a visited SCP for the second embodiment of the invention
- Figure 8 is a schematic illustration of a bandwidth monitoring and allocation procedure according to an embodiment of the invention. Description of the Example Embodiments
- Example home and visited mobile radio networks which conform to the GPRS/UMTS standard are illustrated in Figure 1 and provide mobile radio communication of data via a radio access interface in accordance with the Universal Terrestrial Radio Access Network (UTRAN).
- UTRAN Universal Terrestrial Radio Access Network
- the terminology and architecture used in Figure 1 corresponds to that used for the UMTS and that proposed for 3 G as administered by the 3GPP.
- a home mobile radio network includes a Gateway Support Node (GGSN) 100 which provides an interface between an external network 120 and the home mobile radio network for communicating data to and from external networks for mobile user equipment which are attached to the GPRS/UMTS network.
- the home mobile radio network shown in Figure 1 includes a plurality of base transceiver stations which are referred to in the UMTS standard as Node Bs.
- the Node Bs 112, 114 are connected by a Radio Network Controller 110 (RNC) to a Serving GPRS Support Node (SGSN) 106 which is connected to the GGSN 100.
- RNC Radio Network Controller 110
- SGSN Serving GPRS Support Node
- mobile user equipment 116 communicates radio signals in accordance witibi the UTRAN standard within a radio coverage area provided by the Node Bs.
- a similar network architecture which exists for 2G and 2.5G networks may be provided, in which a Base Transceiver Stations (BTS) will replace the role of a Node B and a Base Station Controller (BSC) will replace the role of an RNC.
- BTS Base Transceiver Stations
- BSC Base Station Controller
- the GGSN 100 acts as the gateway between the external network 120 and the mobile network, which supports GPRS.
- the GGSN 100 routes incoming IP data packets to an SGSN that is serving a particular mobile User Equipment (UE) receiving data via a radio access facility provided by the mobile packet radio network.
- the radio access facility may be provided in accordance with the Universal Terrestrial Radio Access Network (UTRAN) system which is specified in accordance with the 3GPP standard.
- the SGSN 100 is connected to the GGSN 106 via a Gn interface if the SGSN is within the same Public Land Mobile Network (PLMN), and connected via the Gp interface to GGSNs belonging to other PLMNs.
- PLMN Public Land Mobile Network
- An SGSN provides mobility management of UEs, which are moving within an area supported by the mobile radio network. Specifically, the SGSN is responsible for the delivery of data packets from and to the mobile terminal 116 and other mobile terminals within its service area. Its tasks include packet routing and transfer, mobility management, logical link management, and authentication and charging.
- the SGSN includes a location register which stores location information and user profiles of all users registered with this SGSN. To this end, the SGSN 106 is provided with access to a Home Location Register (HLR) 130 from which this user information can be extracted.
- the SGSN 106 is arranged to route data packets to Radio Network Controllers (RNC) 112, 114 for communication via the UTRAN radio access facility to mobile user UE 116.
- RNC Radio Network Controllers
- the UTRAN radio access facility is provided using Node B apparatus 112, 114, which effectively form base transceiver stations providing radio coverage for the area served by the mobile telecommunications network.
- Figure 1 further illustrates a visited mobile network VPLMN into which the user equipment 116 may roam.
- the visited mobile network has a similar architecture to the home mobile network, and as such includes a GGSN 150 which acts as the gateway between the external network 120 and the visited mobile network, an SGSN 156, an RNC 160 and a Node B apparatus 162.
- the user equipment 116 roaming from the home network to the visited network is illustrated as a user equipment 116'.
- the user equipment 116' is thus currently affiliated to the visited network at a node B 162.
- Profile and other information regarding the user equipment 116' continues to be stored at the HLR 130 in the home network.
- the home mobile network can provide the user equipment 116 with access to IMS services using an IMS 170.
- the IMS includes a Session Initiation Protocol (SlP) server (S-CSCF) 172, a Home Subscriber Server (HSS) 174, a CAMEL server 176 and an IMS application server 178.
- the IMS can be used to provide IP multimedia services to the user equipment 116 using the SIP which can be used to register and control IMS sessions.
- the SIP server 172 is the serving CSCF server and performs the functions of controlling sessions, acting as registrar and triggering and executing services, in the present case IMS services.
- the S-CSCF will access the user's profile from the HSS 174 to determine which services are available to the user equipment and to configure a session, and controls the application server 178 using SIP commands.
- the CAMEL server 176 provides a CAMEL state machine which is defined by conditions (states) and messages resulting from those conditions. CAMEL messages to the CAMEL server update the state machine, and CAMEL messages from the CAMEL server specify commands to be carried out by the mobile network. For instance, the CAMEL server is able to control the allocation of data volume, call duration and quality of service available to the user equipment 116. Specifically, the CAMEL server will be informed of session initiation, data usage, quality of service and session termination, and can allocate blocks of data and terminate sessions in response to these incoming reports.
- the visited mobile network is able to provide the user equipment 116' with access to IMS services using the IMS 170, through the GGSN 150.
- FIG. 2 schematically illustrates an attachment and data control procedure for a subscriber in its home mobile network.
- the subscriber is represented by a user equipment 210 attaching itself to the home mobile network via an SGSN 220.
- the network elements of the home mobile network shown in Figure 2 include a GGSN 230 for providing a gateway to an external network, a Signalling Transfer Point (STP) 240 for routing data packets between network elements, a Home Location Register (HLR) 250 storing subscriber data relating to the user equipment 210, and a Service Control Point (SCP) 260 which is an Intelligent Network (IN) entity which controls the duration, data volume and quality of service available to the user equipment 210.
- STP Signalling Transfer Point
- HLR Home Location Register
- SCP Service Control Point
- I Intelligent Network
- the user equipment 210 When the user equipment 210 attaches itself to the mobile network via the SGSN 220, it communicates the International Mobile Subscriber Identity (IMSI) associated with the user equipment 210 to the SGSN 220.
- the IMSI includes a Mobile Country Code (MCC), a Mobile Network Code (MNC) and a Mobile Station Identification Number (MSIN).
- MCC Mobile Country Code
- MNC Mobile Network Code
- MSIN Mobile Station Identification Number
- the HLR on receipt of the location update message, registers the location update, and communicates the users subscriber data to the SGSN 220 via the STP 240.
- the subscriber data corresponding to the user equipment does not include CAMEL Subscription Information (CSI), and so CAMEL services would not usually be available to the user equipment 220.
- the STP 240 upon receiving the subscriber data without CSI, modifies the subscriber data to include CAMEL triggers before passing it on to the SGSN 220.
- the CAMEL triggers instruct the SGSN 220 and STP 240 to perform special handling for this user equipment 210.
- all data the user sends via the GGSN 230 is then controlled by the SCP 260.
- the SCP 260 may, in doing so, examine Access Point Names (APN's) to separate out traffic flow by routing destination.
- APN's Access Point Names
- FIG. 3 schematically illustrates an attachment and data control procedure for a subscriber roaming from its home mobile network to a visited mobile network.
- the subscriber is represented by a user equipment 310 attaching itself to the visited mobile network via an SGSN 320.
- the network elements of the visited mobile network shown in Figure 3 also include a Signalling Transfer Point (STP) 340 for routing data packets between network elements and a visited Service Control Point (SCP) 360 for controlling the duration, data volume and quality of service available to the user equipment 310.
- STP Signalling Transfer Point
- SCP visited Service Control Point
- the home network of the user equipment 310 includes a Home Location Register (HLR) 350 storing subscriber data relating to the user equipment 310, and a home Service Control Point (SCP) 370 which, in combination with the visited SCP 360, controls the duration, data volume and quality of service available to the user equipment 310.
- the home network also includes a GGSN 330 for providing a gateway to an external network.
- IMSI International Mobile Subscriber Identity
- the HLR 350 on receipt of the location update message, registers the location update, and communicates the user's subscriber data to the SGSN 320 via the STP 340.
- the subscriber data corresponding to the user equipment includes CAMEL Subscription Information (CSI) which enables control of the user equipment 310 by the home SCP 370.
- the STP 340 upon receiving the subscriber data in which the CSI is embedded, modifies the CAMEL Subscription Information before passing it on to the SGSN 320.
- the CAMEL Subscription Information includes a Global Title (GT) and a Service Key.
- the Global Title indicates the identity of the Camel Service Environment (CSE) to be used in respect of CAMEL functions.
- CSE Camel Service Environment
- the Service Key specifies the service logic, or application, to be used by the SCP.
- the STP 340 modifies the Global Title, and may also modify the Service Key. The modification of the Global Title and Service Key for the Figure 3 situation will now be described with reference to Figure 4.
- FIG 4 illustrates the flow of subscriber data and CAMEL messages between the network elements of Figure 3, in which like elements are provided with like reference numerals.
- the FfLR 350 communicates subscriber data including CSI to the SGSN 320 via the STP 340.
- the CSI within the subscriber data includes a Global Title of 33777123000 and a Service Key of 2000.
- the first two digits of the Global Title represent the country code of the network in which the HLR 350 and the Home SCP 370 are located. In this case the country code is 33.
- the STP 340 upon receipt of the CSI, stores the initial Global Title and Service Key and then adapts the Global Title to 447980011001 and the Service Key to 5000 before passing the CSI on to the SGSN 320.
- a different country code 44 is used, indicating that the visited network in the present example is in a different country than the home network of the user. Then, when a CAMEL message is generated in response to a triggering condition being met within the SGSN 320, it will use the adapted Global Title of 447980011001 and the adapted Service Key of 5000 in communicating the CAMEL message to the STP 340.
- the STP 340 upon receipt of CAMEL messages from the SGSN 320, is able to communicate the CAMEL messages on to either or both of the visited SCP 360 and the home SCP 370.
- the STP 340 correlates the received CAMEL message with the stored Global Title and Service Key and sends a CAMEL message using the original Global Title and Service Key identified by the HLR 350.
- the STP 340 again adapts the Global Title and the Service Key, this time to 447980011002 and 4000 respectively, in order to route the CAMEL message to the visited SCP 360. It will be recognised that the STP 340 can also send CAMEL messages to both the visited SCP 370 and the home SCP 360 in response to the same CAMEL message from the SGSN 320.
- FIG. 5 schematically illustrates an attachment and data control procedure for a subscriber roaming from its home mobile network to a visited mobile network.
- the subscriber is represented by a user equipment 510 attaching itself to the visited mobile network via an SGSN 520.
- the network elements of the visited mobile network shown in Figure 5 also include a Signalling Transfer Point (STP) 540 for routing data packets between network elements and a visited Service Control Point (SCP) 560 for controlling the duration, data volume and quality of service available to the user equipment 510.
- STP Signalling Transfer Point
- SCP visited Service Control Point
- the home network of the user equipment 510 includes a Home Location Register (HLR) 550 storing subscriber data relating to the user equipment 510 and a GGSN 530 for providing a gateway to an external network.
- HLR Home Location Register
- the user equipment 510 When the user equipment 510 attaches itself to the visited mobile network via the SGSN 520, it communicates the International Mobile Subscriber Identity (IMSI) associated with the user equipment 510 to the SGSN 520. As with the arrangement of Figures 2 and 3, this enables the SGSN 520 to identify the HLR 550 associated with the user equipment 520 and to route a location update message to that HLR 550 via the STP 540.
- IMSI International Mobile Subscriber Identity
- the HLR 550 on receipt of the location update message, registers the location update, and communicates the users subscriber data to the SGSN 520 via the STP 540.
- the subscriber data corresponding to the user equipment does not include any CAMEL Subscription Liformation (CSI).
- the STP 540 upon receiving the subscriber data in which the CSI is embedded, inserts CAMEL Subscription Information into the subscriber data before passing it on to the SGSN 520.
- This CAMEL Subscription Information operates in a similar way to the CAMEL Subscription Information described in Figures 2 and 3. hi the example embodiment of Figure 5, no CAMEL messages are communicated to a home network SCP, because no CAMEL services have been specified by the HLR of the home network for the user equipment 510.
- FIG. 6 is a flow diagram schematically illustrating the steps involved in setting up and processing CAMEL triggers in a mobile network such as that shown in the preceding Figures.
- the process commences at a step Sl, where a user equipment attaches to a network at an SGSN.
- the SGSN determines the identity and HLR of the user equipment from the IMSI of the user equipment and sends a location update message to the HLR via an STP.
- the HLR registers the updated location of the user equipment and sends the subscriber data relating to the user equipment back to the SGSN, again via the STP.
- the STP intercepts the subscriber data determines whether CAMEL Subscription Information is present. If no CAMEL Subscription Information is found, the STP inserts new CAMEL Subscription information to set CAMEL in the SGSN. If existing CAMEL Subscription Information is found, the STP modifies the CAMEL Subscription Information to adapt the CAMEL triggers in the SGSN.
- a PDP context uses the SGSN and sets up a PDP Context defining a bearer for data packets between the User Equipment and a third party.
- the set-up of the PDP context includes the communication of CAMEL messages from the SGSN to the SCP' s via the STP in order to set up CAMEL state logic for controlling a communications session if appropriate triggers have been set.
- the SGSN monitors subscriber data, such as the bandwidth used, the duration of a call and the Quality of Service (QoS), with respect to the CAMEL triggering conditions set in the SGSN.
- subscriber data such as the bandwidth used, the duration of a call and the Quality of Service (QoS)
- processing returns to the step S6, where monitoring by the SGSN continues. However, if at the step S7 a triggering condition is met, then at a step S8, the SGSN sends a CAMEL message to Ihe STP. Upon receipt of the CAMEL message, the STP, at a step S9 passes the CAMEL message on to the relevant SCP. The SCP, at a step SlO, makes decisions in response to the CAMEL message and based on service policy and subscriber data.
- FIG. 7 illustrates a message flow between the SGSN 5 the STP, a home SCP and a visited SCP.
- This example message flow relates to a situation where the VPLMN is monitoring the volume of data which is being sent, however, other services could be provided, such as a service to count all PDP context activations which take place within the VPLMN.
- a CAMEL trigger occurs and an INITDP CAMEL message is sent by the SGSN to the STP at a step Cl.
- the CAMEL message is passed on from the STP to both the visited SCP at a step C2 and the home SCP at a step C3 to configure CAMEL services within the PDP context.
- Steps C2 and C3 may be carried out using Global Title adaptation as described above.
- the home SCP sends an Apply Charge message to the STP which enables the STP to set CAMEL triggers for when the user equipment reaches predetermined data volume or call duration limits in accordance with a policy governed by the home SCP.
- the home SCP sets a volume Vhome and a duration Thome-
- the visited SCP sends an Apply Charge message to the STP which enables the STP to set CAMEL triggers for when the user equipment reaches predetermined data volume or call duration limits in accordance with a policy governed by the visited SCP.
- the visited SCP sets a volume Vvisited and a duration T V j S ited.
- the STP processes the two received Apply Charge messages and sets CAMEL triggering conditions in the SGSN in accordance with the smallest data volume V sm aiiest 5 that is the smallest of Vhome and Vvisited, and the shortest call duration T sma iiest, that is the shortest of Thome and Tested-
- V sm aiiest 5 that is the smallest of Vhome and Vvisited
- T sma iiest that is the shortest of Thome and Tested-
- the CAMEL triggering conditions will have been met and the SGSN will send an Apply Charge Report to the STP at a step C7. Accordingly, it will be understood that tihe values set in the Apply Charge message are effectively constraints dictating the duration and volume of data transfer permitted before the SCP wishes to be consulted. It will be understood that the triggering of the Apply Charge message does not prevent further data transfer from taking place between the user equipment and a third party.
- the STP on receipt of the Apply Charge Report message, will determine which SCP the activated trigger relates to, and will communicate the Apply Charge Report message to that SCP.
- the activated trigger relates to the home SCP, and so the Apply Charge Report is sent there at a step C8.
- the home SCP on receipt of the Apply Charge Report, can either allocate additional bandwidth and/or duration, or can terminate the session.
- the home SCP sends another Apply Charge message to the STP at a step C9, which enables the STP to set further CAMEL triggering conditions for a new predetermined data volume or call duration at a step ClO.
- Steps C7 to ClO can be continued, with CAMEL messages being sent to both the home and visited SCP' s, many times, until either the user equipment, or one of the SCP' s elects to terminate the session.
- the home SCP elects, at a step C27, to terminate the session with an Entity Released message which is communicated to the STP.
- the STP passes the Entity Released message on to the SGSN at a step C28.
- the STP also communicates, at a step C29, the Entity Released message, and any outstanding Apply Charge message, to the visited SCP.
- FIG 8. An example bandwidth allocation and monitoring procedure using the messaging of Figure 7 is schematically illustrated in Figure 8.
- the visited SCP allocates bandwidth V V i S ite d in blocks of 300kbits at a time and the home SCP allocates bandwidth Vh ome in blocks of 500kbits at a time.
- the STP when setting the first bandwidth trigger condition in the SGSN, will compare V V i S i t ed and Vhome against the current bandwidth usage to determine Vsm a iie s t- The current bandwidth usage at the start of the call will be Okbits. It can be seen from Figure 8 that the first value of V sma iie s t will be 300kbits, and that this will therefore be the first trigger condition Al.
- the trigger condition When the bandwidth used reaches 300kbits, the trigger condition will be met and the SGSN will report this back to the STP, which will in turn pass on the report to the SCP which set that particular trigger condition, in this case the visited SCP. Assuming the session continues, the STP will determine the next value of Vsmaiiest, again by comparing Visited and Vhome against the current bandwidth usage of 300kbits. This will result in the trigger condition A2 being set, at a bandwidth of 500kbits.
- the second trigger condition A2 When the bandwidth used reaches 500kbits, the second trigger condition A2 will be met and the SGSN will report this back to the STP, which again will in turn pass on the report to the SCP that set the trigger condition A2, which in this case was the home SCP. Following this, the next trigger condition will be determined.
- the third and fourth trigger conditions A3 and A4 respectively are set by the visited SCP, that the fifth trigger condition A5 is set by the home SCP and that the sixth trigger condition A6 is set by the visited SCP.
- the seventh trigger condition A7 is set by both the home and visited SCPs. Accordingly, when this trigger condition is met, the resulting report will be sent to both SCPs, which will each have the opportunity to allocate additional bandwidth or terminate the session.
- CAMEL triggering by the SGSN it is also possible, if the GGSN is in the HPLMN, to use CAMEL triggering at the GGSN, because there will be sufficient information available at the GGSN to enable triggering to be performed.
- the SCP will be unaware that a trigger has come from the GGSN rather than the SGSN, and so no changes to the message flow are required.
- GGSN forwards the data packets sent to and from the user equipment.
- the role of the policy enforcement module is simply to monitor bandwidth usage and routing in real time and report the data volume and third party locations used.
- Embodiments of the present invention can also handle cases where the visited network VPLMN and the home network HPLMN service request different default call handling.
- the Default GPRS Handling indicates whether the GPRS session or PDP context shall be released or continued as requested in case of error in the gprsSSF to gsmSCF dialogue.'
- the STP can inform of the SGSN to use the release method.
- An STP which uses the present technique in the visited network VPLMN can also allow for cases where one of the local access control functions SCP is set to continue whilst the other is set to request. For example, if the home network HPLMN local access control function is set to continue, whereas the visited network VPLMN local access control function service is set to release, then:
- the STP would set the SGSN to a release mode
- the GGSN may be in the HPLMN while the SGSN is in the VPLMN, the SGSN and the GGSN may both be in the VPLMN, or tihe SGSN and the GGSN may both be in the HPLMN.
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB0505210A GB2424493A (en) | 2005-03-14 | 2005-03-14 | Telecommunications system and method |
PCT/GB2006/000863 WO2006134313A2 (en) | 2005-03-14 | 2006-03-13 | Telecommunications system and method |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1867136A2 true EP1867136A2 (en) | 2007-12-19 |
Family
ID=34509036
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP06794538A Withdrawn EP1867136A2 (en) | 2005-03-14 | 2006-03-13 | Telecommunications system and method |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP1867136A2 (en) |
GB (1) | GB2424493A (en) |
WO (1) | WO2006134313A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11765052B1 (en) | 2022-03-11 | 2023-09-19 | T-Mobile Usa, Inc. | User equipment hosting for customizable 5G services |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8238905B2 (en) | 2003-08-05 | 2012-08-07 | Roamware, Inc. | Predictive intelligence |
US8583109B2 (en) | 2005-05-09 | 2013-11-12 | Roamware, Inc. | Method and system for exchanging NRTRDE files between a visited network and a home network in real time |
ES2354722T3 (en) * | 2005-05-09 | 2011-03-17 | Roamware, Inc. | DYNAMIC GENERATION OF CSI INFORMATION FOR INTRANT ITINERANT SUBSCRIBERS. |
WO2008154942A1 (en) * | 2007-06-20 | 2008-12-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, telecommunication system and network entity for enabling service provisioning to an inbound roaming user in a visited public land mobile network (vplmn) |
CN101572864B (en) * | 2008-05-04 | 2011-09-21 | 电信科学技术研究院 | Method, system and device for notifying user information |
US11882091B1 (en) | 2022-11-10 | 2024-01-23 | T-Mobile Usa, Inc. | Allocation of internet protocol addresses based on a location of a visited network |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6856676B1 (en) * | 1998-10-15 | 2005-02-15 | Alcatel | System and method of controlling and managing voice and data services in a telecommunications network |
EP1156692B1 (en) * | 2000-05-19 | 2008-03-19 | Lucent Technologies Inc. | Internet protocol-based mobile telecommunications networks |
US6904035B2 (en) * | 2000-11-29 | 2005-06-07 | Nokia Corporation | Mobile system, terminal and interface, as well as methods for providing backward compatibility to first and second generation mobile systems |
US6871070B2 (en) * | 2001-07-31 | 2005-03-22 | Lucent Technologies Inc. | Communication system for providing roaming between an internet protocol multimedia system and a circuit-switched domain |
US6954654B2 (en) * | 2001-07-31 | 2005-10-11 | Lucent Technologies Inc. | Provision of services in a communication system including an interworking mobile switching center |
US20030214958A1 (en) * | 2002-04-12 | 2003-11-20 | Lila Madour | Linking of bearer and control for a multimedia session |
WO2004054293A1 (en) * | 2002-12-09 | 2004-06-24 | Me-Omnicom B.V. | Transfer of ussd messages to/from ussd external node |
-
2005
- 2005-03-14 GB GB0505210A patent/GB2424493A/en not_active Withdrawn
-
2006
- 2006-03-13 EP EP06794538A patent/EP1867136A2/en not_active Withdrawn
- 2006-03-13 WO PCT/GB2006/000863 patent/WO2006134313A2/en not_active Application Discontinuation
Non-Patent Citations (1)
Title |
---|
See references of WO2006134313A2 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11765052B1 (en) | 2022-03-11 | 2023-09-19 | T-Mobile Usa, Inc. | User equipment hosting for customizable 5G services |
Also Published As
Publication number | Publication date |
---|---|
GB0505210D0 (en) | 2005-04-20 |
WO2006134313A3 (en) | 2007-02-08 |
GB2424493A (en) | 2006-09-27 |
WO2006134313A2 (en) | 2006-12-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1719380B1 (en) | Allowing barring a call after activation | |
EP1685682B1 (en) | Controlling network resources after determination of a flow termination | |
EP1978706B1 (en) | A method and system for implementing the data routing of the roaming user | |
JP4354643B2 (en) | Interoperability between intelligent network and packet data network | |
EP1829413B1 (en) | A default subscription profile for a roaming terminal device in a packet data based mobile communication network | |
US7483698B2 (en) | Providing roaming status information for service control in a packet data based communication network | |
US7525938B2 (en) | Session control in a communication system | |
US20020128017A1 (en) | Method and system for limiting quality of service of data transmission | |
CN101978716A (en) | Method for optimizing a user equipment pdn (packet data network) connection | |
US10342054B2 (en) | IP address assignment for a UE in 3GPP | |
CA2443690A1 (en) | Technique for providing announcements in mobile-originated calls | |
US20170150536A1 (en) | Communication of Information Between Devices In Communication Networks | |
WO2006134313A2 (en) | Telecommunications system and method | |
EP3078226B1 (en) | Method and apparatus for requesting an initial attachment of a ue to ps mobile communication network | |
US7327724B2 (en) | Method, network device, and terminal device for controlling context activation | |
CN100484290C (en) | Method for realizing PDP address distribution in service cut-in | |
CN101990188B (en) | Method and system for selecting enhanced mobile switching center server | |
US20050099990A1 (en) | Logical connection modification | |
FI115688B (en) | Mediation of multimedia traffic a telecommunications system | |
WO2005015939A1 (en) | Selective handling of user equipment | |
MXPA06008884A (en) | Method and communication system to allow barring a call of a roaming user after pdp context activation | |
MXPA00011313A (en) | Intelligent network and packet data network interoperability |
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 |
|
17P | Request for examination filed |
Effective date: 20071012 |
|
AK | Designated contracting states |
Kind code of ref document: A2 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 |
|
DAX | Request for extension of the european patent (deleted) | ||
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: FRANCE TELECOM |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: ORANGE |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 29/08 20060101AFI20160121BHEP Ipc: H04W 80/10 20090101ALI20160121BHEP Ipc: H04L 29/06 20060101ALI20160121BHEP |
|
INTG | Intention to grant announced |
Effective date: 20160204 |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: ALLAN, ROBERT, MARK |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20160615 |