9612887

Firmware-Related Event Notification

PublishedApril 4, 2017
Assigneenot available in USPTO data we have
Technical Abstract

Patent Claims
20 claims

Legal claims defining the scope of protection, as filed with the USPTO.

1

1. A device to generate firmware-related event notifications, comprising: memory circuitry including at least a shared memory space; a firmware module to: load at least part of a messaging interface into the shared memory space; load at least one globally unique identifier into a platform notification table in the shared memory space; set at least one platform notification bit in a status field of the platform notification table; and cause the messaging interface to generate a notification to an operating system in the device; and processor circuitry to perform operations in the device based at least on instructions received from the operating system, the operating system including an operating system management module to at least react to the notification presented by the messaging interface.

2

2. The device of claim 1 , wherein during initialization of the device the firmware module is to at least one of load at least one globally unique identifier and corresponding service identifier entry into a firmware configuration table, or generate at least one firmware variable.

3

3. The device of claim 2 , wherein the firmware configuration table is based on the Unified Extensible Firmware Interface (UEFI) standard.

4

4. The device of claim 1 , wherein the firmware module is to load at least one globally unique identifier into the platform notification table prior to the generation of said notification.

5

5. The device of claim 4 , wherein the platform notification table is based on the Advanced Configuration and Power Interface (ACPI) standard.

6

6. The device of claim 4 , wherein the notification is a system control interrupt (SCI).

7

7. The device of claim 4 , wherein the platform notification table is protected by at least one of a physical base control register or a physical mask control register.

8

8. The device of claim 7 , wherein in response to determining that the platform notification bit is set in the platform notification table, the operating system management module is to cause the processor circuitry to determine if at least one globally unique identifier in the platform notification table is the same as any globally unique identifiers loaded in the firmware configuration table.

9

9. The device of claim 8 , wherein in response to determining that at least one globally unique identifier in the platform notification table is not the same as any globally unique identifiers loaded in the firmware configuration table, the operating system management module is to cause the processor circuitry to request a firmware variable from the firmware configuration table.

10

10. The device of claim 9 , wherein the operating system management module is to cause the processor circuitry to call at least one service in the operating system based on the service identifier corresponding to the globally unique identifier in the platform notification table that was determined to match a globally unique identifier in the firmware configuration table, or if no matching globally unique identifiers were determined, a returned firmware variable.

11

11. The device of claim 1 , wherein the operating system management module is to cause the processor circuitry to discover a source of the notification by querying at least the platform notification table.

12

12. The device of claim 1 , wherein the notification is generated based on a peripheral topology change detected in the device.

13

13. A method for generating firmware-related notifications, comprising: configuring a firmware configuration table in a device; determining that a notification from a platform in the device needs to be generated for an operating system in the device; configuring a platform notification table in the device; and generating the notification; wherein configuring the platform notification table in the device comprises: loading at least one globally unique identifier in the platform notification table; and setting at least one platform notification bit in a status field.

14

14. The method of claim 13 , wherein configuring the firmware configuration table comprises at least one of loading at least one globally unique identifier and corresponding service identifier entry into a firmware configuration table, or generating at least one firmware variable.

15

15. The method of claim 13 , further comprising: determining that a notification is required based on detecting a peripheral topology change in the device.

16

16. The method of claim 13 , further comprising: protecting at least the platform notification table with at least one of a physical base control register or a physical mask control register.

17

17. At least one non-transitory computer readable storage medium having stored thereon, individually or in combination, instructions for generating firmware-related notifications that, when executed by one or more processors, cause the one or more processors to: configure a firmware configuration table in a device; determine that a notification from a platform in the device needs to be generated for an operating system in the device; configure a platform notification table in the device; and generate the notification; wherein the instruction to configure the platform notification table in the device comprise instructions to cause the one or more processors to: load at least one globally unique identifier into the platform notification table; and set at least one platform notification bit in a status field of the platform notification table.

18

18. The at least one non-transitory computer readable storage medium of claim 17 , wherein the instructions to configure the firmware configuration table comprise instructions to at least one of load at least one globally unique identifier entry into a firmware configuration table or generate at least one firmware variable.

19

19. The at least one non-transitory computer readable storage medium of claim 17 , further comprising instructions that, when executed by one or more processors, cause the one or more processors to: determine that a notification is required based on detecting a peripheral topology change in the device.

20

20. The at least one non-transitory computer readable storage medium of claim 17 , further comprising instructions that, when executed by one or more processors, cause the one or more processors to: protect at least the platform notification table with at least one of a physical base control register or a physical mask control register.

Patent Metadata

Filing Date

Unknown

Publication Date

April 4, 2017

Inventors

SARATHY JAYAKUMAR
MOHAN J. KUMAR
VINCENT J. ZIMMER
RAJESH POORNACHANDRAN

Want to explore more patents?

Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.

Citation & reuse

Analysis on this page is generated by Patentable — an AI-powered patent intelligence platform. AI-generated summaries, explanations, and analysis may be reused with attribution and a visible link back to the canonical URL below. Patent abstracts and claims are USPTO public domain.

Cite as: Patentable. “FIRMWARE-RELATED EVENT NOTIFICATION” (9612887). https://patentable.app/patents/9612887

© 2026 Patentable. All rights reserved.

Patentable is a research and drafting-assistant tool, not a law firm, and does not provide legal advice. Documents we generate are drafts for review by a licensed patent attorney.