Wrapping all Intel AMT software together - AMT SW, part 11

By Shmuel Gershon (Intel) (26 posts) on April 2, 2010 at 3:25 am

Hello again!
We went over a lot of details during the past 10 posts that explained each and every part of the Intel AMT software (full list at the bottom). We've learnt what is each software, how it works and how it's configured.
Now that we know so much about the different apps, what's left?
Well, "putting it all together": better understanding the relationship between applications. This will help when writing and troubleshooting applications that interact with Intel AMT software.

Let's save words by using a simple diagram:

How to read it: Any software that sits on top of other(s) in this diagram depends on the software at the bottom for proper functionality

Any software that sits on top of other(s) in this diagram depends on the software at the bottom for proper functionality.

We can see that each and every software from the Intel AMT kit depends on the Intel MEI (formerly HECI) driver; as we explained in this post, this driver is the one who directly talks with the Intel AMT hardware embedded software.

Let's deep dive into the parts of the AMT software marked with the numbered circles:

  1. Two major applications communicate with the Intel MEI:
    1. the LMS (used for local http traffic).
    2. And either:
      1. In older platforms (until generation 3.x), the Privacy Icon service atchksrv too.
        1. The atchksrv gets the information that the Privacy Icon (AMT pop-up) needs in order to show the Intel AMT status.
      2. From generation 4.x and up, the UNS (used for local user notification).
        1. UNS connects directly with Intel MEI in order to provide status updates for the Intel Management and Security Status application. It is similar to what the atchksrv did for previous versions, but it gets more info -- without the need of a dedicated service.
  2. The LMS provides http access through the interface protocols (SOAP/EOI, WsManagement). Most of the software written for Intel AMT by ISVs will use this traffic interface, so it is recommended to keep the LMS installed and operational.
  3. The part of the UNS that is in charge of notifying the user's log about manageability actions uses the LMS as network.

This explanation is a very good complement to the detailed posts about the Intel AMT applications of intel AMT versions 2.x to 5.x. Reading the rest of the blog posts will fill any part that is harder to understand -- and we'll answer any question in the comments, too :).

Articles in the Intel® AMT software series:

  1. The software bundled with Intel AMT
  2. The notification area icon - understanding the pop-up
  3. Configuring the notification area icon & app
  4. More configurations (disabling) of the Intel AMT icon
  5. Detailed information to the user with the User Notification Service
  6. How the UNS works
  7. UNS Error Messages and how to fix them
  8. Newfangled Intel Management and Security Status
  9. Intel Management and Security Status (IMSS), advanced configurations
  10. Intel AMT software: LMS, HECI, MEI... why do I need those?
  11. Wrapping all Intel AMT software together
Categories: Manageability & Security
Tags: , , , , , , , , , , ,

For more complete information about compiler optimizations, see our Optimization Notice.

Comments (4)

April 2, 2010 10:14 AM PDT

Andrew Schiestl (Intel)
Andrew Schiestl (Intel)Total Points:
6,558
Green Belt
 Great diagram Shmuel, that's the best summary of the local system software stack I've seen.
April 6, 2010 10:53 AM PDT

javierandrescaceres
javierandrescaceresTotal Points:
6,735
Black Belt
 Very useful =)
April 7, 2010 3:02 PM PDT

Kathy Farrel (Intel)
Kathy Farrel (Intel)Total Points:
9,186
Community Manager
 Another great blog Shmuel!
August 4, 2010 10:54 AM PDT

Shmuel Gershon (Intel)
Shmuel Gershon (Intel)Total Points:
2,750
Green Belt
 Thanks Andrew, Javier and Kathy!
Please let know of other questions, I'll be glad to find answers for them :)

Trackbacks (14)


Leave a comment  

To obtain technical support, please go to Software Support.
Name (required)*

Email (required; will not be displayed on this page)*

Your URL (optional)


Comment*