TWI804849B - Method and system for resolving a target - Google Patents

Abstract

Disclosed are a method and a system for resolving a target, which employ two-stage target resolution. A local resolving peer resolves the target at a first-stage target resolution. If the first-stage target resolution fails, the first resolving peer sends target-related information to at least one remote resolving peer for second-stage target resolution in return of a resolvable result indicating that the target is resolvable to corresponding type of identifier. To avoid congested traffic arising from broadcasting target-related information without discrimination to the at least one remote resolving peer, a scheme caching approach and a hint service approach are adopted. Transmission of target-related information can be conducted either concurrently or sequentially in response to traffic condition. Accordingly, the method and the system of the present invention reliably resolve a target with known or unknown format at two stages without compromising the efficiency for target resolution.

Description

Target analysis method and system

The present invention relates to a method and system for parsing a target, in particular to a method for parsing a target from original target data into at least one identifier corresponding to a target resolution type, and the target resolution type is associated with an action transaction.

The global village has undoubtedly facilitated an increasing number of international tourism activities, both for business and leisure. Because these activities generate many payments for the purchase of goods and services abroad, credit cards have been one of the popular options for such cross-border payments for many years.

Contactless payments using personal mobile devices may be a new paradigm, but are commonplace in many countries such as Taiwan and numerous Asian and African countries. Consumers in other regions still prefer to pay by credit card, cash, transfer or check. Due to hygienic issues, such as the recent spread of the epidemic, the use of the PIN pad has become inconvenient. Contactless transactions using Quick Response code and Near-field Communication are becoming more important and more popular than ever.

However, raw target information in matrix codes or NFC tags generated by customer devices or commercial devices through different payment services (such as Softbank's Pay Pay, Alibaba's Alipay, etc.), these raw target information will be converted into transactions Target, because its data format or addressing mechanism has not yet been standardized, causing the matrix code or NFC tag to vary by payment service. example For example, for Taiwanese merchants who only accept matrix codes generated by Taiwan's payment services, the matrix codes generated by devices using SoftBank's payment services cannot be recognized and resolved into corresponding payment targets. In this case, a target parsing service is needed, which can identify the addressing mechanism of the original target information of the customer or merchant, and resolve the target in the original target information.

The object of the present invention is to provide a method and system for analyzing targets, focusing on providing reliable and effective target analysis for subsequent transactions.

In order to achieve the above object, the present invention discloses a method for parsing a target, the method comprising: (a) a local parsing node receives a target and a target parsing type from a user connected to the local parsing node, wherein the local parsing node and at least one remote resolution node as part of a plurality of resolution nodes that are communicatively connected to a cross-node transaction network; (b) the local resolution node determines whether the target can be resolved into at least one type corresponding to the identifier, and upon receipt of a whitelist that includes part of other resolution nodes that can resolve the target, the local resolution node confirms that the target is unresolvable, as suggested by the local resolution node itself; (c) When the target is unresolvable, the local resolution node transmits the target resolution type and the target to at least one remote resolution node; and (d) the local resolution node returns at least A number of parsable results to determine if the target is parsable.

In one embodiment, the local parsing node stores a blacklist, and the blacklist is updated every time a time to live (TTL) elapses, and the blacklist records at least one of the parsing nodes that understand the mechanism one.

In another embodiment, in step (c), the local resolution node transmits the target resolution type and the target to the at least one remote resolution node, each of the at least one remote resolution node will be different from the blacklist Retrieve the parsed nodes for the portion retrieved using the mechanism in .

In another embodiment, in step (c), the local resolution node transmits the target resolution type, the mechanism and the target to the at least one remote resolution node, each of the at least one remote resolution node will follow One of the parsing nodes in the part of the whitelist is the same as and different from at least one of the parsing nodes retrieved from the blacklist using the mechanism.

In another embodiment, both the whitelist and the blacklist are generated according to one of a merchant location and a customer location.

In another embodiment, in step (c), the local resolution node may choose to simultaneously or sequentially transmit the target resolution type, the addressing mechanism and the target to the at least one remote resolution node.

In order to achieve the above purpose, the target resolution system includes: a target resolution system including a cross-node transaction network, a user device and several resolution nodes.

The plurality of resolution nodes are communicatively connected to a cross-node transaction network containing some resolution nodes, wherein a part of the resolution nodes includes at least one remote resolution node and a local resolution node.

The local resolution node will communicate with the user device, receive a target and a target resolution type from the user device, determine whether the target can be resolved into at least one identifier corresponding to the target resolution type, and receive the local resolution If the node itself proposes to include a part of a whitelist of other resolution nodes that can resolve the object and confirm that the object is unresolvable, the local resolution node will send the object resolution type and the object to the at least one remote resolution node node, and according to the at least one solution from the remote Determine whether the target is parseable by counting at least one parseable result returned by the parsing node.

In the case of two-stage target resolution, when the local resolution node cannot resolve the target in the first phase for whatever reason, the at least one remote resolution node will provide more comprehensive resolution services in the second phase of target resolution to eliminate ignorance Mechanisms of raw target information or situations where the target cannot be resolved with knowledge of its mechanism, thus significantly improving the reliability of target resolution. At the same time, the mechanism caching method is used to block the transmission of target information to the resolution nodes in the blacklist that do not understand the mechanism, and the notification service method is used to narrow the transmission range of the target to the resolution nodes in the white list that can resolve the target. Compared with sending the target information to the second stage indiscriminately, the above two methods can reasonably reduce the traffic generated by the message transmission between the target analysis of the first stage and the target analysis of the second stage, and then make the target analysis Faster and more efficient. Therefore, the method and system of the present invention are superior to conventional techniques in providing more reliable and faster object resolution.

Other purposes, advantages and novel technical features of the present invention are further described below.

70: Parsing target

71: Cross-node transaction network

72: user device

73: Parsing nodes

73a: local parsing node

73b, 73c, 73d: remote resolution nodes

73e: target sending node

Fig. 1 is a flow chart, and it shows an embodiment of the method for analyzing object of the present invention; Fig. 2A and 2B are a flow chart related to another embodiment of the method for analyzing object of the present invention; Fig. 3 is Fig. 2 Figure 4 is a flowchart showing the procedure for obtaining the original target information, which supplements the methods in Figures 1 and 2; Figure 5 is a flowchart showing the use of the target analysis of the present invention An embodiment of the transaction payment program; Fig. 6 is a schematic diagram showing an implementation of the network structure of the system for parsing objects of the present invention Example; and FIG. 7 is a schematic diagram showing another embodiment of the network structure of the system for parsing objects according to the present invention.

The words used herein are used to describe the details of specific embodiments of the present invention, and all words should be reasonably interpreted in the broadest sense. Certain terms are emphasized below; any limiting terms are to be defined by the specific examples.

The embodiments described below can be implemented through programmable circuits programmed or configured by software and/or firmware, or through special function circuits as a whole, or a combination of the above. The special function circuit (if present) can be implemented in the following forms, for example: one or several application specific integrated circuits (ASIC), programmable logic device (PLD), field programmable logic gate array (FPGA).. .wait.

Embodiments described herein relate to a method and a system for resolving an object when an object provider provides raw object information to a user, which object may be used in a subsequent transaction. In general, raw goal information can be provided in a number of different ways so long as it can be used to generate a mechanic and the resulting goals. The mechanism described here refers to the data format of the raw object data. According to the nature of the transaction, one of the target provider and the user can propose the original target information, and the other party can obtain the target from the original target information in the transaction. The target resolution type is usually determined by the nature of the transaction. In one embodiment, the target resolution type is specified by the user. A target may be information embedded in the raw target information and parsed into an identifier. In one embodiment, there are three types of identifiers related to mobile transactions, namely MSN (Mobile Subscriber Number), MSID (Merchant Service Universally Unique Identifier), and MSU (MSN and MSID), respectively corresponding to a target resolution type. The key point of the method or system is two-stage target parsing, one is executed by a local parsing node, and the other is executed by at least one remote parsing node. The local parser Both the node and the at least one remote resolution node are part of several resolution nodes in the system. In order to avoid the network congestion caused by sending the target and the target resolution type to other resolution nodes without any choice, the mechanism caching method and prompt service method are used to reduce the query of other resolution nodes for target resolution The number of times to solve the problem of network congestion. For the network structure of the target resolution system, a cross-node transaction network is used to communicate and connect several resolution nodes, including a local resolution node and at least one remote resolution node. Implementations of the method and system are described below.

As previously mentioned, in one embodiment, an object resolution method may be used to facilitate transactions between users and object suppliers. Considering the trend of using mobile wallets for transactions, the target parsing method in Figure 1 focuses on parsing the target into specific identifiers related to mobile transaction services, that is, the MSN of the customer, the MSID of the merchant, and the MSU of the store card, where the The MSU contains customer and merchant identification numbers. Transactions described herein include, but are not limited to, payment transactions.

The goal provider provides its own original goal information, and conveys the original goal information and the mechanism of the original goal information to the user. The user then extracts the goal from the raw goal information and communicates the mechanism, the goal, and the goal resolution type to the local resolution node. The original target information and the mechanism of the target resolution type can be predetermined by the system. Therefore, there may be no need for a mechanism to communicate the original object information and the object resolution type from the object provider to the user and further to the local resolution node. As for the original target information, it is defined as the source information of the captured target and stored in the form of data, including but not limited to matrix code (QR code), near field wireless communication tag (NFC tag), voice signature and fingerprint one. The mechanism of the raw object information is the proprietary data format of the original object information, which is supported by a payment service provider and, in one embodiment, can be provided to the user by the object provider. The types of these mechanisms include but are not limited to matrix code (QR code) mechanism, short-range wireless communication mechanism, voice mechanism and fingerprint mechanism, and these mechanisms can be supported by payment service providers. For example, PAY PAY as A payment service provider can use different mechanisms (such as matrix code mechanism, short-range wireless communication mechanism, voice mechanism and fingerprint mechanism) to generate original target information. The target itself is the information obtained by extracting the features of the original target information. For example, by scanning matrix codes, sensing NFC tags, extracting voice signatures from voices, or scanning fingerprints to extract features and get objects from this raw object information. The format of this target can be a string.

From the perspective of transaction behavior, users may be merchants and target suppliers may be customers. In this case, assuming the matrix code as the mechanism of the original target information, the customer presents the matrix code through a portable/mobile device (such as a mobile phone) and the merchant or the merchant's cashier device (such as a POS machine) scans the customer's matrix code To obtain an object, that is, a matrix code word string. Alternatively, the user may be a customer and the target provider may be a merchant. In this case, assuming that the matrix code is still used as the original target information mechanism, the merchant presents the matrix code, and the customer's mobile device scans the merchant's matrix code to obtain the matrix code string.

The object resolution type is an identifier of an object that has been resolved. In one embodiment, it can be an MSN, an MSID, or an MSU, corresponding to an object that can be resolved to MSN, MSID, or MSN plus MSID, respectively. MSN is used when at least one identifier resolved from the target is related to the customer. MSID is used when at least one identifier parsed from the target is associated with the merchant. MSU is used when at least one identifier parsed from the target relates to both the customer and the merchant. For example, the occasions involving the use of MSN, MSID, and MSU are to use the customer's original target information for transaction payment, the merchant's original target information for transaction payment, and the store card's original target information for transaction payment. The store card stores credit from the merchant to the customer. In one embodiment, after obtaining the target from the original target information, a customer or merchant gives the target resolution type to the local resolution node. Any statement that "the target is parsed into at least one identifier corresponding to the target parsing type" disclosed in the present invention refers to at least one Identifiers from object resolution can be recognized at the local resolution node where object resolution is performed. Regarding the hardware architecture disclosed in the present invention, a local resolution node and at least one remote resolution node are part of a plurality of resolution nodes, and the plurality of resolution nodes are communicatively connected to a cross-node transaction network. The local resolution node service will receive the target directly from the user, while every other remote resolution node will not receive it.

A method of parsing a target includes the following steps

Step S110: a local resolution node receives the target and the target resolution type from the user. In the preprocessing stage before this step, the user obtains the object and the object resolution type, for example by scanning a matrix code or transmitting an NFC tag. In one embodiment, the target resolution type is predetermined by the system, which may be an application program installed on the customer's mobile device or software installed on the merchant's POS machine or server. In this step, the local parsing node receives the goal and the goal parsing type from the user, so as to perform the subsequent first-stage goal parsing.

Step S120: the local resolution node determines whether the object can be resolved into at least one identifier corresponding to the resolution type of the object. This step is for the first stage of object resolution, trying to resolve the object into at least one identifier. If the object is resolvable, the at least one identifier is an MSN when the object resolution type is MSN type, an MSID when the object resolution type is MSID type, or an MSU when the object resolution type is MSU The type is an MSN plus an MSID. In one embodiment, the MSD identifies a globally unique mobile phone number associated with a globally unique customer: the MSID identifies a globally unique merchant ID associated with a globally unique merchant; and the MSU identifies A unique store card in the world, which is related to the amount given to customers by merchants. When the local parsing node determines that the target cannot be parsed without any internal error when parsing the target, step S130 will be executed. Otherwise, report a notification that the object is successfully parsed and do not execute steps S130 and S140.

Step S130: The local resolution node transmits the target resolution type and the target to One less remote parsing node. This step is a transmission stage. The at least one remote resolution node may be one or several remote resolution nodes. As mentioned above, when the local resolution node is not filtered or randomly broadcasts the target resolution type and the target to the remaining or all remote resolution nodes, it will cause network congestion and thus reduce the resolution of the target speed. As suggested above, the notification service method for solving the network congestion problem will be described next.

Step 140: The local parsing node determines whether the target is parsable according to the quantity of at least one parsable result returned by the at least one remote parsing node. This step is the target analysis of the second stage. When each node in the at least one remote parsing node determines that the target is resolvable, the remote parsing node returns a parsable result to the local parsing node. When the remote parsing node judges that the target cannot be parsed, it will not return a parsable result. The number of parsable results sent back to the local parsing node is a criterion for the local parsing node to determine whether the target is parsable. With a two-stage goal resolution, as long as the goal is resolved in either the first or second stage, all parties involved in the transaction relying on the instruction will be allowed to proceed with the transaction.

On the basis of the method shown in FIG. 1 , the method for parsing objects shown in FIG. 2A and FIG. 2B is a detailed version of the aforementioned method. The difference between the two is that step S110' replaces step S110, steps S121 to S124 derived from the confirmation result of step S120, and steps S141 to S144 replace step S140. In order to avoid repeated descriptions, only the steps in FIG. 2A and FIG. 2B that are different from those in FIG. 1 and the additional steps will be described below.

The following step S110' replaces step S110 in FIG. 1 .

Step S110': A local resolution node receives a goal, a mechanism and a goal resolution type from the user. The difference between this step and the original step S110 is that the user additionally transmits the mechanism to the local resolution node for the first stage target resolution. In one embodiment, an object parsing system is implemented to generate And accept the matrix code mechanism and NFC tag mechanism, the user needs to provide this mechanism to the local parsing node.

As shown in FIG. 2A , the following steps S121 to S124 are derived from the determination result of step S120 in FIG. 1 .

Step S121: When the local resolution node understands the mechanism and resolves the object to be the at least one identifier in step S120, the local resolution node confirms that the object is resolvable and skips steps S130 and steps S140 to S144. When the local resolution node understands the mechanism and resolves the object to the at least one identifier, this step concludes that the object can be resolved to the at least one identifier without going through the second-stage object resolution.

In the same high-level mechanism, such as the matrix code mechanism and the NFC tag mechanism, each high-level mechanism can further include several low-level mechanisms (data formats). Taking the matrix code mechanism as an example, if the target is a 13-digit matrix code string and the target resolution type is MSN (which can be used as a globally unique mobile phone number), the low-level mechanism can be country code (3 digits), region code (3 digits) and local phone number (7 digits). Mechanism can mean higher-order mechanism, lower-order mechanism, or both, depending on the context. Each parsing node has a preset list that contains at least one preset mechanism that the parsing node knows about. Therefore, if the mechanism of the original object information is the same as one of the at least one default mechanism in the default list of the local resolution node, the mechanism of the original object information will be considered understandable by the local resolution node. In one embodiment, the default list of the local resolution node is partially or completely different from the default list of at least one remote resolution node (of which the resolution nodes are a part). If the at least one remote resolution node is completely consistent with the preset list of local resolution nodes, the target resolution in the second stage is not very helpful.

Step S122: When any internal error occurs when the local parsing node resolves the object in step S120, the local parsing node determines that the object is unparseable and skips steps S130 and S140 to S144. Different from step S121, when the local parsing node receives an internal error when parsing the object and no matter it is caused by a hardware or software problem, this step concludes that the object cannot be parsed into the at least one identifier and does not need to perform a second Phase goal parsing.

Step S123: When the local resolution node fails to understand the mechanism or understands the mechanism but fails to resolve the object into the at least one identification code in step S120, the local resolution node determines that the object cannot be resolved. The purpose of this step is to determine that the target cannot be resolved in the first stage and to prepare for the target resolution in the second stage. Two conditions are required to start the second-stage analysis. One is that when the mechanism is not in the preset list of the local resolution node, the mechanism is determined not to be understood by the local resolution node. Another is that the mechanism is in the default list of the local resolution node but the local resolution node cannot find the at least one identifier parsed from the target. When one of the above two conditions is fulfilled, the target is determined to be unresolvable to the at least one identifier and the second stage of target resolution should be performed.

Step S124: When the local parsing node receives a whitelist including some other parsing nodes that can parse the target in step S120 and gets suggestions from the prompt service of the local parsing node in step S120, the local parsing node considers the target is unparseable. When the local parsing node receives the white list, this step determines that the target is unparsable but will not execute the remaining steps. The whitelist is a spontaneous response, and not every parsing node will provide the prompt service to itself or other parsing nodes every time. However, when the whitelist is available, the local resolver node only needs to require some of the other resolver nodes in the whitelist rather than all other resolver nodes to resolve the target, that is, a limited number of nodes among all resolver nodes, thereby solving Fan-out issues.

As shown in FIG. 2B , steps S141 to S144 described below replace step S140 in FIG. 1 .

Step S141: Each node in the at least one remote resolution node determines whether it understands the mechanism and can resolve the object into at least one pair of identifiers of the object resolution type. This step aims to It is determined whether each of the at least one remote resolution node understands the mechanism and can resolve the object in a second stage of object resolution. For the understanding of the mechanism, similar descriptions can refer to the description of step S121, which will not be repeated here. When the remote parsing node understands the mechanism and parses the object into the at least one identifier, step S142 is executed. When any internal error occurs, the remote resolution node cannot understand the mechanism, the remote resolution node understands the mechanism but cannot resolve the object as the at least one identifier, or the remote resolution node returns the object that can resolve Part of other resolution nodes and a white list prompted by the prompt service at the remote resolution node are given to the local resolution node, and step S143 is executed.

Step S142: The remote resolution target returns a tag, which can correspond to the at least one identifier and indicates that the target can be resolved by the local resolution node. The mark here refers to the parsable result in step S140, and in order to hide the at least one identifier from the local resolution node that initiates target resolution, the mark may be encrypted data. Since the mark can correspond to the at least one identifier, the mark can be used to correspond back to the at least one identifier when using the mark for transactions.

Step S143: The remote parsing node does not return the token. When an internal error is detected during target parsing in the second stage, the mechanism cannot be understood, the target cannot be parsed after understanding the mechanism, or the whitelist exists, the remote parsing node does not return a flag. It should be noted here that the white list provided by the second-stage target analysis is meaningless to the second-stage target analysis, so it will be discarded.

Step S144: When the number of at least one mark received from the at least one remote resolution node is one, the local resolution node confirms that the target is resolvable: or when the number of the mark is zero or exceeds one, then confirm The target cannot be parsed. This step aims at obtaining a conclusion that the target is resolvable when the quantity of the at least one mark received from the at least one remote resolution node is one. When the number of the tags is zero or greater than one, the local resolution node determines that the object cannot be resolved into the at least one identifier.

According to FIG. 3 , step S142 further includes the following steps.

Step S1421: the remote resolution node confirms the target resolution type. When the target resolution type is MSN type or MSU type, step S1422 is executed. When the target resolution type is MSID class, step S1423 is executed.

Step S1422: The remote resolution node obtains a user ID, and the user ID is passed through KYC (Know-Your-Customer) in the remote resolution node or another server connected to the cross-node transaction network A service is queried to identify the target provider having the MSN of the at least one identifier. Next, the remote resolution node replaces the MSN in the at least one identifier with the user ID, generates a tag corresponding to the at least one identifier, and returns the tag to the local resolution node. Although the target provider may have more than one MSN, the user ID is a unique identifier for the target provider. The main consideration of sending back tags, that is, encrypted information, rather than MSN is to keep the user ID secret from the local resolution node, because the local resolution node may not have any business or service relationship with the remote resolution node. At the same time, compared with the user ID, MSN is not a unique identifier. In the case where the target resolution type is MSN class, this tag will be used to correspond back to a corresponding MSN; in the case of the target resolution type is MSU class, this tag will be used to correspond back to the corresponding MSN and MSID .

Step S1423: the remote resolution node generates a tag corresponding to the at least one identifier and returns the tag to the local resolution node. In the case where the target resolution type is MSID class, KYC query service is not required because MSID itself is a unique identifier. Therefore, the remote parsing node will generate a tag that can only correspond to the MSID.

In addition to providing the notification service method of the whitelist, the mechanism caching method of providing the blacklist is another countermeasure to solve the fan-out problem. Unlike the whitelist, the blacklist includes at least one mechanism and At least one of all parsing nodes does not understand and cannot correspond to any mechanism in the blacklist. Each parsing node has a blacklist, and the blacklist is updated every time a time-to-live (TTL) passes, which is regarded as a self-destruct time. The local resolution node in step S123 and the remote resolution nodes unable to understand the mechanism in step S143 will be recorded in the blacklist of the local resolution node in the next update. In the stage of target information transmission in step S130, the reminder service method and the mechanism cache method can be selected or used together. When the whitelist exists in the local resolution node and the notification service mode is adopted independently, the local resolution node transmits the mechanism, the target and the target resolution type to the at least one remote resolution node, and the at least one remote resolution node This mechanism can be corresponded to in the whitelist. When the mechanism cache method is adopted alone, the local resolution node will transmit the mechanism, the target and the target resolution type to at least one remote resolution node, and each node in the at least one remote resolution node will be different from the blacklist At least one node in all resolution nodes corresponding to the mechanism. When the prompt service method and the mechanism cache method are used together, the local resolution node will transmit the mechanism, the target and the target resolution type to the at least one remote resolution node, and each node in the at least one remote resolution node It will be one of the several parsing nodes corresponding to the mechanism in the white list and different from at least one node among the several parsing nodes corresponding to the mechanism in the black list. In terms of transmission methods, the local resolution node can simultaneously or sequentially transmit the mechanism, the target, and the original target information to at least one remote resolution node. Generally speaking, the whitelist and blacklist can be generated according to at least one factor of the merchant's location and the customer's location.

The method in FIG. 1 and FIG. 2 includes the following steps, as shown in FIG. 4 , the steps are used to generate and obtain the original target information.

Step S410: The user requests the original target information and the target resolution type from the target information sending service of a resolution node, and the resolution node is authorized to send the original target information to the user. The target information delivery service is provided by a back-end server, which is provided as a payment service The provider's resolution node is co-located.

Step S420: The resolution node having the target information delivery service generates a target tag and transmits the tag to one of the plurality of resolution nodes. This object is marked as encrypted information.

Step S430: The parsing node receives the target tag, maps the tag to at least one identifier related to the target parsing type, and records the target tag in a corresponding list of the parsing node. This step aims to establish the correspondence between the target tag and the user-related identifier. When the raw target information is used for target resolution, the target tag can be used to correspond back to the at least one identifier.

Step S440: After receiving the confirmation from the resolution node that the target tag has been added to the corresponding list, the resolution node generates the original target information including the target tag and sends the original target information to the user. The target mark is the encrypted information contained in the original target information, and the target mark can be obtained by retrieving and decoding the content of the original target message.

According to Figure 5, the following steps adopt a program using target resolution technology, which resolves the target provider's target into One MSN.

Step S510: A mechanism whereby the user receives the original goal information from the goal provider and can selectively parse the original goal information to obtain the original goal information.

Step S520: the user sends price information such as amount, currency, the original target information, the optional mechanism, and the optional invoice ID to the user's backend server.

Step S530: After receiving the original target information from the user, the user's backend server will do three things. One is to analyze the original target information and determine its mechanism when the mechanism is not provided to the user in step S510. In step S520, if the user does not provide an invoice ID, an invoice ID can be selectively generated, The third is to determine the price information when the user does not provide the price information in step S520.

Step S540: The user's backend server sends the mechanism, target, amount, currency, optional invoice ID, user's MSID, and user information (such as merchant name, address, etc.) to the host node to request a payment operation. The host node is communicatively connected to the cross-node transaction network and is able to execute cross-node transactions for users and targeted suppliers. The user and the target supplier are also communicatively linked to the cross-node transaction network.

Step S550: The host node checks whether a local resolution node connected to the cross-node transaction network successfully resolves the target into MSN with the target and the mechanism. When the local parsing node cannot parse the target, step S560 is executed. Otherwise, step S580 is executed.

Step S560: The host node broadcasts the target and the mechanism to at least one remote node connected to the cross-node transaction network, and checks whether the at least one remote parsing node can resolve the target as having the target and the Mechanism of MSN. When the at least one remote node cannot resolve the target, step S570 is executed. Otherwise, step S580 is executed.

Step S570: The host node confirms that the transaction is not completed and reports an error to the payment request in step S540.

Step S580: The host node responds to the request of the user's backend server by notifying that the payment request has been successfully sent. At the same time, a remote resolution node notifies a target provider's back-end server of a payment request, the payment request includes amount, currency, user information (if provided by the user's back-end server in step S540), invoice ID (if provided by the user's backend server in step S540) and a parsed user ID.

Step S590: The target provider's backend server sends a notification to the target provider, requesting approval of the payment request required for the transaction.

As can be seen from the above, in order to achieve the method of parsing the goal, there is a system behind it. Referring to FIG. 6 and FIG. 7 , a system of analysis objects 70 includes: a cross-node transaction network 71 , a user device 72 and several analysis nodes 73 . Before starting to describe this system in detail, it should be noted that this system follows the definitions, concepts and embodiments of all terms in the above methods.

In one embodiment, the cross-user transaction network 71 is implemented with distributed ledger technology. The user device 72 owned by the user obtains raw object information, a mechanism, and an object resolution type from an object provider (not shown). In one embodiment, the mechanism and the object resolution type may be defaulted by the system, so the object provider does not need to provide this information. When the owner is a client, the user device 72 can be a mobile device, including but not limited to a mobile phone, a tablet computer, or a notebook computer. When the owner is a merchant, the user device 72 can be a POS machine. The resolution nodes 73 are communicatively connected to the cross-node transaction network 71 and include a local resolution node 73a and at least one remote resolution node 73b, 73c, 73d, which are part of the resolution nodes 73. Figure 6 and Figure 7 are the embodiments of a single remote resolution node 73b and several remote resolution nodes 73b, 73c, 73d respectively. In one embodiment, each of the resolution nodes 73 is a node operated by a telecommunications company, and these nodes can manage transactions of digital assets (such as digital currencies, digital securities, digital bonds, digital futures, and digital precious metal currencies) . The local resolution node 73 is communicatively connected to the user device 72 and the user's transaction service provider, and the at least one remote resolution node 73b, 73c, 73d is not directly connected to the user device 72 (not its own communication service provider) )communication. The local resolution node 73a receives a target, a mechanism (optional) and a target resolution type from the user device 72, determines whether the target can be resolved into at least one identifier corresponding to the target resolution type, and then when no When an internal error occurs and the target cannot be parsed, the target resolution type and the target are sent to the at least one remote parsing node 73b, 73c, 73d, and determine whether the target can be parsed based on the quantity of at least one parseable result returned by the at least one remote parsing node 73b, 73c, 73d.

Since the prompt service method involves a white list, when the local resolution node 73a receives a white list, the local resolution node 73a will transmit the target resolution type, the mechanism and the target to at least one remote resolution node 73b, 73c, 73d ; The white list includes a part of the resolution nodes 73, each node in the part of the resolution nodes can resolve the target, and the white list is suggested by the prompt service of the local resolution node. Mechanism caching, on the other hand, involves blacklists. The local parsing node 73a stores a blacklist which maps the mechanism to those parsing nodes which do not understand the mechanism, and the blacklist is updated every time a time-to-live (TTL) passes. When only the blacklist is in effect, the local resolution node 73a transmits the target, the mechanism and the target resolution type to the at least one remote resolution node 73b, 73c, 73d, and each of the at least one remote resolution node will different from at least one of the resolution nodes retrieved from the blacklist by the mechanism. When only the whitelist is in effect, the local parsing node 73a transmits the target, the mechanism and the target parsing type to the at least one remote parsing node 73b, 73c, 73d, and each of the at least one remote parsing node will is one of the resolution nodes for the portion retrieved from the whitelist by the mechanism. When the whitelist and blacklist take effect at the same time, the local parsing node 73a transmits the target, the mechanism and the target parsing type to the at least one remote parsing node 73b, 73c, 73d, and each of the at least one remote parsing node One will be one of the parsing nodes 73 in the part of the whitelist and different from at least one of the parsing nodes 73 retrieved from the blacklist by this mechanism. In addition to the mechanism cache method and the prompt service method, the transmission method of the local resolution node 73a to the at least one remote resolution node 73b, 73c, 73d to transmit the target, the mechanism and the target resolution type can be based on the traffic of the system 70 sequentially or concurrently implement.

The system 70 further includes a target sending node 73e, which is one of the resolution nodes and is authorized to send the original target information to the user device 72, and the target sending node is communicatively connected to the cross-node transaction network 71. The resolution node may be co-located with a backend server operated by the payment service provider and sending the original target information. In order to obtain the original object information, the user device 72 first sends a request for the original object information and the object resolution type to the object sending node 73e. After receiving the request and the target resolution type, the target sending node 73e generates a target token and sends the target token to one of the other resolution nodes 73 . The other parsing node 73 will receive the target tag, map the target tag to at least one identifier corresponding to the target parsing type, and add the target tag into the corresponding list of the other parsing target 73 . The target sending node 73e generates original target information including the target tag and sends the original target information to the user device 72 after receiving the confirmation that the target tag has been added to the corresponding list of the other parsing nodes 73 . When the target resolution type is one of MSN or MSU, the remote resolution nodes 73b, 73c, 73d perform the following steps: first, obtain a user ID through the KYC query system of the remote node or an external KYC query system, The user ID identifies the target provider by the MSN in the at least one identifier; the second is that the MSN in the at least one identifier is replaced by the user ID; the third is to generate one that can correspond to the at least one identifier mark; finally return the mark to the local parsing node 73a. When the target resolution type is MSID, the remote resolution node 73b, 73c, 73d generates a tag corresponding to the at least one identifier and returns the tag to the local resolution node 73a.

Although many technical features and advantages of the present invention have been described above, the disclosed functions and detailed structures are all illustrative. Without departing from the spirit of the present invention, the patent application for the present invention The broadest interpretation of the scope of rights includes improvements obtained by changing the shape, size, and arrangement of components of the present invention based on the teachings of this specification.

Claims (36)

A method for resolving an object, the method comprising: (a) a local resolution node receiving the object and an object resolution type from a user communicatively connected to the local resolution node, wherein the local resolution node and at least A remote resolution node is part of a plurality of resolution nodes that are communicatively connected to a cross-node transaction network; (b) the local resolution node determines whether the target can be resolved into at least one resolution type corresponding to the target and when receiving a whitelist that includes part of other resolution nodes that can resolve the target, the local resolution node confirms that the target is unresolvable; (c) when the target When it is unresolvable, the local resolution node transmits the target resolution type and the target to at least one remote resolution node; and (d) the local resolution node returns at least one resolveable number of results to determine if the target is parseable. The method as claimed in claim 1, wherein in step (a), the local resolution node further receives a mechanism of original object information provided by the user or an object provider. The method according to claim 2, wherein the user is a merchant and the target provider is a customer, or the user is a customer and the target provider is a merchant. The method according to claim 2, wherein the mechanism is one of a matrix code (Quick Response Code) mechanism, a near field communication (NFC) mechanism, an audio mechanism, and a fingerprint mechanism. The method as claimed in claim 4, wherein the user obtains the target from the target provider by scanning a matrix code, sensing an NFC tag, extracting a voice signature or scanning a fingerprint. The method as described in claim 1, wherein the target resolution type is one of MSN (Mobile Subscriber Number), MSID (Merchant Service Universally Unique Identifier), and MSU (MSN and MSID). The method as described in claim 1, wherein when the target resolution type is MSN, MSID or MSU type, the local resolution target will resolve the target to include an MSN, a MSID or An MSN and at least one identifier of an MSID, the at least one identifier corresponds to the target resolution type being MSN, MSID or MSU. The method as claimed in claim 2, wherein the step (b) further comprises: (b1) when the local resolution node understands the mechanism and resolves the target into at least one identifier, the local resolution node confirms that the target is resolvable And skip steps (c) and (d); (b2) when there is any internal error when parsing the target, the local parsing node confirms that the target is unparseable and skips steps (c) and (d); (b3) when The local resolution target cannot understand the mechanism or understands the mechanism but cannot resolve the target to the at least one identifier, the local resolution target confirms that the target is unresolvable; wherein the whitelist is a hint service of the local resolution node The suggestion, and the unsolicited reply by each of the resolution nodes and the notification service is provided by each of the resolution nodes. The method as claimed in claim 8, wherein the step (d) further comprises: (d1) each of the at least one remote resolution node confirms whether the remote resolution node understands the mechanism and can resolve the target to the At least one identifier corresponding to the target resolution type; (d2) When the remote resolution node understands the mechanism and resolves the target as the at least one identifier, the remote resolution node returns that it can correspond to the at least one identifier and indicates that A mark that the target can be parsed by the local parsing node, where the mark is the parsable result; (d3) when an internal error occurs, the remote parsing node cannot understand the mechanism, and the remote parsing node understands the mechanism but cannot Parsing the target, or the remote parsing node returns the part of the parsing nodes that can parse the target and the white list suggested by the prompt service of the local parsing node, the remote parsing node does not will return the mark; and (d4) when the number of the at least one mark returned from the at least one remote resolution node is one, the local resolution node confirms that the target is resolvable; when the number is zero or greater than one , the local resolver node considers the target unresolvable. The method as described in claim item 9, wherein the local resolution node stores a blacklist, and the blacklist is updated every time a Time to Live (TTL) passes, and the blacklist records the resolutions that do not understand the mechanism at least one of the nodes. The method as described in claim 10, wherein in steps (b3) and (d3), the local resolution node and the at least one remote resolution node that cannot understand the mechanism will be recorded in the blacklist when the blacklist is updated next time list and corresponds to the mechanism. The method as claimed in claim 10, wherein in step (c), the local resolution node transmits the target resolution type and the target to the at least one remote resolution node, each of the at least one remote resolution node will be different from The parsed nodes for the portion retrieved are retrieved from the blacklist using the mechanism. The method as claimed in claim 10, wherein in step (c), the local resolution node transmits the target resolution type, the mechanism and the target to the at least one remote resolution node, each of the at least one remote resolution node One will be the same as one of the parsing nodes in the part of the whitelist and different from at least one of the parsing nodes retrieved from the blacklist using the mechanism. The method as claimed in claim 13, wherein the white list and the black list are generated according to one of a merchant location and a customer location. The method as claimed in claim 2, wherein in step (c), the local resolution node simultaneously or sequentially transmits the target resolution type, the mechanism and the target to the at least one remote resolution node. The method as described in claim 9, wherein step (d2) further includes: the remote resolution node determines the target resolution type; when the target resolution type is one of MSN or MSU, the remote resolution node uses the remote The KYC (Know-Your-Customer) query system of the terminal resolution node or the external KYC query system obtains a user ID, and the user ID is identified by the MSN in the at least one identifier The target provider, then replaces the MSN in the at least one identifier with the user ID, then generates a tag that can correspond to the at least one identifier, and finally returns the tag to the local resolution node; and when the target The resolution type is MSID, and the remote resolution node generates a mark corresponding to the at least one identifier and returns the mark to the local resolution node. The method as described in claim 9, further comprising: the user asks a target sending node for the original target information including the target resolution type, and the target sending node is one of the resolution nodes and is authorized to send the original target information to the user; the target sending node generates a target mark and transmits the target mark to one of the parsing nodes, wherein the target mark is encrypted data; the parsing node receives the target mark and corresponds the target mark to at least one An identifier corresponding to the resolution type of the target, and adding the target mark to the corresponding list of the resolution node; tagging the raw goal information of the goal and sending the raw goal information to the user. The method as claimed in claim 1, wherein the local resolution node is service-bound with the user and the at least one remote resolution node is not service-bound with the user. The method as described in Claim 1, wherein the cross-node transaction network is a distributed ledger that can conduct cross-node transactions, and each of the resolution nodes is connected to the cross-node transaction network by communication A node run by a carrier that can manage digital asset transactions. A system for analyzing targets, the system includes: a cross-node transaction network; A user device; and several resolution nodes, which are communicatively connected to the cross-node transaction network, wherein a part of the resolution nodes include: at least one remote resolution node; and a local resolution node, which is communicatively connected to the user device , receiving a target and a target resolution type from the user device, determining whether the target can be resolved into at least one identifier corresponding to the target resolution type, when receiving the local resolution node itself suggested that the target can be resolved a part of a white list of other resolution nodes and confirm that the object is unresolvable, transmit the object resolution type and the object to the at least one remote resolution node, and based on the at least one remote resolution node returned from the at least one A number of parsable results to determine whether the target is parsable. The system as described in claim 20, wherein the original target information provided by a user or a target provider can be classified into the following mechanisms, namely matrix code (QR code), short-range wireless communication tag (NFC tag) , voice and fingerprints. The system as claimed in claim 21, wherein the user obtains the object from the object provider by scanning a matrix code, sensing an NFC tag, extracting a voice signature from sound, or scanning a fingerprint. The system according to claim 20, wherein the target resolution type is one of MSN (Mobile Subscriber Number), MSID (Merchant Service Universally Unique Identifier) and MSU (MSN and MSID). The system as described in claim 23, wherein when the target resolution type is one of MSN, MSID or MSU, the local resolution node will resolve the target into the at least one identifier, and the corresponding target resolution type is MSN, MSID or MSU, the at least one identifier may include an MSN, an MSID, or an MSN plus an MSID. The system as claimed in claim 21, wherein when receiving the white list, the local resolution node transmitting the target resolution type, the mechanism, and the target to at least one remote resolution node, each of the at least one remote resolution node being identical to one of the portion of the resolution devices in the whitelist, Wherein the white list is a spontaneous reply from each of the resolution nodes and the notification service is provided by each of the resolution nodes. The system as claimed in claim 21, wherein when each of the at least one remote resolution node understands the mechanism and resolves the target as the at least one identifier, the remote resolution node returns a response corresponding to the at least one identifier and a mark indicating that the target can be resolved by the local resolution node, when the quantity of the at least one mark returned from the at least one remote resolution node is one, the local resolution node confirms that the target is resolveable; when When the number is zero or greater than one, the local parsing node considers the object to be unparseable, wherein the flag is the parsable result. The system as described in claim 25, wherein the local parsing node stores a blacklist, and the blacklist maps the mechanism to a part of the parsing units that do not understand the mechanism, and every time the blacklist passes a lifetime ( TTL) will be updated once. The system as described in claim 27, wherein the local resolution node and the at least one remote resolution node that cannot understand the mechanism will be recorded in the blacklist when the blacklist is updated next time, can correspond to the mechanism and can retrieved by this mechanism. The system as recited in claim 27, wherein the local resolution node transmits the target resolution type and the target to at least one remote resolution node, each of the at least one remote resolution node will be different from the black list using the The mechanism retrieves at least one of the retrieved resolution nodes. The system as described in item 27 of the claim, wherein the local resolution node transmits the target resolution type, the mechanism and the target to the at least one remote resolution node, and each of the at least one remote resolution node will communicate with the One of the parsing nodes in the whitelist is the same as and different from the At least one of the parsing nodes retrieved by using the mechanism in the blacklist. The system as claimed in claim 27, wherein the white list and the black list are generated according to one of a merchant location and a customer location. The system as claimed in claim 21, wherein the local resolution node simultaneously or sequentially transmits the target resolution type, the mechanism and the target to the at least one remote resolution node. The system as described in claim 23, wherein when the target resolution type is one of MSN or MSU, the remote resolution node obtains a user ID through the KYC query system of the remote resolution node or an external KYC query system , the user ID identifies the target provider by the MSN of the at least one identifier, then replaces the MSN in the at least one identifier with the user ID, and then generates a corresponding to the at least one identifier a tag, and finally return the tag to the local resolution node; and when the target resolution type is MSID, the remote resolution node generates the tag that can correspond to the at least one identifier and returns the tag to the local resolution node . The system as claimed in claim 26, wherein the parsing nodes further include a target sending node, which is communicatively connected to the cross-node transaction network and authorized to send the original target information to the user device, wherein the target sending node After receiving the request from the user device about the original target information and the target resolution type, generate a target mark and transmit the target mark to one of the resolution nodes, so that the resolution node will correspond to the target resolution type The target tag of the at least one identifier is added to a corresponding list of the parsing node, and the target sending node will generate the target tag containing the target tag after receiving confirmation from the parsing node that the target tag has been added to the corresponding list. The original target information and send the original target information to the user device, wherein the target tag is encrypted data. The system as claimed in claim 20, wherein the local resolution node is service-bind with the user device and the at least one remote resolution node is not service-bound with the user device. The system as described in claim 20, wherein the cross-node transaction network is a distributed ledger network capable of cross-node transactions, and each of the resolution nodes is connected to the cross-node transaction network by communication Routing is a node that can be run by a telecommunications operator that manages digital asset transactions.

Images