CN103685192A - Method and device for limiting calling launched by third-party application - Google Patents
Method and device for limiting calling launched by third-party application Download PDFInfo
- Publication number
- CN103685192A CN103685192A CN201210348238.4A CN201210348238A CN103685192A CN 103685192 A CN103685192 A CN 103685192A CN 201210348238 A CN201210348238 A CN 201210348238A CN 103685192 A CN103685192 A CN 103685192A
- Authority
- CN
- China
- Prior art keywords
- party
- current
- application
- identity characteristic
- calling
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The invention provides a method and a device for limiting the calling launched by third-party application. The method for limiting the calling launched by the third-party application comprises the steps that a server module pre-acquires an identifier library relevant to various types of third-party application, wherein each identifier in the identifier library represents the unique third-party application; a client module acquires an identity feature of the current third-party application when receiving a calling request launched by the current third-party application and sends the identity feature of the current third-party application to the server module, wherein the identity feature of the current third-party application comprises the unique identifier corresponding to the current third-party application; the server module verifies the received identity feature of the current third-party application according to the identifier library and responds to the calling of the current third-party application according to a verifying result. Due to the mode, the method disclosed by the invention has the advantage that the safety of the application during calling can be improved.
Description
[technical field]
The present invention relates to Technology On Data Encryption, particularly a kind of third party is applied to method and the device that calling of initiation limited.
[background technology]
Along with the development of software engineering, the software application that realizes carrier as function also becomes and becomes increasingly complex.The realization of the function of an application, probably relies on the service that other application provide, and for example, Voice Navigation application, depends on the service that speech recognition application provides.During existing software function realizes, the pattern of mutually calling between application, is conducive to code multiplexing, saves social resources, but also may introduce safety problem.
For example, in prior art, one is applied in while being distributed to other application uses, can generate in advance one and authorize password, as long as any application can provide this to authorize password, just can call successfully, for example apply A and be distributed to application B use, and providing key to application B, application B relies on this key can successfully call application A.But, if key is revealed, for example, apply C and also used this key, apply C and also can successfully call application A.Obviously, above-mentioned application call mode, cannot guarantee to apply the safety of A, if certain malicious application is called application A with correct key, and in invoked procedure, attacks A, the paralysis that likely causes applying A.
[summary of the invention]
Technical problem to be solved by this invention is to provide a kind ofly applies to third party the method that calling of initiation limited, to improve the fail safe of application when called.
The present invention is that technical scheme that technical solution problem adopts is to provide and a kind of third party is applied to the method that calling of initiation limited, it is characterized in that, described method comprises: server module obtains in advance to various third parties and applies relevant home banking, and in wherein said home banking, each sign represents unique third party's application; Client modules is when receiving current third party and apply the call request of initiation, obtain the identity characteristic of current third party's application, and the identity characteristic of current third party's application is sent to described server module, the identity characteristic that wherein current third party applies comprises with current third party applies corresponding unique identification; Described server module utilizes described home banking to verify the identity characteristic of the current third party's application receiving, and according to the result, calling of current third party's application is responded.
The preferred embodiment one of according to the present invention, the step that described client modules obtains the identity characteristic of current third party's application comprises: by system interface, obtain current third party's application and be registered in sign in system as the identity characteristic of current third party's application.
The preferred embodiment one of according to the present invention, the step that described server module utilizes described home banking to verify the identity characteristic of the current third party's application receiving comprises: the identity characteristic of the current third party's application receiving and the sign in described home banking are compared, if comparison is passed through, confirm to be proved to be successful, otherwise confirm authentication failed.
The preferred embodiment one of according to the present invention, the step that described client modules obtains the identity characteristic of current third party's application comprises: obtain current third party and apply the timestamp while initiating call request, and, by system interface, obtain current third party application and be registered in the sign in system, and the identity characteristic using described timestamp and described sign as current third party's application.
The preferred embodiment one of according to the present invention, the step that described server module utilizes described home banking to verify the identity characteristic of the current third party's application receiving comprises: S1. compares the sign in the identity characteristic of the current third party's application receiving and the sign in described home banking, if comparison is passed through, perform step S2, otherwise determine authentication failed; S2. according to the timestamp in the identity characteristic of the current third party application receiving, determine calling frequency and whether meeting the requirements of current third party's application, if so, determine and be proved to be successful, otherwise determine authentication failed.
The preferred embodiment one of according to the present invention, described method further comprises: while determining authentication failed in described step S2, apply relevant identification record described in described server module correction in home banking to current third party.
The preferred embodiment one of according to the present invention, described server module comprises the step responding of calling of current third party application according to the result: when the result be successfully time, the result of called service is sent to client modules as the result responding of calling that current third party is applied; When the result is unsuccessfully time, the indication of denial of service is sent to described client modules as the result responding of calling to current third party's application.
The present invention also provides a kind of third party has been applied to the device that calling of initiation limited, comprise client modules and server module, it is characterized in that: described server module comprises: storehouse generation unit, for obtaining to various third parties and apply relevant home banking in advance, in wherein said home banking, each sign represents unique third party's application; Described client modules comprises: receiving element, for receiving current third party, apply the call request of initiation; Acquiring unit, while applying the call request of initiation for receiving current third party at described receiving element, obtains the identity characteristic of current third party's application, and the identity characteristic that wherein current third party applies comprises with current third party applies corresponding unique identification; Client communication unit, for being sent to described server module by the identity characteristic of current third party's application; Described server module also comprises: authentication unit, for utilizing described home banking to verify the identity characteristic of the current third party's application receiving; Response unit, responds calling of current third party's application for the result obtaining according to described authentication unit.
The preferred embodiment one of according to the present invention, the mode that described acquiring unit obtains the identity characteristic of current third party's application comprises: by system interface, obtain current third party's application and be registered in sign in system as the identity characteristic of current third party's application.
The preferred embodiment one of according to the present invention, the mode that described authentication unit is verified the identity characteristic of the current third party's application receiving comprises: the identity characteristic of the current third party's application receiving and the sign in described home banking are compared, if comparison is passed through, confirm to be proved to be successful, otherwise confirm authentication failed.
The preferred embodiment one of according to the present invention, the mode that described acquiring unit obtains the identity characteristic of current third party's application comprises: obtain current third party and apply the timestamp while initiating call request, and, by system interface, obtain current third party application and be registered in the sign in system, and the identity characteristic using described timestamp and described sign as current third party's application.
The preferred embodiment one of according to the present invention, described authentication unit comprises: sign authentication unit, for the sign of the identity characteristic of the current third party's application receiving and the sign in described home banking are compared, if comparison is passed through, trigger behavior authentication unit and carry out, otherwise determine authentication failed;
Behavior authentication unit, for determine calling frequency and whether meeting the requirements of current third party's application according to the timestamp of the identity characteristic of the current third party application receiving, if so, determines and is proved to be successful, otherwise determine authentication failed.
13, device according to claim 12, is characterized in that, described server module further comprises:
Amending unit, for when authentication failed is determined in described time verifying unit, revises in described home banking and applies relevant identification record to current third party.
14, device according to claim 8, it is characterized in that, described response unit comprises the mode responding of calling of current third party application according to the result: when the result be successfully time, the result of called service is sent to described client modules as the result responding of calling that current third party is applied; When the result is unsuccessfully time, the indication of denial of service is sent to described client modules as the result responding of calling to current third party's application.
As can be seen from the above technical solutions; the present invention is by when homophony application adjusts application to initiate call request to quilt; by client modules, obtain and comprise homophony application unique identification and be sent to server module at interior identity characteristic; and the identity characteristic receiving is verified according to the home banking obtaining in advance by server module, can realize being adjusted effective protection of application.While only having within homophony is applied in the scope of authority, can obtain by the service of adjusting application to provide, so the present invention has effectively improved fail safe when application is called.
[accompanying drawing explanation]
Fig. 1 applies the schematic flow sheet of the method that calling of initiation limit to third party in the present invention;
Fig. 2 applies the structural representation block diagram of the embodiment mono-of the device that calling of initiation limit to third party in the present invention;
Fig. 3 applies the structural representation block diagram of the embodiment bis-of the device that calling of initiation limit to third party in the present invention.
[embodiment]
In order to make the object, technical solutions and advantages of the present invention clearer, below in conjunction with the drawings and specific embodiments, describe the present invention.
Please refer to Fig. 1, Fig. 1 applies the schematic flow sheet of the method that calling of initiation limit to third party in the present invention.As shown in Figure 1, the method comprises:
Step S101: server module obtains in advance to various third parties and applies relevant home banking.
Step S102: client modules, when receiving current third party and apply the call request of initiation, obtains the identity characteristic of current third party's application, and the identity characteristic of current third party's application is sent to server module.
Step S103: server module utilizes home banking to verify the identity characteristic of the current third party's application receiving, and according to the result, calling of current third party's application is responded.
Below above-mentioned steps is elaborated.
In the present invention, step S101 is lower execution online in advance, and step S102 and step S103 all carry out on line.
Under step S101 is online, obtain home banking, particularly, comprise the sign that each third party of receiving through examine applies, and this sign is saved to and in database, forms the home banking in the present invention.Each sign in home banking in the present invention all represents unique third party's application.
In the process of carrying out on line, the present invention has provided two embodiment that step S102 and step S103 cooperatively interact, and is specifically introduced respectively below.
Embodiment mono-:
The mode that in step S102, client modules obtains the identity characteristic of current third party application comprises: by system interface, obtain current third party's application and be registered in sign in system as the identity characteristic of current third party's application.
Corresponding with it, the mode that in step S103, server module utilizes home banking to verify the identity characteristic of the current third party's application receiving comprises:
The identity characteristic of the current third party's application receiving and the sign in home banking are compared, if comparison is passed through, confirm to be proved to be successful, otherwise confirm authentication failed.
Technical staff should be appreciated that, the use of any application all needs to depend on certain system, and an application when mounted, can be to the unique identification of system registry oneself, follow-uply just can use.In the present invention, the current third party who initiates to call applies, and does not need as prior art, transmits certain and by called, applies the mandate password providing in advance, but directly send call request to called application.In step S 102, client modules is when receiving the call request that current third party application sends, the interface that can provide by system sends request to system, requirement system is returned to the unique identification of current third party's application, and the identity characteristic using this sign as current third party's application.Afterwards, client modules can be sent to server module by the identity characteristic of current third party's application.
Server module, after receiving the identity characteristic of current third party's application, utilizes the home banking of setting up in advance, can verify the identity characteristic of current third party's application.Each sign in home banking has represented an application of having obtained the authorization in advance, therefore, if current third party application can illustrate that it is safe by checking, can provide service to this third party's application.
Embodiment bis-:
In the step S102 of the present embodiment, the mode that client modules obtains the identity characteristic of current third party's application specifically comprises: obtain current third party and apply the timestamp while initiating call request, and, by system interface, obtain current third party's application and be registered in the sign in system, and this timestamp and this are identified as the identity characteristic of current third party's application.
Corresponding with it, in step S103, the mode that server module utilizes home banking to verify the identity characteristic of the current third party's application receiving specifically comprises:
Step S1031: the sign in the identity characteristic of the current third party's application receiving and the sign in home banking are compared, if comparison is passed through, perform step S1032, otherwise determine authentication failed
Step S1032: determine calling frequency and whether meeting the requirements of current third party's application according to the timestamp in the identity characteristic of the current third party application receiving, if so, determine and be proved to be successful, otherwise determine authentication failed.
In the present embodiment, in the identity characteristic of current third party's application, comprise two factors, one is the unique identification of the current third party application that gets from system, another is that current third party applies the system parameters while initiating call request, timestamp when system parameters is call request initiation in this example.When server module receives after the identity characteristic of current third party's application, first adopt with embodiment mono-in similar mode, utilize home banking to verify the sign in the identity characteristic of current third party's application, if checking is not passed through, illustrate that being identified at of current third party application do not exist respective record in home banking, directly confirm authentication failed, otherwise, recycle timestamp in current third party application and determine calling frequency and whether meeting the requirements of current third party's application, only in the situation that the frequency of calling of current third party application meet the demands, just can be by checking.Current third party application call frequency, refer to a period of time till current time the average call number of current third party's application.Timestamp analysis when this can occur by calling of the current third party application to getting in a period of time is at every turn determined.For example current third party to apply the front timestamp calling for twice be respectively 20 minutes 30 seconds and 20 minutes and 31 seconds, and the current timestamp calling is 20 minutes and 33 seconds, can judge that current third party applies in 4 seconds has initiated call request three times, average per second calling 3/4 time, if only allowed, call number per second is the highest can not surpass 0.5, illustrates that calling of current third party's application is undesirable.
Further, in the present embodiment, if current third party application to call frequency undesirable, server module can also be revised in home banking and apply relevant identification record to current third party.For example, will be in home banking apply relevant sign to current third party and delete, like this upper once when call request is sent in current third party's application, the checking of step S1031 just can not passed through.
Corresponding with the present embodiment, in step S101 when obtaining home banking, can not need manually the sign of each third party's application to be examined in advance, but apply being registered in home banking oneself in advance by each third party, like this, first step S1031 in the present embodiment can guarantee that only having the third party who registered to apply just can get the service of calling, and by step S1032, the undesirable third party's application of the behavior of calling can also be filtered out from home banking, thereby when call request is sent in upper once this third party application, stop in time to this third party's application service is provided.
In this example, the system parameters that the current third party who obtains applies while initiating call request is timestamp, but the invention is not restricted to this, for example system parameters can also be the network address, type of hardware etc., corresponding with it, in step S1032, can determine whether the behavior of calling of current third party's application exists extremely according to system parameters, if there is extremely authentication failed.
No matter be in above-described embodiment one or embodiment bis-, at client modules, the identity characteristic of current third party's application is sent to before server module, can also be encrypted identity characteristic, further to guarantee data security, corresponding with it, server module, before the identity characteristic receiving is verified, can adopt with client modules, identity characteristic to be encrypted to corresponding manner of decryption and first identity characteristic to be decrypted.
In step S103 of the present invention, according to the result, the mode responding of calling of current third party application is specifically comprised: when the result be successfully time, the result of called service is sent to client modules as the result responding of calling that current third party is applied; When the result is unsuccessfully time, the indication of denial of service is sent to client modules as the result responding of calling to current third party's application.
By method of the present invention, can guarantee to be adjusted the safety of application, owing to being adjusted application to provide service need to expend server system resource to homophony application, adopt method of the present invention, can clearly be adjusted what the homophony application of the each service of application is, therefore can add up better resource allocation conditions, be conducive to follow-up different homophony application be classified, according to the configuration of dissimilar homophony optimizing application system resource.
Please refer to Fig. 2, Fig. 2 applies the structural representation block diagram of the embodiment mono-of the device that calling of initiation limit to third party in the present invention.As shown in Figure 2, this device comprises: client modules 201 and server module 301.Wherein client modules 201 comprises: receiving element 2011, acquiring unit 2012 and client communication unit 2013, server module 301 comprises: storehouse generation unit 3011, authentication unit 3012 and response unit 3013.
Wherein storehouse generation unit 3011, for obtaining in advance to various third parties, apply relevant home banking.
Particularly, storehouse generation unit 3011 receives the sign that each third party through examine applies, and this sign is saved to and in database, forms the home banking in the present invention.Each sign in home banking in the present invention all represents unique third party's application.
Receiving element 2011, applies the call request of initiation for receiving current third party.Acquiring unit 2012, while applying the call request of initiation for receiving current third party at receiving element 2011, obtains the identity characteristic of current third party's application.Client communication unit 2013, for being sent to server module by the identity characteristic of current third party's application.Authentication unit 3012, for utilizing home banking to verify the identity characteristic of the current third party's application receiving.Response unit 3013, responds calling of current third party's application for the result obtaining according to authentication unit 3012.
Particularly, the mode that acquiring unit 2012 obtains the identity characteristic of current third party application comprises: by system interface, obtain current third party's application and be registered in sign in system as the identity characteristic of current third party's application.Correspondingly, the mode that authentication unit 3012 utilizes home banking to verify the identity characteristic of the current third party's application receiving comprises: the identity characteristic of the current third party's application receiving and the sign in home banking are compared, if comparison is passed through, confirm to be proved to be successful, otherwise confirm authentication failed.
In the present invention, the current third party who initiates to call applies, and does not need as prior art, transmits certain and by called, applies the mandate password providing in advance, but directly send call request to called application.When receiving element 2011 receives the call request that current third party application sends, the interface that acquiring unit 2012 can provide by system sends request to system, requirement system is returned to the unique identification of current third party's application, and the identity characteristic using this sign as current third party's application.Afterwards, client communication unit 2013 can be sent to server module 301 by the identity characteristic of current third party's application.
Please refer to Fig. 3, Fig. 3 applies the structural representation block diagram of the embodiment bis-of the device that calling of initiation limit to third party in the present invention.In the present embodiment, the mode that acquiring unit 2012 obtains the identity characteristic of current third party's application comprises: obtain current third party and apply the timestamp while initiating call request, and, by system interface, obtain current third party application and be registered in the sign in system, and the identity characteristic using described timestamp and described sign as current third party's application.
In addition,, in the present embodiment, authentication unit 3012 comprises: sign authentication unit 3012_1 and behavior authentication unit 3012_2.Wherein identify authentication unit 3012_1, for the sign of the identity characteristic of the current third party's application receiving and the sign in home banking are compared, if comparison is passed through, trigger behavior authentication unit 3012_2 and carry out, otherwise determine authentication failed.Behavior authentication unit 3012_2, for determine calling frequency and whether meeting the requirements of current third party's application according to the timestamp of the identity characteristic of the current third party application receiving, if so, determines and is proved to be successful, otherwise determine authentication failed.
The foregoing is only preferred embodiment of the present invention, in order to limit the present invention, within the spirit and principles in the present invention not all, any modification of making, be equal to replacement, improvement etc., within all should being included in the scope of protection of the invention.
Claims (14)
1. third party is applied to the method that calling of initiation limited, it is characterized in that, described method comprises:
Server module obtains in advance to various third parties and applies relevant home banking, and in wherein said home banking, each sign represents unique third party's application;
Client modules is when receiving current third party and apply the call request of initiation, obtain the identity characteristic of current third party's application, and the identity characteristic of current third party's application is sent to described server module, the identity characteristic that wherein current third party applies comprises with current third party applies corresponding unique identification;
Described server module utilizes described home banking to verify the identity characteristic of the current third party's application receiving, and according to the result, calling of current third party's application is responded.
2. method according to claim 1, is characterized in that, the step that described client modules obtains the identity characteristic of current third party's application comprises:
By system interface, obtain current third party's application and be registered in the identity characteristic that the sign in system is applied as current third party.
3. method according to claim 2, is characterized in that, the step that described server module utilizes described home banking to verify the identity characteristic of the current third party's application receiving comprises:
The identity characteristic of the current third party's application receiving and the sign in described home banking are compared, if comparison is passed through, confirm to be proved to be successful, otherwise confirm authentication failed.
4. method according to claim 1, is characterized in that, the step that described client modules obtains the identity characteristic of current third party's application comprises:
Obtain current third party and apply the timestamp while initiating call request, and, by system interface, obtain current third party's application and be registered in the sign in system, and the identity characteristic using described timestamp and described sign as current third party's application.
5. method according to claim 4, is characterized in that, the step that described server module utilizes described home banking to verify the identity characteristic of the current third party's application receiving comprises:
S1. the sign in the identity characteristic of the current third party's application receiving and the sign in described home banking are compared, if comparison is passed through, perform step S2, otherwise determine authentication failed;
S2. according to the timestamp in the identity characteristic of the current third party application receiving, determine calling frequency and whether meeting the requirements of current third party's application, if so, determine and be proved to be successful, otherwise determine authentication failed.
6. method according to claim 5, is characterized in that, described method further comprises:
While determining authentication failed in described step S2, in home banking, apply relevant identification record to current third party described in described server module correction.
7. method according to claim 1, is characterized in that, described server module comprises the step responding of calling of current third party's application according to the result:
When the result is successfully time, the result of called service is sent to client modules as the result responding of calling to current third party's application; When the result is unsuccessfully time, the indication of denial of service is sent to described client modules as the result responding of calling to current third party's application.
8. third party is applied to the device that calling of initiation limited, comprises client modules and server module, it is characterized in that:
Described server module comprises:
Storehouse generation unit, applies relevant home banking for obtaining in advance to various third parties, and in wherein said home banking, each sign represents unique third party's application;
Described client modules comprises:
Receiving element, applies the call request of initiation for receiving current third party;
Acquiring unit, while applying the call request of initiation for receiving current third party at described receiving element, obtains the identity characteristic of current third party's application, and the identity characteristic that wherein current third party applies comprises with current third party applies corresponding unique identification;
Client communication unit, for being sent to described server module by the identity characteristic of current third party's application;
Described server module also comprises:
Authentication unit, for utilizing described home banking to verify the identity characteristic of the current third party's application receiving;
Response unit, responds calling of current third party's application for the result obtaining according to described authentication unit.
9. device according to claim 8, is characterized in that, the mode that described acquiring unit obtains the identity characteristic of current third party's application comprises:
By system interface, obtain current third party's application and be registered in the identity characteristic that the sign in system is applied as current third party.
10. device according to claim 9, is characterized in that, the mode that described authentication unit is verified the identity characteristic of the current third party's application receiving comprises:
The identity characteristic of the current third party's application receiving and the sign in described home banking are compared, if comparison is passed through, confirm to be proved to be successful, otherwise confirm authentication failed.
11. devices according to claim 8, is characterized in that, the mode that described acquiring unit obtains the identity characteristic of current third party's application comprises:
Obtain current third party and apply the timestamp while initiating call request, and, by system interface, obtain current third party's application and be registered in the sign in system, and the identity characteristic using described timestamp and described sign as current third party's application.
12. devices according to claim 11, is characterized in that, described authentication unit comprises:
Sign authentication unit, for the sign of the identity characteristic of the current third party's application receiving and the sign in described home banking are compared, if comparison is passed through, triggers behavior authentication unit and carries out, otherwise determine authentication failed;
Behavior authentication unit, for determine calling frequency and whether meeting the requirements of current third party's application according to the timestamp of the identity characteristic of the current third party application receiving, if so, determines and is proved to be successful, otherwise determine authentication failed.
13. devices according to claim 12, is characterized in that, described server module further comprises:
Amending unit, for when authentication failed is determined in described time verifying unit, revises in described home banking and applies relevant identification record to current third party.
14. devices according to claim 8, is characterized in that, described response unit comprises the mode responding of calling of current third party's application according to the result:
When the result is successfully time, the result of called service is sent to described client modules as the result responding of calling to current third party's application; When the result is unsuccessfully time, the indication of denial of service is sent to described client modules as the result responding of calling to current third party's application.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210348238.4A CN103685192A (en) | 2012-09-18 | 2012-09-18 | Method and device for limiting calling launched by third-party application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210348238.4A CN103685192A (en) | 2012-09-18 | 2012-09-18 | Method and device for limiting calling launched by third-party application |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103685192A true CN103685192A (en) | 2014-03-26 |
Family
ID=50321518
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210348238.4A Pending CN103685192A (en) | 2012-09-18 | 2012-09-18 | Method and device for limiting calling launched by third-party application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103685192A (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103905201A (en) * | 2014-03-28 | 2014-07-02 | 北界创想（北京）软件有限公司 | Interaction method and device for master application and multiple slave applications |
| CN103957189A (en) * | 2014-03-28 | 2014-07-30 | 北界创想（北京）软件有限公司 | Application program interaction method and device |
| CN105187449A (en) * | 2015-09-30 | 2015-12-23 | 北京恒华伟业科技股份有限公司 | Interface calling method and device |
| CN105988789A (en) * | 2015-02-09 | 2016-10-05 | 腾讯科技（深圳）有限公司 | Third party application calling method and platform and terminal |
| WO2016177167A1 (en) * | 2015-07-08 | 2016-11-10 | 中兴通讯股份有限公司 | Control method for application feature rules and application feature server |
| CN106295310A (en) * | 2016-07-28 | 2017-01-04 | 乐视控股（北京）有限公司 | Third party's program SDK authentication processing method and device |
| CN109274699A (en) * | 2018-11-28 | 2019-01-25 | 北京锐安科技有限公司 | Method for authenticating, device, server and storage medium |
| US10574526B2 (en) | 2015-07-08 | 2020-02-25 | Xi'an Zhongxing New Software Co., Ltd. | Control method for application feature rules and application feature server |
| CN113760405A (en) * | 2021-01-29 | 2021-12-07 | 北京京东拓先科技有限公司 | Gateway interface signature checking method and device, storage medium and electronic equipment |
| CN113760405B (en) * | 2021-01-29 | 2024-05-17 | 北京京东拓先科技有限公司 | Signature verification method and device for gateway interface, storage medium and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090234713A1 (en) * | 2008-03-11 | 2009-09-17 | The Rubicon Project | Ad matching system and method thereof |
| CN102281311A (en) * | 2010-06-10 | 2011-12-14 | 阿里巴巴集团控股有限公司 | Method, system and device for implementing network service based on open application programming interface |
| CN102413464A (en) * | 2011-11-24 | 2012-04-11 | 杭州东信北邮信息技术有限公司 | GBA (General Bootstrapping Architecture)-based secret key negotiation system and method of telecommunication capability open platform |
| CN102457505A (en) * | 2010-10-28 | 2012-05-16 | 快乐购物有限责任公司 | Shopping website management method and platform |
-
2012
- 2012-09-18 CN CN201210348238.4A patent/CN103685192A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090234713A1 (en) * | 2008-03-11 | 2009-09-17 | The Rubicon Project | Ad matching system and method thereof |
| CN102281311A (en) * | 2010-06-10 | 2011-12-14 | 阿里巴巴集团控股有限公司 | Method, system and device for implementing network service based on open application programming interface |
| CN102457505A (en) * | 2010-10-28 | 2012-05-16 | 快乐购物有限责任公司 | Shopping website management method and platform |
| CN102413464A (en) * | 2011-11-24 | 2012-04-11 | 杭州东信北邮信息技术有限公司 | GBA (General Bootstrapping Architecture)-based secret key negotiation system and method of telecommunication capability open platform |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103957189B (en) * | 2014-03-28 | 2017-01-25 | 北界创想（北京）软件有限公司 | Application program interaction method and device |
| CN103957189A (en) * | 2014-03-28 | 2014-07-30 | 北界创想（北京）软件有限公司 | Application program interaction method and device |
| CN103905201B (en) * | 2014-03-28 | 2017-02-15 | 北界无限（北京）软件有限公司 | Interaction method and device for master application and multiple slave applications |
| CN103905201A (en) * | 2014-03-28 | 2014-07-02 | 北界创想（北京）软件有限公司 | Interaction method and device for master application and multiple slave applications |
| CN105988789A (en) * | 2015-02-09 | 2016-10-05 | 腾讯科技（深圳）有限公司 | Third party application calling method and platform and terminal |
| CN105988789B (en) * | 2015-02-09 | 2020-08-28 | 腾讯科技（深圳）有限公司 | Third-party application calling method, calling platform and terminal |
| WO2016177167A1 (en) * | 2015-07-08 | 2016-11-10 | 中兴通讯股份有限公司 | Control method for application feature rules and application feature server |
| US10574526B2 (en) | 2015-07-08 | 2020-02-25 | Xi'an Zhongxing New Software Co., Ltd. | Control method for application feature rules and application feature server |
| CN105187449A (en) * | 2015-09-30 | 2015-12-23 | 北京恒华伟业科技股份有限公司 | Interface calling method and device |
| CN105187449B (en) * | 2015-09-30 | 2018-10-02 | 北京恒华伟业科技股份有限公司 | A kind of interface call method and device |
| CN106295310A (en) * | 2016-07-28 | 2017-01-04 | 乐视控股（北京）有限公司 | Third party's program SDK authentication processing method and device |
| CN109274699A (en) * | 2018-11-28 | 2019-01-25 | 北京锐安科技有限公司 | Method for authenticating, device, server and storage medium |
| CN113760405A (en) * | 2021-01-29 | 2021-12-07 | 北京京东拓先科技有限公司 | Gateway interface signature checking method and device, storage medium and electronic equipment |
| CN113760405B (en) * | 2021-01-29 | 2024-05-17 | 北京京东拓先科技有限公司 | Signature verification method and device for gateway interface, storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103685192A (en) | Method and device for limiting calling launched by third-party application | |
| CN107135073B (en) | Interface calling method and device | |
| US11831642B2 (en) | Systems and methods for endpoint management | |
| CN108684041B (en) | System and method for login authentication | |
| CN112422532B (en) | Service communication method, system and device and electronic equipment | |
| CN106921663B (en) | Identity continuous authentication system and method based on intelligent terminal software/intelligent terminal | |
| EP3178221B1 (en) | Device identification in service authorization | |
| CN110365483B (en) | Cloud platform authentication method, client, middleware and system | |
| TWI632798B (en) | Server, mobile terminal, and network real-name authentication system and method | |
| CN105262774A (en) | Remote login method | |
| WO2014014793A1 (en) | Anti-cloning system and method | |
| CN106357694B (en) | Access request processing method and device | |
| CN113572728B (en) | Method, device, equipment and medium for authenticating Internet of things equipment | |
| CN105681259A (en) | Open authorization method and apparatus and open platform | |
| CN103391286A (en) | Full IP remote monitoring network system and safety authentication method | |
| CN103747076A (en) | Cloud platform access method and device | |
| CN113472790A (en) | Information transmission method based on HTTPS (hypertext transfer protocol secure protocol), client and server | |
| WO2023093500A1 (en) | Access verification method and apparatus | |
| CN113672897A (en) | Data communication method, device, electronic equipment and storage medium | |
| CN103906050A (en) | WPKI security monitoring and control method and system based on mobile terminal | |
| EP3738012B1 (en) | Asserting user, app, and device binding in an unmanaged mobile device | |
| CN106953873B (en) | Security management system for encrypted information of encryption equipment | |
| CN112422292B (en) | Network security protection method, system, equipment and storage medium | |
| WO2017219886A1 (en) | Simple network protocol authentication method and device | |
| KR102300021B1 (en) | Authentication method and telecommunication server using IP address and SMS |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140326 |