WO2017114205A1 - 短链接处理方法、装置及服务器 - Google Patents
短链接处理方法、装置及服务器 Download PDFInfo
- Publication number
- WO2017114205A1 WO2017114205A1 PCT/CN2016/110699 CN2016110699W WO2017114205A1 WO 2017114205 A1 WO2017114205 A1 WO 2017114205A1 CN 2016110699 W CN2016110699 W CN 2016110699W WO 2017114205 A1 WO2017114205 A1 WO 2017114205A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- short
- link
- database
- short link
- url
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2425—Iterative querying; Query formulation based on the results of a preceding query
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9562—Bookmark management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/672—Short addresses
Definitions
- the present application relates to the field of Internet technologies, and in particular, to a short link processing method, apparatus, and server.
- Short link refers to the conversion of a long Uniform Resource Locator (URL) URL into a short URL string by means of program calculation, thereby saving the character space.
- URL Uniform Resource Locator
- the present application provides a short link processing method, apparatus, and server, to solve the problem in the prior art that if multiple short link applications are applied to the same long URL, multiple short link record information will be generated, which will result in waste of storage space; Storing short link record information in a single database and increasing the amount of memory by increasing the number of bits in the short link short code will result in limited single database access efficiency.
- a short link processing method is provided, which is applied to any server in a distributed server cluster, and includes:
- the corresponding first short link URL is obtained in the first database, and the first short link URL is sent to the requester.
- a short link processing apparatus comprising:
- a first receiving unit configured to receive, by the requesting party, an application request for a short link, where the application request includes a first long link URL;
- a first calculating unit configured to acquire, according to the first long link website address, a corresponding first database table identifier
- a first determining unit configured to determine whether the first database corresponding to the first database table identifier is within its own access range
- a first processing unit configured to: if the first database is determined to be within the scope of its own access, obtain a corresponding first short link URL in the first database, and send the first short link URL to the Requester.
- a server comprising:
- processor a memory for storing the processor executable instructions
- processor is configured to:
- the corresponding first short link URL is obtained in the first database, and the first short link URL is sent to the requester.
- the application by receiving the requesting request of the requesting party for the short link, the application
- the request includes the first long link URL, and the corresponding first database table identifier is calculated according to the first long link URL, and the first database corresponding to the first database table identifier is determined to be within the scope of the access; if the first database is determined to be accessed by itself Within the scope, the corresponding first short link URL is obtained in the first database, and the first short link URL is sent to the requester, so that the server implements the long link URL to the corresponding short in the split table mode.
- the conversion of the link URL, and the corresponding short link URL is unique and short, which enhances the horizontal expansion capability of the short link storage space and also improves the speed of short link processing.
- FIG. 1 is a schematic diagram of a short link processing scenario according to an embodiment of the present application
- FIG. 2 is a flow chart of an embodiment of a short link processing method of the present application.
- FIG. 3 is a flow chart of another embodiment of a short link processing method of the present application.
- FIG. 5 is a flowchart of another embodiment of a short link processing method according to the present application.
- FIG. 6 is a flowchart of another embodiment of a short link processing method of the present application.
- FIG. 7 is a flow chart of another embodiment of a short link processing method of the present application.
- FIG. 8 is a flowchart of another embodiment of a short link processing method of the present application.
- FIG. 9 is a hardware structural diagram of a device in which the short link processing device of the present application is located.
- Figure 10 is a block diagram of an embodiment of a short link processing apparatus of the present application.
- FIG. 11 is a block diagram of another embodiment of the short link processing apparatus of the present application.
- Figure 12 is a block diagram of another embodiment of the short link processing apparatus of the present application.
- first, second, third, etc. may be used to describe various information in this application, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
- first information may also be referred to as the second information without departing from the scope of the present application.
- second information may also be referred to as the first information.
- word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
- FIG. 1 it is a schematic diagram of a short link processing scenario according to an embodiment of the present application:
- the scenario in Figure 1 includes: a requester and a distributed server cluster.
- the requester in the scenario of Figure 1 can request an application for a short link or a short link.
- the requesting party may be a system-side device, a terminal device of an ordinary user, or a partner device.
- the terminal device of the ordinary user may include various smart phones, tablets, personal computers (PCs), and the like.
- Any of the servers in the distributed server cluster in the scenario of Figure 1 can receive the requesting or access request of the requesting party for the short link.
- a distributed server forwarding mechanism in a sub-database partitioning mode is adopted. Specifically:
- Each server is assigned access only to a qualified database. If a server receives an application request or an access request for a short link that is not within the database that it can access, the request or access request is forwarded to a server that can access the corresponding database.
- the database allocated for each server may be one or more.
- the requesting party may send an application request for a short link to any server in the distributed server cluster, where the request request carries a long URL address, and the long URL address may be an actual URL address to be converted, and the purpose is to be short
- the link server returns the corresponding short Link URL.
- the requesting party may also send an access request for the short link to any server in the distributed server cluster, where the access request carries a short link URL, and the purpose is that the server needs to obtain the corresponding long URL address according to the short link URL, and Jump to the long URL.
- the short link URL is: https://m.alipay.com/t9Yv3MZ;
- the server obtains the corresponding long URL address according to the short link URL, it can be: https://cmspromo.alipay.com/finance/fullyear.htm.
- long URL URL is defined as “long link URL” in the embodiment of the present application, and is applicable to all the following embodiments of the present application.
- FIG. 2 it is a flowchart of an embodiment of a short link processing method according to the present application.
- the method can be applied to any server in a distributed server cluster, and includes the following steps:
- Step 210 Receive an application request of the requesting party for the short link, where the application request includes the first long link URL.
- the server may request the requesting party for the short link, and the purpose of the request is that the requesting party needs to obtain the short link URL of the first long link URL.
- the application request received by the server may include a plurality of application short link request parameters.
- the application request for the short link includes the actual URL address to be converted, that is, the effective time of the first long link URL and the short link, as shown in Table 1.
- Step 220 Calculate a corresponding first database table identifier according to the first long link website address.
- the database table identifier is used to represent a unique identifier of a different physical table corresponding to the same logical table in the database. For example: 00 stands for short link 00 table, 01 stands for short link 01 table, and so on.
- the database table identifier may be 100 numbers from 00 to 99 (ie, representing 100 sub-tables), or any other character of one or more digits, used to represent the sub-table name of the short link table.
- the server may perform a corresponding calculation on the first long link URL by using a preset algorithm to obtain a corresponding first database table identifier.
- a preset algorithm is Message-Digest Algorithm 5 (MD5).
- MD5 Message-Digest Algorithm 5
- the application request includes the first database table identifier corresponding to the first long link URL, the first database table identifier may be directly obtained from the application request.
- Step 230 Determine whether the first database corresponding to the first database table identifier is within its own access range.
- the corresponding first database is 67 database.
- the server that receives the application request can access the 67 database. If it can access, the corresponding short link URL can be obtained directly in the 67 database; if it is not accessible, the received application request needs to be forwarded to Access to the 67 database server, and the server accessing the 67 database is responsible for processing the request.
- Step 240 If it is determined that the first database is within the scope of its own access, obtain a corresponding first short link URL in the first database, and send the first short link URL to the requesting party.
- the foregoing first database may include multiple data of the same short link, such as: a long link URL, a corresponding digest value, a corresponding valid time, a corresponding short link short code, and a corresponding short link URL; and may also include only corresponding The short link short code, and then the corresponding short link short code constitutes the corresponding short link URL, which can save the database storage space.
- the method further includes:
- the server If it is determined that the first database is not in the scope of its own access, forwarding the received application request to a server capable of accessing the first database, so that the server is in the first request according to the request.
- the corresponding first short link URL is obtained in the database, and the first short link URL is sent to the requester.
- the application request includes the first long link website address, and the corresponding first database table identifier is calculated according to the first long link website address, and the first database table identifier is determined. Whether the first database is within the scope of its own access; if it is determined that the first database is within its own access scope, the corresponding first short link URL is obtained in the first database, and the first short link URL is sent to the requester, so that the server In the mode of sub-library table, the conversion of the long link URL to the corresponding short link URL is realized, and the corresponding short link URL is unique and short, which enhances the horizontal expansion capability of the short link storage space and also improves the short Link processing speed.
- FIG. 3 is a flowchart of another embodiment of a short link processing method according to the present application, which may be applied to any server in a distributed server cluster, and based on the method shown in FIG. 2, in the execution step
- the following steps may be included:
- Step 310 Calculate a corresponding first digest value according to the first long link web address.
- the first digest value corresponding to the first long link URL may be calculated by using different algorithms.
- the application includes, but is not limited to, the following two algorithms:
- the first digest value corresponding to the first long link web address is calculated by using a message digest algorithm, and the first digest value is a digest value of the message digest algorithm.
- the message digest algorithm can be MD5.
- the first long link URL is:
- the MD5 digest value calculated according to the MD5 algorithm is:
- the secure hash algorithm may be a Secure Hash Algorithm (SHA1).
- Step 320 Calculate a corresponding first database table identifier according to the first digest value.
- the database table identifier is based on the algorithm that the calculated first database table identifier can be evenly distributed.
- the first summary value is the MD5 digest value.
- ASCII American Standard Code for Information Interchange
- 67 is the calculated first database table identifier, and the first database table identifier is represented by a number.
- the first database table identifier is represented by any one or more characters, and is used to represent the sub-table name of the short link table.
- the first digest value corresponding to the first long link web address and the corresponding first database table identifier are calculated by the message digest algorithm or the secure hash algorithm, thereby ensuring the short link record information corresponding to the same long link web address. It is unique and effective, avoiding the problem of repeatedly creating short links, which improves the speed of short link processing.
- FIG. 4 is a flowchart of another embodiment of a short link processing method according to the present application, which may be applied to any server in a distributed server cluster, and based on the method shown in FIG.
- Step 400 Query the first short link short code corresponding to the first digest value in the first database.
- the short link short code refers to a random character string of the agreed number of bits in the short link.
- Step 420 If it is determined whether the first short link short code is queried, and the second long link URL corresponding to the first short link short code is the same as the first long link address carried in the application request, step 420 is performed; Did not query the first short link shortcode, or the first query If the second long link URL corresponding to the short link short code is different from the first long link website carried in the application request, step 440 is performed.
- the first database may include multiple data of the same short link, such as a long link URL, a corresponding digest value, a corresponding valid time, and a corresponding short link short code.
- Step 420 Form a first short link URL according to the first short link shortcode that is queried, and send the first short link URL to the requesting party.
- Step 430 When the application request further includes the valid time of the short link, the valid time of the first short link short code is updated to the valid time included in the application request, and the process ends.
- the application does not limit the execution order of step 420 and step 430, and may be performed simultaneously or sequentially.
- Step 440 Generate a corresponding second short link short code according to the first database table identifier.
- the second short link short code is a short code of a fixed number of bits, for example: 7 bits.
- a corresponding second short link short code may be generated by using different rules.
- the generation rule may be that the first two short codes are calculated according to the first database table identifier according to an agreed algorithm, and the last five short codes, that is, Yv3MZ are random characters.
- the first database table identifier is 67
- the result is ASCII ('X')%100
- the result is 6, ASCII ('Y')%100
- the result is 7 algorithm.
- the value of X can be [8
- Y can take a random character in [9
- the selection algorithm is based on the fact that the characters can be evenly distributed, and the first database table identifier can be deduced based on the calculated characters.
- the first database table identifier is not necessarily represented by the first two digits of the shortcode, and may also be shorthand characters of any position agreed in advance.
- Step 450 If it is determined that the second short link short code is not used, then the second short link website is composed according to the second link short code, and the second short link website is sent to the requesting party.
- the corresponding second short link is generated according to the identifier of the first database table. After the code, it is also determined whether the newly generated second short link short code has been used, and if it has been used, it is necessary to regenerate a second short link short code until the newly generated second short link short code is not used. Use until now.
- Step 460 When the application request further includes the effective time of the short link, set the effective time of the second short link short code to the effective time carried by the application request.
- Step 470 Bind the second short link short code to the corresponding first long link web address, the corresponding first digest value, and the corresponding valid time, and store the data in the first database.
- step 450 The application sequence of step 450, step 460 and step 470 is not limited, and may be performed simultaneously or sequentially.
- the first short link short code corresponding to the first digest value when the first short link short code corresponding to the first digest value is queried in the first database, different processing manners may be adopted according to different results obtained by the query, in particular, the first short link short code is not queried.
- the second long link URL corresponding to the first short link short code is different from the first long link website carried in the application request, the second short link short code corresponding to the first database table identifier is further generated, and The generated second short link short code is a fixed number of bits, so that the server can generate a short link shortcode as short as possible while ensuring that the short link record information corresponding to the same long link URL is unique and effective, thereby saving Transfer the content space of the short link.
- FIG. 5 is a flowchart of another embodiment of a short link processing method according to the present application, which may be applied to any server in a distributed server cluster, and based on the method shown in any one of FIG. 2 to FIG.
- the method may further comprise the following steps:
- Step 510 Detect the effective time in the first database for each short link.
- the effective time for each short link in the first database may be periodically detected.
- Step 520 When the valid time has expired, the corresponding storage information is deleted.
- the server detects the effective time of each short link in the first database every 5 minutes, and deletes the expired short link record directly, so as to improve the effective use rate of the storage space and maintain the benign growth of the short link storage space.
- FIG. 6 is a flowchart of another embodiment of a short link processing method according to the present application, which may be applied to any server in a distributed server cluster, and based on the method shown in any one of FIG. 2 to FIG.
- the method may further comprise the following steps:
- Step 610 Receive an access request of the requesting party for the short link, where the access request includes a third short link URL.
- the server may receive an access request of the requesting party for the short link, and the purpose of the access request is that the requesting party needs to obtain the long link URL corresponding to the third short link URL.
- Step 620 Calculate a corresponding second database table identifier according to the third short link web address.
- the server may perform a corresponding calculation on the third short link URL by using a preset algorithm to obtain a corresponding second database table identifier.
- the corresponding second database table identifier may be directly obtained from the third short link web address.
- Step 630 Determine whether the second database corresponding to the second database table identifier is within the scope of its own access.
- Step 640 If it is determined that the second database is within the scope of its own access, obtain a corresponding third long link URL in the second database, and jump to the third long link URL.
- the second database may include multiple data of the same short link, such as: a long link URL, a corresponding digest value, a corresponding valid time, a corresponding short link short code, and a corresponding short link URL; It is also possible to include only the corresponding short link short code, and then the corresponding short link short code constitutes the corresponding short link website, which can save the database storage space.
- the access request includes a third short link address
- the corresponding second database table identifier is calculated according to the third short link address
- the second database table identifier is determined by the request.
- the corresponding third long link URL is obtained in the second database, and the third long link URL is redirected, so that the server is in the Branch library
- the jump of the short link URL to the corresponding long link URL is implemented, and the corresponding long link URL is unique, which improves the accuracy of the short link processing.
- FIG. 7 is a flowchart of another embodiment of a short link processing method according to the present application, which may be applied to any server in a distributed server cluster, and based on the method shown in FIG.
- the calculating, by the 620, the corresponding second database table identifier according to the third short link URL may include the following steps:
- Step 710 Extract a third short link short code from the third short link website.
- the third short link URL is https://m.alipay.com/t9Yv3MZ.
- t9Yv3MZ is the third short link shortcode.
- Step 720 Generate a corresponding second database table identifier according to the third short link short code.
- the algorithm for generating the corresponding database table identifier according to the short link short code corresponds to the algorithm for generating the corresponding short link short code according to the database table identifier.
- t9Yv3MZ is the third short link shortcode, where t9 is calculated according to some agreed algorithm, and the last five short codes, Yv3MZ, are random characters.
- the server may calculate the corresponding second database table identifier according to t9, that is, the ASCII code pair 10 for each character in t9 is used, and the corresponding second database table identifier is 76.
- the corresponding second database table identifier is generated according to the third short link short code
- the corresponding database table identifier is generated according to the short link short code.
- the algorithm corresponds to an algorithm for generating a short link short code corresponding to the database table identifier, thereby ensuring the uniqueness between the short link short code and the database table identifier.
- FIG. 8 is a flowchart of another embodiment of a short link processing method according to the present application.
- the method can be applied to any server in a distributed server cluster, and the method shown in FIG. 6 is established. If the second database is determined to be in the range of its own access, the corresponding third long link URL is obtained in the second database, and when the third long link URL is redirected, the following steps may be included:
- Step 800 Query the third short link short code in the second database.
- Step 810 Determine whether the third short link short code is queried, and the third short link short code The effective time has not expired. If the third long link URL is queried, and the valid time of the third short link short code is not expired, step 820 is performed; if the third short link short code is not queried, or the effective time of the third short link short code is already If it is due, step 830 is performed.
- Step 820 Jump to the third long link URL corresponding to the third short link short code.
- the third long link URL is
- Step 820 Jump to the specified web address.
- the specified web address may be a universal default web address.
- the present application also provides an embodiment of the short link processing apparatus.
- Embodiments of the short link processing apparatus of the present application can be applied to any of the servers in the distributed server cluster, respectively.
- the device embodiment may be implemented by software, or may be implemented by hardware or a combination of hardware and software. Taking the software implementation as an example, as a logical means, the processor of the device in which it is located reads the corresponding computer program instructions in the non-volatile memory into the memory. From a hardware level, as shown in FIG. 9, a hardware structure diagram of a device in which the short link processing device is located, except for the processor, the memory, the network interface, and the nonvolatile memory shown in FIG.
- the device in which the device is located in the embodiment may also include other hardware according to the actual function of the device.
- the terminal may include a camera, a touch screen, a communication component, etc.
- the server may include processing the packet. Forwarding chips and so on.
- the short link processing apparatus can be applied to a short link processing system, and can be used to execute the short link processing method in the foregoing embodiment.
- the apparatus includes: The first receiving unit 101, the first calculating unit 102, the first determining unit 103, and the first processing unit 104.
- the first receiving unit 101 is configured to receive an application request of the requesting party for the short link, where the application request includes the first long link URL;
- the first calculating unit 102 is configured to obtain a corresponding first database table identifier according to the first long link web address
- the first determining unit 103 is configured to determine whether the first database corresponding to the first database table identifier is within its own access range
- the first processing unit 104 is configured to: if the first database is determined to be within the scope of its own access, obtain a corresponding first short link URL in the first database, and send the first short link URL to the Requester.
- the first calculating unit 102 may include: a first calculating subunit and a second calculating subunit (not shown in FIG. 10).
- the first calculating subunit is configured to calculate a corresponding first digest value according to the first long link web address
- a second calculating subunit configured to calculate a corresponding first database table identifier according to the first digest value.
- the first calculating sub-unit is specifically configured to calculate, by using a message digest algorithm, a first digest value corresponding to the first long link web address, where the first digest value is a message digest algorithm digest value; or a secure hash algorithm is used to calculate the The first digest value corresponding to the first long link URL, where the first digest value is a secure hash algorithm digest value.
- the first database table identifier is represented by a number or a character.
- the first processing unit 103 may include: a first query subunit and a first processing subunit (not shown in FIG. 10).
- the first query subunit is configured to query, in the first database, a first short link short code corresponding to the first digest value
- the first processing sub-unit is configured to: when the first short link short code is queried, and the second long link URL corresponding to the first short link short code is queried, and the first long link carried in the application request If the URLs are the same, the first short link URL is formed according to the first short link shortcode that is queried, and the first short link URL is sent to the requester.
- the application request further includes a valid time of the short link; the first processing unit 103 may further include: an update subunit (not shown in FIG. 10).
- the update subunit is configured to update a valid time of the first short link short code to a valid time carried by the application request.
- the first processing unit 103 may further include: a generating subunit and a second processing subunit (not shown in FIG. 10).
- the generating subunit is configured to: if the first short link short code is not queried, or the second long link web address corresponding to the first short link short code that is queried, and the first long carried in the application request If the link URL is different, generating a corresponding second short link short code according to the first database table identifier;
- the second processing subunit is configured to, if it is determined that the second short link short code is not used, form a second short link website according to the second link short code, and send the second short link website to the The requesting party.
- the application request further includes a valid time of the short link; the first processing unit 103 may further include: setting a subunit (not shown in FIG. 10).
- the setting subunit is configured to set an effective time of the second short link short code to a valid time carried by the application request.
- the first processing unit 103 may further include: a storage subunit (not shown in FIG. 10).
- the storage subunit is configured to bind the second short link short code to the corresponding first long link URL, the corresponding first digest value, and the corresponding valid time, and store the same in the first database.
- the short link processing device further includes: a second processing unit (not shown in FIG. 10).
- the second processing unit is configured to: if it is determined that the first database is not in its own access scope, forward the application request to a server that can access the first database, so that the server requests the Obtaining a corresponding first short link URL in the first database, and sending the first short link URL to the requester.
- FIG. 11 is a block diagram of another embodiment of a short link processing apparatus of the present application.
- the short link processing apparatus may be applied to a short link processing system and is based on the apparatus shown in FIG. 10, and the apparatus may further include: The detecting unit 111 and the deleting unit 112.
- the detecting unit 111 is configured to detect a valid time in the first database for each short link.
- the deleting unit 112 is configured to delete the corresponding storage information when the valid time has expired.
- FIG. 12 it is a block diagram of another embodiment of a short link processing apparatus of the present application.
- the short link processing apparatus can be applied to a short link processing system, and can be used to perform the apparatus shown in FIG.
- the second receiving unit 121, the second calculating unit 122, the second determining unit 123, and the second processing unit 124 are included.
- the second receiving unit 121 is configured to receive, by the requesting party, an access request for a short link, where the access request includes a third short link URL;
- the second calculating unit 122 is configured to calculate a corresponding second database table identifier according to the third short link web address
- the second determining unit 123 is configured to determine whether the second database corresponding to the second database table identifier is within the scope of its own access;
- the third processing unit 124 is configured to: if it is determined that the second database is within its own access range, obtain a corresponding third long link website address in the second database, and jump to the third long link website address.
- the second computing unit 122 may include: an extracting subunit and a generating subunit (not shown in FIG. 12).
- the extracting subunit is configured to extract a third short link short code from the third short link web address
- the generating subunit is configured to generate a corresponding second database table identifier according to the third short link short code.
- the second processing unit 123 may include: a query subunit and a third processing subunit (not shown in FIG. 12).
- the query subunit is configured to query the third short link short code in the second database
- the third processing subunit is configured to: if the third short link short code is queried, and the valid time of the third short link short code is not expired, jump to the third short link short code corresponding to the first Three long link URLs.
- the third processing unit 123 may further include: a fourth processing subunit (not shown in FIG. 12).
- the fourth processing subunit is configured to jump to the specified web address if the third short link short code is not queried, or the valid time of the third short link short code has expired.
- the short link processing device may further include: a fourth processing unit (not shown in FIG. 12).
- the fourth processing unit is configured to forward the access request to a server capable of accessing the first database, so that the server is in accordance with the access request, if it is determined that the second database is not in its own access scope. Obtaining a corresponding third short link URL in the second database, and jumping to the third long link URL.
- the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
- the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present solution. Those of ordinary skill in the art can understand and implement without any creative effort.
- the embodiment of the present application further provides a server, where the server includes:
- processor a memory for storing the processor executable instructions
- processor is configured to:
- the request request including the first long link Website
- the corresponding first short link URL is obtained in the first database, and the first short link URL is sent to the requester.
- the application request includes the first long link website address, and the corresponding first database table identifier is calculated according to the first long link website address, and the first database table identifier is determined. Whether the first database is within the scope of its own access; if it is determined that the first database is within its own access scope, the corresponding first short link URL is obtained in the first database, and the first short link URL is sent to the requester, so that the server In the mode of sub-library table, the conversion of the long link URL to the corresponding short link URL is realized, and the corresponding short link URL is unique and short, which enhances the horizontal expansion capability of the short link storage space and also improves the short Link processing speed.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Computational Linguistics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims (33)
- 一种短链接处理方法,其特征在于,所述方法应用于分布式服务器集群中的任一服务器上,包括:接收请求方针对短链接的申请请求,所述申请请求包括第一长链接网址;根据所述第一长链接网址计算对应的第一数据库表标识;判断所述第一数据库表标识对应的第一数据库是否在自身访问范围内;若确定所述第一数据库在自身访问范围内,则在所述第一数据库中获取对应的第一短链接网址,并将所述第一短链接网址发送至所述请求方。
- 根据权利要求1所述的方法,其特征在于,所述根据所述第一长链接网址计算对应的第一数据库表标识,包括:根据所述第一长链接网址计算对应的第一摘要值;根据所述第一摘要值计算对应的第一数据库表标识。
- 根据权利要求2所述的方法,其特征在于,所述根据所述第一长链接网址计算对应的第一摘要值,包括:采用消息摘要算法计算所述第一长链接网址对应的第一摘要值,所述第一摘要值为消息摘要算法摘要值;或采用安全哈希算法计算所述第一长链接网址对应的第一摘要值,所述第一摘要值为安全哈希算法摘要值。
- 根据权利要求2所述的方法,其特征在于,所述第一数据库表标识的表现形式为数字或字符。
- 根据权利要求2所述的方法,其特征在于,所述在所述第一数据库中获取对应的第一短链接网址,并将所述第一短链接网址发送至所述请求方,包括:在所述第一数据库中查询所述第一摘要值对应的第一短链接简码;若查询到所述第一短链接简码,且查询到的所述第一短链接简码对应的第二长链接网址与所述申请请求中携带的第一长链接网址相同,则根据所查询到的第一短链接简码组成第一短链接网址,并将所述第一短链接网址发送至所述请求方。
- 根据权利要求5所述的方法,其特征在于,所述申请请求还包括短链接的有效时间;所述方法还包括:将所述第一短链接简码的有效时间更新为所述申请请求携带的有效时间。
- 根据权利要求5所述的方法,其特征在于,所述在所述第一数据库中获取对应的第一短链接网址,并将所述第一短链接网址发送至所述请求方,还包括:若没有查询到所述第一短链接简码,或查询到的所述第一短链接简码对应的第二长链接网址与所述申请请求中携带的第一长链接网址不同,则根据所述第一数据库表标识生成对应的第二短链接简码;若确定所述第二短链接简码未被使用时,则根据所述第二链接简码组成第二短链接网址,并将所述第二短链接网址发送至所述请求方。
- 根据权利要求7所述的方法,其特征在于,所述申请请求还包括短链接的有效时间;所述方法还包括:将所述第二短链接简码的有效时间设置为所述申请请求携带的有效时间。
- 根据权利要求7所述的方法,其特征在于,所述方法还包括:将所述第二短链接简码与对应的第一长链接网址、对应的第一摘要值、对应的有效时间进行绑定,并存储在所述第一数据库中。
- 根据权利要求1所述的方法,其特征在于,所述判断所述第一数据库表标识对应的第一数据库是否在自身访问范围内之后,包括:若确定所述第一数据库不在自身访问范围内,则将所述申请请求转发至能够访问所述第一数据库的服务器,以使该服务器根据所述申请请求在所述第一数据库中获取对应的第一短链接网址,并将所述第一短链 接网址发送至所述请求方。
- 根据权利要求1至10任一项所述的方法,其特征在于,所述方法还包括:检测所述第一数据库中针对各个短链接的有效时间;当所述有效时间已经到期时,删除对应的存储信息。
- 根据权利要求1至10任一项所述的方法,其特征在于,所述方法还包括:接收所述请求方针对短链接的访问请求,所述访问请求包括第三短链接网址;根据所述第三短链接网址计算对应的第二数据库表标识;判断所述第二数据库表标识对应的第二数据库是否在自身访问范围内;若确定所述第二数据库在自身访问范围内,则在所述第二数据库中获取对应的第三长链接网址,并跳转至所述第三长链接网址。
- 根据权利要求12所述的方法,其特征在于,所述根据所述第三短链接网址计算对应的第二数据库表标识,包括:从所述第三短链接网址中提取第三短链接简码;根据所述第三短链接简码生成对应的第二数据库表标识。
- 根据权利要求13所述的方法,其特征在于,所述在所述第二数据库中获取对应的第三长链接网址,并跳转至所述第三长链接网址,包括:在所述第二数据库中查询所述第三短链接简码;若查询到所述第三短链接简码,且所述第三短链接简码的有效时间没有到期,则跳转至所述第三短链接简码对应的第三长链接网址。
- 根据权利要求14所述的方法,其特征在于,所述在所述第二数据库表标识对应的第二数据库中获取对应的第三长链接网址,并跳转至所述第三长链接网址,还包括:若没有查询到所述第三短链接简码,或查询到的所述第三短链接简码的有效时间已经到期,则跳转至指定网址。
- 根据权利要求12所述的方法,其特征在于,所述判断所述第二数据库表标识对应的第二数据库是否在自身访问范围内之后,包括:若确定所述第二数据库不在自身访问范围内,则将所述访问请求转发至能够访问所述第一数据库的服务器,以使该服务器根据所述访问请求在所述第二数据库中获取对应的第三短链接网址,并跳转至所述第三长链接网址。
- 一种短链接处理装置,其特征在于,所述装置应用于分布式服务器集群中的任一服务器上,包括:第一接收单元,用于接收请求方针对短链接的申请请求,所述申请请求包括第一长链接网址;第一计算单元,用于根据所述第一长链接网址获取对应的第一数据库表标识;第一判断单元,用于判断所述第一数据库表标识对应的第一数据库是否在自身访问范围内;第一处理单元,用于若确定所述第一数据库在自身访问范围内,则在所述第一数据库中获取对应的第一短链接网址,并将所述第一短链接网址发送至所述请求方。
- 根据权利要求17所述的装置,其特征在于,所述第一计算单元包括:第一计算子单元,用于根据所述第一长链接网址计算对应的第一摘要值;第二计算子单元,用于根据所述第一摘要值计算对应的第一数据库表标识。
- 根据权利要求18所述的装置,其特征在于,所述第一计算子单元具体用于采用消息摘要算法计算所述第一长链接网址对应的第一摘要值,所述第一摘要值为消息摘要算法摘要值;或采用安全哈希算法 计算所述第一长链接网址对应的第一摘要值,所述第一摘要值为安全哈希算法摘要值。
- 根据权利要求18所述的装置,其特征在于,所述第一数据库表标识的表现形式为数字或字符。
- 根据权利要求18所述的装置,其特征在于,所述第一处理单元包括:第一查询子单元,用于在所述第一数据库中查询所述第一摘要值对应的第一短链接简码;第一处理子单元,用于若查询到所述第一短链接简码,且查询到的所述第一短链接简码对应的第二长链接网址与所述申请请求中携带的第一长链接网址相同,则根据所查询到的第一短链接简码组成第一短链接网址,并将所述第一短链接网址发送至所述请求方。
- 根据权利要求21所述的装置,其特征在于,所述申请请求还包括短链接的有效时间;所述第一处理单元还包括:更新子单元,用于将所述第一短链接简码的有效时间更新为所述申请请求携带的有效时间。
- 根据权利要求21所述的装置,其特征在于,所述第一处理单元还包括:生成子单元,用于若没有查询到所述第一短链接简码,或查询到的所述第一短链接简码对应的第二长链接网址与所述申请请求中携带的第一长链接网址不同,则根据所述第一数据库表标识生成对应的第二短链接简码;第二处理子单元,用于若确定所述第二短链接简码未被使用时,则根据所述第二链接简码组成第二短链接网址,并将所述第二短链接网址发送至所述请求方。
- 根据权利要求23所述的装置,其特征在于,所述申请请求还包括短链接的有效时间;所述第一处理单元还包括:设置子单元,用于将所述第二短链接简码的有效时间设置为所述申 请请求携带的有效时间。
- 根据权利要求23所述的装置,其特征在于,所述第一处理单元还包括:存储子单元,用于将所述第二短链接简码与对应的第一长链接网址、对应的第一摘要值、对应的有效时间进行绑定,并存储在所述第一数据库中。
- 根据权利要求17所述的装置,其特征在于,所述装置还包括:第二处理单元,用于若确定所述第一数据库不在自身访问范围内,则将所述申请请求转发至能够访问所述第一数据库的服务器,以使该服务器根据所述申请请求在所述第一数据库中获取对应的第一短链接网址,并将所述第一短链接网址发送至所述请求方。
- 根据权利要求17至26任一项所述的装置,其特征在于,所述装置还包括:检测单元,用于检测所述第一数据库中针对各个短链接的有效时间;删除单元,用于当所述有效时间已经到期时,删除对应的存储信息。
- 根据权利要求17至26任一项所述的装置,其特征在于,所述装置还包括:第二接收单元,用于接收所述请求方针对短链接的访问请求,所述访问请求包括第三短链接网址;第二计算单元,用于根据所述第三短链接网址计算对应的第二数据库表标识;第二判断单元,用于判断所述第二数据库表标识对应的第二数据库是否在自身访问范围内;第三处理单元,用于若确定所述第二数据库在自身访问范围内,则在所述第二数据库中获取对应的第三长链接网址,并跳转至所述第三长链接网址。
- 根据权利要求28所述的装置,其特征在于,所述第二计算单 元包括:提取子单元,用于从所述第三短链接网址中提取第三短链接简码;生成子单元,用于根据所述第三短链接简码生成对应的第二数据库表标识。
- 根据权利要求29所述的装置,其特征在于,所述第三处理单元包括:查询子单元,用于在所述第二数据库中查询所述第三短链接简码;第三处理子单元,用于若查询到所述第三短链接简码,且所述第三短链接简码的有效时间没有到期,则跳转至所述第三短链接简码对应的第三长链接网址。
- 根据权利要求30所述的装置,其特征在于,所述第三处理单元还包括:第四处理子单元,用于若没有查询到所述第三短链接简码,或查询到的所述第三短链接简码的有效时间已经到期,则跳转至指定网址。
- 根据权利要求28所述的装置,其特征在于,所述装置还包括:第四处理单元,用于若确定所述第二数据库不在自身访问范围内,则将所述访问请求转发至能够访问所述第一数据库的服务器,以使该服务器根据所述访问请求在所述第二数据库中获取对应的第三短链接网址,并跳转至所述第三长链接网址。
- 一种服务器,其特征在于,所述服务器为分布式服务器集群中的任一服务器,包括:处理器;用于存储所述处理器可执行指令的存储器;其中,所述处理器被配置为:接收请求方针对短链接的申请请求,所述申请请求包括第一长链接网址;根据所述第一长链接网址计算对应的第一数据库表标识;判断所述第一数据库表标识对应的第一数据库是否在自身访问范 围内;若确定所述第一数据库在自身访问范围内,则在所述第一数据库中获取对应的第一短链接网址,并将所述第一短链接网址发送至所述请求方。
Priority Applications (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2016382908A AU2016382908B2 (en) | 2015-12-30 | 2016-12-19 | Short link processing method, device and server |
JP2018534847A JP6643760B2 (ja) | 2015-12-30 | 2016-12-19 | ショートリンクの処理方法、デバイス、及びサーバ |
KR1020187021982A KR102133951B1 (ko) | 2015-12-30 | 2016-12-19 | 짧은 링크 처리 방법, 디바이스, 및 서버 |
SG11201805624UA SG11201805624UA (en) | 2015-12-30 | 2016-12-19 | Short link processing method, device and server |
EP16880994.5A EP3399434B1 (en) | 2015-12-30 | 2016-12-19 | Short link processing method, device and server |
US16/019,228 US10789321B2 (en) | 2015-12-30 | 2018-06-26 | Short link processing to improve service efficiency |
PH12018501403A PH12018501403B1 (en) | 2015-12-30 | 2018-06-29 | Short link processing method, device and server |
US16/833,021 US10789322B2 (en) | 2015-12-30 | 2020-03-27 | Short link processing to improve service efficiency |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201511021330.XA CN106933854B (zh) | 2015-12-30 | 2015-12-30 | 短链接处理方法、装置及服务器 |
CN201511021330.X | 2015-12-30 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/019,228 Continuation US10789321B2 (en) | 2015-12-30 | 2018-06-26 | Short link processing to improve service efficiency |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017114205A1 true WO2017114205A1 (zh) | 2017-07-06 |
Family
ID=59225612
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2016/110699 WO2017114205A1 (zh) | 2015-12-30 | 2016-12-19 | 短链接处理方法、装置及服务器 |
Country Status (10)
Country | Link |
---|---|
US (2) | US10789321B2 (zh) |
EP (1) | EP3399434B1 (zh) |
JP (1) | JP6643760B2 (zh) |
KR (1) | KR102133951B1 (zh) |
CN (1) | CN106933854B (zh) |
AU (1) | AU2016382908B2 (zh) |
MY (1) | MY178181A (zh) |
PH (1) | PH12018501403B1 (zh) |
SG (1) | SG11201805624UA (zh) |
WO (1) | WO2017114205A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108334569A (zh) * | 2018-01-16 | 2018-07-27 | 中国平安人寿保险股份有限公司 | 基于短链接的保险投保方法、系统、设备及存储介质 |
Families Citing this family (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106933854B (zh) | 2015-12-30 | 2020-06-30 | 阿里巴巴集团控股有限公司 | 短链接处理方法、装置及服务器 |
CN106933871B (zh) * | 2015-12-30 | 2021-08-17 | 创新先进技术有限公司 | 短链接处理方法、装置及短链接服务器 |
DE112016006813T5 (de) * | 2016-07-01 | 2019-01-10 | Intel IP Corporation | Kommunikation in internet-of-things-vorrichtungen |
US10678817B2 (en) * | 2017-02-03 | 2020-06-09 | DataJaguar, Inc | Systems and methods of scalable distributed databases |
CN107733972B (zh) | 2017-08-28 | 2020-09-08 | 阿里巴巴集团控股有限公司 | 一种短链接解析方法、装置及设备 |
CN107749861A (zh) * | 2017-11-16 | 2018-03-02 | 平安科技(深圳)有限公司 | 信息推送方法、装置、终端设备及存储介质 |
CN111352927B (zh) * | 2018-12-24 | 2023-10-03 | 北京嘀嘀无限科技发展有限公司 | 短域名管理方法、装置、服务器及可读存储介质 |
CN109918586A (zh) * | 2019-01-21 | 2019-06-21 | 广东万丈金数信息技术股份有限公司 | 短链接跳转方法、装置、短链接服务器和存储介质 |
CN110147507A (zh) * | 2019-04-08 | 2019-08-20 | 深圳市物联天下技术有限公司 | 一种获取短链接地址的方法、装置及服务器 |
CN110113384A (zh) * | 2019-04-15 | 2019-08-09 | 深圳壹账通智能科技有限公司 | 网络请求处理方法、装置、计算机设备和存储介质 |
CN110113390A (zh) * | 2019-04-17 | 2019-08-09 | 深圳壹账通智能科技有限公司 | 网络请求处理方法、装置、计算机设备和存储介质 |
CN110134889B (zh) * | 2019-04-30 | 2021-08-10 | 中国联合网络通信集团有限公司 | 短链接生成方法、装置及服务器 |
CN111026985A (zh) * | 2019-12-02 | 2020-04-17 | 北京齐尔布莱特科技有限公司 | 一种短链接生成方法、装置和服务器 |
CN111047413B (zh) * | 2019-12-17 | 2023-11-07 | 秒针信息技术有限公司 | 发文内容获取方法、装置、计算机设备和可读存储介质 |
CN113111275A (zh) * | 2020-01-13 | 2021-07-13 | 北京沃东天骏信息技术有限公司 | 短网址生成的方法、装置、电子设备和存储介质 |
CN111225242A (zh) * | 2020-01-17 | 2020-06-02 | 广州酷狗计算机科技有限公司 | 视频播放容灾方法、装置及计算机存储介质 |
CN113254813B (zh) * | 2020-02-13 | 2023-07-18 | 多点(深圳)数字科技有限公司 | 一种短链接生成方法、装置、服务器和计算机可读介质 |
US11556504B2 (en) * | 2020-03-27 | 2023-01-17 | Citrix Systems, Inc. | File sharing service controller |
EP3929773B1 (en) * | 2020-06-26 | 2024-08-28 | RadiateCapital Ltd | Method and system for automatic customisation of uniform resource locators (url) by extracting a url or a content containing one or more urls and replacing with one or more customized urls |
CN112380464B (zh) * | 2020-11-10 | 2023-07-28 | 中国平安人寿保险股份有限公司 | 一种短链接生成方法以及相关设备 |
CN114692027B (zh) * | 2020-12-29 | 2024-09-20 | 福建天泉教育科技有限公司 | 一种将短链接还原成长链接的方法与终端 |
CN113378083B (zh) * | 2021-05-19 | 2023-09-29 | 北京沃东天骏信息技术有限公司 | 一种短链接生成方法、装置、设备及存储介质 |
CN113420238A (zh) * | 2021-06-18 | 2021-09-21 | 浙江集享电子商务有限公司 | 短链接生成方法、装置、电子装置和存储介质 |
CN113612869B (zh) * | 2021-08-25 | 2023-12-19 | 福建凯米网络科技有限公司 | 一种短网址生成方法、终端及存储介质 |
CN116701792B (zh) * | 2023-08-03 | 2023-11-24 | 阿里健康科技(中国)有限公司 | 目标界面的访问方法、装置、设备和存储介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040260722A1 (en) * | 2000-04-27 | 2004-12-23 | Microsoft Corporation | Web address converter for dynamic web pages |
US20090210556A1 (en) * | 2005-05-31 | 2009-08-20 | Access Co., Ltd | Time division address management device and time division routing information management device |
CN101827040A (zh) * | 2009-03-05 | 2010-09-08 | 冲电气网络株式会社 | 信息转换装置、信息转换方法、信息转换程序及中继装置 |
CN104915347A (zh) * | 2014-03-11 | 2015-09-16 | 腾讯科技(北京)有限公司 | 网页地址的处理方法、装置及系统 |
Family Cites Families (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2346231A1 (en) * | 2000-05-08 | 2001-11-08 | Internet Number Corporation | Method and system for accessing information on a network using message aliasing functions having shadow callback functions |
US6957224B1 (en) * | 2000-09-11 | 2005-10-18 | International Business Machines Corporation | Efficient retrieval of uniform resource locators |
JP2003141002A (ja) * | 2001-10-29 | 2003-05-16 | Nec Corp | Url長変換システム及びそのプログラム |
JP2007041632A (ja) * | 2005-07-29 | 2007-02-15 | Fujitsu Ltd | コンテンツアクセス方法および振分装置 |
US8255480B2 (en) * | 2005-11-30 | 2012-08-28 | At&T Intellectual Property I, L.P. | Substitute uniform resource locator (URL) generation |
JP4881651B2 (ja) * | 2006-05-08 | 2012-02-22 | ヤフー株式会社 | 二次元コード生成プログラム、二次元コード生成システムおよび二次元コード生成方法 |
US8281232B2 (en) * | 2010-04-22 | 2012-10-02 | Rockmelt, Inc. | Integrated adaptive URL-shortening functionality |
US8630200B2 (en) * | 2010-06-01 | 2014-01-14 | Meltwater News International Holdings, GmbH | Method and apparatus for embedding information in a short URL |
US9449175B2 (en) * | 2010-06-03 | 2016-09-20 | Nokia Technologies Oy | Method and apparatus for analyzing and detecting malicious software |
CN102402558A (zh) * | 2010-09-16 | 2012-04-04 | 腾讯科技(深圳)有限公司 | 一种提供包含网页地址的消息的方法和系统 |
JP5220141B2 (ja) * | 2011-02-08 | 2013-06-26 | ヤフー株式会社 | Url短縮装置、短縮url処理装置、方法及びプログラム |
JP5640811B2 (ja) * | 2011-02-24 | 2014-12-17 | 大日本印刷株式会社 | データ通信システム、url生成サーバ及びデータ通信プログラム |
US8499099B1 (en) * | 2011-03-29 | 2013-07-30 | Google Inc. | Converting data into addresses |
CN102810089B (zh) * | 2011-05-30 | 2017-07-04 | 盛乐信息技术(上海)有限公司 | 基于内容的短链接系统及实现方法 |
US8812737B2 (en) | 2011-09-19 | 2014-08-19 | Google Inc. | Context-specific unicode characters in shortened URLs |
CN103246659B (zh) * | 2012-02-06 | 2016-05-25 | 阿里巴巴集团控股有限公司 | 键值数据查询的方法和装置 |
US9282424B2 (en) * | 2012-07-12 | 2016-03-08 | Turner Broadcasting System, Inc. | Method and system for logic-based uniform resource locator resolution |
US9210229B2 (en) | 2012-10-15 | 2015-12-08 | Exacttarget, Inc. | System and method for generating personalized short links and monitoring activity |
KR20140093491A (ko) * | 2013-01-18 | 2014-07-28 | 정양원 | 단축 url의 관리 방법, 관리 장치 및 그 관리를 수행하는 컴퓨터 프로그램을 저장한 저장 매체 |
CN104104649B (zh) * | 2013-04-02 | 2017-09-19 | 阿里巴巴集团控股有限公司 | 页面登录的方法、装置及系统 |
JP2015076698A (ja) * | 2013-10-08 | 2015-04-20 | シャープ株式会社 | 画像処理装置並びに画像形成装置、画像読取装置及び画像形成システム |
CN104601736B (zh) * | 2013-10-30 | 2018-10-23 | 腾讯科技(深圳)有限公司 | 一种短url服务的实现方法及装置 |
CN106933854B (zh) | 2015-12-30 | 2020-06-30 | 阿里巴巴集团控股有限公司 | 短链接处理方法、装置及服务器 |
-
2015
- 2015-12-30 CN CN201511021330.XA patent/CN106933854B/zh active Active
-
2016
- 2016-12-19 EP EP16880994.5A patent/EP3399434B1/en active Active
- 2016-12-19 AU AU2016382908A patent/AU2016382908B2/en active Active
- 2016-12-19 SG SG11201805624UA patent/SG11201805624UA/en unknown
- 2016-12-19 JP JP2018534847A patent/JP6643760B2/ja active Active
- 2016-12-19 KR KR1020187021982A patent/KR102133951B1/ko active IP Right Grant
- 2016-12-19 WO PCT/CN2016/110699 patent/WO2017114205A1/zh active Application Filing
- 2016-12-19 MY MYPI2018001214A patent/MY178181A/en unknown
-
2018
- 2018-06-26 US US16/019,228 patent/US10789321B2/en active Active
- 2018-06-29 PH PH12018501403A patent/PH12018501403B1/en unknown
-
2020
- 2020-03-27 US US16/833,021 patent/US10789322B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040260722A1 (en) * | 2000-04-27 | 2004-12-23 | Microsoft Corporation | Web address converter for dynamic web pages |
US20090210556A1 (en) * | 2005-05-31 | 2009-08-20 | Access Co., Ltd | Time division address management device and time division routing information management device |
CN101827040A (zh) * | 2009-03-05 | 2010-09-08 | 冲电气网络株式会社 | 信息转换装置、信息转换方法、信息转换程序及中继装置 |
CN104915347A (zh) * | 2014-03-11 | 2015-09-16 | 腾讯科技(北京)有限公司 | 网页地址的处理方法、装置及系统 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3399434A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108334569A (zh) * | 2018-01-16 | 2018-07-27 | 中国平安人寿保险股份有限公司 | 基于短链接的保险投保方法、系统、设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
PH12018501403A1 (en) | 2019-03-25 |
AU2016382908A1 (en) | 2018-07-19 |
JP6643760B2 (ja) | 2020-02-12 |
EP3399434B1 (en) | 2021-05-26 |
US20180307773A1 (en) | 2018-10-25 |
CN106933854A (zh) | 2017-07-07 |
JP2019504412A (ja) | 2019-02-14 |
KR102133951B1 (ko) | 2020-07-15 |
EP3399434A1 (en) | 2018-11-07 |
PH12018501403B1 (en) | 2019-03-25 |
AU2016382908B2 (en) | 2019-09-12 |
MY178181A (en) | 2020-10-06 |
KR20180100169A (ko) | 2018-09-07 |
US10789322B2 (en) | 2020-09-29 |
CN106933854B (zh) | 2020-06-30 |
US10789321B2 (en) | 2020-09-29 |
US20200226194A1 (en) | 2020-07-16 |
SG11201805624UA (en) | 2018-07-30 |
EP3399434A4 (en) | 2018-11-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017114205A1 (zh) | 短链接处理方法、装置及服务器 | |
WO2017114206A1 (zh) | 短链接处理方法、装置及短链接服务器 | |
WO2018099107A1 (zh) | 一种哈希表管理的方法和装置、计算机存储介质 | |
TWI717866B (zh) | 跨鏈存證方法及接取方法、裝置、電子設備 | |
US9148332B2 (en) | Content delivery network | |
JP6514699B2 (ja) | リソースへの繰返しアクセスについてリソースオーナーから認可を要求する要求のバッチ処理の、サードパーティによる実行の容易化 | |
WO2017092351A1 (zh) | 缓存数据的更新方法及装置 | |
WO2016023357A1 (zh) | 访问网页的方法、装置及路由器 | |
US10693858B2 (en) | CDN-based access control method and related device | |
EP2698730B1 (en) | Data acquisition method, device and system | |
WO2017000439A1 (zh) | 一种恶意行为的检测方法、系统、设备及计算机存储介质 | |
RU2005124131A (ru) | Устройство обработки информации, способ управления содержанием, способ управления информацией содержания и компьютерная программа | |
TW201510761A (zh) | 下載以及安裝客戶端的方法和設備 | |
EP3716580A1 (en) | Cloud file transfers using cloud file descriptors | |
WO2014015808A1 (zh) | 推送信息的方法和装置 | |
EP3217611A1 (en) | Media resource feedback method and device | |
EP2991280A1 (en) | Content sharing method and social synchronizing apparatus | |
US20170155712A1 (en) | Method and device for updating cache data | |
CN102164309B (zh) | 节目的处理方法和系统以及装置 | |
WO2019196225A1 (zh) | 一种反馈资源文件的方法和装置 | |
US9503420B2 (en) | Logical network separation method and apparatus | |
CN111147235A (zh) | 对象访问方法、装置、电子设备及机器可读存储介质 | |
TW201533593A (zh) | 對網路位址進行處理的方法及相關的伺服器與非暫態電腦可讀取儲存媒體 | |
TWI496014B (zh) | Decentralized cache object removal method, system and delete server | |
CN113032820A (zh) | 文件存储方法、访问方法、装置、设备及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16880994 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 12018501403 Country of ref document: PH |
|
ENP | Entry into the national phase |
Ref document number: 2018534847 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11201805624U Country of ref document: SG |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2016382908 Country of ref document: AU Date of ref document: 20161219 Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 20187021982 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2016880994 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2016880994 Country of ref document: EP Effective date: 20180730 |