Method and server for performing capability discovery
View Patent ↗The invention relates to a method for performing a capability discovery. The method is implemented by a home server ( 10 ) and comprising the steps of:—receiving ( 101 ), from a user terminal ( 11 ), a principal discovery request ( 12 ) comprising a complete contact list,—from the complete contact list, determining ( 102 ) which contacts are locally known, and which contacts are locally unknown,—generating a limited contact list containing all contacts that are locally unknown,—sending ( 103 ) a plurality of secondary discovery requests ( 19 ) comprising the limited contact list to a plurality of remote servers ( 17, 18 ),—receiving ( 104 ), from each remote server ( 17, 18 ), a notification ( 16 ) containing information about contacts contained in the limited contact list,—sending ( 105 ), for each unknown contact by the home server ( 10 ) and the plurality of remote servers ( 17, 18 ), a back-end subscription to a home IMS core ( 21 ).
1. Method for performing a capability discovery, said method being implemented by a home server of a home domain and comprising:
receiving, from a user terminal, a principal discovery request comprising a complete contact list,
from the complete contact list, determining which contacts are locally known in the home domain, and which contacts are locally unknown in the home domain,
generating a limited contact list containing all contacts that are locally unknown,
sending a plurality of secondary discovery requests comprising the limited contact list to a plurality of remote servers,
receiving, from each remote server, a notification containing capability discovery contact information about contacts contained in the limited contact list, including which contacts are remotely known and remotely unknown in each remote server of a respective remote domain, and
sending, for each unknown contact both locally unknown by the home server and remotely unknown to the plurality of remote servers, a back-end subscription to a home Internet Protocol Multimedia Subsystem (IMS) core.
2. Method according to claim 1 , wherein a single secondary discovery request containing the limited contact list is sent to each remote server.
3. Method according to claim 1 , wherein the principal discovery request is a Resource List Server subscription with a Request-Contained list using the Session Initiation Protocol Request for Comments (RFC) 5367.
4. Method according to claim 1 , wherein each secondary discovery request is a Resource List Server subscription with a Request-Contained list using the Session Initiation Protocol RFC 5367.
5. Method according to claim 1 , wherein each secondary discovery request is performed by the home server using a Public Service Identity identification identical to the Public Service Identity identification supported by each remote server.
6. Method according to claim 1 , wherein the notification containing information about contacts contained in the limited contact list indicates the contacts that are Rich Communication Suite (RCS) enabled.
7. Method according to claim 1 , wherein the notification containing information about contacts contained in the limited contact list indicates the contacts that are IMS enabled.
8. Method according to claim 1 , wherein the notification containing information about contacts contained in the limited contact list indicates the contacts that are not IMS enabled.
9. Method according to claim 1 , wherein when a remote server has no information about a contact, then the notification indicates for said contact a state of terminated and a reason of no resource.
10. Method according to claim 6 , wherein when a remote server has a contact not RCS enabled, then the notification indicates for said contact a state of terminated and a reason of rejected.
11. Home server of a home domain for performing a capability discovery comprising:
a processor;
a memory;
at least one input/output module constructed and arranged to receive from a user terminal a principal discovery request comprising a complete contact list,
wherein the processor is constructed and arranged to execute instructions contained in the memory in order to determine, from the complete contact list, which contacts are locally known in the home domain, and which contacts are locally unknown in the home domain to generate a limited contact list;
and wherein the input/output module is constructed and arranged to send to a plurality of remote servers, for all contacts that are locally unknown in the home domain, a plurality of secondary discovery requests comprising the limited contact list, to receive from each remote server a notification containing capability discovery contact information about contacts contained in the limited contact list, including which contacts are remotely known and remotely unknown in each remote server of a respective remote domain, and to send, for each unknown contact both locally unknown by the home server and remotely unknown to the plurality of remote servers, a back-end subscription to a home IMS core.
12. Home server according to claim 11 , wherein the home server is a Resource List Server.