Logistics information management system and method
By unifying and displaying parcel data from different platforms through a logistics information management system, the cumbersome problem of users switching between multiple platforms to query parcel logistics information is solved, improving query efficiency and user experience.
Patent Information
- Application Number
- CN202511416933.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-09-29
- Publication Date
- 2026-02-17
AI Technical Summary
Users need to frequently switch between different e-commerce and logistics platforms to check scattered package logistics information, which is cumbersome and inefficient.
A logistics information management system is provided, including a server and a client. The system obtains raw logistics data through package import requests, performs structured processing to generate structured logistics data, and generates a logistics information display list based on category tags. Users can intuitively view package logistics information from different platforms on the interactive page.
It enables unified management and display of package data scattered across various platforms, improving user experience, reducing the number of platform switching times, and increasing query efficiency.
Smart Images

Figure CN121544150A_ABST
Abstract
Description
Technical Field
[0001] The embodiments in this specification relate to the field of computer technology, and in particular to logistics information management systems and methods. Background Technology
[0002] With the development of internet technology, online shopping has become a common consumption model, allowing users to shop on various e-commerce platforms. Correspondingly, the goods purchased can be shipped by different logistics service providers. Alternatively, users can send packages themselves through various logistics platforms. However, to obtain logistics information for these scattered packages, users need to switch between different e-commerce platforms or logistics platforms for individual tracking, which is cumbersome, inefficient, and consumes a significant amount of user time and energy. Therefore, an effective solution is urgently needed to address these problems. Summary of the Invention
[0003] In view of this, embodiments of this specification provide a logistics information management system. One or more embodiments of this specification also relate to a logistics information management method, a logistics information management device, a computing device, a computer-readable storage medium, and a computer program product, to address the technical deficiencies existing in the prior art.
[0004] According to a first aspect of the embodiments of this specification, a logistics information management system is provided, including a server and a client, comprising: The server is configured to respond to a package import request submitted by the client, identify at least one import package, obtain the original logistics data corresponding to each of the at least one import package; perform structured processing on the original logistics data to generate structured logistics data; respond to a logistics information viewing request submitted by the client, identify a category tag; identify the target package corresponding to the category tag among the at least one import package; and send the target logistics structured data corresponding to the target package to the client. The client is used to generate a logistics information display list corresponding to the category tag based on the target logistics structured data corresponding to the target package, and to display the logistics information display list on the interactive page. The logistics information display list includes at least one sublist, which displays the logistics information of the target package corresponding to the tag value of the category tag.
[0005] According to a second aspect of the embodiments of this specification, a logistics information management method is provided, applied to a server, comprising: In response to a package import request submitted by the client, at least one package to be imported is identified, the original logistics data corresponding to the at least one imported package is obtained, and the original logistics data is processed in a structured manner to generate structured logistics data. In response to the logistics information viewing request submitted by the client, a category tag is determined, the target package corresponding to the category tag is identified in the at least one imported package, and the target logistics structured data corresponding to the target package is sent to the client.
[0006] According to a third aspect of the embodiments of this specification, a logistics information management method is provided, applied to a client, comprising: Send a logistics information viewing request to the server, wherein the logistics information viewing request carries category tags; Receive the target logistics structured data corresponding to the target package sent by the server; Based on the target logistics structured data corresponding to the target package, a logistics information display list corresponding to the category tag is generated and displayed on the interactive page. The logistics information display list includes at least one sublist, which displays the logistics information of the target package corresponding to the tag value of the category tag.
[0007] According to a fourth aspect of the embodiments of this specification, a logistics information management device is provided, applied to a server, comprising: The processing module is configured to respond to a package import request submitted by the client, identify at least one import package, obtain the original logistics data corresponding to the at least one import package, perform structured processing on the original logistics data, and generate structured logistics data. The determination module is configured to, in response to a logistics information viewing request submitted by the client, determine a category tag, identify the target package corresponding to the category tag among the at least one imported package, and send the target logistics structured data corresponding to the target package to the client.
[0008] According to a fifth aspect of the embodiments of this specification, a logistics information management device is provided, applied to a client, comprising: The sending module is configured to send a logistics information viewing request to the server, wherein the logistics information viewing request carries a category tag; The receiving module is configured to receive the target logistics structured data corresponding to the target package sent by the server; The generation module is configured to generate a logistics information display list corresponding to the category tag based on the target logistics structured data corresponding to the target package, and display the logistics information display list on the interactive page. The logistics information display list includes at least one sublist, which displays the logistics information of the target package corresponding to the tag value of the category tag.
[0009] According to a sixth aspect of the embodiments of this specification, a computing device is provided, comprising: Memory and processor; The memory is used to store logistics information management instructions, and the processor is used to execute the logistics information management instructions. When the logistics information management instructions are executed by the processor, they implement the steps of any of the above-mentioned logistics information management methods.
[0010] According to a seventh aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores logistics information management instructions, which, when executed by a processor, implement the steps of any of the above-described logistics information management methods.
[0011] According to an eighth aspect of the embodiments of this specification, a computer program product is provided, including a computer program or instructions that, when executed by a processor, implement the steps of any of the above-described logistics information management methods.
[0012] The logistics information management system provided in this embodiment includes a server and a client. The server responds to a package import request submitted by the client, identifies at least one package to import, obtains the original logistics data corresponding to each of these packages, performs structured processing on the original logistics data to generate structured logistics data, and thus obtains the structured logistics data corresponding to each of the at least one imported package. Responding to a logistics information viewing request submitted by the client, the server determines category tags, identifies the target package based on the category tags, and then sends the target logistics structured data corresponding to the target package to the client. The client generates a logistics information display list corresponding to the category tags based on the target structured data. The logistics information display list includes at least one sublist, which corresponds to the tag value of the category tag and displays the logistics information of the target package corresponding to the tag value. Using the logistics information management system provided in this embodiment, data corresponding to packages scattered across various platforms can be obtained and managed uniformly. Furthermore, the logistics information of packages can be displayed on the client's interactive page according to category tags, allowing users to intuitively view the logistics information of packages from different platforms on the interactive page without switching to a specific platform for querying, greatly improving the user experience. Attached Figure Description
[0013] Figure 1 This is a schematic diagram of a logistics information management system provided in one embodiment of this specification; Figure 2 This is a schematic diagram of the structure of a logistics information management system provided in one embodiment of this specification; Figure 3a This is a schematic diagram of a first interactive page provided in one embodiment of this specification; Figure 3bThis is a schematic diagram of a second interactive page provided in one embodiment of this specification; Figure 3c This is a schematic diagram of a third interactive page provided in one embodiment of this specification; Figure 3d This is a schematic diagram of a fourth interactive page provided in one embodiment of this specification; Figure 3e This is a schematic diagram of a fourth interactive page provided in one embodiment of this specification; Figure 4 This is a flowchart illustrating the processing procedure of a logistics information management system according to one embodiment of this specification. Figure 5 This is a flowchart illustrating a logistics information management method provided in one embodiment of this specification; Figure 6 This is a flowchart of another logistics information management method provided in one embodiment of this specification; Figure 7 This is a schematic diagram of the structure of a logistics information management device provided in one embodiment of this specification; Figure 8 This is a schematic diagram of the structure of another logistics information management device provided in one embodiment of this specification; Figure 9 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation
[0014] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.
[0015] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “described,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.
[0016] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."
[0017] Furthermore, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.
[0018] First, the terms and concepts used in one or more embodiments of this specification will be explained.
[0019] pack Parcels are the most basic physical unit in logistics and transportation. They are usually formed by the sender packing one or more items into boxes, bags or envelopes to create an independent mailing unit.
[0020] This specification provides a logistics information management system, and also relates to a logistics information management method, a logistics information management device, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail in the following embodiments.
[0021] With the booming development of e-commerce, online shopping has become an indispensable part of modern life. Users shop on different e-commerce platforms for reasons such as price comparison, product variety, or specific promotional activities. Correspondingly, the packages generated by orders from these e-commerce platforms are handled by numerous different logistics service providers. To check the logistics status of these scattered packages, users typically need to log into each e-commerce platform separately and check their order pages one by one. Alternatively, users may need to manually record the tracking numbers for orders from different platforms and then check them on the websites or applications of the corresponding logistics service providers. Furthermore, users can also mail packages themselves from different platforms. When users need to check the logistics information of their packages, they need to frequently switch between multiple different applications or websites, which is cumbersome, consumes a lot of time and energy, and is prone to problems such as misdelivery or missed deliveries due to negligence or forgetfulness.
[0022] See Figure 1 The schematic diagram illustrates that the logistics information management system provided in this embodiment includes a server and a client. The server responds to a package import request submitted by the client, identifies at least one package to import, obtains the original logistics data corresponding to each of these packages, performs structured processing on the original logistics data to generate structured logistics data, and thus obtains the structured logistics data corresponding to each of the at least one imported package. Responding to a logistics information viewing request submitted by the client, the server determines category tags, identifies the target package based on the category tags, and then sends the target logistics structured data corresponding to the target package to the client. The client generates a logistics information display list corresponding to the category tags based on the target structured data. The logistics information display list includes at least one sublist, which corresponds to the tag value corresponding to the category tag, and displays the logistics information of the target package corresponding to the tag value. Using the logistics information management system provided in this embodiment, data corresponding to packages scattered across various platforms can be obtained and managed uniformly. Furthermore, the logistics information of packages can be displayed on the client's interactive page according to category tags, allowing users to intuitively view the logistics information of packages from different platforms on the interactive page without switching to a specific platform for querying, greatly improving the user experience.
[0023] See Figure 2 , Figure 2 This diagram illustrates the structure of a logistics information management system 200 according to an embodiment of this specification. The logistics information management system 200 includes a server 210 and a client 220, and is implemented as follows: The server 210 is configured to respond to a package import request submitted by the client, identify at least one import package, obtain the original logistics data corresponding to the at least one import package, perform structured processing on the original logistics data to generate structured logistics data, respond to a logistics information viewing request submitted by the client, identify a category tag, identify the target package corresponding to the category tag among the at least one import package, and send the target logistics structured data corresponding to the target package to the client. The client 220 is used to generate a logistics information display list corresponding to the category tag based on the target logistics structured data corresponding to the target package, and to display the logistics information display list on the interactive page. The logistics information display list includes at least one sublist, which displays the logistics information of the target package corresponding to the tag value of the category tag.
[0024] The logistics information management system provided in this embodiment can be applied to scenarios where users need to centrally view the logistics information of packages after shopping on different e-commerce platforms or sending packages through different logistics platforms. This system can import packages from various platforms, integrate the data, and then generate a clear and intuitive visual logistics information display list according to category tags. This allows users to centrally and intuitively view packages from different platforms without having to switch between platforms to find the corresponding package logistics information, greatly improving the user experience.
[0025] Specifically, a package import request is an instruction initiated by the client to request the server to import data corresponding to one or more packages. The package import request typically includes package guidance information for the corresponding package, which the server can use to import the package. Imported packages refer to one or more packages associated with the package guidance information in the package import request. Raw logistics data refers to the unprocessed data related to imported packages obtained by the server from various platforms. Structured logistics data refers to data with a unified format obtained after parsing, cleaning, and standardizing the raw logistics data. Structured logistics data generally includes explicit fields (such as tracking number, logistics time, logistics status, logistics location, etc.). Structured logistics data can be recorded in tables in a database or in other ways; this embodiment does not impose any limitations.
[0026] A logistics information viewing request refers to an instruction initiated by the client to the server, requesting the display of package logistics information according to specific classification criteria. This request typically includes category tags. Category tags refer to the dimensions by which users group packages for display. For example, category tags can be "Logistics Status," "Delivery Location," or "Logistics Platform," etc. The tag value corresponding to a category tag is a specific category under a certain dimension. For example, it could be "Signed For" under "Logistics Status," or Address A under "Delivery Location," etc. Alternatively, category tags can also be set as specific categories under a dimension. For example, category tags could be "Signed For" or "Delivery Location is A," etc. In this case, the category tag has a tag value equal to the category tag. Specifically, in practice, category tags can be set by relevant technical personnel or customized by the user; this embodiment does not impose any limitations. A target package refers to a package selected from imported packages based on the category tag that matches that tag. Target logistics structured data refers to the structured logistics data corresponding to the target package, used to generate a logistics information display list on the client side later.
[0027] Logistics information refers to various information about a package during its transportation process. This may include tracking number, logistics platform, real-time status (e.g., picked up, in transit, being delivered, signed for), operator information, etc., reflecting the package's logistics status. The logistics information display list is a visual list where the client, based on structured logistics data fed back from the server, processes this data and displays the package's logistics information clearly and orderly according to category tags. Sublists are lower-level units of the logistics information display list. Each sublist generally corresponds to a specific category tag value. When the category tag is a tag value, the logistics information display list includes a sublist that displays the logistics information for all packages corresponding to that category tag.
[0028] Based on this, users can input package guidance information on the client's interactive page, such as a communication account, tracking number, or platform account. The client generates a package import request based on this information and sends it to the server. The server determines the package guidance information based on the information carried in the package request. For different package guidance information, the server can request at least one import package associated with that guidance information from different platforms. The server's method for determining the import package for different types of package guidance information will be explained in detail later, and will not be repeated here. After determining at least one import package, the original logistics data corresponding to each import package is obtained. Then, this original logistics data is structured to generate structured logistics data. Specifically, after obtaining the original logistics data from different platforms, it can be parsed to extract target fields. A large language model can be used to extract key information such as tracking number, time, and physical status from the original logistics data. Then, this key information is standardized to have a unified format. Finally, the structured logistics data is obtained.
[0029] Furthermore, for imported packages containing tracking numbers, the server can update the logistics status of the imported package in real time. Specifically, it can request the logistics status of the imported package from the corresponding logistics platform according to the logistics status update cycle, and then update the structured logistics data of the imported package based on the latest logistics status to maintain the most up-to-date logistics status. The server can also predict the delivery time and expected delivery location (collection point or user's actual address) of the imported package based on the structured logistics data. Large-scale models can be used for prediction, and the specific implementation method can be set by relevant technical personnel; this embodiment does not impose any limitations.
[0030] When a user needs to view a package, they can select a category tag on the client's interactive page, or the user can customize a category tag. The client generates a logistics information viewing request based on the category tag and sends it to the server. Upon receiving the logistics information viewing request, the server determines the category tag carried in the request, filters at least one package from those packages that match the category tag, and then groups the target packages according to the tag value, with each group corresponding to a single category tag value. The server then sends the structured logistics data corresponding to the grouped target packages to the client. Based on the target logistics structured data, the client displays the logistics information of the target packages in a logistics information list according to the group. Each group corresponds to a tag value, and each group corresponds to a sublist in the logistics information display list. Each sublist displays the logistics information of the target packages under the tag value corresponding to that sublist.
[0031] For example, suppose the imported packages are Package 1, Package 2, Package 3, Package 4, Package 5, Package 6, Package 7, Package 8, Package 9, and Package 10. The logistics information for Package 1 is: A1 Order placed on e-commerce platform, B2 Transportation on logistics platform, C1 Collection point, In transit...; the logistics information for Package 2 is: A2 Order placed on e-commerce platform, B1 Transportation on logistics platform, C2 Collection point, Awaiting shipment...; the logistics information for Package 3 is: A3 Order placed on e-commerce platform, B3 Transportation on logistics platform, C3 Collection point, Awaiting shipment...; the logistics information for Package 4 is: A2 Order placed on e-commerce platform, B2 Transportation on logistics platform, C2 Collection point, Awaiting pickup...; and the logistics information for Package 5 is: A3 E-commerce platform... The logistics information for package 6 is as follows: Order placed on e-commerce platform, transported by logistics platform B1, collected at collection point C1, pending pickup... The logistics information for package 7 is as follows: Order placed on e-commerce platform A1, transported by logistics platform B3, collected at collection point C3, pending pickup... The logistics information for package 8 is as follows: Order placed on e-commerce platform A2, transported by logistics platform B2, collected at collection point C1, pending pickup... The logistics information for package 9 is as follows: Order placed on e-commerce platform A3, transported by logistics platform B1, collected at collection point C2, pending pickup... The logistics information for package 10 is as follows: Order placed on e-commerce platform A2, transported by logistics platform B2, collected at collection point C1, pending pickup... Users can select the category tag as logistics status. The interactive page displays a list of logistics information as follows: In transit: logistics information of package 1, package 5, package 7, and package 9; Awaiting shipment: logistics information of package 2 and package 3; Awaiting pickup: logistics information of package 4 and package 8; Awaiting collection: logistics information of package 6 and package 10.
[0032] In summary, the logistics information management system provided in this embodiment includes a server and a client. The server responds to a package import request submitted by the client, identifies at least one package to import, obtains the original logistics data corresponding to each of these packages, performs structured processing on the original logistics data to generate structured logistics data, and thus obtains the structured logistics data corresponding to each of the at least one imported package. Responding to a logistics information viewing request submitted by the client, the server determines category tags, identifies the target package based on the category tags, and then sends the target logistics structured data corresponding to the target package to the client. The client generates a logistics information display list corresponding to the category tags based on the target structured data. The logistics information display list includes at least one sublist, which corresponds to the tag value corresponding to the category tag, and displays the logistics information of the target package corresponding to the tag value. Using the logistics information management system provided in this embodiment, data corresponding to packages scattered across various platforms can be obtained and managed uniformly. Furthermore, the logistics information of packages can be displayed on the client's interactive page according to category tags, allowing users to intuitively view the logistics information of packages from different platforms on the interactive page without switching to a specific platform for querying, greatly improving the user experience.
[0033] Furthermore, to facilitate user management of package logistics information, after importing packages and displaying their logistics information in the logistics information display list on the interactive page, users can edit the package logistics information themselves. In this embodiment, the client is also used to receive a logistics information modification instruction submitted for a package to be modified in the logistics information display list, and send a logistics information modification request carrying the information to be modified to the server based on the logistics information modification instruction; the server is also used to respond to the logistics information modification request, update the logistics structured data corresponding to the package to be modified based on the information to be modified, obtain the updated logistics structured data and feed it back to the client; the client is also used to update the logistics information display list based on the updated logistics structured data.
[0034] Specifically, the package to be modified refers to the package selected by the user in the logistics information display list, for which logistics information needs to be edited. The logistics information modification instruction refers to the instruction triggered by the user through a specific operation on the client's interactive page. This specific operation could be long-pressing the logistics information corresponding to a package, or clicking the "Edit" control. The specific method can be set by relevant technical personnel according to actual needs; this embodiment does not impose any limitations. The logistics information modification request refers to the data encapsulated by the client after receiving the logistics information modification instruction, including the identifier of the package to be modified and the specific information to be modified.
[0035] The information to be modified refers to the content that the user intends to change. This information includes at least one of the following: package label information (which can be user-defined labels, such as logistics labels, e-commerce platform labels, pickup method labels, delivery address labels, package owner labels, or package origin labels, etc.), package remarks information (which can be personalized text descriptions added by the user, such as "a birthday gift for mom"), package attribute information (which can be package attributes, such as item name, item category, item price, applicable scenario, applicable season, item receipt time, etc.), package logistics status information (which can be manually marked as "picked up," "returned," etc.), and package visibility information (which can be set to be visible only to the user, visible only to added friends and family, or a temporary link can be generated for sharing with others, with an expiration date, such as 7 days). Updating the logistics structured data refers to the server updating the logistics structured data based on the user-submitted information to be modified after processing the logistics information modification request, indicating that the information to be modified has been persistently stored. The updated logistics information display list shows the updated logistics information of the package to be modified.
[0036] Based on this, users can select a package to be modified from the logistics information display list on the client's interactive page and edit its logistics information. Editing can be triggered by the editing controls on the interactive page, such as long-pressing or other specific operations. The specific triggering method can be set by relevant technical personnel; this embodiment does not impose any limitations. Based on the user-triggered editing operation, the client receives the logistics information modification instruction, encapsulates the identification information of the package to be modified and the information to be modified, generates a logistics information modification request, and sends it to the server. Upon receiving the logistics information modification request, the server updates the logistics structured data corresponding to the package to be modified, that is, it synchronizes the information to be modified to the corresponding logistics structured data, thereby obtaining updated logistics structured data, and then feeds this updated logistics structured data back to the client. The client updates the logistics information display list based on the updated logistics structured data, that is, it updates the logistics information of the package to be modified in the display list, displaying the logistics information edited by the user.
[0037] It should be noted that users can not only update package logistics information, but also delete or archive packages for further package management. Furthermore, users can establish relationships with family and friends to manage their packages. These relationships can be with family members, classmates, colleagues, etc., and the specific relationships can be set by the user; this embodiment does not impose any limitations. Users can import packages from users with whom they have family or friend relationships, for example, through a friend's communication account (which could be a phone number). Users can set access permissions for packages, making them visible only to themselves or adding family and friends to the list. They can also generate temporary packages to share with others. When a package is set to be visible only to oneself, family and friends cannot access the package's logistics information through the package's guidance information (such as the communication account). Users can also share packages in bulk with family and friends; for example, they can share all packages to a specific delivery address or all packages to a specific collection point.
[0038] For example, a user edits package 1, adding the note "A birthday gift for mom." The client sends a logistics information modification request to the server. The server updates the structured logistics data for package 1, adding the note "A birthday gift for mom," and sends the updated structured logistics data back to the client. In the logistics information display list, the client will see the added note "A birthday gift for mom" for package 1.
[0039] In summary, users can modify various information about a package on the client side, and the server will synchronously update the corresponding structured data, thus achieving precise management of logistics information and improving the flexibility of updating package logistics information.
[0040] Furthermore, to improve the efficiency of importing packages for users, import can be performed using a communication account or a tracking number. In this embodiment, the client is used to determine the communication account or tracking number and send a package import request to the server based on the communication account or tracking number. The server is used to respond to the package import request submitted by the client, determine the target logistics platform associated with the communication account or tracking number, determine at least one imported package associated with the communication account or tracking number in the target logistics platform, and request the target logistics platform to return the original logistics data corresponding to the at least one imported package.
[0041] Specifically, a communication account refers to a user's identity identifier on a communication platform or service, used for information exchange and interaction. A communication account can be a phone number, an email address, etc. The target logistics platform associated with the communication account refers to the logistics platform authorized by the user. In this case, at least one imported package associated with the target logistics platform refers to a package on the target logistics platform related to the communication account. For example, it could be a package corresponding to the communication account as the recipient's contact information, or a package corresponding to the communication account as the sender's contact information. The specific association settings can be determined by relevant technical personnel based on actual circumstances; this embodiment does not impose any limitations. A tracking number, or waybill number, is an identifier generated and assigned to a package by the logistics company. A package query request can be sent to the corresponding logistics platform using the tracking number to query the logistics information of the corresponding package. The target logistics platform associated with the tracking number refers to the logistics platform responsible for transporting the package, identified according to the coding rules of the tracking number. In this case, at least one imported package associated with the target logistics platform refers to the package corresponding to the tracking number.
[0042] Based on this, the methods of importing packages via communication accounts or tracking numbers are explained separately. First, the method using communication accounts is introduced. Users enter their communication account on the interactive page. After verification, users select the logistics platform to import to and authorize the selected platform. The client sends a package import request to the server, and the server sends a query request to the corresponding target logistics platform to obtain at least one package associated with that communication account. Typically, packages associated with a communication account are those where the communication account serves as the recipient's contact information. Then, the server requests the original logistics data corresponding to at least one imported package from the target logistics platform. The method of importing packages via tracking numbers involves the user entering the tracking number on the interactive page. The client sends a package import request to the server, and the server identifies the logistics platform responsible for transporting the package based on the tracking number's encoding rules. The server sends a query request to the corresponding target logistics platform to obtain the package associated with that tracking number and then requests the original logistics data corresponding to that package from the target logistics platform.
[0043] For example, a user enters their contact number "130XXXXXXXX" on the interactive page and verifies the number by entering a verification code, authorizing both the B1 and B2 logistics platforms. The server then imports packages from the B1 logistics platform with the recipient's contact information "130XXXXXXXX" and packages from the B2 logistics platform with the recipient's contact information "130XXXXXXXX".
[0044] In summary, users can import packages by entering identifiers such as communication accounts or tracking numbers, and can import packages in batches, thereby greatly improving the efficiency of package import.
[0045] Furthermore, to improve the efficiency of importing packages for users, import can also be performed through platform accounts. In this embodiment, the client is used to determine the platform account and send a package import request to the server based on the platform account, wherein the platform account is an e-commerce platform account or a logistics platform account; the server is used to respond to the package import request submitted by the client, determine the target platform corresponding to the platform account, request the target platform to provide the target order information corresponding to the platform account, and determine at least one imported package and the original logistics data corresponding to the at least one imported package based on the target order information.
[0046] Specifically, a platform account refers to a user's digital identity credential for accessing a website, application, or online service. A platform account typically consists of a username and password. It is used to identify the user and authorize appropriate access permissions, allowing the user to manage their personal data within the platform. A platform account can be for a logistics platform or an e-commerce platform. The target platform refers to the e-commerce or logistics platform corresponding to the platform account. Target order information refers to the order details requested by the server after accessing the target platform.
[0047] Based on this, users can authorize their platform accounts on the client's interactive page. The client then sends a package import request to the server based on the platform account. The server requests order information from the logistics platform or e-commerce platform corresponding to that platform account, and then determines at least one imported package and its corresponding original logistics data based on the order information. When the platform account is a logistics platform, the server can obtain all packages sent by the user or received by the user through that logistics platform. When the platform account is an e-commerce platform, the server can obtain all packages purchased by the user through that e-commerce platform. In this case, the user can further authorize the package, either partially or fully. With partial authorization, the server can obtain the logistics information of the corresponding package and use this information as the original logistics data. With full authorization, the server can obtain the product information, such as the product name, merchant, and order time. The logistics and product information are then used as the original logistics data.
[0048] For example, a user authorizes an account on the A1 e-commerce platform. The server requests the A1 e-commerce platform to provide the order information of the account on the A1 e-commerce platform. Based on the order information, the server determines at least one package corresponding to the goods purchased on the e-commerce platform, and obtains the original logistics data corresponding to at least one package based on the order information.
[0049] In summary, users can authorize e-commerce or logistics platform accounts, and the server can request order information under that platform account and import the corresponding packages based on the order information. When the order information includes multiple packages, they can be imported in batches, which greatly improves the efficiency of package import.
[0050] Furthermore, to enhance the diversity of package import methods, users can manually input pickup information to generate virtual packages. In this embodiment, the client is also used to receive submitted logistics information record requests, determine the pickup information carried in the logistics information record request, and perform a completeness check on the pickup information; if the pickup information is incomplete, display a prompt message on the interactive page, receive missing information input in response to the prompt message, update the pickup information based on the missing information; generate a virtual package and corresponding virtual logistics information based on the updated pickup information; and display the virtual logistics information corresponding to the virtual package in the logistics information display list.
[0051] Specifically, a logistics information record request refers to an instruction initiated by a user to manually create a virtual package. Pickup information refers to the data set used by the user to create the package, which may include a pickup code, pickup address, item summary, contact person, etc. Integrity verification refers to determining the completeness of the pickup information according to a preset integrity evaluation standard (for example, it could be that the pickup information is complete when it includes information A, B, and C; this is just an example of an integrity rule evaluation standard, and specific integrity evaluation standards can be set by relevant technical personnel; this embodiment does not impose any limitations). Incomplete pickup information means that after integrity verification, the pickup information lacks the necessary information to generate a virtual package. Missing information refers to the missing information generated when the logistics information is incomplete. A virtual package is a package created based on complete pickup information; this package may lack a tracking number, and its logistics information is manually created and maintained by the user. Virtual logistics information refers to the physical information that the user manually creates and maintains for the virtual package.
[0052] Based on this, users input pickup information on the interactive page, such as a pickup code, pickup address, item description, and contact person. The client checks the completeness of the user-input pickup information. Specifically, completeness evaluation criteria can be pre-set (for example, the pickup information is considered complete if it includes information A, B, and C; this is just an example of a completeness rule evaluation criterion, and specific completeness evaluation criteria can be set by relevant technical personnel; this embodiment does not impose any limitations). If the pickup information is incomplete, a prompt message is displayed on the interactive page, the missing information is received in response to the prompt message, the pickup information is updated based on the missing information, a virtual package and its corresponding virtual logistics information are generated based on the updated pickup information, and the virtual logistics information corresponding to the virtual package is displayed in the logistics information display list. If the pickup information is complete, a virtual package and its corresponding virtual logistics information are generated based on the pickup information, and the virtual logistics information corresponding to the virtual package is displayed in the logistics information display list.
[0053] In addition, users can input pickup information via voice. The client recognizes the voice, converts it into text, extracts key pickup information, and generates a virtual package and its corresponding virtual logistics information. Users can also upload images containing pickup information, such as screenshots of pickup SMS messages or chat screenshots containing pickup information. The client recognizes the images, extracts key pickup information, and generates a virtual package and its corresponding virtual logistics information. Users can also upload text, which can be a single piece of text, such as a copied pickup SMS message. The client extracts key pickup information from the text to generate a virtual package and its corresponding virtual logistics information.
[0054] For example, suppose the integrity evaluation criterion is that the pickup information is considered complete if it includes a pickup code and a pickup address. When the user enters the pickup code, the interactive page displays the prompt "Please enter the pickup address." The user then enters the pickup address, and a virtual package and its corresponding logistics information are generated based on the pickup code and the address range. This virtual logistics information is then displayed in the logistics information display list.
[0055] In summary, users can input pickup information to generate virtual packages, which further enriches the sources of packages in the logistics information display list. In addition, users can import packages based solely on pickup information, simplifying the package entry process.
[0056] Furthermore, to simplify the user's package import process, the user can import packages via text, voice, or images. In this embodiment, the package import request carries package guidance information, which includes a communication account, a tracking number, and a platform account. The package guidance information is used to guide the user to select at least one imported package, and the data format of the package guidance information is at least one of text, images, or voice.
[0057] Specifically, package guidance information refers to the clues provided by the client when sending a package import request to the server, guiding the server to determine at least one package logistics data to be imported. Package guidance information can be a communication account, tracking number, platform account, or pickup information. The data format of package guidance information is not limited to text; it can also be images or voice.
[0058] Based on this, the format of package guidance information can be text, voice, images, or files, etc. Text can be a single paragraph, which can be a copied paragraph. Images can be photos of logistics documents or chat screenshots, etc. Files can be spreadsheets, which may include information such as the logistics tracking number, e-commerce platform, and recipient. When the data format is text, semantic analysis can be performed on the text to extract the package guidance information; when the data format is voice, the voice can be recognized, converted into text, and then semantic analysis can be performed to extract the package guidance information; when the data format is image data, the image can be recognized, the text information in the image can be extracted to form text, then the text can be corrected and formatted, and finally semantic analysis can be performed to extract the package guidance information. Then, the category of the package guidance information is determined, and based on the category, a specific method for importing the package is selected. Several specific methods for importing packages are provided above, such as importing packages through a communication account, importing packages through a logistics tracking number, importing packages through a platform account, etc. Specific package import methods can be found in the above description, and will not be repeated here. Figure 3a The image shown is a schematic diagram of the package import interface, where users can trigger the package import operation.
[0059] In addition, users can upload spreadsheet files. These spreadsheets can include information such as tracking numbers, e-commerce platforms, and recipients. The client identifies the spreadsheet data, determines the category of the package import information based on the information included in the spreadsheet, and then imports the package using the corresponding method. Users can also enter multiple package import information entries at once. The client can identify these entries, split them into several separate import requests, and then generate a package import request based on each entry. The server then executes the package import operation.
[0060] For example, a user can input "I bought a package today, the tracking number is XXXXXXXX" via voice. The client recognizes the voice, generates text, confirms that the package import information is the tracking number "XXXXXXXX", and sends the package import information to the server based on the tracking number "XXXXXXXX".
[0061] In summary, users can submit diverse package guidance information and support multiple data formats such as text, images, and voice, which significantly reduces the information entry threshold and greatly improves the convenience of users importing packages.
[0062] Furthermore, users can view packages in a personalized way according to their own habits or actual needs. In this embodiment, the client is used to determine a custom category label or a target category label from a preset list, use the custom category label or the target category label as the category label, and send a logistics information viewing request to the server based on the category label. The server is used to respond to the logistics information viewing request submitted by the client, group the target packages based on the category label, obtain at least one label value and group logistics structured data corresponding to the at least one label value respectively; combine the group logistics structured data corresponding to the at least one label value respectively into target logistics structured data, and send the target logistics structured data to the client.
[0063] Specifically, custom category tags refer to category dimensions created by users based on their own needs, habits, or preferences. For example, users can create category tags such as "Project Name" (with corresponding tag values like "Project A Procurement" or "Project B Procurement"), "Urgency Level" (e.g., "Urgent" or "Normal"), and "Recipient" (e.g., "Front Desk" or "Finance Department"). Pre-defined tag lists refer to pre-defined category dimensions provided to users for selection, typically covering common filtering conditions in logistics management. For example... Figure 3b The interactive page shown includes preset tag lists with category tags such as "Logistics Status Tags" (corresponding tag values can be in transit, being delivered, awaiting pickup, signed for, or being returned), "E-commerce Platform Tags," "Logistics Platform Tags," "Pickup Method Tags" (corresponding tag values can be express lockers, express stations, door-to-door delivery, or collection points), "Delivery Address Tags," or "Ownership Tags" (corresponding tag values can be self, spouse, children, or shared by family), etc. Users can select category tags from the preset tag list to display the physical information of imported packages according to the category tags.
[0064] Based on this, users can select category tags from a preset tag list, or they can define their own category tags. The client uses the user-selected category tags or custom category tags as category tags and sends a logistics information viewing request to the server based on these category tags. The server responds to the client's logistics information viewing request. When the category tag matches the one selected by the user from the preset tag list, the server can view the target data associated with the category tag in the target logistics structured data corresponding to at least one imported package. Based on this target data, packages are grouped, with packages having the same tag value grouped together. The corresponding logistics information for each package in a group forms a group of logistics structured data. These groups of logistics structured data are then combined to obtain the target logistics structured data, which is sent to the client. When the category tag is a specific value (e.g., a package from courier platform A), the server can first filter at least one imported package to obtain packages that match the category tag. These packages are the target packages, and the target logistics structured data corresponding to the target packages is sent to the client. Figure 3b The image shows an illustration of selecting category tags or creating custom category tags. Users can enter custom category tags on this interactive page or select category tags from a list of preset tags. Furthermore, users can customize the order of the sub-tags corresponding to the category tags, so that the logistics information of each sub-tag is displayed in the logistics information display list in the customized order.
[0065] For example, continuing with the previous example, let's assume the imported packages are Package 1, Package 2, Package 3, Package 4, Package 5, Package 6, Package 7, Package 8, Package 9, and Package 10, and the corresponding logistics information is as described above.
[0066] Assuming the selected category tag is "e-commerce platform," the results of categorizing imported packages based on the e-commerce platform are as follows: A1 E-commerce Platform: Logistics information for Package 1, Package 6, and Package 7; A2 E-commerce Platform: Logistics information for Package 2, Package 4, Package 8, and Package 10; A3 E-commerce Platform: Logistics information for Package 3, Package 5, and Package 9. The corresponding interactive page displaying the logistics information is as follows. Figure 3c As shown in (1), users can also select any sub-tab from the sub-tabs "All", "A1 E-commerce Platform", "A2 E-commerce Platform" and "A3 E-commerce Platform" above. For example, if a user selects "A2 E-commerce Platform", the corresponding interactive page will look like this. Figure 3c As shown in (2) of the text.
[0067] Assuming the selected category tag is "logistics platform," the result of categorizing imported packages based on the logistics platform is as follows: B1 Logistics Platform: Logistics information for Package 2, Package 5, Package 6, and Package 9; B2 Logistics Platform: Logistics information for Package 1, Package 4, Package 8, and Package 10; B3 Logistics Platform: Logistics information for Package 3 and Package 7. The corresponding interactive page for displaying the logistics information list is as follows. Figure 3d As shown in (1), users can also select any sub-tab from the above sub-tabs "All", "B1 Logistics Platform", "B2 Logistics Platform", and "B3 Logistics Platform". For example, if a user selects "B2 Logistics Platform", the corresponding interactive page will look like this: Figure 3d As shown in (2) of the text.
[0068] Assuming the selected category tag is "Logistics Status," the result of categorizing imported packages based on their logistics status is as follows: In Transit: Logistics information for Package 1, Package 5, Package 7, and Package 9; Awaiting Shipment: Logistics information for Package 2 and Package 3; Awaiting Pickup: Logistics information for Package 4 and Package 8; Awaiting Collection: Logistics information for Package 6 and Package 10. The corresponding interactive page for displaying the logistics information list is as follows: Figure 3e As shown in (1), users can also select any sub-label from the sub-labels "All", "In Transit", "Pending Shipment", "Pending Collection", and "Pending Pickup" above. For example, if a user selects "In Transit", the corresponding interactive page will be as follows: Figure 3e As shown in (2) of the text.
[0069] In summary, in addition to selecting category tags from the preset tag list, users can also customize category tags. This allows users to efficiently and personally view packages according to their own habits or actual needs, greatly improving the diversity and flexibility of package viewing.
[0070] The following is in conjunction with the appendix Figure 4 Taking the application of the logistics information management system provided in this manual in a scenario of viewing logistics information of packages from multiple sources as an example, the logistics information management system will be further explained. Among other things, Figure 4 This specification illustrates a flowchart of the processing procedure of a logistics information management system according to an embodiment, which specifically includes the following steps.
[0071] In step S402, the client sends a package import request to the server.
[0072] Specifically, the package import request carries package guidance information, which includes a communication account, a logistics tracking number, and a platform account. The package guidance information is used to guide the determination of the at least one imported package, and the data format of the package guidance information is at least one of text, image, or voice.
[0073] In step S404, the server responds to the package import request submitted by the client, identifies at least one package to be imported, and obtains the original logistics data corresponding to each of the at least one imported package. The original logistics data is then processed to generate structured logistics data.
[0074] Based on this, the package import request can be generated based on a communication account or a tracking number. The specific processing method is as follows: the client is used to determine the communication account or tracking number, and send a package import request to the server based on the communication account or the tracking number; the server is used to respond to the package import request submitted by the client, determine the target logistics platform associated with the communication account or the tracking number; determine at least one import package associated with the communication account or the tracking number in the target logistics platform, and request the target logistics platform to return the original logistics data corresponding to the at least one import package.
[0075] Furthermore, the package import request can be generated based on a platform account. The specific processing method is as follows: the client is used to determine the platform account and send a package import request to the server based on the platform account, wherein the platform account is an e-commerce platform account or a logistics platform account; the server is used to respond to the package import request submitted by the client, determine the target platform corresponding to the platform account, request the target platform to provide the target order information corresponding to the platform account, and determine at least one import package and the original logistics data corresponding to the at least one import package based on the target order information.
[0076] Step S406: The client sends a request to the server to view logistics information.
[0077] Specifically, the category tags are at least one of the following: logistics platform tags, e-commerce platform tags, logistics status tags, delivery address tags, pickup method tags, and attribution relationship tags. The client can determine a custom category tag or a target category tag from a preset list, use the custom category tag or the target category tag as the category tag, and send a logistics information viewing request to the server based on the category tag. In step S408, the server responds to the logistics information viewing request submitted by the client and determines the category label; and determines the target package corresponding to the category label among the at least one imported package.
[0078] Specifically, in response to the logistics information viewing request submitted by the client, the server groups the target package based on the classification tags to obtain at least one tag value and the group logistics structured data corresponding to the at least one tag value; the group logistics structured data corresponding to the at least one tag value are combined into target logistics structured data, and the target logistics structured data is sent to the client.
[0079] In step S410, the server sends the target logistics structured data corresponding to the target package to the client.
[0080] In step S412, the client generates a logistics information display list corresponding to the category tag based on the target logistics structured data corresponding to the target package, and displays the logistics information display list on the interactive page.
[0081] Specifically, the logistics information display list includes at least one sublist, which displays the logistics information of the target package corresponding to the tag value of the category tag.
[0082] Step S414: The client receives a logistics information modification instruction for the package to be modified in the logistics information display list.
[0083] Specifically, the information to be modified includes at least one of the following: package label information, package remarks information, package attribute information, package logistics status information, and package visibility information.
[0084] Step S416: The client sends a logistics information modification request carrying the information to be modified to the server based on the logistics information modification instruction.
[0085] In step S418, the server responds to the logistics information modification request by updating the logistics structured data corresponding to the package to be modified based on the information to be modified.
[0086] In step S420, the server obtains the updated structured logistics data and sends it back to the client.
[0087] Step S422: The client updates the logistics information display list based on the updated logistics structured data.
[0088] The updated logistics information display list shows the updated logistics information of the package to be modified.
[0089] In addition, the client can also receive logistics information recording requests, determine the pickup information carried in the logistics information recording request, and perform a completeness check on the pickup information; if the pickup information is incomplete, display a prompt message on the interactive page, receive missing information input in response to the prompt message, update the pickup information based on the missing information; generate a virtual package and virtual logistics information corresponding to the virtual package based on the updated pickup information; and display the virtual logistics information corresponding to the virtual package in the logistics information display list.
[0090] In summary, the logistics information management system provided in this embodiment includes a server and a client. The server responds to a package import request submitted by the client, identifies at least one package to import, obtains the original logistics data corresponding to each of these packages, performs structured processing on the original logistics data to generate structured logistics data, and thus obtains the structured logistics data corresponding to each of the at least one imported package. Responding to a logistics information viewing request submitted by the client, the server determines category tags, identifies the target package based on the category tags, and then sends the target logistics structured data corresponding to the target package to the client. The client generates a logistics information display list corresponding to the category tags based on the target structured data. The logistics information display list includes at least one sublist, which corresponds to the tag value corresponding to the category tag, and displays the logistics information of the target package corresponding to the tag value. Using the logistics information management system provided in this embodiment, data corresponding to packages scattered across various platforms can be obtained and managed uniformly. Furthermore, the logistics information of packages can be displayed on the client's interactive page according to category tags, allowing users to intuitively view the logistics information of packages from different platforms on the interactive page without switching to a specific platform for querying, greatly improving the user experience.
[0091] Corresponding to the above system embodiments, this specification also provides embodiments of a logistics information management method, applied to the server side. Figure 5 A flowchart illustrating a logistics information management method according to one embodiment of this specification is shown. Figure 5 As shown, the method includes: Step S502: In response to the package import request submitted by the client, at least one package to be imported is identified, the original logistics data corresponding to the at least one imported package is obtained, and the original logistics data is processed in a structured manner to generate structured logistics data.
[0092] Step S504: In response to the logistics information viewing request submitted by the client, determine the category label, identify the target package corresponding to the category label among the at least one imported package, and send the target logistics structured data corresponding to the target package to the client.
[0093] In one optional embodiment, in response to the logistics information modification request, the logistics structured data corresponding to the package to be modified is updated based on the information to be modified, and the updated logistics structured data is obtained and fed back to the client; In one optional embodiment, in response to the package import request submitted by the client, the target logistics platform associated with the communication account or the tracking number is determined; at least one imported package associated with the communication account or the tracking number in the target logistics platform is determined, and the target logistics platform is requested to provide feedback on the original logistics data corresponding to the at least one imported package.
[0094] In one optional embodiment, in response to the package import request submitted by the client, the target platform corresponding to the platform account is determined; the target platform is requested to provide the target order information corresponding to the platform account, and based on the target order information, at least one import package and the original logistics data corresponding to the at least one import package are determined respectively.
[0095] In one optional embodiment, in response to a logistics information viewing request submitted by the client, the target package is grouped based on the classification tags to obtain at least one tag value and group logistics structured data corresponding to the at least one tag value; the group logistics structured data corresponding to the at least one tag value are combined into target logistics structured data, and the target logistics structured data is sent to the client, wherein the classification tags are at least one of logistics platform tags, e-commerce platform tags, logistics status tags, delivery address tags, pickup method tags, and attribution relationship tags.
[0096] In summary, the logistics information management method provided in this embodiment is applied to the server side. In response to a package import request submitted by the client, at least one package is identified for import. Then, the original logistics data corresponding to each of these at least one imported package is obtained. The original logistics data is then processed to generate structured logistics data, thus obtaining the structured logistics data corresponding to each of the at least one imported package. In response to a logistics information viewing request submitted by the client, category tags are determined. Based on the category tags, the target package is then identified, and the target logistics structured data corresponding to the target package is sent to the client. Using the logistics information management method provided in this embodiment, data corresponding to packages scattered across various platforms can be obtained and then managed uniformly. Furthermore, target logistics structured data can be sent based on category tags to display the package's logistics information on the client's interactive page according to the category tags. This allows users to intuitively view the logistics information of packages from different platforms on the interactive page without switching to a specific platform for querying, greatly improving the user experience.
[0097] The above is an illustrative scheme of a logistics information management method according to this embodiment. It should be noted that the technical solution of this logistics information management method and the technical solution of the logistics information management system described above belong to the same concept. For details not described in detail in the technical solution of the logistics information management method, please refer to the description of the technical solution of the logistics information management system described above.
[0098] Corresponding to the above system embodiments, this specification also provides embodiments of a logistics information management method, applied to a client-side application. Figure 6 A flowchart illustrating another logistics information management method provided in one embodiment of this specification is shown. Figure 6 As shown, the method includes: Step S602: Send a logistics information viewing request to the server.
[0099] The logistics information viewing request includes category tags.
[0100] Step S604: Receive the target logistics structured data corresponding to the target package sent by the server.
[0101] Step S606: Based on the target logistics structured data corresponding to the target package, generate a logistics information display list corresponding to the category tag, and display the logistics information display list on the interactive page.
[0102] The logistics information display list includes at least one sublist, which displays the logistics information of the target package corresponding to the tag value of the category tag.
[0103] In one optional embodiment, a logistics information modification instruction submitted for a package to be modified in the logistics information display list is received, and a logistics information modification request carrying the information to be modified is sent to the server based on the logistics information modification instruction. The information to be modified includes at least one of package tag information, package remarks information, package attribute information, package logistics status information, and package visibility range information.
[0104] In one optional embodiment, the logistics information display list is updated based on the updated logistics structured data, wherein the updated logistics information display list displays the updated logistics information of the package to be modified.
[0105] In one optional embodiment, a communication account or a tracking number is determined, and a package import request is sent to the server based on the communication account or the tracking number.
[0106] In one optional embodiment, a platform account is determined, and a package import request is sent to the server based on the platform account, wherein the platform account is an e-commerce platform account or a logistics platform account.
[0107] In one optional embodiment, a logistics information recording request is received; the pickup information carried in the logistics information recording request is determined and the pickup information is checked for completeness; if the pickup information is incomplete, a prompt message is displayed on the interactive page; missing information is received in response to the prompt message; the pickup information is updated based on the missing information; a virtual package and virtual logistics information corresponding to the virtual package are generated based on the updated pickup information; and the virtual logistics information corresponding to the virtual package is displayed in the logistics information display list.
[0108] In one optional embodiment, a custom category label or a target category label from a preset list is determined, and the custom category label or the target category label is used as the category label. Based on the category label, a logistics information viewing request is sent to the server.
[0109] In summary, the logistics information management method provided in this embodiment is applied to the client side. A logistics information viewing request, carrying category tags, is sent to the server. Then, the target logistics structured data corresponding to the target package is received from the server. Based on the target structured data, a logistics information display list corresponding to the category tags is generated. This list includes at least one sublist, which corresponds to the tag value of the category tag. The sublist displays the logistics information of the target package corresponding to the tag value. Using the logistics information management method provided in this embodiment, logistics information of packages from different platforms can be displayed on the client's interactive page according to category tags. This allows users to intuitively view the logistics information of packages from different platforms on the interactive page without switching to a specific platform for querying, greatly improving the user experience.
[0110] The above is an illustrative scheme of a logistics information management method according to this embodiment. It should be noted that the technical solution of this logistics information management method and the technical solution of the logistics information management system described above belong to the same concept. For details not described in detail in the technical solution of the logistics information management method, please refer to the description of the technical solution of the logistics information management system described above.
[0111] Corresponding to the above method embodiments, this specification also provides embodiments of a logistics information management device applied to a server. Figure 7 A schematic diagram of the structure of a logistics information management device according to one embodiment of this specification is shown. Figure 7 As shown, the device includes: Processing module 702 is configured to respond to a package import request submitted by a client, determine at least one import package, obtain the original logistics data corresponding to the at least one import package, perform structured processing on the original logistics data, and generate structured logistics data. The determination module 704 is configured to respond to a logistics information viewing request submitted by the client, determine a category tag, determine the target package corresponding to the category tag in the at least one imported package, and send the target logistics structured data corresponding to the target package to the client.
[0112] In one optional embodiment, in response to the logistics information modification request, the logistics structured data corresponding to the package to be modified is updated based on the information to be modified, and the updated logistics structured data is obtained and fed back to the client; In one optional embodiment, in response to the package import request submitted by the client, the target logistics platform associated with the communication account or the tracking number is determined; at least one imported package associated with the communication account or the tracking number in the target logistics platform is determined, and the target logistics platform is requested to provide feedback on the original logistics data corresponding to the at least one imported package.
[0113] In one optional embodiment, in response to the package import request submitted by the client, the target platform corresponding to the platform account is determined; the target platform is requested to provide the target order information corresponding to the platform account, and based on the target order information, at least one import package and the original logistics data corresponding to the at least one import package are determined respectively.
[0114] In one optional embodiment, in response to a logistics information viewing request submitted by the client, the target package is grouped based on the classification tags to obtain at least one tag value and group logistics structured data corresponding to the at least one tag value; the group logistics structured data corresponding to the at least one tag value are combined into target logistics structured data, and the target logistics structured data is sent to the client, wherein the classification tags are at least one of logistics platform tags, e-commerce platform tags, logistics status tags, delivery address tags, pickup method tags, and attribution relationship tags.
[0115] In summary, the logistics information management device provided in this embodiment is applied to the server side. Responding to a package import request submitted by the client, it identifies at least one package to import, then obtains the original logistics data corresponding to each of these packages, performs structured processing on the original logistics data to generate structured logistics data, and thus obtains the structured logistics data corresponding to each of the at least one imported package. Responding to a logistics information viewing request submitted by the client, it determines category tags, then identifies the target package based on the category tags, and finally sends the target logistics structured data corresponding to the target package to the client. Using the logistics information management device provided in this embodiment, data corresponding to packages scattered across various platforms can be obtained and then managed uniformly. Furthermore, it can send target logistics structured data based on category tags to display the package's logistics information on the client's interactive page according to the category tags. This allows users to intuitively view the logistics information of packages from different platforms on the interactive page without switching to a specific platform for querying, greatly improving the user experience.
[0116] The above is a schematic diagram of a logistics information management device according to this embodiment. It should be noted that the technical solution of this logistics information management device and the technical solution of the logistics information management method described above belong to the same concept. For details not described in detail in the technical solution of the logistics information management device, please refer to the description of the technical solution of the logistics information management method described above.
[0117] Corresponding to the above method embodiments, this specification also provides embodiments of a logistics information management device applied to a client. Figure 8 A schematic diagram of another logistics information management device provided in one embodiment of this specification is shown. Figure 8 As shown, the device includes: Sending module 802 is configured to send a logistics information viewing request to the server, wherein the logistics information viewing request carries a category tag; The receiving module 804 is configured to receive the target logistics structured data corresponding to the target package sent by the server; The generation module 806 is configured to generate a logistics information display list corresponding to the category label based on the target logistics structured data corresponding to the target package, and display the logistics information display list on the interactive page. The logistics information display list includes at least one sublist, which displays the logistics information of the target package corresponding to the label value of the category label.
[0118] In one optional embodiment, a logistics information modification instruction submitted for a package to be modified in the logistics information display list is received, and a logistics information modification request carrying the information to be modified is sent to the server based on the logistics information modification instruction. The information to be modified includes at least one of package tag information, package remarks information, package attribute information, package logistics status information, and package visibility range information. In one optional embodiment, the logistics information display list is updated based on the updated logistics structured data, wherein the updated logistics information display list displays the updated logistics information of the package to be modified.
[0119] In one optional embodiment, a communication account or a tracking number is determined, and a package import request is sent to the server based on the communication account or the tracking number; In one optional embodiment, a platform account is determined, and a package import request is sent to the server based on the platform account, wherein the platform account is an e-commerce platform account or a logistics platform account; In one optional embodiment, a logistics information recording request is received; the pickup information carried in the logistics information recording request is determined and the pickup information is checked for completeness; if the pickup information is incomplete, a prompt message is displayed on the interactive page; missing information is received in response to the prompt message; the pickup information is updated based on the missing information; a virtual package and virtual logistics information corresponding to the virtual package are generated based on the updated pickup information; and the virtual logistics information corresponding to the virtual package is displayed in the logistics information display list.
[0120] In one optional embodiment, a custom category label or a target category label from a preset list is determined, and the custom category label or the target category label is used as the category label. Based on the category label, a logistics information viewing request is sent to the server. In summary, the logistics information management device provided in this embodiment is applied to a client-side application. It sends a logistics information viewing request to the server, the request carrying category tags. Then, it receives the target logistics structured data corresponding to the target package from the server. Based on the target structured data, it generates a logistics information display list corresponding to the category tags. This list includes at least one sublist, each corresponding to a tag value of the category tag, displaying the logistics information of the target package corresponding to that tag value. Using the logistics information management device provided in this embodiment, logistics information for packages from different platforms can be displayed on the client-side interactive page according to category tags. This allows users to intuitively view the logistics information of packages from different platforms on the interactive page without switching to a specific platform for querying, greatly improving the user experience.
[0121] The above is an illustrative scheme of a logistics information management method according to this embodiment. It should be noted that the technical solution of this logistics information management method and the technical solution of the logistics information management system described above belong to the same concept. For details not described in detail in the technical solution of the logistics information management method, please refer to the description of the technical solution of the logistics information management system described above.
[0122] Figure 9 A structural block diagram of a computing device 900 according to one embodiment of this specification is shown. The components of the computing device 900 include, but are not limited to, a memory 910 and a processor 920. The processor 920 is connected to the memory 910 via a bus 930, and a database 950 is used to store data.
[0123] The computing device 900 also includes an access device 940, which enables the computing device 900 to communicate via one or more networks 960. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 940 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, or a Near Field Communication (NFC) interface.
[0124] In one embodiment of this specification, the above-described components of the computing device 900 and Figure 9 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 9 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.
[0125] The computing device 900 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 900 can also be a mobile or stationary server.
[0126] The processor 920 is used to execute the following logistics information management instructions, which, when executed by the processor, implement the steps of any of the above-mentioned logistics information management methods.
[0127] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device belongs to the same concept as the technical solution of any of the above-described logistics information management methods. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of any of the above-described logistics information management methods.
[0128] An embodiment of this specification also provides a computer-readable storage medium storing logistics information management instructions, which, when executed by a processor, implement the steps of any of the above-described logistics information management methods.
[0129] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium belongs to the same concept as the technical solution of any of the above-described logistics information management methods. Details not described in detail in the technical solution of the storage medium can be found in the description of the technical solution of any of the above-described logistics information management methods.
[0130] An embodiment of this specification also provides a computer program, wherein when the computer program is executed in a computer, it causes the computer to perform the steps of any of the above-described logistics information management methods.
[0131] The above is an illustrative example of a computer program according to this embodiment. It should be noted that the technical solution of this computer program belongs to the same concept as the technical solution of any of the above-described logistics information management methods. Details not described in detail in the computer program's technical solution can be found in the description of the technical solution of any of the above-described logistics information management methods.
[0132] An embodiment of this specification also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of any of the above-described logistics information management methods.
[0133] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product belongs to the same concept as the technical solution of any of the above-mentioned logistics information management methods. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of any of the above-mentioned logistics information management methods.
[0134] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.
[0135] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added or removed according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.
[0136] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.
[0137] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0138] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described herein. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.
Claims
1. A logistics information management system comprising a server and a client, comprising: the server, in response to a package import request submitted by the client, determining at least one import package, obtaining original logistics data corresponding to the at least one import package respectively; performing structural processing on the original logistics data to generate logistics structured data; in response to a logistics information viewing request submitted by the client, determining a classification label; determining a target package corresponding to the classification label in the at least one import package; sending target logistics structured data corresponding to the target package to the client; the client, based on the target logistics structured data corresponding to the target package, generating a logistics information display list corresponding to the classification label, and displaying the logistics information display list on an interactive page, wherein the logistics information display list comprises at least one sub-list, and the sub-list displays the logistics information of the target package corresponding to the label value of the classification label. 2.The logistics information management system of claim 1, wherein the client is further configured to receive a logistics information modification instruction for a package to be modified in the logistics information display list, and send a logistics information modification request carrying information to be modified to the server based on the logistics information modification instruction. The to-be-modified information includes at least one of package label information, package note information, package attribute information, package logistics state information, and package visible range information; The server is further configured to, in response to the logistics information modification request, update the logistics structured data corresponding to the to-be-modified package based on the to-be-modified information, obtain updated logistics structured data, and feed back to the client; The client is further configured to update the logistics information display list based on the updated logistics structured data, wherein the updated logistics information display list displays the updated logistics information of the to-be-modified package.
3. The logistics information management system of claim 1, wherein the client is configured to determine a communication account or a logistics order number, and send a package import request to the server based on the communication account or the logistics order number. The server is configured to, in response to the package import request submitted by the client, determine a target logistics platform associated with the communication account or the logistics order number; determine at least one import package associated with the communication account or the logistics order number in the target logistics platform, and request the target logistics platform to feed back original logistics data corresponding to the at least one import package respectively. 4.The logistics information management system of claim 1, wherein the client is configured to determine a platform account, and send a package import request to the server based on the platform account. The platform account is an e-commerce platform account or a logistics platform account; The server is configured to, in response to the package import request submitted by the client, determine a target platform corresponding to the platform account; request the target platform to feed back target order information corresponding to the platform account, and determine at least one import package and original logistics data corresponding to the at least one import package based on the target order information.
5. The logistics information management system of claim 1, wherein the client is further configured to receive a logistics information record request, determine pick-up information carried in the logistics information record request, and perform an integrity check on the pick-up information. In the case that the pick-up information is incomplete, display prompt information on the interactive page, receive missing information input for the prompt information, update the pick-up information based on the missing information; generate a virtual package and virtual logistics information corresponding to the virtual package based on the updated pick-up information; In the logistics information display list, display the virtual logistics information corresponding to the virtual package. 6.The logistics information management system of claim 1, wherein the client is configured to determine a custom classification label or a target classification label from a preset list, use the custom classification label or the target classification label as a classification label, and send a logistics information viewing request to the server based on the classification label. The server is configured to group target packages based on the classification label in response to the logistics information viewing request submitted by the client, obtain at least one label value and group logistics structured data corresponding to the at least one label value, respectively, combine the group logistics structured data corresponding to the at least one label value into target logistics structured data, and send the target logistics structured data to the client. The classification label is at least one of a logistics platform label, an e-commerce platform label, a logistics status label, a delivery address label, a pickup method label, and a belonging relationship label. 7.A logistics information management method applied to a server, comprising: in response to a package import request submitted by a client, determining at least one imported package, obtaining original logistics data corresponding to the at least one imported package, respectively, structuring the original logistics data, and generating logistics structured data; in response to a logistics information viewing request submitted by the client, determining a classification label, determining target packages corresponding to the classification label in the at least one imported package, and sending target logistics structured data corresponding to the target packages to the client. 8.A logistics information management method applied to a client, comprising: sending a logistics information viewing request to a server, wherein the logistics information viewing request carries a classification label; receiving target logistics structured data corresponding to target packages sent by the server; based on the target logistics structured data corresponding to the target packages, generating a logistics information display list corresponding to the classification label, and displaying the logistics information display list on an interactive page, wherein the logistics information display list includes at least one sub-list, and the sub-list displays logistics information of target packages corresponding to a label value of the classification label. 9.A computing device, comprising: a memory and a processor; the memory is configured to store logistics information management instructions, and the processor is configured to execute the logistics information management instructions, which, when executed by the processor, implement the steps of the method of claim 7 or 8. 10.A computer-readable storage medium storing logistics information management instructions, which, when executed by a processor, implement the steps of the method of claim 7 or 8.