Label-based mobility data management method and apparatus

Abstract

The present disclosure relates to a mobility data management method and apparatus. According to one embodiment of the present disclosure, a mobility data management apparatus can store data collected from a mobility device, receive a data provision request from an external system, and then determine data provision suitability on the basis of label information corresponding to request target data. In addition, on the basis of the provision suitability determination result, a response including whether to provide data and a provision range can be generated and provided to the external system, and, when the label information corresponding to the request target data does not exist, label setting can be performed using a user terminal. Therefore, systematic data provision management based on data provision request conditions and data label attributes becomes possible, and the security and utilization of mobility data can be ensured at the same time. In addition, the transparency and traceability of a data provision process can be improved by providing, to a user, information related to a data provision request and a processing result.

Description

Label-based mobility data management method and device

[0001] The present disclosure relates to a technology for managing data generated in a mobility environment, and more specifically, to a method and apparatus for determining the suitability of providing mobility data based on label information and ensuring transparency in the data provision process.

[0002] The following description merely provides background information related to the present embodiment and does not constitute prior art.

[0003] As various forms of mobility, such as vehicles, UAM (Urban Air Mobility), AAM (Advanced Air Mobility), and autonomous vehicles, become more widespread, the importance of utilizing mobility data generated during the operation of these vehicles is gradually increasing.

[0004] Mobility data can be collected and utilized for various purposes, such as analyzing travel routes, improving traffic flow, supporting safe driving, providing insurance services, and implementing customized mobility services, and can be used by various entities including insurance companies, financial institutions, mobility service providers, and public institutions.

[0005] Generally, the provision of mobility data can be based on the user's prior consent; however, once consent is given, there is a problem in that it is difficult for users to continuously verify or control when, by whom, and for what purpose their mobility data is utilized. Furthermore, there is a possibility that data may be used for purposes different from the originally agreed-upon intent, and in such cases, there are limitations in clearly determining liability regarding the data provision and utilization process.

[0006] In particular, since mobility data can include sensitive personal information such as travel routes, location data, usage patterns, and payment information, technical means are required to finely manage whether and to what extent data is provided. However, conventional technologies have not sufficiently presented a data management structure capable of making policy-based decisions on whether to provide mobility data and systematically managing the history of its provision.

[0007] Therefore, considering the characteristics and utilization environment of mobility data, there is a need for data management technology that can provide users with initiative in data management and enhance transparency and traceability in the data provision process.

[0008] The present disclosure aims to provide a data management technology capable of efficiently managing the provision and utilization of various mobility data generated in a mobility environment.

[0009] The present disclosure aims to provide a technology capable of systematically managing whether to provide data and the scope of provision based on label information in response to a data provision request from an external entity.

[0010] The present disclosure aims to provide a technology that enables a user to verify a request from an external entity for the provision of their mobility data and the results of processing such request.

[0011] The problems that the present invention aims to solve are not limited to those mentioned above, and other unmentioned problems will be clearly understood by a person skilled in the art from the description below.

[0012] According to one aspect of the present disclosure, a method performed by a mobility data management device is provided.

[0013] The above method may include: a process of collecting and storing mobility data from a mobility device; a process of receiving a data provision request from an external system; a process of determining the suitability of data provision based on label information corresponding to the requested target data included in the data provision request; and a process of generating a data provision response including information regarding whether to provide and the scope of provision based on the result of determining the suitability of provision and transmitting it to the external system.

[0014] The above data provision request may include information on the requesting party, identification information on the requested data, information on the purpose of data utilization, and information on the scope of the requested data.

[0015] The above label information may include at least one attribute information among security level, data disclosure scope, data provision permission period, eligible data provider, data utilization purpose, and activation status.

[0016] The process of determining the suitability of the above provision can be performed by comparing the data provision conditions derived based on the above label information with the information included in the above data provision request.

[0017] According to another aspect of the present disclosure, a mobility data management device configured to perform the above method is provided.

[0018] The above mobility data management device comprises a communication interface; at least one memory for storing instructions; and at least one processor, wherein the at least one processor executes the instructions to store mobility data received from a mobility device, receives a data provision request from an external system, determines the suitability for provision based on label information corresponding to the requested target data included in the data provision request, and, based on the result of determining the suitability for provision, generates a data provision response including information regarding whether to provide and the scope of provision, and transmits it to the external system.

[0019] According to the present disclosure, by actively setting and managing the conditions for providing their mobility data, users can enhance data ownership and user privacy protection.

[0020] According to the present disclosure, transparency in the process of providing mobility data can be ensured, and post-verification of the data usage process is possible based on historical information regarding data provision requests and processing results, thereby clarifying the locus of responsibility in the event of data misuse and improving accountability.

[0021] The effects of the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by a person skilled in the art from the description below.

[0022] FIG. 1 is a schematic diagram illustrating an environment in which a label-based mobility data management system according to one embodiment of the present disclosure is applied.

[0023] FIG. 2 is a block diagram illustrating the configuration of a mobility data management device according to one embodiment of the present disclosure.

[0024] FIG. 3 is a flowchart illustrating an operation procedure performed by a label-based mobility data management device according to one embodiment of the present disclosure.

[0025] FIG. 4 is a flowchart illustrating a periodic label setting management procedure performed by a label-based mobility data management device according to one embodiment of the present disclosure.

[0026] FIG. 5 is a flowchart illustrating a procedure for determining data provision suitability performed by a label-based mobility data management device according to one embodiment of the present disclosure.

[0027] FIG. 6 is a flowchart illustrating a data provision and user notification procedure performed by a label-based mobility data management device according to one embodiment of the present disclosure.

[0028] FIG. 7 is a block diagram of an exemplary computing device that can be used to implement a device for performing a method according to an embodiment of the present disclosure.

[0029] Some embodiments of the present disclosure are described in detail below with reference to exemplary drawings. It should be noted that in assigning reference numerals to the components of each drawing, the same components are given the same reference numeral whenever possible, even if they are shown in different drawings. Furthermore, in describing the present disclosure, if it is determined that a detailed description of related known components or functions could obscure the essence of the present disclosure, such detailed description is omitted.

[0030] In describing the components of the embodiments according to the present disclosure, symbols such as first, second, i), ii), a), b), etc., may be used. These symbols are intended only to distinguish the components from other components, and the essence, order, or sequence of the components is not limited by the symbols. When a part in the specification is described as 'comprising' or 'having' a component, this means that, unless explicitly stated otherwise, it does not exclude other components but may include additional components.

[0031] The detailed description set forth below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiment in which the present disclosure may be practiced.

[0032] In this specification, "mobility data" refers to all data that occurs or is generated during the operation of various forms of mobility, such as vehicles, UAM (Urban Air Mobility), AAM (Advanced Air Mobility), and autonomous vehicles. For example, it includes driving records, billing information and records, transmitted and received data, EDR (Event Data Recorder) data, DSSAD (Data Storage System for Automated Driving) data, etc.

[0033] In this specification, 'Label' may refer to data provision judgment criteria information set or assigned in correspondence with mobility data to determine whether mobility data can be provided or the conditions for provision. Labels may be set at the unit of individual mobility data or at the unit of mobility data groups.

[0034] A label may include one or more attribute information indicating the scope and conditions of use of mobility data, and such attribute information may be used to determine whether to provide data, determine the scope of provision, or set conditions for provision restriction.

[0035] The attribute information included in the label may include the type of data, security level, scope of disclosure, disclosure period, place of use, purpose of use, and activation status.

[0036] The types of data may include passenger demand information, personally identifying information (PII), weight information, payment information, location information, route information, or insurance-related information.

[0037] Mobility data can be classified into static data and dynamic data depending on operation characteristics and purpose of use.

[0038] Static data may refer to data that changes infrequently over time or is utilized non-real-time. For example, mobility route information, charging infrastructure location data, service operation statistics, insurance and regulatory information, and regional traffic demographic data may be included in static data.

[0039] Dynamic data may refer to data generated in real-time or near-real-time during operation. For example, current location information, travel speed information, real-time traffic condition information, passenger demand information, vehicle status information, battery level information, payment approval information, and remote control command information may be included in dynamic data.

[0040] Such classification of mobility data can be utilized to set data provision policies or determine data security levels.

[0041] Security grades can be classified according to security level, such as confidential, private, sensitive, or public.

[0042] Mobility data can be classified into multiple security classes based on risk, utility value, and relevant legal regulatory levels. For example, mobility data can be classified as confidential data, private data, sensitive data, or public data.

[0043] Confidential data may require the highest level of security protection as it can directly affect mobility operation safety or system control.

[0044] Personal data is data that includes information capable of identifying an individual or inferring the characteristics of an individual, and may be subject to personal information protection regulations.

[0045] Sensitive data is data that could cause economic or service operational impacts in the event of a security breach and may qualify as data for which security measures are recommended.

[0046] Public data is data that can be provided without separate access restrictions, and may require only a basic level of protection to maintain integrity.

[0047] Depending on the security level, security objectives such as confidentiality, integrity, availability, authentication, authorization, non-repudiation, or accountability may be set differentially.

[0048] The scope of disclosure may be set to all data or part of the data, and the disclosure period may include the validity period of the data or the data provision period set by the data owner.

[0049] The places of use may include insurance companies, credit card companies, or mobility service providers, and the purposes of use may include calculating insurance premiums, analyzing card usage patterns, analyzing routes, or providing customized services.

[0050] The enabled state indicates whether data provision is permitted, and in the disabled state, the provision of mobility data to external entities, excluding the data owner, is restricted.

[0051] The present disclosure relates to a technology for managing data generated in a mobility environment, and more specifically, to a label-based mobility data management method and apparatus capable of determining the suitability of data provision based on label information assigned to mobility data and performing management and control functions of the data provision process.

[0052] According to the present disclosure, whether and how mobility data is provided can be determined based on label information, and by notifying the user of the results of the data provision request processing, the reliability, transparency, and traceability of the mobility data provision process can be improved.

[0053] FIG. 1 is a schematic diagram illustrating an environment in which a label-based mobility data management system according to one embodiment of the present disclosure is applied.

[0054] Referring to FIG. 1, a label-based mobility data management system may include a mobility device (100), a mobility data management device (200), a user terminal (300), and a third-party system (400).

[0055] The mobility device (100) may include various forms of means of transportation such as vehicles, UAM (Urban Air Mobility), AAM (Advanced Air Mobility), and autonomous vehicles, and generates various mobility data such as location information, movement path information, usage pattern information, and payment information generated during operation.

[0056] The mobility device (100) periodically transmits generated mobility data to the mobility data management device (200). The mobility device (100) can transmit mobility data to the mobility data management device (200) via a wired or wireless communication network and a secure communication channel.

[0057] The mobility data management device (200) performs the functions of collecting, storing, managing, and determining whether to provide mobility data. The mobility data management device (200) determines the suitability of providing data based on label information assigned to the mobility data and manages the results of providing data.

[0058] The mobility data management device (200) can be implemented as a cloud-based data management system operated by a car manufacturer, etc., and can perform functions such as providing mobility services, remote diagnosis, software updates, and data sharing.

[0059] The user terminal (300) is an electronic device used by the owner of the mobility data and can perform functions such as setting a label for the mobility data, checking the history of data provision requests, and checking the results of data provision.

[0060] The user terminal (300) may include a smartphone, smart watch, tablet, computer, or portable electronic device, but is not limited thereto.

[0061] The third-party system (400) includes an external data utilization system operated by an insurance company, financial institution, mobility service provider, or public institution, and transmits a data provision request to the mobility data management device (200) and receives the result of the request processing.

[0062] FIG. 2 is a block diagram illustrating the configuration of a mobility data management device according to one embodiment of the present disclosure.

[0063] Referring to FIG. 2, the mobility data management device (200) includes a mobility data storage (210), a mobility data processing module (220), a label management module (230), a data provision decision module (240), and a communication interface module (250).

[0064] The mobility data storage (210) stores mobility data collected from the mobility device (100), label information corresponding to the mobility data, data provision request information, data provision processing result information, etc.

[0065] The mobility data storage (210) may be implemented as a data storage structure including one or more physical storage devices or virtualized storage resources, for example, as a cloud-based distributed storage structure or a network storage system.

[0066] The mobility data processing module (220) collects and processes mobility data. The mobility data processing module (220) receives mobility data from the mobility device (100), performs data consistency verification and preprocessing, and then stores the data in the mobility data storage (210).

[0067] The mobility data processing module (220) can update the corresponding mobility data stored in the mobility data storage (210) with the mobility data to which label information is assigned, based on the label setting result transmitted from the label management module (230).

[0068] The mobility data processing module (220) can extract and configure data to be provided or restrict data provision based on the judgment result of the data provision decision module (240).

[0069] The label management module (230) manages label information corresponding to mobility data.

[0070] The label management module (230) can look up data stored in the mobility data storage (210) to identify data requiring label setting, and interact with the user terminal (300) to send a label setting request and receive a label setting response.

[0071] The label management module (230) can perform a label setting procedure in conjunction with the user terminal (300) even when a request for label setting for specific data is received from a third-party system (400).

[0072] The data provision decision module (240) determines whether to provide mobility data.

[0073] The data provision decision module (240) determines the suitability of providing the requested data when a request for mobility data provision is received from a third-party system (400).

[0074] The data provision decision module (240) can determine the suitability of data provision by comprehensively considering label information assigned to the mobility data, authorization information of the requesting entity, the purpose of data provision, conditions for the data disclosure period, conditions for the scope of data disclosure, etc.

[0075] The data provision decision module (240) may request a label setting from the user terminal (300) through the label management module (230) if the requested data is not assigned label information, and may perform a data provision suitability determination procedure based on the label setting response.

[0076] The data provision decision module (240) can generate response information including whether to provide data or reasons for refusing to provide it and transmit it to a third-party system (400).

[0077] The data provision decision module (240) can generate information to notify the user terminal (300) of the fact that a data provision request occurred or the result of the data provision processing.

[0078] The communication interface module (250) performs communication with an external device or system. The communication interface module (250) can be connected to a mobility device (100), a user terminal (300), and a third-party system (400) via a wired or wireless communication network.

[0079] The communication interface module (250) may include an interface function for receiving mobility data generated from a mobility device (100), an interface function for requesting and responding to label setting with a user terminal (300), and an interface function for requesting and responding to data provision with a third-party system (400).

[0080] FIG. 3 is a flowchart illustrating an operation procedure performed by a label-based mobility data management device according to one embodiment of the present disclosure.

[0081] Referring to FIG. 3, the mobility data management device (200) performs a series of data lifecycle management procedures including the collection of mobility data, label setting management, determination of suitability for data provision, and notification of the result of data provision.

[0082] The mobility data management device (200) collects mobility data generated from the mobility device (100) (S310). The mobility data management device (200) can perform data consistency verification or preprocessing on the collected mobility data and then store it.

[0083] The mobility data management device (200) receives a request for mobility data provision from a third-party system (400) (S320). The data provision request may include, for example, information on the requesting party, identification information on the mobility data to be requested, information on the purpose of data utilization, and information on the scope of the requested data.

[0084] The mobility data management device (200) determines whether there is label information corresponding to the mobility data specified by the received data provision request (S330).

[0085] If label information corresponding to the requested mobility data exists, the mobility data management device (200) determines the suitability of providing the requested mobility data by comparing the data provision conditions derived based on the label attribute information with the requesting subject information, data utilization purpose information, and requested data range information included in the data provision request (S370).

[0086] "Determination of suitability for data provision" may mean a procedure for determining whether the requested mobility data can be provided or the range of possible provision by comparing the information included in the data provision request received from the third-party system (400) with the label attribute information included in the label information set in correspondence with the requested mobility data.

[0087] For example, the mobility data management device (200) can determine the suitability of providing the requested mobility data based on at least one of the following.

[0088] (a) whether the requesting subject information included in the data provision request is included in the eligible subjects for data provision set as the label attribute,

[0089] (b) whether the data usage purpose information included in the data provision request matches the data usage purpose set as a label attribute or falls within the permissible range,

[0090] (c) whether the request data range information included in the data provision request is included within the data disclosure range set by the label attribute,

[0091] (d) whether the time of the data provision request falls within the data provision allowance period set by the label attribute, or

[0092] (e) Whether the activation state set by the label attribute is a state where data provision is allowed.

[0093] The mobility data management device (200) may allow the provision of all or part of the requested mobility data, or restrict or refuse the provision of data, depending on the result of the judgment, and if the provision is allowed, it may determine the range of data that can be provided or the conditions for provision.

[0094] On the other hand, if label information does not exist, the mobility data management device (200) may transmit a label setting request to the user terminal (300) (S340). The label setting request includes data identification information or data range information for identifying mobility data to be labeled, and the label setting request may be performed in units set based on the type of data, data generation period, or purpose of data utilization, but is not limited thereto.

[0095] The mobility data management device (200) can receive a label setting response from a user terminal (300) (S350). The label setting response includes one or more label attribute information that is set in correspondence with the mobility data to be labeled, and the label attribute information may include at least one of a security level, a data disclosure scope, a data provision permission period, a subject eligible for data provision, a purpose of data utilization, and an activation status.

[0096] The mobility data management device (200) can generate label information corresponding to the mobility data to be labeled or update existing label information based on the label attribute information included in the received label setting response, and store the generated or updated label information in the mobility data storage (210) (S360).

[0097] The mobility data management device (200) determines the suitability of providing the requested mobility data by comparing the data provision conditions derived based on label attribute information and the request subject information, data utilization purpose information, and request data range information included in the data provision request (S370).

[0098] The mobility data management device (200) generates a data provision response based on the result of determining the suitability of data provision and transmits the data provision response to a third-party system (400) (S380). The data provision response may include at least one of a response code indicating the processing result of a data provision request, data available for provision, and a reason for restricting provision.

[0099] Additionally, the mobility data management device (200) can notify the user terminal (300) of information regarding the occurrence of a data provision request or the result of the data provision processing (S390).

[0100] FIG. 4 is a flowchart illustrating a periodic label setting management procedure performed by a label-based mobility data management device according to one embodiment of the present disclosure.

[0101] Referring to FIG. 4, the mobility data management device (200) can periodically check the label setting status of mobility data stored in the mobility data storage (210), identify data requiring label setting, and perform a label setting procedure.

[0102] The mobility data management device (200) can periodically query data stored in the mobility data storage (210) (S410). At this time, the query period can be set according to system settings, data generation frequency, data utilization policy or security management policy, etc.

[0103] The mobility data management device (200) can identify mobility data among the retrieved data for which label information has not been assigned or for which a label setting is required (S420). For example, newly collected data, data for which a label setting is missing, or data for which an update of label attribute information is required may be identified.

[0104] The mobility data management device (200) can determine whether a label setting is necessary for the identified data (S430). The determination of whether a label setting is necessary can be performed based on at least one of, for example, whether label information corresponding to the mobility data exists, whether the validity period of the previously set label information has expired, whether there is a request to change the label attribute, or whether the label setting criteria defined by the activation status or data management policy are satisfied.

[0105] If it is determined that label setting is not required, the mobility data management device (200) may perform a periodic inquiry procedure without performing a label setting procedure.

[0106] If it is determined that label setting is required, the mobility data management device (200) may generate label setting request information and transmit it to the user terminal (300) (S440). The label setting request information may include data identification information, data range information, or data type information for identifying mobility data to be labeled, and the label setting request may be performed by the type of data, data generation period, purpose of data utilization, or data group.

[0107] The mobility data management device (200) can receive label setting response information from the user terminal (300) (S450). The label setting response information may include one or more label attribute information that is set in correspondence with the mobility data to be labeled, and the label attribute information may include at least one of a security level, a data disclosure scope, a data provision permission period, a subject eligible for data provision, a purpose of data utilization, and an activation status.

[0108] The mobility data management device (200) can generate label information or update existing label information based on the received label setting response (S460).

[0109] The mobility data management device (200) can reflect the generated or updated label information in the corresponding mobility data and update the mobility data storage (210) (S470).

[0110] Through such a periodic label setting management procedure, the mobility data management device (200) can preemptively set the conditions for providing data at a stage prior to the occurrence of a data provision request, and accordingly, improve the efficiency of the data provision request processing process and the reliability of data management.

[0111] Meanwhile, the mobility data management device (200) can update or delete label attribute information corresponding to the mobility data in response to a change in the management status of the mobility data.

[0112] For example, if the data provision permission period expires, the data provision management policy changes, or the scope of data provision targets changes, one or more attributes included in the label attribute information may change.

[0113] In addition, if mobility data is deleted, label attribute information stored in correspondence with the mobility data may also be deleted.

[0114] In other words, label attribute information can be dynamically managed according to the procedures for the creation, storage, provision, and deletion of mobility data.

[0115] FIG. 5 is a flowchart illustrating a procedure for determining data provision suitability performed by a label-based mobility data management device according to one embodiment of the present disclosure.

[0116] Referring to FIG. 5, the mobility data management device (200) performs a procedure to determine the suitability of providing the requested mobility data based on a mobility data provision request received from a third-party system (400).

[0117] The mobility data management device (200) can analyze information on the requesting subject, identification information on the requested mobility data, information on the purpose of data utilization, and information on the scope of the requested data included in the data provision request (S510).

[0118] The mobility data management device (200) identifies the requested mobility data specified by the data provision request and can retrieve the requested mobility data and corresponding label information from the mobility data storage (210) (S520).

[0119] If the queried label information exists, the mobility data management device (200) can derive data provision conditions applied to the requested mobility data based on the label attribute information (S530). Here, the label attribute information may include at least one of a security grade, data disclosure scope, data provision permission period, subject eligible for data provision, purpose of data utilization, and label activation status.

[0120] The mobility data management device (200) can determine the suitability of providing the requested mobility data by comparing the derived data provision conditions with the request subject information, data utilization purpose information, and request data range information included in the data provision request (S540).

[0121] When it is determined that data can be provided, the mobility data management device (200) can determine the range of mobility data that can be provided or applicable provision conditions (S550).

[0122] On the other hand, if it is determined that data provision is restricted, the reason for the restriction on data provision can be determined (S560).

[0123] The mobility data management device (200) can generate a data provision response based on a judgment result, and the data provision response may include at least one of a response code indicating the processing result of a data provision request, information on available data, and information on the reason for restriction on provision (S570).

[0124] FIG. 6 is a flowchart illustrating a data provision and result notification procedure performed by a label-based mobility data management device according to one embodiment of the present disclosure.

[0125] Referring to FIG. 6, the mobility data management device (200) can perform the provision of requested mobility data and the notification of the result of the data provision processing based on the result of the determination of suitability for data provision.

[0126] The mobility data management device (200) can configure mobility data to be provided based on the result of determining the suitability of data provision (S610). For example, if the mobility data management device (200) determines that data provision is possible, it can generate mobility data to be provided consisting of all data or part data based on the disclosure range conditions defined by the requested data range and label information. If the mobility data management device (200) determines that data provision is restricted or denied, it may not configure mobility data to be provided or may limit the range of data that can be provided.

[0127] The mobility data management device (200) can generate a data provision response based on the result of determining the suitability of data provision (S620). The data provision response may include a response code indicating the processing result of a data provision request, information on available mobility data, information on data provision conditions, or information on the reason for restricting data provision.

[0128] The mobility data management device (200) can transmit the result of performing the provision of the requested mobility data by transmitting the generated data provision response to a third-party system (400) (S630).

[0129] Additionally, the mobility data management device (200) may notify the user terminal (300) of information regarding the occurrence of a data provision request or the result of processing the data provision (S640). For example, the user terminal (300) may be provided with a notification message that includes information on the subject of the data provision request, the range of the requested data, whether the data provision is approved, the time of data provision, or the reason for the restriction on data provision.

[0130] Through such data provision and result notification procedures, the transparency and accountability of the data provision process can be enhanced.

[0131] FIG. 7 is a block diagram of an exemplary computing device that can be used to implement a device for performing a method according to an embodiment of the present disclosure.

[0132] Referring to FIG. 7, the computing device (70) may include some or all of a memory (700), a processor (720), a storage (740), an input / output interface (760), and a communication interface (780). The computing device (70) may be a stationary computing device such as a desktop computer, a server, etc., as well as a mobile computing device such as a laptop computer, a smartphone, an automotive electronic device, etc.

[0133] The computing device (70) may be implemented as an electronic device constituting a mobility data management device (200), a user terminal (300), or a mobility device (100), and may be implemented in various forms such as a cloud server device, a data processing server, an in-vehicle electronic control unit (ECU), a telematics control unit (TCU), or a personal electronic terminal device. The computing device (70) may be configured to perform mobility data management-related processing, such as collecting mobility data, verifying data consistency or preprocessing, generating or updating label information, determining data provision suitability, generating a data provision response, notifying the result of data provision processing, and processing data management policies.

[0134] Memory (700) may store a program that enables the processor (720) to perform a method or operation according to various embodiments of the present disclosure. For example, the program may include a plurality of instructions executable by the processor (720), and at least some of the methods according to the present disclosure may be performed by executing the plurality of instructions by the processor (720). Memory (700) may be composed of a single memory or a plurality of memories. In this case, information required to perform a method or operation according to various embodiments of the present disclosure may be stored in a single memory or distributed and stored in a plurality of memories. Memory (700) may include at least one of volatile memory and non-volatile memory. For example, volatile memory may include Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), and non-volatile memory may include flash memory.

[0135] The processor (720) may include at least one core and execute instructions stored in memory (700). The processor (720) may be composed of a single processor or multiple processors and may be configured to perform data analysis operations, policy judgment operations, label attribute processing operations, or data provision condition comparison operations.

[0136] Storage (740) includes a storage medium capable of retaining stored data even if the power supplied to the computing device (70) is cut off. For example, storage (740) may include non-volatile memory, magnetic tape, optical disc, magnetic disc, or network-based storage device, etc. A program stored in storage (740) may be loaded into memory (700) before being executed by the processor (720). Storage (740) may store a file written in a programming language, and a program generated from the file by a compiler, etc., may be loaded into memory (700). Storage (740) may store data to be processed by the processor (720) and / or data processed by the processor (720). Storage (740) may be configured to store mobility data, label information, data provision request information, data provision processing result information, data management policy information, or data provision history information.

[0137] The input / output interface (760) may include input devices such as a keyboard, mouse, touch display, microphone, etc., and output devices such as a display, speaker, etc. Through the input / output interface (760), the user can trigger the execution of a program by the processor (720) and / or check the processing results of the processor (720).

[0138] The communication interface (780) can provide access to internal and external networks. The communication interface (780) can support cellular communication, wireless LAN, Bluetooth, or telematics communication. The computing device (70) can communicate with other devices through the communication interface (780).

[0139] Each component of the device or method according to the present invention may be implemented in hardware or software, or in a combination of hardware and software. Additionally, the function of each component may be implemented in software, and a microprocessor may be implemented to execute the function of the software corresponding to each component.

[0140] Various embodiments of the systems and techniques described herein may be realized as digital electronic circuits, integrated circuits, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include being implemented as one or more computer programs executable on a programmable system. A programmable system comprises a storage system, at least one input device, and at least one programmable processor (which may be a special-purpose processor or a general-purpose processor) coupled to receive data and instructions from and transmit data and instructions to at least one output device. Computer programs (which are also known as programs, software, software applications, or code) include instructions for the programmable processor and are stored on a "computer-readable recording medium."

[0141] Computer-readable recording media include all types of recording devices in which data that can be read by a computer system is stored. Such computer-readable recording media may be non-volatile or non-transitory media such as ROM, CD-ROM, magnetic tape, floppy disk, memory card, hard disk, magneto-optical disk, and storage device, and may also include transitory media such as data transmission media. Additionally, computer-readable recording media may be distributed across networked computer systems, and computer-readable code may be stored and executed in a distributed manner.

[0142] Although the flowcharts and timing diagrams in this specification describe each process as being executed sequentially, this is merely an illustrative explanation of the technical concept of one embodiment of the present disclosure. In other words, a person skilled in the art to which one embodiment of the present disclosure belongs may modify and adapt the flowcharts and timing diagrams in various ways, such as changing the order described in the flowcharts and timing diagrams or executing one or more of the processes in parallel, without departing from the essential characteristics of one embodiment of the present disclosure; therefore, the flowcharts and timing diagrams are not limited to a chronological order.

[0143] The above description is merely an illustrative explanation of the technical concept of the present embodiment, and a person skilled in the art to which the present embodiment belongs would be able to make various modifications and variations within the scope of the essential characteristics of the present embodiment. Accordingly, the present embodiments are intended to explain, not limit, the technical concept of the present embodiment, and the scope of the technical concept of the present embodiment is not limited by these embodiments. The scope of protection of the present embodiment shall be interpreted by the claims below, and all technical concepts within an equivalent scope shall be interpreted as being included within the scope of rights of the present embodiment.

[0144] CROSS-REFERENCE TO RELATED APPLICATION

[0145] This patent application claims priority to Korean patent application No. 10-2025-0040690 filed on March 28, 2025, the entire contents of which are incorporated into this patent application by reference.

Claims

1. A method performed by a mobility data management device, A process of storing mobility data received from a mobility device; The process of receiving a data provision request from an external system; A process for determining suitability for provision based on label information corresponding to the requested target data included in the above data provision request; and A process of generating a data provision response including information regarding whether to provide and the scope of provision, based on the result of determining the suitability of provision, and transmitting it to the external system. A method including 2. In Paragraph 1, The above data provision request is It includes at least one of information on the requesting entity, identification information on the requested target data, information on the purpose of data utilization, and information on the scope of the requested data, and The above label information It includes at least one attribute information among security level, scope of data disclosure, period for allowing data provision, subject eligible for data provision, purpose of data utilization, and activation status, and The process of determining the suitability of the above provision is A method comprising a process of comparing data provision conditions derived based on label information corresponding to the requested target data with information on the requesting entity, information on the purpose of data utilization, and information on the scope of requested data included in the data provision request.

3. In Paragraph 1, If label information corresponding to the above requested target data does not exist, The process of sending a label setting request to a user terminal; A process of receiving a label setting response from the above user terminal; and A method further comprising the process of generating label information corresponding to the requested target data based on a received label setting response, and storing the generated label information in conjunction with the requested target data.

4. In Paragraph 3, The above label setting request is A method including information or data range information for identifying the above-mentioned request target data.

5. In Paragraph 3, The above label setting response is A method comprising label information including one or more attributes set in correspondence with the above-mentioned request target data.

6. In Paragraph 1, A method further comprising a process of determining at least one of the scope of data provision, conditions of provision, or reasons for restriction of provision based on the result of determining the suitability of provision above.

7. In Paragraph 1, The above data provision response is A method comprising at least one of a response code indicating the result of processing a data provision request, information on available data, and information on the reason for restricting provision.

8. In Paragraph 1, A method further comprising the process of transmitting information regarding the above data provision request and data provision response to a user terminal.

9. In Paragraph 1, A method further comprising the process of querying at predetermined intervals whether label information corresponding to stored mobility data exists, and sending a label setting request to a user terminal for mobility data identified as not having label information.

10. Communication interface; At least one memory for storing instructions; and Includes at least one processor, The above at least one processor executes the above instructions, Stores mobility data received from a mobility device, and Receive a data provision request from an external system, and Determining suitability for provision based on label information corresponding to the requested target data included in the above data provision request, and Based on the result of determining the suitability of the provision above, configured to generate a data provision response including information regarding whether to provide and the scope of provision, and to transmit it to the external system. Mobility data management device.

11. In Paragraph 10, The above data provision request is It includes at least one of information on the requesting entity, identification information on the requested data, information on the purpose of data utilization, and information on the scope of the requested data, and The above label information It includes at least one attribute information among security level, scope of data disclosure, period for allowing data provision, subject eligible for data provision, purpose of data utilization, and activation status, and The above at least one processor A mobility data management device configured to determine suitability for provision by comparing data provision conditions derived based on label information corresponding to the requested target data with information on the requesting entity, information on the purpose of data utilization, and information on the scope of requested data included in the data provision request.

12. In Paragraph 10, The above at least one processor If label information corresponding to the above requested target data does not exist, Send a label setting request to the user terminal, and Receive a label setting response from the above user terminal, and Based on the received label setting response, label information corresponding to the requested target data is generated, and A mobility data management device configured to store generated label information in conjunction with the requested target data.

13. In Paragraph 12, The above at least one processor A mobility data management device configured to transmit a label setting request to the above user terminal, the requesting data including information or data range information for identifying the requested target data.

14. In Paragraph 12, The above at least one processor A mobility data management device configured to receive a label setting response from the above user terminal, the label information including one or more attributes set in correspondence with the requested target data.

15. In Paragraph 10, The above at least one processor A mobility data management device configured to determine at least one of the scope of data provision, conditions of provision, or reasons for restriction of provision based on the result of determining the suitability of provision above.

16. In Paragraph 10, The above at least one processor A mobility data management device configured to generate a data provision response comprising at least one of a response code indicating the result of processing a data provision request, information on available data, and information on the reason for restricting provision.

17. In Paragraph 10, The above at least one processor A mobility data management device configured to transmit information regarding the above data provision request and data provision response to a user terminal.

18. In Paragraph 10, The above at least one processor Check for the existence of label information corresponding to the stored mobility data at preset intervals, and A mobility data management device configured to send a label setting request to a user terminal for mobility data identified as having no label information.

Images