This invention relates generally to the telephony endpoint field, and more specifically to a new and useful system and method for managing telephony endpoint inventory in the telephony endpoint field.
In recent years, telephony communication platforms and IP based phone services, applications, and platforms have partly caused more volatility in the demand of phone numbers and short codes used as telephony endpoints. Similarly, more of the world is becoming connected and moving from shared home phones to individual mobile phones and sometimes multiple numbers managed through various phone applications. Phone numbers have become more disposable, and the demand of phone numbers has increased while the demand fluctuations have more real-time urgency. While previously a user would often hold onto a phone number for a long time, now a phone number may only have a customer lifetime of a month, day, an hour or even a single use. Further complicating phone number management is that there is no central registrar of phone numbers, and various carriers and entities hold and distribute phone numbers. The transfer of such numbers from carriers can at times be slow and unable to keep up with real-time demand requirements. Thus, there is a need in the field to create a new and useful system and method for managing telephony endpoint inventory. This invention provides such a new and useful system and method.
The following description of preferred embodiments of the invention is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.
1. System for Managing Telephony Endpoint Inventory
As shown in
The system is preferably incorporated into a communication platform that provides capabilities of purchasing, renting, or being assigned a telephony endpoint for customer use. For example, the communication platform is preferably a multi-tenant communication application platform where users can set up various applications for facilitating communications to assigned phone numbers. The communication platform is preferably substantially similar to the one described in U.S. Pat. No. 8,306,021, issued 6 Nov. 2012, which is hereby incorporated herein in its entirety by this reference. The communication platform can alternatively have any suitable architecture or functionality. In one variation, the system may be a stand-alone telephony endpoint registrar/service used by multiple outside entities. The system is preferably integrated into the operation of the communication platform such that telephony endpoint inventory can be updated according to endpoint availability and telephony endpoint usage. Requests for a new phone number can have varying forms of desired address patterns and endpoint capabilities. For example, the area code, last four digits, country code, and capabilities are all dimensions, which may be important to various users. The system can automatically track and monitor telephony endpoint inventory across several dimensions so that a pool of desirable telephony endpoints is ready for delivery to a customer.
The telephony endpoint management service 110 functions to provide a service interface for interacting with telephony endpoints. The telephony endpoint management service 110 is preferably an intermediary component between the endpoint repository and components of a communication platform. The telephony endpoint management service 110 preferably includes an application programming interface (API) that can be used by other components for interacting with records of telephony endpoints. The API acts as an intermediary abstraction layer between stored numbers and various services of the communication platform. By implementing the telephony endpoint management service 110 in front of the endpoint repository, the components of the communication platform are independent of the inner functionality of the endpoints. Any request to inspect, request, create, port, delete, and/or interact with an endpoint preferably passes through the telephony endpoint management service 110. This visibility into interactions with the telephony endpoints is preferably exploited to enable the inventory monitor sub-system 130 to track and respond to inventory demand.
The API is preferably a RESTful API but may alternatively be any suitable API such as SOAP. The API can work according to an HTTP request and response model. HTTP requests (or any suitable application layer communication) to the telephony endpoint management service 110 preferably observes the principles of a RESTful design. RESTful is understood in this document to describe a Representational State Transfer architecture as is known in the art. The RESTful HTTP requests are preferably stateless, thus each message communicated from the call router to the application server preferably contains all necessary information for operation of the application server and response generation of the application server. The components of the communication platform and/or the telephony endpoint management service 110 preferably do not need to remember or store previous communications to be aware of the state. The API may be an internal API used by services within the communication platform of the system, but the API may alternatively be at least partially public, wherein external entities can access portions of the API.
The API may include API calls to inspect properties of a telephony endpoint. The API may include API calls to request a telephony endpoint to be used as a customer's terminating endpoint. For example, an API request may initiate a purchase or acquisition of an endpoint for use by an account. Preferably, the communication platform is a multitenant platform that uses an account system to segment functionality. An account can have a number of assigned telephony endpoints. A request can be made to add a new phone number to an account. In some variations, the request may include desired properties of the telephony endpoint. The desired telephony endpoint may be specified by area code, country code, functionality (e.g., SMS capable), type (e.g., toll free, short code, etc.), address patterns (e.g., vanity properties like ending in all zeros), cost, quality (e.g., high voice or messaging quality), and/or any suitable property of a telephony endpoint. Similarly, the API may include API calls to remove an endpoint. An API request is preferably submitted to disassociate an endpoint from an account or customer. Removing an endpoint may return the endpoint to a pool of available endpoints or alternatively a pool of endpoints to test before making it available. Other actions can include porting of an endpoint either into the system (e.g., for an existing user phone number) or out of the system (e.g., transfer management of the endpoint to another system/carrier). In one variation, a record of a telephony endpoint may include application-mapping information that is used during use of the telephony endpoint. Thus, during normal use of the telephony endpoint by an account, the API may be used to access application information such as a URI for a telephony application or application instructions. Accordingly, the telephony endpoint management service 110 can have visibility into usage of the endpoints, which may be used by the inventory monitor sub-system 130. In another variation, the API can include feedback calls to report quality issues, either good performance or bad performance. The inventory monitor sub-system 130 can be notified of any of the above inventory related actions.
As shown in
The telephony endpoint repository 120 functions to store endpoint data. A telephony endpoint preferably has a record stored in a database or distributed through several database tables or other suitable data models. An endpoint record may include various properties of an endpoint such as a unique identifier of the telephony endpoint, the direct inbound address (e.g., the phone number of short code), origin properties, geolocation information, a cleanliness/quality score, capability properties (e.g., SMS, MMS, Fax, etc.), status (e.g., mobile, landline, client application, tool free, business, etc.), and/or other suitable properties of a telephony endpoint. Origin properties can includes NPs (e.g., area code), NXX (e.g., three digit vanity digits of a number), ISO country codes, region properties and/or any suitable origin properties. Endpoints may additionally have different allocation statuses. An endpoint may be allocated, available, or in an evaluation status. An allocated endpoint is preferably an endpoint in use by some entity. An allocated endpoint is associated or otherwise mapped to an entity. The entity is preferably an account in the system, but may alternatively be a device or an external routing destination. An available endpoint is an endpoint that is available for allocation. The available endpoints are preferably not in active use, and may be acquired by a user. An endpoint in an evaluation stage may be undergoing a period of testing to ensure quality standards. An evaluation stage may additionally include a rejected state where the endpoint is deemed unusable. Such endpoints are preferably returned or removed from the system during endpoint transactions with an endpoint source.
Additionally, the telephony endpoint repository 120 may accumulate and track information for endpoints managed outside of the communication platform. Communications made through the communication platform may often include one endpoint managed by the system and an external endpoint. An informational database of external endpoints can be built through use of the system and/or through access to external data sources. The external endpoint information may be used when acquiring and evaluating newly obtained endpoints.
The inventory monitor 130 functions to track, analyze, and manage inventory requirements across multiple categories. The inventory monitor 130 is preferably communicatively coupled to the telephony endpoint management service no. The inventory monitor 130 preferably receives updates on changes made to the inventory repository 120 and/or usage of the various telephony endpoints in the system. The inventory monitor 130 includes a tracking component 132 that facilitates tracking the inventory across various dimensions such as country code, area code, capabilities, vanity features, and other suitable characteristics. In response to the monitored status of the inventory, the inventory monitor 130 can initiate communication with telephony endpoint providers. The inventory monitor 130 can be responsive to changes in quality of one or more endpoints in the repository and to changes in availability or quantity of endpoints aligned to particular endpoint categories. The inventory monitor 130 preferably includes an endpoint order system 134
The tracking component 132 of the inventory monitor 130 preferably updates inventory status according to new endpoint allocation, removal of endpoints, and the use of telephony endpoints. The tracking component 132 preferably works with a number keeping unit to sub-divide, segment, and/or categorize telephony endpoints into classification groups. The number keeping unit preferably maps a telephony endpoint to an endpoint identity. For example, a telephony endpoint identity may just be the area code of a telephone number. More preferably, the number keeping unit maps a telephony endpoint to multiple classifications. The different classifications of telephony numbers preferably overlap—a telephony endpoint can be a member of two groups. The tracking component preferably stores, queries, or calculates inventory analytics for individual classifications. In this way, the inventory along different dimensions can be tracked and maintained. For example, the number of mobile phone numbers, the phone numbers for a particular area code, and the number of mobile phone numbers for the particular area code may all be dimensions in which inventory is tracked and monitored.
The endpoint order system 134 functions to interface and facilitate the transfer of endpoints with at least one endpoint provider. Telephony carriers/network providers often hold a large number of telephony endpoints. They are preferably used as the source of ordered telephony endpoints, but the outside source of the telephony endpoints can be any suitable party. The endpoint order system 134 may directly interface with endpoint providers to submit orders. Alternatively orders or order specifications may be generated and provided to any suitable party.
The system can additionally include a testing component 140, which functions to process telephony endpoints. The testing component 140 can perform initial testing on obtained telephony endpoints prior to fully incorporating the telephony endpoint into the system for use. The testing component 140 may additionally or alternatively be used in periodic evaluation of endpoints already integrated in the system. For example, endpoints that are deallocated for a particular account may be tested before offering to other customers. When a telephony endpoint is moved or ported to the system, the properties of the telephony endpoint may not be known. Often, a provider will deliver telephony endpoints in bulk (e.g., a block of 1000 numbers), wherein several hundred telephony endpoints are transferred to the system. When more telephony endpoint inventory is required, it is often for a target classification of telephony endpoints. As one stage of the testing component, the classification of the obtained telephony endpoints is verified to comply with the desired classification. If an obtained telephony endpoint is not of a desired classification, then the particular telephony endpoint may be returned or exchanged with the provider (e.g., through the endpoint order system 134). As another stage of the testing component 140, the functionality of obtained telephony endpoints can be verified. Testing scripts and testing devices can be coordinated to run various test scenarios on a telephony endpoint. Tested capabilities can include capability of receiving calls, making calls, receiving messages, routing to client applications, and/or performing other suitable tasks. Communication testing may additionally be performed between different geographic regions and/or between different types of devices (e.g., PSTN to SIP device). If an obtained telephony endpoint fails to pass a test, the telephony endpoint may be returned to the provider (depending on the desired capabilities of the telephony endpoint). The functionality testing may measure success and failure of particular capabilities and/or quality measurements. As another stage of the testing component 140, a cleanliness score of a telephony endpoint can be evaluated. The cleanliness score is a measure of undesired communications that are received at the number. An undesired communication can be a call or message that results from a caller entering the wrong phone number, a call or message that was intended to reach a previous owner of the telephony endpoint, unsolicited calls or messages (e.g., telemarketers), spam text messages, or any suitable undesired communication. The cleanliness stage preferably places the telephony endpoints in temporary quarantine state where incoming communication is monitored for a set duration of time. If no incoming calls or messages are transmitted to the telephony endpoint, then the number is considered clean and can be confidently used and distributed to users of the system.
The system may additionally include any suitable subsystem to supplement the endpoint inventory information such as an endpoint information database, a geo data system (which may provide mapping between geographic regions and endpoints), a country regulation manager (which may provide information on regional regulations relating to the endpoints), and/or any endpoint monitoring or information suitable sub-system.
2. Method for Managing Telephony Endpoint Inventory
As shown in
Telephony endpoints are preferably phone numbers, short-codes, toll-free numbers, and/or other suitable telephony communication addresses. In one variation, the telephony endpoints can be SIP addresses, and/or proprietary endpoints. The method is preferably implemented within a communication platform, carrier, or other infrastructure that holds, supplies, and/or works with a large number of telephony endpoints. Distributing telephony endpoints preferably includes allocating telephony endpoints for usage by end-customers user of the communication platform, but can alternatively include exporting/selling the endpoints out of the platform. In another implementation, the method is executed within a telephony endpoint management service that acts as a warehousing/registrar for telephony endpoints. The telephony endpoints are preferably a diverse collection from various countries, different regions, enabled with different features (e.g., voice enabled, SMS enabled, etc.), and/or having different properties (e.g., 800 number, particular area code, NPA-NXX pattern, particular number pattern, and the like). The repository of telephony endpoints may alternatively target a specified subset of telephony endpoints. The method preferably enables inventory to be maintained to satisfy the various patterns of telephony endpoint demand.
Block S110, which includes managing a set of telephony endpoints, functions to provide utility for the telephony endpoints within a platform. The set of telephony endpoints managed by the communication platform preferably means that external telephony and communication systems will direct communication to the communication platform for the endpoints in the set of telephony endpoints. Furthermore, the communication platform can make outgoing communications from an endpoint from the set of endpoints.
The telephony endpoints can preferably be in an allocated state or an unallocated state. An endpoint in an allocated state is preferably mapped to a user, account, or other suitable entity in the communication platform. The allocated telephony endpoints are assigned to or “owned” by a user account. The user account can then associate the telephony endpoint with an application, a routing configuration, and/or used in any suitable manner. A user account can make outgoing calls using an allocated endpoint, and communications directed at that endpoint can be received or otherwise trigger some event (e.g., execution of a telephony application). The communication platform is preferably a multitenant platform, and accordingly must manage a wide variety of telephony endpoint allocations. The various users will have different desires and requirements for the properties and characteristics of the specific endpoint or endpoints allocated to their user accounts. In some cases, a user may request an endpoint managed outside of the communication platform to be ported into the communication platform (e.g., changing routing of outside communication systems).
The unallocated telephony endpoints are preferably endpoints that are available to be allocated. Users can preferably query the set of unallocated telephony endpoints to select, purchase, rent, or otherwise allocated the telephony endpoint to their accounts. When searching for an endpoint, a user may be able to specify specific characteristics of the endpoint such as patterns in the number, geographic associations, communication capability, price, quality, and/or other suitable properties. The unallocated telephony endpoints are preferably managed through the method so as to provide a desirable pool of telephony endpoints. As described below, the managed telephony endpoints will be classified for different dimensions or properties. At least the inventory of unallocated endpoints is maintained to satisfy inventory target conditions. The unallocated endpoints may additionally be in an available and unavailable state. Available endpoints are in a state that can be allocated if or when selected. Unavailable endpoints are endpoints that are managed by the communication platform but may not be suitable or fully enrolled for allocation. The unavailable endpoints are preferably not offered in an endpoint marketplace. For example, an unavailable unallocated endpoint may go through various quality testing processes. One such quality testing process monitors incoming communications while the endpoint is unallocated to determine the dirtiness of the endpoint. The dirtiness of an endpoint preferably describes the level of mis-dialed or mis-directed (e.g., attempting to reach an old owner of the endpoint) communication.
Block S120, which includes receiving an endpoint inventory trigger, functions to intercept actions within a platform that impact inventory usage. Endpoint inventory triggers can include receiving an inventory allocation transaction S122 and/or detecting a change in the quality of at least one endpoint in the endpoint inventory S124 as shown in
Receiving an inventory allocation transaction S122 functions to respond to changes in endpoint status. A telephony endpoint management service is preferably an interface through which other services access or interact with telephony endpoints that are currently active or available in the platform. The management service is preferably a RESTful API exposed to internal services of a platform, but may alternatively be directly exposed to external services. The management service is preferably substantially similar to the telephony endpoint management service described above. As an intermediary component between the telephony endpoint repository and other applications, services, or components, the management service can preferably be configured to react and/or trigger actions when the telephony inventory is impacted. In one variation, a sub-set of types of requests is set to induce an inventory management response. In a preferred implementation, types of requests that trigger inventory monitoring include requesting a new endpoint, returning/canceling endpoint usage, searching for a type of telephony endpoint (e.g., searching for endpoints with a particular area code), porting a telephony endpoint, reserving/requesting a telephony endpoint, reporting quality/issues with a telephony endpoint, exchanging a telephony endpoint, and/or any suitable action to impact the telephony endpoint inventory. In some cases, such requests may be for a particular endpoint, but in other cases, such endpoint inventory requests specify characteristics or traits of an endpoint (e.g., searching for an endpoint with particular properties).
As an exemplary scenario, an outside application may need a new phone number. The outside application makes an API request (or alternatively completes an order online). This request is delivered to the associated communication platform, where a public API service receives the request and then transmits an internal API request to the telephony endpoint management service. The telephony endpoint management service detects that the request changes the amount of available inventory and messages the inventory monitor while processing the request and allocating one of the existing telephony endpoints to the outside application. The architecture of an intermediary telephony endpoint management service abstracts the monitoring of inventory so that inventory management can transparently occur without impacting operation of other services.
Since the telephony endpoint management service is the interface for querying telephony endpoint properties, the telephony endpoint management service can additionally review requests that query the endpoint for general usage. Endpoint usage can include a number of incoming calls, number of outgoing calls, number of messages sent, number of messages received, properties of calls and messages (e.g., where is the other leg of the call, what carrier is used), quality of communication, and other usage based parameters. Such usage may impact inventory predictions, such as predicting if a customer will return a telephony endpoint soon. Numbers that receive high usage and have high quality calls may be considered more static/long-term numbers, and the inventory monitor can account for such inventory stickiness when predicting supply. A telephony endpoint that is rarely used and/or suffers from quality issues may be returned or removed from an account soon and return to available inventory. A telephony endpoint with this usage pattern may be considered potentially available inventory in the future. For example, in one preferred implementation, when a phone call is received by the communication platform, the destination endpoint may be queried through the telephony endpoint management service to identity if an application exists for the phone number, if the call should be routed internally, if the call should be forwarded to another number, or how the call to the number should be handled.
Detecting a change in the quality of at least one endpoint in the endpoint inventory S124 functions to trigger an inventory update when one or more endpoints have changes in quality. The change in quality can occur to endpoints with any suitable status such as allocated, unallocated, available, or unavailable/evaluating. A quality feedback API may facilitate receiving quality feedback updates in response to communications with the endpoint. Similarly, communication monitoring and analytics could similarly provide data on communication quality of an endpoint. In some cases, endpoint registration with carriers or other entities may result in poor performance endpoints, such monitoring could detect when an endpoint enters such a state. Detecting a change in quality can additionally or alternatively include periodically executing automated quality testing. The quality testing may be substantially similar to the endpoint testing described below. The method preferably maintains a set of endpoints with some quality assurances for the endpoint. If the availability of quality endpoints in a particular category changes such quality monitoring can detect the event and respond.
Block S130, which includes evaluating state of an endpoint repository, functions to determine how changes in endpoint inventory are impacted. The evaluation of the state of an endpoint repository may be in performed upon receiving an endpoint inventory trigger, but may alternatively be periodically performed, performed in response to a system request, or triggered for any suitable reason. The evaluation of the state of the endpoint repository preferably transforms endpoint interactions described for Block S120 into recommended inventory actions. The evaluation can identify patterns in endpoints that should be acquired or released and optionally predict upcoming endpoint trends. Demand for endpoints is often not uniform across all endpoint characteristics. Block S130 preferably includes classifying endpoints S132, querying a telephony endpoint inventory monitor S134 and analyzing usage for at least one endpoint category S136 as shown in
Block S132, which includes classifying endpoints, functions to determine a set of tags, labels, or properties for each endpoint. A plurality of classifiers is preferably identified for each endpoint but alternatively a single classifier may be used. Additionally each endpoint may have a different number of classifiers. The classifiers are preferably organized into different classifier types, where each classifier type is for a particular category or dimension. The different types of classifiers can include classifiers for inherent properties of the endpoint and for measured properties. Some classifiers, such as the inherent property classifiers, are immutable. Other forms of classifiers, such as a quality classifier or capability classifier, may change over time. The classifiers can include country classifiers, region classifiers, communication capability classifiers (e.g., mobile capability, voice enabled, SMS enabled, MMS enabled, etc.), number type classifier (e.g., normal number, short code, 800 number, etc.) area code, NPA-NXX pattern (i.e., a numbering plan area code classifier), number patterns (e.g., XXX-XXX-1234), quality classifiers, and/or any suitable classifier type. The quality classifiers can be based on results from endpoint quality results from quality tests described below. The classification process is preferably pre-calculated and/or periodically updated, but the classifiers of the endpoints may alternatively be generated on-demand.
Blocks S134 and S136 function to evaluate endpoint inventory across a set of endpoint classification groupings and to detect at least one classification grouping that, based in part on the allocated and unallocated state of corresponding endpoints, satisfies an inventory update condition.
Block S134, which includes querying an inventory monitor, which functions to check inventory levels and account for changes in inventory. Querying the inventory monitory preferably includes performing a set of queries that use the classifiers in a classification grouping. The classification grouping preferably uses logic and other rule based definitions to define a queried set of endpoints that satisfy that classification grouping. The inventory monitor can be database. The results of the query can be inventory count, change in inventory, or any suitable metric or metrics. The management service preferably transmits a message to the inventory monitor upon detection of a triggerable inventory event. Inventory updates may alternatively be batched and sent in bulk. Triggerable inventory events preferably include allocating or removing a telephony endpoint for a user of the communication platform. Other triggerable events may additionally be used such as telephony usage and quality report events.
In one variation, the query can target a particular change in the inventory. For example, if one endpoint with a classifier identifying it as a number from area code 415 is allocated, then the inventory for area code 415 may be evaluated. The message preferably communicates the particular endpoint and the inventory action. Inventory actions may include allocating the particular endpoint. In other words, the endpoint is removed from available inventory to allocated inventory. Another inventory action may include setting the particular endpoint to available. Users of a platform may cancel their account, which can return telephony endpoints to an available state. Users may also individually cancel an endpoint, or telephony endpoint allocation may expire. For example, endpoints may expire after an account doesn't use the endpoint for a set duration or if the account becomes inactive. When a telephony endpoint become available, the telephony endpoint may receive analysis as described in Block S150. The inventory actions can additionally include porting of a number, which describes a request to move an endpoint out of the system. Another inventory action may be changes to inventory quality, which as mentioned above, can impact predictions on the duration of usage of the endpoint.
Querying a telephony endpoint inventory monitor preferably includes identifying inventory levels, which functions to segment inventory around the endpoint associated with the trigger. In the general scenario, the inventory is all treated as the same group. There are preferably at least two states of inventory: available unallocated inventory and allocated inventory. Available allocated inventory is inventory not assigned to a customer/user but available to be allocated. Allocated inventory is inventory that is currently maintained by the system and is assigned to at least one account or customer. There can be other inventory states such as an evaluation state, quarantine state, new inventory state, retired inventory, and other suitable states. Demand is often very different for different countries, area codes, and capabilities. The inventory monitor preferably allows inventory to managed based on various classification groupings. As shown in
Evaluation of the inventory for particular endpoint characteristics can include accounting for current inventory counts, which may include the count allocated inventory, count of available inventory, ratio of allocated to available inventory, inventory request rate, and other metrics for one or more endpoint identity characteristics or for the global inventory. Evaluating preferably factors in supply and demand aspects of the endpoint inventory.
Additionally, querying a telephony endpoint inventory monitor preferably includes accounting for endpoint inventory changes, which functions to update tracked metrics of inventory. When a message indicates an inventory change, the inventory accounting for the various classifications changes. Each classification of a telephony endpoint is preferably monitored or accounted for individually. For example, a phone number with a 415 area code and with SMS capabilities may be classified according to both these properties. The inventory for 415 numbers can be maintained and processed separately from the SMS-capability property. In this way, inventory for 415 numbers can satisfy demand and inventory for SMS capable numbers can also satisfy demand. Meta-categories may be combinations of properties. For example, a separate classification for SMS capable 415 numbers may ensure that enough inventory is maintained with both of these properties. Accounting preferably includes incrementing an inventory count when an endpoint is ported or added to the repository of endpoints; changing state between available and in-use when appropriate; decrementing an inventory count when an endpoint is removed or retired. When accounting endpoint inventory, the current tally or count of endpoints is preferably stored. Additionally, historical data of endpoint inventory may be stored, such that changes in inventory can be used to project demand. Usage and quality data may be used to generate predictions on lifespan of individual telephony endpoints in different classification groups.
Block S136, which includes analyzing usage for at least one endpoint classification, functions to detect if action should be taken to adjust inventory. In particular, block S136 includes detecting at least one classification grouping that satisfies an inventory update condition. The inventory update condition is preferably detected based at least in part on the allocated and unallocated state of endpoints that correspond to that classification grouping. The inventory monitor preferably compares the inventory metrics resulting from a classification grouping query to inventory thresholds. The inventory thresholds may be preset for different classifications. The inventory thresholds may additionally automatically adjust based on current and/or past inventory metrics. In one variation, if an inventory metric satisfies an inventory threshold (e.g., available inventory drops below a particular number), then a response is triggered to add or remove inventory. Accordingly, evaluating state of an endpoint repository preferably includes identifying at least one endpoint category in condition for transfer S138. The condition for transfer may be low supply or excess supply, which may each result in obtaining endpoints for that endpoint category or releasing endpoints in that endpoint category. Analyzing usage may additionally account for inventory metric history, where slope, acceleration, and other trends and properties are used to predict expected inventory requirements. The analysis may additionally factor in other properties of telephony endpoints other than the total count. As was previously mentioned, quality measurements of an endpoint can be incorporated into the usage analysis. Endpoint quality may be used to predict the lifetime of an in-use endpoint. Alternatively, endpoint quality may be used as a filter of endpoints such that the threshold is enforced upon only high quality endpoints. Analysis of the usage can trigger a response. Primarily, the inventory monitor is configured for managing inventory such that supply can satisfy future demand and thus replenishment is triggered. The inventory monitor can additionally change the state of endpoints to decommission un-needed endpoints or return/exchange/sell overly abundant endpoints.
Block S140, which includes transferring a set of endpoints with an inventory source, functions to initiate or complete an inventory order. Transferring of endpoints can include obtaining, removing/releasing, trading, or any suitable exchange of endpoints either in or out of the communication platform. Transferring a set of endpoints can include generating an endpoint transfer request. The transfer request will preferably specify the type of endpoints requested and the classifiers from the classification grouping. The transfer request can include a request endpoints from one classification grouping, but may additionally request endpoints for multiple classification groupings. Additionally, specific endpoints may be specified as being transferred out of the communication platform. The transfer of a set of endpoints is preferably made with a request for endpoints with characteristics or traits identified in Block S130. Transfer of the endpoints preferably includes selecting a provider S142 as shown in
Selecting a provider S142 functions to identify a source for a new telephony endpoint. A provider is selected if analysis indicates or reports inventory with endpoint property should be replenished. While the usage analysis is primarily focused on inventory replenishment, the inventory monitor can additionally trigger actions for other states of inventory. For example, some events may result in excess inventory and inventory will need to be removed. For example, a user of an endpoint may return or end use of an endpoint. At a certain threshold, endpoint inventory may exceed a maximum threshold, and in response, excess inventory is retired, repurposed, returned/sold to the original owner, exchanged for other telephony inventory, and/or managed in any suitable manner. A provider is preferably selected based on the inventory classification triggering the inventory request—providers may have varying preference based on the characteristics of the desired inventory. Selecting a provider can additionally account for cost, availability, reliability score of a provider (which may be based on inventory history and monitoring), contracts (e.g., a contract or other pre-defined rules may specify numbers of telephony endpoints that should be obtained in a set time frame from a particular provider), and/or any suitable property. While the inventory is preferably ordered to satisfy inventory need of at least one inventory classification, inventory requests may additionally be batched such that several inventory classifications can be replenished through a single telephony endpoint request to a provider. Inventory requests may be queued or held for a set amount of time to allow for other requests to come in. A single provider may be selected to provide telephony endpoints of all the endpoint requests; alternatively, multiple providers may be selected to supply the endpoints.
In a preferred scenario, the selected provider has an API for requesting telephony endpoints. Depending on the selected provider, an API request can be submitted. The request may specify properties of the requested telephony endpoints. Obtaining telephony endpoints through an API is preferably automatically performed. In one variation, a selected provider may not provide an API or other programmatic way of requesting more endpoint inventory. Inventory may require an order form to be submitted through mail, online, and/or over the phone. As a semi-automatic approach, the form can be automatically completed and transmitted to the appropriate party. In one case, a digital file or a printout of a telephony endpoint request form may be automatically completed and then sent to an administrator of the platform. The administrator can then complete delivery of the order with the provider (e.g., send in the mail or in an email). In another variation, an order may not be completed, but an alert message can be transmitted to an administrator or other entity to inform them of the inventory request. The inventory request will preferably include the number of telephony endpoints needed, the provider(s) from which they should be obtained, and any special requests for the endpoints. Transfer of the endpoints preferably includes updating of outside records to direct communications to those endpoints to the platform. In other words, the telephony endpoints are terminated at an IP address of the platform, such that communications are directed or forwarded to this controlled machine address where the platform can take appropriate action. In one variation, the endpoints may be binded through a whitelisted URI. After the order is confirmed, and the telephony endpoint addresses are delivered to the platform, a record is preferably created for each telephony endpoint added to the inventory repository. However, analysis of the endpoint may at least be partially completed prior to adding a record of the telephony endpoints.
Block S150, which includes selectively adding endpoints from the inventory source to the endpoint repository, functions to process, verify, and/or integrate any obtained inventory into the system. Upon fulfillment of the endpoint transfer request, the method preferably adds a set of new endpoints to the communication platform. Newly added endpoints are preferably added in an unavailable unallocated state. The endpoints may be made available after enrolling them (e.g., through a quality check and property check). In the case where endpoints were only transferred out of the system Block S150 may not be performed. However, when new inventory is added to the system, selectively adding endpoints form the inventory source includes analyzing obtained endpoint inventory. As one aspect of obtained inventory analysis, the obtained inventory may be inspected to verify that the endpoints match the desired characteristics and quantity. In some implementations, a provider of endpoints may provide telephony endpoints from a generic pool of endpoints. In other words, the provider may not deliver telephony endpoints matching particular characteristics. When verifying characteristics of the endpoint, undesirable telephony endpoints can be filtered out of the obtained telephony inventory. The undesired inventory may be returned to the provider and/or managed in any suitable manner. For example, the inventory monitor may request more telephone numbers with a 415 area code. If any numbers supplied by the provider do not have a 415 area code, the telephony numbers are returned to the provider. As another aspect, the inventory monitor or another component can perform automated testing of telephony endpoint capabilities. Tested capabilities can include capability of receiving calls, making calls, receiving messages, routing to client applications, and/or performing other suitable tasks.
Selectively adding endpoints to the endpoint repository S150 preferably includes executing automated quality testing of the obtained set of endpoints S152 as shown in
As shown in
The method can additionally include providing an API to endpoint inventory information S160. During the management of the endpoint repository substantial information can be collected to facilitate control monitoring of endpoint supplies. The provided API may be used internally in the communication platform, but the API may additionally be exposed publically for use by outside entities. The API preferably provides insight into metadata surrounding a phone number.
As shown in
The system and methods of the preferred embodiment and variations thereof can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with the telephony endpoint management service and inventory monitor. The computer-readable medium can be stored on any suitable computer-readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a general or application specific processor, but any suitable dedicated hardware or hardware/firmware combination device can alternatively or additionally execute the instructions.
As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments of the invention without departing from the scope of this invention defined in the following claims.
This application claims the benefit of U.S. Provisional Application Ser. No. 61/836,927 filed on 19 Jun. 2013, which is incorporated in its entirety by this reference.
Number | Name | Date | Kind |
---|---|---|---|
5274700 | Gechter et al. | Dec 1993 | A |
5526416 | Dezonno et al. | Jun 1996 | A |
5581608 | Jreij et al. | Dec 1996 | A |
5598457 | Foladare et al. | Jan 1997 | A |
5934181 | Adamczewski | Aug 1999 | A |
6026440 | Shrader et al. | Feb 2000 | A |
6094681 | Shaffer et al. | Jul 2000 | A |
6138143 | Gigliotti et al. | Oct 2000 | A |
6185565 | Meubus et al. | Feb 2001 | B1 |
6192123 | Grunsted et al. | Feb 2001 | B1 |
6206564 | Adamczewski | Mar 2001 | B1 |
6223287 | Douglas et al. | Apr 2001 | B1 |
6269336 | Ladd et al. | Jul 2001 | B1 |
6373836 | Deryugin et al. | Apr 2002 | B1 |
6425012 | Trovato et al. | Jul 2002 | B1 |
6430175 | Echols et al. | Aug 2002 | B1 |
6434528 | Sanders | Aug 2002 | B1 |
6445694 | Swartz | Sep 2002 | B1 |
6445776 | Shank et al. | Sep 2002 | B1 |
6459913 | Cloutier | Oct 2002 | B2 |
6493558 | Bernhart et al. | Dec 2002 | B1 |
6496500 | Nance et al. | Dec 2002 | B2 |
6501832 | Saylor et al. | Dec 2002 | B1 |
6507875 | Mellen-Garnett et al. | Jan 2003 | B1 |
6577721 | Vainio et al. | Jun 2003 | B1 |
6600736 | Ball et al. | Jul 2003 | B1 |
6606596 | Zirngibl et al. | Aug 2003 | B1 |
6614783 | Sonesh et al. | Sep 2003 | B1 |
6625258 | Ram et al. | Sep 2003 | B1 |
6625576 | Kochanski et al. | Sep 2003 | B2 |
6636504 | Albers et al. | Oct 2003 | B1 |
6662231 | Drosset et al. | Dec 2003 | B1 |
6704785 | Koo et al. | Mar 2004 | B1 |
6707889 | Saylor et al. | Mar 2004 | B1 |
6711249 | Weissman et al. | Mar 2004 | B2 |
6738738 | Henton | May 2004 | B2 |
6757365 | Bogard | Jun 2004 | B1 |
6765997 | Zirngibl et al. | Jul 2004 | B1 |
6768788 | Langseth et al. | Jul 2004 | B1 |
6778653 | Kallas et al. | Aug 2004 | B1 |
6785266 | Swartz | Aug 2004 | B2 |
6788768 | Saylor et al. | Sep 2004 | B1 |
6792086 | Saylor et al. | Sep 2004 | B1 |
6792093 | Barak et al. | Sep 2004 | B2 |
6798867 | Zirngibl et al. | Sep 2004 | B1 |
6807529 | Johnson et al. | Oct 2004 | B2 |
6807574 | Partovi et al. | Oct 2004 | B1 |
6819667 | Brusilovsky et al. | Nov 2004 | B1 |
6820260 | Flockhart et al. | Nov 2004 | B1 |
6829334 | Zirngibl et al. | Dec 2004 | B1 |
6834265 | Balasuriya | Dec 2004 | B2 |
6836537 | Zirngibl et al. | Dec 2004 | B1 |
6842767 | Partovi et al. | Jan 2005 | B1 |
6850603 | Eberle et al. | Feb 2005 | B1 |
6870830 | Schuster et al. | Mar 2005 | B1 |
6873952 | Bailey et al. | Mar 2005 | B1 |
6874084 | Dobner et al. | Mar 2005 | B1 |
6885737 | Gao et al. | Apr 2005 | B1 |
6888929 | Saylor et al. | May 2005 | B1 |
6895084 | Saylor et al. | May 2005 | B1 |
6898567 | Balasuriya | May 2005 | B2 |
6912581 | Johnson et al. | Jun 2005 | B2 |
6922411 | Taylor | Jul 2005 | B1 |
6931405 | El-Shimi et al. | Aug 2005 | B2 |
6937699 | Schuster et al. | Aug 2005 | B1 |
6940953 | Eberle et al. | Sep 2005 | B1 |
6941268 | Porter et al. | Sep 2005 | B2 |
6947417 | Laursen et al. | Sep 2005 | B2 |
6947988 | Saleh | Sep 2005 | B1 |
6961330 | Cattan et al. | Nov 2005 | B1 |
6964012 | Zirngibl et al. | Nov 2005 | B1 |
6970915 | Partovi et al. | Nov 2005 | B1 |
6977992 | Zirngibl et al. | Dec 2005 | B2 |
6985862 | Stroem et al. | Jan 2006 | B2 |
6999576 | Sacra | Feb 2006 | B2 |
7003464 | Ferrans et al. | Feb 2006 | B2 |
7006606 | Cohen et al. | Feb 2006 | B1 |
7010586 | Allavarpu et al. | Mar 2006 | B1 |
7020685 | Chen et al. | Mar 2006 | B1 |
7039165 | Saylor et al. | May 2006 | B1 |
7062709 | Cheung | Jun 2006 | B2 |
7076037 | Gonen et al. | Jul 2006 | B1 |
7076428 | Anastasakos et al. | Jul 2006 | B2 |
7089310 | Ellerman et al. | Aug 2006 | B1 |
7103003 | Brueckheimer et al. | Sep 2006 | B2 |
7103171 | Annadata et al. | Sep 2006 | B1 |
7106844 | Holland | Sep 2006 | B1 |
7111163 | Haney | Sep 2006 | B1 |
7140004 | Kunins et al. | Nov 2006 | B1 |
7143039 | Stifelman et al. | Nov 2006 | B1 |
7197331 | Anastasakos et al. | Mar 2007 | B2 |
7197461 | Eberle et al. | Mar 2007 | B1 |
7197462 | Takagi et al. | Mar 2007 | B2 |
7197544 | Wang et al. | Mar 2007 | B2 |
7225232 | Elberse | May 2007 | B2 |
7227849 | Rasanen | Jun 2007 | B1 |
7260208 | Cavalcanti | Aug 2007 | B2 |
7266181 | Zirngibl et al. | Sep 2007 | B1 |
7269557 | Bailey et al. | Sep 2007 | B1 |
7272212 | Eberle et al. | Sep 2007 | B2 |
7272564 | Phillips et al. | Sep 2007 | B2 |
7277851 | Henton | Oct 2007 | B1 |
7283515 | Fowler | Oct 2007 | B2 |
7286521 | Jackson et al. | Oct 2007 | B1 |
7287248 | Adeeb | Oct 2007 | B1 |
7289453 | Riedel et al. | Oct 2007 | B2 |
7296739 | Mo et al. | Nov 2007 | B1 |
7298732 | Cho | Nov 2007 | B2 |
7308085 | Weissman | Dec 2007 | B2 |
7308408 | Stifelman et al. | Dec 2007 | B1 |
7324633 | Gao et al. | Jan 2008 | B2 |
7324942 | Mahowald et al. | Jan 2008 | B1 |
7328263 | Sadjadi | Feb 2008 | B1 |
7330463 | Bradd et al. | Feb 2008 | B1 |
7330890 | Partovi et al. | Feb 2008 | B1 |
7340040 | Saylor et al. | Mar 2008 | B1 |
7349714 | Lee et al. | Mar 2008 | B2 |
7369865 | Gabriel et al. | May 2008 | B2 |
7376223 | Taylor et al. | May 2008 | B2 |
7376586 | Partovi et al. | May 2008 | B1 |
7376733 | Connelly et al. | May 2008 | B2 |
7376740 | Porter et al. | May 2008 | B1 |
7412525 | Cafarella et al. | Aug 2008 | B2 |
7428302 | Zirngibl et al. | Sep 2008 | B2 |
7440898 | Eberle et al. | Oct 2008 | B1 |
7447299 | Partovi et al. | Nov 2008 | B1 |
7454459 | Kapoor et al. | Nov 2008 | B1 |
7457397 | Saylor et al. | Nov 2008 | B1 |
7473872 | Takimoto | Jan 2009 | B2 |
7486780 | Zirngibl et al. | Feb 2009 | B2 |
7496054 | Taylor | Feb 2009 | B2 |
7500249 | Kampe et al. | Mar 2009 | B2 |
7505951 | Thompson et al. | Mar 2009 | B2 |
7519359 | Chiarulli et al. | Apr 2009 | B2 |
7522711 | Stein et al. | Apr 2009 | B1 |
7536454 | Balasuriya | May 2009 | B2 |
7552054 | Stifelman et al. | Jun 2009 | B1 |
7571226 | Partovi et al. | Aug 2009 | B1 |
7613287 | Stifelman et al. | Nov 2009 | B1 |
7623648 | Oppenheim et al. | Nov 2009 | B1 |
7630900 | Strom | Dec 2009 | B1 |
7631310 | Henzinger | Dec 2009 | B1 |
7644000 | Strom | Jan 2010 | B1 |
7657433 | Chang | Feb 2010 | B1 |
7657434 | Thompson et al. | Feb 2010 | B2 |
7668157 | Weintraub et al. | Feb 2010 | B2 |
7672295 | Andhare et al. | Mar 2010 | B1 |
7675857 | Chesson | Mar 2010 | B1 |
7676221 | Roundtree et al. | Mar 2010 | B2 |
7715547 | Ibbotson et al. | May 2010 | B2 |
7779065 | Gupta et al. | Aug 2010 | B2 |
7875836 | Imura et al. | Jan 2011 | B2 |
7882253 | Pardo-Castellote et al. | Feb 2011 | B2 |
7920866 | Bosch et al. | Apr 2011 | B2 |
7926099 | Chakravarty et al. | Apr 2011 | B1 |
7936867 | Hill et al. | May 2011 | B1 |
7962644 | Ezerzer et al. | Jun 2011 | B1 |
7979555 | Rothstein et al. | Jul 2011 | B2 |
8023425 | Raleigh | Sep 2011 | B2 |
8069096 | Ballaro et al. | Nov 2011 | B1 |
8081958 | Soederstroem et al. | Dec 2011 | B2 |
8103725 | Gupta et al. | Jan 2012 | B2 |
8126128 | Hicks, Iii et al. | Feb 2012 | B1 |
8149716 | Ramanathan et al. | Apr 2012 | B2 |
8150918 | Edelman et al. | Apr 2012 | B1 |
8156213 | Deng et al. | Apr 2012 | B1 |
8196133 | Kakumani et al. | Jun 2012 | B2 |
8233611 | Zettner | Jul 2012 | B1 |
8243889 | Taylor et al. | Aug 2012 | B2 |
8266327 | Kumar et al. | Sep 2012 | B2 |
8295272 | Boni et al. | Oct 2012 | B2 |
8306021 | Lawson et al. | Nov 2012 | B2 |
8326805 | Arous et al. | Dec 2012 | B1 |
8346630 | McKeown | Jan 2013 | B1 |
8355394 | Taylor et al. | Jan 2013 | B2 |
8417817 | Jacobs | Apr 2013 | B1 |
8429827 | Wetzel | Apr 2013 | B1 |
8438315 | Tao et al. | May 2013 | B1 |
8462670 | Chien et al. | Jun 2013 | B2 |
8509068 | Begall et al. | Aug 2013 | B2 |
8532686 | Schmidt et al. | Sep 2013 | B2 |
8542805 | Agranovsky et al. | Sep 2013 | B2 |
8594626 | Woodson et al. | Nov 2013 | B1 |
8611338 | Lawson et al. | Dec 2013 | B2 |
8649268 | Lawson et al. | Feb 2014 | B2 |
8667056 | Proulx et al. | Mar 2014 | B1 |
8675493 | Buddhikot et al. | Mar 2014 | B2 |
8755376 | Lawson et al. | Jun 2014 | B2 |
8806024 | Francis et al. | Aug 2014 | B1 |
8837465 | Lawson et al. | Sep 2014 | B2 |
8838707 | Lawson et al. | Sep 2014 | B2 |
9014664 | Kim et al. | Apr 2015 | B2 |
9015702 | Bhat | Apr 2015 | B2 |
20010038624 | Greenberg et al. | Nov 2001 | A1 |
20010043684 | Guedalia et al. | Nov 2001 | A1 |
20020006124 | Jimenez et al. | Jan 2002 | A1 |
20020006125 | Josse et al. | Jan 2002 | A1 |
20020006193 | Rodenbusch et al. | Jan 2002 | A1 |
20020067823 | Walker et al. | Jun 2002 | A1 |
20020077833 | Arons et al. | Jun 2002 | A1 |
20020126813 | Partovi et al. | Sep 2002 | A1 |
20020136391 | Armstrong | Sep 2002 | A1 |
20020176378 | Hamilton et al. | Nov 2002 | A1 |
20020198941 | Gavrilescu et al. | Dec 2002 | A1 |
20030006137 | Wei et al. | Jan 2003 | A1 |
20030018830 | Chen et al. | Jan 2003 | A1 |
20030026426 | Wright et al. | Feb 2003 | A1 |
20030046366 | Pardikar et al. | Mar 2003 | A1 |
20030051037 | Sundaram et al. | Mar 2003 | A1 |
20030058884 | Kallner et al. | Mar 2003 | A1 |
20030059020 | Meyerson et al. | Mar 2003 | A1 |
20030060188 | Gidron et al. | Mar 2003 | A1 |
20030061317 | Brown et al. | Mar 2003 | A1 |
20030061404 | Atwal et al. | Mar 2003 | A1 |
20030088421 | Maes et al. | May 2003 | A1 |
20030103620 | Brown et al. | Jun 2003 | A1 |
20030123640 | Roelle et al. | Jul 2003 | A1 |
20030195990 | Greenblat | Oct 2003 | A1 |
20030196076 | Zabarski et al. | Oct 2003 | A1 |
20030211842 | Kempf et al. | Nov 2003 | A1 |
20030231647 | Petrovykh | Dec 2003 | A1 |
20040011690 | Marfino et al. | Jan 2004 | A1 |
20040044953 | Watkins et al. | Mar 2004 | A1 |
20040052349 | Creamer et al. | Mar 2004 | A1 |
20040071275 | Bowater et al. | Apr 2004 | A1 |
20040101122 | Da Palma et al. | May 2004 | A1 |
20040102182 | Reith et al. | May 2004 | A1 |
20040165569 | Sweatman et al. | Aug 2004 | A1 |
20040172482 | Weissman et al. | Sep 2004 | A1 |
20040205689 | Ellens et al. | Oct 2004 | A1 |
20040213400 | Golitsin et al. | Oct 2004 | A1 |
20040218748 | Fisher | Nov 2004 | A1 |
20050005200 | Matena et al. | Jan 2005 | A1 |
20050010483 | Ling | Jan 2005 | A1 |
20050021626 | Prajapat et al. | Jan 2005 | A1 |
20050025303 | Hostetler | Feb 2005 | A1 |
20050038772 | Colrain | Feb 2005 | A1 |
20050043952 | Sharma et al. | Feb 2005 | A1 |
20050047579 | Salame | Mar 2005 | A1 |
20050091572 | Gavrilescu et al. | Apr 2005 | A1 |
20050125251 | Berger et al. | Jun 2005 | A1 |
20050128961 | Miloslavsky et al. | Jun 2005 | A1 |
20050135578 | Ress et al. | Jun 2005 | A1 |
20050141500 | Bhandari et al. | Jun 2005 | A1 |
20050147088 | Bao et al. | Jul 2005 | A1 |
20050177635 | Schmidt et al. | Aug 2005 | A1 |
20050181835 | Lau et al. | Aug 2005 | A1 |
20050228680 | Malik | Oct 2005 | A1 |
20050238153 | Chevalier | Oct 2005 | A1 |
20050240659 | Taylor | Oct 2005 | A1 |
20050243977 | Creamer et al. | Nov 2005 | A1 |
20050246176 | Creamer et al. | Nov 2005 | A1 |
20060008073 | Yoshizawa et al. | Jan 2006 | A1 |
20060015467 | Morken et al. | Jan 2006 | A1 |
20060047666 | Bedi et al. | Mar 2006 | A1 |
20060067506 | Flockhart et al. | Mar 2006 | A1 |
20060129638 | Deakin | Jun 2006 | A1 |
20060143007 | Koh et al. | Jun 2006 | A1 |
20060168334 | Potti et al. | Jul 2006 | A1 |
20060203979 | Jennings | Sep 2006 | A1 |
20060209695 | Archer et al. | Sep 2006 | A1 |
20060212865 | Vincent et al. | Sep 2006 | A1 |
20060215824 | Mitby et al. | Sep 2006 | A1 |
20060217823 | Hussey | Sep 2006 | A1 |
20060217978 | Mitby et al. | Sep 2006 | A1 |
20060222166 | Ramakrishna et al. | Oct 2006 | A1 |
20060256816 | Yarlagadda et al. | Nov 2006 | A1 |
20060262915 | Marascio et al. | Nov 2006 | A1 |
20060270386 | Yu et al. | Nov 2006 | A1 |
20060285489 | Francisco et al. | Dec 2006 | A1 |
20070002744 | Mewhinney et al. | Jan 2007 | A1 |
20070036143 | Alt et al. | Feb 2007 | A1 |
20070050306 | McQueen | Mar 2007 | A1 |
20070070906 | Thakur | Mar 2007 | A1 |
20070070980 | Phelps et al. | Mar 2007 | A1 |
20070071223 | Lee et al. | Mar 2007 | A1 |
20070074174 | Thornton | Mar 2007 | A1 |
20070121651 | Casey et al. | May 2007 | A1 |
20070127691 | Lert | Jun 2007 | A1 |
20070127703 | Siminoff | Jun 2007 | A1 |
20070130260 | Weintraub et al. | Jun 2007 | A1 |
20070133771 | Stifelman et al. | Jun 2007 | A1 |
20070153711 | Dykas et al. | Jul 2007 | A1 |
20070167170 | Fitchett et al. | Jul 2007 | A1 |
20070192629 | Saito | Aug 2007 | A1 |
20070208862 | Fox et al. | Sep 2007 | A1 |
20070242626 | Altberg et al. | Oct 2007 | A1 |
20070265073 | Novi et al. | Nov 2007 | A1 |
20070286180 | Marquette et al. | Dec 2007 | A1 |
20070291905 | Halliday et al. | Dec 2007 | A1 |
20070293200 | Roundtree et al. | Dec 2007 | A1 |
20070295803 | Levine et al. | Dec 2007 | A1 |
20080005275 | Overton et al. | Jan 2008 | A1 |
20080025320 | Bangalore et al. | Jan 2008 | A1 |
20080037715 | Prozeniuk et al. | Feb 2008 | A1 |
20080037746 | Dufrene et al. | Feb 2008 | A1 |
20080040484 | Yardley | Feb 2008 | A1 |
20080052395 | Wright et al. | Feb 2008 | A1 |
20080091843 | Kulkarni | Apr 2008 | A1 |
20080101571 | Harlow et al. | May 2008 | A1 |
20080104348 | Kabzinski et al. | May 2008 | A1 |
20080134049 | Gupta et al. | Jun 2008 | A1 |
20080139166 | Agarwal et al. | Jun 2008 | A1 |
20080146268 | Gandhi et al. | Jun 2008 | A1 |
20080152101 | Griggs | Jun 2008 | A1 |
20080154601 | Stifelman et al. | Jun 2008 | A1 |
20080155029 | Helbling et al. | Jun 2008 | A1 |
20080162482 | Ahern et al. | Jul 2008 | A1 |
20080165708 | Moore et al. | Jul 2008 | A1 |
20080177883 | Hanai et al. | Jul 2008 | A1 |
20080209050 | Li | Aug 2008 | A1 |
20080222656 | Lyman | Sep 2008 | A1 |
20080232574 | Baluja et al. | Sep 2008 | A1 |
20080235230 | Maes | Sep 2008 | A1 |
20080256224 | Kaji et al. | Oct 2008 | A1 |
20080275741 | Loeffen | Nov 2008 | A1 |
20080310599 | Purnadi et al. | Dec 2008 | A1 |
20080313318 | Vermeulen et al. | Dec 2008 | A1 |
20080316931 | Qiu et al. | Dec 2008 | A1 |
20080317222 | Griggs et al. | Dec 2008 | A1 |
20090046838 | Andreasson | Feb 2009 | A1 |
20090052437 | Taylor et al. | Feb 2009 | A1 |
20090052641 | Taylor et al. | Feb 2009 | A1 |
20090074159 | Goldfarb et al. | Mar 2009 | A1 |
20090075684 | Cheng et al. | Mar 2009 | A1 |
20090083155 | Tudor et al. | Mar 2009 | A1 |
20090089165 | Sweeney | Apr 2009 | A1 |
20090089699 | Saha et al. | Apr 2009 | A1 |
20090093250 | Jackson et al. | Apr 2009 | A1 |
20090125608 | Werth et al. | May 2009 | A1 |
20090129573 | Gavan et al. | May 2009 | A1 |
20090136011 | Goel | May 2009 | A1 |
20090171659 | Pearce et al. | Jul 2009 | A1 |
20090171669 | Engelsma et al. | Jul 2009 | A1 |
20090171752 | Galvin et al. | Jul 2009 | A1 |
20090217293 | Wolber et al. | Aug 2009 | A1 |
20090220057 | Waters | Sep 2009 | A1 |
20090221310 | Chen et al. | Sep 2009 | A1 |
20090222341 | Belwadi et al. | Sep 2009 | A1 |
20090225748 | Taylor | Sep 2009 | A1 |
20090225763 | Forsberg et al. | Sep 2009 | A1 |
20090232289 | Drucker et al. | Sep 2009 | A1 |
20090235349 | Lai et al. | Sep 2009 | A1 |
20090252159 | Lawson et al. | Oct 2009 | A1 |
20090276771 | Nickolov et al. | Nov 2009 | A1 |
20090288165 | Qiu et al. | Nov 2009 | A1 |
20090300194 | Ogasawara | Dec 2009 | A1 |
20090316687 | Kruppa | Dec 2009 | A1 |
20090318112 | Vasten | Dec 2009 | A1 |
20100037204 | Lin et al. | Feb 2010 | A1 |
20100070424 | Monk | Mar 2010 | A1 |
20100082513 | Liu | Apr 2010 | A1 |
20100087215 | Gu et al. | Apr 2010 | A1 |
20100088187 | Courtney et al. | Apr 2010 | A1 |
20100088698 | Krishnamurthy | Apr 2010 | A1 |
20100115041 | Hawkins et al. | May 2010 | A1 |
20100142516 | Lawson et al. | Jun 2010 | A1 |
20100150139 | Lawson et al. | Jun 2010 | A1 |
20100167689 | Sepehri-Nik et al. | Jul 2010 | A1 |
20100188979 | Thubert et al. | Jul 2010 | A1 |
20100191915 | Spencer | Jul 2010 | A1 |
20100208881 | Kawamura | Aug 2010 | A1 |
20100217837 | Ansari et al. | Aug 2010 | A1 |
20100217982 | Brown et al. | Aug 2010 | A1 |
20100232594 | Lawson et al. | Sep 2010 | A1 |
20100235539 | Carter et al. | Sep 2010 | A1 |
20100251329 | Wei | Sep 2010 | A1 |
20100251340 | Martin et al. | Sep 2010 | A1 |
20100281108 | Cohen | Nov 2010 | A1 |
20100291910 | Sanding et al. | Nov 2010 | A1 |
20110029882 | Jaisinghani | Feb 2011 | A1 |
20110053555 | Cai et al. | Mar 2011 | A1 |
20110078278 | Cui et al. | Mar 2011 | A1 |
20110081008 | Lawson et al. | Apr 2011 | A1 |
20110083179 | Lawson et al. | Apr 2011 | A1 |
20110093516 | Geng et al. | Apr 2011 | A1 |
20110096673 | Stevenson et al. | Apr 2011 | A1 |
20110110366 | Moore et al. | May 2011 | A1 |
20110131293 | Mori | Jun 2011 | A1 |
20110167172 | Roach et al. | Jul 2011 | A1 |
20110170505 | Rajasekar et al. | Jul 2011 | A1 |
20110176537 | Lawson et al. | Jul 2011 | A1 |
20110211679 | Mezhibovsky et al. | Sep 2011 | A1 |
20110251921 | Kassaei et al. | Oct 2011 | A1 |
20110253693 | Lyons et al. | Oct 2011 | A1 |
20110255675 | Jasper et al. | Oct 2011 | A1 |
20110265172 | Sharma et al. | Oct 2011 | A1 |
20110267985 | Wilkinson et al. | Nov 2011 | A1 |
20110276892 | Jensen-Horne et al. | Nov 2011 | A1 |
20110276951 | Jain | Nov 2011 | A1 |
20110280390 | Lawson et al. | Nov 2011 | A1 |
20110283259 | Lawson et al. | Nov 2011 | A1 |
20110289126 | Aikas et al. | Nov 2011 | A1 |
20110299672 | Chiu et al. | Dec 2011 | A1 |
20110320449 | Gudlavenkatasiva | Dec 2011 | A1 |
20110320550 | Lawson et al. | Dec 2011 | A1 |
20120000903 | Baarman et al. | Jan 2012 | A1 |
20120017222 | May | Jan 2012 | A1 |
20120028602 | Lisi et al. | Feb 2012 | A1 |
20120036574 | Heithcock et al. | Feb 2012 | A1 |
20120039202 | Song | Feb 2012 | A1 |
20120059709 | Lieberman | Mar 2012 | A1 |
20120079066 | Li et al. | Mar 2012 | A1 |
20120110564 | Ran et al. | May 2012 | A1 |
20120114112 | Rauschenberger et al. | May 2012 | A1 |
20120149404 | Beattie et al. | Jun 2012 | A1 |
20120173610 | Bleau et al. | Jul 2012 | A1 |
20120174095 | Natchadalingam et al. | Jul 2012 | A1 |
20120198004 | Watte | Aug 2012 | A1 |
20120201238 | Lawson et al. | Aug 2012 | A1 |
20120208495 | Lawson et al. | Aug 2012 | A1 |
20120226579 | Ha et al. | Sep 2012 | A1 |
20120239757 | Firstenberg et al. | Sep 2012 | A1 |
20120254828 | Aiylam et al. | Oct 2012 | A1 |
20120281536 | Gell et al. | Nov 2012 | A1 |
20120288082 | Segall | Nov 2012 | A1 |
20120290706 | Lin et al. | Nov 2012 | A1 |
20120304245 | Lawson et al. | Nov 2012 | A1 |
20120304275 | Ji et al. | Nov 2012 | A1 |
20120316809 | Egolf et al. | Dec 2012 | A1 |
20130029629 | Lindholm et al. | Jan 2013 | A1 |
20130031158 | Salsburg | Jan 2013 | A1 |
20130054684 | Brazier et al. | Feb 2013 | A1 |
20130058262 | Parreira | Mar 2013 | A1 |
20130067448 | Sannidhanam et al. | Mar 2013 | A1 |
20130156024 | Burg | Jun 2013 | A1 |
20130212603 | Cooke et al. | Aug 2013 | A1 |
20130244632 | Spence et al. | Sep 2013 | A1 |
20140064467 | Lawson et al. | Mar 2014 | A1 |
20140105372 | Nowack et al. | Apr 2014 | A1 |
20140106704 | Cooke et al. | Apr 2014 | A1 |
20140123187 | Reisman | May 2014 | A1 |
20140129363 | Lorah et al. | May 2014 | A1 |
20140153565 | Lawson et al. | Jun 2014 | A1 |
20140185490 | Holm et al. | Jul 2014 | A1 |
20140274086 | Boerjesson et al. | Sep 2014 | A1 |
20140282473 | Saraf et al. | Sep 2014 | A1 |
20140355600 | Lawson et al. | Dec 2014 | A1 |
20150004932 | Kim et al. | Jan 2015 | A1 |
20150004933 | Kim et al. | Jan 2015 | A1 |
Number | Date | Country |
---|---|---|
1684587 | Mar 1971 | DE |
0282126 | Sep 1988 | EP |
1464418 | Oct 2004 | EP |
1522922 | Apr 2005 | EP |
1770586 | Apr 2007 | EP |
2134107 | Sep 1999 | ES |
10294788 | Apr 1998 | JP |
2004166000 | Jun 2004 | JP |
2004220118 | Aug 2004 | JP |
2006319914 | Nov 2006 | JP |
9732448 | Sep 1997 | WO |
02087804 | Nov 2002 | WO |
2006037492 | Apr 2006 | WO |
2009018489 | Feb 2009 | WO |
2009124223 | Oct 2009 | WO |
2010037064 | Apr 2010 | WO |
2010040010 | Apr 2010 | WO |
2010101935 | Sep 2010 | WO |
2011091085 | Jul 2011 | WO |
Entry |
---|
RFC 3986: Uniform Resource Identifier (URI): Generic Syntax; T. Berners-Lee, R. Fielding, L. Masinter; Jan. 2005; The Internet Society. |
Number | Date | Country | |
---|---|---|---|
20140376389 A1 | Dec 2014 | US |
Number | Date | Country | |
---|---|---|---|
61836927 | Jun 2013 | US |