(19)
(11)EP 1 817 682 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
12.09.2018 Bulletin 2018/37

(21)Application number: 05812791.1

(22)Date of filing:  13.10.2005
(51)Int. Cl.: 
G06F 15/16  (2006.01)
H04L 29/06  (2006.01)
(86)International application number:
PCT/US2005/037116
(87)International publication number:
WO 2006/047111 (04.05.2006 Gazette  2006/18)

(54)

PROVIDING A PROXY SERVER FEATURE AT AN ENDPOINT

BEREITSTELLUNG EINES PROXY-SERVER-FUNKTION AN EINEM ENDPUNKT

FOURNITURE DE CARACTERISTIQUE DE SERVEUR PROXY A UNE EXTREMITE


(84)Designated Contracting States:
AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

(30)Priority: 26.10.2004 US 973146

(43)Date of publication of application:
15.08.2007 Bulletin 2007/33

(73)Proprietor: Cisco Technology, Inc.
San Jose, CA 95134 (US)

(72)Inventors:
  • SANDERS, Jeffery, A.
    Cocoa, FL 32926 (US)
  • MCCLUNG, Michael, H.
    Ruckersville VA 22960-1601 (US)
  • CHEN, Henry
    Plano, TX 75024 (US)
  • FRANCKE, Andrew, J.
    Morgan Hill, CA 95037 (US)

(74)Representative: Kazi, Ilya 
Mathys & Squire LLP
The Shard 32 London Bridge Street London SE1 9SG
The Shard 32 London Bridge Street London SE1 9SG (GB)


(56)References cited: : 
US-A1- 2002 169 887
US-A1- 2004 044 727
US-A1- 2005 033 985
US-A1- 2006 067 323
US-B1- 6 667 968
US-A1- 2002 169 887
US-A1- 2004 131 060
US-A1- 2006 047 742
US-B1- 6 667 968
  
      
    Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


    Description

    TECHNICAL FIELD



    [0001] This invention relates generally to the field of communications and more specifically to providing a proxy server feature at an endpoint.

    BACKGROUND



    [0002] As communications technologies develop, voice services and data services have increasingly converged. One such example is the use of Internet protocol (IP) technology to transport voice data. The use of IP technology enables voice traffic to gain the benefits of packet communication protocols. Similarly, other technologies may provide benefits when applied to telephony systems. Discovering appropriate technologies and uses for these technologies, however, remains a daunting challenge.

    [0003] US 6667968 discloses associating multiple mobile stations with a gateway acting as a proxy device for registering the mobile stations with a gatekeeper in an H.323 network. US 2002/169887 discloses networks utilising SIP proxies.

    [0004] US 2004/0044727 describes a shared resource distributed index mechanism that peers in a peer-to-peer network may utilize to distribute index entries corresponding to resources among one or more other peers. These indexes may be used to direct queries to peers where the queries are most likely to be answered.

    SUMMARY OF THE DISCLOSURE



    [0005] In accordance with the present invention, disadvantages and problems associated with previous techniques for providing proxy server features may be reduced or eliminated.

    [0006] Aspects of the invention are set out in the independent claims. Certain preferred features are set out in the dependent claims.

    [0007] According to one disclosed embodiment, providing a proxy server feature includes initiating the proxy server feature at an endpoint of a number of user endpoints of a network. Registration information comprising addresses for the endpoints is received and then stored in a routing table at the endpoint. The endpoint locates a callee endpoint using the routing table in order to establish a session with the callee endpoint.

    [0008] Certain embodiments of the invention may provide one or more technical advantages. A technical advantage of one embodiment may be that one or more endpoints may each have a proxy server feature. The proxy server feature may allow an endpoint to operate as a proxy server. Another technical advantage of one embodiment may be that a service framework of an endpoint provides a proxy server feature. The service framework may access a web page comprising feature logic defining the proxy server feature. The web page may be executed to readily provide the proxy server feature.

    [0009] Certain embodiments of the invention may include none, some, or all of the above technical advantages. One or more other technical advantages may be readily apparent to one skilled in the art from the figures, descriptions, and claims included herein.

    BRIEF DESCRIPTION OF THE DRAWINGS



    [0010] For a more complete understanding of the present invention and its features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

    FIGURE 1 is a block diagram of one embodiment of a system that includes endpoints;

    FIGURE 2 is a block diagram of one embodiment of an endpoint that includes a service framework;

    FIGURE 3 is a block diagram of one embodiment of a service framework of the endpoint of FIGURE 2;

    FIGURE 4 is a flowchart of one embodiment of a method for providing a proxy server feature using an endpoint of FIGURE 1; and

    FIGURE 5 is a flowchart of another embodiment of a method for providing a proxy server feature using the endpoints of FIGURE 1.


    DETAILED DESCRIPTION OF THE DRAWINGS



    [0011] Embodiments of the present invention and its advantages are best understood by referring to FIGURES 1 through 4 of the drawings, like numerals being used for like and corresponding parts of the various drawings.

    [0012] FIGURE 1 is a block diagram of one embodiment of a system 10 that includes endpoints 12. According to the embodiment, an endpoint 12a may operate as a proxy server for certain services. As an example, endpoint 12a may operate as a session initiation protocol (SIP) proxy server that provides services such as registering endpoints 12, identifying states of endpoints 12, translating addresses of endpoints 12, or any combination of the preceding. SIP attempts to move communication intelligence to the periphery of a network, the embodiment extends the communication intelligence endpoint 12a operating as a proxy server.

    [0013] According to the illustrated embodiment, system 10 includes one or more endpoints 12, one or more switches 14, a server 16, and a communications network 18 coupled as shown. An endpoint 12 represents any suitable combination or arrangement of logic for providing communication services such as telephony services. Logic may refer to hardware, software, or any combination of hardware and software. Examples of an endpoint 12 include a communication device such as a telephone, a cell phone, a personal digital assistant, a voice appliance, an answering machine, a facsimile machine, a computer, or other device. An embodiment of an endpoint 12 is described in greater detail with reference to FIGURE 2.

    [0014] Referring to FIGURE 1, an endpoint 12 may provide certain proxy server features. A proxy server feature may refer to a feature that mediates communications between endpoints 12 or between an endpoint 12 and other network equipment. Proxy server features may support the establishment, modification, and termination of any suitable communication session. For example, a proxy server feature may support negotiating features and capabilities of a session at the time the session is being established, and modifying designated capabilities once the session has been established. Specific proxy server features may include registering endpoints 12, identifying states of endpoints 12, and translating addresses of endpoints 12. Other specific proxy server features may also include building and maintaining routing tables for directing sessions. Routing tables permit endpoints 12 to match dialed digits to the addresses for reaching an endpoint 12 associated with the dialed digits.

    [0015] According to one embodiment, an endpoint 12 may include a service framework that provides proxy server features by executing feature logic. Feature logic manipulates lower-level functions of endpoint 12 to implement a particular state to provide a proxy server feature. Feature logic may be written in any suitable language such as JAVA or a text-based language such as extensible markup language (XML). The feature logic may be included in text files stored at an endpoint 12 or in web pages loaded and executed by a service framework of an endpoint 12.

    [0016] Feature logic may include instructions for endpoint outputs, endpoint operations, or both. An endpoint output refers to information presented through an endpoint interface, such as a sound, light, or display. Feature logic may instruct an output processing module to handle commands that interact with the endpoint interface. For example, feature logic may instruct an output processing module to turn on a flashing light emitting diode (LED) to indicate a waiting voicemail message.

    [0017] An endpoint operation refers to an operation of endpoint 12. As an example, an endpoint operation may generate messages to an external element such as server 14 or other endpoints 12. As another example, a endpoint operation may command internal operations, such as linking multiple call legs within a conference bridge, routing a call leg to a speaker, or initiating a timer. Feature logic may instruct an operations processing module to handle commands that control the components of endpoint 12. State machines such as an output processing module and operations processing module may work in tandem to effect a procedure controlled by a command.

    [0018] Feature logic associated with a proxy server feature may comprise logic associated with making routing decisions. Example routing decisions include handling registration messages; routing session establishment invitations; forking messages for multiple recipients; forwarding, redirecting, or rejecting session establishment invitations; and handling event subscriptions and notifications. According to one embodiment, feature logic may include an event handler that specifies a response of endpoint 12 to an event. Events include internal events and external events, for example, input from users, other endpoints 12, or external devices. Upon detecting an event, a state machine may access a web page to determine whether the page includes an event handler for the detected event. If so, the state machine responds to the event according to the instructions within the event handler. An event handler can link to another location within the feature logic, link to another web page, or process the event.

    [0019] The service framework may also provide other features, such as call hold, call transfer, call pick-up, call distribution, call conferencing, video transmission, voice messaging, and instant messaging, other feature, or any combination of the preceding. One embodiment of a service framework is described in greater detail with reference to FIGURE 3.

    [0020] Referring to FIGURE 1, switches 14 represent network equipment operable to route, translate, or both route and translate communications. Server 16 comprises any suitable combination or arrangement of logic operating to support communication services provided by endpoints 12. Server 16 may provide a centralized repository of web pages for use by endpoints 12 to provide proxy server features. Server 16 may communicate the web pages from memory 20 to endpoints 12 in response to web page requests. Server 16 may reside within endpoints 12 or in system 10.

    [0021] Network 18 represents any suitable combination or arrangement of components supporting communications between endpoints 12 and server 14. For example, network 18 may include one or more local area networks (LANs), one or more wide area network (WANs), elements of a public switched telephone networks (PSTN), portions of the Internet, components of other suitable communications networks, or any combination of the preceding.

    [0022] According to one embodiment of operation, endpoint 12a may operate as a proxy server. Other endpoints 12b-c may be required to register with endpoint 12a to provide endpoints 12a with registration information such as Internet protocol (IP) addresses. Endpoint 12a stores the registration information in a routing table. If an endpoint 12b-c initiates a communication session, endpoint 12a provides the registration information to establish the communication session.

    [0023] According to another embodiment, some or all endpoints 12a-c may operate as proxy servers. Endpoints 12 register with the endpoints 12a-c operating as proxy servers, and endpoints 12a-c store the registration information in their respective routing tables. Registration information may be distributed among the multiple endpoints 12a-c operating as proxy servers in any suitable manner. For example, endpoints 12 may register with an endpoint 12a, and endpoint 12a distributes the registration information to other endpoints 12b-c. As another example, endpoints 12 may register with all of the endpoints 12a-c operating as proxy servers. Multicast communication may be used for the call control signaling.

    [0024] According to yet another embodiment, an endpoint 12a may operate as a primary proxy server, and another endpoint 12b may operate as a secondary proxy server. Endpoints 12 may register with endpoints 12a-b, and endpoints 12a-b may maintain the registration information in their respective routing tables. Primary proxy server 12a operates as a proxy server, and secondary proxy server endpoint 12b operates as a proxy server if primary proxy server endpoint 12a is not operating.

    [0025] According to one embodiment, endpoint 12a operating as a proxy server may request that another endpoint 12b execute commands to provide proxy server features. For example, endpoint 12a may request that endpoint 12b register with endpoint 12a. Endpoint 12a may make the request by providing web pages for executing the commands to endpoint 12b. The web pages may be provided using any suitable techniques. For example, endpoint 12a may communicate web pages directly to endpoint 12b using hyper-text transfer protocol (HTTP). As another example, endpoint 12a may send endpoint 12b links to the web pages.

    [0026] Modifications, additions, or omissions may be made to system 10 without departing from the scope of the invention. The components of system 10 may be integrated or separated according to particular needs. Moreover, the operations of system 10 may be performed by more, fewer, or other modules. For example, the operations of switch 14 and server 16 may be performed by one module, or the operations of server 16 may be performed by more than one module, so long as certain endpoints 12 provide proxy server features. Additionally, operations of system 10 may be performed using any suitable logic comprising software, hardware, other logic, or any suitable combination of the preceding. As used in this document, "each" refers to each member of a set or each member of a subset of a set.

    [0027] FIGURE 2 is a block diagram of one embodiment of an endpoint 12 that includes a service framework 50. According to the illustrated embodiment, endpoint 12 includes service framework 50, a phone platform 54, hardware-specific applications 58, and hardware 62. Service framework 50 provides proxy components that can be monitored and controlled by feature logic. The feature logic may be included in web pages loaded and executed by service framework 50. One embodiment of service framework 50 is described in greater detail with reference to FIGURE 3.

    [0028] Phone platform 54 includes software that allows endpoint 12 to communicate. Phone platform 54 may include code, configuration data, applications, media, other information, or any combination of the preceding. Code represents logic executed by the elements of endpoint 12 to implement functionality. According to one embodiment, code may include logic used by a state engine to interpret and execute feature logic, such as a real-time interpreter operable to run downloaded feature logic. Phone platform 54 may include a JAVA native interface (JNI) and a JAVA virtual machine that interprets executable byte code as a JAVA application is running.

    [0029] Configuration data represents settings used by endpoint 12 during initialization and operation. For example, configuration data may identify a particular server 14 from which endpoint 12 should request web pages. Applications include programs that provide underlying management and control of the operation of endpoint 12. For example, applications may include a media manager, an application manager, a property manager, a call agent, other program, or any combination of the preceding. One or more applications may be managed by an application manager. Media maintained within applications can include data such as user recorded prompts for voicemail applications, messages from other users, or other appropriate information.

    [0030] Hardware-specific applications 58 include programs for controlling hardware 62. Examples of hardware-specific applications 58 include native services or a native operating systems. Hardware 50 may refer to electronic, mechanical, or electromechanical components of endpoint 12. According to the illustrated embodiment, hardware 50 includes a processor 70 and a memory 72. Processor 50 manipulates data to control the operation of endpoint 12. Memory 72 stores and facilitates retrieval of information used by the processor, and may include random access memory (RAM), read only memory (ROM), magnetic drives, disk drives, compact disk (CD) drives, digital video disk (DVD) drives, removable media storage, any other suitable data storage device, or a combination of any of the preceding.

    [0031] According to the illustrated embodiment, memory 72 stores proxy data 74. Proxy data 74 includes information that allows endpoint to provide proxy server features. For example, proxy data 74 may include a routing table that allows endpoint to establish communication sessions among endpoints 12. Memory 72 may also store feature logic. As an example, endpoint 12 may maintain a limited set of commonly used web pages within memory 72 and request other web pages from server 16.

    [0032] Hardware 50 may include other suitable components, for example, interface modules and signal processing modules. Interface modules may include user interface modules and network interface modules. User interface modules provide for the exchange of information with users of endpoint 12, and may include a speaker, a microphone, a display, an input interface, other module, or any combination of the preceding. A speaker generates audio signals, and a microphone receives and processes audio signals from a user. A display presents information to a user, and may include an LED, a graphical display, or other device for visually displaying or otherwise presenting information. An input interface represents any suitable element for receiving input from a user. For example, a user input interface may include a number keypad, one or more buttons referencing portions of display, a pointing device, other appropriate input interface, or any combination of the preceding.

    [0033] Network interface modules provide for communication between endpoint 12 and other equipment. For example, a network interface may link to switch 32 and provide for packet-based voice communications. A network interface may provide for coupling to any suitable communications equipment using any appropriate techniques and protocols. A network interface may support any appropriate wireless, wireline, or both wireless and wireline communications protocol.

    [0034] Signal processing modules provide for the manipulation and enhancement of signals. According to particular embodiments, signal processing modules may include digital signal processing capabilities for compression, echo cancellation, silence detection, or other appropriate signal processing.

    [0035] Modifications, additions, or omissions may be made to endpoint 12 without departing from the scope of the invention. The components of endpoint 12 may be integrated or separated according to particular needs. Moreover, the operations of endpoint 12 may be performed by more, fewer, or other modules. Additionally, operations of endpoint 12 may be performed using any suitable logic comprising software, hardware, other logic, or any suitable combination of the preceding.

    [0036] FIGURE 3 is a block diagram of one embodiment of service framework 50 of endpoint 12. Service framework 50 may allow endpoint 12 to provide proxy server features using any suitable method. An example method is described in more detail with reference to FIGURE 4.

    [0037] According to the illustrated embodiment, service framework 50 includes an endpoint object model 100, one or more state machines 104, a feature router 108, and feature finite state machines (FFSMs) 112 coupled as shown. Endpoint object model 100 includes objects that have platform logic that exposes interaction points or provides a supporting function. An object represents an aspect of endpoint 12, such as a component of endpoint 12. For example, an object may represent a ringer, device, line, call, or dialog. An event occurring at an object may initiate one or more states of endpoint 12.

    [0038] In general, a state machine tracks a current state and defines a next state according to a state process. A state process may refer to a process that defines the next state given a previous state and other conditions, and may be described using a state diagram. A state machine loads and executes instructions of a state process to implement the state process.

    [0039] A state machine 104 is associated with an endpoint object defined by endpoint object model 100. In the illustrated embodiment, routing state machine 104 tracks the current state of phone platform 54 and defines the next state according to an endpoint state process. An endpoint state process refers to a state process that controls the operation of endpoint 12. An endpoint state process may include a feature interaction point (FIP), which refers to a point of the state process at which feature router 108 may intercept the state process and provide a response.

    [0040] According to the illustrated embodiment, a state diagram 120 indicates that state i is followed by a feature interaction point. Feature router 108 intercepts the process at the feature interaction point, routes the intercept to one or more feature finite state machines, determines a response from the feature finite state machines, and provides the response. Depending upon the response, the next state may be state j or state k. Example routing state machines 104 include device, line, call, and dialog state machines.

    [0041] Feature router 108 coordinates feature finite state machines 100 and routing state machines 112 to provide features. Feature router 108 intercepts a state process and provides a response. Feature router 108 may determine the response according to instructions provided by feature finite state machines 112, and resolve conflicts between contradictory instructions.

    [0042] Feature finite state machines 112 are state machines that provide instructions to implement features. A feature finite state machine 112 is notified of the current state of an endpoint state process occurring at routing state machine 104, and defines the next state according a feature state process. A feature state process may refer to a process that provides a telephony feature such as a proxy server feature.

    [0043] According to one embodiment of operation, feature finite state machines 112 register with feature router 108 to obtain an intercept at a specific point of a state process managed by routing state machines 104. Feature finite state machines 112 may be allowed to register for notification at specific feature interaction points. When the specific point occurs, state machine 104 provides an intercept to feature router 108, which in turn notifies feature finite state machines 112. In response, feature finite state machines 112 provide instructions to feature router 108. Feature router 108 determines a response for the event.

    [0044] In certain situations, feature router 108 may receive conflicting instructions from feature finite state machines 112. Feature router 108 may resolve the conflict to determine the response according to the priority of the features. Feature router 108 then sends the response to state machine 104.

    [0045] Modifications, additions, or omissions may be made to service framework 50 without departing from the scope of the invention. The components of service framework 50 may be integrated or separated according to particular needs. Moreover, the operations of service framework 50 may be performed by more, fewer, or other modules. For example, the operations of feature router 108 may be performed by more than one module. Additionally, operations of service framework 50 may be performed using any suitable logic comprising software, hardware, other logic, or any suitable combination of the preceding.

    [0046] FIGURE 4 is a flowchart of one embodiment of a method for providing a proxy server feature using endpoint 12 of FIGURE 1. According to the embodiment, endpoint 12a operates as a proxy server for endpoints 12a-c. Proxy server endpoint 12a has a service framework 50 that includes a feature finite state machine 112 that provides proxy server features. Any combination of endpoints 12, however, may operate as proxy servers for system 10.

    [0047] The method begins at step 200, where endpoints 12 locate proxy server endpoint 12a. Endpoints 12 may locate proxy server endpoint 12a using any suitable discovery procedure such as a standard SIP proxy discovery protocol. Endpoints 12 register with proxy server endpoint 12a at step 202. Endpoints 12 may register by providing proxy server endpoint 12a with registration information such as IP addresses. According to one embodiment, proxy server endpoint 12a may instruct endpoints 12 to provide the registration information by providing endpoints 12b-c with web pages having commands instructing endpoints 12b-c to provide the information.

    [0048] Proxy server endpoint 12a stores the registration information at step 204. According to one embodiment, proxy server endpoint 12a may store the information in a routing table of proxy data 74 stored in memory 72 of endpoint 12a. The routing table may associate each endpoint 12a-c with its registration information. For example, the routing table may associate endpoint 12b with the IP address of 12b, and may associate endpoint 12c with the IP address for 12c.

    [0049] A caller endpoint 12b initiates a session with callee endpoint 12c at step 208. According to one embodiment, web pages may instruct caller endpoint 12b to initiate a session by sending an invite message to proxy server endpoint 12a. Proxy server endpoint 12a locates callee endpoint 12c at step 212. For example, proxy server endpoint 12a may locate callee endpoint 12c using a routing table associating callee endpoint 12c with the IP address for endpoint 12c.

    [0050] The connection is established at step 216. For example, proxy server endpoint 12a may forward the invite message to callee endpoint 12c. Callee endpoint 12c may then send a response message to proxy server endpoint 12a, which forwards the response message to caller endpoint 12b. Alternatively, callee endpoint 12c may send the response directly to caller endpoint 12b. After establishing the connection, the method terminates.

    [0051] Modifications, additions, or omissions may be made to the method without departing from the scope of the invention. The method may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order without departing from the scope of the invention.

    [0052] FIGURE 5 is a flowchart of one embodiment of a method for providing a proxy server feature using endpoints 12 of FIGURE 1. According to the embodiment, each endpoint 12 has a service framework 50 that includes a feature finite state machine 112 that provides proxy server features. Any combination of endpoints 12, however, may operate as proxy servers for system 10.

    [0053] The method begins at step 300, where endpoints 12 discover other endpoints 12. Endpoints 12 may discover other endpoints 12 using any suitable discovery procedure such as a zero configuration networking (zeroconf) procedure. For example, endpoints 12 may broadcast their registration information, such as IP addresses, to the other endpoints 12. According to one embodiment, endpoints 12 may have feature logic instructing them to broadcast their registration information during initialization.

    [0054] Endpoints 12 store the registration information of the other endpoints 12 at step 304. According to one embodiment, an endpoint 12 may store the information in a routing table of proxy data 74 stored in memory 72 of endpoint 12. A caller endpoint 12b locates callee endpoint 12c at step 308. For example, caller endpoint 12b may locate callee endpoint 12c using the routing table.

    [0055] Caller endpoint initiates a session with callee endpoint 12c at step 312. Caller endpoint 12b may initiate a session in accordance with feature logic. The connection is established at step 316. For example, callee endpoint 12c may send a response to caller endpoint 12b to establish the session. After establishing the connection, the method terminates.

    [0056] Modifications, additions, or omissions may be made to the method without departing from the scope of the invention. The method may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order without departing from the scope of the invention.

    [0057] Certain embodiments of the invention may provide one or more technical advantages. A technical advantage of one embodiment may be that one or more endpoints may each have a proxy server feature. The proxy server feature may allow an endpoint to operate as a proxy server. Another technical advantage of one embodiment may be that a service framework of an endpoint provides a proxy server feature. The service framework may access a web page comprising feature logic defining the proxy server feature. The web page may be executed to readily provide the proxy server feature.

    [0058] While this disclosure has been described in terms of certain embodiments and generally associated methods, alterations and permutations of the embodiments and methods will be apparent to those skilled in the art. Accordingly, the above description of example embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the scope of this disclosure, as defined by the following claims.


    Claims

    1. A method for providing a proxy server feature in a communications network (10) comprising a plurality of user endpoints (12), wherein the proxy server feature comprises executable feature logic for mediating communications between user endpoints; and wherein the user endpoints are communications devices having user interfaces for exchange of information with users of the endpoints, characterised in that:
    a first user endpoint (12a) of the plurality of user endpoints is operable to provide the proxy server feature to one or more other user endpoints (12b, 12c) of the plurality of user endpoints, the method comprising:

    initiating the proxy server feature at the first user endpoint;

    receiving at the first user endpoint, from the other user endpoints, registration information corresponding to the other user endpoints, the registration information corresponding to an endpoint comprising an address for the endpoint;

    storing the registration information in a routing table at the first user endpoint;

    receiving, at the first user endpoint, an invite message from a caller endpoint of the other user endpoints to initiate a session with a callee endpoint;

    in response to receiving the invite message, locating, by the first user endpoint, the callee endpoint using the routing table; and

    forwarding the invite message to the callee endpoint in order to establish the session with the callee endpoint.


     
    2. The method of Claim 1, wherein:

    each user endpoint of the plurality of user endpoints is operable to provide the proxy server feature; and

    receiving registration information corresponding to the plurality of user endpoints further comprises:
    broadcasting registration information from the first user endpoint to one or more other user endpoints of the plurality of user endpoints.


     
    3. The method of Claim 1, wherein:

    each user endpoint of the plurality of user endpoints is operable to provide the proxy server feature; and

    receiving registration information corresponding to the plurality of user endpoints further comprises:

    receiving at the first user endpoint registration information from a second user endpoint of the plurality of user endpoints; and

    providing the registration information to a third user endpoint of the plurality of user endpoints.


     
    4. The method of Claim 1, wherein:

    the first user endpoint comprises a primary endpoint; and

    the plurality of user endpoints comprises a secondary endpoint operable to provide the proxy server feature if the primary endpoint fails to provide the proxy server feature.


     
    5. The method of Claim 1, wherein receiving registration information corresponding to the plurality of user endpoints further comprises:
    instructing the other user endpoints to register at the first user endpoint.
     
    6. The method of Claim 1, wherein initiating the proxy server feature at the first user endpoint of the plurality of user endpoints further comprises:

    accessing the feature logic using a service framework (50) at the first user endpoint, the feature logic defining the proxy server feature; and

    initiating the proxy server feature by executing the feature logic.


     
    7. A first user endpoint (12a) of a plurality of user endpoints (12) of a communications network, wherein the user endpoints are communications devices having user interfaces for exchange of information with users of the endpoints, characterised in that the first user endpoint is operable to provide a proxy server feature to one or more other user endpoints (12b, 12c) of the plurality of user endpoints, the first user endpoint comprising:

    a memory (72) operable to store a routing table; and

    a processor (70) coupled to the memory and operable to:

    initiate a proxy server feature, wherein the proxy server feature comprises executable feature logic for mediating communications between user endpoints;

    receive from the other user endpoints registration information corresponding to the other user endpoints, the registration information corresponding to an endpoint comprising an address for the endpoint;

    record the registration information in the routing table;

    receive an invite message from a caller endpoint of the other user endpoints to initiate a session with a callee endpoint;

    in response to receiving the invite message, locate the callee endpoint using the routing table; and

    forward the invite message to the callee endpoint in order to establish the session with the callee endpoint.


     
    8. The endpoint of Claim 7, wherein:

    each user endpoint of the plurality of user endpoints is operable to provide the proxy server feature; and

    the processor is further operable to receive registration information corresponding to the plurality of user endpoints by:
    broadcasting registration information from the first user endpoint to one or more other user endpoints of the plurality of endpoints.


     
    9. The endpoint of Claim 7, wherein:

    each user endpoint of the plurality of user endpoints is operable to provide the proxy server feature; and

    the processor is further operable to receive registration information corresponding to the plurality of endpoints by:

    receiving at the first user endpoint registration information from a second user endpoint of the plurality of user endpoints; and

    providing the registration information to a third user endpoint of the plurality of user endpoints.


     
    10. The endpoint of Claim 7, wherein:

    the first user endpoint comprises a primary endpoint; and

    the plurality of endpoints comprises a secondary endpoint operable to provide the proxy server feature if the primary endpoint fails to provide the proxy server feature.


     
    11. The endpoint of Claim 7, wherein the processor is further operable to receive registration information corresponding to the plurality of user endpoints by:
    instructing the other user endpoints to register at the first user endpoint.
     
    12. The endpoint of Claim 7, wherein the processor is further operable to initiate the proxy server feature by:

    accessing the feature logic using a service framework (50) at the first user endpoint, the feature logic defining the proxy server feature; and

    initiating the proxy server feature by executing the feature logic.


     
    13. Logic for providing a proxy server feature, the logic embodied in a medium and operable to perform a method according to any of claims 1 to 6.
     
    14. A system for providing a proxy server feature, comprising:
    a plurality of user endpoints (12), wherein the user endpoints are communications devices having user interfaces for exchange of information with users of the endpoints, each user endpoint operable to provide registration information, the registration information corresponding to an endpoint comprising an address for the endpoint; and characterised in comprising:
    a first user endpoint (12a) of the plurality of user endpoints operable to provide the proxy server feature to one or more other user endpoints (12b, 12c) of the plurality of user endpoints, the first user endpoint operable to:

    initiate the proxy server feature, wherein the proxy server feature comprises executable feature logic for mediating communications between user endpoints;

    receive from the other user endpoints the registration information corresponding to the other user endpoints;

    record the registration information in a routing table;

    receive an invite message from a caller endpoint of the other user endpoints to initiate a session with a callee endpoint;

    in response to receiving the invite message, locate the callee endpoint using the routing table; and

    forward the invite message to the callee endpoint in order to establish the session with the callee endpoint.


     
    15. The system of Claim 14, wherein each user endpoint of the plurality of endpoints is operable to broadcast registration information to the other user endpoints of the plurality of user endpoints.
     
    16. The system of Claim 14, wherein each user endpoint of the plurality of user endpoints is operable to provide the proxy server feature by receiving registration information from the first user endpoint.
     
    17. The system of Claim 14, wherein:

    the first user endpoint comprises a primary endpoint; and

    the plurality of user endpoints comprises a secondary endpoint operable to provide the proxy server feature if the primary endpoint fails to provide the proxy server feature.


     
    18. The system of Claim 14, wherein the first user endpoint is operable to instruct the other user endpoints to register at the first user endpoint.
     


    Ansprüche

    1. Verfahren zum Bereitstellen eines Proxy-Server-Feature in einem eine Vielzahl von Benutzerendpunkten (12) umfassenden Kommunikationsnetz (10), wobei das Proxy-Server-Feature ausführbare Feature-Logik zum Vermitteln der Kommunikation zwischen Benutzerendpunkten umfasst; und wobei es sich bei den Benutzerendpunkten um Kommunikationsvorrichtungen handelt, die Benutzerschnittstellen zum Austausch von Informationen mit Benutzern der Endpunkte aufweisen, dadurch gekennzeichnet, dass:
    ein erster Benutzerendpunkt (12a) der Vielzahl von Benutzerendpunkten betreibbar ist, um das Proxy-Server-Feature für einen oder mehrere andere Benutzerendpunkte (12b, 12c) der Vielzahl von Benutzerendpunkten bereitzustellen, wobei das Verfahren Folgendes umfasst:

    Initiieren des Proxy-Server-Feature an dem ersten Benutzerendpunkt;

    Empfangen, an dem ersten Benutzerendpunkt, von den anderen Benutzerendpunkten her, von den anderen Benutzerendpunkten entsprechenden Registrierungsinformationen, wobei die einem Endpunkt entsprechenden Registrierungsinformationen eine Adresse für den Endpunkt umfassen;

    Speichern der Registrierungsinformationen in einer Routingtabelle an dem ersten Benutzerendpunkt;

    Empfangen, an dem ersten Benutzerendpunkt, einer Einladungsnachricht von einem Endpunkt des Anrufers der anderen Benutzerendpunkte her, um eine Sitzung mit einem Endpunkt eines Angerufenen zu initiieren;

    als Reaktion auf das Empfangen der Einladungsnachricht, Auffinden, durch den ersten Benutzerendpunkt, des Endpunkts eines Angerufenen unter Verwendung der Routingtabelle; und

    Weiterleiten der Einladungsnachricht zu dem Endpunkt eines Angerufenen, um die Sitzung mit dem Endpunkt eines Angerufenen aufzubauen.


     
    2. Verfahren nach Anspruch 1, wobei:

    jeder Benutzerendpunkt der Vielzahl von Benutzerendpunkten betreibbar ist, um das Proxy-Server-Feature bereitzustellen; und

    das Empfangen von der Vielzahl von Benutzerendpunkten entsprechenden Registrierungsinformationen weiter Folgendes umfasst:
    Aussenden von Registrierungsinformationen von dem ersten Benutzerendpunkt her zu einem oder mehreren anderen Benutzerendpunkten der Vielzahl von Benutzerendpunkten.


     
    3. Verfahren nach Anspruch 1, wobei:

    jeder Benutzerendpunkt der Vielzahl von Benutzerendpunkten betreibbar ist, um das Proxy-Server-Feature bereitzustellen; und

    das Empfangen von der Vielzahl von Benutzerendpunkten entsprechenden Registrierungsinformationen weiter Folgendes umfasst:

    Empfangen, an dem ersten Benutzerendpunkt, von Registrierungsinformationen von einem zweiten Benutzerendpunkt der Vielzahl von Benutzerendpunkten her; und

    Bereitstellen der Registrierungsinformationen für einen dritten Benutzerendpunkt der Vielzahl von Benutzerendpunkten.


     
    4. Verfahren nach Anspruch 1, wobei:

    der erste Benutzerendpunkt einen Primärendpunkt umfasst; und

    die Vielzahl von Benutzerendpunkten einen Sekundärendpunkt umfasst, der betreibbar ist, um das Proxy-Server-Feature bereitzustellen, falls der Primärendpunkt das Proxy-Server-Feature nicht bereitstellt.


     
    5. Verfahren nach Anspruch 1, wobei das Empfangen von der Vielzahl von Benutzerendpunkten entsprechenden Registrierungsinformationen weiter Folgendes umfasst:
    Anweisen der anderen Benutzerendpunkte, sich an dem ersten Benutzerendpunkt zu registrieren.
     
    6. Verfahren nach Anspruch 1, wobei das Initiieren des Proxy-Server-Feature an dem ersten Benutzerendpunkt der Vielzahl von Benutzerendpunkten weiter Folgendes umfasst:

    Zugreifen auf die Feature-Logik unter Verwendung eines Service-Framework (50) an dem ersten Benutzerendpunkt, wobei die Feature-Logik das Proxy-Server-Feature definiert; und

    Initiieren des Proxy-Server-Feature durch Ausführen der Feature-Logik.


     
    7. Erster Benutzerendpunkt (12a) einer Vielzahl von Benutzerendpunkten (12) eines Kommunikationsnetzes, wobei es sich bei den Benutzerendpunkten um Kommunikationsvorrichtungen handelt, die Benutzerschnittstellen zum Austausch von Informationen mit Benutzern der Endpunkte aufweisen, dadurch gekennzeichnet, dass der erste Benutzerendpunkt betreibbar ist, um ein Proxy-Server-Feature für einen oder mehr andere Benutzerendpunkte (12b, 12c) der Vielzahl von Benutzerendpunkten bereitzustellen, wobei der erste Benutzerendpunkt Folgendes umfasst:

    einen Speicher (72) der betreibbar ist, um eine Routingtabelle zu speichern; und

    einen Prozessor (70), der an den Speicher gekoppelt ist und betreibbar ist, um:

    ein Proxy-Server-Feature zu initiieren, wobei das Proxy-Server-Feature ausführbare Feature-Logik zum Vermitteln der Kommunikation zwischen Benutzerendpunkten umfasst;

    von den anderen Benutzerendpunkten her den anderen Benutzerendpunkten entsprechende Registrierungsinformationen zu empfangen, wobei die einem Endpunkt entsprechenden Registrierungsinformationen eine Adresse für den Endpunkt umfassen;

    die Registrierungsinformationen in der Routingtabelle aufzuzeichnen;

    eine Einladungsnachricht von einem Endpunkt des Anrufers der anderen Benutzerendpunkte her zu empfangen, um eine Sitzung mit einem Endpunkt eines Angerufenen zu initiieren;

    als Reaktion auf das Empfangen der Einladungsnachricht den Endpunkt eines Angerufenen unter Verwendung der Routingtabelle aufzufinden; und

    die Einladungsnachricht zu dem Endpunkt eines Angerufenen weiterzuleiten, um die Sitzung mit dem Endpunkt eines Angerufenen aufzubauen.


     
    8. Endpunkt nach Anspruch 7, wobei:

    jeder Benutzerendpunkt der Vielzahl von Benutzerendpunkten betreibbar ist, um das Proxy-Server-Feature bereitzustellen; und

    der Prozessor weiter betreibbar ist, um der Vielzahl von Benutzerendpunkten entsprechende Registrierungsinformationen zu empfangen, indem er:
    Registrierungsinformationen von dem ersten Benutzerendpunkt her zu einem oder mehreren anderen Benutzerendpunkten der Vielzahl von Benutzerendpunkten aussendet.


     
    9. Endpunkt nach Anspruch 7, wobei:

    jeder Benutzerendpunkt der Vielzahl von Benutzerendpunkten betreibbar ist, um das Proxy-Server-Feature bereitzustellen; und

    der Prozessor weiter betreibbar ist, um der Vielzahl von Endpunkten entsprechende Registrierungsinformationen zu empfangen, indem er:

    an dem ersten Benutzerendpunkt, Registrierungsinformationen von einem zweiten Benutzerendpunkt der Vielzahl von Benutzerendpunkten her empfängt; und

    die Registrierungsinformationen für einen dritten Benutzerendpunkt der Vielzahl von Benutzerendpunkten bereitstellt.


     
    10. Endpunkt nach Anspruch 7, wobei:

    der erste Benutzerendpunkt einen Primärendpunkt umfasst; und

    die Vielzahl von Endpunkten einen Sekundärendpunkt umfasst, der betreibbar ist, um das Proxy-Server-Feature bereitzustellen, falls der Primärendpunkt das Proxy-Server-Feature nicht bereitstellt.


     
    11. Endpunkt nach Anspruch 7, wobei der Prozessor weiter betreibbar ist, um der Vielzahl von Benutzerendpunkten entsprechende Registrierungsinformationen zu empfangen, indem er:
    die anderen Benutzerendpunkte anweist, sich an dem ersten Benutzerendpunkt zu registrieren.
     
    12. Endpunkt nach Anspruch 7, wobei der Prozessor weiter betreibbar ist, um das Proxy-Server-Feature zu initiieren, indem er:

    unter Verwendung eines Service-Framework (50) an dem ersten Benutzerendpunkt auf die Feature-Logik zugreift, wobei die Feature-Logik das Proxy-Server-Feature definiert; und

    das Proxy-Server-Feature durch Ausführen der Feature-Logik initiiert.


     
    13. Logik zum Bereitstellen eines Proxy-Server-Feature, wobei die Logik in einem Medium verkörpert ist und betreibbar ist, um ein Verfahren nach einem der Ansprüche 1 bis 6 auszuführen.
     
    14. System zum Bereitstellen eines Proxy-Server-Feature, das Folgendes umfasst:

    eine Vielzahl von Benutzerendpunkten (12), wobei es sich bei den Benutzerendpunkten um Kommunikationsvorrichtungen handelt, die Benutzerschnittstellen für den Austausch von Informationen mit Benutzern der Endpunkte aufweisen, wobei jeder Benutzerendpunkt betreibbar ist, um Registrierungsinformationen bereitzustellen, wobei die einem Endpunkt entsprechenden Registrierungsinformationen eine Adresse für den Endpunkt umfassen; und dadurch gekennzeichnet, dass es Folgendes umfasst:

    einen ersten Benutzerendpunkt (12a) der Vielzahl von Benutzerendpunkten, der betreibbar ist, um das Proxy-Server-Feature für einen oder mehrere andere Benutzerendpunkte (12b, 12c) der Vielzahl von Benutzerendpunkten bereitzustellen, wobei der erste Benutzerendpunkt betreibbar ist, um:

    das Proxy-Server-Feature zu initiieren, wobei das Proxy-Server-Feature ausführbare Feature-Logik zum Vermitteln der Kommunikation zwischen Benutzerendpunkten umfasst;

    von den anderen Benutzerendpunkten her die den anderen Benutzerendpunkten entsprechenden Registrierungsinformationen zu empfangen;

    die Registrierungsinformationen in einer Routingtabelle aufzuzeichnen;

    eine Einladungsnachricht von einem Endpunkt des Anrufers der anderen Benutzerendpunkte her zu empfangen, um eine Sitzung mit einem Endpunkt eines Angerufenen zu initiieren;

    als Reaktion auf das Empfangen der Einladungsnachricht den Endpunkt eines Angerufenen unter Verwendung der Routingtabelle aufzufinden; und

    die Einladungsnachricht zu dem Endpunkt eines Angerufenen weiterzuleiten, um die Sitzung mit dem Endpunkt eines Angerufenen aufzubauen.


     
    15. System nach Anspruch 14, wobei jeder Benutzerendpunkt der Vielzahl von Endpunkten betreibbar ist, um Registrierungsinformationen zu den anderen Benutzerendpunkten der Vielzahl von Benutzerendpunkten auszusenden.
     
    16. System nach Anspruch 14, wobei jeder Benutzerendpunkt der Vielzahl von Benutzerendpunkten betreibbar ist, um durch Empfangen von Registrierungsinformationen von dem ersten Benutzerendpunkt her das Proxy-Server-Feature bereitzustellen.
     
    17. System nach Anspruch 14, wobei:

    der erste Benutzerendpunkt einen Primärendpunkt umfasst; und

    die Vielzahl von Benutzerendpunkten einen Sekundärendpunkt umfasst, der betreibbar ist, um das Proxy-Server-Feature bereitzustellen, falls der Primärendpunkt das Proxy-Server-Feature nicht bereitstellt.


     
    18. System nach Anspruch 14, wobei der erste Benutzerendpunkt betreibbar ist, um die anderen Benutzerendpunkte anzuweisen, sich an dem ersten Benutzerendpunkt zu registrieren.
     


    Revendications

    1. Procédé pour fournir une fonction de serveur mandataire dans un réseau de communication (10) comprenant une pluralité de points d'extrémité d'utilisateurs (12), dans lequel la fonction de serveur mandataire comprend une logique de fonction exécutable pour médier des communications entre des points d'extrémité d'utilisateurs ; et dans lequel les points d'extrémité d'utilisateurs sont des dispositifs de communication ayant des interfaces utilisateurs pour l'échange d'informations avec des utilisateurs des points d'extrémité, caractérisé en ce que :
    un premier point d'extrémité d'utilisateur (12a) de la pluralité de points d'extrémité d'utilisateurs peut être mis en oeuvre pour fournir la fonction de serveur mandataire à un ou plusieurs autres points d'extrémité d'utilisateurs (12b, 12c) de la pluralité de points d'extrémité d'utilisateurs, le procédé comprenant de :

    initier la fonction de serveur mandataire au niveau du premier point d'extrémité d'utilisateur ;

    recevoir au niveau du premier point d'extrémité d'utilisateur, à partir des autres points d'extrémité d'utilisateurs, des informations d'enregistrement correspondant aux autres points d'extrémité d'utilisateurs, les informations d'enregistrement correspondant à un point d'extrémité comprenant une adresse pour le point d'extrémité ;

    stocker les informations d'enregistrement dans une table de routage au niveau du premier point d'extrémité d'utilisateur ;

    recevoir, au niveau du premier point d'extrémité d'utilisateur, un message d'invitation à partir d'un point d'extrémité appelant des autres points d'extrémité d'utilisateurs pour initier une session avec un point d'extrémité appelé ;

    en réponse à la réception du message d'invitation, localiser, par le premier point d'extrémité d'utilisateur, le point d'extrémité appelé en utilisant la table de routage ; et

    transmettre le message d'invitation au point d'extrémité appelé afin d'établir la session avec le point d'extrémité appelé.


     
    2. Procédé selon la revendication 1, dans lequel :

    chaque point d'extrémité d'utilisateur de la pluralité de points d'extrémité d'utilisateurs peut être mis en oeuvre pour fournir la fonction de serveur mandataire ; et

    la réception d'informations d'enregistrement correspondant à la pluralité de points d'extrémité d'utilisateurs comprend en outre de :
    diffuser des informations d'enregistrement à partir du premier point d'extrémité d'utilisateur vers un ou plusieurs autres points d'extrémité d'utilisateurs de la pluralité de points d'extrémité d'utilisateurs.


     
    3. Procédé selon la revendication 1, dans lequel :

    chaque point d'extrémité d'utilisateur de la pluralité de points d'extrémité d'utilisateurs peut être mis en oeuvre pour fournir la fonction de serveur mandataire ; et

    la réception d'informations d'enregistrement correspondant à la pluralité de points d'extrémité d'utilisateurs comprend en outre de :

    recevoir au niveau du premier point d'extrémité d'utilisateur des informations d'enregistrement à partir d'un second point d'extrémité d'utilisateur de la pluralité de points d'extrémité d'utilisateurs ; et

    fournir les informations d'enregistrement à un troisième point d'extrémité d'utilisateur de la pluralité de points d'extrémité d'utilisateurs.


     
    4. Procédé selon la revendication 1, dans lequel :

    le premier point d'extrémité d'utilisateur comprend un point d'extrémité principal ; et

    la pluralité de points d'extrémité d'utilisateurs comprend un point d'extrémité secondaire pouvant être mis en oeuvre pour fournir la fonction de serveur mandataire si le point d'extrémité principal ne parvient pas à fournir la fonction de serveur mandataire.


     
    5. Procédé selon la revendication 1, dans lequel la réception d'informations d'enregistrement correspondant à la pluralité de points d'extrémité d'utilisateurs comprend en outre de :
    ordonner aux autres points d'extrémité d'utilisateurs de s'enregistrer au niveau du premier point d'extrémité d'utilisateur.
     
    6. Procédé selon la revendication 1, dans lequel l'initiation de la fonction de serveur mandataire au niveau du premier point d'extrémité d'utilisateur de la pluralité de points d'extrémité d'utilisateurs comprend en outre de :

    accéder à la logique de fonction en utilisant une structure de service (50) au niveau du premier point d'extrémité d'utilisateur, la logique de fonction définissant la fonction de serveur mandataire ; et

    initier la fonction de serveur mandataire en exécutant la logique de fonction.


     
    7. Premier point d'extrémité d'utilisateur (12a) d'une pluralité de points d'extrémité d'utilisateurs (12) d'un réseau de communication, dans lequel les points d'extrémité d'utilisateurs sont des dispositifs de communication ayant des interfaces utilisateurs pour l'échange d'informations avec des utilisateurs des points d'extrémité, caractérisé en ce que le premier point d'extrémité d'utilisateur peut être mis en oeuvre pour fournir une fonction de serveur mandataire à un ou plusieurs autres points d'extrémité d'utilisateurs (12b, 12c) de la pluralité de points d'extrémité d'utilisateurs, le premier point d'extrémité d'utilisateur comprenant :

    une mémoire (72) pouvant être mise en oeuvre pour stocker une table de routage ; et

    un processeur (70) couplé à la mémoire et pouvant être mis en oeuvre pour :

    initier une fonction de serveur mandataire, dans lequel la fonction de serveur mandataire comprend une logique de fonction exécutable pour la médiation de communications entre des points d'extrémité d'utilisateurs ;

    recevoir à partir des autres points d'extrémité d'utilisateurs, des informations d'enregistrement correspondant aux autres points d'extrémité d'utilisateurs, les informations d'enregistrement correspondant à un point d'extrémité comprenant une adresse pour le point d'extrémité ;

    enregistrer les informations d'enregistrement dans la table de routage ;

    recevoir un message d'invitation à partir d'un point d'extrémité appelant des autres points d'extrémité d'utilisateurs pour initier une session avec un point d'extrémité appelé ;

    en réponse à la réception du message d'invitation, localiser le point d'extrémité appelé en utilisant la table de routage ; et

    transmettre le message d'invitation au point d'extrémité appelé afin d'établir la session avec le point d'extrémité appelé.


     
    8. Point d'extrémité selon la revendication 7, dans lequel :

    chaque point d'extrémité d'utilisateur de la pluralité de points d'extrémité d'utilisateurs peut être mis en oeuvre pour fournir la fonction de serveur mandataire ; et

    le processeur peut en outre être mis en oeuvre pour recevoir des informations d'enregistrement correspondant à la pluralité de points d'extrémité d'utilisateurs en :
    diffusant des informations d'enregistrement à partir du premier point d'extrémité d'utilisateur vers un ou plusieurs autres points d'extrémité d'utilisateurs de la pluralité de points d'extrémité d'utilisateurs.


     
    9. Point d'extrémité selon la revendication 7, dans lequel :

    chaque point d'extrémité d'utilisateur de la pluralité de points d'extrémité d'utilisateurs peut être mis en oeuvre pour fournir la fonction de serveur mandataire ; et

    le processeur peut en outre être mis en oeuvre pour recevoir des informations d'enregistrement correspondant à la pluralité de points d'extrémité en :

    recevant au niveau du premier point d'extrémité d'utilisateur des informations d'enregistrement à partir d'un second point d'extrémité d'utilisateur de la pluralité de points d'extrémité d'utilisateurs ; et en

    fournissant les informations d'enregistrement à un troisième point d'extrémité d'utilisateur de la pluralité de points d'extrémité d'utilisateurs.


     
    10. Point d'extrémité selon la revendication 7, dans lequel :

    le premier point d'extrémité d'utilisateur comprend un point d'extrémité principal ; et

    la pluralité de points d'extrémité comprend un point d'extrémité secondaire pouvant être mis en oeuvre pour fournir la fonction de serveur mandataire si le point d'extrémité principal ne parvient pas à fournir la fonction de serveur mandataire.


     
    11. Point d'extrémité selon la revendication 7, dans lequel le processeur peut en outre être mis en oeuvre pour recevoir des informations d'enregistrement correspondant à la pluralité de points d'extrémité d'utilisateurs en :
    ordonnant aux autres points d'extrémité d'utilisateurs de s'enregistrer au niveau du premier point d'extrémité d'utilisateur.
     
    12. Point d'extrémité selon la revendication 7, dans lequel le processeur peut en outre être mis en oeuvre pour initier la fonction de serveur mandataire en :

    accédant à la logique de fonction en utilisant une structure de service (50) au niveau du premier point d'extrémité d'utilisateur, la logique de fonction définissant la fonction de serveur mandataire ; et en

    initiant la fonction de serveur mandataire en exécutant la logique de fonction.


     
    13. Logique pour fournir une fonction de serveur mandataire, la logique étant incorporée sur un support et pouvant être mise en oeuvre pour exécuter un procédé selon l'une quelconque des revendications 1 à 6.
     
    14. Système pour fournir une fonction de serveur mandataire, comprenant :
    une pluralité de points d'extrémité d'utilisateurs (12), dans lequel les points d'extrémité d'utilisateurs sont des dispositifs de communication ayant des interfaces utilisateurs pour l'échange d'informations avec des utilisateurs des points d'extrémité, chaque point d'extrémité d'utilisateur pouvant être mis en oeuvre pour fournir des informations d'enregistrement, les informations d'enregistrement correspondant à un point d'extrémité comprenant une adresse pour le point d'extrémité ; et caractérisé en ce qu'il comprend :
    un premier point d'extrémité d'utilisateur (12a) de la pluralité de points d'extrémité d'utilisateurs pouvant être mis en oeuvre pour fournir la fonction de serveur mandataire à un ou plusieurs autres points d'extrémité d'utilisateurs (12b, 12c) de la pluralité de points d'extrémité d'utilisateurs, le premier point d'extrémité d'utilisateur pouvant être mis en oeuvre pour :

    initier la fonction de serveur mandataire, dans lequel la fonction de serveur mandataire comprend une logique de fonction exécutable pour médier des communications entre des points d'extrémité d'utilisateurs ;

    recevoir à partir des autres points d'extrémité d'utilisateurs les informations d'enregistrement correspondant aux autres points d'extrémité d'utilisateurs ;

    enregistrer les informations d'enregistrement dans une table de routage ;

    recevoir un message d'invitation à partir d'un point d'extrémité appelant des autres points d'extrémité d'utilisateurs pour initier une session avec un point d'extrémité appelé ;

    en réponse à la réception du message d'invitation, localiser le point d'extrémité appelé en utilisant la table de routage ; et

    transmettre le message d'invitation au point d'extrémité appelé afin d'établir la session avec le point d'extrémité appelé.


     
    15. Système selon la revendication 14, dans lequel chaque point d'extrémité d'utilisateur de la pluralité de points d'extrémité peut être mis en oeuvre pour diffuser des informations d'enregistrement aux autres points d'extrémité d'utilisateurs de la pluralité de points d'extrémité d'utilisateurs.
     
    16. Système selon la revendication 14, dans lequel chaque point d'extrémité d'utilisateur de la pluralité de points d'extrémité d'utilisateurs peut être mis en oeuvre pour fournir la fonction de serveur mandataire en recevant des informations d'enregistrement à partir du premier point d'extrémité d'utilisateur.
     
    17. Système selon la revendication 14, dans lequel :

    le premier point d'extrémité d'utilisateur comprend un point d'extrémité principal ; et

    la pluralité de points d'extrémité d'utilisateurs comprend un point d'extrémité secondaire pouvant être mis en oeuvre pour fournir la fonction de serveur mandataire si le point d'extrémité principal ne parvient pas à fournir la fonction de serveur mandataire.


     
    18. Système selon la revendication 14, dans lequel le premier point d'extrémité d'utilisateur peut être mis en oeuvre pour ordonner aux autres points d'extrémité d'utilisateurs de s'enregistrer auprès du premier point d'extrémité d'utilisateur.
     




    Drawing









    REFERENCES CITED IN THE DESCRIPTION



    This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

    Patent documents cited in the description