Information processing method, device, equipment, storage medium and product

Abstract

The embodiments of the present application disclose an information processing method, apparatus, device and storage medium, the method comprising: receiving a first pull request sent by a first pull object and carrying a target object identifier and a scene field; if it is obtained by authenticating the scene field that there is an association relationship between the first pull object and the target object, then determining the target scene level of the first pull object, the target scene level is used to describe the degree of association between the first pull object and the target object; determining an accessible information field corresponding to the target scene level, wherein different scene levels correspond to accessible information fields of different sensitivities; determining target attribute information of the target object according to the target object identifier and the accessible information field corresponding to the target scene level, and sending the target attribute information to the first pull object; fully meeting the needs of information pulling in various scenarios, having good scalability, and ensuring the security of user information.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and more specifically, to an information processing method, an information processing device, an electronic device, a computer-readable storage medium, and a computer product. Background Art

[0002] With the rapid development of computer technology, big data technology has also emerged. In the era of big data and under the background of data sharing, ensuring the security of personal information is also one of the important research directions. The measures taken to ensure the security of personal information are to restrict access to personal information according to legal rules.

[0003] In related technologies, especially in application products, personal information is involved. This is usually done by adding constraints to the product itself to avoid external and cross-product member information access. For example, enterprise-level products ensure that the interface only accepts data access from members of the same enterprise to ensure data security. However, this method of restricting access is relatively simple and cannot adapt to complex corporate relationships, affecting the scalability of product design. Summary of the invention

[0004] In order to solve the above-mentioned technical problems, the embodiments of the present application provide an information processing method, an information processing device, an electronic device, a computer-readable storage medium and a computer program product, which fully meet the needs of information pulling in various scenarios, have good scalability, and at the same time can well ensure the security of user information of various sensitivity levels, and effectively adapt to product iterations.

[0005] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0006] According to one aspect of an embodiment of the present application, there is provided an information processing method, comprising: receiving a first pull request carrying a target object identifier and a scene field sent by a first pull object; if it is obtained by authenticating the scene field that the first pull object and the target object have an association relationship, then determining a target scene level of the first pull object, wherein the target scene level is used to describe the degree of association between the first pull object and the target object; determining an accessible information field corresponding to the target scene level, wherein different scene levels correspond to accessible information fields of different sensitivities; determining target attribute information of the target object according to the target object identifier and the accessible information field corresponding to the target scene level, and sending the target attribute information to the first pull object.

[0007] According to one aspect of an embodiment of the present application, an information processing device is provided, including: a receiving module, receiving a first pull request carrying a target object identifier and a scene field sent by a first pull object; a level determination module, determining a target scene level of the first pull object if an association relationship is obtained between the first pull object and the target object through authentication of the scene field, wherein the target scene level is used to describe the degree of association between the first pull object and the target object; a field determination module, determining an accessible information field corresponding to the target scene level, wherein different scene levels correspond to accessible information fields of different sensitivities; a sending module, determining target attribute information of the target object according to the target object identifier and the accessible information field corresponding to the target scene level, and sending the target attribute information to the first pull object.

[0008] In one embodiment of the present application, the level determination module is further used to determine that the target scenario level of the first pull object is the first scenario level if the association relationship between the first pull object and the target object represents association with the same application business; if the association relationship between the first pull object and the target object represents association with the same conversation group, determine that the target scenario level of the first pull object is the second scenario level; if the association relationship between the first pull object and the target object represents mutual friends or association with the same group organization, determine that the target scenario level of the first pull object is the third scenario level.

[0009] In one embodiment of the present application, the field determination module is further used to determine that the accessible information field is a field of non-sensitive attribute information if the target scenario level is the first scenario level; if the target scenario level is the second scenario level, determine that the accessible information field is a field of attribute information other than contact information; if the target scenario level is the third scenario level, determine that the accessible information field is a field of any attribute information.

[0010] In one embodiment of the present application, the level determination module is further configured to determine that the first pull request is an unauthorized request if it is determined through authentication of the scene field that there is no association relationship between the first pull object and the target object.

[0011] In one embodiment of the present application, the first pull request also carries a source tag, and the source tag is used to trace the location of the initiation request; the information processing device also includes a recording module, and the recording module is used to record the initiation time point of the first pull request and the request content and source tag contained in the first pull request to form a log record; when it is determined that the first pull request is an unauthorized request, the first pull object is traced according to the log record.

[0012] In one embodiment of the present application, the sending module is further used to obtain attribute information corresponding to the target object identifier, and delete information other than the accessible information field from the attribute information to obtain the target attribute information; send the target attribute information and the target scene level to the first pull object at the same time, so that the first pull object caches the target attribute information, and re-initiates the first pull request when it is determined that the cached information is missing according to the target scene level.

[0013] In one embodiment of the present application, the receiving module is also used to receive a second pull request sent by a second pull object based on a business card, the second pull request carries the first identifier and the second identifier, the first identifier is used to describe the object that first requests to generate a business card, and the second identifier is used to describe the object to which the business card belongs; wherein the business card contains a sensitive information field of the object to which the business card belongs, and the sensitive information field is only visible to the object that first requests to generate a business card; the sending module is also used to send the target attribute information of the object to which the business card belongs to to the second pull object according to the second identifier if the first identifier is not the identifier of the second pull object.

[0014] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the information processing method described above.

[0015] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer executes the information processing method as described above.

[0016] According to one aspect of an embodiment of the present application, a computer program product is provided, including computer instructions, which implement the information processing method described above when executed by a processor.

[0017] In the technical solution provided in the embodiments of the present application, when the first pull request is received, the scene field carried in the request is authenticated to determine whether there is an association relationship between the pulled object and the target object, and the scene level of the access permission is further matched according to the degree of association between the pulled object and the target object. A higher scene level is required to obtain data information with more sensitive levels, and the target attribute information of the target object is determined through the accessible information field corresponding to the scene level to achieve protection of user information. The technical solution provided by the present application can fully meet the needs of information pulling under various scene data, has good scalability, and can well ensure the security of user information. The accessible fields of different sensitivities are divided by different scene levels, thereby ensuring the protection of user information of various sensitive precisons and effectively adapting to product iterations.

[0018] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0020] Figure 1 It is a schematic diagram of an implementation environment involved in this application;

[0021] Figure 2 is a flow chart of an information processing method shown in an exemplary embodiment of the present application;

[0022] Figure 3 yes Figure 2 A schematic diagram of the process after step S110 in the illustrated embodiment;

[0023] Figure 4 yes Figure 2 The flowchart of step S140 in the illustrated embodiment in an exemplary embodiment;

[0024] Figure 5 yes Figure 2 A flow chart in an exemplary embodiment after step S140 in the illustrated embodiment;

[0025] Figure 6-1 This is a schematic diagram of a chat interface for an object requesting to generate a business card for the first time, shown in an exemplary embodiment of the present application;

[0026] Figure 6-2 This is a schematic diagram of a chat interface of a target of business card forwarding shown in an exemplary embodiment of the present application;

[0027] Figure 7 is a flowchart of an information processing method shown in another exemplary embodiment of the present application;

[0028] Figure 8 is a flowchart of another information processing method shown in another exemplary embodiment of the present application;

[0029] Fig. 9 is a schematic diagram of an information processing device shown in an exemplary embodiment of the present application;

[0030] Fig.10 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION

[0031] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.

[0032] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0033] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0034] It should also be noted that the "multiple" mentioned in this application refers to two or more than two. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship.

[0035] See also Figure 1 , Figure 11 is a schematic diagram of an implementation environment involved in the present application. The implementation environment includes a client 10 and a server 20, and the client 10 and the server 20 communicate with each other via a wired or wireless network.

[0036] The client 10 is used to send a pull request to the server 20 based on the user's operation to obtain information of other users.

[0037] The server 20 is used to pull the scene field carried in the request for authentication to determine whether the user has an association relationship with other users, and when the authentication is passed, pull the data of other users, process the data of other users according to the accessible information field corresponding to the scene field to obtain target attribute information, and send the target attribute information to the client 10 so that the client 10 displays the target attribute information.

[0038] Among them, the client 10 can be any electronic device that can play streaming media, such as a smart phone, a tablet, a laptop, a computer, an intelligent voice interaction device, a smart home appliance, a car client, etc. The server 20 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network) and big data and artificial intelligence platforms. There is no restriction on this here.

[0039] It is understandable that in the specific implementation of this application, personal data related to user name, contact information, etc. is involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant personal data need to comply with relevant laws, regulations and standards of relevant countries and regions.

[0040] like Figure 2 As shown, Figure 2 is a flowchart of an information processing method according to an exemplary embodiment. The method can be applied to Figure 1 The implementation environment shown in Figure 1 The server 20 in the embodiment shown in the example is specifically implemented. The information processing method may include steps S110 to S140, which are described in detail as follows:

[0041] S110: Receive a first pull request sent by a first pull object and carrying a target object identifier and a scene field.

[0042] In one embodiment of the present application, the first pull object refers to a user corresponding to the client, and the target object identifier is used to uniquely identify the object, that is, to indicate which target object it is, and the target object is the object about which the first pull object wants to obtain information; it can be understood that the scene field is used to describe the relationship between the first pull object and the target object; the naming of the scene field can be different depending on the relationship between the first pull object and the target object. For example, if the relationship between the first pull object and the target object is friends in the same group, then the scene field is "group relationship scene".

[0043] Optionally, the first pull request may also carry request content, which is used to indicate the information that the first pull object wants to obtain. The scene field can be determined by the relationship between the first pull object and the target object and the request content. For example, the relationship between the first pull object and the target object is friends in the same group, and the request content of the first pull object is to view the list avatar of the target object, then the scene field is "group member list avatar scene".

[0044] As an example, the first pull request may carry one target object identifier and multiple scene fields, or may carry multiple target object identifiers and multiple scene fields; when the multiple target object identifiers do not correspond to the same scene field, it is necessary to form a set of corresponding relationships between the target object identifiers and the scene fields. The server receives the first pull request, which carries a set of carrying information 1, which includes the target object identifier vid1 and the scene field 1 "group relationship scene", and also carries another set of carrying information 2, which includes the target object identifier vid2 and the scene field 2 "group relationship scene"; when the multiple target object identifiers all correspond to the same scene field, there is no need to divide them. For example, the first pull request carries target object identifiers vid1~5 and the scene field "group relationship scene".

[0045] S120. If it is determined through authentication of the scene field that the first pulled object and the target object have an association relationship, determine the target scene level of the first pulled object, where the target scene level is used to describe the degree of association between the first pulled object and the target object.

[0046] In one embodiment of the present application, the specific relationship between the first pull object and the target object is determined by the client, and the server authenticates the scene field, extracts the relationship between the first pull object and the target object from the scene field, and then verifies the relationship between the first pull object and the target object to determine whether the specific relationship determined by the client is correct, and whether the specific relationship between the first pull object and the target object meets the corresponding requirements.

[0047] Optionally, the scene field is authenticated to determine whether there is an association relationship between the first pull object and the target object. If there is an association relationship between the first pull object and the target object, it means that the authentication is passed; wherein the association relationship indicates that the first pull object and the target object are related and have common points, such as being in the same group, being friends with each other, being in the same company, etc.; if it is obtained by authenticating the scene field that there is an association relationship between the first pull object and the target object, the target scene level of the first pull object is further determined; wherein, the target scene level is used to describe the degree of association between the first pull object and the target object. It can be understood that the more common points there are between the first pull object and the target object, the more important they are, and the greater the degree of association; and the greater the degree of association between the first pull object and the target object, the higher the target scene level of the first pull object.

[0048] If authentication of the scene field shows that there is no association between the first pulled object and the target object, indicating that the authentication fails, the first pull request is intercepted, strictly ensuring the privacy and security of user data.

[0049] S130: Determine an accessible information field corresponding to the target scene level, wherein different scene levels correspond to accessible information fields of different sensitivity levels.

[0050] In one embodiment of the present application, each scenario level distribution corresponds to a type of accessible information field, which indicates that the first pull object can access the information field of the target object, and the accessible information field includes but is not limited to the name, avatar field, position field, contact information field, etc.; wherein, the more the information field involves user privacy, the higher its sensitivity, for example, the sensitivity of the contact field and the sensitivity of the position field, the sensitivity of the position field is greater than the sensitivity of the name field; and the higher the scenario level, the higher the sensitivity of the corresponding accessible information field. As shown in Table 1 below, Table 1 is an exemplary correspondence between scenario levels and accessible information fields of the present application.

[0051] Scene Level Accessible Information Fields level1 Name and avatar fields level2 Position Field level3 Contact Field …… ……

[0052] Table 1

[0053] It is understandable that the correspondence between the scene level and the accessible information field can be flexibly adjusted according to actual needs, and this is just an example.

[0054] S140: Determine target attribute information of the target object according to the target object identifier and the accessible information field corresponding to the target scene level, and send the target attribute information to the first pulling object.

[0055] As mentioned above, the accessible information field indicates that the first pulling object can access the information field of the target object. The target attribute information of the target object can be determined based on the accessible information field corresponding to the target object identifier and the target scene level. The target attribute information indicates the information of the target object that can be obtained by the first pulling object. The target attribute information may refer to the personal identity attribute information of the target object. The server then sends the target attribute information to the first pulling object.

[0056] In one embodiment of the present application, since the degree of association between the first pull object and the target object is different, their corresponding target scenario levels are different. Optionally, determining the target scenario level of the first pull object in step S120 includes: if the association relationship between the first pull object and the target object represents association with the same application business, determining the target scenario level of the first pull object to be the first scenario level; if the association relationship between the first pull object and the target object represents association with the same conversation group, determining the target scenario level of the first pull object to be the second scenario level; if the association relationship between the first pull object and the target object represents mutual friends or association with the same group organization, determining the target scenario level of the first pull object to be the third scenario level.

[0057] It should be noted that the degree of association between being friends or being associated with the same group organization is greater than the degree of association with the same conversation group, and the degree of association with the same conversation group is greater than the degree of association with the same application business; wherein being associated with the same application business means that the first pull object and the target object are both associated with the business provided by a certain application, for example, both are associated with the same WeChat red envelope, or both are associated with the same live broadcast; in some examples, if the association relationship between the first pull object and the target object represents having common friends, the target scenario level of the first pull object is also determined to be the first scenario level; wherein having common friends means that the first pull object and the target object have added the same friend in a certain application, but the first pull object and the target object are not friends with each other.

[0058] Associating with the same conversation group means that the first pulled object and the target object are both in the same conversation group. The conversation group refers to a network user group that conducts conversations through a network platform. The network user group can aggregate several users into an online group to enable users to communicate with multiple people in an online group, such as a group that can conduct conversations in an instant messaging application, such as a WeChat group, a live broadcast room, etc.

[0059] Being associated with the same group organization means that the first pull object and the target object both belong to the same group organization, which refers to a group structure composed of individuals that can directly or indirectly contact, rely on, and influence each other in order to achieve a common goal, such as a company, association, etc. The first pull object and the target object are friends with each other, that is, in a certain application, the first pull object adds the target object as a friend, and the target object also adds the first pull object as a friend.

[0060] For example, if the scenario field in the first pull request is "group relationship scenario", it is determined whether the association relationship between the first pull object and the target object represents that they are associated with the same conversation group. If it is determined that the first pull object and the target object are associated with the same conversation group, the target scenario level of the first pull object is determined to be the second scenario level. If the first pull object and the target object are not associated with the same conversation group, it indicates that the authentication has failed.

[0061] In this embodiment, different scene levels are determined by the degree of association between the first pulled object and the target object, and then the accessible information fields corresponding to different scenes can be determined. Determining the accessible information fields in step S130 includes: if the target scene level is the first scene level, determining the accessible information field as a field of non-sensitive attribute information; if the target scene level is the second scene level, determining the accessible information field as a field of attribute information other than contact information; if the target scene level is the third scene level, determining the accessible information field as a field of any attribute information.

[0062] It should be noted that the field of non-sensitive attribute information means that the field does not involve sensitive attribute information, such as the name, avatar, etc. of the target object; the fields of attribute information other than contact information include but are not limited to name, avatar, gender, position, region, etc.; the fields of any attribute information include but are not limited to name, avatar, gender, position, region, telephone, email, etc.

[0063] It is understandable that the accessible information fields corresponding to different scenario levels can be flexibly adjusted according to actual needs, for example, further introducing and refining the accessible fields corresponding to more levels, for example, the accessible information fields corresponding to the first scenario level include name and avatar; the accessible information fields corresponding to the second scenario level include gender and position; the accessible information fields corresponding to the third scenario level include telephone and email; the accessible information fields corresponding to the third scenario level include ID card and home address, etc. In particular, no matter how the accessible information fields corresponding to each scenario level are adjusted, the minimum access field corresponding to the first scenario level is retained, that is, the field that will not cause sensitive information leakage of the target object.

[0064] It is worth noting that the information processing method provided in this embodiment also includes: if it is obtained through authentication of the scene field that there is no association relationship between the first pull object and the target object, then determining that the first pull request is an unauthorized request.

[0065] As mentioned above, there is no association relationship between the first pull object and the target object, and the authentication fails, indicating that the first pull object has initiated unauthorized access, and the server determines that the first pull request is an unauthorized request, and the scene field is an unauthorized scene. For example, the first pull object A requests to pull the attribute information of the target object B, and the scene field carried in the first pull request is "conference call scene", but the server authentication determines that A and B are not in the same conference room, and then determines that the first pull request is an unauthorized request. At this time, the server can reject the unauthorized request.

[0066] It should be noted that in one embodiment of the present application, the first pull request also carries a source tag, and the source tag is used to trace the location where the request is initiated, and then the server can subsequently trace the first pull object according to the source tag; see Figure 3 , Figure 3 The flowchart after step S110 is shown in an embodiment of the present application, including:

[0067] S310: Record the initiation time point of the first pull request and the request content and source tag contained in the first pull request to form a log record.

[0068] The initiation time point of the first pull request may be the time point when the first pull object sends the first pull request, which can be obtained from the first pull request; the initiation time point of the first pull request may also be the time point when the server receives the first pull request; of course, in addition to the time point, the first pull request may also contain request content and source tags, and the request content is used to indicate the content that the first pull object wants to request. The server records the initiation time point, request content, and source tag to form a log record of the first pull request, and the log record may also include a target object identifier and a scene field; after forming a log record for each pull request, the server saves the log record for subsequent queries.

[0069] S320: When it is determined that the first pull request is an unauthorized request, trace the first pull object according to the log record.

[0070] In one embodiment of the present application, when it is determined that the first pull request is an unauthorized request, the first pull object can be traced back according to the source mark, initiation time point and request content in the log record to determine whether there is a problem with the first pull object.

[0071] Exemplarily, the server may feedback the initiation time point and request content to the user to whom the first pull object belongs, so that the user can match the time point and request content to determine whether it is the first pull request initiated by himself. The server can determine where the request was initiated based on the source tag; for example, the server traces the source to determine that the first pull request was not initiated by the user, and determines that the request initiation location is the code location of a certain application. In this case, the code location of this type of application can be recorded and repaired to avoid initiating a pull request at this code location again.

[0072] Optionally, when the server determines that the first pull request is an unauthorized request, in addition to tracing the first pull object according to the log record, an unauthorized mark may be sent to the first pull object to remind the user to whom the first pull object belongs.

[0073] In another embodiment of the present application, if it is found through authentication of the scene field that there is no association relationship between the first pulled object and the target object, the smallest accessible information field can still be pulled to the first pulled object. The smallest accessible information field is a field that can be obtained without authentication. The smallest accessible information field does not involve sensitive data of the user and has been made public; for example, a social avatar.

[0074] See also Figure 4 , Figure 4 yes Figure 2 The flowchart of step S140 in the illustrated embodiment in an exemplary embodiment, the step S140 includes:

[0075] S141. Acquire attribute information corresponding to the target object identifier, and delete information except the accessible information field from the attribute information to obtain target attribute information.

[0076] In one embodiment of the present application, since the target object identifier uniquely identifies the object, the server can search for all attribute information of the target object based on the target object identifier and delete information except the accessible information field from the attribute information; for example, when searching for all attribute information of the target object, such as name, avatar, gender, position, region, telephone number and email address, and the determined accessible information fields are fields of attribute information other than contact information, the telephone number and email address are deleted to obtain the target attribute information of the target object, namely, name, avatar, gender, position and region.

[0077] Optionally, the attribute information corresponding to the target object identifier can be stored locally on the server or in another information database; when the attribute information corresponding to the target object identifier exists in another information database, the server can obtain the attribute information corresponding to the target object identifier directly from the information database without authentication; the information database can also authenticate the server, determine the identity information of the server, and then send the attribute information corresponding to the target object identifier to the server.

[0078] In another embodiment of the present application, the target attribute information of the target object can also be directly obtained based on the target object identifier and the accessible information field. For example, if the accessible information field is a field of attribute information other than contact information, the name, avatar, gender, position and region of the target object can be directly obtained without obtaining telephone and email information.

[0079] S142: Send the target attribute information and the target scene level to the first pulling object at the same time, so that the first pulling object caches the target attribute information, and re-initiates the first pulling request when it is determined according to the target scene level that the cached information is missing.

[0080] It is worth noting that when the server sends the target attribute information to the first pull object, it also sends the target scene level to the first pull object; after receiving the target attribute information, the first pull object will cache it locally; when the first pull object caches it locally, if it finds that the scene level corresponding to the cached information is lower than the target scene level, it can identify that the cached information is missing and re-initiate the first pull request. For example, if the target attribute information, i.e. name, avatar, gender, position and region, is cached to the first pull object, and the scene level of the first pull object is the third scene level, the first pull object identifies that the cached information is missing and sends the first pull request to the server again.

[0081] It should be noted that if the first pull object requests to obtain the attribute information of the target object corresponding to the high scene level and caches it, the first pull object again requests the attribute information of the target object corresponding to the low scene level, and the server does not need to return any information at this time.

[0082] See also Figure 5 , Figure 5 yes Figure 2 In the flowchart of an exemplary embodiment after step S140 in the illustrated embodiment, after sending the target attribute information to the first pull object, further includes:

[0083] S510: Receive a second pull request sent by a second pull object based on the business card.

[0084] In one embodiment of the present application, the second pull object sends a second pull request based on the business card, where the business card refers to an information page used to introduce a person, for example, a user clicks on a business card to initiate a second pull request; wherein the second pull request carries a first identifier and a second identifier, the first identifier being used to describe the object that first requested to generate the business card, that is, who first requested to generate the business card, and the second identifier being used to describe the object to which the business card belongs, that is, who the business card introduces.

[0085] It should be noted that the business card contains sensitive information fields of the object to which the business card belongs. The sensitive information fields are only visible to the object that first requests to generate a business card. For example, the first object A obtains the contact information of the target object B through authentication and generates a business card of the target object B. The business card contains the contact information of the target object B, but the contact information is only visible to the first object A that first requests to generate a business card. When the business card is continuously forwarded, Figure 6-1 As shown, Figure 6-1 The chat interface of the first pulled object A is shown. The business card is sent to the user object C. For the first pulled object A, A can see B's phone number; Figure 6-2 As shown, Figure 6-2 What is shown is the chat interface of user object C. For user object C, user object C cannot see the contact information of user target object B.

[0086] S520: If the first identifier is not the identifier of the second pulled object, send target attribute information of the object to which the business card belongs to the second pulled object according to the second identifier.

[0087] When the server receives the second pull request, it determines whether the first identifier is the identifier of the second pull object. If the first identifier is not the identifier of the second pull object, it indicates that the pull request is not initiated by the object that requests to generate the business card for the first time. At this time, the server obtains the attribute information of the object to which the business card belongs according to the second identifier, and sends the target attribute information to the second pull object. The target attribute information can be the non-sensitive attribute information corresponding to the business card. Continuing with the above example, if object C initiates a second pull request based on the business card, the second pull request will carry the first identifier A corresponding to the first pull object A and the second identifier B of the target object B. The server determines that the first identifier A is not the identifier C of object C, then object C cannot obtain the sensitive information of the target object B, such as object C cannot know the contact information of the target object B, but can obtain the name, position and other non-sensitive attribute information of the target object B through the server.

[0088] It can be understood that if there is an association between the second pull object and the object to which the business card belongs, the second pull object can initiate a pull request by carrying a scene identifier, and then after passing the scene field, obtain the target attribute information corresponding to the scene level; continuing with the above example, object C can also obtain the target attribute information of target object B through steps S110 to S140, which will not be repeated here.

[0089] The information processing method provided in this embodiment formulates different scenarios, performs separate permission checks on the privacy information required for different scenarios, and divides the permission levels by grading different scenarios. A higher permission level is required to obtain more data, and unified data interception is performed in the case of insufficient permissions or verification failures, thereby strictly ensuring the privacy and security of user data.

[0090] For ease of understanding, in one embodiment of the present application, the information processing method is described using a specific application scenario, wherein the server pre-divides the scenario levels and the accessible information fields corresponding to each scenario level.

[0091] Different scene levels correspond to different accessible information fields. The higher the scene level, the higher the scope of accessible information fields and the higher the information sensitivity. The scene levels can be divided into: Level 1 unauthenticated scene: only the user's Chinese and English name and avatar information can be obtained; Level 2 sub-sensitive information scene: all fields except mobile phone number and email address; Level 3 highly sensitive information scene: all fields can be obtained. Level 1 unauthenticated scene means that no authentication is required, that is, any client can obtain the user's Chinese and English name and avatar information.

[0092] It should be noted that if the user's Chinese and English name or avatar information contains sensitive information of the user, the user's Chinese and English name or avatar information will be used as an accessible information field in the level 2 sensitive information scenario.

[0093] Here, taking enterprise WeChat as an example, as shown in Table 2, the server provides a corresponding relationship between a scene field and an accessible information field.

[0094]

[0095] Table 2

[0096] like Figure 7 As shown, the information processing method includes:

[0097] S701. The client sends a pull request carrying a target user identifier and scenario fields to the information pull module of the server.

[0098] It should be noted that when the client pulls the specified user information, it must carry the scenario field. The specific scenario field definition is determined by the relationship chain and business purpose that the user needs to authenticate. For example: the scenario of obtaining the group member list information is defined as the group relationship scenario; the scenario of obtaining the customer contact member list is defined as the external customer relationship scenario; the scenario of obtaining the enterprise member information is defined as the internal enterprise relationship scenario.

[0099] S702. The authentication service module of the server performs corresponding authentication according to the scene field, and determines the scene level when the authentication is successful.

[0100] The server authenticates each scene field to determine whether the puller corresponding to the client and the target user are related, that is, whether they are in the same group, customer friends, or the same company; for example, if the scene field carried in the pull request is SCENE_ROOM, which is used to indicate that the puller and the target user are group members, the server determines whether the puller and the target user are in the same session group. If the puller and the target user are in the same session group, it means that the authentication is passed, and the accessible information field corresponding to level 2 can be accessed, and the scene level is determined to be level 2;

[0101] S703: The information pulling module of the server pulls the target user's information from the information service module.

[0102] The server obtains the target user's information at the bottom layer.

[0103] S704: The information extraction module of the server simplifies the information of the target user according to the accessible information field corresponding to the scenario level to obtain target information, and sends the target information to the client.

[0104] For example, when it is determined that the scenario field is level 2, the server deletes the target user's information outside the accessible information field to obtain the target information, such as the name and avatar information of the target user, and sends it to the client.

[0105] In this example, after receiving the target information, the client caches the target information, and re-initiates a pull request when it is determined that the cached information is missing.

[0106] For the received target user information, the client will cache it locally; however, the field sets at different levels are different, which may result in incomplete fields when accessing high-level scenes after low-level scenes access and caching information. Therefore, the client initiates a request with the scene field, and the server configures the level and field set to which the scene belongs, and will feedback the level in the response; when the client caches locally, if it finds that the level of information in the cache is lower than the required level, it can identify that the information in the cache is incomplete, and re-initiate the pull request through RPC (Remote Procedure Call). For example, if the scene field carried by the client is SCENE_ROOM, the required level is level2, and the level of information in the cache is level1, then when the client caches locally, it finds that the cached information is missing, and re-initiates the pull request.

[0107] In particular, if user A first initiates access to user B in a high-level scenario and caches it, and then initiates access to a low-level scenario, it may cause the fields that are not authorized in this access to be returned; but analysis shows that this scenario will not lead to the leakage of user sensitive information; because user A has reached a higher level of authorization for user B in a previous scenario, and maintaining this authorization status for a short time will not bring additional risks.

[0108] The information processing method provided in this embodiment can fully meet the needs of enterprises for information extraction in various scenarios, while ensuring the security of user information. The solution has good scalability and can divide different security levels according to actual needs, create different scenarios, and effectively adapt to product iterations while meeting security requirements.

[0109] It should be noted that this embodiment also provides a method for processing information of unauthorized requests, such as Figure 8 As shown, the information processing method includes:

[0110] S801. The client sends a pull request carrying a target user identifier, a scene field, and a source tag to the server.

[0111] The pull request also carries the request content and the time when it was initiated. The source tag is used to trace the specific location where the pull request was initiated.

[0112] S802: The server generates a log record of the pull request.

[0113] When the server receives each pull request, it needs to record the initiation time, request content, and source tag of the pull request to generate a log record, which is used by the client to troubleshoot and debug.

[0114] S803: The server performs corresponding authentication according to the scenario field. If the authentication fails, an unauthorized flag is sent to the client.

[0115] If the scene field is "SCENE_ROOM", the puller to which the client belongs needs to pull the target user's information, but when authenticating the scene field, it is found that the puller to which the client belongs and the target user are not in the same session group, indicating that the authentication fails. The server regards the pull request as an unauthorized request and returns an unauthorized flag to the client.

[0116] In an optional example, if the puller and the target user are not in the same conversation group and are only associated with the same red envelope, the server determines that the scenario level is level 1.

[0117] S804: When the client receives the unauthorized flag, it collects information about the unauthorized request.

[0118] When the client finds an unauthorized tag, it supports a UI (User Interface) pop-up window to prompt the requester, and collects the situation of the unauthorized request based on the pop-up window, such as whether the unauthorized request was initiated by the user and whether the request content of the unauthorized request was determined by the user.

[0119] message UserInfoinscene

[0120] {

[0121] optional uint64 vid = 1;

[0122] optional UserInfo info=2;

[0123] optional GetuserInfowithcheckStatus status=3; / / USERINFO_CHECK_FAIL corresponding user information returns empty

[0124] optional bool is_log=4; / / Whether the verification fails but the unauthorized flag is still returned

[0125] }

[0126] S805. The server traces the location where the unauthorized request occurred based on the log records.

[0127] It should be noted that steps S804 and S805 can be performed simultaneously. When the server determines that there is an unauthorized request, it can determine the code location and related account that initiated the unauthorized request based on the initiation time point and source identifier of the log record. The server can also send the log record to the client, and then the client compares the log record with the collected situation. The user can determine whether there is a problem with the client through the client.

[0128] The information processing method provided in this embodiment performs unified information interception in cases of insufficient authority or authentication failure, strictly ensures the privacy and security of user information, and traces the unauthorized request by logging the unauthorized request to troubleshoot and repair the problem.

[0129] The device embodiment of the present application is introduced, which can be used to execute the information processing method in the above embodiment of the present application. For details not disclosed in the device embodiment of the present application, please refer to the above embodiment of the information processing method of the present application.

[0130] Fig. 9 A block diagram of an information processing device according to an embodiment of the present application is shown, the information processing device comprising a receiving module 910, a level determination module 920, a field determination module 930 and a sending module 940;

[0131] The receiving module 910 receives a first pull request sent by a first pull object and carrying a target object identifier and a scene field;

[0132] The level determination module 920 determines the target scene level of the first pulled object if the first pulled object and the target object have an association relationship through authentication of the scene field, where the target scene level is used to describe the degree of association between the first pulled object and the target object;

[0133] A field determination module 930 determines an accessible information field corresponding to a target scene level, wherein different scene levels correspond to accessible information fields of different sensitivity levels;

[0134] The sending module 940 determines the target attribute information of the target object according to the target object identifier and the accessible information field corresponding to the target scene level, and sends the target attribute information to the first pulling object.

[0135] In one embodiment of the present application, based on the aforementioned scheme, the level determination module 920 is further used to determine that the target scenario level of the first pull object is the first scenario level if the association relationship between the first pull object and the target object represents association with the same business or having common friends; if the association relationship between the first pull object and the target object represents association with the same conversation group, determine that the target scenario level of the first pull object is the second scenario level; if the association relationship between the first pull object and the target object represents mutual friends or association with the same group organization, determine that the target scenario level of the first pull object is the third scenario level.

[0136] In one embodiment of the present application, based on the aforementioned scheme, the field determination module 930 is further used to determine that the accessible information field is a field of non-sensitive attribute information if the target scenario level is the first scenario level; if the target scenario level is the second scenario level, determine that the accessible information field is a field of attribute information other than contact information; if the target scenario level is the third scenario level, determine that the accessible information field is a field of any attribute information.

[0137] In one embodiment of the present application, based on the above-mentioned solution, the level determination module 920 is further used to determine that the first pull request is an unauthorized request if it is determined by authenticating the scene field that there is no association relationship between the first pull object and the target object.

[0138] In one embodiment of the present application, based on the aforementioned scheme, the first pull request also carries a source tag, which is used to trace the location of the initiation request; the information processing device also includes a recording module, which is used to record the initiation time point of the first pull request and the request content and source tag contained in the first pull request to form a log record; when it is determined that the first pull request is an unauthorized request, the first pull object is traced according to the log record.

[0139] In one embodiment of the present application, based on the aforementioned scheme, the sending module 940 is further used to obtain attribute information corresponding to the target object identifier, and delete information other than the accessible information field from the attribute information to obtain the target attribute information; the target attribute information and the target scene level are sent to the first pull object at the same time, so that the first pull object caches the target attribute information, and when it is determined that the cached information is missing according to the target scene level, the first pull request is re-initiated.

[0140] In one embodiment of the present application, based on the aforementioned scheme, the receiving module 910 is also used to receive a second pull request sent by the second pull object based on the business card, the second pull request carries a first identifier and a second identifier, the first identifier is used to describe the object that first requests to generate a business card, and the second identifier is used to describe the object to which the business card belongs; wherein, the business card contains sensitive information fields of the object to which the business card belongs, and the sensitive information fields are only visible to the object that first requests to generate a business card; the sending module 940 is also used to send target attribute information of the object to which the business card belongs to the second pull object according to the second identifier if the first identifier is not the identifier of the second pull object.

[0141] The information processing device provided in this embodiment, when receiving the first pull request, authenticates the scene field carried in the request to determine whether there is an association relationship between the pulled object and the target object, and further matches the scene level of the access permission according to the degree of association between the pulled object and the target object. A higher scene level is required to obtain data with more sensitivity. The technical solution provided in this application can fully meet the needs of pulling data in various scenarios, while at the same time can well ensure the security of user data, and divides the accessible fields of different sensitivities by different scene levels, thereby ensuring the protection of various sensitive precisions of information.

[0142] It should be noted that the device provided in the above embodiment and the method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs the operation has been described in detail in the method embodiment and will not be repeated here.

[0143] An embodiment of the present application also provides an electronic device, comprising one or more processors and a storage device, wherein the storage device is used to store one or more programs, which, when one or more programs are executed by the one or more processors, enable the electronic device to implement the information processing method as described above.

[0144] Fig.10 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown.

[0145] It should be noted that Fig.10 The computer system 1000 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0146] like Fig.10As shown, the computer system 1000 includes a central processing unit (CPU) 1001, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1002 or the program loaded from the storage part 1008 to the random access memory (RAM) 1003, such as executing the method described in the above embodiment. In the RAM 1003, various programs and data required for system operation are also stored. The CPU 1001, the ROM 1002 and the RAM 1003 are connected to each other through the bus 1004. The input / output (I / O) interface 1005 is also connected to the bus 1004.

[0147] The following components are connected to the I / O interface 1005: an input section 1006 including a keyboard, a mouse, etc.; an output section 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that a computer program read therefrom is installed into the storage section 1008 as needed.

[0148] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 1009, and / or installed from a removable medium 1011. When the computer program is executed by a central processing unit (CPU) 1001, various functions defined in the system of the present application are executed.

[0149] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium can include a data signal propagated in a baseband or as a part of a carrier wave, wherein a computer-readable computer program is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0150] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0151] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0152] Another aspect of the present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the method described above is implemented. The computer-readable storage medium may be included in the electronic device described in the above embodiment, or may exist independently without being assembled into the electronic device.

[0153] Another aspect of the present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the method provided in each of the above embodiments.

[0154] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0155] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0156] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0157] The above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. A person skilled in the art can easily make corresponding changes or modifications based on the main concept and spirit of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection required by the claims.

Claims

1. An information processing method, characterized in that: include: Receive a first pull request initiated by a first pull object sent by a client and carrying a target object identifier and a scenario field, where the scenario field is determined by a relationship between the first pull object and the target object and request content; Recording the initiation time of the first pull request and the request content and source tag contained in the first pull request to form a log record, wherein the source tag is used to trace the location where the request was initiated; extracting the relationship between the first pulled object and the target object from the scene field, and verifying whether the association relationship between the first pulled object and the target object matches the relationship extracted from the scene field; If the association relationship between the first pulled object and the target object matches the relationship extracted from the scene field, then determining the target scene level of the first pulled object, the target scene level is used to describe the degree of association between the first pulled object and the target object; the association relationship indicates that the first pulled object and the target object have something in common, the number of common points between the first pulled object and the target object is positively correlated with the degree of association, and the degree of association is positively correlated with the target scene level; Determining an accessible information field corresponding to the target scene level, wherein different scene levels in a plurality of scene levels correspond to accessible information fields of different sensitivity levels; Determine target attribute information of the target object according to the target object identifier and the accessible information field corresponding to the target scene level, and send the target attribute information to the first pull object; The method further comprises: If the association relationship between the first pull object and the target object does not match the relationship extracted from the scene field, the first pull request is determined to be an unauthorized request, and an unauthorized mark and the log record are sent to the client, so that the client collects the situation of the unauthorized request according to the unauthorized mark, and compares the log record with the collected situation of the unauthorized request to determine whether there is a problem with the client, the situation of the unauthorized request includes whether the unauthorized request is initiated by the operation of the first pull object, and whether the request content of the unauthorized request is determined by the first pull object; The code location that initiated the unauthorized request is determined according to the initiation time point and source identifier of the log record, and the code location is recorded.

2. The method according to claim 1, characterized in that Determining the target scene level of the first pulling object includes: If the association relationship between the first pulled object and the target object represents association with the same application service, determining that the target scenario level of the first pulled object is a first scenario level; If the association relationship between the first pulled object and the target object represents association with the same conversation group, determining the target scenario level of the first pulled object to be a second scenario level; If the association relationship between the first pulled object and the target object indicates that they are friends with each other or are associated with the same group organization, it is determined that the target scenario level of the first pulled object is the third scenario level.

3. The method according to claim 2, characterized in that The determining of the accessible information field corresponding to the target scene level comprises: If the target scene level is the first scene level, determining that the accessible information field is a field of non-sensitive attribute information; If the target scenario level is the second scenario level, determining that the accessible information field is a field of attribute information other than contact information; If the target scene level is the third scene level, it is determined that the accessible information field is a field of any attribute information.

4. The method according to any one of claims 1 to 3, characterized in that: The determining the target attribute information of the target object according to the target object identifier and the accessible information field corresponding to the target scene level, and sending the target attribute information to the first pull object comprises: Acquire the attribute information corresponding to the target object identifier, and delete the information except the accessible information field from the attribute information to obtain the target attribute information; The target attribute information and the target scene level are sent to the first pull object at the same time, so that the first pull object caches the target attribute information, and re-initiates the first pull request when it is determined according to the target scene level that the cached information is missing.

5. The method according to any one of claims 1 to 3, characterized in that: After determining the target attribute information of the target object according to the target object identifier and the accessible information field corresponding to the target scene level, and sending the target attribute information to the first pull object, the method further includes: Receive a second pull request sent by a second pull object based on the business card, the second pull request carries a first identifier and a second identifier, the first identifier is used to describe the object that first requests to generate a business card, and the second identifier is used to describe the object to which the business card belongs; wherein the business card contains a sensitive information field of the object to which the business card belongs, and the sensitive information field is visible only to the object that first requests to generate a business card; If the first identifier is not the identifier of the second pulled object, the target attribute information of the object to which the business card belongs is sent to the second pulled object according to the second identifier.

6. An information processing device, characterized in that: include: A receiving module receives a first pull request initiated by a first pull object sent by a client and carrying a target object identifier and a scenario field, wherein the scenario field is determined by a relationship between the first pull object and the target object and a request content; a level determination module, extracting the relationship between the first pulled object and the target object from the scene field, and verifying whether the association relationship between the first pulled object and the target object matches the relationship extracted from the scene field; If they match, the target scene level of the first pulled object is determined, and the target scene level is used to describe the degree of association between the first pulled object and the target object; the association relationship indicates that the first pulled object and the target object have common points, and the number of common points between the first pulled object and the target object is positively correlated with the degree of association, and the degree of association is positively correlated with the target scene level; A field determination module, which determines an accessible information field corresponding to the target scene level, wherein different scene levels in a plurality of scene levels correspond to accessible information fields of different sensitivity levels; A sending module, which determines target attribute information of the target object according to the target object identifier and an accessible information field corresponding to the target scene level, and sends the target attribute information to the first pulling object; The information processing device also includes a recording module, which is used to record the initiation time point of the first pull request and the request content and source tag contained in the first pull request to form a log record, and the source tag is used to trace the location of the initiation request; if there is no match, the first pull request is determined to be an unauthorized request, and the unauthorized tag and the log record are sent to the client, so that the client collects the situation of the unauthorized request according to the unauthorized tag, and compares the log record with the collected situation of the unauthorized request to determine whether there is a problem with the client, the situation of the unauthorized request includes whether the unauthorized request is initiated by the operation of the first pull object, and whether the request content of the unauthorized request is determined by the first pull object; the code location that initiates the unauthorized request is determined according to the initiation time point and source identifier of the log record, and the code location is recorded.

7. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that: Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the method according to any one of claims 1 to 5.

9. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images