JP7823971B2 - Regeneration control system and regeneration control program - Google Patents

Description

The present invention relates to a playback control system and a playback control program.

Conventionally, while watching content such as videos on a device such as a PC (personal computer), viewing can be interrupted by disturbances such as notifications from a smartphone application (hereinafter also referred to as an "app"), causing the user to miss scenes. For example, while running the YouTube (registered trademark) web app in a PC web browser to watch a video, a notification may be received from a smartphone calling app, causing the user to miss an important scene while answering the call.

If the system can detect when a program has been missed and save the playback position of the video at that time, when the user finishes using their smartphone and returns to watching, the system can automatically rewind the video to the playback position at the time the program was missed, without the user having to operate the PC.

Several techniques have been proposed for estimating the occurrence of missed programs, including capturing images of users with a camera to estimate their situation. For example, Non-Patent Document 1 captures the state of a user's face with an LED camera and estimates their level of interest in the content they are viewing. If the moment when interest level drops is replaced with the time when the missed program occurred, this can be applied to estimating the occurrence of missed programs.

C. Dickie, R. Vertegaal, C. Sohn, and D. Cheng, "eyeLook: using attention to facilitate mobile media consumption," Proceedings of the 18th annual ACM symposium on User interface software and technology, Seattle WA USA, pp.103-106, Oct. 2005.

However, Non-Patent Document 1 requires special equipment such as an LED camera. Furthermore, not only Non-Patent Document 1 but generally any method of continuously capturing a user's state with a camera places a psychological burden on the user. Furthermore, since the user's face must remain within the camera's field of view, this places physical constraints on the user. Therefore, the present invention aims to make it easier to deal with content oversight.

A playback control system according to one embodiment of the present invention is a playback control system including an operation device and a playback device. The operation device includes a monitoring unit that, when a user operates the operation device, notifies the playback device of the status of the operation. The playback device includes a missed content estimation unit that estimates whether the user has missed content due to operation of the operation device, and a playback management unit that, when it is estimated that the user has missed the content, restarts playback of the content from the start time of operation of the operation device.

The present invention makes it possible to control content playback.

1 is a diagram showing an overall configuration according to an embodiment of the present invention; FIG. 2 is a functional block diagram of an operation device and a playback device according to an embodiment of the present invention. 1 is an example of implementation of an operation device and a playback device according to an embodiment of the present invention. 10 is an example of implementation code of a monitoring service according to an embodiment of the present invention. FIG. 4 is a sequence diagram of playback control according to an embodiment of the present invention. FIG. 2 is a diagram illustrating the hardware configuration of an operation device and a playback device according to an embodiment of the present invention.

The following describes an embodiment of the present invention based on the drawings.

<Terminology>
In this specification, "content" refers to content that changes over time, such as video (which may or may not include sound), music, and voice.

<Overall structure>
1 is a diagram showing the overall configuration of an embodiment of the present invention. A playback control system 30 includes an operation device 10 and a playback device 20. The operation device 10 and the playback device 20 are connected to each other so as to be able to communicate with each other via an arbitrary network.

The operation device 10 is a device that the user operates while watching content played by the playback device 20. For example, the operation device 10 is a smartphone, but is not limited to this. When the user operates the operation device 10, the operation device 10 notifies the playback device 20 of the operation status.

The playback device 20 is a device that plays back content. For example, the playback device 20 is a PC (personal computer), but is not limited to this. The playback device 20 estimates whether the user has missed the content due to the operation of the operation device 10, and if it estimates that the user has missed the content, it replays the content from the start time of the operation of the operation device 10 (i.e., it rewinds the content to the start time of the operation of the operation device 10 and plays it back).

Note that although Figure 1 illustrates an example in which the operation device 10 and the playback device 20 are implemented as separate devices, the operation device 10 and the playback device 20 may also be implemented as a single device.

<Function block>
2 is a functional block diagram of the operation device 10 and the playback device 20 according to an embodiment of the present invention. Note that a server may be configured to implement part of the functions of the operation device 10 and the playback device 20 (in this case, the server manages the operation device and the playback device in association with each other).

[Operation device]
The operation device 10 can include a notification sending unit 101, a notification receiving unit 102, a notification monitoring unit 103, and an operation monitoring unit 104. Furthermore, by executing a program, the operation device 10 can function as the notification sending unit 101, the notification receiving unit 102, the notification monitoring unit 103, and the operation monitoring unit 104. The notification monitoring unit 103 and the operation monitoring unit 104 are collectively referred to as a "monitoring unit."

The notification sending unit 101 sends notifications (for example, notifications of incoming calls in a calling app). Note that there may be multiple notification sending units 101. Notifications are assigned a level of importance according to the urgency of the notification.

The notification receiving unit 102 receives notifications. The user operates the operation device 10 in accordance with the notifications displayed on the screen by the notification receiving unit 102. The notification receiving unit 102 also provides an interface for notifying the notification monitoring unit 103 of the information in the received notifications.

When the user operates the operation device 10 (for example, when the screen of the operation device is turned on by unlocking, etc., it is considered that the user has started operation), the monitoring unit (notification monitoring unit 103 and operation monitoring unit 104) notifies the playback device 20 of the operation status (for example, at least one of the name of the application operated by the user, the importance of the notification from the application, the time until the user starts operating the operation device 10, and the time spent by the user operating the operation device 10).

The notification monitoring unit 103 detects that the notification receiving unit 102 has received a notification, and uses the interface provided by the notification receiving unit 102 to obtain the notification reception time (i.e., the time the notification receiving unit 102 received the notification), the name of the notification sender (i.e., the name of the notification sending unit 101 (e.g., an application)), and the importance of the notification (i.e., the importance set for the notification received by the notification receiving unit 102).

The operation monitoring unit 104 detects the start of a user's operation of the operation device 10, which occurs when a notification is generated. The operation monitoring unit 104 also acquires the operation start time (i.e., the time when the user starts operating the operation device 10). The operation monitoring unit 104 also detects the end of the operation. The operation monitoring unit 104 also acquires the operation end time (i.e., the time when the user ends the operation of the operation device 10). The operation monitoring unit 104 also notifies the playback device 20 (missed broadcast estimation unit 204) of information about the operation start time and operation end time.

[Playback devices]
The playback device 20 can include a web browser 201, a content player 202, a playback management unit 203, and a missed program estimation unit 204. Furthermore, the playback device 20 can function as the web browser 201, the content player 202, the playback management unit 203, and the missed program estimation unit 204 by executing a program.

The web browser 201 retrieves and executes web applications, including content players, from the cloud, etc.

The content player (e.g., video player) 202 plays content (e.g., videos). The content player 202 is deployed on a web application.

Note that while this specification has described an example of playing content on a web app, content may also be played on a native app. In this case, the native app provides an interface that allows information about the content currently being played to be obtained externally, and is able to play the content specified through the interface. It also provides an interface that allows information about the current playback position (e.g., xx seconds from the beginning of the video) to be obtained externally, and is able to play the content from the playback position specified through the interface.

The playback management unit 203 manages and controls the web browser 201 and the content player 202 (specifically, if it is estimated that the user has missed the content, it replays the content from the start time of operation of the operation device 10. Note that the playback management unit 203 may replay the content after receiving an instruction from the user as to whether or not to replay the content). The playback management unit 203 acquires the playback status of the content by the content player 202. The playback management unit 203 also notifies the missed playback estimation unit 204 of the playback status of the content.

The missed content estimation unit 204 calculates the probability that the user has missed the content (hereinafter also referred to as the missed content occurrence probability) based on information obtained from the operation monitoring unit 104 of the operation device 10 and the playback management unit 203 of the playback device 20. In other words, the missed content estimation unit 204 estimates whether the user has missed the content due to operation of the operation device 10 (specifically, it calculates the probability that the user has missed the content based on the operation status, and if the probability is equal to or greater than a threshold, it estimates that the user has missed the content). The missed content estimation unit 204 has a server function for receiving information notifications from the playback management unit 203.

[Calculating the probability of a missed call]
Here, the calculation of the probability of an undetected error will be described.

When the probability of a missed program occurring is y, each variable is x _i , and the weight of each variable is _wi , the probability of a missed program occurring is determined by the following formula (1). When the value of y exceeds a threshold T that is determined in advance for each device, rewinding is performed. The value of the threshold T depends on the type of playback device 20. The specific value depends on the implementation.

The following values are used for the variable x _i . The specific method for determining the value of x _i depends on the implementation.

Name of notification sender: Notifications from a specific notification sender (e.g., a calling app on a smartphone) may have a high ability to bind the user.
Notification importance: If the notification has high importance, it may have a high ability to restrain the user.
The time from when the notification receiving unit 102 receives the notification until when the user starts operating the operation device 10: If this time is short, there is a possibility that the user has not made preparations in case of missing the content.
The time spent by the user operating the operation device 10: If this time is long, the user may have been tied up for a long time and may not have been able to track the playback status of the content.

In other words, the missed-view estimation unit 204 determines that there is a high probability that the user has missed the content if the application name is the name of a specific application. Furthermore, the missed-view estimation unit 204 determines that the higher the importance of the notification from the application, the higher the probability that the user has missed the content. Furthermore, the missed-view estimation unit 204 determines that there is a high probability that the user has missed the content the shorter the time it takes for the user to start operating the operation device 10. Furthermore, the missed-view estimation unit 204 determines that there is a high probability that the user has missed the content the longer the time the user spends operating the operation device 10.

[Device-specific settings]
The threshold used to estimate whether a user has missed content (i.e., the threshold to compare with the probability that the user has missed the content) may be determined for each device (e.g., for each playback device, for each operation device) or for each user.

<Example>
3 shows an example of implementation of the operation device 10 and the playback device 20 according to an embodiment of the present invention. A smartphone (Android (registered trademark)) 11 functions as the operation device 10, and a PC (Linux (registered trademark) OS (Operating System)) 21 functions as the playback device 20. The PC 21 obtains a YouTube web application 260 from the cloud and runs it in a web browser.

[Smartphone (Android)]
The smartphone (Android) 11 can include a native application 110, an OS (notification receiving function) 120, and a monitoring service 150 (notification monitoring function 130 and screen ON/OFF monitoring function 140).

The native application 110 is an arbitrary native application. The native application 110 performs the function of the notification sending unit 101. The native application 110 sends notifications to the OS using the Android notification API. Android provides four values for the importance of each notification: "NotificationManager.IMPORTANCE_HIGH"
"NotificationManager.IMPORTANCE_DEFAULT"
"NotificationManager.IMPORTANCE_LOW"
"NotificationManager.IMPORTANCE_MIN"
In this embodiment, this value is used as the importance of the notification.

OS (notification receiving function) 120 is a function provided by the Android OS that receives notifications from the native application 110. OS (notification receiving function) 120 performs the functions of the notification receiving unit 102.

The monitoring service 150 is a function that runs continuously while Android is powered on. In Android, it is called a Foreground Service. The monitoring service 150 implements the functions of the notification monitoring unit 103 and the operation monitoring unit 104. The monitoring service 150 also notifies the playback device 20 (PC 21) of the information obtained by each function. Figure 4 shows an example of implementation code for the monitoring service according to one embodiment of the present invention.

The Android OS provides APIs related to notifications, and the notification monitoring function 130 can use these to obtain information about notifications sent by the native application 110.

The notification monitoring function 130 obtains information about notifications received by the OS (notification receiving function) 120 (the time the notification was received, the name of the app that sent the notification, and the importance of the notification).

Whether the operating device 10 is being operated is determined by whether the smartphone screen is on or off. When the screen is on, it is determined that the device is being operated, and when the screen is off, it is determined that the device is not being operated. The screen on/off monitoring function 140 makes this determination.

The screen ON/OFF monitoring function 140 detects (1) a screen unlock event (i.e., the screen turns ON) caused by a user operation, and (2) a subsequent screen OFF event (i.e., the screen turns OFF), and obtains the time at which each event occurred.

Websocket is used for communication between the operation device 10 and the playback device 20. The playback device 20 functions as a websocket server and client, and the operation device 10 functions as a websocket client.

[PC]
The PC 21 can include a web browser 210, a video player 220, and a Python (registered trademark) execution environment 250 (playback management.py 230 and missed program estimation.py 240).

The web browser (e.g., Google Chrome (registered trademark)) 210 retrieves and executes the web app and video player from the cloud.

Video player 220 is a video player that runs on the YouTube web application 260.

PlaybackManagement.py 230 performs the functions of the playback management unit 203. Specifically, playbackManagement.py 230 operates Google Chrome 210 and video player 220. PlaybackManagement.py 230 obtains the URL (Uniform Resource Locator) of the video being accessed by Google Chrome 210 and the playback position of the video being played by video player 220. PlaybackManagement.py 230 also specifies and controls the video to be played and the playback position. It is actually a Python program executed in a Python execution environment. Selenium Chrome Driver is used to operate Google Chrome 210.

You can specify the video to play by adding the desired video ID to the URL query parameters when accessing the URL in Google Chrome 210.

The playback position is specified by manipulating the DOM (Document Object Model) of the YouTube web application 260 and specifying the playback position of the video player 220.

Missed event estimation.py 240 performs the functions of the missed event estimation unit 204. Missed event estimation.py 240 receives the notification reception time, the name of the application sending the notification, the importance of the notification, the time from notification reception to the start of operation, and the operation duration from the monitoring service 150, and calculates the probability of a missed event based on these values. Missed event estimation.py 240 also functions as a web socket server, accepting web socket connections and data transmissions from the monitoring service 150. It is actually a Python program executed in a Python execution environment.

[Example of calculation of probability of oversight occurrence]
Here, an example of calculation of the probability of an undetected error will be described.

The probability of a false negative occurring, y, is determined by equation (1). Note that the value range of y is (0 <= y <= 1) due to the domain of definition of each variable described below.

The value of vector x is determined by equation (2). Here, x_{package_name} is a value determined by the name of the app that sent the notification, x_{importance} is a value determined by the importance of the notification, x_{overlook} is a value determined by the time from receiving the notification to starting the operation, and x_{use} is a value determined by the duration of the operation.

The value of each weight is determined using equation (3). Here, w_{package_name} is the weight of the name of the notification sending app, w_{importance} is the weight of the notification importance, w_{overlook} is the weight of the time from receiving the notification to starting the operation, and w_{use} is the weight of the operation duration. Note that weights may be determined for each device (e.g., for each playback device or operation device) or for each user (e.g., determined by machine learning).

The value of x_{package_name} is determined using formula (4). If the notification source app is a specific app, it is set to 1; otherwise, it is set to 0. Here, notification source apps with a value of 1 are assumed to be calling apps, etc.

The value of x_{importance} is determined using equation (5). Set a value that corresponds to each Android notification importance value.

The value of x_{overlook} is determined using formula (6). Let x be the number of seconds from receiving the notification to the start of the operation, and in the range (0 < x < 10), the value decreases linearly and monotonically, and in the range (x >= 10), the value is set to 0.

The value of x_{stay} is determined using equation (7). Let x be the number of seconds from the start of the operation, and the value increases linearly and monotonically in the range (0 < x < 30), and is set to 1 in the range (x >= 30).

The threshold is set to 0.8, and rewinding is performed when the probability of a missed program occurring is greater than the threshold. The threshold value can be set for each playback device 20.

Below are specific examples of calculations for the probability of a missed broadcast assuming [Case 1: Notification from a calling app] and [Case 2: Notification from a news app]. Note that rewinding will be performed if the probability of a missed broadcast is 0.8 or higher.

[Case 1: Notification from a calling app]
Notification sender is a calling app ( x_{package_name} = 1)
The notification's importance is "urgent" (= NotificationManager.IMPORTANCE_HIGH)
Time from receiving a notification to turning on the smartphone screen: 5 seconds Talk time: 60 seconds
Since y = 0.5 * 1 + 0.25 * 1 + 0.125 * (10-5) / 10 + 0.125 * 1 = 0.9375 > 0.8, rewinding is performed.

[Case 2: Notification from a news app]
Notification sender is a news app ( x_{package_name} = 0)
Notification importance is "normal" (= NotificationManager.IMPORTANCE_DEFAULT)
Time from receiving a notification to turning on the smartphone screen: 10 seconds Screen viewing time: 5 seconds
Since y = 0.5 * 0 + 0.25 * 0.66 + 0.125 * 0 + 0.125 * 0.167 = 0.18588 < 0.8, rewinding is not performed.

<Processing method>
5 is a sequence diagram of a playback control process according to an embodiment of the present invention. It is assumed that a YouTube web application is running on Google Chrome 210 and a video is being played. It is assumed that a monitoring service is running on the operation device 10 and a websocket connection is established between the monitoring service and the missed program estimation 240.

<<Receive notifications>>
One of the native applications 110 sends a notification. The OS 120 receives the notification and broadcasts that the notification has been received. The notification monitoring function 130 detects the broadcast and acquires {notifying application name, notification reception time, notification importance} from the OS 120. The notification monitoring function 130 then notifies the screen ON/OFF monitoring function 140 of the notification reception time. The notification reception time is used as an ID to identify the notification event. Note that if another application sent a notification and the OS received the notification before the user started an operation, the notification information acquired here is overwritten with the information of the newly received notification. Each step is explained below.

In step 11 (S11), the native app 110 sends a notification to the Android OS 120.

In step 12 (S12), Android OS 120 notifies notification monitoring function 130 of the notifying app name (i.e., the name of native app 110), the notification reception time (i.e., the time when Android OS 120 received the notification), and the notification importance (i.e., the importance set for the notification received by Android OS 120).

In step 13 (S13), the notification monitoring function 130 notifies the screen ON/OFF monitoring function 140 of the event ID (notification reception time).

<<Operation start detection>>
When the user receives the notification, unlocks the smartphone screen, and turns the screen on, the OS 120 detects this event. The OS 120 then broadcasts the occurrence of this event. The screen ON/OFF monitoring function 140 detects the broadcast and obtains the {operation start time} from the OS 120. The screen ON/OFF monitoring function 140 then notifies the missed program estimation 240 of the playback device 20 that the user has started operating the operation device 10 and the notification reception time as an event ID. In the playback device 20, the missed program estimation 240 notifies the playback management 230 that operation of the operation device 10 has started. In response, the playback management 230 obtains the URL of the video page opened by Google Chrome 210 to obtain the video currently being played. The playback management 230 also obtains the current video playback position from the video player 220. This value is used as the target position for rewinding the video if a video rewind operation is required later. Each step is described below.

In step 21 (S21), the Android OS 120 notifies the screen ON/OFF monitoring function 140 of the operation start time.

In step 22 (S22), the screen ON/OFF monitoring function 140 notifies the missed event estimation function 240 of the event ID (notification reception time).

In step 23 (S23), the missed program estimation 240 notifies the playback management 230 of the start of operation of the operation device 10.

In step 24 (S24), the playback management 230 requests the URL of the video being played from Google Chrome 210.

In step 25 (S25), the playback management 230 requests the playback position of the video from the video player 220.

<<Operation completion detection>>
When the user finishes the operation and turns off the screen, the OS 120 detects this event. The OS 120 then broadcasts the occurrence of this event. The screen ON/OFF monitoring function 140 detects the broadcast and obtains the {operation end time} from the OS 120. The screen ON/OFF monitoring function 140 then notifies the missed program estimation 240 of the playback device 20 of the {notifying app name, notification reception time, notification importance} obtained and saved in the <<Notification reception>> step, the {time until operation start (i.e., the time from notification reception to operation start)} calculated from the notification reception time and operation start time, and the {operation duration (i.e., operation duration)} calculated from the operation end time and operation start time. Each step will be described below.

In step 31 (S31), the Android OS 120 notifies the screen ON/OFF monitoring function 140 of the operation end time.

In step 32 (S32), the screen ON/OFF monitoring function 140 notifies the missed event estimation 240 of the event ID (notification reception time), notifying app name, notification importance, time until operation start, and operation time.

<<Rewind operation>>
The missed program estimation 240 calculates the missed program occurrence probability. If the value of the missed program occurrence probability exceeds a predetermined threshold T, the Google Chrome 210 and the video player 220 are operated to rewind the video. Each step will be described below.

In step 41 (S41), the missed event estimation 240 calculates the probability of a missed event occurring.

In step 42 (S42), the missed program estimation 240 notifies the playback management 230 that a missed program has occurred.

In step 43 (S43), the playback management 230 requests Google Chrome 210 to play the video from the playback position at the start of the operation.

<Effects>
In one embodiment of the present invention, even if viewing of a video is interrupted by operating an operating device, when the user finishes operating the operating device and returns to viewing the video, the system can automatically rewind the video to the playback point at the time the missed portion occurred, without the user having to operate the playback device.

<Hardware configuration>
FIG. 6 is a diagram showing the hardware configuration of the operation device 10 and the playback device 20 according to an embodiment of the present invention.

The operation device 10 and the playback device 20 each have a CPU (Central Processing Unit) 1, ROM (Read Only Memory) 2, and RAM (Random Access Memory) 3. The CPU 1, ROM 2, and RAM 3 form a so-called computer. The operation device 10 and the playback device 20 may also have an auxiliary storage device 4, a display device 5, an operation device 6, an I/F (Interface) device 7, and a drive device 8. The hardware components of the operation device 10 and the playback device 20 are connected to each other via a bus B.

CPU1 is a computing device that executes various programs installed in the auxiliary storage device 4.

ROM2 is non-volatile memory. ROM2 functions as a primary storage device that stores various programs and data necessary for CPU1 to execute the various programs installed in auxiliary storage device 4. Specifically, ROM2 functions as a primary storage device that stores boot programs such as BIOS (Basic Input/Output System) and EFI (Extensible Firmware Interface).

RAM 3 is a volatile memory such as DRAM (Dynamic Random Access Memory) or SRAM (Static Random Access Memory). RAM 3 functions as a primary storage device, providing a working area into which various programs installed in the auxiliary storage device 4 are expanded when executed by the CPU 1.

The auxiliary storage device 4 is an auxiliary storage device that stores various programs and information used when the various programs are executed.

The display device 5 is a display device that displays the internal state of the operation device 10 and the playback device 20.

The operation device 6 is an input device through which the administrator of the operation device 10 and playback device 20 inputs various instructions to the operation device 10 and playback device 20.

The I/F device 7 is a communication device that connects to a network and communicates with other devices.

The drive device 8 is a device for loading the storage medium 9. The storage medium 9 referred to here includes media that record information optically, electrically, or magnetically, such as CD-ROMs, flexible disks, and magneto-optical disks. The storage medium 9 may also include semiconductor memory that records information electrically, such as EPROM (Erasable Programmable Read Only Memory) and flash memory.

The various programs installed in the auxiliary storage device 4 are installed, for example, by inserting the distributed storage medium 9 into the drive device 8 and reading the various programs recorded on the storage medium 9 using the drive device 8. Alternatively, the various programs installed in the auxiliary storage device 4 may be installed by downloading them from a network via the I/F device 7.

The above describes in detail examples of the present invention, but the present invention is not limited to the specific embodiments described above, and various modifications and variations are possible within the scope of the gist of the present invention as set forth in the claims.

10 Operation device 20 Playback device 30 Playback control system 101 Notification sending unit 102 Notification receiving unit 103 Notification monitoring unit 104 Operation monitoring unit 201 Web browser 202 Content player 203 Playback management unit 204 Missed program estimation unit 11 Smartphone (Android)
21 PCs (Linux OS)
110 Native App 120 OS (notification reception function)
130 Notification monitoring function 140 Screen ON/OFF monitoring function 150 Monitoring service
210 Google Chrome
220 Video Player 230 Playback Management.py
240 Missed Estimation.py
250 Python execution environment 260 YouTube web application 1 CPU
2 ROMs
3 RAM
4 Auxiliary storage device 5 Display device 6 Operation device 7 I/F device 8 Drive device 9 Storage medium

Claims (8)

A playback control system including an operation device and a playback device,
The operation device is
a monitoring unit that, when a user operates the operation device, notifies the playback device of a status of the operation;
The playback device
a missed viewing estimation unit that estimates whether the user has missed content due to an operation of the operation device;
a playback management unit that, when it is estimated that the user has missed the content, replays the content from the start time of operation of the operation device ;
the missed content estimation unit calculates a probability that the user has missed the content based on the operation status, and estimates that the user has missed the content if the probability is equal to or greater than a threshold;
A playback control system in which the operation status is at least one of the name of the application operated by the user, the importance of a notification from the application, the time until the user starts operating the operation device, and the time spent by the user operating the operation device . The playback control system according to claim 1 , wherein the missed content estimation unit determines that there is a high probability that the user has missed the content if the name of the application is a name of a specific application. The playback control system according to claim 1 , wherein the missed content estimation unit determines that the higher the importance of the notification from the application, the higher the probability that the user has missed the content. The playback control system according to claim 1 , wherein the missed content estimation unit determines that the probability that the user has missed the content increases as the time until the user starts operating the operation device decreases. The playback control system according to claim 1 , wherein the missed content estimation unit determines that the longer the time the user spends operating the operation device, the higher the probability that the user has missed the content. The playback control system according to claim 1 , wherein the monitoring unit determines that the user has started an operation when a screen of the operation device is turned on. A playback control system including an operation device, a playback device, and a server,
a monitoring unit that, when a user operates the operation device, notifies the playback device of a status of the operation;
a missed viewing estimation unit that estimates whether the user has missed content due to an operation of the operation device;
a playback management unit that, when it is estimated that the user has missed the content, replays the content from the start time of operation of the operation device ;
the missed content estimation unit calculates a probability that the user has missed the content based on the operation status, and estimates that the user has missed the content if the probability is equal to or greater than a threshold;
A playback control system in which the operation status is at least one of the name of the application operated by the user, the importance of a notification from the application, the time until the user starts operating the operation device, and the time spent by the user operating the operation device . A playback control system including an operation device and a playback device, comprising: a monitoring unit that, when a user operates the operation device, notifies the playback device of a status of the operation;
a missed viewing estimation unit that estimates whether the user has missed content due to an operation of the operation device;
when it is estimated that the user has missed the content, the playback management unit replays the content from the start time of the operation of the operation device ;
the missed content estimation unit calculates a probability that the user has missed the content based on the operation status, and estimates that the user has missed the content if the probability is equal to or greater than a threshold;
The program, wherein the operation status is at least one of the name of the application operated by the user, the importance of a notification from the application, the time until the user starts operating the operation device, and the time spent by the user operating the operation device .