CN115396467B

CN115396467B - Open logistics system enabling system construction method, system, storage medium and equipment

Info

Publication number: CN115396467B
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: 2024-02-27
Anticipated expiration: 2042-07-27
Also published as: CN115396467A

Abstract

The invention discloses a method, a system, a storage medium and equipment for constructing an open logistics system enabling system, which are 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 of a cross-logistics system and interconnection and intercommunication of logistics business of the upper layer. By energizing 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 affected.

Description

Open logistics system enabling system construction method, system, storage medium and equipment

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 open logistics system enabling system.

Background

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

For example, the warehouses of emergency logistics generally belong to different departments, and are only responsible for guaranteeing the demands of the departments in the same guaranteeing area, and a vertical tree structure guaranteeing mode is implemented, so that the rear warehouses have cross overlapping construction in the same area, and overall coordination procedures among the departments are complicated, so that the comprehensive guaranteeing capacity of the rear warehouses is greatly restricted.

In order to cope with the above problems, logistic informatization construction is indispensable. However, the logistics informatization construction is limited to the construction and purchase problems of facility equipment, the purposes of information communication and information sharing are not fully achieved, the informatization mechanism establishment and the informatization technology application are not perfect and popular, the software foundation of the informatization construction is not firm enough, and the informatization, the information communication and the information sharing cannot support the accurate logistics guarantee of emergency logistics.

Disclosure of Invention

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

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

the management universe comprises a plurality of levels of management subdomains; wherein the number of the k-th management subdomain is denoted as I _k ；I _k K are natural numbers;

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

a kth level management sub-domain comprising a kth level node and a number of kth +1 level nodes;

each kth management subdomain is loaded with a kth sub-server;

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

the sub-servers comprise application servers and storage servers; 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 k-th management subdomain comprises a plurality of bottom nodes, the bottom nodes store a plurality of labeled material entities, and the k-th management subdomain carries a plurality of edge intelligent terminals; the bottom layer node corresponds to the edge intelligent terminal;

the edge intelligent terminal is connected with 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 acquire 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 total node, all sub-nodes and a bottom node;

the management universe is loaded with a data center station and a root server; the data center station performs data interaction with any sub-server and the 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 or the wireless network;

the root server performs data interaction with the sub-servers through an internal communication network, so that cross-subdomain inquiry 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 open logistics system enabling system construction method comprises a method for establishing information coding, storing and inquiring information;

The information encoding 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 tag information comprises coding information of a material entity; when the material entity is in the logistics transportation stage, the material entity label information 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 the detailed information comprises the supplier code of the material entity, the code of the supplier on the material entity and the static attribute information of the material entity;

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

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

The material entity generating elimination class event comprises material entity generating class event, material entity combination class event, material entity disassembling class event and material entity elimination class event;

the material entity ownership change class event comprises a material entity transfer-in class event and a material entity transfer-out class event;

the entity tracking events comprise material entity in-transit tracking events;

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

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 sub-server of the local domain through a second network channel;

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

The information inquiry method comprises a method for inquiring information through a node and a method for inquiring information through a total node, wherein inquiry contents comprise entity detail inquiry and entity comprehensive information inquiry;

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

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

the entity comprehensive information inquiry refers to statistical inquiry of the entity by class, by position and the like;

when the entity comprehensive information inquiry is carried out, the request direction master node initiates an inquiry request, and after the master node receives 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 the local domain storage server according to the entity code, and returns the entity detail after the query; 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 requesting party, and meanwhile, the subdomain application server stores the query request result in the local domain storage server for review.

Further, the bottom layer nodes are material storage and transfer points, and comprise warehouse nodes, distribution centers, material collection nodes and transportation body nodes; when the bottom layer node is a carrier node, the position information also comprises carrier real-time geographic position information acquired through a global satellite positioning system.

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

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

the material entity coding information comprises a box body, a small box body in the box body and a code of an article in the box body;

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

Further, when a large box is split into a plurality of small boxes, if the small boxes have labels, no new labels are generated, and if the small boxes are not attached with labels, new labels are generated and attached to the corresponding boxes.

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

When the standard event type is entity tracking event, the data message also comprises position information.

The material entity coding information comprises a supplier code of a material entity and a static attribute information code of the material entity; the static attribute information of the material entity comprises names, classifications, quantity, delivery date and validity period; one class of events includes a plurality of events, each event having an event code.

Further, the supply entity generating event includes a supply entity warehouse entry from a provider;

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 material entity delivery;

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

the asset entity elimination event includes an asset entity failure, being used.

Further, the corresponding message number, event code, event type, material entity code information and node code of each material entity have mapping relation.

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

Furthermore, the node is also provided with an interaction platform for accessing the user.

Further, the bottom layer node, the partial nodes, the total nodes and the material entities all have unique coding information.

Further, the data center also stores a transport network; the transport network comprises a sub-node, transport equipment and a transport line provided by a main node, and transport equipment and a transport line provided by a third party logistics service side;

further, the application server also provides transportation information visualization services; the application server retrieves the position information of the transportation network and the physical entity in the transportation process stored in the data center table and displays the position information in the map.

An enabling system of an open logistics system is a distributed system, and comprises a root server and a data center station which are arranged in a management domain, a sub-server, an internal communication network, an external communication network, network security equipment, network switching equipment and an edge intelligent terminal which are arranged in each level of management sub-domain;

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

the edge intelligent terminal generates a static data message according to the material entity tag information and the position information, and uploads the static data message to a superior sub-server for storage; the sub-server receiving the static data message uploads the static data message level to the root server for storage;

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

the network switching equipment comprises routers deployed in management subdomains of each level and switches deployed in data center stations;

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

the switch is used for network communication between 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 in-transit 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, including supplier codes, names, addresses and contact ways;

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

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

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

the in-transit tracking information base is used for storing in-transit material entity position information;

The material entity state library is used for storing material dynamic state information, including unique codes, suppliers, supplier codes, product names, types, numbers, production dates, expiration dates, storage requirements and transportation requirements; entity type, entity packaging state, entity object list, node, valid state and delete marker.

Further, the material entity state library also stores information generated by entity combination events, including entity package states and object containing lists;

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

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

An apparatus for an open architecture enabling 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 described above.

The technical effect of the invention is that without doubt, the invention provides a construction method of an open logistics system enabling system based on the latest open logistics system (PI: physical Internet) theory, CPS (Cyber Physical Systems, information physical fusion system) and RFID (Radio Frequency Identification ) technology, and the open logistics system enabling system constructed by the method can realize the management, organization and allocation of cross-organization and cross-system materials in an open, safe and flexible manner under the open system and environment with minimum cost (minimum modification to the current system, minimum dependence on the current system and minimum inter-system interference).

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 business of the upper layer. By energizing 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 affected.

The invention manages the materials and the capacity resources (quantity, state and position) as the minimum units, tracks the positions of the materials and the capacity resources, and the upper layer carries out material raising and logistics organization based on the minimum units, and breaks the division of the bar blocks through the flattened data management, thereby breaking the bottleneck of cross-system data sharing.

According to the invention, the material dynamics is tracked based on the RFID technology, material management is performed, the key operation of logistics nodes such as a warehouse, a distribution center and the like is standardized, and the standard event trigger is embedded to generate a corresponding event message, so that the dynamic change of the material is obtained. By the patching mode, the condition of the materials is mastered, and the change to the current business system is minimal. The invention constructs an agile emergency logistics enabling system and realizes the material staging and the dynamic tracking of the material state across the logistics platform.

According to the invention, social logistics resources are more fully utilized, and the materials to be transported are placed into a standardized and modularized packaging box for transportation. The package boxes are equivalent to data packets in the digital internet in PI (Physical Internet, entity internet), and package the contents of goods transported by the package boxes, so that the contents are irrelevant to the PI, and the package boxes are more beneficial to the protection of information of the goods transported by the package boxes. Corresponding to the digital internet, the PI can be regarded as a logistics network, the movement of the packaging box in the PI is similar to the flow of the data packet in the digital internet, the unique global identifier is equivalent to the MAC address (Media Access Control Address, local area network address) in the ethernet and the digital internet, and the PI is used as a proxy in 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 the data packet in the digital internet, and the transportation layer combines a plurality of packing boxes and plans routes according to the header information, flexibly organizes logistics transportation and sends the material entity to the destination.

The information entity fusion system based on multi-code fusion realizes unified management of multi-source materials of different suppliers, real-time acquisition and safe transmission of asset flow data and 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 inquiry list according to the area, the position and the range, the nodes (warehouse, distribution center, etc.), the state, and the like, and supports the hierarchical emergency logistics scheduling.

The agile emergency logistics dispatching system is independent of the existing business system, and realizes the digitalization of logistics elements, the automation of data acquisition, the standardization of data exchange and service and the global emergency logistics management under the condition of not changing the existing management business process of enterprises. According to the invention, through researching the management of a multi-code fusion system and a CES information resource library, the digital management of the elements such as material entities, suppliers, carriers, nodes and the like is realized, and a data foundation is laid for agile emergency logistics scheduling.

According to the invention, through researching CES system frames, a material entity and a related information return path in a logistics scheduling process are formed by utilizing root service, branch service (multi-level sub-service), edge service and client side, and automation of collection of the material entity and logistics information 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 data center through the standard message. Meanwhile, the information service system of the data center and the micro-service architecture provides expandable, customizable, high-availability and easy-maintenance standard application service for upper-layer applications. Based on the logistics factor digitization, the data acquisition automation, the data exchange and the service standardization, the application system for the system research can provide the global range of material and operation resource conditions for decision makers and managers and support global scheduling management of material arrangement, allocation, transportation organization and the like.

Drawings

FIG. 1 is a unitary frame; FIG. 2 is a diagram of a code structure uniquely identifying the 2 nd code format of a military article; FIG. 3 is a multi-code fusion system mapping relationship; FIG. 4 is a CES information repository (CES-IR). FIG. 5 (a) is an example of a material entity nested relationship expression; FIG. 5 (b) is an example of a material entity nested relationship expression;

FIG. 6 is a CES (Cyber Entity Systems, information entity fusion system) system architecture; FIG. 7 is a diagram of a variation in CES-IR (Cyber Entity Systems-Information resources, information entity fusion system information repository) data records based on the generation of entity event messages; FIG. 8 is a CES-IR data record change based on a combined entity event message; FIG. 9 is a CES-IR data record change based on a disassembled entity event message; FIG. 10 is a CES-IR data record change based on an erasure entity event message;

FIG. 11 is a CES-IR data record change based on a transfer-in entity event message; FIG. 12 is a CES-IR data record change based on a roll-out physical event message; FIG. 13 is a CES-IR data record change based on a on-the-way trace event message; FIG. 14 is a CES code resolution service architecture diagram; FIG. 15 is a schematic diagram I of an open logistics system architecture; FIG. 16 is a schematic diagram II of an open logistics system architecture.

Detailed Description

The present invention is further described below with reference to examples, but it should not be construed that the scope of the above subject matter of the present invention is limited to the following examples. Various substitutions and alterations are made according to the ordinary skill and familiar means of the art without departing from the technical spirit of the invention, and all such substitutions and alterations are intended to be included in the scope of the invention.

Example 1:

referring to fig. 1 to 16, an open logistics system enabling system construction method, wherein the open logistics system enabling system is a distributed system, and comprises a root server and a data center set up in a management domain, sub servers set up in management domains of all levels, an internal communication network, an external communication network and an edge intelligent terminal;

the enabling system is constructed in a tree structure, and according to the organization structure, all domains and subordinate subfields are set up, and subfields are reset under the subfields. The subdomain manages 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 sub-servers and edge intelligent terminals; the management universe comprises a plurality of levels of management subdomains; wherein the number of the k-th management subdomain is denoted as I _k ；I _k K are natural numbers;

each kth management subdomain is loaded with a kth sub-server;

when the k value is maximum, the k-th management subdomain is the bottommost management subdomain and comprises a plurality of bottom nodes, wherein the bottom nodes store a plurality of labeled material entities, and the k-th management subdomain is provided with a plurality of edge intelligent terminals; the bottom layer node corresponds to the edge intelligent terminal;

the information encoding and storing method comprises the following steps:

the entity tracking events comprise material entity in-transit tracking events;

The bottom layer node is a material storage and transfer point and comprises a warehouse node, a distribution center, a material collection node and a transportation body node; when the bottom layer node is a carrier node, the position information also comprises carrier real-time geographic position information acquired through a global satellite positioning system.

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

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

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

The material entity generation event comprises a material entity warehouse entry from a provider;

the material entity transfer-out event comprises material entity delivery;

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

The labels comprise bar code labels, two-dimensional code labels and RFID labels.

The node is also equipped with an interactive platform for accessing the user.

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

The data center also stores a transport network; the transport network comprises a sub-node, transport equipment and a transport line provided by a main node, and transport equipment and a transport line provided by a third party logistics service side;

the application server also provides transportation information visualization services; the application server retrieves the position information of the transportation network and the physical entity in the transportation process stored in the data center table and displays the position information in the map.

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

The material entity state library also stores information generated by entity combination events, including entity packaging states and object containing lists;

Example 2:

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

The step of scheduling the material entity comprises:

1) The kth level node or the total node receives the logistics scheduling request and transmits the logistics scheduling request to the 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 total node, the root server of the data center station receives the logistics scheduling request;

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

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

the logistics scheduling task comprises the types of material entities, the number of demands, the destination and the time limit;

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

3) The data center station transmits 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 entity according to the material entity demand quantity, so as to obtain the material entity corresponding to the material entity demand quantity, and the material entity is delivered to a destination.

The open logistics system enabling system is constructed based on the latest open logistics system theory, CPS and RFID technology, and the cross-organization and cross-system material management, organization and allocation are realized in an open, safe and flexible manner under the open system and environment with minimum cost (minimum modification to the existing system, minimum dependence on the existing system and minimum inter-system interference).

The open logistics system enabling system is an upper system of the existing logistics system, supports real-time tracking of materials crossing the logistics system and interconnection and intercommunication of logistics business of the upper layer, and can enable the original logistics system to have agile characteristics under the condition that normal operation of the original logistics system is not affected by enabling of the enabling system.

Example 3:

a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the method described above.

Example 4:

Example 5:

a computer terminal for providing a man-machine interaction interface, wherein the man-machine 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 switching between the at least one first control according to the trigger instruction.

Example 6:

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 domain, a sub-server, an internal communication network, an external communication network and an edge intelligent terminal which are arranged in each level of management sub-domain;

each kth management subdomain is loaded with a kth sub-server;

the information encoding and storing method comprises the following steps:

the entity tracking events comprise material entity in-transit tracking events;

the material entity transfer-out event comprises material entity delivery;

The node is also equipped with an interactive platform for accessing the user.

Example 7:

an open logistics system enables a system that is generated based on an entity internet architecture.

The physical internet (PI, physicalInternet, pi) encapsulates goods in intelligent, environmentally friendly and modular packages that can be stacked in layers, from the smallest package to the shipping container. The physical internet PI encapsulates the goods in packages, hereinafter referred to as PI containers. These pi-containers are globally standard, intelligent, green, modular packaging boxes that are modular and standardized worldwide in terms of size, function, and fixtures. PI-containers are key elements for achieving the interoperability necessary for the operation of an entity internet PI. They are equivalent in PI to data packets in the digital internet. Their information part is similar to the header of a data packet in the digital internet. PI containers encapsulate the contents of their shipment such that these contents are PI independent, which is more conducive to the protection of the information of the shipment. Each pi-container has a unique global identifier equivalent to the MAC address in ethernet and digital internet. To ensure the robustness and validity of the identification, the identifier is physically and digitally attached to each pi-container. The intelligent identification is used as a proxy of each PI-container in the PI, and distributed automatic operations such as various processing, storage, routing and the like are realized. At the same time, each pi-vessel intelligently identifies interconnected multiparty, multi-stage and multi-logistics process real-time information can be used to improve the decision making capability of logistics operation management.

In correspondence with the digital internet, PI can be regarded as a logistics network that performs logistics services by PI-nodes (e.g., factories, warehouses, distribution centers, etc.) and standard PI protocols using corresponding PI movers (e.g., fork trucks or trucks, etc.) to handle, transport and store PI-containers.

The open logistics system enables the system architecture to master the state (quantity, state and position) of the materials and the capacity resources in the whole domain from the bottom layer independently of the current management organization architecture and the business information system, manage the materials and the capacity resources in the whole domain based on the state data of the resources, realize the visualization of the materials in the whole domain and support the whole domain material arrangement and logistics organization. Therefore, the material and logistics organization is more open and flexible.

An open logistics system architecture schematic is shown in fig. 15. The system is deployed at nodes (nodes) such as warehouse/distribution center to which the global scope of the implementation of the open logistics system is belonged:

all the nodes, materials and transport resources entering the system management domain need a material and transport checking and coding (unified unique coding) process.

The key operation of the node is standardized, and a plurality of standard events are added. The events automatically upload event messages to the data center station through the CES system while supporting the node current service system, and report the state and position information of the material entity.

CES (information entity fusion system) systems are the core of open logistics system enabled systems. An automatic acquisition, separation/fusion and sharing framework based on the attribute information and the entity transition information of the bottom layer is constructed by Internet thinking, so that the material staging and the dynamic tracking of the material state of the cross-logistics platform are realized. The system may 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 the material entity is endowed with a uniform unique code through a multi-code fusion system. The code is valid for the full life cycle within the management domain.

The multi-code fusion system uses the mapping relation: the unified material unique code-supplier code + supplier material code inherits the static attribute information (name, classification, quantity, delivery date, validity period, etc.) of the original supplier to the material entity.

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

CES system is a distributed client/server architecture. The CES root server is deployed at the global headquarter, and together with the data center, a CES information resource library (CES-IR) is maintained based on the uploaded event message, so that data support is provided for the agile emergency logistics information service; the CES server of the branch company 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 interacts with the whole CES system to finish the functions of generating and uploading event messages of the nodes, inquiring attribute information of material entities and the like; the CES client is deployed on the mobile handheld terminal to complete acquisition of information required by the event message and initiation of material entity coding analysis requirements.

The data center station mainly receives, cleans and manages the global event message from the CES system; event messages from third party logistics or warehousing companies, shipping the storage materials; and related data from other business management systems within the domain, such as global provider information, warehouse node information, etc. The information is stored after being integrated and processed in a correlation way, and is a core foundation of a CES system, and is commonly called CES information resource library (CES-IR). The data center station provides data support for the upper-layer agile emergency logistics information service system based on CES-IR. The CES-IR is specifically 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 class 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 mainly provides data service for an upper application system through web-service based on a data center 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 it with a variety of data services by which to support materials staging and logistics organization.

The system is deployed at nodes such as warehouse/distribution center and the like belonging to the whole domain of the implementation of the open logistics system. All nodes to enter the ontology management domain need to do the following operations:

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

the key operation of the existing system is standardized;

and initializing all materials for checking and coding.

Access to capacity

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

operation standardization: loading and unloading the packing box;

position information is returned: the first mode is that the data center is transmitted through the API of the third party logistics company; and secondly, the position information is returned through a black box mounted on the transportation body during the consignment.

Resource operation

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

Visualization and staging scheduling of resources

Visualization of

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

The system provides visualization of unit (warehouse) dimensions (warehouse storage material types, quantity, etc.), visualization of material type dimensions (distribution of material types), visualization of destination dimensions (materials and capacities within a certain range of destination), visualization of capacities (capacity distribution of cars, boats, trains, airplanes, etc.). The multi-dimensional query of units (warehouses), states (asset effectiveness, schedulability and the like), material types, numbers, positions, time and the like is supported, and the support is provided for scheduling decisions by visually presenting detailed material information and the flow dynamic process of key service points.

Financing scheduling

From the asset and capacity resource status data, visualizations of units (warehouse) dimension, asset type dimension, destination dimension and capacities (car, ship, train, plane, etc.) can be seen. Based on the mastering of the global range material and operation capacity resource conditions, the radius range is adjusted by taking the destination as the circle center, so as to find out the resource to finish the project, make a plan and issue a scheduling instruction.

And issuing an allocation instruction through the service system.

And through the bottom automatic warehouse, a remote dispatching instruction is issued to the unmanned warehouse for the storage instead of the warehouse to directly go out of the warehouse.

In addition, the system can also authorize any level organization to provide data services according to the requirement, and the authorized organization is supported to carry out material financing and logistics organization through the data services.

Open logistics system enabling system logistics organization

Based on the entity internet PI theory, logistics organizations encapsulate materials in modularized and standardized packaging boxes (special and standard material entities), and the packaging boxes are different from the smallest packaging boxes to the shipping containers and can be stacked in layers. The package is easy to handle, store, transport, seal, secure, interlock, load, unload, construct and disassemble, and can be conveniently assembled/disassembled at the nodes. These packages are equivalent to the data packets in the digital internet, and the information part is similar to the header of the data packets in the digital internet, including the information of the material start and delivery addresses.

The transport network and the transport capacity resources formed by the nodes and the transport lines are used as a transportation layer, are similar to a communication subnet in the digital internet, and are used for organizing transportation according to the header information of the packaging boxes so as to send the material entities to the destination. In the logistics transportation organization process, merging (disassembling/combining) planning and dynamic routing selection (selecting a proper next hop node for the packaging box) of the packaging box are reasonably carried out on the transfer node through a standard protocol, so that 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 generation layer (data source), an event acquisition layer, a data management layer, an application service layer and an upper layer application.

a. First layer (bottom layer): critical job event normalization

The key operation event standardization is to define the key operation event of the trigger event to form a standard event, which is the basis of material entity management and is also the 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 specification, including generating entity, combining entity, disassembling entity, transferring entity, in-transit tracking and eliminating entity. The management of the standard events is embedded in the actual business process.

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

The information entity fusion system (CES system) is the core of the system, and the collection and transmission of the information related to the material entity are realized. The CES system carries out unique code identification on the asset through a multi-code fusion system, so that the asset becomes a manageable material entity, corresponding event messages generated by triggering of a bottom standard event are collected through each CES terminal service and transmitted back to CES all-level services and root services, and finally management is carried out in a data center; and the method realizes the tracking of the global materials and supports the raising and logistics organization of the global materials. The enterprise material and logistics organization is more open and flexible.

c. Third layer: data center table

The data center is suitable for the fine operation requirement of enterprises. And by constructing a data middle platform, various data are collected, cleaned, processed, stored and integrated, so that a foundation is laid for data service and upper-layer application.

d. 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 center platform according to the 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 materials staging and logistics organization are supported.

e. Fifth layer (top layer): application system

The application system in the project range comprises an asset capacity visualization system, a logistics task execution system and the like, and aiming at different practical application scenes, user interaction channels such as a PC, a mobile terminal, a large screen and the like are built, so that the service requirements of users are met.

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

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

The seven standard events are described in detail as follows:

a. Generating entities

Generating new material entities. The original codes on the materials are scanned by a handheld terminal; generating unified unique codes of the management domain through a multi-code fusion system and writing the unique codes into the electronic tag; attaching the label to the material entity; and the handheld terminal system uploads the material entity information to the original service management system to complete corresponding service management, and meanwhile, the handheld terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message uploading data center.

b. Combined entity

And (5) boxing/packing the plurality of material entities to form a new material entity. Sweeping an electronic tag of a boxing material entity; boxing/packing; the multi-code fusion system generates a unique code unified in a management domain and writes the unique code into an electronic tag; the label is attached to the new material entity; and the handheld terminal system uploads the material entity information to the original service management system to complete corresponding service management, and meanwhile, the handheld terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message uploading data center.

c. Disassembling entity

One material entity is disassembled and restored into a plurality of material entities. Sweeping an electronic tag of an unpacking material entity; unpacking/unpacking; and the handheld terminal system uploads the material entity information to the original service management system to complete corresponding service management, and meanwhile, the handheld terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message uploading data center.

d. Roll-out entity

The material entity is transferred out from the node. Sweeping out the electronic tags of the material entities; turning out; and the handheld terminal system uploads the material entity information to the original service management system to complete corresponding service management, and meanwhile, the handheld terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message uploading data center.

e. Transfer-in entity

The receiving material entity is transferred to the node. Sweeping into a material entity electronic tag; transferring; and the handheld terminal system uploads the material entity information to the original service management system to complete corresponding service management, and meanwhile, the handheld terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message uploading data center.

f. In-transit tracking

And tracking the position change information of the material entity. The transport body (car, plane, train, etc.) returns the position information at regular time. There are two options: (1) The third party company returns the position information at regular time or according to the transfer node, and transmits the position information to the data center station through the data interface; (2) The black box installed on the transport body during the delivery automatically returns the position information message at fixed time.

g. Eliminating entities

The asset entity disappears from the administrative domain (because the asset is either spent or used). Sweeping the electronic tags of the material entities; recycling the electronic tag; and the handheld terminal system uploads the material entity information to the original service management system to complete corresponding service management, and meanwhile, the handheld terminal system transmits the material entity information to the CES system, and the CES system generates a material entity event message uploading data center.

3.2 information entity fusion System (CES System)

CES (Cyber Entity Systems, information entity fusion system) system is a support enabling system that is the core of an open logistics system enabling system construction and operation.

3.2.1 CES system construction principle

a. Advanced principle

The CES system adopts the international mainstream mature technology, combines the latest entity internet PI theory, EPC, CPS theory and technology, has prospective, and maintains certain technical advancement in a long time in the future.

b. Principle of openness

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

c. Principle of flexibility

The CES system operates independently of the existing asset management system and logistics system, enabling flexible deployment of the system as desired.

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 the high-efficiency interconnection and intercommunication between the distributed CES systems.

e. Principle of security

The CES system separates and transmits the attribute information of the material entity and the entity transition information, thereby guaranteeing the safety of the attribute information of the entity and realizing the safe sharing of the information.

f. Principle of scalability

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

Multi-coding fusion system

Coding standard

The unified unique code of the system adopts the standard GJB+7375-2011 unique identification of military articles, and is about to adopt the 2 nd coding format, namely the variety code. The unique identification (military unique identifier for item, MUII) of the military article, code structure of code format 2 MUII2, is shown in fig. 2:

issuer code (issuingencycode, IAC)

Code assigned to the issuer, which typically has authorization to assign the organization code to the organization.

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

a.1, an authorized full-army organization code management organization;

b.2-authorized national organization code authority;

c 0, 3-9 for standby.

Organization code

The organization code is a code for identifying a unit of unique identification of an article, and is typically a code for identifying a unit of a manufacturer, a supplier, or the like of the article. The organization code should be specified for an authorized full-army organization code authority or a national organization code authority. Code authorities specify codes as required by GB 11714.

The organization code is 9 characters, only contains capital English letters A-Z and numbers 0-9, and does not contain capital English letters O and I.

Variety code

The item code is used to distinguish between 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 a code determined by a authorized military supplies and equipment variety code management mechanism according to the GJB 7001; the item code may also be specified by the entity responsible for the development or design of the item in the event that there is no explicit requirement by the military. The manufacturer, supplier, etc. of the article should ensure that the item code is unique within the organization code.

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

Coding mapping relation

As shown in fig. 3, the multi-coding fusion system passes through the mapping relationship: the unified material unique code-supplier code + supplier material code realizes the fusion operation of multiple material coding systems 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 supplier code to the materials, the attribute information (name, type, quantity, date of production, date of expiration, etc.) of the materials are provided by the current business system and are accessed to the CES system. Wherein data in the current business system originates from local entry or provider exchange provisioning.

The supplier material codes have a one-object one-code and one-class one-code two coding modes, and serial numbers are added at the tail parts of the one-class one-code material to divide the one-class one-code material based on the principle of unique identification (unique identification for item, UII) of the article so as to distinguish the one-class one-code material.

CES information resource library (CES-IR)

The CES system globally maintains information about entities, including material entities and various levels of organization, such as suppliers, carriers, warehouses, etc., involved in logistics activities. The information of these entities is collectively referred to as CES information resource library (CES-IR). As shown in FIG. 4, CES information resource libraries (CES-IR) are divided into two main categories, namely entity dynamic information libraries and entity static information libraries.

Entity class static information base

The entity class 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 storing the attribute information of the material entity in the attribute library of the material entity. The method mainly comprises unique codes, suppliers, supplier codes, product names, types, numbers, production dates and expiration dates; storage requirements, transportation requirements, etc. Wherein, the unique codes of the material entities are endowed by the multi-code fusion system, and other attribute information is inherited from the original supplier management system initially; the expiration date may be calculated based on the date of manufacture and expiration date provided by the original supplier.

Supplier information base

The supplier information base stores supplier information. Mainly including vendor code, name, address, telephone, etc.

Carrier information base

The carrier information is stored in the carrier information base. The method mainly comprises the attributes of carrier mechanism codes, names, addresses and the like.

Node information base

The node information base stores node information. The method mainly comprises the attributes of node codes, names, affiliated institutions, position information and the like. Wherein the node comprises: (1) a warehouse; (2) a transport carrier (being a mobile node), the organization being a 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 event report base and an in-transit tracking information base.

Material entity state library

The material entity state library describes the current content, position, state and the like of the object by taking the material entity object as a unit. The method mainly comprises unique codes, suppliers, supplier codes, product names, types, numbers, production dates and expiration dates; storage requirements, transportation requirements; entity type, entity packaging state, entity object list contained; the node, the valid state (whether available or not, automatically generated according to the current date and the expiration date), the delete mark and the like.

The entity type, the entity packaging state and the entity object list are used for expressing the nesting relationship of the material entities. During the storage and transportation process, the material entities are packaged to form new combined material entities. Thus, the object of the material entity comprises two kinds, namely an original object and a smallest/indissolvable material entity; and secondly, the combined nested objects formed by combining the original objects or other nested objects are called packages, and unique codes are also given as a new material entity. They may be stacked as desired (e.g., warehouse needs, shipping needs). The nested aggregate relationship of such asset entities may be defined by (1) entity types: atom/polymerization; (2) physical packaging state: independent/packaged; (3) the entity object list is contained: the three attributes are described together based on the packing/boxing information generated by the boxing ticket. A typical example and schematic is shown in fig. 5 (a, b):

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

TABLE 1 Material entity object Attribute value

For the combined package, if the valid state of all the original objects in the package is yes (not expired), the package is valid, and if not, the package fails. And sending out early warning information for the material entity object with expiration failure.

Event report library

The event report library is used for storing event messages and mainly comprises attributes such as a message number, an event code, an event type, an entity unique code and the like. Specific attribute information of the material entity is not included.

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

a. entity generation elimination class event

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

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

And (3) disassembly: message number, event code, event type, entity unique code, disassembled entity unique code list and node code.

Elimination: message number, event code, event type, entity unique code, node code.

b. Entity ownership change class event

Transfer into: message number, event code, event type, entity unique code, node code.

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

c. Entity tracking class events

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

In-transit tracking information base

And storing real-time position information of the on-road material entity in an on-road tracking information base, and tracking the position change of the on-road material entity. Mainly comprises a material entity unique code 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 comprises CES clients, CES edge intelligent terminals, CES servers of branches, CES root servers.

The CES root server is deployed at the global headquarter and is combined with the data center, and based on the uploaded event message, the CES-IR information resource library is maintained and updated in real time, so that data support is provided for the agile emergency logistics information service;

the CES server of the branch company is an optional configuration item, can be flexibly configured according to the requirement, is used for accelerating the code analysis speed, and can be deployed in the branch company or a warehouse. More levels of CES servers may also be configured as desired;

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

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

According to the hierarchical coding structure of the unique coding of the multi-coding fusion system, the CES root server maintains a global CES information resource library (CES-IR), other CES servers at all levels have subsets of static information of CES-IR, coding analysis can inquire static attribute information of a material entity through the CES servers at all levels, and analysis requests can also be directly initiated to the CES root server.

CES-IR dynamic maintenance based on event messages

The CES root server updates CES-IR information resource library in real time according to various event messages generated by the triggering of the bottom standard event, mainly a material entity state library in CES-IR, and provides data support for material visualization and raising scheduling. And meanwhile, the event message is stored in an event report library, so that support is provided for inquiring historical events of the material entity.

Entity generation elimination class event

Generating four standard events of an entity, a combination entity, a disassembly entity and an elimination entity, and generating corresponding entity elimination class events: generating entity, combining entity, disassembling entity and eliminating entity.

a. Generating entities

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

b. Combined entity

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

c. disassembling entity

The disassembling entity event causes the composition entity filled with a plurality of material entities to be disassembled and eliminated, so that the uploaded disassembling entity event message is stored in an event report library, and meanwhile, the deletion mark is triggered to be updated from no to yes in the disassembled material entity records in the material entity state library, and the entity package state field of the packaged material entity records is updated from packaged to independent. As shown in fig. 9:

d. eliminating entities

Eliminating entity event causes the material entity to disappear from the management domain (for example, because the material fails or is used), the uploaded eliminating entity event message is stored in an event report library, and meanwhile, the deleting mark in the eliminated material entity record is triggered to update from NO to YES in the material entity state library; in the property entity attribute library, the "delete flag" in the removed property entity record is updated from "no" to "yes". As shown in fig. 10:

Entity ownership change class event

The two standard events of the entity transfer-in and entity transfer-out will generate corresponding entity ownership change event: transfer-in entity, transfer-out entity.

Transfer-in entity

The transfer-in entity event causes the property of the material entity to change, the material entity is received by the new node, the uploaded transfer-in entity event message is stored in the event report library, and meanwhile, the change of the field of the node in the transferred-in material entity record is triggered in the material entity state library, and the name of the node receiving the material entity is changed. As shown in fig. 11:

roll-out entity

The transfer-out entity event causes the property of the material entity to change, the material entity transfers out from the node, the uploaded transfer-out entity event message is stored in the event report library, and meanwhile, the field of the node in the transferred-out material entity record is triggered to change in the state library of the material entity, and the name of the node in which the material entity is received is converted. As shown in fig. 12:

entity tracking class events

Entity tracking events comprise 'in-transit tracking' events, tracking the position change condition of the object of the in-transit material entity, and automatically and regularly returning in-transit tracking event messages containing position information by a transportation body.

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

CES code parsing service

The CES code parsing service is responsible for parsing static attribute information returned to the material entity according to the unique code of the material entity.

The CES code parsing service is closely related to the hierarchical structure of the unique code of the material entity, and is a distributed parsing of the unique code. The unique encoding of the material entity adopts the format of 'issuer code-organization code-variety code-serial number', and the corresponding CES encoding analysis is in a two-stage structure of 'issuer code-organization code', and the architecture is shown in figure 14.

As shown in FIG. 14, the sub-level is added under the organization because the issuing authority of the authority may have authority to assign sub-level organization codes to sub-level organizations as needed. Therefore, each level of organization can be classified in the authority of the organization, unique codes are encoded for material entities, and an internal CES-IR static information base (CES-IR static information subset) is managed.

The CES code parsing process is as follows: the CES client reads a unique code of a material entity and sends an analysis request to the CES edge intelligent terminal based on the unique code; the CES edge intelligent terminal firstly checks a local CES-IR static information subset, if a relevant record is found, analysis is completed, and a result is returned, otherwise, the result is forwarded to a previous CES server (according to configuration); at most, the static attribute information of the material entity corresponding to the unique code is returned to the CES root server (with the global CES-IR stored therein) to complete the analysis

Data center table

The data center of the agile emergency logistics scheduling system mainly realizes unified management of various data, receives data of CES, current business system or third party system, stores and manages the data, and simultaneously provides data service for upper application and other external systems through the agile emergency logistics information service system.

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

CES information resource library information

The CES information resource library (CES-IR) mainly includes dynamic data information such as material entity status information, event message information, in-transit tracking information, and static data information (CES-IR) such as material entity attribute information, vendor information, carrier information, and node information. The data center provides for the collection, processing, and integration of global CES-IR data.

Third party logistics or warehousing information

The part of data is obtained by the data center through the API of the third-party generation storage and transportation company, and is correspondingly processed, the part of data is converted according to the standard format of the system specification, and then is stored in the event report library, and relevant CES-IR information is updated according to rules.

Internal current business system information

The data center of the agile emergency logistics dispatching system is used for interfacing with the current service system as required, acquiring information such as task data and the like, and carrying out association integration, processing, storage and the like on the service information of the current service system and the object information of the material entity and the like in the system through the data center.

Agile emergency logistics information service system

Micro-service architecture

Considering non-functional requirements such as expansibility, maintainability and flexibility of a system, the scheme is based on a SpringBoot framework, an enterprise-level high-availability micro-service architecture system with separated front and back ends is built, and a modular thought is introduced to realize high-cohesion low-coupling application service.

The micro-service architecture has the following advantages:

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

b. Parallel development: because the application is split into independent modules, the development and maintenance can be independently carried out among teams, and the development efficiency is improved.

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

d. Differentiation implementation: aiming at different application scenes and requirements, different deployment is carried out, the access quantity and the concurrency quantity of each functional module are different, and different instance numbers can be deployed for different services through micro-service splitting.

e. The expansibility is high: the service is split so as to facilitate the later addition of new functions, and the progressive development is supported; the upper layer application building function is more flexible and the expansibility is high.

f. High availability: the traditional single application fails to make the whole system unavailable, the micro-service adopts distributed deployment, and each service can have a plurality of instances, even if a certain node is down, only part of the services are affected, and the fault tolerance is high.

Service oriented to agile logistics dispatching system

The agile emergency logistics information service system provides data and application services for upper-layer applications through a micro-service architecture, including but 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 provides multidimensional information inquiry, statistics and visualization services of the material entity based on data managed by the data center table by taking 'assets' as objects, such as asset list, asset classification and quantity, asset storage position and distribution, asset availability status and the like, and provides convenient, rapid and visual presentation for users through upper-layer application.

Transport capacity information service

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

Task information service

The task information service is based on data managed by the data center station, 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 logistics task execution system, and realizes the overall process closed-loop management of the task.

Other application services

Besides the service facing the quick emergency logistics scheduling, the information service system can provide related services for the current service system or other external applications in a micro-service mode, such as data related to task issuing by the current service management system, asset providing, carrying capacity, task execution condition and the like for the external system.

Application system

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

The asset visualization system comprises visualization of assets and transport capacity and provides decision support for emergency material guarantee scheduling. The logistics task execution system mainly realizes closed-loop management for guaranteeing the task to be started and completed. The system can be used for automatic data acquisition, big data analysis, situation display and auxiliary decision support by an enterprise or a company management layer.

Asset capacity visualization system

The asset capacity visualization system obtains object related data, including object names, numbers, states, locations and their changing processes, through the data center. The system provides reports and signboards with various visual angles, and realizes multi-dimensional inquiry and drilling.

Asset list: the multi-stage classification of the materials is taken as a main view angle, and the specific conditions of the materials and the categories are presented through reports, signboards and the like, including but not limited to the quantity (stock), distribution condition (location or position), asset status (validity, schedulability and the like) of the materials of each category.

List of transport capacities: the transport capacity is taken as a main view angle, the transport capacity condition is presented through a map signboard, and the transport capacity system not only comprises self transport capacity such as vehicles, ships, planes, trains and the like, but also comprises transport networks thereof; and the transport capacity and transport network information provided by the third party logistics company.

Service node list: the business points of each unit or warehouse are taken as main visual angles, and unit assets and capacity conditions are presented through reports, signboards and the like, including but not limited to asset types (including multi-level classification), asset quantity (stock of various materials), storage positions, asset states (asset availability, schedulability and the like), self-owned capacity (including available vehicles, ships, planes and trains) and transport networks, third-party logistics company capacity and transport networks and the like.

Destination resource list: the destination is used as a center of a circle, and the asset and the capacity conditions within the radius range of the specified distance are presented, including but not limited to asset types (including multi-level classification), asset quantity (stock of various materials), storage positions, asset states (asset effectiveness, schedulability and the like), self-capacity (including available vehicles, ships, planes and trains) and transport networks, third-party logistics company capacity and transport networks and the like.

Multidimensional query: multi-dimensional queries and data drilling per unit, per object, per state, per location, per time, etc. are supported. And the dynamic circulation process of the material detailed information and the key service points is visually presented.

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

Task initiation and delivery

The logistics task initiator is a head office, and the head office initiates through the logistics task execution system and issues the logistics task to a branch office or a warehouse. The emergency material guarantee logistics tasks are issued to the existing business systems of branch companies, the emergency material allocation plans are issued to the existing business systems of warehouses, and task or plan information comprises material classes, quantity, destinations, time limits and the like.

The task execution process comprises the following steps: the branch company or warehouse receives the task or plan, and then prepares materials, packages/unpacks, sorts out, loads/machines to transport and send to the destination according to the requirement, and then ground personnel search, receive and distribute. The whole execution process involves a plurality of service points such as branch companies, warehouses, collection nodes, ground sites and the like, each service point is provided with a plurality of key operations, and each key operation is transmitted back to a headquarter data center by a fusion terminal and system acquisition data. The logistics task execution system can acquire object data of an execution process through the data center table, and match the object data with task data to realize overall process management.

Task execution results: task execution is completed with the material delivery to the workgroup as termination. The logistics task execution system identifies task execution results, such as normal completion, timeout completion, incomplete, abnormal and the like, based on the data returned by the terminal to the middle station and based on the service requirements.

Example 9:

an open logistics system enabled system, the hardware of which is shown in table 1:

specific rules for data storage

The CES system globally maintains information about entities, including material entities and various levels of organization, such as suppliers, carriers, warehouses, etc., involved in logistics activities. The information of these entities is collectively referred to as CES information resource library (CES-IR). CES information resource libraries (CES-IR) are divided into two major categories, namely entity dynamic information libraries and entity static information libraries.

Entity class static information base

Material entity attribute library

Supplier information base

Carrier information base

Node information base

Entity dynamic information base

Material entity state library

The entity type, the entity packaging state and the entity object list are used for expressing the nesting relationship of the material entities. During the storage and transportation process, the material entities are packaged to form new combined material entities. Thus, the object of the material entity comprises two kinds, namely an original object and a smallest/indissolvable material entity; and secondly, the combined nested objects formed by combining the original objects or other nested objects are called packages, and unique codes are also given as a new material entity. They may be stacked as desired (e.g., warehouse needs, shipping needs). The nested aggregate relationship of such asset entities may be defined by (1) entity types: atom/polymerization; (2) physical packaging state: independent/packaged; (3) the entity object list is contained: the three attributes are described together based on the packing/boxing information generated by the boxing ticket.

Library of event messages: the event report library is used for storing event messages and mainly comprises attributes such as a message number, an event code, an event type, an entity unique code and the like. Specific attribute information of the material entity is not included.

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

a. entity generation elimination class event

Generating: message number, event code, event type, entity unique code, node code. Combination: message number, event code, event type, entity unique code, combined entity unique code list, node code. And (3) disassembly: message number, event code, event type, entity unique code, disassembled entity unique code list and node code. Elimination: message number, event code, event type, entity unique code, node code.

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

c. Entity tracking class events

Tracking in the way: message number, event code, event type, entity unique code, location information. The in-transit tracking information base: and storing real-time position information of the on-road material entity in an on-road tracking information base, and tracking the position change of the on-road material entity. Mainly comprises a material entity unique code and position information (longitude and latitude). The child node accesses the corresponding authorized access rule and flow authorized access rule when the root node data: CES code parsing is in a two-level structure of "issuer code-organizer code", and an authorized issuer may have authorization to assign a sub-level organizer code to a sub-level organization as needed. Therefore, each level of organization can be classified in the authority of the organization, unique codes are encoded for material entities, and an internal CES-IR static information base (CES-IR static information subset) is managed. The access flow is as follows: the CES client reads a unique code of a material entity and sends an analysis request to the CES edge intelligent terminal based on the unique code; the CES edge intelligent terminal firstly checks a local CES-IR static information subset, if a relevant record is found, analysis is completed, and a result is returned, otherwise, the result is forwarded to a previous CES server (according to configuration); and (5) returning static attribute information of the material entity corresponding to the unique code to the CES root server (the global CES-IR is stored) at most, and completing analysis.

The data center and CES edge data updating rule CES root server updates CES-IR information resource library in real time according to various event messages generated by triggering of bottom standard actions, mainly a material entity state library in CES-IR, and provides data support for material visualization and scheduling. And meanwhile, the event message is stored in an event report library, so that support is provided for inquiring historical events of the material entity.

Claims

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

the management universe comprises a plurality of levels of management subdomains; which is a kind ofIn the k-th management subdomain number is denoted as I _k ；I _k K are natural numbers;

Each kth management subdomain is loaded with a kth sub-server;

the external read-write equipment is used for scanning the label of the material entity so as to acquire 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 loaded with a data center; the data center station performs data interaction with the edge intelligent terminal through an external communication network;

the information encoding and storing method comprises the following steps:

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

the entity tracking events comprise material entity in-transit tracking events;

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

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

2. An open logistics system enablement system construction method of claim 1, wherein: the bottom layer node is a material storage and transfer point and comprises a warehouse node, a distribution center, a material collection node and a transportation body node; when the bottom layer node is a carrier node, the position information also comprises carrier real-time geographic position information acquired through a global satellite positioning system.

3. An open logistics system enablement system construction method of claim 1, wherein: the material entity comprises articles and a box body loaded with a plurality of articles;

4. The method for constructing an open logistics 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;

When the standard event type is entity tracking event, the data message also comprises position information;

5. The open logistics system of claim 1, wherein the asset entity generation event comprises an asset entity warehouse entry from a vendor;

the material entity transfer-out event comprises material entity delivery;

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

7. The method of claim 1, wherein the underlying nodes, the sub-nodes, the total nodes, and the material entities each have unique coded information.

8. An open logistics system enablement system, 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 domain, sub servers which are arranged in management domains 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 tag and uploading the standard event triggered by the material entity, the material entity tag information and the position information to the corresponding edge intelligent terminal through the internal communication network, and the edge intelligent terminal uploads the standard event, the material entity tag information and the position information to the data center station through the external communication network; the position information comprises a node code of an edge intelligent terminal and an upper layer node code of the node;

the entity tracking events comprise material entity in-transit tracking events;

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

10. An open logistics system enablement system of claim 9, wherein: the material entity state library also stores information generated by entity combination events, including entity packaging states and object containing lists;