CN112199380B - Account information modification method, device, electronic equipment and storage medium - Google Patents
Account information modification method, device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112199380B CN112199380B CN202010955194.6A CN202010955194A CN112199380B CN 112199380 B CN112199380 B CN 112199380B CN 202010955194 A CN202010955194 A CN 202010955194A CN 112199380 B CN112199380 B CN 112199380B
- Authority
- CN
- China
- Prior art keywords
- target object
- account name
- target
- user
- priority
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003860 storage Methods 0.000 title claims abstract description 28
- 238000002715 modification method Methods 0.000 title abstract description 15
- 230000004048 modification Effects 0.000 claims abstract description 115
- 238000012986 modification Methods 0.000 claims abstract description 115
- 238000000034 method Methods 0.000 claims abstract description 44
- 238000004590 computer program Methods 0.000 claims description 9
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims description 8
- 230000002596 correlated effect Effects 0.000 claims description 6
- 235000019633 pungent taste Nutrition 0.000 claims description 4
- 238000005096 rolling process Methods 0.000 claims description 2
- 230000008569 process Effects 0.000 abstract description 8
- 238000012545 processing Methods 0.000 abstract description 8
- 238000010586 diagram Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 238000012552 review Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000004075 alteration Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000875 corresponding effect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2308—Concurrency control
- G06F16/2315—Optimistic concurrency control
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Abstract
The disclosure discloses a method account information modification method, a device, electronic equipment and a storage medium. The method is used for solving the problem that in the related art, when different users modify account names into the same account name. In the embodiment of the disclosure, when account names expected by different target objects are the same for each data center, each data center preferentially modifies the target object with high priority into the expected target account name, so as to ensure that the target account names are reasonably distributed to solve the problem of data conflict. The different data centers can concurrently process the respective modification requests so as to reduce the system burden caused by cross-private line access, so that the processing efficiency of the modification requests of the account names can be improved, and when different target objects compete for the target account names in a priority level mode, the target objects with high priority finally selected by the different data centers can be ensured to be consistent, and the problem of inconsistent data can be avoided.
Description
Technical Field
The disclosure relates to the field of computer technology, and in particular, to a method and a device for modifying account information, electronic equipment and a storage medium.
Background
Many internet products are popular and used worldwide. In the geographic range, when users of internet products are widely distributed, in order to ensure that users in different regions can efficiently and smoothly use the internet products, internet product suppliers often deploy globalization systems. And a set of data centers are respectively deployed in each region in the globalization system. Data centers in different areas can be synchronized by means of special lines. Different data centers serve users in different areas. After the user starts the terminal equipment, the user is dispatched to the corresponding data center according to the geographic position of the user, and then the request sent by the terminal equipment of the user is processed by the data center. The account names of the users are written into the data center and are synchronized to other data centers through special lines by the data center, so that the consistency of the account names of different data centers is ensured.
In the related art, when users of two or more data centers modify their respective account names at the same time, if the modified account names are the same, a data collision may occur. In order to deal with the problem of data collision, one solution in the related art is that each data center responds to a modification request of one user according to a time stamp of an account name modification request, and the other solution is that the modification requests of each user are serially handled by a unified data center.
However, the first approach may result in data inconsistencies from different data centers. The second scheme adopts a serial processing mode to process the modification request, so that the processing efficiency is low, and the user accesses the first data center across special lines, so that the access speed is slow and the possibility of modification failure is increased, and the repeated modification caused by the slow access speed and the possibility of modification failure also increase the burden of the system. Accordingly, a new scheme for updating account names is needed to make up for the deficiencies of the prior art.
Disclosure of Invention
The disclosure aims to provide an account information modification method, an account information modification device, electronic equipment and a storage medium, which are used for solving the problems of inconsistent data of different data centers or heavy system burden in the related art.
In a first aspect, an embodiment of the present disclosure provides an account information modification method, including:
if a modification request which is sent by a first target object and a second target object respectively and modifies the respective account name into a target account name is received in a designated time period, determining the respective priorities of the first target object and the second target object according to a preset rule;
and modifying the account name of the target object with high priority in the first target object and the second target object into the target account name.
In some embodiments, after said determining the respective priorities of the first target object and the second target object, the method further comprises:
generating a new account name of the target object with low priority;
modifying the account name of the target object with low priority to be the new account name; and is combined with the other components of the water treatment device,
and notifying the new account name to the target object with low priority.
In some embodiments, if the target object of the first target object and the target object of the second target object that first sends the modification request is taken as a preceding target object, and the target object of the later modification request is taken as a later target object, determining that the modification requests sent by the first target object and the second target object respectively and modifying the account names of the first target object and the second target object into the target account names are received in the specified duration includes:
responding to the modification request of the prior target object, and modifying the account name of the prior target object into the target account name;
if the modification request of the subsequent target object is received in the appointed time, determining that the modification requests respectively sent by the first target object and the second target object are received in the appointed time;
After determining the priorities of the first target object and the second target object according to a preset rule, and before modifying the account name of the target object with the higher priority in the first target object and the second target object to the target account name, the method further includes:
and if the priority of the prior target object is low, rolling back the operation of modifying the account name of the prior target object.
In some embodiments, the determining the respective priorities of the first target object and the second target object according to a preset rule includes:
acquiring respective related data of the first target object and the second target object; the related data includes: a user heat value and/or a user viscosity value;
determining respective priorities of the first target object and the second target object based on a preset relationship between the related data and priorities;
wherein the user heat value and the user viscosity value both have a positive correlation with the priority.
In some embodiments, the user hotness value is positively correlated with at least one of the following information by the user over a specified period of time: on-line time length, uploading number of works, praise number, attention amount and comment number;
A weighted sum of the user viscosity value and a plurality of the following information: daily use time length, vermicelli number, work comment number, number of uploaded works in the appointed time length and daily browsed times of works;
the determining the respective priorities of the first target object and the second target object based on the preset relation between the related data and the priorities includes:
when the related data comprises the user heat value and the user viscosity value, carrying out weighted summation on the user heat value and the user viscosity value of the first target object to obtain the priority of the first target object; and is combined with the other components of the water treatment device,
and carrying out weighted summation on the user heat value and the user viscosity value of the second target object to obtain the priority of the second target object.
In some embodiments, the generating the new account name of the low priority target object includes:
and generating a suffix of the target account name, and adding the suffix to the target account name to obtain the new account name.
In some embodiments, the generating the new account name of the low priority target object includes:
searching a historical account name set of the target object with low priority;
When the historical account name formed by the target account name and other information is found in the historical account name set, the historical account name is used as the new account name;
and when the historical account name is not found, generating an account name with the similarity with the target account name being larger than the preset similarity as the new account name.
In some embodiments, the notifying the new account name to the low priority target object is performed simultaneously, and the method further includes:
providing a modification interface of the new account to the target object with low priority;
receiving the custom account name of the target object with low priority sent by the modification interface;
and updating the account name of the target object with low priority according to the custom account name.
In some embodiments, the notifying the new account name to the low priority target object is performed simultaneously, and the method further includes:
and notifying the account name modification reason to the target object with low priority.
In a second aspect, the present disclosure also provides an account information modifying apparatus, the apparatus comprising:
the priority determining module is configured to execute the steps of determining the respective priorities of the first target object and the second target object according to a preset rule if a modification request which is sent by the first target object and the second target object respectively and is used for modifying the respective account names into target account names is received in a specified time period;
And the updating module is configured to execute the modification of the account name of the target object with high priority in the first target object and the second target object into the target account name.
In some embodiments, the update module is further configured to perform further comprising:
generating a new account name of a target object with low priority after the priority determining module determines the respective priorities of the first target object and the second target object;
modifying the account name of the target object with low priority to be the new account name; and is combined with the other components of the water treatment device,
and notifying the new account name to the target object with low priority.
In some embodiments, if the target object of the first target object and the second target object that sent the modification request first is taken as a preceding target object, and the target object that sent the modification request later is taken as a following target object, the apparatus further includes:
the conflict determination module is configured to execute a modification request for modifying the respective account names to the target account names, which is received in the specified time period and is sent by the first target object and the second target object respectively, according to the following method:
responding to the modification request of the prior target object, and modifying the account name of the prior target object into the target account name;
If the modification request of the subsequent target object is received in the appointed time, determining that the modification requests respectively sent by the first target object and the second target object are received in the appointed time;
the apparatus further comprises:
and the rollback module is configured to execute the operation of rollback the modified account name of the previous target object if the priority of the previous target object is low after the priority determining module executes the determination of the respective priorities of the first target object and the second target object according to the preset rule and before the updating module executes the modification of the account name of the target object with high priority in the first target object and the second target object to the target account name.
In some embodiments, the priority determination module is specifically configured to perform:
acquiring respective related data of the first target object and the second target object; the related data includes: a user heat value and/or a user viscosity value;
determining respective priorities of the first target object and the second target object based on a preset relationship between the related data and priorities;
Wherein the user heat value and the user viscosity value both have a positive correlation with the priority.
In some embodiments, respective related data of the first target object and the second target object is acquired; the related data includes: a user heat value and/or a user viscosity value;
determining respective priorities of the first target object and the second target object based on a preset relationship between the related data and priorities;
wherein the user heat value and the user viscosity value both have a positive correlation with the priority.
In some embodiments, the update module is specifically configured to perform:
and generating a suffix of the target account name, and adding the suffix to the target account name to obtain the new account name.
In some embodiments, the update module is specifically configured to perform:
searching a historical account name set of the target object with low priority;
when the historical account name formed by the target account name and other information is found in the historical account name set, the historical account name is used as the new account name;
and when the historical account name is not found, generating an account name with the similarity with the target account name being larger than the preset similarity as the new account name.
In some embodiments, the updating module is further configured to perform notifying the low priority target object of the new account name while providing the low priority target object with a modification interface of the new account;
receiving the custom account name of the target object with low priority sent by the modification interface;
and updating the account name of the target object with low priority according to the custom account name.
In some embodiments, the updating module is further configured to perform the notifying the new account name to the low priority target object while notifying account name modification reasons to the low priority target object.
In a third aspect, another embodiment of the present disclosure also provides an electronic device, including at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform any one of the account information modification methods provided by the embodiments of the present disclosure.
In a fourth aspect, another embodiment of the present disclosure also provides a computer storage medium, where the computer storage medium stores a computer program for causing a computer to perform any one of the account information modification methods in the embodiments of the present disclosure.
In the embodiment of the disclosure, when account names expected by different target objects are the same for each data center, each data center preferentially modifies the target object with high priority into the expected target account name, so as to ensure that more demanding users can use the target account name, and thus solve the problem of data collision. The different data centers can process the respective modification requests concurrently so as to reduce the system burden caused by cross-private line access, so that the processing efficiency of the modification requests of the account names can be improved, and when different target objects compete for the target account names in a priority level mode, the target objects with high priority finally selected by the different data centers can be ensured to be consistent, and the problem of inconsistent data is avoided.
Additional features and advantages of the disclosure will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the disclosure. The objectives and other advantages of the disclosure will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings that are needed in the embodiments of the present disclosure will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present disclosure, and other drawings may be obtained according to these drawings without inventive effort to a person of ordinary skill in the art.
FIG. 1 is a schematic diagram of resolving data collision problems in an embodiment of the disclosure;
FIG. 2 is a schematic diagram of an application environment according to one embodiment of the present disclosure;
FIG. 3 is a schematic diagram of an account information modification flow according to one embodiment of the present disclosure;
FIG. 4 is a schematic diagram of a user interface according to one embodiment of the present disclosure;
FIG. 5 is another schematic diagram of an account information modification process according to one embodiment of the disclosure;
FIG. 6 is a schematic diagram of an apparatus for account information modification according to one embodiment of the present disclosure;
fig. 7 is a schematic diagram of an electronic device according to one embodiment of the present disclosure.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and in the claims are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
As described above, in the first scheme, since different data centers each preferentially process the modification request with the time stamp being the front, data of different data centers may not be consistent. In addition, the user cannot know that the modification request fails to be executed, so that the information understood by the user and the information stored by the system may be inconsistent, and when the user accesses the data center by adopting wrong information, access failure is easy to cause. The second scheme adopts a serial processing mode to process the modification request, so that the processing efficiency is low, and the user accesses the first data center across special lines, so that the access speed is slow and the possibility of modification failure is increased, and the repeated modification caused by the slow access speed and the possibility of modification failure also increase the burden of the system.
In view of this, the present disclosure proposes an account information modification method, apparatus, electronic device, and storage medium for solving the above-mentioned problems. The inventive concept of the present disclosure is shown in fig. 1, where each data center is responsible for a modification request of a local user, that is, the user sends the respective account modification request to the local data center, and a bidirectional synchronization mechanism is adopted between different data centers to perform data synchronization. For each data center, the same data center may process multiple modification requests at the same time, which may be from users of different data centers or from users of the same data center. As shown in fig. 1, the user a and the user B are respectively from the first data center and the second data center, and both the user a and the user B require to change the account name to james, and both the users send the modification request to the respective data centers at the same time. Taking the first data center as an example, the first data center receives the modification requests of the user A and the user B at the same time, and finds that the modification requests of the two users have the data conflict problem, the first data center calculates the priorities of the user A and the user B respectively, and if the priority of the user A is higher than that of the user B, the user A with the higher priority is selected and the user name is modified into james according to the modification requests.
Further, in order to ensure that the user with low priority can also successfully modify the account name, for the user B with low priority, a new account name is reassigned to the user B, and then the account name of the user B is modified to be the new account name, and the user B is notified of the new account name.
Therefore, when the data conflict problem occurs, the modification requests of different users can be executed, and the user with high priority can be ensured to modify preferentially. And further, the user modified the account name is timely informed under the condition of reassigning the account name, so that the user can smoothly perform some operations through the modified account name. And, the scheme provided by the disclosure is executed concurrently by each data center in the disclosure, so that the processing efficiency of the modification request can be ensured.
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present disclosure more clear, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure.
Fig. 2 is a schematic diagram of an application environment according to one embodiment of the present disclosure.
As shown in fig. 2, the application environment may include, for example, two data centers, namely, a data center 1 and a data center 2. Each data center is made up of storage systems 10 and servers 20. Each data center is responsible for a plurality of terminal devices 30. Wherein each terminal device 30 may be any suitable electronic device for network access, including but not limited to a computer, notebook, smart phone, tablet, or other type of terminal. The storage system 10 is capable of storing accessed data, and the server 20 is configured to interact with the local terminal device 30, and obtain the data from the storage system and return the data to the terminal device 30. The terminal devices 30 (e.g., between 30_1 and 30_2 or 30_n) may also communicate with each other via the network 40. Network 40 may be a broad network for information transfer and may include one or more communication networks such as a wireless communication network, the internet, a private network, a local area network, a metropolitan area network, a wide area network, or a cellular data network.
Only a single server or terminal device is detailed in the description in this disclosure, but it should be understood by those skilled in the art that the single server 20, terminal device 30 and storage system 10 are shown to represent the operation of the aspects of this disclosure involving the terminal device, server and storage system. The detailed description of a single terminal device and a single server and storage system is for at least convenience of explanation and does not imply that there are limitations on the number, type, location, etc. of terminal devices and servers. It should be noted that the underlying concepts of the example embodiments of the present disclosure are not altered if additional modules are added to or individual modules are removed from the illustrated environment. In addition, although a bi-directional arrow from the storage system 10 to the server 20 is shown in fig. 2 for convenience of explanation, it will be understood by those skilled in the art that the above-described data transmission and reception may be realized through the network 40.
As shown in fig. 3, a flow chart of an account information modification method provided by an embodiment of the disclosure includes the following steps:
in step 301, if a modification request sent by a first target object and a second target object respectively and modifying their account names into target account names is received in a specified time period, the data center determines the respective priorities of the first target object and the second target object according to a preset rule;
Regarding whether there is a data collision problem, it can be determined according to the following method:
if the target object of the first target object and the second target object which firstly send the modification request is taken as a previous target object and the target object of the later modification request is taken as a later target object, the account name of the earlier target object can be modified into the target account name in response to the modification request of the earlier target object; when the modification request of the subsequent target object is received in the specified time period, the modification request sent by the first target object and the second target object respectively is received in the specified time period, namely, the problem of data collision is determined. When the method is implemented, when a modification request of a later target object is received in a designated time period, a database of a local data center can be searched, and if the target account name of the later target object request is found to exist, the problem of data conflict is determined to exist. Therefore, each data center can respond to the modification request of the user independently and quickly, and the conflict problem can be solved timely. Also, in this case, if the priority of the preceding target object is low, the operation of modifying the account name of the preceding target object is rolled back, and then the respective account names of the preceding target object and the following target object are modified in accordance with the priority. So as to ensure that the target object with high priority has the target account name and ensure the consistency of the data.
Of course, in another embodiment, after receiving a modification request of a user, the modification request may be stored in a queue, and then waiting for a designated duration to be reprocessed, for any modification request received later, a target account name expected by the modification request may be compared with a target account name in the modification request to be processed in the queue, if the target account name is found to be the same as the target account names of other modification requests, it is determined that there is a data conflict, if the target account names are different, it may further search a database of a local data center, if there is no target account name of the same name, it is determined that there is no data conflict, otherwise, if there is a target account name of the same name, it is determined that there is a data conflict, and then performing an operation of determining priorities of respective target objects.
For example, the local database of the data center may store priorities of all users, obtain priorities of the first target object and the second target object by means of table look-up, and then compare priorities of the two target objects to obtain which target object has a high priority and which target object has a low priority. The table storing the priorities of the target objects may be as shown in table 1: in table 1, the priorities of different target objects are represented by numerical values, wherein in implementation, the higher the numerical value is, the higher the priority may be, or the lower the numerical value is, the higher the priority may be. Of course, the priority may be identified by characters or a combination of characters and numerals, which is not limited in the present application, so long as the priority ordering of different target objects can be distinguished. Accordingly, table 1 is merely illustrative of the disclosed embodiments and is not limiting of the disclosed embodiments.
TABLE 1
| Object(s) | Priority level |
| Target object 1 | 2 |
| … | … |
| Target object n | 1 |
In step 302, the data center modifies an account name of a target object with a higher priority from among the first target object and the second target object to the target account name.
In another embodiment, the priorities of the different target objects may be dynamically determined based on the user's real-time status. For example, respective user information for different target objects may be obtained, and then the user priority may be determined in real-time based on the user information. For example, in the embodiment of the present disclosure, respective related data of the first target object and the second target object may be acquired in step A1; the relevant data includes: a user heat value and/or a user viscosity value; then, in step A2, respective priorities of the first target object and the second target object are determined based on a preset relationship between the related data and the priorities; wherein in a preset relationship, the user heat value and the user viscosity value are both positively correlated to the priority. Therefore, the priority of the user can be determined appropriately according to the characteristic information of different users, namely the user heat value and the user viscosity value, and the rationality of priority determination is improved.
Wherein the user heat value and the user viscosity value may be determined based on preset user behavior information.
For example, the user hotness value may relate to the following first type of user information within a specified time period: the online time length A, the uploaded work number B (which of course can also comprise the number of browsed videos), the user popularity value C (which can comprise the received praise number, the praise number given to other users or the sum of the two praise numbers), the attention quantity D (which can comprise the attention times, the attention times of other people or the sum of the two times), the comment times E (which can comprise the comment times of posting, the comment replied times, the comment times given to the work of other people or the sum of the related times of the comments). In practice, the user popularity value may be positively correlated with any of the first type of user information described above. Alternatively, the account liveness is determined in a weighted sum of various information and its weights as shown in equation (1):
F(i)＝a*A+b*B+c*C+d*D+e*E (1)
in the formula (1), a, b, c, d, e represents the weight of the related information, respectively, and a preset value may be empirically set.
The user information of the first type can well describe the heat degree of the user in all users, and can be understood as the popularity, so that the account name can be changed preferentially for the users with high heat degree.
Similarly, the user viscosity value may be related to the following second type of user information: the daily use duration a ', the number of pieces of fan B ', the praise information C ' (may include, for example, the number of praise received, the number of praise given to other users, or the sum of the two praise), the attention information D ' (may include, for example, the number of times of attention to others, or the sum of the two times), the number of reviews of works E ' (may include, for example, the number of times of posting reviews, the number of times of review given to own works by others, or the sum of the numbers related to the above reviews), the number of uploaded works F ' within a specified duration, the number of times of daily browsing of works G ', and the like. In practice, the account liveness may be positively correlated with any of the second type of user information described above. In the specific implementation, all the second-type user information can be adopted, and part of information can also be adopted. The account popularity may also be determined in a weighted summation of various information and its weights as shown in equation (2):
F(j)＝a’*A’+b’*B’+c’*C’+d’*D’+e’*E’+f’*F’+g’*G’ (2)
in the formula (2), a ', b ', c ', d ', e ', f ' and g ' represent weights of the related information, respectively, and a preset value may be empirically set.
The viscosity of the user in all users can be well described by adopting the first type of user information, so that the account name can be changed preferentially for the users with high viscosity.
After determining the priorities of the first target object and the second target object, in step 302, the account name of the target object with the higher priority among the first target object and the second target object is modified to the target account name. For example, the priority of the user B is higher than that of the user a, and the two users simultaneously desire to modify the account name to "the air-borne color cloud is good", then the account name of the user B with the higher priority is preferentially modified to "the air-borne color cloud is good".
In another embodiment, for a low priority target object, the request for modifying the account name is not satisfied with the current account name, and the target object is also intended to be the target account name, so that in order to make the low priority target object use a similar target account name as much as possible, the method is not limited to ensuring that the low priority target object can be successfully modified, and a new account name similar to the target account name is adopted to rename the low priority target object. In practice, as shown in fig. 3, a new account name of the target object with low priority is generated in step 303;
The new account name may be generated in any of two ways:
mode 1: and generating a suffix of the target account name, and adding the suffix to the target account name to obtain the new account name. For example, both user a and user B wish to update the account name to james, and if user B has a high priority, then user B's account name is updated to james01.
Mode 2: the method comprises the following steps:
step B1: searching a historical account name set of the target object with low priority.
Step B2: when a history account name composed of the target account name and other information is found in the history account name set, the history account name is taken as a new account name.
For example, it may be overridden whether the set of historical account names contains a historical account name in the form of a target account name + suffix. If present, may serve as a new account name. The suffix form may be determined based on the number of digits of the suffix, and when the number of digits of the suffix is less than a preset number of digits, for example, three digits, it may be determined that the target account name + the history account name in the suffix form is found.
Step B3: and when the historical account name is not found, generating an account name with the similarity to the target account name being greater than the preset similarity as the new account name.
For example, the account names that user B with low priority has used are james01 and florets, and if user B desires to update the user name to james, a similar account name james01 that user B has used is adopted as the new user name of user B.
Further, in another embodiment, a history user name having a similarity with the target account name greater than a specified threshold value may be searched for as a new user name from among a history user name set of the target object having a low priority. The similarity may be determined using the number of characters matched. For example, if the number of characters in the history account name and the target account name is n and the number of characters in the target account name is m, the similarity between the history account name and the target account name is (n/m). Of course, in another embodiment, the similarity may be a semantic similarity. Thus, the account names with the same semantic meaning can be allocated to the users so as to meet the expectations of the users on the account names.
After the new account name is obtained for the low priority target object, in step 304, the account name of the low priority target object may be modified to the new account name; then, in step 305, the new account name is notified to the target object with low priority, so that the target object can learn the account name actually obtained by itself, and based on the new account name, a subsequent operation can be performed. Furthermore, in the embodiment of the present disclosure, in order to facilitate the low-priority target object to learn the reason why the account name is modified, the account name modification reason may be simultaneously notified to the low-priority target object. For example, as shown in fig. 4, a target object of low priority may be notified by way of private letter that its account name is modified to james01 and that its modification is due to renaming with other users.
In addition, in another embodiment, a modification interface for the new account may also be provided in the hint page. As shown in fig. 4, an account name link may be provided. The target object of the modified account name may click on the link to enter a renaming user interface so that when the target object of the modified account name is not satisfied with the new account name, it may be renamed according to its own preference. Renaming may be followed by processing in accordance with aspects of embodiments of the present disclosure.
For further understanding, the account information modification method provided by the embodiment of the present disclosure is described below with reference to fig. 5. When a local user a of the data center a first initiates a modification request for modifying an account name to james, and then a user B of the data center B initiates a modification request for modifying an account name to james, an implementation scheme of the embodiment of the disclosure is as shown in fig. 5: assume that user a employs terminal device a and user B employs terminal device B.
In step 501, the terminal device a sends a modification request to modify the account name of the user a to james to the data center a.
In step 502, the terminal device B sends a modification request to modify the account name of the user B into james to the data center B.
In step 503, data center a modifies the account name of user a in local database a to james, and then, in step 704, data center a modifies the account name of user a to a modification request of james to data center B.
In step 505, data center B modifies the account name of user B in local database B to james, and then in step 706, data center B modifies the account name of user B to a modification request of james to data center a.
In step 507, the data center a and the data center B respectively determine the priorities of the user a and the user B, and when determining that the priority of the user a is higher than the priority of the user B, in step 508, the data center a keeps the account name of the user a unchanged, updates the user name of the user B to james01, and notifies the terminal device a of the success of the account name modification.
When it is determined in step 509 that the priority of the user a is higher than that of the user B, the data center B changes the user name of the user B to james01 and updates the account name of the user a to james, and then in step 510, notifies the terminal device B of the user B that the account name thereof is changed to james01 due to the duplicate name with other users.
In one implementation scenario, for example, the user a is a fan of numerous stars, which has a great influence in the internet, and when both a general user B and the user a desire to modify the account name to james, since the fan of numerous users a may conduct advertising or other activities based on james. Thus, user A would need the account name james. According to the method of the application, the priority of user A will be higher than that of user B, so that the user name of end user A is james so that the activities of user A can be performed normally.
As shown in fig. 6, based on the same inventive concept, an account information modification apparatus 600 is provided, including:
the priority determining module 601 is configured to execute determining, if a modification request sent by a first target object and a second target object respectively and modifying their account names to target account names is received in a specified duration, the respective priorities of the first target object and the second target object according to a preset rule;
an updating module 602 configured to perform modifying an account name of a target object with a high priority among the first target object and the second target object to the target account name.
In some embodiments, the update module is further configured to perform further comprising:
generating a new account name of a target object with low priority after the priority determining module determines the respective priorities of the first target object and the second target object;
modifying the account name of the target object with low priority to be the new account name; and is combined with the other components of the water treatment device,
and notifying the new account name to the target object with low priority.
In some embodiments, if the target object of the first target object and the second target object that sent the modification request first is taken as a preceding target object, and the target object that sent the modification request later is taken as a following target object, the apparatus further includes:
The conflict determination module is configured to execute a modification request for modifying the respective account names to the target account names, which is received in the specified time period and is sent by the first target object and the second target object respectively, according to the following method:
responding to the modification request of the prior target object, and modifying the account name of the prior target object into the target account name;
if the modification request of the subsequent target object is received in the appointed time, determining that the modification requests respectively sent by the first target object and the second target object are received in the appointed time;
the apparatus further comprises:
and the rollback module is configured to execute the operation of rollback the modified account name of the previous target object if the priority of the previous target object is low after the priority determining module executes the determination of the respective priorities of the first target object and the second target object according to the preset rule and before the updating module executes the modification of the account name of the target object with high priority in the first target object and the second target object to the target account name.
In some embodiments, the priority determination module is specifically configured to perform:
Acquiring respective related data of the first target object and the second target object; the related data includes: a user heat value and/or a user viscosity value;
determining respective priorities of the first target object and the second target object based on a preset relationship between the related data and priorities;
wherein the user heat value and the user viscosity value both have a positive correlation with the priority.
In some embodiments, respective related data of the first target object and the second target object is acquired; the related data includes: a user heat value and/or a user viscosity value;
determining respective priorities of the first target object and the second target object based on a preset relationship between the related data and priorities;
wherein the user heat value and the user viscosity value both have a positive correlation with the priority.
In some embodiments, the update module is specifically configured to perform:
and generating a suffix of the target account name, and adding the suffix to the target account name to obtain the new account name.
In some embodiments, the update module is specifically configured to perform:
Searching a historical account name set of the target object with low priority;
when the historical account name formed by the target account name and other information is found in the historical account name set, the historical account name is used as the new account name;
and when the historical account name is not found, generating an account name with the similarity with the target account name being larger than the preset similarity as the new account name.
In some embodiments, the updating module is further configured to perform notifying the low priority target object of the new account name while providing the low priority target object with a modification interface of the new account;
receiving the custom account name of the target object with low priority sent by the modification interface;
and updating the account name of the target object with low priority according to the custom account name.
In some embodiments, the updating module is further configured to perform the notifying the new account name to the low priority target object while notifying account name modification reasons to the low priority target object.
For implementation and beneficial effects of each operation in each account information modifying apparatus, reference may be made to the description in the foregoing method, and no further description is given here.
Having described the account information modification method and apparatus of the exemplary embodiments of the present disclosure, next, an electronic device according to another exemplary embodiment of the present disclosure is described.
Those skilled in the art will appreciate that the various aspects of the present disclosure may be implemented as a system, method, or program product. Accordingly, various aspects of the disclosure may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.
In some possible implementations, an electronic device according to the present disclosure may include at least one processor, and at least one memory. Wherein the memory stores program code that, when executed by the processor, causes the processor to perform the steps in the account information modification method according to various exemplary embodiments of the present disclosure described above in this specification. For example, the processor may perform steps as in an account information modification method.
An electronic device 130 according to such an embodiment of the present disclosure is described below with reference to fig. 7. The electronic device 130 shown in fig. 7 is merely an example and should not be construed to limit the functionality and scope of use of embodiments of the present disclosure in any way.
As shown in fig. 7, the electronic device 130 is in the form of a general-purpose electronic device. Components of electronic device 130 may include, but are not limited to: the at least one processor 131, the at least one memory 132, and a bus 133 connecting the various system components, including the memory 132 and the processor 131.
Bus 133 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, and a local bus using any of a variety of bus architectures.
Memory 132 may include readable media in the form of volatile memory such as Random Access Memory (RAM) 1321 and/or cache memory 1322, and may further include Read Only Memory (ROM) 1323.
Memory 132 may also include a program/utility 1325 having a set (at least one) of program modules 1324, such program modules 1324 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
The electronic device 130 may also communicate with one or more external devices 134 (e.g., keyboard, pointing device, etc.), one or more devices that enable a user to interact with the electronic device 130, and/or any device (e.g., router, modem, etc.) that enables the electronic device 130 to communicate with one or more other electronic devices. Such communication may occur through an input/output (I/O) interface 135. Also, electronic device 130 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 136. As shown, network adapter 136 communicates with other modules for electronic device 130 over bus 133. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 130, including, but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
In some possible implementations, aspects of an account information modification method provided by the present disclosure may also be implemented in the form of a program product including program code for causing a computer device to perform the steps of an account information modification method according to various exemplary embodiments of the present disclosure as described above when the program product is run on the computer device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The program product for account information modification of embodiments of the present disclosure may employ a portable compact disc read only memory (CD-ROM) and include program code and may run on an electronic device. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the consumer electronic device, partly on the consumer electronic device, as a stand-alone software package, partly on the consumer electronic device, partly on the remote electronic device, or entirely on the remote electronic device or server. In the case of remote electronic devices, the remote electronic device may be connected to the consumer electronic device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external electronic device (e.g., connected through the internet using an internet service provider).
It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, such a division is merely exemplary and not mandatory. Indeed, the features and functions of two or more of the units described above may be embodied in one unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one unit described above may be further divided into a plurality of units to be embodied.
Furthermore, although the operations of the methods of the present disclosure are depicted in the drawings in a particular order, this is not required to or suggested that these operations must be performed in this particular order or that all of the illustrated operations must be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform.
It will be apparent to those skilled in the art that embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable account information modifying apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable account information modifying apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable account information modifying apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable account information modifying apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present disclosure have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the disclosure.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present disclosure without departing from the spirit or scope of the disclosure. Thus, the present disclosure is intended to include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (18)
1. A method for modifying account information, the method comprising:
if a modification request which is sent by a first target object and a second target object respectively and modifies the respective account name into a target account name is received in a designated time period, determining the respective priorities of the first target object and the second target object according to a preset rule;
modifying the account name of a target object with high priority in the first target object and the second target object into the target account name;
after the determining the priorities of the first target object and the second target object, the method further includes:
generating a new account name of the target object with low priority;
modifying the account name of the target object with low priority to be the new account name; and is combined with the other components of the water treatment device,
and notifying the new account name to the target object with low priority.
2. The method according to claim 1, wherein if a target object of the first target object and the second target object that sent the modification request first is taken as a preceding target object, and a target object of the later modification request is taken as a later target object, determining that the modification requests sent by the first target object and the second target object respectively and modifying the respective account names to the target account names are received in the specified duration includes:
responding to the modification request of the prior target object, and modifying the account name of the prior target object into the target account name;
if the modification request of the subsequent target object is received in the appointed time, determining that the modification requests respectively sent by the first target object and the second target object are received in the appointed time;
after determining the priorities of the first target object and the second target object according to a preset rule, and before modifying the account name of the target object with the higher priority in the first target object and the second target object to the target account name, the method further includes:
and if the priority of the prior target object is low, rolling back the operation of modifying the account name of the prior target object.
3. The method according to any one of claims 1-2, wherein determining the respective priorities of the first target object and the second target object according to a preset rule comprises:
acquiring respective related data of the first target object and the second target object; the related data includes: a user heat value and/or a user viscosity value;
determining respective priorities of the first target object and the second target object based on a preset relationship between the related data and priorities;
wherein the user heat value and the user viscosity value both have a positive correlation with the priority.
4. A method according to claim 3, wherein the user hotness value is positively correlated with at least one of the following information by the user over a specified period of time: on-line time length, uploading number of works, praise number, attention amount and comment number;
a weighted sum of the user viscosity value and a plurality of the following information: daily use time length, vermicelli number, work comment number, number of uploaded works in the appointed time length and daily browsed times of works;
the determining the respective priorities of the first target object and the second target object based on the preset relation between the related data and the priorities includes:
When the related data comprises the user heat value and the user viscosity value, carrying out weighted summation on the user heat value and the user viscosity value of the first target object to obtain the priority of the first target object; and is combined with the other components of the water treatment device,
and carrying out weighted summation on the user heat value and the user viscosity value of the second target object to obtain the priority of the second target object.
5. The method of claim 1, wherein generating a new account name for a low priority target object comprises:
and generating a suffix of the target account name, and adding the suffix to the target account name to obtain the new account name.
6. The method of claim 1, wherein generating a new account name for a low priority target object comprises:
searching a historical account name set of the target object with low priority;
when the historical account name formed by the target account name and other information is found in the historical account name set, the historical account name is used as the new account name;
and when the historical account name is not found, generating an account name with the similarity with the target account name being larger than the preset similarity as the new account name.
7. The method of claim 1, wherein the notifying the new account name to the low priority target object is performed simultaneously with the method further comprising:
providing a modification interface of the new account to the target object with low priority;
receiving the custom account name of the target object with low priority sent by the modification interface;
and updating the account name of the target object with low priority according to the custom account name.
8. The method of claim 1, wherein the notifying the new account name to the low priority target object is performed simultaneously with the method further comprising:
and notifying the account name modification reason to the target object with low priority.
9. An account information modifying apparatus, the apparatus comprising:
the priority determining module is configured to execute the steps of determining the respective priorities of the first target object and the second target object according to a preset rule if a modification request which is sent by the first target object and the second target object respectively and is used for modifying the respective account names into target account names is received in a specified time period;
an updating module configured to perform modification of an account name of a target object with a high priority among the first target object and the second target object to the target account name;
The update module is further configured to perform operations further comprising:
generating a new account name of a target object with low priority after the priority determining module determines the respective priorities of the first target object and the second target object;
modifying the account name of the target object with low priority to be the new account name; and is combined with the other components of the water treatment device,
and notifying the new account name to the target object with low priority.
10. The apparatus of claim 9, wherein if a target object of the first target object and the second target object that sent the modification request first is taken as a preceding target object and a target object of the later modification request is taken as a following target object, the apparatus further comprises:
the conflict determination module is configured to execute a modification request for modifying the respective account names to the target account names, which is received in the specified time period and is sent by the first target object and the second target object respectively, according to the following method:
responding to the modification request of the prior target object, and modifying the account name of the prior target object into the target account name;
if the modification request of the subsequent target object is received in the appointed time, determining that the modification requests respectively sent by the first target object and the second target object are received in the appointed time;
The apparatus further comprises:
and the rollback module is configured to execute the operation of rollback the modified account name of the previous target object if the priority of the previous target object is low after the priority determining module executes the determination of the respective priorities of the first target object and the second target object according to the preset rule and before the updating module executes the modification of the account name of the target object with high priority in the first target object and the second target object to the target account name.
11. The apparatus according to any of claims 9-10, wherein the priority determination module is specifically configured to perform:
acquiring respective related data of the first target object and the second target object; the related data includes: a user heat value and/or a user viscosity value;
determining respective priorities of the first target object and the second target object based on a preset relationship between the related data and priorities;
wherein the user heat value and the user viscosity value both have a positive correlation with the priority.
12. The apparatus of claim 11, wherein the user hotness value is positively correlated with at least one of the following information by the user for a specified duration: on-line time length, uploading number of works, praise number, attention amount and comment number;
A weighted sum of the user viscosity value and a plurality of the following information: daily use time length, vermicelli number, work comment number, number of uploaded works in the appointed time length and daily browsed times of works;
the priority determination module is specifically configured to perform:
when the related data comprises the user heat value and the user viscosity value, carrying out weighted summation on the user heat value and the user viscosity value of the first target object to obtain the priority of the first target object; and is combined with the other components of the water treatment device,
and carrying out weighted summation on the user heat value and the user viscosity value of the second target object to obtain the priority of the second target object.
13. The apparatus according to claim 9, wherein the updating module is specifically configured to perform:
and generating a suffix of the target account name, and adding the suffix to the target account name to obtain the new account name.
14. The apparatus according to claim 9, wherein the updating module is specifically configured to perform:
searching a historical account name set of the target object with low priority;
when the historical account name formed by the target account name and other information is found in the historical account name set, the historical account name is used as the new account name;
And when the historical account name is not found, generating an account name with the similarity with the target account name being larger than the preset similarity as the new account name.
15. The apparatus of claim 9, wherein the update module is further configured to perform notifying the low priority target object of the new account name while providing a modification interface of the new account to the low priority target object;
receiving the custom account name of the target object with low priority sent by the modification interface;
and updating the account name of the target object with low priority according to the custom account name.
16. The apparatus of claim 9, wherein the update module is further configured to perform the notifying the low priority target object of the new account name while notifying the low priority target object of account name modification reasons.
17. An electronic device comprising at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-8.
18. A computer storage medium, characterized in that the computer storage medium stores a computer program for causing a computer to perform the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010955194.6A CN112199380B (en) | 2020-09-11 | 2020-09-11 | Account information modification method, device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010955194.6A CN112199380B (en) | 2020-09-11 | 2020-09-11 | Account information modification method, device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112199380A CN112199380A (en) | 2021-01-08 |
| CN112199380B true CN112199380B (en) | 2023-11-28 |
Family
ID=74014780
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010955194.6A Active CN112199380B (en) | 2020-09-11 | 2020-09-11 | Account information modification method, device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112199380B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105101196A (en) * | 2014-05-06 | 2015-11-25 | 阿里巴巴集团控股有限公司 | User account management method and device |
| CN105223913A (en) * | 2014-06-30 | 2016-01-06 | 青岛海尔智能家电科技有限公司 | The method controlled for equipment and device |
| CN108280620A (en) * | 2017-08-28 | 2018-07-13 | 平安科技（深圳）有限公司 | Amending method, device, storage medium and the terminal of account name |
| CN109753621A (en) * | 2019-01-04 | 2019-05-14 | 北京字节跳动网络技术有限公司 | User information processing method, device, electronic equipment and readable storage medium storing program for executing |
| CN110704818A (en) * | 2018-07-10 | 2020-01-17 | 北京国双科技有限公司 | User information modification method and device |
| CN111083684A (en) * | 2019-12-23 | 2020-04-28 | 维沃移动通信有限公司 | Method for controlling electronic equipment and electronic equipment |
-
2020
- 2020-09-11 CN CN202010955194.6A patent/CN112199380B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105101196A (en) * | 2014-05-06 | 2015-11-25 | 阿里巴巴集团控股有限公司 | User account management method and device |
| CN105223913A (en) * | 2014-06-30 | 2016-01-06 | 青岛海尔智能家电科技有限公司 | The method controlled for equipment and device |
| CN108280620A (en) * | 2017-08-28 | 2018-07-13 | 平安科技（深圳）有限公司 | Amending method, device, storage medium and the terminal of account name |
| CN110704818A (en) * | 2018-07-10 | 2020-01-17 | 北京国双科技有限公司 | User information modification method and device |
| CN109753621A (en) * | 2019-01-04 | 2019-05-14 | 北京字节跳动网络技术有限公司 | User information processing method, device, electronic equipment and readable storage medium storing program for executing |
| CN111083684A (en) * | 2019-12-23 | 2020-04-28 | 维沃移动通信有限公司 | Method for controlling electronic equipment and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112199380A (en) | 2021-01-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9990610B2 (en) | Systems and methods for providing suggested reminders | |
| CN109670101B (en) | Crawler scheduling method and device, electronic equipment and storage medium | |
| US9588760B1 (en) | Software application development feature and defect selection | |
| CN106844744B (en) | Click model application method and device and search system | |
| CN113450162A (en) | User grouping method, device and storage medium | |
| CN108769157B (en) | Message popup display method and device, computing equipment and computer storage medium | |
| US20170235464A1 (en) | Computerized Search System Providing Nested Application Card Results | |
| CN115202847A (en) | Task scheduling method and device | |
| GB2536355A (en) | System, method, and non-transitory computer-readable storage media for displaying product information on websites | |
| US10261971B2 (en) | Partitioning links to JSERPs amongst keywords in a manner that maximizes combined improvement in respective ranks of JSERPs represented by respective keywords | |
| US10915557B2 (en) | Product classification data transfer and management | |
| CN112199380B (en) | Account information modification method, device, electronic equipment and storage medium | |
| CN111861322A (en) | Emergency equipment material auxiliary control method, system and storage medium | |
| CN116661936A (en) | Page data processing method and device, computer equipment and storage medium | |
| US10817496B2 (en) | Forum inspection based on correlation rating of response poster | |
| CN115238194A (en) | Book recommendation method, computing device and computer storage medium | |
| CN114386734A (en) | Enterprise management system for technical analysis using artificial intelligence and machine learning | |
| CN113094602A (en) | Hotel recommendation method, system, equipment and medium | |
| EP2667338A1 (en) | Methods and apparatus for use in adding contacts between profiles of different social networks | |
| CN111143328A (en) | Agile business intelligent data construction method, system, equipment and storage medium | |
| US10430427B2 (en) | Partitioning links to JSERPs amongst keywords in a manner that maximizes combined weighted gain in a metric associated with events of certain type observed in the on-line social network system with respect to JSERPs represented by keywords | |
| CN106716969A (en) | Technologies for pre-action execution | |
| CN109831537B (en) | Software modular prefetching model and method based on P2P autonomous domain | |
| CN112016793B (en) | Resource allocation method and device based on target user group and electronic equipment | |
| US11138654B1 (en) | Method and system for dynamic traffic shaping of deals to reduce server stress |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |