Determining the context of a computing device
Summary by NHIP
Context sensing after power off
The method receives a remote request for device context after power loss, activates a sensor, and transmits the data while the device remains off. The context aware circuit turns off the sensor immediately after obtaining the information.
Claim Score by NHIP
Abstract
In some embodiments a remote request is received relating to a context of a device after the device has been powered off. A sensor of the device is turned on to obtain context information of the device from the sensor. The obtained context information is provided from the device to a remote device while the device is still powered off. Other embodiments are described and claimed.

Term
Projected expiry 27 September 2027.
- Priority
- Filed
- Granted
- Today
- Projected expiry
17 claims: 3 independent, 14 dependent
- 1A method comprising:receiving, by a context aware circuit, a remote request relating to a context of a device after the device has been powered off;turning on, by the context aware circuit, a sensor of the device to obtain context information of the device from the sensor;providing, by the context aware circuit, the obtained context information from the device to a remote device while the device is still powered off;and turning off, by the context aware circuit, the sensor after the context information has been obtained from the sensor.
- 4An apparatus comprising:a processor comprising a context aware circuit to receive a remote request relating to a context of a device after the device has been powered off, to turn on a sensor of the device to obtain context information of the device from the sensor, to provide the context information to a remote device while the device is still powered off, and to turn off the sensor after the context information has been obtained from the sensor.
- 11Broadest claimClaim Score 89, very broad(NHIP)A system comprising:a sensor;and an input/output controller to receive a remote request relating to a context of the system after the system has been powered off, to turn on the sensor to obtain context information of the system from the sensor, to provide the context information to a remote device while the system is still powered off, and to turn off the sensor after the context information has been obtained from the sensor.
Independent claims3
32 paragraphs in 5 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATIONS
0001This application is a continuation of U.S. patent application Ser. No. 13/771,816 filed Feb. 20, 2013 entitled “Determining the Context of a Computing Device, which is a continuation of U.S. patent application Ser. No. 11/863,148, filed Sep. 27, 2007, now U.S. Pat. No. 8,387,078 issued Feb. 26, 2013 entitled “Determining the Context of a Computing Device That is Powered Off,” the entire contents of both applications are hereby incorporated by reference as though fully set forth herein.
TECHNICAL FIELD
0002The inventions generally relate to determining the context of a computing device.
BACKGROUND
0003A major barrier to greater Information Technology (IT) efficiency has been removed by Intel® Active Management Technology (Intel AMT). Using built-in platform capabilities and popular third party management and security applications, Intel AMT allows IT users to better discover, heal, and protect their networked computing assets. Intel AMT also includes built-in manageability to provide out-of-band management capabilities. This allows remote healing of systems after Operating System (OS) failures, for example. Further, alerting and event logging help to detect problems quickly and to reduce downtime. Intel AMT also protects networks by proactively blocking incoming threats, containing infected clients before they impact the network, and alerting IT when critical software agents are removed. Intel AMT also helps to protect the network by making it easier to maintain consistent and updated software and virus protection throughout the enterprise.
BRIEF DESCRIPTION OF THE DRAWINGS
The inventions will be understood more fully from the detailed description given below and from the accompanying drawings of some embodiments of the inventions which, however, should not be taken to limit the inventions to the specific embodiments described, but are for explanation and understanding only.
<figref idref="DRAWINGS">FIG. 1</figref> illustrates a system according to some embodiments of the inventions.
<figref idref="DRAWINGS">FIG. 2</figref> illustrates a sequence diagram according to some embodiments of the inventions.
DETAILED DESCRIPTION
0007Some embodiments of the inventions relate to determining the context of a computing device.
0008In some embodiments a remote request is received relating to a context of a computer after the computer has been powered off. A sensor of the computer is turned on to obtain context information of the computer from the sensor. The obtained context information is provided from the computer to a remote device while the overall computer is still powered off (for example, the operating system is powered down).
0009In some embodiments a context aware circuit receives a remote request relating to a context of a computer after the computer has been powered off. The context aware circuit turns on a sensor of the computer to obtain context information of the computer from the sensor. The context aware circuit also provides the context information to a remote device while the computer is still powered off.
0010In some embodiments a system includes a sensor and an input/output controller. The input/output controller receives a remote request relating to a context of the system after the system has been powered off, turns on the sensor to obtain context information of the system from the sensor, and provides the context information to a remote device while the system is still powered off.
0011The computer industry has recently been moving toward “context aware computing”. Context aware computing moves the increasingly ubiquitous computing device (for example, desktop, laptop, tablet, personal digital assistant or PDA, Ultra Mobile Device or UMD, and/or smart phone, etc.) to a new level. In some embodiments this can occur by providing awareness to the current computing environment and also to the environment of the user. In response to this awareness according to some embodiments the computer helps the user by providing information that is relevant to the user's current context.
0012There are several examples of context aware computing that may be implemented according to some embodiments. For example, when a user is working at home a context-aware laptop might show personal information such as personal email, personal desktop, scores from the user's favorite sports teams, etc., and when the user is in the office it might show the user office information such as work email, work desktops, work favorites, company stock ticker, etc. In another example, if a sudden storm arises a context-aware calendaring application notifies the user that 15 additional minutes will be necessary for travel time to the user's next appointment. As another example, when a user moves from office to office (or site to site) a context-aware laptop of the user automatically reconfigures the default printer to the printer that is physically the closest, and may also direct the user to that printer if the user is not familiar with that office. In another example, if a user receives instant messages from the user's spouse, the messages appear without showing the content of the message if someone else is in the user's office or cubicle. In this manner the user can later look at the content when the other person leaves the office or cubicle. Similarly, if the user is alone in their office or cubicle when an instant message is received from the user's spouse that message is automatically shown to the user as it arrives. These examples are meant to be examples of some embodiments, but there are many other examples of the capabilities of such a context-aware platform according to some embodiments.
0013According to some embodiments context-aware applications may be implemented even when the computer of the user is turned off, in a suspend mode, in a hibernate mode, etc., but another system is interested in knowing about the context of the computer. For example, in some embodiments, a first computing device such as a laptop or other device might include a GPS (Global Positioning System) device, an accelerometer, a thermometer, an atmospheric pressure sensor and/or other context related devices coupled with and/or incorporated into the computing device. In some embodiments, even when the first computing device is turned off, a second computing device such as a PDA (for example, with a different user than the first computing device) can determine the context of the first computing device and the user of that device using sensors within the applications of the first computing device. For example, the second computing device might determine the user's location, travel speed, temperature information, etc., and be able to make a decision based on the information provided from both of the computing devices according to some embodiments.
0014<figref idref="DRAWINGS">FIG. 1</figref> illustrates a computer <b>100</b> according to some embodiments. In some embodiments computer <b>100</b> is a desktop, a laptop, a tablet, a personal digital assistant or PDA, an Ultra Mobile Device or UMD, a smart phone, and/or any other type of computing device. In some embodiments computer <b>100</b> includes one or more central processing unit (CPU) <b>102</b> (or processor), a memory controller hub (MCH) <b>104</b> (or Northbridge), an Input/Output Controller Hub (ICH) <b>106</b> (or Southbridge), a memory <b>108</b>, an Accelerated Graphics Port (AGP) device <b>110</b>, a Peripheral Component Interconnect (PCI) device <b>112</b>, a Universal Serial Bus (USB) device <b>114</b>, a power management controller <b>116</b>, flash memory <b>118</b>, a network connection <b>120</b>, a GPS device <b>122</b>, a thermometer <b>124</b>, an accelerometer <b>126</b>, an atmospheric pressure sensor <b>128</b>, and/or other sensors <b>130</b>. Active Management Technology (AMT) <b>132</b> such as Intel AMT may be distributed within the ICH <b>106</b>, the memory <b>108</b>, the network connection <b>120</b>, and/or other elements in the system. A context aware subsystem (CASS) <b>134</b> may be included, for example, in the ICH <b>106</b>. In some embodiments, many or all of the elements illustrated in <figref idref="DRAWINGS">FIG. 1</figref> are resident on a printed circuit board (PCB) such as a motherboard.
0015A computer system such as computer <b>100</b> may include one or more central processing units (CPUs) or processor(s) <b>102</b>. The CPU(s) <b>102</b> may be coupled to a chip set (for example, via a bus). The chipset may include a memory controller hub (MCH) <b>104</b> including a memory controller coupled to a system memory such as memory <b>108</b>. The system memory may store data and/or sequences of instructions that are executed by the CPU(s) or processing device(s) included in the computing system. The MCH may also include, for example, a display controller coupled to a display. The chipset further may include an input/output control hub (ICH) <b>106</b> coupled, for example, to the MCH <b>104</b> via a hub interface. The ICH <b>106</b> may be coupled, for example, to one or more input/output (I/O) devices. The ICH <b>106</b> may also be coupled to a peripheral bus (for example, a Peripheral Component Interconnect or PCI bus). A PCI bridge may be coupled to the PCI bus to provide a data path between the CPU(s) and peripheral devices.
0016With the release of Intel vPro™ technology, new capabilities have been incorporated into computers that actually operate while the system is turned off. For example, Intel AMT, which is a portion of Intel vPro™ technology, keeps part of the motherboard powered even when the computing system is turned off by the user. This small subsystem on the motherboard can respond to a remote request by a management application to do things such as power up the system, install an Operating System (OS) or application patch, etc., and then power the system back down again. AMT <b>132</b> of the computer <b>100</b> can help to perform these types of operations. AMT <b>132</b> allows, among other things, a system to be powered down but still respond to management requests over a network (via network connection <b>120</b>) to manage the system in this type of manner. In some embodiments, these same capabilities allow for a remote system to obtain context information for the system <b>100</b> while the system <b>100</b> is still shut down.
0017According to some embodiments, the AMT <b>132</b> and/or CASS <b>134</b> may be used to respond to requests to provide context information when the system <b>100</b> is powered up. In embodiments where system <b>100</b> is a desktop, for example, this is sometimes a feasible option. However, in other embodiments it may not be a feasible option since the system <b>100</b> is powered down for some reason (for example, a desktop that has already been powered down, a laptop that has been powered down to converse power, etc.). According to some embodiments, the AMT <b>132</b> and/or CASS <b>134</b> may be used to respond to requests to provide context information when the system <b>100</b> is powered down.
0018In some embodiments, when system <b>100</b> has been powered off by a user, CASS <b>134</b> continues to be powered so that it can respond to remote requests over a network (via network connector <b>120</b>). CASS <b>134</b> responds to remote requests that come in over the network connection <b>120</b> via the AMT subsystem <b>132</b>. The CASS <b>134</b> turns sensors such as sensors <b>122</b>, <b>124</b>, <b>126</b>, <b>128</b>, and/or <b>130</b> on and off as needed to collect context information for the system <b>100</b> and returns the collected context information to the requesting computer, for example, via AMT <b>132</b> and/or network connection <b>120</b>. As a result, authorized remote systems (for example, a PDA, a remote management system, and/or any other type of computing device) can obtain information about the context of the system <b>100</b> even when it is powered down, and the remote system can use that obtained information to provide context information to its own application and/or for other uses such as system inventory, for example.
0019As discussed above, CASS <b>134</b> continues to be powered even when the system <b>100</b> is powered down. This enables CASS <b>134</b> to respond to remote requests made, for example, over a network. Sensors <b>122</b>, <b>124</b>, <b>126</b>, <b>128</b>, and/or <b>130</b> allow the CASS to help the system <b>100</b> to determine its context. In some embodiments, sensors <b>122</b>, <b>124</b>, <b>126</b>, <b>128</b>, and/or <b>130</b> are typically turned off in order to conserve power unless a request comes through the CASS <b>134</b> to turn on or more of these sensors on in order to take a measurement, for example.
0020In some embodiments AMT <b>132</b> allows, among other things, the system <b>100</b> to be powered down but still respond to management requests over the network to manage the system. CASS <b>134</b> allows further capabilities of a remote system to obtain context information relating to system <b>100</b>. In some embodiments CASS <b>134</b> is logic added to the ICH <b>106</b> that allows the system <b>100</b> to respond to remote requests for context information. In some embodiments, these remote requests may be made over the AMT <b>132</b> network stack. In some embodiments, CASS <b>134</b> turns on one or more or all of the GPS sensor <b>122</b>, the thermometer <b>124</b>, the accelerometer <b>126</b>, the atmospheric pressure sensor <b>128</b>, and/or other sensors <b>130</b> to take readings of the context and/or environment of the system. The CASS <b>134</b> is also able to turn those sensors off after the readings are taken in order to conserve power. In some embodiments GPS <b>122</b> is a Global Positioning System device used to obtain location information such as, for example, latitude, longitude, and/or altitude of the system <b>100</b>. In some embodiments thermometer <b>124</b> is a sensor to determine an ambient temperature of the location of the system <b>100</b>. In some embodiments accelerometer <b>126</b> is a sensor to determine a direction of travel and an acceleration of the direction of travel of the system <b>100</b>. This can allow, for example, a determination of the speed of the system, for example. In some embodiments the atmospheric pressure gauge <b>128</b> is a sensor used to determine an atmospheric pressure around the system <b>100</b>. This information may be used, for example, to track and predict weather patterns and/or to estimate the altitude of the system <b>100</b>. In some embodiments, the other sensors <b>130</b> may be one or more sensors that perform functions such as, for example, detecting a presence of the user near the system <b>100</b>, detecting presence of other people near the system <b>100</b>, detecting body temperature(s), and/or detecting humidity levels, etc.
0021<figref idref="DRAWINGS">FIG. 2</figref> illustrates a sequence diagram <b>200</b> of an exemplary remote request between a remote system <b>202</b>, an AMT <b>204</b>, a CASS <b>206</b>, and/or a sensor <b>208</b>. Sensor <b>208</b> may be any sensor such as but not limited to sensors <b>122</b>, <b>124</b>, <b>126</b>, <b>128</b>, and/or <b>130</b> of <figref idref="DRAWINGS">FIG. 1</figref>, for example.
0022In the sequence diagram <b>200</b>, a request to get a value is made from the remote system <b>202</b> to the AMT <b>204</b>. The AMT <b>204</b> passes the request along to the CASS <b>206</b>, and the CASS <b>206</b> then turns on the sensor <b>208</b>. Then the CASS <b>206</b> passes a request along to the sensor <b>208</b> to obtain a value from the sensor (for example, a location value in embodiments where sensor <b>208</b> is a GPS device). The value is then returned from the sensor <b>208</b> to the CASS <b>206</b> and the CASS then turns off the sensor <b>208</b>. The value is then returned from the CASS <b>206</b> to the AMT <b>204</b>, and passed along to the remote system <b>202</b>. While <figref idref="DRAWINGS">FIG. 2</figref> illustrates a single sensor <b>208</b>, in some embodiments the get value request may be a request for several values that are requested at once and obtained by the CASS <b>206</b> at the same time from several sensors <b>208</b>. In some embodiments, the functions performed in the sequence diagram <b>200</b> are performed while a system including the AMT <b>204</b>, the CASS <b>206</b>, and/or the sensor <b>208</b> is turned off with system power only being supplied to some or all of the AMT <b>204</b>, the CASS <b>206</b>, and/or the sensor <b>208</b>. In some embodiments all elements of <figref idref="DRAWINGS">FIG. 1</figref> and/or <figref idref="DRAWINGS">FIG. 2</figref> may not be necessary. For example, in some embodiments, the CASS may be implemented without the AMT, and/or in some embodiments the AMT and the CASS may be included in one device, unit, logic, hardware, and/or software, etc.
0023In some embodiments the terms “context” and/or “environment” have been used. It is noted that according to some embodiments these terms may be the same and/or may be subsets of each other. Each term as used herein is intended to broadly encompass sensing of various conditions at and/or surrounding a system, computing device, and/or computer, etc.
0024Although some embodiments have been described in reference to particular implementations, other implementations are possible according to some embodiments. Additionally, the arrangement and/or order of circuit elements or other features illustrated in the drawings and/or described herein need not be arranged in the particular way illustrated and described. Many other arrangements are possible according to some embodiments.
0025In each system shown in a figure, the elements in some cases may each have a same reference number or a different reference number to suggest that the elements represented could be different and/or similar. However, an element may be flexible enough to have different implementations and work with some or all of the systems shown or described herein. The various elements shown in the figures may be the same or different. Which one is referred to as a first element and which is called a second element is arbitrary.
0026In the description and claims, the terms “coupled” and “connected,” along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. Rather, in particular embodiments, “connected” may be used to indicate that two or more elements are in direct physical or electrical contact with each other. “Coupled” may mean that two or more elements are in direct physical or electrical contact. However, “coupled” may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.
0027An algorithm is here, and generally, considered to be a self-consistent sequence of acts or operations leading to a desired result. These include physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers or the like. It should be understood, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities.
0028Some embodiments may be implemented in one or a combination of hardware, firmware, and software. Some embodiments may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by a computing platform to perform the operations described herein. A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium may include read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, the interfaces that transmit and/or receive signals, etc.), and others.
0029An embodiment is an implementation or example of the inventions. Reference in the specification to “an embodiment,” “one embodiment,” “some embodiments,” or “other embodiments” means that a particular feature, structure, or characteristic described in connection with the embodiments is included in at least some embodiments, but not necessarily all embodiments, of the inventions. The various appearances “an embodiment,” “one embodiment,” or “some embodiments” are not necessarily all referring to the same embodiments.
0030Not all components, features, structures, characteristics, etc. described and illustrated herein need be included in a particular embodiment or embodiments. If the specification states a component, feature, structure, or characteristic “may”, “might”, “can” or “could” be included, for example, that particular component, feature, structure, or characteristic is not required to be included. If the specification or claim refers to “a” or “an” element, that does not mean there is only one of the element. If the specification or claims refer to “an additional” element, that does not preclude there being more than one of the additional element.
0031Although flow diagrams and/or state diagrams may have been used herein to describe embodiments, the inventions are not limited to those diagrams or to corresponding descriptions herein. For example, flow need not move through each illustrated box or state or in exactly the same order as illustrated and described herein.
0032The inventions are not restricted to the particular details listed herein. Indeed, those skilled in the art having the benefit of this disclosure will appreciate that many other variations from the foregoing description and drawings may be made within the scope of the present inventions. Accordingly, it is the following claims including any amendments thereto that define the scope of the inventions.
Contents5
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2002104030A1 | Cites | United States of America | Applicant |
| US2007205891A1 | Cites | United States of America | Search report |
| US5664118A | Cites | United States of America | Applicant |
| US5815652A | Cites | United States of America | Applicant |
| US6044476A | Cites | United States of America | Applicant |
| US6112246A | Cites | United States of America | Applicant |
| US6199180B1 | Cites | United States of America | Applicant |
| US6301514B1 | Cites | United States of America | Applicant |
| US6553336B1 | Cites | United States of America | Applicant |
| US6854064B2 | Cites | United States of America | Applicant |
| US7034814B2 | Cites | United States of America | Applicant |
| US7290172B2 | Cites | United States of America | Applicant |
| US7336168B2 | Cites | United States of America | Applicant |
| US8387078B2 | Cites | United States of America | Applicant |
| US9438465B2 | Cites | United States of America | Search report |
| US20020104030A1 | Cites | United States of America | Applicant |
| US20070205891A1 | Cites | United States of America | Search report |
6 members in 1 office
Priority claims10
| Document | Office | Kind | Date |
|---|---|---|---|
| 86314807 | United States of America | A | |
| 86314807 | United States of America | A | |
| 201313771816 | United States of America | A | |
| 201313771816 | United States of America | A | |
| 201615240640 | United States of America | A | |
| 11863148 | – | – | – |
| 13771816 | – | – | – |
| US20070863148 | – | – | – |
| US201313771816 | – | – | – |
| US201615240640 | – | – | – |
Members6
| Document | Office | Kind | |
|---|---|---|---|
| US2009089818A1 | United States of America | A1 | |
| US8387078B2 | United States of America | B2 | |
| US2013346544A1 | United States of America | A1 | |
| US9438465B2 | United States of America | B2 | |
| US2016359716A1 | United States of America | A1 | |
| US9876702B2This record | United States of America | B2 |
60 transactions on the USPTO file
Allowed after 1 non-final rejection and 1 final rejection.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Electronic request for Examiner InterviewM865E | M865E | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Terminal Disclaimer FiledDIST | DIST | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Email NotificationEML_NTR | EML_NTR | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Close TICLTI | CLTI | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Email NotificationEML_NTR | EML_NTR | |
| Application Is Now CompleteCOMP | COMP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Sent to Classification ContractorPGPC | PGPC | |
| FITF set to NO - revise initial settingFTFI | FTFI | |
| Cleared by OIPE CSRL194 | L194 | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| PTO/SB/69-Authorize EPO Access to Search ResultsSREXR141 | SREXR141 | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Entity Status Set To Undiscounted (Initial Default Setting or Status Change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
7 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF |
Numbers
- Publication
- 09876702
- Publication, DOCDB
- 9876702
- Publication, EPODOC
- US9876702
- Application
- 15240640
- Application, DOCDB
- 201615240640
- Application, EPODOC
- US201615240640
Titles
- English
- Determining the context of a computing device
Patent term adjustment
- Net adjustment
- 0 days
Classification
- CPC, 7
- H04L43/12
- G06F1/3209
- G06F1/266
- H04L9/40
- H04L12/12
- H04L29/06
- H04L67/12
- IPC, 6
- H04L12 26
- G06F1 32
- H04L29 06
- G06F1 26
- H04L12 12
- H04L29 08
- USPC, 2
- 340539290
- 001001000