A destination access method and device, a server and a storage medium

Abstract

The application provides a destination access method and device, a server and a storage medium, and relates to the technical field of Internet. The method comprises the following steps: receiving a destination access request sent by a terminal, wherein the destination access request comprises the name of a destination, the first account identifier of a user account and the mobile directory number (MDN) of the user account; performing encryption processing on the name of the destination, the first account identifier of the user account and the MDN of the user account based on a second public key, generating first encryption information, and broadcasting the first encryption information to at least one node; receiving second encryption information sent by the second node, and performing decryption processing on the second encryption information based on a first private key to obtain first prompt information, wherein the first prompt information is used for prompting that the user account cannot access the destination.

Description

Technical Field

[0001] This invention relates to the field of Internet technology, and in particular to a destination access method, apparatus, server, and storage medium. Background Technology

[0002] Currently, users can travel from their origin to their destination based on different modes of transportation.

[0003] However, when users arrive at their destination, they may be unable to access it for various reasons, which could affect their lives and work, resulting in a poor travel experience. Summary of the Invention

[0004] This invention provides a destination access method, apparatus, server, and storage medium, which solves the technical problem that when a user arrives at a destination, they may be unable to access the destination due to certain reasons, which may affect the user's life and work and result in a poor travel experience.

[0005] In a first aspect, the present invention provides a destination access method, comprising: receiving a destination access request sent by a terminal, the destination access request including a destination name, a first account identifier of a user account, and a Mobile Subscriber Number (MDN) of the user account; encrypting the destination name, the first account identifier of the user account, and the MDN of the user account based on a second public key to generate first encrypted information, and broadcasting the first encrypted information to at least one node, the second public key being a public key included in a second node, the second node being one of the at least one nodes, and the first node and the at least one node belonging to the same blockchain; receiving second encrypted information sent by the second node, and decrypting the second encrypted information based on a first private key to obtain a first prompt message, the first prompt message being used to indicate that the user account cannot access the destination, the first private key being a private key included in the first node; and sending a destination access response to the terminal, the destination access response including the first prompt message.

[0006] Optionally, the above destination access method further includes: generating a first digest based on the first encrypted information; encrypting the first digest based on the first private key to generate a first private key signature; and broadcasting the first private key signature to the at least one node.

[0007] Optionally, the above destination access method further includes: receiving a second private key signature sent by the second node; decrypting the second private key signature based on the second public key to obtain a third digest; and generating a fourth digest based on the second encrypted information; the above-mentioned decrypting the second encrypted information based on the first private key to obtain a first prompt message specifically includes: if the fourth digest is the same as the third digest, decrypting the second encrypted information based on the first private key to obtain the first prompt message.

[0008] Secondly, the present invention provides a destination access method, comprising: receiving first encrypted information sent by a first node, and decrypting the first encrypted information based on a second private key to obtain a destination name, a first account identifier of a user account, and a Mobile Subscriber Number (MDN) of the user account, wherein the second private key is a private key included in the second node; if the MDN is stored in the second node, determining whether the second account identifier is the same as the first account identifier, wherein the second account identifier is an account identifier corresponding to the MDN stored in the second node; if the second account identifier is the same as the first account identifier, determining that the MDN is in M... The data of the target business during the time interval is used to verify the identity of the user account, where M is an integer greater than or equal to 1. The target business is verified, and if the verification is successful, a first prompt message is generated to indicate that the user account cannot access the destination. The first prompt message is encrypted based on a first public key to generate a second encrypted message, and the second encrypted message is broadcast to the first node and other nodes. The other nodes are the nodes other than the second node among the at least one node. The first node and the at least one node belong to the same blockchain, and the first public key is the public key included in the first node.

[0009] Optionally, the aforementioned business data includes multiple time periods and the location information of the MDN performing the target business at each of the multiple time periods. The generation of the first prompt information specifically includes: generating the first prompt information based on the name of the destination and the location information of the MDN performing the target business at the first time period, wherein the first time period is one of the multiple time periods.

[0010] Optionally, generating the first prompt information based on the name of the destination and the location information of the MDN performing the target service at the first moment specifically includes: determining the prohibited access location information corresponding to the destination based on the name of the destination; and generating the first prompt information if the prohibited access location information includes the location information of the MDN performing the target service at the first moment.

[0011] Optionally, the above destination access method further includes: receiving a first private key signature sent by the first node; decrypting the first private key signature based on the first public key to obtain a first digest; and generating a second digest based on the first encrypted information; the above decryption of the first encrypted information based on the second private key to obtain the destination name, the first account identifier of the user account, and the MDN of the user account specifically includes: if the second digest is the same as the first digest, decrypting the first encrypted information based on the second private key to obtain the destination name, the first account identifier, and the MDN.

[0012] Optionally, the above destination access method further includes: generating a third digest based on the second encrypted information; encrypting the third digest based on the second private key to generate a second private key signature; and broadcasting the second private key signature to the first node and the other nodes.

[0013] Thirdly, the present invention provides a destination access device, comprising: a receiving module, a processing module, and a sending module; the receiving module is configured to receive a destination access request sent by a terminal, the destination access request including a destination name, a first account identifier of a user account, and the MDN of the user account; the processing module is configured to encrypt the destination name, the first account identifier of the user account, and the MDN of the user account based on a second public key to generate first encrypted information, and broadcast the first encrypted information to at least one node, the second public key being a public key included in a second node, the second node being one of the at least one nodes, and the first node and the at least one node belonging to the same blockchain; the receiving module is further configured to receive second encrypted information sent by the second node, and decrypt the second encrypted information based on a first private key to obtain a first prompt message, the first prompt message being used to indicate that the user account cannot access the destination, the first private key being a private key included in the first node; the sending module is configured to send a destination access response to the terminal, the destination access response including the first prompt message.

[0014] Optionally, the processing module is further configured to generate a first digest based on the first encrypted information; the processing module is further configured to encrypt the first digest based on the first private key to generate a first private key signature; the processing module is further configured to broadcast the first private key signature to the at least one node.

[0015] Optionally, the receiving module is further configured to receive the second private key signature sent by the second node; the processing module is further configured to decrypt the second private key signature based on the second public key to obtain a third digest; and generate a fourth digest based on the second encrypted information; specifically, the processing module is configured to decrypt the second encrypted information based on the first private key when the fourth digest is the same as the third digest to obtain the first prompt information.

[0016] Fourthly, the present invention provides a destination access device, comprising: a receiving module, a determining module, and a processing module; the receiving module is configured to receive first encrypted information sent by a first node, and decrypt the first encrypted information based on a second private key to obtain the destination name, a first account identifier of a user account, and a Mobile Subscriber Number (MDN) of the user account, wherein the second private key is a private key included in the second node; the determining module is configured to, when the second node stores an MDN, determine whether a second account identifier is the same as the first account identifier, wherein the second account identifier is an account identifier stored in the second node corresponding to the MDN; the determining module is further configured to, when the second account identifier is the same as the first account identifier... In this case, the processing module determines the business data of the MDN when performing the target business within M time intervals. The target business is used to verify the identity of the user account, where M is an integer greater than or equal to 1. The processing module is used to verify the target business. If the verification is successful, it generates a first prompt message, which is used to indicate that the user account cannot access the destination. The processing module is also used to encrypt the first prompt message based on the first public key to generate a second encrypted message, and broadcast the second encrypted message to the first node and other nodes. The other nodes are the nodes other than the second node among the at least one node. The first node and the at least one node belong to the same blockchain, and the first public key is the public key included in the first node.

[0017] Optionally, the service data includes multiple times and the location information of the MDN performing the target service at each of the multiple times. The processing module is specifically used to generate a first prompt message based on the name of the destination and the location information of the MDN performing the target service at the first time, where the first time is one of the multiple times.

[0018] Optionally, the determining module is further configured to determine the prohibited access location information corresponding to the destination based on the name of the destination; the processing module is further configured to generate the first prompt information when the prohibited access location information includes the location information of the MDN performing the target service at the first moment.

[0019] Optionally, the receiving module is further configured to receive the first private key signature sent by the first node; the processing module is further configured to decrypt the first private key signature based on the first public key to obtain a first digest; and generate a second digest based on the first encrypted information; specifically, if the second digest is the same as the first digest, the processing module is configured to decrypt the first encrypted information based on the second private key to obtain the destination name, the first account identifier, and the MDN.

[0020] Optionally, the processing module is further configured to generate a third digest based on the second encrypted information; the processing module is further configured to encrypt the third digest based on the second private key to generate a second private key signature; the processing module is further configured to broadcast the second private key signature to the first node and the other nodes.

[0021] Fifthly, the present invention provides a server comprising: a processor and a memory configured to store processor-executable instructions; wherein the processor is configured to execute the instructions to implement any of the optional destination access methods of the first aspect above, or to implement any of the optional destination access methods of the second aspect above.

[0022] In a sixth aspect, the present invention provides a computer-readable storage medium storing instructions that, when executed by a server, enable the server to perform any of the optional destination access methods in the first aspect or any of the optional destination access methods in the second aspect.

[0023] The present invention provides a destination access method, apparatus, server, and storage medium. In an embodiment of the present invention, a first node can receive a destination access request sent by a terminal. The destination access request includes the name of the destination, a first account identifier of the user account, and the MDN of the user account. Then, based on a second public key, the first account identifier of the user account and the MDN of the user account are encrypted to obtain first encrypted information, and the first encrypted information is broadcast to at least one node. Since the second public key is a public key included in the second node, the second node can decrypt the first encrypted information based on a second private key to obtain the name of the destination, the first account identifier of the user account, and the MDN of the user account. If the second node includes the MDN and the account identifier corresponding to the MDN stored in the second node is the same as the first account identifier, the second node can determine the service data of the target service when the MDN is used in M ​​time intervals. Since the target service is used to verify the identity of the user account, the second node can verify the target service, and if the verification is successful, generate a first prompt message. After receiving the first prompt message, the first node can send the destination access response to the terminal. In this invention, since the second node stores multiple MDNs and the account identifier corresponding to each MDN, if the second account identifier is the same as the first account identifier, it indicates that the business data corresponding to the MDN is the business data of the user account. Therefore, the second node can determine the business data of the MDN when performing the target business within M time intervals. Since the target business is used to verify the identity of the user account, the second node generates a first prompt message when verifying the target business and the verification is successful. The first prompt message is used to indicate that the user account cannot access the destination, so that the first node can send the destination access response to the terminal. The destination access response includes the first prompt message, which can improve the accuracy of determining whether the user account can access the destination and improve the travel efficiency of the user account. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0025] Figure 1 A schematic diagram of the network architecture of a blockchain system provided in an embodiment of the present invention;

[0026] Figure 2 A flowchart illustrating a destination access method provided in an embodiment of the present invention;

[0027] Figure 3A flowchart illustrating another destination access method provided in an embodiment of the present invention;

[0028] Figure 4 A flowchart illustrating another destination access method provided in an embodiment of the present invention;

[0029] Figure 5 A flowchart illustrating another destination access method provided in an embodiment of the present invention;

[0030] Figure 6 A flowchart illustrating another destination access method provided in an embodiment of the present invention;

[0031] Figure 7 This is a schematic diagram of the structure of a destination access device provided in an embodiment of the present invention;

[0032] Figure 8 A schematic diagram of another destination access device provided in an embodiment of the present invention;

[0033] Figure 9 A schematic diagram of another destination access device provided in an embodiment of the present invention;

[0034] Figure 10 This is a schematic diagram of another destination access device provided in an embodiment of the present invention. Detailed Implementation

[0035] The destination access method, apparatus, server, and storage medium provided in the embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0036] The terms "first" and "second," etc., in the specification and drawings of this application are used to distinguish different objects, rather than to describe a specific order of objects. For example, "first account identifier" and "second account identifier" are used to distinguish different account identifiers, rather than to describe a specific order of account identifiers.

[0037] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0038] It should be noted that in the embodiments of the present invention, the words "exemplary" or "for example" are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of the present invention should not be construed as being more preferred or advantageous than other embodiments or design options. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0039] The term "and / or" as used in this application includes using either one of two methods or using both methods simultaneously.

[0040] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0041] As described in the background art, in related technologies, when a user arrives at their destination, they may be unable to access it for various reasons, which may affect their life and work, resulting in a poor travel experience. Therefore, this invention provides a destination access method, apparatus, server, and storage medium. Since the second node stores multiple MDNs and an account identifier corresponding to each MDN, if the second account identifier is the same as the first account identifier, it indicates that the business data corresponding to the MDN is the user account's business data. Therefore, the second node can determine the business data of the MDN when performing the target business within M time intervals. Since the target business is used to verify the user account's identity, the second node generates a first prompt message upon successful verification of the target business. This first prompt message indicates that the user account cannot access the destination, allowing the first node to send a destination access response to the terminal. This destination access response includes the first prompt message, improving the accuracy of determining whether a user account can access the destination and increasing the user account's travel efficiency.

[0042] The destination access method, apparatus, server, and storage medium provided in this invention can be applied to blockchain systems, such as... Figure 1 As shown, the blockchain system may include node 101, node 102, and node 103. Typically, in practical applications, the connections between these devices or service functions can be wireless. To easily and intuitively illustrate the connection relationships between the devices, Figure 1 The diagram uses solid lines to illustrate that each node in this blockchain system can broadcast encrypted information to other nodes.

[0043] Optionally, in this embodiment of the invention, nodes 101, 102, and 103 can be independent devices, servers integrated with blockchain node functionality, or cloud servers providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery network (CDN), and big data and artificial intelligence platforms. In this embodiment of the invention, node 101 can be a first node or a second node; this embodiment of the invention does not limit the number of nodes in the blockchain system.

[0044] The destination access method, apparatus, server, and storage medium provided in this invention are applied to destination access scenarios. When a terminal sends a destination access request to a first node, the first node can receive the request and then encrypt the destination name, the first account identifier of the user account, and the MDN of the user account based on a second public key to obtain first encrypted information. The second node can then decrypt the first encrypted information. If the MDN is stored in the second node, the second node determines whether the second account identifier is the same as the first account identifier. If the second account identifier is the same as the first account identifier, the second node determines the service data of the MDN when performing the target service within M time intervals. If the verification result of the MDN performing the target service at the first moment is successful, the first prompt information is generated based on the destination name and the location information of the MDN performing the target service at the first moment. The first prompt information is then encrypted based on the first public key to generate second encrypted information, and the second encrypted information is broadcast to the first node and other nodes so that the first node can receive the first prompt information and send a destination access response to the terminal.

[0045] In combination with the above Figure 1 The following describes the destination access method provided by the embodiments of the present invention from the perspective of the interaction between various devices in the blockchain system, in order to illustrate the process of the first node receiving the destination access request sent by the terminal and the second node generating the first prompt information.

[0046] like Figure 2 As shown, the destination access method provided in this embodiment of the invention may include S101-S109.

[0047] S101, The first node receives the destination access request sent by the terminal.

[0048] The destination access request includes the destination name, the user account's first account identifier, and the user account's MDN.

[0049] Understandably, this destination access request is used to determine whether the user account has access to the destination.

[0050] It should be understood that the primary account identifier of a user account is the user account's identity identifier, such as the user account's ID card number or passport number.

[0051] It should be noted that the MDN of this user account is the MDN registered by the first node based on the ID card number of this user account, and a user account can register at least one MDN.

[0052] In this embodiment of the invention, the name of the destination is used to represent a region, for example, the name of the destination is Beijing.

[0053] Alternatively, the name of the destination can also be an identifier for the destination, such as 1 used to identify Beijing.

[0054] It should be noted that this first node is a node in a blockchain.

[0055] Optionally, the first node can be an operator's node or an operator's blockchain node, which can receive destination access requests sent by the terminal.

[0056] In one alternative implementation, the first node can also receive destination access requests from other nodes in the blockchain, such as a third node. This third node can be a node in the railway system (or a node in the civil aviation system). When a user account purchases a train ticket in the railway system, the terminal corresponding to the user account can send the first account identifier of the user account and the name of the destination to the third node. Then, the third node can send a destination access request to the first node, which includes the first account identifier of the user account and the name of the destination, to request a determination of whether the user account can access the destination.

[0057] S102, the first node encrypts the destination name, the first account identifier of the user account, and the MDN of the user account based on the second public key to generate first encrypted information, and broadcasts the first encrypted information to at least one node.

[0058] The second public key is a public key included in the second node, and the second node is one of the at least one node. The first node and the at least one node belong to the same blockchain.

[0059] Understandably, the first node can send the first encrypted information to the blockchain as a broadcast message so that at least one node in the blockchain can obtain the first encrypted information.

[0060] Optionally, the first node may store a first algorithm, which is an algorithm agreed upon in advance by the first node and the second node. When the first node needs to send information to the second node, the first node can use the second public key and the first algorithm to encrypt the information to be encrypted, and obtain the encrypted information.

[0061] Optionally, the first node and the at least one node may also belong to the same consortium blockchain.

[0062] S103, the second node receives the first encrypted information sent by the first node, and decrypts the first encrypted information based on the second private key to obtain the destination name, the first account identifier of the user account, and the MDN of the user account.

[0063] The second private key is the private key included in the second node.

[0064] Understandably, the second private key is the private key corresponding to the second public key. The second private key is used to decrypt the information encrypted by the second public key. After the first node encrypts the destination name, the first account identifier of the user account, and the MDN of the user account based on the second public key to generate the first encrypted information, the second node can decrypt the first encrypted information based on the second private key to obtain the destination name, the first account identifier of the user account, and the MDN of the user account.

[0065] Optionally, the second node may also store the first algorithm, and the second node can decrypt the first encrypted information sent by the first node based on the second algorithm and the second public key.

[0066] S104. If the second node stores the MDN, the second node determines whether the second account identifier is the same as the first account identifier.

[0067] The second account identifier is the account identifier corresponding to the MDN stored in the second node.

[0068] Understandably, the second node can store multiple MDNs and the account identifier corresponding to each MDN.

[0069] It should be noted that the second node can obtain the account identifier corresponding to each MDN from the terminal. The account identifier corresponding to each MDN obtained by the second node may be the account identifier of other user accounts.

[0070] It should be understood that if the MDN is stored in the second node, it means that the second node stores the correspondence between the account identifier of a certain user account and the MDN. At this time, the second node can determine whether the second account identifier is the same as the first account identifier, that is, determine whether the second account identifier is the account identifier of the user account corresponding to the MDN.

[0071] S105. If the second account identifier is the same as the first account identifier, the second node determines the business data of the MDN when performing the target business in M ​​time intervals.

[0072] The target service is used to verify the identity of the user account, where M is an integer greater than or equal to 1.

[0073] It should be understood that if the second account identifier is the same as the first account identifier, it means that the second account identifier is the account identifier of the user account corresponding to the MDN, and the business data of the MDN when performing the target business in the M time intervals is the business data of the user account. At this time, the second node can determine that the identity information of the user account is stored in the second node, and then determine the business data of the user account when performing the target business in the M time intervals.

[0074] Optionally, the target service can be a QR code registration service. When the user account performs the QR code registration service, the second node can obtain the location information of the QR code scanned by the user account.

[0075] Optionally, the QR code registration service can perform facial verification on the user account, and then verify the user account's identity based on the facial verification information.

[0076] S106. The second node verifies the target service. If the verification is successful, the first prompt message is generated.

[0077] The first notification message is used to inform the user account that it cannot access the destination.

[0078] It should be understood that since the target service is used to verify the identity of the user account, if the second node verifies the target service and the verification is successful, it indicates that the user account is performing the target service. At this time, the second node can generate the first prompt message.

[0079] In one alternative implementation, the business data may also include the verification result of the user account performing the target business. In this case, the second node may generate the first prompt message if the verification result is successful.

[0080] Understandably, if the second node verifies the target service and the verification fails, it means that the user account is not performing the target service. In this case, the second node can delete the service data of the target service and determine that the service data is invalid.

[0081] In one alternative implementation, if the second account identifier is different from the first account identifier, it indicates that the second account identifier is the account identifier of another user account. In this case, the second node can also generate the first prompt message.

[0082] S107. The second node encrypts the first prompt information based on the first public key to generate second encrypted information, and broadcasts the second encrypted information to the first node and other nodes.

[0083] Among them, the other nodes are the nodes other than the second node among the at least one nodes, the first node belongs to the same blockchain as the at least one node, and the first public key is the public key included in the first node.

[0084] Understandably, the second node sends the second encrypted information to the blockchain as a broadcast message so that at least one node in the blockchain can obtain the second encrypted information.

[0085] S108. The first node receives the second encrypted information sent by the second node, and decrypts the second encrypted information based on the first private key to obtain the first prompt information.

[0086] The first prompt message is used to inform the user account that it cannot access the destination, and the first private key is the private key included in the first node.

[0087] It is understandable that the first private key is the private key corresponding to the first public key. Since the second node encrypts the first prompt information based on the first public key to obtain the second encrypted information, and the first public key is the public key included in the first node, the first node can decrypt the second encrypted information based on the first private key to obtain the first prompt information.

[0088] S109. The first node sends a destination access response to the terminal.

[0089] The destination access response includes this first prompt message.

[0090] This destination access response is used to notify the user account that the destination cannot be accessed.

[0091] Optionally, the first prompt message can be displayed on the terminal in the form of a pop-up window or a floating window.

[0092] In one alternative implementation, when the first node receives a destination access request sent by the third node, and the user account is purchasing a train ticket in the railway system, the third node can determine that the user account's train ticket purchase has failed after the first node sends the destination access response to the third node.

[0093] In this embodiment of the invention, a first node can receive a destination access request sent by a terminal. The destination access request includes the name of the destination, the first account identifier of the user account, and the MDN of the user account. Then, based on a second public key, the first account identifier of the user account and the MDN of the user account are encrypted to obtain the first encrypted information, and the first encrypted information is broadcast to at least one node. Since the second public key is a public key included in the second node, the second node can decrypt the first encrypted information based on the second private key to obtain the name of the destination, the first account identifier of the user account, and the MDN of the user account. If the second node includes the MDN and the account identifier corresponding to the MDN stored in the second node is the same as the first account identifier, the second node can determine the service data of the target service when the MDN is used in M ​​time intervals. Since the target service is used to verify the identity of the user account, the second node can verify the target service, and if the verification is successful, generate a first prompt message. After receiving the first prompt message, the first node can send the destination access response to the terminal. In this invention, since the second node stores multiple MDNs and the account identifier corresponding to each MDN, if the second account identifier is the same as the first account identifier, it indicates that the business data corresponding to the MDN is the business data of the user account. Therefore, the second node can determine the business data of the MDN when performing the target business within M time intervals. Since the target business is used to verify the identity of the user account, the second node generates a first prompt message when verifying the target business and the verification is successful. The first prompt message is used to indicate that the user account cannot access the destination, so that the first node can send the destination access response to the terminal. The destination access response includes the first prompt message, which can improve the accuracy of determining whether the user account can access the destination and improve the travel efficiency of the user account.

[0094] Combination Figure 2 ,like Figure 3 As shown, the above-mentioned business data includes multiple time periods and the location information of the MDN performing the target business at each of these multiple time periods. The second node generates the first prompt information, which may specifically include S1061.

[0095] S1061. The electronic device generates a first prompt message based on the destination name and the location information of the target service obtained by the MDN at the first moment.

[0096] The first moment is one of the multiple moments.

[0097] It should be understood that since the business data includes multiple time points, the second node can verify the target business at each time point, and generate the first prompt message if the verification result of the target business at the first time point is successful.

[0098] Understandably, since successful verification indicates that the user account was conducting the target service at the first moment, the second node can determine the location information of the MDN when conducting the target service as the location information of the user account, and generate the first prompt information based on the destination name and the location information of the MDN when conducting the target service at the first moment.

[0099] Combination Figure 3 ,like Figure 4 As shown, the second node generates the first prompt information based on the destination name and the location information of the target service in the first moment of the MDN, which may specifically include S10611-S10612.

[0100] S10611. The second node determines the prohibited access location information corresponding to the destination based on the name of the destination.

[0101] It should be understood that the second node stores the prohibited location information for each of the multiple regions. The prohibited location information for a region is used to represent the user account that has reached the prohibited location information within M time intervals, and is prohibited from accessing the region. The second node can determine the prohibited location information for the destination based on the name of the destination.

[0102] It is understandable that the restricted access information for a given region may include the name of at least one region.

[0103] S10612. If the location information that is prohibited from access includes the location information of the target service of MDN at the first moment, the second node generates the first prompt information.

[0104] It is understandable that if the location information of the MDN performing the target business at the first moment is included in the prohibited access location information corresponding to the destination, it means that the destination prohibits the user account from accessing the destination. At this time, the second node can generate a first prompt message, which is used to prompt the user account that it cannot access the destination.

[0105] For example, Table 1 below shows the multiple regions stored in the second node and the corresponding restricted access location information for these multiple regions.

[0106] Table 1

[0107] area Location information access denied Region 1 Position 1, Position 2, Position 3 Region 2 Position 1, Position 2, Position 3 Region 3 Position 1, Position 2, Position 4

[0108] Referring to Table 1, assuming that the location information of the target business of the MDN at the first moment is location 3, and the destination of the user account is region 2, the second node can determine that the prohibited access location information corresponding to region 2 includes location 3, and then generate a first prompt message, which is used to prompt the user account that it cannot access region 2.

[0109] In one optional implementation, the prohibited access location information includes the name of a region, and the location information of the MDN for the target service at the first moment is a latitude and longitude coordinate or the name of a building. In this case, when the region corresponding to the prohibited access location information includes the latitude and longitude coordinate, or the region corresponding to the prohibited access location information includes the building, the second node can also determine that the prohibited access location information includes the location information of the MDN for the target service at the first moment.

[0110] In another alternative implementation, if the location information of the MDN performing the target service at the first moment is not included in the prohibited access location information, the second node can generate a second prompt message to indicate that the user account can access the destination.

[0111] Combination Figure 2 ,like Figure 5 As shown, the destination access method provided in this embodiment of the invention further includes S110-S114.

[0112] S110. The first node generates a first digest based on the first encrypted information.

[0113] It is understandable that the first node can generate a first digest based on the digest algorithm and the first encrypted information.

[0114] It should be understood that the digest algorithm is a digest algorithm agreed upon in advance with the second node.

[0115] S111. The first node encrypts the first digest based on the first private key to generate a first private key signature.

[0116] Understandably, since the first encrypted information is generated by the first node through encryption based on the second public key, the second node can decrypt the first encrypted information based on the second public key, but cannot determine that the first encrypted information is the first encrypted information sent by the first node. In this case, the first node can encrypt the first digest based on the first private key to generate the first private key signature.

[0117] It should be understood that the first private key signature can also be understood as the signature of the first node. The second node can decrypt the first private key signature based on the first public key to determine that the first private key signature is the signature of the first node.

[0118] S112. The first node broadcasts the first private key signature to at least one node.

[0119] S113, The second node receives the first private key signature sent by the first node.

[0120] S114. The second node decrypts the signature of the first private key based on the first public key to obtain the first digest; and generates the second digest based on the first encrypted information.

[0121] Understandably, the second node decrypts the signature of the first private key based on the first public key to obtain the first digest, indicating that the first digest is the digest sent by the first node, and the second node has successfully authenticated the first node.

[0122] Based on the description of the above embodiments, the first node broadcasts the first encrypted information to the at least one node. It should be understood that the second node can also obtain the first encrypted information and generate a second digest of the first encrypted information based on the pre-agreed digest algorithm.

[0123] Continue as Figure 5 As shown, the second node decrypts the first encrypted information based on the second private key to obtain the destination name, the first account identifier of the user account, and the MDN of the user account, specifically including S1031.

[0124] S1031, if the second digest is the same as the first digest, the second node decrypts the first encrypted information based on the second private key to obtain the destination name, the first account identifier of the user account, and the MDN of the user account.

[0125] It should be understood that if the second digest is the same as the first digest, it indicates that the first encrypted information is encrypted information sent by the first node. In this case, the second node can decrypt the first encrypted information based on the second private key to obtain the destination name, the first account identifier of the user account, and the MDN of the user account.

[0126] In this embodiment of the invention, the first node encrypts the account identifier of the user account based on the second public key to obtain first encrypted information, and encrypts the first digest based on the first private key. It can be determined that the second node can encrypt the first digest based on the first public key to determine that the first digest is the digest of the first node. The second node generates a second digest based on the first encrypted information, which can be determined that the first encrypted information is the encrypted information sent by the second node, thus ensuring the security of the encrypted information transmission.

[0127] Combination Figure 2 ,like Figure 6 As shown, the destination access method provided in this embodiment of the invention further includes S115-S119.

[0128] S115. The second node generates a third digest based on the second encrypted information.

[0129] Understandably, the second node can generate a third digest based on a pre-agreed digest algorithm and the first encrypted information.

[0130] S116. The second node encrypts the third digest based on the second private key to generate a second private key signature.

[0131] It should be understood that the second private key signature can also be understood as the signature of the second node. The first node can decrypt the second private key signature based on the second public key to determine that the second private key signature is the signature of the second node.

[0132] S117, The second node broadcasts the second private key signature to the first node and other nodes.

[0133] It should be understood that the other node is any node other than the second node among the at least one nodes.

[0134] S118, The first node receives the second private key signature sent by the second node.

[0135] S119. The first node decrypts the signature of the second private key based on the second public key to obtain the third digest; and generates the fourth digest based on the second encrypted information.

[0136] Understandably, the first node decrypts the second private key signature based on the second public key to obtain the third digest, indicating that the third digest is the digest sent by the second node, and the first node has successfully authenticated the second node.

[0137] Based on the description of the above embodiments, the second node broadcasts the second encrypted information to the other nodes. It should be understood that the first node can also obtain the second encrypted information and generate a fourth digest of the second encrypted information based on the pre-agreed digest algorithm.

[0138] Continue as Figure 6 As shown, the first node decrypts the second encrypted information based on the first private key to obtain the first prompt information, specifically including S1081.

[0139] S1081. If the fourth digest is the same as the third digest, the first node decrypts the second encrypted information based on the first private key to obtain the first prompt information.

[0140] It should be understood that if the fourth digest is the same as the third digest, it indicates that the second encrypted information is encrypted information sent by the second node. In this case, the first node can decrypt the second encrypted information based on the first private key to obtain the first prompt information.

[0141] In this embodiment of the invention, servers and similar devices can be divided into functional modules according to the above method examples. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this embodiment is illustrative and represents only one logical functional division; other division methods may be used in actual implementation.

[0142] When dividing each function into modules according to its corresponding function. Figure 7 A possible structural schematic diagram of the destination access device involved in the above embodiments is shown, such as... Figure 7 As shown, the destination access device 20 may include a receiving module 201, a processing module 202, and a sending module 203.

[0143] The receiving module 201 is used to receive a destination access request sent by the terminal, which includes the name of the destination, the first account identifier of the user account, and the mobile subscriber number (MDN) of the user account.

[0144] The processing module 202 is used to encrypt the destination name, the first account identifier of the user account and the MDN of the user account based on the second public key, generate first encrypted information, and broadcast the first encrypted information to at least one node. The second public key is a public key included in the second node, and the second node is one of the at least one node. The first node and the at least one node belong to the same blockchain.

[0145] The receiving module 201 is also used to receive the second encrypted information sent by the second node, and decrypt the second encrypted information based on the first private key to obtain the first prompt information. The first prompt information is used to prompt the user account that it cannot access the destination. The first private key is the private key included in the first node.

[0146] The sending module 203 is used to send a destination access response to the terminal, the destination access response including the first prompt information.

[0147] Optionally, the processing module 202 is also configured to generate a first digest based on the first encrypted information.

[0148] The processing module 202 is also used to encrypt the first digest based on the first private key to generate a first private key signature.

[0149] The processing module 202 is also used to broadcast the first private key signature to the at least one node.

[0150] Optionally, the receiving module 201 is also configured to receive the second private key signature sent by the second node.

[0151] The processing module 202 is also used to decrypt the signature of the second private key based on the second public key to obtain a third digest; and to generate a fourth digest based on the second encrypted information.

[0152] The processing module 202 is specifically used to decrypt the second encrypted information based on the first private key when the fourth digest is the same as the third digest, so as to obtain the first prompt information.

[0153] When using integrated units, Figure 8 A possible structural schematic diagram of the destination access device involved in the above embodiments is shown. For example... Figure 8 As shown, the destination access device 30 may include a processing module 301 and a communication module 302. The processing module 301 can be used to control and manage the operation of the destination access device 30. The communication module 302 can be used to support communication between the destination access device 30 and other entities. Optionally, as... Figure 8 As shown, the destination access device 30 may also include a storage module 303 for storing the program code and data of the destination access device 30.

[0154] The processing module 301 can be a processor or a controller. The communication module 302 can be a transceiver, transceiver circuit, or communication interface, etc. The storage module 303 can be a memory.

[0155] In this configuration, when the processing module 301 is a processor, the communication module 302 is a transceiver, and the storage module 303 is a memory, the processor, transceiver, and memory can be connected via a bus. The bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc.

[0156] When dividing each function into modules according to its corresponding function. Figure 9 A possible structural schematic diagram of the destination access device involved in the above embodiments is shown, such as... Figure 9 As shown, the destination access device 40 may include: a receiving module 401, a determining module 402, and a processing module 403.

[0157] The receiving module 401 is used to receive the first encrypted information sent by the first node, and decrypt the first encrypted information based on the second private key to obtain the destination name, the first account identifier of the user account and the mobile subscriber number MDN of the user account, wherein the second private key is the private key included in the second node.

[0158] The determination module 402 is used to determine whether the second account identifier is the same as the first account identifier when the MDN is stored in the second node. The second account identifier is the account identifier corresponding to the MDN stored in the second node.

[0159] The determination module 402 is further configured to determine the business data of the MDN when performing the target business within M time intervals, when the second account identifier is the same as the first account identifier, where the target business is used to verify the identity of the user account, and M is an integer greater than or equal to 1.

[0160] The processing module 403 is used to verify the target service. If the verification is successful, it generates a first prompt message to indicate that the user account cannot access the destination.

[0161] The processing module 403 is further configured to encrypt the first prompt information based on the first public key, generate second encrypted information, and broadcast the second encrypted information to the first node and other nodes, wherein the other nodes are nodes other than the second node among the at least one node, the first node and the at least one node belong to the same blockchain, and the first public key is the public key included in the first node.

[0162] Optionally, the aforementioned business data includes multiple time points and the location information of the MDN performing the target business at each of those multiple time points.

[0163] The processing module 403 is specifically used to generate a first prompt message based on the name of the destination and the location information of the MDN performing the target service at the first moment, wherein the first moment is one of the multiple moments.

[0164] Optionally, the determining module 402 is further configured to determine the prohibited access location information corresponding to the destination based on the name of the destination.

[0165] The processing module 403 is further configured to generate the first prompt information when the location information of the MDN performing the target service at the first moment is included in the prohibited access location information.

[0166] Optionally, the receiving module 401 is also configured to receive the first private key signature sent by the first node.

[0167] The processing module 403 is further configured to decrypt the signature of the first private key based on the first public key to obtain a first digest; and to generate a second digest based on the first encrypted information.

[0168] The processing module 403 is specifically used to decrypt the first encrypted information based on the second private key when the second digest is the same as the first digest, so as to obtain the destination name, the first account identifier and the MDN.

[0169] Optionally, the processing module 403 is also configured to generate a third digest based on the second encrypted information.

[0170] The processing module 403 is also used to encrypt the third digest based on the second private key to generate a second private key signature.

[0171] The processing module 403 is also used to broadcast the second private key signature to the first node and the other nodes.

[0172] When using integrated units, Figure 10 A possible structural schematic diagram of the destination access device involved in the above embodiments is shown. For example... Figure 10 As shown, the destination access device 50 may include a processing module 501 and a communication module 502. The processing module 501 can be used to control and manage the operation of the destination access device 50. The communication module 502 can be used to support communication between the destination access device 50 and other entities. Optionally, as... Figure 10 As shown, the destination access device 50 may also include a storage module 503 for storing the program code and data of the destination access device 50.

[0173] The processing module 501 can be a processor or a controller. The communication module 502 can be a transceiver, transceiver circuit, or communication interface, etc. The storage module 503 can be a memory.

[0174] In this configuration, when the processing module 501 is a processor, the communication module 502 is a transceiver, and the storage module 503 is a memory, the processor, transceiver, and memory can be connected via a bus. The bus can be a PCI bus or an EISA bus, etc. The bus can be categorized as an address bus, data bus, control bus, etc.

[0175] It should be understood that, in various embodiments of the present invention, the order of the above-mentioned process numbers does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0176] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0177] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0178] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0179] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0180] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A destination access method, characterized by, The method applied to a first node comprises: receiving a destination access request sent by a terminal, the destination access request comprising a name of a destination, a first account identifier of a user account, and a mobile directory number (MDN) of the user account; encrypting the name of the destination, the first account identifier of the user account, and the MDN of the user account based on a second public key to generate first encrypted information, and broadcasting the first encrypted information to at least one node, the second public key being a public key included in a second node, the second node being one of the at least one node, and the first node and the at least one node belonging to a same blockchain; receiving second encrypted information sent by the second node, and decrypting the second encrypted information based on a first private key to obtain first prompt information, the first prompt information being used to prompt that the user account cannot access the destination, and the first private key being a private key included in the first node; sending a destination access response to the terminal, the destination access response comprising the first prompt information.

2. The destination access method of claim 1, wherein, The method further comprises: generating a first digest based on the first encrypted information; encrypting the first digest based on the first private key to generate a first private key signature; broadcasting the first private key signature to the at least one node.

3. The destination access method according to claim 1 or 2, characterized by, The method further comprises: receiving a second private key signature sent by the second node; decrypting the second private key signature based on the second public key to obtain a third digest, and generating a fourth digest based on the second encrypted information; decrypting the second encrypted information based on the first private key to obtain the first prompt information comprises: decrypting the second encrypted information based on the first private key to obtain the first prompt information in a case where the fourth digest is the same as the third digest.

4. A destination access method, characterized by, The method applied to a second node comprises: receiving first encrypted information sent by a first node, and decrypting the first encrypted information based on a second private key to obtain a name of a destination, a first account identifier of a user account, and a mobile directory number (MDN) of the user account, the second private key being a private key included in the second node; in a case where the MDN is stored in the second node, determining whether a second account identifier is the same as the first account identifier, the second account identifier being an account identifier corresponding to the MDN and stored in the second node; in a case where the second account identifier is the same as the first account identifier, determining service data of the MDN when performing a target service in M time intervals, the target service being used to verify an identity of the user account, and M being an integer greater than or equal to 1; verifying the target service, and in a case where the verification is successful, generating first prompt information, the first prompt information being used to prompt that the user account cannot access the destination; The first prompt information is generated based on the first public key and the first prompt information is encrypted based on the first public key to generate second encrypted information, and the second encrypted information is broadcast to the first node and other nodes, the other nodes being at least one node other than the second node, the first node and the at least one node belonging to the same blockchain, and the first public key being a public key included in the first node.

5. The destination access method of claim 4, wherein, The service data includes a plurality of time points and location information of the MDN performing the target service at each of the plurality of time points, and the first prompt information is generated based on the name of the destination and the location information of the MDN performing the target service at the first time point. The first prompt information is generated based on the name of the destination and the location information of the MDN performing the target service at the first time point.

6. The destination access method of claim 5, wherein, The first prompt information is generated based on the name of the destination and the location information of the MDN performing the target service at the first time point. The name of the destination is determined based on the name of the destination, and the prohibited access location information corresponding to the destination is determined. The first prompt information is generated when the location information of the MDN performing the target service at the first time point is included in the prohibited access location information.

7. The destination access method of claim 4, wherein, The method further comprises: receiving a first private key signature sent by the first node; decrypting the first private key signature based on the first public key to obtain a first digest, and generating a second digest based on the first encrypted information; decrypting the first encrypted information based on the second private key to obtain the name of the destination, the first account identifier of the user account, and the mobile subscriber number (MDN) of the user account, comprising: decrypting the first encrypted information based on the second private key to obtain the name of the destination, the first account identifier, and the MDN when the second digest is the same as the first digest.

8. The destination access method according to any of claims 4-7, characterized by, The method further comprises: generating a third digest based on the second encrypted information; encrypting the third digest based on the second private key to generate a second private key signature; broadcasting the second private key signature to the first node and the other nodes.

9. A destination access device, characterized by comprises: a receiving module, a processing module, and a sending module; The receiving module is configured to receive a destination access request sent by a terminal, the destination access request comprising a name of a destination, a first account identifier of a user account, and a mobile subscriber number (MDN) of the user account; The processing module is configured to encrypt the name of the destination, the first account identifier of the user account, and the MDN of the user account based on a second public key to generate first encrypted information, and broadcast the first encrypted information to at least one node, the second public key being a public key included in a second node, the second node being one of the at least one node, and the first node and the at least one node belonging to the same blockchain. The receiving module is further configured to receive second encrypted information sent by the second node, and decrypt the second encrypted information based on a first private key to obtain first prompt information, the first prompt information being used to prompt that the user account cannot access the destination, and the first private key being a private key included in the first node. The sending module is configured to send a destination access response to the terminal, the destination access response including the first prompt information.

10. The destination access apparatus according to claim 9, characterized in that, The processing module is further configured to generate a first digest based on the first encrypted information. The processing module is further configured to encrypt the first digest based on the first private key to generate a first private key signature. The processing module is further configured to broadcast the first private key signature to the at least one node.

11. The destination access apparatus according to claim 9 or 10, characterized in that, The receiving module is further configured to receive a second private key signature sent by the second node. The processing module is further configured to decrypt the second private key signature based on the second public key to obtain a third digest, and generate a fourth digest based on the second encrypted information. The processing module is specifically configured to, in a case where the fourth digest is the same as the third digest, decrypt the second encrypted information based on the first private key to obtain the first prompt information.

12. A destination access device, comprising: comprising: a receiving module, a determining module, and a processing module; The receiving module is configured to receive first encrypted information sent by a first node, and decrypt the first encrypted information based on a second private key to obtain a name of a destination, a first account identifier of a user account, and a mobile directory number (MDN) of the user account, the second private key being a private key included in a second node. The determining module is configured to, in a case where the MDN is stored in the second node, determine whether a second account identifier is the same as the first account identifier, the second account identifier being an account identifier corresponding to the MDN and stored in the second node. The determining module is further configured to, in a case where the second account identifier is the same as the first account identifier, determine service data of the MDN when performing a target service in M time intervals, the target service being used to verify an identity of the user account, and M being an integer greater than or equal to 1. The processing module is configured to verify the target service, and in a case where the verification is successful, generate first prompt information, the first prompt information being used to prompt that the user account cannot access the destination. The processing module is further configured to encrypt the first prompt information based on a first public key to generate second encrypted information, and broadcast the second encrypted information to the first node and other nodes, the other nodes being at least one node except the second node, the first node and the at least one node belonging to a same blockchain, and the first public key being a public key included in the first node.

13. The destination access device of claim 12, wherein, The service data comprises a plurality of time points and position information of the MDN performing the target service at each of the plurality of time points, The processing module is specifically configured to generate first prompt information based on the name of the destination and the position information of the MDN performing the target service at the first time point, the first time point being one of the plurality of time points.

14. The destination access apparatus of claim 13, wherein The determination module is further configured to determine prohibited access position information corresponding to the destination according to the name of the destination; The processing module is specifically further configured to generate the first prompt information in a case where the prohibited access position information comprises the position information of the MDN performing the target service at the first time point.

15. The destination access apparatus of claim 12, wherein The receiving module is further configured to receive a first private key signature sent by the first node; The processing module is further configured to decrypt the first private key signature based on the first public key to obtain a first digest, and generate a second digest based on the first encrypted information; The processing module is specifically configured to decrypt the first encrypted information based on the second private key to obtain the name of the destination, the first account identifier and the MDN in a case where the second digest is the same as the first digest.

16. The destination access apparatus of any one of claims 12-15, wherein The processing module is further configured to generate a third digest based on the second encrypted information; The processing module is further configured to encrypt the third digest based on the second private key to generate a second private key signature; The processing module is further configured to broadcast the second private key signature to the first node and the other nodes.

17. A server, characterized by The server comprises: a processor; a memory configured to store instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the destination access method of any one of claims 1-3, or implement the destination access method of any one of claims 4-8.

18. A computer-readable storage medium having stored thereon instructions, the instructions comprising, When the instructions in the computer-readable storage medium are executed by the server, the server is enabled to perform the destination access method of any one of claims 1-3, or perform the destination access method of any one of claims 4-8.

Images