Cisco Technology, Inc.

Ncr Corporation

Ncr Atleos Corporation

Niraj Gopal

David Delano Ward

Sai V Ramamoorthy

Jiong Sun

Alexander William Whytock

Brian Steven Wotherspoon

Satyanarayana Dv Raju

Prasad Yerneni

A unique session is obtained and an anonymous session is generated that maps to the session. The anonymous session is passed to a selected advertisement service, and the selected advertisement service provides, in response thereto, an interface, which is proxied together with an existing interface of a device (associated with the unique session) during the unique session for a consumer to interact with the proxied interface on the device.

Channel integration

A Self-Service Terminal (SST) safe that includes a lock drive adapted and configured to i) operate inside the SST safe, ii) receive a wireless code sent from outside the SST safe, and iii) determine whether to lock or unlock the SST safe from inside the SST safe in response to the wireless code, and wherein the wireless code is cryptographically secured and authenticated prior to any unlock or lock operation.

Self-service terminal (SST) safe and methods of operating a lock for the SST safe

A method and apparatus for configuring an element management system server (an EMS server) to support new network element service application versions without upgrading the EMS server software is provided. The EMS stores base version data that describes the data model of a first version of a service application installed on a network element. When a second version of the service application is available, incremental version data describing changes to the data model from the first version to the second version is obtained and stored. In response to receiving a client request involving a service application on a particular network element, the EMS may apply incremental version data, associated with the version of the service application installed on the particular network element, to the base version data to form merged version data that describes the data model of the version of the service application installed on the particular network element.

Method for supporting new network element software versions in an element management system without upgrading

A method and apparatus for deploying EMS provisioning services is provided. A communication to administer a particular service on a network element is transmitted from an EMS client to an EMS server. The communication contains service data that describes a particular service to be administered on the network element. The EMS server constructs an instance of a generic record that stores the service data. The EMS server selects a service module to process the instance based on which service is associated with the service data stored in the instance. The instance is processed to produce result data that describes the result of processing the service data at the network element. The EMS server stores the result data in a persistent store. This generic framework enables communications between EMS clients and the EMS server involving different services to be processed similarly. New services are added without modification to the generic framework.

Deploying network element management system provisioning services

A method and apparatus for detecting data modifications in MIB tables utilizes a network device having a table registrar, a notification controller, a table modification recorder and a row modification recorder. A Network Management System (NMS) registers a table to be monitored with the table registrar and enables the notification controller when observation of change notifications is desired. With the assistance of a modification count and a timestamp from the table modification recorder, the NMS can determine whether a modified row should be retrieved from the row modification recorder to find data that has been modified since the last poll.

MIB detecting data modification in MIB tables in an SNMP command responder

A method and apparatus for checking the level of SNMP MIB support by network devices. An input text file indicating the MIB variables and their associated VALID/INVALID values is provided by the device designer. An input file is created for each NMS management application for which support is desired or required. The process includes identifying the variable, obtaining the value for the variable, and checking the value against any and all VALID/INVALID) values. If the value of any variable is found to not be valid or to be invalid, then an error message is generated. The process is repeated with each MIB variable in the input file provided by the device designer. After the input file is empty, one or more output files for each NMS management application for which support has been checked is generated.

Growing community of inventors

San Jose, CA, United States of America

Niraj Gopal