This Application is a Section 371 National Stage Application of International Application No. PCT/FR2018/052811, filed Nov. 13, 2018, which is incorporated by reference in its entirety and published as WO 2019/106253 A1 on Jun. 6, 2019, not in English.
The invention falls within the scope of the telecommunications networks and more specifically the telecommunications networks offering Intelligent Network services.
It is recalled that the Intelligent Network services (or IN services) are customized services of an operator that apply to calls whose signaling is standardized.
These Intelligent Network (IN) services are generally distinguished from MMTel services, a standardized 3GPP solution for providing voice, video telephone services and the like on the 2G/3G/4G/5G cellular networks.
The invention is more particularly concerned with the conditions for triggering the Terminating services of an IN upon detection of an incoming call.
It is recalled that a Terminating service (called service) of an IN designates in particular the interception of all or part of the signaling messages of a session received by the input switch (GMSC for Gateway Mobile Switch Center) or application server (TAS for Telephony Application Server) of the nominal network of the called user to transmit said session partially or globally after protocol adaptation to an IN service processing entity which is always located in the nominal network of the called user and which is responsible for applying a specific service logic before giving control to the input switch or application server on this session.
It is recalled that an incoming ISUP (ISDN Signaling User Part) or (Bearer Independent Call Control) call is presented (step (1)), when it arrives in the nominal network, to a GMSC (Gateway Mobile Switch Center) entity. This message includes the MSISDN number of the calling terminal and the MSISDN number of the called terminal.
During a step (2), the GMSC entity sends a MAP SRI (Send Routing Information) request to an SDM (Service Data Management) entity to find out where the called terminal is located. It is recalled that the SDM integrates the HLR (Home Location Register) and the HSS server (Home Subscriber Server).
During a step (3), the SDM checks that there is indeed a user service profile registered for this called MSISDN number. If this is the case, the SDM returns information to the GMSC so that it routes the call towards the SCC-AS (Service Call Continuity Application Server) function of the TAS server. This information includes, in particular, the address of the SCC-AS function, the T-CSI (Terminating Camel Subscription Information) intelligent network mark, a service KEY, the trigger point DP12 and the default handling CONTINUE.
It is recalled that an IN service mark defines the set of the parameters for triggering this IN, including (i) the address of the gsm-SCF (Global System Mobile-Service Control Function) platform for processing the service logic and (ii) the Service Key identifying the service logic which must be invoked in this platform and (iii) TDP (Trigger Detection Point) list identifying the detection point of the automatic calling machine BCSM (Basic Call State Machine) on which the triggering of the IN service must occur and (iiii) the Default Call Handling which indicates whether the call should be continued or released in the event of an error during a dialogue between the gsm-SSF (Global System Mobile-Service Switching Function) and the gsm-SCF (Global System Mobile-Service Control Function).
The GMSC triggers via its gsm-SSF function the routing of the call towards the SCC-AS function of the TAS server which acts as a gsm-SCF (step (4) and the TAS server checks whether the MSISDN number of the called party is registered at the SIP.
In the scenario of
In step (6), the GMSC having received the profile of the user in step (3) determines that the called terminal is in prepaid mode because it is currently located in a visited country and therefore that the call termination between the nominal country and the visited country should be charged thereto. It consults, via its gsm-SSF function, the intelligent network platform PREPAID to check the balance of the account of the user of the called terminal. The intelligent network platform PREPAID replies (step 7), depending on the status of the account, with a message of the type:
In step (10), the V-MSC issues to the SDM the routable number of the called terminal. It is recalled that this internationally routable number is a number temporarily issued by the V-MSC, among a set of numbers managed by this V-MSC.
In step (11), the SDM provides this routable number to the GMSC which routes (step (12)) the call in ISUP/BICC up to the V-MSC on which the called terminal is attached. The V-MSC finds the terminal in the cells it manages by a paging mechanism and presents the call to the called terminal.
The call is then supervised by the IN platform PREPAID and if the user's communication credit is exhausted, the GMSC then triggers the disconnection of the called terminal and sends a call interruption message (of RELEASE type) to the calling terminal.
In this scenario, if the called terminal is registered in VoWiFi in parallel with its 2G/3G connection, therefore in SIP, this called terminal is registered in the TAS server. Consequently, when the SCC-AS function of the TAS server is interrogated by the GMSC in step (4), the TAS server replies in step (5) to the GMSC in CAP protocol “CONNECT” by using a specific routing identifier such as a prefix before the called MSISDN number. The GMSC then routes based on this prefix (step (6)) the call towards the I-CSCF (Interrogating Call State Control Function) in SIP protocol according to the prefix suppression mechanism known to those skilled in the art. The GMSC, via its MGCG function (Media Gateway Control Function) sends for this purpose to the I-CSCF entity a SIP message INVITE including the MSISDN number of the called terminal.
In steps (7) and (8), the I-CSCF entity interrogates the HSS part of the SDM to obtain the address of the S-CSCF (Serving-Call State Control Function) entity on which the called terminal is registered, via its MSISDN number.
In step (9), the I-CSCF routes the call towards this S-CSCF. It is recalled that the S-CSCF has previously downloaded from the HSS the IMS profile of the called terminal during the Initial SIP registration phase of this terminal.
The S-CSCF then triggers (step (10)) the sending of a message INVITE to the TAS server.
In step (11), the TAS server asks the SDM whether the user of the called terminal has Terminating Intelligent Network (IN) marks. In step (12), the SDM replies that the user does actually have IN marks PREPAID.
In step (13), the IM-SSF function (IP Multimedia-Service Switching Function) of the TAS server triggers the Terminating IN service. The intelligent network platform confirms (step (14)), based on the MSISDN number, that the user's prepaid account is sufficiently credited for the call to be authorized.
In step (15), the T-ADS (Terminating Domain Access Selection) function of the TAS server interrogates the SDM to determine the routing domain of the incoming call either towards the PS packet mode VoLTE or VoWiFi or towards the 2G/3G circuit mode.
The called terminal being registered in VoWiFi, the SDM indicates (step (16)) to route the call in PS (Packet Switch) mode, via the IMS core.
The TAS server sends (step (17)), the message INVITE to the S-CSCF; the S-CSCF routes the call towards the P-CSCF (Proxy Call State Control Function) and the P-CSCF routes the call towards the called terminal. The call is then supervised by the IN platform PREPAID and if the user's communication credit is exhausted, the TAS then triggers the disconnection of the called terminal and sends a call interruption message (BYE type) to the MGCF of the GMSC which in turn interrupts the call with the caller to the calling terminal by sending an ISUP/BICC message (of Release type).
With reference to
In the case of an incoming call intended for this terminal, in step (15), the T-ADS function of the TAS server determines that the Terminating domain of the called terminal is the circuit domain and that the call must be routed in circuit mode.
Under these conditions, the TAS server obtains the international routing address of the called terminal by interrogating the SDM (steps (17) to (20)) then routes (step (21)) the message INVITE to the S-CSCF. The S-CSCF sends the message INVITE to the MGCF of the V-MSC which performs the SIP translation towards ISUP/BICC and the call is routed from the V-MSC towards the conventionally called terminal.
It appears from the description of
This situation is not satisfactory. The invention therefore relates to a mechanism allowing an operator to set up a differentiated Terminating service offer.
Thus, according to a first aspect, the invention relates to a method for handling an incoming call intended for a called terminal in an IMS-type telecommunications network. This method is implemented by a TAS server and includes:
Correlatively, the invention relates to a TAS server configured to handle an incoming call intended for a called terminal in an IMS network. This server includes:
Thus, in general, the invention proposes to determine the type of access network to which a called terminal is attached before triggering a Terminating IN service logic, and to differentiate the Terminating IN service to be provided to the user of this terminal depending on the type of access network.
The invention consequently proposes to anticipate the T-ADS function in order to activate, deactivate or adapt a Terminating IN service logic.
In a first variant, the step for differentiating the Terminating IN service provided to the user of the called terminal depending on the type of access network consists in triggering or not the Terminating IN service depending on the type of access network of the called terminal.
In a second variant, the step for differentiating the Terminating IN service provided to the user of the called terminal depending on the type of access network includes the systematic triggering of the Terminating IN service by sending to the IN service execution platform the type of access network of the called terminal, the platform being configured to implement a differentiated service logic depending on the type of access network.
In a particular embodiment of the invention, the step of determining whether the called terminal is actually reachable in packet mode and, if so, via which type of access, includes:
In a particular embodiment of the invention, in order to differentiate the Terminating IN service provided to the user of the called terminal:
The invention thus allows an operator to decide in particular to trigger, not to trigger, or to trigger a differentiated Terminating IN service:
The invention can in particular be used not to trigger the supervision of a call by a Terminating IN platform when the called terminal is actually under WiFi coverage.
This embodiment is particularly advantageous in the case of an IN service PREPAID because it allows an operator not to reduce the communication credits of a user in prepaid mode, when the latter receives a call in roaming abroad, while its terminal is in VoWiFi.
The characteristics and advantages of the TAS server according to the invention are identical to the characteristics and advantages of the method for handling an incoming call described above.
Therefore:
According to a third aspect, the invention also relates to a system including:
In a particular embodiment, the different steps of the method for handling an incoming call according to the invention are determined by computer program instructions.
Consequently, the invention also relates to a computer program, on an information medium, this program including instructions adapted for the implementation of the steps of a method for handling an incoming call according to the invention.
This program can use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in a partially compiled form, or in any other desirable form.
The invention also relates to an information medium readable by a computer, and including instructions of a computer program as mentioned above.
The information medium can be any entity or device capable of storing the program. For example, the support may include a storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or also a magnetic recording means, for example a hard disk.
On the other hand, the information medium can be a transmissible medium such as an electrical or optical signal, which can be conveyed via an electrical or optical cable, by radio or by other means. The program according to the invention can in particular be downloaded from an Internet-type network.
Alternatively, the information medium can be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the method in question.
Other characteristics and advantages of the present invention will emerge from the description given below, with reference to the appended drawings which illustrate an exemplary embodiment thereof devoid of any limiting character. In the figures:
The read-only memory 9 of the device of the entity 10 for managing user profiles constitutes a recording medium according to the invention, readable by the processor 7 and on which a computer program PROG is recorded here according to the invention.
The computer program PROG defines functional and software modules here, configured to implement the steps of a method for handling an incoming call. These functional modules are based on and/or control the hardware elements 7-11 and 15 of the entity 10 mentioned above. They comprise in particular here, as illustrated in
In one embodiment of the invention, the unit 2D for differentiating the Terminating IN service is configured to trigger or not said Terminating IN service depending on the type of access network.
In another embodiment of the invention, the unit 2D for differentiating the Terminating IN service is configured to systematically trigger the Terminating IN service by sending to the IN service processing platform the type of access network of the called terminal. In this embodiment, the Terminating IN service processing platform is configured to implement a differentiated service logic depending on the type of access network of the called terminal.
This method can be implemented by the TAS server in
This method includes a step E10 during which the TAS server interrogates the SDM entity to determine whether the service profile of the user associated with said called terminal has Terminating IN service marks. The result of this interrogation is recorded in a variable VRI stored in the memory 15. This variable VRI is initialized to “Y” if the service profile of the user has Terminating IN service marks and to “N” otherwise.
During a step E20, the TAS server interrogates an SDM entity to determine the circuit or packet routing domain to be used to route the call towards said called terminal. The PS/CS result of this interrogation is recorded in a variable VDR stored in the memory 15.
If said routing domain is of the packet type, step E20 is followed by a step E30 during which the TAS server determines whether the called terminal is actually reachable in packet mode, and if so, via which type of access network. The type of access network is recorded in a variable VRA stored in the memory 15.
During a step E35, the TAS server checks whether the service profile of the user has Terminating IN service marks depending on the content of the variable VRI initialized in step E10.
If this is the case, the Terminating IN service is differentiated during a step E40 depending on the type of access network of the called terminal stored in the variable VRA.
Then the call is routed towards the called terminal during a step E50.
In the first variant of the invention, and as illustrated in
In a particular embodiment, and as illustrated in
According to the invention, before triggering the Terminating IN Prepaid service, the TAS server sends (step (13)) a SIP message OPTIONS to the called terminal. If the called terminal replies to this message (typically with a response 200 OK), the TAS server determines:
(i) with certainty that the called terminal is always reachable via a packet-type routing domain (PS for Packet Switch); and
(ii) the type of access network of the called terminal by analysis of the PANI field comprised in the response 200 OK.
In the example of
This embodiment is particularly advantageous because it allows the operator not to reduce the communication credits of a user in prepaid mode when he receives a call in roaming abroad while his terminal is in VoWiFI.
In the embodiment described here, the conventional algorithm for selecting the call termination domain conventionally applies in steps (15) and (16). These steps will confirm that the terminal is reachable via the PS packet domain but the call will not be supervised by the Terminating IN network logic. The conventional algorithm for selecting the call termination domain could equally well be executed before step (13) of determining the reachability of the called terminal via the packet mode. Likewise, the algorithm for selecting the call termination domain might as well not be applied, for example when the called terminal is detected as registered and reachable in VoWiFi.
In the example of implementation of
The TAS server can also decide to trigger the Terminating intelligent network service if it receives, in response to the SIP message OPTIONS sent to the called terminal in step (13), a response 200 OK/486 Busy Here mentioning a SIP PANI field with GERAN (2G) or UTRAN (3G) access representative of the fact that the called terminal is attached to a cellular network.
In this case, the TAS server does not receive a response to the sending of this SIP message OPTIONS because the called terminal is no longer reachable. In the embodiment described here, the TAS server triggers the Terminating IN services (steps (14), (15)) and the routing is done conventionally by default via the 2G, 3G network in circuit mode.
Description of a Second Variant of the Invention
In a second variant of the invention, and as illustrated in
In the embodiments described above, the TAS server determines the access network of the called terminal after having determined that the service profile of the user associated with the called terminal has Terminating IN service marks. These steps can be reversed, but it is preferable to determine the access network of the called terminal only when the latter benefits from Terminating IN services so as not to overload the network.
In the embodiments described above, the case of an incoming call arriving from a caller in circuit mode has been described. The invention applies in the same way in the case of a caller from the same IMS network core or from another IMS core via an interconnection mechanism in VoIP.
In the embodiments described above, the anchoring procedure in the IMS network is carried out when the called terminal is registered in SIP in the IMS network core. The invention applies in the same way if the anchoring procedure is carried out systematically, in other words whether the called terminal is registered or not in SIP at the core of the IMS network.
In the embodiments described above, the anchoring procedure in the IMS network is carried out by intelligent network mark CAMEL. It can also be done by deploying the ICS (IMS Centralized Service) mode via a standardized interface I2/I3 from the MSC/GMSC to the IMS core.
These different variants are known to those skilled in the art and standardized.
The called terminal does not have to be registered in SIP at the core of the IMS network for the invention to be implemented. Indeed, as soon as an incoming call is held by the IMS network core, if the called terminal is not registered in SIP at the S-CSCF server, this S-CSCF server downloads on itself the profile of the triggering of the TAS server in the HSS/HLR/SDM, this profile defining the systematic routing of all incoming and outgoing SIP messages INVITE towards the TAS server.
Number | Date | Country | Kind |
---|---|---|---|
1761448 | Nov 2017 | FR | national |
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/FR2018/052811 | 11/13/2018 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2019/106253 | 6/6/2019 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
7181401 | Johnson | Feb 2007 | B2 |
8078166 | Bultinck et al. | Dec 2011 | B2 |
10084700 | Malhotra | Sep 2018 | B1 |
20070064886 | Chiu | Mar 2007 | A1 |
20070100981 | Adamczyk | May 2007 | A1 |
20080162637 | Adamczyk | Jul 2008 | A1 |
20080171531 | Vohringer | Jul 2008 | A1 |
20100103888 | Takano | Apr 2010 | A1 |
20100195542 | Li | Aug 2010 | A1 |
20100232417 | Segre | Sep 2010 | A1 |
20100278125 | Clair | Nov 2010 | A1 |
20110249658 | Wohlert | Oct 2011 | A1 |
20110250895 | Wohlert | Oct 2011 | A1 |
20130171974 | Bae | Jul 2013 | A1 |
20150141052 | Bolin | May 2015 | A1 |
20150207847 | Kim | Jul 2015 | A1 |
20160142447 | Mufti | May 2016 | A1 |
20170332281 | Bouvet | Nov 2017 | A1 |
20170347304 | Kodaypak | Nov 2017 | A1 |
20180049275 | Agarwal | Feb 2018 | A1 |
20190297121 | Qiao | Sep 2019 | A1 |
20190349209 | Badar | Nov 2019 | A1 |
20200296572 | Bachmutsky | Sep 2020 | A1 |
Number | Date | Country |
---|---|---|
2882482 | Aug 2016 | FR |
2013121158 | Aug 2013 | WO |
Entry |
---|
English translation of the Written Opinion dated Jan. 24, 2019 for corresponding International Application No. PCT/FR2018/052811, filed Nov. 13, 2018. |
International Search Report and Written Opinion dated Jan. 15, 2019 for corresponding International Application No. PCT/FR2018/052811, filed Nov. 13, 2018. |
Jih-Wei Tsai et al., “The Technique of IMS Sh interface and its NGN LBS application”, Communication Technology (ICCT), 2010 12th IEEE International Conference on, IEEE, Piscataway, NJ, USA, Nov. 11, 2010 (Nov. 11, 2010), pp. 599-602, XP031849982. |
Number | Date | Country | |
---|---|---|---|
20200389504 A1 | Dec 2020 | US |