EP3048828A1 - Constitution preliminaire d'une base de données de numeros portés pour routage de services d'une suite de communication enrichie - Google Patents

Constitution preliminaire d'une base de données de numeros portés pour routage de services d'une suite de communication enrichie Download PDF

Info

Publication number
EP3048828A1
EP3048828A1 EP16152229.7A EP16152229A EP3048828A1 EP 3048828 A1 EP3048828 A1 EP 3048828A1 EP 16152229 A EP16152229 A EP 16152229A EP 3048828 A1 EP3048828 A1 EP 3048828A1
Authority
EP
European Patent Office
Prior art keywords
routing data
mobile station
message
routing
telecommunications 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.)
Granted
Application number
EP16152229.7A
Other languages
German (de)
English (en)
Other versions
EP3048828B1 (fr
Inventor
Phillip Carter
Oscar Gallego Gomez
Jakub NOWICKI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vodafone IP Licensing Ltd
Original Assignee
Vodafone IP Licensing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vodafone IP Licensing Ltd filed Critical Vodafone IP Licensing Ltd
Publication of EP3048828A1 publication Critical patent/EP3048828A1/fr
Application granted granted Critical
Publication of EP3048828B1 publication Critical patent/EP3048828B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H04W8/28—Number portability ; Network address portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/654—International mobile subscriber identity [IMSI] numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering

Definitions

  • the desired destination user device is addressed using the mobile station or mobile subscriber number (MSISDN) of the destination user device.
  • MSISDN mobile subscriber number
  • most territories have a number of different competing mobile network operators who support communications with different user devices. Accordingly, in order to contact the destination user device using the mobile station number and to provide telecommunications services it is necessary to route any communications request to the specific mobile network operator who supports communications with the destination user device, commonly referred to as the specific mobile network operator which owns the mobile station number.
  • mobile station numbers are allocated to user devices by a national or regional number authority assigning each of the mobile network operators in a country or region a block or range of mobile station numbers. The mobile network operators then in turn assign each of their customer user devices a mobile station number taken from their respective assigned range. Historically, lists of the assigned ranges of numbers were made available to mobile network operators so that the mobile network operator supporting communications with a specific destination user device could be identified by comparing the mobile station number of the user device with the lists. Communications requests for the destination user device could then be correctly routed to the identified mobile network operator.
  • One model for changing operator is for a user to request a new operator to take over responsibility for supporting communications with the mobile number of a user device, and for the new operator to take over full responsibility for the mobile number, referred to as the recipient-led model.
  • the recipient-led model When the recipient-led model is used all mobile network operators in a country or region synchronise or combine their number databases so that all mobile network operators are aware which mobile network operator is currently supporting communications with each mobile station number.
  • Another model for changing mobile network operator is for a user to request authorization from their current mobile network operator to allow their new mobile network operator to use the mobile number of a user device, referred to as the donor-led model.
  • the donor-led model only the old and new mobile network operators are aware of the change, so that each mobile network operator is only aware of numbers which it has transferred to other mobile network operators or which other mobile network operators have transferred to it.
  • the donor-led model is used a communications request for a mobile number is made to the original mobile network operator for that number, and the original mobile network operator is responsible for forwarding the communications request to the new mobile network operator.
  • RCS Rich Communications Suite
  • the volume of telecommunications traffic generated by RCS telecommunications services may be much higher than for voice call and SMS services, so that even where this approach is used to deal with number portability for voice call or SMS services it may not be useable for RCS telecommunications services.
  • a further problem with RCS telecommunications services is that third party operators, also known as over the top providers, who are not themselves mobile network operators may provide RCS telecommunications services to user mobile devices in parallel with the mobile network operator owning the mobile station number of the user mobile device. In this case it can be technically complex, difficult and costly to include the third party operators in addition to the mobile network operators in a common routing solution.
  • Another proposal is for a number of mobile network operators to group together and use a common central interconnect hub to provide RCS routing services for telecommunications traffic to and from all of the mobile network operators in the group.
  • This approach can have considerable integration costs, and it may be technically complex and difficult to integrate all of the databases of the different mobile network operators.
  • Another proposal is for countries using the donor-led model to simply use a similar approach as for voice calls and SMS and make the original mobile network operator responsible for routing RCS telecommunications traffic to the new mobile network operator. This has the problem that routing relies on a mobile network operator who may no longer have any relationship with either of the communicating parties, and who may not be willing, or able, to route RCS telecommunications traffic to the new mobile network operator.
  • Another proposal is for two mobile network operators to be interconnected so that each mobile network operator can forward any unresolved RCS telecommunications traffic, that is any RCS telecommunications traffic for mobile device numbers which are not owned by that mobile network operator, to the other interconnected mobile network operator.
  • RCS telecommunications traffic that is any RCS telecommunications traffic for mobile device numbers which are not owned by that mobile network operator.
  • MSISDN mobile station number
  • RCS Rich Communication Services
  • the operator in a region which should be used to route services to a user device addressed by a mobile station number can be determined by recording which operator is the source of any capabilities exchange or signed presence subscription messages relating to the mobile station number which are received.
  • the identified operator identities can then be stored in association with the respective mobile station numbers in a routing database. Messages to be sent to mobile station numbers can then be routed based on respective stored operator identities associated with the mobile station numbers in the routing database.
  • a first aspect provides a method of automatically gathering routing information in a telecommunications network providing Internet Protocol "IP" communications based on mobile station number "MSISDN”, the method comprising the steps of: analyzing incoming telecommunications traffic to identify messages from other telecommunications networks, which messages include mobile station numbers; and, when such a message is identified: extracting the mobile station number from the identified message; obtaining routing data for the telecommunications network from which the message was received; and storing the extracted mobile station number in association with the obtained routing data.
  • IP Internet Protocol
  • MSISDN mobile station number
  • a second aspect provides a method of operating a telecommunications network providing Internet Protocol "IP” communications based on mobile station number "MSISDN”, the method comprising automatically gathering routing information according to the first aspect, and further comprising: sending a message to a mobile station number, the message being sent with a routing based on routing data previously stored in association with the mobile station number.
  • IP Internet Protocol
  • MSISDN mobile station number
  • a third aspect provides an apparatus for automatically gathering routing information from a telecommunications network providing Internet Protocol "IP” communications based on mobile station numbers "MSISDN”, the apparatus comprising: an analyser arranged to analyse incoming telecommunications traffic to identify messages from other telecommunications networks, which messages include mobile station numbers; and a number extractor arranged to extract the mobile station number from the identified messages; a routing data component arranged to obtain routing data for the telecommunications network from which each identified message was received; and a data store for storing said extracted mobile station number in association with said obtained routing data.
  • IP Internet Protocol
  • MSISDN mobile station numbers
  • a fourth aspect provides a telecommunications network providing Internet Protocol "IP” communications based on mobile station number "MSISDN”, the network comprising apparatus for automatically gathering routing information according to the third aspect, and further comprising: a routing component arranged to control the routing of a message sent to a mobile station number, so that the message is sent with a routing based on routing data stored in association with the mobile station number in the data store.
  • IP Internet Protocol
  • MSISDN mobile station number
  • a fifth aspect provides computer software comprising a series of instructions which, when executed on a processor, will cause the processor to carry out the method according to any one of the first and second aspects.
  • a sixth aspect provides a tangible computer-readable storage comprising computer-readable instructions which, when executed on a processor of a computer will cause the computer to carry out the method according to any one of the first and second aspects.
  • the methods described herein may be performed by software in machine readable form on a tangible storage medium e.g. in the form of a computer program comprising computer program code means adapted to perform all the steps of any of the methods described herein when the program is run on a computer and where the computer program may be embodied on a computer readable medium.
  • tangible (or non-transitory) storage media include disks, thumb drives, memory cards etc and do not include propagated signals.
  • the software can be suitable for execution on a parallel processor or a serial processor such that the method steps may be carried out in any suitable order, or simultaneously.
  • firmware and software can be valuable, separately tradable commodities. It is intended to encompass software, which runs on or controls “dumb” or standard hardware, to carry out the desired functions. It is also intended to encompass software which "describes” or defines the configuration of hardware, such as HDL (hardware description language) software, as is used for designing silicon chips, or for configuring universal programmable chips, to carry out desired functions.
  • HDL hardware description language
  • Embodiments of the present invention are described below by way of example only. These examples represent the best ways of putting the invention into practice that are currently known to the Applicant although they are not the only ways in which this could be achieved.
  • the description sets forth the functions of the example and the sequence of steps for constructing and operating the example. However, the same or equivalent functions and sequences may be accomplished by different examples.
  • FIG. 1 illustrates a routing information system for gathering and recording routing information according to a first embodiment of the present invention.
  • a first telecommunications network 1 is shown.
  • the first telecommunications network 1 supports IP communications using MSISDNs, in this example Rich Communications Suite (RCS) telecommunications services, and is operated by a local mobile network operator.
  • the first telecommunications network 1 comprises a routing information system 2 according to the present invention.
  • the first telecommunications network 1 is shown schematically in figure 1 and only parts of the first telecommunications network 1 which are required to allow the present invention to be understood are shown. It will be understood that the first telecommunications network 1 will in practice comprise a very large number of other components, but these are not described or shown to improve clarity and to avoid obscuring the scope of the present invention.
  • the network supports RCS and the concepts will described in this context.
  • many of the concepts are also applicable to IP communications based on MSISDNs where it is important to be able to easily identify the location, destination or origin of the user device, whether that be in the network of a particular operator, a new operator or a third party IP communications network.
  • This is further evidenced using embodiments operating the Session Initial Protocol (SIP) upon which many RCS services are based.
  • SIP Session Initial Protocol
  • This protocol is similarly just one example of a protocol that can be utilised to embody the described concepts.
  • the first telecommunications network 1 comprises a multimedia service platform 3 which supports RCS telecommunications services, and a local subscriber or user database 4, which can be accessed by the multimedia service platform 3.
  • the local user database 4 contains data regarding users who are customers or subscribers of the local network operator, which data includes the mobile station numbers (MSISDN) of the user devices of those users.
  • MSISDN mobile station numbers
  • the first telecommunications network 1 further comprises a border gateway control component 5 and an interconnect service border gateway component 6.
  • the border gateway control component 5 acts as a routing component and selects routing paths for outbound telecommunications traffic. That is, telecommunications traffic with a destination outside the first telecommunications network 1.
  • the interconnect service border gateway component 6 carries out telecommunications traffic management and accounting for telecommunications connections between the first telecommunications network 1 and remote telecommunications networks separate from the first telecommunications network 1. These telecommunications connections are referred to as interconnections.
  • the first telecommunications network 1 further comprises a number of point of interconnect (POI) components 7a to 7n.
  • Each point of interconnect component 7a to 7n is a component through which the first telecommunications network 1 exchanges telecommunications traffic with a specific remote telecommunications network.
  • Each point of interconnect component 7a to 7n may be a physical or logical component.
  • telecommunications systems providing RCS telecommunications services must be able to identify user devices able to participate in RCS services.
  • a user device must have the necessary functionality to support RCS services in order to participate at all.
  • the ability to participate also depends upon the current capabilities of the user device, which may change rapidly and unpredictably, for example due to changes in the type and quality of network access currently available to the user device. Further, the ability to participate may change based on user activities, which may also change rapidly and unpredictably, for example a user may identify themselves as unable to participate in RCS services when they are making a voice call or are in a meeting where they do not wish to be disturbed. Accordingly, the ability of user devices to participate in RCS services will change over time and so must be tracked and updated.
  • a telecommunications system providing RCS telecommunications services incorporates a capabilities exchange mechanism or a signed presence subscription mechanism, or both ,to provide or retrieve up to date information on the current ability of user devices to participate in RCS services.
  • the telecommunications system incorporates both a capabilities exchange mechanism and a signed presence subscription mechanism.
  • the capabilities exchange mechanism operates when a user device indicates an intention to communicate with another user device.
  • a capabilities exchange mechanism when an RCS client of a first, originating, user device detects a possible intention to communicate with another, terminating, user device, the RCS client of the originating user device initiates an ad-hoc capabilities check by sending a capabilities exchange request message to the terminating user device.
  • the capabilities exchange request message includes the mobile station number (MSISDN) of the originating user device.
  • An RCS client of the terminating user device responds to this capabilities exchange request message by sending a capabilities exchange response message indicating the current ability of the terminating user device to participate in RCS services.
  • the RCS client of the originating device may for example detect a possible intention to communicate with a terminating user device when a user of the originating user device opens a contact card or chat message relating to the terminating user device.
  • the capabilities exchange mechanism may also be used to determine the capability of user devices to participate in RCS services when user devices are initially or subsequently discovered as contacts eligible for IP services based on MSISDN.
  • the signed presence subscription mechanism is used in a telecommunications system providing RCS telecommunications services to allow different users to establish permanent presence exchange relationships in which user devices may actively publish their current ability to participate in RCS services, and thus act as presentities, and may also subscribe to presence notifications from other user devices, and thus act as presence watchers.
  • a user device in order to become a presence watcher a user device sends a signed presence notification subscription request message identifying the user device to be subscribed to and including the mobile station number (MSISDN) of the requesting user device to the telecommunications system.
  • MSISDN mobile station number
  • This mobile station number is then used by the user device which is the subject of the request to identify the requester to the user of the subject user device when the user is asked to authorise any presence notification subscription request.
  • the signed presence subscription mechanism may typically be used by a user device to attempt to subscribe to the presence information of all RCS user devices discovered on initial start of the user device, and will then be refreshed periodically.
  • RCS telecommunications systems may also include an anonymous subscription mechanism which can be sent from an originating user device to determine whether a terminating user device can be contacted via Internet Protocol (IP) without identifying the originating user device.
  • IP Internet Protocol
  • the anonymous subscription mechanism is not used in the present invention since the message does not include the identity of the originating device, that is, it is anonymous. Accordingly, in the description below the wording presence subscription mechanism or presence subscription message refers to a signed presence subscription mechanism and signed presence subscription messages respectively.
  • RCS telecommunications systems including capabilities exchange mechanisms and presence subscription mechanisms are well known to the skilled person in the technical field of the present invention. Accordingly, the capabilities exchange mechanism and presence subscription mechanism are only described in general terms herein, and not in detail.
  • the first telecommunications network 1 In operation of the first telecommunications network 1, as a result of the routine operations of the capabilities exchange mechanism and the presence subscription mechanism the first telecommunications network 1 will receive capabilities exchange request messages and presence notification subscription request messages from user devices of other remote telecommunications networks.
  • a second, remote, telecommunications network 8 is connected to the first telecommunications network 1 through a first point of interconnect component 7a.
  • a first user device 9 is provided with RCS telecommunications services by the first telecommunications network 1
  • a second user device 10 is provided with RCS telecommunications services by the second telecommunications network 8.
  • the second user device 10 acting as an originating device sends a capabilities exchange request message to the first user device 9, the capabilities exchange request message is sent from the second user device 10 to the second telecommunications network 8, as indicated by arrow 11 a.
  • the capabilities exchange request message is then sent by the second telecommunications network 8 to the first telecommunications network 1, where the message is received by the first point of interconnect component 7a, as indicated by the arrow 11 b.
  • the first point of interconnect component 7a then sends the capabilities exchange request message to the interconnect service border gateway component 6, as indicated by the arrow 11c, which in turn sends the capabilities exchange request message to the multimedia service platform 3, as indicated by the arrow 11 d.
  • the multimedia service platform 3 then extracts the identity of the first user device 9 from the capabilities exchange request message and retrieves any necessary data regarding the first user device 9 from the local user database 4. The multimedia service platform 3 then uses the retrieved data to forward the capabilities exchange request message through the first telecommunications network 1 to the first user device 9, as indicated by the arrow 11e.
  • the second user device 10 When, as a part of the operation of the presence subscription mechanism, the second user device 10 sends a presence notification subscription request message to subscribe to presence information regarding the first user device 9, the presence notification subscription request message is sent from the second user device 10 to the first user device 9 as indicated by arrows 11 a to 11 e in a similar manner to a capabilities exchange request message.
  • the routing information system 2 comprises a traffic analyser 20, a routing database provisioning component 21 and a routing database 22.
  • An example of a method of operation 100 of the routing information system 2 is shown in FIG. 2 .
  • the traffic analyser 20 is connected to the point of interconnect components 7a to 7n and is arranged to passively view and analyse incoming telecommunications traffic passing through the point of interconnect components 7a to 7n in a viewing step 101.
  • the viewing by the traffic analyser 20 is described as passive because the traffic analyser does not interfere with the normal processing and forwarding of the incoming telecommunications traffic by the point of interconnect components 7a to 7n.
  • the traffic analyser 20 is arranged to identify any capabilities exchange request messages and presence notification subscription request messages in the viewed incoming telecommunications traffic in an identifying step 102.
  • a capabilities exchange request message or a presence notification subscription request message is identified a number extractor component of the traffic analyser 20 extracts the mobile station number (MSISDN) of the originating or requesting user device from the message, and a routing data component of the traffic analyser 20 obtains the identity of the point of interconnect in which the message was identified, in an extracting step 103.
  • the traffic analyser 20 then forwards the extracted mobile station number together with the identity of the point of interconnect in which the message was identified to the routing database provisioning component 21 in a forwarding step 104.
  • the routing database provisioning component 21 generates a current association record stating that the extracted mobile station number is associated with the identified point of interconnect in a generating step 105.
  • the routing database provisioning component 21 then uses the generated current association record to update the routing database 22 in an updating step 106.
  • the updating step 106 if there is no existing association record for the extracted mobile station number in the routing database 22, the routing database is updated by storing the current association record as a new record. If there is an existing record for the extracted mobile station number in the routing database 22 which differs from the current association record, the routing database is updated by storing the current association record as an update of the existing record. If there is an existing record for the extracted mobile station number in the routing database 22 which is the same as the current association record, the updating does not change the existing record.
  • the second user device 10 acting as an originating device sends a capabilities exchange request message to the first user device 9, the capabilities exchange request message is sent by the second telecommunications network 8 to the first telecommunications network 1, where the message is received by the first point of interconnect component 7a, as indicated by the arrow 11 b.
  • the traffic analyser 20 views the incoming telecommunications traffic passing through the point of interconnect components 7a to 7n in the viewing step 101, and identifies the capabilities exchange request message from the second user device 10 in the identifying step 102.
  • the traffic analyser 20 then extracts the mobile station number of the originating second user device 10 in the extracting step 103.
  • the traffic analyser 20 then forwards the mobile station number of the originating second user device 10 together with the identity of the first point of interconnect 7a to the routing database provisioning component 21 in the forwarding step 104.
  • the routing database provisioning component 21 generates a current association record for the mobile number of the second user device 10, in the generating step 105.
  • the generated current association record indicates that the mobile station number of the second user device 10 is associated with the first point of interconnect component 7a.
  • the routing database provisioning component 21 then uses the generated current association record to update the record for the mobile number of the second user device 10 in the routing database 22 in the updating step 106.
  • a presence notification subscription request message from the second user device 10 would be processed in a corresponding manner.
  • the routing information system 2 continues to carry out the method 100, over a period of time the data stored in the routing database 22 will accumulate to form an up to date set of routing data in the routing database 22 for all, or substantially all, mobile user devices in contact with mobile user devices of the first telecommunications network 1.
  • This set of routing data can them be used by the first telecommunications network 1 to carry out routing of telecommunications traffic without having to rely on other parties to provide routing information or carry out the routing, and without incurring the cost, technical complexity and difficulty of integrating multiple databases belonging to different mobile network operators and/or third party operators.
  • the first embodiment of the invention described above generates entries for a routing database by using both capabilities exchange request messages and presence notification subscription request messages.
  • these messages types may be used. In principle either of these message types may be used.
  • capabilities exchange request messages and/or presence notification subscription request messages has the advantage that these messages are already being sent in the normal operation of the telecommunications network, so that the present invention does not impose any additional traffic overhead on the telecommunications system.
  • these messages include an identifier of an originating user device on an interconnected remote network. Usually this identifier will be the mobile station number of the originating user device, but this is not essential.
  • routing database 22 An example of the use of the routing database 22 according to the first embodiment to route outbound traffic will now be described with reference to FIG. 3 .
  • FIG. 3 shows the first telecommunications network 1.
  • the first telecommunications network 1 comprises a multimedia service platform 3, a local user database 4, a border gateway control component 5, an interconnect service border gateway component 6, a number of point of interconnect components 7a to 7n, and a routing information system 2 comprising a traffic analyser 20, a routing database provisioning component 21 and a routing database 22.
  • the first user device 9 When the first user device 9 attempts to communicate with the second user device 10 using RCS telecommunications, the first user device 9 sends a communication request message including the mobile station number of the second user device 10 through the first telecommunications network 1 to the multimedia service platform 3, as indicated by the arrow 23a.
  • the multimedia service platform 3 queries the local users database 4 to confirm whether the second user device 10 is a customer of the first telecommunications network 1 provisioned in the local user database 4, as indicated by the arrow 23b.
  • the second user device 10 was a customer of the first telecommunications network 1 provisioned in the local user database 4 the first telecommunications network 1 would be able to contact the second user device 10 directly without any interconnect to another telecommunications network being required.
  • the multimedia service platform 3 sends the request to the border gateway control component 5, as indicated by the arrow 23c.
  • the border gateway control component 5 queries the routing database 22 to identify any association record for the mobile station number of the second user device 10, indicated by the arrow 23d.
  • the routing database 22 If there is an association record for the mobile station number of the second user device 10 in the routing database 22, the routing database 22 returns data identifying which of the points of interconnect 7a to 7n should be used to route telecommunications traffic to the second user device 10 to the border gateway control component 5, as indicated by the arrow 23e. In this example the returned data will indicate that the first point of interconnection 7a should be used.
  • the border gateway control component 5 then adds routing information to the message which indicates the correct point of interconnection 7a to 7n is to be used, in this example the first point of interconnection 7a, and then sends the message to the service border gateway component 6, as indicated by the arrow 23f.
  • the border gateway component 6 reads the routing information and routes the message to the indicated point of interconnection 7a to 7n, in this example the first point of interconnection 7a, as indicated by the arrow 23g.
  • the point of interconnection then sends the message to the respective telecommunications network to which the point of interconnection is connected, and this telecommunications network sends the message to the destination user device.
  • the first point of interconnection 7a sends the message to the second telecommunications network 8, as indicated by the arrow 23h
  • the second telecommunications network 8 sends the message to the second user device 10, as indicated by the arrow 23i.
  • the routing database 22 does not contain any association record for the mobile station number of the second user device 10
  • the first telecommunications network 1 can follow its usual procedure for unresolved traffic, for example returning an error message to the first user device 9.
  • routing database 22 An alternative example of the use of the routing database 22 according to the first embodiment to route outbound traffic will now be described with reference to FIG. 4 .
  • FIG. 4 shows the first telecommunications network 1, which comprises the same components as in the example of FIG. 3 .
  • the first user device 9 when the first user device 9 attempts to communicate with the second user device 10 using RCS telecommunications, the first user device 9 sends a communication request message including the mobile station number of the second user device 10 through the first telecommunications network 1 to the multimedia service platform 3, as indicated by the arrow 24a.
  • the multimedia service platform 3 queries the local user database 4 to confirm whether the second user device 10 is a customer of the first telecommunications network 1 provisioned in the local user database 4, as indicated by the arrow 24b.
  • FIG. 4 Similar to the example of FIG.
  • the first telecommunications network 1 would be able to contact the second user device 10 directly without any interconnect to another telecommunications network being required.
  • the second user device 10 is not provisioned in the local user database 4. Accordingly, the local user database 4 then queries the routing database 22 to identify any association record for the mobile station number of the second user device 10, indicated by the arrow 24c.
  • the routing database 22 If there is an association record for the mobile station number of the second user device 10 in the routing database 22, the routing database 22 returns data identifying which of the points of interconnect 7a to 7n should be used to route telecommunications traffic to the second user device 10 to the local user database 4, as indicated by the arrow 24d. The local user database 4 then sends this data to the multimedia service platform 3, as indicated by the arrow 24e. In this example the returned data will indicate that the first point of interconnection 7a should be used.
  • the multimedia service platform 3 then adds routing information to the message which indicates the correct point of interconnection 7a to 7n is to be used, in this example the first point of interconnection 7a, and then sends the message to the service border gateway component 6, as indicated by the arrow 24f.
  • the border gateway component 6 reads the routing information and routes the message to the indicated point of interconnection 7a to 7n, in this example the first point of interconnection 7a, as indicated by the arrow 24g.
  • the point of interconnection then sends the message to the respective telecommunications network to which the point of interconnection is connected, and this telecommunications network sends the message to the destination user device, as in the previous example.
  • the first point of interconnection 7a sends the message to the second telecommunications network 8, as indicated by the arrow 24h
  • the second telecommunications network 8 sends the message to the second user device 10, as indicated by the arrow 24i.
  • the routing database 22 does not contain any association record for the mobile station number of the second user device 10
  • the first telecommunications network 1 can follow its usual procedure for unresolved traffic.
  • routing database 22 can be used in a similar manner to send any other type of telecommunications traffic.
  • the routing information system according to the second embodiment is based upon the routing information system according to the first embodiment, but with additional functionality.
  • the first telecommunications network 1 comprises a routing information system 30 instead of the routing information system 2, the other components of the first telecommunications network 1 are the same as in the first embodiment illustrated in FIG. 1 .
  • the routing information system 30 comprises a traffic analyser 31, a routing database provisioning component 32, and routing database 33. These have the same functionality as the traffic analyser 20, a routing database provisioning component 21, and routing database 22 of the first embodiment, and also have some additional functionality, as will be explained below.
  • the first telecommunications network 1 comprising the routing information system 30 it may occur that a mobile station number for which there is an association record stored in the routing database 33 is migrated from one mobile network operator to another, so that the telecommunications network providing RCS telecommunications services to that mobile station number changes.
  • the first telecommunications network 1 attempts to send telecommunications traffic to a user device having the mobile station number based on the association record stored in the routing database 33 the telecommunications traffic will be routed to the incorrect telecommunications network, and this incorrect telecommunications network will return a "user not found" error message indicating that this mobile station number cannot be found.
  • the first telecommunications network 1 has routed telecommunications traffic intended to be sent to the second user device 10 through the first point of interconnection 7a to the second telecommunications network 8, as indicated by an arrow 34a.
  • This routing being based on an association record for the second user device 10 stored in the routing database 33. This may for example have been done in the manners of the examples of use shown in FIG. 3 or FIG. 4 .
  • the second user device has been migrated from the second telecommunications network 8 to a third telecommunications network 35. Accordingly, the second telecommunications network 8 is unable to send the telecommunications traffic to the second user device 10, and the second telecommunications network 8 returns a "user not found" error message indicating that the second user device cannot be found to the first point of interconnection 7a of the first telecommunications network 1, as indicated by the arrow 34b.
  • the traffic analyser 31 is arranged to identify error messages of this type in the viewed incoming telecommunications traffic. When the error message is identified the traffic analyser 31 extracts the mobile station number of the second user device 10 from the error message, as indicated by the arrow 34c, and then forwards the extracted mobile station number to the routing database provisioning component 32, as indicated by the arrow 34d.
  • the routing database provisioning component 32 then sends an instruction to delete the association record for the second user device 10 to the routing database 33, as indicted by the arrow 34e, and the routing database 33 deletes this association record.
  • the first telecommunications network 1 may further respond to the "user not found" error message by sending capabilities exchange requests to other interconnected telecommunications networks through their respective points of interconnect. This is a known feature of RCS telecommunications services referred to as sequential search or serial forking.
  • the third telecommunications network 35 responds with a "user found” message indicating that the telecommunications network is the owner of the mobile station number of the second user device 10.
  • this "user found” message may be identified by the traffic analyser 31 and used by the routing information system 30 to store a new association record for the mobile station number of the second user device 10 in the routing database 33 in a similar manner to a capabilities exchange request message or a presence notification subscription request message.
  • the traffic analyser may be implemented as a part of each of the point of interface components.
  • the point of interface component is an IP layer 2 switch with a port mirroring interface.
  • Port mirroring interface is a common functionality of IP layer 2 switches that copies all traffic to a separate Ethernet interface, and can be used for traffic monitoring purposes.
  • the traffic analyser should implement protocol parsers able to understand protocols used for capabilities exchange, for example the session initiation protocol OPTIONS request.
  • the traffic analyser may have the functionality to detect an incoming capabilities exchange request from a remote operator and a mobile number and to respond by sending a request to the routing database provisioning component containing: the type of event, the association detected, and the parameters of the mobile number from the capabilities exchange request and an identifier of the remote operator associated with the point of interconnect carrying the capabilities exchange request.
  • the traffic analyser may have the functionality to detect a 200 OK response with capability tags to an outgoing capabilities exchange request from the local operator to a remote operator and a mobile number and to respond by sending a request to the routing database provisioning component containing: the type of event, the association detected, and the parameters of the mobile number from the capabilities exchange To parameter, and an identifier of the remote operator associated with the point of interconnect carrying the response.
  • the traffic analyser may have the functionality to detect an empty 200 OK response or 404 Not Found response to an outgoing capabilities exchange request from the local operator to a remote operator and a mobile number and to respond by sending a request to the routing database provisioning component containing: the type of event user not found detected, and the parameters of the mobile number from the capabilities exchange To parameter, and an identifier of the remote operator associated with the point of interconnect carrying the response.
  • the routing database provisioning component may have the functionality to receive requests from the traffic analyser and to update associations in a routing database standby instance depending on the type of event in the request.
  • the routing database provisioning component may have the functionality to respond to the event association detected by checking the current association for the mobile number in the request, and if an association does not exist or is associated with an operator with a predefined priority lower than the predefined priority of the remote operator in the request, then updating the record with a new association and setting the association refresh timestamp to the current time, and recording the change in the delta log, or, if an association does exist and is associated with an operator with a predefined priority higher than the predefined priority of the remote operator in the request, not modifying the association.
  • the routing database provisioning component may have the functionality to respond to the event user not found detected by checking the current association for the mobile number in the request, and if an association does not exist or is associated with an operator different from the remote operator in the request, then not taking any action, or, if an association does exist and is associated with the same operator as the remote operator in the request, removing the association, and recording the change in the delta log.
  • the routing database provisioning component may be able to buffer operations requested to the routing database if they are confirmed by the routing database in order to allow the routing database to perform all read and update requests regardless of the internal database switchovers described below.
  • routing database provisioning component may also have further functionality to carry out the optional features described in the present application.
  • the routing database provides a database of associations between mobile numbers and interconnected remote operators.
  • the routing database may implement an ENUM interface, as commonly used in telecommunications routing systems to resolve mobile numbers to routable destination addresses.
  • ENUM interface as commonly used in telecommunications routing systems to resolve mobile numbers to routable destination addresses.
  • the database may be implemented using two identical instances, which change roles, so that at any point in time one is in active and the other is in standby mode, in order to improve performance and reliability.
  • the operations performed by the database instances in each mode may include: the active instance responding to ENUM queries from the IP multimedia service platform component responsible for locating a destination network using a Call Session Control Function or Border Gateway Control Function, depending on the IP multimedia service platform implementation; the passive instance immediately after being switched to backup mode performing all change operations recorded in the delta log of the previously passive node, accepting read and update requests from the routing database provisioning component, confirming to the routing database provisioning component if provisioning requests were executed correctly or not, and maintaining a new delta log with all changes performed while in passive mode.
  • the currently active instance may be switched to standby mode, and at the same time the standby instance may be switched to active mode.
  • the routing database may switch both instances to active mode for short period of time significantly longer than the longest possible switchover lag to eliminate any risk that active node is not available at any time due to switchover lag.
  • the routing database provisioning component should store in the buffer all update operations that were not confirmed and retry them until they are confirmed or time out.
  • the routing database may be initially populated with association records based on the number ranges of mobile station numbers issued to different mobile network operators.
  • the routing database will still contain an association record associating the mobile station number with the point of interconnect for the mobile network operator which originally owned the mobile station number. If this routing data is used and the mobile network operator which originally owned the mobile station number cannot find the mobile station number it will return a "user not found" message.
  • the serial forking process and subsequent steps as discussed above can then be used to update the association record for the mobile station number.
  • all of the association records in the routing database relating to a particular telecommunications network may be may be updated using information provided by the network operator. In some examples this may be done periodically. In some examples this may be done for one, some or all interconnected telecommunications networks. This will require the agreement and cooperation of the relevant network operator(s).
  • the association records in the routing database may have a validity period that would be refreshed each time the traffic analyser detects suitable incoming telecommunications traffic to generate a corresponding new current association record. Association records which are not refreshed before their validity period expires would not be used, and may optionally be deleted.
  • all association records related to one or more interconnected telecommunications networks may be periodically removed.
  • the association records for these telecommunications networks would then be repopulated over time by the methods described above. This may allow incorrect association records to be purged from the routing database.
  • the invention is used in a first telecommunications network interconnected to other telecommunications networks operated by mobile network operators.
  • the invention may be used in a telecommunications network which is interconnected both to other telecommunications networks operated by mobile network operators and to secondary points of interest who are not mobile network operators, but who provide telecommunications services to mobile station numbers owned by the mobile network operators.
  • routing database In the embodiments described above the use of a routing database is described. In alternative examples other forms of data store may be used instead of a database.
  • a mobile network operator may be regarded as owning mobile station numbers, while secondary points of interest do not own mobile station numbers.
  • Mobile network operators are operators who have been issued blocks of mobile station numbers by a regulator.
  • the mobile network operator of the first mobile telecommunications network may perceive a conflict where a particular mobile station number may be provisioned with services both by a mobile network operator and a secondary point of interest.
  • the present invention may identify a single mobile station number as being found in two different interconnected telecommunications networks, one being the network of the mobile network operator and the other being the network of the secondary point of interest.
  • routing information system may be further provided with a conflict resolution mechanism.
  • each mobile network operator and secondary point of interest operating a telecommunications network interconnected to the first telecommunications network is assigned a priority.
  • the assigned priorities reflect the interconnect agreements reached with the operators of the different interconnected telecommunications networks in a given country. However, this is not essential and the priorities may be assigned arbitrarily in any manner preferred by the operator of the first telecommunications network.
  • Each operator of an interconnected telecommunications networks should be assigned a different priority.
  • the assigned priorities may be configurable to reflect any changes in the relationships and agreements between the different operators.
  • mobile network operators are assigned higher priorities and secondary points of interest are assigned lower priorities.
  • the conflict resolution mechanism of the routing information system 2 carries out a conflict resolution method as shown in the flow chart 200 of FIG. 6 .
  • each association record additionally includes the assigned priority of the operator of the telecommunication network on which the mobile station number was identified.
  • a conflict resolution mechanism determines whether an association record for that mobile station number for a different operator is already stored in the routing database 22.
  • step 202 If no association record for a different operator is stored in the routing database 22, the method moves to step 202 and the generated current association record is stored in the routing database 22.
  • step 203 If an association record for a different operator is stored in the routing database 22 the method moves to step 203 and the priorities of the current and stored association records are compared to determine if the stored association record has a higher priority than the current association record.
  • the method moves to step 204 and ends the method without taking any action. Accordingly, the stored association record is retained without change.
  • the method moves to step 202 and the generated current association record is stored in the routing database 22. Accordingly, the stored association record is replaced by the newly generated current association record.
  • This conflict resolution method ensures that association records relating to the higher priority operators are retained in cases of conflict. Accordingly, the method may be used to ensure that association records relating to mobile network operators are retained in preference to association records relating to secondary points of interest.
  • routing is carried out from the first telecommunications network to other telecommunications networks interconnected directly to the first telecommunications network.
  • telecommunications networks may be linked to a telecommunications network employing the present invention through one or more communications hubs or aggregators, so that the present invention may only be able to identify or derive the routing to the intermediating communications hub or aggregator and not to the telecommunications networks themselves.
  • each remote network is associated with one point of interconnect. In other examples there may be more than one point of interconnect associated with a remote network.
  • the association record comprises data identifying which point of interconnect is associated with a mobile station number, and this point of interconnect is used to route telecommunications traffic to the mobile station number.
  • the association record may comprise alternative data which can be used to route telecommunications traffic.
  • the association record may comprise the identity of the telecommunications network from which the mobile station number has been received.
  • the routing data for a mobile user device is deduced from the identity of the point of interconnect carrying messages from the mobile user device.
  • the routing data may be obtained in different ways, provided that the routing data can be unambiguously derived.
  • the routing data for a mobile user device may be derived from signals parameters of the messages.
  • the routing data may be derived from telecommunications traffic from a mobile user device, as will be understood by the person skilled in the art.
  • the components may be hardware components or logical components such as software modules or elements.
  • routing information system 2, 30 may be implemented as any form of a computing and/or electronic device.
  • the computing-based device 2, 30 comprises one or more processors which may be microprocessors, controllers or any other suitable type of processors for processing computer executable instructions to control the operation of the device in order to gather and record routing information.
  • the processors may include one or more fixed function blocks (also referred to as accelerators) which implement a part of the method in hardware (rather than software or firmware).
  • Platform software comprising an operating system or any other suitable platform software may be provided at the computing-based device to enable application software to be executed on the device.
  • Computer-readable media may include, for example, computer storage media such as a memory and communications media.
  • Computer storage media such as a memory, includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.
  • Computer storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device.
  • communication media may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transport mechanism. As defined herein, computer storage media does not include communication media.
  • the database 22, 33 is shown within the computing-based device 2, 30 it will be appreciated that the database 2, 30 may be distributed or located remotely and accessed via a network or other communication link (e.g. using a communication interface).
  • 'computer' is used herein to refer to any device with processing capability such that it can execute instructions. Those skilled in the art will realise that such processing capabilities are incorporated into many different devices and therefore the term 'computer' includes PCs, servers, mobile telephones, personal digital assistants and many other devices.
  • a remote computer may store an example of the process described as software.
  • a local or terminal computer may access the remote computer and download a part or all of the software to run the program.
  • the local computer may download pieces of the software as needed, or execute some software instructions at the local terminal and some at the remote computer (or computer network).
  • a dedicated circuit such as a DSP, programmable logic array, or the like.
  • any reference to 'an' item refers to one or more of those items.
  • the term 'comprising' is used herein to mean including the method blocks or elements identified, but that such blocks or elements do not comprise an exclusive list and a method or apparatus may contain additional blocks or elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
EP16152229.7A 2015-01-26 2016-01-21 Constitution preliminaire d'une base de données de numéros portés pour communication sip Active EP3048828B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
GB1501264.4A GB2534426B (en) 2015-01-26 2015-01-26 Telecommunications routing system

Publications (2)

Publication Number Publication Date
EP3048828A1 true EP3048828A1 (fr) 2016-07-27
EP3048828B1 EP3048828B1 (fr) 2017-12-06

Family

ID=52673931

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16152229.7A Active EP3048828B1 (fr) 2015-01-26 2016-01-21 Constitution preliminaire d'une base de données de numéros portés pour communication sip

Country Status (3)

Country Link
US (1) US10237805B2 (fr)
EP (1) EP3048828B1 (fr)
GB (1) GB2534426B (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109257710A (zh) * 2018-11-16 2019-01-22 安徽时也网络技术有限公司 一种短信服务系统

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102266879B1 (ko) * 2017-04-14 2021-06-22 삼성전자주식회사 대화형 콘텐츠 제공 시스템
EP3665920B1 (fr) 2017-09-12 2023-12-06 Samsung Electronics Co., Ltd. Conservation de numéro mobile
US11140105B2 (en) 2019-07-12 2021-10-05 nativeMsg, Inc. Method and system for providing interoperability for Rich Communication Suite (RCS) messaging
US11553314B2 (en) 2019-07-12 2023-01-10 nativeMsg, Inc. Method and system for providing interoperability for rich communication suite (RCS) messaging with local and remote applications with e-commerce and data collection
US11558320B2 (en) 2019-07-12 2023-01-17 nativeMsg, Inc. Method and system for providing interoperability for rich communication suite (RCS) messaging with local and remote applications
CN114640957B (zh) * 2022-02-15 2024-03-19 深圳市梦网云创科技有限公司 短信发送方法、系统、设备及计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050111640A1 (en) * 2003-02-27 2005-05-26 Tekelec Methods and systems for automatically and accurately generating call detail records for calls associated with ported subscribers
US20060240819A1 (en) * 2002-02-08 2006-10-26 Jianming Xu Method and system for providing mobile number portability between different wireless networks of different technologies
US20080201441A1 (en) * 2007-02-21 2008-08-21 Oz Communications Inc. Method and System for Instant Messaging Traffic Routing
WO2013127667A1 (fr) * 2012-03-02 2013-09-06 Markport Limited Procédé, appareil et support pouvant être lu par un ordinateur pour terminer et reconstruire un message routage de messages d'envoi d'informations d'acheminement (sri) dans des réseaux mobiles

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7269157B2 (en) * 2001-04-10 2007-09-11 Internap Network Services Corporation System and method to assure network service levels with intelligent routing
US7953415B2 (en) * 2005-06-03 2011-05-31 Alcatel-Lucent Usa Inc. Method and system for wireless number portability
US9008039B2 (en) * 2010-12-17 2015-04-14 Verizon Patent And Licensing Inc. Mobile phone/docking station call continuity
US9462436B2 (en) * 2012-12-20 2016-10-04 Intel Corporation Preventing dropped calls through behavior prediction

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060240819A1 (en) * 2002-02-08 2006-10-26 Jianming Xu Method and system for providing mobile number portability between different wireless networks of different technologies
US20050111640A1 (en) * 2003-02-27 2005-05-26 Tekelec Methods and systems for automatically and accurately generating call detail records for calls associated with ported subscribers
US20080201441A1 (en) * 2007-02-21 2008-08-21 Oz Communications Inc. Method and System for Instant Messaging Traffic Routing
WO2013127667A1 (fr) * 2012-03-02 2013-09-06 Markport Limited Procédé, appareil et support pouvant être lu par un ordinateur pour terminer et reconstruire un message routage de messages d'envoi d'informations d'acheminement (sri) dans des réseaux mobiles

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
TOM VAN PELT: "RCS-e - Advanced Communications: Services and Client Specification", 4 July 2012 (2012-07-04), XP055263476, Retrieved from the Internet <URL:http://www.gsma.com/network2020/wp-content/uploads/2012/03/rcs-e_advanced_comms_specification_v1_2_2_approved.pdf> [retrieved on 20160407] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109257710A (zh) * 2018-11-16 2019-01-22 安徽时也网络技术有限公司 一种短信服务系统

Also Published As

Publication number Publication date
US20160219490A1 (en) 2016-07-28
GB2534426B (en) 2018-01-03
US10237805B2 (en) 2019-03-19
EP3048828B1 (fr) 2017-12-06
GB201501264D0 (en) 2015-03-11
GB2534426A (en) 2016-07-27

Similar Documents

Publication Publication Date Title
US10237805B2 (en) Telecommunications routing system
US9692793B2 (en) Communication session allocation
US11864098B2 (en) Methods and apparatuses for network function selection in 5G for a user
WO2021004528A1 (fr) Procédé, dispositif et appareil d&#39;acquisition d&#39;adresse d&#39;exemple d&#39;application et support d&#39;informations
US20130054635A1 (en) Procuring communication session records
CN109246078B (zh) 一种数据交互方法及服务器
CN111757353B (zh) 5g核心网中的网络数据处理方法及装置
US11133946B2 (en) Systems and methods for selective provisioning of a charging function in a wireless network
EP2924942A2 (fr) Procédé, dispositif et système permettant la distribution du protocole d&#39;ouverture de session (sip) par un serveur multi-service
US20150036587A1 (en) Providing services based on radio access network type information
US9942766B1 (en) Caller validation for end service providers
EP3414926B1 (fr) Système de connexion d&#39;appel sélectif avec une commande en vol
US20170111402A1 (en) Call method, call apparatus, voip server, and call system
US9813317B2 (en) Self-localizing data distribution network
WO2017161565A1 (fr) Procédé, appareil et système pour qu&#39;un ensemble de services de réseau accède à des données de contexte
CN107517162B (zh) 一种cdn缓存服务器的确定方法及装置
US11546463B2 (en) Systems and methods for managing software telephones
CN114845350A (zh) 一种路由选择方法及装置
US10917480B2 (en) Service orchestration across multiple service domains
US20150282121A1 (en) Local resource sharing method of machine to machine component and apparatus thereof
US20070140457A1 (en) Method and apparatus for selectively routing callers to service call centers
CN106331270B (zh) 管理联系人的号码的方法和装置
US20230179696A1 (en) Method for managing an unallocated telephone number in a communication network, method for processing a request for allocating a telephone number, corresponding devices, item of communication equipment, system and computer programs
US7966656B2 (en) Method of coupling a switched circuit network to an internet protocol network
US20150032819A1 (en) Provisioning A Relation Between Users In A Network Subsystem

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

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: BA ME

17P Request for examination filed

Effective date: 20170127

RBV Designated contracting states (corrected)

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

RIC1 Information provided on ipc code assigned before grant

Ipc: H04M 3/42 20060101ALN20170518BHEP

Ipc: H04W 8/28 20090101AFI20170518BHEP

Ipc: H04W 40/30 20090101ALI20170518BHEP

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: H04M 3/42 20060101ALN20170606BHEP

Ipc: H04W 8/28 20090101AFI20170606BHEP

Ipc: H04W 40/30 20090101ALI20170606BHEP

INTG Intention to grant announced

Effective date: 20170629

RIC1 Information provided on ipc code assigned before grant

Ipc: H04M 3/42 20060101ALN20170619BHEP

Ipc: H04W 8/28 20090101AFI20170619BHEP

Ipc: H04W 40/30 20090101ALI20170619BHEP

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 953394

Country of ref document: AT

Kind code of ref document: T

Effective date: 20171215

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016000974

Country of ref document: DE

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 3

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20171206

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

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

Ref country code: SE

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

Effective date: 20171206

Ref country code: NO

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

Effective date: 20180306

Ref country code: LT

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

Effective date: 20171206

Ref country code: FI

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

Effective date: 20171206

Ref country code: ES

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

Effective date: 20171206

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 953394

Country of ref document: AT

Kind code of ref document: T

Effective date: 20171206

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

Ref country code: LV

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

Effective date: 20171206

Ref country code: BG

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

Effective date: 20180306

Ref country code: HR

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

Effective date: 20171206

Ref country code: RS

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

Effective date: 20171206

Ref country code: GR

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

Effective date: 20180307

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

Ref country code: NL

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

Effective date: 20171206

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

Ref country code: CZ

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

Effective date: 20171206

Ref country code: SK

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

Effective date: 20171206

Ref country code: EE

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

Effective date: 20171206

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

Ref country code: AT

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

Effective date: 20171206

Ref country code: RO

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

Effective date: 20171206

Ref country code: PL

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

Effective date: 20171206

Ref country code: SM

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

Effective date: 20171206

Ref country code: IT

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

Effective date: 20171206

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016000974

Country of ref document: DE

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

Ref country code: MC

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

Effective date: 20171206

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

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

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180121

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20180131

26N No opposition filed

Effective date: 20180907

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

Ref country code: DK

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

Effective date: 20171206

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180131

Ref country code: SI

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

Effective date: 20171206

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

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180121

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190131

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190131

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

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180121

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

Ref country code: TR

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

Effective date: 20171206

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

Ref country code: PT

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

Effective date: 20171206

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

Ref country code: CY

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

Effective date: 20171206

Ref country code: MK

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20171206

Ref country code: HU

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

Effective date: 20160121

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

Ref country code: AL

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

Effective date: 20171206

Ref country code: IS

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

Effective date: 20180406

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230124

Year of fee payment: 8

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

Effective date: 20230519

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240119

Year of fee payment: 9

Ref country code: GB

Payment date: 20240123

Year of fee payment: 9