Abstract: ABSTRACT Multimedia subsystem, IMS, containing a set of call session control function elements, CSCF suitable for sending a signaling message (m) between a first communication client (T) connected to said multimedia subsystem and at least one second communication client, where this second communication client may be connected to said multimedia subsystem or remote and accessible through an interrogating functional element, l-CSCF, and routing methods used to determine a path for the transmission of the signaling message, based on a logical address contained in the signaling message. The multimedia subsystem, IMS, is characterized in that the routing methods implement a distributed hashing table. Figure to be published: 4
IMS architecture using a distributed tiashing table
The invention concerns communication networks and, more specifically, IP Multimedia Subsystems (IMS) as standardized by the 3GPP and the ETSI Tispan.
The IMS architecture is specified by the document TS 23.228 of the SGPP'T'^, entitled "IP Multimedia Subsystem (IMS); Stage 2 (Release 7)'The objective of the IMS architecture is to provide a convergence solution between the fixed and mobile infrastructures of the communication networks. This common infrastructure also allows the deployment of known telecommunication services (call transfer, billing, video-conference, efc] or services yet fo come.
Figure 1 shows a simplified IMS architecture. It should be noted that this architecture is functional: the same functional element may therefore be distributed over several network devices and, vice verso, the same network device may carry out several IMS architecture functions.
A multimedia subsystem IMS consists mainly of three CSCF (Call Session Control Function) functions:
- The P-CSCF (Proxy CSCF) is the contact point of the communication terminals (or clients) T in the IMS communication network. One of its roles is fo authenticate the terminal T and, if necessary, inspect the signaling messages coming from this terminal.
- The S-CSCF (Sen/ing CSCF) provides the interface between the application servers AS, and is used to route signaling
messages within the IMS communication network, in collaboration with the Home Subscriber Server HSS, coming from or intended for a client connected to this subsystem. - The 1-CSCF (Interrogating CSCF) is used to interface with other IMS networks and to route signaling messages from one subsystem to another.
When a communication terminal registers with the IMS communication network, it sends a registration signaling message to an S-CSCFI functional element through the P-CSCFl functional element to which it is attached.
This signaling message allows the S-CSCFl element to add information within the HSSl subscriber server, connecting the logical address of the user of terminal T (in other words the subscriber to the IMS network) with the identifier of the S-CSCFl element.
An SLF (Subscription Locator Function) functional element is also affected and memorizes the association between the logical address of the user of terminal T and the HSSl subscriber server which possesses its information.
Finally, the S-CSCFl element retains the association between the logical address and the physical address of terminal T.
The S-CSCFl functional element is also connected to an application server AS which is used to provide subscribers with different telecommunication services: billing, call waiting, re-directing of calls, announcements, audio and/or video conference, etc. The S-CSCFl functional element is therefore able to analyze the signaling messages in order to contact one or more application servers AS depending on the content.
For an incoming call Intended for the client T, the SLF, HSSl and S-CSCFl elements are used as a means for associating the logical address contained in the Incoming signaling message and the physical address of the client T.
As specified by the 3GPP {y^ Generation Partnership Project) and ETSI (European Telecommunications Sfandards \nsi\Me] standardization bodies, the communication protocol used for the transmission of signaling messages is SIP (Session Initiation Proioco}). This protocol is specified in the RFC 3261 of the IETF (Internet Engineering Task Force) and extended upon by subsequent RFCs.
The registration signaling message is therefore normally a SIP "REGISTER" message, and the invitation signaling message is a SIP "INVITE' message.
1
With the deployment of IMS architectures, the applicant expects an explosion in logical addresses and terminals likely to be connected. In fact, it will become possible to connect a large number of terminals for the same subscriber (computer, fixed line telephone, mobile telephone, personal assistant, television, etc.). It will also be possible to connect devices which are currently usually disconnected from communication networks (household appliances, etc.) in order to provide new services to users.
The subscriber server HSS and above all the subscription location element SLF will then increase considerably in size. They will become bottleneck nodes within the IMS architecture: as they increase in size, they will become more difficult to manage and their access times will also increase, at the expense of the general system performance.
One aim of the invention is io resolve this problem by proposing a distributed architecture.
A distributed approach has already been proposed by the article "Using an External DHT as a SIP Location Service" by Kundan Singh and Henning Schul^rinne, or by the article Teer-fo-peer tnfernef Te/ephony using SIP" by the same authors.
The patent request WO2006/068365 presents a similar approach.
This approach is illustrated in figure 2.
The terminals {or clients) Tl, T2, T3 are connected to a Distributed Hashing Table, or DHT. This distributed hashing table plays the role of SIP registrar in a traditional SIP architecture: the associations between logical subscriber addresses and physical terminal addresses are memorized in this distributed hashing table.
Each of the terminals Tl, T2, T3 possesses a part of this hashing table. Using the mechanisms of the distributed hashing table, a terminal con obtain a physical address of a terminal based on the logical address of the subscriber it wishes to call.
As the registrar is distributed over multiple terminals, there is no longer congestion within a central subscriber server as in the IMS architecture.
However, this approach is not compatible with the IMS architecture, as specified by the 3GPP and ETSI TISPAN standards.
In fact, the terminals must be modified: they do not interact with a P-CSCF functional element through a standardized interface, but must implement a distributed hashing table DHT and implement a specific protocol.
Another state of the art is provided by the Skype Internet telephony product. The principle is mainly the same but the protocol used Is a proprietary protocol and not the SIP protocol.
Since this is a proprietary solution, the terminals must include a module provided by the Skype company, and as previously, they do not interface with a P-CSCF functional element of the (MS architecture.
It is generally accepted that the distributed approach, based on the intelligence of the terminals, and the IMS approach, based on the location of the intelligence in the communication network, are antinomic. For an example, see the participative encyclopedia "Wikipedia" at the address: http://fr.wikipedia.org/wiki/P2P
The aim of this invention is to adopt the principle of a distributed architecture to implement the association between logical addresses and physical addresses, but remaining compatible with the IMS architecture. In particular, one of the aims of the invention is io be transparent with regard to the communication terminals.
To do this, the first aim of the invention is a multimedia subsystem, IMS, containing a set of call session control function elements, CSCF, suitable for sending a signaling message between a first communication client connected to said multimedia subsystem and at least one second communication client. The second communication client may be connected to the multimedia subsystem or remote and accessible through an interrogating functional element, 1-CSCF. The multimedia subsystem also contains routing methods used to determine a path for the transmission of the
signaWng message, based on a logical address contained in the signaling message. The multimedia subsystem is characterized in that these routing methods implement a distributed hashing table.
According to a first execution method of the invention, the routing methods contain a subscriber selection functional element, SLF, used io determine the subscriber server HSS associated with the logical address and implemented by a distributed hashing table.
According to a second execution method, the multimedia subsystem, IMS, contains multiple domains, each containing a set of call session control function elements, CSCF. The routing methods contain a federating functional element used to determine one of these domains based on the logical address (contained in the signaling message), and are implemented by a distributed hashing table.
According to an implementation of this execution method of the invention, the serving functional elements, S-CSCF, of at least some of the domains form the distributed hashing table nodes.
At least one domain can be planned so that signaling messages from said first communication cWenf connected fo this domain are sent to the interrogating functional element, l-CSCF, of the domain concerned. This interrogating functional element is then itself intended fo interrogate the federating functional element in order io determine the path for the signaling messages.
The interrogating functional element can for example implement the functions of a THIG gateway.
The interrogating functional element, l-CSCF, can also be intended, on receipt of a signaling message from the first
communication client, to determine whether the recipient communication client determined by ihe logical address contained in the signaling message is connected to one of these domains, and if not, to send the signaling message outside the multimedia subsystem without interrogating the federating functional element.
The interrogating functional elements, l-CSCF, can on the other hand be intended, on receipt of a signaling message from the first communication client, to systematically interrogate the federating functional element (FF) and, in the absence of a response from this element determining a path, to send the signaling message outside the multimedia subsystem.
The interface between the interrogating functional elements of the domains and the federating functional element can be a Dx interface, implementing the Diameter protocol.
This interface may contain an initial function used to insert an association between the logical address and the domain, and a second function used to determine the domain corresponding to a given logical address.
The logical addresses con contain on identifier corresponding to the multimedia subsystem.
The second aim of the invention is a communication network containing at least one multimedia subsystem, IMS, as described previously.
The third aim of the invention is a federating functional element for a multimedia subsystem, IMS. The multimedia subsystem contains multiple domains, each containing a set of call session control function elements, CSCF. According to this aim of the invention, the federating functional element contains means to determine a domain
based on a logical address contained in a signaling message, these means implementing a distributed hashing table.
The serving functional elements, S-CSCF, of at least some of these domains can form nodes of the distributed hashing table.
The federating functional element may hove a Dx interface implementing the Diameter protocol.
This interface may contain an initial function used to insert an association between the logical address and domain, and a second function used to determine the domain corresponding to a given logical address.
The fourth aim of the invention is a method for sending a signaling message through a multimedia subsystem, IMS, containing a set of coil session control function elements, CSCF, between a first communication client, connected to this multimedia subsystem, and a second communication client which may be connected to the multimedia subsystem or remote and accessible through an Interrogating functional element l-CSCF.
The method includes a stage for the determination of a path for sending the signaling message, based on a logical address contained in this signaling message.
The method is characterized in that this stage implements a distributed hashing table.
According to a first execution method, the method contains a stage for the determination of a subscriber server HSS associated with the logical address; this determination is carried out by a subscriber selection functional element, SLF, implemented by a distributed hashing table.
According to a second execution method, the multimedia subsystem contains multiple domains, each containing a set of call session control function elements, CSCF.
The method contains a stage for the determination of a domain among these multiple domains, based on the logical address; the determination ts carried out by a federating functional element implemented by a distributed hashing table.
According to an implementation of this execution method, the serving functional elements, S-CSCF, of at least some of the domains form the nodes of the distributed hashing table.
Furthermore, at least one domain can be planned so that the signaling messages from a communication client connected to this domain are sent to the interrogating functional element, I-CSCF, of the domain. The interrogating functional element can itself be intended to interrogate the federating functional element in order to determine the path for these signaling messages.
The invention also has the aim of a software product implementing this method in the different possible implementations.
The invention also has the aim of a system containing a domain name server, DNS, and a federating functional element according to the third aim of the invention.
Lastly, the invention has the aim of on interrogating functional element I-CSCF for the domain of a multimedia subsystem, IMS, containing multiple domains, each containing a set of call session control function elements, CSCF, and a federating functional element used to route signaling messages between these domains of the multimedia subsystem.
The interrogating functional element is intended to receive a signaling messag^ from a first client connected to this domain and intended for a second client.
It is characterized in that it is also intended to:
Determine whether the second client is connected to one
of the domains of the multimedia subsystem.
If this is not the cose, to send the signaling message
outside the multimedia subsystem without interrogating
the federating functional element, and
if this is the case, to interrogate the federating functional
element, in order to determine the path for this signaling
message.
The invention, its different implementations and its advantages will appear more clearly in the implementation description which follows, together with the attached figures.
Figure ), mentioned previously, represents the IMS architecture.
Figure 2, also mentioned previously, represents a solution for the state of the art.
Figure 3 shows a diagram for a first implementation of the invention.
Figure 4 shows a diagram for a second implementation of the invention.
Figure 5 illustrates the operation of a distributed hashing table.
First implementation
According \o a first implementation of the invention, the subscription location functional element, SLF, is implemented by a distributed hashing table.
The SLF (Subscriber Locator Function or Subscription Locator Function) functional element is a used to determine a subscriber server HSS in a multimedia subsystem IMS which contains severol.
This functional element is for example described in the documents TS 29.228 and TS 29.229, respectively entitled "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signaliing flows and message contents" and "Cx and Dx interfaces based on the Diameter protocol; Protocol details". These two documents are produced by the 3GPP standardization body and ore available on its website.
The SLF functional element is also mentioned in the RFC 4457 of the IETF entitled 'The Session Initiation Protocol (SiPj - P-User-Database Private-Header fP-hleaderj", published in April 2006.
This subscriber selection functional element SLF forms part of the routing methods of the multimedia subsystem IMS, in other words of all the technical means used for the resolution of a logical address contained in a signaling message to route it towards the corresponding destination. Other than this SLF element, the routing methods can also include subscriber sen/ers HSS, the serving functional elements S-CSCF, and the domain name servers DNS.
It is possible that one multimedia subsystem IMS may have several subscriber servers HSS. On figure 3, three subscriber servers HSSi, HSS2 and HSS3, have been shown.
When the interrogating functional element 1-CSCF receives on incoming signaling message (or an incoming call), it must determine how to route this message to the recipient communication client. This is the case, for example, for SIP "Invite" messages aiming to set up a call session. These "Invite" messages, in accordance with the SIP
protocol, conioin the logical address of one or more recipient subscribers.
To route the "Invite" signaling message to the recipient communication client L it interrogates the subscriber location functional element SLF, providing in its request the logical address of the recipient contained in the "Invite" signaling message.
This determines a subscriber server Identifier associated v^lth this logical address, and sends it in a response message to the interrogating functional element l-CSCF.
Possessing this identifier (its IP address, for example), it can then interrogate the correct subscriber server HSSl, in other vs^ords the one which has the information relating to the user subscriber of the communication client T and corresponding to the logical address.
The subscriber server contains associations between logical addresses and identifiers of serving functional elements S-CSCF. By providing the logical address in its request, the interrogating functional element l-CSCF receives in response an identifier of the serving functional element S-CSCFi with which the recipient communication client T is registered.
It can then send the "Invite" signaling message to this serving functional element S-CSCFi. This has the information relating to the communication client T and to the user subscriber of this client.
It in particular has the association between the logical address of the subscriber and the physical address of the communication client T. It can then send the signaling message to the recipient subscriber using the physical address (for example its IP address) of its communication client T.
Furthermore, when a communication client T registers with the multimedia subsystem IMS, information is memorized in the serving functional element S-CSCFi to which it is attached, in a subscriber server HSSi and in the subscriber selection functional element SLF.
It is possible to limit the size of the subscriber servers HSS by scaling them down, but the subscriber location functional element SLF remains a centralized element, the size of which is proportional to the number of subscribers (in other words registered logical addresses).
According to the invention, this subscriber location functional element SLF is implemented by a distributed hashing table, it therefore contains a set of nodes Ni, N2...Nn inter-connected between themselves.
The operation of this network of nodes will be explained In more detail below. It is important however that it should hove the following as an interface:
- a function used to determine a subscriber server HSS based on a logical address; and,
- o function used to memorize in the distributed hashing table an association between the logical address of the user of the communication client T and the subscriber server HSSi which has been assigned to it.
This first execution method has the advantage of only modifying the implementation of the subscriber location functional element SLF.
This can retain the same interface and for example a Dx interface compliant with the Diameter protocol. In this way, it can interface with the other functional elements of the multimedia subsystem IMS, without requiring modification of the other elements.
Second implementation
According to a second implementation of the invention, illustrated by figure 4, the multimedia subsystem IMS contains multiple domains, IMSi, IMS2... IMSn. Each domain can be seen as an entirely separate IMS subsystem, having its own call session control function (CSCF) elements:
- a serving functional element S-CSCF, respectively Si, S2... Sn
- an interrogating functional element I-CSCF, respectively h, I2... In.
- (if necessary) a proximity functional element P-CSCF, not shown.
The routing methods contain, as in the previous example, subscriber selecfion functional elements SLFi, SLF2... SLFn; serving functional elements Si, S2... Sn; a domain name server DNS; subscriber servers (HSS, not shown).
According to the invention, they also contain, a federating functional element FF. This new functional element is used to determine one of the domains IMSi, IMS2... IMSn, based on a logical address contained in a signaling message.
This federating functional element FF is implemented by a distributed hashing table.
Distributed hashina table
A distributed hashing table (DHT) is a technology used to memorize and retrieve information in a widely distributed system such
as a peer to peer netv^ork. In principle, the content of the hashing table is distributed over all the stations or nodes of the network and there is no centralized device.
Such distributed hashing tables are described for example in the article 'looking up Dafo in P2P Systems" by H. Balakrishna, F. Kaashoek, D. Karger, R. Morris and I. Stoica, published in February 2003, in the review Communications of the ACM, vol. 46, no. 2.
The patent request WO2006/068365 mentions some of the principles of the state of the art and proposes a new distributed hashing table approach.
There are different possible implementations of a distributed hashing table. Figure 5 shows a simplified example to help understanding, but the invention should not be considered to be limited to this specific implementation.
The set of nodes Xj, X2, X3.... XN of the distributed hashing table DHT plays the same role. In order to memorize or retrieve a value from this table [or network), any of these nodes can be consulted.
In the example of figure 5, the interrogating functional element \-CSCF interrogates the node X3, providing ii with a logical address.
This then calculates a hashing function on this logical address.
A hashing function is a function used to convert a vaiue belonging to a large set (all possible logical addresses) to a second value belonging to a reduced set. This second value here is an integer between 1 and N, where N is the number of nodes in the distributed hashing table DHT.
The hashing function H should generally respect the following mathematical property: H(x) ^t H(y) => x ?t y
Furthermore, if x = y then the probability must be greater/less thanH(x)=H(y),
The value i returned by the hashing function indicates to node X3 that node Xi is probably the one which possesses the association between the logical address received and the corresponding domain. H sends the request to this node Xi. If this node does indeed possess the association, it can return the domain associated with the logical address. Otherwise, it can send the request to another node (neighbor) which may possess the association.
Iterativeiy, the algorithm converges to the node which possesses the association.
The principle for the memorization of a new association is similar. Any node of the DHT peer to peer network receives a request for memorization and calculates a value based on the hashing function and the logical address.
This value determines a specific node of the set of nodes of the distributed hashing table DHT, to which the first node resends the request for memorization. The node designated in this way memorizes the association.
According to one execution method of the invention, the nodes of this distributed hashing table are mode up of all or some of the serving functional elements Si, S2... Sn.
This execution method is used in order not to add a new element within the global architecture, and to use the already defined,functional elements. It allows better respect for the current standardization of the multimedia subnetworks IMS.
Preferentially, the federating functional element FF presents a Dx interface which can be used by the other functional elements (serving, S-CSCF , or interrogating, I-CSCF).
This Dx interface can typically implement the Diameter protocol, standardized by the IETF. Two main functions ore of use for this interface: a function used to memorize a new association, and a function used to retrieve the value associated with a value provided.
Registration of a new client with a domain
When a communication client T registers with a domain of the IMS communication subsystem, information is memorized in the distributed hashing table of the federating functional element FF. This information contains the association between the logical address of the user of this communication client T and an identifier for this domain.
Within the domain itself, the communication client is registered in a known manner and as described previously.
Incomina call
During an incoming call, a signaling message m is sent to the multimedia subsystem IMS. This signaling message m is \ypica\\y an "Invite" message compliant with the SIP protocol. It contains the logical address of a called subscriber. It is assumed in the example of figure 4 that this subscriber is the user of the communication client T, connected to the domain IMS2.
This address, in accordance with the specifications of the 3GPP and the ETSITISPAN, is a SIP URI (Universal Resource Identifier).
It can take the form a@x.com. The term "a" identifies the subscriber, while the term "x.com" identifies the multimedia subsystem, IMS.
The association of this term "x.com" with the multimedia subsystem (MS is carried out by the domain name sen/er DNS. It is used to determine a physical address (an IP address, for example) of an entry point to this multimedia subsystem.
Typically, it is intended to take into account service registrations known as "SRV registration", defined by the RFC 2782 of the IETF.
Since the multimedia subsystem according to the invention does not have a unique entry point, all or part of the interrogating functional elements, h, b... In, can be associated with the term "x.com" within the DNS server. This can choose which address to send in a random manner, or according to a heuristic method based on certain criteria such as the load of the different interrogating functional elements, priorities, etc.
!n the example of figure 4, it is assumed that the domain name server DNS has determined the interrogating functional element h. The signaling message m is consequently sent to this functional element.
This then interrogates the federating functional element FF.
In its request, it inserts the logical address of the called user (here, "a@x.com").
In response it receives the identifier of the domain with which the terminal used by the called party is connected. This identifier can for example be the physical address (IP) of the interface functional element of the domain in question.
In the example of figure 4, this identifier is that of the domain IMS2, and the physical address sent can be that of the interface functional element I2.
The interrogating functional element h can then send the signaling message m to the interrogating functional element I2.
The fnierrogarmg funciiona} e/emenf h can fhen act in accordance with the standardization of the IMS, since the domain IMS2 is a standard multimedia subsystem in itself. The signaling message m can then be routed to the terminal L used by the called party.
Another situation may arise corresponding to the case in which the terminal T is connected to the domain IMSi. In this situation, the interrogating functional element li after interrogation of the federating functional element FF sends the signaling message m directly to its domain IMSi (more precisely to the serving functional element Si).
Outaoing call
Returning to the example of figure 4, it is assumed now that the communication client (or terminal) T, connected to the domain IMS2, sends a signaling message representing an outgoing call.
The description in fact only applies to the case of an outgoing call from the domain IMS2. The situation in which the called communication client is connected to the same multimedia subsystem IMS2 corresponds to the state of the art in terms of operation of a multimedia subsystem.
In the case of an outgoing call, the signaling message is sent through the domain or multimedia subsystem IMS2 to the serving functional element S2 (if necessary using a proximity functional element P-CSCF, not shown).
This serving functional element S2 can then be intended to interrogate the federating functional element FF in order to determine a path (or route) for this signaling message.
Two scenarios may then arise: the called party may be connected to one of the domains IMSi... IMSn, or to another network or multimedia subsystem.
As in the situation of an incoming call, described previously, the federating functional element FF can determine to which domain the called communication client is connected.
According to a f\rs\ implementation, the serving functional element S2 systematically interrogates the federating functional element FF. If the called party is connected io one of the other domains, the federating functional element determines this and sends an identifier of the determined domain. If the called party is not connected to one of these domains IMSj... IMSn. the federating functional element FF does not find its address and sends a specific message which can be interpreted by the serving functional element S2 as meaning that the called communication client is outside the domains IMSi... IMSn- This specific message can be on error message or a message containing a specific identifier to indicate the absence of the called communication client in its information base.
It is also possible to plan for the serving functional elements to have means to determine whether or not the communication client forms part of one of the domains IMSi... IMSn without having to interrogate the federating functional element FF.
According to another execution method of the invention, the domain is configured in such a way that ali the outgoing signaling messages are sent to the interrogating functional element l-CSCF.
This execution method can for example be implemented by granting the interrogating functional element l-CSCF the functions of a THIG (Topology Hiding Internetwork Gateway). The interrogating
global domain determined by the domain name "x". With such a convention. It is easy to determine through the interrogating functional elements whether or not this name corresponds to its own name.
If it does not li means that the client belongs to another network and the signaling message must be routed externally. If the name corresponds, however, it means that the federating functional element must be interrogated and the signaling message must be routed to the domain corresponding to the response given by this federating functional element FF.
This operating method in which all the outgoing signaling messages pass through the interrogating functional element ('THIG" method) has the advantage of only requiring the modification of the interrogating functional elements. In the situation of an incoming call or that of an outgoing call it is these elements which ore responsible for interrogating the federating functional element FF, and therefore only they need to be intended for this purpose and to process the response from the federating functional element FF.
The other functional elements, in particular the serving functional elements, are unchanged.
Such an operating-method therefore reduces the impact of this new feature on the global architecture of the communication network, and the cost of its addition.
In all coses, the interrogating functional element ('THIG method") or the serving functional element (other execution method) ore intended to determine whether the recipient communication client is connected to one of the domains (whether by its own means, or by interrogation of the federating functional element FF).
tf it is not, it sends the signaling message outside the network. Otherwise, it sends it to the domain corresponding to the identifier sent by the federating functional element FF.
This invention is. therefore used to federate a smalfer set of multimedia subsystems (the domains) to form a larger one.
The global multimedia subsystem IMS can in fact have an interface with regard to the other communication networks which masks its implementation and the fact that it conioins multiple domains IMSi, IMS2... IMSn. The federating functional element is therefore used to make the architecture of the multimedia subsystem and its breakdown into multiple domains transparent for the signaling message senders and for the rest of the communication networks.
It then becomes possible to open certain domains - of a reduced size - to management by private operators. For example, a domain can represent a company or a subsidiary of a company and its management can be made the responsibility of an administrator of. this company or this subsidiary.
The global multimedia subsystem, federating several domains, can be administered by an operator which guarantees the interface with regard to the external network.
It should also be noted that the two implementations can be combined, so that the subscriber selection functional elements (SLF) contained in each domain IMSi, IMS2... IMSn are implemented by a distributed hashing table, and that these domains are federated by a federating functional element FF.
From an architectural point of view the federating functional element FF can be integrated with other functional elements. In particular, a block containing the federating functional element FF and the domain name server DNS con be integrated into a single function, forming a system.
Claims
1) Multimedia subsystem, IMS, containing a set of call session control function elements, CSCF, suitable for sending a signaling message (m) between a first communication client (T) connected to said multimedia subsystem and at least one second communication client where said second communication client may be connected to said multimedia subsystem or remote and accessible through an interrogating functional element, l-CSCF, and routing methods allowing a path to be determined for the transmission of said signaling message, based on a logical address contained in said signaling message, characterized in that the routing methods implement a distributed hashing table.
2) Multimedia subsystem according to the previous claim, in which said routing methods contain a subscriber selection functional element, SLF, used to determine the subscriber server HSS associated with said logical address and implemented by a distributed hashing table.
3) Multimedia subsystem according to claim 1, containing multiple domains, each containing a set of call session control function elements, CSCF, said routing methods containing a federating functional element (FF) used to determine one of said domains based on said logical address, and implemented by a distributed hashing table.
4) Multimedia subsystem, IMS, according to claim 3, in which the serving functional elements, S-CSCF, of at least some of said domains form the nodes of said distributed hashing table.
5) Multimedia subsystem, IMS, according to one of claims 3 or 4, in which at least one domain is intended so that the signaling messages from said first communication client connected to said domain are sent to the interrogating functional element, l-CSCF, of said domain, said interrogating functional element itself being intended to interrogate said federating functional element (FF) in order to determine the path for said signaling messages.
6) Multimedia subsystem, IMS, according to the previous claim, in which said interrogating functional element implements the functions of a THIG gateway.
7) Multimedia subsystem, IMS, according to claim 5, in which said interrogating functional element, l-CSCF, is intended, on receipt of a signaling message from said first communication client, to determine whether the recipient communication client determined by the logical address contained in said signaling message is connected to one of said domains, and if not, to send said signaling message outside said multimedia subsystem without interrogating said federating functional element (FF).
8) Multimedia subsystem, IMS, according to claim 5, in which said interrogating functional elements, l-CSCF, are intended, on receipt of a signaling message from said first communication client, to systematically interrogate said federating functional element (FF) and, in the absence of a response from this element determining a path, to send said signaling message outside said multimedia subsystem.
9) Multimedia subsystem, IMS, according to one of claims 3 to
8, in which the interface between the ir)ierrogaV\ng functional
elements of said domains and said federating functional element (FF)
Is a Dx interface, implementing the Diameter protocol.,
10) Multimedia subsystem, IMS, according to one of claims 3 to
9, in which the interface between the interrogating functional
elements of said domains and said federating functional element (FF)
contains a first function used to insert an association between the
logical address and domain and a second function used to determine
the domain corresponding to a given logical address.
11) Multimedia subsystem, IMS, according to one of claims 3 to
10, in which said logical addresses contain an identifier corresponding
to said multimedia subsystem.
12) Communication network containing at least one
multimedia subsystem according to one of the previous claims.
13) Federating functional element (FF) for multimedia
subsystem, IMS, containing multiple domains, each containing a set of
call session control function elements, CSCF, said federating functional
element containing means to determine a domain based on a logical
address contained in a signaling message, said means implementing
a distributed hashing table,
14) Federating functional element (FF) according to the
previous claim, in which the sen/ing functional elements, S-CSCF, of at
least some of said domains form the nodes of said distributed hashing
table.
15) Federating functional element (FF) according to one of claims 13 or 14, presenting a Dx interface implementing the Diameter protocol.
16) Federating functional element (FF) according to one of claims 13 to 15, presenting an interface containing a first function used to insert an association between the logical address and domain and a second function used to determine the domain corresponding to a given logical address.
17) Interrogating functional element, l-CSCF, for domain of a multimedia subsystem, IMS, containing multiple domains, each containing a set of call session control function elements, CSCF, and a federating functional element (FF) used to route signaling messages between said domains of said multimedia subsystem, said interrogating functional element being intended to receive a signaling message from a first client connected to said domain and intended for a second client, and characterized in that it is also intended to:
Determine whether said second client is connected to
one of said domains of said multimedia subsystem,
if this is not the case, to send said signaling message
outside said multimedia subsystem without interrogating
said federating functional element (FF),
If this is the case, to interrogate said federating functional
element (FF) in order to determine the path for said
signaling message.
18) Interrogating functional element occording to the previous claim, in which the interface with said federating functional element (FF) is a Dx interface, implementing the Diameter protocol.
19) Interrogating functional element according to one of claims 17 or 18, in which said determination is carried out based on a logical address contained in said signaling message.
20) Interrogating functional element according to the previous claim, in which the interface with said federating functional element (FF) contains a first function used to insert an association between the logical address and domain and a second function used to determine the domain corresponding io a given logical address.
21) Interrogating functional element, according to claim 19, in which said logical addresses confain an identifier corresponding io said multimedia subsystem.
22) Method of sending a signaling message through a multimedia subsystem, IMS, containing a set of call session control function elements, CSCF, between a first communication client, connecied fo said multimedia subsystem, and a second communication client, where said second communication client may be connected to said multimedia subsystem or remote and accessible through an interrogating functional element, l-CSCF, said process containing a stage for the determination of a path for the transmission of said signaling message, based on a logical address contained In said signaling message, characterized in that said stage implements a distributed hashing table.
23) Method of sending a signaling message according to the previous claim, containing a stage for the determination of a subscriber server HSS associated with said logical address, through a subscriber selection functional element, SLF, implemented by a distributed hashing table.
24) Method of sending a signaling message according to claim 22, in which said multimedia subsystem contains multiple domains, each containing a set of coll session control function elements, CSCF, said method containing a stage for the determination of a domain based on said logical address, through a federating functional element (FF) implemented by a distributed hashing table.
25) Method of sending a signaling message, according to the previous claim, in which the serving functional elements, S-CSCF, of at \easi some of satd domains form the nodes of said distributed hashing table.
26) Method of sending a signaling message, according to one of claims 24 or 25, in which at least one domain is intended so that the signaling rhessages from a communication client connected to said domain ore sent to the interrogating functional element, l-CSCF, of said domain, sold interrogating functional element itself being intended to Interrogate said federating functional element (FF) in order to determine the path for said signaling messages.
27) Software product implementing the method according io one of claims 22 to 24 when it Is run on a data processing device.
28) System containing a domain name server, DNS, and a
federating functional element according to one of claims 13 to 16.
29) Multimedia subsystem containing multiple domains, each
containing at least one catt session control function element, CSCF,
and a federating functional element implementing a distributed
hashing table, and used to .federate said domains by routing an
incoming signaling message to the appropriate domain in a
transparent manner for the sender of said signaling message.
30) Multimedia subsystem according to the previous claim, in
v/hich at least some of said domains are managed by private
operators.
31) Multimedia subsystem according to the previous claim, in
which at least one of said private operators is independent of the
operator of said multimedia subsystem and of the federaYmg
functional element.
| Section | Controller | Decision Date |
|---|---|---|
| # | Name | Date |
|---|---|---|
| 1 | 4007-CHENP-2009 FORM-3 24-09-2009.pdf | 2009-09-24 |
| 1 | 4007-CHENP-2009-US(14)-HearingNotice-(HearingDate-05-10-2020).pdf | 2021-10-03 |
| 2 | 4007-CHENP-2009 FORM-3 15-10-2009.pdf | 2009-10-15 |
| 2 | 4007-CHENP-2009-Correspondence to notify the Controller [01-10-2020(online)].pdf | 2020-10-01 |
| 3 | 4007-CHENP-2009-FORM 3 [09-05-2018(online)].pdf | 2018-05-09 |
| 3 | 4007-chenp-2009 correspondence others 15-12-2010.pdf | 2010-12-15 |
| 4 | Correspondence by Agent_Power of Attorney_13-12-2017.pdf | 2017-12-13 |
| 4 | 4007-CHENP-2009 FORM-18 15-12-2010.pdf | 2010-12-15 |
| 5 | 4007-CHENP-2009-PETITION UNDER RULE 137 [12-12-2017(online)].pdf | 2017-12-12 |
| 5 | 4007-chenp-2009 pct.pdf | 2011-09-04 |
| 6 | 4007-CHENP-2009-Proof of Right (MANDATORY) [12-12-2017(online)].pdf | 2017-12-12 |
| 6 | 4007-chenp-2009 pct search report.pdf | 2011-09-04 |
| 7 | 4007-CHENP-2009-ABSTRACT [15-11-2017(online)].pdf | 2017-11-15 |
| 7 | 4007-chenp-2009 drawings.pdf | 2011-09-04 |
| 8 | 4007-CHENP-2009-CLAIMS [15-11-2017(online)].pdf | 2017-11-15 |
| 8 | 4007-chenp-2009 description(complete).pdf | 2011-09-04 |
| 9 | 4007-chenp-2009 claims.pdf | 2011-09-04 |
| 9 | 4007-CHENP-2009-COMPLETE SPECIFICATION [15-11-2017(online)].pdf | 2017-11-15 |
| 10 | 4007-chenp-2009 abstract.pdf | 2011-09-04 |
| 10 | 4007-CHENP-2009-DRAWING [15-11-2017(online)].pdf | 2017-11-15 |
| 11 | 4007-chenp-2009 others.pdf | 2011-09-04 |
| 11 | 4007-CHENP-2009-FER_SER_REPLY [15-11-2017(online)].pdf | 2017-11-15 |
| 12 | 4007-chenp-2009 form-26.pdf | 2011-09-04 |
| 12 | 4007-CHENP-2009-FORM 3 [15-11-2017(online)].pdf | 2017-11-15 |
| 13 | 4007-chenp-2009 form-5.pdf | 2011-09-04 |
| 13 | 4007-CHENP-2009-FORM 4(ii) [15-11-2017(online)].pdf | 2017-11-15 |
| 14 | 4007-chenp-2009 form-3.pdf | 2011-09-04 |
| 14 | 4007-CHENP-2009-OTHERS [15-11-2017(online)].pdf | 2017-11-15 |
| 15 | 4007-chenp-2009 form-1.pdf | 2011-09-04 |
| 15 | 4007-CHENP-2009-PETITION UNDER RULE 137 [15-11-2017(online)].pdf | 2017-11-15 |
| 16 | 4007-chenp-2009 correspondence others.pdf | 2011-09-04 |
| 16 | 4007-CHENP-2009-FER.pdf | 2017-05-15 |
| 17 | Form 3 [05-05-2017(online)].pdf | 2017-05-05 |
| 17 | 4007-CHENP-2010 CORRESPONDENCE OTHERS 09-09-2011.pdf | 2011-09-09 |
| 18 | 4007-CHENP-2010 FORM-13 09-09-2011.pdf | 2011-09-09 |
| 18 | Form 3 [22-08-2016(online)].pdf | 2016-08-22 |
| 19 | 4007-CHENP-2009 FORM-13 09-09-2011.pdf | 2011-09-09 |
| 19 | 4007-CHENP-2009-Correspondence-231015.pdf | 2015-10-26 |
| 20 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 09-09-2011.pdf | 2011-09-09 |
| 20 | 4007-CHENP-2009-Form 3-231015.pdf | 2015-10-26 |
| 21 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 01-07-2013.pdf | 2013-07-01 |
| 21 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 26-06-2015.pdf | 2015-06-26 |
| 22 | 4007-CHENP-2009 FORM-3 01-07-2013.pdf | 2013-07-01 |
| 22 | 4007-CHENP-2009 FORM-3 26-06-2015.pdf | 2015-06-26 |
| 23 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 16-10-2014.pdf | 2014-10-16 |
| 23 | 4007-CHENP-2009 FORM-3 24-09-2013.pdf | 2013-09-24 |
| 24 | 4007-CHENP-2009 FORM-3 16-10-2014.pdf | 2014-10-16 |
| 24 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 24-09-2013.pdf | 2013-09-24 |
| 25 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 21-02-2014.pdf | 2014-02-21 |
| 25 | 4007-CHENP-2009 FORM-3 21-02-2014.pdf | 2014-02-21 |
| 26 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 21-02-2014.pdf | 2014-02-21 |
| 26 | 4007-CHENP-2009 FORM-3 21-02-2014.pdf | 2014-02-21 |
| 27 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 24-09-2013.pdf | 2013-09-24 |
| 27 | 4007-CHENP-2009 FORM-3 16-10-2014.pdf | 2014-10-16 |
| 28 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 16-10-2014.pdf | 2014-10-16 |
| 28 | 4007-CHENP-2009 FORM-3 24-09-2013.pdf | 2013-09-24 |
| 29 | 4007-CHENP-2009 FORM-3 01-07-2013.pdf | 2013-07-01 |
| 29 | 4007-CHENP-2009 FORM-3 26-06-2015.pdf | 2015-06-26 |
| 30 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 01-07-2013.pdf | 2013-07-01 |
| 30 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 26-06-2015.pdf | 2015-06-26 |
| 31 | 4007-CHENP-2009 CORRESPONDENCE OTHERS 09-09-2011.pdf | 2011-09-09 |
| 31 | 4007-CHENP-2009-Form 3-231015.pdf | 2015-10-26 |
| 32 | 4007-CHENP-2009 FORM-13 09-09-2011.pdf | 2011-09-09 |
| 32 | 4007-CHENP-2009-Correspondence-231015.pdf | 2015-10-26 |
| 33 | 4007-CHENP-2010 FORM-13 09-09-2011.pdf | 2011-09-09 |
| 33 | Form 3 [22-08-2016(online)].pdf | 2016-08-22 |
| 34 | 4007-CHENP-2010 CORRESPONDENCE OTHERS 09-09-2011.pdf | 2011-09-09 |
| 34 | Form 3 [05-05-2017(online)].pdf | 2017-05-05 |
| 35 | 4007-CHENP-2009-FER.pdf | 2017-05-15 |
| 35 | 4007-chenp-2009 correspondence others.pdf | 2011-09-04 |
| 36 | 4007-chenp-2009 form-1.pdf | 2011-09-04 |
| 36 | 4007-CHENP-2009-PETITION UNDER RULE 137 [15-11-2017(online)].pdf | 2017-11-15 |
| 37 | 4007-chenp-2009 form-3.pdf | 2011-09-04 |
| 37 | 4007-CHENP-2009-OTHERS [15-11-2017(online)].pdf | 2017-11-15 |
| 38 | 4007-chenp-2009 form-5.pdf | 2011-09-04 |
| 38 | 4007-CHENP-2009-FORM 4(ii) [15-11-2017(online)].pdf | 2017-11-15 |
| 39 | 4007-chenp-2009 form-26.pdf | 2011-09-04 |
| 39 | 4007-CHENP-2009-FORM 3 [15-11-2017(online)].pdf | 2017-11-15 |
| 40 | 4007-chenp-2009 others.pdf | 2011-09-04 |
| 40 | 4007-CHENP-2009-FER_SER_REPLY [15-11-2017(online)].pdf | 2017-11-15 |
| 41 | 4007-chenp-2009 abstract.pdf | 2011-09-04 |
| 41 | 4007-CHENP-2009-DRAWING [15-11-2017(online)].pdf | 2017-11-15 |
| 42 | 4007-chenp-2009 claims.pdf | 2011-09-04 |
| 42 | 4007-CHENP-2009-COMPLETE SPECIFICATION [15-11-2017(online)].pdf | 2017-11-15 |
| 43 | 4007-chenp-2009 description(complete).pdf | 2011-09-04 |
| 43 | 4007-CHENP-2009-CLAIMS [15-11-2017(online)].pdf | 2017-11-15 |
| 44 | 4007-chenp-2009 drawings.pdf | 2011-09-04 |
| 44 | 4007-CHENP-2009-ABSTRACT [15-11-2017(online)].pdf | 2017-11-15 |
| 45 | 4007-CHENP-2009-Proof of Right (MANDATORY) [12-12-2017(online)].pdf | 2017-12-12 |
| 45 | 4007-chenp-2009 pct search report.pdf | 2011-09-04 |
| 46 | 4007-CHENP-2009-PETITION UNDER RULE 137 [12-12-2017(online)].pdf | 2017-12-12 |
| 46 | 4007-chenp-2009 pct.pdf | 2011-09-04 |
| 47 | Correspondence by Agent_Power of Attorney_13-12-2017.pdf | 2017-12-13 |
| 47 | 4007-CHENP-2009 FORM-18 15-12-2010.pdf | 2010-12-15 |
| 48 | 4007-CHENP-2009-FORM 3 [09-05-2018(online)].pdf | 2018-05-09 |
| 48 | 4007-chenp-2009 correspondence others 15-12-2010.pdf | 2010-12-15 |
| 49 | 4007-CHENP-2009-Correspondence to notify the Controller [01-10-2020(online)].pdf | 2020-10-01 |
| 49 | 4007-CHENP-2009 FORM-3 15-10-2009.pdf | 2009-10-15 |
| 50 | 4007-CHENP-2009 FORM-3 24-09-2009.pdf | 2009-09-24 |
| 50 | 4007-CHENP-2009-US(14)-HearingNotice-(HearingDate-05-10-2020).pdf | 2021-10-03 |
| 1 | search4007_25-04-2017.pdf |
| 1 | Search_SER_4007CHENP2009AE_24-08-2020.pdf |
| 2 | search4007_25-04-2017.pdf |
| 2 | Search_SER_4007CHENP2009AE_24-08-2020.pdf |