CN113360296A

CN113360296A - Address management method and device, electronic equipment and readable storage medium

Info

Publication number: CN113360296A
Application number: CN202110689346.7A
Authority: CN
Inventors: 熊琅钰
Original assignee: Vivo Mobile Communication Hangzhou Co Ltd
Current assignee: Vivo Mobile Communication Hangzhou Co Ltd
Priority date: 2021-06-21
Filing date: 2021-06-21
Publication date: 2021-09-07

Abstract

The application discloses an address management method and device, electronic equipment and a readable storage medium, and belongs to the field of communication. The method comprises the following steps: receiving a use request of a first application for a first address in a first address list, wherein the use request comprises a first address ID and a first version number of the first address, and the first address list is a local address list which is sent to the first application in advance; in response to the use request, sending a first response result to the first application when a second version number of a second address matched with the first address ID in a local second address list is different from the first version number, wherein the first response result comprises address information of the second address, the second version number and a first preset message; the first preset message is used for informing the first application, and updating information of a first address in a first address list by adopting target information, wherein the target information comprises address information of a second address and a second version number.

Description

Address management method and device, electronic equipment and readable storage medium

Technical Field

The application belongs to the technical field of communication, and particularly relates to an address management method and device, an electronic device and a readable storage medium.

Background

With the popularization of electronic devices and the explosive growth of the number of Applications (APPs), people use more and more APPs in life and work. Various service type APPs such as online shopping, takeout and express delivery bring great convenience to the life of people.

Most of the APPs provide services for users, the users are required to store communication addresses in the APPs, especially the service-type APPs. However, currently, the communication addresses stored in the APPs are managed independently from each other, and there is management isolation. When a user wants to write an existing communication address in one APP into another APP, the user mainly extracts address information by screenshot and then performing character recognition on the screenshot, and then writes the extracted address information into another APP; or, the user copies each field content in the communication address in the APP one by one, and then pastes the copied field content into another APP to achieve the cross-APP storage function of the communication address.

Obviously, the management method of the communication address in the related art needs to perform complex operations across APPs, wherein a user needs to switch the APPs many times, and needs to perform complex extraction work on address information, which results in poor flexibility of address management.

Disclosure of Invention

An object of the embodiments of the present application is to provide an address management method, an address management apparatus, an electronic device, and a readable storage medium, which can solve the problems of complicated operation and poor flexibility when a management method for a communication address in the related art performs address management across APPs.

In a first aspect, an embodiment of the present application provides an address management method, where the method includes:

receiving a use request of a first application to a first address in a first address list, wherein the use request comprises a first address ID and a first version number of the first address, and the first address list is a local address list which is sent to the first application in advance;

in response to the use request, sending a first response result to the first application when a second version number of a second address matched with the first address ID in a local second address list is different from the first version number, wherein the first response result comprises address information of the second address, the second version number and a first preset message;

the first preset message is used for notifying the first application, and updating the information of the first address in the first address list by using target information, wherein the target information includes address information of the second address and the second version number.

In a second aspect, an embodiment of the present application provides an address management apparatus, including:

the first receiving module is used for receiving a use request of a first application to a first address in a first address list, wherein the use request comprises a first address ID and a first version number of the first address, and the first address list is a local address list which is sent to the first application in advance;

a first response module, configured to send, in response to the use request, a first response result to the first application when a second version number of a second address matching the first address ID in a local second address list is different from the first version number, where the first response result includes address information of the second address, the second version number, and a first preset message;

In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and when executed by the processor, the program or instructions implement the steps of the method according to the first aspect.

In a fourth aspect, embodiments of the present application provide a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method according to the first aspect.

In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect.

In the embodiment of the application, when a certain third party APP, that is, a first application wants to use a certain address, address management operation does not need to be performed across APPs, for example, address is copied and pasted from other third party APPs or an address is edited again, the method of the embodiment of the application can send a uniformly managed address list to the first application in advance, when the first application wants to use a certain address in the address list, the method of the embodiment of the application can receive an address use request carrying an address ID and a version number of the address of the first application, therefore, when the third party application wants to use a local address information which is not stored originally, cross-application cumbersome operation does not need to be performed among the third party APPs, a user does not need to switch APPs many times any more, so that tedious extraction work is performed on the address information, and the operation flow is simplified; in addition, when responding to the request for use, the method in the embodiment of the present application determines whether the address is updated based on the comparison of the version numbers by querying the second address list maintained locally for the version number matching the address ID, and when the version numbers are different, it indicates that the address content of the address has changed in the unified address list (i.e., the second address list) maintained in the embodiment of the present application, so that the version number and the address information matching the address ID in the second address list need to be returned to the first application, the first application obtains the latest address information of the address to be used by means of version check, and when responding to the request for use of the address, the method in the embodiment of the present application may further send a first preset message for notifying the first application of updating the information of the first address in the first address list by using the address information of the second address and the second version number Therefore, the first application can update the information of the first address with the changed address content in the first address list maintained locally, and the first address list maintained in the third-party application can be updated in time. In the process that the first application requests to use the address information of the first address, the first application can acquire the latest address information for use only by selecting the required address from the address list acquired in advance and triggering the use request, so that the address management is more flexible and accurate; when the address information in the uniformly managed address list (second address list) is changed and the first application uses the address, the latest address information can be obtained through the version check mechanism of the embodiment of the application, so that the accuracy of the address use is ensured.

Drawings

FIG. 1 is a block diagram of an interaction between a third party APP and a UAM according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a UAP protocol of one embodiment of the present application;

FIG. 3 is one of the flow diagrams of an address management method of one embodiment of the present application;

FIG. 4 is a second flowchart of an address management method according to an embodiment of the present application;

FIG. 5 is a third flowchart of an address management method according to an embodiment of the present application;

FIG. 6 is a schematic diagram of an interface for UAM identification of an address according to an embodiment of the present application;

FIG. 7 is a UAM address export interface diagram according to an embodiment of the present application;

FIG. 8 is a schematic diagram of an UAM interface for new address creation according to an embodiment of the present application;

FIG. 9 is a block diagram of an address management apparatus according to an embodiment of the present application;

FIG. 10 is a diagram of a hardware configuration of an electronic device according to an embodiment of the present application;

fig. 11 is a hardware configuration diagram of an electronic device according to another embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described clearly below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the application may be practiced in sequences other than those illustrated or described herein, and that the terms "first," "second," and the like are generally used herein in a generic sense and do not limit the number of terms, e.g., the first term can be one or more than one. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

The address management method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

In an embodiment, the Address management method of the embodiment of the present application may be executed by a system APP named "Unified Address Manager (UAM)" designed by the inventor, and the UAM is used to perform global management on addresses. The managed address may be a communication address, a network address, or the like, and the communication address will be described as an example.

Optionally, when each third party APP communicates with the UAM, a Unified Address Protocol (UAP) set by the method in the embodiment of the present application may be used.

As shown in fig. 1, a block diagram of the interaction between a third party APP and a UAM is shown.

Among them, third party APPs, APP1, APP2, APP3, and APP4, all need to adopt the UAP protocol defined in the embodiments of the present application when performing interactive communication with the UAM. When the third party APP wants to use the address information, the UAM can read or write the communication address information through the UAP protocol.

The address list in the UAM (i.e. the second address list described below) may store address information of the user, where the address information in the address list may include addresses collected from the third party APP, and may also include addresses written by the user in the UAM;

when the third party APP wants to use the address in the UAM, only the address information needs to be read;

if the third party APP acquires the write-in permission, the third party APP can also write the address information in the third party APP into the UAM, or change the existing address in the UAM.

The basic functions of the UAM may include creating addresses, modifying addresses, deleting addresses, sharing addresses, and authorization management.

The basic functions of the UAM are explained below:

newly building an address: newly building a communication address;

the new communication address establishment method may include: a user triggers a request for creating a new address for the UAM in the UAM, and then the UAM carries out positioning to generate a communication address to an address list in the figure 1; the user can also add an address to the address list in fig. 1 by manual input in the UAM; the APP writes an address stored inside the application into the UAM to newly create an address in the address list in fig. 1, and the APP here can execute an operation of newly creating an address only when acquiring a write permission for the UAM.

Modifying the address: modifying an existing communication address in the UAM;

the manner of modifying the communication address may include that the user operates the UAM to modify an address in the address list in fig. 1; the manner in which the third party APP modifies the address in the address list in the UAM may also be included.

Deleting the address: deleting one or more communication addresses in the UAM;

the manner of deleting the communication address may include: the user performs an address deletion operation on the address list in the UAM to delete at least one address in the address list in fig. 1.

Sharing addresses: sharing addresses in the UAM;

the address sharing method may include: sharing the address in the UAM used by the user for logging in to the UAM logged in by other users through a network, for example, sending a message (meeting a UAP protocol) to the UAM of an opposite-end user by the UAM; the address in the address list can also be shared by the UAM to a third party APP of another user, for example, the APP1 logged in by the user a reads the address from the UAM, and then the APP1 shares the read address to the APP1 logged in by the user B, where when the addresses are shared among the APPs of different users, the address sharing can be realized in a manner of sharing text or pictures;

and (3) authorization management: and managing the authority of the third party APP to read the address from the UAM and the authority to write the address into the UAM. The authority for writing the address can include the authority for the APP to perform addition, modification and deletion of the address in the UAM; the permission for reading the address can include permission of sharing the address in the UAM executed by the APP, and after the third-party APP is authorized, interaction of reading operation, writing operation or reading and writing operation can be performed with the UAM through a UAP protocol.

The UAP protocol contains the basic operation and address specifications as shown in fig. 2. The UAP contains the operations of: request authorization, address reading, version checking, address adding, address modification, subscription and notification.

The address specification related to the UAP protocol is shown in fig. 2, and the UAP address specification: unique address ID, contact name, contact phone, city district information, detailed address, version number and latitude and longitude data contained in the UAM.

The address ID and the version number are controlled by the UAM, and the address ID and the version number are not provided when the third party APP writes in a new address of the UAM (namely when the APP adds an address to the UAM).

With respect to request authorization in fig. 2: the method comprises the steps that a third party APP obtains a certificate communicated with a UAM, and the UAM issues the certificate and the certificate expiration time to the third party APP only after the UAM obtains the permission of a user. In subsequent address reading, version checking, address adding, address modifying, subscribing and notifying, the certificate is required to be carried.

The type of the request authorization can be divided into a read authority, a write authority and a read-write authority. After the read permission is obtained, the APP can read the address of the UAM, check the version and subscribe the notification operation, after the write permission is obtained, the APP can perform the operation of adding the address and modifying the address to the UAM, and the read-write permission is the union of the read permission and the write permission.

As shown in fig. 2, the process of requesting authorization may include:

the APP sends an authorization request to the UAM, and request parameters of the authorization request may include: a unique name of the third party APP, a requested authorization right (e.g., read, write, or read-write); after receiving the authorization request, the UAM may respond to the authorization request and return a response result to the third party APP, where the response result includes the credential allocated to the APP and the expiration time of the credential.

In this example, the UAM assigns this credential, Token, to the APP, which can identify the identity of the APP, that is, for different APPs, the credential issued by the UAM is different, and the credential can also carry parameters indicating its permission type, such as a credential having read permission, a credential having write permission, and a credential having read-write permission. The credential may be expressed as a string.

The following describes various operations of the UAM in fig. 2 in more detail with reference to the address management methods of different embodiments of the present application, wherein the execution subject of each address management method in the following may be the UAM, i.e., a system application.

Referring to fig. 3, a flowchart of an address management method according to an embodiment of the present application is shown, where the method specifically includes the following steps:

step 101, receiving a use request of a first application to a first address in a first address list, wherein the use request comprises a first address ID and a first version number of the first address, and the first address list is a local address list which is sent to the first application in advance;

optionally, before step 101, the method according to the embodiment of the present application may further include: receiving an address reading request of the first application; and responding to the address reading request, and sending a local address list to the first application so that the first application acquires the first address list.

The description will be given by taking RequestAddress (read address) in fig. 2 as an example:

when the third party APP performs read-write interaction with the UAM for the first time, since the local address list pulled from the UAM is not stored in the third party APP, it cannot be determined which address in the UAN needs to be used, therefore, in this embodiment of the application, the third party APP may send an address reading request to the UAM, and parameters of the request may include a credential, a paging tag, and the like pre-assigned to the APP by the UAM;

then, the UAM responds to the address reading request, and sends an address list stored locally in the UAM, for example, the local address list in the UAM shown in fig. 1, to the third party APP; in addition, when the UAM responds to the address read request, if the number of addresses in the local address list in the UAM is large, there is a paging of addresses, for example, the 1 st to 10 th addresses are the first page, the paging tag is 0, the 11 th to 20 th addresses are the second page, the paging tag is 1, and so on. Then the initial value of the page tag in the address read request is 0, the UAM returns the first 10 addresses to the third party APP, and since there is a list of local addresses for the second page, the response result may also include the value of the next available page tag, i.e. 1. In this way, after the third party APP acquires the first 10 addresses in the local address list of the UAM, the third party APP may further continue to request the address of the second page, and so on, so that the third party APP may acquire and store all local address lists (i.e., the first address list) in the UAM, and the third party APP may store the detailed information of each address in the first address list as an address snapshot.

The detailed information of each address in the local address list returned by the UAM to the third party APP conforms to the above mentioned UAP address specification.

In addition, the above description is given by taking the example that the third party APP and the UAM perform the address reading interaction for the first time, but in other application scenarios, even if the third party APP and the UAM do not already perform the first address reading interaction, if a certain target address that the user wants to use in the third party APP does not exist in the pre-acquired first address list, the process of reading the address in fig. 2 may also be used to re-acquire the local address list in the UAM (the local address list may be updated compared to the local address list acquired by the third party APP for the first time) (where the process of acquiring the local address list is the same as the above-mentioned example process, and is not described here again), updating a first address list which is obtained and stored in advance in the third-party APP by adopting a local address list in the UAM which is obtained last time; and then, the third party APP selects a target address to be used from the updated first address list through user operation.

In summary, whenever a third party APP wants to use a new address that does not exist locally at the third party APP, regardless of whether the third party APP has read the local address list in the UAM from the UAM in advance, the third party APP (here, the first application) can re-obtain the latest local address list from the UAM through the process of reading the address in fig. 2, thereby updating the first address list.

In the embodiment of the present application, whenever a first application wants to use a new address, a local address list set by the system application in the embodiment of the present application may be first obtained (the local address list is named as a first address list on the first application side), and then a first address to be used is selected from the first address list, so that by uniformly maintaining addresses in the local address list in the system application, when different third-party APPs use addresses, operations of copying and pasting addresses or recognizing addresses across applications between different third-party APPs are not required, only the first address to be used needs to be selected from the uniform local address list in the system application, not only does not need to switch APPs many times, but also does not need to perform tedious extraction work on address information in the third-party APPs, thereby improving flexibility of address management, moreover, the addresses used by different third-party APPs are selected from a uniformly maintained address list, so that the same address information can be ensured to be used by different applications for the same address, and the accuracy of the use of the address information is ensured.

In the embodiment of fig. 3, the above step 101 is continued to be exemplified:

after a first application (i.e. a certain third party APP) has previously acquired a local address list (named as a first address list) in the UAM, an address snapshot of a first address to be used may be selected from address snapshots of the first address list at any time, and since address contents in the local address list in the UAM may be updated, in order to ensure that the address snapshot used by each third party APP is the latest address information, after the address snapshot of the first address is selected, the first application needs to acquire the address information of the first address through version check in fig. 2.

The first application may trigger a request for using the first address to be sent to the UAM, as shown in the version check of fig. 2, where the request for using needs to carry the address ID of the first address and its version number.

Optionally, the usage request may also carry a credential previously assigned to the first application by the UAM as described above, and then the UAM may verify the credential first after receiving the usage request, and respond to various requests after the verification is passed, otherwise reject the request;

when various requests sent to the UAM by the third party APP are verified, the requests are classified into validity verification and functional verification, the validity verification is firstly carried out, the functional verification is carried out after the validity verification passes, if both the validations pass, the response is carried out, and if not, the response is rejected.

The validity verification is specifically embodied as whether the UAM allocates the certificate to the first application, wherein after the UAM authorizes the certificate to the third-party APP, the UAM can locally store a mapping relation between the unique name of the third-party APP and the issued certificate in the UAM, so that the legality verification can be performed on the certificate carried in the request of the third-party APP by inquiring the mapping relation, and if the mapping relation exists, the legality verification is passed;

and the functional verification is performed on the basis of passing the validity verification, which is specifically embodied as whether the operation type of the request sent by the third party APP to the UAM is matched with the certificate in the request and whether the certificate is in the validity period, and if the operation type of the request is matched with the certificate and the certificate is not expired, the functional verification is passed.

That is, the credentials may include a credential 1 that matches read rights, a credential 2 that matches write rights, and a credential 3 that matches read and write rights. As described above, the operation types matched by the read authority include operations of reading an address, version checking, and subscribing to a notification; the write permission matching operation desirably includes an operation of adding an address and modifying an address.

In this example, if the UAM preauthorizes the read right to the first application, the credential 1 identifying the identity of the first application is issued to the first application, then the request for using the first address by the first application may be responded, and if only the credential 2 identifying the identity of the first application is issued to the first application, then the request for using the first address by the first application may be denied, that is, the first application cannot read the latest address information of the first address to be used from the UAM.

Step 102, in response to the use request, sending a first response result to the first application when a second version number of a second address matched with the first address ID in a local second address list is different from the first version number, where the first response result includes address information of the second address, the second version number, and a first preset message;

the first preset message is used for notifying the first application, and updating the information of the first address in the first address list by using target information, wherein the target information comprises address information of the second address and the second version number;

since the local address list in the UAM may be updated, in order to distinguish the local address lists stored in different objects, the local address list stored in the UAM by the first application and acquired from the UAM in advance is named as a first address list, and the local address list stored in the UAM is named as a second address list. After the UAM sends the local address list to the first application, if the local address list in the UAM is updated, the second address list is the updated local address list, and if the local address list is not updated, the second address list is the same as the first address list.

Since the address data of each address in the list conforms to the above-mentioned UAP address specification regardless of the first address list or the second address list, each address has a version number, and when an address is updated, the version number of the address changes, but the address ID of the address in the UAM does not change.

Thus, in step 102, the UAM, upon receiving a request for use of the first address by the first application, a second version number of an address matching the first address ID, here denominated second address, may be extracted from a local second address list, and determined, whether the second version number is the same as the first version number in the use request, if not, the first address is updated with the address information, and since the local address list (named as the second address list) within the UAM maintains the latest address information for each address, therefore, the second version number, address information of the second address, and a first preset message indicating that the first application is notified to update each item of address information matched with the first address ID in the first address list by using the address information of the second address may be extracted from the second address list.

Referring to the version check of fig. 2, the response result returned by the UAM to the third party APP includes: whether the address (i.e., the first address) is the latest information; the response result also includes the latest address if the first version number of the first address requested by the third party APP is not the latest.

Then in step 102, the values of the isLatest field in the version check of FIG. 2 are: if not; the value of the latestAddress field is the second version number and the address information of the second address.

The first application may update the version number corresponding to the first address ID in the first address list to a second version number, and update the address information to the address information of the second address.

In the embodiment of the present application, the UAM is used as a system application to globally manage address information of users. The UAP is used as a standard protocol for obtaining the address, so that the address book data of the user can be conveniently obtained only by a third party APP meeting the UAP protocol under the authorization permission of the user. By means of the UAP and the UAM, a user does not need to frequently add and modify communication address information in various third-party APPs any more, only needs to uniformly manage the address in the UAM and then authorizes the address to be used by the third-party APP, and the effect that the address information can be used in each third-party APP can be really achieved by modifying once in the UAM.

Optionally, in combination with the embodiment of fig. 3, the method according to the embodiment of the present application may further include: and sending a second response result to the first application under the condition that the first version number is the same as the second version number, wherein the second response result comprises second preset information which indicates that the first application is approved to use the first address.

Optionally, in the example of fig. 2, if the first version number is the same as the second version number, it indicates that the address information of the first address is not updated on the UAM side, and in the version check in fig. 2, the value of the islate field is: is that; the value of the latestAddress field is null.

In this embodiment of the present application, the third party application may determine whether the first address requested by the third party application is updated by using the method of performing version check on the address that the third party application needs to read in this embodiment of the present application, and then, under the condition that the version number comparison finds that the first address is not updated, the third party application may directly use the address information of the first address that needs to be used and is read from the first address list acquired in advance from the UAM, and does not need to read addresses from other third party APPs, and generates the second address list by performing unified management on the addresses, so that the third party APP can conveniently and quickly acquire the needed address information.

Optionally, in combination with the embodiment of fig. 3, the method according to the embodiment of the present application may further include: receiving a newly added address request of the first application, wherein the newly added address request comprises address information of a third address to be newly added; responding to the new address request, allocating a third address ID and a third version number to the third address, and storing the third address ID, the third version number and address information of the third address in the second address list in an associated manner.

Wherein, after responding to the new address request, the first address list includes the third address ID, the third version number, and address information of the third address.

The execution sequence between the steps of the method in the embodiment of the present application and the steps in fig. 3 is not limited, that is, the execution sequence between the operation of adding an address to the UAM by the APP and the operation of reading an address from the UAM by the APP is not limited, and may be determined according to the user requirement.

The description will be given by taking AddAddress (new address) in fig. 2 as an example:

if the third party APP writes a new address to the UAM, in an example, the new address may be an address in the third party APP, that is, the new address is not an address in the first address list acquired in advance from the UAM, so that the function of importing an existing address in the third party APP to the UAM may be implemented by the method of this embodiment; in another example, the new address may also be an address requesting a new addition to the first address list; in another example, the new address may also be an address newly added by the user when the third party APP performs an operation of newly creating the address by using a conventional method; in order to write the new address into the UAM for unified management, after the address information of the third address to be newly added is received by the third party APP through the request of the newly-created address, the third party APP can carry the address information of the third address to be newly added into the request of the newly-created address to send to the UAM, the address information of the third address to be newly added can include a contact name, a contact phone number, city district information, a detailed address and the like, and optionally can also include latitude and longitude without an address ID and a version number; optionally, the new address request may further include a credential that the third party APP has acquired from the UAM in advance; then, the UAM responds to the new address request, specifically including giving an ID and a version number to the address to be written by the UAM, and then, the address information of the address to be added can be written into a local address list of the UAM in association with the newly given address ID and the version number, so that the second address list is updated; moreover, as shown in fig. 2, the UAM may further send information indicating whether the addition is successful to the third party APP as a response result, and, if the addition is successful, the response result may further include complete information (address ID, version number, address information) of the added address in the second address list.

Then on the third party APP side, the UAM responds to the new address request to the second address list

After the update, the third party APP side may also update the first address list, that is, newly add the first address list

The items of information of the third address (including the third address ID, the third version number, and the address information of the third address) are written in the first address list.

In this embodiment of the present application, a third party APP may write a new address into a second address list maintained by the method in this embodiment of the present application, so that when the second address list (i.e., a local address list) maintained by this embodiment of the present application is provided for each third party APP to be used, the second address list may include not only address information generated by a user in the UAM through editing, but also address information written to the UAM by the user through the third party APP, so that the address information in the UAM is richer and more diverse, and it is convenient for other third party APPs to select required address information from the address information provided by the UAM.

Optionally, in combination with the embodiment of fig. 3, after the first application acquires the first address list, the method according to the embodiment of the present application may further include: under the condition that the first application updates a fourth address in the first address list, receiving a modification request of the first application for the fourth address, wherein the modification request comprises a fourth address ID of the fourth address and address information after the fourth address is updated; responding to the modification request, allocating a fourth version number to the fourth address, updating an original version number matched with the fourth address ID in the second address list by adopting the fourth version number, updating original address information matched with the fourth address ID in the second address list by adopting the updated address information of the fourth address, and sending the fourth version number of the fourth address to the first application.

The update address in fig. 2 is taken as an example for explanation:

after the third party APP reads its local address list from the UAM by reading the address, and stores the first address list, the user may modify an address (e.g. a fourth address) in the first address list stored by the third party APP, which will result in that address information of the fourth address in the first address list is updated, but address information of the fourth address in the second address list in the UAM is not updated, so that, after the user modifies the fourth address in the first address list, a modification request for the fourth address is generated and sent to the UAM, where the modification request includes an address ID of the fourth address and the modified address information; then, the UAM may respond to the modification request, assign a new version number to the fourth address (an original version number different from the address ID of the fourth address in the second address list), update the original version number matched with the address ID of the fourth address in the second address list in the UAM with the new version number, and update the original address information matched with the address ID of the fourth address in the second address list with the modified address information in the modification request. In addition, since the version number is reassigned to the fourth address, the UAM needs to return the reassigned version number to the third party APP, so that the third party APP can update the version number of the fourth address in the first address list.

Optionally, in fig. 2, when the UAM responds to the modification request, information indicating whether the update is successful may also be sent, and in a case that the UAM successfully updates the fourth address, the latest information (specifically, the address ID, the version number, and the address information) of the fourth address is returned.

In this embodiment of the present application, after a user modifies an address in a first address list in a third-party APP, the address information of the address in a second address list of unified management maintained in the UAM may be updated by sending a modification request to the UAM of the method in this embodiment of the present application, where, since the address information is updated, it is further necessary to reassign a version number to the address, and return the reassigned version number to the third-party APP, so that the third-party APP may also update the version number of the modified address in the first address list with a new version number, and after the third-party APP side updates the first address list stored in the third-party APP, the address in the address list uniformly maintained by the UAM side may also be updated synchronously, so that the address list maintained by the UAM side maintains a latest state, and when other third-party APPs read the address from the UAM side, the latest version of the address information can be read each time.

Optionally, in combination with the embodiment of fig. 3, the method of the embodiment of the present application may further include:

in the case that an updated address exists in the second address list, sending a notification message to a second application, wherein the second application includes applications that subscribe to the second address list with an address update function (that is, the second application includes an application that obtains an address update case for the second address list), wherein the notification message includes a fifth address ID of a fifth address in the second address list with an update;

receiving an update request of the second application for the fifth address, wherein the update request comprises the fifth address ID;

and responding to the updating request, and sending the updated version number matched with the fifth address ID in the second address list and the updated address information to the second application.

The condition that at least one address in the second address list in the UAM is updated may include that a user operates the second address list in the UAM to cause the update; the method can also include the situation that the address in the local first address list is modified by the third party APP, so that the second address list on the UAM side is synchronously updated; the method can also include a case that the third party APP adds an address to the UAM, and any of the above cases can cause address update of the second address list of the UAM.

In case there is an updated address in the second address list, the notification function of the UAM may be triggered, i.e. all applications (here, the second application) that subscribe to the address update function to send a notification message to the UAM, so that the second application may update the fifth address in the locally stored first address list.

The function of subscribing and notifying the UAM by the third party APP may refer to a Subscribe function of fig. 2, where the third party APP may send a subscription request to the UAM, where the subscription request includes a credential of the third party APP, and the UAM configures the subscription function for the third party APP, and then may send a response result indicating whether subscription is successful. The UAM may locally store information of a third party APP (for example, a name of the APP, or an ID of the APP) configured with a subscription function; then, when the address in the UAM is updated, the address ID of the updated address, the updated version number, and the updated address information may be sent to all third-party APPs configured with the subscription function, so that the third-party APP with the subscription function may update the address in the first address list stored in the third-party APP in synchronization when the address in the UAM is updated.

If some third party APPs do not subscribe to the notification, or if the third party APPs subscribed to the notification do not run when the UAM issues the notification message, for example, address 1 is updated inside the UAM, the additional steps of the embodiment of the present application are combined with the above technical solution of fig. 3, and still address 1 in the third party APPs can be updated to the latest version number and the latest address information by means of version check when these third party APPs use address 1.

It should be noted that, since the above embodiment in which the APP adds an address to the UAM and the above embodiment in which the APP modifies the address in the UAM are also the case of updating the address on the UAM side, the additional steps of the method of this embodiment may also be combined with the above embodiment in which the APP adds an address to the UAM or with the above embodiment in which the APP modifies the address in the UAM to form different embodiments.

When the additional steps of the method in the embodiment of the present application are combined with the embodiment in which the APP modifies the address in the UAM, if the first application updates the address 1 in the first address list, the method in the embodiment of the present application can synchronize and automatically update the address information of the address 1 stored in the UAM and other third party APPs including the address 1, so that one application updates the address in the UAM, and then synchronously update the address information of a plurality of third party APPs using the addresses in the UAM in a linked manner.

In addition, it should be noted that the first application and the second application may be the same, that is, the first application for reading the address may be the same as the second application for updating the address of the UAM; further, the fifth address may be the same as the first address of the above-described embodiment, or the fifth address may be the same as the second address of the above-described embodiment, or the fifth address may be the same as the third address of the above-described embodiment, or the fifth address may be the same as the fourth address of the above-described embodiment.

In this embodiment of the present application, when an address in a second address list that is uniformly maintained in the UAM is updated, where the address that is updated is a fifth address, the method in this embodiment of the present application may notify, in a subscription manner, a second application that has a subscription address update function, to update information of the fifth address in a first address list that is locally stored by the second application; for other applications without subscribing to the address update function, or under the condition that the third party APP is not in a running state (cannot receive the notification message) when the UAM sends the notification message while subscribing to the address update function, the third party APP may check whether data of the address to be used has changed through a version check mechanism each time the address snapshot function is used, so as to ensure that the used address has the latest address data.

In other embodiments, as shown in fig. 2, the Notify function may also directly carry, in the notification message, a fifth address ID of the second address list where an updated fifth address exists, and an updated version number and updated address information in the second address list, where the version number and the updated address information are matched with the fifth address ID, without requiring that a third party APP obtains the updated version number and the updated address information of the fifth address through the fifth address ID issued by the UAM; the result of the third party APP's response to the notification message may include whether the notification message was successfully received.

In addition, along with the outburst of mobile APP well-blowout type, more and more homogeneous APPs appear, the APP such as online shopping, takeaway and express delivery can use the information of the goods receiving address, however, the APPs are isolated, the contact address of the user is obviously, but the APP is difficult to transfer into another APP from one APP, so that a mobile phone manufacturer can consider to be a system-level unified address management software, the user can conveniently manage the communication addresses of the user and friends, and the APP can be authorized to be used by a third party. Except the information that the communication address is used in many APPs, the address information in the embodiment of the present application may not only be the communication address information exemplified above, but also be other types of address information that can be used commonly among the APPs of the same type (or the same type), and of course, the address information in the above technical solution may also be replaced by user data (for example, personal information, name, telephone, identification number, social account number, etc. of the user) that is used or common among the APPs of the same type, and also be unified at a system level.

Optionally, in an embodiment, the UAM may be further adapted to automatically identify an address fill-in and extract scenario, so as to facilitate a user to import an address and export an existing address.

Fig. 4 shows a flow chart of UAM extracting an existing address:

when a user checks an existing communication address of a third party APP (the communication address is not an address in the first address list and can be an original communication address in the third party APP), the user can automatically identify the communication address in a page displayed by the third party APP by calling an 'identification address' function of the UAM by pressing a screen for a long time, and after obtaining permission of the user, the UAM can import the identified communication address into an address book of the UAM (namely, the second address list).

Regarding the "identify address" function, refer to FIG. 6:

firstly, a user opens an APP, an interface 11 of the APP is displayed, and the user checks communication address information in the APP; then, the user jumps to the interface 12 by pressing the screen for a long time, and the interface 12 can display a 'UAM' option; then, the user clicks the "UAM" option in the interface 12, calls out an option box (including an "identification address" option, an "export address" option, and a "new address" option), and jumps to the interface 13; then, selecting an option of 'identification address' in the interface 13 to trigger an 'identification address' function, wherein the UAM can identify the address information by performing OCR character identification on the address information in the interface 11 or acquiring a screenshot of the interface 11; after the UAM identifies the address, jumping to the interface 14, and displaying a dialog box of an identification result in the interface 14; finally, the user clicks the "save" option of the dialog box in the interface 14, and the UAM can save the recognition result (i.e., the address information of the contact shown in fig. 6) to the second address list in the UAM, and jump to the interface 15 indicating that the saving is successful; and clicking to cancel, not saving the identification result to the second address list of the UAM.

In this embodiment, the address information of the third address in the newly added address request may be a communication address originally stored in the third party APP except the first address list, and by clicking the "identify address" option, the UAM may identify the address information of the third address to be newly added by performing OCR character recognition on the address information in the interface 11 in fig. 6 or acquiring a screenshot of the interface 11, so that the UAM receives the newly added address request (including the identified address information) from the third party APP.

FIG. 5 shows a flow diagram of exporting an address within a UAM to a third party APP;

when a user wants to newly establish a communication address in a certain third-party APP, a second address list of the UAM can be called through user operation to judge whether the communication address to be newly established exists in the UAM, if the communication address exists in the UAM, the function of 'deriving the address' of the UAM can be called through long-time pressing of a screen, and the existing address can be quickly filled in the third-party APP. If the newly-built communication address does not exist in the second address list in the UAM, the user can select the function of the UAM for building the address, and the communication address is conveniently led out to more third-party APPs subsequently.

Regarding the "derive address" function, refer to FIG. 7:

firstly, a user opens an interface 21 of a communication address of a newly added contact of an APP; then, the user jumps to the interface 22 by pressing the screen for a long time, and the interface 22 can display a "UAM" option; then, the user clicks the "UAM" option in the interface 22, calls out an option box (including an "identification address" option, an "export address" option, and a "new address" option), and jumps to the interface 23; then selects the "export address" option in the interface 23 to trigger the "export address" function; then, jumping to an interface 24, displaying an existing address list (including an address one, an address two and an address three) in the UAM popped up by the UAM in the interface 24 for a user to select; assuming that the user selects "address one", it jumps to the interface 25 to pop up a dialog box for the detailed information of "address one"; by clicking the "use" button of the dialog box in the interface 25, the user can fill the address information of "address one" into the APP and jump to the interface 26. When address information in the UAM is filled into the APP, if the APP is compatible with the UAM, the UAM directly sends the address information to the past, and if the APP is not compatible with the UAM, the APP fills addresses into each field of the address to be newly created of the APP in a mode of intercepting keywords from the address information, so that the function of adding the address information in the APP is completed.

Regarding the "new address" function, refer to fig. 8:

firstly, a user opens an interface 31 of a communication address of a newly added contact of an APP; the user then jumps to the interface 32 by pressing the screen for a long time, which interface 32 may display a "UAM" option; then, the user clicks the "UAM" option in the interface 32, calls out an option box (including an "identification address" option, an "export address" option, and a "new address" option), and jumps to the interface 33; then, selecting a "new address" option in the interface 33 to trigger a "new address" function; then, jump to the interface 34, the interface 34 displays a popup window 41 with the new address popped up by the UAM, and after the user can fill the address information in the popup window 41 and click "confirm", the user can save the new address in the UAM, apply the new address to the APP, and jump to the interface 35. The advantage of creating new addresses in third party APPs via UAM is that the new addresses can be subsequently applied to other APPs more quickly.

In a specific example of the embodiment where the UAM receives the new address request of the first application, the user clicks the "new address" option, fills in the address information, and clicks the "confirm", so that the third-party APP triggers the new address request (including the address information input by the user at the third-party APP through the new address) and sends the new address request to the UAM.

In the embodiment of the application, the UAM can automatically identify the address filling and extracting scene, so that a user can conveniently import and export the existing address and the newly-built address. The user only needs to call out the "identification address", "export address" and "newly-built address" function of UAM through long pressing the screen, has had address to UAM in leading-in APP from other APP that just can be quick, has had the address to more APP in deriving from UAM, can maximize the multiplexing user existing communication address information, can greatly facilitate the user manage the communication address of oneself in different APPs.

It should be noted that, in the address management method provided in the embodiment of the present application, the execution subject may be an address management apparatus, or a control module in the address management apparatus for executing the address management method. The address management device provided in the embodiment of the present application is described by taking an example in which the address management device executes an address management method.

Referring to fig. 9, a block diagram of an address management apparatus according to an embodiment of the present application is shown. The address management apparatus includes:

a first receiving module 51, configured to receive a request for using a first address in a first address list by a first application, where the request includes a first address ID and a first version number of the first address, and the first address list is a local address list sent to the first application in advance;

a first response module 52, configured to, in response to the use request, send a first response result to the first application when a second version number of a second address matching the first address ID in a local second address list is different from the first version number, where the first response result includes address information of the second address, the second version number, and a first preset message;

Optionally, the apparatus further comprises:

a second receiving module, configured to receive an address reading request of the first application;

and the second response module is used for responding to the address reading request and sending a local address list to the first application so that the first application can acquire the first address list.

Optionally, the apparatus further comprises:

a third receiving module, configured to receive a new address request of the first application, where the new address request includes address information of a third address to be newly added;

a third responding module, configured to respond to the new address request, allocate a third address ID and a third version number to the third address, and store the third address ID, the third version number, and address information of the third address in the second address list in an associated manner, where after responding to the new address request, the first address list includes the third address ID, the third version number, and address information of the third address.

Optionally, the apparatus further comprises:

a fourth receiving module, configured to receive a modification request of a fourth address from the first application when the first application updates the fourth address in the first address list, where the modification request includes a fourth address ID of the fourth address and address information of the fourth address after update;

a fourth response module, configured to respond to the modification request, assign a fourth version number to the fourth address, update, with the fourth version number, an original version number in the second address list that matches the fourth address ID, update, with the updated address information of the fourth address, original address information in the second address list that matches the fourth address ID, and send the fourth version number of the fourth address to the first application.

Optionally, the apparatus further comprises:

a first sending module, configured to send a notification message to a second application if an updated address exists in the second address list, where the second application includes an application that subscribes to the second address list and has an address update function, and the notification message includes a fifth address ID of a fifth address in the second address list, where the fifth address is updated;

a fifth receiving module, configured to receive an update request of the second application for the fifth address, where the update request includes the fifth address ID;

a fifth response module, configured to send, in response to the update request, the updated version number and the updated address information that are in the second address list and are matched with the fifth address ID to the second application.

Optionally, the apparatus further comprises:

a second sending module, configured to send a second response result to the first application when the first version number is the same as the second version number, where the second response result includes second preset information indicating that the first application is permitted to use the first address.

The address management device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be mobile electronic equipment or non-mobile electronic equipment. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a Personal Computer (PC), a Television (TV), a teller machine or a self-service machine, and the like, and the embodiments of the present application are not particularly limited.

The address management device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system (Android), an iOS operating system, or other possible operating systems, which is not specifically limited in the embodiments of the present application.

The address management device provided in this embodiment of the present application can implement each process implemented by the foregoing method embodiment, and is not described here again to avoid repetition.

Optionally, as shown in fig. 10, an electronic device 2000 is further provided in this embodiment of the present application, and includes a processor 2002, a memory 2001, and a program or an instruction stored in the memory 2001 and executable on the processor 2002, where the program or the instruction implements the processes of the above address management method embodiment when executed by the processor 2002, and can achieve the same technical effect, and no further description is provided here to avoid repetition.

It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and the non-mobile electronic devices described above.

Fig. 11 is a schematic diagram of a hardware structure of an electronic device implementing an embodiment of the present application.

The electronic device 1000 includes, but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010.

Those skilled in the art will appreciate that the electronic device 1000 may further comprise a power source (e.g., a battery) for supplying power to various components, and the power source may be logically connected to the processor 1010 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The electronic device structure shown in fig. 11 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than those shown, or combine some components, or arrange different components, and thus, the description is not repeated here.

The processor 1010 is configured to receive a use request of a first application for a first address in a first address list, where the use request includes a first address ID and a first version number of the first address, and the first address list is a local address list sent to the first application in advance; in response to the use request, sending a first response result to the first application when a second version number of a second address matched with the first address ID in a local second address list is different from the first version number, wherein the first response result comprises address information of the second address, the second version number and a first preset message;

Optionally, the processor 1010 is further configured to receive an address read request of the first application; and responding to the address reading request, and sending a local address list to the first application so that the first application acquires the first address list.

Optionally, the processor 1010 is further configured to receive an address addition request of the first application, where the address addition request includes address information of a third address to be added newly; responding to the new address request, allocating a third address ID and a third version number to the third address, and storing the third address ID, the third version number and address information of the third address in the second address list in an associated manner, wherein after responding to the new address request, the first address list comprises the third address ID, the third version number and address information of the third address.

Optionally, the processor 1010 is further configured to receive a modification request of the first application for a fourth address in the first address list when the first application updates the fourth address, where the modification request includes a fourth address ID of the fourth address and address information of the fourth address after the fourth address is updated; responding to the modification request, allocating a fourth version number to the fourth address, updating an original version number matched with the fourth address ID in the second address list by adopting the fourth version number, updating original address information matched with the fourth address ID in the second address list by adopting the updated address information of the fourth address, and sending the fourth version number of the fourth address to the first application.

Optionally, the processor 1010 is further configured to send a notification message to a second application if an updated address exists in the second address list, where the second application includes applications that subscribe to the second address list and have an address update function, and the notification message includes a fifth address ID of a fifth address in the second address list, where the fifth address is updated; receiving an update request of the second application for the fifth address, wherein the update request comprises the fifth address ID; and responding to the updating request, and sending the updated version number matched with the fifth address ID in the second address list and the updated address information to the second application.

Optionally, the processor 1010 is further configured to send a second response result to the first application when the first version number is the same as the second version number, where the second response result includes second preset information indicating that the first application is approved to use the first address.

It should be understood that in the embodiment of the present application, the input Unit 1004 may include a Graphics Processing Unit (GPU) 10041 and a microphone 10042, and the Graphics Processing Unit 10041 processes image data of still pictures or videos obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also referred to as a touch screen. The touch panel 10071 may include two parts, a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein. The memory 1009 may be used to store software programs as well as various data, including but not limited to application programs and operating systems. Processor 1010 may integrate an application processor that handles primarily operating systems, user interfaces, applications, etc. and a modem processor that handles primarily wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 1010.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the process of the embodiment of the address management method is implemented, and the same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.

The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the above address management method embodiment, and can achieve the same technical effect, and the details are not repeated here to avoid repetition.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. An address management method, characterized in that the method comprises:

2. The method of claim 1, wherein prior to receiving the request for use of the first address from the first application on the first address list, the method further comprises:

receiving an address reading request of the first application;

and responding to the address reading request, and sending a local address list to the first application so that the first application acquires the first address list.

3. The method of claim 1, further comprising:

receiving a newly added address request of the first application, wherein the newly added address request comprises address information of a third address to be newly added;

responding to the new address request, allocating a third address ID and a third version number to the third address, and storing the third address ID, the third version number and address information of the third address in the second address list in an associated manner, wherein after responding to the new address request, the first address list comprises the third address ID, the third version number and address information of the third address.

4. The method of claim 1, wherein after the first application obtains the first address list, the method further comprises:

under the condition that the first application updates a fourth address in the first address list, receiving a modification request of the first application for the fourth address, wherein the modification request comprises a fourth address ID of the fourth address and address information after the fourth address is updated;

responding to the modification request, allocating a fourth version number to the fourth address, updating an original version number matched with the fourth address ID in the second address list by adopting the fourth version number, updating original address information matched with the fourth address ID in the second address list by adopting the updated address information of the fourth address, and sending the fourth version number of the fourth address to the first application.

5. The method of claim 1, 3 or 4, further comprising:

sending a notification message to a second application in the case that an updated address exists in the second address list, wherein the second application comprises an application subscribed with an address update function to the second address list, and wherein the notification message comprises a fifth address ID of a fifth address in the second address list, where the updated address exists;

6. The method of claim 1, further comprising:

and sending a second response result to the first application under the condition that the first version number is the same as the second version number, wherein the second response result comprises second preset information which indicates that the first application is approved to use the first address.

7. An address management apparatus, characterized in that the apparatus comprises:

8. The apparatus of claim 7, further comprising:

9. An electronic device comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the address management method according to any one of claims 1 to 6.

10. A readable storage medium, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the address management method according to any one of claims 1 to 6.