System and method for managing information handling system service communication
Claim Score by NHIP
Abstract
A technical support button accepts user activation to request a technical support session for an information handling system. For instance, activation of technical support sends an electronic message, such as an e-mail or instant message, to a technical support site that includes technical support information for establishing a technical support session, such as identification and diagnostics information. The technical support session is established through the information handling system to aid a technical support agent in investigating the system directly while communicating with the user of the system. For instance, VoIP communication is established through a management subsystem that operates on auxiliary power so that a technical support session is supported even if the information handling system is powered down or inoperative.

Term
Term ended
Projected expiry passed 23 May 2025, 1.3 years ago.
- Priority and filed
- Published
- Projected expiry
- Today
20 claims: 4 independent, 16 dependent
- 1An information handling system comprising:a housing;plural processing components disposed in the housing and operable to process information;a technical support button disposed at the housing and operable to accept a physical user input that requests technical support;and a technical support request module running on one or more of the processing components and interfaced with the technical support button, the support request module operable to communicate over a network with a technical support site to request a technical support session upon activation of the technical support button.
- 9An information handling system server comprising:plural processing components operable to process information and communicate information with a network;a management subsystem operable to run independent of the processing component, the management subsystem having a service processor, an audio card and a network interface card;a microphone interfaced with the audio card and operable to receive audio sounds;a speaker interfaced with the audio card and operable to play audio sounds;and a VoIP module running on the management subsystem and operable to support VoIP communication with the microphone and speaker through the network interface card.
- 16A method for providing technical support to an information handling system, the method comprising:pressing a support button at the information handling system to request technical support;automatically initiating a request for technical support in response to the pressing of the support button;and automatically establishing network communication with a technical support site with the information handling system to obtain technical support.
- 20Broadest claimClaim Score 97, very broad(NHIP)The method of 16 further comprising:storing technical support communication at the information handling system;and retrieving the technical support communication at the information handling system.
Independent claims4
21 paragraphs in 4 sections, as filed
BACKGROUND OF THE INVENTION
00011. Field of the Invention
0002The present invention relates in general to the field of information handling systems, and more particularly to a system and method for managing information handling system service communication.
00032. Description of the Related Art
0004As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
0005Information handling systems generally operate with good reliability, however, for information handling systems that perform some critical functions, such as communication, additional components are often added to enhance operating reliability. For instance, server information handling systems sometimes include a management subsystem to monitor and adjust system operations. One example of a management subsystem is a remote access card (RAC) that is integrated within a server information handling system. A typical RAC is essentially a miniature information handling system on a card complete with a relatively powerful processor, such as a 333 MHz 8086 processor, and with integrated peripherals, such as Ethernet, USB, AC'97 audio, and extensive local FLASH and RAM. Generally, the RAC operates on auxiliary power and may thus operate normally even if its associated information handling system is powered down or otherwise not operating. An independent RAC provides remote access to perform functions at the information handling system including system resets and reboots initiated through network commands or other functions that diagnose and manage the server information handling system. The network commands are sent through an out-of-band network interface card to support independent RAC operation using a variety of communication protocols, such as virtual KVM over IP, virtual media and IPMI.
0006An advantage of having a RAC loaded on a server information handling system is that information technology professionals can perform management functions on the server from a location distal to the server. Similarly, the manufacturer of the server information handling system obtains direct access to the system for providing analysis of system performance or other technical assistance. Although a RAC will allow multiple different sources to simultaneously access system management functions, if the different sources need to communicate directly with each other they generally must establish a separate telephone conversation. For instance, if an information technology professional needs technical assistance from the manufacturer, the information technology professional typically calls the manufacture technical help center and, once a conversation between the two has established the identity of the system in question, the technical help center contacts the RAC for management information as needed. The establishment of separate telephone and network communications introduces delay in the technical service process and adds to frustration already generally present with the end user who is dealing with a misbehaving system.
SUMMARY OF THE INVENTION
0007Therefore a need has arisen for a system and method which provides audio communication supported through an information handling system management subsystem independent of operation of the information handling system.
0008In accordance with the present invention, a system and method are provided which substantially reduce the disadvantages and problems associated with previous methods and systems for information handling system management subsystem supported communication. Communication between plural users is supported through the management subsystem, such as to provide technical support to a user of the information handling system from a technical support network location. Automated initiation of communication through the management subsystem, such as a technical support session, is provided by the pressing of a physical support button located at the housing of the information handling system.
0009More specifically, a technical support subsystem runs on a management subsystem of a server information handling system to provide technical support independent of the operation of the server information handling system. Pressing a support button prompts a support request module to send a message, such as an e-mail or instant message, to request a technical support session. A technical support module establishes the technical support session and couples the session with server management functions of a server management module for integrated system and user technical support. For instance, a Voice over Internet Protocol (VoIP) module establishes voice communication between the end user and a technical support agent while the technical support agent has access to server management functions over the same network communication. Thus, for instance, rather than telling the user to reboot the information handling system, the agent can initiate a reboot and explain to the end user what is happening. A conference module <b>66</b> supports communication between multiple network locations so that the management subsystem provides a training tool for distributed users. A session storage module stores technical support sessions for later reference or to record predetermined events, such as an unauthorized access or a system failure.
0010The present invention provides a number of important technical advantages. One example of an important technical advantage is that multiple users are able to communicate directly with each other through a management subsystem, such as a RAC. Audio communication between users through a management subsystem simplifies servicing of the information handling system with the end-user and technical support having substantially equal and simultaneous access to the management information and control functions. Conventional telephone conversations to coordinate technical assistance are avoided with VoIP communication conveniently associating the information handling system with the request for assistance. On system single button activation of a request for technical assistance provides rapid and direct response for an improved customer experience and reduced time spent by a technical assistant in identifying the end user and the problem. Further, end users are encouraged to initiate technical support sessions with button activation thus increasing the likelihood of a resolution of the end users difficulty with support communication media that are less expensive than telephone support.
BRIEF DESCRIPTION OF THE DRAWINGS
0011The present invention may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference number throughout the several figures designates a like or similar element.
0012<figref idref="DRAWINGS">FIG. 1</figref> depicts a block diagram of a server information handling system having a VoIP enabled independently operable management subsystem with a technical support request button;
0013<figref idref="DRAWINGS">FIG. 2</figref> depicts a block diagram of a system for providing technical support with a technical request support button; and
0014<figref idref="DRAWINGS">FIG. 3</figref> depicts an example of a graphical user interface for initiating a technical support request.
DETAILED DESCRIPTION
0015Technical support coordinated through an information handling system provides multiple media for rapidly and accurately addressing difficulties with the information handling system. For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components.
0016Referring now to <figref idref="DRAWINGS">FIG. 1</figref>, a block diagram depicts a server information handling system having a VoIP enabled independently operable management subsystem with a technical support request button. Server information handling system <b>10</b> has plural processing components disposed in a housing <b>12</b> including a CPU <b>14</b>, RAM <b>16</b>, a hard disk drive (HDD) <b>18</b>, a chipset <b>20</b> and plural network interface cards (NIC) <b>22</b>. Server information handling system <b>10</b> coordinates communication over a network <b>24</b> between client information handling systems <b>26</b> and other server information handling systems <b>10</b>, such as in a local area network (LAN) configuration. A cooling fan <b>28</b> removes excess heat produced by the processing components and a power supply <b>30</b> maintains DC power to the processing components. For improved reliability and remote access, a management subsystem <b>32</b> configured as a remote access card is integrated with server information handling system <b>10</b>. Management subsystem <b>32</b> includes a service processor, such as a 333 MHz INTEL 8086 compatible processor, RAM, FLASH memory, an audiovisual card <b>40</b>, such as an AC'97 compatible card, and a NIC <b>42</b> to interface with network <b>24</b>. Management subsystem <b>32</b> operates on an auxiliary power supply <b>44</b> to run independently of the rest of information handling system <b>10</b>. Independent operation of management subsystem <b>32</b> allows it to reset, power down and power up information handling system <b>10</b>. Management subsystem <b>32</b> manages the operations of information handling system <b>10</b> so that a remote user interfaced through network <b>24</b> can exercise full control over system operations.
0017Management subsystem <b>32</b> aids in the coordination of technical support for server information handling system <b>10</b> with a technical support button <b>46</b> and a variety of peripherals, such as an audio microphone <b>48</b>, an audio speaker <b>50</b>, a display <b>52</b> and a cameral <b>54</b>. A user located at server information handling system initiates a request for technical support by pressing button <b>46</b> and management subsystem <b>32</b> establishes a technical support session through network <b>24</b> with a technical support site <b>56</b>, such as the technical support of the manufacturer of server information handling system <b>10</b>. Audiovisual card <b>40</b> supported by an appropriate driver, such as an AC'97 LINUX driver, allows the end user to interact with a technical support agent using VoIP, much like a conventional telephone. However, coordinating voice communications for technical support through management subsystem <b>32</b> allows direct interaction of the technical support agent with server information handling system <b>10</b> during the support session, such as to see the display of system <b>10</b>, virtual storage and control I/O devices. Direct interaction reduces the amount verbal communication needed to identify the system and the technical issues involved, and thus reduces the time involved in coordinating the technical support and the risk of inadvertent errors caused by human communication of identification information and technical codes. Further, the relatively simple and robust management subsystem <b>32</b> remains operational on auxiliary power even if server information handling system <b>10</b> is inoperative due to a virus infection, an operating system crash, an application failure, or a hardware failure.
0018Referring now to <figref idref="DRAWINGS">FIG. 2</figref>, a block diagram depicts a system for providing technical support with a technical request support button. The functional modules depicted in <figref idref="DRAWINGS">FIG. 2</figref> run on service processor <b>34</b> which manages coordination of management subsystem <b>32</b> hardware components under, for instance, a LINUX operating system kernel, such as to open and maintain network socket connections. Upon pressing of support button <b>46</b>, a technical support request module <b>58</b> initiates a technical support session with a technical support site <b>56</b> through network <b>24</b>. For instance, technical support request module sends an electronic message, such as an e-mail or an instant message, which includes information for technical support site <b>56</b> to apply in order to efficiently assign the request to an appropriate technical support agent. For instance, technical support request module <b>58</b> includes a unique identifier with the message to identify the type of information handling system, the level of service and any automated error tracking information that is available for review by the agent. Technical support site <b>56</b> replies to the message with session information to establish a technical support session, such as an IP address to establish VoIP communication. A technical support module <b>60</b> establishes the technical support session with the session information and coordinates retrieval of management information related to the operations of server information handling system <b>10</b> from a server management module <b>62</b>. For instance, technical support module <b>60</b> coordinates communication of diagnostics information tracked by server management module <b>62</b> to technical support site <b>56</b> in addition to the VoIP communication. Coordination of management information and voice communication through a common network communication allows technical support site <b>56</b> to more quickly and accurately gather information for use by an agent to provide technical support.
0019A VoIP module <b>64</b> establishes and maintains VoIP communication for the technical support session and a conference module <b>66</b> coordinates communication between plural locations. Depending upon the processing components of management subsystem <b>32</b> and the available bandwidth, technical support sessions may include between 4 and 16 different locations simultaneously. Thus, for instance, a technical support session provides a tool for corporate training for the use of server information handling system <b>10</b> with dispersed participants, whether or not a manufacturer technical support site is involved. A session storage module <b>68</b> provides storage for a support session, such as storage in MP3 format, so that an end user may subsequently refer to information or solutions provided by the support session. Similarly, session recording may be initiated at the occurrence of a predetermined event, such as an operating system failure or an unauthorized access to the system. One advantage of a voice technical support session is that remote participants to the session can hear system operations, such as beeps or whining fans, along with viewing system video. In one embodiment, a voice recognition module <b>70</b> operates during a support session to accept user voice commands for managing server operations, such as reboot, shutdown, virtual drive online, and boot to BIOS setup. Audio and visual interactions with end users are managed by a support user interface <b>72</b>. For instance, in addition to presenting information at a display, audible system management information may be provided, such as a generated voice to indicate time until support is available or that an access is not authorized. In one embodiment, “headless” servers are managed by voice information provided through external audio jacks so that a display device is not needed.
0020Referring now to <figref idref="DRAWINGS">FIG. 3</figref>, an example is depicted of a graphical user interface <b>74</b> for initiating a technical support request. User interface <b>74</b> is automatically generated at the pressing of the support button at the housing of server information handling system <b>10</b>. A dialog box <b>76</b> allows a user to describe the type of technical support sought and provides the description with system management information automatically generated for the technical support site, such as a unique identifier for the system and any diagnostics indicative of a particular system failure. The presentation of the dialog box before a request is sent helps avoid inadvertent activations. The technical support information is sent as an e-mail or instant message, and a reply message from the technical support site populates the wait time expected before a technical support agent becomes available. Advantageously, a technical support agent may be able to determine a solution for the difficulty without even establishing a voice link, thus reducing the time and cost involved in providing the technical support. For this and other reasons, a technical support button provided on an information handling system is helpful even where the information handling system does not have a management subsystem that runs independently. Add-on technical support subsystems may be included by inserting an appropriately configured card into an existing system PCI slot or similar interface.
0021Although the present invention has been described in detail, it should be understood that various changes, substitutions and alterations can be made hereto without departing from the spirit and scope of the invention as defined by the appended claims.
Contents4
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| CN109752989A | Cited by | China | Search report |
| US2019141134A1 | Cited by | United States of America | Search report |
| US2009204667A1 | Cited by | United States of America | Pre-grant |
| US2012140763A1 | Cited by | United States of America | Pre-grant |
| US10601924B2 | Cited by | United States of America | Search report |
| US8826289B2 | Cited by | United States of America | Search report |
| US8468451B1 | Cited by | United States of America | Search report |
| US8171485B2 | Cited by | United States of America | Search report |
| US7716099B1 | Cited by | United States of America | Search report |
| US9680939B2 | Cited by | United States of America | Search report |
| US8995670B2 | Cited by | United States of America | Applicant |
| US9146855B2 | Cited by | United States of America | Applicant |
| US8650471B2 | Cited by | United States of America | Applicant |
| FR2909787A1 | Cited by | France | Search report |
| US2006282530A1 | Cited by | United States of America | Pre-grant |
| US2015180985A1 | Cited by | United States of America | Pre-grant |
| US9652267B2 | Cited by | United States of America | Applicant |
| US8549401B1 | Cited by | United States of America | Search report |
| US8904105B2 | Cited by | United States of America | Applicant |
| US2012240114A1 | Cited by | United States of America | Pre-grant |
| US2008301674A1 | Cited by | United States of America | Pre-grant |
| US9304819B2 | Cited by | United States of America | Search report |
| US9621697B2 | Cited by | United States of America | Search report |
| US9811305B2 | Cited by | United States of America | Applicant |
| US2008244579A1 | Cited by | United States of America | Pre-grant |
| US7668912B2 | Cited by | United States of America | Search report |
| US2006200550A1 | Cited by | United States of America | Pre-grant |
| US2001040892A1 | Cites | United States of America | Pre-grant |
| US2002064259A1 | Cites | United States of America | Pre-grant |
| US2002069112A1 | Cites | United States of America | Pre-grant |
| US2003048288A1 | Cites | United States of America | Pre-grant |
| US2004015559A1 | Cites | United States of America | Pre-grant |
| US2004044585A1 | Cites | United States of America | Pre-grant |
| US2004128496A1 | Cites | United States of America | Pre-grant |
| US2004139156A1 | Cites | United States of America | Pre-grant |
| US2006200550A1 | Cites | United States of America | Pre-grant |
| US6760324B1 | Cites | United States of America | Pre-grant |
| US6801613B1 | Cites | United States of America | Pre-grant |
| US6829348B1 | Cites | United States of America | Pre-grant |
2 priority claims, no other members on record
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 13496605 | United States of America | A | |
| US20050134966 | – | – | – |
75 transactions on the USPTO file
Abandoned after 3 non-final rejections, 1 final rejection and 3 appeals.
- Non-final rejections
- 3
- Final rejections
- 1
- RCEs
- 0
- Appeals
- 3
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Email NotificationEML_NTR | EML_NTR | |
| Mailing of Abandonment after Board of AppealsAbandonedMABN10 | MABN10 | |
| Abandonment after Board of AppealsAbandonedABN10 | ABN10 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail BPAI Decision on Appeal - AffirmedMAPDA | MAPDA | |
| BPAI Decision - Examiner AffirmedAPDA | APDA | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| Docketing Notice Mailed to AppellantAP_DK_M | AP_DK_M | |
| Assignment of Appeal NumberAPAS | APAS | |
| Appeal Awaiting BPAI DocketingAPWD | APWD | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Reply Brief Noted by ExaminerMRBNE | MRBNE | |
| Reply Brief Noted by ExaminerRBNE | RBNE | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Reply Brief FiledAPRB | APRB | |
| Exam. Ans. Review CompletePACC | PACC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| 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 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Appeal Brief Review CompleteAPBR | APBR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Appeal Brief FiledAP.B | AP.B | |
| Notice of Appeal FiledN/AP | N/AP | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Appeal Brief Review CompleteAPBR | APBR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Appeal Brief FiledAP.B | AP.B | |
| Notice of Appeal FiledN/AP | N/AP | |
| Email NotificationEML_NTR | EML_NTR | |
| 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 | |
| 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... | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
2 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 |
Numbers
- Publication
- 20060265656
- Publication, DOCDB
- 2006265656
- Publication, EPODOC
- US2006265656
- Application
- 11134966
- Application, DOCDB
- 13496605
- Application, EPODOC
- US20050134966
Titles
- English
- System and method for managing information handling system service communication
Classification
- CPC, 1
- G06Q10/00
- IPC, 1
- G06F17 00
- USPC, 1
- 715705000