# US 10,455,055 B2 · System and method for customization of a local application > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,455,055 B2 - Document ID: US10455055B2 - Status: Granted - Kind: B2 - Application number: 14/746,987 - Filed: 2015-06-23 - Published: 2016-10-06 - Granted: 2019-10-22 - Earliest claimed: 2015-04-02 - Assignees: Avaya Inc. - Applicants: Avaya Inc. - Inventors: Luciano Godoy Fagundes - Web page: https://patentgrep.com/patent/US10455055B2 ## CPC - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - H04L 67/63: Routing a service request depending on the request content or context - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A common vendor application that can be called from multiple vendor applications is loaded onto a communication device. When the common vendor application is called from an application provided by a vendor, the common vendor application sends a request to access vendor configuration information to a common vendor server. The request includes a vendor identifier that uniquely identifies the vendor. In response to receiving the request to access the vendor configuration information, the common vendor server identifies vendor configuration information for the vendor. The vendor configuration information is sent the common vendor application on the communication device. The common vendor application uses the vendor configuration information to customize the common vendor application specific to the vendor. This allows multiple vendors to use the same common vendor application, but to have a common look-and-feel. It also reduces the number of applications necessary to support multiple vendors. ## Claims ### Claim 1 A system comprising: a processor; and a non-transitory computer readable medium, coupled with the processor and comprising readable and executable instructions that program the processor to execute: a common vendor server that receives, via a network and from a communication device, a first request to access vendor configuration information from a common vendor application called by a first vendor application on the communication device, wherein the request includes a first vendor identifier, wherein the first vendor identifier uniquely identifies the first vendor from other vendors using the common vendor server, and wherein the first vendor and the other vendors are at least one of a person, an individual, a company, and an enterprise; identifies, using the first vendor identifier, first vendor configuration information for the common vendor application in response to receiving the first request to access the vendor configuration information, wherein the first vendor configuration information customizes the common vendor application specific to the first vendor; sends the first vendor configuration information to the communication device, wherein the common vendor server receives a second request to access the vendor configuration information from the common vendor application called by a second vendor application on the communication device, wherein the request includes a second vendor identifier, and wherein the second vendor application is created by a different vendor than the first vendor application; identifies, using the second vendor identifier, second vendor configuration information for the common vendor application in response to receiving the second request to access the vendor configuration information, wherein the second vendor configuration information customizes the common vendor application specific to the second vendor; and sends the second vendor configuration information to the communication device. ### Claim 2 (depends on 1) The system of claim 1, wherein the common vendor server determines if the first vendor configuration information in the communication device is outdated, wherein the first vendor configuration information is sent to the communication device to update the communication device if the first vendor configuration information in the communication device is outdated. ### Claim 3 (depends on 2) The system of claim 2, wherein the common vendor application is automatically loaded using the first vendor configuration information. ### Claim 4 (depends on 1) The system of claim 1, wherein the common vendor application is automatically loaded using the second vendor configuration information. ### Claim 5 (depends on 1) The system of claim 1, wherein the first vendor configuration information is uploaded to the common vendor server by the first vendor and wherein the second vendor configuration information is uploaded to the common vendor server by the second vendor. ### Claim 6 (depends on 1) The system of claim 1, wherein the first vendor configuration information is used to disable at least a first portion of the functionality of the common vendor application and the second vendor configuration information is used to disable a second portion of the functionality of the common vendor application, the second portion being different than the first portion. ### Claim 7 (depends on 1) The system of claim 1, wherein the first vendor application accesses the common vendor application from multiple points in the first vendor application. ### Claim 8 (depends on 1) The system of claim 1, wherein the first vendor application and the common vendor application are downloaded to the communication device from an application store. ### Claim 9 (depends on 1) The system of claim 1, wherein the first vendor configuration information customizes the common vendor application specific to the first vendor by changing a look and feel of a graphical interface on the common vendor application. ### Claim 10 A method comprising: receiving, by a processor via a network and from a communication device, a first request to access vendor configuration information from a common vendor application called from a first vendor application on the communication device, wherein the first request includes a first vendor identifier, wherein the first vendor identifier uniquely identifies the first vendor from other vendors, and wherein the first vendor and the other vendors are at least one of a person, an individual, a company, and an enterprise; in response to receiving the first request to access the vendor configuration information, identifying, using, by the processor, the first vendor identifier, first vendor configuration information for the common vendor application, wherein the first vendor configuration information customizes the common vendor application specific to the first vendor; sending, by the processor, the first vendor configuration information to the communication device; receiving a second request to access the vendor configuration information from the common vendor application called from a second vendor application on the communication device, wherein the second request includes a second vendor identifier, and wherein the second vendor application is created by a different vendor than the first vendor application; In response to receiving the second request to access the vendor configuration Information, identifying, using the second vendor identifier, second vendor configuration Information for the common vendor application, wherein the second vendor configuration Information customizes the common vendor application specific to the second vendor; and sending the second vendor configuration Information to the communication device. ### Claim 11 (depends on 10) The method of claim 10, further comprising: determining if the first vendor configuration information in the communication device is outdated, wherein the first vendor configuration information is sent to the communication device to update the communication device if the first vendor configuration information in the communication device is outdated. ### Claim 12 (depends on 11) The method of claim 11, wherein the common vendor application is automatically loaded using the first vendor configuration information. ### Claim 13 (depends on 10) The method of claim 10, wherein the common vendor application is automatically loaded using the second vendor configuration information. ### Claim 14 (depends on 10) The method of claim 10, wherein the first vendor configuration information is uploaded to a common vendor server by the first vendor and wherein the second vendor configuration information is uploaded to the common vendor server by the second vendor. ### Claim 15 (depends on 10) The method of claim 10, wherein the first vendor configuration information is used to disable at least a first portion of the functionality of the common vendor application and the second vendor configuration information is used to disable a second portion of the functionality of the common vendor application, the second portion being different than the first portion. ### Claim 16 (depends on 10) The method of claim 10, wherein the first request is in the form of a Uniform Resource Locator (URL), wherein the URL comprises the first vendor identifier, a make call identifier, a callee identifier, a product identifier, and a communication type. ### Claim 17 (depends on 16) The method of claim 16, wherein the URL is sent in the first request when a call button in the first vendor application is selected. ### Claim 18 A non-transitory computer readable medium having stored thereon instructions that, when executed, cause a processor to perform a method, the instructions comprising: instructions to receive a first request, via a network and from a communication device, to access vendor configuration information from a common vendor application called from a first vendor application on the communication device, wherein the first request includes a first vendor identifier, wherein the first vendor identifier uniquely identifies the first vendor from other vendors, and wherein the first vendor and the other vendors are at least one of a person, an individual, a company, and an enterprise; in response to receiving the first request to access the vendor configuration information, instructions to identify, using the first vendor identifier, first vendor configuration information for the common vendor application, wherein the first vendor configuration information customizes the common vendor application specific to the first vendor; instructions to send the first vendor configuration information to the communication device; instructions to receive a second request to access the vendor configuration information from the common vendor application called from a second vendor application on the communication device, wherein the second request includes a second vendor identifier, and wherein the second vendor application is created by a different vendor than the first vendor application; in response to receiving the second request to access the vendor configuration information, instructions to identify, using the second vendor identifier, second vendor configuration information for the common vendor application, wherein the second vendor configuration information customizes the common vendor application specific to the second vendor; and instructions to send the second vendor configuration information to the communication device. ### Claim 19 (depends on 1) The system of claim 1, wherein the first request is in the form of a Uniform Resource Locator (URL), wherein the URL comprises the first vendor identifier, a make call identifier, a callee identifier, a product identifier, and a communication type. ### Claim 20 (depends on 19) The system of claim 19, wherein the URL is sent in the first request when a call button in the first vendor application is selected.