JP7614726B2 - Information processing device and method for controlling information processing device - Google Patents

Description

The present invention relates to an information processing device that requests image processing from a server having RAW video data via a communication network and obtains the image processing results from the server.

In recent years, there has been a trend toward increasing video resolution and frame rates. In particular, when executing image processing applications that handle large amounts of RAW video data, each frame of the video is played back while undergoing image processing such as decoding and demosaicing, requiring equipment with large storage capacity and high processing power. The problem with introducing such equipment is that it is expensive, and one possible solution to this problem is to use a cloud server via a communications network.

In this case, a server with large-capacity storage and high processing power will hold the RAW video data, perform image processing in response to requests received from the client user terminal, and return the image processing results. The user terminal will then display images based on the image processing results received from the server. This eliminates the need for the user terminal to have large-capacity storage and high processing power.

Patent Document 1 discloses an image distribution system in which a server transmits reduced versions of original video data to a client terminal, thereby reducing the amount of data required for communication. In this image distribution system, a client terminal specifies a desired scene and transmits it to the server, and the server extracts the specified scene from the original video data and transmits it to the client terminal.

However, in the image distribution system of Patent Document 1, if a problem occurs in the communication between the server and the client terminal, the client terminal cannot receive the images, and the user cannot edit the received images.

JP 2017-059953 A

The present invention acquires image data based on RAW video data stored on a server in advance according to the content of the editing work on the user terminal, and in the event of a communication error, makes it possible to perform editing work on the user terminal using the acquired image data.

According to one embodiment of the present invention, an information processing device comprises a communication means for communicating with a server having RAW video data, an execution means for communicating with the server via the communication means and executing an application for performing image processing of the RAW video data on the server, and a control means, wherein when the control means receives an image processing operation in the application, it obtains from the server each image data based on each of a portion of all frames that constitute the RAW video data in accordance with the operation, and in the event of an error in communication with the server, it is capable of performing image processing on the device itself using each of the obtained image data.

According to the present invention, image data based on RAW video data stored on a server is acquired in advance according to the content of the editing work on the user terminal, and if a communication error occurs, it is possible to perform editing work on the user terminal using the acquired image data.

FIG. 1 is a configuration diagram of an entire system according to first and second embodiments of the present invention. FIG. 2 is a block diagram showing a configuration of a client device according to the first and second exemplary embodiments of the present invention. 1A and 1B are examples of screen configurations of a user interface of an application in the first and second embodiments of the present invention, in which (a) is an example when operating in cut edit mode, and (b) is an example when operating in RAW edit mode. 10 is a flowchart showing a preview processing procedure of a client apparatus according to the first and second exemplary embodiments of the present invention. 10 is a flowchart showing a procedure of a backup data storage process of a client device according to the first and second exemplary embodiments of the present invention. 5 is a flowchart showing a data transmission process procedure of the server device according to the first embodiment of the present invention. 10 is a flowchart showing a spare data request process procedure of a client device according to the second embodiment of the present invention. 10 is a flowchart showing a procedure of a spare data transmission process of a server device according to a second embodiment of the present invention.

The embodiment of the present invention will be described in detail with reference to the drawings.

The embodiment described below is an example of the present invention and may be modified or changed as appropriate depending on the configuration of the device to which the present invention is applied and various conditions.

(First embodiment)
In this embodiment, a system is exemplified in which a client device requests image data and spare data for display from a server device in response to a user's operation on the client device. The server device is a server on a cloud, and the client device is a terminal for remotely editing original RAW video data stored on the server. The client device is, for example, an information processing device such as a personal computer (PC), a smartphone, or a tablet device.

Figure 1 is a diagram showing the overall system configuration in this embodiment.

101 is a client device that executes a video editing application. The video editing application will be described later.

103 is a server device that stores original RAW video data. In addition, the server device 103 can perform image processing on the original RAW video data as instructed by the client device.

The client device 101 and the server device 103 transmit and receive data related to video editing via the Internet 102. The client device 101 requests image data from the server device 103 in response to user operations on the video editing application. The server device 103 then transmits data in response to the request to the client device 101.

Figure 2 is a block diagram showing the configuration of a PC 200 that constitutes the client device 101 and the server device 103. The client device 101 and the server device 103 may be realized by a single PC, or may be realized by distributing each function to multiple PCs as necessary. When configured with multiple PCs, it is preferable that they are connected by a local area network (LAN) or the like so that they can communicate with each other.

In FIG. 2, 210 is a CPU. The CPU 210 controls the entire PC 200 and can execute image processing commands to perform image processing.

220 is a GPU, which can execute image processing commands generated by the CPU 210 and perform image processing. The GPU 220 has an internal Video Random Access Memory (VRAM), and receives data transfer commands to send and receive data to and from the CPU 210.

230 is a Random Access Memory (RAM) that temporarily stores programs and data supplied from the outside. RAM 230 is also used as a storage area for temporarily storing data that is output in accordance with the execution of a program.

240 is a read only memory (ROM) that stores programs and parameters. ROM 240 stores the program code of the software executed by CPU 210, parameters required for the operation of the software, and the like. This program code is executed by CPU 210. Note that ROM 240 in this embodiment is a flash ROM, and the control program can be rewritten.

250 is a recording medium that can be read and written by PC 200. The recording medium refers to a medium capable of recording electronic data, such as an internal memory of a computer, a memory card that can be detachably connected to a computer, a HDD, a CD-ROM, an MO disk, an optical disk, or a magneto-optical disk. Digital data such as video data is stored as a file on recording medium 250.

260 is an operation unit, which is composed of a keyboard, mouse, etc. Based on instructions input via the operation unit 260, input/output data is specified, programs are changed, image processing is started or stopped, etc.

270 is a display unit such as a liquid crystal display incorporated in the PC 200. The display unit 270 displays, for example, the Graphical User Interface (GUI) screen of an application, the results of image processing, etc.

280 is an internal bus that serves as a transmission path for control signals and data signals between each element in PC 200.

Next, the operation of the client device 101 of this embodiment will be described with reference to Figs. 3 to 5. Note that, in this embodiment, an example is shown in which a program (video editing application) that realizes the processing of the flowchart is recorded in the ROM 240 of the client device 101, but it may also be recorded in a recording medium 250 such as a memory card. Similarly, the present invention can also be applied when the program is present on a network.

Figure 3 shows an example of the configuration of a user interface (UI) of a video editing application 300 that runs on the client device 101. The video editing application 300 is an application that creates an edited video from raw video data that serves as material. The video editing application has at least a cut editing mode and a raw editing mode.

In cut edit mode, RAW video data can be placed on a timeline to edit the composition of the edited video. In RAW edit mode, color, brightness, etc. can be adjusted using RAW image processing. Users can switch between cut edit mode and RAW edit mode by operating the menu, etc.

Figure 3(a) is a diagram showing the UI configuration of a video editing application 300 operating in cut edit mode.

310 is a video data list display area, which displays a list of video data loaded from the recording medium 250. 311 represents a single video data item with an icon.

320 is a preview area that plays and displays the results of image processing performed on the video data selected by the user.

330 is a playback control section that allows the user to control playback. By clicking the play/stop button on playback control section 330, the user can instruct the video playback function to start or stop image processing. The play/stop button pauses playback when a video is being played, and starts playback when the video is not being played. In addition to the play/stop button, playback control section 330 also has a frame forward button that moves the playback position one frame forward or backward, and a jump button that moves to the start or end position of video playback.

340 is a timeline section that displays in chronological order how video and audio data are arranged on each track of the edited video. In the cut edit mode, the user can arrange video data at any position by dragging and dropping the icon 311 onto the timeline section 340. In the timeline section 340, video data is displayed as a rectangle, and the start and end positions of each video data can be specified by dragging the left and right ends of the rectangle. 341 is an icon that indicates the current playback position in the edited video. The result of image processing performed on the frame indicated by the playback position icon 341 is displayed in the preview area 320. The position of the playback position icon 341 can be changed by the user dragging and dropping the playback position 341 or clicking the frame forward button or jump button of the playback control section 330. When the user clicks the play button of the playback control section 330, the input video data is played back starting from the frame indicated by the playback position icon 341.

Figure 3(b) is a diagram showing the UI configuration of a video editing application 300 operating in RAW editing mode. 310 to 341 in Figure 3(b) are the same as those in Figure 3(a).

350 is a general parameter control section for performing image processing during video playback. Parameter control section 350 is composed of a slider bar and a pull-down list. By operating parameter control section 350, the user can change various image processing parameters (including development parameters) to be applied to the RAW video data.

Note that the video editing application 300 has an operation unit for executing various general functions related to video editing and playback, but this is not shown here. The video editing application 300 may also have a video editing function for video data in a format other than RAW video data. In this embodiment, only processing for RAW video data will be described.

Next, using FIG. 4, we will explain the preview process by the video editing application 300 running on the client device 101.

In step S401, if the frame to be displayed in the preview area 320 has been changed, the CPU 210 proceeds to step S402, otherwise proceeds to step S403. The frame is changed, for example, when the video data to be edited is changed by the user operating the video data list display area 310, when the position of the playback position icon 341 is changed by the user operating the playback control unit 330, or when the video is being played and the time to display the next frame has arrived. The CPU 210 continuously detects user operations in the video editing application and transmits information to the server device 103 based on the detection results.

In step S402, the CPU 210 requests the server device 103 for a display image of the new frame after the change. The display image is image data that has been subjected to image processing including development processing for a specified frame of the RAW video data, and is, for example, general image data expressed in RGB or YUV. The display image may be compressed. When requesting the display image, information such as the file name of the RAW video data, the frame number, and a list of parameters set by the parameter control unit 350 is sent to the server device 103.

In step S403, if the image processing parameters have been changed in the video editing application 300, the CPU 210 proceeds to step S404, otherwise the CPU 210 proceeds to step S407. The image processing parameters are changed, for example, when the user operates the parameter control unit 350.

In step S404, the CPU 210 requests the server device 103 to transmit an image for display that has been image-processed by applying the new image processing parameters after the change to the frame displayed in the preview area 320. The information transmitted at this time is the same as that in step S402.

In step S405, the CPU 210 determines whether the display image requested in step S402 or S404 has been received from the server device 103. If the display image has been received, the process proceeds to step S406; if not, the process proceeds to step S407.

In step S406, if a communication error occurs between the client device 101 and the server device 103, the CPU 210 proceeds to step S407, otherwise the CPU 210 proceeds to step S405. The CPU 210 determines that a communication error has occurred, for example, when an error notification is received from the server device 103, or when a timeout occurs because there is no response for a certain period of time after sending an image request to the server device 103.

In step S407, the CPU 210 acquires data of a frame that is closest to the frame to be displayed from among the preliminary data stored in the recording medium 250, and generates an image for display. At this time, if the preliminary data is RAW image data, image processing including development processing is performed based on the parameters set by the parameter control unit 350. If the preliminary data is general image data other than RAW image data, image processing is performed using only applicable parameters set by the parameter control unit 350. Note that the preliminary data is image data that has been acquired in advance from the server device 103 in response to operations in the video editing application. The preliminary data is image data based on the original RAW video data held by the server device 103, and the format, resolution, number of frames, etc. of the image data differ depending on operations in the video application.

In step S408, if the generation of the display image in step S408 is successful, the CPU 210 proceeds to step S410, otherwise the CPU 210 proceeds to step S409. If the generation of the display image in step S408 is not successful, it may be that the corresponding preliminary data is not found, or that the PC constituting the client device 101 does not have the capability to execute the specified image processing.

In step S409, the CPU 210 displays an error message in the preview area 320 indicating that a preview is not possible.

In step S410, the CPU 210 displays the display image in the preview area 320. The CPU 210 may have a function of determining whether the display image was received from the server in step S405 or was generated from preliminary data in step S407, and notifying the user.

In step S411, if the user has performed an operation to end the application, the CPU 210 ends the preview process, otherwise the process proceeds to step S401.

Next, the preliminary data saving process by the video editing application 300 running on the client device 101 will be described with reference to FIG. 5. The preliminary data saving process starts simultaneously with the RAW video editing process, and is performed in the background when the CPU 210 is capable of performing additional processing.

In step S501, if the video editing application 300 is operating in cut edit mode, the CPU 210 transitions the process to step S502, and if not, transitions the process to step S504.

In step S502, the CPU 210 requests the server device 103 to send reduced display images for all frames included within _T1 seconds before and after the currently displayed frame (current frame). _T1 is an integer, e.g., 5 seconds. Note that the display images requested at this time have a lower resolution than the images requested in steps S402 and S404 in FIG. 4.

In step S503, the CPU 210 requests from the server device 103 display images that are reduced by one frame for every N frames per second for all RAW video data arranged in the timeline section 350. The display images at this time have a lower resolution than those requested in steps S402 and S404 of FIG. 4. Note that display images may be similarly requested not only for the RAW video data arranged in the timeline section 350, but also for all RAW video data displayed in the video data list display area 310.

In step S504, if the video editing application 300 is operating in RAW editing mode, the CPU 210 transitions the process to step S505; otherwise, the CPU 210 transitions the process to step S509.

In step S505, the CPU 210 requests original RAW image data for all frames included within _T2 seconds before and after the current frame from the server device 103. _T2 is an integer, e.g., 1 second. Note that the display images requested in steps S502 and S505 are frames within a predetermined time before and after the current frame, but may be a predetermined number of frames before and after the current frame.

In step S506, the CPU 210 requests from the server device 103 one frame of original RAW image data for each scene of all RAW video data arranged in the timeline section 350. A scene is a unit obtained by dividing each RAW video data into N-second intervals. N is an integer, e.g., 30 seconds. Note that a scene may be a unit obtained by dividing each RAW video data into points where the content of the image changes significantly, or points where a mark or the like has been added by the user. Note that the original RAW image data may be similarly requested not only for the RAW video data arranged in the timeline section 350, but also for all RAW video data displayed in the video data list display area 310.

Note that in steps S502 and S503, or steps S505 and S506, if similar backup data already exists, the request may be skipped.

In step S507, if the image data requested in steps S502 and S503, or steps S505 and S506, has been received from the server device 103, the CPU 210 proceeds to step S508; otherwise, the CPU 210 proceeds to step S507.

In step S508, the CPU 210 stores the image data received from the server device 103 as spare data in the recording medium 250. Note that spare data that is no longer in use may be erased.

In step S509, if the user operates to switch between cut edit mode and RAW edit mode, or to switch the display frame, the CPU 210 transitions the process to step S501; otherwise, the CPU 210 transitions the process to step S510.

In step S510, if the user has performed an operation to end the application, the CPU 210 transitions the process to step S511; otherwise, the CPU 210 transitions the process to step S509.

In step S511, the CPU 210 erases the backup data and ends the backup data storage process.

In this embodiment, the client device 101 determines in steps S501 to S506 how to obtain the preliminary data from the server device 103 depending on the content of the user operation in the video editing application.

In cut edit mode, since it is conceivable that the user will fine-tune the start and end positions of the RAW video data while viewing the preview, in step S502, display images before and after the current frame are requested without thinning. Also, since it is conceivable that the user will arrange the images on the timeline section 340 while checking the overall shot content, in step S503, display images of all RAW video data are requested after thinning out a certain number of frames. In either case, it is sufficient for the user to be able to check the image content in the spare data, so low-resolution display images are requested to keep the amount of data down.

In RAW editing mode, the user may wish to make fine adjustments to colors while viewing the preview, and so RAW image data before and after the current frame is requested. Also, the user may wish to compare the results of color adjustments made to each scene, and so RAW image data is requested for one frame for each scene. In either case, image processing including RAW development processing must be performed in response to the operation of the parameter control unit 350, and so RAW image data for one frame of the original RAW video data is required. However, if the PC constituting the client device 101 does not have the ability to perform RAW development processing, a configuration may be adopted in which a display image with the same resolution as the original is requested, and if this is to be used as spare data for the preview, the results of image processing performed to the extent possible by the client device 101 are used.

The values of T ₁ T ₂ , N, etc., relating to the reduction ratio of the display image and frame thinning, may be changed according to the communication speed via the Internet 102 and the capacity of the recording medium 250 of the client device 101 .

Next, the operation of the server device 103 of this embodiment will be described with reference to FIG. 6. Note that, in this embodiment, an example is shown in which the program that realizes the processing of the flowchart is recorded in the ROM 240 of the server device 103, but the program may also be recorded in a recording medium 250 such as a memory card. Similarly, the present invention can also be applied when the program is present on a network.

The data transmission process of the server device 103 will be explained using Figure 6.

In step S601, if the client device 101 requests to send image data, the CPU 210 transitions the process to step S602; otherwise, the CPU 210 transitions the process to step S601.

In step S602, the CPU 210 acquires RAW image data of a specified frame from the RAW video data stored on the recording medium 250 in response to a request from the client device 101.

In step S603, if the request from the client device 101 received in step S601 is a request for an image to be displayed, the CPU 210 transitions the process to step S604, and if not, transitions the process to step S607.

In step S604, the CPU 210 performs image processing on the RAW image data acquired in step S602 in response to a request from the client device 101.

In step S605, if the request from the client device 101 received in step S601 is for a low-resolution image to be displayed, the CPU 210 transitions the process to step S606, and if not, transitions the process to step S607.

In step S606, the CPU 210 performs a reduction process on the result of the image processing in step S604.

In step S607, the CPU 210 transmits data to the client device 101.

In step S608, if the user has performed an operation to end the application, the CPU 210 ends the data transmission process, otherwise the process proceeds to step S601.

In this way, according to the present invention, the client device 101 can continue the preview process by using the spare data even if an error occurs in communication with the server device 103. Furthermore, the spare data does not store the original RAW video data as is, but thins or reduces the data in a manner suited to the user's operating conditions, thereby reducing the amount of spare data and allowing the user to continue the same editing work on their own device in the event of a communication error.

Second Embodiment
In the first embodiment, an example of a system in which a client device requests image data and preliminary data for display from a server device based on a user's operation status has been described. In the present embodiment, an example of a system in which a server device transmits preliminary data based on information regarding a user's operation status will be described.

The overall system configuration diagram, the block diagram showing the configuration of the PC, the UI configuration diagram of the video editing application, the flowchart of the preview process by the video editing application running on the client device 101, and the flowchart of the data transmission process of the server device 103 in this embodiment are similar to those in Figures 1 to 4 and Figure 6 in the first embodiment, respectively, and therefore will not be described.

Next, the preliminary data request process by the video editing application running on the client device 101 will be described with reference to FIG. 7. The preliminary data request process starts at the same time as the RAW video editing process, and is performed in the background when the CPU 210 is capable of performing additional processing.

In step S701, the CPU 210 transmits information about the operating mode and current frame of the video editing application 300 to the server device 103.

In step S702, if the CPU 210 has completed receiving the preliminary data from the server device 103, it transitions the process to step S703; otherwise, it transitions the process to step S704.

In step S703, the CPU 210 stores the image data received from the server device 103 as spare data in the recording medium 250. Note that spare data that is no longer in use may be erased.

In step S704, if the user operates to switch between cut edit mode and RAW edit mode, or to switch the display frame, the CPU 210 transitions the process to step S701; otherwise, the CPU 210 transitions the process to step S705.

In step S705, if the user has performed an operation to end the application, the CPU 210 transitions the process to step S706, otherwise the CPU 210 transitions the process to step S702.

In step S706, the CPU 210 erases the backup data and ends the backup data storage process.

Next, the preliminary data transmission process by the server device 103 will be described with reference to FIG. 8. The preliminary data transmission process starts at the same time as the data transmission process, and is performed in the background when the CPU 210 is capable of performing surplus processing.

In step S801, if the CPU 210 receives information about the edit mode or display frame of the application 300, the process proceeds to step S802; otherwise, the process proceeds to step S808.

In step S802, if the video editing application 300 is operating in cut edit mode, the CPU 210 transitions the process to step S803; otherwise, the CPU 210 transitions the process to step S805.

In step S803, the CPU 210 starts generating reduced display images for all frames within _T1 seconds before and after the current frame, where _T1 is an integer, e.g., 5 seconds. The display images at this time have a lower resolution than those requested in steps S402 and S404 of FIG.

In step S804, the CPU 210 starts generating a display image that is reduced by one frame for every N frames per second for all RAW video data arranged in the timeline section 350. The display image at this time has a lower resolution than that requested in steps S402 and S404 of FIG. 4.

In step S805, if the video editing application 300 is operating in RAW editing mode, the CPU 210 transitions the process to step S806, and if not, transitions the process to step S808.

In step S806, the CPU 210 starts generating original RAW image data for all frames included within _T2 seconds before and after the current frame, where _T2 is an integer, for example 1 second.

In step S807, the CPU 210 starts generating one frame of original RAW image data for each scene for all RAW video data arranged in the timeline section 350. A scene is a unit in which each RAW video data is divided every N seconds. N is an integer, for example, 30 seconds.

In step S808, if the CPU 210 has completed the generation of any of the preliminary data that was started in steps S803, S804, S806, or S807, it transitions the process to step S809; otherwise, it transitions the process to step S810.

In step S809, the CPU 210 transmits the generated preliminary data to the client device 101.

In step S810, if the user has performed an operation to end the application, the CPU 210 ends the preliminary data transmission process; otherwise, the process proceeds to step S801.

In this embodiment, how to obtain the preliminary data is determined in steps S802 to S807.

The method of determining whether to acquire spare data is the same as steps S501 to S506 in FIG. 5, but the server device 103 can improve processing efficiency by changing each parameter depending on its own operating status. For example, when there are many requests from the client device 101 and the processing load is high, the number of spare data sheets can be thinned out to generate the minimum amount of spare data with a low processing load.

In this way, according to the present invention, even if an error occurs in communication with the server device 103, the client device 101 can continue the preview process on its own device by using the backup data. Furthermore, by determining the backup data to be generated by the server device 103, processing can be performed more efficiently according to the operating conditions within the server device.

Although the embodiments of the present invention have been described above in detail, the present invention is not limited to these embodiments, and various forms within the scope of the gist of the present invention are also included in the present invention. Note that parts of the above-described embodiments may be combined as appropriate.

The object of the present invention is also achieved by carrying out the following process:

First, a storage medium (or storage media) on which is recorded the program code of the software that realizes the functions of the above-mentioned embodiments is supplied to a system or device. Then, the computer (or CPU or MPU) of that system or device reads and executes the program code stored in the storage medium. In this case, the program code read from the storage medium itself realizes the functions of the above-mentioned embodiments, and the storage medium on which the program code is stored constitutes the present invention.

In addition, by executing the program code read by the computer, not only can the functions of the above-mentioned embodiments be realized, but it can also be achieved as follows. That is, based on the instructions of the read program code, an operating system (OS) running on the computer performs some or all of the actual processing, and the functions of the above-mentioned embodiments are realized by this processing. Examples of storage media for storing the program code here include hard disks, ROMs, RAMs, non-volatile storage media such as CD-ROMs, CD-Rs, DVDs, optical disks, magneto-optical disks, and MOs. Also, computer networks such as LANs (local area networks) and WANs (wide area networks) can be used to supply the program code.

Claims (10)

A communication means for communicating with a server having RAW video data;
an execution means for communicating with the server via the communication means and executing an application for performing image processing of the RAW video data on the server;
A control means,
The information processing device is characterized in that, when the control means receives an image processing operation in the application, it obtains from the server image data based on each of the frames out of all the frames that make up the RAW video data in accordance with the operation, and in the event of an error in communication with the server, it is capable of performing image processing on the device itself using the obtained image data. The information processing device according to claim 1, characterized in that, when the operation accepted by the application is a cut edit of a video, the control means acquires each developed frame obtained by developing the portion of the frames constituting the RAW video data as each of the image data. The information processing device according to claim 2, characterized in that the control means acquires the image data of each of the developed frames constituting the RAW video data by reducing it. The information processing device according to claim 2 or 3, characterized in that the control means acquires image data by thinning out some of the frames from each image data obtained by developing the some of the frames that constitute the RAW video data. The information processing device according to claim 1, characterized in that the control means, when the operation accepted by the application is the setting of development parameters, acquires RAW image data for each of the frames constituting the RAW video data. The information processing device according to claim 5, characterized in that the control means acquires RAW image data for each frame before and after the current frame for which the development parameters are set. The information processing device according to claim 6, characterized in that the control means acquires RAW image data of all frames included in a predetermined time before and after the current frame for which the development parameters are set. The information processing device according to claim 7, characterized in that the control means acquires RAW image data for each frame at a predetermined interval from among all frames that are not included in the predetermined time before and after the current frame for which the development parameters are set. A storage means for storing each of the image data,
9. The information processing apparatus according to claim 1, wherein the control means erases the image data from the storage means when the application is terminated. 1. A method for controlling an information processing device that communicates with a server having RAW video data and executes an application for performing image processing of the RAW video data on the server, comprising:
A control method for an information processing device, characterized in that, when an image processing operation is received in the application, image data based on each of a portion of all frames that make up the RAW video data is obtained from the server in accordance with the operation, and if an error occurs in communication with the server, image processing is performed on the device using the obtained image data.

Images