CN111143832A - Mobile terminal SDK (software development kit) suitable for multiple scenes and hybrid authorization method thereof - Google Patents
Mobile terminal SDK (software development kit) suitable for multiple scenes and hybrid authorization method thereof Download PDFInfo
- Publication number
- CN111143832A CN111143832A CN201911398700.XA CN201911398700A CN111143832A CN 111143832 A CN111143832 A CN 111143832A CN 201911398700 A CN201911398700 A CN 201911398700A CN 111143832 A CN111143832 A CN 111143832A
- Authority
- CN
- China
- Prior art keywords
- authorization
- authorization file
- file
- mobile terminal
- online
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/51—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephone Function (AREA)
Abstract
The invention discloses a mobile terminal SDK mixed authorization method applicable to multiple scenes, which comprises the steps of embedding an offline trial authorization file in a mobile terminal SDK when the mobile terminal SDK is issued; responding to an initialization request of a mobile terminal SDK, and performing an authorization request of the mobile terminal SDK, wherein the authorization request is realized by acquiring a currently existing authorization file from the mobile terminal SDK for judgment, requesting an online authorization file when the authorization file is an offline trial authorization file, updating the offline trial authorization file into an online authorization file when the request is successful, and performing authorization verification according to the online authorization file; when the request fails, performing authorization verification according to the off-line trial authorization file; and when the authorization file is an online authorization file, performing authorization verification according to the online authorization file. The invention also discloses a mobile terminal SDK suitable for multiple scenes. According to the scheme disclosed by the invention, local and online mixed authorization can be realized, the authorization process is simple to operate, and the development and maintenance cost is low.
Description
Technical Field
The invention relates to the technical field of application authorization, in particular to a mobile terminal SDK (secure digital Key) suitable for multiple scenes and a mixed authorization method thereof.
Background
In order to ensure that core technologies in an SDK (Software Development Kit) are protected and controlled by respective manufacturers, the core technologies are prevented from being lost outside and uncontrollable, and when a mobile terminal SDK is used on a device, an SDK manufacturer generally needs to perform authorization verification on the SDK provided by the SDK manufacturer. Currently, the common authorization verification methods are generally classified into online authorization and offline authorization. The online authorization is that the SDK requests an authorization server through a network before being used to verify the local equipment and the application information, if the verification is passed, an authorization file is usually issued, and then whether the authorization file is legal or not is repeatedly checked in the SDK using process. The off-line authorization is to manually copy the generated authorization file to the device in advance, check whether the file is legal or not in the process of using the SDK, and directly use the functional module of the SDK if the file is legal, so that the effect of using the SDK even under the condition of no network is achieved. However, since the online authorization method depends heavily on the state of the network, if the network condition is poor, authorization fails and the product function cannot be used, which affects the user experience. However, the offline authorization method depends heavily on the uniqueness of the device, in order to ensure that the device and the authorization file are uniquely matched, each device needs to output a specific authorization file separately and needs to be burned into the corresponding device, which is tedious in process and low in efficiency.
Disclosure of Invention
In order to solve the problems, the inventor conceives that authorization adaptation is carried out on the SDK so as to release dependence on equipment uniqueness during local offline authorization, preferentially tries an online authorization request before offline authorization, and updates a local offline trial authorization file into an online authorization file when the request is successful, so that automatic switching between a no-network scene and a network scene is realized, authorization flow is simplified, and development and maintenance costs are reduced.
According to a first aspect of the present invention, a mobile terminal SDK hybrid authorization method suitable for multiple scenarios is provided, which includes the following steps:
when the mobile terminal SDK is released, an offline trial authorization file is built in the mobile terminal SDK;
responding to an initialization request of the mobile terminal SDK, and performing an authorization request of the mobile terminal SDK, wherein the implementation comprises
Obtaining the currently existing authorization file from the SDK of the mobile terminal for judgment,
when the authorization file is an offline trial authorization file, requesting an online authorization file, when the request is successful, updating the built-in offline trial authorization file into an online authorization file, and performing authorization verification according to the online authorization file; when the request fails, carrying out authorization verification according to the built-in off-line trial authorization file;
and when the authorization file is an online authorization file, performing authorization verification according to the online authorization file.
According to a second aspect of the present invention, there is provided a mobile terminal SDK suitable for multiple scenarios, comprising:
the storage module is used for storing an authorization file, wherein the stored authorization file is a built-in off-line trial authorization file or an on-line authorization file;
an authorization verification module for responding to the initialization request of the mobile terminal SDK and making the request of the mobile terminal SDK authorization, which is realized by comprising
The first authorization unit is used for acquiring the currently stored authorization file from the storage module for judgment, and calling the second authorization unit for authorization verification when the authorization file is an off-line trial authorization file; when the authorization file is an online authorization file, authorization verification is carried out according to the online authorization file;
the second authorization unit is used for requesting an online authorization file, updating the built-in offline trial authorization file into the online authorization file when the request is successful, and performing authorization verification according to the online authorization file; and when the request fails, performing authorization verification according to the built-in offline trial authorization file.
According to a third aspect of the present invention, there is provided an electronic apparatus comprising: the system comprises at least one processor and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to perform the steps of the method.
According to a fourth aspect of the invention, a storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method.
According to the mobile terminal SDK online + trial offline mixed authorization scheme provided in this embodiment, offline authorization verification can be successfully performed under the condition of no network or weak network, and the use of an offline function is allowed. Meanwhile, in the scheme of the embodiment of the invention, the networking online authorization operation is tried during each offline trial authorization check, if the online authorization is successful, the local trial offline authorization file is automatically updated to be an online authorization file, and the file can be used in an offline or online mode; if the updating fails (due to the network), the local trial offline authorization file is continuously checked until the updating is the online authorization file, so that the scene switching is convenient. For developers, the authorization flow is simple to operate, authorization adaptation is completely completed by the SDK, and development and maintenance cost is low. More importantly, the scheme furthest protects the interests of technical providers, so that the two partners realize technical and commercial win-win.
Drawings
Fig. 1 is a flowchart of a method of a mobile terminal SDK hybrid authorization method for multiple scenarios according to an embodiment of the present invention;
fig. 2 is a flowchart of a method of a mobile SDK hybrid authorization method for multiple scenarios according to another embodiment of the present invention;
fig. 3 is a schematic block diagram of a mobile terminal SDK applicable to multiple scenarios according to an embodiment of the present invention;
fig. 4 is a schematic diagram of an electronic device according to an embodiment of the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
As used in this disclosure, "module," "device," "system," and the like are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, or software in execution. In particular, for example, an element may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. Also, an application or script running on a server, or a server, may be an element. One or more elements may be in a process and/or thread of execution and an element may be localized on one computer and/or distributed between two or more computers and may be operated by various computer-readable media. The elements may also communicate by way of local and/or remote processes based on a signal having one or more data packets, e.g., from a data packet interacting with another element in a local system, distributed system, and/or across a network in the internet with other systems by way of the signal.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The mobile terminal SDK hybrid authorization method applicable to multiple scenes in the embodiment of the invention can be applied to any terminal equipment loaded with the SDK to be authorized and verified, such as a computer, a smart phone, a tablet computer, a smart home and other terminal equipment, and the invention is not limited to this. The scheme provided by the invention can realize authorization adaptation based on SDK in an off-line scene, timely update of an on-line authorization file in the on-line scene, simple operation of an authorization flow, and reduction of development and maintenance cost, and realizes seamless joint of a non-network scene and a network scene through the combination of off-line authorization and on-line authorization, so that product functions can be used when the network is limited.
The present invention will be described in further detail with reference to the accompanying drawings.
Fig. 1 schematically shows a method flow of a mobile terminal SDK hybrid authorization method applicable to multiple scenarios according to an embodiment of the present invention, as shown in fig. 1, the method of this embodiment includes the following steps:
step S101: when the mobile terminal SDK is released, an offline trial authorization file is built in the mobile terminal SDK. The embodiment of the invention carries out local offline authorization verification by embedding the offline trial authorization file in the mobile terminal SDK, wherein the offline trial authorization file is stored in the mobile terminal SDK and can be added in the SDK when the SDK is issued. Preferably, the built-in offline trial authorization file may be set to a read-only property. Therefore, a user only needs to install the mobile terminal SDK on the equipment according to the installation process, the authorization file does not need to be recorded on the equipment, all equipment uses the same off-line trial authorization file in the mobile terminal SDK, the process is simple and efficient, each equipment does not need to produce the unique authorization file, unnecessary troubles in the processes of butt joint, production and debugging are reduced, manpower and material resources are reduced, and the link of performing unique authentication on the equipment is also reduced. For a technical provider, only one shared SDK needs to be provided, an offline trial authorization file is built in the SDK, the file is read only and cannot be accessed by a user, the file cannot be deleted or damaged even if the equipment is returned to factory or formatted, the equipment can be normally used without a network and after being formatted, safety and efficiency are achieved, and operation is simple.
Step S102: and responding to the initialization request of the mobile terminal SDK, and performing the authorization request of the mobile terminal SDK. When initializing the mobile terminal SDK, firstly, an authorization request is required to be carried out on the SDK, when the authorization verification is successful, the SDK can be successfully initialized to use the function, and when the authorization verification is failed, the SDK is initialized according to the condition. In particular, it may be implemented to include: firstly, when an initialization request is received, acquiring a currently existing authorization file from a mobile terminal SDK to determine a file type, the embodiment of the present invention embeds an offline trial authorization file in an initial stage, but updates an online authorization file when the mobile terminal SDK is used over a network, so that the locally existing authorization file may be a file of a previous online authorization request or may be a built-in offline authorization file, when the locally stored authorization file is acquired, the type of the authorization file needs to be determined, specifically, for example, whether a trail field is included to distinguish the online authorization file or the offline trial authorization file is specified, for example, a trail field is additionally disposed in the offline trial authorization file, so that when the current authorization file is determined to include the trail field, the offline trial authorization file is determined, and when the trail field is not included, determining the file as an online authorization file; when the currently stored authorization file is an offline trial authorization file, requesting the online authorization file, including performing online verification (verify) and registration (register), and when the verification and registration are successful (namely when the request is successful), pulling down and storing the online authorization file to the local from the server side, and deleting the built-in offline trial authorization file, namely updating the locally stored authorization file from the offline trial authorization file to the online authorization file, and performing authorization verification according to the online authorization file; when the request fails, the off-line trial authorization file is not updated, but authorization verification is carried out according to the built-in off-line trial authorization file; and when the current locally stored authorization file is judged to be the online authorization file, authorization verification is directly carried out according to the online authorization file. It should be noted that the verify and the register belong to the operation of the authorization service logic, the verify checks whether the product ID is legal at the server side, and the register applies for the online authorization file. And the online verification and registration are authorization verification requests initiated by the client SDK to the authorization server, if the server successfully issues the online authorization file to the local equipment, and if the server fails, an error is returned and the SDK performs error processing.
Illustratively, the offline trial authorization file includes a validity period and/or a product ID, and the authorization verification according to the built-in offline trial authorization file is implemented as follows: checking whether the authorization is valid authorization or not according to the validity period and the current use information in the offline trial authorization file; and/or checking whether the product ID in the off-line trial authorization file is valid authorization or not according to the product ID and the current product ID. The valid period in the offline trial authorization file can be a specific expiration date, such as 9-30-9 in 2020, or the number of allowed uses, such as 5 times, and can be set by user according to requirements. Correspondingly, when the validity period is verified, the used current use information can be the current date or the current use times, if the current use information is within the validity period, the verification is successful, otherwise, the verification fails. In addition, whether the product ID, namely the product ID in the application information is consistent or not can be verified, so that when the product ID is consistent, the authorization verification is judged to be successful, and when the product ID is inconsistent, the authorization verification is judged to be failed. And when the authorization verification is successful, carrying out initialization operation of the mobile terminal SDK, and when the authorization verification is failed, carrying out corresponding error prompt. Wherein, the product ID is applied by the user at the same time of applying for the SDK. The product ID applied from the server needs to be imported when the developer uses the SDK. When the SDK performs the authorization check, the incoming product ID and the product ID stored in the authorization file are checked for consistency to determine whether the product ID is legal (if the product ID is consistent, the product ID is considered legal). If it is not legitimate, indicating that the product ID was not generated by the server, the authorization may be deemed invalid.
Different from the offline trial authorization file, the online authorization file comprises a device ID, a product ID and a valid period, and the authorization verification according to the online authorization file comprises the verification of whether the authorization is valid or not according to the matching condition of the current device ID, the product ID and the current use information with the valid period, the device ID and the product ID in the online authorization file, and when the device ID, the product ID and the current use information are consistent with the device ID and the product ID in the online authorization file, the valid authorization is judged, namely the verification is successful, otherwise, the invalid authorization is judged, namely the verification is failed. When the authorization verification is successful, the mobile terminal SDK is initialized, and when the verification fails (for example, when the validity period is exceeded), the online authorization request is continued, so as to obtain a new online authorization file according to the limitation condition of the server (for example, according to the request frequency set by the server). The validity period and the product ID may be checked as described above, and the device ID is checked by obtaining the local device ID and comparing the local device ID with the device ID in the authorization file to determine that the local device ID is valid authorization if the local device ID is consistent with the device ID in the authorization file.
In a preferred embodiment, the offline trial authorization file is further configured with usage module limitation information, and when the offline trial authorization file is subjected to authorization verification and the offline trial authorization file passes authorization verification (i.e., when it is determined that authorization is valid), the available function module is started according to the usage module limitation information. Illustratively, it is assumed that there are ten module functions provided in the current SDK, but only three fixed module functions are allowed to be used by using the module restriction information setting in the offline trial authorization file (i.e. the function module listed in the authorization file is available, otherwise, disabled), then the other seven module functions are not used, and only after the online authorization file is updated, the other seven module functions are available. Therefore, intellectual property rights of technical output parties can be well protected.
In other embodiments, there may be a case where no authorization file is stored locally, that is, in the SDK (for example, only the online authorization is applied, but not the mixed authorization, or the built-in offline authorization file is forgotten to be added or is deleted by mistake), at this time, it is necessary to directly perform the online authorization request, so as to obtain the online authorization file from the server to be stored locally and perform authorization verification when the request is successful.
When the online authorization file is used for authorization verification, if the verification is successful, the login request operation of the server can be performed before initialization is performed, so that monitoring and keeping-alive are performed, and the statistics and monitoring of the service condition of the equipment are facilitated for the server.
Preferably, when an online authorization request is made, if a return code (response code) of the server is 200, it indicates that the request is successful, and acquires an authorization file; otherwise (i.e., return code is not 200) the request is considered to have failed.
Fig. 2 schematically shows a method flow of another embodiment of the present invention, and as shown in fig. 2, the method embodiment differs from the method embodiment shown in fig. 1 in that, before step S102, the method further includes:
step S100: before the mobile terminal SDK authorization request is carried out, the validity of the product application information corresponding to the mobile terminal SDK is verified in response to the mobile terminal SDK initialization request, and the mobile terminal SDK authorization request is carried out only when the product application information is verified to be legal. The validity of the product application information corresponding to the SDK is the premise and the basis for using the SDK, so when the authorization of the SDK is requested, the product application information is preferentially checked locally, and if the SDK application is not allowed by a technical provider, the SDK application is not allowed to be used any more. Specifically, the user applies for an application ID (apiKey) at the same time of applying for the SDK, and the apiKey represents a unique ID of an application (application). Meanwhile, the SDK of the server side and the SDK of the mobile side both have encryption and decryption algorithms (common algorithms such as MD5 and SHA-2) for generating the apiKey. When a developer uses an SDK (i.e., when an initialization request is made to the SDK), an apiKey applied from a server needs to be passed in. Before authorization, the SDK preferentially performs local decryption verification on the incoming apiKey, and judges whether the decrypted field is legal or not (the legal field is contained in an effective value range). If the apiKey is not generated by the server side in a legal way, the apiKey can be determined to be invalid, and meanwhile, the user using the SDK is informed of an error prompt, such as an interface callback mode, to the device application layer. If the external interface of the SDK is called after the failure, the 'unauthorized use and no use' can be prompted, and the function of the SDK cannot be used at the moment.
Fig. 3 schematically illustrates a mobile terminal SDK applicable to multiple scenarios according to an embodiment of the present invention, as shown in fig. 3, which includes:
the storage module 30 is used for storing an authorization file, wherein the stored authorization file is an offline trial authorization file or an online authorization file, the offline trial authorization file is embedded in the mobile terminal when the mobile terminal SDK is issued, and the offline authorization file is preferably set to be a read-only attribute;
and the authorization verification module 31 is configured to respond to the initialization request of the mobile terminal SDK, and perform an authorization request of the mobile terminal SDK.
As shown in FIG. 3, authorization verification module 31 may be implemented to include
The first authorization unit 31A is configured to acquire a currently stored authorization file from the storage module 30 for judgment, and when the authorization file is an offline trial authorization file, call the second authorization unit 31B for authorization verification; when the authorization file is an online authorization file, authorization verification is carried out according to the online authorization file;
the second authorization unit 31B is configured to request an online authorization file, update the offline trial authorization file into an online authorization file when the request is successful, and perform authorization verification according to the online authorization file; and when the request fails, performing authorization verification according to the off-line trial authorization file.
Illustratively, the offline trial authorization file includes a validity period and/or a product ID, and the online authorization file includes a device ID, a product ID and a validity period.
In a specific implementation, the authorization verification module 31 calls the mobile SDK30 to perform an initialization operation when the authorization verification is successful, and performs an error prompt when the authorization verification fails, such as whether the mobile SDK expires or not, whether the network is abnormal, and the like.
In addition, the specific implementation of each module and unit in the embodiment of the present invention may be described with reference to the foregoing method part, and the preferred implementation scheme mentioned in the above method part is also applicable to the mobile terminal SDK, which is not described herein again.
The embodiment of the invention adopts the scheme of online SDK + trial offline mixed authorization of the mobile terminal, can successfully carry out offline authorization verification under the condition of no network or weak network and allows the use of offline functions. And personalized verification characteristic customization is carried out in the offline authorization file, for example, application information such as limiting an offline trial function module and product ID is bound, so that for a user, partial SDK functions can be used through verification of the offline trial authorization file under the condition of real network switching or abnormity, and the condition that the product function is limited due to authorization failure is avoided. Meanwhile, in the scheme of the embodiment of the invention, the networking online authorization operation is tried during each offline trial authorization check, if the online authorization is successful, the local trial offline authorization file is automatically updated to be an online authorization file, and the file can be used in an offline or online mode; if the updating fails (due to the network), the local trial offline authorization file is continuously checked until the local trial offline authorization file is updated to the online authorization file, so that scene switching is facilitated. For developers, the authorization flow is simple to operate, the authorization adaptation is completely completed by the SDK, and the development and maintenance cost is low. More importantly, the scheme furthest protects the interests of technical providers, so that the two partners realize technical and commercial win-win.
In some embodiments, the present invention further provides a computer-readable storage medium, where one or more programs including execution instructions are stored in the storage medium, where the execution instructions can be read and executed by an electronic device (including but not limited to a computer, a server, or a network device, etc.) to perform the above-described mobile terminal SDK hybrid authorization method applicable to multiple scenarios according to the present invention.
In some embodiments, the present invention further provides a computer program product, where the computer program product includes a computer program stored on a non-volatile computer-readable storage medium, and the computer program includes program instructions, which, when executed by a computer, cause the computer to execute the above mobile terminal SDK hybrid authorization method applicable to multiple scenarios.
In some embodiments, an embodiment of the present invention further provides an electronic device, which includes: at least one processor, and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the mobile terminal SDK hybrid authorization method applicable to multiple scenarios.
In some embodiments, the present invention further provides a storage medium, on which a computer program is stored, where the computer program is capable of executing the above-mentioned mobile terminal SDK hybrid authorization method applicable to multiple scenarios when executed by a processor.
The mobile terminal SDK applicable to multiple scenarios in the embodiment of the present invention may be used to execute the mobile terminal SDK hybrid authorization method applicable to multiple scenarios in the embodiment of the present invention, and accordingly, the technical effect achieved by the mobile terminal SDK hybrid authorization method applicable to multiple scenarios in the embodiment of the present invention is achieved, and details are not repeated here. In the embodiment of the present invention, the relevant functional module may be implemented by a hardware processor (hardware processor).
Fig. 4 is a schematic hardware structure diagram of an electronic device for executing a mobile SDK hybrid authorization method applicable to multiple scenarios according to another embodiment of the present application, and as shown in fig. 4, the electronic device includes:
one or more processors 510 and memory 520, with one processor 510 being an example in fig. 4.
The apparatus for executing the mobile terminal SDK hybrid authorization method applicable to multiple scenarios may further include: an input device 530 and an output device 540.
The processor 510, the memory 520, the input device 530, and the output device 540 may be connected by a bus or other means, such as by a bus connection in fig. 4.
The memory 520, which is a non-volatile computer-readable storage medium, may be used to store a non-volatile software program, a non-volatile computer-executable program, and modules, such as program instructions/modules corresponding to the mobile terminal SDK hybrid authorization method applicable to multiple scenarios in this embodiment of the application. The processor 510 executes various functional applications and data processing of the server by running the nonvolatile software program, instructions and modules stored in the memory 520, that is, implements the mobile terminal SDK hybrid authorization method applicable to multiple scenarios in the above method embodiment.
The memory 520 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the mobile terminal SDK applicable to multiple scenes, and the like. Further, the memory 520 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, the memory 520 may optionally include a memory remotely located from the processor 510, and these remote memories may be connected to the mobile terminal SDK adapted for multi-scenarios via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 530 may receive input numeric or character information and generate signals related to user settings and function control of the mobile terminal SDK suitable for multiple scenes. The output device 540 may include a display device such as a display screen.
The one or more modules are stored in the memory 520, and when executed by the one or more processors 510, perform the mobile terminal SDK hybrid authorization method applicable to multiple scenarios in any of the above method embodiments.
The product can execute the method provided by the embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the methods provided in the embodiments of the present application.
The electronic device of the embodiments of the present application exists in various forms, including but not limited to:
(1) mobile communication devices, which are characterized by mobile communication capabilities and are primarily targeted at providing voice and data communications. Such terminals include smart phones (e.g., iphones), multimedia phones, functional phones, and low-end phones, among others.
(2) The ultra-mobile personal computer equipment belongs to the category of personal computers, has calculation and processing functions and generally has the characteristic of mobile internet access. Such terminals include PDA, MID, and UMPC devices, such as ipads.
(3) Portable entertainment devices such devices may display and play multimedia content. Such devices include audio and video players (e.g., ipods), handheld game consoles, electronic books, as well as smart toys and portable car navigation devices.
(4) The server is similar to a general computer architecture, but has higher requirements on processing capability, stability, reliability, safety, expandability, manageability and the like because of the need of providing highly reliable services.
(5) And other electronic devices with data interaction functions.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a general hardware platform, and certainly can also be implemented by hardware. Based on such understanding, the above technical solutions substantially or contributing to the related art may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (10)
1. The method for the mixed authorization of the SDK of the mobile terminal suitable for multiple scenes is characterized by comprising the following steps:
when the mobile terminal SDK is released, an offline trial authorization file is built in the mobile terminal SDK;
responding to an initialization request of the mobile terminal SDK, and performing an authorization request of the mobile terminal SDK, wherein the implementation comprises
Obtaining the currently existing authorization file from the SDK of the mobile terminal for judgment,
when the authorization file is an offline trial authorization file, requesting an online authorization file, when the request is successful, updating the built-in offline trial authorization file into an online authorization file, and performing authorization verification according to the online authorization file; when the request fails, carrying out authorization verification according to the built-in off-line trial authorization file;
and when the authorization file is an online authorization file, performing authorization verification according to the online authorization file.
2. The method of claim 1, wherein the offline trial authorization file includes an expiration date and/or a product ID; the authorization verification according to the built-in off-line trial authorization file comprises
Checking whether the authorization is valid authorization or not according to the validity period and the current use information in the offline trial authorization file; and/or
And checking whether the product ID in the off-line trial authorization file is valid authorization or not according to the product ID and the current product ID.
3. The method of claim 2, wherein the offline trial authorization file further comprises usage module restriction information, and the method further comprises
And starting the available functional module according to the using module limit information when the authorization verification of the off-line trial authorization file passes.
4. The method of any of claims 1 to 3, wherein the online authorization file comprises a device ID, a product ID and a validity period, and wherein the authorization verification according to the online authorization file comprises
And according to the matching condition of the current equipment ID, the product ID and the current use information with the validity period, the equipment ID and the product ID in the online authorization file, verifying whether the current equipment ID, the product ID and the current use information are valid authorization.
5. The method according to claim 4, wherein before the request for authorizing the mobile terminal SDK is made, in response to an initialization request of the mobile terminal SDK, validity verification is performed on product application information corresponding to the mobile terminal SDK, and when the product application information verification is legal, the request for authorizing the mobile terminal SDK is made.
6. The method of claim 5, wherein the offline trial authorization file has a read-only property.
7. Mobile terminal SDK suitable for many scenes, its characterized in that includes:
the storage module is used for storing the authorization file, wherein the stored authorization file is an off-line trial authorization file or an on-line authorization file; and
an authorization verification module for responding to the initialization request of the mobile terminal SDK and making the request of the mobile terminal SDK authorization, which is realized by comprising
The first authorization unit is used for acquiring the currently stored authorization file from the storage module for judgment, and calling the second authorization unit for authorization verification when the authorization file is an off-line trial authorization file; when the authorization file is an online authorization file, authorization verification is carried out according to the online authorization file;
the second authorization unit is used for requesting an online authorization file, updating the offline trial authorization file into an online authorization file when the request is successful, and performing authorization verification according to the online authorization file; and when the request fails, performing authorization verification according to the offline trial authorization file.
8. The mobile terminal SDK according to claim 7, wherein the offline trial authorization file includes a validity period and/or a product ID, and the online authorization file includes a device ID, a product ID, and a validity period.
9. An electronic device, comprising: at least one processor, and a memory communicatively coupled to the at least one processor, wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the steps of the method of any one of claims 1-6.
10. Storage medium on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911398700.XA CN111143832A (en) | 2019-12-30 | 2019-12-30 | Mobile terminal SDK (software development kit) suitable for multiple scenes and hybrid authorization method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911398700.XA CN111143832A (en) | 2019-12-30 | 2019-12-30 | Mobile terminal SDK (software development kit) suitable for multiple scenes and hybrid authorization method thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111143832A true CN111143832A (en) | 2020-05-12 |
Family
ID=70521985
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911398700.XA Pending CN111143832A (en) | 2019-12-30 | 2019-12-30 | Mobile terminal SDK (software development kit) suitable for multiple scenes and hybrid authorization method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111143832A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626105A (en) * | 2021-08-18 | 2021-11-09 | 赞同科技股份有限公司 | SDK system and mobile device of mobile terminal mixed mode |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102479304A (en) * | 2010-11-26 | 2012-05-30 | 深圳市硅格半导体有限公司 | Method, client and system for software access control |
| CN105933358A (en) * | 2016-07-11 | 2016-09-07 | 福建方维信息科技有限公司 | Application Internet on-line real-time authorization method and system |
| CN106951741A (en) * | 2017-03-15 | 2017-07-14 | 北京深思数盾科技股份有限公司 | A kind of software license management method and device |
| CN109740306A (en) * | 2018-12-27 | 2019-05-10 | 苏州思必驰信息科技有限公司 | The method and device that application software is authorized based on hybrid plan |
| CN110046477A (en) * | 2019-04-04 | 2019-07-23 | 上海望友信息科技有限公司 | Industrial application software verification authorization method, system, medium, client/server-side |
-
2019
- 2019-12-30 CN CN201911398700.XA patent/CN111143832A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102479304A (en) * | 2010-11-26 | 2012-05-30 | 深圳市硅格半导体有限公司 | Method, client and system for software access control |
| CN105933358A (en) * | 2016-07-11 | 2016-09-07 | 福建方维信息科技有限公司 | Application Internet on-line real-time authorization method and system |
| CN106951741A (en) * | 2017-03-15 | 2017-07-14 | 北京深思数盾科技股份有限公司 | A kind of software license management method and device |
| CN109740306A (en) * | 2018-12-27 | 2019-05-10 | 苏州思必驰信息科技有限公司 | The method and device that application software is authorized based on hybrid plan |
| CN110046477A (en) * | 2019-04-04 | 2019-07-23 | 上海望友信息科技有限公司 | Industrial application software verification authorization method, system, medium, client/server-side |
Non-Patent Citations (1)
| Title |
|---|
| 张春生: "《FPGA数字信号处理与工程应用实践》", 30 June 2013, 中国铁路出版社 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626105A (en) * | 2021-08-18 | 2021-11-09 | 赞同科技股份有限公司 | SDK system and mobile device of mobile terminal mixed mode |
| CN113626105B (en) * | 2021-08-18 | 2023-10-27 | 赞同科技股份有限公司 | SDK system of mobile terminal mixed mode and mobile device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106875518B (en) | Control method and device of intelligent lock and intelligent lock | |
| CN110351269B (en) | Method for logging in open platform through third-party server | |
| US8438621B2 (en) | Method and apparatus for secure management of debugging processes within communication devices | |
| CN109815683B (en) | Authority verification method and related device | |
| US8533811B2 (en) | Developer phone registration | |
| CN107579966B (en) | Control method, device and system for remotely accessing intranet and terminal equipment | |
| TWI725352B (en) | Method for authentication and authorization and authentication server using the same | |
| US7523211B2 (en) | Information processing apparatus, information processing method, and computer-readable storage medium | |
| CN111991813B (en) | Method and device for logging in game, electronic equipment and storage medium | |
| CN107820702B (en) | Management and control method, device and electronic equipment | |
| CN103744686A (en) | Control method and system for installing application in intelligent terminal | |
| CN111881441B (en) | Method for online activation of device, electronic device and storage medium | |
| CN112714158A (en) | Transaction processing method, relay network, cross-link gateway, system, medium, and device | |
| MXPA05011088A (en) | Portable computing environment. | |
| CN110971617A (en) | Voice equipment authorization method, authentication method and system | |
| CN110784474B (en) | Embedded product access authorization method and device | |
| CN111143832A (en) | Mobile terminal SDK (software development kit) suitable for multiple scenes and hybrid authorization method thereof | |
| JP2013041587A (en) | System and method for executing command from remote source | |
| CN109740306B (en) | Method and device for authorizing application software based on mixed scheme | |
| CN116560691A (en) | Data processing method, device, computer equipment and readable storage medium | |
| CN110247877B (en) | Management method and terminal for offline management instruction | |
| CN115580641A (en) | Equipment control method based on Internet of things platform, electronic equipment and storage medium | |
| CN115515012A (en) | Key burning method and device, electronic equipment board card and storage medium | |
| CN113596600A (en) | Security management method, device, equipment and storage medium for live broadcast embedded program | |
| KR100993936B1 (en) | System for verifying legitimate program user and method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 215123 building 14, Tengfei Innovation Park, 388 Xinping street, Suzhou Industrial Park, Suzhou City, Jiangsu Province Applicant after: Sipic Technology Co.,Ltd. Address before: 215123 building 14, Tengfei Innovation Park, 388 Xinping street, Suzhou Industrial Park, Suzhou City, Jiangsu Province Applicant before: AI SPEECH Co.,Ltd. |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200512 |