US20140301334A1 - Method of managing a communication to a user, and an application server - Google Patents
Method of managing a communication to a user, and an application server Download PDFInfo
- Publication number
- US20140301334A1 US20140301334A1 US14/354,038 US201214354038A US2014301334A1 US 20140301334 A1 US20140301334 A1 US 20140301334A1 US 201214354038 A US201214354038 A US 201214354038A US 2014301334 A1 US2014301334 A1 US 2014301334A1
- Authority
- US
- United States
- Prior art keywords
- terminal
- core network
- voice over
- user
- communication
- 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
Links
- 238000004891 communication Methods 0.000 title claims abstract description 74
- 238000000034 method Methods 0.000 title claims abstract description 17
- 230000000694 effects Effects 0.000 claims abstract description 71
- 238000007726 management method Methods 0.000 claims abstract description 17
- 238000004590 computer program Methods 0.000 claims description 6
- 230000006870 function Effects 0.000 description 8
- 230000008901 benefit Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 206010048669 Terminal state Diseases 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000004377 microelectronic Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/75—Media network packet handling
- H04L65/752—Media network packet handling adapting media to network capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
- H04M7/0075—Details of addressing, directories or routing tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1016—IP multimedia subsystem [IMS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1059—End-user terminal functionalities specially adapted for real-time communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1063—Application servers providing network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
Definitions
- the invention relates to the general field of telecommunications.
- VoIP voice over IP
- IMS IP multimedia subsystem
- IMS centralized service As developed by the 3GPP standard, and as described in particular in the document 3GPP TS 23.292 entitled “Technical specification group services and system aspects; IP multimedia subsystem centralized services; stage 2”, Release 11, v11.0.0, June 2011.
- the ICS service seeks to use an IMS core network to offer multimedia services to a mobile user independently of the access network with which the user is connected (i.e. a circuit-switched or a packet-switched access network).
- a circuit-switched or a packet-switched access network i.e. a circuit-switched or a packet-switched access network.
- Circuit-switched access network users can thus benefit from new IMS services while continuing to benefit from the services conventionally available on circuit-switched access networks, with those services now being managed by the IMS core network.
- the ICS service relies in particular on triggering a service centralization and continuity application server (SCC-AS) in charge of ensuring continuity of services for various access networks.
- SCC-AS server has in particular the function of managing the terminating of each communication passing therethrough by selecting the domain (packet-switched or circuit-switched) to which the communication is to be routed.
- the functions of the SCC-AS server are described in greater detail in the document 3GPP TS 24.292 entitled “Technical specification group core network and terminals; IP multimedia core network subsystem; centralized services; stage 3”, Release 10, v10.5.0, September 2001.
- the 3GPP standard provides the possibility of a user registering a plurality of addresses of contact with the IMS core network, all linked to the same identifier of that user on the core network (e.g. an SIP address). These addresses of contact may be associated with a plurality of different terminals.
- the 3GPP standard provides for the possibility of the SCC-AS server taking account of multiple terminals linked to the same identifier of the user on the core network, the standard does not describe how this might or must be implemented.
- the invention satisfies this need in particular by proposing a management method for managing a communication to a user having an identifier allocated thereto on a voice over IP core network, the method being performed by an application server of the voice over IP core network through which the communication transits.
- the method comprises a step, performed on receiving the communication, of consulting a database to select a terminal linked to the identifier of the user for the purpose of routing the communication to the terminal, the database associating at least one terminal registered on the voice over IP core network and linked to the identifier of the user with at least one period of activity of the terminal on the voice over IP core network, and the terminal that is selected being the terminal associated in the database with the most recent period of activity.
- the invention also provides an application server of a voice over IP core network, suitable for managing a communication transiting therethrough and intended for a user having an identifier allocated thereto on the voice over IP core network.
- the server includes means that are activated on receiving the communication to consult a database in order to select a terminal linked to the identifier of the user for the purpose of routing the communication to the terminal, the database associating at least one terminal registered on the voice over IP core network and linked to the identifier of the user with at least one period of activity of the terminal on the voice over IP core network, and the terminal that is selected being the terminal associated in the database with the most recent period of activity.
- the invention has a preferred but non-limiting application when the voice over IP core network is an IMS core network and the application server is an SCC-AS server of the IMS core network.
- the invention thus makes it possible to enrich the functions of the SCC-AS server as defined in the 3GPP standard.
- the term “activity” of a terminal is used to cover any protocol activity of that terminal, i.e. any activity associated with exchanging messages over the voice over IP core network (sending or receiving one or more messages), such as for example messages in compliance with the session initiation protocol (SIP).
- This may comprise in particular a period of activity associated with setting up a call (e.g. associated with sending or receiving an SIP INVITE message), or exchanging information between two terminals (associated with sending or receiving an SIP OPTIONS message), or exchanging information between a terminal and some other piece of equipment of the network, or indeed registering or unregistering the terminal (associated with sending an SIP REGISTER or UNREGISTER message), etc.
- the invention When in the presence of a plurality of registered terminals linked to the same identifier of a user on the voice over IP core network, the invention thus proposes routing an incoming communication to the most recently active terminal of the user, i.e. to the terminal that is associated in a database maintained by the application server with the period of activity that is the most recent relative to the incoming communication.
- the invention thus enhances the reachability of the terminal when performing the selection for the purpose of routing the communication.
- a “communication” intended for a user designates any exchange of data that is to be performed with a terminal of that user, whether in the circuit-switched (CS) domain, or in the packet-switched (PS) domain.
- the invention makes it possible not only to manage communications of the telephone call type, but also to exchange multimedia data such as, for example: files, photos, multimedia messages, short message service (SMS), etc.
- the invention is also particularly advantageous in that it is performed in the voice over IP core network by the application server through which communications transit in the core network, and consequently it does not require any modification to the source or destination terminals of the communication.
- Terminal selection is also performed in a manner that is automatic, without requiring any intervention by the terminal originating the communication or by the user to whom the communication is being made.
- the database is updated by the application server, periodically or on the application server detecting a period of activity of a terminal linked to the identifier of the user on the voice over IP core network.
- the invention thus makes it possible to have recent and reliable knowledge about the state of activity of a terminal on the voice over IP core network and to adapt communication routing accordingly.
- the terminal linked to the identifier of the user and associated with the most recent period of activity is selected while also verifying a predetermined criterion relating to the nature of the activity of the terminal in that period.
- the terminal linked to the identifier of the user and associated with the most recent period of activity is selected with reference to a communication of the same kind as the incoming communication that the application server is seeking to route.
- This first variant enables routing to be optimized by taking account of the reachability of the selected terminal relative to the nature of the incoming communication.
- the terminal linked to the identifier of the user that is selected is the terminal associated with the most recent period of activity associated with setting up a communication with another terminal.
- the selection as performed in this way is particularly pertinent when the communication being managed by the method of the invention is an incoming telephone call.
- the method of the invention when other types of incoming communication are managed by the method of the invention, it also makes it possible to give precedence to the terminal on which the user has had activity in real time.
- a kind of hierarchy is established between the activities of terminals, i.e. certain activities of terminals, such as for example exchanging messages in the context of setting up a call, are considered as having higher priority (or being more pertinent) compared with other activities when selecting a terminal for routing purposes.
- This makes it possible to optimize routing by taking account of the reachability of the selected terminal given the nature of its past activity, and also relative to the nature of the incoming communication.
- the predetermined criterion relates to the type message that was sent or received by the terminal during that period.
- terminal selection gives precedence to the terminal for which the period of activity corresponds to sending an SIP INVITE message, since that corresponds to setting up a call.
- the management method further comprises a step of routing the communication to the selected terminal.
- the various steps of the management method are determined by computer program instructions.
- the invention also provides a computer program on a data medium, the program being suitable for being performed by an application server or more generally by a computer, the program including instructions adapted to performing steps of the management method as defined above.
- the program may use any programming language, and may be in the form of source code, object code, or code intermediate between source code and object code, such as in a partially compiled form, or in any other desirable form.
- the invention also provides a computer readable data medium, including instructions of a computer program as mentioned above.
- the data medium may be an entity or device capable of storing the program.
- the medium may comprise storage means, such as a read only memory (ROM), e.g. a compact disk (CD) ROM, or a microelectronic circuit ROM, or indeed magnetic recording means, e.g. a floppy disk or a hard disk.
- ROM read only memory
- CD compact disk
- microelectronic circuit ROM indeed magnetic recording means, e.g. a floppy disk or a hard disk.
- the data medium may be a transmissible medium, such as an electrical or optical signal, that may be conveyed via an electrical or optical cable, by radio, or by other means.
- the program of the invention may in particular be downloaded from an Internet type network.
- the data medium may 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.
- the invention also provides a database prepared by an application server of a voice over IP core network and associating at least one terminal registered on the voice over IP core network and linked to an identifier of a user on said voice over IP core network with at least one period of activity of the terminal on the voice over IP core network.
- the invention provides a voice over IP core network system comprising:
- management method the application server, the database, and the system of the invention present in combination all or some of the above-specified characteristics.
- FIG. 1 is a diagrammatic representation of a system, an application server, and a database in accordance with the invention in a particular embodiment
- FIG. 2 is a diagrammatic representation of the hardware architecture of the FIG. 1 application server in a particular embodiment
- FIG. 3 shows the main steps performed during the communication management method of the invention, with the method being performed by the FIG. 1 application server;
- FIG. 4 shows an example of a database in accordance with the invention.
- FIG. 1 shows, in its environment, a system 1 of a voice over IP core network IP-CN in accordance with the invention in a particular embodiment.
- the VoIP core network IP-CN is a core network incorporating IMS architecture and making use of the SIP protocol for the signaling that is exchanged in the core network.
- IMS architecture and SIP protocol are defined respectively in the 3GPP and IETF standards, and in particular in the documents: 3GPP TS 22.228 “Service requirements for the IP multimedia core network subsystem (stage 1)”; and IETF RFC 3261 “Session initiation protocol”. They are therefore not described in detail herein.
- the IMS core network IP-CN comprises a plurality of functional entities, including in particular:
- Each of the terminals T1, T2, and T3 of the user U1 is associated with a respective address of contact AoC1, AoC2, and AoC3 on the core network IP-CN.
- the addresses of contact AoC1, AoC2, and AoC3 are all linked to the identifier IdSIP 1 of the user U1, as is possible in the 3GPP standard.
- the terminals T1 and T2 are suitable for communicating via an access network AN1, e.g. via a packet-switched access network such as the universal mobile telecommunication system (UMTS) network; the terminal T3 is suitable for communicating via an access network AN2, e.g. via a circuit-switched access network such as the global system for mobile communication (GSM) network.
- UMTS universal mobile telecommunication system
- GSM global system for mobile communication
- the terminals T, T1, T2, and T3 need to register with the core network IP-CN in conventional manner as described in particular in the document 3GPP TS 23.292.
- the intervention of an enhanced mobile switching server (eMSC) forming the transition between the “circuit” core network and the IMS core network may be required for terminals connected to circuit-switched networks.
- eMSC enhanced mobile switching server
- This registration serves in particular to enable the core network IP-CN to associate, in the home subscriber server (HSS) of the core network, the addresses of contact AoC1, AoC2, and AoC3 with the identifier IdSIP 1 of the user U1, the address of contact AoC with the identifier IdSIP 2 of the user U2, and where appropriate to trigger initial filter criteria (IFC) to enable the terminals to benefit from the ICS service.
- HSS home subscriber server
- this registration marks the beginning of a potential period of activity in the protocol meaning of the term, i.e. following this registration, the terminals T1, T2, and T3 are in a position to send and/or receive one or more messages in accordance with the SIP protocol, in this example via the core network IP-CN.
- the sending or reception of a message by a terminal via the core network IP-CN constitutes a period of activity of the terminal in the meaning of the invention.
- the SCC AS server 3 in this example is an application server of the system 1 in accordance with the invention. It is suitable for acting in accordance with the invention to manage and route a communication for the user U1 as placed by the user U2 so that the communication goes to that one of the terminals of the user U1 that is associated with the most recent period of activity.
- the SCC AS server 3 prepares and keeps up to date a database 4 in accordance with the invention, which database associates each of the terminals of the user U1 that is registered with the core network IP-CN with at least one period of activity of that terminal on the voice over IP core network.
- This period of activity may in particular be identified in the database 4 by the instant at which the terminal sent or received a message during the period of activity, and possibly by the type of SIP message that was sent or received during that period of activity.
- FIG. 4 shows an example of such a database.
- a “database” designates any type of architecture suitable for storing data, such as a table as shown in FIG. 4 .
- the terminals T1, T2, and T3 having respective addresses of contact AoC1, AoC2, and AoC3 that are linked to the identifier IdSIP 1 of the user U1 are registered with the core network IP-CN: this is represented by the value “REGISTERED” for the terminal state as given in the fourth column of the database with the heading “STATE”.
- M1 is an SIP INVITE message
- M2 and M3 are SIP OPTIONS messages
- x2 ⁇ x1 ⁇ x3 the most recent period of activity of the period T1 is later than the most recent period of activity of the terminal T2 and earlier than the most recent period of activity of the terminal T3.
- this database 4 is kept up to date by the SCC-AS server 3 so as to reflect as accurately as possible the most recent periods of activity of the terminals of the user U1.
- This updating is possible because the SCC-AS server 3 is the anchor point for all of the communications passing via the IMS core network, so it is informed in real time about the periods of activity of the terminals T1, T2, and T3.
- this updating of the database 4 is performed firstly by the SCC-AS server 3 detecting a change of state of a terminal (which change of state is conveyed by the S-CSCF server in known manner, such as, for example:
- the database 4 is also updated in this example on detecting a new period of activity associated with a terminal already included in the database. Since this new period of activity is more recent than the period previously stored in the database for the terminal, it replaces the previously stored period of activity. As a result, the database 4 advantageously reflects only the most recent periods of activity of the terminals.
- the SCC-AS server 3 in this example has the hardware architecture of a computer, as shown diagrammatically in FIG. 2 .
- it comprises a processor 5, a RAM 6, a ROM 7, communication means 8 for communicating over the IMS core network (in particular incorporating means for performing the SIP protocol), together with consultation means 9 for consulting a database 4 in accordance with the invention.
- the ROM 7 of the SCC-AS server 3 constitutes a storage medium in accordance with the invention that is readable by the processor 5 and that stores a computer program in accordance with the invention, including instructions for executing steps of a communication management method of the invention as described below with reference to FIG. 3 .
- FIG. 3 is a flow chart showing the main steps of a method of the invention in a particular implementation in which the method is performed by the SCC-AS server 3 in order to manage a communication placed by the terminal T of the user U2 and intended for the user U1.
- the communication is a telephone call.
- the invention is not limited to managing telephone calls; it also applies to other types of communication enabling multimedia data to be exchanged, both in the circuit-switched domain and in the packet-switched domain (e.g. SMS, multimedia messaging, etc.).
- the invention is not limited to a communication placed by a terminal T, but also applies when the communication comes from some other piece of equipment, e.g. such as a server, etc.
- the terminals T1, T2, and T3 of the user U1 are registered with the core network IP-CN, and that the database 4 is up to date concerning the periods of activity of these terminals, and is identical to the example shown in FIG. 4 .
- the SCC-AS server 3 of the system 1 on receiving a communication (step E 10 ) for the user U1 (i.e. a communication message for the user U1), the SCC-AS server 3 of the system 1 consults the database 4 using the identifier IdSIP 1 allocated to the user U1 (step E 20 ) in order to identify the most recently active terminal associated with the user U1 and registered with the core network IP-CN.
- the communication message placed by the terminal T does not necessarily contain the identifier IdSIP 1 of the user U1 on the core network IP-CN, but it may contain an identifier of the user U1 on the access network AN2, e.g. such as a telephone number.
- the CSCF control entities of the core network replace in conventional manner the identifier of U1 as contained in the message with the identifier IdSIP 1 of the user U1 on the core network IP-CN, as stored in the HSS server.
- the SCC-AS server 3 interrogates the database 4 initially in order to determine whether there exists a terminal associated with the identifier IdSIP 1 that is also registered with the core network (step E 30 ).
- the database 4 is interrogated (step E 50 ) to determine whether a plurality of terminals associated with the identifier IdSIP 1 are registered simultaneously.
- the three terminals T1, T2, and T3 are currently registered with the core network (E 50 , yes).
- the SCC-AS server 3 selects the most recently active terminal from among these terminals for the purpose of routing the communication, i.e. it selects the terminal that is associated in the database 4 with the period of activity that is the most recent at the moment the database 4 is interrogated by the SCC-AS server 3 (or in a variant at the moment the SCC-AS server 3 receives or began processing the communication placed by the terminal T).
- the SCC-AS server 3 selects from the terminals registered and listed in the database 4 a terminal that also satisfies a predetermined criterion relating to the nature of the activity of the terminal during its most recent period of activity.
- Adding this constraint seeks to enable the SCC-AS server 3 to select a terminal corresponding to a message of the same kind as the communication placed by the terminal T of the user U2.
- the communication being set up is a telephone call such that the SCC-AS server 3 is configured to select the most recently active terminal listed in the database 4 that sent or received an SIP message associated with setting up a call during its most recent period of activity (step E 60 ).
- step E 60 the SCC-AS server 3 uses the database 4 to analyze the type of message that was exchanged during its most recent period of activity by each of the terminals T1, T2, and T3 as stored in the database 4 and the instant at which the message was exchanged.
- M1 is a message associated with setting up a call (M1 is an SIP INVITE message).
- M1 is an SIP INVITE message.
- the SCC-AS server 3 thus selects the terminal T1 in order to route the communication placed by the user U2.
- the SCC-AS server 3 selects the terminal corresponding to the most recent period of activity involving setting up a call.
- step E 70 the communication is routed to that terminal, which terminal corresponds to the terminal having the most recent period of activity.
- the SCC-AS server 3 takes into consideration as a criteria relating to the nature of the activity of the terminal, the sending or receiving during said activity of a message relating to setting up a telephone call, and does so independently of the nature of the communication that has been placed by the terminal T of the user U2, and that the application server is seeking to route.
- SCC-AS server 3 does not take into consideration any other criterion for selecting the terminal to which to route the communication. In this implementation, and with reference to the example shown in FIG. 4 , it selects the terminal T3 for routing the communication.
- the communication is then routed to the selected terminal, i.e. in the example of FIG. 4 to the terminal T1, in conventional manner (step E 80 ).
- the database associates each terminal with the most recent period of activity of that terminal on the IMS core network, and the SCC-AS server 3 selects the terminal to which the communication is to be routed by analyzing the data available in the table identifying that period of activity (specifically the instant t and the message type Msg).
- the database 4 could be maintained by the SCC-AS server 3 so as to reflect only the most recent period of activity of the most recently active terminal, such that the selection step consists in extracting from the database 4 the only terminal that is listed in the database.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Disclosed is a management method for managing a communication to a user having an identifier allocated thereto on a voice over IP core network, the method being performed by an application server of the voice over IP core network through which the communication transits, and comprises a process, performed on receiving the communication, of consulting a database to select a terminal linked to the identifier of the user for the purpose of routing the communication to the terminal, the database associating at least one terminal registered on the voice over IP core network and linked to the identifier of the user with at least one period of activity of the terminal on the voice over IP core network, and the terminal that is selected being the terminal associated in the database with the most recent period of activity.
Description
- The invention relates to the general field of telecommunications.
- More particularly it relates to managing and routing a communication to a user by means of an application server of a voice over IP (VoIP) core network, such as for example an IP multimedia subsystem (IMS) core network, and in a context in which a plurality of terminals are linked to the same user identifier on the voice over IP core network.
- A preferred but non-limiting application of the invention thus lies in the IMS centralized service (ICS) as developed by the 3GPP standard, and as described in particular in the document 3GPP TS 23.292 entitled “Technical specification group services and system aspects; IP multimedia subsystem centralized services;
stage 2”, Release 11, v11.0.0, June 2011. - In general, the ICS service seeks to use an IMS core network to offer multimedia services to a mobile user independently of the access network with which the user is connected (i.e. a circuit-switched or a packet-switched access network). Circuit-switched access network users can thus benefit from new IMS services while continuing to benefit from the services conventionally available on circuit-switched access networks, with those services now being managed by the IMS core network.
- For this purpose, the ICS service relies in particular on triggering a service centralization and continuity application server (SCC-AS) in charge of ensuring continuity of services for various access networks. The SCC-AS server has in particular the function of managing the terminating of each communication passing therethrough by selecting the domain (packet-switched or circuit-switched) to which the communication is to be routed. The functions of the SCC-AS server are described in greater detail in the document 3GPP TS 24.292 entitled “Technical specification group core network and terminals; IP multimedia core network subsystem; centralized services;
stage 3”, Release 10, v10.5.0, September 2001. - Furthermore, the 3GPP standard provides the possibility of a user registering a plurality of addresses of contact with the IMS core network, all linked to the same identifier of that user on the core network (e.g. an SIP address). These addresses of contact may be associated with a plurality of different terminals.
- Although the 3GPP standard provides for the possibility of the SCC-AS server taking account of multiple terminals linked to the same identifier of the user on the core network, the standard does not describe how this might or must be implemented.
- The invention satisfies this need in particular by proposing a management method for managing a communication to a user having an identifier allocated thereto on a voice over IP core network, the method being performed by an application server of the voice over IP core network through which the communication transits. In accordance with the invention, the method comprises a step, performed on receiving the communication, of consulting a database to select a terminal linked to the identifier of the user for the purpose of routing the communication to the terminal, the database associating at least one terminal registered on the voice over IP core network and linked to the identifier of the user with at least one period of activity of the terminal on the voice over IP core network, and the terminal that is selected being the terminal associated in the database with the most recent period of activity.
- Correspondingly, the invention also provides an application server of a voice over IP core network, suitable for managing a communication transiting therethrough and intended for a user having an identifier allocated thereto on the voice over IP core network. In accordance with the invention, the server includes means that are activated on receiving the communication to consult a database in order to select a terminal linked to the identifier of the user for the purpose of routing the communication to the terminal, the database associating at least one terminal registered on the voice over IP core network and linked to the identifier of the user with at least one period of activity of the terminal on the voice over IP core network, and the terminal that is selected being the terminal associated in the database with the most recent period of activity.
- It should be observed that the invention has a preferred but non-limiting application when the voice over IP core network is an IMS core network and the application server is an SCC-AS server of the IMS core network. The invention thus makes it possible to enrich the functions of the SCC-AS server as defined in the 3GPP standard.
- In the meaning of the invention, the term “activity” of a terminal is used to cover any protocol activity of that terminal, i.e. any activity associated with exchanging messages over the voice over IP core network (sending or receiving one or more messages), such as for example messages in compliance with the session initiation protocol (SIP). This may comprise in particular a period of activity associated with setting up a call (e.g. associated with sending or receiving an SIP INVITE message), or exchanging information between two terminals (associated with sending or receiving an SIP OPTIONS message), or exchanging information between a terminal and some other piece of equipment of the network, or indeed registering or unregistering the terminal (associated with sending an SIP REGISTER or UNREGISTER message), etc.
- When in the presence of a plurality of registered terminals linked to the same identifier of a user on the voice over IP core network, the invention thus proposes routing an incoming communication to the most recently active terminal of the user, i.e. to the terminal that is associated in a database maintained by the application server with the period of activity that is the most recent relative to the incoming communication. The invention thus enhances the reachability of the terminal when performing the selection for the purpose of routing the communication.
- In the meaning of the invention, a “communication” intended for a user designates any exchange of data that is to be performed with a terminal of that user, whether in the circuit-switched (CS) domain, or in the packet-switched (PS) domain. The invention makes it possible not only to manage communications of the telephone call type, but also to exchange multimedia data such as, for example: files, photos, multimedia messages, short message service (SMS), etc.
- The invention is also particularly advantageous in that it is performed in the voice over IP core network by the application server through which communications transit in the core network, and consequently it does not require any modification to the source or destination terminals of the communication. Terminal selection is also performed in a manner that is automatic, without requiring any intervention by the terminal originating the communication or by the user to whom the communication is being made.
- Preferably, the database is updated by the application server, periodically or on the application server detecting a period of activity of a terminal linked to the identifier of the user on the voice over IP core network.
- The invention thus makes it possible to have recent and reliable knowledge about the state of activity of a terminal on the voice over IP core network and to adapt communication routing accordingly.
- In a particular implementation of the invention, during the selection step, the terminal linked to the identifier of the user and associated with the most recent period of activity is selected while also verifying a predetermined criterion relating to the nature of the activity of the terminal in that period.
- Thus, in a first variant, the terminal linked to the identifier of the user and associated with the most recent period of activity is selected with reference to a communication of the same kind as the incoming communication that the application server is seeking to route.
- This first variant enables routing to be optimized by taking account of the reachability of the selected terminal relative to the nature of the incoming communication.
- In a second variant, during the selection step, the terminal linked to the identifier of the user that is selected is the terminal associated with the most recent period of activity associated with setting up a communication with another terminal.
- The selection as performed in this way is particularly pertinent when the communication being managed by the method of the invention is an incoming telephone call. However, when other types of incoming communication are managed by the method of the invention, it also makes it possible to give precedence to the terminal on which the user has had activity in real time.
- In other words, in this implementation, a kind of hierarchy is established between the activities of terminals, i.e. certain activities of terminals, such as for example exchanging messages in the context of setting up a call, are considered as having higher priority (or being more pertinent) compared with other activities when selecting a terminal for routing purposes. This makes it possible to optimize routing by taking account of the reachability of the selected terminal given the nature of its past activity, and also relative to the nature of the incoming communication.
- In a variant implementation, the predetermined criterion relates to the type message that was sent or received by the terminal during that period.
- For example, for an IMS core network and an incoming communication of the telephone call type, when the database has two terminals linked to the same identifier, one of the terminals being associated with a period of activity during which an SIP INVITE message was sent and the other terminal being associated with a period of activity during which an SIP OPTIONS message was sent, terminal selection gives precedence to the terminal for which the period of activity corresponds to sending an SIP INVITE message, since that corresponds to setting up a call.
- In a particular implementation of the invention, the management method further comprises a step of routing the communication to the selected terminal.
- In a particular implementation, the various steps of the management method are determined by computer program instructions.
- Consequently, the invention also provides a computer program on a data medium, the program being suitable for being performed by an application server or more generally by a computer, the program including instructions adapted to performing steps of the management method as defined above.
- The program may use any programming language, and may be in the form of source code, object code, or code intermediate between source code and object code, such as in a partially compiled form, or in any other desirable form.
- The invention also provides a computer readable data medium, including instructions of a computer program as mentioned above.
- The data medium may be an entity or device capable of storing the program. For example, the medium may comprise storage means, such as a read only memory (ROM), e.g. a compact disk (CD) ROM, or a microelectronic circuit ROM, or indeed magnetic recording means, e.g. a floppy disk or a hard disk.
- Furthermore, the data medium may be a transmissible medium, such as an electrical or optical signal, that may be conveyed via an electrical or optical cable, by radio, or by other means. The program of the invention may in particular be downloaded from an Internet type network.
- Alternatively, the data medium may 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.
- In another aspect, the invention also provides a database prepared by an application server of a voice over IP core network and associating at least one terminal registered on the voice over IP core network and linked to an identifier of a user on said voice over IP core network with at least one period of activity of the terminal on the voice over IP core network.
- In yet another aspect, the invention provides a voice over IP core network system comprising:
-
- an application server in accordance with the invention; and
- a database in accordance with the invention prepared by the application server and used to select a terminal to which to route a communication transiting via the application server and intended for a user identified on the voice over IP core network.
- In other implementations, it is also possible to envisage that the management method, the application server, the database, and the system of the invention present in combination all or some of the above-specified characteristics.
- Other characteristics and advantages of the present invention appear from the following description made with reference to the accompanying drawings that show an implementation having no limiting character. In the figures:
-
FIG. 1 is a diagrammatic representation of a system, an application server, and a database in accordance with the invention in a particular embodiment; -
FIG. 2 is a diagrammatic representation of the hardware architecture of theFIG. 1 application server in a particular embodiment; -
FIG. 3 shows the main steps performed during the communication management method of the invention, with the method being performed by theFIG. 1 application server; and -
FIG. 4 shows an example of a database in accordance with the invention. -
FIG. 1 shows, in its environment, a system 1 of a voice over IP core network IP-CN in accordance with the invention in a particular embodiment. - In this embodiment, the VoIP core network IP-CN is a core network incorporating IMS architecture and making use of the SIP protocol for the signaling that is exchanged in the core network. The characteristics of IMS architecture and SIP protocol are defined respectively in the 3GPP and IETF standards, and in particular in the documents: 3GPP TS 22.228 “Service requirements for the IP multimedia core network subsystem (stage 1)”; and IETF RFC 3261 “Session initiation protocol”. They are therefore not described in detail herein.
- This assumption concerning the core network is nevertheless not limiting. Thus, the invention is equally applicable to other core network architectures, such as for example an H323 architecture.
- In known manner, the IMS core network IP-CN comprises a plurality of functional entities, including in particular:
-
- a call session control function (CSCF)
entity 2, itself made up of a plurality of servers (not shown inFIG. 1 ) including in particular a serving call session control function (S-CSCF) server in charge of registering terminals on the core network IP-CN, and one or more proxy call session control functions (P-CSCF) servers, which are points of contact for terminals with the core network IP-CN; and - one or more application servers hosting and supplying services, for example a telephony application server (TAS) (not shown) and a service centralization and continuity application server (SCC AS) 3, participating in making an IMS centralized service (ICS) available by the core network IP-CN. The architecture and the functions of an SCC AS server and of the ICS service are described in greater detail in the above-mentioned documents: 3GPP TS 23.292 and 3GPP TS 24.292.
- a call session control function (CSCF)
- In the presently described example, attention is given to managing a communication placed by a user U2 having a terminal T and intended for a user U1 having a plurality of terminals T1, T2, and T3 linked to the same identifier IdSIP1 (e.g. an SIP address) of the user U1 on the core network IP-CN. It is assumed that the user U2 is identified on the IP core network by the identifier IdSIP2.
- Each of the terminals T1, T2, and T3 of the user U1 is associated with a respective address of contact AoC1, AoC2, and AoC3 on the core network IP-CN. The addresses of contact AoC1, AoC2, and AoC3 are all linked to the identifier IdSIP1 of the user U1, as is possible in the 3GPP standard.
- In the presently described example, the terminals T1 and T2 are suitable for communicating via an access network AN1, e.g. via a packet-switched access network such as the universal mobile telecommunication system (UMTS) network; the terminal T3 is suitable for communicating via an access network AN2, e.g. via a circuit-switched access network such as the global system for mobile communication (GSM) network. In similar manner, it is assumed that the user U2 has a single terminal T suitable for communicating over the circuit-switched network AN2.
- Naturally, other access networks (whether circuit-switched or packet-switched) or some other configuration of the access networks of the terminals T1, T2, T3, and T could be envisaged, given the functions of the IMS architecture under consideration. Likewise, the invention applies to other numbers of terminals associated with the user U1.
- In order to be able to benefit from the ICS service made available by the core network IP-CN, the terminals T, T1, T2, and T3 need to register with the core network IP-CN in conventional manner as described in particular in the document 3GPP TS 23.292. The intervention of an enhanced mobile switching server (eMSC) forming the transition between the “circuit” core network and the IMS core network may be required for terminals connected to circuit-switched networks.
- This registration serves in particular to enable the core network IP-CN to associate, in the home subscriber server (HSS) of the core network, the addresses of contact AoC1, AoC2, and AoC3 with the identifier IdSIP1 of the user U1, the address of contact AoC with the identifier IdSIP2 of the user U2, and where appropriate to trigger initial filter criteria (IFC) to enable the terminals to benefit from the ICS service.
- It should be observed that for the terminals T1, T2, and T3, this registration marks the beginning of a potential period of activity in the protocol meaning of the term, i.e. following this registration, the terminals T1, T2, and T3 are in a position to send and/or receive one or more messages in accordance with the SIP protocol, in this example via the core network IP-CN. The sending or reception of a message by a terminal via the core network IP-CN constitutes a period of activity of the terminal in the meaning of the invention.
- The SCC AS
server 3 in this example is an application server of the system 1 in accordance with the invention. It is suitable for acting in accordance with the invention to manage and route a communication for the user U1 as placed by the user U2 so that the communication goes to that one of the terminals of the user U1 that is associated with the most recent period of activity. - For this purpose, in the presently described implementation, the SCC AS
server 3 prepares and keeps up to date a database 4 in accordance with the invention, which database associates each of the terminals of the user U1 that is registered with the core network IP-CN with at least one period of activity of that terminal on the voice over IP core network. This period of activity may in particular be identified in the database 4 by the instant at which the terminal sent or received a message during the period of activity, and possibly by the type of SIP message that was sent or received during that period of activity. -
FIG. 4 shows an example of such a database. In the meaning of the invention, a “database” designates any type of architecture suitable for storing data, such as a table as shown inFIG. 4 . - In this example, the terminals T1, T2, and T3 having respective addresses of contact AoC1, AoC2, and AoC3 that are linked to the identifier IdSIP1 of the user U1 are registered with the core network IP-CN: this is represented by the value “REGISTERED” for the terminal state as given in the fourth column of the database with the heading “STATE”.
- Furthermore, in this example, only the most recent period of activity of each of the terminals T1, T2, and T3 is stored in the database 4. This period of activity is identified herein for each terminal in the third column of the database 4 (headed “LAST SIP MESS”), firstly by the type of SIP message Msg sent or received by the terminal during this period, and secondly by the time t the message was sent or received.
- Thus, in this example:
-
- the most recent period of activity of the terminal T1 is represented by sending or receiving a message M1 at an instant t=x1;
- the most recent period of activity of the terminal T2 is represented by sending or receiving a message M2 at an instant t=x2; and
- the most recent period of activity of the terminal T3 is represented by sending or receiving a message M3 at an instant t=x3.
- For exemplary purposes, it is assumed that M1 is an SIP INVITE message, while M2 and M3 are SIP OPTIONS messages, and that x2<x1<x3. In other words, the most recent period of activity of the period T1 is later than the most recent period of activity of the terminal T2 and earlier than the most recent period of activity of the terminal T3.
- Advantageously, this database 4 is kept up to date by the SCC-
AS server 3 so as to reflect as accurately as possible the most recent periods of activity of the terminals of the user U1. This updating is possible because the SCC-AS server 3 is the anchor point for all of the communications passing via the IMS core network, so it is informed in real time about the periods of activity of the terminals T1, T2, and T3. - In the presently described implementation, this updating of the database 4 is performed firstly by the SCC-
AS server 3 detecting a change of state of a terminal (which change of state is conveyed by the S-CSCF server in known manner, such as, for example: -
- as a result of a new terminal linked to the identifier IdSIP1 being registered, with this being reflected in the database 4 by adding a period of activity associated with this new terminal (i.e. new entry), this period being identified by an SIP REGISTER message and by an instant t corresponding to the instant at which the terminal was registered; or
- as a result of one of the terminals T1, T2, and T3 unregistering, which is reflected in the database 4 by deletion of the corresponding entry or by causing the state in the “STATE” column to become UNREGISTERED.
- The database 4 is also updated in this example on detecting a new period of activity associated with a terminal already included in the database. Since this new period of activity is more recent than the period previously stored in the database for the terminal, it replaces the previously stored period of activity. As a result, the database 4 advantageously reflects only the most recent periods of activity of the terminals.
- In a variant, it is possible to envisage updating periodically, with detected periods of activity being stored, e.g. in a random access memory (RAM) of the application server.
- The SCC-
AS server 3 in this example has the hardware architecture of a computer, as shown diagrammatically inFIG. 2 . In particular, it comprises aprocessor 5, aRAM 6, aROM 7, communication means 8 for communicating over the IMS core network (in particular incorporating means for performing the SIP protocol), together with consultation means 9 for consulting a database 4 in accordance with the invention. - The
ROM 7 of the SCC-AS server 3 constitutes a storage medium in accordance with the invention that is readable by theprocessor 5 and that stores a computer program in accordance with the invention, including instructions for executing steps of a communication management method of the invention as described below with reference toFIG. 3 . -
FIG. 3 is a flow chart showing the main steps of a method of the invention in a particular implementation in which the method is performed by the SCC-AS server 3 in order to manage a communication placed by the terminal T of the user U2 and intended for the user U1. In this example, the communication is a telephone call. - Nevertheless, the invention is not limited to managing telephone calls; it also applies to other types of communication enabling multimedia data to be exchanged, both in the circuit-switched domain and in the packet-switched domain (e.g. SMS, multimedia messaging, etc.). Correspondingly, the invention is not limited to a communication placed by a terminal T, but also applies when the communication comes from some other piece of equipment, e.g. such as a server, etc.
- In order to illustrate these steps, it is assumed that the terminals T1, T2, and T3 of the user U1 are registered with the core network IP-CN, and that the database 4 is up to date concerning the periods of activity of these terminals, and is identical to the example shown in
FIG. 4 . - In accordance with the invention, on receiving a communication (step E10) for the user U1 (i.e. a communication message for the user U1), the SCC-
AS server 3 of the system 1 consults the database 4 using the identifier IdSIP1 allocated to the user U1 (step E20) in order to identify the most recently active terminal associated with the user U1 and registered with the core network IP-CN. - It should be observed that depending on the nature of the terminal T of the user U2 (i.e. whether or not it is suitable for communicating using the SIP protocol in this example), the communication message placed by the terminal T does not necessarily contain the identifier IdSIP1 of the user U1 on the core network IP-CN, but it may contain an identifier of the user U1 on the access network AN2, e.g. such as a telephone number.
- Nevertheless, while this communication message is transiting via the core network IP-CN, the CSCF control entities of the core network replace in conventional manner the identifier of U1 as contained in the message with the identifier IdSIP1 of the user U1 on the core network IP-CN, as stored in the HSS server.
- Thus, on receiving the possibly modified communication message containing the identifier IdSP1 of the user U1, the SCC-
AS server 3 interrogates the database 4 initially in order to determine whether there exists a terminal associated with the identifier IdSIP1 that is also registered with the core network (step E30). - If the database 4 indicates (E30, no) that there is no terminal associated with the identifier IdSIP1 and registered (and thus potentially active), a not available message is sent by the SCC AS
server 3 to the terminal T (step E40) informing it that the communication has failed. - Otherwise (E30, yes), the database 4 is interrogated (step E50) to determine whether a plurality of terminals associated with the identifier IdSIP1 are registered simultaneously.
- In the presently described example, the three terminals T1, T2, and T3 are currently registered with the core network (E50, yes).
- In accordance with the invention, the SCC-
AS server 3 selects the most recently active terminal from among these terminals for the purpose of routing the communication, i.e. it selects the terminal that is associated in the database 4 with the period of activity that is the most recent at the moment the database 4 is interrogated by the SCC-AS server 3 (or in a variant at the moment the SCC-AS server 3 receives or began processing the communication placed by the terminal T). - In the implementation described and shown in
FIG. 3 , it is also assumed that the SCC-AS server 3 selects from the terminals registered and listed in the database 4 a terminal that also satisfies a predetermined criterion relating to the nature of the activity of the terminal during its most recent period of activity. - Adding this constraint seeks to enable the SCC-
AS server 3 to select a terminal corresponding to a message of the same kind as the communication placed by the terminal T of the user U2. - In this example, the communication being set up is a telephone call such that the SCC-
AS server 3 is configured to select the most recently active terminal listed in the database 4 that sent or received an SIP message associated with setting up a call during its most recent period of activity (step E60). - To do this, in step E60, the SCC-
AS server 3 uses the database 4 to analyze the type of message that was exchanged during its most recent period of activity by each of the terminals T1, T2, and T3 as stored in the database 4 and the instant at which the message was exchanged. - In the example shown in
FIG. 4 , only the message M1 is a message associated with setting up a call (M1 is an SIP INVITE message). The SCC-AS server 3 thus selects the terminal T1 in order to route the communication placed by the user U2. - In contrast, if a plurality of terminals are associated with respective call setup messages, then the SCC-
AS server 3 selects the terminal corresponding to the most recent period of activity involving setting up a call. - Furthermore, if only one terminal is registered in the database 4 (E50, no), the communication is routed to that terminal, which terminal corresponds to the terminal having the most recent period of activity (step E70).
- In another implementation of the invention, the SCC-
AS server 3 takes into consideration as a criteria relating to the nature of the activity of the terminal, the sending or receiving during said activity of a message relating to setting up a telephone call, and does so independently of the nature of the communication that has been placed by the terminal T of the user U2, and that the application server is seeking to route. - In another implementation of the invention, the
- SCC-
AS server 3 does not take into consideration any other criterion for selecting the terminal to which to route the communication. In this implementation, and with reference to the example shown inFIG. 4 , it selects the terminal T3 for routing the communication. - The communication is then routed to the selected terminal, i.e. in the example of
FIG. 4 to the terminal T1, in conventional manner (step E80). - It should be observed that in the presently described implementation, the database associates each terminal with the most recent period of activity of that terminal on the IMS core network, and the SCC-
AS server 3 selects the terminal to which the communication is to be routed by analyzing the data available in the table identifying that period of activity (specifically the instant t and the message type Msg). In a variant, the database 4 could be maintained by the SCC-AS server 3 so as to reflect only the most recent period of activity of the most recently active terminal, such that the selection step consists in extracting from the database 4 the only terminal that is listed in the database.
Claims (13)
1. A management method for managing a communication to a user having an identifier allocated thereto on a voice over IP core network, said method being performed by an application server of the voice over IP core network through which said communication transits, said method comprising a process, performed on receiving said communication, of consulting a database to select a terminal linked to the identifier of the user for the purpose of routing said communication to the terminal, said database associating at least one terminal registered on the voice over IP core network and linked to the identifier of the user with at least one period of activity of said terminal on the voice over IP core network, the terminal that is selected being the terminal associated in the database with the most recent period of activity.
2. A management method according to claim 1 , wherein said database is updated by the application server, periodically or on the application server detecting a period of activity of a terminal linked to the identifier of the user on the voice over IP core network.
3. A management method according to claim 1 , wherein during the selection process, the terminal linked to the identifier of the user and associated with the most recent period of activity is selected while also verifying a predetermined criterion relating to the nature of the activity of the terminal in that period.
4. A management method according to claim 3 , wherein, during the selection process, the terminal linked to the identifier of the user that is selected is the terminal associated with the most recent period of activity associated with setting up a communication with another terminal.
5. A management method according to claim 3 , wherein the predetermined criterion relates to the nature of a message sent or received by the terminal during that period.
6. A management method according to claim 1 , further including a process of routing the communication to the selected terminal.
7. A management method according to claim 1 , wherein the voice over IP core network is an IMS core network and the application server is an SCC-AS server as defined by the 3GPP standard.
8. A computer program including instructions for executing steps of the management method of claim 1 when said program is executed by a computer.
9. A non-transitory computer readable storage medium having a computer program stored thereon including instructions for executing the steps of the management method of claim 1 .
10. An application server of a voice over IP core network, suitable for managing a communication transiting therethrough and intended for a user having an identifier allocated thereto on the voice over IP core network, said server including a component configured to be activated on receiving said communication to consult a database in order to select a terminal linked to the identifier of the user for the purpose of routing said communication to the terminal, said database associating at least one terminal registered on the voice over IP core network and linked to the identifier of the user with at least one period of activity of the terminal on the voice over IP core network, the terminal that is selected being the terminal associated in the database with the most recent period of activity.
11. A database maintained by an application server of a voice over IP core network and associating at least one terminal registered on the voice over IP core network and linked to an identifier of a user on said voice over IP core network with at least one period of activity of the terminal on the voice over IP core network.
12. A voice over IP core network system comprising:
an application server according to claim 10 ; and
a database according to claim 11 prepared by said application server and used to select a terminal to which to route a communication transiting via the application server and intended for a user identified on the voice over IP core network.
13. A system according to claim 12 , wherein the voice over IP core network is an IMS core network and the application server is an SCC-AS server as defined by the 3GPP standard.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR1159841 | 2011-10-28 | ||
FR1159841A FR2982107A1 (en) | 2011-10-28 | 2011-10-28 | METHOD FOR MANAGING A COMMUNICATION FOR A USER AND APPLICATION SERVER |
PCT/FR2012/052370 WO2013060967A1 (en) | 2011-10-28 | 2012-10-18 | Method for managing a communication intended for a user, and application server |
Publications (2)
Publication Number | Publication Date |
---|---|
US20140301334A1 true US20140301334A1 (en) | 2014-10-09 |
US10154146B2 US10154146B2 (en) | 2018-12-11 |
Family
ID=47221454
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/354,038 Active US10154146B2 (en) | 2011-10-28 | 2012-10-18 | Method of managing a communication to a user, and an application server |
Country Status (5)
Country | Link |
---|---|
US (1) | US10154146B2 (en) |
EP (1) | EP2772035B1 (en) |
ES (1) | ES2554294T3 (en) |
FR (1) | FR2982107A1 (en) |
WO (1) | WO2013060967A1 (en) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150012757A1 (en) * | 2010-12-22 | 2015-01-08 | May Patents Ltd. | System and method for routing-based internet security |
US20160105530A1 (en) * | 2013-08-28 | 2016-04-14 | Hola Networks Ltd. | System and Method for Improving Internet Communication by Using Intermediate Nodes |
US10069936B2 (en) | 2009-10-08 | 2018-09-04 | Hola Newco Ltd. | System providing faster and more efficient data communication |
US10387316B2 (en) | 2009-05-18 | 2019-08-20 | Web Spark Ltd. | Method for increasing cache size |
US10616294B2 (en) | 2015-05-14 | 2020-04-07 | Web Spark Ltd. | System and method for streaming content from multiple servers |
US20200367155A1 (en) * | 2018-02-03 | 2020-11-19 | Nokia Technologies Oy | Application based routing of data packets in multi-access communication networks |
US10880266B1 (en) | 2017-08-28 | 2020-12-29 | Luminati Networks Ltd. | System and method for improving content fetching by selecting tunnel devices |
US10902080B2 (en) | 2019-02-25 | 2021-01-26 | Luminati Networks Ltd. | System and method for URL fetching retry mechanism |
US11190374B2 (en) | 2017-08-28 | 2021-11-30 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11411922B2 (en) | 2019-04-02 | 2022-08-09 | Bright Data Ltd. | System and method for managing non-direct URL fetching service |
US12260364B2 (en) | 2015-04-24 | 2025-03-25 | United Parcel Service Of America, Inc. | Location-based pick up and delivery services |
US12277189B2 (en) | 2023-01-23 | 2025-04-15 | Bright Data Ltd. | System and method for URL fetching retry mechanism |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4551546B2 (en) * | 2000-09-28 | 2010-09-29 | キヤノン株式会社 | Server device of network system and control method thereof |
US20080075064A1 (en) * | 2006-08-30 | 2008-03-27 | Microsoft Corporation | Device to PC authentication for real time communications |
US8432923B2 (en) * | 2008-12-18 | 2013-04-30 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for providing inter-carrier IP-based connections using a common telephone number mapping architecture |
US8238538B2 (en) * | 2009-05-28 | 2012-08-07 | Comcast Cable Communications, Llc | Stateful home phone service |
-
2011
- 2011-10-28 FR FR1159841A patent/FR2982107A1/en not_active Withdrawn
-
2012
- 2012-10-18 ES ES12790593.3T patent/ES2554294T3/en active Active
- 2012-10-18 WO PCT/FR2012/052370 patent/WO2013060967A1/en active Application Filing
- 2012-10-18 EP EP12790593.3A patent/EP2772035B1/en active Active
- 2012-10-18 US US14/354,038 patent/US10154146B2/en active Active
Cited By (210)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10387316B2 (en) | 2009-05-18 | 2019-08-20 | Web Spark Ltd. | Method for increasing cache size |
US11902351B2 (en) | 2009-10-08 | 2024-02-13 | Bright Data Ltd. | System providing faster and more efficient data communication |
US12003568B2 (en) | 2009-10-08 | 2024-06-04 | Bright Data Ltd. | System providing faster and more efficient data communication |
US12177285B2 (en) | 2009-10-08 | 2024-12-24 | Bright Data Ltd. | System providing faster and more efficient data communication |
US10069936B2 (en) | 2009-10-08 | 2018-09-04 | Hola Newco Ltd. | System providing faster and more efficient data communication |
US10225374B2 (en) | 2009-10-08 | 2019-03-05 | Hola Newco Ltd. | System providing faster and more efficient data communication |
US10257319B2 (en) | 2009-10-08 | 2019-04-09 | Web Spark Ltd. | System providing faster and more efficient data communication |
US12107911B2 (en) | 2009-10-08 | 2024-10-01 | Bright Data Ltd. | System providing faster and more efficient data communication |
US10313484B2 (en) | 2009-10-08 | 2019-06-04 | Web Spark Ltd. | System providing faster and more efficient data communication |
US12101372B2 (en) | 2009-10-08 | 2024-09-24 | Bright Data Ltd. | System providing faster and more efficient data communication |
US12095840B2 (en) | 2009-10-08 | 2024-09-17 | Bright Data Ltd. | System providing faster and more efficient data communication |
US12095841B2 (en) | 2009-10-08 | 2024-09-17 | Bright Data Ltd. | System providing faster and more efficient data communication |
US10469628B2 (en) | 2009-10-08 | 2019-11-05 | Web Spark Ltd. | System providing faster and more efficient data communication |
US12095843B2 (en) | 2009-10-08 | 2024-09-17 | Bright Data Ltd. | System providing faster and more efficient data communication |
US10484510B2 (en) | 2009-10-08 | 2019-11-19 | Web Spark Ltd. | System providing faster and more efficient data communication |
US10484511B2 (en) | 2009-10-08 | 2019-11-19 | Web Spark Ltd. | System providing faster and more efficient data communication |
US10491712B2 (en) | 2009-10-08 | 2019-11-26 | Web Spark Ltd. | System providing faster and more efficient data communication |
US10491713B2 (en) | 2009-10-08 | 2019-11-26 | Web Spark Ltd. | System providing faster and more efficient data communication |
US10523788B2 (en) | 2009-10-08 | 2019-12-31 | Web Sparks Ltd. | System providing faster and more efficient data communication |
US10582014B2 (en) | 2009-10-08 | 2020-03-03 | Luminati Networks Ltd. | System providing faster and more efficient data communication |
US10582013B2 (en) | 2009-10-08 | 2020-03-03 | Luminati Networks Ltd. | System providing faster and more efficient data communication |
US10616375B2 (en) | 2009-10-08 | 2020-04-07 | Luminati Networks Ltd. | System providing faster and more efficient data communication |
US12081612B2 (en) | 2009-10-08 | 2024-09-03 | Bright Data Ltd. | System providing faster and more efficient data communication |
US10637968B2 (en) | 2009-10-08 | 2020-04-28 | Luminati Networks Ltd. | System providing faster and more efficient data communication |
US12021914B2 (en) | 2009-10-08 | 2024-06-25 | Bright Data Ltd. | System providing faster and more efficient data communication |
US12021916B2 (en) | 2009-10-08 | 2024-06-25 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11457058B2 (en) | 2009-10-08 | 2022-09-27 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11539779B2 (en) | 2009-10-08 | 2022-12-27 | Bright Data Ltd. | System providing faster and more efficient data communication |
US12003566B2 (en) | 2009-10-08 | 2024-06-04 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11412025B2 (en) | 2009-10-08 | 2022-08-09 | Bright Data Ltd. | System providing faster and more efficient data communication |
US10785347B1 (en) | 2009-10-08 | 2020-09-22 | Luminati Networks Ltd. | System providing faster and more efficient data communication |
US10805429B1 (en) | 2009-10-08 | 2020-10-13 | Luminati Networks Ltd. | System providing faster and more efficient data communication |
US12003567B2 (en) | 2009-10-08 | 2024-06-04 | Bright Data Ltd. | System providing faster and more efficient data communication |
US12003569B2 (en) | 2009-10-08 | 2024-06-04 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11962636B2 (en) | 2009-10-08 | 2024-04-16 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11956299B2 (en) | 2009-10-08 | 2024-04-09 | Bright Data Ltd. | System providing faster and more efficient data communication |
US10931792B2 (en) | 2009-10-08 | 2021-02-23 | Luminati Networks Ltd. | System providing faster and more efficient data communication |
US10958768B1 (en) | 2009-10-08 | 2021-03-23 | Luminati Networks Ltd. | System providing faster and more efficient data communication |
US11949729B2 (en) | 2009-10-08 | 2024-04-02 | Bright Data Ltd. | System providing faster and more efficient data communication |
US12200038B2 (en) | 2009-10-08 | 2025-01-14 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11916993B2 (en) | 2009-10-08 | 2024-02-27 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11206317B2 (en) | 2009-10-08 | 2021-12-21 | Bright Data Ltd. | System providing faster and more efficient data communication |
US10986216B2 (en) | 2009-10-08 | 2021-04-20 | Luminati Networks Ltd. | System providing faster and more efficient data communication |
US11888921B2 (en) | 2009-10-08 | 2024-01-30 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11611607B2 (en) | 2009-10-08 | 2023-03-21 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11616826B2 (en) | 2009-10-08 | 2023-03-28 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11876853B2 (en) | 2009-10-08 | 2024-01-16 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11838119B2 (en) | 2009-10-08 | 2023-12-05 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11038989B2 (en) | 2009-10-08 | 2021-06-15 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11044344B2 (en) | 2009-10-08 | 2021-06-22 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11044345B2 (en) | 2009-10-08 | 2021-06-22 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11044346B2 (en) | 2009-10-08 | 2021-06-22 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11044341B2 (en) | 2009-10-08 | 2021-06-22 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11044342B2 (en) | 2009-10-08 | 2021-06-22 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11050852B2 (en) | 2009-10-08 | 2021-06-29 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11811848B2 (en) | 2009-10-08 | 2023-11-07 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11089135B2 (en) | 2009-10-08 | 2021-08-10 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11811849B2 (en) | 2009-10-08 | 2023-11-07 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11811850B2 (en) | 2009-10-08 | 2023-11-07 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11128738B2 (en) | 2009-10-08 | 2021-09-21 | Bright Data Ltd. | Fetching content from multiple web servers using an intermediate client device |
US11770435B2 (en) | 2009-10-08 | 2023-09-26 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11178258B2 (en) | 2009-10-08 | 2021-11-16 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11190622B2 (en) | 2009-10-08 | 2021-11-30 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11700295B2 (en) | 2009-10-08 | 2023-07-11 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11888922B2 (en) | 2009-10-08 | 2024-01-30 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11228666B2 (en) | 2009-10-08 | 2022-01-18 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11233880B2 (en) | 2009-10-08 | 2022-01-25 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11233879B2 (en) | 2009-10-08 | 2022-01-25 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11659017B2 (en) | 2009-10-08 | 2023-05-23 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11233881B2 (en) | 2009-10-08 | 2022-01-25 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11671476B2 (en) | 2009-10-08 | 2023-06-06 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11297167B2 (en) | 2009-10-08 | 2022-04-05 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11303734B2 (en) | 2009-10-08 | 2022-04-12 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11659018B2 (en) | 2009-10-08 | 2023-05-23 | Bright Data Ltd. | System providing faster and more efficient data communication |
US11303612B2 (en) | 2010-12-22 | 2022-04-12 | May Patents Ltd. | System and method for routing-based internet security |
US20150012757A1 (en) * | 2010-12-22 | 2015-01-08 | May Patents Ltd. | System and method for routing-based internet security |
US11876785B2 (en) | 2010-12-22 | 2024-01-16 | May Patents Ltd. | System and method for routing-based internet security |
US10652214B2 (en) | 2010-12-22 | 2020-05-12 | May Patents Ltd. | System and method for routing-based internet security |
US9762547B2 (en) * | 2010-12-22 | 2017-09-12 | May Patents Ltd. | System and method for routing-based internet security |
US9634995B2 (en) | 2010-12-22 | 2017-04-25 | Mat Patents Ltd. | System and method for routing-based internet security |
US11689639B2 (en) | 2013-08-28 | 2023-06-27 | Bright Data Ltd. | System and method for improving Internet communication by using intermediate nodes |
US10469615B2 (en) | 2013-08-28 | 2019-11-05 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US12231519B2 (en) | 2013-08-28 | 2025-02-18 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11388257B2 (en) | 2013-08-28 | 2022-07-12 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US20160105530A1 (en) * | 2013-08-28 | 2016-04-14 | Hola Networks Ltd. | System and Method for Improving Internet Communication by Using Intermediate Nodes |
US12200084B2 (en) | 2013-08-28 | 2025-01-14 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11451640B2 (en) | 2013-08-28 | 2022-09-20 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11349953B2 (en) | 2013-08-28 | 2022-05-31 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11336746B2 (en) | 2013-08-28 | 2022-05-17 | Bright Data Ltd. | System and method for improving Internet communication by using intermediate nodes |
US12200083B2 (en) | 2013-08-28 | 2025-01-14 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11575771B2 (en) | 2013-08-28 | 2023-02-07 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11588920B2 (en) | 2013-08-28 | 2023-02-21 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11595496B2 (en) | 2013-08-28 | 2023-02-28 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US9742866B2 (en) * | 2013-08-28 | 2017-08-22 | Hola Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US11595497B2 (en) | 2013-08-28 | 2023-02-28 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11336745B2 (en) | 2013-08-28 | 2022-05-17 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11316950B2 (en) | 2013-08-28 | 2022-04-26 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11632439B2 (en) | 2013-08-28 | 2023-04-18 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12166843B2 (en) | 2013-08-28 | 2024-12-10 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11310341B2 (en) | 2013-08-28 | 2022-04-19 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11303724B2 (en) | 2013-08-28 | 2022-04-12 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11272034B2 (en) | 2013-08-28 | 2022-03-08 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11677856B2 (en) | 2013-08-28 | 2023-06-13 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12143460B2 (en) | 2013-08-28 | 2024-11-12 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11233872B2 (en) | 2013-08-28 | 2022-01-25 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12143462B2 (en) | 2013-08-28 | 2024-11-12 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12143461B2 (en) | 2013-08-28 | 2024-11-12 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US10277711B2 (en) | 2013-08-28 | 2019-04-30 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US11729297B2 (en) | 2013-08-28 | 2023-08-15 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US10440146B2 (en) | 2013-08-28 | 2019-10-08 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US10447809B2 (en) | 2013-08-28 | 2019-10-15 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US10469614B2 (en) | 2013-08-28 | 2019-11-05 | Luminati Networks Ltd. | System and method for improving Internet communication by using intermediate nodes |
US11758018B2 (en) | 2013-08-28 | 2023-09-12 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11412066B2 (en) | 2013-08-28 | 2022-08-09 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11178250B2 (en) | 2013-08-28 | 2021-11-16 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12088684B2 (en) | 2013-08-28 | 2024-09-10 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11799985B2 (en) | 2013-08-28 | 2023-10-24 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12069150B2 (en) | 2013-08-28 | 2024-08-20 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11102326B2 (en) | 2013-08-28 | 2021-08-24 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12069148B2 (en) | 2013-08-28 | 2024-08-20 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11838386B2 (en) | 2013-08-28 | 2023-12-05 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11838388B2 (en) | 2013-08-28 | 2023-12-05 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11012530B2 (en) | 2013-08-28 | 2021-05-18 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12021944B2 (en) | 2013-08-28 | 2024-06-25 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11870874B2 (en) | 2013-08-28 | 2024-01-09 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12021946B2 (en) | 2013-08-28 | 2024-06-25 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11012529B2 (en) | 2013-08-28 | 2021-05-18 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US11005967B2 (en) | 2013-08-28 | 2021-05-11 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US10652358B2 (en) | 2013-08-28 | 2020-05-12 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US12021945B2 (en) | 2013-08-28 | 2024-06-25 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US10999402B2 (en) | 2013-08-28 | 2021-05-04 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US10986208B2 (en) | 2013-08-28 | 2021-04-20 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US10652357B2 (en) | 2013-08-28 | 2020-05-12 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US11902400B2 (en) | 2013-08-28 | 2024-02-13 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12010196B2 (en) | 2013-08-28 | 2024-06-11 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US10659562B2 (en) | 2013-08-28 | 2020-05-19 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US10721325B2 (en) | 2013-08-28 | 2020-07-21 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US12003605B2 (en) | 2013-08-28 | 2024-06-04 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US10979533B2 (en) | 2013-08-28 | 2021-04-13 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US11924307B2 (en) | 2013-08-28 | 2024-03-05 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11924306B2 (en) | 2013-08-28 | 2024-03-05 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11949756B2 (en) | 2013-08-28 | 2024-04-02 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11985212B2 (en) | 2013-08-28 | 2024-05-14 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11949755B2 (en) | 2013-08-28 | 2024-04-02 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US11985210B2 (en) | 2013-08-28 | 2024-05-14 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US10924580B2 (en) | 2013-08-28 | 2021-02-16 | Luminati Networks Ltd. | System and method for improving internet communication by using intermediate nodes |
US11979475B2 (en) | 2013-08-28 | 2024-05-07 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12260364B2 (en) | 2015-04-24 | 2025-03-25 | United Parcel Service Of America, Inc. | Location-based pick up and delivery services |
US12003562B2 (en) | 2015-05-14 | 2024-06-04 | Bright Data Ltd. | System and method for streaming content from multiple servers |
US11757961B2 (en) | 2015-05-14 | 2023-09-12 | Bright Data Ltd. | System and method for streaming content from multiple servers |
US11770429B2 (en) | 2015-05-14 | 2023-09-26 | Bright Data Ltd. | System and method for streaming content from multiple servers |
US12088651B2 (en) | 2015-05-14 | 2024-09-10 | Bright Data Ltd. | System and method for streaming content from multiple servers |
US10616294B2 (en) | 2015-05-14 | 2020-04-07 | Web Spark Ltd. | System and method for streaming content from multiple servers |
US11057446B2 (en) | 2015-05-14 | 2021-07-06 | Bright Data Ltd. | System and method for streaming content from multiple servers |
US11888639B2 (en) | 2017-08-28 | 2024-01-30 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11729012B2 (en) | 2017-08-28 | 2023-08-15 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US12261712B2 (en) | 2017-08-28 | 2025-03-25 | Bright Data Ltd. | Managing and selecting proxy devices by multiple servers |
US10985934B2 (en) | 2017-08-28 | 2021-04-20 | Luminati Networks Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11962430B2 (en) | 2017-08-28 | 2024-04-16 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US12250089B2 (en) | 2017-08-28 | 2025-03-11 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11902044B2 (en) | 2017-08-28 | 2024-02-13 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US12250090B2 (en) | 2017-08-28 | 2025-03-11 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11888638B2 (en) | 2017-08-28 | 2024-01-30 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US12231253B2 (en) | 2017-08-28 | 2025-02-18 | Bright Data Ltd. | Software development kit (SDK) for selecting and implementing client devices as proxies |
US11876612B2 (en) | 2017-08-28 | 2024-01-16 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11863339B2 (en) | 2017-08-28 | 2024-01-02 | Bright Data Ltd. | System and method for monitoring status of intermediate devices |
US12034559B2 (en) | 2017-08-28 | 2024-07-09 | Bright Data Ltd. | System and method for selecting and using a proxy device |
US12040910B2 (en) | 2017-08-28 | 2024-07-16 | Bright Data Ltd. | Content fetching by mobile device selected based on battery changing level |
US12047191B2 (en) | 2017-08-28 | 2024-07-23 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US12218777B2 (en) | 2017-08-28 | 2025-02-04 | Bright Data Ltd. | Selecting a proxy device based on communication property |
US12057958B2 (en) | 2017-08-28 | 2024-08-06 | Bright Data Ltd. | System and method for improving content fetching by using an appliance as a proxy device |
US10880266B1 (en) | 2017-08-28 | 2020-12-29 | Luminati Networks Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11115230B2 (en) | 2017-08-28 | 2021-09-07 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US12218776B2 (en) | 2017-08-28 | 2025-02-04 | Bright Data Ltd. | Content fetching by client device selected based on hardware feature |
US11424946B2 (en) | 2017-08-28 | 2022-08-23 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11956094B2 (en) | 2017-08-28 | 2024-04-09 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11979249B2 (en) | 2017-08-28 | 2024-05-07 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11764987B2 (en) | 2017-08-28 | 2023-09-19 | Bright Data Ltd. | System and method for monitoring proxy devices and selecting therefrom |
US11979250B2 (en) | 2017-08-28 | 2024-05-07 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11757674B2 (en) | 2017-08-28 | 2023-09-12 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11729013B2 (en) | 2017-08-28 | 2023-08-15 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11909547B2 (en) | 2017-08-28 | 2024-02-20 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US12137008B2 (en) | 2017-08-28 | 2024-11-05 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11711233B2 (en) | 2017-08-28 | 2023-07-25 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11190374B2 (en) | 2017-08-28 | 2021-11-30 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11558215B2 (en) | 2017-08-28 | 2023-01-17 | Bright Data Ltd. | System and method for content fetching using a selected intermediary device and multiple servers |
US12192026B2 (en) | 2017-08-28 | 2025-01-07 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US12149374B2 (en) | 2017-08-28 | 2024-11-19 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US12184437B2 (en) | 2017-08-28 | 2024-12-31 | Bright Data Ltd. | System and method for improving content fetching by selecting tunnel devices |
US11902890B2 (en) * | 2018-02-03 | 2024-02-13 | Nokia Technologies Oy | Application based routing of data packets in multi-access communication networks |
US12185237B2 (en) | 2018-02-03 | 2024-12-31 | Nokia Technologies Oy | Application based routing of data packets in multi-access communication networks |
US20200367155A1 (en) * | 2018-02-03 | 2020-11-19 | Nokia Technologies Oy | Application based routing of data packets in multi-access communication networks |
US10963531B2 (en) | 2019-02-25 | 2021-03-30 | Luminati Networks Ltd. | System and method for URL fetching retry mechanism |
US12147490B2 (en) | 2019-02-25 | 2024-11-19 | Bright Data Ltd. | System and method for URL fetching retry mechanism |
US11593446B2 (en) | 2019-02-25 | 2023-02-28 | Bright Data Ltd. | System and method for URL fetching retry mechanism |
US11657110B2 (en) | 2019-02-25 | 2023-05-23 | Bright Data Ltd. | System and method for URL fetching retry mechanism |
US11675866B2 (en) | 2019-02-25 | 2023-06-13 | Bright Data Ltd. | System and method for URL fetching retry mechanism |
US12056202B2 (en) | 2019-02-25 | 2024-08-06 | Bright Data Ltd. | System and method for URL fetching retry mechanism |
US12229210B2 (en) | 2019-02-25 | 2025-02-18 | Bright Data Ltd. | System and method for URL fetching retry mechanism |
US10902080B2 (en) | 2019-02-25 | 2021-01-26 | Luminati Networks Ltd. | System and method for URL fetching retry mechanism |
US11411922B2 (en) | 2019-04-02 | 2022-08-09 | Bright Data Ltd. | System and method for managing non-direct URL fetching service |
US12069029B2 (en) | 2019-04-02 | 2024-08-20 | Bright Data Ltd. | System and method for managing non-direct URL fetching service |
US12010101B2 (en) | 2019-04-02 | 2024-06-11 | Bright Data Ltd. | System and method for managing non-direct URL fetching service |
US11902253B2 (en) | 2019-04-02 | 2024-02-13 | Bright Data Ltd. | System and method for managing non-direct URL fetching service |
US11418490B2 (en) | 2019-04-02 | 2022-08-16 | Bright Data Ltd. | System and method for managing non-direct URL fetching service |
US12277188B2 (en) | 2022-01-10 | 2025-04-15 | Bright Data Ltd. | System and method for URL fetching retry mechanism |
US12277187B2 (en) | 2022-01-10 | 2025-04-15 | Bright Data Ltd. | System and method for URL fetching retry mechanism |
US12278878B2 (en) | 2022-04-10 | 2025-04-15 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
US12277189B2 (en) | 2023-01-23 | 2025-04-15 | Bright Data Ltd. | System and method for URL fetching retry mechanism |
US12278880B2 (en) | 2023-03-11 | 2025-04-15 | Bright Data Ltd. | System and method for improving internet communication by using intermediate nodes |
Also Published As
Publication number | Publication date |
---|---|
WO2013060967A1 (en) | 2013-05-02 |
US10154146B2 (en) | 2018-12-11 |
ES2554294T3 (en) | 2015-12-17 |
EP2772035B1 (en) | 2015-08-26 |
FR2982107A1 (en) | 2013-05-03 |
EP2772035A1 (en) | 2014-09-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10154146B2 (en) | Method of managing a communication to a user, and an application server | |
US9185139B2 (en) | Location based routing | |
JP4856241B2 (en) | Number portability for IMS networks | |
US9854005B2 (en) | Methods and apparatus for providing network based services to non-registering endpoints | |
US9692793B2 (en) | Communication session allocation | |
CA2680069C (en) | System and method for indicating circuit switched access at ims registration | |
CN101599924B (en) | Communication system | |
US11115441B2 (en) | Method and server for selecting an entry server of an IMS communication network | |
CN103703737A (en) | Methods and apparatus for supporting the implementation of ims service continuity | |
CN105282730B (en) | Terminal communications status acquisition methods and system and application server in IMS network | |
CN103975566A (en) | Service domain selection service indicator | |
CN102883302A (en) | Migration and activation of services in a network | |
CN101433050A (en) | Method for registering multi-contact device | |
US9021300B2 (en) | Method of changing over from a primary HSS to a backup HSS in an IP network | |
CN101188802A (en) | A realization method and system for call transfer and forward class | |
US10212193B2 (en) | Service support for suspended and inactive subscribers | |
CN105306758A (en) | Method for transmitting enterprise network identifier when call is established, IBCF and IMS | |
JP2011049687A (en) | Communication network system, sip signal relay method therefor and sip application server | |
KR100807863B1 (en) | Service provisioning in a communication system | |
CN101222478A (en) | Method, system and device for implementing call establishment | |
KR20070036847A (en) | Method of Provisioning Representative Number Service in 3BPPI IMS-based Network | |
CN105830412B (en) | Session initiation handling | |
EP4231617A1 (en) | Method for managing and/or signaling at least one voip call and a communication system | |
KR101653323B1 (en) | System and Method for call processing | |
US8320896B1 (en) | Unified communication access system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ORANGE, FRANCE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LABRANCHE, MIGUEL;TOSSOU, BRUNO;KANOUTE, MBEMBA;REEL/FRAME:033160/0564 Effective date: 20140515 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |