Binding relationship conflict verification method and related equipment for private numbers

Abstract

The present application provides a method, device, electronic device, and storage medium for checking conflicts in binding relationships of private numbers. The method comprises: in response to a user's request to add or update a binding relationship, determining a target private number included in the newly added or updated binding relationship, and determining a binding mode for the newly added or updated binding relationship; based on the binding mode, reading at least one key-value pair corresponding to at least one existing binding relationship from a cache; the key of the key-value pair includes an existing private number, and the value of the key-value pair includes an identification number of an existing binding relationship to which the existing private number belongs; searching the at least one key-value pair using the target private number as a key, and determining a conflict checking result based on the search result.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, electronic device, and storage medium for checking binding conflicts of private numbers. Background Art

[0002] A privacy number, also known as a virtual number, is a service that can be used in a variety of business scenarios (such as food delivery, taxi-hailing, express delivery, sales, etc.). It hides the real numbers of business personnel (riders, drivers, couriers, sales, etc.) and users, allowing them to contact each other only through a privacy number, thereby protecting the privacy of both parties' numbers.

[0003] In related technologies, platforms providing privacy number services bind user numbers to corresponding privacy numbers to form a binding relationship, store this binding relationship in a database, and then provide the privacy number service. In actual use, when conflicts arise between binding relationships, privacy numbers can be assigned to different users, impacting their normal use. Therefore, maintaining binding relationships and verifying conflicts are crucial tasks in privacy number services.

[0004] However, binding relationship conflict verification solutions in related technologies generally have problems such as poor service performance and inability to support common binding modes. Summary of the Invention

[0005] In view of this, the purpose of this application is to propose a method, device, electronic device and storage medium for checking the binding relationship conflict of private numbers.

[0006] Based on the above objectives, this application provides a method for checking binding conflicts of private numbers, including:

[0007] In response to a user's request to add or update a binding relationship, determining a target privacy number included in the newly added or updated binding relationship, and determining a binding mode for the newly added or updated binding relationship;

[0008] Reading, from a cache, at least one key-value pair corresponding to at least one existing binding relationship according to the binding mode; the key of the key-value pair includes an existing private number, and the value of the key-value pair includes an identification number of an existing binding relationship to which the existing private number belongs;

[0009] Using the target private number as a key, searching is performed in the at least one key-value pair, and a conflict check result is determined according to the search result.

[0010] In some embodiments, when the binding mode is exclusive mode, the key-value pair uses an existing private number as a key and an identification number of an existing binding relationship to which the existing private number belongs as a value;

[0011] Determining the conflict check result according to the search result includes:

[0012] In response to retrieving a value corresponding to the target private number, determining that there is an existing binding relationship that conflicts with the newly added or updated binding relationship;

[0013] In response to not retrieving a value corresponding to the target private number, it is determined that there is no existing binding relationship that conflicts with the newly added or updated binding relationship.

[0014] In some embodiments, when the binding mode is a sharing mode, the key-value pair uses an existing private number as a key and at least one data pair corresponding to the existing private number as a value; the data pair includes: a user number bound to the existing private number, and an identification number of an existing binding relationship to which the existing private number belongs;

[0015] Determining the conflict check result according to the search result includes:

[0016] In response to retrieving a data pair including a target user number bound to the target privacy number, determining that there is an existing binding relationship that conflicts with the newly added or updated binding relationship;

[0017] In response to not retrieving a data pair including the target user number bound to the target privacy number, it is determined that there is no existing binding relationship that conflicts with the newly added or updated binding relationship.

[0018] In some embodiments, when the binding mode is a sharing mode with an extension number, any existing binding relationship corresponds to a first key-value pair and a second key-value pair;

[0019] The first key-value pair uses an existing private number as a key and at least one first data pair corresponding to the existing private number as a value; the first data pair includes: a user number bound to the existing private number, and an identification number of an existing binding relationship to which the existing private number belongs;

[0020] The second key-value pair uses an existing private number as a key and at least one second data pair corresponding to the existing private number as a value; the second data pair includes: an extension number bound to the existing private number, and an identification number of an existing binding relationship to which the existing private number belongs;

[0021] Determining the conflict check result according to the search result includes:

[0022] In response to retrieving a first data pair including a target user number bound to the target privacy number and / or retrieving a second data pair including a target extension number bound to the target privacy number, determining that there is an existing binding relationship that conflicts with the newly added or updated binding relationship;

[0023] In response to not retrieving a first data pair including a target user number bound to the target privacy number and not retrieving a second data pair including a target extension number bound to the target privacy number, it is determined that there is no existing binding relationship that conflicts with the newly added or updated binding relationship.

[0024] In some implementations, after determining that there is an existing binding relationship that conflicts with the newly added or updated binding relationship, the method further includes:

[0025] The identification number of the conflicting existing binding relationship is returned to the user.

[0026] In some implementations, after returning the identification number of the conflicting existing binding relationship to the user, the method further includes:

[0027] According to the operation instruction submitted by the user, the existing binding relationship with conflict is released, or the target privacy number is changed.

[0028] In some implementations, after returning the identification number of the conflicting existing binding relationship to the user, the method further includes:

[0029] Storing the target private number in a preset conflicting private number set;

[0030] In response to a request from any user to add or update a binding relationship, a corresponding privacy number is determined for the newly added or updated binding relationship according to the set of conflicting privacy numbers.

[0031] Based on the same technical concept, the present application also provides a device for checking binding conflicts of private numbers, including:

[0032] a determination module configured to, in response to a user's request to add or update a binding relationship, determine a target privacy number included in the newly added or updated binding relationship, and determine a binding mode for the newly added or updated binding relationship;

[0033] a reading module configured to read, from a cache, at least one key-value pair corresponding to at least one existing binding relationship according to the binding mode; the key of the key-value pair comprising an existing private number, and the value of the key-value pair comprising an identification number of the existing binding relationship to which the existing private number belongs;

[0034] The verification module is configured to use the target privacy number as a key to search in the at least one key-value pair, and determine a conflict verification result according to the search result.

[0035] Based on the same technical concept, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, any of the methods described above is implemented.

[0036] Based on the same technical concept, the present application also provides a non-transitory computer-readable storage medium, which stores computer instructions, and the computer instructions are used to enable a computer to execute any of the methods described above.

[0037] From the above, it can be seen that the binding relationship conflict verification method, device, electronic device and storage medium for privacy numbers provided by this application, in order to avoid the database performance bottleneck problem, the storage and maintenance of existing binding relationships are set in the cache, based on the high-speed data reading and writing capabilities of the cache, to achieve efficient and fast storage and maintenance of existing binding relationships. In addition, a corresponding data model is constructed in the cache for storage of binding relationships of different binding modes, and the data model is constructed as a key-value pair including an existing privacy number and an identification number of an existing binding relationship; when performing conflict verification, the data model in the cache is retrieved according to the binding mode, and the conflict verification result is determined according to the retrieval result. The data model corresponding to different binding modes can support conflict verification of various common binding modes, wherein the identification number of the binding relationship can also be used to verify and determine when a conflict occurs, and accurately determine the existing binding relationship that has a conflict, further improving the service performance and data processing efficiency of binding relationship conflict verification. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in this application or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are merely embodiments of this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0039] Figure 1 A schematic diagram of an application scenario of an embodiment of the present application;

[0040] Figure 2 This is a flowchart of a method for checking conflicts in binding relationships of private numbers according to an embodiment of the present application;

[0041] Figure 3 This is a schematic diagram of the data structure of key-value pairs used in exclusive mode in an embodiment of the present application;

[0042] Figure 4 Schematic diagram of the data structure of key-value pairs used in the shared mode AXB in an embodiment of the present application;

[0043] Figure 5 Schematic diagram of the data structure of key-value pairs applied to the shared mode AXNE with extension numbers in an embodiment of the present application;

[0044] Figure 6 This is a schematic diagram of the structure of a device for checking the binding relationship conflict of a private number according to an embodiment of the present application;

[0045] Figure 7 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the objectives, technical solutions and advantages of this application more clear, this application is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0047] The principles and spirit of the present application will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided solely to enable those skilled in the art to better understand and implement the present application, and are not intended to limit the scope of the present application in any way. Rather, these embodiments are provided to make the present application more thorough and complete, and to fully convey the scope of the present application to those skilled in the art.

[0048] According to the implementation of the present application, a method, device, electronic device and storage medium for checking the binding relationship conflict of a private number are proposed.

[0049] It should be understood herein that any number of elements in the drawings is for illustration only and not for limitation, and any naming is only for distinction and does not have any limiting meaning.

[0050] The principles and spirit of the present application are explained in detail below with reference to several representative implementations of the present application.

[0051] In the related art, the privacy number service will store the binding relationship between the user number and the corresponding privacy number in a predetermined data structure in the database. When checking whether the existing binding relationship conflicts, the newly added or updated binding relationship will be used to search and query all the existing binding relationships stored in the database. If the corresponding result is retrieved, it indicates that there is a conflict. Otherwise, it indicates that there is no conflict. The above-mentioned conflict verification scheme based on the binding relationship stored in the database can achieve acceptable service performance when the number of checks and the number of binding relationships are not large. However, when the number of checks and the number of binding relationships reach a certain number, the database will reach a performance bottleneck, which will affect the service performance and even cause the service to be unavailable.

[0052] In related technologies, to adapt to different business scenarios, privacy number services also set different types of binding modes when implementing them. Refer to Table 1 for a description of the binding modes.

[0053] Table 1 Description of binding mode

[0054]

[0055]

[0056] As can be seen from the different types of binding modes mentioned above, the judgment logic used in the corresponding conflict verification will be more complex based on the characteristics of different binding modes. The search and query method based on the binding relationship stored in the database in the related technology will undoubtedly exacerbate the problem of poor service performance caused by database performance bottlenecks. In addition, when the verification finds that there is a conflict in the binding relationship, the user often wants to specifically determine which existing binding relationship is in conflict so as to take appropriate measures. The method in the related technology can only query the database for the conflicting binding relationship during the verification. This also further increases the processing logic and data processing volume, seriously affecting service performance.

[0057] In the related art, there are also some solutions for performing binding relationship conflict verification for different binding modes, but they still cannot support binding relationship conflict verification for all binding modes.

[0058] In response to the above problems, the present application provides a binding relationship conflict verification scheme for privacy numbers. In order to avoid database performance bottlenecks, the storage and maintenance of existing binding relationships are set in the cache. Based on the high-speed data reading and writing capabilities of the cache, efficient and fast storage and maintenance of existing binding relationships are achieved. In addition, corresponding data models are constructed in the cache for storage of binding relationships of different binding modes. The data model is constructed as a key-value pair including an existing privacy number and an identification number of an existing binding relationship. When performing conflict verification, the data model in the cache is retrieved according to the binding mode, and the conflict verification result is determined based on the retrieval result. The data model corresponding to different binding modes can support conflict verification for various common binding modes. When a conflict is determined, the identification number of the binding relationship can also be used to verify and determine that a conflict occurs, and accurately determine the existing binding relationship that has a conflict, thereby further improving the service performance and data processing efficiency of binding relationship conflict verification.

[0059] refer to Figure 1, is a schematic diagram of an application scenario of the binding relationship conflict verification method for a private number according to an embodiment of the present application. The application scenario includes a terminal device 101, a server 102, and a data storage system 103. Among them, the terminal device 101, the server 102, and the data storage system 103 can be connected through a wired or wireless communication network. The terminal device 101 includes but is not limited to a desktop computer, a mobile phone, a mobile computer, a tablet computer, a media player, a smart wearable device, a personal digital assistant (PDA), or other electronic devices capable of realizing the above functions. The server 102 and the data storage system 103 can both be independent physical servers, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0060] Server 102 provides a private number service to users of terminal device 101. After a user successfully obtains permission for the private number service from server 102 through terminal device 101, they can set up and maintain a certain number of binding relationships. Data storage system 103 stores the data corresponding to the binding relationships set by the user. Each binding relationship includes a user number and a corresponding private number. Subsequently, the user can use terminal device 101 to contact other users using the private number based on the binding relationship.

[0061] The following combination Figure 1 The following application scenarios are used to describe the method for checking conflicts in private number binding relationships according to an exemplary embodiment of the present application. It should be noted that the above application scenarios are merely provided to facilitate understanding of the spirit and principles of the present application, and the embodiments of the present application are not limited in this respect. Rather, the embodiments of the present application can be applied to any applicable scenario.

[0062] First, an embodiment of the present application provides a method for checking binding relationship conflicts of private numbers, which is applied to a server.

[0063] refer to Figure 2 The binding relationship conflict verification method of the privacy number of this embodiment may include the following steps:

[0064] Step S201: In response to a user's request to add or update a binding relationship, determine a target private number included in the newly added or updated binding relationship, and determine a binding mode of the newly added or updated binding relationship.

[0065] During specific implementation, the server receives a request for adding or updating a binding relationship submitted by the user through a terminal device. Adding a new binding relationship means establishing and storing a new binding relationship, and the binding relationship may include: the user number included in the newly added binding relationship, the privacy number bound to the user number, and the binding mode of the newly added binding relationship. Updating a binding relationship means updating a binding relationship that has been established and stored by the user, and the content of the update generally refers to updating the privacy number in the binding relationship. In addition, in order to clearly distinguish it from other similar features, the privacy number included in the newly added or updated binding relationship is referred to as the target privacy number in the embodiment of the present application.

[0066] In specific implementations, in response to a user's request to add or update a binding relationship, the server determines the target private number included in the newly added or updated binding relationship, as well as the binding mode of the newly added or updated binding relationship. The binding mode can be any of the aforementioned AX, AXB, AXN, and AXNE.

[0067] Step S202: read at least one key-value pair corresponding to at least one existing binding relationship from the cache according to the binding mode; the key of the key-value pair includes an existing privacy number, and the value of the key-value pair includes the identification number of the existing binding relationship to which the existing privacy number belongs.

[0068] In a specific implementation, after determining the binding mode of a newly added or updated binding relationship, the data model corresponding to the binding mode stored in the cache is read based on the binding mode. The data model includes at least one key-value pair corresponding to at least one existing binding relationship. A key-value pair is a data representation in a computer system that is used to express a set of data or a set of data groups with corresponding relationships.

[0069] In specific implementations, depending on the specific binding mode, key-value pairs can correspond one-to-one with existing binding relationships, or one existing binding relationship can correspond to multiple key-value pairs. For example, if a user stores and maintains 10 existing binding relationships, then at least 10 key-value pairs corresponding to these 10 existing binding relationships will be stored in the cache. The number of key-value pairs corresponding to each existing binding relationship will be determined based on specific implementation needs.

[0070] During specific implementation, for any key-value pair, the key of the key-value pair includes the privacy number in the existing binding relationship, that is, an existing privacy number; the value of the key-value pair at least includes the identification number of the existing binding relationship to which the existing privacy number belongs. Among them, the identification number is the identification number set for each existing binding relationship in the embodiment of the present application, and one identification number uniquely corresponds to an existing binding relationship, that is, an existing binding relationship can be uniquely determined by the identification number in the embodiment of the present application. Among them, the specific form and content of the number used to implement the identification number is not specifically limited in the embodiment of the present application, as long as it can achieve the unique identification function of the existing binding relationship.

[0071] In some optional implementations, the aforementioned exclusive mode AX or AXN can be understood as private number X being exclusive to user number A. This means that any other number wishing to contact user number A must use private number X. Based on the aforementioned characteristics of the exclusive mode, when the binding mode is exclusive, the key-value pairs stored in the cache use the existing private number as the key and the identification number of the existing binding relationship to which the existing private number belongs as the value. In specific implementations, key-value pairs used in exclusive mode can be stored in the cache using any type of data structure, such as a string.

[0072] refer to Figure 3 , a diagram of the key-value pair data structure used in exclusive mode. Here, X1, X2, X3, etc. are different existing private numbers, and ld1, ld2, ld3, etc. are the identification numbers of the corresponding existing binding relationships. A key-value pair is constructed with an existing private number as the key and the corresponding existing binding relationship identification number as the value, for example: X1-ld1.

[0073] In some optional implementations, for the aforementioned sharing mode AXB, it can be understood that the private number X is shared by a combination of different user numbers A and B. Based on the characteristics of the above-mentioned sharing mode AXB, when the binding mode is sharing mode AXB, the key-value pairs stored in the cache use the existing private number as the key and at least one data pair corresponding to the existing private number as the value; in this embodiment, the data pair specifically includes: the user number bound to the existing private number, and the identification number of the existing binding relationship to which the existing private number belongs. In specific implementation, the key-value pairs applied to the sharing mode AXB can be implemented through two sets of nested key-value structures. Under the key-value structure with the existing private number as the key and the corresponding data pair as the value, the data pair can also be implemented as a key-value structure. For example, a key-value correspondence between the user number and the identification number of the existing binding relationship can be constructed through a field data structure. It is understandable that the key-value pairs applied to the sharing mode AXB can also be stored in the cache through any other type of data structure, and this is not limited in the embodiments of the present application.

[0074] refer to Figure 4 , which is a diagram of the key-value pair data structure used in shared mode AXB. Here, X1, X2, etc. are different existing private numbers, user numbers 1-4, etc. are the corresponding user numbers bound to the existing private numbers (any one of user numbers 1-4 includes two user numbers, namely user numbers A and B mentioned above), and ld1-ld4, etc. are the identification numbers of the corresponding existing binding relationships.

[0075] In some optional implementations, for the aforementioned shared mode AXNE with extension numbers, it can be understood that the privacy number X is shared by a combination of user number A and different extension numbers E. Based on the characteristics of the above-mentioned shared mode AXNE with extension numbers, it is necessary to establish a key-value correspondence for the user number and the extension number respectively. Therefore, when the binding mode is the shared mode AXNE with extension numbers, for any key-value pair stored in the cache, the key-value pair corresponds to two key-value pairs, which are respectively referred to as the first key-value pair and the second key-value pair in the embodiment of the present application. The first key-value pair is used to express the correspondence between the user numbers, with the existing privacy number as the key and at least one first data pair corresponding to the existing privacy number as the value; the first data pair specifically includes: the user number bound to the existing privacy number, and the identification number of the existing binding relationship to which the existing privacy number belongs. The second key-value pair is used to express the correspondence of the extension number, with the existing privacy number as the key and at least one second data pair corresponding to the existing privacy number as the value; the second data pair specifically includes: the extension number bound to the existing privacy number, and the identification number of the existing binding relationship to which the existing privacy number belongs. In specific implementation, for the first key-value pair and the second key-value pair corresponding to the shared mode AXNE with the extension number, two key-value correspondences can be constructed respectively through the hash data structure; for the first data pair and the second data pair, similar to the shared mode AXB, the key-value correspondence can be constructed accordingly through the field data structure. It can be understood that the key-value pair applied to the shared mode AXNE with the extension number can also be stored in the cache through any other type of data structure, and this is not limited in the embodiments of the present application.

[0076] refer to Figure 5 , which is a diagram of the key-value data structure for the shared mode AXNE with extension numbers. Here, X1, X2, etc. are different existing private numbers, A1-A4, etc. are the user numbers bound to the existing private numbers, E1-E4, etc. are the corresponding extension numbers, and ld1-ld4, etc. are the identification numbers of the corresponding existing binding relationships.

[0077] Step S203: Using the target private number as a key, search the at least one key-value pair, and determine a conflict check result based on the search result.

[0078] In specific implementation, according to the aforementioned key-value pairs corresponding to the existing binding relationships constructed based on different binding modes and stored in the cache, the target privacy number included in the newly added or updated binding relationship is used as the key to search in the corresponding key-value pairs read, and the conflict check result can be determined based on the search result. Specifically, when the corresponding value is retrieved with the target privacy number as the key, it indicates that the target privacy number already exists in the existing binding relationship, that is, the newly added or updated binding relationship conflicts with the existing binding relationship; when the corresponding value is not retrieved with the target privacy number as the key, it indicates that the target privacy number does not exist in the existing binding relationship, that is, the newly added or updated binding relationship does not conflict with the existing binding relationship.

[0079] In some optional implementations, for different binding modes, the specific determination method for determining the conflict check result based on the search results can also be set accordingly, specifically including:

[0080] When the binding mode is exclusive mode AX or AXN, in response to retrieving a value corresponding to the target privacy number, it is determined that there is an existing binding relationship that conflicts with the newly added or updated binding relationship; conversely, in response to not retrieving a value corresponding to the target privacy number, it is determined that there is no existing binding relationship that conflicts with the newly added or updated binding relationship.

[0081] When the binding mode is shared mode AXB, in response to retrieving a data pair including a target user number bound to a target privacy number, it is determined that there is an existing binding relationship that conflicts with the newly added or updated binding relationship; conversely, in response to not retrieving a data pair including a target user number bound to a target privacy number, it is determined that there is no existing binding relationship that conflicts with the newly added or updated binding relationship.

[0082] When the binding mode is the shared mode AXNE with an extension number, in response to retrieving a first data pair including a target user number bound to a target privacy number, and / or retrieving a second data pair including a target extension number bound to a target privacy number, it is determined that there is an existing binding relationship that conflicts with the newly added or updated binding relationship; conversely, in response to not retrieving the first data pair including the target user number bound to the target privacy number, and not retrieving the second data pair including the target extension number bound to the target privacy number, it is determined that there is no existing binding relationship that conflicts with the newly added or updated binding relationship.

[0083] In some optional implementations, for any binding mode, after searching the key-value pairs stored in the cache using the target privacy number as the key and determining that there is an existing binding relationship that conflicts with the newly added or updated binding relationship, the method of the embodiment of the present application may further include the step of returning to the user the identification number of the existing binding relationship in conflict. In the embodiment of the present application, the identification number can uniquely identify an existing binding relationship. Therefore, after retrieving the corresponding value using the target privacy number as the key, the identification number included in the retrieved value can be obtained, and the user can use the identification number to correspondingly determine the existing binding relationship that conflicts with the newly added or updated binding relationship. The conflict can then be processed subsequently.

[0084] In some optional implementations, after returning the identification number of the conflicting existing binding relationship to the user, the conflicting binding relationship may be further resolved based on the user's operational instructions. Specifically, resolving the conflicting binding relationship may include, based on the operational instructions submitted by the user, dissolving the conflicting existing binding relationship or changing the target privacy number. In specific implementations, after returning the identification number of the conflicting existing binding relationship to the user, the user can be informed of which existing binding relationship conflicts with the newly added or updated binding relationship. Based on this, the user can take appropriate action to resolve the conflict based on the specific business scenario or implementation needs. In some cases, the target privacy number in the newly added or updated binding relationship is actively specified by the user, so the user can choose a conflict resolution method based on their needs for the target privacy number. For example, the user may choose to dissolve the conflicting existing binding relationship and retain the newly added or updated binding relationship, thereby allowing the target privacy number to take effect in the newly added or updated binding relationship and be used subsequently. Furthermore, the user may also change the target privacy number included in the currently added or updated binding relationship and use the new target privacy number for the newly added or updated binding relationship.

[0085] In some optional implementations, when adding or updating a binding, the target privacy number used is assigned to the user by the platform providing the privacy number service. Related technologies offer privacy number allocation strategies that can avoid conflicts to a certain extent. However, in actual implementation, due to the high volume of service requests, multiple requests for adding or updating bindings may be concurrent, which can still cause conflicts between bindings. In this embodiment, for existing bindings with conflicts, the platform can set a proactive conflict resolution strategy. Specifically, after returning the identification number of the conflicting binding to the user, the target privacy number can be stored in a preset conflicting privacy number set. This conflicting privacy number set can store the privacy numbers in conflicting bindings identified during previous conflict checks. Subsequently, when responding to any user's request to add or update a binding, the corresponding privacy number for the new or updated binding can be determined based on this conflicting privacy number set. In other words, when proactively assigning a target privacy number to a user for a new or updated binding, a privacy number outside the conflicting privacy number set must be selected.

[0086] As can be seen from the above embodiments, the binding relationship conflict verification method of the privacy number of the present application, in order to avoid the database performance bottleneck problem, sets the storage and maintenance of the existing binding relationship in the cache, and realizes efficient and fast storage and maintenance of the existing binding relationship based on the high-speed data reading and writing capabilities of the cache. In addition, a corresponding data model is constructed in the cache for storage of binding relationships of different binding modes. The data model is constructed as a key-value pair including the existing privacy number and the identification number of the existing binding relationship; when performing conflict verification, the data model in the cache is retrieved according to the binding mode, and the conflict verification result is determined according to the retrieval result. The data model corresponding to different binding modes can support conflict verification of various common binding modes, wherein the identification number of the binding relationship can also be used to verify and determine when a conflict occurs, and accurately determine the existing binding relationship that has conflicted, further improving the service performance and data processing efficiency of binding relationship conflict verification.

[0087] It should be noted that the method of the embodiment of the present application can be performed by a single device, such as a computer or server. The method of this embodiment can also be applied in a distributed scenario and performed by multiple devices working together. In such a distributed scenario, one of the multiple devices may only perform one or more steps of the method of the embodiment of the present application, and the multiple devices will interact with each other to complete the method.

[0088] It should be noted that the above description is limited to some embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in an order different from that described in the above embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0089] Based on the same technical concept, the embodiment of the present application also provides a binding relationship conflict verification device for a privacy number. Figure 6 The private number binding relationship conflict verification device 600 includes:

[0090] Determining module 601 is configured to, in response to a user's request to add or update a binding relationship, determine a target privacy number included in the newly added or updated binding relationship, and determine a binding mode for the newly added or updated binding relationship;

[0091] The reading module 602 is configured to read, from the cache, at least one key-value pair corresponding to at least one existing binding relationship according to the binding mode; the key of the key-value pair includes the existing private number, and the value of the key-value pair includes the identification number of the existing binding relationship to which the existing private number belongs;

[0092] The verification module 603 is configured to use the target private number as a key to search the at least one key-value pair, and determine a conflict verification result according to the search result.

[0093] In some optional embodiments, when the binding mode is an exclusive mode, the key-value pair uses an existing privacy number as a key and an identification number of an existing binding relationship to which the existing privacy number belongs as a value; the verification module 603 is specifically configured to, in response to retrieving a value corresponding to the target privacy number, determine that there is an existing binding relationship that conflicts with the newly added or updated binding relationship; in response to not retrieving a value corresponding to the target privacy number, determine that there is no existing binding relationship that conflicts with the newly added or updated binding relationship.

[0094] In some optional embodiments, when the binding mode is a sharing mode, the key-value pair uses an existing privacy number as a key and at least one data pair corresponding to the existing privacy number as a value; the data pair includes: a user number bound to the existing privacy number, and an identification number of an existing binding relationship to which the existing privacy number belongs; the verification module 603 is specifically configured to, in response to retrieval of a data pair including a target user number bound to the target privacy number, determine that there is an existing binding relationship that conflicts with the newly added or updated binding relationship; in response to not retrieving a data pair including a target user number bound to the target privacy number, determine that there is no existing binding relationship that conflicts with the newly added or updated binding relationship.

[0095] In some optional embodiments, when the binding mode is a sharing mode with an extension number, any existing binding relationship corresponds to a first key-value pair and a second key-value pair; the first key-value pair uses the existing privacy number as a key and at least one first data pair corresponding to the existing privacy number as a value; the first data pair includes: the user number bound to the existing privacy number, and the identification number of the existing binding relationship to which the existing privacy number belongs; the second key-value pair uses the existing privacy number as a key and at least one second data pair corresponding to the existing privacy number as a value; the second data pair includes: the extension number bound to the existing privacy number, and the existing the identification number of the existing binding relationship to which the privacy number belongs; the verification module 603 is specifically configured to determine that there is an existing binding relationship that conflicts with the newly added or updated binding relationship in response to retrieving a first data pair including a target user number bound to the target privacy number, and / or retrieving a second data pair including a target extension number bound to the target privacy number; and determine that there is no existing binding relationship that conflicts with the newly added or updated binding relationship in response to not retrieving the first data pair including the target user number bound to the target privacy number and not retrieving the second data pair including the target extension number bound to the target privacy number.

[0096] In some optional embodiments, the verification module 603 is further configured to return an identification number of the conflicting existing binding relationship to the user after determining that there is an existing binding relationship that conflicts with the newly added or updated binding relationship.

[0097] In some optional embodiments, the verification module 603 is further configured to release an existing binding relationship that is in conflict, or change the target privacy number according to an operation instruction submitted by the user.

[0098] In some optional embodiments, the verification module 603 is further configured to store the target privacy number in a preset conflicting privacy number set; and in response to any user's request to add or update a binding relationship, determine the corresponding privacy number for the newly added or updated binding relationship based on the conflicting privacy number set.

[0099] For the convenience of description, the above devices are described as being divided into various modules according to their functions. Of course, when implementing this application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0100] The device of the above embodiment is used to implement the corresponding privacy number binding relationship conflict verification method in any of the aforementioned embodiments applied to the anchor end, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0101] Based on the same technical concept, an embodiment of the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and runnable on the processor. When the processor executes the program, it implements the binding relationship conflict verification method for the privacy number as described in any of the above embodiments.

[0102] Figure 7 10 is a schematic diagram showing a more specific hardware structure of an electronic device provided in this embodiment. The device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are communicatively connected to each other within the device via the bus 1050.

[0103] The processor 1010 can be implemented using a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0104] The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage devices, dynamic storage devices, etc. The memory 1020 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1020 and is called and executed by the processor 1010.

[0105] The input / output interface 1030 is used to connect input / output modules to implement information input and output. The input / output modules can be configured as components within the device (not shown in the figure) or can be externally connected to the device to provide corresponding functions. Input devices may include a keyboard, mouse, touch screen, microphone, various sensors, etc., and output devices may include a display, speaker, vibrator, indicator light, etc.

[0106] The communication interface 1040 is used to connect to a communication module (not shown) to enable communication between the device and other devices. The communication module can communicate via a wired method (such as USB, network cable, etc.) or a wireless method (such as mobile network, WiFi, Bluetooth, etc.).

[0107] The bus 1050 comprises a path for transmitting information between the various components of the device (eg, the processor 1010 , the memory 1020 , the input / output interface 1030 , and the communication interface 1040 ).

[0108] It should be noted that although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040, and the bus 1050, in a specific implementation, the device may also include other components necessary for normal operation. In addition, it will be understood by those skilled in the art that the above device may only include the components necessary to implement the embodiments of this specification, and does not necessarily include all the components shown in the figure.

[0109] The electronic device of the above embodiment is used to implement the corresponding binding relationship conflict verification method of the privacy number in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0110] Based on the same technical concept, an embodiment of the present application also provides a non-transitory computer-readable storage medium, which stores computer instructions, and the computer instructions are used to enable the computer to execute the binding relationship conflict verification method for the private number as described in any of the above embodiments.

[0111] The computer-readable media of this embodiment include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0112] The computer instructions stored in the storage medium of the above embodiment are used to enable the computer to execute the binding relationship conflict verification method of the private number as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0113] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present application should have the usual meaning understood by people with ordinary skills in the field to which this application belongs. The "first", "second" and similar words used in the embodiments of the present application do not indicate any order, quantity or importance, but are only used to distinguish different components. "Include" or "comprise" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The article "one" or "an" before an element does not exclude the presence of multiple such elements.

[0114] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present application (including the claims) is limited to these examples. Within the scope of the present application, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of simplicity.

[0115] The embodiments of the present application are intended to cover all such substitutions, modifications, and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the scope of protection of this application.

Claims

1. A method for checking conflict in binding relationship of private numbers, characterized in that: include: In response to a user's request to add or update a binding relationship, determining a target privacy number included in the newly added or updated binding relationship, and determining a binding mode for the newly added or updated binding relationship; According to the binding mode, at least one key-value pair corresponding to at least one existing binding relationship is read from the cache; the key of the key-value pair includes the existing privacy number, and the value of the key-value pair includes the identification number of the existing binding relationship to which the existing privacy number belongs; when the binding mode is a shared mode with an extension number, any existing binding relationship corresponds to a first key-value pair and a second key-value pair; the first key-value pair uses the existing privacy number as a key and at least one first data pair corresponding to the existing privacy number as a value; the first data pair includes: the user number bound to the existing privacy number, and the identification number of the existing binding relationship to which the existing privacy number belongs; the second key-value pair uses the existing privacy number as a key and at least one second data pair corresponding to the existing privacy number as a value; the second data pair includes: the extension number bound to the existing privacy number, and the identification number of the existing binding relationship to which the existing privacy number belongs; Using the target private number as a key, searching is performed in the at least one key-value pair, and a conflict check result is determined according to the search result.

2. The method according to claim 1, characterized in that When the binding mode is exclusive mode, the key-value pair uses the existing private number as the key and the identification number of the existing binding relationship to which the existing private number belongs as the value; Determining the conflict check result according to the search result includes: In response to retrieving a value corresponding to the target private number, determining that there is an existing binding relationship that conflicts with the newly added or updated binding relationship; In response to not retrieving a value corresponding to the target private number, it is determined that there is no existing binding relationship that conflicts with the newly added or updated binding relationship.

3. The method according to claim 1, characterized in that When the binding mode is a sharing mode, the key-value pair uses an existing private number as a key and at least one data pair corresponding to the existing private number as a value; the data pair includes: a user number bound to the existing private number, and an identification number of an existing binding relationship to which the existing private number belongs; Determining the conflict check result according to the search result includes: In response to retrieving a data pair including a target user number bound to the target privacy number, determining that there is an existing binding relationship that conflicts with the newly added or updated binding relationship; In response to not retrieving a data pair including the target user number bound to the target privacy number, it is determined that there is no existing binding relationship that conflicts with the newly added or updated binding relationship.

4. The method according to claim 1, wherein Determining the conflict check result according to the search result includes: In response to retrieving a first data pair including a target user number bound to the target privacy number and / or retrieving a second data pair including a target extension number bound to the target privacy number, determining that there is an existing binding relationship that conflicts with the newly added or updated binding relationship; In response to not retrieving a first data pair including a target user number bound to the target privacy number and not retrieving a second data pair including a target extension number bound to the target privacy number, it is determined that there is no existing binding relationship that conflicts with the newly added or updated binding relationship.

5. The method according to any one of claims 2 to 4, characterized in that After determining that there are existing binding relationships that conflict with the newly added or updated binding relationship, the following also applies: The identification number of the conflicting existing binding relationship is returned to the user.

6. The method according to claim 5, characterized in that After returning the identification number of the conflicting existing binding relationship to the user, the method further includes: According to the operation instruction submitted by the user, the existing binding relationship with conflict is released, or the target privacy number is changed.

7. The method according to claim 5, characterized in that After returning the identification number of the conflicting existing binding relationship to the user, the method further includes: Storing the target private number in a preset conflicting private number set; In response to a request from any user to add or update a binding relationship, a corresponding privacy number is determined for the newly added or updated binding relationship according to the set of conflicting privacy numbers.

8. A device for checking binding relationship conflicts of private numbers, characterized in that: include: a determination module configured to, in response to a user's request to add or update a binding relationship, determine a target privacy number included in the newly added or updated binding relationship, and determine a binding mode for the newly added or updated binding relationship; The reading module is configured to read at least one key-value pair corresponding to at least one existing binding relationship from the cache according to the binding mode; the key of the key-value pair includes an existing privacy number, and the value of the key-value pair includes an identification number of the existing binding relationship to which the existing privacy number belongs; when the binding mode is a shared mode with an extension number, any existing binding relationship corresponds to a first key-value pair and a second key-value pair; the first key-value pair uses the existing privacy number as a key and at least one first data pair corresponding to the existing privacy number as a value; the first data pair includes: a user number bound to the existing privacy number, and an identification number of the existing binding relationship to which the existing privacy number belongs; the second key-value pair uses the existing privacy number as a key and at least one second data pair corresponding to the existing privacy number as a value; the second data pair includes: an extension number bound to the existing privacy number, and an identification number of the existing binding relationship to which the existing privacy number belongs; The verification module is configured to use the target privacy number as a key to search in the at least one key-value pair, and determine a conflict verification result according to the search result.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the method according to any one of claims 1 to 7 is implemented.

10. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: The computer instructions are used to enable a computer to execute the method according to any one of claims 1 to 7.

Images