CN116506165A - Cloud mobile phone identification method and device, electronic equipment and readable storage medium - Google Patents

Cloud mobile phone identification method and device, electronic equipment and readable storage medium Download PDF

Info

Publication number
CN116506165A
CN116506165A CN202310386573.1A CN202310386573A CN116506165A CN 116506165 A CN116506165 A CN 116506165A CN 202310386573 A CN202310386573 A CN 202310386573A CN 116506165 A CN116506165 A CN 116506165A
Authority
CN
China
Prior art keywords
feature
client
mobile phone
features
target
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
CN202310386573.1A
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.)
Beijing Baidu Netcom Science and Technology Co Ltd
Original Assignee
Beijing Baidu Netcom Science and 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 Beijing Baidu Netcom Science and Technology Co Ltd filed Critical Beijing Baidu Netcom Science and Technology Co Ltd
Priority to CN202310386573.1A priority Critical patent/CN116506165A/en
Publication of CN116506165A publication Critical patent/CN116506165A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H04L63/205—Network architectures or network communication protocols for network security for managing network security; network security policies in general involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Power Engineering (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The disclosure provides a cloud mobile phone identification method, a cloud mobile phone identification device, electronic equipment and a readable storage medium. The identification method applied to the server side comprises the following steps: receiving equipment information sent by a client; selecting source features corresponding to the equipment information from the feature library, and generating a feature strategy according to the source features; the feature strategy is sent to the client, and target features sent by the client are received; and under the condition that the target characteristics are inconsistent with the source characteristics, determining that the client runs on the cloud mobile phone. The identification method applied to the client comprises the following steps: acquiring equipment information; the equipment information is sent to a server side, and a feature strategy sent by the server side is received; and executing the feature strategy to acquire target features, and sending the target features to the server side. According to the cloud mobile phone identification method and the cloud mobile phone identification device, cloud mobile phone identification is carried out through interaction between the server side and the client side, and accuracy of cloud mobile phone identification can be improved.

Description

Cloud mobile phone identification method and device, electronic equipment and readable storage medium
Technical Field
The disclosure relates to the technical field of internet, in particular to the technical field of artificial intelligence such as big data, cloud service and the like. Provided are a cloud mobile phone identification method, a cloud mobile phone identification device, an electronic device and a readable storage medium.
Background
Cloud mobile phone (CloudPhone) is a technology of applying cloud computing technology to network terminal service and realizing cloud service through a cloud server, and the mobile phone can realize a plurality of functions through a network by virtue of a self-contained system and a network terminal erected by a manufacturer. The cloud mobile phone technology provides convenience for users, but also brings hidden danger to information security. Therefore, how to identify the cloud mobile phone is a technical problem to be solved.
Disclosure of Invention
According to a first aspect of the present disclosure, there is provided a method for cloud mobile phone identification, applied to a server side, including: receiving equipment information sent by a client; selecting source features corresponding to the equipment information from a feature library, and generating a feature strategy according to the source features; the feature strategy is sent to the client, target features sent by the client are received, and the target features are features obtained by the client by executing the feature strategy; and under the condition that the target characteristics are inconsistent with the source characteristics, determining that the client runs on a cloud mobile phone.
According to a second aspect of the present disclosure, there is provided a method for cloud mobile phone identification, applied to a client, including: acquiring equipment information; the device information is sent to a server side, the feature strategy sent by the server side is received, and the device information is used for the server side to generate the feature strategy; and executing the feature policy to acquire target features, and sending the target features to the server side, wherein the target features are used for comparing the server side with source features to determine whether the client side operates on a cloud mobile phone.
According to a third aspect of the present disclosure, there is provided a device for cloud mobile phone identification, applied to a server, including: the receiving unit is used for receiving the equipment information sent by the client; the generating unit is used for selecting source features corresponding to the equipment information from the feature library and generating a feature strategy according to the source features; the first sending unit is used for sending the feature policy to the client, receiving target features sent by the client, and executing the feature obtained by the feature policy for the target features by the client; and the first processing unit is used for determining that the client runs on the cloud mobile phone under the condition that the target characteristic is inconsistent with the source characteristic.
According to a fourth aspect of the present disclosure, there is provided a device for cloud mobile phone identification, applied to a client, including: an acquisition unit configured to acquire device information; the second sending unit is used for sending the equipment information to a server side, receiving the characteristic strategy sent by the server side, and the equipment information is used for generating the characteristic strategy by the server side; and the execution unit is used for executing the feature policy to acquire target features, sending the target features to the server side, and comparing the target features with the source features by the server side to determine whether the client side operates on the cloud mobile phone.
According to a fifth aspect of the present disclosure, there is provided 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 method as described above.
According to a sixth aspect of the present disclosure, there is provided a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method as described above.
According to a seventh aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements a method as described above.
According to the technical scheme, whether the client runs on the cloud mobile phone is identified through interaction between the server side and the client side, the server side obtains target features returned by the client side and used for comparison with source features in a mode of dynamically generating feature strategies according to equipment information sent by the client side, the possibility that the target features are tampered is further reduced, accuracy of the obtained target features can be improved, and accuracy of cloud mobile phone identification is further improved.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
Drawings
The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is a schematic diagram according to a first embodiment of the present disclosure;
FIG. 2 is a schematic diagram according to a second embodiment of the present disclosure;
FIG. 3 is a schematic diagram according to a third embodiment of the present disclosure;
FIG. 4 is a schematic diagram according to a fourth embodiment of the present disclosure;
FIG. 5 is a schematic diagram according to a fifth embodiment of the present disclosure;
FIG. 6 is a schematic diagram according to a sixth embodiment of the present disclosure;
fig. 7 is a block diagram of an electronic device used to implement a method of cloud handset identification according to an embodiment of the disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram according to a first embodiment of the present disclosure. As shown in fig. 1, the cloud mobile phone identification method of the embodiment is applied to a server, and specifically includes the following steps:
s101, receiving equipment information sent by a client;
s102, selecting source features corresponding to the equipment information from a feature library, and generating a feature strategy according to the source features;
s103, the feature strategy is sent to the client, target features sent by the client are received, and the target features are features obtained by the client executing the feature strategy;
and S104, determining that the client runs on a cloud mobile phone under the condition that the target characteristics are inconsistent with the source characteristics.
The execution subject of the cloud mobile phone identification method in this embodiment is a server, after receiving device information sent by a client, the server firstly generates a feature policy according to source features corresponding to the device information selected from a feature library, then sends the feature policy to the client, further receives target features sent by the client, and finally determines whether the client operates on the cloud mobile phone according to whether the target features are consistent with the source features, and the server in this embodiment adopts a manner of dynamically generating the feature policy according to the device information sent by the client to obtain target features returned by the client for comparison with the source features, so that the possibility of tampering of the target features is further reduced, the accuracy of the obtained target features can be improved, and the accuracy of cloud mobile phone identification is further improved.
When the server side of the embodiment executes S101, the received device information sent by the client side includes at least one of vendor information, model information, ROM (read only memory) name, ROM version, system version, buildld (information for providing platform version, code branch, date when version is subdivided from development branch or synchronized with development branch) of the terminal device where the client side is located; preferably, in this embodiment, a terminal device where a client is located supports an Android (Android) system, and the client corresponds to an Application (Application) in the terminal device.
After executing S101 to receive the device information sent by the client, executing S102 to select source features corresponding to the device information from the feature library, and generating a feature policy according to the source features; the server executes the feature policy generated in S102, so that the client obtains the target feature corresponding to the feature policy.
In this embodiment, a feature library is pre-established for the server, where the feature library includes different device information and features corresponding to the different device information; among the features corresponding to the different device information, at least one of a system class feature of the client system layer and a so instruction feature of the client system layer is included.
The system class features correspond to SDK (software development kit) of the client and comprise at least one of constructor features, member method features and member variable features; the constructor feature includes different constructors, parameters and modifiers corresponding to the different constructors, the member method feature includes different member methods, parameters and modifiers corresponding to the different member methods, and execution results, and the member variable feature includes different member variables, parameters and modifiers corresponding to the different member variables, and variable values.
The so instruction features correspond to NDKs (native development kits) of clients, and include different so instructions, and file names, types, modifiers, symbol names, and the like corresponding to the different so instructions.
For example, one constructor included in the constructor feature is "public android.text.extensible $factor ()", a parameter corresponding to the constructor is "[ ]", and a modifier is 1; one so instruction contained in the so instruction feature is "aarch64-linux-android", the file name corresponding to the so instruction is "libandroid. So", the symbol name is "amotionEvent_gethistoryiyy", the modifier is "GLOBAL", and the type is "FUNC".
It can be understood that the system class feature and/or the so instruction feature in the present embodiment corresponds to the device information, for example, the constructor feature 1 corresponds to the vendor a, the constructor feature 2 corresponds to the model a, the member method feature 1 corresponds to the model a, the so instruction feature 1 corresponds to the ROM version a, and the like; according to the embodiment, the system class characteristics and/or the so instruction characteristics corresponding to the equipment information can be obtained according to the equipment information.
Specifically, when executing S102 to select a source feature corresponding to the device information from the feature library, the server side of this embodiment may adopt the following alternative implementation manners: the device information is randomly selected, the selected result is used as target device information, and the embodiment can randomly select the first preset number of device information as target device information; and selecting the characteristics corresponding to the target equipment information from the characteristic library as source characteristics.
That is, the server side of the embodiment acquires the source feature by randomly selecting the target device information from the device information, so that randomness in acquiring the source feature can be improved, randomness of the generated feature strategy is further improved, and the problem that the target feature is tampered due to the fixed feature strategy is effectively avoided.
In addition, when executing S102 to select a source feature corresponding to the device information from the feature library, the server side of the embodiment may also randomly select, for each device information, a feature corresponding to the device information in the feature library, and further use the selected result as the source feature; the second preset number of features may be randomly selected as the source features in this embodiment.
It can be understood that, when executing S102, the server side of the present embodiment may also select all the features (system class features and/or so instruction features) corresponding to the device information from the feature library as source features.
In the embodiment, when the step S102 of selecting the feature corresponding to the target device information from the feature library as the source feature is performed, all the features corresponding to the target device information may be used as the source features, or for each target device information, the feature corresponding to the target device information in the feature library may be randomly selected, and the selection result may be used as the source features.
For example, if the device information received in S101 includes information 1, information 2, information 3 and information 4, the server may randomly select the information 2 and the information 4 as the target device information when executing S102; if the features corresponding to the information 2 in the feature library include the features 1, 2 and 3, and the features corresponding to the information 4 include the features 4, 5 and 6, the server side may randomly select the feature 1 as the source feature for the information 2 and may randomly select the features 4 and 6 as the source feature for the information 4 when executing S102.
After executing S102 to select source features, the server side of the embodiment generates feature strategies according to the selected source features, wherein the feature strategies are used for being sent to the client side for execution, so that corresponding target features are obtained; in addition, a corresponding relation exists between the feature strategy and the source feature generating the feature strategy, and the corresponding source feature can be determined according to the feature strategy.
For example, if the server side generates the feature policy according to the feature 1, the feature 4 and the feature 6, the MD5 value corresponding to the feature policy may be further generated, and the correspondence between the MD5 value and the feature 1, the correspondence between the feature 4 and the feature 6 may be further established, so that after the server side receives the target feature sent by the client side, the corresponding source feature is determined according to the MD5 value corresponding to the feature policy, and then the source feature is compared.
When executing S102 to generate a feature policy according to source features, the server side of this embodiment may generate a feature policy according to all the contents included in each source feature, or may randomly select, for each source feature, a content from the source feature, and then generate a feature policy according to the randomly selected content.
The server side in this embodiment executes the feature policy generated in S102, which may be used for the client side to obtain one or more source features in the terminal device where the client side is located, or may be used for the client side to obtain features such as parameters, modifiers, execution results, variable values, file names, types, modifiers, symbol names, etc. corresponding to the one or more source features in the terminal device where the client side is located.
For example, if the source feature selected by the server side is the constructor feature 1, the constructor feature 1 includes the constructor a, and the parameters a and modifiers a corresponding to the constructor a, and the server side executes the feature policy generated in S102, which may be used for the client side to obtain the constructor a of the terminal device where the client side is located, or may be used for the client side to obtain the parameters and modifiers corresponding to the constructor a of the terminal device where the client side is located, or may be used for the client side to obtain the constructor a and the parameters and modifiers corresponding to the constructor a of the terminal device where the client side is located.
After executing S102 to generate a feature policy according to the source feature, executing S103 to send the feature policy to the client and receive the target feature sent by the client; the target features are features obtained by the client executing the feature policy.
For example, if the feature policy is to obtain the constructor a and the parameters and modifiers corresponding to the constructor a, the server executes the target feature sent by the client and received in S103, that is, the client obtains the constructor a and the parameters and modifiers of the constructor a in the terminal device where the client is located.
After executing S103 to receive the target feature sent by the client, the server in this embodiment executes S104 to determine that the client is operating in the cloud mobile phone, or may refer to determining that the client is operating in the cloud mobile phone environment, where it is determined that the target feature is inconsistent with the source feature of the generated feature policy.
The server side of this embodiment may compare the target feature sent by the client side with the source feature when executing S104, and determine that the target feature is consistent with the source feature only when the target feature is the same as the source feature, or determine that the target feature is inconsistent with the source feature.
In addition, after executing S104 to determine that the client runs on the cloud mobile phone, the server in this embodiment may send a prompt message to the client to remind the user that there is a risk of running the client on the cloud mobile phone, or may send a stop running instruction to the client after determining that the client meets a preset requirement, for example, the type of the client is a preset type (the preset type may be a game client or a social client), so that the client stops running on the cloud mobile phone.
After executing S104 to determine that the client is running on the cloud mobile phone, the server in this embodiment may further include the following: a list acquisition request is sent to a client, and the list acquisition request is used for the client to acquire an installation list of an application program in a cloud mobile phone running in the client; receiving an installation list sent by a client; and under the condition that the existence of the preset application program in the cloud mobile phone is determined according to the installation list, determining that the cloud mobile phone has cheating risk.
That is, the server side of the embodiment can further detect an application program of the cloud mobile phone where the client side operates, so as to identify whether the cloud mobile phone has a cheating risk, and can improve the identification effect of the cloud mobile phone, and further take corresponding measures to avoid the cheating behavior in advance.
After executing S104 to determine that the cloud mobile phone where the client operates has the cheating risk, the server side of the embodiment may send a prompt message to the client side to prompt the user to delete the cheating program in the cloud mobile phone, or directly send an operation stopping instruction to the client side, so that the client side stops operating in the cloud mobile phone.
Fig. 2 is a schematic diagram according to a second embodiment of the present disclosure. As shown in fig. 2, the cloud mobile phone identification method of the embodiment is applied to a client, and specifically includes the following steps:
s201, acquiring equipment information;
s202, sending the equipment information to a server side, and receiving a feature strategy sent by the server side, wherein the equipment information is used for generating the feature strategy by the server side;
s203, executing the feature policy to obtain target features, and sending the target features to the server, wherein the target features are used for comparing the server with source features to determine whether the client runs on a cloud mobile phone.
The execution subject of the cloud mobile phone identification method in the embodiment is a client, after the client acquires the equipment information, the equipment information is firstly sent to the server, then the feature strategy sent by the server is received, then the feature strategy is executed to acquire the target feature, and finally the target feature is sent to the server, so that the server can determine whether the client operates on the cloud mobile phone or not according to the target feature.
The device information obtained in S201 by the client in this embodiment includes at least one of vendor information, model information, ROM name, ROM version, system version, and buildld of the terminal device in which the client is located.
After the client in this embodiment obtains the device information in S201, S202 sends the device information to the server and receives the feature policy sent by the server, where the feature policy is dynamically generated by the server according to the device information.
After executing S202 the feature policy sent by the server, the client executes S203 the feature policy to obtain the target feature, and sends the target feature to the server, so that the server determines whether the client operates on the cloud mobile phone according to the target feature.
When executing the execution feature policy of S203 to obtain the target feature, the client of this embodiment first determines the system class feature and/or the so instruction feature to be obtained according to the feature policy, and then uses the obtained system class feature and/or the so instruction feature as the target feature.
The client of the present embodiment may further include the following after executing S203 to send the target feature to the server: receiving a list acquisition request sent by a server side; acquiring an installation list of an application program in a cloud mobile phone where a client operates; and sending the installation list to a server side so as to be used for determining whether the cloud mobile phone has cheating risk or not by the server side.
In addition, after executing S203 to send the application installation list to the server, the client in this embodiment may also receive the prompt message sent by the server, or stop the operation instruction.
Fig. 3 is a schematic diagram according to a second embodiment of the present disclosure. Fig. 3 shows an architecture diagram of a server-side generated feature library according to the present embodiment: the server side firstly acquires equipment information uploaded by a mass client side, and system class characteristics and so instruction characteristics of corresponding equipment information; then processing the equipment information and the corresponding system class features and so instruction features through a cloud data detection model, wherein the processing process can comprise removing inaccurate features (such as features obtained when a client runs on a cloud mobile phone), and further determining special features and common features corresponding to different equipment information; and finally, generating a feature library containing different equipment information and features corresponding to the different equipment information.
In order to facilitate the management of the features contained in the feature library, the server side of the embodiment may use different device information as different feature dimensions (for example, vendor dimensions, model dimensions, etc.), so that only features corresponding to the dimensions are contained in the different feature dimensions, for example, features corresponding to vendor 1 and features corresponding to vendor 2 are contained in the vendor dimensions, and features corresponding to model 1 and features corresponding to model 2 are contained in the model dimensions.
Fig. 4 is a schematic diagram according to a third embodiment of the present disclosure. Fig. 4 shows a structure diagram of interaction between a server and a client to implement cloud mobile phone identification in this embodiment: s401, the client acquires equipment information and sends the equipment information to the server so as to acquire a characteristic strategy generated by the server according to the equipment information; s402, the server generates a feature strategy according to the equipment information and the feature library sent by the client and sends the feature strategy to the client; s403, the client executes the feature strategy sent by the server to acquire target features, and sends the target features to the server; s404, the server side performs cloud mobile phone identification or cloud mobile phone risk identification according to the target characteristics sent by the client side so as to determine whether the client side operates on the cloud mobile phone or whether the cloud mobile phone on which the client side operates has cheating risk.
Fig. 5 is a schematic diagram according to a fifth embodiment of the present disclosure. As shown in fig. 5, the cloud mobile phone identification device 500 of the present embodiment is applied to a server, and includes:
a receiving unit 501, configured to receive device information sent by a client;
a generating unit 502, configured to select a source feature corresponding to the device information from a feature library, and generate a feature policy according to the source feature;
a first sending unit 503, configured to send the feature policy to the client, receive a target feature sent by the client, where the target feature is a feature obtained by the client by executing the feature policy;
the first processing unit 504 is configured to determine that the client is running on a cloud mobile phone if it is determined that the target feature is inconsistent with the source feature.
The device information sent by the client and received by the receiving unit 501 includes at least one of vendor information, model information, ROM (read only memory) name, ROM version, system version, buildld (information for providing a platform version, a code branch, a date when the version is subdivided from a development branch or synchronized with the development branch) of the terminal device where the client is located; preferably, in this embodiment, a terminal device where a client is located supports an Android (Android) system, and the client corresponds to an Application (Application) in the terminal device.
After the receiving unit 501 receives the device information sent by the client, the generating unit 502 selects the source feature corresponding to the device information from the feature library, and generates a feature policy according to the source feature; the feature policy generated by the generating unit 502 is used for being executed by the client, so that the client obtains the target feature corresponding to the feature policy.
In this embodiment, a feature library is pre-established for the server, where the feature library includes different device information and features corresponding to the different device information; among the features corresponding to the different device information, at least one of a system class feature of the client system layer and a so instruction feature of the client system layer is included.
Specifically, when the generating unit 502 selects the source feature corresponding to the device information from the feature library, the optional implementation manner may be: the device information is randomly selected, the selected result is used as target device information, and the embodiment can randomly select the first preset number of device information as target device information; and selecting the characteristics corresponding to the target equipment information from the characteristic library as source characteristics.
That is, the generating unit 502 acquires the source feature by randomly selecting the target device information from the device information, so that randomness in acquiring the source feature can be improved, randomness of the generated feature policy is further improved, and the problem that the target feature is tampered due to the fixed feature policy is effectively avoided.
In addition, when the generating unit 502 selects the source feature corresponding to the device information from the feature library, for each device information, the generating unit may randomly select the feature corresponding to the device information in the feature library, and further use the selected result as the source feature; the generating unit 502 may randomly select a second preset number of features as the source features.
It is to be understood that the generating unit 502 may also select all features (system class features and/or so instruction features) corresponding to the device information from the feature library as source features.
When the generating unit 502 selects the feature corresponding to the target device information from the feature library as the source feature, all the features corresponding to the target device information may be used as the source feature, or for each target device information, the feature corresponding to the target device information in the feature library may be randomly selected, the selection result is used as the source feature, and the generating unit 502 may randomly select a third preset number of features as the source feature.
After selecting the source feature, the generating unit 502 generates a feature policy according to the selected source feature, where the feature policy is used to send the feature policy to the client for executing, so as to obtain a corresponding target feature; in addition, a corresponding relation exists between the feature strategy and the source feature generating the feature strategy, and the corresponding source feature can be determined according to the feature strategy.
When generating the feature policy according to the source features, the generating unit 502 may generate the feature policy according to all the contents included in each source feature, or may randomly select, for each source feature, the contents from the source features, and then generate the feature policy according to the randomly selected contents.
The feature policy generated by the generating unit 502 may be used for the client to obtain one or more source features in the terminal device where the client is located, or may be used for the client to obtain features such as parameters, modifiers, execution results, variable values, file names, types, modifiers, symbol names and the like corresponding to the one or more source features in the terminal device where the client is located.
After the generating unit 502 generates the feature policy according to the source feature, the first transmitting unit 503 transmits the feature policy to the client and receives the target feature transmitted by the client; the target features are features obtained by the client executing the feature policy.
After the first sending unit 503 receives the target feature sent by the client, the first processing unit 504 determines that the client is running in the cloud mobile phone, which may also be referred to as determining that the client is running in the cloud mobile phone environment, if it is determined that the target feature is inconsistent with the source feature of the generated feature policy.
The first processing unit 504 may compare the target feature sent by the client with the source feature and determine that the target feature is consistent with the source feature only if the target feature is the same as the source feature, or otherwise determine that the target feature is inconsistent with the source feature.
The apparatus 500 for cloud mobile phone identification applied to the server side of the present embodiment may further include a second processing unit 505, configured to execute the following: a list acquisition request is sent to a client, and the list acquisition request is used for the client to acquire an installation list of an application program in a cloud mobile phone running in the client; receiving an installation list sent by a client; and under the condition that the existence of the preset application program in the cloud mobile phone is determined according to the installation list, determining that the cloud mobile phone has cheating risk.
That is, the second processing unit 505 may further detect an application program of the cloud mobile phone where the client is running, so as to identify whether the cloud mobile phone has a cheating risk, and improve the identification effect of the cloud mobile phone, so that corresponding measures are taken to avoid the cheating behavior in advance.
After determining that the cloud mobile phone on which the client operates has the cheating risk, the second processing unit 505 may send a prompt message to the client to prompt the user to delete the cheating program in the cloud mobile phone, or directly send an operation stopping instruction to the client, so that the client stops operating in the cloud mobile phone.
Fig. 6 is a schematic diagram according to a sixth embodiment of the present disclosure. As shown in fig. 6, the cloud mobile phone identification apparatus 600 of the present embodiment is applied to a client, and includes:
an acquiring unit 601, configured to acquire device information;
a second sending unit 602, configured to send the device information to a server, receive a feature policy sent by the server, where the device information is used by the server to generate a feature policy;
the execution unit 603 is configured to execute the feature policy to obtain a target feature, and send the target feature to the server, where the target feature is used for comparing the server with a source feature to determine whether the client operates in a cloud mobile phone.
The device information acquired by the acquiring unit 601 includes at least one of vendor information, model information, ROM name, ROM version, system version, and buildld of the terminal device where the client is located.
The client of the present embodiment, after acquiring the device information by the acquiring unit 601, transmits the device information to the server by the second transmitting unit 602, and receives the feature policy transmitted by the server, where the feature policy is dynamically generated by the server according to the device information.
After the client in this embodiment receives the feature policy sent by the server by the second sending unit 602, the executing unit 603 executes the feature policy to obtain the target feature, and sends the target feature to the server, so that the server determines whether the client operates on the cloud mobile phone according to the target feature.
The apparatus 600 for cloud mobile phone identification applied to a client according to the present embodiment may further include a third processing unit 604, configured to perform: receiving a list acquisition request sent by a server side; acquiring an installation list of an application program in a cloud mobile phone where a client operates; and sending the installation list to a server side so as to be used for determining whether the cloud mobile phone has cheating risk or not by the server side.
In addition, after the third processing unit 604 sends the application installation list to the server, the third processing unit may also receive a prompt message sent by the server, or stop running an instruction.
In the technical scheme of the disclosure, the acquisition, storage, application and the like of the related user personal information all conform to the regulations of related laws and regulations, and the public sequence is not violated.
According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.
As shown in fig. 7, a block diagram of an electronic device is provided for a method of cloud mobile phone identification according to an embodiment of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 7, the apparatus 700 includes a computing unit 701 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 702 or a computer program loaded from a storage unit 708 into a Random Access Memory (RAM) 703. In the RAM703, various programs and data required for the operation of the device 700 may also be stored. The computing unit 701, the ROM702, and the RAM703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
Various components in device 700 are connected to I/O interface 705, including: an input unit 706 such as a keyboard, a mouse, etc.; an output unit 707 such as various types of displays, speakers, and the like; a storage unit 708 such as a magnetic disk, an optical disk, or the like; and a communication unit 709 such as a network card, modem, wireless communication transceiver, etc. The communication unit 709 allows the device 700 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The computing unit 701 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 701 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 701 performs the various methods and processes described above, such as the method of cloud handset identification. For example, in some embodiments, the method of cloud handset identification may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 708.
In some embodiments, part or all of the computer program may be loaded and/or installed onto device 700 via ROM702 and/or communication unit 709. When the computer program is loaded into RAM703 and executed by computing unit 701, one or more steps of the method of cloud handset identification described above may be performed. Alternatively, in other embodiments, the computing unit 701 may be configured to perform the method of cloud handset identification by any other suitable means (e.g., by means of firmware).
Various implementations of the systems and techniques described here can be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable cloud cell phone identified device such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a presentation device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for presenting information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service ("VirtualPrivate Server" or simply "VPS") are overcome. The server may also be a server of a distributed system or a server that incorporates a blockchain.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel, sequentially, or in a different order, provided that the desired results of the disclosed aspects are achieved, and are not limited herein.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.

Claims (15)

1. A cloud mobile phone identification method is applied to a server and comprises the following steps:
receiving equipment information sent by a client;
selecting source features corresponding to the equipment information from a feature library, and generating a feature strategy according to the source features;
the feature strategy is sent to the client, target features sent by the client are received, and the target features are features obtained by the client by executing the feature strategy;
and under the condition that the target characteristics are inconsistent with the source characteristics, determining that the client runs on a cloud mobile phone.
2. The method of claim 1, wherein the selecting source features from a feature library that correspond to the device information comprises:
randomly selecting the equipment information, and taking the selected result as target equipment information;
and selecting the characteristics corresponding to the target equipment information from the characteristic library as the source characteristics.
3. The method of claim 2, wherein the selecting, as the source feature, a feature corresponding to the target device information from the feature library comprises:
and randomly selecting the features corresponding to the target equipment information in the feature library, and taking the selected result as the source features.
4. The method of claim 1, further comprising,
after determining that the client runs on a cloud mobile phone, sending a list acquisition request to the client;
receiving an installation list sent by the client;
and under the condition that the preset application program exists in the cloud mobile phone according to the installation list, determining that the cloud mobile phone has cheating risk.
5. A cloud mobile phone identification method is applied to a client and comprises the following steps:
acquiring equipment information;
the device information is sent to a server side, the feature strategy sent by the server side is received, and the device information is used for the server side to generate the feature strategy;
executing the feature policy to obtain target features, and sending the target features to the server, wherein the target features are used for comparing the server with source features to determine whether the client operates in a cloud mobile phone;
wherein the server side performs the method of any of claims 1-4.
6. The method of claim 5, further comprising,
after the target feature is sent to the server, receiving a list acquisition request sent by the server;
Acquiring an installation list of an application program in a running cloud mobile phone;
and sending the installation list to the server side, wherein the installation list is used for determining whether the cloud mobile phone has cheating risk or not by the server side.
7. A cloud mobile phone identification device is applied to a server side and comprises:
the receiving unit is used for receiving the equipment information sent by the client;
the generating unit is used for selecting source features corresponding to the equipment information from the feature library and generating a feature strategy according to the source features;
the first sending unit is used for sending the feature policy to the client, receiving target features sent by the client, and executing the feature obtained by the feature policy for the target features by the client;
and the first processing unit is used for determining that the client runs on the cloud mobile phone under the condition that the target characteristic is inconsistent with the source characteristic.
8. The apparatus of claim 7, wherein the generating unit, when selecting the source feature corresponding to the device information from a feature library, specifically performs:
randomly selecting the equipment information, and taking the selected result as target equipment information;
And selecting the characteristics corresponding to the target equipment information from the characteristic library as the source characteristics.
9. The apparatus according to claim 8, wherein the generating unit, when selecting a feature corresponding to the target device information from the feature library as the source feature, specifically performs:
and randomly selecting the features corresponding to the target equipment information in the feature library, and taking the selected result as the source features.
10. The apparatus of claim 7, further comprising a second processing unit to perform:
after the first processing unit determines that the client runs on a cloud mobile phone, a list acquisition request is sent to the client;
receiving an installation list sent by the client;
and under the condition that the preset application program exists in the cloud mobile phone according to the installation list, determining that the cloud mobile phone has cheating risk.
11. A cloud mobile phone identification device is applied to a client and comprises:
an acquisition unit configured to acquire device information;
the second sending unit is used for sending the equipment information to a server side, receiving the characteristic strategy sent by the server side, and the equipment information is used for generating the characteristic strategy by the server side;
The execution unit is used for executing the feature policy to acquire target features, sending the target features to the server side, and comparing the target features with source features by the server side to determine whether the client side operates on a cloud mobile phone or not;
wherein the server side comprises the apparatus of any one of claims 7-10.
12. The apparatus of claim 11, further comprising a third processing unit to perform:
after an execution unit sends the target feature to the server side, receiving a list acquisition request sent by the server side;
acquiring an installation list of an application program in a running cloud mobile phone;
and sending the installation list to the server side, wherein the installation list is used for determining whether the cloud mobile phone has cheating risk or not by the server side.
13. 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 method of any one of claims 1-6.
14. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-6.
15. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any of claims 1-6.
CN202310386573.1A 2023-04-12 2023-04-12 Cloud mobile phone identification method and device, electronic equipment and readable storage medium Pending CN116506165A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310386573.1A CN116506165A (en) 2023-04-12 2023-04-12 Cloud mobile phone identification method and device, electronic equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310386573.1A CN116506165A (en) 2023-04-12 2023-04-12 Cloud mobile phone identification method and device, electronic equipment and readable storage medium

Publications (1)

Publication Number Publication Date
CN116506165A true CN116506165A (en) 2023-07-28

Family

ID=87323935

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310386573.1A Pending CN116506165A (en) 2023-04-12 2023-04-12 Cloud mobile phone identification method and device, electronic equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN116506165A (en)

Similar Documents

Publication Publication Date Title
CN109684188B (en) Test method and device
CN112328301B (en) Method and device for maintaining consistency of operating environments, storage medium and electronic equipment
CN113766487A (en) Cloud mobile phone information acquisition method, device, equipment and medium
CN114389969B (en) Method and device for testing client, electronic equipment and storage medium
CN114372256A (en) Application program running method, device, equipment and storage medium
CN113377381A (en) Method and device for distributing small program package, electronic equipment and medium
CN113220367A (en) Applet running method and device, electronic equipment and storage medium
CN115481594B (en) Scoreboard implementation method, scoreboard, electronic equipment and storage medium
CN116506165A (en) Cloud mobile phone identification method and device, electronic equipment and readable storage medium
CN114218166A (en) Data processing method and device, electronic equipment and readable storage medium
CN114138358A (en) Application program starting optimization method, device, equipment and storage medium
CN114301975B (en) Method, device, equipment and storage medium for processing push information in application
CN113961263B (en) Applet distribution method, device, apparatus and storage medium
CN114647578B (en) System testing method, device, equipment and storage medium
CN116738470B (en) User identity association method and device, electronic equipment and storage medium
CN113626409B (en) Test data processing method, device, equipment and storage medium
CN116436883A (en) Method, device, electronic equipment and readable storage medium for link transmission
CN116301992A (en) Upgrading method, device, equipment and storage medium
CN116302086A (en) Application processing method and device, electronic equipment and readable storage medium
CN116471268A (en) Delivery method and device of private cloud project, electronic equipment and readable storage medium
CN116991737A (en) Software testing method, system, electronic equipment and storage medium
CN116233051A (en) Page sharing method, device and equipment for applet and storage medium
CN117762462A (en) Code examination method, device, equipment and storage medium based on large model
CN115270672A (en) Verification method, device, equipment and storage medium of TCAM (ternary content addressable memory) encapsulation module
CN113713378A (en) Content generation method and device

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