Server and method for providing connected services

Abstract

To provide a connected service that by enabling communication between a vehicle video imaging device and a user terminal device, provides a user of the user terminal device with various types of significant information on a vehicle and enables control of operation of the vehicle video imaging device on the basis of various types of control commands input received from the user.SOLUTION: A connected service system 100 includes the steps of: storing service subscription information including information on a subscriber subscribing to a service and device information on the subscriber; receiving a terminal registration request from a vehicle video imaging device; comparing identification information corresponding to the terminal registration request with already stored service subscription information to determine validity of the terminal registration request; when it is determined that the terminal registration request is valid, registering the vehicle video imaging device as a device having received service provision; and receiving operation data generated in an operation process of the registered vehicle video imaging device to store the received operation data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a vehicle video capture device, a server, a user terminal device, and a method for providing connected services to vehicles by utilizing a wireless communication network, and to a method for providing connected services using these. [Background technology]

[0002] Vehicle video recording devices are devices that record video while a vehicle is running, stopped, or parked, and are extremely useful in identifying the cause of a vehicle accident. For this reason, the number of vehicles equipped with video recording devices has been increasing in recent years.

[0003] Since the images captured by such a vehicle-mounted video recording device include images captured while the vehicle is driving, stopped, and parked, as well as information about the location where the images were captured, the vehicle-mounted video recording device can further enhance driving convenience for the driver and provide the driver with various functions or services that utilize this information. Summary of the Invention [Problem to be solved by the invention]

[0004] The object of the present invention is to realize a connected service that enables communication between a vehicle-mounted video capture device and a user terminal device, thereby providing the user of the user terminal device with various meaningful information about the vehicle and allowing the operation of the vehicle-mounted video capture device to be controlled by receiving various control commands from the user. [Means for solving the problem]

[0005] To achieve the above-mentioned object, a method of providing a connected service by a connected service providing server according to one embodiment of the present invention includes the steps of: storing service subscription information including information of a subscriber who has subscribed to the service and device information of the subscriber; receiving a terminal registration request from a vehicle-mounted video camera; comparing identification information corresponding to the terminal registration request with previously stored service subscription information to determine the validity of the terminal registration request; registering the vehicle-mounted video camera as a device that has received the service if it is determined that the terminal registration request is valid; and receiving operational data generated during the operation of the registered vehicle-mounted video camera and storing the received operational data.

[0006] The operation data may include at least one of event data corresponding to an event that occurred in the vehicle-mounted video camera, video data captured by the vehicle-mounted video camera, and position data of the vehicle-mounted video camera.

[0007] The method may further include the steps of: searching for identification information and / or subscriber identification information of a user terminal device corresponding to the vehicle-mounted video camera that transmitted the operational data based on the stored service subscription information; generating a notification message to be transmitted to the user terminal device based on the searched information; and transmitting the generated notification message to the user terminal device.

[0008] The method may further include, when the user terminal device requests operation data corresponding to the notification message, transmitting the operation data corresponding to the request of the user terminal device to the user terminal device.

[0009] The method may further include the steps of receiving a service request from the user terminal device, searching for subscriber identification information corresponding to the user terminal device that has requested the service based on the stored service subscription information, and detecting the operation data corresponding to the searched subscriber identification information.

[0010] The method may further include the steps of providing the detected type of motion data to the user terminal device, and, when the user terminal device requests the provision of the motion data based on the detected type of motion data, transmitting the motion data corresponding to the request from the user terminal device to the user terminal device.

[0011] The terminal registration request of the vehicle-mounted image camera may include at least one of identification information of the vehicle-mounted image camera and identification information of a communication module provided in the vehicle-mounted image camera.

[0012] The terminal registration request of the user terminal device may include at least one of identification information of the user terminal device and identification information of a user of the user terminal device.

[0013] Meanwhile, a method for providing a connected service for a vehicle-mounted video camera according to one embodiment of the present invention for achieving the above-mentioned object may include the steps of: connecting the vehicle-mounted video camera to a connected service providing server using a wireless communication module; generating event data including event code information and operation mode information of the vehicle-mounted video camera when an event occurs in the vehicle-mounted video camera; and transmitting the generated event data to the connected service providing server via the wireless communication module.

[0014] The event may include a first event including at least one of an impact event while parking, an impact event while driving, and a movement event while parking, and when the first event occurs, the method may further include a step of extracting at least two images from images taken within a predetermined time range of the occurrence of the first event and generating image upload data using the extracted images, and in the transmitting step, the first event data and the image upload data may be transmitted to the connected service providing server via the wireless communication module.

[0015] The image upload data may also include information on the total number of images.

[0016] The event may include a second event including at least one of a parking position image request response event and a live image request response event in response to a request from a user terminal device receiving the connected service, and when the second event occurs, the method may further include a step of extracting an image at a time point corresponding to the second event and generating image upload data, and in the transmitting step, the second event data and the image upload data may be transmitted to the connected service providing server via the wireless communication module.

[0017] Furthermore, the event may include a third event corresponding to an ADAS (Advanced Driving Assistance System) event, and the method may further include a step of generating third event data when the third event occurs, the third event data including the type of the third event, the time when the third event occurred, and the location where the third event occurred.

[0018] The ADAS may include at least two of a forward vehicle departure notification, a forward vehicle rear-end collision notification, and a lane departure notification.

[0019] The method may further include generating data for a terminal registration request of the vehicle-mounted video camera at the time of initial connection of the vehicle-mounted video camera and transmitting the data to the connected service providing server via the wireless communication module; and receiving registration request response data from the connected service providing server in response to the terminal registration request, the registration request response data including at least one of a daily traffic information usage limit, a remaining number of parking position images, a remaining number of live images, and a remaining number of impact images.

[0020] The terminal registration request may be repeated every time the vehicle-mounted image capturing device is powered on.

[0021] Also, the wireless communication module can be NB-IOT or CAT-M1.

[0022] In the generating step, the vehicle-mounted video camera may adjust the size of the data to be transmitted to the server, taking into consideration the data communication speed with the connected service providing server, the battery status of the vehicle-mounted video camera, and the size of the storage space allocated to the connected service providing server.

[0023] Meanwhile, to achieve the above-mentioned object, a method for providing a connected service for a user terminal device according to one embodiment of the present invention includes the steps of connecting to a connected service providing server, receiving data transmitted from a vehicle-mounted video camera to the connected service providing server, generating a user interface based on the received data, and displaying the generated user interface, wherein the user interface includes a main user interface, and the main user interface can display at least two of connection status information of the connected vehicle-mounted video camera, the operation mode of the vehicle-mounted video camera, whether or not a vehicle impact event has occurred, and whether or not a vehicle movement event has occurred.

[0024] A vehicle image is displayed in one area of ​​the main user interface, and whether an impact event of the vehicle has occurred and whether a movement event of the vehicle has occurred may be displayed as an icon on the vehicle image.

[0025] In addition, a vehicle image is displayed in one area of ​​the main user interface, and the operation modes of the vehicle image capturing device include a continuous recording mode and a parking recording mode, and the edges of the vehicle image in the continuous recording mode and the parking recording mode may be displayed in different colors to distinguish them from each other.

[0026] The user interface includes a driving information display area that displays the vehicle driver's driving record for a predetermined period of time, the driving record including at least one of sudden deceleration, sudden acceleration, overspeed, front collision warning, and lane departure warning, and the driving information display area can display the driving record by adjusting the size of a graphic according to the number of times each type of driving record occurs.

[0027] The user interface may further include a last parking position user interface, which displays an image of the last parking position, and the image of the last parking position may be an image captured at a predetermined time during a transition period when the vehicle video camera is switched from a continuous recording mode to a parking recording mode by turning off the engine after the vehicle has been parked.

[0028] The user interface includes a last parking position user interface, which displays the user's current position and the vehicle's last parking position on a map, and can connect the user's current position and the vehicle's last parking position with a line to display the relationship between the two positions.

[0029] The user interface may also include an event user interface corresponding to an impact event or a movement event, the event user interface displaying an event image, and the event image may be a motion image generated by combining at least two images taken between a predetermined time before the event occurs and a predetermined time after the event occurs.

[0030] The user interface may include a live user interface that displays a live image, and the live image may be a motion image generated by combining at least two images after a live image request time.

[0031] Additionally, the live user interface may further display information about the remaining number of times the live image can be used.

[0032] Meanwhile, a connected service providing server according to one embodiment of the present invention for achieving the above-mentioned object includes: a storage unit that stores service subscription information including information of subscribers who have subscribed to a service and device information of the subscribers; a communication unit that receives a terminal registration request from a vehicle-mounted video camera; and a control unit that compares identification information corresponding to the terminal registration request with already-stored service subscription information to determine the validity of the terminal registration request, and if it is determined that the terminal registration request is valid, registers the vehicle-mounted video camera as a device that has received a service. When operational data generated during the operation of the registered vehicle-mounted video camera is received via the communication unit, the control unit can control the storage unit to store the received operational data.

[0033] The operation data may include at least one of event data corresponding to an event that occurred in the vehicle-mounted video camera, video data captured by the vehicle-mounted video camera, and position data of the vehicle-mounted video camera.

[0034] In addition, the control unit may search for identification information and / or subscriber identification information of a user terminal device corresponding to the vehicle-mounted video camera that transmitted the operational data based on the stored service subscription information, generate a notification message to be transmitted to the user terminal device based on the searched information, and control the communication unit to transmit the generated notification message to the user terminal device.

[0035] The control unit can control the communication unit to transmit, when the user terminal device requests operational data corresponding to the notification message, the operational data corresponding to the request of the user terminal device to the user terminal device.

[0036] In addition, when a service provision request is received from the user terminal device via the communication unit, the control unit can search for subscriber identification information corresponding to the user terminal device that requested the service provision based on the stored service subscription information, and detect the operation data corresponding to the searched subscriber identification information.

[0037] The control unit then controls the communication unit to provide the detected type of operation data to the user terminal device, and when the user terminal device requests the provision of the operation data based on the detected type of operation data, the control unit can control the communication unit to transmit operation data corresponding to the request from the user terminal device to the user terminal device.

[0038] The terminal registration request of the vehicle-mounted image camera may include at least one of identification information of the vehicle-mounted image camera and identification information of a communication module provided in the vehicle-mounted image camera.

[0039] The terminal registration request of the user terminal device may include at least one of identification information of the user terminal device and identification information of a user of the user terminal device.

[0040] Meanwhile, to achieve the above-mentioned object, a vehicle video camera according to one embodiment of the present invention includes a communication unit that communicates with a connected service providing server, and a control unit that generates event data including event code information and operating mode information of the vehicle video camera when an event occurs in the vehicle video camera, and controls the communication unit to transmit the generated event data to the connected service providing server.

[0041] The event may include a first event including at least one of an impact event while parking, an impact event while driving, and a movement event while parking, and the control unit may extract at least two images from images taken within a predetermined time range of the first event when the first event occurs, generate image upload data using the extracted images, and transmit the first event data and the image upload data to the connected service providing server via the communication unit.

[0042] The image upload data may also include information on the total number of images.

[0043] The event may include a second event including at least one of a parking position image request response event and a live image request response event in response to a request from a user terminal device receiving the connected service, and the control unit may extract an image of a point in time corresponding to the second event when the second event occurs, generate image upload data, and transmit the second event data and the image upload data to the connected service providing server via the communication unit.

[0044] Furthermore, the event may include a third event corresponding to an ADAS (Advanced Driving Assistance System) event, and when the third event occurs, the control unit may generate third event data including the type of the third event, the time when the third event occurred, and the location where the third event occurred.

[0045] The ADAS may include at least two of a forward vehicle departure notification, a forward vehicle rear-end collision notification, and a lane departure notification.

[0046] In addition, the control unit generates data for a terminal registration request of the vehicle-mounted video camera at the time of initial connection of the vehicle-mounted video camera and controls the control unit to transmit the data to the connected service providing server via the communication unit, and the communication unit can receive registration request response data including at least one of a daily traffic information usage limit, a remaining number of parking position images, a remaining number of live images, and a remaining number of impact images from the connected service providing server in response to the terminal registration request.

[0047] The terminal registration request may be repeated every time the vehicle-mounted image capturing device is powered on.

[0048] Also, the communication unit can be NB-IOT or CAT-M1.

[0049] The control unit can adjust the size of data transmitted to the server taking into consideration the data communication speed between the vehicle video camera and the connected service providing server, the battery status of the vehicle video camera, and the size of storage space allocated to the connected service providing server.

[0050] Meanwhile, a user terminal device according to one embodiment of the present invention for achieving the above-mentioned object includes a display unit, a communication unit that connects to a connected service providing server and receives data transmitted from a vehicle-mounted video camera to the connected service providing server, and a control unit that generates a user interface based on the received data and controls the display unit to display the generated user interface, wherein the user interface includes a main user interface that can display at least two of connection status information of the connected vehicle-mounted video camera, the operation mode of the vehicle-mounted video camera, whether or not a vehicle impact event has occurred, and whether or not a vehicle movement event has occurred.

[0051] A vehicle image is displayed in one area of ​​the main user interface, and whether an impact event of the vehicle has occurred and whether a movement event of the vehicle has occurred may be displayed as an icon on the vehicle image.

[0052] In addition, a vehicle image is displayed in one area of ​​the main user interface, and the operation modes of the vehicle image capturing device include a continuous recording mode and a parking recording mode, and the edges of the vehicle image in the continuous recording mode and the parking recording mode may be displayed in different colors to distinguish them from each other.

[0053] The user interface includes a driving information display area that displays the vehicle driver's driving record for a predetermined period of time, the driving record including at least one of sudden deceleration, sudden acceleration, overspeed, front collision warning, and lane departure warning, and the driving information display area can display the driving record by adjusting the size of a graphic according to the number of times each type of driving record occurs.

[0054] The user interface may further include a last parking position user interface, which displays an image of the last parking position, and the image of the last parking position may be an image captured at a predetermined time during a transition period when the vehicle video camera is switched from a continuous recording mode to a parking recording mode by turning off the engine after the vehicle has been parked.

[0055] The user interface includes a last parking position user interface, which displays the user's current position and the vehicle's last parking position on a map, and can display the relationship between the user's current position and the vehicle's last parking position by connecting them with a line.

[0056] The user interface may also include an event user interface corresponding to an impact event or a movement event, the event user interface displaying an event image, and the event image may be a motion image generated by combining at least two images taken between a predetermined time before the event occurs and a predetermined time after the event occurs.

[0057] The user interface may include a live user interface that displays a live image, and the live image may be a motion image generated by combining at least two images after a live image request time.

[0058] Additionally, the live user interface may further display information about the remaining number of times the live image can be used.

[0059] Meanwhile, in order to achieve the above object, a computer-readable recording medium according to an embodiment of the present invention may have program code recorded thereon for executing the above-described method for providing a connected service.

[0060] Furthermore, a computer program according to an embodiment of the present invention for achieving the above object may include program code for executing the above-described method for providing a connected service. [Effects of the Invention]

[0061] According to an embodiment of the present invention, various meaningful information about a vehicle can be provided to a user of the user terminal device by providing information generated by the vehicle video camera to a server and a user terminal device via a wireless communication network. For example, various data collected by the vehicle video camera, such as video, parking location, parking time, whether or not an impact / movement event was detected, and ADAS driving record, can be exchanged with the server and the user terminal device via the wireless communication network, enabling a connected service connected between the vehicle, the vehicle video camera, and the server, thereby improving convenience for users of the vehicle and the vehicle video camera.

[0062] Furthermore, according to one embodiment of the present invention, a connected service that provides various meaningful information about a vehicle to a user of a user terminal device can be realized by applying low-power wide-area communication-based Internet of Things (IoT) technology to a vehicle video capture device. For example, the low-power wide-area communication device can expand the range of more advanced functions in terms of transmission speed, transmission volume, power efficiency, etc., and can apply a handover function that enables continuous monitoring of the vehicle not only when parked but also when driving.

[0063] Furthermore, the present invention can provide an interworking protocol between a low-power wide-area communication device and a server for connected services.

[0064] On the other hand, the effects obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present invention pertains from the following description. [Brief explanation of the drawings]

[0065] [Figure 1] 1 is a block diagram showing a connected service system according to an embodiment of the present invention. [Figure 2] 1 is a block diagram showing a vehicle-mounted video imaging device according to an embodiment of the present invention; [Figure 3] FIG. 2 is a block diagram illustrating a user terminal device according to an embodiment of the present invention. [Figure 4] FIG. 2 is a block diagram showing a connected service providing server according to an embodiment of the present invention. [Figure 5] FIG. 2 is a timing diagram illustrating the operation scenario of the connected service system during the black box registration and user registration process according to the present invention. [Figure 6] 2 is a timing diagram illustrating an operation scenario of a connected service system during an event registration process according to an embodiment of the present invention. [Figure 7] FIG. 2 is a timing diagram illustrating an operation scenario of a connected service system when uploading an image from a black box according to an embodiment of the present invention. [Figure 8] 1 is a timing diagram illustrating an operation scenario of a connected service system when an image is requested by a user terminal device according to an embodiment of the present invention. [Figure 9] FIG. 2 is a timing diagram illustrating an operation scenario of a connected service system when a power-off request is made in a black box according to an embodiment of the present invention. [Figure 10] 1 is a timing diagram illustrating an operation scenario of a connected service system when a black box is powered off in response to a request from a user terminal device according to an embodiment of the present invention. [Figure 11] 10 is a timing diagram illustrating a motion image registration process according to an embodiment of the present invention. [Figure 12] FIG. 2 illustrates a main user interface according to one embodiment of the present invention. [Figure 13] 10A and 10B are user interface diagrams illustrating a process of refreshing a main user interface according to an embodiment of the present invention. [Figure 14] 10 is a user interface diagram illustrating a black box registration process using a main user interface according to an embodiment of the present invention. [Figure 15] FIG. 10 illustrates a last park position user interface according to one embodiment of the present invention. [Figure 16] FIG. 10 illustrates a user interface displaying a user's current location and last parked location according to an embodiment of the present invention. [Figure 17] 10 is a user interface diagram illustrating a process for sharing an image of a final parking position according to an embodiment of the present invention. [Figure 18] 10 is a user interface diagram illustrating a process for sharing a last parking position according to an embodiment of the present invention. [Figure 19] FIG. 10 is a diagram illustrating a user interface for managing parking history according to an embodiment of the present invention. [Figure 20] FIG. 10 is a diagram illustrating a user interface for managing parking history according to an embodiment of the present invention. [Figure 21] FIG. 10 is a diagram illustrating a user interface for managing parking history according to an embodiment of the present invention. [Figure 22] 10A-10C illustrate user interfaces in a vehicle impact event or vehicle movement event situation according to one embodiment of the present invention. [Figure 23] FIG. 10 is a diagram illustrating a user interface when inputting a live command according to an embodiment of the present invention. [Figure 24] FIG. 10 is a user interface diagram illustrating live history image management according to one embodiment of the present invention. [Figure 25] 10A and 10B are user interface diagrams illustrating a method for converting an image display according to an embodiment of the present invention; [Figure 26] FIG. 10 illustrates an environment setting user interface according to one embodiment of the present invention. [Figure 27]10A and 10B are diagrams illustrating user interfaces showing a coupon usage process according to an embodiment of the present invention. [Figure 28] FIG. 10 illustrates a user interface for directions to a coupon-enabled agency according to one embodiment of the present invention. [Figure 29] 10A and 10B are user interface diagrams illustrating a process for setting an emergency SOS notification according to an embodiment of the present invention. [Figure 30] 10A and 10B are user interface diagrams illustrating a process for registering an emergency SOS contact in accordance with an embodiment of the present invention. [Figure 31] FIG. 1 is a user interface diagram illustrating a processing scenario when an emergency situation occurs according to an embodiment of the present invention. [Figure 32] FIG. 1 illustrates an example of a push notification according to an embodiment of the present invention. [Figure 33] 10 illustrates a user interface for requesting remote playback in a continuous recording mode of a black box according to an embodiment of the present invention. [Figure 34] 10A and 10B are diagrams illustrating a remote playback scenario in a continuous recording mode of a black box according to an embodiment of the present invention. [Figure 35] 10 illustrates an operational scenario of a black box when a request for additional playback is received during video playback according to an embodiment of the present invention. [Figure 36] 10 illustrates a user interface for requesting remote playback in a parking mode state of a black box according to an embodiment of the present invention. [Figure 37] 1 is a diagram illustrating an operation scenario of a black box when the black box is switched from a parking mode state to a constant mode according to an embodiment of the present invention. FIG. [Figure 38] FIG. 2 is a block diagram showing a connected service providing server according to an embodiment of the present invention. [Figure 39] FIG. 10 illustrates a user interface for selecting a wireless communication network in a black box according to an embodiment of the present invention. [Figure 40]FIG. 2 is a timing diagram illustrating a method for providing connected services according to an embodiment of the present invention. [Figure 41] FIG. 10 is a timing diagram illustrating a method for providing a connected service according to another embodiment of the present invention. [Figure 42] 10 is a timing diagram illustrating a communication connection process between a user terminal device and a black box according to an embodiment of the present invention. [Figure 43] FIG. 10 is a diagram illustrating a main user interface of a user terminal device according to another embodiment of the present invention. [Figure 44] 10 is a user interface diagram illustrating a service subscriber's account login process according to an embodiment of the present invention; [Figure 45] 10A and 10B are user interface diagrams illustrating a process of displaying the location of a vehicle according to an embodiment of the present invention. [Figure 46] 10 is a diagram illustrating a process of setting whether or not to notify geofencing according to an embodiment of the present invention. [Figure 47] 10 is a user interface diagram illustrating a process for setting a geofencing area according to an embodiment of the present invention. [Figure 48] 10A and 10B are user interface diagrams illustrating a process for setting a strong impact notification while the vehicle is moving according to an embodiment of the present invention. [Figure 49] 10A and 10B are user interface diagrams illustrating a process for setting an impact notification while the vehicle is parked according to an embodiment of the present invention. [Figure 50] 10A and 10B are user interface diagrams illustrating a process for setting a strong impact notification while the vehicle is parked according to an embodiment of the present invention. [Figure 51] 10A and 10B are diagrams illustrating a process of checking an impact image according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0066] The following merely exemplifies the principles of the present invention. Thus, those skilled in the art will be able to embody the principles of the present invention and invent various devices encompassed within the concept and scope of the present invention, even if not explicitly described or illustrated herein. Furthermore, it should be understood that all conditional terms and embodiments listed herein are expressly intended solely for the purpose of understanding the concept of the present invention, and are not limited by the embodiments and conditions specifically listed in this specification.

[0067] Moreover, all detailed descriptions reciting specific embodiments, as well as principles, aspects, and embodiments of the present invention, should be understood to be intended to encompass both structural and functional equivalents of such items, and such equivalents should be understood to include not only currently known equivalents but also equivalents developed in the future, i.e., all elements invented that perform the same function, regardless of structure.

[0068] Thus, for example, block diagrams herein should be understood to represent conceptual views of illustrative circuitry embodying the principles of the invention. Similarly, all flowcharts, state transition diagrams, pseudocode, and the like, may be substantially represented on a computer-readable medium and should be understood to represent various processes performed by a computer or processor, whether or not a computer or processor is explicitly illustrated.

[0069] The functions of the various elements illustrated in the figures, including functional blocks represented as processors or similar concepts, may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a processor, the functions may be provided by a single dedicated processor, a single shared processor, or a plurality of individual processors, some of which may be shared.

[0070] Additionally, the explicit use of terms such as processor, control, or similar concepts should not be construed as exclusively referring to hardware capable of executing software, but should be understood to implicitly include, without limitation, digital signal processor (DSP) hardware, ROM, RAM, and non-volatile memory for storing software. Other commonly known and commonly used hardware may also be included.

[0071] In the claims of this specification, elements expressed as means for performing a function described in the detailed description are intended to include any method for performing that function, including, for example, a combination of circuit elements that perform that function, or any form of software, including firmware / microcode, combined with appropriate circuitry for executing the software to perform that function. The invention defined by such claims is such that the functionality provided by the various recited means is combined and combined in the manner required by the claims, and therefore any means that can provide that functionality should be understood to be equivalent to what is understood from this specification.

[0072] The above-mentioned objects, features, and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, which will enable those skilled in the art to easily implement the technical concept of the present invention. Furthermore, in describing the present invention, if it is determined that a detailed description of known technologies related to the present invention may obscure the gist of the present invention, the detailed description will be omitted.

[0073] Various embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0074] 1 is a block diagram showing a connected service system according to an embodiment of the present invention. Referring to FIG. 1, the connected service system 1000 includes a vehicle-mounted video imaging device 100, a vehicle-mounted communication device 200, a connected service providing server 300, a user terminal device 400, and a base station 500.

[0075] In the present invention, a vehicle is an example of a moving body, and the moving body of the present invention is not limited to a vehicle. The moving body of the present invention may include various objects that can move, such as a vehicle, a person, a bicycle, a ship, a train, etc. For convenience of explanation, the following description will be given using a case where the moving body is a vehicle.

[0076] The base station 500 is a wireless communication device that connects a network and various terminals for wireless communication services, and enables communication between the vehicular video imaging device 100, the vehicular communication device 200, the connected service providing server 300, and the user terminal device 400 that constitute the connected service system 1000 according to the present invention. As an example, the vehicular communication device 200 can be wirelessly connected to a communication network via the base station 500. When the vehicular communication device 200 is connected to the communication network, it can exchange data with other devices connected to the network (e.g., the connected service providing server 300, the user terminal device 400).

[0077] The vehicle video shooting device 100 is installed in a vehicle and can capture video related to the vehicle's driving conditions, such as driving, stopping, parking, etc. (hereinafter, driving, stopping, and parking will be collectively referred to as driving), and store the captured video.

[0078] The vehicle-mounted video camera 100 can be controlled by user control input via the user terminal 400. For example, when a user selects an executable object installed in the user terminal 400, the vehicle-mounted video camera 100 can perform an operation corresponding to an event generated by the user's input to the executable object. Here, the executable object can be a type of application installed in the user terminal 400 that can remotely control the vehicle-mounted video camera 100.

[0079] In this specification, an event is defined as an action that triggers the operation of the vehicle-mounted video camera 100. For example, types of events include impact detection, motion detection, user gesture detection, user touch detection, and receiving a remote control command. Here, the vehicle-mounted video camera 100 may include all or some of a front camera that captures the front of the vehicle, a rear camera that captures the rear, a side camera that captures the left and right sides, a camera that captures the face of the vehicle driver, and an interior camera that captures the interior of the vehicle.

[0080] In this specification, the terms "vehicle infrared camera," "vehicle black box," "car dash cam," or "car video recorder" are other expressions for the vehicle video capture device 100, and may all mean the same thing.

[0081] The vehicular communication device 200 is a device connected to the vehicular video camera 100 to enable communication of the vehicular video camera 100, and the vehicular video camera 100 can communicate with an external server via the vehicular communication device 200. The vehicular communication device 200 can use various wireless communication connection methods, such as cellular mobile communication such as LTE (Long Term Evolution) and Wireless LAN (Local Area Network) such as WiFi (Wireless Fidelity).

[0082] According to an embodiment of the present invention, the vehicle communication device 200 that performs wireless communication with the server may be implemented as a communication module using a low-power wide-area (LPWA) technology. Examples of low-power wide-area communication technologies include low-power wideband wireless communication modules such as LoRa (Long Range), NB-IoT (Narrow Band Internet of Things), and Cat M1.

[0083] For convenience of explanation, the following description will be given taking as an example a case where the vehicle communication device 200 is implemented as a communication module using low-power wide-area communication technology. However, this is merely one implementation example of the present invention, and the implementation example of the vehicle communication device 200 is not limited to this. The vehicle communication device 200 of the present invention may be implemented as any communication module capable of communicating with external devices.

[0084] Meanwhile, the vehicle communication device 200 according to the embodiment of the present invention can also perform a location tracking function like a GPS (Global Positioning System) tracker.

[0085] Furthermore, in FIG. 1, the vehicle communication device 200 is described as an external device provided separately from the vehicle video imaging device 100, but this is not limited to this, and the vehicle communication device 200 may be realized as a built-in communication module provided inside the vehicle video imaging device 100.

[0086] In this specification, the term "dongle" may be a different term for a low-power wide-area communication device (or a low-power wide-area communication module) or a vehicle communication device 200, both of which may mean the same thing.

[0087] The connected service providing server 300 relays various data between the vehicle communication device 200 and the user terminal device 400, enabling various connected services to be described later.

[0088] For example, the connected service providing server 300 may receive data including various information generated by the vehicle-mounted video camera 100 from the vehicle-mounted communication device 200, match the received data with user identification information, and store the data. The connected service providing server 300 may then transmit the data generated by the vehicle-mounted video camera 100 to a user corresponding to the user identification information. Here, the user corresponding to the user identification information may refer to a user who has authority over the data.

[0089] In this case, the user terminal device 400 can display a screen that provides various kinds of significant information based on the received data.

[0090] Here, the connected service providing server 300 may include an MQTT server and a TCP server in terms of messaging protocols.

[0091] MQTT (Message Queuing Telemetry Transport) is a lightweight publish / subscribe-based messaging protocol designed for use in low-power, low-bandwidth environments for the Internet of Things (IoT). The MQTT server according to the present invention communicates with the vehicle communication device 200 and the user terminal device 400 using the MQTT protocol, thereby enabling various connected services, which will be described later.

[0092] TCP (Transmission Control Protocol) is a protocol used in the fourth layer, the Transport Layer, of the OSI model, which was developed as a communication standard. The TCP server according to the present invention communicates with the vehicle communication device 200 and the user terminal device 400 using the TCP protocol, thereby enabling various connected services, which will be described later.

[0093] The user terminal device 400 may have installed thereon an application (hereinafter referred to as a "connected service application") that transmits and receives various data to and from the vehicular video camera 100 and / or the vehicular communication device 200 via the connected service providing server 300 and displays the results. This allows the user to execute the connected service application installed in the user terminal device 400, and by executing the application, a guidance screen can be displayed based on various data related to the vehicle's driving conditions received from the vehicular video camera 100. Here, the user terminal device 400 may be implemented as a smartphone, tablet computer, notebook computer, personal digital assistant (PDA), portable multimedia player (PMP), or the like, or may be implemented as a wearable device such as smart glasses or a head-mounted display (HMD) that can be worn on the user's body.

[0094] Here, the user may be a person who has management authority over the vehicle and / or the vehicle-mounted video camera 100, such as the owner of the vehicle, the driver of the vehicle, the owner of the vehicle-mounted video camera 100, or the supervisor of the vehicle-mounted video camera 100.

[0095] Hereinafter, a vehicle-mounted video imaging device, a connected service providing server, and a user terminal device according to an embodiment of the present invention will be described in more detail with reference to the following drawings.

[0096] 2 is a block diagram showing a vehicle-mounted video camera 100 according to an embodiment of the present invention. Referring to FIG. 2, the vehicle-mounted video camera 100 may include a camera unit 110, a user input unit 120, a microphone unit 130, a display unit 140, an audio unit 150, a storage unit 160, an impact detection unit 170, a vehicle driving assistance function unit 180, a communication unit 190, and a control unit 195.

[0097] The image capturing unit 110 may capture a driving image of the vehicle. The driving image of the vehicle may be captured in at least one of the following situations: parking, stopping, and driving, and may include at least one of the front, rear, side, and interior of the vehicle. The image capturing unit 110 may include an infrared camera that can monitor the driver's face or pupils, and the control unit 195 may determine the driver's condition, including whether the driver is drowsy at the wheel, by monitoring the driver's face or pupils using the infrared camera.

[0098] The photographing unit 110 may include a lens unit and an image sensor. The lens unit may focus an optical signal, and the optical signal transmitted through the lens unit reaches an imaging area of ​​the image sensor to form an optical image. The image sensor may be a charge coupled device (CCD), a complementary metal oxide semiconductor image sensor (CIS), or a high-speed image sensor that converts an optical signal into an electrical signal. The photographing unit 110 may further include all or part of a lens unit driver, an aperture, an aperture driver, an image sensor controller, and an image processor.

[0099] The user input unit 120 is configured to receive various user inputs for operating the vehicle-mounted video imaging device 100, and can receive various user inputs, such as user input for setting the operating mode of the vehicle-mounted video imaging device 100, user input for displaying recorded video on the display unit 140, and user input for setting manual recording.

[0100] Here, the operation modes of the vehicle-mounted video shooting device 100 may include a continuous recording mode, an event recording mode, a manual recording mode, and a parking recording mode.

[0101] The continuous recording mode is a mode that is executed when the vehicle engine is started and the vehicle starts to move, and the continuous recording mode can be maintained while the vehicle continues to move. In the continuous recording mode, the vehicular video camera 100 can record video at predetermined time intervals (for example, 1 to 5 minutes). In the present invention, the continuous recording mode and the continuous mode can be used interchangeably.

[0102] The parking recording mode may refer to a mode in which the vehicle operates in a parked state with the vehicle engine turned off or the battery power supply for driving the vehicle interrupted. In the parking recording mode, the vehicular video camera 100 may record a certain period from a predetermined time before the occurrence of an impact event to a predetermined time after the occurrence of the impact event (for example, recording from 10 seconds before to 10 seconds after the event occurrence). In the present invention, the parking recording mode and the parking mode may be used interchangeably.

[0103] The event recording mode may refer to a mode that is activated when an impact event is detected by the impact detection unit 170 while the vehicle is running, or when an ADAS (Advanced Driving Assistance System) event is detected by the vehicle driving assistance function unit 180. In the event recording mode, the vehicular video imaging device 100 can record from a predetermined time before the event occurs to a predetermined time after the event occurs (for example, recording from 10 seconds before to 10 seconds after the event occurs).

[0104] The manual recording mode may refer to a mode that is activated by a user's manual recording input. In the manual recording mode, the vehicle-mounted video camera 100 can record from a predetermined time before to a predetermined time after the user's manual recording request (for example, recording from 10 seconds before to 10 seconds after an event occurs).

[0105] Here, the user input unit 120 may be configured in various ways capable of receiving user input, such as a keypad, a dome switch, a touchpad, a jog wheel, or a jog switch.

[0106] The microphone unit 130 can receive sounds generated inside or outside the vehicle, voices generated by the user, etc. Here, the received voices and sounds may be sounds caused by external impacts or may be related to the situation inside / outside the vehicle, and together with the video captured by the camera unit 110, can help recognize the situation at the time.

[0107] The display unit 140 can display various information processed by the vehicle-mounted video camera 100. For example, the display unit can display a "live view video" that is a video captured in real time by the camera unit 110, and can display a setting screen for setting the operation mode of the vehicle-mounted video camera 100.

[0108] The audio unit 150 can output audio data received from an external device or stored in the storage unit 160. Here, the audio unit 150 can be realized as a speaker that outputs audio data.

[0109] The storage unit 160 stores various data and programs necessary for the operation of the vehicle-mounted video imaging device 100. In particular, the storage unit 160 can store driving video captured by the imaging unit 110 and audio data input via the microphone unit 130.

[0110] The storage unit 160 can classify and store the acquired data in different storage areas according to the operation mode of the vehicle-mounted video camera 100 .

[0111] The storage unit 160 may be configured inside the vehicle-mounted video camera 100, may be configured to be detachable via a port provided in the vehicle-mounted video camera 100, or may be located outside the vehicle-mounted video camera 100. If the storage unit 160 is configured inside the vehicle-mounted video camera 100, it may exist in the form of a hard disk drive or flash memory. If the storage unit 160 is configured to be detachable from the vehicle-mounted video camera 100, it may exist in the form of an SD card, Micro SD card, USB memory, etc. If the storage unit 160 is configured outside the vehicle-mounted video camera 100, it may exist in storage space in another device or database server via the communication unit 190.

[0112] The impact detection unit 170 can detect an impact applied to the vehicle or detect when the amount of change in acceleration is equal to or greater than a certain amount. Here, the impact detection unit 170 can include an acceleration sensor, a geomagnetic sensor, etc. to detect the impact or acceleration.

[0113] The vehicle driving assistance function unit 180 can determine, based on the driving video captured by the image capturing unit 110, whether or not the driver of the vehicle needs a driving assistance function.

[0114] As an example, the vehicle driving assistance function unit 180 can detect the departure of a vehicle located ahead of the vehicle based on the driving video captured by the image capturing unit 110, and determine whether a forward vehicle start alarm (FVSA) is required for the driver. When a predetermined time has elapsed since the forward vehicle departed, the vehicle driving assistance function unit 180 can determine that a forward vehicle start alarm is required.

[0115] Furthermore, the vehicle driving assistance function unit 180 can detect whether or not there is a traffic light change based on the driving video captured by the imaging unit 110, and determine whether or not a traffic light change notification (TLCA: Traffic Light Change Alarm) is required for the driver. As an example, if the traffic light changes from a stop signal to a straight-through signal and the vehicle remains stopped (0 km / h) for four seconds, the vehicle driving assistance function unit 180 can determine that a traffic light change notification is required.

[0116] Furthermore, the vehicle driving assistance function unit 180 can detect whether the vehicle has departed from its lane based on the driving video captured by the image capturing unit 110, and determine whether a lane departure warning system (LDWS) is required for the driver. As an example, when the vehicle departs from its lane, the vehicle driving assistance function unit 180 can determine that a lane departure warning is required.

[0117] Furthermore, the vehicle driving assistance function unit 180 can detect a risk of collision with a vehicle ahead of the vehicle based on the driving video captured by the imaging unit 110, and determine whether a forward collision warning system (FCWS) is required for the driver. As an example, when an initial risk of a front collision is detected, the vehicle driving assistance function unit 180 can determine that a primary forward collision warning is required, and when the distance between the vehicle ahead is further reduced after detecting the initial risk of a front collision, the vehicle driving assistance function unit 180 can determine that a secondary forward collision warning is required.

[0118] Here, the forward collision warning may further include an urban forward collision warning (uFCWS) that provides forward collision warning at lower driving speeds so as to be suitable for environments where driving speeds are low.

[0119] The communication unit 190 enables the vehicular video camera 100 to communicate with other devices. Here, the communication unit 190 may be implemented by the low-power wide-area communication device 200 described above. Therefore, the vehicular video camera 100 can communicate with the connected service providing server 300 and / or the user terminal device 400 via the communication unit 190. Alternatively, the communication unit 190 may be directly connected to the user terminal device 400, such as via WiFi Direct.

[0120] For convenience of explanation, the following description will be given taking as an example a case where the communication unit 190 is provided separately as a vehicle communication device 200.

[0121] The control unit 195 controls the overall operation of the vehicle video imaging device 100. Specifically, the control unit 195 can control all or some of the imaging unit 110, the user input unit 120, the microphone unit 130, the display unit 140, the audio unit 150, the storage unit 160, the impact detection unit 170, the vehicle driving assistance function unit 180, and the communication unit 190.

[0122] In particular, the control unit 195 can set the operation mode of the vehicular video camera 100 to one of a continuous recording mode, an event recording mode, a parking recording mode, and a manual recording mode based on at least one of whether the vehicle has started, the measurement result of the vehicle battery voltage, the detection result of the impact detection unit 170, the determination result of the vehicle driving assistance function unit 180, and an operation mode setting value.The control unit 195 can also control the vehicular video camera 100 to stop operation when the vehicle battery voltage drops below a threshold.

[0123] In addition, the control unit 195 can generate the data shown in Figures 5 to 11 based on various collected data. For example, when the impact detection unit 170 detects an impact while the vehicle is parked or in motion, or detects the movement of the vehicle, it can generate impact event data, extract at least two images from images taken within a predetermined time range of the event occurrence, and generate image upload data using the extracted images. Here, the movement of the vehicle can refer to a situation where the vehicle is towed, etc.

[0124] As yet another example, the control unit 195 may generate event data corresponding to a parking position image request response event or a live image request response event in accordance with a request from a user terminal device receiving a connected service, and may extract an image at a time corresponding to the event to generate image upload data.

[0125] As another example, the control unit 195 may generate ADAS event data when the vehicle driving assistance function unit 180 determines that a driving assistance function is necessary. Here, the ADAS event data may include the type of event indicating the type of ADAS, the time when the event occurred, the location where the event occurred, etc.

[0126] As another example, the control unit 195 may control the size of data transmitted to the connected service providing server 300 to be adjusted taking into consideration the data communication speed with the connected service providing server 300, the battery status of the vehicle video camera, the size of the user storage space allocated to the connected service providing server 300, etc.

[0127] Meanwhile, the control unit 195 can transmit the generated data to the connected service providing server 300 via the low-power wide-area communication module. Here, the data transmitted to the connected service providing server 300 can be used when providing the connected service described below.

[0128] 3 is a block diagram illustrating a user terminal device according to an embodiment of the present invention. Referring to FIG. 3, the user terminal device 400 may include all or some of a communication unit 410, a storage unit 420, an input unit 430, an output unit 440, and a control unit 450.

[0129] The communication unit 410 is provided to enable the user terminal device 400 to communicate with other devices. Specifically, the user terminal device 400 can transmit and receive data to and from at least one of the vehicular video imaging device 100, the vehicular communication device 200, and the connected service providing server 300 via the communication unit 410.

[0130] Here, the communication unit 410 can be realized using various communication methods, such as a form of connection via a wireless or wired method via a local area network (LAN) and the Internet network, a form of connection via a USB (Universal Serial Bus) port, a form of connection via a mobile communication network such as 3G or 4G, or a form of connection via a wireless local area network method such as NFC (Near Field Communication), RFID (Radio Frequency Identification), Wi-Fi, etc.

[0131] The storage unit 420 functions to store various data and applications necessary for the operation of the user terminal device 400. In particular, the storage unit 420 may store a 'connected service application' according to an embodiment of the present invention.

[0132] Here, the storage unit 420 may be realized by a built-in storage element such as a RAM (Random Access Memory), flash memory, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electronically Erasable and Programmable ROM), register, hard disk, removable disk, memory card, USIM (Universal Subscriber Identity Module), etc., as well as a removable storage element such as a USB memory.

[0133] The input unit 430 functions to convert a physical input from outside the user terminal device 400 into a specific electrical signal. Here, the input unit 430 may include all or part of a user input unit and a microphone unit.

[0134] The user input unit may receive user input such as a touch, gesture, or push operation. Here, the user input unit may be implemented in the form of various buttons, a touch sensor that receives touch input, a proximity sensor that receives approaching motion, etc. The microphone unit may receive the user's voice and sounds generated inside or outside the vehicle.

[0135] The output unit 440 is configured to output data from the user terminal device 400 , and may include a display unit 441 and an audio output unit 443 .

[0136] The display unit 441 can output data that can be visually recognized by a user of the user terminal device 400. In particular, the display unit 441 can display a connected service user interface by executing a 'connected service application' according to an embodiment of the present invention.

[0137] Here, the connected service user interface may include various user interfaces such as a "main user interface that aggregates and displays various information useful to the user," a "last parking location guidance user interface," a "live image display user interface," a "remote video playback user interface," a "coupon service user interface," an "emergency SOS user interface," etc. These various user interfaces will be described later with reference to FIGS. 12 to 37.

[0138] Meanwhile, the audio output unit 443 can output data that can be audibly recognized by the user of the user terminal device 400. Here, the audio output unit 443 can be realized by a speaker that expresses data to be notified to the user of the user terminal device 400 as sound.

[0139] The control unit 450 controls the overall operation of the user terminal device 400. Specifically, the control unit 450 may control all or some of the communication unit 410, the storage unit 420, the input unit 430, and the output unit 440. In particular, when various data is received from the vehicle video camera 100, the vehicle communication device 200, and / or the connected service providing server 300 via the communication unit 410, the control unit 450 may process the received data to generate a user interface and control the display unit 441 to display the generated user interface.

[0140] The controller 450 may execute applications that provide advertisements, internet access, games, video images, etc. In various embodiments, the controller 450 may include one processor core or multiple processor cores. For example, the controller 450 may include a multi-core, such as a dual-core, a quad-core, or a hexa-core. Depending on the embodiment, the controller 450 may further include an internal or external cache memory.

[0141] The control unit 450 can receive commands from other components of the user terminal device 400, interpret the received commands, and perform calculations or process data according to the interpreted commands.

[0142] The control unit 450 may process data or signals generated or generated by an application. For example, the control unit 450 may request commands, data, or signals from the storage unit 420 to execute or control an application. The control unit 450 may record (or store) or update commands, data, or signals in the storage unit 420 to execute or control an application.

[0143] The control unit 450 can interpret and process messages, data, commands, or signals received from the communication unit 410, the storage unit 420, the input unit 430, and the output unit 440. The control unit 450 can also generate new messages, data, commands, or signals based on the received messages, data, commands, or signals. The control unit 450 can provide the processed or generated messages, data, commands, or signals to the communication unit 410, the storage unit 420, the input unit 430, the output unit 440, etc.

[0144] All or part of the control unit 450 may be electrically or functionally coupled with or connected to other components within the user terminal device 400 (e.g., the communication unit 410, the storage unit 420, the input unit 430, and the output unit 440).

[0145] Depending on the embodiment, the control unit 450 may be configured with one or more processors. For example, the control unit 450 may include an application processor (AP) that controls a higher layer program such as an application program, or a communication processor (CP) that controls communication.

[0146] Meanwhile, the input unit 430 may receive instructions, interactions, or data from a user. The input unit 430 may detect touch or hovering input from a finger or pen. The input unit 430 may detect input caused by a rotatable structure or a physical button. The input unit 430 may include sensors for detecting various inputs. The input received by the input unit 430 may be of various types. For example, the input received by the input unit 430 may include touch and release, drag and drop, long touch, force touch, physical depression, etc. The input unit 430 may provide the received input and data related to the received input to the control unit 450. In various embodiments, although not shown in FIG. 3 , the input unit 430 may include a microphone (or transducer) capable of receiving a user's voice command. In various embodiments, although not shown in FIG. 3, the input unit 430 may include an image sensor or a camera capable of receiving the user's motion.

[0147] Meanwhile, the display unit 441 may output content, data, or signals. In various embodiments, the display unit 441 may display a video signal processed by the control unit 450. For example, the display unit 441 may display a capture or still image. As another example, the display unit 441 may display a moving image or a camera preview image. As yet another example, the display unit 441 may display a graphical user interface (GUI) for a user to interact with the terminal device 400.

[0148] The display unit 441 may be configured with an LCD (liquid crystal display) or an OLED (organic light emitting diode).

[0149] According to an embodiment, the display unit 441 may be configured with an integrated touch screen by being combined with a sensor capable of receiving touch inputs, etc.

[0150] In various embodiments, the control unit 450 may map at least one function to the input unit 430 such that the input unit 430 has at least one function among a plurality of functions that the user terminal device 400 can provide to the user. For example, the at least one function may include at least one of an application execution function, a vehicle's last parked position display function, a parking position guidance function, a my driving record notification function, a live view viewing function for viewing real-time captured video of the black box 100, a black box 100 power on / off control function, a vehicle power on / off function, a weather-related function, a driving time guidance function, a fuel efficiency guidance function, a vehicle parking / driving mode guidance function, a vehicle driving information guidance function, an event occurrence guidance function, a current vehicle position inquiry function, a vehicle parking position and parking time guidance function, a parking history guidance function, a driving history guidance function, a video sharing function, an event history function, a remote playback function, and a video viewing function.

[0151] In various embodiments, the input unit 430 can receive the configuration information from the control unit 450. The input unit 430 can display an indication to indicate the function based on the configuration information.

[0152] For example, referring to FIGS. 11 to 36 described below, the input unit 430 can display various indications as visual objects based on the configuration information received from the control unit 450.

[0153] In various embodiments, the control unit 450 may send configuration information to the input unit 430 to indicate the at least one function mapped to the input unit 430. The configuration information may include data for displaying, via the display unit 441, an indication of which of the plurality of functions is provided via the input unit 430. The configuration information may include data for indicating a function selected by the control unit 450 from the plurality of functions.

[0154] 4 is a block diagram illustrating a connected service providing server according to an embodiment of the present invention. Referring to FIG. 4, the connected service providing server 300 may include a communication unit 310, a storage unit 320, and a control unit 330.

[0155] The communication unit 310 is provided to enable the connected service providing server 300 to communicate with other devices. Specifically, the communication unit 310 can transmit and receive data to and from at least one of the vehicular video imaging device 100, the vehicular communication device 200, and the user terminal device 400. Here, the communication unit 310 can be realized by various known communication modules.

[0156] The storage unit 320 may store various data and programs for the operation of the connected service providing server 300. Here, the storage unit 320 may include a service subscription information storage unit 321 and a service operation information storage unit 322.

[0157] Specifically, when a user who desires to receive a connected service subscribes to the service using his / her terminal device 400, the service subscription information storage unit 321 may store service subscription information generated based on the information entered upon subscription. Here, the service subscription information storage unit 321 may store subscriber information of the user who subscribes to the connected service and device information of the subscriber. The subscriber information may include subscriber identification information and subscribed service information.

[0158] The subscription service information is information detailing the services to which the subscriber has subscribed, and may include details of the service subscription, fee system, validity period of the service, data rate, type of service, and the like.

[0159] Subscriber identification information is information that enables each of multiple subscribers to be identified, and may include the subscriber's ID, subscriber's password, subscriber's resident registration number, subscriber's name, subscriber's nickname, subscriber's PIN (Personal Identification Number), etc.

[0160] The subscriber device information may include at least one of identification information of the vehicular video camera 100 and identification information of the vehicular communication device 200 purchased by the subscriber. The identification information of the vehicular video camera 100 is information that enables each of the plurality of vehicular video camera devices to be identified, and may include the model name of the black box, the unique serial number of the black box, etc. The identification information of the vehicular communication device 200 is information that enables each of the plurality of vehicular communication devices to be identified, and may include the model name of the dongle, the telephone number of the dongle, the serial number of the dongle, the serial number of the USIM (Universal Subscriber Identity Module), etc.

[0161] The subscriber device information may further include identification information of the subscriber's terminal device 400. The identification information of the user terminal device 400 may include an International Mobile Subscriber Identity (IMSI), an Integrated Circuit Card ID (ICCID), and an International Mobile Equipment Identity (IMEI), which are unique information assigned by the network to identify the user terminal device 400.

[0162] In this case, the service subscription information storage unit 321 can match and store subscriber information and subscriber device information for each subscriber who has subscribed to the service.

[0163] Meanwhile, when a user who has subscribed to a service receives a connected service based on data generated by the vehicle video imaging device 100, the service operation information storage unit 322 can store various data generated in the operation process of the connected service. As an example, the service operation information storage unit 322 can store various data generated in the operation process of the connected service as shown in Tables 1 to 49 described below.

[0164] For example, when various events occur, such as a vehicle impact detection, a vehicle battery off detection, or a live image request from a user terminal device, the vehicular video camera 100 can generate corresponding event data and transmit it to the server 300 via the vehicular communication device 200. In this case, the service operation information storage unit 322 can match the received event data with service subscription information corresponding to the vehicular video camera 100 and store it.

[0165] Here, the storage unit 320 may be realized by a built-in module of the server 300, or may be realized by a separate database (DB) server.

[0166] Meanwhile, the control unit 330 can control the overall operation of the connected service providing server 300 so that the connected service according to the present invention is provided.

[0167] The operation of the connected service providing server 300 can be divided into a "new subscription process" in which a user newly subscribes to the service, and a "connected service providing process" in which connected services are provided to subscribers who have subscribed to the service.

[0168] In the "new subscription process," when a subscriber requests to subscribe to a service, the control unit 330 may control to start a service subscription procedure, acquire subscriber information who has subscribed to the connected service and device information of the subscriber, classify the acquired information, and store it in the storage unit 320. In this way, the storage unit 320 may build a service subscriber information database.

[0169] In the "connected service providing process," the control unit 330 controls various processes such as a black box / user registration process, an event registration process, and an image registration / upload process, which are shown in Figures 5 to 11, to provide a connected service to the user terminal device 400. As an example of providing such a connected service, the user terminal device 400 may display a user interface that provides various information related to the vehicle, as shown in Figures 12 to 37.

[0170] As an example, when performing the "black box registration process," the control unit 330 receives unique information for identifying the communication device, such as a USIM (Universal Subscriber Identity Module) chip built into the vehicle communication device 200, through communication with the vehicle communication device 200, and compares the unique information with information already stored in the storage unit 320 to confirm the validity of the communication device 200 that has requested registration.

[0171] Similarly, in the "user registration process," when the user terminal 400 connects to the server 300, the control unit 330 acquires user identification information, such as a USIM card, embedded in the user terminal 400, and then compares the acquired user identification information with information already stored in the storage unit 320 to check whether the user terminal 400 has subscribed to a service and the type of service subscribed to. If the user authentication is successful, the control unit 330 can provide various information related to the vehicle video camera 100 in various UX formats based on the authority assigned to the user.

[0172] As another example, when performing the “image registration / upload process,” the control unit 330 receives an image captured from the vehicle-mounted video camera 100, and when the upload of the received image is completed, it can notify the user terminal device 400 that the image upload is complete.

[0173] More specifically, the control unit 330 may notify the user terminal 400 of a message indicating that the received image upload has been completed in the form of a push message, and in this case, the user terminal 400 may display the completion of the image upload to the user in the form of a pop-up message via the display unit. When the user clicks on the displayed pop-up message, the user terminal 400 may download the uploaded image to the server 300 and display it to the user.

[0174] The operation of the connected service system 1000 and the link protocol between the vehicle communication device 200 and the connected service providing server 300 will be described in more detail below with reference to FIGS.

[0175] Here, the black box / user registration process, event registration process, and image registration / upload process shown in Figures 5 to 11 may be processes that are performed after a user subscribes to the connected service according to the present invention by signing up as a member.

[0176] 5 to 11, the black box may refer to the vehicle video imaging device 100, and the dongle may refer to the vehicle communication device 200.

[0177] 5 is a timing diagram showing an operation scenario of a connected service system for black box registration and user registration processes according to the present invention. The black box / user registration process in FIG. 5 is a procedure performed before a connected service is provided to a user who has subscribed to the service, and can be performed every time the black box is powered on. For example, the black box / user registration process can be performed every time the black box is powered on, such as when the vehicle engine is started while the black box is powered off and power is applied to the black box, or when the black box is powered on again after being forcibly shut down.

[0178] Referring to FIG. 5, first, the vehicle 10 applies power to the black box 100 (S11), the black box 100 applies power to the dongle 200 (S12), the dongle 200 transmits an Attach Request to the base station 500 (S13), and the base station 500 transmits an Attach Accept to the dongle 200 (S14).

[0179] Then, when dongle 200 connects to a network via low-power wide-area communication, dongle 200 can receive A-GPS (Assisted GPS) information from base station 500 (S15). Black box 100 can calculate the position of vehicle 10 using the A-GPS information received via dongle 200. In addition, DNS (Domain Name System) queries can be shared between dongle 200 and base station 500 (S16).

[0180] Meanwhile, when the dongle 200 connects to the communication network via the base station 500 through the above process, the black box 100 transmits a terminal registration request including terminal data (AT$BBINFO) to the dongle 200 (S17), the dongle 200 transmits the terminal registration request to the TCP server 302, and the TCP server 302 can transmit a terminal registration response, which is a response to the terminal registration request, to the dongle 200 (S18). Here, the terminal registration request can be a request to register for a service before providing a connected service to the black box 100 and / or dongle 200 that has subscribed to the service.

[0181] Here, the terminal registration request transmitted from the dongle 200 to the TCP server 302 can be configured in a data format as shown in Table 1 below.

[0182] JPEG0007767001000001.jpg168170

[0183] The BBOX Name field in the Contents of Table 1 is a field that includes the model name of the black box, which is a vehicle video capture device, and the version information of the corresponding model, and is described in Table 2 below.

[0184] JPEG0007767001000002.jpg36170

[0185] The terminal registration response transmitted from the TCP server 302 to the dongle 200 may be configured in a data format as shown in Table 3 below.

[0186] JPEG0007767001000003.jpg187170

[0187] The A-GPS URL, A-GPS Port, Traffic Day Pro, Traffic Gather, Traffic Report, Park Img Cnt., Live Img Cnt, Shock Img Cnt, and BBOX Name fields in the Contents section of Table 3 are explained in Table 4 below.

[0188] JPEG0007767001000004.jpg95170

[0189] That is, in consideration of the characteristics of low-power broadband wireless communication and in order to reduce data usage, the response to the terminal registration request at the time of initial connection may include data fields that can manage data usage, such as traffic information daily usage limit (Traffic Day Pro), traffic information collection cycle (Traffic Gather), traffic information transmission cycle (Traffic Report), remaining number of parking images (Park Img Cnt), remaining number of live images (Live Img Cnt), remaining number of shock images (Shock Img Cnt), etc.

[0190] Meanwhile, through the above process, the registration of the black box 100 and / or the dongle 200 can be completed.

[0191] Thereafter, the black box 100 can transmit an MQTT server connection request including the terminal setting data (AT$BBCFG) to the dongle 200 (S19). In this case, the dongle 200 can send and receive a connection request (CONNECT) and a connection response (CONNECT ACK) to and from the MQTT server 301 (S20).

[0192] Here, the connection request (CONNECT) from the dongle 200 to the MQTT server 301 can be configured using a protocol such as that shown in Table 5 below.

[0193] JPEG0007767001000005.jpg213170

[0194] The connection response (CONNECT ACK) transmitted from the MQTT server 301 to the dongle 200 may be configured in accordance with the protocol shown in Table 6 below.

[0195] JPEG0007767001000006.jpg53170

[0196] Thereafter, the vehicle communication device 200 can transmit and receive a subscription request (SUBSCRIBE) and a subscription response (SUBSCRIBE ACK) to and from the MQTT server 301 (S21).

[0197] Here, the subscription request (SUBSCRIBE) transmitted from the dongle 200 to the MQTT server 301 may be configured in accordance with the protocol shown in Table 7 below.

[0198] JPEG0007767001000007.jpg88170

[0199] The subscription response (SUBSCRIBE ACK) transmitted from the MQTT server 301 to the dongle 200 may be configured in accordance with the protocol shown in Table 8 below.

[0200] JPEG0007767001000008.jpg61170

[0201] Thereafter, the vehicle communication device 200 can transmit and receive a publication request (PUBLISH) and a publication response (PUBLISH ACK) to and from the MQTT server 301 (S22).

[0202] Here, the publish request (PUBLISH) transmitted from the dongle 200 to the MQTT server 301 may be configured in accordance with the protocol shown in Table 9 below.

[0203] JPEG0007767001000009.jpg88170

[0204] The publish response (PUBLISH ACK) transmitted from the MQTT server 301 to the dongle 200 may be configured in accordance with the protocol shown in Table 10 below.

[0205] JPEG0007767001000010.jpg53170

[0206] Thereafter, the user terminal device 400 may transmit a user registration and authentication request to the MQTT server 301 (S23), and the dongle 200 may transmit and receive a publication request (PUBLISH) and a publication response (PUBLISH ACK) to and from the MQTT server 301 (S24). Here, the user registration and authentication request may be a procedure for registering and authenticating a user before providing a connected service to the user who has subscribed to the service.

[0207] Then, the dongle 200 can transmit a user registration and authentication request ($BBAUTHREQ) to the black box 100 (S25).

[0208] In this case, the black box 100 transmits a user registration and authentication success response (AT@BBAUTH=1) to the dongle 200 (S26), and the dongle 200 can send and receive a publication request (PUBLISH) and a publication response (PUBLISH ACK) to and from the MQTT server 301 (S27).

[0209] Then, the MQTT server 301 can notify the user terminal device 400 that the user registration and authentication have been successful (S28).

[0210] Here, the protocols for the publication request (PUBLISH) and publication response (PUBLISH ACK) in steps S24 and S27 are as shown in Tables 9 and 10 above.

[0211] Through the process of FIG. 5, the black box 100 and / or the dongle 200 can be registered by powering on the black box, and user registration and authentication can be performed.

[0212] 6 is a timing diagram illustrating an operation scenario of a connected service system during an event registration process according to an embodiment of the present invention. Referring to FIG. 6, first, the black box 100 may notify the dongle 200 of an event registration request including an event occurrence notification and event data ("AT$BBEVT=1") (S31). Here, the event may include various events such as an event that may occur during the vehicle's driving status, an event that may occur during the operation of the black box 100, and an event requested by the user terminal device 400. For example, as shown in Table 15 below, the events according to the present invention may include various events such as an impact event, a black box power-off event, a black box low-voltage occurrence event, and a black box authentication completion event.

[0213] In this case, the vehicle communication device 200 can transmit and receive a publication request (PUBLISH) and a publication response (PUBLISH ACK) for event registration to and from the MQTT server 301 (S32).

[0214] Here, the data format of the MQTT PUBLISH for the publication request (PUBLISH) for event registration is as shown in Tables 11 and 12 below.

[0215] JPEG0007767001000011.jpg212170JPEG0007767001000012.jpg47170

[0216] Table 12 below explains the Time, Latitude / Longitude, Battery / Fuel, Battery Percent, and Auth Number fields from the data format (payload) of the MQTT PUBLISH (Table 11).

[0217] JPEG0007767001000013.jpg119170

[0218] The driving status of the content of Table 11 above can be configured as shown in Table 13 below. In Table 13 below, the continuous mode can be the same as the continuous recording mode, which is one of the operation modes of the black box, and the parking mode can be the same as the parking recording mode, which is one of the operation modes of the black box.

[0219] JPEG0007767001000014.jpg106170

[0220] And, the "DriveX" of the contents of Table 11 can be configured as shown in Table 14 below. Here, OBD (On Board Diagnostics) may refer to a diagnostic standard for checking and controlling the overall operating status of a vehicle.

[0221] JPEG0007767001000015.jpg36170

[0222] The event code of the content in Table 11 can be configured as shown in Table 15 below.

[0223] JPEG0007767001000016.jpg144170

[0224] In the above Table 15, "Normal" indicates that no event has occurred, "Impact" indicates that an impact event has occurred, "Black Box Power OFF" indicates that an event has occurred in which the power to the black box is turned off, "Low Voltage" indicates that an event has occurred in which the voltage value of the black box has dropped below a predetermined value, "Authentication Completed" indicates that an event has occurred in which user authentication has been completed for the user terminal device, "Start ON" indicates that an event has occurred in which the vehicle engine has been turned on, "Start OFF" indicates that an event has occurred in which the vehicle engine has been turned off, and "Parking Location Request Response" indicates that an event has occurred in which a response has been made to a parking location request from the user terminal device.

[0225] The "image request response" refers to the occurrence of a response event to an image request from a user terminal device. Here, the image request from the user terminal device may include an image request at a vehicle parking position, an image request corresponding to a vehicle impact event, or a vehicle movement event.

[0226] "Live image request response" indicates the occurrence of a response event to a live image request from a user terminal device, "dongle update start" indicates the occurrence of an update start event of the dongle 200, "dongle update completion (success)" indicates the occurrence of an update successful completion event of the dongle 200, "dongle update completion (failure)" indicates the occurrence of an update failure completion event of the dongle 200, "shock in normal mode (SOS)" indicates the occurrence of an emergency situation event in which a shock equal to or greater than a preset shock value is detected in normal mode, "normal mode conversion reset" indicates the occurrence of an event in which the black box 100 converts from another mode to the normal mode, and "image count initialization" indicates the occurrence of an event in which the number of images that can be transmitted from the black box 100 is initialized. The update of the dongle 200 according to the embodiment of the present invention can be performed by an OTA (Over The Air) method, and can be performed when the manufacturer of the dongle 200 decides to distribute the latest software for the dongle 200.

[0227] The event division of the contents of Table 11 can be configured as shown in Table 16 below.

[0228] JPEG0007767001000017.jpg116170

[0229] That is, according to the present invention, the black box 100 and / or the dongle 200 can generate event data including time, terminal unique number, driving state, event code, location, driving fuel consumption, etc., and transmit the event data to the server.

[0230] When the MQTT server 301 receives a publish request (PUBLISH) for event registration from the dongle 200, the MQTT server 301 can transmit a publish response (PUBLISH ACK) to the dongle 200.

[0231] Meanwhile, when various commands for controlling the black box 100 are input from the user terminal device 400, the MQTT server 301 can transmit a publish request (PUBLISH) for event registration to the dongle 200, inversely to the above. In this case, the data format of the MQTT PUBLISH ACK as data transmitted from the MQTT server 301 to the dongle 200 is as shown in Table 17 below.

[0232] JPEG0007767001000018.jpg142170

[0233] Among the fields in Table 17, the Time, Tid, and Reserved fields are explained in Table 18 below.

[0234] JPEG0007767001000019.jpg45170

[0235] The external device command code (External Code) of the contents of Table 17 can be configured as shown in Table 19 below.

[0236] JPEG0007767001000020.jpg36170

[0237] The command code of the contents of Table 17 can be configured as shown in Table 20 below.

[0238] JPEG0007767001000021.jpg154170

[0239] The reserved field of the content in Table 17 can be configured as shown in Tables 21 to 25 below according to the value of the command code of the content.

[0240] JPEG0007767001000022.jpg108170

[0241] JPEG0007767001000023.jpg72170

[0242] JPEG0007767001000024.jpg71170

[0243] JPEG0007767001000025.jpg122170

[0244] JPEG0007767001000026.jpg87170

[0245] That is, according to the present invention, the MQTT server 301 can generate event registration request data including various black box control commands such as a black box power off control command, a vehicle location inquiry request, an image request, a live check request, and a motion image request in response to a request from the user terminal device 400, and transmit the generated event registration request data to the dongle 200.

[0246] When the dongle 200 receives a publish request (PUBLISH) for event registration from the MQTT server 301, the dongle 200 can transmit a publish response (PUBLISH ACK) to the MQTT server 301.

[0247] Meanwhile, when an event is registered through the above process, the MQTT server 301 registers the event in the user terminal device 400, and the user terminal device 400 can display the registered event through the display unit (S33).

[0248] 7 is a timing diagram illustrating an operation scenario of a connected service system when uploading an image from a black box according to an embodiment of the present invention. Referring to FIG. 7, first, the black box 100 can transmit an image upload request including image data (AT$BBIMG) to the dongle 200 (S41).

[0249] Then, the dongle 200 can transmit and receive an image registration request and an image registration response, which is a response to the image registration request, to and from the TCP server 302 (S42).

[0250] As an example, the data format of the image registration request transmitted from the dongle 200 to the TCP server 302 is as shown in Table 26 below.

[0251] JPEG0007767001000027.jpg172170

[0252] Among the fields in Table 26, the Tid and Img Chunk Len fields are explained in Table 27 below.

[0253] JPEG0007767001000028.jpg36170

[0254] In an embodiment of the present invention, when the dongle 200 uploads an image to the TCP server 302, the image data to be transmitted is divided into chunks of short time units and transmitted for efficient traffic transmission. In an embodiment of the present invention, a chunk, which is a unit for uploading, refers to a block of image data corresponding to a certain size, a certain number of frames, and a certain number of frames. To this end, the TCP server 302 can schedule the time and bandwidth for uploading images to each dongle 200 connected to the entire network for quality of service (QoS) management of the entire network. For example, the TCP server 302 can perform scheduling taking into account the urgency of the image to be transmitted by the dongle 200, the size of the image, the degree of urgency depending on the type of event that occurred in the vehicle to which the dongle 200 is attached, the available bandwidth of the network, etc. Such scheduling may be performed by the MQTT server 301 instead of the TCP server 302.

[0255] The data format of the response to the image registration request transmitted from the TCP server 302 to the dongle 200 is as shown in Table 28 below.

[0256] JPEG0007767001000029.jpg122170

[0257] That is, the image registration request according to the present invention may include event data such as a time corresponding to the image registration request, a driving status, an event code, and location information. As a result, a user receiving a connected service can check not only the event image but also event-related information on the user terminal device 400. The TCP server 302 according to an embodiment of the present invention may schedule data to be uploaded by the dongle 200 according to field information included in the image registration request message transmitted by the dongle 200.

[0258] In addition, considering that an image is divided and transmitted depending on the amount of data transmitted in low-power wide-area communication, the data format according to the present invention can include information such as an image division criterion, an image completion number, etc.

[0259] Meanwhile, the dongle 200 can then transmit and receive an image upload request and an image upload response to the image upload request with the TCP server 302 (S43).

[0260] As an example, the data format of the image upload request transmitted from the dongle 200 to the TCP server 302 is as shown in Table 29 below.

[0261] JPEG0007767001000030.jpg132170

[0262] The data format of the response to the image upload request transmitted from the TCP server 302 to the dongle 200 is as shown in Table 30 below.

[0263] JPEG0007767001000031.jpg150170

[0264] Here, the image upload request may include an upload image, and the image upload process may be repeated until the image upload is completed.

[0265] Meanwhile, when the image registration is completed, the TCP server 302 notifies the user terminal 400 of the image registration, and the user terminal 400 can display the received image on the display unit (S44).

[0266] The process of step S44 being performed in the user terminal 400 will be described as follows: When the TCP server 302 notifies the user terminal 400 of the completion of the image upload from the dongle 200 in the form of a push message, the user terminal 400 displays the completion of the image upload to the user in the form of a pop-up on the display unit. When the user clicks on the displayed pop-up message, the user terminal 400 downloads the uploaded image to the TCP server 302 and displays it to the user.

[0267] 8 is a timing diagram illustrating an operation scenario of a connected service system when a user terminal device requests an image according to an embodiment of the present invention. Referring to FIG. 8, first, the user terminal device 400 may transmit an image request to the MQTT server 301 (S51). Here, examples of the image request from the user terminal device 400 may include a live image request requesting an image captured in real time by the black box 100, and a parking position image request requesting an image of the parking position of a vehicle.

[0268] Then, the MQTT server 301 can transmit and receive a publication request (PUBLISH) and a publication response (PUBLISH ACK) to and from the dongle 200 (S52). Here, the data format of the publication request (PUBLISH) is as shown in Table 11, and the data format of the publication response (PUBLISH ACK) is as shown in Table 17.

[0269] Then, the dongle 200 transmits an image request ($BBIMGREQ) to the black box 100 (S53), and the black box 100 can transmit a response including an image (AT$BBIMG) to the dongle 200 (S54).

[0270] Then, dongle 200 can send and receive an image registration request and an image registration response, which is a response to the image registration request, to TCP server 302 (S55). Here, the data format of the image registration request is as shown in Table 26. And the data format of the response to the image registration request is as shown in Table 28.

[0271] Thereafter, dongle 200 can transmit and receive an image upload request and an image upload response to the image upload request with TCP server 302 (S56). Here, the data format of the image upload request is as shown in Table 29. And the data format of the response to the image upload request is as shown in Table 30.

[0272] Meanwhile, when the image upload is completed, the TCP server 302 registers the image in the user terminal device 400, and the user terminal device 400 can display the received image through the display unit (S57).

[0273] 9 is a timing diagram illustrating an operation scenario of a connected service system when a power-off request is made in a black box according to an embodiment of the present invention. Referring to FIG. 9, first, the black box 100 can transmit a power-off request (AT$CMNPWDN) of the black box 100 to the dongle 200 (S61).

[0274] Then, the dongle 200 can send and receive a publication request (PUBLISH) and a publication response (PUBLISH ACK) to and from the MQTT server 301 (S62). Here, the data format of the publication request (PUBLISH) is as shown in Table 11, and the data format of the publication response (PUBLISH ACK) is as shown in Table 17.

[0275] Then, the MQTT server 301 registers the power off of the black box 100 in the user terminal device 400, and the user terminal device 400 can display via the display unit that the power of the black box has been turned off (S63).

[0276] Then, the dongle 200 disconnects from the MQTT server 301 (S64), and the dongle 200 transmits a Detach Request to the base station 500, and then can proceed with the detachment procedure with the base station 500 (S65).

[0277] Here, the Disconnect message transmitted from the dongle 200 to the MQTT server 301 may be configured in accordance with the protocol shown in Table 31 below.

[0278] JPEG0007767001000032.jpg50170

[0279] Meanwhile, if the communication connection of the dongle 200 is cut off through the above process, the dongle 200 transmits a power supply cutoff request ($NOSVC) to the black box 100 (S66), and the black box 100 can cut off the power supply to the dongle 200 (S67). Additionally, in step S67, the black box 100 may notify the dongle 200 that the supply of operating power has been cut off.

[0280] 10 is a timing diagram illustrating an operation scenario of a connected service system when the black box is powered off in response to a request from a user terminal device according to an embodiment of the present invention. Referring to FIG. 10, first, the user terminal device 400 may transmit a power-off request for the black box 100 to the MQTT server 301 (S71). Then, the MQTT server 301 may transmit and receive a publication request (PUBLISH) and a publication response (PUBLISH ACK) to and from the vehicle communication device 200 (S72). Here, the data format of the publication request (PUBLISH) is as shown in Table 11, and the data format of the publication response (PUBLISH ACK) is as shown in Table 17.

[0281] Then, dongle 200 transmits a black box power-off request ($BBOFF) to black box 100 (S73), and black box 100 can transmit a power-off response (AT$CMNPWDN) to notify dongle 200 that the power has been turned off (S74).

[0282] Then, the MQTT server 301 and the dongle 200 can send and receive a publication request (PUBLISH) and a publication response (PUBLISH ACK) (S75). Here, the data format of the publication request (PUBLISH) is as shown in Table 11, and the data format of the publication response (PUBLISH ACK) is as shown in Table 17.

[0283] Then, the MQTT server 301 registers the power-off of the black box 100 in the user terminal device 400, and the user terminal device 400 can display the fact that the power of the black box 100 has been turned off via the display unit (S76). At this time, in S76, the MQTT server 301 can notify the user terminal device 400 that the power of the black box 100 has been turned off by a push message, and the user terminal device 400 can display to the user that the power of the black box 100 has been turned off by a pop-up message.

[0284] Then, the dongle 200 can disconnect communication with the MQTT server 301 (S77) and transmit a Detach Request to the base station 500 (S78).

[0285] Then, the dongle 200 transmits a power supply cutoff request ($NOSVC) to the black box 100 (S79), and the black box 100 can cut off the power supply to the dongle 200 (S80).

[0286] Meanwhile, in the above-mentioned FIGS. 5 to 10, the server 300 is divided into the MQTT server 301 and the TCP server 302 from the viewpoint of protocol, and event registration, power off registration, etc. are performed in the MQTT server 301, and image registration and upload are performed in the TCP server 302. However, this is not limited to this, and according to other embodiments of the present invention, the above-mentioned processes may be performed without dividing the servers.

[0287] 11 is a timing diagram illustrating a motion image upload process according to an embodiment of the present invention, where a motion image is generated by combining at least two images rather than a single image to represent the movement of an object within the image, and the image and the motion image may be different from each other.

[0288] Referring to FIG. 11, first, the black box 100 transmits a motion image upload request (AT$BBMIMG) corresponding to a front-view image to the dongle 200 (S101), and the dongle 200 can transmit a motion image registration request to the server 300 (S102).

[0289] Here, the data format of the motion image registration request transmitted from the dongle 200 to the server 300 is as shown in Table 32 below.

[0290] JPEG0007767001000033.jpg228170

[0291] Among the fields in Table 32, the All Override, Img Chunk Len, and Img Count fields are explained in Table 33 below.

[0292] JPEG0007767001000034.jpg40170

[0293] That is, since the motion image according to the present invention is generated by combining multiple images, the registration request for uploading a motion image may further include “total number of images” information compared to the registration request for uploading an image shown in Table 26.

[0294] The event position of the content in Table 32 can be configured as shown in Table 34 below.

[0295] JPEG0007767001000035.jpg54170

[0296] Then, the server 300 may transmit a response to the motion image registration request to the dongle 200 (S103).

[0297] Here, the data format of the response to the motion image registration request transmitted from the server 300 to the dongle 200 is as shown in Table 35 below.

[0298] JPEG0007767001000036.jpg123170

[0299] Among the fields in Table 35, the Img Chunk Len, Img File No, and Img Chunk No fields are explained in Table 36 below.

[0300] JPEG0007767001000037.jpg45170

[0301] That is, the registration request response for motion image upload according to the present invention may further include "image file complete" information compared to the registration request response for image upload listed in Table 28.

[0302] The content code of Table 35 can be configured as shown in Table 37 below.

[0303] JPEG0007767001000038.jpg201170

[0304] Thereafter, the dongle 200 may transmit a motion image upload request to the server 300 (S104). Here, the data format of the motion image upload request transmitted from the dongle 200 to the server 300 is as shown in Table 38 below.

[0305] JPEG0007767001000039.jpg166170

[0306] That is, since the motion image according to the present invention is generated by combining multiple images, the motion image upload request may further include the image file number and information on whether the entire process is complete, compared to the registration request for image upload described in Table 29.

[0307] Then, the server 300 may transmit a response to the motion image upload request to the dongle 200 (S105). Here, the data format of the response to the motion image upload request transmitted from the server 300 to the dongle 200 is as shown in Table 39 below.

[0308] JPEG0007767001000040.jpg115170

[0309] The Image Count field in Table 39 can be used to count the number of times that the dongle 200 can upload images to the server 300 if there is a limit. For example, if the service to which the user subscribes allows only 10 uploads per day (total daily uploads = 10), the server 300 can count the number of images uploaded by the dongle 200 and transmit the remaining number of uploads, calculated by subtracting that number from the total daily uploads, to the dongle 200 via the Image Count field. This allows the black box 100 to display to the user the number of images currently uploaded out of the total daily uploads, or the remaining number of uploads.

[0310] The Image Count field in Table 39 is explained in Table 40 below.

[0311] JPEG0007767001000041.jpg53170

[0312] In this case, steps S104 to S105 may be repeated as many times as the number of photos to be transmitted to the server 300. The photos transmitted to the server 300 may be used to generate a motion image of the area in front of the vehicle.

[0313] Then, when a sufficient number of images required to generate a motion image in front of the vehicle have been uploaded, the server 300 notifies the dongle 200 that the upload of all front photos has been completed (S106), and the dongle 200 can transmit a front motion image upload completion response ($BBMIMG:0) to the black box 100 (S107).

[0314] Then, the black box 100 transmits a motion image upload request (AT$BBMIMG) for the rear-view video to the dongle 200 (S108), and the dongle 200 can transmit a motion image registration request for the rear-view video to the server 300 (S109). The server 300 can then transmit a response to the motion image registration request to the dongle 200 (S110). Here, the data format of the motion image upload request in step S109 is as shown in Table 32, and the response to the motion image registration request in step S110 is as shown in Table 35.

[0315] Thereafter, the dongle 200 may transmit a motion image upload request to the server 300 (S111). Here, the data format of the motion image upload request transmitted from the dongle 200 to the server 300 is as shown in Table 38 above.

[0316] Then, the server 300 can transmit a response to the motion image upload request to the dongle 200 (S112). Here, the data format of the response to the motion image upload request transmitted from the server 300 to the dongle 200 is as shown in Table 39.

[0317] In this case, steps S111 to S112 may be repeated as many times as the number of photos to be transmitted to the server 300. The photos transmitted to the server 300 may be used to generate a motion image behind the vehicle.

[0318] Then, the server 300 notifies the dongle 200 that the upload of all rear photos has been completed (S113), and the dongle 200 can transmit a rear motion image upload completion response ($BBMIMG:0) to the black box 100 (S114).

[0319] 11, only images of the front and rear of a vehicle are shown as examples of images for motion image registration, but the present invention is not limited thereto. For example, images for motion image registration according to the present invention may be images captured in any direction, such as the front, rear, left, or right, of a vehicle, or may be images captured in accordance with a control command received from the user terminal device 400.

[0320] Meanwhile, although not shown in the above figures, the connected service system 1000 according to an embodiment of the present invention may also transmit data to other external devices. In this case, the data format of the other external device interworking request transmitted from the dongle 200 to the server 300 for interworking with the other external device is as shown in Table 41 below.

[0321] JPEG0007767001000042.jpg123170

[0322] The data format of the response to the request for interlocking with another external device transmitted from the server 300 to the dongle 200 is as shown in Table 42 below.

[0323] JPEG0007767001000043.jpg133170

[0324] Although not shown in the above figures, the connected service system 1000 according to an embodiment of the present invention can also transmit ADAS data.

[0325] In addition, the safe driving data version transmission format transmitted from the dongle 200 to the server 300 is as shown in Table 43 below.

[0326] JPEG0007767001000044.jpg97170

[0327] The Safe Guide Ver field in Table 43 is a field containing the safe operation data version. The server 300 can provide the safe operation data of the black box 100 over the air by comparing the safe operation data version of the black box 100 transmitted via the dongle 200 with the latest version of the safe operation data version, and the black box 100 can update the safe operation data received from the server 300 to the latest version of the safe operation data.

[0328] The safe driving data is data for safety guidance required for road driving and route driving guidance, and may include, for example, the creation of new roads, the creation of traffic lights, the setting of specific areas such as school zones, revisions to traffic-related laws and regulations, and information on new speed limit areas.

[0329] Among the fields in Table 43, the Safe Guide Ver. can be used as shown in Table 44 below.

[0330] JPEG0007767001000045.jpg27170

[0331] In Table 44, the Safe Guide Ver field indicates that the safe driving data currently stored in the black box 100 will expire after August 2019. That is, the Safe Guide Ver field can also be set to indicate when the safe driving data stored in the black box 100 will be updated.

[0332] The data format of the safe driving data version transmission response transmitted from the server 300 to the dongle 200 is as shown in Table 45 below.

[0333] JPEG0007767001000046.jpg97170

[0334] Although not shown in the above figures, the connected service system 1000 according to an embodiment of the present invention can transmit and receive traffic information. In this case, the header of the data format for a traffic information request transmitted from the dongle 200 to the server 300 can be configured as shown in Table 46 below.

[0335] JPEG0007767001000047.jpg115170

[0336] Among the fields in Table 46, the Log Version, Function Flag, Device Number, Time Stamp, Latitude, and Longitude fields are explained in Table 47 below.

[0337] JPEG0007767001000048.jpg130170

[0338] The ADAS data format body transmitted from the dongle 200 to the server 300 can be configured as shown in Table 48 below.

[0339] JPEG0007767001000049.jpg115170

[0340] Among the fields in Table 48, the Latitude / Longitude, Time Stamp Diff, HDOP, Course, Speed, and ADAS Event fields are explained in Table 49 below.

[0341] JPEG0007767001000050.jpg122170

[0342] Also, referring to Tables 48 and 49, according to an embodiment of the present invention, the ADAS data message transmitted from dongle 200 to server 300 includes, in the header information of the ADAS data message, difference information between previously generated location information and timestamp and currently generated location information and timestamp, rather than the entire location information and timestamp information, in order to minimize the size of the transmitted message. In other words, if there is previously generated location information and timestamp information for an ADAS data message to be transmitted from dongle 200 to server 300, and a new ADAS data message is generated due to a specific event, dongle 200 transmits only the difference (Latitude diff / Longitude diff) between the previously generated location information and newly generated location information (latitude coordinates, longitude coordinates) and the difference (Time Stamp Diff) between the previously generated timestamp and the newly generated timestamp to server 300, thereby reducing data usage compared to the conventional method.

[0343] In addition, the body of the ADAS data format transmitted from the dongle 200 to the server 300 may include ADAS event information. Here, although only the lane departure warning (LDWS) and forward vehicle collision warning (FCWS, uFCWS) have been described as examples of the ADAS event information, the ADAS event information may further include forward vehicle departure warning (FVSA), traffic light change warning (TLCA), pedestrian detection and collision alarm (PDCA), etc.

[0344] The protocol of the present invention optimizes data compared to existing methods, thereby reducing data usage to suit low-power wide-area communications. That is, according to the present invention, the existing Jason method is changed to a binary method, and data that previously used an average of 200 bytes for all events in the existing header is transmitted as TCP-based raw data, thereby reducing data usage to suit low-power wide-area communications. Table 50 below is a table illustrating the improvement effect of the protocol of the present invention.

[0345] JPEG0007767001000051.jpg121170

[0346] Meanwhile, the connected system 1000 according to an embodiment of the present invention can provide the connected service according to the present invention based on the above-mentioned protocol. The connected service can be provided by executing a connected service application on the user terminal device 400, causing the user terminal device 400 to connect to the server 300, acquire various data stored in the server 300 (e.g., data acquired by the vehicle-mounted video camera 100), and generate and display various user interfaces on the screen based on the acquired data.

[0347] Hereinafter, an example of implementing a connected service according to an embodiment of the present invention will be described in more detail with reference to the following drawings.

[0348] FIG. 12 illustrates a main user interface according to an embodiment of the present invention. Here, the main user interface is an interface displayed when a connected service application according to the present invention is executed for the first time. The interface may be configured by the user terminal device 400 receiving data transmitted from the black box 100 and the dongle 200 to the server 300 through the processes described above with reference to FIGS. 5 to 11. For example, the user terminal device 400 displays executable objects on a display unit in the form of a user experience (UX) to provide information about user content to a user. When a user selects an executable object displayed on the display unit, the user receives and provides data corresponding to the selection from the server 300. For example, if a connected service providing application according to an embodiment of the present invention is installed in the user terminal device 400, the user executes the application when the user inputs an execution command (e.g., click, voice control) for the application. The user terminal device 400 also requests various data selected by the user from the UX screen provided to the user from the server 300, receives the data, and provides the data to the user. In this manner, the user terminal device 400 can display notifications for various events such as information about the remote black box 100, vehicle impact notifications, vehicle movement detection notifications, and images captured by the black box 100.

[0349] 12(a), the main user interface 1101 may display connection status information of the black box 100 connected to the server 300, a vehicle image, and an event notification icon for the vehicle. In this case, the screen of FIG. 12(a) may be displayed after authentication is completed through a user registration procedure of the black box 100 and the user terminal device 400.

[0350] 12, for example, the operation mode of the black box 100 may be visually distinguished by the color of the border of the vehicle image object on the UX screen of the application provided to the user. For example, the color of the border of the vehicle image object may be changed to different colors when the operation mode of the black box 100 is the parking mode and the normal mode. As another example, the user may be able to visually distinguish between each operation mode by using representative text indicating the operation mode of the black box 100. For example, the letter "P" may be displayed on the vehicle image when the operation mode is the parking mode, and the letter "N" may be displayed when the operation mode is the normal mode.

[0351] As another example, the color of the edge of the vehicle image object may indicate the vehicle's safe (positive) / danger (negative) state. For example, in various dangerous situations, such as when an impact occurs to the vehicle, when vehicle movement is detected, or when a danger is detected during an ADAS function, the color of the edge of the vehicle image object may be displayed in red. However, when the vehicle is parked or in a safe state, the color of the edge of the vehicle image object may be displayed in green.

[0352] As another example, when an impact event occurs while the vehicle is parked or running, the application may display an impact notification icon 1103 on the vehicle image as a visual object notifying the occurrence of an impact event on the vehicle, as shown in FIG. 12(b). In this case, the visual object may be modified and displayed depending on the magnitude of the impact value received from the server 300. For example, the icon size may be changed, a different icon may be displayed, or the icon color may be changed. As yet another example, when an impact event occurs while the vehicle is parked or running, the application may indicate the occurrence of the event by vibrating the vehicle image. For example, the magnitude of the vibration of the vehicle image may be adjusted and displayed depending on the degree or frequency of the event. In this case, the vibration of the vehicle image may be displayed by the vehicle image vibrating left and right or up and down, or by a vibration animation.

[0353] As another example, if vehicle movement is detected while the vehicle is parked, a visual object (e.g., an arrow icon 1104) indicating the vehicle movement event may be displayed on the vehicle image as shown in Fig. 12(c). In this case, the direction of vehicle movement may be displayed as a corresponding arrow depending on the direction and / or magnitude of the impact value received from the server 300.

[0354] Meanwhile, the area 1105 of the main user interface 1101 can display information (such as product name) of the black box 100 connected to the smartphone, connection status information of the black box 100, etc. as visual objects.

[0355] Area 1106 of the main user interface 1101 is an area that displays vehicle status information, and can display the current vehicle mode (parking mode / driving mode) information, vehicle battery status information (e.g., current vehicle battery value, driving range), and auxiliary battery information (e.g., remaining battery charge percentage) if an auxiliary battery is installed as visual objects.

[0356] Specifically, area 1106-1 may display the current vehicle mode, for example, continuous mode, parking mode.

[0357] Additionally, area 1106-2 may display vehicle battery status information (eg, the current value of the vehicle battery).

[0358] Additionally, area 1106-3 may display current status information of the black box and / or vehicle, such as vehicle safety, vehicle impact occurrence, vehicle movement detection, need to check black box communication connection status, black box ultra-low power mode, black box communication module update, etc., as visual objects.

[0359] Additionally, area 1106-4 may display driving fuel efficiency information and a corresponding icon. For example, if the vehicle's average fuel efficiency is higher than a preset value, the vehicle's average fuel efficiency and an "ECO" icon may be displayed. When the user selects the "ECO" icon, user terminal device 400 may display a fuel efficiency statistics detail screen.

[0360] Additionally, area 1106-5 may display elapsed parking time information and a corresponding icon. Here, the elapsed parking time may refer to the time difference between when the vehicle was parked and the current time. When the user selects the elapsed parking time icon, user terminal device 400 may display a user interface that displays the last parking position of the vehicle. Here, the user interface that displays the last parking position is as shown in FIGS. 15 to 17.

[0361] If there is no information about the vehicle's last parked location, the user terminal device 400 can display default location information in the area 1106.

[0362] Meanwhile, area 1107 is a live button, and when area 1107 is selected, user terminal device 400 requests real-time captured video from black box 100 via server 300, and can display a user interface that displays video captured in real time by black box 100 received via server 300 in response to the request. Here, the user interface that displays a real-time image is as shown in FIG. 23.

[0363] In addition, an area 1108 is a black box off button, and when the area 1108 is selected, the user terminal device 400 can generate a control signal for powering off the black box 100 and transmit it to the server 300 .

[0364] In addition, area 1109 is a vehicle engine ON / OFF button, and the vehicle engine ON / OFF state can be displayed depending on whether an LED in area 1109 is ON / OFF. When area 1109 is selected, user terminal device 400 can generate a control signal for turning the vehicle engine ON / OFF and transmit it to server 300.

[0365] Area 1110 is a weather information display area, which can display address, weather, and vehicle-related phrases, temperature, and weather icons based on the location of the user terminal device 400. Here, vehicle-related phrases can mean useful phrases related to vehicles based on the current weather, such as "Today is a good day for a car wash."

[0366] Additionally, area 1111 is a my driving information display area, which can display the cumulative driving record for a predetermined period (e.g., the last 7 days). If there is a day during the predetermined period when the vehicle was not driven, my driving information display area 1111 can display the remaining driving information excluding information related to that day. The my driving information displayed in area 1111 visually displays the cumulative driving record of the vehicle, and is therefore also referred to as driving history information, and can be displayed as a visual object (e.g., the size of a circle) that can distinguish the cumulative driving distance for each date.

[0367] Here, the driving information displayed in the area 1111 may include at least one of event information that occurs while the vehicle is driving, such as sudden deceleration, sudden acceleration, overspeed, front collision warning, and lane departure warning. In addition, the driving information displayed for each date in the area 1111 may display a visual object corresponding to the number of events that occurred on the corresponding date. For example, the more events that have occurred, the larger the circle displayed, and the smaller the number of events that have occurred, the smaller the circle displayed.

[0368] The driving information may be displayed in the order of sudden deceleration, sudden acceleration, overspeed, front collision warning, and lane departure warning, and each circle in the area 1111 may be an icon indicating sudden deceleration / sudden acceleration / overspeed / front collision warning / lane departure warning from left to right. Here, different colors may be mapped to the area 1111 for each piece of driving information.

[0369] The date representation in the area 1111 can be provided in chronological order from the left, such as today, yesterday, two days ago, three days ago, four days ago, five days ago, and six days ago.

[0370] If there is no trip information at all, then area 1111 may provide a phrase such as "No trips recorded. Try starting a trip."

[0371] On the other hand, when travel information for a specific date is selected, the user terminal device 400 can display a user interface that displays the travel information for the selected date in detail.

[0372] Meanwhile, in the area 1111, the number of events can be expressed in a total of three sizes as a standard for providing circle sizes according to the driving record. For example, the first number (e.g., 5 times) or more can be displayed as the largest circle, the second number (e.g., between 2 and 4 times) as the medium circle, and the third number (e.g., less than 1 time) as the smallest circle.

[0373] However, the circular display of the driving information in area 1111 is merely one embodiment of the present invention and is not limited thereto. For example, the driving information may be displayed using other polygons such as a rectangle or visual bubbles such as balloons. According to another embodiment of the present invention, the driving record information may be displayed using a bar shape instead of a circle while maintaining the above criteria (e.g., large bar / medium bar / small bar).

[0374] 13 is a user interface diagram showing a process of reloading the main user interface according to an embodiment of the present invention. As shown in (a) of FIG. 13, the user can input an up / down flick operation 1201, which is sliding from top to bottom, on the main user interface.

[0375] In this case, the user terminal device 400 can display an icon 1202 indicating that the main user interface is being refreshed, as shown in FIG. 13(b).

[0376] Then, when the refresh is completed, the user terminal device 400 can update the information displayed on the main user interface to the current information and display it, as shown in FIG. 13(c).

[0377] 14 is a user interface diagram illustrating a black box registration process using a main user interface according to an embodiment of the present invention. As shown in FIG. 14(a), a user can select an area 1301 that displays information about linked black boxes. In this case, the user terminal 400 can display a list 1302 of registered black boxes in a pop-up window as shown in FIG. 14(b), with the currently linked black box "QXD3000" displayed at the top. Here, the pop-up window display can be performed only when there are two or more registered devices.

[0378] If the user selects another device in the black box list 1302 other than the currently connected video camera, the user can connect to the selected device and then close the pop-up window.

[0379] Figure 15 is a diagram illustrating a last parking position user interface according to an embodiment of the present invention. When the parking elapsed time icon 1106-5 shown in Figure 12 is selected, the user terminal device 400 may display a user interface 1401 that displays the vehicle's last parking position on a map, as shown in Figure 15(a). In Figure 15(a), the vehicle's last parking position is displayed on the map in the form of a visual bubble containing a vehicle icon. In addition, the vehicle's parking position, parking time, and parking elapsed time information may be displayed in an upper region 1402 of the user interface 1401.

[0380] 15(b), the user interface 1401 may provide the last parking position and an image of the last parking position 1403. Here, the image of the last parking position 1403 may be an image captured at a predetermined time during the transition period when the black box 100 is transitioned from the normal mode to the parking mode by turning off the engine after the vehicle has been parked.

[0381] The map displayed on the user interface 1401 can receive various touch inputs from the user, such as tapping, dragging, zooming in, zooming out, and rotating.

[0382] Meanwhile, area 1404 is a parking history button, and when area 1404 is selected, a parking history user interface can be displayed, which will be described later with reference to FIG.

[0383] An area 1405 is an image download button, and when the area 1405 is selected, the corresponding image can be stored in the user terminal device 400 .

[0384] Area 1408 is a button that displays the user's current location and the last parked location of the vehicle, and when area 1408 is selected, the user's current location and the last parked location of the vehicle can be displayed on a map. This will be described later with reference to FIG. 16.

[0385] Area 1406 can then be a share button and area 1407 can be a vehicle location button, as will be described below with reference to Figures 17 and 18.

[0386] On the other hand, if there is no last parking position for the vehicle, the user terminal device 400 can display a default position on the user interface 1401. Alternatively, if there are past parking positions but no last parking position, the user terminal device 400 can display the previous parking position on the user interface 1401.

[0387] 16 is a diagram showing a user interface for displaying a user's current location and the vehicle's last parked location according to an embodiment of the present invention. Referring to FIG. 16, when a user selects area 1501, user terminal device 400 displays the user's current location and the vehicle's last parked location on a map. In this case, the user's current location and the vehicle's last parked location can be connected by a straight line (dotted line) to show the relationship between the two locations.

[0388] When displaying a straight line connecting the user's current location and the vehicle's last parked location, the user terminal device 400 can adjust the scale of the map so that the vehicle's last parked location and the user's current location are displayed on one screen.

[0389] 16, the user terminal device 400 may calculate the straight-line distance between the user's current location and the last parking location of the vehicle, as well as the distance via drivable roads, and display the calculated distance on the screen. The user terminal device 400 may also work in conjunction with a navigation application to provide route guidance from the user's current location to the last parking location of the vehicle.

[0390] 17 is a user interface diagram illustrating a process for sharing a final parking position image according to an embodiment of the present invention. When an area 1602 corresponding to a share button is selected in a user interface 1601 as shown in FIG. 17(a), the user terminal device 400 can display a share type selection pop-up window 1603 as shown in FIG. 17(b).

[0391] When the user selects "Share an image of my car" in the sharing type selection pop-up window 1603, the user terminal device 400 can display a shareable image list screen shown in Fig. 17(c). Here, the shareable image list screen can include a front image list 1605 and a rear image list 1606, and the user can select an image that he or she wants to share from the displayed shareable image list screen.

[0392] When the user selects an image to be shared and selects the share button 1607, the user terminal device 400 can display a list of sharable social network services (SNS) or a list of contacts.

[0393] 18 is a user interface diagram showing a process for sharing a last parking location according to an embodiment of the present invention. When a share button 1702 is selected on a user interface 1701 as shown in FIG. 18(a), the user terminal device 400 can display a share type selection pop-up 1703 as shown in FIG. 18(b).

[0394] When the user selects "Share my car's location" in the sharing type selection pop-up 1703, the user terminal device 400 may display a screen for sharing the last parked location of the car, as shown in FIG. 18(c). Here, in FIG. 18(c), the last parked location of the car may be displayed in the center of the map, and the address of the last parked location may be displayed at the top of the screen. In this case, when the user selects "Share" 1705, the user terminal device 400 may display a shareable application list 1706, as shown in FIG. 18(d). Here, the shareable applications are a list of applications installed in the user terminal device 400 that can share location information, and the list 1706 may display icons and application names.

[0395] When the user selects an application from the sharable application list 1706, the user terminal device 400 generates shared information and can share the shared information via the selected application.

[0396] In this case, the shared information displayed when the last parking position is shared is as shown in (e) of Figure 18. That is, the shared information 1707 may include an image of the last parking position of the vehicle displayed on a map and a link URL of the map.

[0397] As an example, if the shared information 1707 is shared via a message, the terminal device of another user can display the shared information via the message, and when another user selects the shared information, the user's last parking location can be displayed on a map.

[0398] Fig. 19 is a diagram showing a user interface for parking history management according to one embodiment of the present invention. Area 1802 displayed in user interface 1801 of Fig. 19(a) is a parking history button, and when a user selects area 1802, user terminal device 400 can display user interface 1803 as shown in Fig. 19(b).

[0399] The user interface 1803 can provide parking location information and parking date and time information in the order of the most recent parking record. In this case, the user interface 1803 does not need to provide the last parking location information displayed on the user interface 1801 as parking history.

[0400] When one parking history is selected in the user interface 1803, a map user interface 1805 may be opened and displayed below the selected parking history, as shown in (c) of Fig. 19. In this case, the map user interface 1805 may display a parking location image corresponding to the selected parking history and the parking location on the map. Here, touch interaction on the map may be applied in the same manner as the map interaction described above.

[0401] 20 is a diagram illustrating a parking history management user interface according to an embodiment of the present invention. Referring to (a) of FIG. 20, when a user inputs a left flick, moving from left to right while maintaining touch, in a user interface 1901 showing a parking history list, a delete button 1902 for the parking history for which the left flick was input may be activated, as shown in (b) of FIG. 19. When the user selects the delete button 1902, the selected parking history may be deleted from the parking history list.

[0402] 21 is a diagram illustrating a parking history management user interface according to an embodiment of the present invention. Referring to (a) of FIG. 21, when a user inputs a touch and then a press and hold command by maintaining the touch for a certain period of time on a user interface 2001 showing a parking history list, the user terminal device 400 can display a parking history list editing user interface 2003 as shown in (b) of FIG. 21.

[0403] In the user interface 2003, when the user selects the "All" button, the check boxes for all lists are selected, and when the user selects the "All" button again while all lists are selected, the check boxes for all lists can be deselected.

[0404] In addition, when a user selects a checkbox in the user interface 2003, the checkbox is checked and a delete button at the bottom is activated, and when a user selects the delete list button, the selected list can be deleted.

[0405] 22A and 22B are diagrams illustrating a user interface in a vehicle impact event or vehicle movement event situation according to an embodiment of the present invention. As shown in FIG. 22A, the main user interface may display an impact notification icon on the vehicle image to notify the occurrence of an impact event to the vehicle when an impact event occurs while the vehicle is parked or moving. Alternatively, as shown in FIG. 22B, the main user interface may display a visual object (e.g., an arrow icon) on the vehicle image to notify the occurrence of a vehicle movement event when vehicle movement is detected while the vehicle is parked.

[0406] When a user selects a vehicle image object in the main user interface, the user terminal device 400 may display an event history list 2101 as shown in Figure 22(c). Here, the event history list 2101 may display event information for each event, and the event information may display the event location, event date, and event time.

[0407] The event history list 2101 can display information about the most recently occurred event at the top.

[0408] The event history list 2101 can display event type icons 2102. Here, the event type icons 2102 can be displayed by classifying impact events while parking, moving events while parking, and impact events while driving with different icons.

[0409] The event history list 2101 may include an area 2103 corresponding to a remote playback button. Here, the area 2103 may provide notifications that have occurred within a predetermined period from the current time. Here, the "remote playback" may be a function that provides a video corresponding to a selected notification on the black box 100 instead of the user terminal device 400.

[0410] However, the present invention is not limited to this, and the "remote playback" may be implemented by providing a video corresponding to the selected notification on the user terminal device 400. In this case, video information of an event that occurred during a predetermined period of time may be provided, taking into consideration the size of the user data storage space allocated to the server 300, the data transmission rate, etc.

[0411] If area 2103 is selected when the black box 100 is in the continuous recording mode, the black box 100 can play back the corresponding video after the continuous recording mode ends. Alternatively, if area 2103 is selected when the black box 100 is in the parking recording mode, remote playback on the black box 100 is not possible.

[0412] On the other hand, when the user selects one event from the event history list 2101, the user terminal device 400 can display a user interface 2104 as shown in FIG. 22(d).

[0413] If the event is an impact event, the user interface 2104 can display information about the impact occurrence location and impact occurrence time in the top area, or if the event is a movement event while parked, can display information about the movement detection location and movement detection time in the top area.

[0414] The user interface 2104 may display an image 2105 captured at the event location. The image 2105 may be a motion image generated by combining at least two images captured between a predetermined time before the event occurred and a predetermined time after the event occurred. In this case, the image 2105 may be displayed by vibrating left and right or up and down, or may be displayed in a vibrating animation format, to visually indicate that the event has occurred. The image 2105 may be displayed using various visual design elements, such as a rectangle, a square, a circle, a water drop, or a bubble.

[0415] An image download button may be provided in one area of ​​the image 2105. When the user selects the image download button, the corresponding image may be stored in the user terminal device 400.

[0416] The user interface 2104 can then display the event occurrence location on a map, and the map can receive touch interactions such as tapping, dragging, zooming in, zooming out, and rotating.

[0417] 23 is a diagram illustrating a user interface for inputting a live command according to an embodiment of the present invention. The main user interface shown in FIG. 23(a) may include an area 2201 corresponding to a live button. Here, the live button may be a button for requesting an image captured in real time by the black box 100 of a parked vehicle.

[0418] When the user selects the area 2201 corresponding to the live button in the main user interface, a user interface 2202 such as that shown in FIG. 23(b) can be displayed.

[0419] Here, the user interface 2202 may include an area 2203 at the top that displays parking information, and the area 2203 may display the last parking location and the time of live command request.

[0420] The user interface 2202 may then display a pop-up window 2204 related to the provision of live images, where the pop-up window 2204 related to the provision of live images may be positioned on top of the current vehicle position displayed on the map.

[0421] Since the amount of data is limited due to the characteristics of low-power wideband wireless communication, the number of times a live image can be used may be predetermined, and information about the number of times the live image can be used may be displayed in the pop-up window 2204. For example, if the number of times a live image is still available for the user to use may be displayed, and if the number of times the live image is available for use has been exceeded, a phrase such as "The number of uses for this month has been exceeded" may be displayed.

[0422] Meanwhile, when the pop-up window 2204 is selected, the user terminal device 400 may display a live image 2205 as shown in Figure 23(c). Here, the live image 2205 is an image captured in real time by the black box 100 operating in parking recording mode, a motion image generated by combining at least two images after a request made by the live image button 2201, or a moving image acquired in real time by the black box 100 upon request. When the user selects a download button 2206 arranged in one area of ​​the live image 2205, the corresponding image may be stored in the user terminal device 400.

[0423] Meanwhile, user interface 2202 may include a share button 2206 that operates similarly to the share button described above, and a vehicle location button 2207 that operates similarly to the vehicle location button described above.

[0424] Meanwhile, the user interface 2202 may include a live image history area 2208 at the top. When a user selects the live image history area 2208, the user terminal device may display a live image history management user interface, which will be described in more detail with reference to FIG. 24.

[0425] 24 is a user interface diagram showing live history image management according to an embodiment of the present invention. When a user selects area 2208 shown in FIG. 23, the user terminal device may display a live image history management user interface as shown in FIG. 24(a). Here, the live image history list may display location and time information of live requests.

[0426] If the user selects one from the live image history list and then selects the View More object 2302 on the right, a user interface including the live image, map, and location corresponding to the selected list can be displayed at the bottom of the selected list, as shown in Figure 24 (b).

[0427] 25 is a user interface diagram illustrating a method for switching between image display modes according to an embodiment of the present invention. As described above, when a user inputs a request for a last parking position, a request for a live image, or a request for event confirmation, the user terminal device 400 can display a user interface including a map showing the vehicle's location and an image captured by the black box 100, as shown in (a) of FIG. 25.

[0428] When a user touches an image (2401), the user terminal device 400 can display an image viewing screen as shown in Fig. 25(b). When a user touches the image viewing screen as shown in Fig. 25(b), the user terminal device 400 can display a screen for receiving various user inputs such as closing the screen, switching the screen, and downloading an image as shown in Fig. 25(c).

[0429] When the user rotates the terminal device 400 from portrait to landscape orientation while the image viewing screen shown in (b) of Figure 25 is displayed, the user terminal device 400 may rotate and enlarge the image viewing screen and display it as shown in (d) of Figure 25. Alternatively, when the user selects the screen conversion icon located at the top right corner while the image viewing screen shown in (c) of Figure 25 is displayed, the user terminal device 400 may rotate and enlarge the image viewing screen and display it as shown in (e) of Figure 25.

[0430] Meanwhile, each image displayed on the image viewing screen can receive various user operations. For example, as shown in (f) of Figure 25, an image can be enlarged or reduced by the user's pinch zoom in / out operation. That is, when the user selects two points on the image and inputs a pinch zoom in operation to bring them together, the image can be reduced, and when the user selects two points on the image and inputs a pinch zoom out operation to spread them out, the image can be enlarged.

[0431] 26 is a diagram illustrating an environment setting user interface according to an embodiment of the present invention. Referring to (a) of FIG. 26, the environment setting user interface 2501 may include a member information area, a service period area, a notice / event area, a coupon service area, a device management area, an emergency SOS notification area, a cloud safety alert area, and a My Driving area.

[0432] Here, the coupon service area can display information about the number of coupons that the user can use. When the coupon service confirmation area 2502 of the environment setting user interface 2501 is selected, the user terminal device 400 can display a coupon list 2503 as shown in FIG. 26(b).

[0433] Here, coupon list 2503 can display coupons assigned to a user, and coupon list 2503 can be configured with multiple coupon items. Each coupon item can display a coupon icon, coupon name (e.g., washer fluid, wiper, etc.), coupon provision conditions (e.g., provided when visiting an agency), coupon usage period, and coupon status. Here, coupon status can include "Use" indicating a currently available coupon, "To be provided" indicating a coupon that is scheduled to be provided, "Used" indicating a used coupon, and "Expired" indicating a coupon whose period has expired.

[0434] The coupon items can be displayed in the following order from top to bottom: available, upcoming availability, upcoming offer, used, and expired.

[0435] The activation status of information displayed in the coupon item can be adjusted according to the status of the coupon. For example, a currently available coupon can be displayed with all text and icons activated. A coupon that is scheduled to be offered can be displayed with all text and icons activated and only the "To be offered" button deactivated. A used coupon can be displayed with all text and icons deactivated except for the "Used" stamp icon. A coupon whose usage period has expired can be displayed with all text and icons deactivated except for the "Expired" stamp icon.

[0436] According to the present invention, a user can use the user terminal device 400 to make a payment using a coupon before visiting an agency or in a vehicle.

[0437] Figure 27 is a diagram showing a user interface illustrating a coupon usage process according to an embodiment of the present invention. When a user selects "Use" for a specific coupon in the coupon list 2601 shown in Figure 27(a), the user terminal device 400 can display a coupon usage agency list 2602 as shown in Figure 27(b).

[0438] Here, the number of agencies that can be displayed in the coupon available agency list 2602 can be up to 10, displayed in order of proximity within a predetermined radius (for example, a 50 km radius) from the user's current location as the base point.

[0439] If there are no available agencies within a predetermined radius from the user's current location, the user terminal device 400 can display at least one or more of the closest agencies that are outside the predetermined radius.

[0440] In addition, each agency item in the coupon applicable agency list 2602 may display the agency name, address, phone number, route guidance button, and distance information from the current location. When the user selects a phone number, a call application may be called with the corresponding number pre-entered.

[0441] When the user selects the route guidance button, the user terminal device 400 can display a route guidance screen that provides guidance on the route from the current location to the agency. This will be described in more detail with reference to FIG.

[0442] 28 is a diagram showing a user interface for route guidance to agencies where coupons can be used according to one embodiment of the present invention. Referring to (a) of FIG. 28, when a user selects the route guidance button in the list of agencies where coupons can be used 2701, the user terminal device 400 can display a user interface 2702, as shown in (b) of FIG. 28, which shows the locations of agencies on a map.

[0443] When the user selects "route search" on user interface 2702, user terminal device 400 can display user interface 2703 as shown in FIG. 28(c). Here, user interface 2703 can be a route search guidance user interface that displays multiple routes (e.g., a recommended route and a fast route) from the user's current location to the selected agency. When the user selects one of the multiple routes on user interface 2703, user terminal device 400 can display a route guidance screen that provides guidance on the selected route.

[0444] 29 is a user interface diagram illustrating a process for setting up an emergency SOS notification according to an embodiment of the present invention. When a user selects the "Emergency SOS Notification" field in the environment setting user interface illustrated in FIG. 29, the user terminal device 400 may display an emergency contact management user interface 2801 illustrated in (a) of FIG. 29. Here, the emergency contact management user interface 2801 may display previously registered emergency contact information.

[0445] When the user selects the setting icon of the user interface 2801, the user terminal device 400 can display a list pop-up window 2802 shown in Fig. 29(b). Then, the user can input commands such as changing the name, changing the number, deleting the contact, etc. in the list pop-up window 2802.

[0446] 30 is a user interface diagram illustrating a process for registering an emergency SOS contact according to an embodiment of the present invention. Referring to FIG. 30, when no emergency contact information has been registered, the user terminal 400 may display a user interface 2901 as shown in FIG. 30(a). When the user selects a "Register New Contact" area of ​​the user interface 2901, the user terminal 400 may display a user interface 2902 as shown in FIG. 30(b) for directly entering an SOS contact.

[0447] That is, the user interface 2902 for directly entering SOS contacts may include an input area for the name and phone number of the emergency contact, and when the user selects "Register," the contact may be registered as an SOS contact.

[0448] In this case, the user terminal 400 may generate a message to be sent to the emergency SOS contact in order to confirm the newly registered emergency SOS contact, and may transmit the generated message to the terminal corresponding to the registered emergency SOS contact. In this case, the terminal corresponding to the emergency SOS contact may receive and display a text message such as that shown in (c) of FIG.

[0449] Meanwhile, in the above-described process of registering an emergency SOS contact in Fig. 30, the user directly inputs the name and contact information of the user's contact, but the present invention is not limited to this. According to another embodiment of the present invention, the "connected service application" can be linked with a contact application already installed in the user terminal device 400 to display a list of already registered contacts, and the user can register an emergency SOS contact by selecting at least one contact to be registered as an emergency SOS contact from the already registered contact list.

[0450] 31 is a user interface diagram illustrating a processing scenario when an emergency situation occurs according to an embodiment of the present invention. Here, the emergency situation according to the present invention refers to an emergency situation that is more serious than the occurrence of a normal impact event or a movement event, for example, the occurrence of an accident event corresponding to an impact greater than a preset impact value.

[0451] If the black box 100 detects an impact value greater than a preset impact value, the black box 100 transmits an emergency situation event to the server 300, and the server 300 can notify the user terminal device 400 of an emergency situation. In this case, the user terminal device 400 can detect a registered emergency SOS contact and create an emergency situation notification message to be sent to the corresponding emergency SOS contact. The user terminal device 400 can then transmit the created emergency situation notification message to the registered emergency SOS contact.

[0452] 31(a) shows an example of an emergency situation notification message transmitted to an emergency SOS contact point. Referring to FIG. 31(a), the emergency situation notification message 3001 may include an emergency announcement, the driver's phone number, the time and location of the accident, a URL where the location of the accident can be confirmed, a URL of the sound recorded during the accident, a link address where a video of the accident can be confirmed, etc.

[0453] The emergency situation notification message 3001 may further include a preview of the location of the accident, and when the preview is selected, the user may proceed to a map screen that displays the preview in detail.

[0454] When the recipient of the emergency situation notification message selects the URL included in the message at which the location of the accident can be confirmed, the corresponding terminal device can display a user interface 3002 that shows the location of the accident on a map, as shown in Figure 31(b). Here, user interface 3002 can include an area 3003 that displays the vehicle location at the time of the impact and information about the time of the impact. User interface 3002 can also include a map area that displays the location of the vehicle where the impact occurred on a map. User interface 3002 can also include a vehicle location display button 3005.

[0455] Meanwhile, when the recipient of the emergency situation notification message selects the recorded sound URL included in the message, the corresponding terminal device can play the sound recorded during the accident.

[0456] In addition, when the recipient of the emergency situation notification message selects the URL for viewing the emergency situation video included in the message, the corresponding terminal device can connect to the URL address via a communication network and play the video captured in the emergency situation.

[0457] 32 is a diagram illustrating an example of a push notification according to an embodiment of the present invention. According to an embodiment of the present invention, the user terminal device 400 can receive notifications of various event occurrences from the server 300, and the user terminal device 400 can display the received notification information on the screen in the form of a push message.

[0458] As an example, referring to FIG. 32, the push notification may include various notifications such as "notification of impact occurrence while driving," "notification of completion of impact image upload," "notification of vehicle movement detection," "notification of recommendation of popular spots near destination," "notification of weather / atmospheric information," "notification of low battery voltage," "notification of transition to driving state," "notification of impact occurrence while parking," and "notification of black box power ON / OFF."

[0459] Here, "notification of impact while driving" refers to a notification that is displayed when an impact occurs to a vehicle while it is moving. When the user selects "notification of impact while driving," the user terminal device 400 executes the connected service application and can display the impact notification history screen shown in (c) of FIG. 22.

[0460] The "Shocking Image Upload Completion Notification" refers to a notification that is displayed when the upload of the shocking image is completed.

[0461] "Vehicle movement detection notification" refers to a notification that is displayed when vehicle movement is detected while the vehicle is parked. When the user selects "Vehicle movement detection notification," the user terminal device 400 executes the connected service application and can display the impact notification history screen shown in (c) of FIG. 22.

[0462] "Notification of popular spots around destination" refers to a notification that is displayed when the vehicle arrives at the destination. When the user selects "Notification of popular spots around destination," the user terminal device 400 executes a connected service application and can display popular spots around the user's destination. In this case, the popular spots can be popular spots selected based on the preference information of the registered user.

[0463] "Parking Impact Notification" refers to a notification that is displayed when a parking impact occurs. When the user selects "Parking Impact Notification," the user terminal device 400 executes the connected service application and can display the impact notification history screen shown in (c) of FIG. 22.

[0464] The "weather / atmospheric information notification" may refer to a notification informing users of the surrounding weather and / or atmospheric conditions. Here, the "weather / atmospheric information notification" may be displayed in a phrase informing users of the surrounding weather and / or atmospheric conditions.

[0465] Specifically, the "weather / atmospheric information notification" may be displayed when it is detected that the surrounding fine dust concentration is poor. For example, if the surrounding fine dust concentration is "poor" or higher while the vehicle is running, a notification may be displayed in the form of a phrase such as "The surrounding fine dust concentration is poor. Please close the windows tightly and switch the air conditioner to indoor circulation."

[0466] In addition, the "Weather / Atmospheric Information Notification" can be displayed when the surrounding yellow sand concentration is detected as bad. For example, if the surrounding yellow sand concentration is "bad" or higher while the vehicle is running, the corresponding notification can be displayed in the form of a phrase / sentence.

[0467] In addition, the 'Weather / Atmospheric Information Notification' can be displayed when the air quality improves after receiving a fine dust / yellow sand warning for the relevant area while driving. For example, if the air quality improves after receiving a fine dust warning for the relevant area while driving, a notification can be provided in text form, such as, "The air around you has become comfortable. Please open the windows and ventilate the room." As another example, if the air quality in the relevant area is good while driving, a notification can be provided in text form, such as, "The air around you is comfortable. Please open the windows and ventilate the room."

[0468] In addition, the "weather / atmospheric information notification" may generate and provide a notification based on current time information and vehicle driving / parking status information. For example, if the black box is in parking mode and rain is predicted before the user's arrival time (here, the arrival time may be a result value learned through learning about the user's arrival time), the notification may be provided in the form of a guidance phrase such as, "It is expected to rain today. Please be sure to bring an umbrella, even if it is small, and drive safely." If snow is predicted, the notification may be provided in the form of a guidance phrase such as, "It is expected to snow today. Please be sure to bring an umbrella, even if it is small, and drive safely." If both rain and snow are predicted, the notification may be provided in the form of a guidance phrase such as, "It is expected to rain and snow today. Please be sure to bring an umbrella, even if it is small, and drive safely."

[0469] As another example, if the black box is switched from driving mode to parking mode after the engine is turned off on a weekday and rain is predicted, a notification can be provided in the form of a guidance phrase such as "It is expected to rain. We recommend parking indoors today if possible." Also, if snow is predicted, a notification can be provided in the form of a guidance phrase such as "It is expected to snow. We recommend parking indoors today if possible."

[0470] As yet another example, if the black box is in parking mode at the time before the user turns on the engine on the weekend (where the time can be a value learned based on the user's weekend behavioral patterns) and there is no snow or rain expected within seven days from today, a notification can be provided in the form of a guide phrase such as "It looks like there will be no rain for a while. This weekend will be a good day to wash your car" or "It looks like there will be no rain or snow for a while. This weekend will be a good day to wash your car."

[0471] In addition, the "Vehicle Battery Low Voltage Notification" notifies the user of a low battery voltage in the vehicle, and when the user selects the "Vehicle Battery Low Voltage Notification", the user terminal device 400 can execute the connected service application and display the main user interface.

[0472] In addition, the "Black Box Power Off Notification" notifies the user that the black box has been powered off, and when the user selects the "Black Box Power Off Notification," the user terminal device 400 can execute the connected service application and display the main user interface.

[0473] Here, the "black box power off notification" may be notified when the black box 100 reaches a low voltage cut-off setting value and is automatically turned off, when the user turns off the black box at will, when the black box is turned off by unplugging the power cord, or when the power is turned off due to a timer setting.

[0474] In addition, the "Black Box Power On Notification" notifies that the power of the black box is being turned on, and when the user selects the "Black Box Power On Notification", the user terminal device 400 can execute the connected service application and display the main user interface.

[0475] Furthermore, although not shown in FIG. 32, a push notification according to one embodiment of the present invention may further include a "membership used notification."

[0476] The "Membership Used Notification" notifies the details of coupon service usage using a mobile barcode. When the user selects "Membership Used Notification," the user terminal device 400 executes the connected service application and can display the membership usage details screen.

[0477] 33 is a diagram illustrating a user interface for requesting remote playback in a continuous recording mode of a black box according to an embodiment of the present invention. A user may select a 'remote playback button' in the event history list 3201 shown in FIG. 33(a) or the event impact notification user interface 3202 shown in FIG. 33(b). Here, the remote playback button 3202 may be a button that receives a user input for requesting playback on the black box of a video corresponding to an event selected from the event history list 3201 or an event displayed on the user interface 3202.

[0478] When the operating mode of the black box 100 is in continuous recording mode, the user terminal device 400 can display a pop-up window 3203 asking whether to request the black box 100 to play the corresponding video, as shown in (c) or (d) of Figure 33.

[0479] If the user selects “Yes” in the pop-up window 3203, the user terminal device 400 can display a message 3204 informing the black box that the playback of the corresponding video has been requested, as shown in (e) or (f) of Figure 33.

[0480] 34 is a diagram illustrating a scenario of remote playback in a continuous recording mode of a black box according to an embodiment of the present invention. Referring to FIG. 34, when a user requests remote playback of a video through the user interface shown in FIG. 33, the server 300 can transmit a request to play the corresponding video to the black box 100 (3301).

[0481] In this case, the black box 100 can display a pop-up window 3302 indicating that video playback has been requested in the connected service application of the user terminal device 400, and can simultaneously output a sound to notify the same.

[0482] If the user selects "Cancel" in the pop-up window 3302, the black box 100 may display a live view image corresponding to the image currently being captured by the camera.

[0483] However, if the user selects "OK" in the pop-up window 3302, the black box 100 determines whether the video requested by the user terminal device 400 is stored in the black box 100 (3303), and if the video is available (3303: Y), the black box 100 can play the video (3304). After the playback of the video is completed, the black box 100 can display the live view video (3305).

[0484] However, if there is no corresponding video (3303:N), a pop-up window 3306 is displayed informing the user that there is no corresponding video, and when the user selects "OK" in the pop-up window 3306, or after a preset time has elapsed, the live view video can be displayed (3307).

[0485] 35 is a diagram illustrating an operation scenario of the black box when a request for additional playback is received during playback of a video according to an embodiment of the present invention. Referring to FIG. 35, the black box 100 may display a pop-up window 3401 indicating that video playback has been requested in a connected service application of the user terminal device 400, and may simultaneously output a sound notifying the request. When the user selects "OK" in the pop-up window 3401, the black box 100 may determine whether the video requested by the user terminal device 400 is stored in the black box 100, and if the video is available, may play the video.

[0486] Meanwhile, if a request to play another video is made by the connected service application of the user terminal device 400 while the video is being played (3402), the black box can display a pop-up window 3402 indicating that a request to play another video has been made by the connected service application of the user terminal device 400.

[0487] When the user selects "OK" in the pop-up window 3403, the black box 100 determines whether the video requested by the user terminal device 400 is the same video or a different video, and if it is the same video, it plays the same video (3404), or if it is a different video, it plays a different video (3405).

[0488] 36 is a diagram illustrating a user interface for requesting remote playback in a parking mode state of a black box according to an embodiment of the present invention. A user may select a 'remote playback button' in an event history list 3501 shown in (a) of FIG. 36 or an event impact notification user interface 3502 shown in (b) of FIG. 36. Here, the remote playback button 3502 may be a button that receives a user input requesting that a video corresponding to an event selected in the event history list 3501 or an event displayed on the user interface 3502 be played back on the black box.

[0489] When the operating mode of the black box 100 is in continuous recording mode, the user terminal device 400 can display a pop-up window 3503 as shown in Figure 36 (c) or Figure 36 (d) asking whether to schedule playback of the corresponding video after the black box 100 is converted from parking recording mode to continuous recording mode.

[0490] If the user selects "Yes" in the pop-up window 3503, the user terminal device 400 can display a message 3504 in the black box informing the user that playback of the video has been reserved, as shown in (e) or (f) of Figure 36.

[0491] 37 is a diagram illustrating an operation scenario of the black box 100 when the black box 100 switches from parking mode to continuous mode according to an embodiment of the present invention. Referring to FIG. 37, when the operation mode of the black box 100 switches from parking recording mode to driving recording mode (3601), the black box 100 may receive a remote playback request scheduled by the user terminal device 400 (3602). In this case, the black box 100 may display a pop-up window 3603 indicating that video playback has been requested by the connected service application of the user terminal device 400, and may simultaneously output a sound notifying the request. When the user selects "OK" in the pop-up window 3603, the black box 100 determines whether the video requested by the user terminal device 400 is stored in the black box 100, and if the video is available, may play the video.

[0492] However, if the reserved remote playback request is received after the USIM registration pop-up, the black box 100 may first display a USIM registration pop-up window 3604. Then, the black box 100 receives the reserved remote playback request from the user terminal device 400 (3605), and the black box 100 may display a pop-up window 3606 indicating that video playback has been requested in the connected service application of the user terminal device 400, and may simultaneously output a sound notifying the request.

[0493] That is, if the remote playback request reserved in the user terminal device 400 is received before the USIM registration pop-up window, the playback request pop-up window may be displayed, but the USIM registration pop-up window may not be displayed.

[0494] However, if the remote playback request reserved in the user terminal device 400 is received after the USIM registration pop-up, the playback request pop-up window may be displayed after the USIM registration pop-up window.

[0495] 38 is a diagram illustrating a user interface for selecting a wireless communication network in a black box according to an embodiment of the present invention. The black box 100 according to an embodiment of the present invention can connect to the server 300 using various wireless communication connection methods. For example, the wireless communication connection method may be various, such as Long Term Evolution (LTE), Wireless Fidelity (WiFi), Low-Power Wide-Area (LPWA), etc.

[0496] The black box 100 can display a user interface that allows the user to select a wireless communication connection method according to the type of wireless communication module included. When the user selects one wireless communication connection method on the user interface, the black box 100 can transmit various data to the server 300 using the selected wireless communication connection method. As an example, if the black box 100 is equipped with only an NB-IOT communication module, it can display a user interface such as that shown in FIG. 38(a).

[0497] When the user selects NB-IoT in the user interface as shown in (a) of Figure 38, the black box 100 may display a dongle registration user interface as shown in (b) of Figure 38, and when the user selects 'OK' in the dongle registration user interface, the procedure for registering the NB-IoT dongle in the server 300 may proceed. Here, the procedure for registering the NB-IoT dongle in the server 300 is the same as that described above with reference to Figure 5.

[0498] Through this procedure, the registration process of the communication module of the black box 100 to the server 300 for wireless communication can be performed, and once the server 300 successfully authenticates the communication module of the black box 100 and registration is completed, the black box 100 can be connected to the server 300 via wireless communication.

[0499] FIG. 39 is a user interface diagram illustrating a service membership subscription process in a user terminal device according to an embodiment of the present invention. Referring to FIG. 39, the interface for subscription to a service membership may include a user interface for inputting subscriber identification information. For example, referring to FIG. 39(a), when a user selects "Subscribe to Member" 3901 displayed on the left interface, the user terminal device 400 may switch to the interface shown on the right for inputting the subscriber's ID (email address), subscriber password, subscriber nickname, etc. When the user enters user identification information and selects "Subscribe to Member" 3902 while viewing the screen displayed on the device 400, the user terminal device 400 transmits the input user identification information to the server 300. The server 300 may then determine whether the user is authorized to use the service and approve or reject the membership subscription request. The subscriber identification information for a subscription request approved may be stored in the subscriber information storage unit 321 of the server 300.

[0500] Further, the interface for signing up for a service membership may include a user interface for inputting identification information of the black box 100 and / or dongle 200 provided by the subscriber. For example, referring to (b) of FIG. 39, when a user selects 'Device Registration' 3903 displayed on the left interface, the user terminal 400 may switch to the interface shown on the right for inputting the USIM serial number of the NB-IoT terminal 200 provided by the user. When the user inputs the USIM serial number 3904 of the NB-IoT terminal 200 in the interface shown on the right and selects 'Authentication Request' 3905, the user terminal 400 transmits the input USIM serial number to the server 300, and the server 300 may determine whether the corresponding NB-IoT terminal 200 is a terminal authorized to use the service and approve or reject the authentication request. Identification information of the device for which the authentication request is approved may be stored in the subscriber information storage unit 321 of the server 300.

[0501] In this case, the server 300 can match and store subscriber identification information and device identification information for each of a plurality of service subscribers.

[0502] Meanwhile, when the user's membership registration and terminal authentication are completed through the processes shown in (a) and (b) of Figure 39, the user terminal device 400 can display a user interface as shown in (c) of Figure 39. That is, as shown in (c) of Figure 39, one area 3906 of the user interface can display the USIM serial number of the dongle 200 authenticated for the user.

[0503] Fig. 40 is a timing diagram showing a method for providing a connected service according to one embodiment of the present invention. Fig. 41 is a timing diagram showing a method for providing a connected service according to another embodiment of the present invention.

[0504] 40, the black box 100 generates various data during its operation and transmits the generated data to the server 300 (S4001). Here, the data generated by the black box 100 is various, such as image upload data, event occurrence notification data, location data, time data, etc., as described above with reference to FIGS.

[0505] Then, the server 300 may store the data received from the black box 100 in the storage unit (S4002). As an example, the server 300 may store the data received from the black box 100 in the service operation information storage unit 322.

[0506] Then, the server 300 can search for the identification information of the user terminal device 400 corresponding to the black box that generated the data (S4003). As an example, the server 300 can search for the identification information of the user terminal device 400 corresponding to the black box 100 based on the information stored in the service subscriber information storage unit 321.

[0507] The server 300 may then generate a notification message to be transmitted to the searched user terminal device 400 (S4004). Here, the notification message is a message informing the black box 100 of data generation, and may be in a push message format.

[0508] Meanwhile, when a message is transmitted to the user terminal device 400 (S4005), the user terminal device 400 displays a notification message (S4006), and when the user selects the message, the user terminal device 400 can request the server 300 to provide data generated in the black box corresponding to the message (S4007).

[0509] In this case, the server 300 transmits black box data corresponding to the request of the user terminal device 400 to the user terminal device 400 (S4008), and the user terminal device 400 can construct a user interface based on the data generated in the black box and display it on the screen (S4009).

[0510] On the other hand, Fig. 40 is one implementation example of the present invention, and may be implemented as in Fig. 41 according to another embodiment of the present invention. Steps S4001 to S4002 in Fig. 40 are also applicable to Fig. 41.

[0511] Specifically, the black box 100 can generate various data during its operation (S4101), and the server 300 can store the black box data generated by the black box and received from the black box 100 in a storage unit (S4102).

[0512] Then, the server 300 can receive a service provision request from the user terminal device 400 (S4103). In this case, the server 300 searches the service subscriber information storage unit 321 for subscriber identification information corresponding to the user terminal device 400 that has requested the provision of the service (S4104). If the searched subscriber identification information exists as a result of the search, the server 300 can detect black box data corresponding to the subscriber identification information from the service operation information storage unit 322 (S4105).

[0513] Then, the server 300 provides the detected type of black box data to the user terminal device 400 (S4106), and the user terminal device 400 can display the type of data as a visual object (S4107).

[0514] When a user of the user terminal device 400 requests the provision of data generated by the black box 100 by clicking on a visual object or issuing a voice command, the user terminal device 400 transmits a request for providing black box data to the server 300 (S4108), and the server 300 can provide the black box data corresponding to the request to the user terminal device 400 (S4109).

[0515] In this case, the user terminal device 400 can configure a user interface based on the black box data and display it on the screen (S4110).

[0516] According to an embodiment of the present invention, video data generated from a plurality of black boxes subscribed to the service can be stored separately based on the identification information of the black boxes. Thus, when a request for video data is received from a user terminal device of a user corresponding to each black box identifier, the server can check the identifier of the user terminal device that sent the data request to determine whether there is video data to be provided and whether the request for video data is from a legitimate user by checking the identifier of the user terminal device that sent the data request.

[0517] Hereinafter, a method for providing a connected service according to another embodiment of the present invention will be described with reference to the following drawings.

[0518] 42 is a timing diagram illustrating a communication connection process between a user terminal device and a black box according to an embodiment of the present invention. Referring to FIG. 42, a user executes a connected service application through the user terminal device 400 (S4201), and can select a “Black box communication connection request” tab in a user interface displayed by the execution (S4202).

[0519] The user can then select a black box model to be connected to from among the multiple black box models displayed on the user interface (S4203). If there is only one registered black box, only that one black box model can be displayed on the user interface.

[0520] Then, the user can select one of a plurality of wireless communication connection methods of the user terminal device 400 (S4204). Here, the plurality of wireless communication connection methods are various, such as Long Term Evolution (LTE), Wireless Fidelity (WiFi), WiFi hotspot, etc.

[0521] Then, the user terminal 400 can connect to the server 300 through the selected wireless communication connection method (S4205). For example, if the user selects Wi-Fi as the wireless communication connection method, the user terminal 400 can connect to the server 300 through a Wi-Fi network.

[0522] Then, the user terminal device 400 can be connected to the black box 100 selected by the user through the connected server 300 (S4205). When the communication between the user terminal device 400 and the black box 100 is connected, the interface of the user terminal device 400 can display a visual object indicating that the connection has been established (S4206).

[0523] 43 is a diagram illustrating a main user interface of a user terminal device according to another embodiment of the present invention. Referring to FIG. 43, the user interface may include multiple regions.

[0524] When an area 4301 of the user interface is selected, the user terminal device 400 can display a connected black box or a screen for configuring a new connection.

[0525] When area 4302 of the user interface is selected, a screen can be displayed to show and play back recorded images of the black box 100 .

[0526] When area 4303 of the user interface is selected, product information for the black box can be displayed.

[0527] When area 4304 of the user interface is selected, a main menu may be displayed.

[0528] When area 4305 of the user interface is selected, a connected services menu can be displayed.

[0529] Area 4306 of the user interface can be selected to display various menus for account settings, firmware updates, and safety camera data.

[0530] When area 4307 of the user interface is selected, a screen for changing the type of the current communication connection or disconnecting the current connection can be displayed. Here, the bar area included in area 4307 can display the communication connection method of the black box or the connection status of the black box (e.g., "Connected via Hotspot").

[0531] Area 4308 of the user interface may be selected to display a screen that shows connected WiFi networks or allows a new network to be added.

[0532] When area 4309 of the user interface is selected, a screen for setting the black box can be displayed.

[0533] When an area 4310 of the user interface is selected, a screen for displaying a live image can be displayed.

[0534] When area 4311 of the user interface is selected, various notification information such as firmware update notifications, geo-fencing zone entry and exit notifications, and impact notifications can be displayed.

[0535] Hereinafter, a user interface for providing a connected service according to another embodiment of the present invention will be described with reference to Figures 44 to 51. The connected service shown in Figures 44 to 51 can be performed when the black box 100 is connected to a wireless communication network, and the connected service can provide various services such as a service that shows the location of a vehicle, a service that notifies the user that the vehicle is entering or leaving a geofencing zone, and a service that notifies the user that a strong impact has been detected.

[0536] Figure 44 is a user interface diagram showing an account login process of a service subscriber according to an embodiment of the present invention. When a user selects an area 4401 of the main user interface shown in Figure 44(a), the user terminal 400 can display the user interface shown in Figure 44(b). When a user selects 'sign in' 4402 in the user interface shown in Figure 44(b), the user terminal 400 can display the user interface shown in Figure 44(c).

[0537] 44(c) and selects "sign in" 4404, the user terminal device 400 can connect to the server 300 and log in. If the user's information is stored in the service subscriber information storage unit 321 of the server 300, the server 300 can permit the user to log in.

[0538] Figure 45 is a user interface diagram showing a process for displaying the vehicle location according to one embodiment of the present invention. When a user selects an area 4501 of the main user interface in Figure 45(a), the user terminal device 400 can display the user interface in Figure 45(b).

[0539] The user interface of FIG. 45(b) can display the position 4502 of the user terminal device 400 on a map, and a "Live View" button is displayed at the bottom of the map, which can provide the user with an image generated by the black box 100. When the user clicks the "Live View" button, the image provided by the black box 100 may be an image generated in real time, or an image generated in advance and stored on a server or in the internal memory of the black box 100. In FIG. 45(b), the "Live View" button is displayed at the bottom of the map, but this is merely an example, and the button may be displayed on any side of the map screen or around the position 4502 displayed on the map. When the user selects the map in the user interface of FIG. 45(b), the user terminal device 400 can display the user interface of FIG. 45(c).

[0540] Here, the user interface in FIG. 45(c) is an interface that displays the vehicle's position and direction 4503 on a map, and the interface can simultaneously display the position 4504 of the user terminal device 400.

[0541] The user interface of FIG. 45(c) can also display address information 4505 corresponding to the vehicle's location, and can also display last information reception time information 4506 for the vehicle's location.

[0542] 46 is a diagram illustrating a process of setting whether or not to use geofencing notification according to an embodiment of the present invention. Here, geofencing refers to a technology for setting a radius based on a location information solution.

[0543] Specifically, when a user selects an area 4601 of the main user interface in (a) of Fig. 46, the user terminal device 400 can display the user interface in (b) of Fig. 46. Then, when the user selects "push notification settings" 4602 in (b) of Fig. 46, the user terminal device 400 can display a settings screen such as that in (c) of Fig. 46.

[0544] In this case, the user can set a geofencing notification (GEO-Fence Notification) 4603 on the setting screen of (c) in Fig. 46. Furthermore, the setting screen of (c) in Fig. 46 can further include areas for setting a firmware update notification (Firmware Update Notification), a strong impact notification while driving (Strong Impact Notification While Driving), an impact notification while parked (Impact Notification While Parked), and a strong impact notification while parked (Strong Impact Notification While Parked).

[0545] 47 is a user interface diagram illustrating a process for setting a geofencing area according to an embodiment of the present invention. When a user selects an area 4701 of the main user interface in FIG. 47(a), the user terminal device 400 can display the user interface in FIG. 47(b).

[0546] The user interface of (b) in Figure 47 is a user interface that displays the location of the user terminal device 400 on a map, and when the user selects an area 4702 of the user interface, the user terminal device 400 can display the user interface of (c) in Figure 47.

[0547] Then, when the user selects Set Geo-Fence 4703 in the user interface of Figure 47(c) and selects area 4704 in the user interface of Figure 47(d), the user terminal device 400 can display a user interface such as that shown in Figure 47(e).

[0548] 47(e) shows a user interface for setting a geofencing area. The user can set the geofencing area by first selecting a specific point 4705 on a map and then selecting a radius distance 4706 centered on the selected point. In this case, the geofencing area to be set may be set in the shape of a polygon such as a circle or a triangle, or the shape of the geofencing area may be set by user input. Then, the user can set a notification 4707 when entering the geofencing area.

[0549] In this case, the user terminal device 400 can display a user interface that displays the set geofencing area on a map as shown in (f) of Figure 47, and when the user selects area 4708, the geofencing setting can be completed.

[0550] 48 is a user interface diagram illustrating a process for setting a strong impact notification while a vehicle is running according to an embodiment of the present invention. Here, a strong impact refers to a situation in which a large impact equal to or greater than the second impact level occurs, and a situation in which an impact greater than the first impact level but less than the second impact level occurs may be referred to as a general impact.

[0551] Specifically, when a user selects an area 4801 of the main user interface in (a) of Fig. 48, the user terminal device 400 can display the user interface in (b) of Fig. 48. Then, when the user selects "push notification settings" 4802 in (b) of Fig. 48, the user terminal device 400 can display a settings screen such as that in (c) of Fig. 48.

[0552] In this case, the user can set the Strong Impact Notification While Driving on the setting screen of FIG. 48(c).

[0553] 49 is a user interface diagram showing a process for setting an impact notification while the vehicle is parked according to an embodiment of the present invention. (a) of FIG. 49 and (b) of FIG. 49 can be performed through the same process as (a) of FIG. 48 and (b) of FIG. 48, respectively.

[0554] Then, the user can set Impact Notification While Parked 4901 on the user interface of FIG. 49(c).

[0555] 50 is a user interface diagram showing a process for setting a strong impact notification while the vehicle is parked according to an embodiment of the present invention. (a) and (b) of FIG. 50 can be performed through the same process as (a) and (b) of FIG. 48, respectively.

[0556] Then, the user can set a strong impact notification while parked (Strong Impact Notification While Parked) 5001 on the user interface of FIG. 50(c).

[0557] 51 is a diagram illustrating a process of confirming an impact image according to an embodiment of the present invention. When a user selects an area 5101 of the main user interface in FIG. 51(a), the user terminal device 400 can display the user interface in FIG. 51(b).

[0558] The user interface of (b) in Figure 51 is a user interface that displays the location of the user terminal device 400 on a map, and when the user selects an area 5102 of the user interface, the user terminal device 400 can display the user interface of (c) in Figure 51.

[0559] Then, when the user selects cloud video 5103 in the user interface of (c) of Figure 51 and selects Driving Impact Video or Strong Impact Notification While Parked in the user interface of (d) of Figure 51, the user terminal device 400 can display a user interface such as (e) of Figure 51.

[0560] 51(e) is a user interface that displays a list of shocking videos, and a user can select a video that the user wants to play from the displayed list and request downloading. In this case, the user terminal device 400 can transmit a request to the server 300 to transmit the selected video and can receive the selected video from the server 300.

[0561] Meanwhile, when terms such as "first," "second," "third," and "fourth" appear in the specification and claims, they are used to distinguish between similar elements and to describe, but not necessarily, a particular sequence or order of occurrence. Such terms are understood in accordance with the embodiments of the present invention described herein. Similarly, when a method is described herein as including a series of steps, the order of such steps presented herein is not necessarily the order in which such steps may be performed, and any described steps may be omitted and / or any other steps not described herein may be added to the method. For example, a first element may be designated a second element, and similarly, a second element may be designated a first element, without departing from the scope of the present invention.

[0562] Additionally, in the specification and claims, terms such as "left," "right," "front," "rear," "top," "bottom," "above," and "below" are used for descriptive purposes only and do not necessarily describe fixed relative positions. Terms used in this specification and claims are understood to be interchangeable under appropriate circumstances, such that the embodiments of the invention described herein operate in other orientations than those shown or described herein. The term "coupled," as used herein, is defined as directly or indirectly connected in an electrical or non-electrical manner. Objects described as "adjacent" to one another may be in physical contact with one another, in close proximity to one another, or in the same general area or region as one another, as appropriate for the context in which the term is used. The term "in one embodiment" herein refers to the same embodiment, although this does not necessarily mean so.

[0563] Furthermore, in the specification and claims, the terms "connected," "couple," "fastened," "fasten," "coupled," "couple," and various variations of these expressions are used to mean either being directly connected to another component or being indirectly connected via another component.

[0564] In contrast, when an element is referred to as being "directly coupled" or "directly connected" to another element, it should be understood that there are no other elements in between.

[0565] Furthermore, the suffixes "module" and "section" used in this specification for components are given or mixed together solely for the convenience of drafting the specification, and do not have any meanings or roles that are distinct from each other.

[0566] Furthermore, the terms used in this specification are intended to describe the embodiments and are not intended to limit the present invention. As used in this specification, singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, terms such as "comprise" or "include" should not be interpreted as necessarily including all of the various components or steps described in the specification, but should be interpreted as not including some of the components or some of the steps, or as including additional components or steps.

[0567] The present invention has been described above focusing on its preferred embodiments. All embodiments and conditional examples disclosed in this specification are described so that a person skilled in the art can easily understand the principles and concepts of the present invention, and it is understood that the present invention can be realized in modified forms within the scope of the essential characteristics of the present invention.

[0568] Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense, and the scope of the invention is indicated by the appended claims, not the foregoing description, and all variations within the range of equivalents thereto should be construed as being encompassed within the invention.

[0569] Meanwhile, the lane detection methods according to the various embodiments of the present invention may be implemented as a program and provided to a server or device, whereby each device can connect to the server or device storing the program and download the program.

[0570] Furthermore, the methods according to the various embodiments of the present invention may be implemented as a program and stored in various non-transitory computer readable media for provision. A non-transitory readable medium refers to a medium that stores data semi-permanently and is readable by a device, rather than a medium that stores data for a short period of time, such as a register, cache, or memory. Specifically, the various applications or programs described above may be stored in non-transitory computer readable media such as a CD, DVD, hard disk, Blu-ray disc, USB, memory card, ROM, etc. for provision.

[0571] Furthermore, although the preferred embodiments of the present invention have been illustrated and described above, the present invention is not limited to the specific embodiments described above, and it goes without saying that various modifications can be made by a person having ordinary knowledge in the technical field to which the invention pertains without departing from the gist of the present invention as claimed in the claims, and such modifications should not be understood individually from the technical ideas and prospects of the present invention. [Explanation of symbols]

[0572] 100 Vehicle video recording device 200 Vehicle communication device 300 Connected service provider server 400 User terminal device

Claims

1. A method for providing a connected service by a connected service providing server, comprising: storing service subscription information including information of subscribers who have subscribed to the service and device information of the subscribers; receiving a terminal registration request from the vehicle-mounted video capture device; comparing identification information corresponding to the terminal registration request with pre-stored service subscription information to determine the validity of the terminal registration request; If it is determined that the terminal registration request is valid, registering the vehicle-mounted video camera device as a device that has received a service; receiving operational data generated during the operation of the registered vehicle-mounted video capture device; and storing the received operational data; The step of receiving and storing the operational data includes: receiving a motion image registration request from the vehicle-mounted video camera, the motion image registration request including an image division criterion and information on the total number of motion image files, and the image division criterion is configured to variably set an image division unit according to a data transmission amount; transmitting a response to the motion image registration request to the vehicle-mounted video camera; receiving a motion image upload request from the vehicle-mounted video camera; transmitting a response to the motion image upload request to the vehicle-mounted video camera; The motion image upload request and response process are repeated for the number of images to be transmitted. The connected service providing server may combine the transmitted images to generate a motion image.

2. The operational data is 2. The method for providing a connected service according to claim 1, characterized in that the connected service includes at least one of event data corresponding to an event that occurred in the vehicle-mounted video camera, video data captured by the vehicle-mounted video camera, and location data of the vehicle-mounted video camera.

3. retrieving, based on the stored service subscription information, identification information and / or subscriber identification information of a user terminal device corresponding to the vehicle-mounted video camera that transmitted the operation data; generating a notification message to be transmitted to the user terminal device based on the retrieved information; The method of claim 1 , further comprising: transmitting the generated notification message to the user terminal device.

4. The method of claim 3, further comprising the step of transmitting, when the user terminal device requests operational data corresponding to the notification message, the operational data corresponding to the request of the user terminal device to the user terminal device.

5. receiving a service provision request from a user terminal device; retrieving subscriber identification information corresponding to the user terminal device that has requested the provision of the service based on the stored service subscription information; The method for providing connected services according to claim 1 or 2, further comprising the step of: detecting the operation data corresponding to the searched subscriber identification information.

6. providing the detected type of motion data to the user terminal; The method for providing a connected service according to claim 5, further comprising the step of, when the user terminal device requests the provision of the operation data based on the type of the detected operation data, transmitting the operation data corresponding to the request of the user terminal device to the user terminal device.

7. 7. The method for providing a connected service according to claim 1, wherein the terminal registration request for the vehicle-mounted video camera includes at least one of identification information of the vehicle-mounted video camera and identification information of a communication module provided in the vehicle-mounted video camera.

8. The method for providing a connected service according to claim 3 , wherein the terminal registration request of the user terminal device includes at least one of identification information of the user terminal device and identification information of a user for the user terminal device.

9. A connected service providing server, a storage unit for storing service subscription information including information on subscribers who have subscribed to the service and device information of the subscribers; a communication unit that receives a terminal registration request from the vehicle-mounted video capture device; a control unit that compares identification information corresponding to the terminal registration request with already-stored service subscription information to determine the validity of the terminal registration request, and if it is determined that the terminal registration request is valid, registers the vehicle-mounted video camera as a device that has received a service; When the control unit receives operation data generated during an operation of the registered vehicle video imaging device via the communication unit, the control unit controls the storage unit to store the received operation data; The control unit, for providing a motion image, a motion image registration request is received from the vehicle-mounted video shooting device, the motion image registration request includes an image division criterion and information on the total number of motion image files, and the image division criterion is configured to variably set an image division unit according to a data transmission amount; transmitting a response to the motion image registration request to the vehicle-mounted video camera; receiving a motion image upload request from the vehicle-mounted video camera; transmitting a response to the motion image upload request to the vehicle-mounted video camera; The motion image upload request and response process are repeated for the number of images to be transmitted. The connected service providing server generates a motion image by combining the transmitted images.

10. The operational data is The connected service providing server according to claim 9, characterized in that it includes at least one of event data corresponding to an event that occurred in the vehicle-mounted video camera, video data captured by the vehicle-mounted video camera, and location data of the vehicle-mounted video camera.

11. The control unit searching for identification information and / or subscriber identification information of a user terminal device corresponding to the vehicle-mounted video camera that transmitted the operation data based on the stored service subscription information; generating a notification message to be transmitted to the user terminal device based on the retrieved information; The connected service providing server according to claim 9 , further comprising: controlling the communication unit to transmit the generated notification message to the user terminal device.

12. The control unit The connected service providing server of claim 11, wherein, when the user terminal device requests operation data corresponding to the notification message, the communication unit is controlled to transmit the operation data corresponding to the request of the user terminal device to the user terminal device.

13. The control unit 11. The connected service providing server according to claim 9, wherein when a service provision request is received from a user terminal device via the communication unit, subscriber identification information corresponding to the user terminal device that has requested the service provision is searched for based on the stored service subscription information, and the operation data corresponding to the searched subscriber identification information is detected.

14. The control unit controlling the communication unit to provide the detected type of operation data to the user terminal device; The connected service providing server according to claim 13, characterized in that, when the user terminal device requests the provision of the operation data based on the type of the detected operation data, the communication unit is controlled to transmit the operation data corresponding to the request of the user terminal device to the user terminal device.

15. A recording medium on which program code for executing the method for providing connected services according to any one of claims 1 to 8 is recorded.

Images