JP6266827B1 - Terminal and server - Google Patents

Abstract

[PROBLEMS] To promote sharing of content experiences. According to one aspect of the present invention, a terminal includes a reception unit and an execution unit. The reception unit indicates application operation data including operation input data for the application and time data indicating a time for applying the operation input data to the application, and a random access point set in specific time data included in the application operation data. Receive tag data. The execution unit applies the operation input data to the application at the time indicated by the time data corresponding to the operation input data. The execution unit causes the application to transition to an execution state corresponding to the time indicated by the specific time data, triggered by a user input for selecting a random access point. [Selection] Figure 3

Description

  The present invention relates to a technology for sharing a content experience between users.

  Patent Document 1 discloses sharing state save data generated by state save processing with other players ([0101]). By sharing the state save data with other players, the player can cause other players to continue the game play. Using the state save data created by another player, the game can be played from the continuation. Furthermore, there is also disclosed a sharing condition that is information indicating how the target state save data is shared with other players (for example, shared with a specific player) ([0104]).

  Patent Document 2 discloses a technique for sharing a screen of a game played by a user as a reproduced video with other users. The reproduced moving image is constructed based on log information that is a character code such as ASCII data ([0042], [0044], [FIG. 2]). By inputting the reproduction movie construction condition, for example, a reproduction movie can be constructed in which a scene desired to be browsed is extracted from the game screen ([0076]). In addition, by setting a reproduction movie construction condition to extract other log information excluding log information for a predetermined period, it is possible to construct a reproduction movie that excludes one scene that you do not want to share from the entire game you played ([0077]).

JP-T-2015-515284 JP 2017-6695 A

  According to the technique of Patent Document 1, the player can cause another player to play the continuation of his / her game play, or conversely, can play the continuation of the game play of the other player. However, in any case, the number of points that can be resumed from one state save data is limited to one (at the time when the state save is performed). Therefore, in order to share state save data that can be resumed from various points with other players, it is necessary for the player to save the state at all of the points and give a sharing instruction. Furthermore, if it is attempted to specify the sharing condition, the trouble of the player becomes even more complicated.

  Patent Document 2 is merely a technique for constructing a reproduced moving image, and it is not assumed that a user who views the moving image is involved in the game play represented by the reproduced moving image.

  The present invention aims to promote sharing of content experiences.

  According to an aspect of the present invention, the terminal includes a reception unit and an execution unit. The reception unit indicates application operation data including operation input data for the application and time data indicating a time for applying the operation input data to the application, and a random access point set in specific time data included in the application operation data. Receive tag data. The execution unit applies the operation input data to the application at the time indicated by the time data corresponding to the operation input data. The execution unit causes the application to transition to an execution state corresponding to the time indicated by the specific time data using a user input for selecting a random access point as a trigger.

  According to another aspect of the present invention, the terminal includes a generation unit and a transmission unit. The generation unit adds tag data indicating a random access point set to specific time data included in application operation data including operation input data for the application and time data indicating the time to apply the operation input data to the application. Generate a request to change or delete. The transmission unit transmits a request. The other terminals to which the application operation data and the tag data are distributed apply the operation input data to the application at the time indicated by the time data corresponding to the operation input data. Other terminals use the user input for selecting a random access point as a trigger to transition the application to an execution state corresponding to the time indicated by the specific time data.

  According to another aspect of the present invention, the server includes a reception unit, a management unit, and a transmission unit. The receiving unit adds tag data indicating a random access point set to specific time data included in application operation data including operation input data for the application and time data indicating the time to apply the operation input data to the application, Receive a request to change or delete. The management unit manages the tag data according to the request. The transmission unit transmits tag data. The terminal to which the application operation data and the tag data are distributed applies the operation input data to the application at the time indicated by the time data corresponding to the operation input data. The terminal causes the application to transition to an execution state corresponding to a time indicated by specific time data, triggered by a user input for selecting a random access point.

  According to another aspect of the present invention, the terminal includes a reception unit and an execution unit. The receiving unit receives application operation data including operation input data for the application and time data indicating a time to apply the operation input data to the application, and comment data associated with the application operation data. The execution unit applies the operation input data to the application at the time indicated by the time data corresponding to the operation input data. The execution unit generates display data including comment data during execution of the application.

  According to another aspect of the present invention, the terminal includes a generation unit and a transmission unit. The generation unit generates a request to add, change, or delete comment data associated with application operation data including operation input data for the application and time data indicating a time for applying the operation input data to the application. The transmission unit transmits a request. The other terminal to which the application operation data and the comment data are distributed applies the operation input data to the application at the time indicated by the time data corresponding to the operation input data. Other terminals generate display data including comment data during execution of the application.

  According to another aspect of the present invention, the server includes a reception unit, a management unit, and a transmission unit. The receiving unit receives a request to add, change, or delete comment data associated with application operation data including operation input data for the application and time data indicating a time to apply the operation input data to the application. The management unit manages comment data in response to a request. The transmission unit transmits comment data. The terminal to which the application operation data and comment data are distributed applies the operation input data to the application at the time indicated by the time data corresponding to the operation input data. The terminal generates display data including comment data during execution of the application.

  The present invention can facilitate sharing of content experiences.

1 is a block diagram illustrating a content experience sharing system according to a first embodiment. The block diagram which illustrates the metadata server of FIG. The block diagram which illustrates the operation data utilization terminal of FIG. The block diagram which illustrates the operation data provision terminal of FIG. 3 is a flowchart illustrating the operation of the metadata server in FIG. The flowchart which illustrates the operation | movement regarding the application operation data and tag data of the operation data utilization terminal of FIG. The flowchart which illustrates the operation | movement regarding the tag data of the operation data provision terminal of FIG. The figure which illustrates the structure of the application operation data shared in the content experience sharing system of FIG. The figure which illustrates the display screen by the display apparatus connected to the operation data utilization terminal of FIG. The flowchart which illustrates the operation | movement regarding the application operation data and comment data of the operation data utilization terminal of FIG.

  Hereinafter, embodiments will be described with reference to the drawings. Hereinafter, elements that are the same as or similar to elements already described are denoted by the same or similar reference numerals, and redundant descriptions are basically omitted. For example, when there are a plurality of identical or similar elements, a common reference may be used to explain each element without distinction, and the common reference may be used to distinguish each element. In addition, branch numbers may be used.

(First embodiment)
As illustrated in FIG. 1, the content experience sharing system according to the first embodiment includes an operation data providing terminal 10, operation data utilization terminals 20-1 and 20-2, an operation data server 30, and metadata. Server 40. 1 are connected to each other via a network and can transmit and receive data to and from each other. The total number of operation data utilization terminals 20 is not limited to 2, and may be 1 or 3 or more. The server configuration shown in FIG. 1 is merely an example, and the functions of one server may be shared by a plurality of devices, or the functions of a plurality of servers may be assigned to one device. A web server (not shown) may also be connected to the network.

  In the content experience sharing system of FIG. 1, the operation data providing terminal 10 provides application operation data, as will be described later. The operation data server 30 distributes the application operation data provided by the operation data providing terminal 10 in response to a distribution request from the operation data utilization terminal 20. Then, the operation data utilization terminal 20 executes an application using the received application operation data.

  The application generates content as at least a part of the execution result. The content is, for example, a moving image, a still image, sound, text, or the like. The application can be, for example, a video game, a questionnaire, a quiz, a drawing software, or the like. The operation data providing terminal 10 and the operation data using terminal 20 execute the same application. The operation data providing terminal 10 generates content according to the user's application operation. The operation data utilization terminal 20 reproduces the same content as the operation data providing terminal 10 using the received application operation data.

  For example, if a plurality of operation data use terminals 20 apply the same application operation data to the same application at approximately the same timing (desirably synchronized, but not required to be synchronized), the operation The user of the data use terminal 20 can share a live broadcast content experience.

  Further, in the content experience sharing system of FIG. 1, the metadata server 40 distributes metadata associated with application operation data in response to a distribution request from the operation data utilization terminal 20. In the following description, “distribution request” may be read as “acquisition request” or other “request”. The metadata is data that can be used to promote a content experience using application operation data, as will be described later.

  The operation data providing terminal 10 provides application operation data to the operation data server 30 as described above. Here, the provision of application operation data means that application operation data can be distributed from the operation data server 30 to the operation data utilization terminal 20. Specifically, the provision of the application operation data may be transmission of the application operation data to the operation data server 30, or sharing of the application operation data stored inside or outside the operation data server 30. It can mean giving explicit or implied instructions to allow. The explicit instruction can be, for example, sending a sharing setting request. The timing for transmitting the application operation data may be in parallel with the operation data providing terminal 10 when the user operates the application (real time), or the accumulated data is stored in the operation data providing terminal 10. You may send it collectively after the application ends.

  Further, the application operation data may be generated by the operation data providing terminal 10, or may be generated by an external device (for example, the operation data server 30) in response to an operation request from the operation data providing terminal 10. .

  As illustrated in FIG. 8, the application operation data includes at least a data set of operation input data for the application and time data indicating a time for applying the operation input data to the application. More specifically, the application operation data includes all operation input data applied to the application from the start of execution (initial state) of the application and time data indicating the time for applying the operation input data.

  Depending on the type of application, the application operation data may include additional data such as a random number seed, for example. The additional data may be data that is useful for improving the reproducibility of the execution result of the application. The reproducibility of the execution result of the application is, for example, how much the execution result when the application operation data is used at a certain point in time is the same as the execution result when the application operation data is used in the future. It can be evaluated by how much the execution result when the application execution device uses the application operation data is the same as the execution result when the other application execution device uses the application operation data.

  The operation data utilization terminal 20 transmits a distribution request for application operation data to the operation data server 30 and transmits a distribution request for metadata associated with the application operation data to the metadata server 40. And the operation data utilization terminal 20 can reproduce | regenerate a content by executing an application using application operation data, and can promote this content experience using metadata. Further, the operation data utilization terminal 20 may transmit a metadata addition (post) / change / deletion request to the metadata server 40.

  For example, in response to a sharing setting request from the operation data providing terminal 10, the operation data server 30 sets application operation data corresponding to the sharing setting request to a sharable state. Then, the operation data server 30 distributes application operation data in response to a distribution request from the operation data providing terminal 10 or the operation data using terminal 20. The operation data server 30 only needs to be able to access at least the application operation data, and the application operation data may be stored in another file server. The operation data server 30 may have a function of generating application operation data.

  The metadata server 40 manages metadata associated with application operation data in response to a request for adding / changing / deleting metadata from the operation data providing terminal 10 or the operation data using terminal 20. Further, the metadata server 40 distributes metadata associated with application operation data in response to a distribution request from the operation data providing terminal 10 or the operation data using terminal 20. The metadata server 40 only needs to be able to access at least the metadata, and the metadata may be stored in another file server.

  Specifically, the metadata can include tag data, period data, comment data, and the like, and can also include authority data regarding addition / change / deletion of these.

  The tag data indicates a random access point set in specific time data included in the application operation data. The random access point is set to allow the application to transit to an execution state corresponding to the time indicated by this specific time data, triggered by a user input to the operation data utilization terminal 20.

  The period data indicates a branchable period. The branchable period means a period during which it is allowed to branch from the middle of the application operation data and generate (branch) another application operation data based on a user input to the operation data utilization terminal 20.

  The comment data is text data that can be displayed when the operation data using terminal 20 is executing an application using the application operation data. The comment data may be displayed so as to overlap the content, or may be displayed in a region different from the content display region.

  The authority data indicates, for example, the authority given to the operation data utilization terminal 20 or the user regarding addition / change / deletion of tag data, period data, or comment data.

Hereinafter, details of the operation data using terminal 20, the operation data providing terminal 10, and the metadata server 40 will be described in order.
The operation data utilization terminal 20 applies the operation input data included in the application operation data to the application at the time indicated by the time data corresponding to the operation input data. Since all the operation data utilization terminals 20 operate in the same manner, the user can enjoy the same execution result, that is, the same content (for example, a play video of a video game).

  The operation data utilization terminal 20 is typically a television receiver (including Internet television), a PC (Personal Computer), a mobile terminal (for example, a tablet, a smartphone, a laptop, a feature phone, a portable game machine, a digital music player). A VR (Virtual Reality) terminal, and an AR (Augmented Reality) terminal, but are not limited thereto.

  The operation data utilization terminal 20 includes a processor that performs execution and control of an application, output control for an output device connected to the operation data utilization terminal 20, generation of various requests (data), communication control, and the like. It includes a program that is executed by the processor and a memory that temporarily stores data and the like used by the processor to realize.

  The operation data utilization terminal 20 further includes a communication device for connecting to a network, an output device for outputting content, an input device for receiving user input, and an auxiliary storage device for storing programs or data. Is available. These communication device, output device, input device, and auxiliary storage device may be built in the operation data utilization terminal 20 or may be externally attached to the operation data utilization terminal 20.

  The communication device communicates with the operation data server 30 and the metadata server 40 via a network. For example, the communication apparatus transmits a distribution request for application operation data to the operation data server 30, transmits a distribution request for metadata or an add / change / delete request to the metadata server 40, Operation data is received or metadata is received from the metadata server 40.

  The output device may include a display device for displaying moving images, still images, text, and / or a speaker for outputting sound, music, and the like. Examples of the display device include a liquid crystal display, an organic EL (electroluminescence) display, and a CRT (Cathode Ray Tube) display. The display device displays display data including content. Note that the display device may have a function of an input device like a touch screen.

  The input device may be, for example, a keyboard, a mouse, a numeric keypad, or the like, or may have a display device function like a touch screen. User input may typically be a tap, a click, a specific key press, and the like. In addition, user input includes, for example, voice captured by a microphone, biological data detected by a biological sensor (for example, body temperature, facial expression, etc.), GPS (Global Positioning System) or position data identified by base station information, an acceleration sensor The user action estimated based on the acceleration data detected by (for example, swung the operation data utilization terminal 20) can also be included.

  The auxiliary storage device stores, for example, a program or data related to the application. The auxiliary storage device is preferably a non-volatile storage medium such as an HDD (Hard Disk Drive) and an SSD (Solid State Drive). The auxiliary storage device may be a file server connected to the operation data utilization terminal 20 via a network.

  Hereinafter, the details of the operation data utilization terminal 20 will be described with reference to FIG. The operation data utilization terminal 20 includes a reception unit 201, an execution unit 202, an output unit 203, an input unit 204, an execution control unit 205, a request generation unit 206, and a transmission unit 207.

  The receiving unit 201 receives application operation data from the operation data server 30 via the network. The receiving unit 201 sends application operation data to the execution unit 202. The receiving unit 201 receives metadata from the metadata server 40 via the network. Also in this case, the receiving unit 201 sends metadata to the execution control unit 205. The receiving unit 201 may be the communication device described above or an interface with the communication device.

  As described above, the application operation data includes at least a data set of operation input data for the application and time data indicating the time to apply the operation input data to the application, and further includes additional data such as a random number seed. obtain.

  Here, when the application operation data is generated every unit time, for example, the time data may be a value obtained by quantizing the elapsed time based on a predetermined timing (for example, execution start of the application) with this unit time. . Specifically, when the content includes a moving image, the frame interval can be regarded as a unit time. In this example, the time data may indicate the number of frames to which the corresponding operation input data is applied.

  The execution unit 202 executes an application. The execution unit 202 receives application operation data from the execution control unit 205, and applies the operation input data included in the application operation data to the application at the time indicated by the time data corresponding to the operation input data. The application generates an execution result according to the applied operation input data. The execution unit 202 sends content (for example, a moving image) included in the execution result to the output unit 203. The execution unit 202 can be the aforementioned processor and memory.

  The execution unit 202 may generate display data including a seek bar that visualizes the position of the time corresponding to the current execution state of the application on the time axis, and may send the display data to the output unit 203. The execution unit 202 may generate display data including a GUI (Graphical User Interface) component that visualizes a random access point indicated by the tag data, and may send the generated display data to the output unit 203. Furthermore, the execution unit 202 may generate display data including comment data associated with application operation data during execution of the application, and send the display data to the output unit 203.

  The output unit 203 receives content (display data and / or audio data) from the execution unit 202 and outputs the content. For example, the output unit 203 displays a moving image, a still image, or text, or outputs a sound or music. The output unit 203 may be the above-described output device or an interface with the output device.

  The input unit 204 receives user input. The input unit 204 sends the user input to the execution control unit 205 or the request generation unit 206. The input unit 204 may be the above-described input device or an interface with the input device.

  Specifically, the user input includes user input relating to application execution control (application operation data application control), user input relating to addition / change / deletion of metadata of application operation data, and distribution of application operation data or metadata thereof. User input, application input (active) operation, etc.

  User input related to application execution control may include user input for selecting a random access point, user input for changing the execution speed of the application, and the like. The input unit 204 sends user input related to the execution state of the application to the execution control unit 205.

  User input for adding / changing / deleting metadata of application operation data is added for adding, changing or deleting random access points indicated by tag data, and adding text data associated with random access points indicated by tag data , User input for changing or deleting, adding (posting) comment data, user input for changing or deleting, and the like. The input unit 204 sends a user input regarding addition / change / deletion of metadata of application operation data to the request generation unit 206.

  The user input related to the distribution of the application operation data or its metadata may be a user input for requesting distribution of the application operation data, a user input for requesting distribution of metadata, or the like.

  The user input regarding the operation of the application may be a user input for actively operating the application while the user of the operation data using terminal 20 takes over the execution state of the application. For example, if the application is a video game, user input may mean operations such as selection, movement, action, state change, etc. of objects (eg, characters, items, backgrounds, etc.) in the game. Then, the user of the operation data utilization terminal 20 branches off from the middle of the game progress by another user (provider of application operation data) (takes over the progress state of the game at that time) and actively plays the game. You can play.

  When there is such user input, the user input may be used (consumed) only for the operation of the subsequent application. However, in order to share the content experience with other users, the user input is used. It is also possible to generate another application operation data by branching from the time when the error occurred. In this case, the application operation data after branching is accumulated on the application operation data before branching. The input unit 204 sends an instruction for operating the application to the execution control unit 205 when the generation subject of the application operation data is the operation data using terminal 20 or when branch generation of the application operation data is not performed. In this case, the request is sent to the request generation unit 206.

  Application branch execution or application operation data branch generation may be uniformly prohibited or conditionally prohibited. For example, a provider of application operation data may think that another user can view his / her game play video, but cannot allow another user to ride in the progress of his / her game. Absent. In such a case, the operation data providing terminal 10 may uniformly prohibit branch execution of the application or branch generation of the application operation data. The fact that branching of application operation data is uniformly prohibited or permitted can be transmitted to the operation data utilization terminal 20 as flag data, for example.

  Further, the provider of application operation data may think that other users may use a limited portion of the game progress state. In such a case, the operation data providing terminal 10 may set a branchable period. The branchable period can be transmitted to the operation data utilization terminal 20 as period data indicating the branchable period, for example.

  The execution control unit 205 receives user input corresponding to an instruction related to application execution control from the input unit 204. The execution control unit 205 controls the execution state of the application by the execution unit 202 based on the user input. The execution control unit 205 can be the aforementioned processor and memory.

  Upon receiving a user input corresponding to an instruction for selecting a random access point, the execution control unit 205 causes the application to transition to an execution state corresponding to the time indicated by the specific time data set for the random access point. The execution unit 202 is instructed.

For example, if the time (t _RAP ) indicated by the specific time data is later than the current time (t), the execution control unit 205 normally sends the operation input data applied from t to t _RAP to the application. The execution unit 202 may be instructed to apply at a higher speed (for example, at a maximum speed that can be set) than (actual time flow). On the other hand, if the time (t _RAP ) indicated by the specific time data is before the current time (t), the execution control unit 205 resets the application to the initial state and is applied from 0 to t _RAP. It is only necessary to instruct the execution unit 202 to apply the operation input data to the application at a higher speed than usual (actual time flow). If the current time (t) is the same as the time (t _RAP ) indicated by the specific time data, the execution control unit 205 does not have to do anything.

  When receiving a user input corresponding to an instruction for changing the execution speed, the execution control unit 205 instructs the execution unit 202 to apply the application operation data to the application at a speed corresponding to the user input. If the execution speed is variable, the user can fast-forward a portion that is not of interest in the content, or can perform slow playback of a portion that the user wants to watch.

  As described above, the execution control unit 205 may receive user input corresponding to an instruction for operating an application from the input unit 204. The execution control unit 205 generates operation input data for the application based on the user input, and provides the operation input data to the execution unit 202. Note that when the operation data utilization terminal 20 is a subject that branches and generates application operation data, the operation data utilization terminal 20 generates application operation data by associating time data with the generated operation input data, which is not illustrated. You may accumulate in storage.

  The request generation unit 206 receives user input regarding addition (posting) / change / deletion of metadata of application operation data from the input unit 204. The request generation unit 206 generates a metadata addition / change / deletion request in response to a user input, and sends the request to the transmission unit 207. The request generation unit 206 can be the aforementioned processor and memory.

  Note that the operation data utilization terminal 20 may be authorized (by the operation data providing terminal 10) to add / change / delete metadata. In this case, the receiving unit 201 can receive authority data indicating the authority given to the operation data using terminal 20. For example, addition, change, or deletion of a random access point is prohibited, but addition, change, or deletion of text data associated with the random access point may be allowed.

  If the user input regarding addition / change / deletion of metadata exceeds the authority, the request generation unit 206 may reject the generation of a request according to the user input. If the request generation unit 206 performs the authority check in this way, it is not necessary to send an unnecessary request.

  Further, the request generation unit 206 receives user input related to distribution of application operation data or metadata thereof from the input unit 204. The request generation unit 206 generates a distribution request for application operation data or metadata in response to a user input, and sends the request to the transmission unit 207.

  The transmission unit 207 receives various requests from the request generation unit 206 and transmits them to the outside via the network. For example, the transmission unit 207 transmits a metadata distribution request and a metadata addition / change / deletion request to the metadata server 40. In addition, the transmission unit 207 transmits a distribution request for application operation data to the operation data server 30. The transmission unit 207 may be the communication device described above or an interface with the communication device.

Hereinafter, an operation example of the operation data utilization terminal 20 related to the application operation data and the tag data will be described with reference to FIG. The start trigger of the operation in FIG. 6 may be that the transmission unit 207 transmits a distribution request for application operation data or tag data, but is not limited thereto.
The receiving unit 201 receives application operation data from the operation data server 30 via the network (step S501). The receiving unit 201 receives tag data from the metadata server 40 via the network (step S502). The execution unit 202 initializes a variable t representing time (for example, the number of frames) (step S503). In addition, the execution order of step S501-step S503 may differ from FIG. After step S501 to step S503, the process proceeds to step S504.

  In step S504, the execution unit 202 refers to the time data included in the application operation data received in step S501, and applies operation input data corresponding to the time data indicating the current time (t) to the application. Then, the output unit 203 outputs the content included in the execution result.

  The user can select a random access point indicated by the tag data received in step S502 at any time during execution of the application. For example, during execution of the application, a screen as shown in FIG. 9 is displayed on the display device built in or externally attached to the operation data utilization terminal 20.

  The display screen of FIG. 9 visualizes the position on the time axis of the time corresponding to the current execution state of the application by the GUI component (slider) 703 in addition to the display area 701 of the content included in the execution result of the application. A seek bar 702 and GUI components (buttons) 705-1 to 705-3 for visualizing random access points indicated by the tag data are included.

  In the display area 701, comment data associated with application operation data may be displayed in addition to the content. In addition, text data (tag) associated with application operation data may be further displayed around the display area 701 (for example, at the top). Tags are mainly used for classifying or associating content included in application execution results, but for content descriptions, jokes, or for communication between users experiencing the same content. It is also assumed that it will be used.

  The GUI components 705-1 to 705-3 are “0:30 stage 1”, “5:00 stage 2”, and “8:00 stage 3” as text data (index tag) associated with the corresponding random access point. Is displayed. This index tag is typically used to let the user know what execution state (content scene) the application can transition to when the GUI component is selected. Sometimes used for jokes or for communication between users experiencing the same content.

  The seek bar 702 includes GUI parts (anchor icons) 704-1 to 704-3 that visualize the positions on the time axis of the time indicated by specific time data in which random access points are set. If there is no user input, the GUI component 703 moves on the seek bar from the left end to the right end as time passes. On the other hand, the GUI parts 704-1 to 704-3 are fixed regardless of the passage of time. The appearance of each GUI component is not limited to that illustrated in FIG. The appearance of each GUI component may be fixed or editable.

  In the example of FIG. 9, upon receiving user input for selecting either the GUI components 704-1 to 704-3 or the GUI components 705-1 to 705-3, the application displays a random access point indicated by the selected GUI component. Transition to the execution state corresponding to the set time.

  If there is a user input for selecting a random access point during time = t, the process proceeds to step S506, and if not, the process proceeds to step S507 (step S505).

In step S506, the execution control unit 205 instructs the execution unit 202 to transition the application to the execution state corresponding to the time (t _RAP ) indicated by the specific time data set for the selected random access point, The process proceeds to step S507 (step S506).

  In step S507, the execution unit 202 increments the variable t by 1, and the process returns to step S504.

  Hereinafter, an operation example of the operation data utilization terminal 20 related to application operation data and comment data will be described with reference to FIG. The start trigger of the operation in FIG. 10 may be that the transmission unit 207 transmits a distribution request for application operation data or comment data, but is not limited thereto. 6 and 10 can be compatible.

  The receiving unit 201 receives application operation data from the operation data server 30 via the network (step S801). The receiving unit 201 receives comment data from the metadata server 40 via the network (step S802). The execution unit 202 initializes a variable t representing time (for example, the number of frames) (step S803). Note that the execution order of steps S801 to S803 may be different from that in FIG. After step S801 to step S803, the process proceeds to step S804.

  In step S804, the execution unit 202 refers to the time data included in the application operation data received in step S801, and applies operation input data corresponding to the time data indicating the current time (t) to the application. Moreover, the execution part 202 produces | generates the display data containing what should be displayed in the present time (t) among the comment data received in step S802 (step S805). For example, the comment data may be displayed on the content display area so as to overlap the content, or may be displayed in a comment-dedicated area. And the output part 203 outputs the content contained in the execution result of an application, and the display data containing comment data.

  After step S804 and step S805, the execution unit 202 increments the variable t by 1, and the process returns to step S804.

  The operation data providing terminal 10 may be any of various devices listed as examples of the operation data utilization terminal 20. That is, the operation data providing terminal 10 can include a processor, a memory, a communication device, an output device, an input device, an auxiliary storage device, and the like, similar to the operation data utilization terminal 20.

  Hereinafter, the details of the operation data providing terminal 10 will be described with reference to FIG. The operation data providing terminal 10 includes a reception unit 301, an execution unit 302, an output unit 303, an input unit 304, an execution control unit 305, a request generation unit 306, and a transmission unit 307.

  The receiving unit 301 receives application operation data from the operation data server 30 via the network. The receiving unit 301 sends application operation data to the execution control unit 305. When the user of the operation data providing terminal 10 adds / changes / deletes metadata such as tag data and period data associated with the application operation data provided by the user, the application is executed using the application operation data. This makes it easy to work while viewing the content.

  Note that the receiving unit 301 may be omitted depending on the execution mode of the application. Specifically, operation input data (or application operation data generated based on the application operation) performed in the local host of the operation data providing terminal 10 is recorded in the auxiliary storage device, and after the application ends. When various data are collectively transmitted to the operation data server 30 or the metadata server 40 according to a user instruction, the receiving unit 301 can be omitted. Alternatively, the operation data providing terminal 10 concentrates on transmitting an operation request for an application or locally generated application operation data (concentrating resources such as a bandwidth and a CPU there), and the operation data using terminal 20 Even when it is desired to realize a synchronous state as much as possible, the receiving unit 301 can be omitted.

  The receiving unit 301 receives metadata from the metadata server 40 via the network. Also in this case, the reception unit 301 sends the metadata to the execution control unit 305. When the user of the operation data providing terminal 10 adds / changes / deletes metadata such as tag data and period data associated with application operation data provided by the user, the currently registered metadata is displayed. , You will be able to work easily.

  The receiving unit 301 may be the communication device described above or an interface with the communication device.

  The execution unit 302 executes an application. The execution unit 302 receives application operation data from the execution control unit 305, and applies the operation input data included in the application operation data to the application at the time indicated by the time data corresponding to the operation input data. The application generates an execution result according to the applied operation input data. The execution unit 302 sends content (for example, a moving image) included in the execution result to the output unit 303. The execution unit 302 may be the aforementioned processor and memory.

  The execution unit 302 may generate display data including a seek bar that visualizes the position on the time axis of the time corresponding to the current execution state of the application, and may send the display data to the output unit 303. By performing user input for adding / changing / deleting a random access point or a branchable period using such a seek bar, the user of the operation data providing terminal 10 can easily add / change / delete tag data or period data. it can.

  The output unit 303 receives content (display data and / or audio data) from the execution unit 302 and outputs the content. For example, the output unit 303 displays a moving image, a still image, or text, and outputs a sound or music. The output unit 303 may be the above-described output device or an interface with the output device.

  The input unit 304 receives user input. The input unit 304 sends the user input to the execution control unit 305 or the request generation unit 306. The input unit 304 may be the above-described input device or an interface with the input device.

  Specifically, the user input includes user input related to application execution control, user input related to addition / change / deletion of metadata of application operation data, user input related to sharing setting / distribution of application operation data or distribution of the metadata. And so on.

  User input relating to application execution control may include user input for changing the execution speed of the application, user input for listing frame images displayed in the vicinity of a specified time point for moving image content, and the like. The input unit 304 sends user input related to the execution state of the application to the execution control unit 305.

  User input for adding / changing / deleting metadata of application operation data is added for adding, changing or deleting random access points indicated by tag data, and adding text data associated with random access points indicated by tag data , User input for changing or deleting, user input for adding, changing or deleting a branchable period, and the like. The input unit 304 sends user input related to addition / change / deletion of metadata of application operation data to the request generation unit 306.

  The user input related to the sharing setting / delivery of application operation data or the delivery of metadata may be a user input for requesting the sharing setting / delivery of application operation data or the delivery of metadata.

  The execution control unit 305 receives user input corresponding to an instruction related to application execution control from the input unit 304. The execution control unit 305 controls the execution state of the application by the execution unit 302 based on the user input. The execution control unit 305 may be the aforementioned processor and memory.

  Upon receiving a user input corresponding to an instruction for changing the execution speed, the execution control unit 305 instructs the execution unit 302 to apply the application operation data to the application at a speed corresponding to the user input. If the execution speed is variable, the user can perform slow playback near the time point at which a random access point or the start point or end point of a branchable period is to be set, or can fast forward other parts.

  Upon receiving a user input for listing the frame images displayed near the time point specified for the moving image content, the execution control unit 305, for example, within a predetermined time before and after the currently displayed frame image The execution unit 302 is controlled so as to generate display data in which displayed frame images are arranged in chronological order and listed. Thereby, the user of the operation data providing terminal 10 can set a random access point or a start point or an end point of a branchable period while looking down on a nearby frame image.

  The request generation unit 306 receives user input related to addition / change / deletion of metadata of application operation data from the input unit 304. The request generation unit 306 generates a metadata addition / change / deletion request in response to a user input, and sends the request to the transmission unit 307. The request generation unit 306 can be the aforementioned processor and memory.

  Note that the metadata that can be used by the operation data utilization terminal 20 (or its user) may be set differently between the operation data utilization terminals 20 (or their users). For example, the random access point or the branchable period that can be selected by the operation data utilization terminal 20-1 (or its user) may be different from the one that can be selected by the operation data utilization terminal 20-2 (or its user). .

  In addition, the request generation unit 306 receives user input related to sharing setting / distribution of application operation data or distribution of metadata from the input unit 304. The request generation unit 306 generates an application operation data sharing setting / distribution request or a metadata distribution request in response to a user input, and sends the request to the transmission unit 307.

  The transmission unit 307 receives various requests from the request generation unit 306 and transmits them to the outside via the network. For example, the transmission unit 307 transmits an application operation data sharing setting / distribution request to the operation data server 30. The transmission unit 307 also transmits a metadata distribution request and a metadata addition / change / deletion request to the metadata server 40. The transmission unit 307 may be the communication device described above or an interface with the communication device.

  Hereinafter, an operation example of the operation data providing terminal 10 related to addition of tag data will be described with reference to FIG. For example, addition of other metadata such as period data, and change and deletion of metadata can also be realized by a similar operation.

  The input unit 304 receives user input designating a random access point (step S601). Such user input may be an input for designating a time for setting a random access point by a numerical value, an input for selecting a position on a seek bar corresponding to the time for setting a random access point, It may be an input for selecting a frame image corresponding to a time for setting a random access point from the frame images listed by the user input.

  The request generation unit 306 generates a tag data addition request based on the user input accepted in step S601 (step S602). The transmission unit 307 transmits the addition request generated in step S602 to the metadata server 40 (step S603).

  The metadata server 40 is a server computer, a processor that performs management (addition / change / deletion / distribution) and communication control of metadata, a program executed by the processor to realize such processing, and the And a memory for temporarily storing data used by the processor.

  The metadata server 40 can further use a communication device for connecting to a network and an auxiliary storage device for accumulating a large amount of data. The communication device and the auxiliary storage device may be built in the metadata server 40 or may be externally attached to the metadata server 40.

  The communication device communicates with the operation data providing terminal 10 or the operation data using terminal 20 via the network. For example, the communication device distributes metadata to the operation data providing terminal 10 or the operation data using terminal 20, or requests addition / change / deletion of metadata or metadata from the operation data providing terminal 10 or the operation data using terminal 20. Receive delivery requests.

  The auxiliary storage device stores, for example, metadata managed by the metadata server 40. The auxiliary storage device is preferably a non-volatile storage medium such as an HDD or an SSD. The auxiliary storage device may be a file server connected to the metadata server 40 via a network.

  The details of the metadata server 40 will be described below with reference to FIG. The metadata server 40 includes a reception unit 101, a metadata management unit 102, a storage unit 103, and a transmission unit 104.

  The receiving unit 101 receives a metadata addition / change / deletion request or a metadata distribution request from the operation data providing terminal 10 or the operation data using terminal 20 via the network. The reception unit 201 sends a metadata addition / change / deletion request or a metadata distribution request to the metadata management unit 102. The receiving unit 101 may be the communication device described above or an interface with the communication device.

  The metadata management unit 102 reads / writes metadata from / to the storage unit 103 in response to a request received from the receiving unit 101. The metadata management unit 102 can be the aforementioned processor and memory.

  When the metadata management unit 102 receives a metadata addition request from the reception unit 101, the metadata management unit 102 adds metadata associated with the application operation data based on the addition request and stores the metadata in the storage unit 103. The request for adding metadata may include an identifier of a requesting user, an identifier of application operation data, and metadata requesting addition.

  When the metadata management unit 102 receives a metadata change request from the receiving unit 101, the metadata management unit 102 changes the metadata associated with the application operation data based on the change request and stores the metadata in the storage unit 103. The metadata change request may include an identifier of the requesting user, an identifier of the application operation data, an identifier of the metadata requesting the change, and the metadata after the change.

  When the metadata management unit 102 receives a metadata deletion request from the reception unit 101, the metadata management unit 102 deletes metadata associated with application operation data from the storage unit 103 based on the deletion request. The metadata deletion request may include an identifier of a requesting user, an identifier of application operation data, and an identifier of metadata requesting deletion.

  Note that the metadata management unit 102 may check the authority of the request before executing the request for adding / changing / deleting metadata. Specifically, the metadata management unit 102 may read authority data related to the identifier of the requesting user included in the request from the storage unit 103, and may reject the request if the request exceeds the authority.

  When the metadata management unit 102 receives a metadata distribution request from the reception unit 101, the metadata management unit 102 reads the metadata associated with the application operation data based on the distribution request from the storage unit 103 and sends the metadata to the transmission unit 104. The metadata distribution request may include an identifier of a requesting user and an identifier of application operation data.

  The storage unit 103 stores the metadata written (added or changed) by the metadata management unit 102. The storage unit 103 may be the above-described auxiliary storage device or an interface with the auxiliary storage device.

  The transmission unit 104 receives metadata from the metadata management unit 102. The transmission unit 104 transmits the metadata to the operation data providing terminal 10 or the operation data using terminal 20 via the network. The transmission unit 104 may be the communication device described above or an interface with the communication device.

Hereinafter, an operation example of the metadata server 40 will be described with reference to FIG.
The receiving unit 101 waits for a metadata addition / change / deletion request and a metadata distribution request. When the reception unit 101 receives a request for adding / changing / deleting metadata, the process proceeds to step S402 (step S401). On the other hand, when the receiving unit 101 receives a request to add / change / delete metadata, the process proceeds to step S404 (step S403).

  In step S402, the metadata management unit 102 executes the received metadata addition / change / deletion request. Specifically, the metadata management unit 102 saves new metadata in the storage unit 103, changes metadata stored in the storage unit 103, and metadata stored in the storage unit 103. Or delete.

  In step S <b> 404, the metadata management unit 102 reads from the storage unit 103 metadata associated with the application operation data (identifier thereof) that is the target of the distribution request. Then, the metadata management unit 102 transmits the metadata read in step S404 to the operation data utilization terminal 20 that is the transmission source of the distribution request (step S405).

  As described above, in the content experience sharing system according to the first embodiment, the operation data server distributes application operation data to the operation data utilization terminal. Each of the operation data utilization terminals applies the operation input data included in the application operation data to the application at the time indicated by the time data corresponding to the operation input data, thereby allowing the content experience included in the application execution result to the user. provide. Furthermore, in this content experience sharing system, the metadata server distributes the metadata to the operation data utilization terminal. Therefore, according to this content experience sharing system, sharing of content experiences using application operation data can be promoted.

  Specifically, the metadata may include tag data indicating a random access point. In this case, the user of the operation data using terminal can jump immediately to the scene he / she desires without having to view all the content from the beginning. Since the provider or user of the application operation data can set the display place of the content, sharing of the content experience can be promoted.

  The metadata may include comment data that is text data that can be displayed during execution of the application. In this case, the user of the operation data using terminal can write comments data to inform other users or application operation data providers of their opinions or opinions about the content, or browse the displayed comment data. It is possible to enjoy comments or opinions from other users' contents or comments from the provider of application operation data.

  The above-described embodiments are merely specific examples for helping understanding of the concept of the present invention, and are not intended to limit the scope of the present invention. The embodiment can add, delete, or convert various components without departing from the gist of the present invention.

  The various functional units described in the above embodiments may be realized by using a circuit. The circuit may be a dedicated circuit that realizes a specific function, or may be a general-purpose circuit such as a processor.

  At least a part of the processing of each of the above embodiments can also be realized by using a general-purpose computer as basic hardware. A program for realizing the above processing may be provided by being stored in a computer-readable recording medium. The program is stored in the recording medium as an installable file or an executable file. Examples of the recording medium include a magnetic disk, an optical disk (CD-ROM, CD-R, DVD, etc.), a magneto-optical disk (MO, etc.), and a semiconductor memory. The recording medium may be any recording medium as long as it can store the program and can be read by the computer. The program for realizing the above processing may be stored on a computer (server) connected to a network such as the Internet and downloaded to the computer (client) via the network.

DESCRIPTION OF SYMBOLS 10 ... Operation data provision terminal 20 ... Operation data utilization terminal 30 ... Operation data server 40 ... Metadata server 101, 201, 301 ... Reception part 102 ... Metadata management part 103- .. Storage unit 104, 207, 307 ... Transmission unit 202, 302 ... Execution unit 203, 303 ... Output unit 204, 304 ... Input unit 205, 305 ... Execution control unit 206, 306 ... request generation unit 701 ... display area 702 ... seek bar 703, 704, 705 ... GUI parts

Claims (9)

A terminal,
Tag indicating application operation data including operation input data for application and time data indicating time to apply the operation input data to the application, and a random access point set in specific time data included in the application operation data A receiving unit for receiving data;
An execution unit that applies the operation input data to the application at a time indicated by time data corresponding to the operation input data; and
The execution unit causes the application to transition to an execution state corresponding to a time indicated by the specific time data, triggered by a user input for selecting the random access point ,
The receiving unit further receives authority data indicating authority given to the terminal or a user of the terminal regarding addition, change or deletion of the tag data;
Terminal. A terminal,
Tag indicating application operation data including operation input data for application and time data indicating time to apply the operation input data to the application, and a random access point set in specific time data included in the application operation data A receiving unit for receiving data;
An execution unit that applies the operation input data to the application at a time indicated by time data corresponding to the operation input data; and
The execution unit causes the application to transition to an execution state corresponding to a time indicated by the specific time data, triggered by a user input for selecting the random access point ,
The receiving unit further receives period data indicating a branchable period in which branching from the middle of the application operation data and generation of another application operation data based on user input to the terminal are permitted.
Terminal. The execution unit generates display data including a seek bar for visualizing a position on a time axis of a time corresponding to a current execution state of the application operation data,
The seek bar includes a GUI (Graphical User Interface) part that visualizes a position on a time axis of time indicated by the specific time data.
The terminal according to claim 1 or 2 . The terminal according to claim 2 , wherein the branchable period can be set to be different between the terminal or a user of the terminal and another terminal or the user of the other terminal. The terminal according to any one of claims 1 to 4 , wherein the execution unit is capable of changing a speed at which the application operation data is applied to the application. A terminal,
Add, change, or change tag data indicating a random access point set in specific time data included in application operation data including operation input data for an application and time data indicating a time for applying the operation input data to the application A generation unit for generating a request to be deleted;
A transmission unit for transmitting the request,
The other terminal to which the application operation data and the tag data are distributed applies the operation input data to the application at a time indicated by time data corresponding to the operation input data,
The other terminal causes the application to transition to an execution state corresponding to a time indicated by the specific time data, triggered by a user input for selecting the random access point ,
The generation unit further generates a request to add, change, or delete authority data indicating authority given to the other terminal or a user of the other terminal regarding addition, change, or deletion of the tag data, and the transmission Part further sends the request,
Terminal. A terminal,
Add, change, or change tag data indicating a random access point set in specific time data included in application operation data including operation input data for an application and time data indicating a time for applying the operation input data to the application A generation unit for generating a request to be deleted;
A transmission unit for transmitting the request,
The other terminal to which the application operation data and the tag data are distributed applies the operation input data to the application at a time indicated by time data corresponding to the operation input data,
The other terminal causes the application to transition to an execution state corresponding to a time indicated by the specific time data, triggered by a user input for selecting the random access point ,
The generation unit further adds or changes period data indicating a branchable period during which branching from the middle of the application operation data and generation of another application operation data based on user input to the other terminal are allowed Alternatively, a request to delete is generated, and the transmission unit further transmits the request.
Terminal. Add, change, or change tag data indicating a random access point set in specific time data included in application operation data including operation input data for an application and time data indicating a time for applying the operation input data to the application A receiver for receiving a request to be deleted;
A management unit for managing the tag data in response to the request;
A transmission unit for transmitting the tag data,
The terminal to which the application operation data and the tag data are distributed applies the operation input data to the application at a time indicated by time data corresponding to the operation input data.
The terminal causes the application to transition to an execution state corresponding to a time indicated by the specific time data, triggered by a user input for selecting the random access point ,
The management unit refers to authority data indicating authority given to a terminal that is a transmission source of the request or a user of the terminal regarding addition, change, or deletion of the tag data, and the request exceeds the authority. If the request is rejected,
server. Add, change, or change tag data indicating a random access point set in specific time data included in application operation data including operation input data for an application and time data indicating a time for applying the operation input data to the application A receiver for receiving a request to be deleted;
A management unit for managing the tag data in response to the request;
A transmission unit for transmitting the tag data,
The terminal to which the application operation data and the tag data are distributed applies the operation input data to the application at a time indicated by time data corresponding to the operation input data.
The terminal causes the application to transition to an execution state corresponding to a time indicated by the specific time data, triggered by a user input for selecting the random access point ,
The transmission unit further transmits period data indicating a branchable period in which branching from the middle of the application operation data and generation of another application operation data based on user input to the terminal are allowed,
server.