Delivery robot service provider and operation method of the same

Abstract

To disclose a delivery robot service provider and an operation method of the same.SOLUTION: An operation method for a delivery robot service provider includes the operations of: receiving a delivery request from a user device; generating delivery information on the delivery request; assigning a delivery robot that performs the delivery request; transmitting the delivery information to the delivery robot; and sharing a current location of the delivery robot and a loading status of the goods with the delivery robot service provider while the delivery robot is delivering goods according to delivery information.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The following disclosure relates to a delivery robot service provider and its method of operation. [Background technology]

[0002] An autonomous delivery robot service refers to a service in which a delivery robot delivers goods through collaboration with urban infrastructure and other entities.

[0003] For autonomous delivery robot services, an interworking protocol between entities (e.g., delivery robots, service providers, users, infrastructure) is required.

[0004] The background art described above was maintained or acquired by the inventors in the process of deriving the contents of the disclosure of this specification, and cannot necessarily be said to be publicly known art that was made public to the general public prior to the filing of this application. Summary of the Invention [Problem to be solved by the invention]

[0005] One embodiment provides an interoperability method for an autonomous robot-based delivery service.

[0006] However, the technical issues are not limited to those mentioned above, and further technical issues exist. [Means for solving the problem]

[0007] According to one embodiment, a method for operating a delivery robot service provider may include receiving a delivery request from a user device, generating delivery information for the delivery request, allocating a delivery robot that performs the delivery request, transmitting the delivery information to the delivery robot, and sharing a current location of the delivery robot and a loading status of the goods with the delivery robot service provider while the delivery robot delivers goods according to the delivery information.

[0008] The delivery information may include at least one of a pickup location for the goods, a delivery location for the goods, a delivery time for the goods, information on infrastructure that must be interconnected with the delivery robot for the delivery of the goods, a delivery route for the goods, and a type of the goods.

[0009] The delivery robot service provider may have information about infrastructure that can interwork with the delivery robot.

[0010] The method may further include an operation of interoperating with infrastructure located along a delivery route of the goods.

[0011] The operating method may further include an operation of determining access priority for the infrastructure between the delivery robot and the other delivery robots based on the presence of other delivery robots competing with the delivery robot for access to the infrastructure.

[0012] The determining operation may include an operation of determining the access priority through interoperation with the other delivery robot service provider when the other delivery robot is managed by the delivery robot service provider.

[0013] The operating method may further include an operation of transmitting a loading status of the item or an unloading status of the item to the corresponding user terminal.

[0014] According to one embodiment, an apparatus for managing a delivery robot includes a processor and a memory for storing instructions, and when the instructions are executed by the processor, the apparatus performs a plurality of operations, including receiving a delivery request from a user device, generating delivery information for the delivery request, allocating a delivery robot that makes the delivery request, transmitting the delivery information to the delivery robot, and sharing a current location of the delivery robot and a loading status of the goods with the delivery robot service provider while the delivery robot delivers goods according to the delivery information.

[0015] The delivery information may include at least one of a pickup location for the goods, a delivery location for the goods, a delivery time for the goods, information on infrastructure that must be interconnected with the delivery robot for the delivery of the goods, a delivery route for the goods, and a type of the goods.

[0016] The device may contain information about infrastructure that can interwork with the delivery robot.

[0017] The plurality of operations may further include an operation of interoperating with infrastructure located along a delivery route of the goods.

[0018] The plurality of operations may further include an operation of determining access priorities for the infrastructure between the delivery robot and the other delivery robots based on the presence of other delivery robots competing with the delivery robot for access to the infrastructure.

[0019] The determining operation may include an operation of determining the access priority through interoperation with the other delivery robot service provider when the other delivery robot is managed by the delivery robot service provider.

[0020] The plurality of operations may further include an operation of transmitting a loading status of the item or an unloading status of the item to the corresponding user terminal. [Brief explanation of the drawings]

[0021] [Figure 1] FIG. 1 is a diagram illustrating a delivery service system according to an embodiment.

[0022] [Figure 2] FIG. 1 is a diagram illustrating a delivery robot service provider according to an embodiment.

[0023] [Figure 3] FIG. 1 is a diagram illustrating a delivery robot according to an embodiment.

[0024] [Figure 4] FIG. 1 is a diagram illustrating urban infrastructure according to an embodiment.

[0025] [Figure 5] FIG. 1 is a diagram illustrating a user device according to an embodiment.

[0026] [Figure 6] 1 illustrates a workflow for requesting delivery and initiating delivery on a user device according to one embodiment.

[0027] [Figure 7] 1 illustrates a workflow for receiving a goods load completion notification from a delivery robot according to one embodiment.

[0028] [Figure 8] 10 illustrates a workflow for receiving a notification of completion of goods unloading from a delivery robot according to one embodiment.

[0029] [Figure 9] 10 illustrates a workflow for receiving a product load completion notification on a user device according to one embodiment.

[0030] [Figure 10] 10 illustrates a workflow for receiving a notification of completion of goods unloading on a user device according to one embodiment.

[0031] [Figure 11] 1 illustrates a workflow for interworking between delivery robots and city infrastructure according to one embodiment.

[0032] [Figure 12] 1 illustrates a workflow for interworking between delivery robots and city infrastructure according to one embodiment.

[0033] [Figure 13] 1 is a schematic block diagram of an apparatus according to an embodiment; DETAILED DESCRIPTION OF THE INVENTION

[0034] Specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only and may be modified in various forms. Therefore, the embodiments are not limited to the specific disclosed forms, and the scope of this specification includes modifications, equivalents, or alternatives that fall within the technical ideas described in the embodiments.

[0035] Although terms such as "first" or "second" may be used to describe multiple components, such terms should be construed only to distinguish one component from the other components. For example, a first component may be designated as a second component, and similarly, a second component may be designated as a first component.

[0036] When any component is referred to as being "connected" to another component, it is directly linked or connected to the other component, but it should be understood that there may be other components in between.

[0037] The singular expression includes the plural expression unless the context clearly dictates otherwise. In this specification, each of the phrases "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B, or C" includes any one or all possible combinations of the items listed together in the corresponding phrase. In this specification, the words "comprise" or "have" and the like indicate the presence of a feature, numeral, step, operation, element, component, or combination thereof described in the specification, and should be understood as not precluding the possibility of the presence or addition of one or more other features, numerals, steps, operations, elements, components, or combinations thereof.

[0038] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art. Commonly used, predefined terms should be interpreted to have a meaning consistent with the meaning they have in the context of the relevant art, and should not be interpreted as having an ideal or overly formal meaning unless expressly defined herein.

[0039] As used herein, the term "module" includes a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integrated component, or the smallest unit or portion of such a component that performs one or more functions. For example, according to one embodiment, a module is implemented in the form of an application-specific integrated circuit (ASIC).

[0040] As used herein, the term "module" refers to software or hardware components such as FPGAs or ASICs, and the "module" performs some function. However, the term "module" is not limited to software or hardware. A "module" may reside on an addressable storage medium or be configured to implement one or more processors. For example, a "module" may include components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within a component and a "module" may be combined into fewer components and "modules" or further divided into additional components and "modules." Furthermore, components and "modules" may be embodied to implement one or more CPUs within a device or secure multimedia card. A "module" may also include one or more processors.

[0041] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. When describing with reference to the drawings, the same components will be given the same reference numerals regardless of the reference numerals, and redundant description thereof will be omitted.

[0042] As used herein, a "Function" may be defined as a collection of functionality, and a "functional entity (FE)" may be defined as a representation of a function that has not been further refined at the level of detail described herein.

[0043] FIG. 1 is a diagram illustrating a delivery service system according to an embodiment.

[0044] Referring to FIG. 1 , a delivery service system 10 includes a delivery robot service provider (DRSP) 200, a delivery robot (DR) 300, urban infrastructures (UI) 400, user devices (UD) 500, and an external entity (EE) 100.

[0045] The DRSP 200 includes delivery service interworking functions (DSIF) 210, delivery service management functions (DSMF) 230, and delivery robot management functions (DRMF) 250.

[0046] The DR 300 includes delivery robot interworking functions (DRIF) 310.

[0047] The UI 400 includes urban infrastructure interworking functions (UIIF) 410 .

[0048] The UD 500 includes user device interworking functions (UDIF) 510 and user device management functions (UDMF) 530.

[0049] The EE 100 may include devices (e.g., servers) of public institutions (e.g., urban control centers, disaster management agencies, and emergency rescue agencies) and devices (e.g., servers) of other delivery robot service providers. The EE 100 can directly interact with the DRSP 200.

[0050] In the delivery service system 10, interfaces for delivery services include DSI-DRM, DSI-DRM, DSI-UDI, DSI-UII, DSM-DRMn, DRM-DRI, DRI-UDI, DRI-UII, and UDI-UDMn. The DSI-DSM may be an interface between functional entities of the DSIF 210 and the DSMF 230. The DSI-DRM may be an interface between functional entities of the DSIF 210 and the DRMF 250. The DSI-UDI may be an interface between functional entities of the DSIF 210 and the UDIF 510. The DSI-UII may be an interface between functional entities of the DSIF 210 and the UIIF 410. The DSM-DRMn may be an interface between functional entities of the DSIF 210 and the DRMF 250. The DRM-DRI may be an interface between functional entities of the DRMF 250 and the DRIF 310. The DRI-UDI may be an interface between the functional entities of the DRIF 310 and the functional entities of the UDIF 510. The DRI-UII may be an interface between the functional entities of the DRIF 310 and the functional entities of the UIIF 410. The UDI-UDMn may be an interface between the functional entities of the UDIF 510 and the functional entities of the UDMF 530.

[0051] FIG. 2 is a diagram illustrating a delivery robot service provider according to an embodiment.

[0052] Referring to Figure 2, the DRSP 200 can be implemented as a server-like device. The DRSP 200 manages the DR 300. The DRSP 200 can directly interact with the DR 300, UI 400, UD 500, and EE 100. The DRSP 200 can maintain and / or manage information about the DR 300 (e.g., identifier, capabilities). The DRSP 200 can collect and manage information about the UI 400 (e.g., location, identifier, capabilities).

[0053] The DRSP 200 determines whether there is an available delivery robot (e.g., DR300) in response to receiving a delivery request from the UD 500. The DRSP 200 may send information (e.g., delivery request approval, delivery request rejection) to the UD 500 based on the available delivery robot.

[0054] The DRSP 200 may identify one or more user devices related to the received delivery request. For example, the DRSP 200 may identify a user device of the delivery requester, a user device related to loading of goods, and a user device related to unloading of goods (e.g., a user device of the recipient).

[0055] The DRSP 200 may generate delivery information for a delivery request. The delivery information may include at least one of a pickup location, a delivery location, a delivery time, information about infrastructure that must be interconnected with the delivery robot (e.g., location, identifier), a delivery route, a type of goods, a weight of goods, a size of goods, and a delivery condition (e.g., an appropriate temperature).

[0056] The DRSP 200 can generate a delivery request or separately assign a DR 300 for the delivery request.

[0057] The DRSP 200 may collect the current location, movement direction, status (e.g., breakdown, battery status), goods loading status, and goods status (e.g., temperature) of the DR 300.

[0058] The DRSP 200 may transmit delivery status information generated by the DR 300 to the UD 500.

[0059] The DRSP 200 may notify the UD 500 that the DR 300 is waiting to load or unload goods after the DR 300 arrives at a pickup location or a delivery location.

[0060] After the DR 300 arrives at the UI 400, the DRSP 200 may notify the UI 400 that the DR 300 is waiting for interaction with the UI 400.

[0061] The DRSP 200 may notify the DR 300 of a response to the interworking request received from the UI 400 (for example, a result of the interworking request).

[0062] The DRSP 200 may collect additional information in addition to the delivery information from the UI 400 and / or the EE 100. The DRSP 200 can provide the collected additional information to the DR 300.

[0063] The DRSP 200 may receive information indicating that loading or unloading of goods has been completed from the UD 500. The DRSP 200 may transmit the received information to the DR 300.

[0064] The DRSP 200 may receive information indicating that loading or unloading of goods has been completed from the DR 300. The DRSP 200 may transmit the received information to the UD 500.

[0065] The DRSP 200 determines whether the DR 300 can continue to deliver the goods based on the delivery status information generated by the DR 300.

[0066] The DRSP 200 may receive the result of the direct interworking from the DR 300. The DRSP 200 may update the delivery information in response to receiving the result.

[0067] The DRSP 200 can receive a request from the EE 100. For example, the EE 100 may request the DRSP 200 to transmit visual information about the space surrounding the DR 300. The DRSP 200 may evaluate (or determine) the request (e.g., the contents of the request) from the EE 100. The DRSP 200 can classify the request of the EE 100 into an emergency request / non-emergency request. The DRSP 200 can notify the DR 300 of the request of the EE 100. For example, when the request of the EE 100 must be processed with priority, the DRSP 200 may transmit priority information of the request together with the request of the EE 100 to the DR 300.

[0068] The DRSP 200 can process a request from the EE 100 and notify the EE 100 of the processing result.

[0069] When multiple delivery robots are waiting to interact with the same city infrastructure, the DRSP 200 can determine the priority among the multiple delivery robots. The priority indicates the order in which the multiple delivery robots will use the corresponding city infrastructure. The DRSP 200 may use delivery status information (e.g., type of goods, state of goods) of each of the multiple delivery robots to determine the priority.

[0070] The DRSP200 may receive from the DR300 the results of interworking (e.g., direct interworking) between the DR300 and another delivery robot (e.g., another delivery robot 21). The DRSP200 may determine from the received results that the other delivery robot 21 is managed by another delivery robot service provider. The DRSP200 may determine from the received results that the DR300 and another delivery robot 21 are waiting for interworking with the same city infrastructure. The DRSP200 may interwork with the other delivery robot service provider to coordinate priorities between the DR300 and the other delivery robot.

[0071] The DRSP200 may convert a particular coordinate system (e.g., a Cartesian coordinate system) to another coordinate system (e.g., a spherical coordinate system). The DRSP200 can determine the current position of the DR300 using the appropriate coordinate system. The DRSP200 can use the appropriate coordinate system to assist the operation of the DR300 (e.g., loading and unloading goods or approaching the UI400). The DRSP200 can use the appropriate coordinate system for information exchange with other delivery robot service providers.

[0072] The DRSP 200 includes delivery service interworking functions (DSIF) 210, delivery service management functions (DSMF) 230, and delivery robot management functions (DRMF) 250.

[0073] In the DRSP 200, interfaces for delivery services include DSI-DSM1, DSI-DRM, DSI-UII, DSI-UDI, DSM-DRM1, DSM-DRM2, and DRM-DRI. DSI-DSM1 may be an interface between the DSIM-FE 211 and the DM-FE 233. DSI-DRM may be an interface between the DSIM-FE 211 and the DRM-FE 251. DSI-UII may be an interface between the DSIM-FE 211 and the UIIM-FE 411. DSI-UDI may be an interface between the DSIM-FE 211 and the UDIM-FE 511. DSM-DRM1 may be an interface between the DM-FE 233 and the DRM-FE 251. DSM-DRM2 may be an interface between the GHM-FE 235 and the DRM-FE 251. DRM-DRI may be an interface between the DRM-FE 251 and the DRIM-FE 311.

[0074] The DSIF 210 provides functionality for interworking with the UI 400, UD 500, DSMF 230, and DRMF 250. The DSIF 210 interacts with the DSMF 230, DRMF 250, the UIIF 410 of the UI, and the UDIF 510 of the UD. The DSIF 210 includes a Delivery service interworking management functional entity (DSIM-FE) 211, a Collecting / Identification functional entity (CI-FE) 213, and an Access priority handling functional entity (APH-FE) 215.

[0075] The DSIM-FE211 can perform operations related to delivery service interlock management. For example, the operations related to delivery service interlock management include:

[0076] · Receive (request) delivery requests from UD500 and respond (request) to UD500 delivery requests;

[0077] · A request to determine whether to assign a delivery robot to DRMF250;

[0078] Notify UI400 when DR300 is waiting to access UI400;

[0079] Receive access request results from UI400 to DR300;

[0080] ·Evaluate requests received from EE100 and notify DR300;

[0081] If a response is required for the request, the EE100 is notified of the processing result.

[0082] The CI-FE 213 can perform collection / identification related operations, such as:

[0083] UD500 Identification (requesting / forwarding / receiving);

[0084] Collect additional delivery information from UI400 or EE100 and provide it to DR300;

[0085] Collecting information such as the identifier, capabilities, and location of the UI 400

[0086] The APH-FE 215 may perform operations related to access priority processing, including, for example, the following:

[0087] -Determines UI400 access priority for DR300

[0088] The DSMF 230 can interact with the DSIF 210 and the DRMF 250. The DSMF 230 includes a Routing management functional entity (RM-FE) 231, a Delivery management functional entity (DM-FE) 233, and a Goods handling management functional entity (GHM-FE) 235.

[0089] The RM-FE 231 can perform operations related to routing management, including, for example, the following:

[0090] Generate delivery route information including pickup / delivery location, delivery time, and UI400 location;

[0091] Conversion between other coordinate systems

[0092] The DM-FE 233 can perform operations related to delivery management, including, for example:

[0093] ·Request delivery route information from RM-FE231;

[0094] Generate delivery information;

[0095] Generate goods information;

[0096] · Notify DRMF250 of delivery information;

[0097] · Monitoring delivery status and goods status;

[0098] -Notify UD500 of delivery status during delivery;

[0099] · Update delivery status by receiving direct interaction results from DR300 with UD500 or UI400

[0100] The GHM-FE235 can perform operations related to goods handling management, such as:

[0101] Receive goods handling request message from DR300

[0102] Notify UD500 when DR300 is waiting to load / unload goods at a pickup location or delivery location

[0103] When goods are received from the DR300, the UD500 is notified of the completion of goods loading / unloading.

[0104] When goods are received from the UD500, the DR300 is notified of the completion of goods loading / unloading.

[0105] The DRMF 250 includes a Delivery robot management functional entity (DRM-FE) 251. The DRM-FE 251 can perform operations related to DR management. For example, operations related to DR management include:

[0106] Maintaining a register of information about the DR300, such as its identifier and capabilities

[0107] Decide (or confirm) whether to allocate DR300 to the delivery request

[0108] - Notify the designated DR300 of delivery information

[0109] DR300 Monitoring

[0110] DR300 determines (or checks) whether the goods can be delivered continuously based on the delivery status information.

[0111] FIG. 3 is a diagram illustrating a delivery robot according to an embodiment.

[0112] Referring to Figure 3, the DR 300 can deliver goods based on a user's delivery request. The DR 300 includes an autonomous driving-based robot. The DR 300 can directly interact with the UD 500, the DRSP 200, and the UI 400. The DR 300 can indirectly interact with an external organization 15 via the DRSP 200.

[0113] The DR 300 may share information about the DR 300 (eg, identifiers, capabilities) with the DRSP 200.

[0114] The DR 300 may share delivery status information (eg, the current location of the DR 300, the item loading status, the type of item, and the item status) with the DRSP 200.

[0115] The DR 300 may identify one or more user devices for which goods must be delivered. For example, the DR 300 may identify a user device for loading goods and a user device for unloading goods (e.g., a recipient's user device).

[0116] If goods are loaded or unloaded by an object other than DR300 (e.g., a human, another robot), DR300 can notify DRSP200 that it is waiting to load or unload goods after arriving at the receiving location or delivery location.

[0117] The DR 300 receives information indicating that loading or unloading is completed from an object (e.g., a human, another robot) responsible for loading or unloading goods. After receiving the information, the DR 300 may notify the DRSP 200 that loading or unloading is completed.

[0118] When goods are loaded or unloaded by the DR 300, the DR 300 may notify the DRSP 200 that the loading or unloading has been completed after completing the loading or unloading of the goods.

[0119] After arriving at the UI 400, the DR 300 notifies the DRSP 200 that it is waiting to approach the UI 400.

[0120] The DR 300 may request the DRSP 200 to transmit additional information necessary for autonomous driving or for approaching the UI 400.

[0121] The DR 300 may maintain time synchronization with the DRSP 200 .

[0122] When an event that interferes with delivery (for example, a failure of the DR 300) occurs, the DR 300 may notify information about the event to the DRSP 200. The DR 300 takes the necessary action to resolve the event.

[0123] The DR300 may directly interact with the UD500, the UI400, and other delivery robots as needed. For example, the DR300 may directly interact with other delivery robots when a collision with another delivery robot located within a preset distance (or a distance that can be detected by a sensor) from the DR300 is predicted. The DR300 may directly interact with other delivery robots when congestion due to sharing a narrow space (e.g., a staircase) with the other delivery robot is predicted. The DR300 may calculate a congestion level based on at least one of the area of ​​the space surrounding the DR300, the type of the space surrounding the DR300, the size of the DR300, and the size of the other delivery robots. For example, the DR300 may determine a higher congestion level when the space surrounding the DR300 (e.g., an elevator) is more likely to be occupied by a person. The DR300 may directly interact with other delivery robots when the congestion level satisfies a threshold. The DR 300 may directly interact with the UI 400 when a communication failure occurs with the DRSP 200. The DR 300 may directly interact with the UD 500 when it needs to move to a location close to the UD 500 or when user authentication is required.

[0124] The DR 300 may notify the DRSP 200 of the result of the direct interworking.

[0125] The DR300 may interact with other delivery robots via the DRSP200.

[0126] The DR 300 may receive a request from the DRSP 200 to process a specific task with priority. The DR 300 can process the requested task with priority. The DR 300 transmits the processing result of the requested task to the DRSP 200.

[0127] The DR300 includes delivery robot interworking functions (DRIF310). In the DR300, interfaces for delivery services include DRM-DRI, DRI-UII, and DRI-UDI. The DRM-DRI may be an interface between the DRIM-FE311 and the DRM-FE251. The DRI-UII may be an interface between the DRIM-FE311 and the UIIM-FE411. The DRI-UDI may be an interface between the DRIM-FE311 and the UDIM-FE511.

[0128] The DRIF 310 can provide a function for interworking with the DRSP 200, the UI 400, and the UD 500. The DRIF 310 can interact with the DRMF 250 in the DRSP 200, the UIIF 410 of the UI 400, and the UDIF 510 of the UD 500.

[0129] DRIF 310 includes a Delivery robot interworking management functional entity (DRIM-FE) 311, a Delivery robot status monitoring functional entity (DRSM-FE) 313, and a Delivery robot goods handling functional entity (DRGH-FE) 315.

[0130] The DRIM-FE 311 can perform operations related to DR interworking management, such as:

[0131] ·Receive delivery information from DRSP200;

[0132] Generates results for direct interoperability with UD500 or UI400;

[0133] -When directly interlocking with UD500, UI400, and other DRs at close range, the interlocking results are notified to DRSP200;

[0134] Shares identifiers and capability information with DRSP200;

[0135] Identify UD500 (forwarding / receiving);

[0136] - When DR300 arrives at UI400, notify DRSP200;

[0137] If necessary, request updated delivery information from the DRSP 200 while self-driving or accessing the UI 400;

[0138] · Notify DRSP200 of delivery status and product status;

[0139] Maintains time synchronization with the DRSP200;

[0140] ·Identify other DRs;

[0141] · Indirect interoperability with other DRs via DRSP200;

[0142] Direct interoperability with UD500, UI400, and DR300 at close range

[0143] When a request (for example, a priority processing request) is received from the DRSP200, the priority processing request is specified as the priority and processed.

[0144] The DRSM-FE 313 can perform operations related to DR state monitoring, including, for example, the following:

[0145] Collect delivery status (e.g., DR's current heading and location, robot status, and battery status)

[0146] Immediately notify the DRSP200 of exceptions such as breakdowns

[0147] The DRGH-FE315 can perform actions related to goods handling, such as:

[0148] Collect goods status (e.g., condition and loading status of goods in transit);

[0149] Generates a completion message for loading / unloading goods;

[0150] Notify DRSP200 of the completion of loading / unloading of goods;

[0151] Generate a goods handling request message when the DR300 is waiting to load / unload goods at a pickup location or delivery location;

[0152] When loading / unloading is required, a goods handling request message is sent to the DRSP200.

[0153] FIG. 4 is a diagram illustrating urban infrastructure according to an embodiment.

[0154] Referring to FIG. 4, the UI 400 may include facilities (e.g., elevators, gates, communal entrances, electric charging stations) that the DR 300 must use, approach, and / or pass through to deliver goods. In this disclosure, the UI 400 refers to a device (e.g., a server) that manages the UI 400. The UI 400 can directly interact with the DR 300 and the DRSP 200.

[0155] The UI 400 may share information about the UI 400 (e.g., identifier, capabilities, location) with the DRSP 200.

[0156] The UI 400 may notify the DRSP 200 whether the approach of the DR 300 is approved.

[0157] The UI 400 may request the DRSP 200 to transmit information about goods loaded in the DR 300 .

[0158] The UI 400 can directly interface with the DRSP 200. The UI 400 may also interface with the DRSP 200 via another system (e.g., a building management system, an external infrastructure management service system).

[0159] The UI 400 may directly interact with the DR 300 located around the UI 400 .

[0160] In response to a request from the DRSP 200, the UI 400 may provide the DRSP 200 with information about the UI 400 (for example, service status, availability, breakdown, inspection).

[0161] The UI 400 includes urban infrastructure interworking functions (UIIF) 410. In the UI 400, interfaces for delivery services include a DSI-UII and a DRI-UII. The DSI-UII may be an interface between the UIIM-FE 411 and the DSIM-FE 211. The DRI-UII may be an interface between the UIIM-FE 411 and the DRI-FE 311.

[0162] The UIIF 410 can provide a function for interoperation with the DRSP 200 and the DR 300. The UIIF 410 can interoperate with the DSIF 210 of the DRSP 200 and the DRIF 310 of the DR 300.

[0163] The UIIF 410 includes an Urban infrastructure interworking management functional entity (UIIM-FE) 411, an Urban infrastructure monitoring functional entity (UIM-FE) 413, and an Access control functional entity (AC-FE) 415.

[0164] The UIIM-FE 411 can perform operations related to UI interworking management, such as:

[0165] Sharing information about city infrastructure (e.g., identifiers, capabilities, and location) with DRSP200

[0166] Interacts directly with the DRSP200 or indirectly with other systems such as a building management system or an external infrastructure management service system

[0167] Direct interlocking with DR300 in near-field

[0168] The UIM-FE 413 can perform actions related to UI monitoring, including, for example, the following:

[0169] Collecting infrastructure status (e.g., service status, availability, faults, inspections)

[0170] - Notify the DRSP200 of infrastructure status

[0171] The AC-FE 415 can perform operations related to access control, such as:

[0172] - Notifies the DR300 of the results of the access request to the UI400

[0173] When DR300 accesses UI400, it requests delivery information from DRSP200

[0174] FIG. 5 is a diagram illustrating a user device according to an embodiment.

[0175] 5, the UD 500 includes one or more terminals. For example, the UD 500 may include one or more of a terminal of a delivery requester, a device related to loading goods, and a terminal related to unloading goods. The terminals include electronic devices operated by users, such as mobile devices and computing devices, and / or unattended electronic devices that can store and / or manage goods. The UD 500 can directly interface with the DRSP 200 and the DR 300.

[0176] The UD 500 may provide functionality (eg, a user interface) that can receive delivery requests from users and provide delivery status information to users.

[0177] The UD 500 may transmit the delivery information input by the user to the delivery service provider 17 .

[0178] The UD 500 may collect location information of the UD 500 .

[0179] When the UD 500 receives information that must be confirmed or processed by the user, it may notify the user using various means (e.g., sound, vibration, light).

[0180] The UD 500 may directly interact with the DR 300 located near the UD 500. For example, the UD 500 may directly interact with the DR 300 when the DR 300 is located within a preset distance from the UD 500.

[0181] When the UD 500 receives a request to load or unload goods from the DRSP 200, the UD 500 may notify a user (for example, a person in charge of loading, a recipient).

[0182] The UD 500 may notify the DRSP 200 that the loading or unloading of goods has been completed.

[0183] The UD 500 includes user device interworking functions (UDIF) 510 and user device management functions (UDMF) 530. In the UD 500, interfaces for delivery services include UDI-UDM1, UDI-UDM2, UDI-UDM3, DSI-UDI, and DRI-UDI. The UDI-UDM1 may be an interface between the UDIM-FE 511 and the UN-FE 531. The UDI-UDM2 may be an interface between the UDIM-FE 511 and the CL-FE 533. The UDI-UDM3 may be an interface between the UDGH-FE 513 and the UN-FE 531. The DSI-UDI may be an interface between the UDIM-FE 511 and the DSIM-FE 211. The DRI-UDI may be an interface between the UDIM-FE 511 and the DRIM-FE 311.

[0184] The UDIF 510 can provide a function for interoperation with the DRSP 200, the DR 300, and the UDMF 530. The UDIF 510 may interoperate with the UDMF 530, the DSIF 210 of the DRSP 200, and the DRIF 310 of the DR 300.

[0185] The UDIF 510 includes a User Device Interworking Management Functional Entity (UDIM-FE) 511 and a User Device Goods Handling Functional Entity (UDGH-FE) 513.

[0186] UDIM-FE511 can perform operations related to UD interoperability management, including the following:

[0187] · Receive delivery requests from users;

[0188] ·Notify DRSP200 of delivery request;

[0189] Direct interlocking with DR300 at close range when necessary

[0190] The UDGH-FE513 can perform operations related to goods handling, such as:

[0191] Generates messages for the completion of goods loading / unloading;

[0192] Notify DRSP200 of the completion of loading / unloading of goods;

[0193] Collecting product status (e.g., the condition and loading status of products being delivered) and sharing the product status with the DRSP 200;

[0194] Upon receiving a request for loading / unloading goods, notify the responsible entity for performing the loading / unloading function

[0195] The UDMF 530 can provide a function for interoperating with the UDIF 510. The UDMF 530 may interoperate with the UDIF 510.

[0196] The UDMF 530 includes a User Notification Functional Entity (UN-FE) 531 and a Collecting Location Functional Entity (CL-FE) 533.

[0197] The UN-FE 531 can perform actions related to user notification, such as:

[0198] When information requiring confirmation or processing is received, the user is notified by means such as sound, vibration, or light.

[0199] -Display delivery status to users

[0200] The CL-FE 533 may provide location collection related operations, such as:

[0201] Obtain your own location information

[0202] FIG. 6 illustrates a workflow for requesting delivery and initiating delivery on a user device according to one embodiment.

[0203] In operations 611 to 616, the UDIM-FE 511 of the UD 500 transmits a request for goods delivery to the DRSP 200. The DRSP 200 can check whether the DR 300 is available for use and notify the UN-FE 531 of the UD 500 of approval of the delivery request.

[0204] In operations 621 to 625, after generating delivery information including delivery route information, the DRM-FE 251 of the DRSP 200 allocates a DR 300 to the delivery request.

[0205] In operations 631 and 632, the DRM-FE 251 of the DRSP 200 notifies the DRIM-FE 311 of the DR 300 of the delivery information. The DR 300 can then start delivery.

[0206] In operations 641 to 643, during delivery, the DRSM-FE 313 collects and notifies the DRSP 200 of the delivery status (for example, the current heading and position, the robot and battery status, etc.).

[0207] In operations 651 to 656, the DM-FE 233 monitors the delivery status based on the received notification and notifies the UN-FE 531 of the UD 500 of the status.

[0208] FIG. 7 illustrates a workflow for receiving a goods load completion notification from a delivery robot according to one embodiment.

[0209] In operations 711 to 717, the DRGH-FE 315 of the DR 300 notifies the UD 500 via the DRSP 200 when the DR 300 is waiting to load goods at the loading position.

[0210] In operation 720, based on the received notification, the UDGH-FE 513 of the UD 500 sends a request to the UN-FE 531 to load the goods.

[0211] In operation 730, the DR 300 loads the goods at the loading location.

[0212] In operations 741 to 748, when the loading is completed, the DRSP 200 receives a completion message from the DR 300 and then notifies the UN-FE 531 of the UD.

[0213] FIG. 8 illustrates a workflow for receiving a notification of completion of goods unloading from a delivery robot according to one embodiment.

[0214] In operations 811 to 817, the DRGH-FE 315 of the DR 300 notifies the UD 500 via the DRSP 200 when the DR is waiting to unload goods at the delivery location.

[0215] In operation 820, based on the received notification, the UDGH-FE 513 of the UD 500 sends a request to the UN-FE 531 to unload the goods.

[0216] In operation 830, the DR 300 unloads the goods at the unloading location.

[0217] In operations 841 to 848, when the unloading is completed, the DRSP 200 receives a completion message from the DR 300 and notifies the UN-FE 531 of the UD 500 of the completion message.

[0218] FIG. 9 illustrates a workflow for receiving a product load completion notification on a user device according to one embodiment.

[0219] In operations 911 to 917, the DRGH-FE 315 of the DR 300 notifies the UD 500 via the DRSP 200 when the DR 300 is waiting to load goods at the loading position.

[0220] In operation 920, based on the received notification, the UDGH-FE 513 of the UD 500 sends a request to the UN-FE 531 to load the goods.

[0221] In operation 930, the DR 300 loads the goods at the loading location.

[0222] In operations 941 to 947, when the loading is completed, the DRSP 200 receives a completion message from the UD 500 and notifies the DRIM-FE 311 of the DR 300 of the completion message.

[0223] FIG. 10 illustrates a workflow for receiving a notification of the completion of goods unloading on a user device according to one embodiment.

[0224] In operations 1011 to 1017, the DRGH-FE 315 of the DR 300 notifies the UD 500 via the DRSP 200 when the DR 300 is waiting to unload goods at the unload position.

[0225] In operation 1020, based on the received notification, the UDGH-FE 513 of the UD 500 sends a request to the UN-FE 531 to unload the goods.

[0226] In operation 1030, the DR 300 unloads the goods at the unload location.

[0227] In operations 1041 to 1047, when the unloading is completed, the DRSP 200 receives a completion message from the UD 500 and notifies the DRIM-FE 311 of the DR 300 of the completion message.

[0228] FIG. 11 illustrates a workflow for interworking between delivery robots and city infrastructure according to one embodiment.

[0229] In operations 1111 to 1113, when the DR300 waits in the UI400, the DRIM-FE311 notifies the UIIM-FE411 via the DRSP200.

[0230] In operation 1120, based on the received notification, the UIIM-FE 411 sends a request to the AC-FE 415 for the DR 300 to access the UI 400.

[0231] In operations 1131 to 1135, when the UIIM-FE 411 receives access approval from the AC-FE 415, it notifies the DRIM-FE 311 via the DRSP 200.

[0232] In operation 1140, the DR 300 accesses the UI 400.

[0233] FIG. 12 illustrates a workflow for interworking between delivery robots and city infrastructure according to one embodiment.

[0234] In operation 1210, the DRIM-FE 311 directly notifies the UIIM-FE 411 when the DR 300 is waiting in the vicinity of the UI 400.

[0235] In operation 1220, based on the received notification, the UIIM-FE 411 sends a request to the AC-FE 415 for the DR 300 to access the UI 400.

[0236] In operations 1231 to 1233, when the access approval is received from the AC-FE 415, the UIIM-FE 411 notifies the DRIM-FE 311.

[0237] In operation 1240, the DR 300 accesses the UI 400.

[0238] In operations 1251 and 1252, the DRIM-FE 311 notifies the DM-FE 233 of the interworking result directly via the DRM-FE 251 of the DR 300.

[0239] FIG. 13 is a schematic block diagram of an apparatus according to one embodiment.

[0240] 13, according to one embodiment, the device 1300 includes a processor 1320, a memory 1340, and a communication module 1360. The device 1300 may be the delivery robot service provider 200 or the delivery robot 300 described with reference to FIGS.

[0241] Memory 1340 stores instructions (or programs) executable by processor 1320. For example, the instructions may include instructions for performing operations of processor 1320 and / or each component of processor 1320.

[0242] Memory 1340 includes one or more computer-readable storage media, and may include non-volatile storage elements (e.g., magnetic hard disk, optical disk, floppy disk, flash memory, electrically programmable memories (EPROM), electrically erasable and programmable memories (EEPROM)).

[0243] The memory 1340 may be a non-transitory medium. The term "non-transitory" indicates that the storage medium is not embodied in a carrier wave or radio-transmitted signal. However, the term "non-transitory" should not be construed as meaning that the memory 1340 is immovable.

[0244] The processor 1320 can process data stored in the memory 1340. The processor 1320 can execute computer-readable code (e.g., software) stored in the memory 1340 and instructions triggered by the processor 1320.

[0245] The processor 1320 is a data processing device implemented in hardware having circuits with physical structures for performing desired operations, which may include, for example, code or instructions contained in a program.

[0246] For example, a data processing device implemented in hardware may include a microprocessor, a central processing unit, a processor core, a multi-core processor, a multiprocessor, an ASIC (Application-Specific Integrated Circuit), or an FPGA (Field Programmable Gate Array).

[0247] The processor 1320 executes codes, instructions, and / or applications stored in the memory 1340, causing the device 1300 to perform one or more operations. The operations performed by the device 1300 may be substantially the same as the operations performed by the delivery robot service provider 200 or the delivery robot 300 described with reference to Figures 1 to 12. Here, a duplicated description will be omitted.

[0248] The communication module 1360 can establish a communication channel (e.g., a wireless communication channel) for communication. The communication module 1360 supports communication through the established communication channel. The communication module 1360 may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. The communication module 1360 includes a wireless communication module (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (e.g., a local area network (LAN) communication module, or a power line communication module).

[0249] The above-described embodiments may be implemented using hardware components, software components, and / or a combination of hardware and software components. For example, the adaptive supersampling apparatus, methods, and components described in the embodiments may be implemented using a general-purpose computer or a special-purpose computer, such as a processor, controller, arithmetic logic unit (ALU), digital signal processor, microcomputer, field programmable gate array (FPGA), programmable logic unit (PLU), microprocessor, or other device capable of executing and responding to commands. The processing device may execute an operating system (OS) and software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to the execution of software. For ease of understanding, the description may refer to a single processing device, but those skilled in the art will recognize that the processing device may include multiple processing elements and / or multiple types of processing elements. For example, the processing adaptive supersampling apparatus may include multiple processors or one processor and one controller. Other processing configurations are also possible, such as parallel processors.

[0250] The software may include a computer program, code, instructions, or any combination thereof, capable of configuring a processing device or instructing the processing device, either individually or collectively, as desired. The software and / or data may be permanently embodied in any type of machine, component, physical adaptive supersampling device, virtual adaptive supersampling device, computer storage medium, or adaptive supersampling device, or transmitted signal wave, to be interpreted by or provide instructions or data to the processing adaptive supersampling device. The software may be distributed across networked computer systems and stored or executed in a distributed manner. The software and data may be stored on a computer-readable recording medium.

[0251] The method according to the present invention may be embodied in the form of program instructions that can be executed by various computer means and recorded on a computer-readable recording medium. The recording medium may include program instructions, data files, data structures, and the like, alone or in combination. The recording medium and program instructions may be specially designed and constructed for the purposes of the present invention, or they may be well known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language code, such as that generated by a compiler, but also high-level language code that is executed by a computer using an interpreter, for example.

[0252] The hardware devices described above may be configured to operate as one or more software models to perform the operations described in the present invention, and vice versa.

[0253] Although the embodiments have been described above with reference to limited drawings, those skilled in the art may apply various technical modifications and variations based on the above description. For example, the described techniques may be performed in a different order than described, and / or the components of the described systems, structures, devices, circuits, etc. may be combined or combined in a different manner than described, and may be replaced or substituted with other components or equivalents, while still achieving suitable results.

[0254] Accordingly, other implementations, other embodiments, and equivalents of the claims are intended to fall within the scope of the following claims.

Claims

1. 1. A method of operation of a delivery robot service provider, comprising: receiving a delivery request from a user device; generating delivery information for the delivery request; An operation of allocating a delivery robot that performs the delivery request; an operation of transmitting the delivery information to the delivery robot; While the delivery robot delivers the goods according to the delivery information, sharing the current location of the delivery robot and the loading status of the goods with the delivery robot service provider; , including a method of operation.

2. 2. The method of claim 1, wherein the delivery information includes at least one of a pick-up location for the goods, a delivery location for the goods, a delivery time for the goods, information about infrastructure that must be interconnected with the delivery robot to deliver the goods, a delivery route for the goods, and a type of the goods.

3. The method of claim 1 , wherein the delivery robot service provider maintains information regarding infrastructure that can interact with the delivery robot.

4. The method of claim 1 , further comprising interfacing with infrastructure located along a delivery route of the goods.

5. 5. The method of claim 4, further comprising determining access priorities for the infrastructure between the delivery robot and the other delivery robots based on the presence of other delivery robots competing with the delivery robot for access to the infrastructure.

6. The method of claim 5 , wherein the determining operation includes an operation of determining the access priority through mutual cooperation with the other delivery robot service provider when the other delivery robot is managed by the delivery robot service provider.

7. The method of claim 1 , further comprising transmitting to the user device a corresponding loading status of the item or an unloading status of the item.

8. A device for managing a delivery robot, a processor; a memory for storing instructions; Including, The instructions, when executed by the processor, cause the device to perform a number of operations; The plurality of operations include: receiving a delivery request from a user device; generating delivery information for said delivery request; An operation of allocating a delivery robot that performs the delivery request; an operation of transmitting the delivery information to the delivery robot; sharing a current location of the delivery robot and a loading status of the goods with a delivery robot service provider while the delivery robot delivers the goods according to the delivery information; 1. An apparatus comprising:

9. 10. The device of claim 8, wherein the delivery information includes at least one of a pick-up location for the goods, a delivery location for the goods, a delivery time for the goods, information about infrastructure that must be interconnected with the delivery robot to deliver the goods, a delivery route for the goods, and a type of the goods.

10. The device of claim 8 , wherein the device maintains information about infrastructure that can interact with the delivery robot.

11. The apparatus of claim 8 , wherein the plurality of operations further comprises an operation to interact with infrastructure located along a delivery route of the good.

12. 12. The apparatus of claim 11, wherein the plurality of operations further includes an operation of determining access priorities for the infrastructure between the delivery robot and the other delivery robots based on the presence of other delivery robots competing with the delivery robot for access to the infrastructure.

13. The apparatus of claim 12 , wherein the determining operation includes determining the access priority through interaction with the other delivery robot service provider when the other delivery robot is managed by the delivery robot service provider.

14. The device of claim 8 , wherein the plurality of operations further comprises an operation of transmitting a loading status of the item or an unloading status of the item to a corresponding one of the user devices.

Images