CN115396467A

CN115396467A - Method, system, storage medium and equipment for constructing open logistics system enabling system

Info

Publication number: CN115396467A
Application number: CN202210892173.3A
Authority: CN
Inventors: 刘卫宁; 郑林江; 孙棣华
Original assignee: Chongqing University
Current assignee: Chongqing University
Priority date: 2022-07-27
Filing date: 2022-07-27
Publication date: 2022-11-25
Anticipated expiration: 2042-07-27
Also published as: CN115396467B

Abstract

The invention discloses a method, a system, a storage medium and equipment for constructing an open logistics system enabling system, and provides the method for constructing the open logistics system enabling system based on the latest open logistics system theory, CPS and RFID technology. The enabling system constructed by the method can be used as an upper layer system of the original logistics system, and the system supports real-time tracking of materials across a logistics system and interconnection and intercommunication of logistics services on the upper layer. Through the enabling of the enabling system, the original logistics system can have agility characteristics under the condition that the normal operation of the original logistics system is not influenced.

Description

Method, system, storage medium and equipment for constructing open logistics system enabling system

Technical Field

The invention relates to the field of logistics transportation, in particular to a method, a system, a storage medium and equipment for constructing an enabling system of an open logistics system.

Background

At present, all links of logistics transportation in China are not integrated, all systems are relatively independent and limited to internal vertical operation, parallel connection among the systems is few, and the whole logistics is in a separated linear guarantee state.

For example, the warehouse of the emergency logistics usually belongs to different departments, and is only responsible for guaranteeing the requirements of the department in the same guarantee area, and a vertical tree structure guarantee mode is implemented, so that the rear warehouse is in cross overlapping construction in the same area, and the overall coordination program among all the departments is complex, thereby greatly restricting the comprehensive guarantee capability of the rear warehouse.

In order to cope with the above problems, logistics informatization construction is indispensable. However, logistics informatization construction is limited to construction and purchase problems of facility equipment, the purposes of information communication and information sharing cannot be achieved comprehensively, the informatization mechanism construction and the information technology application are not perfect and popularized enough, and the software foundation of informatization construction is not firm enough, so that the informatization, the information communication and the information sharing cannot support the accuracy of emergency logistics guarantee.

Disclosure of Invention

The invention aims to provide a method for constructing an open logistics system enabling system, wherein the open logistics system enabling system is a distributed system and comprises a root server and a data center station which are arranged in a management universe, sub-servers arranged in management subdomains at all levels, an internal communication network, an external communication network and an edge intelligent terminal;

the management universe is provided with a root server and used for managing all the sub servers and the edge intelligent terminals;

the management universe comprises a plurality of levels of management subdomains; wherein the number of the kth level management subdomains is marked as I _k ；I _k K is a natural number;

the management subdomain is used for managing the material entity label information and the standard events of the subordinate management subdomain;

a kth level management subdomain comprises a kth level node and a plurality of (k + 1) th level nodes;

each kth-level management sub-domain is provided with a kth-level sub-server;

the kth-level sub server respectively carries out data interaction with the upper-level sub server and the lower-level sub server through an internal communication network;

the sub server comprises an application server and a storage server; the application server is used for realizing data query, processing and statistics; the storage server is used for storing data;

when the k value is maximum, the kth level management sub-domain comprises a plurality of bottom layer nodes, the bottom layer nodes store a plurality of material entities attached with labels, and the level management sub-domain carries a plurality of edge intelligent terminals; the bottom layer node corresponds to the edge intelligent terminal;

the edge intelligent terminal is connected with the external read-write equipment and the logistics system, so that the connection between the external logistics system and the open logistics system enabling system is established;

the external read-write equipment is used for scanning the label of the material entity so as to obtain the label information of the material entity; the external read-write equipment performs data interaction with the edge intelligent terminal through an internal communication network; the internal communication network can be a network with better safety, such as an internal local area network;

the management universe comprises a general node, all sub-nodes and a bottom layer node;

the management universe is provided with a data middlebox and a data root server; the data center station performs data interaction with any sub-server and any edge intelligent terminal through an external communication network; the external communication network comprises the Internet or a wireless network, and can be an open network with lower security, such as the Internet and the wireless network;

the root server performs data interaction with the sub-servers through an internal communication network, so that cross-subdomain query and data sharing are realized;

the root server comprises an application root server and a storage root server; the application root server is used for realizing data query, processing and statistics; the storage root server is used for storing data;

the construction method of the open logistics system enabling system comprises the steps of establishing information coding and storing methods and information inquiring methods;

the information coding and storing method comprises the following steps:

setting a label on a material entity, wherein the label stores label information of the material entity; the material entity label information comprises coding information of a material entity; when the material entity is in a logistics transportation stage, the label information of the material entity also comprises delivery address information for logistics transportation;

the detailed information of the material entity is stored in the sub-server of the level to which the node belongs when the entity is created, and comprises supplier codes of the material entity, codes of the supplier to the material entity, and static attribute information of the material entity;

after the material entity triggers the standard event, the external read-write equipment collects label information of the material entity, and uploads the standard event, the label information of the material entity and the position information which are triggered by the material entity to the corresponding edge intelligent terminal, and the edge intelligent terminal uploads the standard event, the label information of the material entity and the position information to a data center station through an external communication network; the position information comprises a node code where the edge intelligent terminal is located and an upper layer node code where the node belongs;

the standard event type comprises a material entity generation elimination event, a material entity ownership change event and an entity tracking event;

the matter entity generation elimination events comprise matter entity generation events, matter entity combination events, matter entity disassembly events and matter entity elimination events;

the material entity ownership change events comprise material entity transfer-in events and material entity transfer-out events;

the entity tracking type event comprises a material entity in-transit tracking event;

the tasks completed by the edge intelligent terminal comprise 1) processing a standard event from an external read-write device to form an event message, and uploading the event message to a superior sub-server and a data center; 2) Processing the material detail query service from the external read-write equipment, and returning a query result;

the edge intelligent terminal comprises a first network channel connected with an internal communication network and a second network channel connected with an external communication network;

the edge intelligent terminal performs data interaction with other servers through a first network channel and reports an event message to a top-level sub-server of the local domain through a second network channel;

the edge intelligent terminal generates a static data message according to the label information and the position information of the material entity, and uploads the static data message to the upper-level sub-server through a first network channel for storage; the sub-server receiving the static data message uploads the static data message hierarchy to a root server by using an intranet to be stored;

the information query method comprises a method for performing information query through a sub-node and a method for performing information query through a general node, wherein query contents comprise entity detail query and entity comprehensive information query;

the entity detail query refers to querying the supplier code of the entity, the code of the supplier on the material entity and the static attribute information of the material entity according to the entity code;

when entity detail inquiry is carried out, a request side initiates an inquiry request to a subdomain server of a local domain;

the entity comprehensive information query refers to the statistical query of entities according to classes, positions and the like;

when entity comprehensive information inquiry is carried out, a request party initiates an inquiry request to a master node, and after receiving the inquiry request, the master node inquires a dynamic and static message according to the authority of the request initiator and provides inquiry service for the request party in a micro-service mode;

for the entity detail query request, the subdomain application server queries a local domain storage server according to the entity code, and returns the entity details after the query is found; if not, transmitting the request to the root server;

after receiving the query request result returned by the root server, the subdomain application server returns the result to the query requester, and meanwhile, the subdomain application server stores the query request result in the local domain storage server for future reference.

Further, the bottom layer nodes are material storage and transfer points and comprise warehouse nodes, distribution centers, material collection nodes and transporter nodes; when the bottom node is a carrier node, the position information further includes real-time geographical position information of the carrier acquired through a global satellite positioning system.

Further, the material entity comprises articles and a box loaded with a plurality of articles;

when a plurality of articles form a new box body, generating a new label and pasting the label on the box body; the label carries material entity coding information;

the material entity coding information comprises a box body, a small box body inside the box body and codes of articles inside the box body;

the entity packaging state comprises a box body, a small box body inside the box body and the packaging state of articles inside the box body; the packing state includes independent and packed.

Further, when a large box body is disassembled into a plurality of small box bodies, if the small box bodies have labels, no new label is generated, and if the small box bodies are not pasted with the labels, a new label is generated and pasted on the corresponding box body.

Further, the data message comprises a message number, an event type, an event code, material entity code information, a node code and an object code list which is combined or disassembled;

when the standard event type is an entity tracking type event, the data message further comprises position information.

The goods and materials entity code information comprises supplier codes of goods and materials entities and static attribute information codes of the goods and materials entities; the static attribute information of the material entity comprises a name, a classification, a quantity, a delivery period and an effective period; one type of event includes a plurality of events, each event having an event code.

Further, the goods and materials entity generation event comprises goods and materials entity warehousing from a supplier;

the material entity combination event comprises material entity boxing and packaging;

the material entity disassembling event comprises material entity unpacking and unpacking;

the material entity transfer-out event comprises the step of delivering a material entity out of the warehouse;

the material entity transfer event comprises the step of putting material entities from other bottom layer nodes into a warehouse;

the material entity elimination event comprises that the material entity is invalid and is used.

Furthermore, the message number, the event code, the event type, the material entity code information and the node code corresponding to each material entity have a mapping relation.

Further, the label comprises a bar code label, a two-dimensional code label and an RFID label.

Further, the node is also provided with an interactive platform for accessing the access of the user.

Furthermore, the bottom layer node, the sub-nodes, the total node and the material entity all have unique coding information.

Further, the data center also stores a transportation network; the transportation network comprises sub-nodes, transportation equipment and transportation lines provided by a main node, and transportation equipment and transportation lines provided by a third-party logistics service party;

further, the application server also provides transportation information visualization service; and the application server calls the transport network stored in the data and the position information of the material entity in the transport process, and displays the position information in the map.

An open logistics system enabling system is a distributed system and comprises a root server and a data center station which are arranged in a management universe, sub servers arranged in management subdomains of all levels, an internal communication network, an external communication network, network security equipment, network switching equipment and an edge intelligent terminal;

the external read-write equipment is used for scanning the material entity label and transmitting the scanned material entity label information to the edge intelligent terminal through the internal communication network;

the tasks completed by the edge intelligent terminal comprise 1) processing a standard event from external read-write equipment to form an event message, and uploading the event message to a superior sub-server and a data center station; 2) Processing the material detail query service from the external read-write equipment, and returning a query result;

the edge intelligent terminal generates a static data message according to the label information and the position information of the material entity, and uploads the static data message to the upper-level sub-server for storage; the sub server which receives the static data message uploads the static data message hierarchy to a root server for storage;

the network safety equipment is used for realizing safety isolation and information exchange among different internal communication networks, the internal communication networks and external communication networks;

the network switching equipment comprises routers deployed in management subdomains at all levels and switches deployed in data terminals;

the router is used for connecting an external network and a neutral area network; the neutral area network is used for safely transferring data between an internal network and an external network;

the switch is used for network communication of the neutral zone workstation and the server.

Further, the storage server stores a plurality of information bases for storing data;

the information base comprises a material entity attribute base, a supplier information base, a carrier information base, a node information base, an event report base, an on-the-road tracking information base and a material entity state base;

the material entity attribute library is used for storing material entity attribute information;

the supplier information base is used for storing supplier information of the material entity, and the supplier information comprises supplier codes, names, addresses and contact ways;

the carrier information base is used for storing carrier information of the material entity, and comprises a carrier code, a name, an address and a contact way;

the node information base is used for storing node information, including node codes, names, superior node codes with a main relationship and position information;

the event report library is used for storing the report data uploaded by the lower node;

the on-the-way tracking information base is used for storing the position information of the on-the-way material entity;

the material entity state library is used for storing material dynamic state information, and the material dynamic state information comprises unique codes, suppliers, supplier codes, product names, types, quantities, production dates, expiration dates, storage requirements and transportation requirements; entity type, entity packing state, contained entity object list, located node, valid state and deletion mark.

Further, the material entity state library also stores information generated by entity combination events, wherein the information comprises an entity packaging state and an object containing list;

the entity packing state information comprises a box body, a small box body inside the box body and the packing state of articles inside the box body; the packaged state includes both individual and packaged.

A computer-readable storage medium having stored thereon a computer program, comprising: which program, when being executed by a processor, is arranged to carry out the steps of the method as described above.

An apparatus of an open logistics architecture enabled system, comprising a memory for storing computer program instructions and a processor for executing the computer program instructions;

wherein the computer program instructions, when executed by the processor, cause the apparatus to perform the steps of the method as described above.

The technical effect of the invention is undoubtedly that the invention provides a method for constructing an open logistics system enabling system based on the latest open logistics system (PI: physical Internet) theory, CPS (Cyber Physical Systems ) and RFID (Radio Frequency Identification) technology, and the open logistics system enabling system constructed by the method realizes management, organization and allocation of cross-organization and cross-system materials in an open, safe and flexible way under the open system and environment with minimum cost (minimum modification to the existing system, minimum dependence on the existing system and minimum mutual interference between Systems).

The enabling system constructed by the method can be used as an upper layer system of the original logistics system, and the system supports real-time tracking of materials of a cross-logistics system and interconnection and intercommunication of logistics services of the upper layer. Through enabling of the enabling system, the original logistics system can have agile characteristics under the condition that the normal operation of the original logistics system is not influenced.

The invention manages material and transport resources (quantity, state and position) as minimum units, tracks the positions of the minimum units, conducts material financing and logistics organization on the upper layer based on the minimum units, breaks through segmentation of strips through the flattened data management, and breaks through the bottleneck of cross-system data sharing.

The invention tracks the material dynamics based on the RFID technology, manages the material, standardizes the key operation of logistics nodes such as warehouses, distribution centers and the like, embeds standard event triggers to generate corresponding event messages, and acquires the dynamic change of the material. By the patching mode, the condition of materials is mastered, and the change to the existing service system is minimum. The invention constructs an agile emergency logistics enabling system and realizes the dynamic tracking of material financing and material state of a cross-logistics platform.

The invention makes full use of social logistics resources and puts the materials to be transported into a standardized and modularized packing box for transportation. The packaging box is equivalent to a data packet in the digital Internet in a PI (Physical Internet) and encapsulates the contents of goods transported by the packaging box, so that the contents are independent of the PI, and the protection of goods information carried by the packaging box is facilitated. Corresponding to the digital internet, the PI can be regarded as a logistics network, the movement of the packing box in the PI is similar to the flow of the data packet in the digital internet, the unique global identifier of the PI is equivalent to the MAC Address (local area network Address) in the ethernet and the digital internet, and the PI can be used as a proxy for the PI to realize distributed automation operations such as various processing, storage, routing and the like. The information part of the packing box is similar to the header of a data packet in the digital Internet, and the transportation layer can combine a plurality of packing boxes and plan routing according to the header information, flexibly organize logistics transportation and deliver material entities to destinations.

The information entity fusion system based on multi-code fusion realizes the unified management of multi-source materials of different suppliers, the real-time acquisition and safe transmission of asset flow data and the real-time tracking of asset states; the invention realizes the visualization and statistical analysis of the distribution and the state of the material and the logistics assets, supports the multidimensional query list according to the region, the position and the range, the node (warehouse, distribution center, etc.), the state, and the like, and supports the hierarchical emergency logistics scheduling.

The agile emergency logistics scheduling system is independent of the existing business system, and realizes digitization of logistics elements, automation of data acquisition, data exchange and service standardization and emergency logistics management globalization without changing the existing management business process of an enterprise. The invention realizes the digital management of the material entities, suppliers, carriers, nodes and other elements by researching the multi-code fusion system and the management of the CES information resource library, and lays a data foundation for agile emergency logistics scheduling.

According to the invention, through researching a CES system framework, a material entity and a related information return passage in a logistics scheduling process are formed by utilizing root service, branch service (multi-level sub-service), edge service and a client, so that the automation of material entity and logistics information acquisition is realized. The invention realizes the standardization of the state change information of the material entity by the standard definition of the key operation event in the logistics scheduling process, and returns the information to the data center through the standard message. Meanwhile, the information service system of the data center and the micro-service architecture provides expandable, customizable, highly available and easily maintained standard application service for the upper-layer application. Based on the logistics element digitization, the data acquisition automation, the data exchange and the service standardization, the application system researched by the system can provide global material and transportation resource conditions for decision makers and managers, and support global scheduling management such as material financing, allocation, transportation organization and the like.

Drawings

FIG. 1 is an integral frame; FIG. 2 is a coding structure of a military article uniquely identifying a 2 nd coding format; FIG. 3 is a mapping relationship of a multi-coding fusion system; fig. 4 shows a CES information resource pool (CES-IR). FIG. 5 (a) is an example of a nested relationship expression for material entities; FIG. 5 (b) is an example of a nested relationship expression for material entities;

FIG. 6 is a CES (Cyber Entity Systems) system architecture; FIG. 7 shows a change in CES-IR (Cyber Entity Systems-Information resources) data records based on a generated Entity event message; fig. 8 shows CES-IR data record changes based on a combined entity event message; fig. 9 shows CES-IR data record changes based on a disassembled entity event message; fig. 10 shows CES-IR data record changes based on an elimination entity event message;

fig. 11 shows the change of CES-IR data records based on the transfer-in entity event message; fig. 12 shows CES-IR data record changes based on roll-out entity event messages; FIG. 13 is a graph of CES-IR data record changes based on an in-transit trace event message; fig. 14 is a view of a CES coding resolution service architecture; FIG. 15 is a schematic diagram of an open logistics system enabling system architecture I; fig. 16 is a schematic diagram II of an open logistics system enabling system architecture.

Detailed Description

The present invention is further illustrated by the following examples, but it should not be construed that the scope of the above-described subject matter is limited to the following examples. Various substitutions and alterations can be made without departing from the technical idea of the invention and the scope of the invention is covered by the present invention according to the common technical knowledge and the conventional means in the field.

Example 1:

referring to fig. 1 to 16, a method for constructing an open logistics system enabling system, which is a distributed system, includes a root server and a data center station which are set up in a management universe, sub-servers which are set up in management subdomains of each level, an internal communication network, an external communication network, and an edge intelligent terminal;

the enabling system is constructed in a tree structure, a universe domain and a subordinate sub domain are set according to an organizational structure, and the sub domain is set below the sub domain. The subdomains manage unique codes and events of entities in each domain, and the root server is responsible for cross-subdomain query and data sharing.

The management universe is provided with a root server and is used for managing all the sub servers and the edge intelligent terminals; the management universe comprises a plurality of levels of management subdomains; wherein the number of the kth level management subdomains is marked as I _k ；I _k K is a natural number;

the management sub-domain is used for managing the material entity label information and the standard event of the subordinate management sub-domain;

each kth level management subdomain is provided with a kth level sub-server;

when the k value is maximum, the kth level management sub-domain is a bottommost level management sub-domain and comprises a plurality of bottom level nodes, the bottom level nodes store a plurality of material entities attached with labels, and the level management sub-domain carries a plurality of edge intelligent terminals; the bottom layer node corresponds to the edge intelligent terminal;

the construction method of the open logistics system enabling system comprises the steps of establishing information coding and storage and information query;

the information coding and storing method comprises the following steps:

after the material entity triggers the standard event, the external read-write equipment collects label information of the material entity, and uploads the standard event, the label information of the material entity and the position information which are triggered by the material entity to the corresponding edge intelligent terminal, and the edge intelligent terminal uploads the standard event, the label information of the material entity and the position information to a data center station through an external communication network; the position information comprises a node code of the edge intelligent terminal and an upper layer node code of the node;

the method comprises the following steps that the elimination events generated by the material entities comprise material entity generation events, material entity combination events, material entity disassembly events and material entity elimination events;

the edge intelligent terminal generates a static data message according to the label information and the position information of the material entity, and uploads the static data message to the upper-level sub-server through a first network channel for storage; the sub-server receiving the static data message uploads the static data message hierarchy to a root server by using an internal network for storage;

after receiving the query request result returned by the root server, the subdomain application server returns the result to the side who provides the query request, and meanwhile, the subdomain application server stores the query request result in the local storage server for future reference.

The bottom layer nodes are material storage and transfer points and comprise warehouse nodes, distribution centers, material collection nodes and transporter nodes; when the bottom node is a carrier node, the position information further includes real-time geographical position information of the carrier acquired through a global satellite positioning system.

The material entity comprises articles and a box body loaded with a plurality of articles;

the entity packaging state comprises a box body, a small box body in the box body and the packaging state of articles in the box body; the packing state includes independent and packed.

When a large box body is split into a plurality of small box bodies, if the small box bodies have labels, no new label is generated, and if the small box bodies are not pasted with the labels, a new label is generated and pasted on the corresponding box body.

The data message comprises a message number, an event type, an event code, material entity code information, a node code and an object code list which is combined or disassembled;

The goods and materials entity code information comprises supplier codes of goods and materials entities and static attribute information codes of the goods and materials entities; the static attribute information of the material entity comprises name, classification, quantity, delivery date and validity period; one type of event includes a plurality of events, each event having an event code.

The goods and materials entity generating event comprises warehousing of goods and materials entities from a supplier;

the material entity transfer event comprises material entity storage from other bottom layer nodes;

the material entity elimination event comprises failure and use of the material entity.

The message number, the event code, the event type, the material entity code information and the node code corresponding to each material entity have a mapping relation.

The label comprises a bar code label, a two-dimensional code label and an RFID label.

The node is also provided with an interactive platform for accessing the access of the user.

The bottom layer nodes, the sub nodes, the total nodes and the material entities all have unique coding information.

The data center also stores a transportation network; the transportation network comprises transportation equipment and transportation lines provided by branch nodes and a main node, and transportation equipment and transportation lines provided by a third-party logistics service party;

the application server also provides transportation information visualization service; and the application server calls the position information of the transport network and the material entity stored in the data in the transport process and displays the position information in the map.

An open logistics system enabling system is a distributed system and comprises a root server and a data center station which are arranged in a management universe, sub-servers arranged in management subdomains at all levels, an internal communication network, an external communication network, network safety equipment, network switching equipment and an edge intelligent terminal;

the edge intelligent terminal generates a static data message according to the label information and the position information of the material entity, and uploads the static data message to the upper-level sub-server for storage; the sub-servers receiving the static data messages upload the static data message levels to a root server for storage;

The storage server stores a plurality of information bases for storing data;

the information base comprises a material entity attribute base, a supplier information base, a carrier information base, a node information base, an event report base, an on-the-way tracking information base and a material entity state base;

the event report library is used for storing the message data uploaded by the lower node;

The material entity state library also stores information generated by entity combination events, wherein the information comprises an entity packaging state and an object containing list;

A computer-readable storage medium having stored thereon a computer program, comprising: which when executed by a processor implements the steps of the method described above.

wherein the computer program instructions, when executed by the processor, cause the apparatus to perform the steps of the method described above.

Example 2:

The storage server stores a plurality of information bases for storing data;

the node information base is used for storing node information which comprises node codes, names, superior node codes with a main attribute relationship and position information;

the entity packing state information comprises a box body, a small box body inside the box body and the packing state of articles inside the box body; the packing state includes independent and packed.

The step of scheduling the material entity comprises:

1) Receiving a logistics scheduling request by a kth level node or a master node, and transmitting the logistics scheduling request to a data center station;

if the logistics scheduling request comes from the kth level node, the kth level sub-server of the data center station receives the logistics scheduling request; if the logistics scheduling request comes from the master node, a root server of the data center station receives the logistics scheduling request;

2) When the kth-level sub-server receives a logistics scheduling request, the kth-level sub-server matches the material entity type in the logistics scheduling request with the material entity type in the information base of the kth-level sub-server;

if the material entities of the same type exist, generating a logistics scheduling task according to the bottom node codes corresponding to the material entities; if the material entity of the same type does not exist, uploading the logistics scheduling request hierarchy until the material entity of the same type is matched, and generating a logistics scheduling task by a server storing the material entity data of the type according to a bottom node code corresponding to the material entity;

the logistics scheduling task comprises material entity types, required quantity, destinations and time limits;

when the root server receives the logistics scheduling request, the root server matches the material entity type in the logistics scheduling request with the material entity type in the information base of the root server, if the material entities of the same type exist, a logistics scheduling task is generated according to the bottom node code corresponding to the material entities, and the step 3 is carried out; if the same type of material entities do not exist, feeding back the lack result of the material entities to the total node, and ending;

3) The data center station issues the logistics scheduling task level to a bottom node corresponding to the bottom node code;

4) And after receiving the logistics scheduling task, the bottom layer node executes a material entity combination event or a material entity disassembly event on the material entities according to the quantity required by the material entities, thereby obtaining the material entities corresponding to the quantity required by the material entities, and delivering the material entities to a destination.

The open logistics system enabling system is constructed based on the latest open logistics system theory, CPS and RFID technology, and management, organization and allocation of cross-organization and cross-system materials are achieved in an open, safe and flexible mode under the open system and environment with the minimum cost (minimum modification to the existing system, minimum dependence on the existing system and minimum mutual interference among systems).

The open logistics system enabling system is an upper-layer system of the existing logistics system, supports real-time tracking of materials of a cross-logistics system and interconnection and intercommunication of logistics services of the upper layer, and can enable the original logistics system to have agility characteristics under the condition that normal operation of the original logistics system is not influenced through enabling of the enabling system.

Example 3:

a computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method.

Example 4:

Example 5:

a computer terminal is used for providing a human-computer interaction interface, wherein the human-computer interaction interface comprises at least one first control and at least one second control;

the first control is used for displaying data of a material entity corresponding to the first control;

the second control is used for receiving a trigger instruction and controlling the switching between the at least one first control according to the trigger instruction.

Example 6:

an open logistics system enabling system construction method is a distributed system and comprises a root server and a data center station which are arranged in a management universe, sub servers arranged in management subdomains at all levels, an internal communication network, an external communication network and an edge intelligent terminal;

each kth level management subdomain is provided with a kth level sub-server;

the kth-level sub-server respectively performs data interaction with the previous-level sub-server and the next-level sub-server through an internal communication network;

when the k value is maximum, the kth level management sub-domain comprises a plurality of bottom layer nodes, the bottom layer nodes store a plurality of labeled material entities, and the level management sub-domain carries a plurality of edge intelligent terminals; the bottom layer node corresponds to the edge intelligent terminal;

the information coding and storing method comprises the following steps:

when entity detail inquiry is carried out, a request party initiates an inquiry request to a subdomain server of a local domain;

when entity comprehensive information is inquired, a request side initiates an inquiry request to a master node, and after receiving the inquiry request, the master node inquires a dynamic and static message according to the authority of the request initiator and provides inquiry service to the request side in a micro-service mode;

The goods and materials entity coding information comprises supplier codes of goods and materials entities and static attribute information codes of the goods and materials entities; the static attribute information of the material entity comprises name, classification, quantity, delivery date and validity period; one type of event includes a plurality of events, each event having an event code.

the material entity transfer-out event comprises the step of delivering the material entity out of the warehouse;

And the node is also provided with an interactive platform for accessing the access of the user.

The bottom layer node, the sub-nodes, the total node and the material entity all have unique coding information.

the application server also provides transportation information visualization service; and the application server calls the transport network stored in the data and the position information of the material entity in the transport process, and displays the position information in the map.

Example 7:

the open logistics system enables a system, which is generated based on a physical internet architecture.

The Physical Internet (PI) packages commodities in intelligent, environment-friendly and modular packing boxes, which are different from the smallest packing boxes to shipping containers and can be stacked. The physical internet PI encloses goods in a packaging box, hereinafter referred to as PI-container. These pi-containers are globally standard, smart, green, modular packaging boxes that are modular and standardized worldwide in terms of size, function, and fixtures. PI-containers are a key element to achieve the interoperability necessary for physical internet PI operations. They are equivalent in PI to packets in the digital internet. Their information parts are similar to the headers of data packets in the digital internet. The PI container encapsulates the contents of the goods transported by the PI container, so that the contents are irrelevant to the PI, and the protection of the information of the transported goods is more facilitated. Each pi-container has a unique global identifier that is equivalent to the MAC address in ethernet and digital internet. To ensure the robustness and validity of the identification, the identifier is physically and numerically appended to each pi-container. The intelligent identification can be used as a proxy of each PI-container in PI to realize distributed automation operations such as various processing, storage, routing and the like. Meanwhile, the intelligent identification of each pi-container can improve the decision-making capability of logistics operation management by using the real-time information of interconnected multiple parties, multiple stages and multiple logistics processes.

In contrast to the digital internet, a PI can be viewed as a logistics network that uses PI movers (e.g., forklifts or trucks) to handle, transport, and store PI-containers via PI-nodes (e.g., factories, warehouses, distribution centers, etc.) and standard PI protocols to accomplish logistics services.

The open logistics system enables the system architecture to be independent of the existing management organization architecture and the business information system, global domain materials and capacity resource conditions (quantity, state and position) are mastered from the bottom layer, global materials and capacity resources are managed based on the resource state data, global material visualization is achieved, and global material planning and logistics organization are supported. Therefore, the material financing and logistics organization is more open and flexible.

A schematic diagram of an open logistics system enabling system architecture is shown in fig. 15. Deploying the system at a node (node) of a warehouse/distribution center and the like belonging to the universe range implemented by the open logistics system enabling system:

all nodes, materials and transportation resources entering the system management domain need a material and transportation inventory and code assignment (uniform unique coding) process.

The key operation of the nodes is standardized, and some standard events are added. The events support the current service system of the node, and simultaneously, an event message is automatically uploaded to the data center station through the CES system, and the state and the position information of the material entity are reported.

A CES (information entity fusion system) system is the core of an open logistics system enabled system. An automatic acquisition, separation/fusion and sharing architecture based on bottom entity attribute information and entity transition information is constructed by internet thinking, and the dynamic tracking of material financing and material state of a cross-logistics platform is realized. The system can operate independently of existing asset management systems and logistics systems.

When the material entity enters the system management domain, the original supplier material code on the material entity needs to be read, and then a uniform unique code is given to the material entity by the multi-code fusion system. The code is valid for the full life cycle within the present administrative domain.

The multi-code fusion system is characterized in that the mapping relation is as follows: the uniform material unique code, namely the supplier code and the supplier material code inherits the static attribute information (name, classification, quantity, delivery date, validity period and the like) of the original supplier to the material entity.

The CES system generates a corresponding event message according to the bottom layer standard event and uploads the event message to the data center station; meanwhile, the CES also realizes the separated transmission of the attribute information and the transition information of the material entity and returns the detailed static attribute information (CES coding analysis service) of the material entity of the client system according to the unique code of the material entity.

The CES system is a distributed client/server architecture. The CES root server is deployed in the global headquarters, maintains a CES information resource base (CES-IR) together with the data middlebox based on the uploaded event message, and provides data support for agile emergency logistics information service; the branch CES server is an optional configuration item and can be flexibly configured to accelerate the code analysis speed; the CES edge intelligent terminal is deployed at nodes such as a warehouse and the like, and the edge intelligent terminal interacts with the whole CES system to complete the functions of generating and uploading event messages of the node, inquiring attribute information of material entities and the like; and the CES client is deployed on the mobile handheld terminal to complete the acquisition of information required by the event message and the initiation of the requirement for the code analysis of the material entity.

The data center station mainly receives, cleans and manages the global event message from the CES system; from third-party logistics or warehousing companies, carrying event messages for replacing the materials; and related data from other business management systems in the domain, such as global provider information, warehousing node information, etc. The information is stored after being associated, integrated and processed, is the core basis of a CES system and is generally called a CES information resource base (CES-IR). And the data center station provides data support for an upper-layer agile emergency logistics information service system based on CES-IR. The CES-IR is divided into an entity dynamic information base and an entity type static information base, wherein the entity dynamic information base comprises a material entity state base, an event report base and an in-transit tracking information base; the entity type static information base comprises a material entity attribute base, a supplier information base, a carrier information base and a node information base.

The agile emergency logistics information service system is mainly used for providing data service for an upper application system through web-service based on a data center station according to application scenes and requirements of the upper application system or an external application system. Any level of organization may be authorized as needed to provide a variety of data services to it, through which financing and logistics organizations are supported.

And deploying the system at the nodes such as the warehouse/distribution center and the like in the global range implemented by the open logistics system enabling system. All nodes that are to enter the system management domain need to do the following operations:

deploying an enabling system, and arranging a CES server at a node;

standardizing key operation of the existing system;

and (4) performing initialization operation of checking and code assigning on all materials.

Access of capacity

The capacity resource (quantity, state and position) in the domain is one of the minimum management units of the system, and the system also needs to be accessed to realize the management of the capacity resource and the tracking of the position change of the material. The capacity resource to enter the management domain needs to do the following operations:

operation standardization: loading, unloading and cleaning the packing box;

position information returning: the method is characterized in that a data center is introduced through an API of a third-party logistics company; the second mode is to transmit back the position information through the black box installed on the transportation body during consignment.

Resource operations

And remote operation instructions are completed by depending on logistics operation automation equipment and a logistics operation automation system. The storage process comprises the following steps: the storage and material warehouse can adopt an unmanned management storage scheme, and remotely issue instructions for entering and exiting the warehouse; the transportation process comprises the following steps: and a transportation instruction is issued to a third-party logistics company, and the third-party logistics company collects the goods to be transported from the storage and transportation warehouse and stores the goods in place.

Visualization and financing scheduling of resources

Visualization

The asset visualization system provides visualization of assets and transport capacity based on data services provided by the agile emergency logistics information service system according to the quantity, state and position data of the assets and transport capacity resources, and provides decision support for emergency material guarantee scheduling.

The system provides visualization of unit (warehouse) dimension (warehouse storage material type, quantity and the like), visualization of material type dimension (distribution of each material type), visualization of destination dimension (material and transport capacity within a certain range of the destination), and visualization of transport capacity (distribution of transport capacity of vehicles, ships, trains, airplanes and the like). The multi-dimensional query according to units (warehouses), states (asset effectiveness, schedulability and the like), material types, quantity, positions, time and the like is supported, and the scheduling decision is supported by visually presenting detailed material information and a flow-to-flow dynamic process of key service points.

Financing scheduling

From the material and capacity resource status data, a visualization of the unit (warehouse) dimensions, material type dimensions, destination dimensions and capacity (car, ship, train, plane, etc.) can be seen. Based on the grasp of the global range material and the transport capacity resource condition, the radius range is adjusted by taking the destination as the circle center to search resources, complete the financing, make a plan and issue a scheduling command.

And issuing a call instruction through the service system.

Through bottom automatic warehousing, the unmanned warehousing of the generation is assigned a remote scheduling instruction and directly delivered out of the warehouse.

In addition, data services can be authorized to be provided for any level of organization according to needs, and the authorized organization is supported to carry out material financing and logistics organization through the data services.

Open logistics system enables system logistics organization

Based on the entity internet PI theory, logistics organizations package materials in modular and standardized packing boxes (special and standard material entities), and the packing boxes can be stacked layer by layer from the smallest packing box to a shipping container. The package is easy to handle, store, transport, seal, secure, interlock, load, unload, construct and remove, and can be easily combined/disassembled at a node. The packing cases are equivalent to data packets in the digital internet, and the information part of the packing cases is similar to the header of the data packets in the digital internet, and the packing cases comprise information such as material starting addresses and delivery addresses.

The transportation network composed of the nodes and the transportation lines and the transportation capacity resource are used as a transportation layer, similar to a communication subnet in the digital Internet, and the transportation is organized according to the header information of the packing boxes to deliver the material entity to the destination. In the logistics transportation organization process, the combination (disassembly/combination) planning and dynamic routing selection (selecting a proper next hop node for the packing box) of the packing box are reasonably carried out at the transfer node through a standard protocol, the accessibility of the bottom layer is ensured, and the logistics organization is carried out more flexibly and reliably.

Example 8:

The system framework comprises five layers from bottom to top, namely an object event occurrence layer (data source), an event acquisition layer, a data management layer, an application service layer and an upper application layer.

a. First layer (bottom layer): key job event standardization

The standardization of the key operation events is to carry out standard definition on the key operation events of the trigger events to form standard events, is the basis of material entity management, and is also a core data source of the agile emergency logistics scheduling system. According to the key operation of the existing business process, seven standard events are defined in a standard way, including generating an entity, combining the entities, disassembling the entity, transferring out the entity, transferring in the entity, tracking in the process and eliminating the entity. The management of the standard events is embedded in the actual business process.

b. A second layer: information entity fusion system (CES system)

An information entity fusion system (CES system) is the core of the system and realizes the acquisition and transmission of the related information of the material entity. The CES system carries out unique coding identification on the asset by the system through a multi-coding fusion system to enable the asset to become a manageable material entity, and corresponding event messages generated by triggering of bottom-layer standard events are collected and transmitted back to CES (service center) level services and root services through each CES terminal service, and are finally managed in a data center; the global material tracking is realized, and global material financing and logistics organization are supported. The enterprise material planning and logistics organization is more open and flexible.

c. And a third layer: data center

The data center is suitable for the refined operation requirements of enterprises. By building a data middle platform, various data are collected, cleaned, processed, stored and integrated, and a foundation is laid for data service and upper-layer application.

d. A fourth layer: agile emergency logistics information service system

The agile emergency logistics information service system provides personalized and customized services for each scene application based on data provided by the data console according to actual requirements of upper-layer applications or external application requirements. Any level of organization may be authorized to provide data services as needed, through which financing and logistics organizations are supported.

e. Fifth layer (top layer): application system

The application systems in the project range comprise an asset transport capacity visualization system, a logistics task execution system and the like, user interaction channels such as a PC (personal computer), a mobile terminal and a large screen are built according to different practical application scenes, and the service requirements of users are met.

The material entity and the dynamic change in the emergency logistics scheduling process are triggered and generated by key operation. Key operations extracted from the whole emergency logistics scheduling process are standardized, and tracking management of material entity attribute and state dynamic changes is achieved by collecting and returning event message information triggered by standard events.

The project agile emergency logistics scheduling system standard event comprises the following steps: generating entities, combining entities, disassembling entities, transferring entities out, transferring entities in, tracking in transit, and eliminating entities. And the material entity event data of each standard event is acquired to a CES edge service through a CES client, and the CES edge service is communicated with a sub-company CES service and a CES root service of the data center station and is transmitted back to the data center station. With the development of the emergency logistics scheduling service, the standard events can be expanded based on actual development requirements.

The seven standard events are detailed below:

a. generating an entity

And generating a new material entity. Scanning the original code on the material by using a handheld terminal; generating a unique code unified by a cost management domain through a multi-code fusion system and writing the unique code into an electronic tag; attaching a label to the material entity; the hand-held terminal system uploads the material entity information to the original service management system to complete corresponding service management, meanwhile, the hand-held terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message and uploads the material entity event message to the data center.

b. Combined entity

And (4) boxing/packaging the plurality of material entities to form a new material entity. Scanning the electronic tags of the material entities to be boxed; boxing/packaging; the multi-code fusion system generates a unique code unified in a management domain and writes the unique code into the electronic tag; the label is attached to the new material entity; the hand-held terminal system uploads the material entity information to the original service management system to complete corresponding service management, meanwhile, the hand-held terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message and uploads the material entity event message to the data center.

c. Disassembling entity

One material entity is disassembled and reduced into a plurality of material entities. Scanning an electronic tag of a material entity for unpacking the box; unpacking/unpacking; the hand-held terminal system uploads the material entity information to the original service management system to complete corresponding service management, meanwhile, the hand-held terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message and uploads the material entity event message to the data center.

d. Roll-out entity

And the material entity is transferred out from the node. Scanning out the electronic tag of the material entity; rolling out; the hand-held terminal system uploads the material entity information to the original service management system to complete corresponding service management, meanwhile, the hand-held terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message and uploads the material entity event message to the data center.

e. Transfer-in entity

And transferring the receiving material entity to the node. Scanning the electronic tag of the transferred material entity; transferring in; the hand-held terminal system uploads the material entity information to the original service management system to complete corresponding service management, meanwhile, the hand-held terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message and uploads the material entity event message to the data center.

f. On-the-road tracking

And tracking position change information of the material entity. The position information is returned by the transportation body (automobile, airplane, train, etc.) at regular time. There are two options: (1) The third party company returns position information regularly or according to the transit node, and transmits the position information to the data center station through the data interface; (2) The black box installed on the transportation body during consignment automatically returns the position information message at regular time.

g. Elimination of entities

The asset entity disappears from the management domain (because the asset is dead or used). Scanning a material entity electronic tag; recovering the electronic tag; the hand-held terminal system uploads the material entity information to the original service management system to complete corresponding service management, meanwhile, the hand-held terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message to upload to the data center.

3.2 information entity fusion System (CES System)

A CES (Cyber Entity Systems, information Entity fusion system) system is a support enabling system for constructing and operating an open logistics system enabling system, and is the core of the open logistics system enabling system.

3.2.1 CES system construction principle

a. Principle of advancement

The CES system architecture adopts the international mainstream mature technology, combines the latest entity Internet PI concept, EPC and CPS theory and technology, has prospective property, and keeps certain technical advancement for a long time in the future.

b. Principle of openness

The CES system design follows the open principle, and can support various hardware devices, network systems and database management systems, and the software and hardware support secondary development. The CES system adopts a standard data interface and supports various typical data exchange and service integration of cross-logistics systems.

c. Principle of flexibility

The CES system is independent of the existing asset management system and the logistics system to operate, and can be flexibly deployed according to needs.

d. Principle of high efficiency

The CES system adopts a distributed client/server architecture, can meet the requirements of national and even global real-time query and data exchange, and ensures high-efficiency interconnection and intercommunication among the distributed CES systems.

e. Principle of safety

The CES system transmits the material entity attribute information and the entity transition information separately, thereby ensuring the security of the entity attribute information and realizing the information security sharing.

f. Scalability principle

The CES system has good expandability in the aspects of scale, hierarchical structure, function, service and the like so as to adapt to the popularization and application of future systems.

Multi-code fusion system

Coding standard

The unified unique code of the system adopts the unique identification of military articles of standard GJB + 7375-2011, and is supposed to adopt a 2 nd code format, namely a 'variety code'. Military article unique identification (MUII) the encoding structure of the 2 nd encoding format MUII2 is shown in fig. 2:

issuing organization code (IAC)

A code assigned to an issuing authority, which typically has authority to assign the organization code to the organization.

The issuer code is a 1-bit number from 0 to 9. Wherein:

a.1 — authorized general organization code authority;

b.2 — authorized national organization code authority;

c, 0, 3-9-standby.

Organization code

An organisation code is a code that determines the unit of unique identification of an item, typically the unit of the manufacturer or supplier of the item. The organization code should be specified by an authorized general organization code authority or national organization code authority. The code authority requires a specified code as per GB 11714.

The organization code is 9 characters, which only comprises capital English letters A-Z and numbers 0-9, but does not comprise capital English letters O and I.

Variety code

The item code is used to distinguish different kinds of items, and one item having the same structure, shape, function, fit and interface should have the same item code.

The variety code is determined by an authorized military material and equipment variety code management organization according to GJB 7001; in the case where the military has no explicit requirement, the item code may also be specified by the entity responsible for the development or design of the item. The manufacturer, supplier, etc. of the article should ensure that the item code is unique within the present organizational code.

The variety code is 1-9 characters, only including capital English letters A-Z and numbers 0-9, not including capital English letters O and I.

Coding mapping relationships

As shown in fig. 3, the multi-code fusion system uses the mapping relationship: the unified material unique code-supplier code + supplier material code realizes the fusion operation of a multi-material coding system related to multiple suppliers and solves the problem of unified tracking management of materials of different suppliers and different coding systems. The supplier code, the code of the supplier to the material, and the attribute information (name, type, quantity, production date, expiration date, etc.) of the material are provided by the current service system, and the CES system is accessed. Wherein the data in the current business system is sourced from local entries or provider exchanges.

The supplier material codes have two coding modes of one material and one code, and based on the principle of unique identification (UII) of the article, the materials of one code of one class need to be divided by adding serial numbers at the tail part for distinguishing.

CES information resource library (CES-IR)

The CES system globally maintains information about entities, including material entities and organizations involved in logistics activities, such as suppliers, carriers, warehouses, etc. The information of these entities is collectively referred to as a CES information resource pool (CES-IR). As shown in fig. 4, the CES information resource pool (CES-IR) is divided into two main categories, namely an entity dynamic information pool and an entity class static information pool.

Entity class static information base

The entity type static information base comprises a material entity attribute base, a supplier information base, a carrier information base and a node information base.

Material entity attribute library

And the material entity attribute library stores material entity attribute information. The method mainly comprises a unique code, a supplier code, a product name, a type, a quantity, a production date and an expiration date; storage requirements, transportation requirements, etc. The unique code of the material entity is given by a multi-code fusion system, and other attribute information is inherited from an original supplier management system; the expiration date may be calculated based on the production date and expiration date provided by the original supplier.

Supplier information base

The supplier information base stores supplier information. Mainly including attributes such as vendor code, name, address, phone, etc.

Carrier information base

The carrier information base stores carrier information. Mainly including attributes such as carrier organization code, name, address, etc.

Node information base

And the node information base stores the node information. The method mainly comprises the attributes of node codes, names, affiliated mechanisms, position information and the like. Wherein, the node includes: (1) a warehouse; (2) the transport carrier (is a mobile node), and the mechanism is the carrier; (3) collecting nodes; (4) other logistics nodes, etc.

Entity dynamic information base

The entity dynamic information base comprises a material entity state base, an incident report base and an in-transit tracking information base.

Material entity state library

The material entity state library takes a material entity object as a unit and describes the current content, position, state and the like of the object. The method mainly comprises a unique code, a supplier code, a product name, a type, a quantity, a production date and an expiration date; storage requirements, transportation requirements; entity type, entity packing state, and entity object list contained; the node, the valid state (whether available, automatically generated according to the current date and the expiration date), the delete marker, and the like.

The entity type, the entity packaging state and the contained entity object list are used for expressing the nesting relation of the material entities. During the storage and transportation process, the material entities are boxed/packaged to form a new combined material entity. Therefore, the material entity object comprises two types, namely an original object which is a minimum/non-separable material entity; and the other is a combined nested object formed by combining the original object or other nested objects, which is called a package, and also gives a unique code as a new material entity. They can be laminated according to the needs (such as storage needs and transportation needs). The nested aggregation relationship of the material entities can be realized by (1) entity types: atom/polymerization; (2) and (3) solid packaging state: stand alone/packaged; (3) list of entity objects involved: three attributes are described together according to the packing/casing information generated by the packing sheet. A typical example and schematic is shown in fig. 5 (a, b):

the attribute values of the material entity objects (original objects and packages) in the figure are shown in table 1:

TABLE 1 Material entity object Attribute values

For the combined packet, if the valid states of all the original objects in the packet are yes (not expired), the packet is valid, and if not, the packet is invalid. And sending out early warning information for the expired and invalid material entity object.

Incident newspaper library

The event report library is used for storing event reports and mainly comprises attributes such as a report number, an event code, an event type and an entity unique code. And does not contain specific attribute information of the material entity.

The specific information contained in each event message is as follows:

a. entity generation of elimination class events

Generating: message number, event code, event type, entity unique code and node code.

Combining: message number, event code, event type, entity unique code, combined entity unique code list and node code.

Disassembling: message number, event code, event type, entity unique code, disassembled entity unique code list and node code.

Eliminating: message number, event code, event type, entity unique code and node code.

b. Entity ownership change class events

And (3) turning into: message number, event code, event type, entity unique code and node code.

And (3) rolling out: message number, event code, event type, entity unique code and node code.

c. Entity tracking class events

Tracking in the way: message number, event code, event type, entity unique code, and location information.

In-transit tracking information base

The real-time position information of the goods and materials entity is stored in the on-the-road tracking information base, and the position change of the goods and materials entity is tracked. Mainly comprises a unique code of a material entity and position information (longitude and latitude).

CES system framework

As shown in fig. 6, the CES system is a distributed client/server architecture, and mainly includes a CES client, a CES edge intelligent terminal, a branch CES server, and a CES root server.

The CES root server is deployed in the global headquarters, is integrated with the data center, and is used for maintaining and updating a CES-IR information resource base in real time based on the uploaded event message and providing data support for agile emergency logistics information service;

the branch CES server is an optional configuration item, can be flexibly configured according to needs, is used for accelerating the coding analysis speed, and can be deployed in a branch or a warehouse and the like. More levels of CES servers can be configured according to needs;

the CES edge intelligent terminal is deployed at nodes such as a warehouse and the like, and the edge intelligent terminal interacts with the whole CES system to complete the functions of generating and uploading event messages of the node, inquiring attribute information of material entities and the like;

and the CES customer service end is arranged on the mobile handheld terminal to complete the acquisition of information required by the event message and the initiation of the coding analysis requirement of the material entity.

According to the unique coding hierarchical coding structure of the multi-coding fusion system, a CES root server maintains a CES information resource library (CES-IR) of the whole domain, other CES servers at all levels have subsets of similar static information in the CES-IR, coding analysis can inquire static attribute information of material entities through the CES servers at all levels, and an analysis request can be directly sent to the CES root server.

CES-IR dynamic maintenance based on event message

And the CES root server updates a CES-IR information resource library in real time according to various event messages generated by triggering of the underlying standard events, mainly a material entity state library in the CES-IR, and provides data support for material visualization and planning scheduling. Meanwhile, the event message is stored in an event message library, and support is provided for the query of the historical events of the material entity.

Entity generation elimination class events

Generating four standard events of an entity, combining the entity, disassembling the entity and eliminating the entity, and generating a corresponding entity elimination event: generating an entity, combining the entities, disassembling the entities and eliminating the entities.

a. Generating an entity

The generation of the entity event can prompt the generation of a new material entity, so that the uploaded generation entity event message is stored in an event report library, and a material entity attribute library and a material entity state library are triggered to add a new material entity record. As shown in fig. 7:

b. composite entity

Combining entity events allows multiple asset entities to be boxed/packaged, resulting in a new asset entity. Therefore, the uploaded combined entity event message is stored in the event report library, and meanwhile, the corresponding new material entity record is added in the material entity state library, and the 'entity packing state' field of the packed material entity records is updated from 'independent' to 'packed'. As shown in fig. 8:

c. disassembling entities

The disassembly entity event enables the composition material entity containing a plurality of material entities to be disassembled and eliminated, so that the uploaded disassembly entity event message is stored in an event message library, and meanwhile, the 'deletion mark' is updated from 'no' to 'yes' in the disassembled material entity record in the material entity state library, and the 'entity packaging state' field of the packaged material entity record is updated from 'packaged' to 'independent'. As shown in fig. 9:

d. elimination of entities

The elimination entity event causes the material entity to disappear from the management domain (for example, because the material is invalid or used), the uploaded elimination entity event message is stored in an event report library, and meanwhile, a material entity state library is triggered, and a 'deletion mark' in the eliminated material entity record is updated from 'no' to 'yes'; and in the material entity attribute library, updating the deleted 'deletion mark' in the deleted material entity record from 'no' to 'yes'. As shown in fig. 10:

entity ownership change class events

Two standard events of transferring entity and transferring entity will generate corresponding entity ownership change event: transferring into entity and transferring out entity.

Transfer-in entity

The transfer-in entity event enables the ownership of the material entity to change, the material entity is received by a new node, an uploaded transfer-in entity event message is stored in an event report library, and meanwhile, a field of a 'located node' in a transferred material entity record is triggered to change and is converted into the name of the node receiving the material entity. As shown in fig. 11:

roll out entity

The method comprises the steps that a material entity right is changed due to an entity event which is transferred out, a material entity is transferred out from a node, an uploaded transferred-out entity event message is stored in an event report library, meanwhile, a material entity state library is triggered, and a 'located node' field in a transferred-out material entity record is changed and is changed into a name of a node where the material entity is located. As shown in fig. 12:

entity tracking class events

The entity tracking type events comprise 'on-the-road tracking' events, the position change condition of the on-the-road material entity object is tracked, and the on-the-road tracking event message containing the position information is automatically returned by the transportation body at regular time.

The returned on-the-way tracking event message is stored in an event message library, and the change of a 'position information' field in the tracked material entity record in the on-the-way tracking information library is triggered. The position information is represented by longitude and latitude. As shown in fig. 13:

CES code resolution service

And the CES code analysis service is responsible for analyzing and returning the static attribute information of the material entity according to the unique code of the material entity.

The CES code resolution service is closely related to the hierarchy of the unique codes of the material entities, and is a distributed resolution of the unique codes. The unique code of the material entity adopts a format of 'issuing organization code-variety code-serial number', and correspondingly, the CES code analysis layer is a two-level structure of 'issuing organization code-organization code', and the system structure is shown in figure 14.

As with fig. 14, the sub-levels are added to the graph under the organization, since the authorized issuing entity may have the authority to assign sub-level organization codes to the sub-level organization as needed. Therefore, organizations at all levels can be graded in the authority of the organizations, unique codes are coded for the material entities, and internal CES-IR static information bases (CES-IR static information subsets) are managed.

The CES coding resolution process is as follows: the CES client reads a unique code of a material entity and sends an analysis request to a CES edge intelligent terminal based on the unique code; the CES edge intelligent terminal firstly checks the local CES-IR static information subset, if finding the relevant record, the analysis is completed and the result is returned, otherwise, the CES edge intelligent terminal forwards the result to the CES server at the upper stage (according to the configuration); returning the static attribute information of the material entity corresponding to the unique code at most until a CES root server (storing the whole CES-IR) to finish analysis

Data center

The agile emergency logistics dispatching system data center mainly realizes unified management of various data, receives data of a CES (control element access), a current business system or a third-party system, stores and manages the data, and provides data service for upper-layer application and other external systems through the agile emergency logistics information service system.

The core of the data center station is to realize the extraction, management, processing and integration of the following three types of information. The three types of information are as follows:

CES information resource pool information

The CES information resource base (CES-IR) mainly comprises dynamic data information such as material entity state information, event message information and on-the-way tracking information, and static data information (CES-IR) such as material entity attribute information, supplier information, carrier information and node information. The data center station provides collection, processing and integration of global CES-IR data.

Third party logistics or warehousing information

The partial data is acquired by the data center through the API of the third-party agent storage and transportation company, is correspondingly processed, is converted according to the standard format of the system specification, is stored in the event report library and updates related CES-IR information according to the rule.

Internal incumbent business system information

The data center station of the agile emergency logistics scheduling system is connected with the current service system as required to acquire information such as task data, and the service information of the current service system and the material entity object information in the system are subjected to associated integration, processing, storage and the like through the data center station.

Agile emergency logistics information service system

Microservice architecture

In consideration of non-functional requirements such as expansibility, maintainability and flexibility of the system, the scheme is based on a SpringBoot framework, an enterprise-level and high-availability micro-service architecture system with a front end and a rear end separated is built, and a modularization idea is introduced to realize high-cohesion low-coupling application service.

The micro-service architecture has the following advantages:

a. loose coupling property: the complexity is solved by dividing the single application into a plurality of service modules, and the modules are interacted through REST API or messages, so that the coupling between the modules is reduced, and the complexity is controllable.

b. And (3) parallel development: because the application is divided into independent modules, the teams can be independently developed and maintained, and the development efficiency is improved.

c. Independent deployment: each micro service can be independently deployed, a developer does not need to coordinate the influence of the deployment of other services on the service, the deployment speed can be increased, and the deployment can be continued.

d. Differentiated implementation: the differentiated deployment is carried out according to different application scenes and requirements, the access amount and the concurrency amount of each functional module are different, and different instances of different services can be deployed through splitting of the micro-service.

e. The expansibility is high: by splitting the service, new functions can be added in the later period conveniently, and progressive development is supported; the upper application building function is more flexible, and the expansibility is high.

f. High availability: the traditional single application fails to enable the whole system to be unavailable, the micro-services are deployed in a distributed mode, each service has multiple instances, even if a certain node is down, only part of the services are affected, and the fault tolerance is high.

Agile logistics scheduling system-oriented service

The agile emergency logistics information service system provides data and application services for upper-layer applications through a micro-service architecture, wherein the data and application services include but are not limited to asset information services, transport capacity information services, task information services and the like required by agile logistics scheduling.

Asset information service

The asset information service is based on data managed by a data center station, takes 'assets' as objects, provides multi-dimensional information query, statistics and visualization services for material entities, such as asset list, asset classification and quantity, asset storage position and distribution, asset available state and the like, and provides convenient, quick and visual presentation for users through upper-layer application.

Transport capacity information service

The capacity information service is based on data managed by a data center station, takes the capacity as an object, provides multi-dimensional inquiry, statistics and visualization services of the capacity, such as capacity list, capacity statistics, capacity distribution, capacity allocation and the like, and provides visual capacity information for users through upper-layer application.

Task information service

The task information service is based on data managed by a data center, takes a task as an object, provides related services such as task issuing, task execution management, task tracking, task feedback and the like, supports the operation of an upper layer logistics task execution system, and realizes the whole-process closed-loop management of the task.

Other application services

Besides the services oriented to agile emergency logistics scheduling, the information service system can also provide related services for the existing business system or other external applications in a micro-service mode, such as docking with the existing business management system to issue tasks, providing assets, capacity, task execution conditions and other related data for the external systems.

Application system

The application system mainly faces to system users, and various functions of front-end interaction are realized based on actual requirements and application scenes. The application system of the technical scheme of the system comprises an asset visualization system and a logistics task execution system. The data center station provides required data, and the agile emergency logistics information service system provides service support.

The asset visualization system comprises asset and transport capacity visualization and provides decision support for emergency material guarantee scheduling. The logistics task execution system mainly achieves closed-loop management for guaranteeing that tasks are automatically completed. The system can be used by an enterprise or company management layer for automatic data acquisition, big data analysis, situation display and assistant decision support.

Asset transport capacity visualization system

The asset transport capacity visualization system acquires object related data including object names, numbers, states, positions and change processes of the objects through a data center. The system provides reports and boards with various visual angles, and realizes multi-dimensional query and drilling.

Property list: the method takes the multi-level classification of the materials as a main view angle, and presents the concrete conditions of the materials and the categories through reports, signboards and the like, including but not limited to the quantity (stock) of the materials of each category, the distribution condition (location or position), the asset state (effectiveness, schedulability and the like).

The fortune is listed as: the transportation capacity is taken as a main visual angle, and the transportation capacity condition is presented through a map board, so that the transportation capacity condition not only comprises the own transportation capacity, such as vehicles, ships, airplanes, trains and the like, but also comprises transportation networks thereof; and the system also comprises the transportation capacity and transportation network information provided by the third-party logistics company.

Service node list: the method takes business points of each unit or warehouse and the like as main visual angles, and presents the unit assets and the transportation capacity conditions through reports, signboards and the like, wherein the unit assets and the transportation capacity conditions comprise but are not limited to asset types (including multi-level classification), asset quantity (inventory of various types of materials), storage positions, asset states (asset effectiveness, schedulability and the like), self-owned transportation capacity (comprising available vehicles, ships, airplanes and trains), transportation networks, third-party logistics company transportation capacity and transportation networks and the like.

Destination resources list: the assets and the transport capacity conditions within the designated distance radius range are presented by taking the destination as the center of a circle, wherein the assets and the transport capacity conditions comprise but are not limited to asset types (including multi-level classification), asset quantity (stock of various types of materials), storage positions, asset states (asset effectiveness, schedulability and the like), self-owned transport capacity (comprising available vehicles, ships, airplanes and trains) and transport networks, transport capacity and transport networks of third-party logistics companies and the like.

Multi-dimensional query: and multidimensional query and data drilling according to units, objects, states, positions, time and the like are supported. And displaying detailed material information and a dynamic circulation process of the key service points through visualization.

The logistics task execution system comprises: and the whole process management and tracking of the agile emergency logistics scheduling task are realized. The system covers closed-loop management of the whole process of task initiation, task execution process, execution result condition and the like, and tracks the execution condition of the whole process through objects and related information returned by each service point received by the data center.

Task initiation and issuance

The logistics task initiator is a head office, and the head office initiates the logistics task through the logistics task execution system and issues the logistics task to branch companies or warehouses. The emergency material guarantee logistics task is issued to the existing service system of the branch company, the emergency material allocation plan is issued to the existing service system of the warehouse, and the task or plan information comprises material types, quantity, destination, time limit and the like.

And a task execution process: when the branch company or warehouse receives the task or plan, the branch company or warehouse needs to prepare materials, pack/unpack, sort out the warehouse, transport by a loading machine or a machine and deliver to the destination according to the requirement, and search, receive and distribute by ground personnel. The whole execution process relates to a plurality of service point locations such as branch companies, warehouses, collection nodes, ground sites and the like, each service point location has a plurality of key operations, and each key operation is transmitted back to a headquarter data center station by a fusion terminal and system collected data. The logistics task execution system can acquire object data of an execution process through the data transfer station, and match the object data with task data to realize overall process management.

And a task execution result: the task execution is finished by the material delivery working group. The logistics task execution system identifies task execution results based on data returned by the terminal and based on business requirements, such as normal completion, overtime completion, incompletion, exception and the like.

Example 9:

the open logistics system enables the system, and the hardware thereof is shown in table 1:

specific rules for data storage

The CES system globally maintains information about entities, including material entities and organizations involved in logistics activities, such as suppliers, carriers, warehouses, etc. The information of these entities is collectively referred to as a CES information resource pool (CES-IR). The CES information resource base (CES-IR) is divided into two categories, namely an entity dynamic information base and an entity static information base.

Entity class static information base

Material entity attribute library

And the material entity attribute library stores material entity attribute information. The method mainly comprises a unique code, a supplier code, a product name, a type, a quantity, a production date and an expiration date; storage requirements, shipping requirements, etc. The unique code of the material entity is given by a multi-code fusion system, and other attribute information is inherited from an original supplier management system; the expiration date may be calculated based on the production date and expiration date provided by the original supplier.

Supplier information base

Carrier information base

Node information base

The node information base stores node information. The method mainly comprises the attributes of node codes, names, affiliated mechanisms, position information and the like. Wherein, the node includes: (1) a warehouse; (2) the transport carrier (is a mobile node), and the mechanism is the carrier; (3) collecting nodes; (4) other logistics nodes, etc.

Entity dynamic information base

Material entity state library

The material entity state library takes a material entity object as a unit and describes the current content, position, state and the like of the object. The method mainly comprises a unique code, a supplier code, a name, a type, a quantity, a production date and an expiration date; storage requirements, transportation requirements; entity type, entity packing state, and contained entity object list; the node, the valid state (whether available, automatically generated according to the current date and the expiration date), the delete marker, and the like.

The entity type, the entity packaging state and the contained entity object list are used for expressing the nesting relation of the material entities. During the storage and transportation process, the material entities are boxed/packaged to form a new combined material entity. Therefore, the material entity object comprises two kinds, namely an original object which is a minimum/non-separable material entity; and the other is a combined nested object formed by combining the original object or other nested objects, which is called a package, and also gives a unique code as a new material entity. They can be laminated according to the requirements (such as storage requirements and transportation requirements). The nested aggregation relationship of the material entities can be realized by (1) entity types: atom/polymerization; (2) and (3) solid packaging state: stand alone/packaged; (3) list of included entity objects: three attributes are described together according to the packing/casing information generated by the packing sheet.

An incident report library: the event message library is used for storing event messages and mainly comprises attributes such as message numbers, event codes, event types and entity unique codes. And does not contain specific attribute information of the material entity.

The specific information contained in each event message is as follows:

a. entity generation elimination class events

Generating: message number, event code, event type, entity unique code, node code. Combining: message number, event code, event type, entity unique code, combined entity unique code list and node code. Disassembling: message number, event code, event type, entity unique code, disassembled entity unique code list and node code. Eliminating: message number, event code, event type, entity unique code and node code.

b. Entity ownership change class event: and (3) turning into: message number, event code, event type, entity unique code, node code. And (3) rolling out: message number, event code, event type, entity unique code and node code.

c. Entity tracking class events

Tracking in the way: message number, event code, event type, entity unique code, and location information. An on-road tracking information base: and the real-time position information of the goods and materials entity is stored in the on-the-road tracking information base, and the position change of the goods and materials entity is tracked. The method mainly comprises the unique code of the material entity and the position information (longitude and latitude). And (3) corresponding authorized access rules and flow authorized access rules when the child nodes access the root node data: the CES coding analysis layer is a two-level structure of 'issuer code-organization code', and an authorized issuer can assign authorization of a sub-level organization code to a sub-level organization according to needs. Therefore, organizations at all levels can be graded in the authority of the organizations, unique codes are coded for the material entities, and internal CES-IR static information bases (CES-IR static information subsets) are managed. And (3) access flow: the CES client reads a unique code of a material entity and sends an analysis request to a CES edge intelligent terminal based on the unique code; the CES edge intelligent terminal firstly checks the local CES-IR type static information subset, if finding out the relevant record, the return result is analyzed, otherwise, the return result is forwarded to the CES server at the upper stage (according to the configuration); and returning the static attribute information of the material entity corresponding to the unique code at most until a CES root server (storing the global CES-IR) completes the analysis.

And a data center and a CES root server for updating CES edge data update rules update a CES-IR information resource base in real time according to various event messages generated by triggering of bottom-layer standard actions, wherein the CES-IR information resource base is mainly a material entity state base in the CES-IR and provides data support for material visualization and financing scheduling. Meanwhile, the event message is stored in an event report library, and support is provided for the query of the historical events of the material entity.

Claims

1. The method is characterized in that the open logistics system enabling system is a distributed system and comprises a root server and a data center station which are arranged in a management universe, sub-servers which are arranged in management subdomains of all levels, an internal communication network, an external communication network and an edge intelligent terminal.

each kth-level management sub-domain is provided with a kth-level sub-server;

the external reading and writing equipment is used for scanning the label of the material entity so as to obtain the label information of the material entity; the external read-write equipment performs data interaction with the edge intelligent terminal through an internal communication network;

the management universe is provided with a data middlebox and a data root server; the data center station performs data interaction with the edge intelligent terminal through an external communication network;

the information coding and storing method comprises the following steps:

the detailed information of the material entity is stored in the local level sub-server and the root server to which the node belongs when the entity is created, and comprises supplier codes of the material entity, codes of the supplier to the material entity and static attribute information of the material entity;

after the goods and materials entity triggers the standard event, the external read-write equipment collects the label information of the goods and materials entity, and uploads the standard event, the label information of the goods and materials entity and the position information triggered by the goods and materials entity to the corresponding edge intelligent terminal, and the edge intelligent terminal uploads the standard event, the label information of the goods and materials entity and the position information to the data center station through an external communication network; the position information comprises a node code where the edge intelligent terminal is located and an upper layer node code where the node belongs;

2. The method for constructing an open logistics system enabling system according to claim 1, wherein: the bottom layer nodes are material storage and transfer points and comprise warehouse nodes, distribution centers, material collection nodes and transporter nodes; when the bottom node is a carrier node, the position information further includes real-time geographical position information of the carrier acquired through a global satellite positioning system.

3. The method for constructing an open logistics system enabling system according to claim 1, wherein: the material entity comprises articles and a box body loaded with a plurality of articles;

the entity packaging state comprises a box body, a small box body inside the box body and the packaging state of articles inside the box body; the packaged state includes both individual and packaged.

4. The method for constructing the open logistics system enabling system according to claim 1, wherein the data message comprises a message number, an event type, an event code, material entity code information, a node code, a combined or disassembled object code list;

5. The method for constructing an open logistics system enabling system according to claim 1, wherein the material entity generation event comprises warehousing of material entities from suppliers;

6. The method for constructing the open logistics system enabling system according to claim 1, wherein the message number, the event code, the event type, the material entity code information and the node code corresponding to each material entity have a mapping relationship.

7. The method as claimed in claim 1, wherein the bottom node, the sub-nodes, the total node, and the material entity have unique coding information.

8. An open logistics system enabling system, characterized by: the open logistics system enabling system is a distributed system and comprises a root server and a data center station which are arranged in a management universe, sub servers arranged in management subdomains at all levels, an internal communication network, an external communication network, network safety equipment, network switching equipment and an edge intelligent terminal;

the network switching equipment comprises routers deployed in management subdomains at all levels and switches deployed in data intermediate stations;

9. The open logistics system enabling system of claim 8, wherein: the storage server stores a plurality of information bases for storing data;

10. The open logistics system enabling system of claim 9, wherein: the material entity state library also stores information generated by entity combination events, wherein the information comprises an entity packaging state and an object containing list;