A registration verification method and device and a storage medium

Abstract

A registration verification method and device and a storage medium are applied to the technical field of Internet security. The registration verification method performs local verification through an electronic device and cloud verification through a server. The electronic device sends a first request including first short message source information to the server in the case of triggering a first short message (a short message matching the first short message source information). The server verifies the short message information according to the first request and sends a first response to the electronic device in the case of passing the verification. Thus, the risk of false registration and malicious registration can be reduced by establishing an association relationship only according to application party declaration, and the accuracy, security and reliability of short message service configuration can be improved.

Description

Technical Field

[0001] This application relates to the field of Internet security technology, and in particular to a registration verification method, device and storage medium. Background Technology

[0002] With the development of smart terminals and mobile applications, users frequently receive short messages (or "SMS") related to an application while using it, such as verification code SMS, business notification SMS, or service application SMS. These SMS messages are usually sent by a specific SMS port, and the SMS body typically includes a message signature.

[0003] To display the application name, icon, or relevant access points of a specific application in the SMS interface, it's typically necessary to pre-establish a mapping between SMS ports, SMS signatures, and applications. This mapping usually relies on manual configuration and maintenance by operations staff. Due to the large number of applications, different applications may use different SMS ports and signatures. It's difficult for operations staff to verify the accuracy and authenticity of the reported SMS ports, signatures, and mappings for each application.

[0004] Therefore, how to verify the authenticity of the correspondence between the SMS port and SMS signature declared by the application and the application is a technical problem that urgently needs to be solved. Summary of the Invention

[0005] This application provides a registration verification method, apparatus, and storage medium, which can reduce the risk of applications arbitrarily or incorrectly declaring SMS source information and improve the security and reliability of the SMS service information verification process.

[0006] In a first aspect, this application provides a registration verification system, which includes an electronic device and a server. The electronic device is used to obtain first short message source information of a first application, and in response to an event occurring in the electronic device where the first application triggers the sending of a first short message, sends a first request to the server, wherein the first request includes the first short message source information. The server is used to receive the first request, verify the short message service information of the first application based on the first short message source information, and, if the verification is successful, send a first response to the electronic device, wherein the first response includes short message service information, or includes indication information indicating that the short message service information has been verified successfully. The short message service information includes second short message source information, both of which correspond to the first application. The short message service information is configuration information used by the electronic device to identify and process short messages related to the first application.

[0007] For example, the electronic device may be a tablet computer, personal computer, laptop computer, computer, in-vehicle computer, in-vehicle terminal, smartphone, smart wearable device (such as smart glasses), etc.

[0008] For example, the first short message is a short message that matches the source information of the first short message (i.e., the source information of the first short message is the source information of the first short message). This short message can be a message sent to the electronic device through a third-party service (such as a short message service provider). For example, application notification messages are usually sent directly by the application to the system of the electronic device, and then displayed by the system. Since such notification messages are not sent through a third-party service, they do not belong to the short messages in this embodiment.

[0009] For example, the first application can be an application or a meta-service; there is no limitation here. The first and second SMS source information can be the same or different; there is no limitation here. It is understood that "inconsistency" here usually refers to the different ports corresponding to the first and second SMS source information. The granularity of the representation used for the first and second SMS source information can be different; for example, the first SMS source information may include a port number, while the second SMS source information may be a number range. However, when the port number in the first SMS source information belongs to the number range in the second SMS source information, they can be considered the same.

[0010] For example, the SMS service information also includes at least one of the following: application name, application icon, menu information, and interactive control information, wherein the interactive control information is used to provide access to the first application.

[0011] In this way, since the first SMS source information is associated with the first event that triggers the sending of the SMS by the first application, the server can use the first request itself as evidence of the association between the first application and the SMS source when verifying the SMS service information of the first application based on the first SMS source information. That is, the first SMS source information provided by the first application does not solely originate from the first application's unilateral declaration, but is combined with the actual event that triggers the sending of the first SMS. This reduces the risk of the first application arbitrarily or incorrectly declaring the SMS source information, and improves the security and reliability of the SMS service information verification process.

[0012] In one possible implementation, the first request further includes risk control information, which includes device attribute information and / or network attribute information; in the process of the server verifying the short message service information of the first application based on the first short message source information in the received first request, it is specifically used to: verify the short message service information based on the first short message source information and risk control information in the first request.

[0013] For example, device attribute information includes the type of electronic device, and network attribute information includes the IP address information of the electronic device.

[0014] In this way, by carrying risk control information in the first request, the server can not only determine whether there is a connection between the first application and the first short message source based on the first short message source information when verifying the short message service information, but also determine whether there is a risk in the reporting environment of this first request by combining device attribute information and / or network attribute information, thereby improving the accuracy and security of the short message service information verification process.

[0015] For example, for a given application, if most of the electronic devices sending the first request to the server correspond to the same risky IP address, the server can determine that the application poses a risk of malicious or abnormal registration. Therefore, when verifying SMS service information, the server can combine risk control information to identify batch abnormal reporting behavior, thereby improving the security of the SMS service information verification process.

[0016] In one possible implementation, before sending the first request to the server, the electronic device is specifically configured to: determine whether the first short message is sent in response to a business request initiated by the first application in response to receiving the first short message; during the process of sending the first request to the server, the electronic device is specifically configured to: send the first request to the server if the first short message is sent in response to a business request initiated by the first application.

[0017] For example, the service request could be a verification code request or another request that triggers the sending of a short message.

[0018] In this way, the first request is not sent directly after the first application unilaterally declares the source information of the SMS message. Instead, it is confirmed by combining two events: the first application initiating a business request and the electronic device receiving the corresponding SMS message. This further eliminates the influence of SMS messages unrelated to the first application or accidentally received SMS messages on the registration verification process, giving the server a clearer basis for triggering the business request, thereby improving the credibility and security of the SMS service information verification process.

[0019] In one possible implementation, during the process of verifying the SMS service information of the first application based on the first SMS source information in the received first request, the server specifically performs the following steps: obtaining a cumulative value representing the progress of the SMS service information verification, the cumulative value being determined based on historical first requests used to verify the SMS service information; determining a risk coefficient based on the first SMS source information and / or risk control information in the first request; updating the cumulative value based on the risk coefficient; and verifying the SMS service information based on the updated cumulative value.

[0020] In this way, the server can make a comprehensive judgment based on the cumulative historical request data and the risk level of the current request. For requests with a high degree of trust, the cumulative value can be updated significantly; for requests with abnormal risks, the cumulative value can be updated less significantly, not at all, or negatively. This reduces the undue impact of a single abnormal request on the verification results and improves the accuracy of SMS service information verification.

[0021] In one possible implementation, the SMS service information included in the first response is encrypted and protected using a security key.

[0022] For example, the server is also used to send a security key to an electronic device; the electronic device is also used to decrypt the short message service information based on the security key after receiving the first response.

[0023] In this way, the security of the configuration distribution process can be improved through encryption.

[0024] In one possible implementation, whether the SMS service information is successfully verified depends on the number of first requests received by the server to request verification of the SMS service information.

[0025] In this way, when the number of first requests reaches a certain level, it can be shown that the association between the first application and the corresponding SMS source information has a certain degree of universality and stability, thereby improving the reliability of the SMS service information verification results.

[0026] Secondly, this application provides a registration verification method applied to an electronic device. The method includes: obtaining first short message source information of a first application; in response to an event occurring in the electronic device where the first application triggers the sending of a first short message, sending a first request to a server, wherein the first request includes the first short message source information, and the first request is used to request the server to verify the short message service information of the first application based on the first short message source information; receiving a first response from the server, the first response including short message service information, or including indication information indicating that the short message service information verification is successful, wherein the short message service information is configuration information used by the electronic device to identify and process short messages related to the first application.

[0027] In this way, since the first SMS source information is associated with the first event that triggers the sending of the SMS by the first application, the server can use the first request itself as evidence of the association between the first application and the SMS source when verifying the SMS service information of the first application based on the first SMS source information. That is, the first SMS source information provided by the first application does not solely originate from the first application's unilateral declaration, but is combined with the actual event that triggers the sending of the first SMS. This reduces the risk of the first application arbitrarily or incorrectly declaring the SMS source information, and improves the security and reliability of the SMS service information verification process.

[0028] Thirdly, this application provides a registration verification method applied to a server. The method includes: receiving a first request from an electronic device, the first request including first short message source information of a first application; responding to the first short message source information of the first request, verifying short message service information of the first application, the short message service information including second short message source information, both the second short message source information and the first short message source information corresponding to the first application; and if the short message service information verification is successful, sending a first response to the electronic device, the first response including short message service information, or including indication information indicating that the short message service information verification is successful, the short message service information being configuration information used by the electronic device to identify and process short messages related to the first application.

[0029] Fourthly, this application provides a registration verification device, including an acquisition module and a processing module. The acquisition module is used to acquire first short message source information of a first application. The processing module is used to send a first request to a server in response to an event occurring in an electronic device where the first application triggers the sending of a first short message. The first request includes the first short message source information and is used to request the server to verify the short message service information of the first application based on the first short message source information. The processing module receives a first response from the server. The first response includes short message service information or includes indication information indicating that the short message service information verification is successful. The short message service information is configuration information used by the electronic device to identify and process short messages related to the first application.

[0030] Fifthly, embodiments of this application provide an electronic device including a display screen, one or more processors, and a memory; the display screen is used to display a user interface, the one or more processors are coupled to the memory, and the one or more processors are used to read a computer program stored in the memory to execute the method provided in the second / third aspect. The computer program code includes computer instructions.

[0031] Sixthly, embodiments of this application provide a chip including a processor coupled to a memory. The processor is used to call computer program instructions stored in the memory during runtime to implement the methods provided in the second / third aspects above. Optionally, the chip may also include components such as a memory, a communication interface, and a power supply module. The memory is used to store computer programs; the communication interface is used to receive and send data; and the power supply module is used to supply power to the processor.

[0032] In a seventh aspect, embodiments of this application provide a computer storage medium storing computer program instructions that, when executed on an electronic device, cause the computer to perform the methods provided in the second / third aspects described above.

[0033] Eighthly, embodiments of this application provide a computer program product, which includes computer program instructions; when the computer program instructions are run on a computer, the computer performs the method provided in the second / third aspect.

[0034] It is understood that the beneficial effects of aspects two through eight above can be found in the relevant descriptions in aspect one above, and will not be repeated here. Attached Figure Description

[0035] Figure 1 This is a schematic diagram of a short message display interface provided in an embodiment of this application; Figure 2This is a schematic diagram of the overall process of a registration verification scheme provided in an embodiment of this application; Figure 3 This is a schematic diagram of the functional module interaction of an electronic device provided in an embodiment of this application; Figure 4 This is a flowchart illustrating a method for generating data to be authenticated provided in an embodiment of this application; Figure 5 This is a schematic diagram of the interaction flow of a target association authentication method provided in an embodiment of this application; Figure 6 This is a flowchart illustrating a method for determining a risk coefficient provided in an embodiment of this application; Figure 7 This is a schematic diagram illustrating the process of an electronic device using first configuration information according to an embodiment of this application; Figure 8 This is a schematic diagram illustrating the display effect of a short message list interface provided in an embodiment of this application; Figure 9 This is a schematic diagram of a cumulative score update process provided in an embodiment of this application; Figure 10 This is a schematic diagram of the functional module interaction of another electronic device provided in an embodiment of this application; Figure 11 This is a schematic diagram of the architecture of a registration verification system provided in an embodiment of this application; Figure 12 This is a schematic diagram of a registration verification device provided in an embodiment of this application; Figure 13 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0036] First, the relevant technical terms involved in the technical solution provided in this application will be introduced.

[0037] (1) Application (APP): is a software program that runs on devices such as mobile phones and computers to provide users with specific functions, such as chatting, navigation, taking pictures or playing music.

[0038] (2) Application package name: This is a unique identifier set by the developer for the application, usually in the form of com.xxx.xxx in Android, used by the system to identify and distinguish different applications. The application also has an application name. The application name is different from the application package name. It usually refers to the display name that the user sees on the desktop, in the store or settings, such as "XX Map" or "XX App Market". It is more focused on the name shown to the user and has a different function than the package name.

[0039] (3) Meta-service: This is a lightweight application form that can be deployed to electronic devices without the traditional application installation method. Instead, it can be triggered and used through system-provided entry points, cards, search results, scene recommendations, or other service entry points. Meta-services can be used to provide users with one or more relatively independent service functions. Compared with traditional applications, meta-services usually have the characteristics of being installation-free, lightweight, and ready to use and then gone. However, they can still participate in the service invocation, information display, or business processing of electronic devices as a service provider.

[0040] (4) Metaservice foundation: refers to the basic components, framework components or system services in electronic devices that support the operation, management or access to the system of metaservices.

[0041] In this article, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The symbol " / " in this article indicates that the related objects are in an "or" relationship; for example, A / B means A or B.

[0042] The terms "first" and "second," etc., used in the specification and claims herein are used to distinguish different objects, not to describe a specific order of objects. For example, "first response message" and "second response message," etc., are used to distinguish different response messages, not to describe a specific order of response messages.

[0043] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0044] In the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more, for example, multiple processing units means two or more processing units, multiple elements means two or more elements, etc.

[0045] The technical solution provided in this application will now be described in detail with reference to the accompanying drawings.

[0046] With the development of smart terminals and mobile applications, users frequently receive short messages related to an application while using it. For example, when a user logs into an application, obtains a verification code, inquires about business information, or conducts business, the service provider corresponding to the application may send a short message to the user's terminal. These short messages are usually sent through a specific short message port, and the message body typically includes a short message signature.

[0047] The SMS port refers to the service port used by the SMS sender to send SMS messages. For example, the SMS port can be a service number used by an operator, merchant, or SMS service platform. The SMS signature (sign) is a field in the SMS body used to identify the merchant, organization, or business provider. For example, content appearing in the form of "【】" in the SMS body can serve as the SMS signature.

[0048] like Figure 1 As shown in (A), in a typical SMS message, the SMS interface usually displays the SMS port and the SMS body. The SMS body can include the SMS signature and the specific SMS content. For example, the SMS port can be displayed as "1234", and the SMS body can display the SMS signature "[Service A]".

[0049] and Figure 1 Unlike (A) in the previous example, in some SMS display scenarios (or intelligent display scenarios), electronic devices can also parse the received SMS messages and determine the corresponding application based on the SMS port and SMS signature. Then, the application name, application icon, or related operation entry points can be displayed on the SMS interface. Therefore, the SMS interface no longer only displays the SMS port and SMS text, but can also provide further information based on the corresponding application.

[0050] like Figure 1 As shown in (B), in the smart SMS display scenario, the SMS interface can display application icons, application names, and one or more operation buttons. For example, the top of the SMS interface can display the application icon and application name of the corresponding application, the "Pay Bill" operation button can be displayed in the SMS, and the bottom of the SMS interface can display operation buttons such as "Recharge," "Check Balance," and "Customer Service." Users can trigger services related to the SMS content through these operation buttons, thereby reducing the operational cost of manually switching between the SMS interface and the application.

[0051] In order to achieve Figure 1The display effect shown in (B) typically requires a pre-established correspondence between SMS ports, SMS signatures, and applications. In other words, the system needs to determine which application corresponds to a specific SMS port and SMS signature, and which application name, icon, or navigation entry should be displayed in the SMS interface. Only when this correspondence exists can the electronic device, upon receiving an SMS, query the corresponding application based on the SMS port and SMS signature, and display the application name, icon, or relevant navigation entry in the SMS interface.

[0052] However, SMS ports and signatures are typically authorized by the mobile operator (i.e., the SMS service provider) to application developers, and applications are usually managed by the application developers. There is no inherent, mandatory binding relationship between SMS ports, SMS signatures, and applications. In other words, although electronic devices can obtain the SMS port and signature from the SMS message itself, they cannot determine which application the SMS message should correspond to, nor can they determine which application icon, application name, or redirection should be displayed solely based on the SMS message itself.

[0053] Therefore, in Figure 1 In the technology shown in (B), the correspondence between SMS port, SMS signature, and application typically relies on manual configuration by the SMS app's operators. For example, operators can configure the corresponding application information for a specific SMS port and SMS signature in the SMS app's management platform. After receiving an SMS, the electronic device queries the cloud or retrieves the corresponding application information from the local configuration based on the SMS port and SMS signature, and then displays it on the SMS interface.

[0054] The above method can achieve this. Figure 1 The enhanced display shown in (B) relies on manual configuration of the correspondence between SMS ports, SMS signatures, and applications. Due to the large number of applications, different applications may use different SMS ports and different SMS signatures. Therefore, maintaining this correspondence manually is inefficient, has limited coverage, and is difficult to cover a large number of applications and SMS service scenarios in a timely manner.

[0055] Furthermore, allowing applications to configure SMS ports and SMS signatures within the system can easily lead to mis-registration or malicious registration. For example, a malicious application might claim a correspondence between itself and others' SMS ports and signatures, causing electronic devices to mistakenly associate SMS messages with the malicious application, resulting in security risks such as incorrect information display, misuse of redirect links, or user misguidance.

[0056] In view of this, this application provides a technical concept for security verification that can reliably verify the association between SMS port, SMS signature, and application while reducing manual configuration costs. This approach improves the automation level of SMS enhancement display configuration and ensures the reliability of the association between SMS source information and application during automated configuration, reducing the risks of mis-registration or malicious registration.

[0057] Figure 2 This is a schematic diagram illustrating a security verification technical concept provided in an embodiment of this application. For example... Figure 2 As shown, this technical concept may include a local verification part, a cloud verification part, and a first configuration information usage part (not shown in the figure). The local verification part is mainly used to perform preliminary verification of the registration request initiated by the application on the electronic device 202 side, and generate authentication data if the local verification is successful. The cloud verification part is mainly used by the server 201 to verify the association between the application and the SMS source information based on the authentication data (or "first request") reported by multiple electronic devices 202, and issue the first configuration information if the verification is successful. The first configuration information usage part is mainly used to save and use the first configuration information on the electronic device 202 side to display the application information corresponding to the SMS in the SMS interface. For ease of explanation, the above parts are described below.

[0058] 1) Local verification section

[0059] In this embodiment, the electronic device 202 may send authentication data to the server 201 if it confirms that the first short message (the short message that matches the source information of the first short message) was triggered by the first application. Optionally, the electronic device 202 may further determine whether to send authentication data to the server 201 based on whether the trusted source information of the first application (such as the installation source) and / or the source information of the first short message belongs to a risky short message.

[0060] Below, in conjunction with Figure 3 and Figure 4 The local verification part is illustrated by example.

[0061] Figure 3 This is a schematic diagram illustrating the interaction of functional modules in an electronic device. For example... Figure 3 As shown, the electronic device 202 may include a first application, an association management module 301, an application information management module 302 (optional), a historical behavior management module 303, a short message processing module 304, a trusted storage module 305, and an association display module 306.

[0062] exist Figure 3The document describes the flow of information between different modules. Specifically, the first application can send a registration request to the association management module 301. The association management module 301 can obtain the application identifier information and trusted source information of the first application from the application information management module 302. If the trusted source information meets the trusted source conditions, it generates a first association relationship based on the first short message source information (short message port and short message signature) and the application identifier information in the registration request. Subsequently, the association management module 301 can save the first association relationship to the trusted storage module 305. After receiving a short message, the short message processing module 304 can provide the short message port and short message signature of the short message to the association management module 301. The association management module 301 can access the trusted storage module 305 to query whether a first association relationship matching the short message port and short message signature exists. If a matching first association relationship exists, the association management module 301 can obtain the historical behavior information of the corresponding application through the historical behavior management module 303 and determine whether the short message was triggered by the first application based on the historical behavior information. If the message is determined to be triggered by the first application, the association management module 301 can generate authentication data and report it to the server 201. After successful authentication by the server 201, the server can return or send the first configuration information to the association management module 301, which can then save the first configuration information to the trusted storage module 305. The association display module 306 can query the first configuration information in the trusted storage module 305 and provide application display information or application redirection entry based on the first configuration information.

[0063] Figure 4 This is a flowchart illustrating a method for generating data to be authenticated. Figure 4 The process steps and Figure 3 The information flow between modules corresponds to the information flow between them. Figure 4 This is used to further explain the process of generating the data to be authenticated and the collaborative relationship between the modules.

[0064] like Figure 4 As shown, in S401, the association management module 301 receives a registration request from the first application.

[0065] For example, a registration request refers to a request from a first application to establish its association with the first short message source information. The first short message source information refers to the short message source information corresponding to the first application carried in the registration request. Short message source information refers to features that can be used to characterize the source of a short message transmission or the source of a short message service. Typically, the first short message source information includes the short message port and the short message signature.

[0066] As one possible implementation, the registration request may include the first SMS source information. In this implementation, the first application can pre-obtain the SMS port and SMS signature corresponding to its own business. The SMS port and SMS signature can be pre-installed in the first application, or they can be obtained by the first application from the corresponding application server; this is not limited here.

[0067] As one possible implementation, such as Figure 2 As shown, a registration request can be initiated when the first application meets preset triggering conditions. For example, the preset triggering conditions may include at least one of the following: the first application is installed, the first application is opened, the first application requests the user to grant a first permission, or the user agrees to grant the first permission to the first application.

[0068] For example, after a user downloads and installs a first application, the first application can request the user to configure SMS settings. The first permission could be the permission for the electronic device 202 to display the application name, application icon, or application navigation entry point in the SMS interface based on authentication configuration information. If the user agrees to grant this first permission, the first application can initiate a registration request to the electronic device 202.

[0069] In S402, the association management module 301 obtains the application identification information and trusted source information of the first application from the application information management module 302.

[0070] In this embodiment, the application information management module 302 is mainly used to provide application-related information.

[0071] For example, trusted source information refers to information used to determine whether the source of the first application is trusted. Trusted source information may include at least one of installation source information, application signing certificate information, and developer information. The application identification information may include the application package name of the first application, or other information that can identify the application.

[0072] As one possible implementation, the association management module 301 can obtain the application package name of the first application through the remote call framework in the electronic device 202. Thus, it can obtain the application identification information of the first application from the system environment.

[0073] In S403, the association management module 301 determines whether the trusted source information of the first application meets the trusted source conditions.

[0074] As one possible implementation, the trusted source conditions may include the first application coming from a preset application market, the first application being a pre-installed application on the system, the application signature certificate of the first application being verified, and the first application belonging to at least one of the preset trusted application sets.

[0075] If the first application does not meet the trusted source criteria, the association management module 301 rejects the registration request. For example, if the first application is not from the preset application market, the registration request can be rejected.

[0076] If the first application meets the trusted source criteria, proceed to step S404.

[0077] In S404, the association management module 301 further determines whether the source information of the first short message in the registration request falls within the scope of risky short messages.

[0078] For example, the scope of risky SMS messages refers to the range of SMS messages identified as posing a harassment, fraud, impersonation, or other security risks. As one possible implementation, the scope of risky SMS messages may include harassment SMS ports, fraudulent SMS ports, blacklisted SMS signatures, or other SMS messages marked as risky.

[0079] If the source information of the first short message falls within the scope of risky short messages, the association management module 301 rejects this registration request. If the source information of the first short message does not fall within the scope of risky short messages, then proceed to S405.

[0080] In S405, the association management module 301 generates a first association relationship based on the application identification information of the first application and the first short message source information, and saves the first association relationship to the trusted storage module 305.

[0081] In this embodiment, the first association relationship is the association relationship between the first application and the first SMS source information. Specifically, the association management module 301 can save the application identifier information of the first application and the corresponding information of the first SMS source to obtain the first association relationship.

[0082] In this embodiment, the trusted storage module 305 refers to the storage area in the electronic device 202 used for securely storing data. As one possible implementation, the trusted storage module 305 can be a trusted application area in a trusted execution environment, or it can be other secure storage areas with access control capabilities.

[0083] For example, the trusted storage module 305 can be used to store the first association relationship and the first configuration information issued by the server 201. The first association relationship refers to an association relationship generated by the electronic device 202 based on information submitted by the first application, which has not yet been authenticated by the server 201.

[0084] After the first association is generated, it is not directly used as the first configuration information. That is, the electronic device 202 will not determine a credible correspondence between the first application and the first SMS source information based solely on a single registration request from the first application. To further improve the accuracy of the association, the electronic device 202 can also perform historical behavior verification on the first association after receiving a target SMS.

[0085] In S406, the short message processing module 304 receives a short message and determines whether the received short message is the target short message based on the short message port and short message signature of the received short message.

[0086] The target short message refers to the short message received by the electronic device 202, whose short message port and short message signature are consistent with the first short message source information in the first association relationship.

[0087] In this embodiment, the short message processing module 304 refers to a functional module used to receive short messages and parse short message-related information. The short message processing module 304 can obtain the short message port and short message signature from the received short message. The association management module 301 can query the trusted storage module 305 for the existence of matching first short message source information based on the short message port and short message signature provided by the short message processing module 304. If no first short message source information is found, it means that the short message is not the target short message, and the electronic device 202 can process the short message according to the default short message processing method, or continue to judge other short messages received subsequently. If matching first short message source information is found, it means that the short message is the target short message, and the association management module 301 can determine the corresponding application identification information based on the matched first short message source information and proceed to S407.

[0088] In S407, in response to the received short message being the target short message, the association management module 301 queries the historical behavior information of the first application within a preset time window.

[0089] In this embodiment, the association management module 301 can query the historical behavior information of the first application through the historical behavior management module 303.

[0090] For example, the historical behavior management module 303 refers to a functional module used to record or query application usage behavior. Historical behavior information refers to information used to describe whether the first application has been actually used by the user.

[0091] For example, historical behavior information may include one or more historical behaviors of the first application within a preset time window. Historical behavior refers to behavioral events that reflect the user's actual use of the first application. For example, historical behavior may include at least one of the following: application launch event, application foreground running event, application background running event, application in task list event, and user interaction event.

[0092] For example, a preset time window refers to a time range set based on the time the target SMS message is received. For instance, the preset time window could be one minute, three minutes, or five minutes before the time the target SMS message is received.

[0093] In S408, the association management module 301 determines whether the target SMS message was triggered by the first application.

[0094] As one possible implementation, if the first application's historical behavior exists within a preset time window, the target SMS message can be considered to have been triggered by the first application. If the first application's historical behavior does not exist within the preset time window, the target SMS message can be considered not to have been triggered by the first application. In this case, the first association relationship may be at risk of misregistration or malicious registration.

[0095] Furthermore, the association management module 301 can determine whether there are historical behaviors matching a preset behavior type within a preset time window. This preset behavior type may include at least one of foreground running events, startup events, user interaction events, etc. If there are historical behaviors matching the preset behavior type of the first application within the preset time window, the target SMS message can be considered to have been triggered by the first application. If there are no historical behaviors matching the preset behavior type of the first application within the preset time window, the target SMS message can be considered not to have been triggered by the first application.

[0096] If the target SMS message is determined not to have been triggered by the first application, the association management module 301 may delete the first association relationship or mark the first association relationship as invalid, and may not generate authentication data based on the first association relationship.

[0097] If it is determined that the target SMS message was triggered by the first application, then proceed to S409.

[0098] In S409, the association management module 301 determines that the first association relationship has passed local verification and generates data to be authenticated based on the first association relationship.

[0099] The data to be authenticated is used by server 201 to determine whether the association between the first application and the first SMS source information is trustworthy. The data to be authenticated may include application identification information and risk information. Risk information may include at least one of the following: the model information of the electronic device 202 and network address information. Of course, the data to be authenticated may also include the first SMS source information.

[0100] Furthermore, the data to be authenticated may also include the application icon and / or application name. Of course, this data may also include other data used to generate the first configuration information, such as menu information, interactive control information, etc., which are not limited here. The interactive control information is used to provide access to the first application.

[0101] After the association management module 301 generates the data to be authenticated, it can report the data to the server 201. Subsequently, the server 201 can, in accordance with the method described below in conjunction with the cloud verification section, statistically analyze the data to be authenticated reported by multiple electronic devices 202, verify the credibility of the target association relationship corresponding to the first application, and generate the first configuration information if it is verified as credible.

[0102] 2) Cloud verification section

[0103] In this embodiment, server 201 verifies the target association relationship based on the data to be authenticated. If the verification is successful, it sends out first configuration information. This target association relationship is the association relationship determined by server 201 for the first application. This target association relationship characterizes the association relationship between the first application and the second SMS source information. Optionally, server 201 can also verify the target association relationship based on risk information in the data to be authenticated.

[0104] Specifically, the cloud verification component involves the interaction between server 201 and multiple electronic devices 202. Server 201 receives authentication data reported by multiple electronic devices 202 and authenticates and manages target associations based on this authentication data.

[0105] For ease of explanation, the following description uses the first application as an example. The authentication data reported by multiple electronic devices 202 can be understood as authentication data corresponding to the first application. The server 201 can aggregate this authentication data and determine whether the association between the first application and its corresponding SMS source information meets the authentication conditions.

[0106] The following is combined with Figure 5 The authentication process for server 201 is explained.

[0107] In S501, server 201 receives the authentication data corresponding to the first application and determines the target association.

[0108] For example, the second SMS source information includes at least an SMS port and / or the corresponding SMS sending number segment. The SMS sending number segment is used to determine the number to which the SMS belongs. Further, the second SMS source information may also include an SMS signature.

[0109] As one possible implementation, the target association can be obtained by server 201 based on the first piece of data to be authenticated corresponding to the first application. For example, when electronic device 202 first sends the data to be authenticated to server 201, server 201 can determine whether the first application corresponding to the data already has a corresponding target association authentication record. If not, the second SMS source information can be determined from the first piece of data to be authenticated, and the target association can be confirmed. For example, the first SMS source information in the first piece of data to be authenticated can be used as the second SMS source information to determine the target association.

[0110] As another possible implementation, the target association can be selected by server 201 from multiple pieces of data to be authenticated. For example, the short message source information with the largest proportion among the multiple pieces of data to be authenticated can be used as the second short message source information to determine the target association.

[0111] Furthermore, server 201 can perform authentication judgment on the target association corresponding to the first application after receiving a certain number of data to be authenticated. For example, after receiving m data to be authenticated, S502 is executed, where m is a positive integer, such as 300. Of course, server 201 can also perform a judgment on the target association corresponding to the first application after receiving each data to be authenticated; this is not limited here.

[0112] In S502, server 201 determines the corresponding risk coefficient K for each piece of data to be authenticated. i .

[0113] For example, the risk coefficient K i This is used to indicate the degree of influence of the corresponding data to be certified on the credibility of the target association.

[0114] As one possible implementation method, the risk factor K i The range can be any value within [-1, 1]. It is understandable that when the risk coefficient K... i When the value is positive, it indicates that the corresponding data to be certified contributes positively to the cumulative score of the target association; when the risk coefficient K is positive, it indicates that the data to be certified contributes positively to the cumulative score of the target association. iWhen a negative value is taken, it indicates that the corresponding data to be certified has a negative impact on the cumulative score of the target association.

[0115] Next, we will determine the risk coefficient K of the data to be certified, A. A (K of the data to be authenticated A) i Called K A Taking ) as an example, combined with Figure 6 S502 will be explained.

[0116] exist Figure 6 In this process, the risk coefficient K corresponding to the data to be certified can be determined through S601-S604. A .

[0117] In S601, server 201 obtains the target association relationships from each application and stores them in the database.

[0118] For example, the database stores SMS source information for each application.

[0119] In S602, server 201 determines one or more candidate application identifiers from the database based on the first short message source information in the data to be authenticated A.

[0120] For example, server 201 can use the first short message source information in the data to be authenticated A as a query condition to query the database for candidate application identifier information corresponding to the first short message source information.

[0121] In S603, server 201 determines whether one or more candidate application identification information includes the application identification information in the data to be authenticated A.

[0122] For example, if one or more candidate application identification information does not include the application identification information in the data to be authenticated A, it means that the application in the data to be authenticated A is inconsistent with the registration information recorded on the server 201 side. In this case, the data to be authenticated A may have risks such as misregistration or fraudulent registration.

[0123] In this case, server 201 can determine that the data to be authenticated A has a negative impact on the target association, and will set the risk coefficient K corresponding to the data to be authenticated A as follows: i=A Determined to be a negative value, such as K A =-1.

[0124] If one or more candidate application identification information includes the application identification information in data A to be authenticated, it means that the application identification information in data A to be authenticated is consistent with the target association recorded by server 201. In this case, server 201 can further determine the risk coefficient K corresponding to data A to be authenticated based on the risk information in data A to be authenticated. AExecute S604.

[0125] In S604, server 201 determines the risk coefficient K of the data to be authenticated A based on the risk information in the data to be authenticated A. A .

[0126] For example, server 201 can determine risk factor K based on one or more of the model information or network address information of electronic device 202. A In one possible implementation, data to be authenticated from high-risk aircraft models and high-risk regions can be assigned a low or even negative risk coefficient K. A For data awaiting authentication from low-risk aircraft models and low-risk regions, a higher risk coefficient K can be assigned. A .

[0127] For example, if the risk information of the data to be authenticated, A, indicates that the data to be authenticated, A, comes from a low-risk environment and a low-risk machine model, then server 201 can assign a risk coefficient K. i=A The value is determined to be relatively high; for example, the risk coefficient at this point can be determined to be K. A =1. If the risk information of the data to be authenticated, A, indicates that the data to be authenticated, A, comes from a high-risk environment and a high-risk machine model, then server 201 can assign a risk coefficient K. A The value is determined to be relatively low; for example, the risk coefficient can be determined to be K. A =-0.7.

[0128] In S503, server 201 calculates the cumulative score.

[0129] In this embodiment, server 201 can determine the cumulative score of the target association based on the risk coefficient Ki corresponding to each piece of data to be authenticated. For example, the cumulative score is used to characterize the overall credibility of the target association.

[0130] For example, cumulative score It can be determined using formula (1): (1) in, This is the base score, representing the initial score of the target association. The single-report weight represents the basic contribution of a piece of data to the cumulative score. Since the risk coefficient Ki can be positive or negative, the data to be certified may either increase or decrease the cumulative score.

[0131] In formula (1), the cumulative score of the target association is determined based on the risk coefficient Ki of m pieces of data to be certified.

[0132] In S504, server 201 determines whether the cumulative score has reached the preset threshold.

[0133] In this embodiment, the preset threshold can be a score threshold pre-set on the server 201 side, used to determine whether the target association has the basic credibility to be certified as a trustworthy association.

[0134] If the cumulative score does not reach the preset threshold, it indicates that the credibility of the current target association is still insufficient. At this time, server 201 can keep the target association in a pending authentication state and continue to receive pending authentication data reported by subsequent electronic devices 202 to further update the cumulative score.

[0135] If the cumulative score reaches the preset threshold, it means that the target relationship has met the authentication conditions and enters S505.

[0136] In S505, server 201 issues the first configuration information.

[0137] In this embodiment, the first configuration information refers to the configuration data generated by the server 201 after the target association meets the authentication conditions, which can be used by the electronic device 202. The first configuration information can be used to enable the electronic device 202 to determine the correspondence between the first application and the SMS source information.

[0138] For example, the first configuration information may include application identification information and second SMS source information.

[0139] As mentioned above, the second SMS source information may include the SMS port and / or the SMS sending number range. It may also include the SMS signature.

[0140] In one possible implementation, the second SMS source information includes a specified SMS port, and the first configuration information can be used to indicate an association between the first application and the specified SMS port. In another possible implementation, the second SMS source information includes a specified SMS sending number segment, and the first configuration information can be used to indicate an association between the first application and the specified SMS sending number segment. In yet another possible implementation, the second SMS source information includes a specified SMS port and a specified SMS signature, and the first configuration information can be used to indicate an association between the first application and the specified SMS port and the specified SMS signature.

[0141] In some embodiments, after generating the first configuration information, the server 201 can provide the first configuration information to the electronic device 202. The server 201 provides the first configuration information in the following manner: 1) Server 201 sends the first configuration information to all electronic devices 202 that have reported data to be authenticated. In this embodiment, server 201 can send first configuration information to electronic devices 202 that have reported authentication data corresponding to the first application. That is, server 201 can send the first configuration information to electronic devices 202 participating in the target association authentication process, enabling these electronic devices 202 to update their configurations based on the first configuration information.

[0142] 2) Server 201 sends first configuration information to electronic device 202 with the first application.

[0143] In this embodiment, the server 201 may also send the first configuration information to the electronic device 202 with the first application. The electronic device 202 with the first application is an electronic device that has the first application installed.

[0144] Furthermore, to enhance the security of the first configuration information during transmission, server 201 can encrypt the first configuration information and send the encrypted first configuration information to electronic device 202. For example, server 201 can encrypt the first configuration information using a pre-agreed symmetric key with electronic device 202. After receiving the encrypted first configuration information, electronic device 202 can store it in a trusted storage area (i.e., Figure 3 The trusted storage module 305 in the middle uses the corresponding symmetric key to decrypt and saves the first configuration information obtained by decryption in the trusted storage area.

[0145] For example, the symmetric key can be obtained through a key negotiation process between server 201 and electronic device 202. For instance, the trusted execution environment in electronic device 202 can generate a key pair and provide public key information to server 201; server 201 can encrypt the symmetric key based on this public key information and send the encrypted symmetric key; after receiving the encrypted symmetric key, the trusted execution environment in electronic device 202 decrypts it and saves it. Subsequently, server 201 can use the symmetric key to encrypt the first configuration information, and electronic device 202 can use the saved symmetric key to decrypt the first configuration information.

[0146] In some embodiments, unlike S505, in this embodiment, the electronic device 202 obtains the first configuration information itself, and the content sent by the server 201 is indication information. This indication information is used to indicate that the first configuration information is trustworthy. For example, the electronic device 202 can also obtain configuration information such as the application icon and application name corresponding to the first application from locally pre-saved configurations, the application server corresponding to the first application, or a preset configuration interface to obtain the first configuration information. After receiving the indication information sent by the server 201, the electronic device 202 can save or enable the first configuration information as a trustworthy configuration.

[0147] Afterwards, once the electronic device 202 obtains and saves the first configuration information, it can determine the first application corresponding to the target short message based on the first configuration information. For example, when the electronic device 202 receives a short message that matches the second short message source information in the first configuration information, it can determine that the short message corresponds to the first application based on the first configuration information, and display the application name and application icon of the first application in the short message interface, or provide an entry point to jump to the first application.

[0148] Using the above method, server 201 can determine the credibility of the target association between the first application and the second SMS source information based on the authentication data reported by multiple electronic devices 202 and the corresponding risk coefficient Ki, and generate first configuration information after the cumulative score reaches a preset threshold. Furthermore, server 201 can provide the first configuration information to the electronic device 202 with the first application, enabling the electronic device 202 to display SMS messages and redirect to applications based on the first configuration information. Encrypting the transmission of the first configuration information also reduces the risk of it being tampered with, forged, or illegally obtained during the distribution process.

[0149] 3) First configuration information usage section

[0150] The following is combined with Figure 7 The process of using the first configuration information in electronic device 202 will be explained.

[0151] In S701, the association management module 301 receives and stores the first configuration information.

[0152] In this embodiment, the electronic device 202 can receive the first configuration information actively sent by the server 201.

[0153] After obtaining the first configuration information, the electronic device 202 can store the first configuration information in the trusted storage module 305 through the association management module 301. The first configuration information may include at least one or more of the following: application name, application icon, and target association relationship.

[0154] In some implementations, server 201 can send encrypted first configuration information to electronic device 202. After receiving the encrypted first configuration information, association management module 301 can decrypt the encrypted first configuration information in trusted storage module 305 and save the decrypted first configuration information to trusted storage module 305.

[0155] In S702, the associated display module 306 obtains the first configuration information and displays the application information of the first application in the short message interface.

[0156] In this embodiment, after the association management module 301 saves the first configuration information to the trusted storage module 305, the association display module 306 can query the first configuration information in the trusted storage module 305 during the display of the short message interface. Specifically, the association display module 306 can query whether the corresponding first configuration information exists in the trusted storage module 305 based on the short message port, short message signature, or short message sending number segment.

[0157] If the corresponding first configuration information is found, the association display module 306 can determine the first application corresponding to the short message based on the first configuration information, and display the application information of the first application in the short message interface. The application information may include the application name and / or application icon of the first application.

[0158] For example, such as Figure 8 As shown, the left-hand interface displays a short message list without using the first configuration information. In this interface, short messages are mainly displayed using information such as the short message port, short message signature, and short message body. The right-hand interface displays a short message list with the first configuration information. The electronic device 202 can query the first configuration information based on the short message port and short message signature. If the corresponding first configuration information is found, the electronic device 202 determines the first application corresponding to the short message based on the first configuration information, and then displays the application icon and application name of the first application in the short message list interface. For short messages for which no corresponding first configuration information is found, the electronic device 202 can continue to display the short message port, short message signature, or short message content in the default manner.

[0159] Furthermore, such as Figure 1As shown in (B), in the SMS details interface, the associated display module 306 can also display the application name and / or application icon of the first application based on the first configuration information, and can generate an application jump entry based on the application package name in the first configuration information. The application jump entry may include a jump button or a function button. After the user triggers the application jump entry, the electronic device 202 can launch the first application based on the application package name, or jump to the page corresponding to the first application.

[0160] It should be noted that the process of displaying the application name and icon by the association display module 306 is not limited to the moment when the electronic device 202 receives a short message. For example, the association display module 306 can display the short messages in the short message interface based on the saved first configuration information after the user opens the short message list interface, enters the short message details interface, refreshes the short message interface, or the electronic device 202 obtains new first configuration information.

[0161] Furthermore, the following is combined with Figure 9 The process of calculating the cumulative score of server 201 based on formula (1) is illustrated by example.

[0162] like Figure 9 As shown, server 201 can first set a base score for the target association. For example, base score It can be 100. Each time server 201 receives authentication data corresponding to the first application, it can determine the risk coefficient Ki and the single-report weight based on the authentication data. Determine the bonus points corresponding to the data to be certified this time, and update the cumulative score W based on the bonus points.

[0163] For example, server 201 can report weights in a single instance. Set to 20. If the risk coefficient K corresponding to a certain piece of data to be authenticated... i If the value is 0.8, then the bonus for this authentication data can be 20 × 0.8 = 16. Therefore, with an initial cumulative score of 100, after receiving the first authentication data, server 201 can update the cumulative score to 116; after receiving the second authentication data, it can continue to update the cumulative score to 132.

[0164] If the authentication data received by server 201 contains conflicting data (i.e., the first SMS source information is inconsistent with the second SMS source information), then the risk coefficient K corresponding to this authentication data can be changed. iThe value is determined to be negative. For example, in the third report, if the first SMS source information received in the data to be authenticated is inconsistent with the second SMS source information determined by server 201 for the target association, it indicates that the data to be authenticated may not match the target association, and there is a risk of false registration, impersonation registration, or abnormal reporting. In this case, server 201 can assign a risk coefficient K to the data to be authenticated. i The score is set to -1. Therefore, the score for this data to be certified is 20 × (-1) = -20, and the cumulative score can be updated from 132 to 112.

[0165] Similarly, if the data to be authenticated reported in the 4th and 5th reports are also conflicting data, then server 201 can also determine the corresponding risk coefficient Ki as -1, and update the cumulative score from 112 to 92 and from 92 to 72 respectively. It can be seen that formula (1) can increase the cumulative score of data to be authenticated that is consistent with the target or has a low risk, and decrease the cumulative score of data to be authenticated that is inconsistent with the target or has a high risk, thereby judging whether the target relationship is credible based on the cumulative results of multiple data to be authenticated.

[0166] Subsequently, after each update of the cumulative score, server 201 can compare the updated cumulative score W with a preset threshold. If the cumulative score W reaches the preset threshold, server 201 can determine that the target association meets the authentication conditions and execute S505 to generate and send the first configuration information. If the cumulative score W does not reach the preset threshold, server 201 can continue to keep the target association in a pending authentication state and continue to update the cumulative score based on subsequently received pending authentication data.

[0167] Furthermore, the security verification scheme provided in this application embodiment can also be applied to meta-service scenarios. The following, in conjunction with... Figure 10 This section explains the registration and verification process in the context of meta-services.

[0168] like Figure 10 As shown, the electronic device 202 may include a first meta-service, a meta-service base, an association management module 301, an application information management module 302, a historical behavior management module 303, a short message processing module 304, a trusted storage module 305, and an association display module 306. Among these, Figure 10 The historical behavior management module 303, SMS processing module 304, trusted storage module 305, and related display module 306 can be referenced. Figure 3 The relevant descriptions of the corresponding modules are not repeated here.

[0169] exist Figure 10In this context, the first-element service does not need to be pre-installed on the electronic device 202. The developer of the first-element service can provide a configuration file in a preset format within the application package of the first-element service. This configuration file can be used to specify the SMS port, SMS signature, and application identification information corresponding to the first-element service. For example, the configuration file may include the application identification information of the first-element service and configuration items for the first SMS source information.

[0170] The meta-service base can read the configuration file from the application package of the first meta-service and obtain the first short message source information and application identifier information corresponding to the first meta-service based on the configuration file. Afterwards, the meta-service base can initiate a registration request to the association management module 301 on behalf of the first meta-service.

[0171] For example, a configuration file looks like this: appid: com.example.metaservice001 msgInfos: msg: port: 100001 sign: Service A msg: port: 100002 sign: Service payment In this example, the configuration file may include application identifier information for the first meta-service and configuration items for the first short message source information. For instance, the configuration file may include an application identifier field (applicationidentifier, appid) and a message information field (message information, msgInfos). The appid can represent the application identifier information for the first meta-service; msgInfos may include one or more sets of message configuration items (message, msg), each set of msg configuration items may include the short message port and short message signature. For example, the appid could be "com.example.metaservice001", and msgInfos could include configuration items such as "port:100001, sign:A service" and "port:100002, sign:A service payment".

[0172] exist Figure 10In this process, after receiving the registration request from the meta-service base, the association management module 301 can obtain information related to this registration request from the application information management module 302. Since the first meta-service does not require installation, the electronic device 202 no longer needs to obtain the installation source information of the first meta-service from the application market, nor does it need to determine whether its source is trustworthy based on the installation source information of the first meta-service. Accordingly, the association management module 301 can determine whether the caller of this registration request is the meta-service base and verify the signature certificate of the meta-service base. If it is determined that the caller is the meta-service base and the signature certificate of the meta-service base is verified, it can be considered that this registration request meets the trustworthy source conditions in the meta-service scenario.

[0173] After the trusted source condition is met, further processing can be performed. This processing can be referred to in S404-S409 above, and will not be elaborated here. After receiving the authentication data corresponding to the first meta-service, server 201 can perform trust verification. This trust verification can be referred to in S501-S505 above, and will not be elaborated here. Finally, the associated display module 306 displays the application icon, application name, etc. of the first meta-service in the SMS interface based on the first configuration information.

[0174] The following describes the specific implementation process of the above technical concept.

[0175] For example, Figure 11 An embodiment of this application illustrates a registration verification system 1100, which includes an electronic device 202 and a server 201. The electronic device 202 is used to obtain first short message source information of a first application. In response to an event occurring in the electronic device where the first application triggers the sending of a first short message, the electronic device sends a first request to the server 201, wherein the first request includes the first short message source information. The server 201 is used to receive the first request, verify the short message service information of the first application based on the first short message source information, and, if the verification is successful, send a first response to the electronic device 202. The first response includes short message service information, or includes indication information indicating that the short message service information verification is successful. The short message service information includes second short message source information, both of which correspond to the first application. The short message service information is configuration information used by the electronic device to identify and process short messages related to the first application.

[0176] For example, the first short message is a short message that matches the source information of the first short message (i.e., the source information of the first short message is the source information of the first short message). This short message may be a message sent to the electronic device 202 through a third-party service (such as a short message service provider). For example, application notification messages are usually sent directly by the application to the operating system of the electronic device 202, and then displayed by the operating system. Since such notification messages are not sent through a third-party service, they do not belong to the category of short messages in this embodiment.

[0177] For example, the first short message source information includes at least one of a short message port, a short message number segment, and a short message signature; the second short message source information includes at least one of a short message port, a short message number segment, and a short message signature. Typically, the first short message source information may include a short message port. Additionally, the first short message source information may also include a short message signature. Typically, the second short message source information may include either a short message port or a short message number segment. The short message number segment can be identified and obtained from the corresponding short message port. Of course, the second short message source information may also include a short message signature.

[0178] For example, the first application can be an application or a meta-service; this is not limited here. The first and second SMS source information can be the same or different; this is not limited here either. It is understood that "inconsistency" here usually refers to the different ports corresponding to the first and second SMS source information. As mentioned above, the granularity of the representation used for the first and second SMS source information can be different; for example, the first SMS source information may include a port number, while the second SMS source information may be a number range. However, when the port number in the first SMS source information belongs to a number range in the second SMS source information, they can be considered the same.

[0179] For example, the SMS service information also includes at least one of the following: application name, application icon, menu information, and interactive control information, wherein the interactive control information is used to provide access to the first application.

[0180] In this way, since the first short message source information is associated with the first event that triggers the sending of the short message by the first application, when the server 201 verifies the short message service information of the first application based on the first short message source information, it can use the first request itself as evidence of the association between the first application and the short message source. That is to say, the first short message source information provided by the first application does not solely originate from the first application's unilateral declaration, but is combined with the actual event that triggers the sending of the first short message by the first application. Therefore, the risk of the first application arbitrarily or incorrectly declaring short message source information can be reduced, improving the security and reliability of the short message service information verification process.

[0181] In one possible implementation, the first request further includes risk control information, which includes device attribute information and / or network attribute information; in the process of verifying the short message service information of the first application based on the first short message source information in the received first request, the server 201 is specifically used to: verify the short message service information based on the first short message source information and risk control information in the first request.

[0182] For example, the device attribute information includes the type information of electronic device 202, and the network attribute information includes the IP address information of electronic device 202.

[0183] In this way, by carrying risk control information in the first request, when verifying the SMS service information, the server 201 can not only determine whether there is a connection between the first application and the first SMS source based on the first SMS source information, but also determine whether there is a risk in the reporting environment of this first request by combining device attribute information and / or network attribute information, thereby improving the accuracy and security of the SMS service information verification process.

[0184] For example, for a given application, if most of the multiple electronic devices 202 that send the first request to server 201 correspond to the same risky IP address, server 201 can determine that the application poses a risk of malicious or abnormal registration. Therefore, when verifying SMS service information, server 201 can combine risk control information to identify batch abnormal reporting behavior, thereby improving the security of the SMS service information verification process.

[0185] In one possible implementation, before sending the first request to the server 201, the electronic device 202 is specifically configured to: determine whether the first short message is sent in response to a business request initiated by the first application in response to receiving the first short message; during the process of sending the first request to the server 201, the electronic device 202 is specifically configured to: send the first request to the server 201 if the first short message is sent in response to a business request initiated by the first application.

[0186] For example, the service request could be a verification code request or another request that triggers the sending of a short message.

[0187] In this way, the first request is not sent directly after the first application unilaterally declares the source information of the SMS message. Instead, it is confirmed by combining two events: the first application initiating a business request and the electronic device 202 receiving the corresponding SMS message. This further eliminates the influence of SMS messages unrelated to the first application or accidentally received SMS messages on the registration verification process, giving the first request received by the server 201 a clearer business trigger basis, thereby improving the credibility and security of the SMS service information verification process.

[0188] In one possible implementation, during the process of verifying the SMS service information of the first application based on the first SMS source information in the received first request, the server 201 specifically performs the following steps: obtaining a cumulative value representing the progress of the SMS service information verification, the cumulative value being determined based on historical first requests used to verify the SMS service information; determining a risk coefficient based on the first SMS source information and / or risk control information in the first request; updating the cumulative value based on the risk coefficient; and verifying the SMS service information based on the updated cumulative value.

[0189] In this way, Server 201 can make a comprehensive judgment based on the cumulative historical request data and the risk level of the current request. For requests with a high degree of trust, the cumulative value can be updated significantly; for requests with abnormal risks, the cumulative value can be updated less significantly, not at all, or negatively. This reduces the undue impact of a single abnormal request on the verification result and improves the accuracy of SMS service information verification results.

[0190] In one possible implementation, the SMS service information included in the first response is encrypted and protected using a security key.

[0191] For example, server 201 is also configured to send a security key to electronic device 202; electronic device 202 is also configured to decrypt short message service information according to the security key after receiving the first response.

[0192] In this way, the security of the configuration distribution process can be improved through encryption.

[0193] In one possible implementation, whether the short message service information is successfully verified depends on the number of first requests received by the server 201 to request verification of the short message service information.

[0194] In this way, when the number of first requests reaches a certain level, it can be shown that the association between the first application and the corresponding SMS source information has a certain degree of universality and stability, thereby improving the reliability of the SMS service information verification results.

[0195] Furthermore, this application embodiment also provides a flowchart of a registration verification method. The method includes: obtaining first short message source information of a first application; in response to an event occurring in an electronic device where the first application triggers the sending of a first short message, sending a first request to a server, wherein the first request includes the first short message source information, and the first request is used to request the server to verify the short message service information of the first application based on the first short message source information; receiving a first response from the server, the first response including short message service information, or including indication information indicating that the short message service information verification is successful, wherein the short message service information is configuration information used by the electronic device to identify and process short messages related to the first application.

[0196] In one possible implementation, the first request also includes risk control information, which includes device attribute information and / or network attribute information, and is used to verify the SMS service information of the first application.

[0197] For example, device attribute information includes the type of electronic device, and network attribute information includes the IP address information of the electronic device.

[0198] In one possible implementation, before sending the first request to the server, the method further includes: in response to receiving the first short message, determining whether the first short message is a short message sent in response to a business request initiated by the first application; sending the first request to the server includes: if the first short message is sent in response to a business request initiated by the first application, sending the first request to the server.

[0199] For example, determining whether a first short message is a short message sent in response to a business request initiated by a first application includes: obtaining historical behavior information of the first application, wherein the historical behavior information is used to record the historical behavior of the first application within the most recent first duration; if the historical behavior information includes the historical behavior of the first application initiating a business request, then it is determined that the first short message is a short message sent in response to a business request initiated by the first application.

[0200] In one possible implementation, the short message service information of the first application included in the first response is encrypted and protected according to a security key; the method further includes: decrypting the short message service information of the first application based on the security key; wherein the security key is generated by the server and sent to the electronic device.

[0201] In one possible implementation, obtaining the first SMS source information of the first application includes: in response to a second event of the first application, verifying the legitimacy of the first application; and if the legitimacy verification of the first application is successful, obtaining the first SMS source information.

[0202] For example, the legitimacy of the installation source of the first application is verified; and / or, whether the first SMS source information is set to be blocked is verified. For example, the port set to be blocked can be: a harassing SMS port, a fraudulent SMS port, a blacklisted SMS signature, or other SMS ports marked as risky.

[0203] For example, the second event includes at least one of the following: the first application is opened, the first permission of the first application is enabled, and the first application is installed; wherein the first permission allows the display of short messages based on trusted short message service information.

[0204] In this way, electronic devices can pre-filter the registration behavior initiated by the first application, preventing untrusted applications from directly participating in the subsequent SMS service information verification process, thereby improving the security of the registration verification process.

[0205] In one possible implementation, the method further includes: if the legitimacy verification of the first application passes, obtaining the short message service information of the first application; and after receiving the first response, setting the short message service information of the first application as trusted according to the instruction information in the first response.

[0206] In one possible implementation, the SMS service information includes second SMS source information, and the method further includes: in response to a first user operation of displaying an SMS list, displaying an SMS list, the SMS list including summary information of a second SMS message, the second SMS message being an SMS message matching the second SMS source information, the summary information including a first portion of information from the SMS service information of a first application verified as trustworthy, the first portion of information including at least one of the following: application icon, application name; in response to a second user operation of selecting a second SMS message from the SMS list, displaying details information of the second SMS message, the details information including a second portion of information from the SMS service information of the first application, the second portion of information including at least one of the following: application icon, application name, function menu, access point of the first application.

[0207] Furthermore, this application provides a registration verification method applied to a server. The method includes: receiving a first request from an electronic device, the first request including first short message source information of a first application; responding to the first short message source information of the first request, verifying the short message service information of the first application, the short message service information including second short message source information, both the second short message source information and the first short message source information corresponding to the first application; and if the short message service information verification is successful, sending a first response to the electronic device, the first response including short message service information, or including indication information indicating that the short message service information verification is successful, the short message service information being configuration information used by the electronic device to identify and process short messages related to the first application.

[0208] In one possible implementation, whether the SMS service information is successfully verified depends on the number of first requests received by the server to request verification of the SMS service information.

[0209] In one possible implementation, verifying the short message service information of the first application includes: obtaining a cumulative value representing the progress of short message service information verification, the cumulative value being determined based on historical first requests used to verify the short message service information; determining a risk coefficient based on the first short message source information and / or risk control information in the first request; updating the cumulative value based on the risk coefficient; and verifying the short message service information based on the updated cumulative value.

[0210] For example, risk control information includes device attribute information and / or network attribute information.

[0211] In one possible implementation, the first request further includes an identifier of a first application; determining a risk coefficient based on the first SMS source information in the first request includes: obtaining an application identifier corresponding to the SMS source information stored in the database based on the first SMS source information; determining a risk coefficient based on the consistency between the identifier of the first application in the first request and the obtained application identifier; or, determining a risk coefficient based on the first SMS source information in the first request includes: obtaining SMS service information corresponding to the identifier of the first application stored in the database based on the identifier of the first application in the first request; determining a risk coefficient based on the consistency between the first SMS source information and the obtained SMS source information.

[0212] In one possible implementation, the SMS service information included in the first response is encrypted and protected using a security key. For example, the method further includes sending the security key to the electronic device.

[0213] It is understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. In addition, the various embodiments described above can be combined according to actual conditions, and the combined solutions are still within the protection scope of this application.

[0214] Next, based on the methods in the above embodiments, a registration verification device provided in this application will be introduced.

[0215] For example, Figure 12 A schematic diagram of a registration verification device provided in an embodiment of this application is shown. Figure 12 As shown, the registration verification device 1200 includes: an acquisition module 1201 and a processing module 1202.

[0216] The acquisition module 1201 is used to acquire the first short message source information of the first application; the processing module 1202 is used to send a first request to the server in response to an event in the electronic device in which the first application triggers the sending of the first short message, wherein the first request includes the first short message source information and is used to request the server to verify the short message service information of the first application based on the first short message source information; and to receive a first response from the server, wherein the first response includes short message service information or includes indication information indicating that the short message service information verification is successful, and the short message service information is configuration information used by the electronic device to identify and process short messages related to the first application.

[0217] In one possible implementation, the first request also includes risk control information, which includes device attribute information and / or network attribute information. This risk control information is used to verify the SMS service information of the first application. For example, the device attribute information includes the type of electronic device, and the network attribute information includes the IP address information of the electronic device.

[0218] In one possible implementation, before sending the first request to the server, the processing module 1202 is further configured to: determine whether the first short message is sent in response to a business request initiated by the first application in response to receiving the first short message; specifically, during the process of sending the first request to the server, the processing module 1202 is configured to: send the first request to the server if the first short message is sent in response to a business request initiated by the first application.

[0219] For example, determining whether a first short message is a short message sent in response to a business request initiated by a first application includes: obtaining historical behavior information of the first application, wherein the historical behavior information is used to record the historical behavior of the first application within the most recent first duration; if the historical behavior information includes the historical behavior of the first application initiating a business request, then it is determined that the first short message is a short message sent in response to a business request initiated by the first application.

[0220] In one possible implementation, the short message service information of the first application included in the first response is encrypted and protected according to a security key; the processing module 1202 is further configured to: decrypt the short message service information of the first application based on the security key; wherein the security key is generated by the server and sent to the electronic device.

[0221] In one possible implementation, the processing module 1202, during the process of obtaining the first short message source information of the first application, is further configured to: verify the legitimacy of the first application in response to a second event of the first application; and obtain the first short message source information if the legitimacy verification of the first application is successful.

[0222] For example, the legitimacy of the installation source of the first application is verified; and / or, whether the first SMS source information is set to be blocked is verified. For example, the port set to be blocked can be: a harassing SMS port, a fraudulent SMS port, a blacklisted SMS signature, or other SMS ports marked as risky.

[0223] For example, the second event includes at least one of the following: the first application is opened, the first permission of the first application is enabled, and the first application is installed; wherein the first permission allows the display of short messages based on trusted short message service information.

[0224] In this way, electronic devices can pre-filter the registration behavior initiated by the first application, preventing untrusted applications from directly participating in the subsequent SMS service information verification process, thereby improving the security of the registration verification process.

[0225] In one possible implementation, the processing module 1202 is further configured to: obtain the short message service information of the first application if the legitimacy verification of the first application is passed; and, after receiving the first response, set the short message service information of the first application to be trusted according to the indication information in the first response.

[0226] In one possible implementation, the SMS service information includes second SMS source information. The processing module 1202 is further configured to: in response to a first user operation of displaying an SMS list, display an SMS list, the SMS list including summary information of a second SMS, the second SMS being an SMS that matches the second SMS source information, the summary information including a first part of the SMS service information of a first application verified as trustworthy, the first part of the information including at least one of the following: application icon, application name; in response to a second user operation of selecting a second SMS in the SMS list, display detailed information of the second SMS, the detailed information including a second part of the SMS service information of the first application, the second part of the information including at least one of the following: application icon, application name, function menu, access point of the first application.

[0227] The above-mentioned possible implementations are only illustrative examples. There may be other possible implementations, and the specific implementation shall be subject to the actual application. The embodiments of this application are not specifically limited.

[0228] It should be noted that in the above embodiments, the concepts and explanations of the same terms can be referred to each other, and the same or similar steps can also be referred to each other. In addition, the methods provided in the above embodiments can be implemented independently; where there is no logical conflict, the methods provided in the various embodiments can also be combined for implementation, and this application does not limit this.

[0229] It should also be noted that each step in the above embodiments can be executed by the corresponding device, or by components such as chips, processors, or chip systems within that device. The embodiments of this application do not limit their execution. The above embodiments are merely illustrative examples of execution by corresponding devices. Furthermore, the specific implementation methods or examples in the above embodiments do not limit the solutions provided by the embodiments of this application.

[0230] It should be noted that in the above embodiments, some steps may be selected for implementation, and the order of the steps in the figures may be adjusted. This application does not limit this. It should be understood that performing some of the steps in the figures, adjusting the order of the steps, or combining them in a specific implementation all fall within the protection scope of this application.

[0231] It is understood that, in order to achieve the functions described in the above embodiments, each device involved in the above embodiments includes a hardware structure and / or software module corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0232] It is understood that the architecture and application scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present invention, and do not constitute a limitation on the technical solutions provided by the embodiments of the present invention. As those skilled in the art will know, with the evolution of network architecture and the emergence of new services, the technical solutions provided by the embodiments of the present invention are also applicable to similar technical problems.

[0233] It should be noted that the "steps" in the embodiments of this application are merely illustrative, intended to better understand one method of presentation used in the embodiments, and do not constitute a substantial limitation on the execution of the solution of this application. For example, the "step" can also be understood as a "feature". Furthermore, the steps do not constitute any limitation on the execution order of the solution of this application. Any changes to the order of steps, or the merging or splitting of steps made on this basis without affecting the overall solution implementation, resulting in a new technical solution, are also within the scope of disclosure of this application.

[0234] Based on the same concept, embodiments of this application also provide an electronic device. For example... Figure 13 As shown, the electronic device 202 includes one or more processors 1301 and a memory 1302. Optionally, the electronic device 202 may also include a display and a transceiver. For example, the above-mentioned devices can be connected via one or more communication buses. The one or more computer programs are stored in the memory 1302 and configured to be executed by the one or more processors 1301. The one or more computer programs include instructions that can be used to cause the electronic device 202 to perform various steps of the methods in the above embodiments.

[0235] Based on the same concept, embodiments of this application also provide an electronic device, which includes units for performing the various steps of the methods provided in the above embodiments.

[0236] For details on the specific functions of each module, please refer to the above embodiments; they will not be repeated here.

[0237] Based on the above embodiments, this application also provides a computer program product, which includes instructions; when the computer program is run on a computer, it causes the computer to execute the methods provided in the above embodiments.

[0238] Based on the above embodiments, this application also provides a computer-readable storage medium storing computer program instructions, which, when executed by a computer, cause the computer to perform the methods provided in the above embodiments.

[0239] Optionally, the aforementioned computer may include, but is not limited to, control devices.

[0240] The storage medium can be any available medium that a computer can access. For example, but not limited to, a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0241] Based on the above embodiments, this application also provides a chip for reading a computer program stored in a memory to implement the method provided in the above embodiments. Optionally, the chip may include a processor and a memory, wherein the processor is coupled to the memory and is used to read the computer program stored in the memory to implement the method provided in the above embodiments.

[0242] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the functions involved in the control device in the above embodiments. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete components.

[0243] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0244] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0245] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0246] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

Claims

1. A registration verification method, characterized in that, Applied to electronic devices, the method includes: Obtain the first SMS source information from the first application; In response to an event occurring in the electronic device in which the first application triggers the sending of a first short message, a first request is sent to the server, wherein the first request includes the source information of the first short message, and the first request is used to request the server to verify the short message service information of the first application based on the source information of the first short message; The system receives a first response from the server. The first response includes the short message service information, or includes indication information indicating that the short message service information has been verified. The short message service information is configuration information used by the electronic device to identify and process short messages related to the first application. The configuration information is used to determine the correspondence between the first application and the second short message source information.

2. The method according to claim 1, characterized in that, The first request also includes risk control information, which includes device attribute information and / or network attribute information, and is used to verify the short message service information of the first application.

3. The method according to claim 2, characterized in that, The device attribute information includes the type information of the electronic device, and the network attribute information includes the IP address information of the electronic device.

4. The method according to claim 1, characterized in that, Before sending the first request to the server, the method further includes: In response to receiving the first short message, determine whether the first short message is a short message sent in response to a business request initiated by the first application; Sending the first request to the server includes: If the first short message is sent in response to a business request initiated by the first application, the first request is sent to the server.

5. The method according to claim 4, characterized in that, Determining whether the first short message is a short message sent in response to a service request initiated by the first application includes: Obtain historical behavior information of the first application, wherein the historical behavior information is used to record the historical behavior of the first application within the most recent first time period; If the historical behavior information includes the historical behavior of the first application initiating a service request, then it is determined that the first short message is a short message sent in response to the service request initiated by the first application.

6. The method according to claim 1, characterized in that, The step of obtaining the first SMS source information of the first application includes: In response to a second event of the first application, verify the legitimacy of the first application; If the legitimacy verification of the first application is successful, the source information of the first short message is obtained.

7. The method according to claim 6, characterized in that, Also includes: If the legitimacy verification of the first application is passed, obtain the short message service information of the first application; Upon receiving the first response, the SMS service information of the first application is set to trusted according to the indication information in the first response.

8. The method according to claim 6, characterized in that, The verification of the legitimacy of the first application includes: Verify the legitimacy of the installation source of the first application; and / or, Verify whether the source information of the first short message is set to be blocked.

9. The method according to any one of claims 6-8, characterized in that, The second event includes at least one of the following: the first application is opened, the first permission of the first application is granted, and the first application is installed; The first permission allows the display of short messages based on trusted short message service information.

10. The method according to any one of claims 1-8, characterized in that, The short message service information includes second short message source information, and the method further includes: In response to a first user action to display a short message list, a short message list is displayed, the short message list including summary information of a second short message, the second short message being a short message that matches the source information of the second short message, the summary information including a first part of information from the short message service information of the first application that has been verified as trustworthy, the first part of information including at least one of the following: application icon, application name; In response to a second user action where the second short message in the short message list is selected, the details of the second short message are displayed. The details include a second part of the short message service information of the first application. The second part of the information includes at least one of the following: application icon, application name, function menu, and access point of the first application.

11. The method according to any one of claims 1-8, characterized in that, The first short message source information includes at least one of short message port, short message number segment, and short message signature; the second short message source information includes at least one of short message port, short message number segment, and short message signature.

12. A registration verification system, characterized in that, The system includes electronic devices and servers; The electronic device is configured to obtain first short message source information of a first application, and in response to an event occurring in the electronic device that triggers the sending of a first short message by the first application, send a first request to the server, wherein the first request includes the first short message source information; The server is configured to receive the first request, verify the short message service information of the first application based on the first short message source information, and send a first response to the electronic device if the verification is successful. The first response includes the short message service information or includes indication information indicating that the short message service information has been verified. The short message service information includes second short message source information, both of which correspond to the first application. The short message service information is configuration information used by the electronic device to identify and process short messages related to the first application, and the configuration information is used to determine the correspondence between the first application and the second short message source information.

13. The system according to claim 12, characterized in that, The first request also includes risk control information, which includes device attribute information and / or network attribute information; During the process of verifying the SMS service information of the first application based on the first SMS source information received in the first request, the server is specifically used for: The short message service information is verified based on the first short message source information and risk control information in the first request.

14. The system according to claim 12, characterized in that, Before sending the first request to the server, the electronic device is specifically used for: In response to receiving the first short message, determine whether the first short message is a short message sent in response to a business request initiated by the first application; During the process of sending a first request to the server, the electronic device is specifically used for: If the first short message is sent in response to a business request initiated by the first application, the first request is sent to the server.

15. The system according to any one of claims 12-14, characterized in that, During the process of verifying the SMS service information of the first application based on the first SMS source information received in the first request, the server is specifically used for: Obtain a cumulative value representing the progress of the SMS service information verification, the cumulative value being determined based on a historical first request, the historical first request being used to verify the SMS service information; The risk coefficient is determined based on the source information of the first short message and / or risk control information in the first request; Update the cumulative value based on the risk coefficient; The SMS service information is verified based on the updated cumulative value.

16. The system according to any one of claims 12-14, characterized in that, Whether the short message service information is successfully verified depends on the number of first requests received by the server to verify the short message service information.

17. The system according to any one of claims 12-14, characterized in that, The short message service information also includes at least one of the following: application name, application icon, menu information, and interactive control information. The interactive control information is used to provide an access point for the first application.

18. A registration verification device, characterized in that, include: Acquisition module and processing module The acquisition module is used to acquire the first short message source information of the first application; The processing module is configured to respond to an event occurring in the electronic device where the first application triggers the sending of a first short message, by sending a first request to the server, wherein the first request includes the first short message source information, and the first request is configured to request the server to verify the short message service information of the first application based on the first short message source information; and to receive a first response from the server, wherein the first response includes the short message service information, or includes indication information indicating that the short message service information has been verified, wherein the short message service information is configuration information for the electronic device to identify and process short messages related to the first application, and the configuration information is configured to determine the correspondence between the first application and the second short message source information.

19. An electronic device comprising a memory and a processor, characterized in that, The memory stores instructions that, when executed by a processor, cause the method described in any one of claims 1-11 to be implemented.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processing circuit, implement the method as described in any one of claims 1-11.

21. A computer program product containing instructions, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1-11.

Images