Automatic user device presence registration system
Claim Score by NHIP
Abstract
A user device automatically sends a presence message to a presence server when the user device is powered on. Thereafter, the user device may send a sleep message to the presence server upon power down or prolonged period of inactivity, or the device may be required to send periodic messages to the presence server to maintain it as being listed as an active device. The presence server is then used to manage communication with the user device based on the presence information.

Term
Term ended
Projected expiry passed 21 June 2024, 2.3 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
21 claims: 6 independent, 15 dependent
- 1A system for managing communication with at least one user device, comprising:at least one presence server receiving at least one of: a first message automatically generated and transmitted by a user device when the user device receives a power down command, and/or when the user device has not been operated for a predetermined period, and/or when a user device receives a power on message, and a second message automatically generated and transmitted by a user device indicating the user device should remain indicated as being active, the presence server using the messages to maintain data indicating user devices available for communication.
- 6A user device comprising:means for registering with a presence server;at least one means selected from the group consisting of: means for generating, without user intervention, a message to the presence server indicating that the user device has been inactive for a period longer than a threshold, whereby the presence server can indicate the user device as being available for communication;and means for generating, without user intervention and after having been authenticated with the presence server, a message to the presence server indicating that the user device remains available for communication, whereby the presence server can indicate the user device as remaining available for communication.
- 11A user computing device comprising logic embodying method acts including:generating, without user intervention, a message to a presence server indicating that the user device has been inactive for a period longer than a threshold, whereby the presence server can indicate the user device as being available for communication.
- 12A user computing device comprising logic embodying method acts including:generating, without user intervention and while being indicated as being an active device by a presence server, a message to the presence server indicating that the user device remains available for communication, whereby the presence server can continue to indicate the user device as remaining available for communication.
- 13A presence server, comprising logic for undertaking method acts comprising:maintaining data indicating what devices are active based at least in part on at least one of: user device messages indicating no activity at the user device for a period at least a great as a threshold, and user device messages indicating continuing desire to remain designated an active device.
- 18Broadest claimClaim Score 92, very broad(NHIP)A method for advertising over the Internet, comprising:accessing information in a presence server indicating active user devices;and based on the information, transmitting, over the Internet, at least one advertisement to the active user devices.
Independent claims6
26 paragraphs in 6 sections, as filed
RELATED APPLICATIONS
0001This application claims priority from U.S. provisional application Ser. No. 60/544,602, filed Feb. 12, 2004.
FIELD OF THE INVENTION
0002The present invention relates generally to Internet communications that are managed by presence servers.
BACKGROUND
0003To send a message to a recipient, the message must be addressed to the recipient using the protocol of a particular communication or messaging system. For example, email messages require a SMTP, IMAP, or POP address. As part of sending a message, the sender must decide which messaging service is best suited to deliver the message, including determining which service will recognize the recipient. This can require that the recipient be available on the service.
0004Accordingly, in determining accessibility it is often necessary to have reliable presence information relating to intended recipients. In some systems such as instant messaging systems, presence information is maintained once the user logs onto the service. However, this requires the user to invoke the instant messaging application, which the user might forget to do. Moreover, once logged on, the system has no way of determining whether the user is actually observing the user device terminal and, hence, has no way of knowing whether the user, as opposed to the user device, is actually present unless the user logs off or otherwise indicates that he or she is away. With this in mind, the inventions herein are provided.
SUMMARY OF THE INVENTION
0005A system for managing communication with a user device includes a presence server that receives a message which is automatically generated and transmitted by a user device when the user device has been powered down, and/or when the user device has not been operated for a predetermined period, and/or when the user device receives a power on message. Also, the presence server may receive another type of message that is automatically generated and transmitted by a user device which indicates the user device should remain indicated as being active. The presence server uses the messages to maintain data indicating user devices available for communication.
0006In another aspect, a user device includes means for registering with a presence server, and means for generating, without user intervention, a message to the presence server indicating that the user device has been inactive for a period longer than a threshold. In addition or alternatively, the user device can generate a message to the presence server indicating that the user device remains available for communication. With this invention, the presence server can indicate the user device as being available for communication.
0007In yet another aspect, a presence server maintains data indicating what devices are active based on user device messages indicating no activity at the user device for a period at least a great as a threshold, and/or based on user device messages indicating continuing desire to remain designated an active device.
0008In still another aspect, a method for advertising over the Internet includes accessing information in a presence server indicating active user devices. The method also includes, based on the information, transmitting, over the Internet, at least one advertisement to the active user devices.
0009The details of the present invention, both as to its structure and operation, can best be understood in reference to the accompanying drawings, in which like reference numerals refer to like parts, and in which:
BRIEF DESCRIPTION OF THE DRAWINGS
0010<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of the present system;
0011<figref idref="DRAWINGS">FIG. 2</figref> is a flow chart showing the set up process;
0012<figref idref="DRAWINGS">FIG. 3</figref> is a flow chart showing the subsequent log on process;
0013<figref idref="DRAWINGS">FIG. 4</figref> is a flow chart showing the automatic sleep message process;
0014<figref idref="DRAWINGS">FIG. 5</figref> is a flow chart showing the automatic keep alive process; and
0015<figref idref="DRAWINGS">FIG. 6</figref> is a flow chart showing a method for advertising using the presence server.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
0016Referring initially to <figref idref="DRAWINGS">FIG. 1</figref>, a system is shown, generally designated <b>10</b>, that includes a presence server <b>12</b>. The presence server <b>12</b> may be any appropriate Internet-capable server computer, and it may be owned by or associated with a particular organization. Without limitation, the presence server may be an instant messaging server.
0017As shown in <figref idref="DRAWINGS">FIG. 1</figref>, the presence server <b>12</b> can communicate, over the Internet <b>14</b>, with Internet Service Provider (ISP) servers/networks <b>16</b> (only a single ISP server <b>16</b> shown for clarity). The ISP server/network <b>16</b> in turn provides a gateway to the Internet <b>14</b>, including to the presence server <b>12</b>, in accordance with principles known in the art for a user's various computing devices (only the devices of a single user shown for illustration). Specifically, a user can communicate with the ISP server <b>16</b> using a mobile computer <b>18</b> such as a Sony Clie® and a home PC, laptop, or home network computing system <b>20</b> (shown as two blocks in <figref idref="DRAWINGS">FIG. 1</figref> to indicate that a standalone PC <b>20</b> can communicate directly with the ISP server <b>16</b> or through a home network). The computing devices <b>18</b>, <b>20</b> communicate using software such as browsers and hardware such as, e.g., modems, or wireless communication systems, or other means known in the art. Also, the user might access the presence server <b>12</b> using his or her office computer/computer network system <b>22</b> (likewise shown as two blocks in <figref idref="DRAWINGS">FIG. 1</figref> to indicate both the office PC and the office network). As well, the mobile device <b>18</b> might include wireless communication capability, such as a mobile telephone chip or system, that communicates with various base stations <b>26</b> in a wireless communication system and thus with an Internet-accessing wireless communication system server/network <b>28</b>. As shown, the wireless communication system server <b>28</b> communicates with the presence server <b>12</b> using the Internet. Still further, the mobile device <b>18</b> might possess capabilities such as wi-fi to communicate with the presence server <b>12</b> through the Internet <b>14</b> and a local relay station <b>29</b>, colloquially referred to as a “hot spot”.
0018<figref idref="DRAWINGS">FIG. 2</figref> shows how a user can set up one or more of the user devices to cooperate with the presence server <b>12</b> to implement the present invention. Commencing at block <b>30</b>, communication is established between, e.g., the home PC <b>20</b> and the ISP server <b>16</b>. Then, at block <b>32</b> subscription information such as the user's name, billing information, user ID, and password are sent to the server. Block <b>34</b> indicates that the server may respond with an acknowledgement of the user ID and password.
0019At block <b>36</b>, communication is established between the user device and the presence server <b>12</b>, which accesses the registration information sent at block <b>32</b>. That is, the initial registration information exchange can be between the ISP server <b>16</b> and user device, or it can be direct between the user device and the presence server <b>12</b>.
0020In any case, at block <b>38</b> application software for executing the service associated with the presence server <b>12</b> is downloaded to the user device. Authentication information can be sent to the presence server <b>12</b> at block <b>40</b> in accordance with Internet authentication principles known in the art. The user is authenticated at block <b>42</b> and as part of the authentication process a cookie or other token may be returned to the user device. Each user device in turn can be registered by sending authentication information from the device to the presence server and receiving back a token for that device.
0021<figref idref="DRAWINGS">FIG. 3</figref> shows the non-limiting process that can be followed after registration. Commencing at block <b>44</b>, one of the user devices is turned on, or logged onto the Internet, or unlocked. Automatically, at block <b>46</b> the user device sends a message to the presence server <b>12</b> indicating that the device is present and available for communication. The message can be sent with the device's token if desired. At block <b>48</b> the presence server updates a data structure such as a list, table, or other structure of active devices to reflect the presence of the user device. The presence server <b>12</b> may alert other active devices that the user device has just become available for communication. Block <b>50</b> indicates that the other devices may address messages to the user device which, owing to its being included in the data structure of the presence server <b>12</b>, receives messages through the presence server <b>12</b>.
0022The present invention recognizes that once a user device is reflected as being present, the user of the device may, at some point, stop using the device without logging off or otherwise indicating that the user himself or herself is no longer monitoring the device. Accordingly, <figref idref="DRAWINGS">FIG. 4</figref> shows that when it is determined at decision diamond <b>52</b> that an active user device has been inactive for longer than a threshold period or that a user has entered a “deenergize” command, an “inactive” or “off” message can be automatically (without user intervention or interaction) sent by the user device to the presence server at block <b>54</b> so indicating. Inactivity can be indicated by, e.g., a lack of an input from a keyboard or mouse for longer than the threshold period, and can be determined by the user device itself. At block <b>56</b> the data structure of active user devices is updated by the presence server <b>12</b>, and then at block <b>58</b> the presence server <b>12</b> can send an acknowledgement to the user device that the user device is no longer active. The user device and/or presence server may clear authentication codes, and the user device can enter a power save mode, screen saver mode, or can even deenergize itself (particularly if battery-powered) automatically.
0023In contrast, when, for instance, the user device is a mobile computing device, it may be desirable to automatically remove the device from the data structure of active devices unless messages are periodically received from the device. Accordingly, referring now to <figref idref="DRAWINGS">FIG. 5</figref>, if a user device that is active with the presence server <b>12</b> determines at decision diamond <b>60</b> that the user has not input a command to deactivate, the logic moves to block <b>62</b> to automatically (without user intervention) send a message to the presence server <b>12</b> indicating that the user device should remain indicated as being active. An acknowledgement of receiving the message and continuing the active status of the user device may be sent by the presence server <b>12</b> to the user device at block <b>64</b>. It is to be understood that for a user device employing the logic of <figref idref="DRAWINGS">FIG. 5</figref>, failure on the part of the presence server <b>12</b> to receive a message from the user device after the elapse of a predetermined time period will cause the presence server <b>12</b> to remove the user device from the data structure of active devices.
0024<figref idref="DRAWINGS">FIG. 6</figref> shows an exemplary application afforded by the presence server <b>12</b> system described above. At block <b>66</b> an advertiser, by means of an advertising Web server (not shown), can communicate with the presence server to access information in the presence server indicating active user devices. Then, at block <b>68</b>, based on the information, advertisements can be transmitted over the Internet only to the active user devices. The advertisements can be sent from the presence server <b>12</b> if desired, or the presence server <b>12</b> can provide active user information to the advertiser who can send the advertisements directly to user devices. If desired, active user devices receiving advertisements may acknowledge receipt at block <b>70</b>, with accounting data being generated at block <b>72</b>.
0025The accounting data is based on the advertisements. In one non-limiting embodiment, accounting data is generated only for advertisements sent to users who return acknowledgements of receipt of the advertisement. Or, accounting data can be generated for advertisements sent to active user devices regardless of acknowledgements of receipt. If desired, a user device service charge can be reduced for users agreeing to accept advertisements.
0026While the particular AUTOMATIC USER DEVICE PRESENCE REGISTRATION SYSTEM as herein shown and described in detail is fully capable of attaining the above-described objects of the invention, it is to be understood that it is the presently preferred embodiment of the present invention and is thus representative of the subject matter which is broadly contemplated by the present invention, that the scope of the present invention fully encompasses other embodiments which may become obvious to those skilled in the art, and that the scope of the present invention is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean “one and only one” unless explicitly so stated, but rather “one or more”. It is not necessary for a device or method to address each and every problem sought to be solved by the present invention, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. Absent express definitions herein, claim terms are to be given all ordinary and accustomed meanings that are not irreconcilable with the present specification and file history.
Contents6
5 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2007142065A1 | Cited by | United States of America | Pre-grant |
| US8539365B2 | Cited by | United States of America | Applicant |
| US2009019298A1 | Cited by | United States of America | Pre-grant |
| US2009063677A1 | Cited by | United States of America | Pre-grant |
| US2008040433A1 | Cited by | United States of America | Pre-grant |
| CN104584485A | Cited by | China | Search report |
| WO2005089485A2 | Cited by | World Intellectual Property Organization (WIPO) | Applicant |
| US7809968B2 | Cited by | United States of America | Applicant |
| US10303510B2 | Cited by | United States of America | Search report |
| US2007061405A1 | Cited by | United States of America | Pre-grant |
| US2007242656A1 | Cited by | United States of America | Pre-grant |
| US8386769B2 | Cited by | United States of America | Applicant |
| US10117178B2 | Cited by | United States of America | Search report |
| US9065786B2 | Cited by | United States of America | Applicant |
| US2015331714A1 | Cited by | United States of America | Pre-grant |
| US10268493B2 | Cited by | United States of America | Search report |
| US2014040399A1 | Cited by | United States of America | Pre-grant |
| US2008201419A1 | Cited by | United States of America | Pre-grant |
| US2014040400A1 | Cited by | United States of America | Pre-grant |
| US2010169279A1 | Cited by | United States of America | Pre-grant |
| US2010095109A1 | Cited by | United States of America | Pre-grant |
| EP1845673A1 | Cited by | European Patent Office (EPO) | Search report |
| US2010083255A1 | Cited by | United States of America | Pre-grant |
| US8103730B2 | Cited by | United States of America | Applicant |
| EP1962473A1 | Cited by | European Patent Office (EPO) | Applicant |
| US9817741B2 | Cited by | United States of America | Applicant |
| US9065785B2 | Cited by | United States of America | Search report |
| US2008307042A1 | Cited by | United States of America | Pre-grant |
| US7412657B2 | Cited by | United States of America | Search report |
| US10475010B2 | Cited by | United States of America | Applicant |
| US2010099387A1 | Cited by | United States of America | Pre-grant |
| US8473733B2 | Cited by | United States of America | Applicant |
| US2009171762A1 | Cited by | United States of America | Pre-grant |
| US2008040485A1 | Cited by | United States of America | Pre-grant |
| US7899171B2 | Cited by | United States of America | Search report |
| US2006048061A1 | Cited by | United States of America | Pre-grant |
| WO2010044899A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US8375088B2 | Cited by | United States of America | Applicant |
| US8935350B2 | Cited by | United States of America | Applicant |
| US2011119599A1 | Cited by | United States of America | Pre-grant |
| WO2005089485A2 | Cited by | World Intellectual Property Organization (WIPO) | Applicant |
| US2010093366A1 | Cited by | United States of America | Pre-grant |
| US9781677B2 | Cited by | United States of America | Applicant |
| US2010064051A1 | Cited by | United States of America | Pre-grant |
| US9571431B2 | Cited by | United States of America | Applicant |
| US2007071204A1 | Cited by | United States of America | Pre-grant |
| US2008037755A1 | Cited by | United States of America | Pre-grant |
| US8473562B2 | Cited by | United States of America | Applicant |
| US8751584B2 | Cited by | United States of America | Applicant |
| US2010100617A1 | Cited by | United States of America | Pre-grant |
| US9426100B2 | Cited by | United States of America | Search report |
| US2014040398A1 | Cited by | United States of America | Pre-grant |
| US2010077038A1 | Cited by | United States of America | Pre-grant |
| US7774001B2 | Cited by | United States of America | Applicant |
| US2017150443A1 | Cited by | United States of America | Pre-grant |
| US10506194B2 | Cited by | United States of America | Search report |
| US2008126475A1 | Cited by | United States of America | Pre-grant |
| US2008133742A1 | Cited by | United States of America | Pre-grant |
| EP1962473A1 | Cited by | European Patent Office (EPO) | Search report |
| US2006064502A1 | Cited by | United States of America | Pre-grant |
| US8312092B2 | Cited by | United States of America | Applicant |
| US2010199307A1 | Cited by | United States of America | Pre-grant |
| US9094352B2 | Cited by | United States of America | Search report |
| US8589496B2 | Cited by | United States of America | Search report |
| US8095603B2 | Cited by | United States of America | Applicant |
| RU2720639C1 | Cited by | Russian Federation | Search report |
| US7890875B2 | Cited by | United States of America | Applicant |
| US2010094993A1 | Cited by | United States of America | Pre-grant |
| US2009006624A1 | Cited by | United States of America | Pre-grant |
| US8504525B2 | Cited by | United States of America | Search report |
| US8355320B1 | Cited by | United States of America | Search report |
| CN101924844A | Cited by | China | Search report |
| US8335825B2 | Cited by | United States of America | Search report |
| US8099670B2 | Cited by | United States of America | Applicant |
| US2010093328A1 | Cited by | United States of America | Pre-grant |
| US9083660B2 | Cited by | United States of America | Search report |
| US2006253593A1 | Cited by | United States of America | Pre-grant |
| US8682994B2 | Cited by | United States of America | Applicant |
| US2010131754A1 | Cited by | United States of America | Pre-grant |
| KR100917555B1 | Cited by | Republic of Korea | Search report |
| US8554856B2 | Cited by | United States of America | Search report |
| WO2021040565A3 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2012117568A1 | Cited by | United States of America | Pre-grant |
| US8332474B2 | Cited by | United States of America | Applicant |
| US2001031641A1 | Cites | United States of America | Pre-grant |
| US2002035605A1 | Cites | United States of America | Pre-grant |
| US2002065894A1 | Cites | United States of America | Pre-grant |
| US2002078150A1 | Cites | United States of America | Pre-grant |
| US2002126701A1 | Cites | United States of America | Pre-grant |
| US2002163572A1 | Cites | United States of America | Pre-grant |
| US2003028597A1 | Cites | United States of America | Pre-grant |
| US2003041141A1 | Cites | United States of America | Pre-grant |
| US2003065788A1 | Cites | United States of America | Pre-grant |
| US2003131142A1 | Cites | United States of America | Pre-grant |
| US2003154293A1 | Cites | United States of America | Pre-grant |
| US2004003042A1 | Cites | United States of America | Pre-grant |
| US2004028208A1 | Cites | United States of America | Pre-grant |
| US2004059781A1 | Cites | United States of America | Pre-grant |
| US2004064511A1 | Cites | United States of America | Pre-grant |
| US2004071150A1 | Cites | United States of America | Pre-grant |
9 members in 5 offices
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 54460204 | United States of America | P | |
| 54460204 | United States of America | P | |
| 87299304 | United States of America | A | |
| 60544602 | – | – | – |
| US20040544602P | – | – | – |
| US20040872993 | – | – | – |
Members9
| Document | Office | Kind | |
|---|---|---|---|
| US2005198545A1 | United States of America | A1 | |
| WO2005081738A2 | World Intellectual Property Organization (WIPO) | A2 | |
| EP1714205A2 | European Patent Office (EPO) | A2 | |
| KR20070001128A | Republic of Korea | A | |
| WO2005081738A3 | World Intellectual Property Organization (WIPO) | A3 | |
| CN1965284A | China | A | |
| CN1965284B | China | B | |
| EP1714205A4 | European Patent Office (EPO) | A4 | |
| KR101089401B1 | Republic of Korea | B1 |
65 transactions on the USPTO file
Abandoned after 2 non-final rejections, 2 final rejections, 1 RCE and 1 appeal.
- Non-final rejections
- 2
- Final rejections
- 2
- RCEs
- 1
- Appeals
- 1
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Mailing of Abandonment after Board of AppealsAbandonedMABN10 | MABN10 | |
| Abandonment after Board of AppealsAbandonedABN10 | ABN10 | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Mail BPAI Decision on Appeal - AffirmedMAPDA | MAPDA | |
| BPAI Decision - Examiner AffirmedAPDA | APDA | |
| Docketing Notice Mailed to AppellantAP_DK_M | AP_DK_M | |
| Assignment of Appeal NumberAPAS | APAS | |
| Appeal Awaiting BPAI DocketingAPWD | APWD | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Mail Reply Brief Noted by ExaminerMRBNE | MRBNE | |
| Reply Brief Noted by ExaminerRBNE | RBNE | |
| Return of Undocketed appeal to the TCTCRD | TCRD | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Exam. Ans. Review CompletePACC | PACC | |
| Reply Brief FiledAPRB | APRB | |
| Mail Examiner's AnswerMAPEA | MAPEA | |
| Examiner's Answer to Appeal BriefAPEA | APEA | |
| Appeal Brief Review CompleteAPBR | APBR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Appeal Brief FiledAP.B | AP.B | |
| Notice of Appeal FiledN/AP | N/AP | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| New or Additional Drawing FiledC614 | C614 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response to Election / Restriction FiledELC. | ELC. | |
| Mail Restriction RequirementMCTRS | MCTRS | |
| Restriction/Election RequirementCTRS | CTRS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Correspondence Address ChangeC.ADB | C.ADB | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Return from OIPEWROIPE | WROIPE | |
| Application Return TO OIPEROIPE | ROIPE | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Initial Exam Team nnIEXX | IEXX |
3 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Information on status: application discontinuationABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISIONSTCB | STCB | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 20050198545
- Publication, DOCDB
- 2005198545
- Publication, EPODOC
- US2005198545
- Application
- 10872993
- Application, DOCDB
- 87299304
- Application, EPODOC
- US20040872993
Titles
- English
- Automatic user device presence registration system
Classification
- CPC, 6
- H04L51/04
- H04L67/54
- G06F15/16
- G06F1/30
- G06F1/00
- G06F9/00
- IPC, 5
- G06F1 30
- G06F12 14
- G06F15 173
- H04L12 58
- H04L29 08
- USPC, 2
- 713323000
- 709224000