CN116382934A - SDK call control method and device, electronic equipment and storage medium - Google Patents

SDK call control method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN116382934A
CN116382934A CN202211733337.4A CN202211733337A CN116382934A CN 116382934 A CN116382934 A CN 116382934A CN 202211733337 A CN202211733337 A CN 202211733337A CN 116382934 A CN116382934 A CN 116382934A
Authority
CN
China
Prior art keywords
sdk
target page
switch information
list
jump
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
Application number
CN202211733337.4A
Other languages
Chinese (zh)
Inventor
周明辉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
58tongcheng Information Technology Co ltd
Original Assignee
58tongcheng Information Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 58tongcheng Information Technology Co ltd filed Critical 58tongcheng Information Technology Co ltd
Priority to CN202211733337.4A priority Critical patent/CN116382934A/en
Publication of CN116382934A publication Critical patent/CN116382934A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • 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/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • 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/60—Protecting data
    • G06F21/602—Providing cryptographic facilities or services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/40—Transformation of program code
    • G06F8/52—Binary to binary

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Storage Device Security (AREA)

Abstract

The application discloses a method, a device, electronic equipment and a storage medium for controlling SDK call, which are applied to a client, wherein the method comprises the following steps: under the condition of receiving a page jump request, jumping to a target page through a jump protocol; acquiring authority switch information corresponding to a target page stored in a jump protocol; and determining whether each SDK in the preset software development kit SDK list can be called in the target page according to the authority switch information. By applying the technical scheme provided by the embodiment of the application, the SDK call can be conveniently, effectively and quickly controlled.

Description

SDK call control method and device, electronic equipment and storage medium
Technical Field
The present disclosure relates to the field of computer applications, and in particular, to a method and apparatus for controlling SDK call, an electronic device, and a storage medium.
Background
A software development kit (Software Development Kit, SDK), broadly refers to a collection of related documents, examples, and tools that assist in developing a certain class of software. The SDK developer may provide a plurality of SDKs to related applications, such as third party applications, through the client, and the related applications may use the corresponding functions by calling the SDKs in the client.
Call control is required to avoid misuse of the SDK. How to conveniently, effectively and quickly control the SDK call is a technical problem that needs to be solved by those skilled in the art.
Disclosure of Invention
The embodiment of the application provides a method, a device, electronic equipment and a storage medium for controlling SDK call, so as to conveniently, effectively and quickly control the SDK call.
In order to solve the technical problems, the application provides the following technical scheme:
in a first aspect, an SDK call control method is provided, applied to a client, and includes:
under the condition of receiving a page jump request, jumping to a target page through a jump protocol;
acquiring authority switch information corresponding to the target page stored in the jump protocol;
and determining whether each SDK in a preset Software Development Kit (SDK) list can be called on the target page according to the permission switch information.
Optionally, the permission switch information is a binary sequence, each bit of the binary sequence corresponds to one SDK in the SDK list, the SDKs corresponding to different bits are different, each bit is a first value or a second value, the first value is used for indicating that the corresponding SDK cannot be called, and the second value is used for indicating that the corresponding SDK can be called.
Optionally, in the case of a newly added SDK, the newly added SDK is placed at the top of the SDK list.
Optionally, the binary sequence is stored in a multilevel manner.
Optionally, the permission switch information is encrypted information, and after the permission switch information corresponding to the target page stored in the jump protocol is obtained, before determining whether each SDK in the preset SDK list can be called on the target page according to the permission switch information, the method further includes:
and decrypting the authority switch information.
Optionally, after determining whether each SDK in the preset SDK list can be called in the target page according to the permission switch information, the method further includes:
for each SDK in the SDK list, if the current SDK can be called in the target page, responding to the call request when receiving the call request for the current SDK.
Optionally, the SDK list is the latest SDK list pulled from the platform when the client is constructed in a packaging manner.
Optionally, the method further comprises:
and modifying the authority switch information corresponding to the target page in response to a modification request for the authority switch information corresponding to the target page in the jump protocol.
Optionally, the method further comprises:
when the permission switch information corresponding to the target page in the platform is detected to be updated, the permission switch information corresponding to the target page in the platform is acquired;
and updating the authority switch information corresponding to the target page stored in the jump protocol according to the acquired authority switch information.
In a second aspect, there is provided an SDK call control apparatus including:
the jump unit is used for jumping to the target page through a jump protocol under the condition of receiving the page jump request;
the acquisition unit is used for acquiring the authority switch information corresponding to the target page stored in the jump protocol;
and the determining unit is used for determining whether each SDK in the preset software development kit SDK list can be called on the target page according to the authority switch information.
In a third aspect, there is provided an electronic device comprising: a processor, a memory, and a computer program stored on the memory and executable on the processor, which when executed by the processor, performs the steps of the SDK call control method according to the first aspect.
In a fourth aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the SDK call control method according to the first aspect.
In a fifth aspect, there is provided a computer program product comprising computer instructions stored in a computer readable storage medium and adapted to be read and executed by a processor to cause an electronic device having the processor to perform the steps of the SDK call control method as described in the first aspect.
By applying the technical scheme provided by the embodiment of the application, under the condition that the client receives the page jump request, the client jumps to the target page through the jump protocol, acquires the authority switch information corresponding to the target page stored in the jump protocol, and determines whether each SDK in the preset SDK list can be called in the target page according to the authority switch information. The method comprises the steps that an SDK list is preset at a client, authority switch information corresponding to a page is stored in a skip protocol, and when the client skips to a target page, the authority switch information corresponding to the target page is conveniently and timely obtained, so that whether each SDK in the SDK list can be called on the target page or not can be rapidly determined according to the obtained authority switch information, the network is not required, and the call of the SDK can be conveniently, effectively and rapidly controlled.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
FIG. 1 is a flowchart of an implementation of an SDK call control method in an embodiment of the present application;
FIG. 2 is a flowchart of another implementation of the SDK call control method in an embodiment of the present application;
fig. 3 is a schematic structural diagram of an SDK call control device in the embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The core of the application is to provide an SDK call control method, which can be applied to a client, wherein an SDK list can be preset in the client, and authority switch information is stored in a jump protocol, the client jumps to a target page through the jump protocol under the condition of receiving a page jump request, acquires the authority switch information corresponding to the target page stored in the jump protocol, and determines whether each SDK in the preset SDK list can be called in the target page according to the authority switch information. The target page may be a page of the client itself, or may be a page of a third party application.
The technical scheme provided by the embodiment of the application can be applied to all scenes with the call of the SDK for call control.
Because the SDK list is preset at the client, the authority switch information corresponding to the page is stored in the skip protocol, when the client skips to the target page, the authority switch information corresponding to the target page is conveniently and timely acquired, so that whether each SDK in the SDK list can be called on the target page or not can be rapidly determined according to the acquired authority switch information, the network is not required, and the call of the SDK can be conveniently, effectively and rapidly controlled.
Referring to fig. 1, a flowchart of an implementation of an SDK call control method according to an embodiment of the present application is shown, where the method may include the following steps:
s110: and under the condition that the page jump request is received, jumping to the target page through a jump protocol.
In the embodiment of the application, the client may provide a plurality of SDKs for related applications, where each SDK has a corresponding function, such as volume adjustment, vibration control, longitude and latitude information acquisition, and the like. The relevant application may be the client itself or a third party application.
Under the condition that the client receives the page jump request, the client can jump to a target page through a jump protocol, wherein the target page is a page of related application. If the related application is the client, the target page is a page of the client, and if the related application is the third party application, the target page is a page of the third party application. The client can provide a carrier page for related applications, and when a page jump request exists, the client jumps to a target page through a jump protocol, so that the target page can be displayed on the carrier page. The carrier page provided by the client can be used to present different pages.
S120: and acquiring authority switch information corresponding to the target page stored in the jump protocol.
In the embodiment of the application, the authority switch information corresponding to different pages can be stored in the jump protocol, and the jump protocol can be stored in the client. After the target page is jumped to through the jump protocol, the authority switch information corresponding to the target page stored in the jump protocol can be acquired. Optionally, the permission switch information corresponding to the target page stored in the jump protocol can be searched and obtained according to the address or the identifier of the target page.
S130: and determining whether each SDK in the preset software development kit SDK list can be called in the target page according to the authority switch information.
In the embodiment of the present application, the client may be preset with an SDK list. The latest SDK list can be obtained from the platform when the client is packed and constructed, and in addition, the authority switch information can be stored in the jump protocol and packed into the local code when the client is constructed.
Each SDK included in the SDK list is an SDK that the client can provide for invocation, but requires the relevant application to have the corresponding rights to invoke.
Whether each SDK in the preset SDK list can be called or not may be indicated by rights switch information. The rights switch information may include a plurality of rights switches, each of which may correspond to one SDK. For each SDK, if the permission switch corresponding to the SDK is in an on state, the SDK can be called, and if the permission switch corresponding to the SDK is in an off state, the SDK can not be called.
After receiving the page skip request, the client skips to the target page through the skip protocol, acquires the authority switch information corresponding to the target page stored in the skip protocol, and then determines whether each SDK in the preset SDK list can be called in the target page according to the authority switch information.
Optionally, for each permission switch in the permission switch information corresponding to the target page, if the permission switch is in an on state, the SDK corresponding to the permission switch may be called in the target page, and in the target page, a corresponding function of the SDK corresponding to the permission switch may be used, and if the permission switch is in an off state, the SDK corresponding to the permission switch may not be called in the target page, and in the target page, a corresponding function of the SDK corresponding to the permission switch may not be used.
The client side can perform SDK call control locally without network interaction, so that the dependence on the network is reduced, and the SDK initialization time is more controllable.
By applying the method provided by the embodiment of the application, under the condition that the client receives the page jump request, the client jumps to the target page through the jump protocol, acquires the authority switch information corresponding to the target page stored in the jump protocol, and determines whether each SDK in the preset SDK list can be called in the target page according to the authority switch information. The method comprises the steps that an SDK list is preset at a client, authority switch information corresponding to a page is stored in a skip protocol, and when the client skips to a target page, the authority switch information corresponding to the target page is conveniently and timely obtained, so that whether each SDK in the SDK list can be called on the target page or not can be rapidly determined according to the obtained authority switch information, the network is not required, and the call of the SDK can be conveniently, effectively and rapidly controlled.
In some embodiments of the present application, the permission switch information is a binary sequence, each bit of the binary sequence corresponds to one SDK in the SDK list, the SDKs corresponding to different bits are different, and each bit is a first value or a second value, where the first value is used to indicate that the corresponding SDK cannot be called, and the second value is used to indicate that the corresponding SDK can be called.
In this embodiment of the present application, the permission switch information may be a binary sequence, where the binary sequence includes a plurality of bits, each bit of the binary sequence corresponds to one SDK in the SDK list, and SDKs corresponding to different bits are different. The number of SDKs included in the SDK list may be greater than or equal to the number of bits included in the binary sequence.
For example, the SDK list includes A, B, C, D four SDKs, and the binary sequence includes four bits, the first bit corresponding to SDK a, the second bit corresponding to SDK B, the third bit corresponding to SDK C, and the fourth bit corresponding to SDK D. Alternatively, the binary sequence includes three bits, the first bit corresponding to SDK a, the second bit corresponding to SDK B, and the third bit corresponding to SDK C. For an SDK to which a binary sequence does not correspond, the SDK may be considered not to be callable.
Each bit may be a first value indicating that the corresponding SDK may not be called or a second value indicating that the corresponding SDK may be called. For example, the first value is 0, the second value is 1, or the first value is 1, and the second value is 0.
For example, the first bit of the binary sequence is the second value, which indicates that the corresponding SDK a can be called, the second bit of the binary sequence is the first value, which indicates that the corresponding SDK B cannot be called, the current target page has no call right of the SDK B, the third bit of the binary sequence is the second value, which indicates that the corresponding SDK C can be called, the current target page has call right of the SDK C, and the fourth bit of the binary sequence is the first value, which indicates that the corresponding SDK D cannot be called, and the current target page has no call right of the SDK D.
And whether each SDK in the SDK list can be called in the target page or not is indicated through the binary sequence corresponding to the target page, so that the method is simple and convenient.
In some embodiments of the present application, in the case of a newly added SDK, the newly added SDK is placed at the top of the SDK list.
In this embodiment of the present application, the SDK list may include a plurality of SDKs, and as the use or development of the client progresses, the SDKs available to the relevant applications may increase, so that an iterative update needs to be performed on the SDK list, and in the case that there is a new SDK, the new SDK may be placed at the top of the SDK list, that is, each time the new SDK increases at the top of the SDK list. For example, the SDK list includes a plurality of SDKs sequentially arranged from the top: SDKs a, SDK B, SDK C, SDK D, and newly added SDK E, the updated SDK list includes a plurality of SDKs sequentially arranged from the top, respectively: SDK E, SDK a, SDK B, SDK C, SDK D.
According to the sequence from the lower order to the upper order of the binary sequence and the sequence from the bottom to the top of the SDK list, each bit in the binary sequence corresponds to one SDK in the SDK list, and the lowest bit in the binary sequence corresponds to the SDK at the bottom of the SDK list. If the binary sequence has an update, the updated binary sequence may have a bit added to the most significant bit as compared to the pre-update binary sequence to indicate whether the newly added SDK may be called.
Therefore, the method is beneficial to ensuring that the corresponding relation between the binary sequence and the SDK list is not easy to be destroyed, ensuring that each time of iterating the SDK list, the existing authority switch combination is not affected to cause problems, and ensuring that whether each SDK in the SDK list can be called or not can be accurately determined according to the binary sequence.
In some embodiments of the present application, the binary sequence may be stored in a multi-level manner.
In the embodiment of the present application, the number of SDKs included in the SDK list may be greater, and correspondingly, the number of bits of the binary sequence used to indicate whether the SDK can be called is greater, and if the binary sequence is directly stored for storage, more storage space will be occupied. Therefore, the binary sequence can be converted into multiple systems to be stored in a multiple system mode, and the storage space is saved.
Alternatively, the binary sequence may be stored in a thirty-six system manner.
The acquired authority switch information corresponding to the target page stored in the jump protocol is multi-system information, the multi-system information can be converted into a binary sequence, and whether each SDK in the SDK list can be called in the target page or not is determined through the binary sequence.
Taking the example that the binary sequence is stored in thirty-six system, the meaning that the newly added SDK is placed at the top of the SDK list in the case that the newly added SDK exists is explained again:
the obtained authority switch information is thirty-six system information, the thirty-six system information is converted into a binary sequence, the binary sequence obtained by conversion may be a sequence 1 '000110001', and the sequence 1 corresponds to the original binary sequence, namely a sequence 2 '110001'. If there is a newly added SDK, adding a bit at the lowest order of the binary sequence to indicate that the newly added SDK can be invoked, sequence 1 will become sequence 3"001100011", sequence 3 cannot correspond to sequence 2"110001". If there is a newly added SDK, adding a bit at the most significant bit of the binary sequence to indicate that the newly added SDK can be called, sequence 1 will become sequence 4"001110001", which can smoothly correspond to sequence 2"110001" through sequence 4. Therefore, under the condition that the newly added SDK exists, the newly added SDK is arranged at the top of the SDK list, so that the corresponding relation between the binary sequence and the SDK list is not easy to destroy.
In some embodiments of the present application, the permission switch information is encrypted information, and after obtaining permission switch information corresponding to a target page stored in a jump protocol, determining, according to the permission switch information, whether each SDK in a preset SDK list is before the target page can be called, the method may further include the following steps:
and decrypting the authority switch information.
In the embodiment of the present application, the rights switch information stored in the skip protocol may be encrypted information. For example, the binary sequence may be converted to multi-level information and stored encrypted by an exclusive or operation. After the permission switch information corresponding to the target page is obtained, the permission switch information can be decrypted, for example, the permission switch information is decrypted through exclusive or operation to obtain multi-system information, and then the multi-system information is converted into a binary sequence.
After the permission switch information is decrypted, determining whether each SDK in the preset SDK list can be called in the target page or not according to the decrypted permission switch information.
The authority switch information is stored in an encrypted mode, so that the safety of the authority switch information can be improved.
In general, the rights switch information is stored within the jump protocol, and its exact location is not easily known from the outside. And the length of the permission switch information and the SDK list can be changed when the client is constructed by packing each time, the corresponding relationship between the permission switch information and the SDK list can be changed, and the security can be further improved.
In some embodiments of the present application, after determining whether each SDK in the preset SDK list can be called at the target page according to the rights switch information, the method may further include the steps of:
for each SDK in the SDK list, if the current SDK can be called in the target page, responding to the call request when receiving the call request for the current SDK. In the embodiment of the application, the client determines whether each SDK in the preset SDK list can be called in the target page according to the authority switch information corresponding to the target page. And when a call request exists, the control can be performed according to the determination result.
For each SDK in the SDK list, if the current SDK can be called in the target page, when a call request for the current SDK is received, the call request can be responded, the current SDK is allowed to be called in the target page, and the corresponding function of the current SDK can be used in the target page. If the current SDK cannot be called in the target page, the call request can be ignored when the call request for the current SDK is received, no response is made, or prompt information for the current SDK cannot be called can be output. The current SDK is the SDK for which the current operation is directed.
For each call request received at the target page, relevant information can be recorded in a call log for subsequent viewing in terms.
In some embodiments of the present application, the method may further comprise the steps of:
and responding to a modification request aiming at the authority switch information corresponding to the target page in the jump protocol, and modifying the authority switch information corresponding to the target page.
In the embodiment of the application, the permission switch information can be directly modified in the jump protocol according to actual conditions, such as adding the permission switch corresponding to the newly added SDK or modifying the existing permission switch. In response to a modification request for the permission switch information corresponding to the target page in the jump protocol, the permission switch information corresponding to the target page can be modified in the jump protocol, so that call control can be more accurately performed on the SDKs in the SDK list.
In some embodiments of the present application, the method may further comprise the steps of:
step one: acquiring authority switch information corresponding to a target page in the platform when the authority switch information corresponding to the target page in the platform is updated;
step two: and updating the authority switch information corresponding to the target page stored in the jump protocol according to the acquired authority switch information.
For ease of description, the two steps described above are combined.
In the embodiment of the application, the permission switch information can be configured or updated in the platform, the client can interact with the platform to determine whether the permission switch information corresponding to the target page in the platform is updated, if so, the permission switch information corresponding to the target page in the platform can be obtained, and then the permission switch information corresponding to the target page stored in the jump protocol is updated. Therefore, the authority switch information in the jump protocol can be ensured to be the latest information, and the accuracy of determining whether the SDK in the SDK list can be called or not is ensured.
In order to facilitate understanding, embodiments of the present application are described below by way of specific examples.
As shown in fig. 2, setting of authority switch information and an SDK list can be performed on a platform, when a client terminal packages, the SDK list can be pulled on the platform, and the SDK list can include a plurality of SDKs, such as SDK a, SDK B, SDK C and SDK D, and the authority switch information corresponding to a target page is acquired on the platform, such as a binary sequence 1010, and the binary sequence is converted into multiple systems, such as thirty-six systems, and is subjected to exclusive-or encryption operation and stored in a skip protocol. When a client enters a webpage view (WebView), the client can jump to a target page through a jump protocol, obtain authority switch information corresponding to the target page stored in the jump protocol, decrypt and carry out binary conversion to obtain a binary sequence, and carry out SDK call control according to the binary sequence.
According to the method and the device, whether the SDK can be called or not is controlled through the permission switch, the SDK list is pre-arranged in the client, permission switch information is stored in the jump protocol, call control can be carried out without a network, limitation and delay of the network on call control of the SDK are reduced, in addition, different carrier pages do not need to be developed for different services, and development cost and maintenance cost can be reduced.
Corresponding to the above method embodiment, the embodiment of the present application further provides an SDK call control device, where the SDK call control device described below and the SDK call control method described above may be referred to correspondingly.
Referring to fig. 3, the SDK call control apparatus 300 may include the following units:
a jumping unit 310, configured to jump to the target page through a jumping protocol when receiving the page jumping request;
an obtaining unit 320, configured to obtain rights switch information corresponding to a target page stored in a jump protocol;
and a determining unit 330, configured to determine, according to the permission switch information, whether each SDK in the preset software development kit SDK list can be called on the target page.
By applying the device provided by the embodiment of the application, the client jumps to the target page through the jump protocol under the condition of receiving the page jump request, acquires the authority switch information corresponding to the target page stored in the jump protocol, and determines whether each SDK in the preset SDK list can be called in the target page according to the authority switch information. The method comprises the steps that an SDK list is preset at a client, authority switch information corresponding to a page is stored in a skip protocol, and when the client skips to a target page, the authority switch information corresponding to the target page is conveniently and timely obtained, so that whether each SDK in the SDK list can be called on the target page or not can be rapidly determined according to the obtained authority switch information, the network is not required, and the call of the SDK can be conveniently, effectively and rapidly controlled.
In some embodiments of the present application, the permission switch information is a binary sequence, each bit of the binary sequence corresponds to one SDK in the SDK list, the SDKs corresponding to different bits are different, and each bit is a first value or a second value, where the first value is used to indicate that the corresponding SDK cannot be called, and the second value is used to indicate that the corresponding SDK can be called.
In some embodiments of the present application, in the case of a newly added SDK, the newly added SDK is placed at the top of the SDK list.
In some embodiments of the present application, the binary sequences are stored in a multi-level manner.
In some embodiments of the present application, the rights switch information is encrypted information, and the SDK call control device 300 further includes a decryption unit configured to:
after the permission switch information corresponding to the target page stored in the jump protocol is acquired, determining whether each SDK in the preset SDK list can be called or not before the target page according to the permission switch information, and performing decryption processing on the permission switch information.
In some embodiments of the present application, the SDK call control device 300 further includes a response unit configured to:
for each SDK in the SDK list, if the current SDK can be called in the target page, responding to the call request when receiving the call request for the current SDK.
In some embodiments of the present application, the SDK list is the latest SDK list pulled from the platform when the client is built in a package.
In some embodiments of the present application, the SDK call control apparatus 300 further includes a modification unit configured to:
and responding to a modification request aiming at the authority switch information corresponding to the target page in the jump protocol, and modifying the authority switch information corresponding to the target page.
In some embodiments of the present application, the SDK call control apparatus 300 further includes an updating unit configured to:
acquiring authority switch information corresponding to a target page in the platform when the authority switch information corresponding to the target page in the platform is updated;
and updating the authority switch information corresponding to the target page stored in the jump protocol according to the acquired authority switch information.
The specific manner in which the individual units perform the operations in relation to the apparatus of the above embodiments has been described in detail in relation to the embodiments of the method and will not be described in detail here.
Corresponding to the above method embodiment, the embodiment of the present application further provides an electronic device, including: the processor, the memory, store on the memory and can be on the computer program of the operation of processor, this computer program realizes the above-mentioned SDK and calls each procedure of the control method embodiment when being carried out by the processor, and can reach the same technical result, in order to avoid repetition, will not be repeated here.
As shown in fig. 4, which is a schematic structural diagram of an electronic device, the electronic device may include: a processor 410, a memory 411, a communication interface 412, and a communication bus 413. The processor 410, the memory 411, and the communication interface 412 all perform communication with each other through the communication bus 413.
In the present embodiment, the processor 410 may be a central processing unit (Central Processing Unit, CPU), an asic, a dsp, a field programmable gate array, or other programmable logic device, etc.
The processor 410 may call a computer program stored in the memory 411, and in particular, the processor 410 may perform operations in an embodiment of the SDK call control method.
The memory 411 is used to store one or more programs, and the programs may include program codes, where the program codes include computer operation instructions, and in this embodiment, at least the programs for implementing the following functions are stored in the memory 411:
under the condition of receiving a page jump request, jumping to a target page through a jump protocol;
acquiring authority switch information corresponding to a target page stored in a jump protocol;
and determining whether each SDK in the preset software development kit SDK list can be called in the target page according to the authority switch information.
In one possible implementation, the memory 411 may include a storage program area and a storage data area, where the storage program area may store an operating system, and applications required for at least one function (e.g., a jump function, an information acquisition function), and so on; the storage data area may store data created during use, such as SDK data, rights data, and the like.
In addition, the memory 411 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device or other volatile solid state storage device.
The communication interface 412 may be an interface of a communication module for interfacing with other devices or systems.
Of course, it should be noted that the structure shown in fig. 4 is not limited to the electronic device in the embodiment of the present application, and the electronic device may include more or fewer components than those shown in fig. 4 or may combine some components in practical applications.
The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the processes of the SDK call control method embodiment are implemented, and the same technical effects can be achieved, so that repetition is avoided, and no further description is provided here. Among them, a computer-readable storage medium such as Read-Only Memory (ROM), random access Memory (Random Access Memory RAM), magnetic disk or optical disk, and the like.
Furthermore, embodiments of the present application provide a computer program product or computer program that may include computer instructions that may be stored in a computer-readable storage medium. The processor of the electronic device reads the computer instructions from the computer readable storage medium, and the processor may execute the computer instructions, so that the electronic device performs the description of the SDK call control method in the foregoing corresponding embodiment, and therefore, a detailed description will not be given here. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the computer program product or the computer program embodiments related to the present application, please refer to the description of the method embodiments of the present application.
It should be noted that, in this document, 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 one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), including several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (12)

1. An SDK call control method, applied to a client, includes:
under the condition of receiving a page jump request, jumping to a target page through a jump protocol;
acquiring authority switch information corresponding to the target page stored in the jump protocol;
and determining whether each SDK in a preset Software Development Kit (SDK) list can be called on the target page according to the permission switch information.
2. The method of claim 1, wherein the permission switch information is a binary sequence, each bit of the binary sequence corresponds to one SDK in the list of SDKs, the SDKs corresponding to different bits are different, each bit is a first value or a second value, the first value is used to indicate that the corresponding SDK is not callable, and the second value is used to indicate that the corresponding SDK is callable.
3. The method of claim 2, wherein in the event of a newly added SDK, the newly added SDK is placed at the top of the SDK list.
4. The method of claim 2, wherein the binary sequence is stored in a multi-system manner.
5. The method according to claim 1, wherein the permission switch information is encrypted information, and after the obtaining permission switch information corresponding to the target page stored in the jump protocol, the determining, according to the permission switch information, whether each SDK in the preset SDK list is before the target page can be called, further includes:
and decrypting the authority switch information.
6. The method of claim 1, wherein after said determining whether each SDK in the preset list of SDKs is callable on the target page according to the rights switch information, further comprising:
for each SDK in the SDK list, if the current SDK can be called in the target page, responding to the call request when receiving the call request for the current SDK.
7. The method of claim 1, wherein the SDK list is a latest SDK list pulled from a platform when the client is built in a package.
8. The method as recited in claim 1, further comprising:
and modifying the authority switch information corresponding to the target page in response to a modification request for the authority switch information corresponding to the target page in the jump protocol.
9. The method according to any one of claims 1 to 8, further comprising:
acquiring authority switch information corresponding to the target page in the platform when the authority switch information corresponding to the target page in the platform is updated;
and updating the authority switch information corresponding to the target page stored in the jump protocol according to the acquired authority switch information.
10. An SDK call control apparatus, comprising:
the jump unit is used for jumping to the target page through a jump protocol under the condition of receiving the page jump request;
the acquisition unit is used for acquiring the authority switch information corresponding to the target page stored in the jump protocol;
and the determining unit is used for determining whether each SDK in the preset software development kit SDK list can be called on the target page according to the authority switch information.
11. An electronic device, comprising: a processor, a memory and a computer program stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the SDK call control method of any one of claims 1 to 9.
12. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the SDK call control method according to any one of claims 1 to 9.
CN202211733337.4A 2022-12-30 2022-12-30 SDK call control method and device, electronic equipment and storage medium Pending CN116382934A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211733337.4A CN116382934A (en) 2022-12-30 2022-12-30 SDK call control method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211733337.4A CN116382934A (en) 2022-12-30 2022-12-30 SDK call control method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN116382934A true CN116382934A (en) 2023-07-04

Family

ID=86979376

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211733337.4A Pending CN116382934A (en) 2022-12-30 2022-12-30 SDK call control method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116382934A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116582639A (en) * 2023-07-13 2023-08-11 深圳星网信通科技股份有限公司 Conference control method, terminal device and storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116582639A (en) * 2023-07-13 2023-08-11 深圳星网信通科技股份有限公司 Conference control method, terminal device and storage medium
CN116582639B (en) * 2023-07-13 2023-11-07 深圳星网信通科技股份有限公司 Conference control method, terminal device and storage medium

Similar Documents

Publication Publication Date Title
CN108353462B (en) Configuration file downloading method and related equipment and system
CN108322461B (en) Method, system, device, equipment and medium for automatically logging in application program
US11115201B2 (en) Downloading of data to secure devices
CN108898005B (en) Hard disk identification method, system, equipment and computer readable storage medium
CN101189617A (en) Electronic device, update server device, key update device
KR101756978B1 (en) Method and System for Protecting application program in trusted execution environment
JP5540109B2 (en) System and method for loading application classes
CN109891415B (en) Securing a Web server for an unauthorized client application
WO2011134207A1 (en) Method for protecting software
CN105574414A (en) Method for loading a file into ram in an electronic apparatus and associated electronic apparatus
CN116382934A (en) SDK call control method and device, electronic equipment and storage medium
CN110753018A (en) Login authentication method and system
CN111460437A (en) Firmware running method and device, firmware burning method and device and computer equipment
CN113839780A (en) Encryption method, decryption method, server and storage medium
EP2689367B1 (en) Data protection using distributed security key
CN112966229A (en) Method and device for safely operating SDK
CN106295327B (en) Executable file reinforcing method and device
CN113765950A (en) Internet of things equipment, server and software updating method
CN113220314B (en) APP resource loading and APK generation method, device, equipment and medium
CN111182010A (en) Local service providing method and device
CN105184173A (en) Method and device for request processing
CN101112040B (en) Method for protection of a digital rights file
CN113934988A (en) Software security protection method, computer device and storage medium
CN112506810B (en) Storage space distribution method applied to chip and chip
CN113506390B (en) Access control method, device, equipment and readable storage medium

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