Patent Grant
11392671
The present invention relates to a technique of delivering an updated application to an appropriate delivery destination.
Conventionally, there is known a technique of delivering an updated application to a device installing an old-version application. However, out of applications, even the same applications in the same version may have different “destinations.” The “destination” is the delivery destination of the application, and the destinations fall into classifications, for example, “Japan,” “Europe,” and the like. More specifically, the destinations may be classified into groups according to a sales company selling devices.
Japanese Patent Laid-open No. 2005-215945 discloses a technique of making an application available only at a specific delivery destination. In Japanese Patent Laid-open No. 2005-215945, there is stored a license file including identification data on a manufacturer of a memory card. At the time of executing the application, the identification data on the manufacturer included in the license file is read by using an encryption key inside the application to specify an authentication key. This makes the application available only at the specific delivery destination.
However, the technique disclosed in Japanese Patent Laid-open No. 2005-215945 uses information included in the application to make the application available only at the specific delivery destination. Since the above “destination” is information which is not generally included in the application, the technique disclosed in Japanese Patent Laid-open No. 2005-215945 cannot deliver the application to the appropriate delivery destination.
In an aspect of the present invention, there is provided a delivery management server for managing delivery of an application connected via network to a license management server for managing a license of the application and an information processing device installing the application, the delivery management server comprising: a first receiving unit configured to receive, from the information processing device, application identification information for identifying the application and key information on the application; a managing unit configured to manage the application identification information and the key information received by the first receiving unit in association with device identification information on the information processing device; a first transmitting unit configured to transmit, to the license management server, the application identification information and the key information received by the first receiving unit; and a second receiving unit configured to receive destination information transmitted from the license management server in response to transmission by the first transmitting unit, the destination information indicating a destination of the application, wherein the managing unit manages the destination information received by the second receiving unit in association with the managed information.
Further features of the present invention will become apparent from the following description of exemplary embodiments (with reference to the attached drawings).
With reference to the accompanying drawings, the present invention will be described in detail below based on preferred embodiments of the present invention. Incidentally, the features of the following embodiments are mere examples and the present invention is not limited to the illustrated features.
In subsequent descriptions, an application may be abbreviated as an app, and the word “app” is synonymous with the word “application.”
The license management server 110 includes a destination information extracting unit 111, a related application information managing unit 112, an application delivery information transmitting unit 113, and a license information issuing unit 114. Further, the license management server 110 includes a license information management database 115 for managing destination information, application information, and license information.
The user terminal 120 includes a displaying unit 121 and an inputting unit 122. The user terminal 120 requests the delivery management server 140 to perform processing. Incidentally, explanation has been made on an example in which the user terminal 120 is a separate device, but it is possible to use, as the user terminal, an input device and a display device connected to an interface of the delivery management server 140.
The image forming device 130 capable of installing and executing an application as explained according to the present embodiment includes an app & key information transmitting unit 131, a delivery setting checking unit 132, a delivery information receiving unit 133, a license file obtaining unit 134, and an installing unit 135. Incidentally, in the present embodiment, explanation has been made by citing, as an example, the image forming device such as a multifunction peripheral (MFP) as the device capable of installing and executing an application, but the present invention is not limited to this. Any device can be used as long as the device can install and execute an application, and it is possible to use various information processing devices (apparatuses) such as general computers, smartphones, and tablets.
The delivery management server 140 includes a list generating unit 141, a delivery information setting unit 142, and an app & key information managing unit 143. Further, the delivery management server 140 includes a delivery information management database 144 for managing app & key information and delivery setting information. Incidentally, in the present embodiment, explanation has been made on an example in which the license management server 110 and the delivery management server 140 are separate server devices, but the present invention is not limited to this. More specifically, it is possible to use a server device in which the function of the license management server 110 and the function of the delivery management server 140 are integrated.
<Processing Sequence for a System>
The delivery management server 140 having received this information stores the received information in association with information for identifying the image forming device having transmitting the information. Managing the information in this manner, the delivery management server 140 can deliver an updated application to the image forming device requiring the updated application. In the present embodiment, in step S230, which has been described later, the delivery management server 140 further associates the information managed by the delivery management server 140 with the destination information. Associating the managed information with the destination information, the delivery management server 140 can specify the image forming device on which the application having a predetermined destination is installed.
In step S220, the delivery management server 140 transmits the ID of the application and the hash value of the common key to the license management server 110. The license management server 110 having received this information extracts the destination information based on the received application ID and the received hash value of the common key.
In step S230, the license management server 110 transmits the extracted destination information to the delivery management server 140 as a response to step S220. The delivery management server 140 stores the received destination information in association with the transmitted application ID and the transmitted hash value of the common key. In this manner, the delivery management server 140 associates and manages the ID and version of the application, the hash value of the common key, the information for identifying the image forming device, and the destination information.
Thereafter, the delivery management server 140 determines the application to be updated and the image forming device 130 according to an instruction from an operating user, and specifies the destination information associated with the application and the image forming device 130. In step S240, the delivery management server 140 transmits the application ID and the destination information to the license management server 110.
In step S250, the license management server 110 transmits, to the delivery management server 140, a list of updatable versions which may vary according to the destination information based on the transmitted application ID and destination information.
In step S260, the delivery management server 140 transmits, to the license management server 110, information indicative of the update version of the application. Then in step S270, the license management server 110 transmits delivery information on the update version of the application to the delivery management server 140.
Then in step S280, the image forming device obtains the delivery information from the delivery management server 140 at any timing. The delivery information includes information indicative of a delivery source of the updated application. Then the image forming device installs the updated application, and in step S290, notifies the delivery management server of the result of installation. In this manner, in the present embodiment, it becomes possible to deliver the updated application only to a certain destination by using the destination information. Detailed explanation will be made below on processing by the image forming device and the server.
<Process Flow for the Image Forming Device>
Next, with reference to
In the image forming device 130 of the present invention, processing shown in
In a case where the image forming device is activated to start the processing, the app & key information transmitting unit 131 starts the processing in step S301. As described later, in the processing in step S301, the processing in S210 of
Next, in step S302, the delivery setting checking unit 132 inquires of the delivery management server 140 as to whether the delivery setting of the own image forming device 130 is made. If the result of the delivery setting checking unit 132 inquiring of the delivery management server indicates that no delivery setting is made in step S303, the process returns to step S302, and the processing in step S302 is repeated at certain intervals. If the result of the inquiry indicates that the delivery setting is made in step S303, the delivery information receiving unit 133 receives and obtains delivery information from the delivery management server 140 in step S304. The processing for obtaining the delivery information corresponds to the processing in step S280 of
Next, the details of the processing will be explained.
<Process Flow for the App & Key Information Transmitting Unit of the Image Forming Device>
In step S401, the app & key information transmitting unit 131 determines whether the delivery management server 140 has transmitted application configuration information to the delivery management server 140. The application configuration information includes, for example, application identification information (ID) for identifying the application installed on the image forming device 130, information indicative of the version of the application, and the hash value of the common key for the application. In a case where a plurality of applications are installed, information on the respective applications is collectively referred to as application configuration information. If the application configuration information has already been transmitted, the process ends. If the application configuration information has not been transmitted, the process proceeds to step S402.
In step S402, the app & key information transmitting unit 131 determines whether the application is installed on the own image forming device 130. If no application is installed, the process ends.
If the application is installed, in step S403, the app & key information transmitting unit 131 obtains information (hereinafter referred to as application information) indicative of the ID and version of the application managed in the own image forming device 130 and the corresponding common key. In the image forming device 130, the app & key information transmitting unit 131 manages information as shown in Table 1 as information on the installed application.
In Table 1, AppID is an identifier for uniquely identifying the application in the image forming device 130, Version is the version of the application, and Common Key is information on the common key used to encrypt the application. The image forming device 130 decrypts the encrypted application by using the managed common key and executes the application. In the present embodiment, the processing is performed by using information on the managed application without using information included in the application.
Next, in step S404, the app & key information transmitting unit 131 generates each hash value from the common key each obtained in step S403. Next, in step S405, the app & key information transmitting unit 131 transmits, to the delivery management server 140, the hash values of the common keys generated in step S404 and the corresponding application information, and the process ends. The image forming device 130 transmits information as shown in Table 2, for example to the delivery management server 140. Incidentally, DS# is device identification information for uniquely identifying the image forming device 130 which transmits the information. As shown in Table 2, the app & key information transmitting unit 131 transmits the application configuration information and the information for uniquely specifying the image forming device to the delivery management server 140. Incidentally, in a case where the delivery management server 140 can identify the image forming device based on information used at the time of transmission such as the IP address of the transmission source, the information (ID) for identifying the image forming device may not be transmitted to the delivery management server 140 as the information. In step S405, transmission of the information corresponds to S210 in
<Process Flow for the License File Obtaining Unit of the Image Forming Device>
In step S501, the license file obtaining unit 134 obtains the delivery information received by the delivery information receiving unit 133 from the delivery management server 140. In step S502, the license file obtaining unit 134 determines whether an application identical to the one specified by the AppID included in the obtained delivery information is installed on the own image forming device 130. If it is determined that the application is installed, the process proceeds to step S503, and the license file obtaining unit 134 generates a disabling license file for the corresponding application. The disabling license file is a license file which is generated in a case where an installed license file is uninstalled. The disabling license file includes a common key for decrypting an encrypted application, and can be used to decrypt a different version of an application managed by the license management server 110. Next, in step S504, the license file obtaining unit 134 uninstalls an application corresponding to the disabling license file generated in step S503. In the meantime, if it is determined in step S502 that the corresponding application is not installed, the license file obtaining unit 134 ends the process as an update error in step S505.
<Process Flow for the Installing Unit of the Image Forming Device>
In step S601, the installing unit 135 determines whether or not the result of the processing by the license file obtaining unit 134 is an update error. If the result is an update error, in step S602, the installing unit 135 notifies the delivery management server 140 of the error and ends the process.
Meanwhile, if the result is not an update error, in step S603, the installing unit 135 downloads the corresponding application from the URI included in the delivery information received by the delivery information receiving unit 133. Then in step S604, the installing unit 135 installs the application downloaded in step S603. Next, in step S605, the installing unit 135 installs the disabling license file generated by the license file obtaining unit 134. In step S606, the installing unit 135 notifies the delivery management server 140 of completion of installation, and ends the process. This processing corresponds to the processing in S290 of
The above is an explanation of the process flow for the image forming device. Next, explanation will be made below on a process flow for the delivery management server.
<Process Flow for the App & Key Information Managing Unit of the Delivery Management Server>
In step S701, the app & key information managing unit 143 notifies the license management server 110 of the AppID and the hash value of the common key which are received from the app & key information transmitting unit 131 of the image forming device 130. This processing corresponds to the processing in S220 in response to S210 of
Table 4 illustrates information managed by the app & key information managing unit 143. The app & key information managing unit 143 manages the destination information for each application received from the license management server 110 in addition to the information transmitted from the app & key information transmitting unit 131 of the image forming device 130.
<Entire Process Flow for Delivery Setting of the Delivery Management Server>
Next, with reference to
The processing shown in
Table 5 shows examples of the user information managed by using the delivery information management database 144 of the delivery management server 140. The delivery information management database 144 is used to manage the destination information on the operating user as well as an ID/password for checking whether or not the operating user is right.
In step S901, the list generating unit 141 receives, from the operating user who has logged in, the designation of a tenant ID and information (an application ID) for specifying an application to be updated. A tenant is a client to whom the operating user provides the application. In a case where setting is made so that the application to be updated is delivered to a specific client, the operating user can designate the tenant by using the tenant ID. In the present embodiment, the tenant ID is associated with the image forming device, and the image forming device to be updated can be specified by designating the tenant ID. In step S902, the list generating unit 141 specifies the image forming device 130 corresponding to the information designated in step S901. More specifically, the image forming device which is subject to updating processing is specified.
Next, in step S903, a variable i is initialized with 0. Processing in subsequent steps S904 to S908 is repeated the number of times which is equal to the number of the image forming devices specified in step S902. In step S904, the list generating unit 141 determines whether the variable i is smaller than the number of the image forming devices specified in step S902. In a case where the variable i is smaller than the number of the image forming devices specified in step S902, the process proceeds to step S905. In step S905, the list generating unit 141 specifies the destination information on the application corresponding to the i-th image forming device by using the app & key information managing unit 143. As explained above with respect to Table 4, the app & key information managing unit 143 associates and manages the ID and version of the application, the hash value of the common key, the identification information of the image forming device, and the destination information. Accordingly, it is possible to specify the destination information on the application corresponding to the i-th image forming device based on the application ID whose designation is received in step S901 and the identification information of the i-th image forming device.
Next, in step S906, the list generating unit 141 determines whether the destination information on the i-th image forming device as specified in step S905 is identical to the destination information on the operating user obtained in step S803 of
In step S906, if it is determined that the destination information on the i-th image forming device is identical to the destination information on the operating user, the process proceeds to step S908 without going through step S907. In step S908, the list generating unit 141 increments the variable i, and the process proceeds to step S904.
Then in step S904, if it is determined that the variable i is not smaller than the number of the image forming devices specified in step S902, the list generating unit 141 obtains a list corresponding to a delivery condition specified by the operating user in step S909.
<Example of a User Interface Screen in the Delivery Management Server>
A search result screen 1051 displays information 1052 for uniquely specifying the image forming device, information 1053 indicative of the version of the application, and destination information 1054. The search result screen 1051 displays, as the list, information for the number of the image forming devices specified as a result of search (1055-1057). Further, the search result screen 1051 includes a delivery setting button 1058 for selecting the image forming device 130 which is subject to the delivery setting and executing the delivery setting and a Cancel button 1059 for cancelling the delivery setting.
In the example of
Next, in a case where the operating user presses the delivery setting button 1058 in
According to the operating user's instruction given via the screen shown in
<Process Flow for the Delivery Information Setting Unit of the Delivery Management Server>
In step S1301, the delivery information setting unit 142 firstly notifies the license management server 110 of the AppID, version, and destination information of the application which is set to be delivered. More specifically, the delivery information setting unit 142 notifies the license management server 110 of the application ID designated by the operating user in the screen shown in
In response to this notification, the license management server 110 transmits a list of updatable applications to the delivery management server 140. This processing corresponds to the processing in S250 of
In step S1302, the delivery information setting unit 142 displays the list of applications received from the license management server 110 in the application version designation screen shown in
In step S1303, the delivery information setting unit 142 determines the update version of the application according to the operating user's instruction. In step S1304, the delivery information setting unit 142 notifies the license management server 110 of a registration number corresponding to the version of the application determined in step S1303. The registration number is information for uniquely specifying the application on the license management server 110, and is included in the list of applications obtained from the license management server 110 in step S1302. Table 7 shows information on the list of applications received from the license management server 110 in a case where in step S1301, it is specified that the AppID is “ABC1234” and that the destination information is “JP.”
Table 7 corresponds to matters displayed in the list box 1104 for selecting the update version in
In step S1304, in response to notifying the license management server 110 of the registration number, the application delivery information transmitting unit 113 of the license management server 110 transmits delivery information for downloading the application to the delivery management server 140. This processing corresponds to the processing in step S270 of
In step S1305, the delivery information setting unit 142 obtains the application delivery information from the license management server 110. Then in step S1306, the delivery information setting unit 142 registers the delivery information obtained in step S1305 in the delivery information management database 144, and the process ends. Table 8 shows examples of the delivery information managed by the delivery information management database 144.
Table 8 shows a state in which the version determined in step S1303, the delivery information (URI) obtained in step S1306, a delivery date and time the designated by the operating user through the screen displayed in
<Process Flow for the License Management Server>
Next, explanation will be made on the process flow for the license management server 110. Firstly, explanation will be made on processing by the destination information extracting unit 111 of the license management server 110. As stated above, the destination information extracting unit 111 extracts the destination information based on the application ID and the hash value of the common key transmitted from the delivery management server 140, and transmits the extracted destination information to the delivery management server 140.
<Process Flow for the Destination Information Extracting Unit of the License Management Server>
Next, in step S1402, the destination information extracting unit 111 obtains a common key corresponding to the AppID received in step S1401 out of common keys managed by the license management server 110. Next, in step S1403, a variable i is initialized with zero.
In next step S1404, the destination information extracting unit 111 determines whether the variable i is smaller than the number of the common keys obtained in step S1402. If the variable i is smaller than the number of the common keys obtained in step S1402, the process proceeds to step S1405, and if the variable i is not smaller than the number of the common keys obtained in step S1402, the process proceeds to step S1409.
In step S1405, the destination information extracting unit 111 generates the hash value of the i-th common key. Then, in step S1406, the destination information extracting unit 111 determines whether the hash value of the common key generated in step S1405 is equal to the hash value of the common key received in step S1401. In a case where these hash values are equal to each other, the process proceeds to step S1407. In step S1407, the destination information extracting unit 111 extracts the destination information associated with the i-th common key as the destination information corresponding to the AppID and the hash value of the common key received in step S1401, and the process proceeds to step S1410. In the meantime, in a case where the above hash values are not equal to each other, in step S1408, the destination information extracting unit 111 increments the variable i, and the process proceeds to step S1404. In a case where none of the hash values of all the common keys managed by the license management server 110 is equal to the hash value of the common key received in step S1401, it is determined that the destination information is not extracted, and the process proceeds to step S1410.
In step S1410, the destination information extracting unit 111 transmits the result obtained in step S1407 or step S1409 to the delivery management server 140. More specifically, in a case where the destination information can be extracted in step S1407, the destination information extracting unit 111 transmits, to the delivery management server 140, the destination information corresponding to the AppID and the hash value of the common key transmitted from the delivery management server 140. This processing corresponds to the processing in S230 of
Table 9 shows examples of combinations of the hash value of the common key and the destination information managed by the license management server 110.
The license management server 110 manages the common keys uniquely identified in combination with the AppID and the destination information. Accordingly, it is possible to specify the destination information corresponding to the hash value of the common key and the AppID received from the delivery management server 140 by using a combination of the hash value of the common key and the AppID.
Next, explanation will be made on the processing by the related application information managing unit 112 of the license management server 110. The related application information managing unit 112 receives the AppID, version, and destination information transmitted from the delivery management server 140 as stated above, and transmits a version-upgrade list of updatable applications to the delivery management server 140.
<Process Flow for the Related Application Information Managing Unit of the License Management Server>
Next, in step S1502, the related application information managing unit 112 specifies the registration number of the corresponding application managed by the license management server 110 based on the AppID, Version, and destination information received in step S1501. Next, in step S1503, the related application information managing unit 112 obtains the upgrade list set for the application whose registration number is specified in step S1502. Next, in step S1504, the related application information managing unit 112 determines whether the upgrade list exists, and if the list exists, transmits the list of corresponding applications to the delivery management server 140 in step S1505. If the list does not exist, the process ends.
The application in which the registration number is “2000” is associated with an application 1652 in which the version is “1.1” and the registration number is “2001,” an application 1653 in which the version is “1.2” and the registration number is “2002,” and an application 1654 in which the version is “1.3” and the registration number is “2003.” In the meantime, it is shown that the application in which the registration number is “2000” is not associated with an application 1655 in which the version is “2.0” and the registration number is “2004.”
Even in a case where the AppID maintains the uniqueness of the applications in the image forming device 130, the applications having the different destination information may exist as shown in
In the first embodiment, explanation has been made on the example in which the destination information is specified and the application update setting suitable for the applications installed on the image forming device is performed by using the list of updatable applications corresponding to the specified destination information. In the second embodiment, explanation will be made on an example in which the application installed on the image forming device is updated to an application having destination corresponding to the operating user performing the delivery setting.
The delivery setting registration screen 1751 includes setting 1752 performing delivery registration for the device ID “AAA00502” on which the application having “EN” destination is installed. Further, the delivery setting registration screen 1751 displays a message 1753 in a case where the application whose destination is different from that of the operating user is updated to the application whose destination is identical to that of the operating user. In the example of
<Process Flow for the Delivery Setting of the Delivery Management Server>
In a case where the delivery information corresponding to the destination information on the operating user is obtained in step S1305, the process proceeds to step S1801. In step 1801, the delivery information setting unit 142 determines whether there is an image forming device whose destination is to be changed. More specifically, it is determined whether out of image forming devices selected in
Next, in step S1802, the delivery information setting unit 142 notifies the license management server 110 of identification information (DS#) for uniquely specifying the image forming device whose destination is to be changed and the registration number of the application. In the license management server 110, the license information issuing unit 114 generates a license file corresponding to the application and the image forming device. In step S1803, the delivery information setting unit 142 receives the license file from the license management server 110.
Thereafter, in step S1804, the delivery information setting unit 142 registers the delivery information in the delivery information management database 144. The registered delivery information is the delivery information obtained in step S1305, and further, in a case where the license file is received in step S1803, the delivery information including the license file is registered.
<Process Flow for the License Management Server>
<Process Flow for the Image Forming Device>
Next, explanation will be made on processing relating to installation of the application on the image forming device.
In the present embodiment, the delivery information obtained from the delivery management server is, for example, information shown in Table 10. The image forming device can obtain, as the information for specifying the application, the application name and the URI for downloading the application as well as the AppID/Version. Further, some application may include the license file (LF).
In a case where the application whose AppID is identical to the AppID obtained in step S502 is installed on the own image forming device 130, the process proceeds to step S2001. In step S2001, the license file obtaining unit 134 determines whether the license file is included in the delivery information obtained in step S501. In a case where the license file is included, the process proceeds to step S504, and the target application is uninstalled. More specifically, since the license file is included, the target application is uninstalled without generating the disabling license file. In the case of Table 10, since the license file is included in the application whose AppID is “ABC1234,” the disabling license file is not generated for the application whose AppID is “ABC1234,” and the disabling license file is generated only for the application whose AppID is “CDE5678.”
In the present embodiment, as shown in
According to the above-described embodiments, it is possible to deliver the updated application to the appropriate destination.
Embodiment(s) of the present invention can also be realized by a computer of a system or apparatus that reads out and executes computer executable instructions (e.g., one or more programs) recorded on a storage medium (which may also be referred to more fully as a ‘non-transitory computer-readable storage medium’) to perform the functions of one or more of the above-described embodiment(s) and/or that includes one or more circuits (e.g., application specific integrated circuit (ASIC)) for performing the functions of one or more of the above-described embodiment(s), and by a method performed by the computer of the system or apparatus by, for example, reading out and executing the computer executable instructions from the storage medium to perform the functions of one or more of the above-described embodiment(s) and/or controlling the one or more circuits to perform the functions of one or more of the above-described embodiment(s). The computer may comprise one or more processors (e.g., central processing unit (CPU), micro processing unit (MPU)) and may include a network of separate computers or separate processors to read out and execute the computer executable instructions. The computer executable instructions may be provided to the computer, for example, from a network or the storage medium. The storage medium may include, for example, one or more of a hard disk, a random-access memory (RAM), a read only memory (ROM), a storage of distributed computing systems, an optical disk (such as a compact disc (CD), digital versatile disc (DVD), or Blu-ray Disc (BD)™), a flash memory device, a memory card, and the like.
While the present invention has been described with reference to exemplary embodiments, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions.
This application claims the benefit of Japanese Patent Application No. 2015-009740, filed Jan. 21, 2015, which is hereby incorporated by reference herein in its entirety.
| Number | Date | Country | Kind |
|---|---|---|---|
| JP2015-009740 | Jan 2015 | JP | national |
| Number | Name | Date | Kind |
|---|---|---|---|
| 7080043 | Chase, Jr. | Jul 2006 | B2 |
| 7814023 | Rao et al. | Oct 2010 | B1 |
| 7865445 | Maeda | Jan 2011 | B2 |
| 8321949 | Green | Nov 2012 | B1 |
| 8395797 | Anno | Mar 2013 | B2 |
| 8539595 | Tsuboi | Sep 2013 | B2 |
| 8831995 | Holler | Sep 2014 | B2 |
| 8856318 | Nakamoto | Oct 2014 | B2 |
| 8868692 | Khanna | Oct 2014 | B1 |
| 8966472 | Hayami | Feb 2015 | B2 |
| 9699195 | Ito | Jul 2017 | B2 |
| 10417432 | Mahaffey | Sep 2019 | B2 |
| 20070064268 | Hino | Mar 2007 | A1 |
| 20080027742 | Maeda | Jan 2008 | A1 |
| 20080178298 | Arai | Jul 2008 | A1 |
| 20090228982 | Kobayashi | Sep 2009 | A1 |
| 20090310179 | Tamura | Dec 2009 | A1 |
| 20100058468 | Green | Mar 2010 | A1 |
| 20100242117 | Tsuboi | Sep 2010 | A1 |
| 20100293619 | Hayami | Nov 2010 | A1 |
| 20110276501 | Sako et al. | Nov 2011 | A1 |
| 20120210442 | Ito | Aug 2012 | A1 |
| 20120257240 | Yuki | Oct 2012 | A1 |
| 20130019233 | Pardehpoosh et al. | Jan 2013 | A1 |
| 20130019234 | Pardehpoosh et al. | Jan 2013 | A1 |
| 20130019237 | Pardehpoosh | Jan 2013 | A1 |
| 20130036160 | Sasao | Feb 2013 | A1 |
| 20130275553 | Shilo | Oct 2013 | A1 |
| 20140082608 | Hayami | Mar 2014 | A1 |
| 20140258644 | Stark | Sep 2014 | A1 |
| 20140344846 | Yamamura | Nov 2014 | A1 |
| 20150310354 | Mahalingam | Oct 2015 | A1 |
| 20150317151 | Falcy | Nov 2015 | A1 |
| 20160099963 | Mahaffey | Apr 2016 | A1 |
| 20160210709 | Uchida | Jul 2016 | A1 |
| 20180059999 | Kawakami | Mar 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 1449527 | Oct 2003 | CN |
| 101114329 | Jan 2008 | CN |
| 101887377 | Nov 2010 | CN |
| 102308301 | Jan 2012 | CN |
| 102667790 | Sep 2012 | CN |
| 102859529 | Jan 2013 | CN |
| 103207793 | Jul 2013 | CN |
| 103685824 | Mar 2014 | CN |
| 104662864 | May 2015 | CN |
| 2005-215945 | Aug 2005 | JP |
| 2010-211469 | Sep 2010 | JP |
| 5182445 | Apr 2013 | JP |
| 2014106690 | Jun 2014 | JP |
| WO-2009108471 | Sep 2009 | WO |
| 2010092655 | Aug 2010 | WO |
| WO-2010092655 | Aug 2010 | WO |
| Entry |
|---|
| Nima Zahadat et al. BYOD security engineering: A framework and its analysis, Computers & Security, vol. 55, 2015, pp. 81-99, www.sciencedirect.com/science/article/pii/S0167404815000978 (Year: 2015). |
| Mar. 16, 2016 European Search Report in European Patent Appln. No. 15202286.9. |
| Mar. 22, 2019 Chinese Official Action in Chinese Patent Appln. No. 201610041816.8. |
| Jul. 23, 2019 Chinese Official Action in Chinese Patent Appln. No. 201610041816.8. |
| Dec. 11, 2019 Chinese Official Action in Chinese Patent Appln. No. 201610041816.8. |
| Number | Date | Country | |
|---|---|---|---|
| 20160210709 A1 | Jul 2016 | US |
