PATENT CLAIM ANALYSIS

Application Number: 15775493
Application Type: Utility
Filing Date: 2018-05
Publication Date: 2018-12
Patent Classification: ["379", "211010"]

Abstract:
The invention namely provides a presence server ( 103 ) comprising: —a data repository in which is stored a plurality of user ( 106, 107 ) identities recorded in association with at least one device address and a status, —an input interface for receiving a busy or available status updating request ( 2 ) comprising an address of a calling device ( 201 ) and a called user ( 107 ) identity of a user of a called device ( 202 ), —a processing unit configured to: when the input interface receives the busy status updating request ( 2 ): —retrieve from the data repository a calling user ( 106 ) identity, —change the status associated to the calling user ( 106 ) identity into a busy status, when the input interface receives the available status updating request ( 7 ), change the status associated to the calling user identity into an available status, —an output interface to access the status of user identities.

Claim (Index 21):
A presence system in a communication system comprising:\n a presence server comprising a directory of users on the communication system, comprising a plurality of user identities, each user identity identifying a user in association with at least one terminal address, and each user identity being associated with a status that is either \u00abbusy\u00bb or \u00abavailable\u00bb, wherein the users of the communication system may update information in relation to their identity and associated terminals through display endpoints; a first presence agent associated with a first Private Branching eXchange (PBX), comprising a first database comprising a plurality of user identities, each user identity identifying a user in association with at least one terminal address of a terminal connected to the first PBX; and a second presence agent associated with a second PBX, comprising a second database comprising a plurality of user identities, each user identity identifying a user in association with at least one terminal address of a terminal connected to the second PBX;\n the presence server, the first and the second presence agents being interconnected via a messaging and signaling system and protocol, \n wherein the presence server is configured to, upon request from a first user using a first terminal which is not connected to the first PBX: \n update information in the directory in relation to the identity of the first user and the associated first terminal;\n wherein the second presence agent is configured to, upon the second PBX receiving from an operator a call placed by the first user using the first terminal, to a second user using a second terminal connected to the second PBX, the call comprising the information of the number of the first terminal and the number of the second terminal, and routing the call to the second terminal: \n retrieve in the second database the identity of the second user; and send to the presence server a request for identity of the first user, the request comprising the number of the first terminal and the identity of the second user;\n wherein the presence server is further configured to, upon request from the second presence agent comprising the number of the first terminal and the identity of the second user:\n retrieve in the directory the identity of the first user; \n change in the directory a presence status for the second user from \u00abavailable\u00bb to busy\u00bb; and \n return to the second presence agent the identity of the first user; \n \n wherein the second presence agent is further configured to: \n receive from the presence server the identity of the first user; and \n send to the first presence agent information that the first user should have a presence status of \u00abbusy\u00bb; \n wherein the first presence agent is configured to: \n send to the presence server a request for changing the presence status for the first user from \u00abavailable\u00bb to \u00abbusy\u00bb; \n and wherein the presence server is yet further configured to, upon request from the first presence agent: \n change in the directory a presence status for the first user from \u00abavailable\u00bb to busy\u00bb.

Metadata:
- Claim Count in Document: 35.0
- Percentile: 93.0
- Lexical Diversity: 2.5
- Patent Class: 379.0
- Transitional Phrase Type: open
- Component Type: 1
- Foreign Priority: True
- Related Applications: ['15163517', '11766368', '13357732', '12136335', '12211431']

Analysis Scores:
- 35 USC 101 Eligibility (BERT): 0.4619318206608023
- 35 USC 102 Novelty (BERT): 0.4851496716090945
- Combined Prediction Score: 0.4642536057556315
- Mean Citation Score: 176.974756
- Max Citation Score: 188.01196
- Similarity Product: 128.43093345972775

Labels:
- Claim Label 101: 1
- Claim Label 102: 1
- Claim Label 103: 1
- Claim Label 112: 0
- Combined Label: 1
- Label 101 Adjusted: 1

Dataset: test