A commodity state recognition method based on link access data

Abstract

The application discloses a commodity state recognition method based on link access data, relates to the technical field of electronic commerce data processing, and aims at solving the problem that the existing method is easy to confuse the target SKU originally pointed by the commodity link with the actual effective SKU of the landing page, leading to the misjudgment of the commodity state; the method acquires a commodity link to be recognized, determines the target SKU identifier corresponding to the commodity link, accesses the commodity link and acquires landing page data, determines the page effective SKU identifier according to the landing page data, compares the target SKU identifier with the page effective SKU identifier for consistency, and outputs a commodity state recognition result according to the comparison result; through the method, the situation that the target SKU is not actually effective in the landing page can be recognized, the misjudgment of the purchasable state of a non-target SKU as the target SKU state is avoided, and the commodity state recognition accuracy is improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method for identifying the status of goods based on linked access data. Background Technology

[0002] In scenarios such as e-commerce, shopping guide recommendations, advertising, price comparison monitoring, and inventory monitoring, systems typically need to access product links to determine whether a product is still valid, available for purchase, or has been removed from the shelves or sold out. Existing product status identification methods mostly determine product status based on whether the link is accessible, whether the page returns successfully, and whether the page contains information such as product title, price, inventory information, or a purchase button. For multi-specification products, the product link may also carry SKU parameters, which point to a specific color, size, capacity, version, or package. Existing methods usually combine the SKU parameter with the final landing URL to determine whether the corresponding specification is valid.

[0003] However, in actual e-commerce pages, the final landing URL still retains the target SKU parameter, which does not necessarily mean that the target SKU is actually active on the page. Some platforms will redetermine the currently selected SKU during page loading based on inventory status, default specification rules, recommended specification rules, regional inventory, or front-end initialization logic. When the target SKU corresponding to the original link is sold out, removed from the shelves, or temporarily unavailable for purchase, the page may still retain the SKU parameter, but the specification area has automatically fallen back to other available SKUs, or the purchase entry request actually submits a different SKU. In this case, the page may still display the price and purchase button, but the purchase status does not correspond to the target SKU pointed to by the original link.

[0004] Therefore, existing methods tend to equate "target SKU parameters being retained" directly with "target SKU being effective," making it difficult to identify situations where the target SKU originally pointed to by the product link is inconsistent with the actual effective SKU on the landing page. This leads to shopping guide recommendation, advertising, price comparison monitoring, and inventory monitoring systems misjudging the purchase status of non-target SKUs as the purchase status of target SKUs, resulting in inconsistent recommendation specifications, wasted ad clicks, incorrect price association, and distorted inventory status monitoring. Summary of the Invention

[0005] This application provides a product status identification method based on link access data, which is used to identify situations where the target SKU corresponding to the product link is inconsistent with the actual effective SKU on the landing page, thereby avoiding misjudging the status of a non-target SKU as the status of the original target SKU pointed to by the product link.

[0006] Firstly, this application provides a product status identification method based on link access data, which can be executed by a product status identification device. In this method, the product status identification device acquires a product link to be identified; determines a target SKU identifier corresponding to the product link, the target SKU identifier representing the target specification product originally pointed to by the product link; accesses the product link to acquire landing page data corresponding to the product link; determines a page-activated SKU identifier based on the landing page data, the page-activated SKU identifier representing the specification product currently actually pointed to or submitted by the landing page; performs a consistency comparison between the target SKU identifier and the page-activated SKU identifier; and outputs a product status identification result based on the consistency comparison result. Wherein, when the target SKU identifier and the page-activated SKU identifier are inconsistent, the product status identification result represents that the target SKU corresponding to the product link is not actually activated on the landing page.

[0007] In the above method, the product status recognition device does not determine the validity of the target SKU corresponding to the product link solely based on whether the product link is accessible or whether the landing page has a price or a buy button. Instead, it determines the target SKU identifier that the product link originally pointed to and the effective SKU identifier of the page that the landing page currently points to or submits to, and outputs the product status recognition result based on the consistency of the two. Through this scheme, it is possible to identify situations where the default SKU, recommended SKU, or other available SKUs replace the target SKU, thereby improving the accuracy of identifying the specific SKU status corresponding to the product link.

[0008] In one possible design, determining the target SKU identifier corresponding to the product link includes: extracting candidate SKU information from the query parameters, path parameters, fragment parameters, and / or link context parameters of the product link; standardizing the candidate SKU information to obtain candidate SKU identifiers; and determining the target SKU identifier from the candidate SKU identifiers based on the parameter source, parameter name priority, platform identifier, and / or a pre-stored SKU mapping table. This design allows for obtaining target SKU identifiers representing products of the original target specifications under different link formats and platform parameter naming rules.

[0009] In one possible design, the link context parameters include at least one of the following: the target SKU field passed in by the business system along with the product link, the target SKU field returned by the short link parsing service, and the target SKU field in the promotion link parsing result. With this design, when the URL parameters in the product link are insufficient to express the target SKU, the target SKU identifier can be determined by combining the context information.

[0010] In one possible design, accessing the product link and obtaining the landing page data corresponding to the product link includes: accessing the product link and recording the redirection path formed during the access process; obtaining the final landing URL after the redirection ends; executing the page script in the final landing page through the browser execution environment until the page loading completion condition is met; and obtaining at least one of the following after the page loading completion condition is met: the page document object model, page initialization data, page specification data, network interface return data, and purchase entry data, as the landing page data. This design allows for obtaining data closer to the actual page state after page script execution and asynchronous data loading.

[0011] In one possible design, the method further includes: determining whether the SKU parameter corresponding to the target SKU identifier is retained based on the redirection link and / or the final landing URL; Specifically, when the landing SKU identifier in the final landing URL is the same as the target SKU identifier, or when the landing SKU identifier and the target SKU identifier satisfy a preset mapping relationship, it is determined that the SKU parameter corresponding to the target SKU identifier is retained; This design allows for the output of SKU parameter retention results, making it easier to distinguish between two states: parameter loss and parameter retention that has not actually taken effect.

[0012] In one possible design, determining the effective SKU identifier based on the landing page data includes: identifying the selected specification node from the page specification data in the landing page data; obtaining the specification attribute value combination corresponding to the selected specification node; querying the SKU mapping table based on the specification attribute value combination to obtain the effective SKU identifier; through this design, the effective SKU identifier can be determined based on the currently selected specification combination on the landing page.

[0013] In one possible design, determining the effective SKU identifier based on the landing page data includes: extracting at least one of the currently selected SKU identifier, the default SKU identifier, and the SKU identifier to be submitted from the page initialization data, asynchronous specification interface return data, or network interface return data in the landing page data; and determining the effective SKU identifier based on at least one of the currently selected SKU identifier, the default SKU identifier, and the SKU identifier to be submitted. This design allows for the determination of the effective SKU identifier from page data or interface data when the page specification area is incomplete or cannot be directly identified.

[0014] In one possible design, determining the effective SKU identifier based on the landing page data includes: triggering or simulating the triggering of a purchase control or add-to-cart control on the landing page without submitting a real order; intercepting the purchase entry request generated by the purchase control or add-to-cart control before it is sent; extracting the SKU identifier to be submitted from at least one of the request address, request body, or request header of the purchase entry request; and determining or correcting the effective SKU identifier based on the SKU identifier to be submitted. This design allows for further determination or correction of the effective SKU identifier based on the SKU actually carried by the purchase entry.

[0015] In one possible design, the method further includes: obtaining or constructing a specification matrix based on the landing page data, the specification matrix including multiple specification combination records, each specification combination record including at least one of SKU identifier, specification attribute value set, existence status, clickable status, grayed-out status, and inventory status; querying the specification matrix based on the target SKU identifier to determine the target SKU's active status; when the specification combination record corresponding to the target SKU identifier does not exist, or the specification combination record corresponding to the target SKU identifier indicates that the target SKU is not clickable, grayed out, or has zero inventory, it is determined that the target SKU is not actually active on the landing page; through this design, the specification matrix can be used to further verify whether the target SKU still exists, is selectable, and has inventory.

[0016] In one possible design, the step of outputting the product status identification result based on the consistency comparison result includes: when the target SKU identifier matches the page-activated SKU identifier, outputting the target SKU activated status; when the target SKU identifier does not match the page-activated SKU identifier, outputting the target SKU inactive status; the product status identification result includes at least one of the following: product link, final landing URL, target SKU identifier, page-activated SKU identifier, SKU parameter retention result, page purchase availability judgment result, status code, and status reason; through this design, the output content of the identification result can be clearly defined, enabling subsequent business systems to use it directly.

[0017] Secondly, this application provides a device that includes multiple functional modules; The multiple functional modules interact to achieve the first aspect mentioned above, and the method executed by the commodity status recognition device in its various embodiments; The multiple functional modules can be implemented based on software, hardware, or a combination of software and hardware.

[0018] Thirdly, this application provides an apparatus including at least one processor and at least one memory, wherein the at least one memory stores computer program instructions, and when the apparatus is in operation, the at least one processor executes the method executed by the commodity status identification apparatus in the first aspect and its various embodiments described above.

[0019] Fourthly, this application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, causes the computer to perform the method executed by the commodity status recognition device in the first aspect and its various embodiments described above.

[0020] For the technical effects that can be achieved by the second to fourth aspects mentioned above, please refer to the description of the technical effects that can be achieved by the corresponding design scheme in the first aspect mentioned above. This application will not repeat them here. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the architecture of a commodity status recognition system provided in an embodiment of this application; Figure 2 A flowchart illustrating a product status identification method based on link access data provided in this application embodiment; Figure 3 A schematic diagram illustrating a discrepancy between the target SKU and the page-enabled SKU, provided as an embodiment of this application; Figure 4 This application provides an embodiment of a schematic diagram illustrating the determination of the effective SKU identifier of a page based on page specification data. Figure 5 This application provides an embodiment of a schematic diagram illustrating the determination or modification of the effective SKU identifier on a page based on purchase entry data. Figure 6 This is a schematic diagram of the functional module structure of a commodity status recognition device provided in an embodiment of this application; Figure 7 This is a schematic diagram of the hardware structure of a commodity status recognition device provided in an embodiment of this application. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings; wherein, in the description of the embodiments of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly indicating the number of indicated technical features.

[0023] It should be understood that in the embodiments of this application, "at least one" means one or more, "more" means two or more; "and / or" describes the relationship between the associated objects, indicating that there can be three relationships, for example, A and / or B, which can mean: A exists alone, A and B exist at the same time, or B exists alone, where A and B can be singular or plural.

[0024] In this embodiment, the product status recognition device can be a server, a cloud platform, an edge computing device, or a terminal device. The product status recognition device is used to obtain the product link to be identified, determine the target SKU identifier corresponding to the product link, and determine the page-effective SKU identifier based on the landing page data obtained by accessing the product link, thereby identifying whether the target SKU is actually effective on the landing page.

[0025] In this embodiment, the product link can be an e-commerce product detail page link, an advertising landing page link, a shopping guide link, a short link, a promotion link, or a product link with channel parameters; the target SKU identifier is used to characterize the target specification product that the product link originally points to, and can be determined by the SKU parameter in the product link, the link context parameter, or a pre-stored mapping relationship; the page-effective SKU identifier is used to characterize the specification product that the landing page currently actually points to or actually submits, and can be determined by page specification data, page initialization data, asynchronous specification interface return data, network interface return data, or purchase entry data.

[0026] Page specification data includes at least one of specification area data, page initialization data, and asynchronous specification interface return data; specification area data is used to represent specification nodes such as color, size, capacity, version, and package on the page and their selected status; SKU mapping table is used to represent the correspondence between specification attribute value combinations and SKU identifiers; SKU mapping relationship table is used to represent the equivalence or correspondence between two SKU identifiers, and the SKU mapping relationship table may include a first SKU identifier, a second SKU identifier, a mapping type, and an applicable platform identifier; purchase entry data includes at least one of the request address, request body, and request header generated by the purchase control or add-to-cart control.

[0027] The preset SKU parameter name set can be stored in the configuration file, database, or rule engine of the product status recognition device; the preset SKU parameter name set can be configured according to the platform identifier, with each platform identifier corresponding to one or more SKU parameter names; when parsing a product link, the product status recognition device can first determine the target platform based on the domain name, path, or platform identifier passed in by the business system of the product link, and then call the SKU parameter name set corresponding to the target platform.

[0028] Figure 1 This is a schematic diagram of the architecture of a commodity status recognition system provided in an embodiment of this application; see reference. Figure 1 The system may include a product status recognition device, a page access component, a product status database, and at least one business system; wherein, the page access component may be used to access product links, record redirection links, obtain the final landing URL, and obtain landing page data; the product status database may be used to store product status recognition results; the business system may include at least one of a product monitoring system, an advertising delivery system, a shopping guide system, or a price comparison system.

[0029] In this embodiment, the product status recognition device may include a link parsing module, a page access module, a page data extraction module, an SKU consistency judgment module, and a result output module. The link parsing module determines the target SKU identifier corresponding to the product link; the page access module accesses the product link through a page access component and obtains landing page data; the page data extraction module determines the effective SKU identifier from the landing page data; the SKU consistency judgment module compares the target SKU identifier with the effective SKU identifier; and the result output module generates and outputs the product status recognition result based on the consistency comparison result.

[0030] Figure 2 A flowchart illustrating a product status identification method based on link access data, provided in an embodiment of this application. (Reference) Figure 2 The method includes the following steps.

[0031] S201: The product status recognition device obtains the product link to be recognized; The product links to be identified can be sent to the product status recognition device by the product monitoring system, advertising system, shopping guide system or price comparison system, or they can be input by the user through the front-end device, or they can be obtained by the product status recognition device from the queue of product links to be detected.

[0032] In one optional implementation, the product status recognition device periodically retrieves product links to be recognized from the product link queue; in another optional implementation, the product status recognition device responds to a detection request sent by the business system and retrieves the product links carried in the detection request.

[0033] S202: The product status recognition device determines the target SKU identifier corresponding to the product link; The product status recognition device can extract candidate SKU information from the query parameters, path parameters, fragment parameters and / or link context parameters of the product link; the link context parameters may include at least one of the target SKU field passed in by the business system along with the product link, the target SKU field returned by the short link parsing service, and the target SKU field in the promotion link parsing result.

[0034] The product status recognition device can standardize candidate SKU information to obtain candidate SKU identifiers. The standardization process can include at least one of the following: URL decoding, character case unification, removal of channel prefix, removal of version suffix, removal of whitespace characters, and removal of invalid separators. For example, when the parameter value in the product link is "SKU%3AABC-001_v2", the product status recognition device can decode its URL and remove the version suffix to obtain the candidate SKU identifier "ABC-001".

[0035] refer to Figure 4 When multiple candidate SKU identifiers exist, the product status recognition device can determine the target SKU identifier from the candidate SKU identifiers based on the parameter source, parameter name priority, platform identifier, and / or a pre-stored SKU mapping table. For example, the priority of the target SKU field passed in by the business system with the product link can be higher than the target SKU field in the promotion chain parsing result, and the priority of the skuId parameter can be higher than the priority of the channelSku parameter. The pre-stored SKU mapping table can be obtained in advance by the product status recognition device from the product library, the merchant SKU library, or historical data.

[0036] When the target SKU identifier cannot be determined from the product link, link context parameters, or pre-stored SKU mapping table, the product status recognition device can output a no-target SKU status or enter the overall product status recognition process.

[0037] S203: The product status recognition device accesses the product link and obtains the landing page data corresponding to the product link; A page access component can include an HTTP access component and a browser execution environment. The HTTP access component can be used to initiate access requests and record redirection paths; the browser execution environment can be used to execute page scripts, load asynchronous interface data, and obtain data after page rendering.

[0038] The product status recognition device accesses product links through a page access component and records the redirection paths formed during the access process. These redirection paths can include at least one of the following: a shortened URL, an intermediate redirect URL, a platform-standardized URL, and a final landing URL. After the redirection is complete, the product status recognition device can obtain the final landing URL.

[0039] The product status recognition device can execute the page script in the final landing page through the browser execution environment until the page loading completion conditions are met. The page loading completion conditions may include at least one of the following: the page document object model is loaded, the specification area appears, the purchase control appears, the asynchronous specification interface returns, or the network request is idle for a preset time. After the page loading completion conditions are met, the product status recognition device obtains at least one of the following: the page document object model, page initialization data, page specification data, network interface return data, and purchase entry data, as the landing page data.

[0040] S204: The product status identification device determines the SKU parameter retention result based on the redirection link and / or the final landing URL; This step is optional; the product status identification device can determine whether the SKU parameters corresponding to the target SKU identifier are retained based on the redirection link and / or the final landing URL.

[0041] In one optional implementation, the product status recognition device can extract the landing SKU parameter value from the final landing URL and standardize the landing SKU parameter value to obtain the landing SKU identifier. When the landing SKU identifier in the final landing URL is the same as the target SKU identifier, or when the landing SKU identifier and the target SKU identifier satisfy a preset mapping relationship, the product status recognition device determines that the SKU parameter corresponding to the target SKU identifier is retained.

[0042] refer to Figure 5 The preset mapping relationship can be determined by the SKU mapping relationship table. Each mapping record in the SKU mapping relationship table may include a first SKU identifier, a second SKU identifier, a mapping type, and an applicable platform identifier. The mapping type may include at least one of the following: platform SKU to merchant SKU mapping, promotional SKU to regular SKU mapping, and SKU alias mapping.

[0043] S205: The product status recognition device determines the effective SKU identifier on the landing page based on the data from the landing page; The page-activated SKU identifier is used to represent the specification of the product that the landing page is currently pointing to or actually submitting. The product status identification device can determine the page-activated SKU identifier based on at least one of the following: page specification data, page initialization data, asynchronous specification interface return data, network interface return data, and purchase entry data.

[0044] In one optional implementation, the product status recognition device can identify a selected specification node from the page specification data in the landing page data; the selected state can be determined based on at least one of the specification node's selection style, selection attribute, control status identifier, or page script variable; for example, when a specification node has attributes or styles such as selected, active, checked, or current, it can be determined that the specification node is in a selected state.

[0045] The product status recognition device can obtain the combination of specification attribute values ​​corresponding to the selected specification node, and query the SKU mapping table based on the combination of specification attribute values ​​to obtain the page-effective SKU identifier; for example, if the selected specification nodes in the specification area are white and 128GB, and there is a record "attrs=[white,128GB],skuId=WHITE-128" in the SKU mapping table, then the product status recognition device can determine that the page-effective SKU identifier is "WHITE-128".

[0046] In another optional implementation, the product status recognition device can extract at least one of the currently selected SKU identifier, the default SKU identifier, and the SKU identifier to be submitted from the page initialization data, the asynchronous specification interface return data, or the network interface return data, and determine the page-effective SKU identifier based on at least one of the currently selected SKU identifier, the default SKU identifier, and the SKU identifier to be submitted.

[0047] In another optional implementation, the product status recognition device can trigger or simulate triggering the purchase control or add-to-cart control on the landing page without submitting a real order; intercept the purchase entry request before the purchase entry request generated by the purchase control or add-to-cart control is sent; extract the SKU identifier to be submitted from at least one of the request address, request body or request header of the purchase entry request; and determine or correct the effective SKU identifier on the page based on the SKU identifier to be submitted.

[0048] In one optional implementation, the product status recognition device can listen to web page network requests via browser debugging protocols. After triggering the purchase control, it intercepts the network request containing the purchase entry path identifier before the request is sent, and reads the request address, request body, and request header of the request. After reading, the product status recognition device can block the request from being sent further, or redirect the request to a local empty response service, thereby avoiding the generation of a real order or changes to the shopping cart data. The purchase entry path identifier may include path keywords such as addCart, cart, buy, checkout, stockCheck, and skuCheck.

[0049] S206: The product status recognition device performs a consistency comparison between the target SKU identifier and the SKU identifier that is active on the page; The product status recognition device can perform string consistency comparison, standardized consistency comparison, or mapping relationship consistency comparison between the target SKU identifier and the page-validated SKU identifier. When the target SKU identifier and the page-validated SKU identifier are the same, or the two satisfy the preset SKU mapping relationship, the product status recognition device determines that the two are consistent. When the target SKU identifier and the page-validated SKU identifier are different, and the two do not satisfy the preset SKU mapping relationship, the product status recognition device determines that the two are inconsistent.

[0050] refer to Figure 3 For example, if the target SKU identifier is BLACK-256 and the page-enabled SKU identifier is WHITE-128, and the two do not meet the preset mapping relationship, the product status recognition device determines that the target SKU identifier and the page-enabled SKU identifier are inconsistent.

[0051] S207: The product status recognition device determines the effective status of the target SKU based on the specification matrix; This step is optional; the product status recognition device can obtain or construct a specification matrix based on the landing page data; the specification matrix can include multiple specification combination records, and each specification combination record includes at least one of the following: SKU identifier, specification attribute value set, existence status, clickable status, grayed-out status, and inventory status.

[0052] When the page data contains a skuList, skuMap, or specification combination list, the product status recognition device can directly parse and obtain the specification matrix; when the page data only contains specification nodes and their linkage relationships, the product status recognition device can generate specification combination records based on the optional relationships between specification nodes, thereby constructing the specification matrix.

[0053] For example, a specification combination record can be represented as: skuId=BLACK-256, attrs=[black,256GB], exist=true, clickable=false, disabled=true, stock=0; where skuId represents the SKU identifier, attrs represents the set of specification attribute values, exist indicates whether the specification combination exists, clickable indicates whether the specification combination is clickable, disabled indicates whether the specification combination is grayed out, and stock represents the inventory quantity.

[0054] The product status recognition device can query the specification matrix based on the target SKU identifier to determine the effective status of the target SKU. When the specification combination record corresponding to the target SKU identifier does not exist, or the specification combination record corresponding to the target SKU identifier indicates that the target SKU is not clickable, grayed out, or has zero inventory, the product status recognition device determines that the target SKU is not actually effective on the landing page.

[0055] S208: The product status recognition device outputs the product status recognition result based on the consistency comparison result; When the target SKU identifier matches the valid SKU identifier on the page, the product status recognition device can output the target SKU status as valid; when the target SKU identifier does not match the valid SKU identifier on the page, the product status recognition device can output the target SKU status as invalid.

[0056] The product status identification result may include at least one of the following: product link, final landing URL, target SKU identifier, page-effective SKU identifier, SKU parameter retention result, page purchase availability judgment result, status code, and status reason; wherein, the status reason may include at least one of the following: target SKU parameter is retained but the page is actually effective for a non-target SKU, target SKU parameter is retained but the purchase entry is submitted for a non-target SKU, and target SKU is unavailable in the specification matrix.

[0057] The product status recognition device can store the product status recognition results in the product status database and / or send the product status recognition results to the product monitoring system, advertising system, shopping guide system or price comparison system. After receiving the product status recognition results, the business system can stop the delivery of product links for target SKUs that are not effective, prompt the operations staff to review, update the product inventory status, adjust the price comparison display results or trigger the re-collection process.

[0058] refer to Figure 6 It is understood that, in order to realize the function of the product status recognition device in the above embodiments, this application embodiment also provides a device; the device may include a link parsing module, a page access module, a page data extraction module, an SKU consistency judgment module, and a result output module; wherein, the link parsing module is used to execute S202; the page access module is used to execute S203; the page data extraction module is used to execute S204 to S205; the SKU consistency judgment module is used to execute S206 to S207; and the result output module is used to execute S208.

[0059] The module division in this application embodiment is illustrative and is only a logical functional division. In actual implementation, there may be other division methods. In addition, each functional module in the various embodiments of this application can be integrated into a processor, or it can exist as a separate physical entity, or two or more modules can be integrated into one module. The integrated module can be implemented in hardware or as a software functional module.

[0060] refer to Figure 7 This application also provides a device that may include at least one processor, at least one memory, and a communication interface; the at least one memory stores computer program instructions, and when the device is running, the at least one processor executes the method executed by the commodity status recognition device in any of the above embodiments; the communication interface can be used to communicate with a commodity monitoring system, an advertising system, a shopping guide system, a price comparison system, or a commodity status database.

[0061] This application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, causes the computer to perform the method executed by the commodity status recognition device in any of the above embodiments.

[0062] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application; thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A method for identifying the status of goods based on link access data, characterized in that, The method, applied to a product status recognition device, includes: Obtain the product link to be identified; Extract candidate SKU information from the query parameters, path parameters, fragment parameters and / or link context parameters of the product link; The candidate SKU information is standardized to obtain candidate SKU identifiers; The target SKU identifier is determined from the candidate SKU identifiers based on the parameter source, parameter name priority, platform identifier, and / or pre-stored SKU mapping table. The target SKU identifier is used to represent the target specification of the product that the product link originally points to; Access the product link to obtain the landing page data corresponding to the product link; The effective SKU identifier of the page is determined based on the landing page data. The effective SKU identifier of the page is used to represent the specifications of the product that the landing page is currently pointing to or actually submitting. Perform a consistency comparison between the target SKU identifier and the page-effective SKU identifier; Output the product status identification result based on the consistency comparison result; Specifically, when the target SKU identifier is inconsistent with the page-effective SKU identifier, the product status identification result is used to indicate that the target SKU corresponding to the product link is not actually effective on the landing page.

2. The method as described in claim 1, characterized in that, The standardization process includes at least one of the following: URL decoding, case-sensitive character encoding, removal of channel prefixes, removal of version suffixes, and removal of invalid separators.

3. The method as described in claim 1, characterized in that, The link context parameters include at least one of the following: the target SKU field passed in by the business system along with the product link, the target SKU field returned by the short link parsing service, and the target SKU field in the promotion link parsing result.

4. The method as described in claim 1, characterized in that, The step of accessing the product link and obtaining the landing page data corresponding to the product link includes: Access the product link and record the redirection links formed during the access process; Get the final landing URL after the redirection ends; The browser execution environment executes the page scripts in the final landing page until the page loading conditions are met. Obtain at least one of the following: the page document object model, page initialization data, page specification data, network interface return data, and purchase entry data after the page loading conditions are met, and use it as the landing page data.

5. The method as described in claim 4, characterized in that, The method further includes: Based on the redirection link and / or the final landing URL, determine whether the SKU parameter corresponding to the target SKU identifier is retained; Specifically, when the landing SKU identifier in the final landing URL is the same as the target SKU identifier, or when the landing SKU identifier and the target SKU identifier satisfy a preset mapping relationship, it is determined that the SKU parameter corresponding to the target SKU identifier is retained.

6. The method as described in claim 1, characterized in that, The step of determining the effective SKU identifier of the page based on the landing page data includes: Identify the selected specification nodes from the page specification data in the landing page data; Obtain the combination of specification attribute values ​​corresponding to the selected specification node; The SKU mapping table is queried based on the combination of the specification attribute values ​​to obtain the SKU identifier that is effective on the page; The SKU mapping table is used to represent the correspondence between specification attribute value combinations and SKU identifiers.

7. The method as described in claim 1, characterized in that, The step of determining the effective SKU identifier of the page based on the landing page data includes: Extract at least one of the following from the landing page data: page initialization data, asynchronous specification interface return data, or network interface return data: currently selected SKU identifier, default SKU identifier, and SKU identifier to be submitted; The effective SKU identifier for the page is determined based on at least one of the currently selected SKU identifier, the default SKU identifier, and the SKU identifier to be submitted.

8. The method as described in claim 1, characterized in that, The step of determining the effective SKU identifier of the page based on the landing page data includes: Without submitting a real order, trigger or simulate triggering the purchase control or add-to-cart control on the landing page; Intercept the purchase entry request before the purchase control or add-to-cart control generates the purchase entry request; Extract the SKU identifier to be submitted from at least one of the request address, request body, or request header of the purchase entry request; The effective SKU identifier of the page is determined or corrected based on the SKU identifier to be submitted.

9. The method as described in claim 1, characterized in that, The method further includes: Based on the landing page data, a specification matrix is ​​obtained or constructed. The specification matrix includes multiple specification combination records. Each specification combination record includes at least one of the following: SKU identifier, specification attribute value set, existence status, clickable status, grayed-out status, and inventory status. The target SKU status is determined by querying the specification matrix based on the target SKU identifier. When the specification combination record corresponding to the target SKU identifier does not exist, or the specification combination record corresponding to the target SKU identifier indicates that the target SKU is not clickable, is grayed out, or has zero inventory, it is determined that the target SKU is not actually effective on the landing page.

10. The method as described in claim 1, characterized in that, The step of outputting the product status identification result based on the consistency comparison result includes: When the target SKU identifier matches the page-activated SKU identifier, the target SKU activation status is output; When the target SKU identifier is inconsistent with the page-activated SKU identifier, the target SKU is not activated. The product status identification result includes at least one of the following: product link, final landing URL, target SKU identifier, page-activated SKU identifier, SKU parameter retention result, page purchaseability judgment result, status code, and status reason; The reasons for the status include at least one of the following: the target SKU parameter is retained but the page is actually active with a non-target SKU; the target SKU parameter is retained but the purchase entry is submitted with a non-target SKU; or the target SKU is unavailable in the specification matrix.

Images