WO2014036903A1 - Efficient presence distribution mechanism for a large enterprise - Google Patents

Efficient presence distribution mechanism for a large enterprise Download PDF

Info

Publication number
WO2014036903A1
WO2014036903A1 PCT/CN2013/082394 CN2013082394W WO2014036903A1 WO 2014036903 A1 WO2014036903 A1 WO 2014036903A1 CN 2013082394 W CN2013082394 W CN 2013082394W WO 2014036903 A1 WO2014036903 A1 WO 2014036903A1
Authority
WO
WIPO (PCT)
Prior art keywords
presence information
information message
ring
server
local
Prior art date
Application number
PCT/CN2013/082394
Other languages
French (fr)
Inventor
Frederick P. Block
Dennis C. Episkopos
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to CN201380045307.7A priority Critical patent/CN104604189B/en
Priority to EP13835415.4A priority patent/EP2891279B1/en
Publication of WO2014036903A1 publication Critical patent/WO2014036903A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/01—Social networking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/42—Loop networks
    • H04L12/427—Loop networks with decentralised control
    • H04L12/433—Loop networks with decentralised control with asynchronous transmission, e.g. token ring, register insertion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/42—Loop networks
    • H04L12/437—Ring fault isolation or reconfiguration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42365—Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity
    • H04M3/42374—Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity where the information is provided to a monitoring entity such as a potential calling party or a call processing server

Definitions

  • the present invention relates to network communication, and, in particular, to efficient presence distribution mechanism for a large enterprise.
  • a network service which accepts, stores, and distributes presence information for a plurality of users may be referred to as a presence service.
  • a presence service may be implemented on one or more servers, for example arranged in some architecture or topology in the network.
  • a presence server in a network may be configured to receive and manage presence information from a user or client device, also referred to as a user equipment (UE) in some scenarios. Examples of a UE include smartphones, laptop computers, computer tablets, and desktop computers.
  • UE user equipment
  • a presence server may share the presence information of a user (on a UE) with other users (on one or more other UEs) that are authorized by the user to obtain such information either directly by sending the presence information to these other users or indirectly by sending the presence information to other presence servers which in turn distribute the presence information to other users .
  • the presence information indicates the status of the user on the network, such as the availability, ability, or willingness of the user to communicate with other users of the network. Presence information has wide application in many communication services, such as instant messaging, voice over Internet Protocol (IP), and social networking services or applications.
  • IP voice over Internet Protocol
  • a UE may display an indicator icon, for example corresponding to an instant messaging application, from a choice of graphic symbols with easy- to-convey meanings and a list of corresponding text descriptions of each of the states.
  • Common states that indicate the user's availability are “free for chat”, “busy”, “away”, “do not disturb”, and “out to lunch”. Such states exist in many variations across different instant messaging applications. Some applications also support a rich choice of additional presence attributes that can be used for presence information, such as user mood, location, or free text status.
  • clients send presence updates to one of a pool of servers, which then distributes updates to all of the user's subscribed contacts.
  • SIP Session Initiation Protocol
  • XMPP Extensible Messaging and Presence Protocol
  • the number of sent updates increases, e.g., proportionally, as the numbers of users, servers, and initiated updates increase, which can be substantial in larger networks (e.g., with hundred thousands of users) and incur substantial cost (e.g., in terms of used servers and resources). Reducing the number of used servers and/or sent presence information messages is desirable to reduce cost and improve efficiency (e.g., in terms of resource and network utilization).
  • the disclosure includes a method implemented in a network component, the method comprising receiving a presence information message from a presence server in a ring of a plurality of presence servers, removing content in the presence information message that is previously originated by the network component and previously sent on the ring, copying the presence information message locally for subsequent processing, appending to the presence information message buffered presence information from a local client coupled to the network component, and forwarding the presence information message to a second presence server in the ring.
  • the disclosure includes a method for forwarding presence information implemented in a presence server coupled to a plurality of presence servers in a ring architecture, the method comprising receiving a presence information message on a link from a second presence server in the plurality of presence servers, processing the presence information message, receiving a local presence information message from a local client coupled to the presence server, processing the local presence information message, and processing previously received and buffered presence information intended to one or more local clients coupled to the presence server, wherein the presence information message has a higher priority than the local presence information message and the previously received and buffered presence information.
  • the disclosure includes a network component for processing and forwarding presence information to a plurality of presence servers coupled via a ring in one or more networks and a plurality of user devices coupled to the presence server, the network component comprising a processor configured to receive a presence information message from a previous hop on the ring, process and forward the presence information message, receive a local presence information message from a user device coupled locally to the network component, buffer the local presence information message for subsequent processing and forwarding, and forward previously received and buffered presence information to one or more intended clients coupled to the network component wherein the presence information message has a higher priority than the local presence information message and previously received and buffered presence information, wherein the presence information message has a higher priority than the local presence information message and the previously received and buffered presence information.
  • the disclosure includes a computer program product in a non-transitory computer readable media comprising first instructions executable by a processor for receiving a presence information message from a presence server in a ring of a plurality of presence servers, second instructions executable by a processor for removing content in the presence information message that is previously originated by the network component and previously sent on the ring, third instructions executable by a processor for copying the presence information message locally for subsequent processing, fourth instructions executable by a processor for appending to the presence information message buffered presence information from a local client coupled to the network component, and fifth instructions executable by a processor for forwarding the presence information message to a second presence server in the ring.
  • FIG. 1 is a schematic diagram of a typical presence distribution fan-out architecture.
  • FIG. 2 is a schematic diagram of a presence distribution ring architecture according to an example embodiment of the disclosure.
  • FIG. 3 is a flowchart of a presence distribution method according to an example embodiment of the disclosure.
  • FIG. 4 is a schematic diagram of an example embodiment of a network unit.
  • FIG. 5 is a schematic diagram of an example embodiment of a general -purpose network component.
  • the presence information may be effectively broadcast to a set of presence servers arranged in a ring architecture.
  • the presence information for one or more users may be sent from server to server on the ring in a high priority message (at a first rate), and may be sent to the user's contacts at a lower priority (at a second lower rate).
  • this scheme may reduce the total number of messages exchanged and processed by a presence server by a factor of about two or more, e.g., in comparison to a fan-out distribution architecture, without substantially affecting operations. This may increase efficiency and reduce cost since fewer servers may be used to support a population of users as compared to previous presence information distribution architectures.
  • FIG. 1 illustrates a typical presence distribution fan-out architecture 100, which may be used for presence distribution between users of one or more networks.
  • the presence distribution fan-out architecture 100 may be used based on the SIP-SIMPLE and XMPP presence standards.
  • the presence distribution fan-out architecture 100 may include a plurality of servers 110 and a plurality of UEs 120 coupled to the servers 110.
  • the servers 110 may be located in one or more networks, data centers, or combinations thereof.
  • the servers 110 may be configured to receive, process, and forward presence information for a UE 120, including presence updates and presence queries.
  • the queries may be sent from contacts of a user to request presence information updates (current status) from the user.
  • the servers 110 may be any processors suitable for handling data, such as computer hardware, circuit cards or boards, and networking components (e.g., routers, switches).
  • the UEs 120 may be any devices used by individuals (users) to communicate with each other (via one or more networks), exchange presence information (updates and queries), and run related applications. Examples of the UEs 120 include telephones, cellular telephones, smartphones, laptop computers, desktop computers, and tablet computers.
  • the presence distribution fan-out architecture 100 may distribute presence information traffic among a set of servers 110, which may fan out incoming presence updates from users to other users subscribed to the originating user's presence status.
  • Each presence update sent from a UE 120 to a corresponding server 110 may cause about O(N) messages to be sent between the set of servers 110, where N is the number of contacts, i.e., the number of other UE 120 subscribed to receive presence status or updates from the originating UE 120.
  • each of the servers 110 may send about N messages to the remaining servers 110 and the associated contacts (UEs 120).
  • the notation O(N) signifies a linear or proportional increase in the messages from the servers 110 with respect to the number of UEs 120.
  • the presence distribution fan-out architecture 100 scales the presence update messages linearly or proportionally with the number of UEs 120, a relatively large number of servers 110 (e.g., tens of servers) may be needed to handle a relatively large number of messages (e.g., hundreds of thousands of messages).
  • FIG. 2 illustrates a presence distribution ring architecture 200 according to an example embodiment of the disclosure.
  • the presence distribution ring architecture 200 may include a plurality of servers 210 and a plurality of UEs 220 coupled to the servers 210.
  • the servers 210 and the UEs 220 may be similar to the servers 110 and the UEs 120, respectively.
  • the servers 210 may be arranged in a ring topology, as shown in FIG. 2, where a ring (of links) may be established between the servers 210 and may be used to transport ring information or messages (including ring updates and queries) between the servers 210 in their corresponding order on the ring.
  • the ring may be a unidirectional ring, where the presence information may be sent from server to server in sequence along the same direction (e.g., clockwise or counter clockwise) on the ring.
  • each server 210 may be configured to send presence information to a next hop server 210 in the ring and receive presence information from a previous hop server 210 in the ring.
  • Each server 210 may also exchange presence information messages with one or more UEs 220 that are coupled to that server 210.
  • the servers 210 may be configured to handle and distribute presence information from and to a UE 220, including presence queries and/or updates.
  • a client UE 220
  • the presence update may indicate the user's availability status.
  • the presence update may also indicate the originating user.
  • the presence query may request for a user (a UE 220) presence information for one or more contacts of the user (other UE 220).
  • the presence query may indicate the requesting user and the one or more contacts.
  • the presence update may be sent from a first client to a second client (another UE 210) that is subscribed to obtain such information from the first client.
  • the presence update or query may also be sent from a client upon connecting to a server 210 as part of a set up procedure of an application that uses presence information.
  • the server 210 may receive and buffer the presence update or query in local memory or a dedicated buffer.
  • the received presence update or query may be buffered for a suitable time after which the server 210 forwards the update or query on the ring (to a next hop server 210).
  • a timer or the size of the buffer may be configured to determine the buffer time for the message update or query, and hence the rate for sending presence updates and queries on the ring of servers 210.
  • the server 210 may add the presence update or query to a presence information message that is forwarded as a single network message between the servers 210 on the ring.
  • the server 210 may add the presence update or query to a presence information message received from a previous hop server 210 on the ring before forwarding the message to a next hop server 210.
  • the server 210 may add the presence update or query to a new presence information message generated and sent by the server 210 onto the ring.
  • the server 210 may process the received presence information message before forwarding the message to a next hop server 210. For instance, the server 210 may delete in a received presence information message on the ring any content that was previously added by the server 210 and sent on the ring. Since the information (presence update or query) was passed from the server 210 along the ring before returning to the server 210, the information was at some point (at one or more other servers 210) handled and processed. Thus, the information may be removed by the originating server 210 to prevent further circulating unnecessary information on the ring. Processing the received presence information message may also include copying the message (e.g., in local memory or buffer) before further sending the message on the ring to handle locally at the server 210 any relevant content in the received message.
  • processing the received presence information message may also include copying the message (e.g., in local memory or buffer) before further sending the message on the ring to handle locally at the server 210 any relevant content in the received message.
  • the server 210 may buffer a copy of the message information message before sending the message to a next hop server 210.
  • the copied information message received on the ring (from a previous hop server 210) may be buffered in the same or different buffer or memory location than the presence updates or queries received from the local UE 220 associated with the server 210.
  • the server 210 may process the copied content to determine whether any presence updates or queries in the received message are intended for clients or UE 220 associated with the server 210, and hence send the presence updates or queries to the corresponding clients.
  • Processing the received presence information message may also include appending any buffered presence updates or queries to the message, as described above.
  • the appended presence updates and/or queries may be for one or more clients or UEs 220 associated with other servers 210.
  • the server 210 may process the exchanged presence information messages on the ring at a higher priority and rate than the presence information (update or query) from the local UE and the copied presence information from messages received on the ring. This may guarantee limited or reduced delays in exchanging the presence information messages between the servers 210 on the ring.
  • the presence information (presence updates and queries) from local clients and the content copied from received messages on the ring may be handled by the server 210 at lower priority and rate, such as when the server 210 is idle or is not processing and forwarding presence information messages on the ring.
  • handling the presence information from the local clients comprises receiving and buffering such information in a buffer or local memory.
  • Handling the copied (and buffered) information from messages received on the ring comprises determining whether such content is intended for and hence to be forwarded to the local clients or is intended for other clients of other servers 210. If the content is intended for other clients not associated with the processing server 210, the copied content may be deleted.
  • each server 210 may have capacity for limiting or controlling the communications delays with the local UEs at a tolerated or acceptable level.
  • processing local clients' presence information and previously received and copied information that, which may affect communications for the local clients (UEs 220) may be tolerated at lower priority and rate.
  • network delays may be caused by different traffic in the network, and thus reducing message forwarding delays between the servers 210 on the ring may be beneficial and significant to reduce overall communications delays of presence information on the network. Assigning higher priority to presence information communications on the network over presence information communications with local clients may improve overall presence information communications efficiency, and thus reduce the number of needed servers 210 and associated network cost.
  • the server 210 may forward the messages to a next hop server 210 on the ring without additional delays, e.g., without temporarily holding the message in a wait buffer.
  • the servers 210 may buffer the information received from local clients and the copied content from the received information on the ring at a determined buffer time.
  • the server 210 may temporarily buffer the received information on the ring (before or after processing) at a shorter time than the information with lower priority.
  • Each server 210 on the ring may similarly process and forward at higher priority the received presence information messages from a previous hop server 210 and process presence information from local clients and copied content from received information on the ring at lower priority.
  • the server 210 may create a new message to send around the ring if any buffered presence updates and/or queries from local clients are not appended into a message sent around the ring within a determined threshold interval. For example, a message may be generated to forward pending (buffered) client's presence information every about 100 millisecond (ms) if the information is not appended to a message on the ring or no message is received on the ring within that time.
  • the server 210 may also send any copied and buffered information from received messages on the ring to corresponding clients at a determined interval. For example, a message comprising received updates and/or queries may be sent to one or more local clients every about 100 ms. One or more updates and/or queries intended for the local clients may be bundled in the same message that is sent to the clients. The bundled information may be located in a dedicated buffer on the server 210.
  • high priority messages (containing presence updates for multiple users of the network) may be sent at a higher priority around the ring to quickly and efficiently convey presence information to all servers 210 on the ring, which may then act on this information at a lower priority.
  • the high priority messages may comprise updates (and/or queries) for more users, but since the rate of originating these messages is controlled, additional load may not increase the number of the messages substantially beyond the determined rate. Updates to individual clients may be buffered as well to increase the likelihood that updates from multiple contacts are bundled and sent to the client in a single message.
  • Distributing presence information at a determined rate around a ring may be suitable for traffic size and characteristics of large enterprises (e.g., with few hundred thousand users and about ten servers).
  • the number of users or UEs 220 communicating with the servers 210 may be on the order of tens of thousands, for example about 10,000 or 60,000 UEs 220.
  • the number of servers 210 may be less than or equal to about 10 servers 210, for example, 9 or 8 servers 210.
  • Each server may also service about the same number of UEs 220.
  • a numerical example is provided to demonstrate substantial performance improvements of a ring-based approach as compared with a conventional approach.
  • the number of presence servers is represented by the positive integer P.
  • P the number of presence servers
  • a client logs into a server and then: (1) on initial login sends a query/subscribe for each contact (which the server may have to send to another server depending on which server the contact logged into - assuming the initial server somehow knows which server each contact logs into and does not have to broadcast this request to all other servers to find the contact); and (2) on every state change sends the state change to the server it has logged into (and the server, in turn, forks the update to every server into which one of the original client's contacts has logged into).
  • each of the presence servers serve a random set of 10,000/P clients, and assume all 10,00 clients log in within the same one hour interval.
  • the conventional approach results in a grand total of 2,000,000 * (P-l) / P server to server messages, 1,010,000 client to server messages (counting logins as "messages") and 10,000 server to client messages.
  • the ring approach described herein results in: (1) 10,000 client logins; (2) 10,000 client to server messages (the initial queries); (3) 10,000 queries (subscribes are redundant) sent around the ring - this means 10,000 * (P-l) messages altogether assuming no consolidation of requests (this rate is likely not high enough to result in much consolidation of requests); (4) 10,000 query responses sent around the ring; and (5) 10,000 server to client messages (indicating the initial state of all the client's contacts).
  • the ring approach results in a grand total of 20,000 * (P-l) server to server messages, 20,000 client to server messages, and 10,000 server to client messages.
  • FIG. 3 illustrates a presence distribution method 300 according to an example embodiment of the disclosure.
  • the presence distribution method 300 may be implemented by a presence server coupled to one or more local clients and to other presence servers in a ring architecture, such as any of the servers 210.
  • the method 300 may start at decision block 302, where the method 300 may determine whether a presence information message is received on a ring of servers. If the condition of block 302 is true, then the method 300 may proceed to block or step 304. Otherwise, the method 300 may proceed to block 308.
  • the message may be processed (by the local server) by deleting any content in the message that was previously locally added and sent on the ring, copying the content in the message locally, and appending to the message any buffered content from local clients.
  • the presence information message may be sent to a next hop on the ring.
  • the received message on the ring may be processed at high priority to accelerate the forwarding of the message on the next hop server on the ring. The method 300 may then end.
  • the method 300 may determine whether there are any locally buffered presence updates/queries from local clients. If the condition of block 308 is true, then the method 300 may proceed to block 310. Otherwise, the method 300 may proceed to block 314. At block 310, the method 300 may determine whether a timer for sending a presence information message on the ring has expired. For example, the timer may be set to send a message on the ring every about 100 ms. If the condition of block 310 is true, then the method 300 may proceed to block 312. Otherwise, the method 300 may end. At block 312, the buffered presence updates/queries may be sent in a new message to a next hop server on the ring. The new message may bundle a plurality of updates/queries for a plurality of clients, which may reduce the frequency of sending presence information on the ring and improve efficiency. The method 300 may then end.
  • the method 300 may determine whether a presence update or query is received from a local client. If the condition of block 314 is true, then the method 300 may proceed to block 316. Otherwise, the method 300 may proceed to block 318.
  • the presence update or query may be buffered, e.g., in a local buffer. As such, the presence update or query received from a local client may be processed at lower priority to forwarding received or new presence information messages on the ring. The method 300 may then end.
  • the method 300 may determine whether there is any locally copied content from a previously received presence information message on the ring. If the condition of block 318 is true, then the method 300 may proceed to block 320. Otherwise, the method 300 may end. At block 320, the method 300 may determine whether any of the copied content is intended to any local clients. If the condition of block 320 is true, then the method 300 may proceed to block 324. Otherwise, the method 300 may proceed to block 322. At block 322, the copied content may be deleted. The method 300 may then end.
  • the method 300 may determine whether a timer for sending presence information to clients has expired. For example, the timer may be set to send a message to local clients every about 100 ms. If the condition of block 324 is true, then the method 300 may proceed to block 326. Otherwise, the method 300 may then end.
  • the copied content may be sent to the intended local client(s).
  • the copied content may comprise one or more presence updates and/or queries for one or more local clients. As such, the presence updates/queries may be sent to local clients at a controlled frequency, which may improve efficiency.
  • the copied updates/queries intended for local clients may also be processed at lower priority to forwarding received or new presence information messages on the ring. The method 300 may then end.
  • the presence update or query received from a local client and the copied content including presence updates/queries for local clients may be processed at about the same priority when no presence information messages are processed and forwarded on the ring.
  • the method 300 may be implemented continuously in a loop, where the method 300 may return (after blocks or steps 306, 310, 312, 316, 318, 322, 324, and 326) to block 302 instead of ending.
  • FIG. 4 illustrates an example embodiment of a network unit 400, which may comprise or be part of, located at, or coupled to any of the components described above.
  • the network unit 400 may be located at or coupled to any of a plurality of presence servers coupled to each other in a ring topology and to a plurality of local clients, such as the servers 210.
  • the network unit 400 may be any device that transports data through the network.
  • the network unit 400 may comprise one or more ingress ports or units 410 coupled to a receiver (Rx) 412 for receiving signals and packets/data from other network components.
  • the network unit 400 may comprise a logic unit 420 to determine which network components to send data to.
  • the logic unit 420 may be implemented using hardware, software, or both.
  • the network unit 400 may also comprise one or more egress ports or units 430 coupled to a transmitter (Tx) 432 for transmitting signals and packets/data to the other network components.
  • the receiver 412, logic unit 420, and transmitter 432 may also implement or support the schemes and methods described above for processing and forwarding presence information (updates and queries) for the clients on the ring of servers (at high priority) and to/from the clients (at low priority).
  • the receiver 412, logic unit 420, and transmitter 432 may be configured (via hardware and/or software) to implement or support the schemes described above for the presence distribution ring architecture 200 and the method 300.
  • FIG. 5 illustrates a typical, general-purpose network component 500 suitable for implementing one or more example embodiments of the components disclosed herein.
  • the network component 500 may comprise or be part of, located at or coupled to any of a plurality of presence servers coupled to each other in a ring topology and to a plurality of local clients, such as the servers 210.
  • the network component 500 includes a processor 502 (which may be referred to as a central processor unit or CPU) that is in communication with memory devices including secondary storage 504, read only memory (ROM) 506, random access memory (RAM) 508, input/output (I/O) devices 510, and network connectivity devices 512.
  • the processor 502 may be implemented as one or more CPU chips, cores (e.g., a multi-core processor), field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), and/or digital signal processors (DSPs), and/or may be part of one or more ASICs.
  • the processor 502 may be configured to implement any of the schemes and methods described above for processing and forwarding presence information (updates and queries) for the clients on the ring of servers (at high priority) and to/from the clients (at low priority). For instance, the processor 502 may be configured (via hardware and/or software) to implement or support the schemes described above for the presence distribution ring architecture 200 and the method 300.
  • the secondary storage 504 is typically comprised of one or more disk drives or erasable programmable ROM (EPROM) and is used for non-volatile storage of data. Secondary storage 504 may be used to store programs that are loaded into RAM 508 when such programs are selected for execution.
  • the ROM 506 is used to store instructions and perhaps data that are read during program execution. ROM 506 is a non-volatile memory device that typically has a small memory capacity relative to the larger memory capacity of secondary storage 504.
  • the RAM 508 is used to store volatile data and perhaps to store instructions. Access to both ROM 506 and RAM 508 is typically faster than to secondary storage 504.
  • At least one example embodiment is disclosed and variations, combinations, and/or modifications of the example embodiment(s) and/or features of the example embodiment(s) made by a person having ordinary skill in the art are within the scope of the disclosure. Alternative embodiments that result from combining, integrating, and/or omitting features of the example embodiment(s) are also within the scope of the disclosure.
  • numerical ranges or limitations are expressly stated, such express ranges or limitations should be understood to include iterative ranges or limitations of like magnitude falling within the expressly stated ranges or limitations (e.g., from about 1 to about 10 includes, 2, 3, 4, etc.; greater than 0.10 includes 0.11, 0.12, 0.13, etc.).
  • R Ri + k * (R u - Ri), wherein k is a variable ranging from 1 percent to 100 percent with a 1 percent increment, i.e., k is 1 percent, 2 percent, 3 percent, 4 percent, 5 percent, 50 percent, 51 percent, 52 percent, ..., 95 percent, 96 percent, 97 percent, 98 percent, 99 percent, or 100 percent.
  • Ri Ri + k * (R u - Ri)
  • k is a variable ranging from 1 percent to 100 percent with a 1 percent increment, i.e., k is 1 percent, 2 percent, 3 percent, 4 percent, 5 percent, 50 percent, 51 percent, 52 percent, ..., 95 percent, 96 percent, 97 percent, 98 percent, 99 percent, or 100 percent.
  • any numerical range defined by two R numbers as defined in the above is also specifically disclosed.

Abstract

A method implemented in a network component, the method comprising receiving a presence information message from a presence server in a ring of a plurality of presence servers, removing content in the presence information message that is previously originated by the network component and previously sent on the ring, copying the presence information message locally for subsequent processing, appending to the presence information message buffered presence information from a local client coupled to the network component, and forwarding the presence information message to a second presence server in the ring.

Description

Efficient Presence Distribution Mechanism for a Large Enterprise
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] The present application claims priority to U.S. Patent Application No. 13/602,769 filed September 4, 2012 and entitled "Efficient Presence Distribution Mechanism for a Large Enterprise", which is incorporated herein by reference as if reproduced in its entirety.
FIELD OF INVENTION
[0002] The present invention relates to network communication, and, in particular, to efficient presence distribution mechanism for a large enterprise.
BACKGROUND
[0003] A network service which accepts, stores, and distributes presence information for a plurality of users may be referred to as a presence service. A presence service may be implemented on one or more servers, for example arranged in some architecture or topology in the network. A presence server in a network may be configured to receive and manage presence information from a user or client device, also referred to as a user equipment (UE) in some scenarios. Examples of a UE include smartphones, laptop computers, computer tablets, and desktop computers. A presence server may share the presence information of a user (on a UE) with other users (on one or more other UEs) that are authorized by the user to obtain such information either directly by sending the presence information to these other users or indirectly by sending the presence information to other presence servers which in turn distribute the presence information to other users . The presence information indicates the status of the user on the network, such as the availability, ability, or willingness of the user to communicate with other users of the network. Presence information has wide application in many communication services, such as instant messaging, voice over Internet Protocol (IP), and social networking services or applications.
[0004] To communicate presence information, a UE may display an indicator icon, for example corresponding to an instant messaging application, from a choice of graphic symbols with easy- to-convey meanings and a list of corresponding text descriptions of each of the states. Common states that indicate the user's availability are "free for chat", "busy", "away", "do not disturb", and "out to lunch". Such states exist in many variations across different instant messaging applications. Some applications also support a rich choice of additional presence attributes that can be used for presence information, such as user mood, location, or free text status.
[0005] In some presence distribution architectures, clients send presence updates to one of a pool of servers, which then distributes updates to all of the user's subscribed contacts. For example, both Session Initiation Protocol (SIP) for Instant Messaging and Presence Leveraging Extensions (SIMPLE) and Extensible Messaging and Presence Protocol (XMPP) presence standards discuss presence updates in terms of a subscribe/notify model, where the contact subscribes for presence updates from an originating user. The implementation is one where presence updates are sent from an originating user's device to one of a cluster of presence servers, which then distributes the presence updates to the user's contacts (typically through other servers). In such presence distribution architectures, the number of sent updates increases, e.g., proportionally, as the numbers of users, servers, and initiated updates increase, which can be substantial in larger networks (e.g., with hundred thousands of users) and incur substantial cost (e.g., in terms of used servers and resources). Reducing the number of used servers and/or sent presence information messages is desirable to reduce cost and improve efficiency (e.g., in terms of resource and network utilization). SUMMARY
[0006] In one example embodiment, the disclosure includes a method implemented in a network component, the method comprising receiving a presence information message from a presence server in a ring of a plurality of presence servers, removing content in the presence information message that is previously originated by the network component and previously sent on the ring, copying the presence information message locally for subsequent processing, appending to the presence information message buffered presence information from a local client coupled to the network component, and forwarding the presence information message to a second presence server in the ring.
[0007] In another example embodiment, the disclosure includes a method for forwarding presence information implemented in a presence server coupled to a plurality of presence servers in a ring architecture, the method comprising receiving a presence information message on a link from a second presence server in the plurality of presence servers, processing the presence information message, receiving a local presence information message from a local client coupled to the presence server, processing the local presence information message, and processing previously received and buffered presence information intended to one or more local clients coupled to the presence server, wherein the presence information message has a higher priority than the local presence information message and the previously received and buffered presence information.
[0008] In yet another example embodiment, the disclosure includes a network component for processing and forwarding presence information to a plurality of presence servers coupled via a ring in one or more networks and a plurality of user devices coupled to the presence server, the network component comprising a processor configured to receive a presence information message from a previous hop on the ring, process and forward the presence information message, receive a local presence information message from a user device coupled locally to the network component, buffer the local presence information message for subsequent processing and forwarding, and forward previously received and buffered presence information to one or more intended clients coupled to the network component wherein the presence information message has a higher priority than the local presence information message and previously received and buffered presence information, wherein the presence information message has a higher priority than the local presence information message and the previously received and buffered presence information.
[0009] In yet another example embodiment, the disclosure includes a computer program product in a non-transitory computer readable media comprising first instructions executable by a processor for receiving a presence information message from a presence server in a ring of a plurality of presence servers, second instructions executable by a processor for removing content in the presence information message that is previously originated by the network component and previously sent on the ring, third instructions executable by a processor for copying the presence information message locally for subsequent processing, fourth instructions executable by a processor for appending to the presence information message buffered presence information from a local client coupled to the network component, and fifth instructions executable by a processor for forwarding the presence information message to a second presence server in the ring.
[0010] These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.
BRIEF DESCRIPTION OF THE DRAWINGS
[0011] For a more complete understanding of this disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts. [0012] FIG. 1 is a schematic diagram of a typical presence distribution fan-out architecture.
[0013] FIG. 2 is a schematic diagram of a presence distribution ring architecture according to an example embodiment of the disclosure.
[0014] FIG. 3 is a flowchart of a presence distribution method according to an example embodiment of the disclosure.
[0015] FIG. 4 is a schematic diagram of an example embodiment of a network unit.
[0016] FIG. 5 is a schematic diagram of an example embodiment of a general -purpose network component.
DETAILED DESCRIPTION
[0017] It should be understood at the outset that although an illustrative implementation of one or more example embodiments are provided below, the disclosed systems and/or methods may be implemented using any number of techniques, whether currently known or in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.
[0018] Disclosed herein are systems, methods, and apparatuses for presence information distribution. The presence information may be effectively broadcast to a set of presence servers arranged in a ring architecture. The presence information for one or more users may be sent from server to server on the ring in a high priority message (at a first rate), and may be sent to the user's contacts at a lower priority (at a second lower rate). For the number of users and contacts per user in a typical large enterprise (e.g., with about few hundred thousands of users), this scheme may reduce the total number of messages exchanged and processed by a presence server by a factor of about two or more, e.g., in comparison to a fan-out distribution architecture, without substantially affecting operations. This may increase efficiency and reduce cost since fewer servers may be used to support a population of users as compared to previous presence information distribution architectures.
[0019] FIG. 1 illustrates a typical presence distribution fan-out architecture 100, which may be used for presence distribution between users of one or more networks. For example, the presence distribution fan-out architecture 100 may be used based on the SIP-SIMPLE and XMPP presence standards. The presence distribution fan-out architecture 100 may include a plurality of servers 110 and a plurality of UEs 120 coupled to the servers 110. The servers 110 may be located in one or more networks, data centers, or combinations thereof. The servers 110 may be configured to receive, process, and forward presence information for a UE 120, including presence updates and presence queries. The queries may be sent from contacts of a user to request presence information updates (current status) from the user. The servers 110 may be any processors suitable for handling data, such as computer hardware, circuit cards or boards, and networking components (e.g., routers, switches). The UEs 120 may be any devices used by individuals (users) to communicate with each other (via one or more networks), exchange presence information (updates and queries), and run related applications. Examples of the UEs 120 include telephones, cellular telephones, smartphones, laptop computers, desktop computers, and tablet computers.
[0020] The presence distribution fan-out architecture 100 may distribute presence information traffic among a set of servers 110, which may fan out incoming presence updates from users to other users subscribed to the originating user's presence status. Each presence update sent from a UE 120 to a corresponding server 110 may cause about O(N) messages to be sent between the set of servers 110, where N is the number of contacts, i.e., the number of other UE 120 subscribed to receive presence status or updates from the originating UE 120. For instance, each of the servers 110 may send about N messages to the remaining servers 110 and the associated contacts (UEs 120). The notation O(N) signifies a linear or proportional increase in the messages from the servers 110 with respect to the number of UEs 120. Since the presence distribution fan-out architecture 100 scales the presence update messages linearly or proportionally with the number of UEs 120, a relatively large number of servers 110 (e.g., tens of servers) may be needed to handle a relatively large number of messages (e.g., hundreds of thousands of messages).
[0021] FIG. 2 illustrates a presence distribution ring architecture 200 according to an example embodiment of the disclosure. The presence distribution ring architecture 200 may include a plurality of servers 210 and a plurality of UEs 220 coupled to the servers 210. The servers 210 and the UEs 220 may be similar to the servers 110 and the UEs 120, respectively. However, the servers 210 may be arranged in a ring topology, as shown in FIG. 2, where a ring (of links) may be established between the servers 210 and may be used to transport ring information or messages (including ring updates and queries) between the servers 210 in their corresponding order on the ring. The ring may be a unidirectional ring, where the presence information may be sent from server to server in sequence along the same direction (e.g., clockwise or counter clockwise) on the ring. Thus, each server 210 may be configured to send presence information to a next hop server 210 in the ring and receive presence information from a previous hop server 210 in the ring. Each server 210 may also exchange presence information messages with one or more UEs 220 that are coupled to that server 210.
[0022] The servers 210 may be configured to handle and distribute presence information from and to a UE 220, including presence queries and/or updates. A client (UE 220) may send a presence update or query (in a message) to a corresponding server 210. The presence update may indicate the user's availability status. The presence update may also indicate the originating user. The presence query may request for a user (a UE 220) presence information for one or more contacts of the user (other UE 220). The presence query may indicate the requesting user and the one or more contacts. For example, the presence update may be sent from a first client to a second client (another UE 210) that is subscribed to obtain such information from the first client. The presence update or query may also be sent from a client upon connecting to a server 210 as part of a set up procedure of an application that uses presence information. The server 210 may receive and buffer the presence update or query in local memory or a dedicated buffer. The received presence update or query may be buffered for a suitable time after which the server 210 forwards the update or query on the ring (to a next hop server 210). For example, a timer or the size of the buffer may be configured to determine the buffer time for the message update or query, and hence the rate for sending presence updates and queries on the ring of servers 210.
[0023] To forward the presence update or query on the ring, the server 210 may add the presence update or query to a presence information message that is forwarded as a single network message between the servers 210 on the ring. The server 210 may add the presence update or query to a presence information message received from a previous hop server 210 on the ring before forwarding the message to a next hop server 210. Alternatively, the server 210 may add the presence update or query to a new presence information message generated and sent by the server 210 onto the ring.
[0024] The server 210 may process the received presence information message before forwarding the message to a next hop server 210. For instance, the server 210 may delete in a received presence information message on the ring any content that was previously added by the server 210 and sent on the ring. Since the information (presence update or query) was passed from the server 210 along the ring before returning to the server 210, the information was at some point (at one or more other servers 210) handled and processed. Thus, the information may be removed by the originating server 210 to prevent further circulating unnecessary information on the ring. Processing the received presence information message may also include copying the message (e.g., in local memory or buffer) before further sending the message on the ring to handle locally at the server 210 any relevant content in the received message. The server 210 may buffer a copy of the message information message before sending the message to a next hop server 210. The copied information message received on the ring (from a previous hop server 210) may be buffered in the same or different buffer or memory location than the presence updates or queries received from the local UE 220 associated with the server 210. The server 210 may process the copied content to determine whether any presence updates or queries in the received message are intended for clients or UE 220 associated with the server 210, and hence send the presence updates or queries to the corresponding clients. Processing the received presence information message may also include appending any buffered presence updates or queries to the message, as described above. The appended presence updates and/or queries may be for one or more clients or UEs 220 associated with other servers 210.
[0025] The server 210 may process the exchanged presence information messages on the ring at a higher priority and rate than the presence information (update or query) from the local UE and the copied presence information from messages received on the ring. This may guarantee limited or reduced delays in exchanging the presence information messages between the servers 210 on the ring. The presence information (presence updates and queries) from local clients and the content copied from received messages on the ring may be handled by the server 210 at lower priority and rate, such as when the server 210 is idle or is not processing and forwarding presence information messages on the ring. As described above, handling the presence information from the local clients comprises receiving and buffering such information in a buffer or local memory. Handling the copied (and buffered) information from messages received on the ring comprises determining whether such content is intended for and hence to be forwarded to the local clients or is intended for other clients of other servers 210. If the content is intended for other clients not associated with the processing server 210, the copied content may be deleted.
[0026] Since typically each server 210 communicates with a manageable group of local UEs 220, each server 210 may have capacity for limiting or controlling the communications delays with the local UEs at a tolerated or acceptable level. Thus, processing local clients' presence information and previously received and copied information that, which may affect communications for the local clients (UEs 220), may be tolerated at lower priority and rate. However, network delays may be caused by different traffic in the network, and thus reducing message forwarding delays between the servers 210 on the ring may be beneficial and significant to reduce overall communications delays of presence information on the network. Assigning higher priority to presence information communications on the network over presence information communications with local clients may improve overall presence information communications efficiency, and thus reduce the number of needed servers 210 and associated network cost.
[0027] Upon receiving and processing the received presence information messages on the ring as described above, the server 210 may forward the messages to a next hop server 210 on the ring without additional delays, e.g., without temporarily holding the message in a wait buffer. However, the servers 210 may buffer the information received from local clients and the copied content from the received information on the ring at a determined buffer time. Alternatively, the server 210 may temporarily buffer the received information on the ring (before or after processing) at a shorter time than the information with lower priority. Each server 210 on the ring may similarly process and forward at higher priority the received presence information messages from a previous hop server 210 and process presence information from local clients and copied content from received information on the ring at lower priority.
[0028] Additionally, the server 210 may create a new message to send around the ring if any buffered presence updates and/or queries from local clients are not appended into a message sent around the ring within a determined threshold interval. For example, a message may be generated to forward pending (buffered) client's presence information every about 100 millisecond (ms) if the information is not appended to a message on the ring or no message is received on the ring within that time. The server 210 may also send any copied and buffered information from received messages on the ring to corresponding clients at a determined interval. For example, a message comprising received updates and/or queries may be sent to one or more local clients every about 100 ms. One or more updates and/or queries intended for the local clients may be bundled in the same message that is sent to the clients. The bundled information may be located in a dedicated buffer on the server 210.
[0029] According to the high and low priority presence information processing scheme above, high priority messages (containing presence updates for multiple users of the network) may be sent at a higher priority around the ring to quickly and efficiently convey presence information to all servers 210 on the ring, which may then act on this information at a lower priority. As load increases, the high priority messages may comprise updates (and/or queries) for more users, but since the rate of originating these messages is controlled, additional load may not increase the number of the messages substantially beyond the determined rate. Updates to individual clients may be buffered as well to increase the likelihood that updates from multiple contacts are bundled and sent to the client in a single message. Distributing presence information at a determined rate around a ring may be suitable for traffic size and characteristics of large enterprises (e.g., with few hundred thousand users and about ten servers). In one exemplary scenario of a large enterprise, where the scheme above may be implemented efficiently and effectively, the number of users or UEs 220 communicating with the servers 210 may be on the order of tens of thousands, for example about 10,000 or 60,000 UEs 220. The number of servers 210 may be less than or equal to about 10 servers 210, for example, 9 or 8 servers 210. Each server may also service about the same number of UEs 220.
[0030] A numerical example is provided to demonstrate substantial performance improvements of a ring-based approach as compared with a conventional approach. Suppose the number of presence servers is represented by the positive integer P. Suppose that in each approach a client logs into a server and then: (1) on initial login sends a query/subscribe for each contact (which the server may have to send to another server depending on which server the contact logged into - assuming the initial server somehow knows which server each contact logs into and does not have to broadcast this request to all other servers to find the contact); and (2) on every state change sends the state change to the server it has logged into (and the server, in turn, forks the update to every server into which one of the original client's contacts has logged into). Assume 10,000 users with 100 contacts each, each of the presence servers serve a random set of 10,000/P clients, and assume all 10,00 clients log in within the same one hour interval.
[0031] Under the assumptions above, the conventional approach results in: (1) 10,000 client logins; (2) 1,000,000 client to server messages (the query/subscribes - in some conventional systems there are only 10,000 of these directed to "list servers", which then in turn do the fan out to 1,000,000 query/subscribes on the clients behalf - whether the fan out is done directly by the client or indirectly by a list server doesn't really affect the total number of messages very much); (3) 1,000,000 * (P-l) / P server to server messages (these messages are to get the queries/subscribes to the right server - assuming here each client's 100 contacts log into a perfectly random one of the P servers); (4) 1,000,000 * (P-l) P responses to the above queries/subscribes; and (5) 10,000 server to client messages (indicating the initial state of all the client's contacts - assuming here these are batched somehow, without this assumption this is 1,000,000 server to client messages). The conventional approach results in a grand total of 2,000,000 * (P-l) / P server to server messages, 1,010,000 client to server messages (counting logins as "messages") and 10,000 server to client messages. The average messages sent/received per server per second is: (1) messages received (per server per second) = 280/P + (555 * (P-l) / P**2); and (2) messages sent (per server per second) = 2.8/P + (555 * (P-l) / P**2).
[0032] Under the assumptions above, the ring approach described herein, assuming 100 milliseconds (ms) buffering, results in: (1) 10,000 client logins; (2) 10,000 client to server messages (the initial queries); (3) 10,000 queries (subscribes are redundant) sent around the ring - this means 10,000 * (P-l) messages altogether assuming no consolidation of requests (this rate is likely not high enough to result in much consolidation of requests); (4) 10,000 query responses sent around the ring; and (5) 10,000 server to client messages (indicating the initial state of all the client's contacts). The ring approach results in a grand total of 20,000 * (P-l) server to server messages, 20,000 client to server messages, and 10,000 server to client messages. The average messages sent/received per server per second is: (1) messages received (per server per second) = 5.6/P; and (2) messages sent (per server per second) = (2.8 + 5.6)/P = 8.4/P.
[0033] A table comparing the conventional and ring approaches, assuming P=10 and the other assumptions detailed above, is presented below. Approach Total server to Total client to server Total server to client
server messages messages messages
Conventional 1.8 million 1.01 million 10,000
Ring 180,000 20,000 10,000
Table 1. Comparison of conventional and ring approaches.
Note the drastic reduction in the number of presence messages, and therefore traffic, generated using the ring based approach. Similar performance improvements are available during steady state operation in which there are a fixed number of updates per transmitted per client per unit time. [0034] FIG. 3 illustrates a presence distribution method 300 according to an example embodiment of the disclosure. The presence distribution method 300 may be implemented by a presence server coupled to one or more local clients and to other presence servers in a ring architecture, such as any of the servers 210. The method 300 may start at decision block 302, where the method 300 may determine whether a presence information message is received on a ring of servers. If the condition of block 302 is true, then the method 300 may proceed to block or step 304. Otherwise, the method 300 may proceed to block 308. The message may be processed (by the local server) by deleting any content in the message that was previously locally added and sent on the ring, copying the content in the message locally, and appending to the message any buffered content from local clients. At block 306, the presence information message may be sent to a next hop on the ring. As such, the received message on the ring may be processed at high priority to accelerate the forwarding of the message on the next hop server on the ring. The method 300 may then end.
[0035] At block 308, the method 300 may determine whether there are any locally buffered presence updates/queries from local clients. If the condition of block 308 is true, then the method 300 may proceed to block 310. Otherwise, the method 300 may proceed to block 314. At block 310, the method 300 may determine whether a timer for sending a presence information message on the ring has expired. For example, the timer may be set to send a message on the ring every about 100 ms. If the condition of block 310 is true, then the method 300 may proceed to block 312. Otherwise, the method 300 may end. At block 312, the buffered presence updates/queries may be sent in a new message to a next hop server on the ring. The new message may bundle a plurality of updates/queries for a plurality of clients, which may reduce the frequency of sending presence information on the ring and improve efficiency. The method 300 may then end.
[0036] At block 314, the method 300 may determine whether a presence update or query is received from a local client. If the condition of block 314 is true, then the method 300 may proceed to block 316. Otherwise, the method 300 may proceed to block 318. At block 316, the presence update or query may be buffered, e.g., in a local buffer. As such, the presence update or query received from a local client may be processed at lower priority to forwarding received or new presence information messages on the ring. The method 300 may then end.
[0037] At block 318, the method 300 may determine whether there is any locally copied content from a previously received presence information message on the ring. If the condition of block 318 is true, then the method 300 may proceed to block 320. Otherwise, the method 300 may end. At block 320, the method 300 may determine whether any of the copied content is intended to any local clients. If the condition of block 320 is true, then the method 300 may proceed to block 324. Otherwise, the method 300 may proceed to block 322. At block 322, the copied content may be deleted. The method 300 may then end.
[0038] At block 324, the method 300 may determine whether a timer for sending presence information to clients has expired. For example, the timer may be set to send a message to local clients every about 100 ms. If the condition of block 324 is true, then the method 300 may proceed to block 326. Otherwise, the method 300 may then end. At block 326, the copied content may be sent to the intended local client(s). The copied content may comprise one or more presence updates and/or queries for one or more local clients. As such, the presence updates/queries may be sent to local clients at a controlled frequency, which may improve efficiency. The copied updates/queries intended for local clients may also be processed at lower priority to forwarding received or new presence information messages on the ring. The method 300 may then end. In the method 300, the presence update or query received from a local client and the copied content including presence updates/queries for local clients may be processed at about the same priority when no presence information messages are processed and forwarded on the ring. In some example embodiments, the method 300 may be implemented continuously in a loop, where the method 300 may return (after blocks or steps 306, 310, 312, 316, 318, 322, 324, and 326) to block 302 instead of ending.
[0039] FIG. 4 illustrates an example embodiment of a network unit 400, which may comprise or be part of, located at, or coupled to any of the components described above. For example, the network unit 400 may be located at or coupled to any of a plurality of presence servers coupled to each other in a ring topology and to a plurality of local clients, such as the servers 210. The network unit 400 may be any device that transports data through the network. The network unit 400 may comprise one or more ingress ports or units 410 coupled to a receiver (Rx) 412 for receiving signals and packets/data from other network components. The network unit 400 may comprise a logic unit 420 to determine which network components to send data to. The logic unit 420 may be implemented using hardware, software, or both. The network unit 400 may also comprise one or more egress ports or units 430 coupled to a transmitter (Tx) 432 for transmitting signals and packets/data to the other network components. The receiver 412, logic unit 420, and transmitter 432 may also implement or support the schemes and methods described above for processing and forwarding presence information (updates and queries) for the clients on the ring of servers (at high priority) and to/from the clients (at low priority). For instance, the receiver 412, logic unit 420, and transmitter 432 may be configured (via hardware and/or software) to implement or support the schemes described above for the presence distribution ring architecture 200 and the method 300.
[0040] The network components described above may be implemented on any general-purpose network component, such as a computer or network component with sufficient processing power, memory resources, and network throughput capability to handle the necessary workload placed upon it. FIG. 5 illustrates a typical, general-purpose network component 500 suitable for implementing one or more example embodiments of the components disclosed herein. For example, the network component 500 may comprise or be part of, located at or coupled to any of a plurality of presence servers coupled to each other in a ring topology and to a plurality of local clients, such as the servers 210. The network component 500 includes a processor 502 (which may be referred to as a central processor unit or CPU) that is in communication with memory devices including secondary storage 504, read only memory (ROM) 506, random access memory (RAM) 508, input/output (I/O) devices 510, and network connectivity devices 512. The processor 502 may be implemented as one or more CPU chips, cores (e.g., a multi-core processor), field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), and/or digital signal processors (DSPs), and/or may be part of one or more ASICs. The processor 502 may be configured to implement any of the schemes and methods described above for processing and forwarding presence information (updates and queries) for the clients on the ring of servers (at high priority) and to/from the clients (at low priority). For instance, the processor 502 may be configured (via hardware and/or software) to implement or support the schemes described above for the presence distribution ring architecture 200 and the method 300.
[0041] The secondary storage 504 is typically comprised of one or more disk drives or erasable programmable ROM (EPROM) and is used for non-volatile storage of data. Secondary storage 504 may be used to store programs that are loaded into RAM 508 when such programs are selected for execution. The ROM 506 is used to store instructions and perhaps data that are read during program execution. ROM 506 is a non-volatile memory device that typically has a small memory capacity relative to the larger memory capacity of secondary storage 504. The RAM 508 is used to store volatile data and perhaps to store instructions. Access to both ROM 506 and RAM 508 is typically faster than to secondary storage 504.
[0042] At least one example embodiment is disclosed and variations, combinations, and/or modifications of the example embodiment(s) and/or features of the example embodiment(s) made by a person having ordinary skill in the art are within the scope of the disclosure. Alternative embodiments that result from combining, integrating, and/or omitting features of the example embodiment(s) are also within the scope of the disclosure. Where numerical ranges or limitations are expressly stated, such express ranges or limitations should be understood to include iterative ranges or limitations of like magnitude falling within the expressly stated ranges or limitations (e.g., from about 1 to about 10 includes, 2, 3, 4, etc.; greater than 0.10 includes 0.11, 0.12, 0.13, etc.). For example, whenever a numerical range with a lower limit, Ri, and an upper limit, Ru, is disclosed, any number falling within the range is specifically disclosed. In particular, the following numbers within the range are specifically disclosed: R = Ri + k * (Ru - Ri), wherein k is a variable ranging from 1 percent to 100 percent with a 1 percent increment, i.e., k is 1 percent, 2 percent, 3 percent, 4 percent, 5 percent, 50 percent, 51 percent, 52 percent, ..., 95 percent, 96 percent, 97 percent, 98 percent, 99 percent, or 100 percent. Moreover, any numerical range defined by two R numbers as defined in the above is also specifically disclosed. Use of the term "optionally" with respect to any element of a claim means that the element is required, or alternatively, the element is not required, both alternatives being within the scope of the claim. Use of broader terms such as comprises, includes, and having should be understood to provide support for narrower terms such as consisting of, consisting essentially of, and comprised substantially of. Accordingly, the scope of protection is not limited by the description set out above but is defined by the claims that follow, that scope including all equivalents of the subject matter of the claims. Each and every claim is incorporated as further disclosure into the specification and the claims are example embodiment(s) of the present disclosure. The discussion of a reference in the disclosure is not an admission that it is prior art, especially any reference that has a publication date after the priority date of this application. The disclosure of all patents, patent applications, and publications cited in the disclosure are hereby incorporated by reference, to the extent that they provide exemplary, procedural, or other details supplementary to the disclosure.
[0043] While several example embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods might be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented.
[0044] In addition, techniques, systems, subsystems, and methods described and illustrated in the various example embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein.

Claims

1. A method implemented in a network component, the method comprising:
receiving a presence information message from a presence server in a ring of a plurality of presence servers;
removing content in the presence information message that is previously originated by the network component and previously sent on the ring;
copying the presence information message locally for subsequent processing;
appending to the presence information message buffered presence information from a local client coupled to the network component; and
forwarding the presence information message to a second presence server in the ring.
2. The method of claim 1, wherein the presence information message comprises one or more presence updates or queries for one or more clients associated with the plurality of presence servers, and wherein the removed content and the appended content includes one or more presence updates or queries for the local client.
3. The method of claim 1 further comprising:
bundling buffered presence information from the local client into a new presence information message; and
sending the new presence information message to the second presence server.
4. The method of claim 3, wherein the bundled presence information includes one or more presence updates or queries for the local client, and wherein the new presence information message is sent on the ring at a frequency based on a predetermined time interval.
5. The method of claim 4, wherein the predetermined time interval is set to every about 100 milliseconds.
6. The method of claim 1 further comprising:
receiving presence information comprising a presence update or query from the local client; and
buffering the presence information.
7. The method of claim 6, wherein receiving, copying, and forwarding the presence information message on the ring has a higher priority than receiving and buffering the presence information.
8. The method of claim 1 further comprising:
sending content copied locally from one or more previously received presence information messages to the local client; and
deleting he content copied locally if the content is not intended for the local client.
9. The method of claim 8, wherein receiving, copying, and forwarding the presence information message on the ring has higher priority than sending or deleting the content copied locally.
10. The method of claim 8, wherein the content copied locally is sent to the one or more intended clients at a frequency based on a predetermined time interval.
11. The method of claim 10, wherein the predetermined time interval is set to every about 100 milliseconds.
12. A method for forwarding presence information implemented in a presence server coupled to a plurality of presence servers in a ring architecture, the method comprising:
receiving a presence information message on a link from a second presence server in the plurality of presence servers;
processing the presence information message;
receiving a local presence information message from a local client coupled to the presence server;
processing the local presence information message; and
processing previously received and buffered presence information intended for one or more local clients coupled to the presence server,
wherein the presence information message has a higher priority than the local presence information message and the previously received and buffered presence information.
13. The method of claim 12, wherein the local presence information message and the previously received and buffered presence information have about the same priority.
14. The method of claim 12, wherein processing the presence information message comprises: removing detected content in the presence information message that is previously originated by the presence server component and previously sent on the ring;
copying the content of the presence information message locally for subsequent processing; and
appending to the presence information message buffered presence information from one or more local clients coupled to the presence server.
15. The method of claim 12, wherein processing the local presence information message comprises:
buffering the local presence information message locally at the presence server; and bundling local presence information of the local presence information message with other buffered local presence information for one or more local clients into a new presence information message; and
sending the new presence information message to a next hop on the ring.
16. The method of claim 12, wherein processing the previously received and buffered presence information comprises sending the previously received and buffered information to the one or more local clients.
17. A network component for processing and forwarding presence information to a plurality of presence servers coupled via a ring in one or more networks and a plurality of user devices coupled to the presence server, the network component comprising:
a processor configured to:
receive a presence information message from a previous hop on the ring;
process and forward the presence information message;
receive a local presence information message from a user device coupled to the network component;
buffer the local presence information message for subsequent processing and forwarding; and
forward previously received and buffered presence information to one or more intended user devices coupled to the network component,
wherein the presence information message has a higher priority than the local presence information message and the previously received and buffered presence information.
18. The network component of claim 17, wherein the number of presence servers on the ring is less than or equal to about ten, and wherein the number of user devices coupled to the presence server is at least ten of thousand.
19. The network component of claim 17, wherein the presence information message comprises one or more presence updates for one or more corresponding users that indicate current availability status to one or more contacts that have subscribed to obtain presence information from the users.
20. The network component of claim 19, wherein the one or more presence updates are sent when the one or more user devices connect to one or more corresponding presence servers.
21. The network component of claim 17, wherein the presence information message forwarded on the ring comprises one or more presence queries sent to one or more corresponding users to indicate current availability status to one or more contacts subscribed to obtain presence information from the users.
22. The network component of claim 21, wherein the one or more presence updates are sent when the one or more user devices receive the one or more presence queries from one or more presence servers.
23. A computer program product in a non-transitory computer readable media comprising: first instructions executable by a processor for receiving a presence information message from a presence server in a ring of a plurality of presence servers;
second instructions executable by a processor for removing content in the presence information message that is previously originated by the network component and previously sent on the ring;
third instructions executable by a processor for copying the presence information message locally for subsequent processing;
fourth instructions executable by a processor for appending to the presence information message buffered presence information from a local client coupled to the network component; and fifth instructions executable by a processor for forwarding the presence information message to a second presence server in the ring.
24. The computer program product of claim 23, wherein the presence information message comprises one or more presence updates or queries for one or more clients associated with the plurality of presence servers, and wherein the removed content and the appended content includes one or more presence updates or queries for the local client.
25. The computer program product of claim 23 further comprising:
sixth instructions executable by a processor for bundling buffered presence information the local client into a new presence information message; and
seventh instructions executable by a processor for sending the new presence information message to the second presence server.
PCT/CN2013/082394 2012-09-04 2013-08-27 Efficient presence distribution mechanism for a large enterprise WO2014036903A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201380045307.7A CN104604189B (en) 2012-09-04 2013-08-27 The efficient state issue mechanism of large enterprise
EP13835415.4A EP2891279B1 (en) 2012-09-04 2013-08-27 Efficient presence distribution mechanism for a large enterprise

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/602,769 US9299111B2 (en) 2012-09-04 2012-09-04 Efficient presence distribution mechanism for a large enterprise
US13/602,769 2012-09-04

Publications (1)

Publication Number Publication Date
WO2014036903A1 true WO2014036903A1 (en) 2014-03-13

Family

ID=50188967

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/082394 WO2014036903A1 (en) 2012-09-04 2013-08-27 Efficient presence distribution mechanism for a large enterprise

Country Status (4)

Country Link
US (1) US9299111B2 (en)
EP (1) EP2891279B1 (en)
CN (1) CN104604189B (en)
WO (1) WO2014036903A1 (en)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9344458B2 (en) * 2012-07-16 2016-05-17 eZuce, Inc. Providing unified communications services
US10447575B1 (en) 2012-12-27 2019-10-15 Sitting Man, Llc Routing methods, systems, and computer program products
US20140189154A1 (en) * 2012-12-27 2014-07-03 Deep River Ventures, Llc Methods, Systems, and Computer Program Products for Determining a Shared Identifier for a Hop in a Network
US10397101B1 (en) * 2012-12-27 2019-08-27 Sitting Man, Llc Routing methods, systems, and computer program products for mapping identifiers
US10212076B1 (en) * 2012-12-27 2019-02-19 Sitting Man, Llc Routing methods, systems, and computer program products for mapping a node-scope specific identifier
US10587505B1 (en) 2012-12-27 2020-03-10 Sitting Man, Llc Routing methods, systems, and computer program products
US10404583B1 (en) * 2012-12-27 2019-09-03 Sitting Man, Llc Routing methods, systems, and computer program products using multiple outside-scope identifiers
US20140189153A1 (en) * 2012-12-27 2014-07-03 Deep River Ventures, Llc Methods, Systems, and Computer Program Products for Routing Based on a Scope-Specific Address
US10904144B2 (en) 2012-12-27 2021-01-26 Sitting Man, Llc Methods, systems, and computer program products for associating a name with a network path
US10411997B1 (en) * 2012-12-27 2019-09-10 Sitting Man, Llc Routing methods, systems, and computer program products for using a region scoped node identifier
US10411998B1 (en) * 2012-12-27 2019-09-10 Sitting Man, Llc Node scope-specific outside-scope identifier-equipped routing methods, systems, and computer program products
US10397100B1 (en) * 2012-12-27 2019-08-27 Sitting Man, Llc Routing methods, systems, and computer program products using a region scoped outside-scope identifier
US10419335B1 (en) * 2012-12-27 2019-09-17 Sitting Man, Llc Region scope-specific outside-scope indentifier-equipped routing methods, systems, and computer program products
US10419334B1 (en) * 2012-12-27 2019-09-17 Sitting Man, Llc Internet protocol routing methods, systems, and computer program products
US10404582B1 (en) 2012-12-27 2019-09-03 Sitting Man, Llc Routing methods, systems, and computer program products using an outside-scope indentifier
US9342554B2 (en) * 2013-07-05 2016-05-17 Facebook, Inc. Techniques to generate mass push notifications
EP3104558B1 (en) * 2015-06-11 2018-12-12 Airbus Defence and Space GmbH Network interface, network and method for transferring data within the network
CN107735817B (en) * 2015-06-15 2021-04-30 亚萨合莱有限公司 Credential cache
US20170339086A1 (en) * 2016-05-19 2017-11-23 Machine Zone, Inc. Efficient message exchange system

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003049459A1 (en) 2001-12-07 2003-06-12 Telefonaktiebolaget Lm Ericsson (Publ) Service access and conferencing system and method in a telecommunications network
US20080288572A1 (en) 2007-05-14 2008-11-20 Galvin Jr James Patrick Scalable presence server architecture
CN101345742A (en) * 2007-07-11 2009-01-14 飞塔信息科技（北京）有限公司 System and method for displaying instant communication user state
CN101635689A (en) * 2009-06-18 2010-01-27 北京亿企通信息技术有限公司 Method for detecting friend state in instant messaging tool
US20110230173A1 (en) * 2010-03-18 2011-09-22 BLC Wireless Oy Method and system for managing status information of a user of a mobile device
CN102347847A (en) * 2011-09-26 2012-02-08 深圳中兴网信科技有限公司 Contact state releasing method and system

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7184415B2 (en) * 2001-12-07 2007-02-27 Telefonaktiebolaget Lm Ericsson (Publ) Service access system and method in a telecommunications network
US20060010203A1 (en) * 2004-06-15 2006-01-12 Nokia Corporation Personal server and network
DE102004044987A1 (en) * 2004-09-16 2006-03-30 Siemens Ag A method, computer program with program code means and computer program product for monitoring a system state of a distributed component system, in particular a distributed component network, a distributed component network
US7464168B1 (en) * 2004-10-19 2008-12-09 Sun Microsystems, Inc. Mechanism for decentralized entity presence
CN1794709A (en) * 2005-11-04 2006-06-28 华为技术有限公司 Noticing method and system of display information
US7676577B2 (en) * 2004-12-21 2010-03-09 Alcatel Lucent Scalable presence distribution system and method
US20070165554A1 (en) * 2004-12-23 2007-07-19 Agovo Communications Inc. System, Method and Portable Communication Device
EP1724971B1 (en) * 2005-03-10 2008-07-09 Hewlett-Packard Development Company, L.P. Server system, server device, and method therefor
US20070124393A1 (en) * 2005-11-18 2007-05-31 Oracle International Corporation Presence based notifications
US8078191B2 (en) * 2007-01-10 2011-12-13 Synchronica Plc System and method of updating presence information
JP5239184B2 (en) * 2007-03-20 2013-07-17 日本電気株式会社 Presence service system
JP4753316B2 (en) * 2007-07-03 2011-08-24 株式会社Ｋｄｄｉ研究所 Load distribution server and program for distributing and managing load of presence information
EP2020801A1 (en) * 2007-07-31 2009-02-04 Seiko Epson Corporation Posting server, sending terminal, posting server control method and sending terminal control method
US8060121B1 (en) * 2007-11-06 2011-11-15 Sprint Spectrum L.P. Mobile network presence service with load-based notification throttling
EP2073118A1 (en) * 2007-12-17 2009-06-24 Nokia Siemens Networks Oy Load distribution in distributed database system
US8553534B2 (en) * 2007-12-21 2013-10-08 Telecom Italia S.P.A. Protecting an ethernet network having a ring architecture
US7814051B2 (en) * 2008-01-09 2010-10-12 International Business Machines Corporation Managing watcher information in a distributed server environment
US20090276653A1 (en) * 2008-05-02 2009-11-05 Pattabhiraman Ramesh V Presence server for discrete time updates
US8203932B2 (en) * 2008-12-02 2012-06-19 Electronics And Telecommunications Research Institute Method and system for protection switching in ethernet ring
ES2702464T3 (en) * 2009-06-17 2019-03-01 Bridgeport Networks Inc Improved presence detection for routing decisions
US8458321B2 (en) * 2009-06-26 2013-06-04 Motorola Solutions, Inc. Method and system of updating presence information in a communication system
US8880725B2 (en) * 2010-05-26 2014-11-04 Microsoft Corporation Continuous replication for session initiation protocol based communication systems
TWI455525B (en) * 2011-08-09 2014-10-01 Nat Univ Tsing Hua Recovery method for ring-based network

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003049459A1 (en) 2001-12-07 2003-06-12 Telefonaktiebolaget Lm Ericsson (Publ) Service access and conferencing system and method in a telecommunications network
US20080288572A1 (en) 2007-05-14 2008-11-20 Galvin Jr James Patrick Scalable presence server architecture
CN101345742A (en) * 2007-07-11 2009-01-14 飞塔信息科技（北京）有限公司 System and method for displaying instant communication user state
CN101635689A (en) * 2009-06-18 2010-01-27 北京亿企通信息技术有限公司 Method for detecting friend state in instant messaging tool
US20110230173A1 (en) * 2010-03-18 2011-09-22 BLC Wireless Oy Method and system for managing status information of a user of a mobile device
CN102347847A (en) * 2011-09-26 2012-02-08 深圳中兴网信科技有限公司 Contact state releasing method and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2891279A4

Also Published As

Publication number Publication date
US9299111B2 (en) 2016-03-29
EP2891279A4 (en) 2015-08-19
US20140067911A1 (en) 2014-03-06
CN104604189A (en) 2015-05-06
CN104604189B (en) 2018-05-04
EP2891279B1 (en) 2016-12-21
EP2891279A1 (en) 2015-07-08

Similar Documents

Publication Publication Date Title
US9299111B2 (en) Efficient presence distribution mechanism for a large enterprise
JP5898980B2 (en) Method, system, and storage medium for managing multiple queues of non-persistent messages in a network environment
US8996637B2 (en) Push notification delivery system
CN103718578B (en) Method and device for notification messages and providing notification messages
US10171661B2 (en) System and method of distributed maintenance of contact center state
US11128991B2 (en) Method, apparatus, and system for floor control on multiple MCPTT systems
RU2608469C2 (en) Method and apparatus for high performance low latency real time notification delivery
CN101809950A (en) Method and apparatus for performing load balancing for a control plane of a mobile communication network
US20170019484A1 (en) System and method for aggregating communication connections
US20160142275A1 (en) Method, system and apparatus for detecting instant message spam
CN113747373B (en) Message processing system, device and method
US9088629B2 (en) Managing an electronic conference session
US20170048081A1 (en) Multi-ring reliable messaging system
US10268532B2 (en) Application message processing system, method, and application device
US10063648B2 (en) Relaying mobile communications
US10157102B2 (en) Techniques to scan and reorganize media files to remove gaps
CN110247847B (en) Method and device for back source routing between nodes
CN109831385B (en) Message processing method and device and electronic equipment
CN111866100A (en) Method, device and system for controlling data transmission rate
GB2545639B (en) Presence notifications
KR20140040948A (en) System and method for dynamic message routing
CN115022110B (en) Message distribution method, readable medium and electronic device
CN103780503A (en) Load balancing realization method and apparatus
US20240031486A1 (en) Batch Ringing For Large Call Queues
CN113452739A (en) Message processing method and device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13835415

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2013835415

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2013835415

Country of ref document: EP