RU2777274C1 - Method for organising a computer logistics network using a tree-type domain hierarchical structure and system for implementation thereof - Google Patents

Abstract

FIELD: computing technology.

SUBSTANCE: invention relates to a method and system for operation of a computer logistics network using a tree-type domain hierarchical structure. Method includes creating, in the computer network, a tree-type hierarchical structure of servers of logistics domains, including control domain servers forming their own subdomains with the users, containing contact information of the subdomain users, accessible only to the control domain; wherein the control domain servers are configured to set trusted relationships between user subdomains; wherein the subdomains within the same domain establish trusted relationships directly using authentication and without providing personal data; wherein subdomains from servers of different domains establish trusted relationships using a request approved in each of the control domain servers.

EFFECT: ensured confidentiality of user information in the computer network.

2 cl, 4 dwg

Description

Technical field

The invention relates to a field of technology designed to organize digital interaction between independent participants in the transport and logistics market among themselves on mutually beneficial terms according to certain rules for setting up trusted relationships.

Thanks to the rules for setting up trust relationships, users of a computer logistics network can be sure of their privacy and the confidentiality of their databases of Customers and Carriers.

Terms and their definitions

For the purposes of this application, the following terms and their definitions are used:

"Domain" - a subset of participants in the logistics network, in which a certain number of Clients and / or Suppliers are grouped.

"Subdomain" - a subset of participants in the logistics network of a domain that is part of a higher-level domain.

“Management domain is a member of the logistics network that performs the function of managing the logistics domain.

"Link" - a connection between two participants in the logistics network, which determines the possibility of commercial interaction between the participants.

"Client" - a member of the logistics network, acting as the end user of the transportation service for which he places an order.

"Carrier" - a member of the logistics network, acting as the final producer of the cargo transportation service.

"Trust Relationships" - relationships between subdomains of Carriers and Clients located in the same domain, using authentication and without providing personal data.

State of the art

US 2016026971 describes a system and method that enables traceability within a professional web-based system for consumer products, accessible to all participants in the supply chain, from source to consumer. The system is able to: identify, select and search for goods; create, host and match lists of buyers and sellers; trade, and confirm purchases; organize logistics such as but not limited to transportation; ensure / obtain full traceability; and record and archive transactions.

Known computer logistics systems developed on the basis of the platform "1C.Enterprise". Within the terminology of the claimed method, an analogue of the claimed method operates according to the scheme shown in Fig. 1, which shows that company domains 301 and 306 are completely isolated from each other. Client 302 (aka Customer, aka Freight Forwarder) of the first company sees only their own carriers 303 and can assign only them to orders. A similar picture for Client 307 of the second company.

Thus, the technical problem of known computerized logistics networks is that these systems operate in isolation from the global logistics market. The aim of the invention is to solve the above technical problem.

The technical result of the claimed invention is the possibility of setting up trusted relationships between subdomains of users, namely Carriers and customers of services (Clients) for the carriage of goods.

Trusted relationships mean relationships between subdomains of Carriers and Clients located in the same domain, using authentication and without providing personal data. Moreover, the user subdomains contain the contact information of the user su 6 of the domain, available only to the owner of the domain.

Thus, domain forwarders can see, by mutual agreement, Carriers and Clients from other domains, can use, for example, the services of a supplier from another domain in case of a shortage of their carriers. Thanks to the rules for setting up trust relationships, users of a computer logistics network can be sure of their privacy and the confidentiality of their databases of Customers and Carriers.

The essence of the invention

The above technical result is achieved due to the fact that the method of organizing a computer logistics network using a domain tree hierarchical structure includes:

creating a hierarchical tree structure of logistical domains in the network, including control domains that form their subdomains with users that contain contact information of subdomain users that is available only to the control domain;

moreover, the control domains are configured to configure trust relationships between user subdomains;

moreover, subdomains located in the same domain establish trust relationships directly, using authentication and without providing personal data;

moreover, subdomains from different domains establish trust relationships with a request that passes approval in each of the control domains.

Implementation of the invention

The method of organizing a computer logistics network using a domain tree hierarchical structure and a system for its implementation is illustrated by the drawings attached to the application.

On FIG. 2 shows the sequence of actions in the method of organizing a computer logistics network, in a scenario where subdomains located in the same domain establish trust relationships directly, using authentication and without providing personal data. When the subdomain of the Carrier wants to obtain a trusted relationship with the Client's subdomain in order to subsequently be able to conclude transportation contracts with it and for the Client to see it in its list of carriers.

The Carrier 501 subdomain, wanting to get a trusted relationship with the Client 502 subdomain, enters the Link Browser (a section in the carrier's personal account that displays all the carrier's links).

In the list of associated participants, the Carrier searches for the subdomain (505) of the desired customer. The trust relationship capability is configured by the managing domains.

515. If the Carrier's subdomain does not find the required Client's subdomain in the visibility list, then the process ends here due to the impossibility of this Carrier's subdomain to create trusted relationships with this Client's subdomain.

506. If the Carrier's subdomain sees the Client's subdomain, then it forms and sends a request for a Link to it.

507. The Client in his personal account sees a request for a Link from the Carrier. He reacts to it.

515. If the Client's subdomain does not agree to the trust relationship, then it rejects the request from the Carrier's subdomain.

508. If the Client's subdomain agrees to a trusted relationship, then it responds positively and the process is moved to the personal account of the managing domain. The rights to create trusted relationships with the given subdomain of the Client are checked.

509. If there are rights to automatically create trust relationships upon request from carriers, then trust relationships are created without the intervention of the management domain.

515. If the Client's subdomain does not have rights to trust relationships with carriers, then the relationship is not created.

510. If the Client's subdomain has rights to trust relationships with carriers only through agreement with the managing domain, then the request is included in the list of approvals. The managing domain sees the request and makes a 511 decision on it.

509. If the governing domain approves the association, then a trust relationship between the Carrier and the Client is created.

515. If the governing domain does not approve the relationship, then no trust relationship is created between the Carrier and the Client.

Two places in the process turn on Time Counter 512:

- Simultaneously with the creation of a communication request 506 from the Carrier's subdomain;

- Simultaneously with the creation of a request for approval 510 in the personal account of the managing domain.

The time counter 512 checks (513) with a certain regularity for the presence of a response from the participant to whom the request is addressed. If there is a response, then the counter ends its work. If there is no response, then the counter checks (514) the timer to see if the time limit has expired. If the time has expired, then the process ends with nothing. If the time has not expired, then the counter goes into the waiting mode for the next iteration.

On FIG. 3 depicts a sequence of steps in a method of organizing a computer logistics network, in a scenario where subdomains from different domains establish trust relationships with a request that passes approval in each of the control domains. When the subdomain of the Carrier 601 wants to get into another Domain in order to expand the list of its potential Clients. In another future control domain 603, he will get without leaving his domain. The method allows one Carrier or Client to be simultaneously in more than one domain.

The Carrier subdomain 601 wants to get 604 to get into another domain. To do this, he goes to the Link Browser and looks for 605 in the visibility list for the future control domain 603.

618. If the Carrier's domain does not find the desired control domain in the visibility list, then the process ends here because this Carrier's domain cannot get into the desired domain.

606. The Carrier subdomain checks to see if another domain has a ban on accepting members from other domains.

618. If there is a ban, then the process ends there.

607. If there is no prohibition, then the Carrier's subdomain forms and sends a trust request to the managing domain.

608. The request intercepts the current control domain 602 of the Carrier 601 and makes a decision. If he does not agree to the presence of his Carrier's subdomain in another domain, then he rejects the request and the process ends with nothing. If the current control domain agrees, then the request is forwarded to the future control domain 603.

609. First, the request is checked at the level of another domain - the other domain has the rights to include participants from other domains.

610. If there is a right to automatically include in another domain, then a trust relationship is created with the future control domain 603.

611. The carrier undergoes an inspection by the Security Service and receives an assessment based on the results of the inspection.

612. The Carrier's subdomain is considered included in another domain and can use the business processes established for this domain.

613. If there is no right to automatically connect participants from other domains, then a request is made to the future control domain for such inclusion of the 601 Carrier domain.

614. Future control domain 603 makes a decision. If he agrees to include the Carrier's subdomain, then the process goes further along the chain 610 ->611 ->612.

618. If the future control domain 603 does not agree with the desire of the Carrier 601 domain, then the process ends there.

Two places in the process turn on Time Counter 615:

- Before the decision of the present control domain 602 on the request of the subdomain of the Carrier 601;

- Simultaneously with the creation of a request 613 to make a decision 614 on the request of the Carrier's subdomain in the personal account of the managing domain.

The time counter 615 checks (616) at regular intervals for a response from the control domain. If there is a response, then the counter ends its work. If there is no answer, then the counter checks (617) the timer - whether the control period has expired. If the time has expired, then the process ends with nothing. If the time has not expired, then the counter goes into the waiting mode for the next iteration.

A computer logistics networking system 701 using a domain tree hierarchical structure is shown in FIG. 4 and consists of the server part 702, where the servers with the infrastructure they need are located, which host the program code and databases, and the client part 703, which includes personal accounts of system participants running on local devices. Carrier 704 can contact the Logistic Domains Module 709 through the personal account, namely, the connection submodule 711 in order to be registered in the Client's logistic domain 707. After the approval procedure, which is provided by the submodule 711, information about successful connection is entered into the Database 710. Information about the inclusion of the Carrier 704 in the logistics domain of the Client 707 is transmitted to the interface of the Client's personal account. When Customer 707 places an order for shipping via order module 708, the system checks the inclusion of Carriers in Customer 707's logistics domain using verification submodule 712, which queries and retrieves information about carriers from database 710 and sends an invitation to order only to those Carriers 704 who are included in its domain. The carrier 704 sends the order parameters to its driver on the phone 706, and the driver executes the order using his vehicle 705.

As used in this application, the terms "module" and "sub-module" refer to a computer entity that is either hardware, or a combination of hardware and software, or software, or executable software. For example, a "submodule" may be, but is not limited to, a process running on a processor, a processor, a hard disk drive, multiple drives (optical and/or magnetic media), an object, an executable, a thread of execution, a program, and/or a computer.

By way of illustration, a "submodule" can be either an application running on a server or the server itself. One or more "sub-modules" may be hosted in a process and/or thread of execution, and a component may be hosted on one computer and/or distributed between two or more computers.

While the above description relates generally to computer instructions that can be executed on one or more computers, those skilled in the art will appreciate that the new embodiment could also be implemented in conjunction with other "sub-modules". In general, "submodules" include procedures, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types.

In addition, those skilled in the art will appreciate that the methods of the invention may be practiced on other computer system configurations, including uniprocessor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, handheld computing devices, microprocessor or programmable consumer electronic devices, etc., each of which can be connected to one or more appropriate devices during operation.

The illustrated aspects may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked to each other via a data network. In a distributed computing environment, "submodules" may be located in local and remote storage devices.

Claims (10)

1. The method of operation of a computer logistics network using a domain tree hierarchical structure, including: - creation in a computer network of a hierarchical tree structure of servers of logistic domains, including servers of control domains that form their subdomains with users that contain contact information of users of the subdomain, available only to the control domain; - moreover, the servers of the control domains are configured to configure trusted relationships between user subdomains; - moreover, subdomains located in the same domain establish trust relationships directly, using authentication and without providing personal data; - moreover, subdomains from servers of different domains establish trust relationships using a request that passes approval in each of the servers of the control domains. 2. The system of operation of a computer logistics network using a domain tree hierarchical structure according to claim 1, including: - a module of logistic domain servers 709, organized in a computer network in a hierarchical tree structure, including servers of control domains, which form their subdomains with computer network users, which contain contact information of subdomain users, available only to the control domain; - a connection submodule 711 configured to set up trust relationships between user subdomains; a validation submodule 712 configured to establish a trust relationship with a request that passes approval at each of the control domain servers; - a database configured to store information about established trust relationships between the specified logistical domains.

Images