Waybill delivery processing method, device and computing equipment

Abstract

The embodiment of the present invention discloses a waybill delivery processing method, device and computing equipment, the method comprising: receiving a waybill delivery request initiated by a merchant end, querying the delivery resource configuration information corresponding to the merchant end; parsing to obtain a set of capability labels; distributing the waybill delivery request carrying the label data corresponding to each capability label to each service subdomain node, so that each service subdomain node can query the capability label information in the label data according to the service subdomain node information; each service subdomain node executes the delivery service capability corresponding to the capability label information. The present invention standardizes the service capabilities provided by each service subdomain node through the capability label, and then can provide the merchant end with standardized configuration information of the delivery resources through the capability label set, so that the merchant end can use the standardized configuration information to realize the pre-configuration of personalized delivery resources and meet the diverse service needs of the merchant.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of Internet technology, and specifically to a waybill delivery processing method, device, computing equipment, and computer storage medium. Background Art

[0002] Internet services are services that rely on Internet information technology. When facing service users, Internet service platforms usually sell services to service users in the form of service items. However, in the Internet field, Internet services are generally non-standardized service products. Service users need to sign contracts for the required service items according to their own needs. The contract signing method is complicated and it is difficult to meet the diverse needs of service users. In addition, when adding extended service products on the basis of service items, there are problems such as high transformation costs and difficulty in expansion. Summary of the invention

[0003] In view of the above problems, embodiments of the present invention are proposed to provide a waybill delivery processing method, apparatus, computing device, and computer storage medium that overcome the above problems or at least partially solve the above problems.

[0004] According to one aspect of an embodiment of the present invention, a method for processing waybill delivery is provided, comprising:

[0005] Receive the waybill delivery request initiated by the merchant, and query the delivery resource configuration information corresponding to the merchant;

[0006] Parsing the distribution resource configuration information to obtain a capability label set and label data corresponding to each capability label in the capability label set; wherein the label data includes service subdomain node information and capability label information;

[0007] Distribute the waybill delivery request carrying the label data corresponding to each capability label to each service subdomain node, so that each service subdomain node can query the label data to obtain the capability label information according to the service subdomain node information;

[0008] Each service subdomain node executes the delivery service capability corresponding to the capability label information.

[0009] In an optional manner, parsing the distribution resource configuration information to obtain a capability tag set and tag data corresponding to each capability tag in the capability tag set further includes:

[0010] Parsing the distribution resource configuration information to obtain a capability tag set and capability tag information corresponding to each capability tag in the capability tag set;

[0011] The service subdomain node information of the corresponding delivery service capability is queried according to the capability label information to obtain label data.

[0012] In an optional manner, the distribution resource configuration information includes first resource configuration information, and the first resource configuration information includes basic capability tag information corresponding to at least one basic capability tag.

[0013] In an optional manner, the distribution resource configuration information further includes at least one second resource configuration information, and any second resource configuration information includes extended capability tag information corresponding to at least one extended capability tag.

[0014] In an optional manner, the second resource configuration information has a higher priority than the first resource configuration information;

[0015] Any second resource configuration information also includes the delivery resource configuration second resource configuration effective time, and the priority of the second resource configuration with a later effective time is higher than the priority of the second resource configuration with an earlier effective time.

[0016] In an optional manner, parsing the distribution resource configuration information to obtain a capability tag set and tag data corresponding to each capability tag in the capability tag set further includes:

[0017] The distribution resource configuration information is parsed according to priority to obtain a set of capability labels; wherein, for capability labels belonging to the same dimension, the label data corresponding to the capability label corresponding to the distribution resource configuration information with higher priority covers the label data corresponding to the capability label corresponding to the distribution resource configuration information with lower priority.

[0018] In an optional manner, the method further includes:

[0019] Receive a registration request for delivery service capability sent by any service subdomain node;

[0020] The service subdomain node information and capability label information corresponding to the delivery service capability are registered to the registration center.

[0021] According to another aspect of an embodiment of the present invention, a waybill delivery processing device is provided, comprising:

[0022] A query module, used to receive a waybill delivery request initiated by a merchant, and query the delivery resource configuration information corresponding to the merchant;

[0023] A parsing module, used to parse the distribution resource configuration information to obtain a capability label set and label data corresponding to each capability label in the capability label set; wherein the label data includes service subdomain node information and capability label information;

[0024] An execution module is used to distribute the waybill delivery request carrying the label data corresponding to each capability label to each service subdomain node, so that each service subdomain node can query the capability label information in the label data based on the service subdomain node information; each service subdomain node executes the delivery service capability corresponding to the capability label information.

[0025] In an optional manner, the parsing module is further used to:

[0026] Parsing the distribution resource configuration information to obtain a capability tag set and capability tag information corresponding to each capability tag in the capability tag set;

[0027] The service subdomain node information of the corresponding delivery service capability is queried according to the capability label information to obtain label data.

[0028] In an optional manner, the distribution resource configuration information includes first resource configuration information, and the first resource configuration information includes basic capability tag information corresponding to at least one basic capability tag.

[0029] In an optional manner, the distribution resource configuration information further includes at least one second resource configuration information, and any second resource configuration information includes extended capability tag information corresponding to at least one extended capability tag.

[0030] In an optional manner, the second resource configuration information has a higher priority than the first resource configuration information;

[0031] Any second resource configuration information also includes the delivery resource configuration second resource configuration effective time, and the priority of the second resource configuration with a later effective time is higher than the priority of the second resource configuration with an earlier effective time.

[0032] In an optional manner, the parsing module is further used to:

[0033] The distribution resource configuration information is parsed according to priority to obtain a set of capability labels; wherein, for capability labels belonging to the same dimension, the label data corresponding to the capability label corresponding to the distribution resource configuration information with higher priority covers the label data corresponding to the capability label corresponding to the distribution resource configuration information with lower priority.

[0034] In an optional manner, the device further includes: a registration module, configured to receive a registration request for a delivery service capability sent by any service subdomain node; and register the service subdomain node information and capability label information corresponding to the delivery service capability to a registration center.

[0035] According to another aspect of an embodiment of the present invention, there is provided a computing device, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus;

[0036] The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute operations corresponding to the above-mentioned waybill delivery processing method.

[0037] According to another aspect of an embodiment of the present invention, a computer storage medium is provided, wherein the storage medium stores at least one executable instruction, and the executable instruction enables a processor to execute operations corresponding to the above-mentioned waybill delivery processing method.

[0038] According to the waybill delivery processing method and device provided by the embodiment of the present invention, after receiving the waybill delivery request initiated by the merchant end, the queried merchant end corresponding delivery resource configuration information is parsed to obtain a capability tag set and corresponding tag data; the tag data corresponding to each capability tag is encapsulated into the waybill delivery request, and distributed to each service subdomain node, and each service subdomain node executes the delivery service capability corresponding to the capability tag information in its own tag data. The embodiment of the present invention standardizes the service capabilities provided by each service subdomain node through capability tags, and then can provide the merchant end with standardized configuration information of delivery resources through the capability tag set, so that the merchant end can use the standardized configuration information to realize personalized pre-configuration of delivery resources to meet the merchant's diverse service needs. During the waybill delivery process, a set of capability tags is obtained based on the pre-configuration analysis of the merchant side, and the tag data corresponding to each capability tag is encapsulated into the waybill delivery request, and distributed to each service subdomain node, thereby improving the execution efficiency of each service subdomain node in executing the delivery service capability; further, when each service subdomain node needs to expand its service capability, the newly added service capability is registered in the form of a capability tag, realizing capacity expansion in a standardized manner, reducing the transformation cost, and solving the problem of difficulty in expansion.

[0039] The above description is only an overview of the technical solution of the embodiment of the present invention. In order to more clearly understand the technical means of the embodiment of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present invention more obvious and easy to understand, the specific implementation method of the embodiment of the present invention is specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the embodiments of the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0041] Figure 1 A flow chart of a method for processing waybill delivery according to an embodiment of the present invention is shown;

[0042] Figure 2 A schematic diagram showing the composition of distribution resource configuration information according to an embodiment of the present invention is shown;

[0043] Figure 3 A flowchart of a method for processing waybill delivery according to another embodiment of the present invention is shown;

[0044] Figure 4 A schematic diagram of the structure of a waybill delivery processing device provided by an embodiment of the present invention is shown;

[0045] Figure 5 A schematic diagram of the structure of a computing device according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0046] The exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present invention and to enable the scope of the present invention to be fully communicated to those skilled in the art.

[0047] Figure 1 FIG. 4 is a flow chart showing a method for processing a waybill delivery according to an embodiment of the present invention. Figure 1 As shown, the method comprises the following steps:

[0048] Step 101, receiving a waybill delivery request initiated by a merchant, and querying the corresponding delivery resource configuration information of the merchant.

[0049] In an embodiment of the present invention, a service provider (such as an Internet service platform) provides merchants with standardized configuration information of distribution resources when signing a service contract, so that the merchant can use the standardized configuration information to pre-configure personalized distribution resources and obtain a set of capability labels. Among them, the capability label represents a standardized service capability provided by a service subdomain node of the service provider. Taking logistics services as an example, in the diversion capability dimension, there are various types of diversion capabilities such as main carrier diversion and rule diversion. The diversion service subdomain node can register the corresponding diversion capability with the registration center based on the various types of diversion capabilities it can provide. After registration, the registration center records the information of each service subdomain node and the capability label information corresponding to the service capabilities that each service subdomain node can provide, that is, the registration center records the label data corresponding to the capability label.

[0050] When the platform faces merchants, it provides contract services to merchants based on capability tags. Merchants select corresponding capability tags according to their needs and sign service contracts. Service contracts record the distribution resource configuration information, which is essentially a collection of capability tags. During the service performance process, the platform receives the waybill delivery request initiated by the merchant, queries the service contract signed by the merchant, and obtains the distribution resource configuration information of the merchant.

[0051] Step 102, parse the distribution resource configuration information to obtain a capability label set and label data corresponding to each capability label in the capability label set; wherein the label data includes service subdomain node information and capability label information.

[0052] Since the distribution resource configuration information is essentially a set of capability labels, the distribution resource configuration information can be parsed to obtain the set of capability labels and the label data corresponding to each capability label in the set of capability labels. The label data specifically includes service subdomain node information and capability label information. Optionally, the service subdomain node information includes the service subdomain node name and node identifier, and the capability label information includes the capability label name and label identifier.

[0053] Step 103: distribute the waybill delivery request carrying the label data corresponding to each capability label to each service subdomain node, so that each service subdomain node can query the label data to obtain the capability label information according to the service subdomain node information.

[0054] Step 104: Each service subdomain node executes the delivery service capability corresponding to the capability label information.

[0055] In the response process of the waybill delivery request, the waybill delivery request is distributed to each service subdomain node according to the service order (or timing). Each service subdomain node queries its own label data in the capability label set and executes the service capability corresponding to the capability label information in its own label data.

[0056] According to the waybill delivery processing method provided by the embodiment of the present invention, after receiving the waybill delivery request initiated by the merchant end, the queried delivery resource configuration information corresponding to the merchant end is parsed to obtain a capability tag set and corresponding tag data; the tag data corresponding to each capability tag is encapsulated into the waybill delivery request, and distributed to each service subdomain node, and each service subdomain node executes the delivery service capability corresponding to the capability tag information in its own tag data. The embodiment of the present invention standardizes the service capabilities provided by each service subdomain node through capability tags, and then can provide the merchant end with standardized configuration information of delivery resources through the capability tag set, so that the merchant end can use the standardized configuration information to realize personalized pre-configuration of delivery resources and meet the diverse service needs of the merchant end. During the waybill delivery process, a set of capability tags is obtained based on the pre-configuration analysis of the merchant side, and the tag data corresponding to each capability tag is encapsulated into the waybill delivery request, and distributed to each service subdomain node, thereby improving the execution efficiency of each service subdomain node in executing the delivery service capability; further, when each service subdomain node needs to expand its service capability, the newly added service capability is registered in the form of a capability tag, realizing capacity expansion in a standardized manner, reducing the transformation cost, and solving the problem of difficulty in expansion.

[0057] Figure 2 FIG. 2 shows a schematic diagram of the composition of distribution resource configuration information according to an embodiment of the present invention. Figure 2 In the optional implementation shown, an embodiment of the present invention provides merchants with pre-configured services for distribution resources in the form of a package. Optionally, the package can be divided into a basic package and an extended package. The basic package defines a subset of capability labels consisting of capability labels corresponding to all necessary service capabilities in the service process. Merchants can meet some basic service needs by signing a basic package. The extended package defines a more fine-grained subset of capability labels, which serves to expand and supplement the basic package. Merchants can sign various types of extended packages according to their own needs. When a merchant signs a basic package, the first resource configuration information will be generated, and when a merchant signs an extended package, the second resource configuration information will be generated. The second resource configuration information is attached to the first resource configuration information and cannot exist alone. When a merchant signs a basic package and an extended package at the same time, a package package is formed.

[0058] In an optional implementation, the distribution resource configuration information includes first resource configuration information, the first resource configuration information includes basic package information, the basic package information includes basic capability label information corresponding to at least one basic capability label. The distribution resource configuration information also includes at least one second resource configuration information, any second resource configuration information includes extended package information, and the extended package information includes extended capability label information corresponding to at least one extended capability label.

[0059] like Figure 2 As shown, the first resource configuration information further includes one or more of the following information: first resource configuration information id, merchant id, basic package id, effective time and expiration time. The second resource configuration information includes one or more of the following information: second resource configuration information id, associated first resource configuration information id, merchant id, extended package id, effective time and expiration time. Basic package information includes one or more of the following information: package id, package type, package name. Extended package information includes one or more of the following information: package id, package type, package name. Package package information includes one or more of the following information: package package id, package package name. Capability tag information includes: tag id, tag name and tag execution code.

[0060] Optionally, the priority of the second resource configuration information is higher than that of the first resource configuration information, and the priority of the second resource configuration information with a later effective time is higher than that of the second resource configuration information with an earlier effective time. For capability tags belonging to the same dimension, the priority of the resource configuration information determines the priority of the capability tag corresponding to the resource configuration, and each service subdomain node executes the service capability corresponding to the capability tag with a higher priority.

[0061] In order to more clearly describe the specific solution of the embodiment of the present invention, the following embodiment takes logistics service as an example for introduction. It should be understood that the technical solution of the embodiment of the present invention is not limited to logistics service, and any Internet service provided by each service subdomain node is applicable.

[0062] Based on the above description, the logistics service platform sells packages to merchants, and merchants sign basic packages and extended packages that meet their needs through the contract platform (merchants can also only sign basic packages) to generate logistics service contracts. Optionally, before generating a logistics service contract, a contract check is performed. Specifically, based on the merchant's location information, find the geographic area where the merchant is located; check whether the corresponding package is sold in the geographic area; check the transportation coverage of the geographic area; check whether the transportation coverage can meet the merchant's needs, for example, the transportation capacity required by the merchant is dedicated delivery or crowdsourcing.

[0063] Figure 3FIG. 4 is a flow chart showing a method for processing waybill delivery according to another embodiment of the present invention. Figure 3 As shown, the method comprises the following steps:

[0064] Step 301: receiving a waybill delivery request initiated by a merchant, and querying first resource configuration information and second resource configuration information corresponding to the merchant.

[0065] After the merchant completes the above contract, the merchant can initiate a waybill delivery demand based on the service contract. Specifically, the merchant initiates a waybill delivery request to the logistics service platform, and the platform queries the delivery resource configuration information signed by the merchant based on the merchant ID, which optionally includes the first resource configuration information and the second resource configuration information.

[0066] like Figure 2 As shown, both the first resource configuration information and the second resource configuration information include an effective time and an expiration time. When querying, the resource configuration information that is in the effective stage should be queried. In some cases, the merchant side may have signed multiple second resource configurations at different times, and the effective time and expiration time of the multiple second resource configurations are different. When querying, attention should be paid to querying the second resource configuration that is in the effective stage, and excluding the second resource configuration that is in the expiration stage.

[0067] Step 302, parse the second resource configuration information and the first resource configuration information in order from low to high priority, and obtain a capability label set and label data corresponding to each capability label in the capability label set; wherein, for capability labels belonging to the same dimension, the label data corresponding to the capability label corresponding to the distribution resource configuration information with higher priority covers the label data corresponding to the capability label corresponding to the distribution resource configuration information with lower priority.

[0068] Parse the distribution resource configuration information to obtain the capability label set and the capability label information corresponding to each capability label in the capability label set. Query the service subdomain node information that registers the corresponding service capability according to the capability label information to obtain the label data.

[0069] In an optional implementation of the present invention, the distribution resource configuration information is parsed by a label parsing engine. Specifically, the label parsing engine adopts a bus design, and the bus provides slots, and the processing procedures (Procedure) can be plugged in and out as needed. The capability label set is the object to be processed (Container), which is processed by a series of procedures on the bus and finally becomes a finished product and output to the service subdomain node.

[0070] During the parsing process, the distribution resource configuration information is parsed according to the priority to obtain a set of capability labels. Optionally, the label parsing engine can parse the distribution resource configuration information in order from low to high priority. Among them, the priority of the second resource configuration information is higher than the priority of the first resource configuration information, and the priority of the second resource configuration information with a later effective time is higher than the priority of the second resource configuration information with an earlier effective time. For capability labels belonging to the same dimension, the label data corresponding to the capability label corresponding to the distribution resource configuration information with a higher priority overrides the label data corresponding to the capability label corresponding to the distribution resource configuration information with a lower priority.

[0071] For capability labels belonging to the same dimension, the priority of resource configuration information determines the priority of capability labels corresponding to the resource configuration information. For example, strong store-based and weak store-based are capability labels belonging to the standard store-based dimension. Strong store-based means that delivery personnel need to stay in the merchant's store during periods other than the time period for executing delivery tasks, so as to receive the merchant's delivery tasks at any time; weak store-based means that delivery personnel do not need to stay in the merchant's store for a long time. If the capability label set of the merchant's first resource configuration information includes a weak store-based capability label, and the capability label set of the second resource configuration information includes a strong store-based capability label, then when parsing, the label parsing engine first parses the first resource configuration information in order from low to high priority to obtain the weak store-based capability label; then parses the second resource configuration information to obtain the strong store-based capability label. When it is found that strong store-based and weak store-based are capability labels belonging to the same dimension, the label data of the strong store-based label will be overwritten with the label data of the weak store-based label, so that the corresponding service subdomain node can perform the service capability of the strong store-based service.

[0072] Since each service subdomain node has registered the service capabilities it can provide with the registration center in advance, the registration center records the information of each service subdomain node and the capability label information corresponding to the service capabilities that each service subdomain node can provide, that is, the registration center records the label data corresponding to the capability label. In this step, the service subdomain node information that registers the corresponding service capability can be queried according to the capability label information to obtain the label data.

[0073] Optionally, the data structure of the label data output by the label parsing engine can be: {service subdomain node name; service subdomain node code; label name; label execution code}, wherein the service subdomain node code is the identifier of the service subdomain node, and the label execution code is the identifier of the capability label.

[0074] Step 303: distribute the waybill delivery request carrying the label data corresponding to each capability label to each service subdomain node, so that each service subdomain node can query the label data to obtain the capability label information according to the service subdomain node information.

[0075] Step 304: Each service subdomain node executes the delivery service capability corresponding to the capability tag information.

[0076] In the response process of the waybill delivery request, the waybill delivery request flows to each service subdomain node according to the service order (or timing). Each service subdomain node queries its own label data in the capability label set and executes the service capability corresponding to the capability label information in its own label data.

[0077] Specifically, in the response process of the waybill delivery request, the capability tag set is marked on the waybill. When the waybill starts to circulate according to the life cycle, it will be distributed to various service subdomain nodes of the logistics. Any service subdomain node queries whether the capability tag set has the capability tag provided by itself. If so, the tag execution code of the capability tag is obtained, and the code logic corresponding to the tag execution code is executed to execute the corresponding delivery service capability.

[0078] The technical solution of the embodiment of the present invention is introduced below through a specific example.

[0079] User A bought a cup of coffee at merchant B's online store. Merchant B signed a contract with the logistics distribution platform for the resource configuration information of constant temperature delivery in advance. During the fulfillment process, the merchant receives the delivery request initiated by merchant B and queries the resource configuration information signed by merchant B. By parsing the resource configuration information, the delivery capability label set and label data are obtained, and the delivery capability label set and label data are marked in the waybill. When the waybill flows to the diversion service subdomain node, the diversion service subdomain node queries according to the service subdomain node code and finds that there is a label execution code for constant temperature delivery. The diversion service subdomain node executes the code logic corresponding to the label execution code for constant temperature delivery and distributes the waybill to the site with constant temperature delivery capability; then, when the waybill flows to the dispatch service subdomain node, the dispatch service subdomain node queries according to the service subdomain node code and finds that there is a label execution code for constant temperature dispatch. The dispatch service subdomain node executes the code logic corresponding to the label execution code for constant temperature dispatch and dispatches the waybill to the rider with constant temperature delivery capability for delivery.

[0080] Furthermore, the method of the embodiment of the present invention also includes: receiving a registration request for a delivery service capability sent by any service subdomain node; registering the service subdomain node information and capability label information corresponding to the delivery service capability to the registration center. If any service subdomain node has a new delivery service capability, the newly added delivery service capability can be registered by requesting the registration center. After registration, the registration center records the service subdomain node information and the capability label information corresponding to the newly added delivery service capability of the service subdomain node. When a new merchant signs a contract or the original merchant updates the resource configuration, the capability label corresponding to the newly added service capability can be added to the resource configuration information, thereby realizing capacity expansion in a standardized manner, reducing transformation costs, and solving the problem of difficulty in expansion.

[0081] The embodiment of the present invention standardizes the service capabilities provided by each service subdomain node through capability labels, and can provide service contracts to merchants through a set of capability labels, simplifying the contract signing method and meeting the diverse service needs of merchants. When it is necessary to expand service capabilities, the newly added service capabilities are registered in the form of capability labels, realizing capacity expansion in a standardized manner, reducing transformation costs, and solving the problem of difficulty in expansion. This embodiment can parse resource configuration information according to priority, avoiding the problem of contract conflicts for capability labels of the same dimension in different types of resource configuration information, and improving the efficiency of service performance.

[0082] Figure 4 FIG. 2 shows a schematic diagram of the structure of a waybill delivery processing device provided by an embodiment of the present invention. Figure 4 As shown, the device 400 includes: a query module 410, a parsing module 420, and an execution module 430.

[0083] The query module 410 is used to receive a waybill delivery request initiated by a merchant terminal and query the delivery resource configuration information corresponding to the merchant terminal;

[0084] The parsing module 420 is used to parse the distribution resource configuration information to obtain a capability label set and label data corresponding to each capability label in the capability label set; wherein the label data includes service subdomain node information and capability label information;

[0085] The execution module 430 is used to distribute the waybill delivery request carrying the label data corresponding to each capability label to each service subdomain node, so that each service subdomain node can query the capability label information in the label data based on the service subdomain node information; each service subdomain node executes the delivery service capability corresponding to the capability label information.

[0086] In an optional manner, the parsing module 420 is further configured to:

[0087] Parsing the distribution resource configuration information to obtain a capability tag set and capability tag information corresponding to each capability tag in the capability tag set;

[0088] The service subdomain node information of the corresponding delivery service capability is queried according to the capability label information to obtain label data.

[0089] In an optional manner, the distribution resource configuration information includes first resource configuration information, and the first resource configuration information includes basic capability tag information corresponding to at least one basic capability tag.

[0090] In an optional manner, the distribution resource configuration information further includes at least one second resource configuration information, and any second resource configuration information includes extended capability tag information corresponding to at least one extended capability tag.

[0091] In an optional manner, the second resource configuration information has a higher priority than the first resource configuration information;

[0092] Any second resource configuration information also includes the delivery resource configuration second resource configuration effective time, and the priority of the second resource configuration with a later effective time is higher than the priority of the second resource configuration with an earlier effective time.

[0093] In an optional manner, the parsing module 420 is further configured to:

[0094] The distribution resource configuration information is parsed according to priority to obtain a set of capability labels; wherein, for capability labels belonging to the same dimension, the label data corresponding to the capability label corresponding to the distribution resource configuration information with higher priority covers the label data corresponding to the capability label corresponding to the distribution resource configuration information with lower priority.

[0095] In an optional manner, the device further includes: a registration module 440, configured to receive a registration request for a delivery service capability sent by any service subdomain node; and register the service subdomain node information and capability label information corresponding to the delivery service capability to a registration center.

[0096] The description of each module above refers to the corresponding description in the method embodiment and will not be repeated here.

[0097] According to the waybill delivery processing device provided by the embodiment of the present invention, the service capabilities provided by each service subdomain node are standardized through capability labels, and then the standardized configuration information of the delivery resources can be provided to the merchant end through the capability label set, so that the merchant end can use the standardized configuration information to realize the pre-configuration of personalized delivery resources and meet the diverse service needs of the merchant end. In the waybill delivery process, the capability label set is obtained according to the pre-configuration analysis of the merchant end, and the label data corresponding to each capability label is encapsulated into the waybill delivery request and distributed to each service subdomain node, which improves the execution efficiency of each service subdomain node in executing the delivery service capability; further, when each service subdomain node needs to expand the service capability, the newly added service capability is registered in the form of capability label, which realizes the capacity expansion in a standardized form, reduces the transformation cost, and solves the problem of difficulty in expansion.

[0098] An embodiment of the present invention further provides a non-volatile computer storage medium, wherein the computer storage medium stores at least one executable instruction, and the executable instruction can execute the waybill delivery processing method in any of the above method embodiments.

[0099] Figure 5 A schematic diagram of the structure of a computing device according to an embodiment of the present invention is shown, and the specific implementation of the embodiment of the present invention does not limit the specific implementation of the computing device.

[0100] like Figure 5 As shown, the computing device may include: a processor (processor) 502 , a communications interface (Communications Interface) 504 , a memory (memory) 506 , and a communication bus 508 .

[0101] in:

[0102] The processor 502 , the communication interface 504 , and the memory 506 communicate with each other via a communication bus 508 .

[0103] The communication interface 504 is used to communicate with other devices such as clients or other servers.

[0104] The processor 502 is used to execute the program 510, and specifically can execute the relevant steps in the above-mentioned waybill delivery processing method embodiment.

[0105] Specifically, the program 510 may include program codes, which include computer operation instructions.

[0106] The processor 502 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention. The one or more processors included in the computing device may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0107] The memory 506 is used to store the program 510. The memory 506 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0108] The program 510 can be specifically used to enable the processor 502 to execute the waybill delivery processing method in any of the above-mentioned method embodiments. The specific implementation of each step in the program 510 can refer to the corresponding descriptions in the corresponding steps and units in the above-mentioned waybill delivery processing method embodiments, which will not be repeated here. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the above-mentioned devices and modules can refer to the corresponding process description in the above-mentioned method embodiments, which will not be repeated here.

[0109] The algorithm or display provided herein is not inherently related to any particular computer, virtual system or other device. Various general purpose systems can also be used together with the teachings based on this. According to the above description, it is obvious that the structure required for constructing such systems. In addition, the embodiment of the present invention is not directed to any specific programming language either. It should be understood that various programming languages ​​can be utilized to realize the content of the embodiment of the present invention described herein, and the description of the above specific language is to disclose the preferred implementation of the embodiment of the present invention.

[0110] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.

[0111] Similarly, it should be understood that in order to streamline the embodiments of the present invention and to aid in understanding one or more of the various inventive aspects, in the above description of the exemplary embodiments of the present invention, the various features of the embodiments of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, the disclosed method should not be interpreted as reflecting the following intention: that the claimed embodiments of the present invention require more features than the features explicitly recited in each claim. More specifically, as reflected in the claims below, the inventive aspects lie in less than all the features of the single embodiment disclosed above. Therefore, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, wherein each claim itself serves as a separate embodiment of the present invention.

[0112] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and in addition they may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner may be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.

[0113] In addition, those skilled in the art will appreciate that, although some embodiments herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present invention and form different embodiments. For example, in the claims below, any one of the claimed embodiments may be used in any combination.

[0114] The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components according to the embodiments of the present invention. The embodiments of the present invention may also be implemented as a device or apparatus program (e.g., a computer program and a computer program product) for executing part or all of the methods described herein. Such a program implementing an embodiment of the present invention may be stored on a computer-readable medium, or may have the form of one or more signals. Such a signal may be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0115] It should be noted that the above embodiments illustrate rather than limit the present invention, and that those skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets shall not be construed as a limitation on the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention may be implemented by means of hardware comprising a number of different elements and by means of a suitably programmed computer. In a unit claim listing a number of devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.

Claims

1. A waybill delivery processing method, comprising: Receive the waybill delivery request initiated by the merchant, and query the delivery resource configuration information corresponding to the merchant; Parsing the distribution resource configuration information to obtain a capability label set and label data corresponding to each capability label in the capability label set; wherein the label data includes service subdomain node information and capability label information; Distribute the waybill delivery request carrying the label data corresponding to each capability label to each service subdomain node, so that each service subdomain node can query the label data to obtain the capability label information according to the service subdomain node information; Each service subdomain node executes the delivery service capability corresponding to the capability label information.

2. The method according to claim 1, wherein: The parsing of the distribution resource configuration information to obtain a capability tag set and tag data corresponding to each capability tag in the capability tag set further includes: Parsing the distribution resource configuration information to obtain a capability tag set and capability tag information corresponding to each capability tag in the capability tag set; The service subdomain node information of the corresponding delivery service capability is queried according to the capability label information to obtain label data.

3. The method according to claim 1 or 2, wherein: The distribution resource configuration information includes first resource configuration information, and the first resource configuration information includes basic capability label information corresponding to at least one basic capability label.

4. The method according to claim 3, wherein: The distribution resource configuration information further includes at least one second resource configuration information, and any second resource configuration information includes at least one extended capability tag information corresponding to the extended capability tag.

5. The method according to claim 4, wherein: The priority of the second resource configuration information is higher than that of the first resource configuration information; Any second resource configuration information also includes the delivery resource configuration second resource configuration effective time, and the priority of the second resource configuration with a later effective time is higher than the priority of the second resource configuration with an earlier effective time.

6. The method according to claim 1 or 2, wherein: The parsing of the distribution resource configuration information to obtain a capability tag set and tag data corresponding to each capability tag in the capability tag set further includes: The distribution resource configuration information is parsed according to priority to obtain a set of capability labels; wherein, for capability labels belonging to the same dimension, the label data corresponding to the capability label corresponding to the distribution resource configuration information with higher priority covers the label data corresponding to the capability label corresponding to the distribution resource configuration information with lower priority.

7. The method according to claim 1 or 2, wherein: The method further comprises: Receive a registration request for delivery service capability sent by any service subdomain node; The service subdomain node information and capability label information corresponding to the delivery service capability are registered to the registration center.

8. A waybill delivery processing device, comprising: A query module, used to receive a waybill delivery request initiated by a merchant, and query the delivery resource configuration information corresponding to the merchant; A parsing module, used to parse the distribution resource configuration information to obtain a capability label set and label data corresponding to each capability label in the capability label set; wherein the label data includes service subdomain node information and capability label information; An execution module is used to distribute the waybill delivery request carrying the label data corresponding to each capability label to each service subdomain node, so that each service subdomain node can query the capability label information in the label data according to the service subdomain node information; each service subdomain node executes the delivery service capability corresponding to the capability label information.

9. The device according to claim 8, wherein: The parsing module is further used for: Parsing the distribution resource configuration information to obtain a capability tag set and capability tag information corresponding to each capability tag in the capability tag set; The service subdomain node information of the corresponding delivery service capability is queried according to the capability label information to obtain label data.

10. The device according to claim 8 or 9, wherein: The distribution resource configuration information includes first resource configuration information, and the first resource configuration information includes basic capability label information corresponding to at least one basic capability label.

11. The device according to claim 10, wherein: The distribution resource configuration information further includes at least one second resource configuration information, and any second resource configuration information includes at least one extended capability tag information corresponding to the extended capability tag.

12. The device according to claim 11, wherein: The priority of the second resource configuration information is higher than that of the first resource configuration information; Any second resource configuration information also includes the delivery resource configuration second resource configuration effective time, and the priority of the second resource configuration with a later effective time is higher than the priority of the second resource configuration with an earlier effective time.

13. The device according to claim 8 or 9, wherein: The parsing module is further used for: The distribution resource configuration information is parsed according to priority to obtain a set of capability labels; wherein, for capability labels belonging to the same dimension, the label data corresponding to the capability label corresponding to the distribution resource configuration information with higher priority covers the label data corresponding to the capability label corresponding to the distribution resource configuration information with lower priority.

14. The device according to claim 8 or 9, wherein: The device also includes: a registration module, which is used to receive a registration request for a distribution service capability sent by any service subdomain node; and register the service subdomain node information and capability label information corresponding to the distribution service capability to a registration center.

15. A computing device comprising: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the waybill delivery processing method as described in any one of claims 1-7.

16. A computer storage medium, wherein at least one executable instruction is stored in the storage medium, and the executable instruction enables a processor to execute operations corresponding to the waybill delivery processing method according to any one of claims 1 to 7.

Images