A method for providing telephony features at an endpoint includes accessing a service framework at an endpoint. The service framework is operable to provide one or more telephony features. Feature logic associated with a first telephony feature is accessed. The feature logic specifies a plurality of actions for implementing the first telephony feature. The first telephony feature is registered to receive an intercept upon the occurrence of an event. The occurrence of the event for which the first telephony feature is registered is identified. The event initiates a transition from a first state to a second state. The feature logic associated with the first telephony feature is loaded to provide the first telephony feature.
Jiahe Zhuang - Allen TX, US Liang Wu - Frisco TX, US Henry Chen - Plano TX, US Michael H. McClung - Ruckersville VA, US Jeffery Sanders - Cocoa FL, US
Assignee:
Cisco Technology, Inc. - San Jose CA
International Classification:
H04L 12/28
US Classification:
379351, 37921102, 709238
Abstract:
In one embodiment, a method can include: when performing a park operation: (i) receiving a first message from a park call phone; (ii) providing a second message having a park code to the park call phone; and (iii) receiving a third message having call information from the park call phone; and when performing a retrieve operation: (iv) receiving a fourth message having the park code from a retrieve call phone; (v) providing a fifth message having the call information to the retrieve call phone; (vi) forwarding a sixth message having the park code from the retrieve call phone to a parked device; (vii) forwarding a seventh message from the parked device to the retrieve call phone; and (viii) receiving an eighth message having the park code from the retrieve call phone.
Distributed Service Creation Environment For Intelligent Endpoints
Henry Chen - Plano TX, US Michael H. McClung - Earlysville VA, US Jeffery A. Sanders - Cocoa FL, US
Assignee:
Cisco Technology, Inc. - San Jose CA
International Classification:
H04M 3/42
US Classification:
37920112, 37920102
Abstract:
According to one embodiment, a method for creating telephony features for an endpoint includes receiving a plurality of instructions defining a graphical representation of an implementation of one or more telephony features for an endpoint. The graphical representation includes a plurality of graphical elements representing a state process of the one or more telephony features. The graphical representation is generated in accordance with the plurality of instructions. A plurality of text commands corresponding to the graphical elements are determined. The text commands specify a plurality of actions of the state process. The graphical representation is converted into customized feature logic that includes the plurality of text commands. The text commands provide the one or more telephony features for the endpoint.
Jeffery Sanders - Cocoa FL, US Michael McClung - Vienna VA, US Henry Chen - Plano TX, US Andrew Francke - Morgan Hill CA, US
International Classification:
G06F 15/16
US Classification:
709227000
Abstract:
Providing a proxy server feature includes initiating the proxy server feature at an endpoint of a number of endpoints. Registration information comprising addresses for the endpoints is received and then stored in a routing table at the endpoint. The endpoint locates a callee endpoint using the routing table in order to establish a session with the callee endpoint.
Validating Sensor Data At A Community Sensor-Coordinating Entity
In one embodiment, a method includes receiving sensor data from a source associated with a person; comparing the sensor data against a sensor information model of the person that includes a description of the person, a description of a sensor associated with the person, a description of a property associated with the person, and a description of a virtual community that the person is associated with; determining whether the sensor data are valid based on the comparison; and if the sensor data are valid, routing the sensor data to an application provider associated with the virtual community.
Validating Sensor Data At A Property Sensor-Coordinating Entity
In one embodiment, a method includes receiving sensor data with preamble information from a sensor at a property associated with a person. The preamble information includes user-identification (ID) information identifying the person; sensor-type information identifying a sensor type of the sensor; sensor-ID information identifying the sensor; and sensor-characteristics information identifying one or more operating characteristics of the sensor. The method includes determining whether the sensor data is valid based at least in part on the preamble information; and, if the sensor data is valid, adapting the sensor data for communication to a community-based sensor coordination entity configured to associate the sensor data with a virtual community and route the sensor data to an application provider associated with the virtual community and communicating the sensor data as adapted to the community-based sensor coordination entity.
Aggregating And Routing Sensor Data At A Community Sensor-Coordinating Entity
In one embodiment, a method includes receiving sensor data from multiple sensors associated with multiple persons; for each of the sensors, identifying the person associated with the sensor; determining whether the sensor data are valid; and, for the sensor data that are valid, aggregating them based on the associations of their sensors with the persons and routing them to one or more sensor-application-service providers based on associations of the persons with the sensor-application-service providers.
In one embodiment, a method includes receiving at a sensor-application-service provider sensor data from sensors associated with persons. The method includes, based on a service information model at the sensor-application-service provider, determining whether the sensor data are valid and, for the sensor data that are valid applying to the sensor data one or more terms of one or more service agreements between the sensor-application-service provider and the persons associated with the sensor data, determining one or more amounts to bill or compensate the persons associated with the sensor data or others for processing of the sensor data at the sensor-application-service provider to provide a sensor-application service, and providing the sensor-application service to the persons associated with the sensor data or to others.