Information processing system, information processing method, and program

Abstract

[Problem] To provide an information processing system that determines the validity of a mobile body on the basis of mobile body certification information acquired from the mobile body, and can efficiently select an appropriate mobile body as a delivery candidate. [Solution] This information processing system comprises: an acquisition unit 104 that acquires encrypted mobile body certification information from a mobile body 2; a decryption unit 105 that executes decryption processing on the mobile body certification information; a determination unit 106 that determines whether or not to set the mobile body 2 as a delivery candidate mobile body in accordance with a result of success or failure of the decryption processing; and a delivery management unit 107 that sets a delivery mobile body for delivering a delivery object from among delivery candidate mobile bodies.

Description

Information processing system, information processing method, and program.

[0001] The present disclosure relates to an information processing system, an information processing method, and a program.

[0002] In recent years, autonomous controllable moving bodies such as flying bodies such as drones (Drones) and unmanned aerial vehicles (UAVs: Unmanned Aerial Vehicles) and running bodies such as unmanned ground vehicles (UGVs: Unmanned Ground Vehicles) have begun to be used in the industry. Patent Document 1 discloses the delivery of delivery items by a flying body.

[0003] Japanese Patent Application Laid-Open No. 2021-160887

[0004] In such a delivery system, as disclosed in Patent Document 1, although it is assumed that a plurality of moving bodies are delivery control targets, in a demonstration experiment, virtual delivery goods (for example, daily necessities and foodstuffs) within the range that can be loaded on one moving body are set, and test delivery flights are made at the timing when a predetermined route can be flown.

[0005] However, since more delivery trips than those in a demonstration experiment may occur in the future, it is conceivable to use a large number of moving bodies. Therefore, it is desired that the management of those moving bodies (especially the management of the legitimacy of each moving body) be ensured on the system. [[ID=1!]]

[0006] Therefore, the present disclosure provides an information processing system, an information processing method, and a program that can determine the legitimacy of a moving body based on the moving body certification information acquired from the moving body and efficiently select an appropriate moving body as a delivery candidate.

[0007] To solve the above problems, an information processing system according to one aspect of the present invention includes an acquisition unit that acquires encrypted moving body certification information from a moving body, a decryption unit that executes a decryption process on the moving body certification information, a determination unit that determines whether to set the moving body as a delivery candidate moving body according to the success or failure result of the decryption process, and a delivery management unit that sets a delivery moving body that delivers a delivery item from among the delivery candidate moving bodies.

[0008] Further issues disclosed in this application and their solutions will be made clear in the section on embodiments of the invention and in the drawings.

[0009] This disclosure can improve the safety and reliability of delivery services.

[0010] This figure shows the configuration of an information processing system according to an embodiment of the present invention. This is a block diagram showing the hardware configuration of the management server in Figure 1. This figure shows an example of the configuration of the mobile unit in Figure 1. This is a block diagram showing the hardware configuration of the user terminal and worker terminal in Figure 1. This is a block diagram showing the hardware configuration of the authentication server in Figure 1. This is a block diagram showing the functions of the control unit of the management server in Figure 2. This is a block diagram showing the storage structure of the management server in Figure 2. This is an example illustrating a delivery schedule according to an embodiment of the present invention. This is a block diagram showing the functions of the control unit of the authentication server in Figure 5. This is a block diagram showing the storage structure of the authentication server in Figure 5. This is a block diagram showing the functions of the control unit of the mobile unit in Figure 3. This is a block diagram showing the storage structure of the mobile unit in Figure 3. This is a flowchart of the information processing method relating to the authentication server in Figure 5, among the information processing methods according to an embodiment of the present invention. This is a flowchart of the information processing method relating to the mobile unit in Figure 3, among the information processing methods according to an embodiment of the present invention. This is a flowchart of the information processing method relating to the management server in Figure 2, among the information processing methods according to an embodiment of the present invention.

[0011] The embodiments of the present invention will be described below. An information processing system according to an embodiment of the present invention has the following configuration: [Item 1] An information processing system comprising: an acquisition unit that acquires encrypted mobile identity information from a mobile body; a decryption unit that performs a decryption process on the mobile identity information; a determination unit that determines whether or not to set the mobile body as a candidate mobile body for delivery according to the success or failure result of the decryption process; and a delivery management unit that sets a delivery mobile body to deliver the delivered goods from among the candidate mobile bodies for delivery. [Item 2] The information processing system according to Item 1, wherein the mobile identity information includes plain text and aircraft identification information. [Item 3] The information processing system according to Item 1, wherein if the determination unit determines that the mobile identity information is incorrect as a result of the decryption process, the mobile body corresponding to the mobile identity information is not included in the target for setting as a candidate mobile body for delivery. [Item 4] The information processing system according to Item 1, further comprising a candidate mobile body storage unit for storing the candidate mobile bodies for delivery, wherein the determination unit does not store the mobile body corresponding to the mobile body certification information in the candidate storage unit if it determines that the mobile body certification information is incorrect as a result of the decoding process. [Item 5] The information processing system according to Item 1, further comprising a candidate mobile body storage unit for storing the candidate mobile bodies for delivery, wherein the determination unit stores the status of the mobile body corresponding to the mobile body certification information as an error if it determines that the mobile body certification information is incorrect as a result of the decoding process. [Item 6] The information processing system according to Item 2, wherein the plaintext includes at least expiration date information. [Item 7] The information processing system according to Item 2, wherein the plaintext includes at least regulation pass / fail information. [Item 8] The information processing system according to Item 2, wherein the plaintext includes at least manufacturer information. [Item 9] The information processing system according to Item 2, wherein the aircraft identification information includes at least manufacturer identification information. [Item 10] The information processing system according to Item 2, wherein the aircraft identification information includes at least aircraft serial information. [Item 11] The aircraft identification information includes at least the operational system identification information, as described in Item 2.[Item 12] An information processing method that is executed in an information processing system, comprising the steps of: an acquisition unit acquiring encrypted mobile identity information from a mobile body; a decryption unit performing a decryption process on the mobile identity information; a determination unit determining whether or not to set the mobile body as a candidate delivery mobile body according to the success or failure result of the decryption process; and a delivery management unit setting a delivery mobile body to deliver the goods from among the candidate delivery mobile bodies. [Item 13] A program that causes an information processing system to execute the steps of: an acquisition unit acquiring encrypted mobile identity information from a mobile body; a decryption unit performing a decryption process on the mobile identity information; a determination unit determining whether or not to set the mobile body as a candidate delivery mobile body according to the success or failure result of the decryption process; and a delivery management unit setting a delivery mobile body to deliver the goods from among the candidate delivery mobile bodies.

[0012] Embodiments of the present invention will now be described in detail with reference to the drawings. In the accompanying drawings, identical or similar elements are given identical or similar reference numerals and names, and redundant descriptions of identical or similar elements may be omitted in the description of each embodiment. Furthermore, the features shown in this embodiment are applicable to other embodiments as long as they do not contradict each other.

[0013] <Configuration> Figure 1 shows the overall configuration of the information processing system according to this embodiment. The information processing system according to this embodiment includes a management server 1 (also called an "information processing device"), one or more mobile devices 2, one or more user terminals 3, one or more worker terminals 4, and an authentication server 6 (which may also be called an "information processing device"), and is connected to each other via a communication network NW so that they can communicate with each other. Note that the illustrated configuration is just an example and is not limited thereto.

[0014] <Management Server 1> Figure 2 shows the hardware configuration of Management Server 1. Note that the configuration shown is just one example, and other configurations are also possible.

[0015] The management server 1 may be a general-purpose computer such as a workstation or personal computer, or it may be logically implemented through cloud computing.

[0016] The management server 1 comprises at least a control unit 10, memory 11, storage 12, a transmitting / receiving unit 13, an input / output unit 14, etc., which are electrically connected to each other via a bus 15.

[0017] The control unit 10 is a computing device that controls the operation of the entire management server 1, controls the transmission and reception of data between each element, and performs information processing necessary for application execution and authentication processing. For example, the control unit 10 is a CPU (Central Processing Unit) and / or a GPU (Graphics Processing Unit), and executes programs for this system stored in the storage 12 and loaded into the memory 11 to perform various information processing tasks.

[0018] Memory 11 includes main memory, which is composed of volatile storage devices such as DRAM (Dynamic Random Access Memory), and auxiliary memory, which is composed of non-volatile storage devices such as flash memory and HDD (Hard Disk Drive). Memory 11 is used as a work area for the processor 10, and also stores the BIOS (Basic Input / Output System) executed when the management server 1 starts up, as well as various configuration information.

[0019] Storage 12 stores various programs, such as application programs. A database containing data used for each process may also be built on storage 12.

[0020] The transmitting / receiving unit 13 connects the management server 1 to the communication network NW. The transmitting / receiving unit 13 may also be equipped with Bluetooth® and BLE (Bluetooth Low Energy) short-range communication interfaces. The transmitting / receiving unit 13 transmits various information (including requests) to and receives various information (including requests) from external devices (e.g., mobile device 2, user terminal 3, worker terminal 4, etc.) that are directly or indirectly connected to the management server 1 via the network NW.

[0021] The input / output unit 14 consists of information input devices such as keyboards and mice, and output devices such as displays.

[0022] Bus 15 is connected in common to all of the above elements and transmits, for example, address signals, data signals, and various control signals.

[0023] <Mobile Unit 2> Mobile unit 2 according to this embodiment is a mobile unit used in delivery operations such as delivering or collecting goods. For example, mobile unit 2 is used when delivering goods requested by a user from a warehouse or the like where the goods are stored.

[0024] The mobile body 2 according to this embodiment includes an unmanned mobile body that moves by autonomous control. For example, the unmanned mobile body may move by autonomous control using input information such as the positions of two points, such as a starting point (e.g., the delivery start position of the delivered goods or the starting position of the unmanned mobile body) and an ending point (e.g., the delivery receipt position (including the proxy receipt position)), or three or more points, including an intermediate point (e.g., the delivery collection position in the case of delivery involving collection of goods) and a return point (e.g., the same position as the starting position of the unmanned mobile body, or a different waiting position). The input information used for autonomous control may also include various other information such as intermediate points and delivery routes.

[0025] Furthermore, the control unit of the mobile unit 2 (for example, the CPU and chipset) may be configured to periodically or at any time to transmit mobile unit information to at least one of the management server 1, user terminal 3, or worker terminal 4 via the network. Alternatively, the control unit of the mobile unit 2 may be configured to transmit mobile unit information to at least one of the control units of the management server 1, user terminal 3, or worker terminal 4, which may periodically or at predetermined intervals, and in response, the mobile unit 2 may transmit the mobile unit information. Mobile entity information may include, for example, mobile entity control information (for example, control amount information for the propulsion configuration of mobile entity 2 (for example, rotor blades of an aircraft or tires of a self-propelled vehicle), position information (position information indicating the position represented by two-dimensional coordinates (for example, latitude and longitude coordinates) or three-dimensional coordinates (for example, latitude, longitude and height))), altitude information, battery charge amount information (especially charge capacity information, remaining charge information, etc.), and history information related to the mobile entity's usage history (for example, cumulative number of battery charges, cumulative number of flights (e.g., 2 times per delivery, for delivery and return), cumulative number of deliveries, cumulative number of abnormal occurrences (especially abnormalities described later, such as when the position does not match the standard during landing or unloading), and the cumulative number that is reset at predetermined timings such as inspections).

[0026] Furthermore, the unmanned mobile unit may be moved by remote control using operation information remotely entered by the administrator managing the unmanned mobile unit.

[0027] For example, the unmanned mobile vehicle may be an aircraft as shown in Figure 3 (a so-called drone or UAV (Unmanned Aerial Vehicle)), and may have, for example, a loading section 30 capable of loading deliveries. The loading section 30 may be configured to rotate independently of the aircraft body around a rotation axis 31, and may be controlled to maintain the delivery placed inside the loading section 30 horizontally during flight (including during hovering, cruising, etc.). Note that loading deliveries inside the loading section 30 may include the delivery being stored in a container (for example, a cardboard box) and then loaded, or the delivery being directly placed inside the loading section 30 and then loaded.

[0028] Furthermore, the unmanned mobile vehicle may have a loading section located inside the aircraft (as illustrated in Figure 3) or outside the aircraft (for example, a known type located on the underside of the aircraft). The loading section may be provided with a loading port for loading goods and an unloading port for unloading goods. The loading port and unloading port may be located in the same space (hole) or in different locations. If they are located in different locations, it is preferable that the loading port be located on the upper side of the aircraft and the unloading port on the lower side, but this is not limited to this. The loading port may be located on the rear, front, bottom, top, right side, or left side of the aircraft, and the unloading port may be located in a different location on the rear, front, bottom, top, right side, or left side (for example, the loading port may be on the rear and the unloading port on the lower side, or any other combination). The loading port may be provided with a cover mechanism (which may also be the aircraft cover), which may be opened and closed manually or automatically according to a control signal. The unloading port may be equipped with an opening and closing mechanism, which can be opened and closed manually or automatically according to a control signal. For example, after loading the goods into the loading port, the lid may be closed manually, the aircraft may fly along a predetermined flight path, and after landing, the unloading port may automatically begin opening control (goods release control) to disable the support structure that supports the bottom of the goods, so that the goods can be placed on the goods placement surface.

[0029] Furthermore, the unmanned mobile vehicle according to this embodiment is not limited to an aerial vehicle. For example, the unmanned mobile vehicle may be a vehicle that moves on land, such as an UGV (Unmanned Ground Vehicle) as shown in Figure 1, or a vessel that moves on waterways such as sea or river routes. The detailed configuration may be the same as that of the drone described above.

[0030] Furthermore, for example, mobile body 2 includes a manned mobile body used by a delivery person to deliver or collect goods.

[0031] For example, the manned mobile body according to this embodiment may be a vehicle that travels by land (e.g., a passenger car, a light truck, a light van or other cargo vehicle, a motorcycle, a bicycle, a kick scooter, etc.). However, the manned mobile body is not limited to a vehicle. For example, the manned mobile body may be an aircraft that flies by air, or a vessel that travels by waterways such as sea or river. For example, a configuration that can store delivery items, such as the trunk of a passenger car, the cargo area of ​​a light van, or a luggage container provided on a motorcycle, can be considered the above-mentioned loading unit. In this case, the manned mobile body (especially the loading unit) may be configured to enable direct communication of necessary information by mounting a separately attachable information processing device (including a control unit and a memory unit, etc.) on it, or it may be configured to enable indirect communication via a network from the information processing device to a passenger terminal (not shown) held by the passenger of the manned mobile body.

[0032] Furthermore, the mobile body 2 may be a mobile body capable of traveling along at least two or more routes, including land, water, and air routes.

[0033] <User Terminal 3, Worker Terminal 4> The user terminal 3 shown in Figure 4 is an information processing device such as a personal computer, tablet, smartphone, mobile phone, PHS, or PDA, which is owned by the user. The user terminal 3 also includes a control unit 20, memory 21, storage 22, transmission / reception unit 23, input / output unit 24, etc., which are electrically connected to each other via a bus 25. The main functions of each element can be configured in the same way as the management server 1 described above, so a detailed explanation of each element is omitted. The worker terminal 4 is an information processing device such as a personal computer, tablet, smartphone, mobile phone, PHS, or PDA, which is owned by a worker who manages deliveries at a collection center, etc. The main functions of each element can be configured in the same way as the user terminal 3 described above, so a detailed explanation of each element is omitted.

[0034] <Authentication Server 6> The authentication server 6 shown in Figure 5, like the management server 1, may be a general-purpose computer such as a workstation or personal computer, or it may be logically implemented by cloud computing. The authentication server 6 also includes a control unit 60, memory 61, storage 62, transmission / reception unit 63, input / output unit 64, etc., which are electrically connected to each other via a bus 65. Since the main functions of each element can be configured in the same way as the management server 1 described above, a detailed explanation of each element will be omitted.

[0035] <Functions of Management Server 1> Figure 6 is a block diagram illustrating the functions implemented in the control unit 10 of the management server 1, and Figure 7 is a block diagram illustrating the information stored in the storage 12. In this embodiment, the control unit 10 of the management server 1 includes a screen information generation unit 102, a data management unit 103, an acquisition unit 104, a decoding unit 105, a determination unit 106, and a delivery management unit 107 as functional units. The storage 12 also includes various databases such as a candidate mobile object storage unit 121.

[0036] The screen information generation unit 102 generates screen information that is displayed via the user interface of the user terminal 3 or worker terminal 4. The screen information may be, for example, user interface screen information generated by arranging various images and text based on predetermined layout rules, using image and text data stored in the storage 12 as source material. The screen information generation unit 102 may also be a functional unit executed by the control unit 20 by an application (including a web browser) stored in each user terminal 3, etc. That is, the management server 1 transmits information necessary to generate a user interface screen, such as image data, and the application in the user terminal 3, etc., generates a user interface screen based on this necessary information and predetermined layout rules, and displays it on the user terminal 3. Processing related to the screen information generation unit 102 can also be executed by a GPU (Graphics Processing Unit).

[0037] The data management unit 103 performs data management such as transmitting various information received by the transmission / reception unit 13 to various functional units and acquiring various information from various functional units.

[0038] The acquisition unit 104 acquires encrypted mobile device authentication information from the mobile device 2. The acquisition unit 100 may, for example, receive mobile device authentication information in response to periodic transmissions from the mobile device 2, or acquire mobile device authentication information from the mobile device 2 in response to acquisition requests transmitted from the management server 1, user terminal 3, or worker terminal 4. The acquisition unit 104 can acquire mobile device authentication information via wired or wireless communication. Specifically, the acquisition unit 100 can acquire mobile device authentication information using the TCP / IP protocol, HTTPS, or a dedicated protocol.

[0039] The decryption unit 105 performs a decryption process on the encrypted mobile identity information obtained by the acquisition unit 104. The decryption unit 105 performs the decryption process using a pre-set decryption key, such as one obtained from the acquisition unit 104. After performing the decryption process, the decryption unit 105 transmits the success or failure result of the decryption process to the determination unit 106. The decryption unit 105 determines one of the following states as a result of the decryption process: (1) a "success" state indicating that the encrypted mobile identity information was successfully decrypted and the decrypted information is in a valid format; (2) a "format error" state indicating that the encrypted mobile identity information was decrypted but the decrypted information is not in a valid format; or (3) a "decryption error" state indicating that the encrypted mobile identity information could not be decrypted. The decryption unit 105 transmits these determination results to the determination unit 106 as a success or failure result.

[0040] The decryption unit 105 can perform decryption processing based on existing methods such as public-key cryptography, symmetric-key cryptography, or hybrid methods. Specifically, it can perform decryption processing corresponding to RSA encryption, AES encryption, or other encryption methods. Detailed examples of encryption will be described later.

[0041] The determination unit 106 determines whether or not to set the mobile body 2 associated with the decrypted mobile body identification information as a candidate mobile body for delivery, based on the success or failure result of the decryption process obtained from the decryption unit 105. The data management unit 103 stores the mobile body information (e.g., aircraft identification information) related to the mobile body 2 associated with the decrypted mobile body identification information in the candidate mobile body storage unit 121 as a candidate mobile body for delivery, based on the determination result obtained from the determination unit 106.

[0042] As a specific example, the determination unit 106 performs the following determination process. First, if the success / failure result received from the decryption unit 105 is in the "success" state, the determination unit 106 performs the following verifications on the contents of the decrypted mobile identity information: (1) Verification of the expiration date information (whether the current date and time is within the expiration period), (2) Verification of the regulation compliance information (whether all necessary regulatory requirements are met), and (3) Verification of the mobile identity information (whether it conforms to a legitimate identity information system). If all of these verifications are passed, the determination unit 106 determines that the mobile entity should be set as a candidate mobile entity for delivery. On the other hand, if the success / failure result is in the "formula error" state or the "decryption error" state, or if any of the above verifications are failed, the determination unit 106 determines that the mobile entity should not be set as a candidate mobile entity for delivery.

[0043] Here, if the determination unit 106 determines that the mobile entity authentication information is incorrect, it may record the determination result as history in the storage 12. Specifically, for example, the mobile entity's identification information, the date and time of determination, and the type of error (format error, decryption error, etc.) may be recorded. The determination unit 106 refers to this history and determines that there is a high probability that a mobile entity is invalid if it has recorded more than a predetermined number of determination errors within a predetermined period, and permanently excludes it from the list of mobile entities for delivery. Mobile entities that have been permanently excluded are configured and managed so that they cannot be re-registered as mobile entities for delivery even if they are determined to be in a "successful" state, unless a special approval procedure is followed by the administrator.

[0044] The setting process of the delivery candidate mobile body by the determination unit 106 may be specifically executed as follows. When the determination unit 106 determines to set a mobile body as a delivery candidate mobile body, it generates the following exemplified information regarding the mobile body as candidate mobile body information: (1) mobile body identification information, (2) performance information of the mobile body (maximum loading weight, maximum flight distance, maximum flight time, etc.), (3) status information of the mobile body (current position, remaining battery level, maintenance status, etc.), (4) operation restriction information (flightable time zone, flightable area, etc.). The generated candidate mobile body information is stored in the candidate mobile body storage unit 121 via the data management unit 103.

[0045] The mobile body certification information includes plain text and mobile body identification information (also referred to as aircraft identification information). The plain text includes at least one of expiration date information, regulation compliance information, and manufacturer information. The mobile body identification information includes at least one of manufacturer identification information, aircraft serial information, and operation system identification information, etc. These pieces of information may be included alone or in any combination.

[0046] The expiration date information is information indicating the expiration date of the mobile body certification information. The expiration date information may include, for example, the start date and time and end date and time of the expiration date, or may include information indicating the expiration period. The expiration date information may be described in the format of year, month, day, hour, minute, and second, or may be described in the epoch time format. Also, the expiration date information may be expressed as a relative period from the issue date and time of the certificate. The expiration date information may be configured to be updated periodically, for example, updated every predetermined period such as 1 day, 1 week, 1 month, 3 months, 6 months, 1 year, etc. Furthermore, the expiration date information may be configured to be updated in conjunction with the inspection period or maintenance period of the mobile body.

[0047] The regulation compliance information is information indicating the compliance of a moving object with various regulations. Specific examples include information indicating compliance or non-compliance with regulations regarding the allowable altitude, allowable speed, allowable flight time zone, allowable flight area, weight limit, size limit, weather condition limit, safety standards, and operator qualification requirements, etc. for each regulatory requirement.

[0048] The regulation compliance information includes at least one of, for example, the type compliance information regarding the type of the moving object and the aircraft compliance information regarding an individual moving object. The type compliance information is information indicating that the type of the moving object itself complies with the regulatory requirements, and includes, for example, the confirmation result that each component constituting the moving object is included in the approved parts list, and the confirmation result that the specifications of the moving object meet the requirements of the regulation checklist. The aircraft compliance information is information indicating that an individual moving object complies with the regulatory requirements in actual operation, and includes, for example, the dynamic compliance evaluation results based on the inspection results during manufacture, the periodic inspection results, the operation status and operation performance, etc.

[0049] The regulation compliance information is generated based on the inspection results by the manufacturer or the inspector of the moving object. The inspection results include the confirmation results based on a predetermined regulation checklist, and the confirmation results are recorded together with the type information and the manufacturing number of the moving object. These information can be expressed, for example, by true or false values (0 or 1, YES or NO, etc.).

[0050] The generation and verification of regulation compliance information is carried out, for example, through the following process: First, the type information of the mobile body and the type information of each component are compared with the information registered in the approved parts list. Next, the results of the checks based on the mobile body's regulation checklist are verified. Once these checks and verifications are completed, the regulation compliance information is certified as valid information. The regulation compliance information may be configured to be updatable in response to revisions of laws and regulations or changes in operational standards, or it may be configured to be updatable based on the results of periodic conformity assessments.

[0051] To ensure the reliability of regulation compliance information, the information may be authenticated by a certification authority server, and the authentication result may be issued as a type approval certificate. The type approval certificate is stored in the certificate memory installed on the mobile device and used for authentication as needed. This ensures that the mobile device's compliance with regulations is reliably confirmed.

[0052] Manufacturer information provides details about the manufacturing of the mobile device. Specifically, it includes the manufacturer's name, country of manufacture, date of manufacture, manufacturing plant, product model name, service life, recommended inspection cycle, and recommended parts replacement cycle. Manufacturer information can be used as necessary information for the maintenance and quality control of the mobile device.

[0053] Mobile object identification information is a set of information used to uniquely identify individual mobile objects.

[0054] Manufacturer identification information is information that identifies the manufacturer of the mobile device, and can include, for example, manufacturer codes established by the International Organization for Standardization (ISO) or manufacturer codes established by industry associations.

[0055] The aircraft serial information is information used by the manufacturer to individually identify each mobile unit it has produced. For example, it may include a manufacturing number, a product number, or a combination of these.

[0056] Operation system identification information is information that identifies the system that manages the operation of a mobile vehicle. For example, it can be an identifier for the operation management system, an identifier for the operating company, or a combination of these.

[0057] Mobile object identification information may be configured to have a hierarchical structure. For example, it can be configured to identify mobile objects at multiple levels, such as manufacturer identification information at the upper level, product model identification information at the middle level, and individual aircraft identification information at the lower level. Furthermore, mobile object identification information may be configured to include identification information based on multiple identification systems in order to comply with regulations specific to each region or country.

[0058] The candidate mobile object storage unit 121 stores information about the mobile object 2 that has been set as a candidate mobile object for delivery by the determination unit 106. The candidate mobile object storage unit 121 can be implemented as, for example, a relational database, a NoSQL database, or a file system. The candidate mobile body storage unit 121 may store any of the following as mobile body information: for example, mobile body identification information (manufacturer type information that identifies the manufacturer that produced the mobile body, management company type information that identifies the management company that manages the mobile body, mobile body type information that identifies the product type or unique type of the mobile body (including mobile body product type information and mobile body unique type information), mobile body registration identification information assigned to each registered mobile body, mobile body system identification information that identifies the type of system to which the mobile body is connected, etc.), mobile body control information (for example, control amount information of the propulsion configuration of the mobile body 2 (for example, rotor blades of an aircraft or tires of a self-propelled vehicle, etc.), position information (position information that indicates the position represented by two-dimensional coordinates (for example, latitude and longitude coordinates) or three-dimensional coordinates (for example, latitude, longitude and height)), altitude information, battery charge amount information (especially chargeable amount information, remaining charge information, etc.), history information (for example, cumulative number of battery charges, cumulative number of flights, cumulative number of deliveries, cumulative number of abnormal occurrences, and cumulative counts that are reset at predetermined timings such as inspections), mobile body inspection information that indicates whether a predetermined inspection of the mobile body has been completed or not. The candidate mobile body storage unit 121 can also store status information of the mobile body 2 (for example, before delivery preparation, during delivery preparation, delivery preparation complete, during delivery, returning, delivery completed, etc.).

[0059] The delivery management unit 107 selects a delivery vehicle to deliver the goods from among the candidate delivery vehicles. The delivery management unit 107 selects a delivery vehicle based on one of the following selection algorithms: (1) Evaluation of essential conditions - The weight of the goods is less than or equal to the maximum load capacity of the vehicle. - The size of the goods is within the size that the vehicle can carry. - The distance to the delivery destination is within the maximum flight distance of the vehicle. - The estimated delivery completion time from the vehicle's current position is within the vehicle's operating time limit. (2) Evaluation of priority - Delivery efficiency score (evaluation based on predicted energy consumption) - Time efficiency score (evaluation based on the speed of the estimated delivery completion time) - Cost score (evaluation based on operating costs) (3) Calculation of overall score - Weight each evaluation item is applied to calculate an overall score - The vehicle with the highest overall score is selected. (4) Selection of alternative vehicles - If the selected vehicle is unavailable, multiple alternative vehicles are selected in order of overall score.

[0060] The delivery management unit 107 can also employ a selection method using machine learning. In this case, the delivery management unit 107 uses past delivery performance data as training data to predict indicators such as delivery success rate, time efficiency, and energy efficiency. The training data includes information such as flight logs of the mobile vehicle, delivery completion time, energy consumption, weather conditions, and traffic conditions. Using this information, the delivery management unit 107 constructs machine learning models such as neural networks and random forests to select the optimal mobile vehicle for new delivery requests. In addition, the delivery management unit 107 periodically retrains itself using new delivery performance data to improve prediction accuracy.

[0061] The delivery management unit 107 can also employ a selection method using a multi-agent system. In this case, the delivery management unit 107 treats each mobile object as an agent and provides a messaging function between agents. Each agent optimizes the assignment of delivery tasks while considering its own status (location, battery level, load capacity, etc.) and the status of other agents. The delivery management unit 107 also controls the cooperative operation between agents, enabling real-time status changes and autonomous selection of alternative routes in the event of failures. Standard protocols such as FIPA (Foundation for Intelligent Physical Agents) can be used as the communication protocol between agents.

[0062] The delivery management unit 107 can also employ a selection method using a genetic algorithm. In this case, the delivery management unit 107 represents the combination of delivery routes and mobile units as chromosomes and performs optimization considering multiple constraints. Specifically, it calculates fitness based on evaluation functions such as delivery time, energy consumption, and cost, and searches for the optimal solution by repeatedly performing genetic operations such as selection, crossover, and mutation. To avoid the risk of falling into a local minimum, the delivery management unit 107 starts the search from multiple initial solutions and also has a function to appropriately adjust the mutation rate.

[0063] The delivery management unit 107 can also employ a selection method using a priority queue. In this case, the delivery management unit 107 calculates a priority score for each mobile unit and manages them in order based on the score. The priority score is calculated based on multiple evaluation criteria, such as the mobile unit's current location, battery level, past delivery performance, and maintenance status. Each evaluation criterion is assigned a weight, which is dynamically adjusted according to the urgency and importance of the delivery. The delivery management unit 107 updates the queue contents in real time and can always select the optimal mobile unit for new delivery requests and urgent delivery requests.

[0064] The delivery management unit 107 can use the above selection methods individually or in combination with other methods. For example, it can use prediction results from machine learning as the initial solution for a genetic algorithm, or implement a priority queue for each agent in a multi-agent system. The delivery management unit 107 may also have a function to dynamically switch the appropriate selection method depending on the type of delivery (normal delivery, emergency delivery, reserved delivery, etc.) and the situation (normal, busy, emergency, etc.). The processing results of each selection method are recorded in the delivery information storage unit 122 and used to improve and optimize the system.

[0065] The delivery management unit 107 generates information about the selected delivery vehicle as delivery vehicle information and stores this information in the delivery information storage unit 122. The delivery vehicle information may include vehicle identification information, delivery route information, delivery schedule information, and predicted energy consumption information. The delivery management unit 107 can also periodically re-evaluate the selection results and change the delivery vehicle as necessary.

[0066] Furthermore, the delivery management unit 107 may also have a movement instruction function that controls the movement instructions for the mobile unit 2 to deliver the goods. The movement instruction function may be configured as a functional unit of a separately provided operation management server (not shown).

[0067] Furthermore, the delivery management unit 107 may have a delivery schedule management function that manages delivery plans and delivery schedules related to deliveries and collections by the mobile unit 2. The delivery schedule management function may be configured as a functional unit of a separately provided delivery schedule management server (not shown).

[0068] The delivery management unit 107 may be configured to register the delivery schedule for delivery or collection of a delivery item in the delivery slot of the delivery plan for deliveries that require setting a delivery schedule due to the registration of information such as the addition of delivery identification information or the association of user identification information in the delivery information storage unit 122 described later.

[0069] A delivery slot is a time frame (also called a time zone) during which the mobile unit 2 responds to delivery requests. For example, the daily delivery plan of mobile unit 2 is divided into predetermined delivery slots (for example, 15 minutes or 30 minutes for an unmanned mobile unit, or 1 hour for a manned mobile unit), and mobile unit 2 delivers the registered items for each delivery slot in accordance with the time indicated by that delivery slot (at least starts the delivery). In the case of an unmanned mobile unit, a delivery slot may, for example, contain items to be delivered to destinations such as 1 or 2, but is not limited to this.

[0070] Figure 8 is an explanatory diagram illustrating an example of a delivery slot according to this embodiment. For example, the daily delivery plan DS of the mobile unit 2 is divided into predetermined delivery slots (e.g., 15 minutes), and the items to be delivered, registered for each delivery slot, are delivered by mobile units registered for each delivery slot or delivery route at the time indicated by the delivery slot. Such a combination of delivery plan DS and delivery slots may be set for each of multiple candidate receiving locations (e.g., for each of multiple delivery routes).

[0071] For example, a delivery plan DS set at a certain receiving location includes two types of delivery slots: a "full" delivery slot (hereinafter referred to as "full slot DF") indicating that the delivery schedule by the mobile unit 2 is already filled, and an "available" delivery slot (hereinafter referred to as "available slot DE") indicating that there is availability in the delivery schedule by the mobile unit 2. These are stored, updated, and managed as delivery information in the delivery information storage unit 122 by the delivery schedule management function.

[0072] In particular, when registering mobile units for each delivery slot, the delivery schedule management function may refer to the mobile unit information stored in the candidate mobile unit storage unit 121 to search for mobile units that have a status indicating they are available for delivery and assign them to the corresponding delivery slot.

[0073] Furthermore, the delivery schedule management function may also allow the registration of future delivery schedules (especially delivery slots) based on delivery requests. Alternatively, or in addition to this, if the current delivery schedule is feasible, the delivery schedule management function may refer to the mobile body information stored in the candidate mobile body storage unit 121 to search for a mobile body indicating a status that allows for delivery, assign a currently available mobile body, and / or transmit information identifying the corresponding mobile body (e.g., mobile body identification information, especially mobile body identification information) to the worker terminal 4 for presentation to the worker.

[0074] Furthermore, the delivery schedule management function may be configured to store delivery-related status information linked to the delivery schedule (especially each delivery slot). The delivery schedule management function may also be configured to transmit some or all of the delivery information and delivery-related status information in the delivery schedule (especially each delivery slot) to the user terminal 3 or worker terminal 4 for viewing and presentation to the worker.

[0075] The delivery information stored in the delivery information storage unit 122 may include, for example, delivery identification information, delivery mobile information, user identification information (e.g., destination user identification information and / or origin user identification information), delivery item identification information, delivery type information (e.g., standard delivery, express delivery (delivery with a shorter delivery period than standard delivery), time-specified delivery), scheduled delivery time information (e.g., scheduled delivery start time information, scheduled delivery end time information, scheduled delivery time zone information, etc.), delivery-related status information (e.g., before delivery preparation, during delivery preparation, delivery preparation complete, in delivery, returning, delivery completed, etc., which may be partially or entirely the same as the status information of mobile 2), delivery cost information, etc., and may also include, but is not limited to, storage container type information, weight information, management temperature zone information, presence or absence of fresh products information, etc., linked to the delivery item identification information. Only some of the above may be included, or information not exemplified may be included. The delivery information storage unit 122 can be implemented, for example, as a relational database, a NoSQL database, or a file system.

[0076] The user information stored in the user information storage unit 123 may include, but is not limited to, basic user information (user's name, username, email address, address, telephone number, etc.), user identification information, and external application account information. For example, when conducting electronic commerce on this information processing system or on an external system that transmits or receives related information to this information processing system and cooperates with it, the user information may include payment information (credit card information, etc.), subscription information, and information on items that can be included in a mixed shipment. In addition, delivery destination information may be registered as basic user information, and the delivery destination information may be address information or identification information indicating a receiving agency location that is separately registered in this information processing system (for example, it may include ID information, address information, name information (including branch information), etc.). The user information storage unit 123 can be implemented as, for example, a relational database, a NoSQL database, or a file system.

[0077] The delivery information stored in the delivery information storage unit 124 may include, but is not limited to, delivery identification information, user identification information, size information (depth, width, height), weight information, temperature control zone information, presence or absence of perishable goods, and stacking capability information (top stacking capability information or bottom stacking capability information). The delivery information storage unit 124 can be implemented, for example, as a relational database, a NoSQL database, or a file system.

[0078] <Functions of Authentication Server 6> Next, the functional configuration of the authentication server 6 will be described. Figure 9 is a block diagram illustrating the functions implemented in the control unit 60 of the authentication server 6, and Figure 10 is a block diagram illustrating the information stored in the storage 62. In this embodiment, the control unit 60 of the authentication server 6 includes a certification information generation unit 600, an encryption unit 601, and a communication control unit 602, and the storage 62 includes a certification information storage unit 621.

[0079] The authentication information generation unit 600 generates mobile authentication information necessary for the authentication of the mobile body 2. The authentication information generation unit 600 generates mobile authentication information using the plaintext information and mobile body identification information stored in the authentication information storage unit 621. The plaintext information and mobile body identification information may be stored in the authentication information storage unit 621, for example, based on input data from an external device such as a worker terminal 4. The plaintext information may also include information regarding the expiration date and issuer.

[0080] The encryption unit 601 encrypts the mobile identity certificate information generated by the certificate information generation unit 600. The encryption unit 601 performs the encryption process using a pre-set encryption key. The encryption method used corresponds to the decryption method used in the decryption unit 101 of the management server 1.

[0081] Here, specific examples of encryption methods in the encryption unit 601 and the decryption unit 101 will be described. In this embodiment, any of the three methods described below can be adopted.

[0082] The first method involves the encryption unit 601 of the authentication server 6 generating a private key and a public key pair, and providing the public key to the decryption unit 101 of the management server 1. The encryption unit 601 includes a private key generation unit and a public key generation unit (it can also be said to have private key generation and public key generation functions), and these generate the private key and public key pair. The encryption unit 601 uses the generated private key to attach a digital signature to the mobile identity certificate information. Specifically, it calculates the hash value of the mobile identity certificate information and generates a digital signature by encrypting that hash value with the private key. In this case, the decryption unit 101 can verify the authenticity and integrity of the mobile identity certificate information by verifying the digital signature using the public key provided in advance. In the first method, since the private key is managed within the authentication server 6 and not disclosed externally, a high level of security can be ensured.

[0083] The second method involves the decryption unit 101 of the management server 1 generating a private key and a public key pair, and providing the public key to the encryption unit 601 of the authentication server 6. The decryption unit 101 includes a private key generation unit and a public key generation unit (it can also be said to have private key generation and public key generation functions), and these generate the private key and public key pair. The encryption unit 601 encrypts the mobile identity certificate information using the provided public key. In this case, the decryption unit 101 can decrypt the encrypted mobile identity certificate information using the private key it holds. In the second method, since the private key is managed within the management server 1 and not disclosed externally, the confidentiality of the encrypted information can be ensured.

[0084] The third method involves sharing a common key between the encryption unit 601 of the authentication server 6 and the decryption unit 101 of the management server 1. The common key is shared between the two in advance, for example, via a secure channel. Alternatively, the common key can be dynamically generated and shared using a key exchange protocol with public-key cryptography. The encryption unit 601 encrypts the mobile identity information using the common key, and the decryption unit 101 decrypts the encrypted mobile identity information using the same common key. The third method has the advantage of faster processing speed compared to public-key cryptography.

[0085] The cryptographic algorithms used in each method include, for example, RSA and ECC (Elliptic Curve Cryptography) in the first and second methods, and AES and ChaCha20 in the third method. Furthermore, SHA-2 and SHA-3 can be used as hash functions. Other known cryptographic algorithms may also be adopted.

[0086] In each of the above methods, the frequency of encryption key updates and expiration dates can be set. For example, keys can be updated periodically or when a specific event occurs (such as detection of unauthorized access). Furthermore, by managing key generations, the expiration dates of mobile entity authentication information and keys can be linked. The candidate mobile entity storage unit 121 can also manage various expiration date information related to mobile entities. Specifically, it manages the expiration dates of mobile entity authentication information, encryption keys, and type certification. These expiration dates are set and managed independently. If any of these expiration dates expire, the mobile entity no longer meets the requirements to be a delivery candidate mobile entity and is managed to be excluded from the list of delivery candidate mobile entities. Excluded mobile entities will not be re-registered as delivery candidate mobile entities until the corresponding expiration date is renewed.

[0087] In each system, key updates can be performed using one of the following methods: (1) Periodic updates: - Updates at fixed intervals (e.g., daily, weekly, monthly) - Different update intervals can be set for each mobile device to distribute the update timing. (2) Event-based updates: - Immediate updates when unauthorized access is detected - Updates during system updates - Updates during maintenance and inspection of mobile devices. (3) Usage-based updates: - Updates based on the number of encryption and decryption operations - Updates based on the amount of data transferred.

[0088] Furthermore, these methods can be used in combination. For example, by using a digital signature by the first method and encryption by the third method in combination, the authenticity, integrity, and confidentiality of mobile identity information can be ensured simultaneously. In this case, the encryption unit 601 first assigns a digital signature to the mobile identity information, and then encrypts the signed mobile identity information with a common key. The decryption unit 101 decrypts the received data with the common key and then verifies the digital signature.

[0089] The communication control unit 602 transmits the mobile device authentication information encrypted by the encryption unit 601 to the mobile device 2. The communication control unit 602 can transmit the mobile device authentication information via wired communication or wireless communication.

[0090] <Functions of Mobile Unit 2> Next, the functional configuration of the mobile unit 2 will be described. Figure 11 is a block diagram illustrating the functions implemented in the control unit 20 of the mobile unit 2, and Figure 12 is a block diagram illustrating the information stored in the storage unit 22. The mobile unit 2 comprises a control unit 20 (for example, a CPU and a chipset) and a storage unit 22. The control unit 20 comprises a communication control unit 200 and a flight control unit 201, and the storage unit 22 comprises a certification information storage unit 221 and a flight control information storage unit 222. Each functional unit and storage unit may be configured with the same CPU and chipset as hardware, or they may be configured with different CPUs and chipsets.

[0091] The communication control unit 200 receives encrypted mobile identity information from the authentication server 6 and stores it in the identity information storage unit 221. The communication control unit 200 also transmits the encrypted mobile identity information stored in the identity information storage unit 221 to the management server 1 upon request from the management server 1, or periodically thereafter. The identity information storage unit 221 may also store the plaintext and mobile identity information mentioned above in addition to the encrypted mobile identity information. This information may be transmitted to the management server 1 along with the encrypted mobile identity information and used by the determination unit 106 to determine the correctness of the decrypted data (mobile identity information).

[0092] The flight control unit 201 controls the flight of the mobile unit 2. Based on the flight control information stored in the flight control information storage unit 222, the flight control unit 201 performs controls such as motor rotation speed, attitude control, and path planning. The flight control unit 201 can also perform flight control when carrying a delivery.

[0093] The authentication information storage unit 221 stores encrypted mobile authentication information received from the authentication server 6. The authentication information storage unit 221 can be implemented as non-volatile memory.

[0094] The flight control information storage unit 222 stores information necessary for the flight control of the mobile unit 2. Specifically, the flight control information storage unit 222 stores motor control parameters, attitude control parameters, path planning parameters, etc. In addition, the flight control information storage unit 222 can also store flight control parameters according to the weight and shape of the delivered goods.

[0095] Next, the processes of each control unit in this embodiment will be described with reference to Figures 13 to 15.

[0096] First, with reference to Figure 13, the encryption process executed by the control unit 60 of the authentication server 6 will be described.

[0097] The control unit 60 first reads plaintext information and mobile identification information from the certification information storage unit 621 using the certification information generation unit 600, and generates mobile certification information (S101).

[0098] Next, the encryption unit 601 performs encryption processing on the generated mobile identity certificate information. At this time, the encryption unit 601 performs signature with a private key, encryption with a public key, or encryption with a symmetric key, depending on the encryption method adopted (S102).

[0099] Subsequently, the communication control unit 602 transmits the encrypted mobile device authentication information to the mobile device 2 (S103).

[0100] Next, with reference to Figure 14, the process executed by the control unit 20 of the mobile body 2 will be described.

[0101] The control unit 20 first receives encrypted mobile identity information from the authentication server 6 via the communication control unit 200 (S201).

[0102] Next, the received encrypted mobile identity information is stored in the identity information storage unit 221 (S202).

[0103] Subsequently, when a request is received from the management server 1, or at periodic intervals, the communication control unit 200 reads the encrypted mobile identity authentication information from the authentication information storage unit 221 and transmits it to the management server 1 (S203).

[0104] Next, with reference to Figure 15, the process executed by the control unit 10 of the management server 1 will be described.

[0105] The control unit 10 first obtains encrypted mobile device authentication information from the mobile device 2 using the acquisition unit 104 (S301).

[0106] Next, the decryption unit 105 performs a decryption process on the acquired encrypted mobile identity certificate information. At this time, the decryption unit 105 performs signature verification using a public key, decryption using a private key, or decryption using a symmetric key, depending on the encryption method used (S302).

[0107] Next, the determination unit 106 determines whether or not to set the mobile body 2 as a candidate mobile body for delivery, depending on the success or failure of the decoding process (S303).

[0108] If it is determined that the mobile body 2 related to the decryption process should be set as a candidate mobile body for delivery, the data management unit 103 stores the mobile body information in the candidate mobile body storage unit 121 (S304).

[0109] Subsequently, the delivery management unit 107 selects a delivery mobile body from the candidate delivery mobile bodies stored in the candidate delivery mobile body storage unit 121 based on the delivery conditions, and stores the information of the selected delivery mobile body in the delivery information storage unit 122 (S305). Then, based on the delivery information, the delivery mobile body performs the delivery work according to the instructions.

[0110] On the other hand, if it is determined that the mobile body 2 related to the decryption process should not be set as a candidate mobile body for delivery, the operator terminal 4 is notified of this (S306).

[0111] Thus, this disclosure can improve the safety and reliability of delivery services.

[0112] The following describes modifications of this embodiment. These modifications improve upon the basic configuration described in this embodiment from the standpoint of the configuration of mobile identity information, authentication method, and system configuration. The modifications described below can be implemented independently or in any combination.

[0113] <Modification 1> The following describes a modification regarding the structure of mobile identification information. In this modification, by extending the structure of the mobile identification information, it is possible to achieve more detailed management of mobile objects. Specifically, by extending the plaintext information, introducing hierarchical aircraft identification information, and introducing time-limited control information, it is possible to more accurately grasp the status and performance of mobile objects and realize efficient delivery management.

[0114] In this modified example, the plaintext information may include the following information in addition to the expiration date information, regulation compliance information, and manufacturer information in the above-described embodiment. First, it may include maintenance record information related to the maintenance of the mobile unit. The maintenance record information may include periodic inspection records, parts replacement records, repair records, and maintenance personnel information. Periodic inspection records may include the inspection date, inspection items, inspection results, and next scheduled inspection date. Parts replacement records may include the name of the replaced part, replacement date, reason for replacement, and next scheduled replacement date. Repair records may include the repair details, repair date, repair location, and results of post-repair operational checks. Maintenance personnel information may include the maintenance personnel's identification information, qualification information, and affiliation information.

[0115] Furthermore, the plaintext information may include safety assessment information related to the safety of the moving object. This safety assessment information includes durability test results, vibration test results, environmental resistance test results, and collision avoidance function test results. Each test result includes the test date, test conditions, evaluation items, evaluation results, and evaluation expiration date. Additionally, the safety assessment information may include risk assessment results, recording anticipated risks and the status of countermeasures.

[0116] Furthermore, the plaintext information may include operational performance information for the mobile device. Operational performance information includes cumulative flight time, cumulative number of deliveries, cumulative distance traveled, and anomaly occurrence history. Anomaly occurrence history includes the type of anomaly, the date and time of occurrence, the circumstances of the occurrence, and the response result. In addition, operational performance information may include operational performance by weather conditions and operational performance by time of day.

[0117] Next, in this modified example, mobile object identification information is structured as a hierarchical structure. The first level is the manufacturer level and includes manufacturer identification information, country of manufacture information, and manufacturing site information. The second level is the product level and includes product category information, model information, and type information. The third level is the individual unit level and includes serial number, date of manufacture, and production line information. The fourth level is the operation level and includes operator information, operation region information, and operation category information. The information in each level is structured in such a way that it can be uniquely identified from the higher level to the lower level.

[0118] Furthermore, this modification introduces time-limited control information into the mobile identification information. Time-limited control information indicates temporary operational restrictions or special permits and is valid only for a specific period or under specific conditions. For example, time-limited control information may include flight permit information during a specific event period, temporary relaxation of flight altitude restrictions, or operational restriction information depending on weather conditions. This information includes the start and end dates and times of the validity period, applicable conditions, and approver information.

[0119] By extending the mobile object identification information in this way, it becomes possible to manage the maintenance status, safety, and operational history of mobile objects in detail, enabling the selection of more appropriate mobile objects for delivery. Furthermore, the hierarchical identification information allows for flexible setting of the management granularity of mobile objects. In addition, time-limited control information enables flexible operation according to the situation.

[0120] <Modification 2> The following describes modifications related to the authentication method. In this modification, it is possible to achieve a more secure and reliable system operation by enhancing the authentication method. Specifically, the security level is improved by introducing multi-factor authentication, implementing a hierarchical authentication process, and introducing a function to change authentication requirements dynamically.

[0121] In this modified version, multi-factor authentication is first introduced. Authentication of mobile device credentials is performed by combining the following three authentication elements. The first authentication element is authentication based on information owned by the mobile device, using the decrypted result of encrypted mobile device credentials. The second authentication element is authentication based on the characteristics of the mobile device, using hardware information that indicates the unique characteristics of the mobile device (e.g., unique parameters of various sensors, characteristic values ​​of motors, individual identification information of control boards, etc.). The third authentication element is authentication based on the operation of the mobile device, using the operation patterns of the mobile device (e.g., control characteristics during hovering, output patterns of acceleration sensors, power consumption patterns, etc.).

[0122] The decryption unit 105 performs an authentication process that combines these three authentication elements. Specifically, it decrypts and verifies the mobile device identification information as the first authentication element, verifies the hardware information as the second authentication element, and analyzes the operation pattern as the third authentication element. The determination unit 106 comprehensively evaluates these three authentication results to determine the authenticity of the mobile device.

[0123] Next, in this modified version, a hierarchical authentication process is implemented. The authentication process consists of the following three layers: The first layer is basic authentication, which performs basic verification of mobile identification information (e.g., checking the expiration date, confirming the presence of required items, etc.). The second layer is detailed authentication, which verifies the detailed contents of the mobile identification information (e.g., maintenance records, safety evaluation results, operational performance, etc.). The third layer is dynamic authentication, which performs real-time status checks (e.g., validity of current location, normality of sensor values, communication quality, etc.).

[0124] The determination unit 106 executes these hierarchical authentication processes step by step. Only if authentication is successful at each level does it proceed to the next level's authentication process. If authentication fails at any level, the authentication process is terminated at that point, and a decision is made not to set the mobile object as a candidate for delivery. Furthermore, the importance and priority of authentication at each level can be set, allowing the authentication process to be optimized according to the situation.

[0125] Furthermore, this modified version implements a dynamic authentication requirement change function. Authentication requirements are dynamically changed based on the following factors: (1) Time of day factor: Authentication requirements are tightened during certain times, such as late at night or early in the morning. (2) Regional factor: Stricter authentication is required in densely populated areas or around critical facilities. (3) Weather factor: Additional security checks are required during inclement weather. (4) Event factor: Special authentication requirements are set when large-scale events are held. (5) Risk factor: The authentication level is automatically increased when unauthorized access is detected.

[0126] The determination unit 106 dynamically adjusts the authentication requirements, taking these factors into consideration. Specifically, it changes the combination of elements required for authentication, the weighting of each authentication element, the validity period of the authentication, and the timing of re-authentication requests depending on the situation. For example, it is possible to require all three authentication elements in densely populated areas and allow a combination of two authentication elements in other areas.

[0127] Furthermore, the history of changes to the authentication requirements is recorded in the candidate mobile device storage unit 121. The recorded information includes the factors that triggered the changes, the content of the changed authentication requirements, the period during which the changes were applied, and the impact of the changes on the authentication results. This information is used for the continuous improvement of the authentication process.

[0128] Thus, the introduction of multi-factor authentication, the implementation of hierarchical authentication processes, and the ability to dynamically change authentication requirements enable more reliable and flexible authentication of mobile entities. This further enhances the security and reliability of delivery services.

[0129] <Variation 3> The following describes a variation regarding the system configuration. In this variation, it is possible to achieve more stable and efficient system operation by optimizing the system configuration. Specifically, the overall availability and processing efficiency of the system are improved by implementing it as a distributed system, utilizing edge computing, and introducing a redundant configuration.

[0130] First, in this modified version, the information processing system is implemented as a distributed system. Specifically, the functions of the management server 1, authentication server 6, and mobile device 2 are realized by multiple servers geographically distributed. These distributed servers consist of the following three layers: (1) Central management layer: Formulates global delivery plans, monitors the entire system, and analyzes statistical data. (2) Regional management layer: Manages deliveries in specific regions, authenticates mobile devices, and detects anomalies. (3) Local management layer: Directly controls mobile devices at individual delivery hubs and makes immediate decisions.

[0131] Each layer's servers can operate independently and can continue autonomously to a certain extent even if communication with the upper layer is interrupted. For example, the local management layer server can perform mobile authentication processing based on its cached mobile identity information and pre-configured criteria.

[0132] Next, in this modified example, edge computing is utilized. Mobile unit 2 is equipped with a control device that functions as an edge server, and the following processes are performed on the mobile unit side: (1) Pre-verification of mobile unit identification information, confirmation of expiration date, basic format check, and confirmation of consistency with hardware information (2) Collection and analysis of real-time data, detection of anomalies in sensor data, analysis of operating patterns, and evaluation of environmental conditions (3) Emergency decision processing, decision to temporarily wait in the event of communication failure, decision to make an emergency landing in the event of an anomaly detection, and decision to change the route to avoid collisions

[0133] The processing results from the edge servers are used as supplementary information for the final decision made by the management server 1. Furthermore, the edge servers can receive some or all of the processing delegated from the management server 1, contributing to load balancing across the entire system.

[0134] The embodiments described above are merely illustrative examples to facilitate understanding of this disclosure and are not intended to limit it. This disclosure may be modified or improved without departing from its intent, and its equivalents are included.

[0135] 1. Management server 2. Mobile device 3. User terminal 4. Worker terminal 6. Authentication server

Claims

1. An information processing system comprising: an acquisition unit that obtains encrypted mobile entity identification information from a mobile entity; a decryption unit that performs a decryption process on the mobile entity identification information; a determination unit that determines whether or not to set the mobile entity as a candidate mobile entity for delivery according to the success or failure of the decryption process; and a delivery management unit that sets a delivery mobile entity to deliver the goods from among the candidate mobile entities for delivery.

2. The information processing system according to claim 1, wherein the mobile entity certification information includes plain text and aircraft identification information.

3. The information processing system according to claim 1, wherein if the determination unit determines that the mobile body certification information is incorrect as a result of the decoding process, the mobile body corresponding to the mobile body certification information is not included in the target for setting the candidate mobile body for delivery.

4. The information processing system according to claim 1, further comprising a candidate mobile body storage unit for storing the candidate mobile bodies for delivery, wherein if the determination unit determines that the mobile body certification information is incorrect as a result of the decoding process, it does not store the mobile body corresponding to the mobile body certification information in the candidate storage unit.

5. The information processing system according to claim 1, further comprising a candidate mobile body storage unit for storing the candidate mobile bodies for delivery, wherein if the determination unit determines that the mobile body certification information is incorrect as a result of the decoding process, it stores the status of the mobile body corresponding to the mobile body certification information as an error.

6. The information processing system according to claim 2, wherein the plain text includes at least expiration date information.

7. The information processing system according to claim 2, wherein the plain text includes at least regulation pass / fail information.

8. The information processing system according to claim 2, wherein the plain text includes at least manufacturer information.

9. The information processing system according to claim 2, wherein the plain text includes at least maintenance record information.

10. The information processing system according to claim 2, wherein the plain text includes at least safety evaluation information.

11. The information processing system according to claim 2, wherein the plain text includes at least operational performance information.

12. The information processing system according to claim 2, wherein the aircraft identification information includes at least manufacturer identification information.

13. The information processing system according to claim 2, wherein the aircraft identification information includes at least aircraft serial information.

14. The information processing system according to claim 2, wherein the aircraft identification information includes at least operational system identification information.

15. The information processing system according to claim 1, further comprising a delivery schedule management unit for managing delivery schedules, wherein the delivery schedule management unit assigns a candidate delivery vehicle to each delivery slot.

16. The information processing system according to claim 1, wherein the mobile entity authentication information is generated by an authentication server, the authentication server encrypts the mobile entity authentication information and transmits it to the mobile entity, and the mobile entity stores the received encrypted mobile entity authentication information in a storage unit.

17. The information processing system according to claim 1, wherein the mobile body certification information includes type conformity information relating to type certification of the mobile body and aircraft conformity information relating to an individual mobile body.

18. The information processing system according to claim 1, wherein the encryption is performed using a private key, and the decryption process is performed using a public key generated together with the private key.

19. The information processing system according to claim 1, wherein the determination unit determines, as a result of the decoding process, a success state, a format error state, and a decoding error state, and sets the mobile body as a delivery candidate mobile body only when the success state is reached.

20. The information processing system according to claim 1, wherein the determination unit performs verification of the expiration date, verification of regulation compliance information, and verification of mobile identification information with respect to the contents of the mobile identification information obtained by the decryption process, and sets the mobile as a candidate mobile for delivery only if all verifications are passed.

21. The information processing system according to claim 6, wherein the candidate mobile body storage unit manages the expiration dates of the mobile body certification information, the encryption key, and the type certification for the mobile body, and if any of these expiration dates expires, the mobile body is removed from the list of candidate mobile bodies for delivery.

22. The information processing system according to claim 6, wherein the determination unit determines that the mobile body certification information is incorrect, records the identification information of the mobile body and the determination result as history, and permanently excludes mobile bodies from the list of candidate mobile bodies for delivery if a predetermined number of determination errors have been recorded.

23. An information processing method in an information processing system, comprising the steps of: acquiring encrypted mobile identity information from a mobile body using an acquisition unit; performing a decryption process on the mobile identity information using a decryption unit; determining whether or not to set the mobile body as a candidate mobile body for delivery using a determination unit, depending on the success or failure of the decryption process; and setting a mobile body for delivery of goods from among the candidate mobile bodies for delivery using a delivery management unit.

24. A program that causes an information processing system to execute the following steps: an acquisition unit acquires encrypted mobile identity information from a mobile body; a decryption unit performs a decryption process on the mobile identity information; a determination unit determines whether or not to set the mobile body as a candidate delivery mobile body according to the success or failure of the decryption process; and a delivery management unit sets a delivery mobile body to deliver the goods from among the candidate delivery mobile bodies.

Images