CN109302376B - Account code generation method, account authorization method and account code fetching method - Google Patents
Account code generation method, account authorization method and account code fetching method Download PDFInfo
- Publication number
- CN109302376B CN109302376B CN201810485264.9A CN201810485264A CN109302376B CN 109302376 B CN109302376 B CN 109302376B CN 201810485264 A CN201810485264 A CN 201810485264A CN 109302376 B CN109302376 B CN 109302376B
- Authority
- CN
- China
- Prior art keywords
- account
- code
- information
- server
- batch
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/018—Certifying business or products
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
- G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/102—Entity profiles
Abstract
The invention discloses a method for authorizing a first account to a second account, which is characterized by being applied to a server and comprising the following steps: s1: generating first account code generation information according to a first account application ID, a first account interface ID and a first account code system ID confirmed by a first account client, and writing the first account code generation information into a batch table; s2: receiving second account authorization information sent by a first account client, wherein the second account authorization information at least comprises a second account ID, second account code fetching request range information and second account authority information; s3: and checking whether the inherent code generating structure of the second account is matched with the code generating structure of the second account requesting code fetching, and if so, writing the authorization information of the second account into the batch table. The invention has the beneficial effects that: (1) the authority setting of the code operation of different accounts is definite; (2) excessive authorization of accounts without corresponding permissions is avoided.
Description
Technical Field
The invention relates to the field of data tracing, in particular to an account code generating method, an account authorization method and an account code fetching method.
Background
The Open platform packages the service into a series of data interfaces which are easily recognized by a computer, namely Open application programming interfaces (openapis) through a software system Open Application Programming Interface (API) or function (function), so that the service can be called by a third party application, and an external third party application can increase the functions of the software system or use the resources of the software system through the Open API.
With the rise of the internet and open platforms, the phenomenon of multiple applications based on the same open platform is increasingly common, but the use authority setting of the applications is very fuzzy, so that the necessary secret information between the applications is possibly leaked. For example, a printing factory account downloads a code through an application, but since no authority control is performed, the printing factory authorizes the code authority to others, resulting in a large loss of code information leakage. Based on this drawback, the present invention proposes a method for code control by using an application through the relationship between the account and the code.
Disclosure of Invention
The invention aims to provide an account code generating method, an account authorization method and an account code fetching method, so that the permission setting of code operation of different accounts is definite.
Specifically, the invention is realized by the following technical scheme:
a method for authorizing a first account to a second account is applied to a server and comprises the following steps:
s1: generating first account code generation information according to a first account application ID, a first account interface ID and a first account code system ID confirmed by a first account client, and writing the first account code generation information into a batch table;
s2: receiving second account authorization information sent by a first account client, wherein the second account authorization information at least comprises a second account ID, second account code fetching request range information and second account authority information;
s3: and checking whether the inherent code generating structure of the second account is matched with the code generating structure of the second account requesting code fetching, and if so, writing the authorization information of the second account into the batch table.
Preferably, the step of checking in S3 whether the intrinsic code generating structure of the second account matches the code generating structure of the second account requesting code fetching includes:
and judging whether an application ID-interface ID-code system ID path consistent with the first account application ID, the first account interface ID and the first account code system ID exists or not according to a prestored 'account ID-application ID-interface ID-code system ID' association table of the second account, if so, judging that the paths are matched, and if not, judging that the paths are not matched.
Preferably, the batch table includes an ownership account ID identification bit and a usage right account ID identification bit, and the writing the second account authorization information into the batch table includes writing the second account ID in the second account authorization information into the ownership account ID identification bit and/or the usage right account ID identification bit.
Preferably, the batch table includes a start external code service serial number identification bit and an end external code service serial number identification bit, the second account request code fetching range information includes a start number and an end number, in S3, the writing the second account authorization information into the batch table includes: and respectively writing the start number and the end number into the identification bits corresponding to the start outer code service serial number and the end outer code service serial number.
Preferably, after S2 and before S3, the method further comprises:
s21: and judging whether the first account has authorization authority to the second account, if so, executing S3, and if not, sending authorization failure information to the first account.
Preferably, the batch table includes an ownership account ID flag and a usage right account ID flag, the second account permission information includes ownership and usage right, and in S21, the determining whether the first account has permission granted to the second account includes:
and judging whether the identification position of the ID of the first account in the batch table is consistent with the authority information of the second account, if so, judging that the first account has the authority authorized to the second account, and if not, judging that the first account does not have the authority authorized to the second account.
A first account code generation method, the method comprising:
SS 1: the method comprises the steps that a server receives first account information sent by a client, wherein the first account information comprises an account ID;
SS 2: the server sends each application ID associated with the account ID of the first account to the client according to a pre-stored association table of the account ID and the application ID of the first account;
SS 3: the client confirms that one application ID is a standby application ID in all application IDs sent by the server, and sends standby application ID confirmation information to the server;
SS 4: the server receives standby application ID confirmation information sent by the client, and sends each interface ID associated with the standby application ID to the client according to a prestored first account application ID and interface ID association table;
SS 5: the client confirms that one interface ID is a standby interface ID in all the interface IDs sent by the server, and sends standby interface ID confirmation information to the server;
SS 6: the server receives standby interface ID confirmation information sent by the client, determines a code system used by a first account code according to a pre-stored first account interface ID and code system ID association table, performs code generation operation, generates first account code generation information corresponding to the secondary code operation, and writes the first account code generation information into a batch table.
Preferably, the first account interface ID and the code system ID association table are one-to-one correspondence association tables.
A method of second account code fetching, the method comprising:
SSS 1: the client side where the second account is located sends the batch ID, the range information of the code to be taken in the code corresponding to the batch ID and the second account ID to the server;
SSS 2: the server finds an attribute column corresponding to the batch ID in a batch table stored in the server according to the batch ID;
SSS 3: the server checks whether a second account ID exists in the using account ID identification position in the attribute column, if so, the server sends a code corresponding to the range information to the second account, and if not, the server does not send the code to the second account.
Preferably, the range information of the code to be taken in the code corresponding to the batch ID includes a taking start number and a taking end number.
The invention has the beneficial effects that: (1) the authority setting of the code operation of different accounts is definite; (2) excessive authorization of accounts without corresponding permissions is avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram illustrating a method for a first account to authorize a second account according to a first embodiment of the present invention;
FIG. 2 is a diagram illustrating a method for a first account to authorize a second account according to a second embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a first account code generation method according to the present invention;
fig. 4 is a schematic diagram of a second account code fetching method provided by the present invention.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present invention. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The present invention will be described in detail below by way of examples.
The invention provides a method for authorizing a first account to a second account, which is applied to a server as shown in figure 1, and the method comprises the following steps:
s1: and generating first account code generation information according to the first account application ID, the first account interface ID and the first account code system ID confirmed by the first account client, and writing the first account code generation information into the batch table.
When each account generates a code, code generation information corresponding to the secondary code is generated at the same time, the batch table can be understood as a set of key data in the code generation operation of the account, specifically, if there is an account a, the account ID of the account a is "zhanghuA", the application ID of the application used for code generation is 1001, the interface ID of the interface used for code generation is 2001, and the code system ID of the code generation used for code generation is 3001, when the account a performs the first code generation, the information recorded in the batch table is as shown in table 1 below:
TABLE 1
An example of a lot table is shown in table 1 above, the data shown as "xxx" in table 1 represents data irrelevant to the present invention, and the information that can be read from table 1 above is:
the "batch ID" corresponds to a number of 1, indicating that this is the code generation information of the first batch of codes generated in the global;
"code system ID" is 3001, which indicates that the code system used for generating the code is code system No. 3001;
the "ownership account ID" is zhanghuA, "the right-to-use account ID" is zhanghuA, "the" start foreign code service serial number "is 000, and the" end foreign code service serial number "is 999, and these four pieces of information should be understood at the same time, that is, they are expressed as: the account A has ownership rights to 1000 generated codes corresponding to the external code service serial numbers 000-999, and the account A has usage rights to 1000 generated codes corresponding to the external code service serial numbers 000-999.
S2: and receiving second account authorization information sent by the first account client, wherein the second account authorization information at least comprises a second account ID, second account code fetching request range information and second account authority information.
The related information of the second account is sent to the server by the first account. Assuming that an account B exists and the account ID of the account B is zhanghuB, when the account A wants to authorize 100 codes of the foreign code service serial numbers of 101-200 in the generated codes to the account B for use, a client of the account A sends the account ID of the account B, zhanghuB, to a server, and simultaneously sends the corresponding foreign code service serial number range of 101-200 and the batch ID of the codes to be authorized to the server, so that the server can uniquely determine the codes authorized by the account A to the account B, wherein the codes corresponding to the batch ID of 1 and having the foreign code service serial numbers of 101-200 in the codes corresponding to the batch ID of 1.
S3: checking whether the inherent code generating structure of the second account code is matched with the code generating structure of the second account code requesting code fetching, and if so, writing the second account authorization information into the batch table; if not, no processing is performed.
The account A authorizes the generated code to the account B, and the inherent code generating structure of the account B is required to be the same as that of the code authorized by the account A no matter whether the account A grants the account B the use right or the ownership of the code. The code generation structure may be understood as a path structure for generating a code, i.e. an "application ID-interface ID-symbology ID" path, e.g. in table 2:
TABLE 2
The code generated by account A with code system ID of 1001 has three code generation paths, namely, the paths of application ID-interface ID-code system ID are respectively
Route 1: 1001-2001-3001;
route 2: 1003-2001-3001;
route 3: 1004-2001-3001;
assume that account a generates a batch of codes in path 1 and wishes to authorize the generated batch of codes to account B, and that the "account ID-application ID-interface ID-symbology ID" association table for account B, which is known to be pre-stored in the server, is shown in table 3:
TABLE 3
It can be seen that, in account B, there is no case where "application ID-interface ID-code system ID" is "1001-; similarly, the account a has an "application ID-interface ID-code system ID" path 1004-.
Further, the batch table includes an ownership account ID identification bit and a usage right account ID identification bit, and the writing the second account authorization information into the first account batch table includes writing the second account ID in the second account authorization information into the ownership account ID identification bit and/or the usage right account ID identification bit.
Similarly, taking table 1 as an example, the column of "ownership account ID" in table 1 is "zhanghuA" and the column of "right-of-use account ID" is also "zhanghuA", that is, the ownership account ID flag and the right-of-use account ID flag in the batch table are both the account ID "zhanghuA" of account a, when the code generated by account a needs to be authorized to account B, if the right of use is granted, the account ID "zhanghuA" of account B is written into the column corresponding to the "right-of-use account ID", that is, table 1 is modified to table 4:
TABLE 4
It can be clearly understood from table 4 that among the codes with the lot ID number of 1, the account B has the right of use for 51 codes with the external code service serial numbers of 50 to 100. Similarly, if the account ID of account B is written into the column corresponding to the "ownership account ID", the ownership of the corresponding code is also granted to account B.
Further, the batch table includes a start external code service serial number identification bit and an end external code service serial number identification bit, the second account request code fetching range information includes a start number and an end number, in S3, the writing the second account authorization information into the batch table includes: and respectively writing the start number and the end number into the identification bits corresponding to the start outer code service serial number and the end outer code service serial number.
That is, as shown in table 4, the start number 50 and the end number 100 are written into the corresponding columns of the start outer code service serial number and the end outer code service serial number, respectively, that is, the 51 codes with outer code service serial numbers of 50 to 100 are used to clarify the authority granted to the account B.
The invention has the beneficial effects that: the authority setting of the different accounts for operating the code is definite, namely the first account defines the authority of the code to be generated, such as the use right and/or ownership are granted to the second account.
Further, as shown in fig. 2, after S2 and before S3, the method further includes:
s21: and judging whether the first account has authorization authority to the second account, if so, executing S3, and if not, sending authorization failure information to the first account.
Taking account a as an example to authorize account B, the operation performed in step S21 is: the server checks whether account a is eligible to grant the corresponding rights to account B, i.e. if account a is to grant usage rights to self-generated codes to account B, account a is to have usage rights to these codes, if account a is to grant ownership rights to self-generated codes to account B, account a is to have ownership rights to these codes. For the server, the operation to be completed by the server is to determine whether the identifier where the first account ID is located is consistent with the second account permission information in the batch table, if so, determine that the first account has permission to authorize the second account, and if not, determine that the first account does not have permission to authorize the second account. For example, in table 1, account a is used as the first account in an example, the identification bits where the account ID "zhanghuA" is located correspond to the "ownership account ID" and the "usage right account ID", account B is used as the second account in this example, and regardless of whether the authority information of account B is "ownership" or "usage right", the identification bits where the account ID of account a is located are consistent with the authority information of account B, and account a can both authorize account B; assuming account a has granted the use of the code to account B without granting ownership of the code, and assuming account C also exists, account B can only grant the use of the corresponding code to account C, but not the ownership of the corresponding code, because account B itself has no ownership of the corresponding code. The invention has the beneficial effects that: excessive authorization of accounts without corresponding permissions is avoided. For example, the scheme of the invention ensures that the second account which has no ownership right only for the codes cannot grant ownership right for the codes to the other account, but only grants the use right for the codes to the other account.
Suitably, the present invention further provides a first account code generating method, as shown in fig. 3, where the method includes:
SS 1: the method comprises the steps that a server receives first account information sent by a client, wherein the first account information comprises an account ID;
SS 2: the server sends each application ID associated with the account ID of the first account to the client according to a pre-stored association table of the account ID and the application ID of the first account;
SS 3: the client confirms that one application ID is a standby application ID in all application IDs sent by the server, and sends standby application ID confirmation information to the server;
SS 4: the server receives standby application ID confirmation information sent by the client, and sends each interface ID associated with the standby application ID to the client according to a prestored first account application ID and interface ID association table;
SS 5: the client confirms that one interface ID is a standby interface ID in all the interface IDs sent by the server, and sends standby interface ID confirmation information to the server;
SS 6: the server receives standby interface ID confirmation information sent by the client, determines a code system used by a first account code according to a pre-stored first account interface ID and code system ID association table, performs code generation operation, generates first account code generation information corresponding to the secondary code operation, and writes the first account code generation information into a batch table.
For example, assuming that account a is a first account and the account ID thereof is "zhanghuA", the user logs in account a at the client, and then sends account ID "zhanghuA" of account a to the server; the server stores an association table of the association relationship between the account ID of the account a and each application ID, and further stores an association table of the application ID and the interface ID, and an association table of the interface ID and the code system ID, which may be a summary table as shown in table 2. Taking the information recorded in table 2 as an example, after the client provides the server with the account ID "zhanghuA", the server returns the application ID numbers 1001, 1002, 1003, 1004 to the client, so that the user selects one application ID from the client according to the needs of the user, assuming that the application ID selected by the client is 1001, and sends the application ID confirmation information to the server, and then the server returns the interface ID numbers 2001, 2002, 2003, and 2004 corresponding to the application ID 1001 to the client, the user selects one interface ID from the client according to the needs of the user, assuming that the interface ID selected by the user is 2002, and sends the interface ID confirmation information to the server; the server automatically confirms the code system with code system ID 3002 as the code system for account A code generation based on interface ID number 2002. Specifically, as shown in table 2, the first account interface ID and the code system ID association table are one-to-one association tables.
The server generates the code and generates the code generation information according to the code system ID, which is the prior art and is not described in detail in the invention.
The invention also provides a method for fetching a code of a second account, as shown in fig. 4, the method includes:
SSS 1: the client side where the second account is located sends the batch ID, the range information of the code to be taken in the code corresponding to the batch ID and the second account ID to the server;
SSS 2: the server finds an attribute column corresponding to the batch ID in a batch table stored in the server according to the batch ID;
SSS 3: the server checks whether a second account ID exists in the using account ID identification position in the attribute column, if so, the server sends a code corresponding to the range information to the second account, and if not, the server does not send the code to the second account.
The code fetching refers to an operation of fetching a corresponding code for an account granted with a corresponding authority of the code. For example, as shown in table 4, account B is granted a lot of codes, when account B needs to use the corresponding codes, as shown in SSS 1-SSS 3, account B sends the server a lot ID corresponding to the corresponding code, as shown in lot ID number 1 in table 4, and a range of codes to be taken, as clearly shown in table 4, account B has a right of use for 51 codes of the foreign code service serial numbers 50-100, account B can take part or all of the codes in the range as needed, for example, account B wants to take 5 codes of 56-60 this time, and then 56 and 60 are sent to the server as a start number and an end number for taking, respectively, that is, a data range of the codes to be taken is uniquely determined to the server.
After the server receives the batch ID number 1, the taking start number 56 and the taking end number 60, an attribute column corresponding to the batch ID is found in a batch table stored in the server; thereafter, the server checks whether the account ID of account B exists in the use account ID flag in the attribute column, and if so, transmits the code corresponding to the access start number 150 and the access end number 199 to account B, and if not, the server does not transmit the code to account B. The attribute column described in the present application is an information column for showing attribute information of a code as shown in columns 2 to 5 in table 4.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (8)
1. A method for authorizing a first account to a second account, which is applied to a server, the method comprises the following steps:
s1: generating first account code generation information according to a first account application ID, a first account interface ID and a first account code system ID confirmed by a first account client, and writing the first account code generation information into a batch table;
the code generation information comprises a code system ID, a batch ID, an application ID, a starting external code service serial number and an ending external code service serial number, and the batch table is a set of key data in the code generation operation of the account;
s2: receiving second account authorization information sent by a first account client, wherein the second account authorization information at least comprises a second account ID, second account code fetching request range information and second account authority information;
s3: checking whether the inherent code generating structure of the second account is matched with the code generating structure of the second account requesting code fetching, and if so, writing the authorization information of the second account into the batch table;
wherein, the code generating structure is a path structure for generating codes;
step S3 includes: judging whether an application ID-interface ID-code system ID path consistent with the first account application ID, the first account interface ID and the first account code system ID exists or not according to a prestored account ID-application ID-interface ID-code system ID association table of the second account, if so, judging that the paths are matched, and if not, judging that the paths are not matched;
the batch table comprises an ownership account ID identification bit and a usage right account ID identification bit, and the writing of the second account authorization information into the batch table comprises writing a second account ID in the second account authorization information into the ownership account ID identification bit and/or the usage right account ID identification bit.
2. The method of claim 1, wherein the batch table includes a start outsde service serial number identification bit and an end outsde service serial number identification bit, the second account request code fetching range information includes a start number and an end number, in S3, the writing the second account authorization information into the batch table includes: and respectively writing the start number and the end number into the identification bits corresponding to the start outer code service serial number and the end outer code service serial number.
3. A method for a first account to authorize a second account according to any of claims 1-2, wherein after S2 and before S3, the method further comprises:
s21: and judging whether the first account has authorization authority to the second account, if so, executing S3, and if not, sending authorization failure information to the first account.
4. The method of claim 3, wherein the batch table includes an ownership account ID identification bit and a usage right account ID identification bit, the second account permission information includes ownership and usage right, and the determining whether the first account has permission to be granted to the second account in S21 includes:
and judging whether the identification position of the ID of the first account in the batch table is consistent with the authority information of the second account, if so, judging that the first account has the authority authorized to the second account, and if not, judging that the first account does not have the authority authorized to the second account.
5. A first account code generation method, the method comprising:
SS 1: the method comprises the steps that a server receives first account information sent by a client, wherein the first account information comprises an account ID;
SS 2: the server sends each application ID associated with the account ID of the first account to the client according to a pre-stored association table of the account ID and the application ID of the first account;
SS 3: the client confirms that one application ID is a standby application ID in all application IDs sent by the server, and sends standby application ID confirmation information to the server;
SS 4: the server receives standby application ID confirmation information sent by the client, and sends each interface ID associated with the standby application ID to the client according to a prestored first account application ID and interface ID association table;
SS 5: the client confirms that one interface ID is a standby interface ID in all the interface IDs sent by the server, and sends standby interface ID confirmation information to the server;
SS 6: the server receives standby interface ID confirmation information sent by the client, determines a code system used by a first account code according to a pre-stored first account interface ID and code system ID association table, performs code generation operation, generates first account code generation information corresponding to the secondary code operation, and writes the first account code generation information into a batch table.
6. The method of claim 5, wherein the first account interface ID and the system code ID association table are a one-to-one association table.
7. A method for code fetching of a second account, which is used for the method for authorizing the second account by the first account according to any one of claims 1-4, and is characterized in that the method comprises the following steps:
SSS 1: the client side where the second account is located sends the batch ID, the range information of the code to be taken in the code corresponding to the batch ID and the second account ID to the server;
SSS 2: the server finds an attribute column corresponding to the batch ID in a batch table stored in the server according to the batch ID;
SSS 3: the server checks whether a second account ID exists in the using account ID identification position in the attribute column, if so, the server sends a code corresponding to the range information to the second account, and if not, the server does not send the code to the second account.
8. The method of secondary account code fetching according to claim 7,
and the range information of the code to be taken in the code corresponding to the batch ID comprises a taking starting number and a taking ending number.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810296824 | 2018-03-30 | ||
| CN2018102968246 | 2018-03-30 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109302376A CN109302376A (en) | 2019-02-01 |
| CN109302376B true CN109302376B (en) | 2021-05-28 |
Family
ID=65167731
Family Applications (3)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810485264.9A Active CN109302376B (en) | 2018-03-30 | 2018-05-18 | Account code generation method, account authorization method and account code fetching method |
| CN201810485534.6A Active CN109299952B (en) | 2018-03-30 | 2018-05-18 | System and method for realizing correlated retrieval of multiple commodity codes |
| CN201810485262.XA Pending CN109299951A (en) | 2018-03-30 | 2018-05-18 | A kind of realization more than one piece commodity are mutually related method |
Family Applications After (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810485534.6A Active CN109299952B (en) | 2018-03-30 | 2018-05-18 | System and method for realizing correlated retrieval of multiple commodity codes |
| CN201810485262.XA Pending CN109299951A (en) | 2018-03-30 | 2018-05-18 | A kind of realization more than one piece commodity are mutually related method |
Country Status (1)
| Country | Link |
|---|---|
| CN (3) | CN109302376B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110490654B (en) * | 2019-08-19 | 2022-05-20 | 广州凯晟信息科技有限公司 | Film shrinking and code assigning method and device, terminal and computer storage medium |
| CN110992070B (en) * | 2019-12-26 | 2024-03-01 | 上海中商网络股份有限公司 | Commodity tracing code association method and device |
| CN115034346B (en) * | 2022-06-01 | 2023-04-07 | 浙江省标准化研究院(金砖国家标准化(浙江)研究中心、浙江省物品编码中心) | Unique product code assigning method and device based on GS1 codes and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102664933A (en) * | 2012-04-06 | 2012-09-12 | 中国联合网络通信集团有限公司 | User authorization method, application terminal, open platform and system |
| CN104104673A (en) * | 2014-06-30 | 2014-10-15 | 重庆智韬信息技术中心 | Method for realizing security payment through third party unified dynamic authorization code |
| CN105359179A (en) * | 2013-05-15 | 2016-02-24 | 维萨国际服务协会 | Mobile tokenization hub |
| CN105989491A (en) * | 2015-02-17 | 2016-10-05 | 孙宏铭 | Dynamic authorization code generation method, device, payment transaction method and system |
| CN106664300A (en) * | 2014-06-04 | 2017-05-10 | 搜诺思公司 | Cloud queue access control |
Family Cites Families (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110016052A1 (en) * | 2009-07-16 | 2011-01-20 | Scragg Ernest M | Event Tracking and Velocity Fraud Rules for Financial Transactions |
| CN102013072A (en) * | 2010-11-29 | 2011-04-13 | 吴东杰 | Over two-group associated data-based commodity anti-counterfeiting method |
| DE102011114248A1 (en) * | 2011-04-15 | 2012-10-18 | Oliver C. Mehler | Procedure for handling product information |
| CN104036397A (en) * | 2014-05-26 | 2014-09-10 | 北京五洲全景信息技术有限公司 | Internet of Things anti-counterfeiting and tracing scheme based on NFC and combination of two-dimensional code and password |
| CN104091258A (en) * | 2014-07-23 | 2014-10-08 | 湖南中财化学建材有限公司 | Dicode anti-counterfeiting anti-channel conflict method for tubular products |
| US20160125396A1 (en) * | 2014-10-29 | 2016-05-05 | Google Inc. | Confirming physical possession of plastic nfc cards with a mobile digital wallet application |
| CN105023136A (en) * | 2015-08-14 | 2015-11-04 | 深圳正品创想科技有限公司 | Two-dimensional code operating method and apparatus of commodity |
| CN105956867A (en) * | 2016-05-23 | 2016-09-21 | 无锡市鸿太阳印刷有限公司 | Anti-fake method by associating color codes of commodity and anti-fake system of anti-fake method |
| CN106897341A (en) * | 2016-07-08 | 2017-06-27 | 阿里巴巴集团控股有限公司 | 2 D code information querying method, server, client and system |
| CN106846013A (en) * | 2017-01-24 | 2017-06-13 | 浙江甲骨文超级码科技股份有限公司 | A kind of false proof identity management system and method for tracing to the source |
| CN106934439A (en) * | 2017-03-03 | 2017-07-07 | 信码互通（北京）科技有限公司 | The bottle code and the correlating method and bottle cap of case code realized based on concealed code |
| CN107146060A (en) * | 2017-05-26 | 2017-09-08 | 现代城市数据科技（深圳）有限公司 | The method for building up and its system of a kind of respiratory sensation relation of Quick Response Code and commodity |
| CN107506817B (en) * | 2017-07-13 | 2023-06-27 | 拍拍看(海南)人工智能有限公司 | Commodity virtual coding method and system based on personality patterns |
-
2018
- 2018-05-18 CN CN201810485264.9A patent/CN109302376B/en active Active
- 2018-05-18 CN CN201810485534.6A patent/CN109299952B/en active Active
- 2018-05-18 CN CN201810485262.XA patent/CN109299951A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102664933A (en) * | 2012-04-06 | 2012-09-12 | 中国联合网络通信集团有限公司 | User authorization method, application terminal, open platform and system |
| CN105359179A (en) * | 2013-05-15 | 2016-02-24 | 维萨国际服务协会 | Mobile tokenization hub |
| CN106664300A (en) * | 2014-06-04 | 2017-05-10 | 搜诺思公司 | Cloud queue access control |
| CN104104673A (en) * | 2014-06-30 | 2014-10-15 | 重庆智韬信息技术中心 | Method for realizing security payment through third party unified dynamic authorization code |
| CN105989491A (en) * | 2015-02-17 | 2016-10-05 | 孙宏铭 | Dynamic authorization code generation method, device, payment transaction method and system |
Non-Patent Citations (1)
| Title |
|---|
| API开放平台高性能技术探索与实践;赵叶红;《中国金融电脑》;20160228;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109299951A (en) | 2019-02-01 |
| CN109302376A (en) | 2019-02-01 |
| CN109299952B (en) | 2021-10-29 |
| CN109299952A (en) | 2019-02-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109302376B (en) | Account code generation method, account authorization method and account code fetching method | |
| US20050289348A1 (en) | System and method for providing security to an application | |
| CN101217367B (en) | An operation right judgment system and method realized by introducing right judgment client end | |
| US20170186117A1 (en) | License management apparatus, license management method, and license authentication program | |
| CN110602216B (en) | Method and device for using single account by multiple terminals, cloud server and storage medium | |
| CN105101196A (en) | User account management method and device | |
| CN102004866A (en) | Method and device for user identity verification and access control of information system | |
| KR101668550B1 (en) | Apparatus and Method for Allocating Role and Permission based on Password | |
| CN101395632A (en) | Management and application of entitlements | |
| CN104702415A (en) | Account number permission control method and device | |
| CN105337925A (en) | User account management method and apparatus | |
| CN101360110B (en) | Set-top box application security detecting method, apparatus and system | |
| JP5013931B2 (en) | Apparatus and method for controlling computer login | |
| CN109831435B (en) | Database operation method, system, proxy server and storage medium | |
| CN108173839B (en) | Authority management method and system | |
| JP2008299702A (en) | Information processing program and information processing system | |
| KR20140035382A (en) | Method for allowing user access, client, server, and system | |
| US8959356B2 (en) | Double authentication for controlling disruptive operations on storage resources | |
| JPWO2007077615A1 (en) | Software execution management apparatus, method and program thereof | |
| US7743412B1 (en) | Computer system identification | |
| KR20190026394A (en) | METHOD FOR ACCESS CONTROL BETWEEN IoT TERMINALS | |
| CN109063461B (en) | Third-party password-free login method and system | |
| CN112287305B (en) | Data processing method, user lock and server | |
| KR101690968B1 (en) | Method of federating internet of things platforms | |
| KR101368122B1 (en) | Method for security of computer using mobile communication terminal and computer therefor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |