Receiving device, converting device, and program
The receiving device addresses inconsistent reading methods across different devices by dynamically converting metadata into audible attribute values, ensuring accurate guidance for users with visual impairments.
Patent Information
- Application Number
- JP2024080486
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-23
- Filing Date
- 2024-05-16
- Publication Date
- 2024-12-05
AI Technical Summary
Conventional receiving devices for content, such as TVs and PCs, have inconsistent methods for accessing and reading out meta information, leading to incorrect guidance for users with visual impairments, especially when accessing content from different viewing environments.
A receiving device with a metadata receiving unit that extracts and converts data into a markup language file for screen display, using a conversion function unit to dynamically convert and embed attribute values, enabling correct reading of metadata regardless of the device model, including dynamically changing metadata and playback positions.
Ensures accurate and unified reading of metadata information, allowing users with visual impairments to access content and services effectively by converting metadata into audible attribute values in a markup language file.
Smart Images

Figure 2024169349000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a receiving device, a converting device, and a program. [Background technology]
[0002] In recent years, accessibility has been taken into consideration in content distribution. Accessibility in content distribution means that all users can access the content without difficulty. In some cases, accessibility functions are provided in receiving devices for receiving content to improve accessibility. One of the accessibility functions in devices for receiving content is the function of reading aloud characters displayed on the screen. For example, personal computers (PCs) may be equipped with dedicated screen reader software that has the function of reading aloud characters on the screen. In addition, some television sets (hereinafter referred to as "TVs") have their own character reading function. These reading functions contribute to delivering the services and content of content distribution providers (broadcasting stations, etc.) to people with visual impairments, etc.
[0003] For example, claim 1 of Patent Document 1 describes a screen information reading device that reads screen information and reads out the contents. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2018-206009 A Summary of the Invention [Problem to be solved by the invention]
[0005] Receiving devices (televisions, PCs, tablet devices, smartphones, wristwatch-type devices, etc.) for receiving content are required to have the ability to read out the content itself, as well as the ability to read out meta-information related to the content (such as a program guide, for example).
[0006] However, conventional televisions and PCs have the following problems: The method of accessing the text to be read aloud and the method of reading aloud themselves may differ depending on the viewing environment of the television, PC, etc. This may result in insufficient content being read aloud. As a result, even if meta information (such as a program guide) is read out, the guidance provided may be incorrect, and users who hear the information, particularly those with visual impairments, may not be able to access the services or content provided by the content distribution provider.
[0007] In other words, it is desirable to have meta information read out based on standardized information, regardless of the model of the receiving device (viewing environment) such as a television or PC.
[0008] The present invention has been made based on the above-mentioned problem recognition, and aims to provide a receiving device, a conversion device, and a program that enable information contained in given metadata to be read out correctly, regardless of the model (viewing environment).The present invention also aims to provide a receiving device etc. that enables information that can change dynamically, such as dynamically changing metadata and the current playback position of the content, to be read out correctly. [Means for solving the problem]
[0009] [1] In order to solve the above problem, a receiving device according to one aspect of the present invention includes a metadata receiving unit that receives metadata related to content distribution, a conversion function unit that extracts predetermined data to be read aloud from the metadata and converts the extracted data to be read aloud into a description of an attribute value of a predetermined attribute for the data to be read aloud in a markup language file for screen display, and further dynamically converts dynamically changing data to be read aloud into a description of an attribute value of a predetermined attribute for the data to be read aloud in a markup language file for screen display, or converts the data to a description of the attribute value of the predetermined attribute and dynamically embeds it in the markup language file, and a presentation unit that performs screen display based on the markup language file converted by the conversion function unit and controls a process to read aloud the attribute value of the predetermined attribute by voice.
[0010] [2] Moreover, one aspect of the present invention is that in the receiving device of [1] above, the dynamically changing data to be read aloud is at least one of data to be read aloud in the metadata and playback position information which is the playback time of the content being played, and when the conversion function unit receives playback position information of the content being played from the presentation unit, it converts the received playback position information and dynamically embeds it in the markup language file, and when the data to be read aloud in the metadata changes, it dynamically converts the changed data to be read aloud.
[0011] [3] Moreover, one aspect of the present invention is a conversion device having a conversion function unit that extracts specified data to be read aloud from metadata related to content distribution, converts the extracted data to be read aloud into a description of attribute values of specified attributes for the data to be read aloud in a markup language file for screen display, and further dynamically converts dynamically changing data to be read aloud into a description of attribute values of specified attributes for the data to be read aloud in a markup language file for screen display, or converts the data to a description of the attribute values of the specified attributes and dynamically embeds it in the markup language file.
[0012] [4] Also, one aspect of the present invention is a program for causing a computer to function as a receiving device including: a metadata receiving unit that receives metadata related to content distribution; a conversion function unit that extracts predetermined data to be read aloud from the metadata and converts the extracted data to be read aloud into a description of an attribute value of a predetermined attribute for the data to be read aloud in a markup language file for screen display, and further dynamically converts dynamically changing data to be read aloud into a description of an attribute value of a predetermined attribute for the data to be read aloud in a markup language file for screen display, or converts the data to a description of the attribute value of the predetermined attribute and dynamically embeds it in the markup language file; and a presentation unit that performs screen display based on the markup language file converted by the conversion function unit and controls a process to read aloud the attribute value of the predetermined attribute by voice.
[0013] [5] Another aspect of the present invention is a program for causing a computer to function as a conversion device having a conversion function unit that extracts specified data to be read aloud from metadata related to content distribution, converts the extracted data to be read aloud into a description of attribute values of specified attributes for the data to be read aloud in a markup language file for screen display, and further dynamically converts dynamically changing data to be read aloud into a description of attribute values of specified attributes for the data to be read aloud in a markup language file for screen display, or converts the data to a description of the attribute values of the specified attributes and dynamically embeds it in the markup language file.
[0014] [Reference Embodiment 1] Moreover, a receiving device according to one reference embodiment includes a metadata receiving unit that receives metadata related to content distribution, a conversion function unit that extracts specified data to be read aloud from the metadata and converts the extracted data to be read aloud into a description of an attribute value of a specified attribute for the data to be read aloud in a markup language file for screen display, and a presentation unit that performs screen display based on the markup language file converted by the conversion function unit and controls a process to read aloud the attribute value of the specified attribute by voice.
[0015] [Reference Aspect 2] In another reference aspect, in the receiving device of the above [Reference Aspect 1], the metadata receiving unit receives service metadata related to a content distribution service, and the conversion function unit extracts service name information in the service metadata as the data to be read aloud, and converts the extracted service name information into a description of an attribute value in the markup language file.
[0016] [Reference Aspect 3] In another reference aspect, in the receiving device of [Reference Aspect 1] or [Reference Aspect 2] above, the metadata receiving unit receives content metadata related to the content to be distributed, and the conversion function unit extracts at least one of content name information and content distribution date and time information in the content metadata as the data to be read aloud, and converts at least one of the extracted content name information and content distribution date and time information into a description of an attribute value in the markup language file.
[0017] [Reference Aspect 4] In another reference aspect, in any of the receiving devices according to [Reference Aspect 1] to [Reference Aspect 3] above, the metadata receiving unit receives content metadata relating to the content to be distributed, and further includes a commentary audio playback unit that acquires the commentary audio based on location information of the commentary audio contained in the content metadata, the commentary audio being related to the content, and plays back the acquired commentary audio as audio.
[0018] [Reference Embodiment 5] Another reference embodiment is a conversion device that includes a conversion function unit that extracts specified data to be read aloud from metadata related to content distribution, and converts the extracted data to be read aloud into a description of attribute values of specified attributes for the data to be read aloud in a markup language file for screen display.
[0019] [Reference Aspect 6] Another reference aspect is a program that causes a computer to function as a receiving device that includes a metadata receiving unit that receives metadata related to content distribution, a conversion function unit that extracts specified data to be read aloud from the metadata and converts the extracted data to be read aloud into a description of an attribute value of a specified attribute for the data to be read aloud in a markup language file for screen display, and a presentation unit that performs screen display based on the markup language file converted by the conversion function unit and controls a process to read aloud the attribute value of the specified attribute by voice.
[0020] [Reference Embodiment 7] Another reference embodiment is a program that causes a computer to function as a conversion device that has a conversion function unit that extracts specified data to be read aloud from metadata related to content distribution and converts the extracted data to be read aloud into a description of attribute values of specified attributes for the data to be read aloud in a markup language file for screen display. Effect of the Invention
[0021] According to the present invention, the conversion function unit can embed predetermined information extracted from the metadata as a value of a predetermined attribute of a predetermined tag in a markup language file. The conversion function unit can also embed information of a playback position of content as a value of a predetermined attribute of a predetermined tag in a markup language file. The presentation unit controls a process to read out the attribute value of the predetermined attribute by voice. This causes the predetermined information in the metadata to be read out by voice. This allows the user to grasp the metadata information by hearing. [Brief description of the drawings]
[0022] [Figure 1] 1 is a block diagram showing a schematic functional configuration of a receiving device according to a first embodiment of the present invention. [Diagram 2] 2 is a block diagram showing the overall configuration of a content distribution system configured to include a receiving device according to the embodiment. FIG. [Diagram 3] 11 is a flowchart (1 / 3) showing an example of an operation sequence of the receiving device according to the embodiment. [Figure 4] 13 is a flowchart (2 / 3) showing an example of an operation sequence of the receiving device according to the embodiment. [Diagram 5] 13 is a flowchart (3 / 3) showing an example of an operation sequence of the receiving device according to the embodiment. [Figure 6] 4 is a schematic diagram showing an example of user profile data used by the content distribution system according to the embodiment. FIG. [Figure 7] FIG. 13 is a schematic diagram showing an example (part 1) in which the receiving device according to the embodiment inserts information acquired from metadata into HTML for display. [Figure 8] FIG. 11 is a schematic diagram showing an example (part 2) in which the receiving device according to the embodiment inserts information acquired from metadata into HTML for display. [Figure 9] FIG. 2 is a schematic diagram (1 / 2) showing an example of service metadata used by the content distribution system according to the embodiment. [Figure 10]FIG. 2 is a schematic diagram (2 / 2) showing an example of service metadata used by the content distribution system according to the embodiment. [Figure 11] FIG. 13 is a schematic diagram (1 / 7) showing an example of content metadata used by the content distribution system according to the embodiment. [Figure 12] FIG. 2 is a schematic diagram (2 / 7) showing an example of content metadata used by the content distribution system according to the embodiment. [Figure 13] FIG. 3 is a schematic diagram (3 / 7) showing an example of content metadata used by the content distribution system according to the embodiment. [Figure 14] FIG. 4 is a schematic diagram (4 / 7) showing an example of content metadata used by the content distribution system according to the embodiment. [Figure 15] FIG. 5 is a schematic diagram (5 / 7) showing an example of content metadata used by the content distribution system according to the embodiment. [Figure 16] FIG. 6 is a schematic diagram (6 / 7) showing an example of content metadata used by the content distribution system according to the embodiment. [Figure 17] FIG. 7 is a schematic diagram (7 / 7) showing an example of content metadata used by the content distribution system according to the embodiment. [Figure 18] 10 is a schematic diagram showing an example of a script describing a processing procedure for playing commentary audio in a receiving device according to the embodiment. FIG. [Figure 19] 1 is a schematic diagram showing an example of event metadata used by the content distribution system according to the embodiment. FIG. [Figure 20] 3A to 3C are schematic diagrams showing examples of screens displayed by a receiving device according to the embodiment and transitions between those screens. [Figure 21] FIG. 2 is a block diagram showing an example of the internal configuration (computer) of each device constituting the content distribution system according to the embodiment. [Figure 22] FIG. 11 is a block diagram showing a schematic functional configuration of a receiving device according to a second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0023] [First embodiment] Next, an embodiment of the present invention will be described with reference to the drawings. In this embodiment, a receiving device uses structured metadata to perform audio reading based on the metadata. The metadata is data in a format that is independent of the model of the receiving device. The receiving device receives the metadata and converts information extracted from the metadata into a format that can be read by a machine. As a result, the reading function of the receiving device is improved, and for example, even visually impaired people can easily find the services and content of content distributors.
[0024] In the following description, "app" is an abbreviation for application program. Additionally, "HTML" stands for Hypertext Markup Language. Additionally, "URL" stands for Uniform Resource Locator. Additionally, "API" stands for Application Program Interface. Additionally, "VOD" stands for video on demand.
[0025] 1 is a block diagram showing a schematic functional configuration of a receiving device according to this embodiment. As shown in the figure, the receiving device 1 includes a receiving unit 31 (transmitting and receiving unit), a content receiving unit 11, a decoding unit 12, a presenting unit 13, a profile determining unit 151, an environment determining unit 152, a converting function unit 153, a screen display unit 154, a reading function unit 17, an audio output unit 18, and a commentary audio reproducing unit 19.
[0026] Among the above-mentioned functions of the receiving device 1, for example, the functions of the profile determination unit 151, the environment determination unit 152, the conversion function unit 153, and the screen display unit 154 may be realized as a web application 150. The web application 150 is a program written in a language such as JavaScript (registered trademark) as an HTML file having executable code. The receiving device 1 includes a browser 15, and the web application 150 runs on the browser 15.
[0027] The receiving device 1 may be a television (television receiver) or an information terminal (personal computer, tablet terminal, smartphone, wristwatch-type terminal, etc.). When the receiving device 1 is a television, the receiving device 1 has a function of receiving a broadcast signal and can receive content (broadcast program, etc.) carried as a broadcast signal. When the receiving device 1 is a television, the receiving device 1 can also receive online video content via a communication line such as the Internet. The television of the receiving device 1 may be a television compatible with Hybridcast. Hybridcast is a service realized by combining broadcast and communication. Hybridcast itself is based on existing technology. When the receiving device 1 is an information terminal, the receiving device 1 can receive online video content via a communication line such as the Internet.
[0028] The receiving device 1, whether it is a television or an information terminal, can receive metadata from an external server device via a communication line such as the Internet. As will be described later, the receiving device 1 according to this embodiment is connected to a content transmitting device 3 and the like via a communication line to configure a content distribution system 100 (see FIG. 2).
[0029] At least some of the above-mentioned functions of the receiving device 1 can be realized, for example, by a computer and a program. Furthermore, each functional unit has a storage means as necessary. The storage means is, for example, a variable in the program, or a memory allocated by the execution of the program. Furthermore, non-volatile storage means such as a magnetic hard disk drive or a solid state drive (SSD) may be used as necessary. Furthermore, at least some of the functions of each functional unit may be realized as a dedicated electronic circuit rather than a program.
[0030] The functions of the presentation unit 13 and the screen display unit 154 may be collectively referred to as the "presentation unit."
[0031] Next, each of the functional units of the receiving device 1 will be described.
[0032] The receiving unit 31 (transmitting / receiving unit) communicates with an external device, etc., and receives data. Since the receiving unit 31 may transmit some data (including control information) when communicating with an external device, etc., the receiving unit 31 may be called a "transmitting / receiving unit."
[0033] The receiving unit 31 also receives metadata while receiving various data. That is, the receiving unit 31 functions as a "metadata receiving unit" that receives metadata related to content distribution. That is, the receiving unit 31 receives service metadata related to a content distribution service, content metadata related to content distributed by the content distribution service, and event metadata related to a distributed event.
[0034] The content distribution service includes a broadcasting service that distributes content using broadcast signals and an online video distribution service that distributes content (videos, etc.) via the Internet (this may be a broadcast type distribution or a VOD type distribution). The content distribution service may also be another type of service.
[0035] The content receiving unit 11 receives data of the content to be reproduced by the receiving device 1 via the receiving unit 31. The content may be broadcast content or online video content. When the content is broadcast content, the content receiving unit 11 receives a broadcast signal and demodulates it.
[0036] The decryption unit 12 decrypts the content data received by the content receiving unit 11. As a result of the decoding, the decryption unit 12 outputs the video, audio, text, and other resources of the content.
[0037] The presentation unit 13 presents the content decoded by the decoding unit 12. Specifically, the presentation unit 13 displays video, text, and the like on a screen. The presentation unit 13 also outputs sound from the sound output unit 18.
[0038] The profile determination unit 151 performs a determination on the profile of a specific user when the receiving unit 31 receives user profile data from the web application server device 7 (see FIG. 2). For example, the profile determination unit 151 determines whether the accessibility mode (accessibilityMode) is set to true or false for a specific user. The profile determination unit 151 also determines whether the read-out function (screenReaderAudio) of the receiving device 1 is set to true or false. The profile determination unit 151 also determines whether the guide audio (guideAudio) is set to true or false. The operation of the receiving device 1 depends on these determination results.
[0039] The environment determination unit 152 determines the operating environment of the device itself (the receiving device 1). Specifically, the environment determination unit 152 determines whether the device itself is a television or an information terminal (such as a PC). Depending on the result of this determination, the receiving device 1 performs processing using a function according to the operating environment.
[0040] The conversion function unit 153 extracts predetermined data to be read out from the metadata received by the receiving unit 31, and converts the extracted data to be read out into a description of attribute values of predetermined attributes for the data to be read out in a markup language file (HTML file) for screen display. In other words, the conversion function unit 153 embeds the data to be read out in the markup language file.
[0041] When the target metadata is service metadata, the conversion function unit 153 extracts predetermined information (e.g., information on a service name) from the service metadata as data to be read aloud, and converts the extracted information on the data to be read aloud (such as the service name) into a description of an attribute value in a markup language file. Note that the information to be read aloud may be information other than the service name. When the target metadata is content metadata, the conversion function unit 153 extracts predetermined information from the content metadata (e.g., information on a content name or information on a content distribution date and time) as data to be read aloud, and converts at least one of the extracted information into a description of an attribute value in a markup language file. When the target metadata is event metadata, the conversion function unit 153 extracts predetermined information from the event metadata as data to be read aloud, and converts the extracted information into a description of an attribute value in a markup language file.
[0042] That is, the conversion function unit 153 embeds predetermined information extracted from the metadata into the markup language file. The information to be read is embedded in the markup language file as a value of a specific attribute of a specific tag. That is, in the markup language file after the information is embedded by the conversion function unit 153, it is mechanically possible to determine whether the information included in the file is the information to be read.
[0043] Screen display unit 154 performs control so as to perform a screen display based on the markup language file (HTML file) converted by conversion function unit 153, and to perform a process of reading out the attribute value of the predetermined attribute by voice. Specifically, screen display unit 154 passes the text, which is the attribute value of the predetermined attribute, to read-out function unit 17, thereby performing control so that the text is read out by voice.
[0044] Screen display unit 154 presents a portal screen, contents, menu screen, and the like, and is also called a "presentation unit."
[0045] The read-out function unit 17 reads out a character string passed from the outside (screen display unit 154). When the receiving device 1 is a television, the read-out function unit 17 realizes the read-out by passing the character string via a read-out API. When the receiving device 1 is an information terminal (such as a PC or a smartphone), the read-out function unit 17 is a screen reader realized by hardware, software, or a combination of both.
[0046] The audio output unit 18 outputs the audio output by the read-aloud function unit 17, the audio reproduced by the commentary audio reproduction unit 19, and other audio. The audio output unit 18 includes a function such as a speaker or an earphone.
[0047] The commentary audio playback unit 19 plays back the specified commentary audio and outputs the audio. The commentary audio is typically audio associated with video content. The location of the commentary audio is described in the content metadata. The commentary audio playback unit 19 acquires the commentary audio based on the location information (URL, etc.) of the commentary audio included in this content metadata, and plays back the acquired commentary audio as audio. The content metadata referred to by the commentary audio playback unit 19 here is metadata that has information about a specific content. This content metadata has location information of the commentary audio related to the content.
[0048] The browser 15 has a function for displaying web information on a screen. The browser 15 displays the screen by reading a markup language file (such as an HTML file) and interpreting the content.
[0049] The web application 150 is an application program that runs on the browser 15. The web application 150 is written in a markup language such as HTML, and can include procedural processing code therein. The web application 150 in this embodiment includes the functions of a profile determination unit 151, an environment determination unit 152, a conversion function unit 153, and a screen display unit 154.
[0050] The conversion device 301 shown in FIG. The function of the conversion function unit 153 has already been described. The conversion device 301, as an independent device, extracts predetermined data to be read aloud from metadata related to content distribution, converts the extracted data to be read aloud into a description of attribute values of predetermined attributes for the data to be read aloud in a markup language file for screen display, and embeds the result in the markup language file. This allows the conversion device 301 to generate a markup language file including information to be read aloud based on the metadata. In other words, by displaying the markup language file, it becomes possible to read aloud the information extracted from the metadata.
[0051] 2 is a block diagram showing a configuration of a content distribution system configured to include the above-mentioned receiving device 1. As shown in the figure, the content distribution system 100 includes the receiving device 1, a content transmitting device 3, a metadata providing device 5, a web application server device 7, and a content distributor device 9.
[0052] At least a part of the functions of the content transmitting device 3, the metadata providing device 5, the web application server device 7, and the content distributor device 9 can be realized by a computer and a program, similar to the above-mentioned receiving device 1. Also, at least a part of the functions of each device may be realized as a dedicated electronic circuit or the like, rather than a program.
[0053] In the content distribution system 100, communication can be performed between the receiving device 1, the content transmitting device 3, the metadata providing device 5, the web application server device 7, and the content distributor device 9 via a communication line (not shown) such as the Internet. Furthermore, if the receiving device 1 is a television, content, control information, and the like can be transmitted from the content transmitting device 3 (broadcast wave transmitting device) to the receiving device 1 via a broadcast signal (radio wave or cable television signal).
[0054] The content transmitting device 3 transmits (distributes) content to the receiving device 1. The content that the content transmitting device 3 transmits to the receiving device 1 may be either a broadcast program or online streaming video content. When the content transmitting device 3 is a broadcast signal transmitting device of a broadcast station (including a cable television station), the content transmitting device 3 transmits content to the receiving device 1 by broadcast signals. When the content transmitting device 3 is a distribution server device for online streaming video content, the content transmitting device 3 transmits content to the receiving device 1 by using IP communication (IP is an abbreviation for "Internet Protocol") via a communication line such as the Internet. Whether the content is a broadcast program or online streaming video content, the method by which the content transmitting device 3 transmits content itself belongs to existing technology.
[0055] The metadata providing device 5 provides metadata related to the content transmitted by the content transmitting device 3. That is, when requested by the receiving device 1, the metadata providing device 5 transmits the above metadata to the receiving device 1. The metadata may include the title of the content, service specific information (information for identifying a broadcasting station or a channel, etc.), information related to the distribution date and time of the content, and information on a summary text of the content. Examples of the metadata format and a procedure for transmitting the metadata will be described later.
[0056] The web application server device 7 is a device that provides services to web applications running on the receiving device 1. In response to a request from the receiving device 1, the web application server device 7 provides user profile data and HTML files for displaying screens (accessibility portal screen, accessibility playback screen, etc.).
[0057] The content distributor device 9 is a device operated by a content distributor (for example, a broadcasting company, an online video distributor, etc.), and has a function of providing content and metadata. The content distributor device 9 provides content data to the content transmission device 3. The content distributor device 9 also provides metadata related to the content to the metadata providing device 5. The content distributor device 9 transmits content to the content transmission device 3 and transmits metadata to the metadata providing device 5, for example, via the Internet or a dedicated communication line. Alternatively, the content distributor device 9 may provide content (broadcast programs, etc.) and metadata using a portable medium such as a magnetic tape, a magnetic hard disk, or an optical disk, instead of via a communication line. The content and metadata are created by a content production company (which may be the same as the broadcasting company) or a related service provider.
[0058] Next, an example of an operation sequence of the receiving device 1 will be described with reference to Figures 3, 4, and 5. The flowcharts shown in Figures 3, 4, and 5 show one processing sequence, and are connected to each other by connectors. Note that the processing from step S5 to S9 shown in Figure 3 is processing by the conversion function unit 153. The following description will be given along this flowchart.
[0059] In step S1, the web application 150 running on the receiving device 1 requests the web application server device 7 to start a portal. Here, a "portal" is one type of application. An "accessibility portal" is one type of "portal". The accessibility portal screen may be displayed as one of the functions of the portal, or a transition from a normal portal application to the accessibility portal as a separate application may be performed. In response to this start request from the receiving device 1, the web application server device 7 starts the portal and returns the profile data to the receiving device 1 that made the request.
[0060] In step S2, the web application 150 of the receiving device 1 receives the profile data transmitted from the web application server device 7.
[0061] In step S3, the profile determination unit 151 of the receiving device 1 performs profile determination based on the profile data received in step S1. Specifically, the profile determination unit 151 determines whether the accessibility function (sometimes referred to as "A11Y function") is enabled or disabled. Examples of profile data and enabling / disabling of the accessibility function will be described later with reference to FIG. 6. For users for whom the accessibility function is enabled, the web application 150 of the receiving device 1 enables the accessibility function described below. For users for whom the accessibility function is disabled, the web application 150 of the receiving device 1 may perform control so that the accessibility function does not work.
[0062] In step S4, the web application 150 of the receiving device 1 requests an accessibility portal screen from the web application server device 7. In response to this request, the web application server device 7 returns the accessibility portal screen to the receiving device 1. The receiving device 1 receives this accessibility portal screen.
[0063] In step S5, the conversion function unit 153 of the receiving device 1 requests structured metadata from the metadata providing device 5. In response to this request, the metadata providing device 5 transmits the structured metadata to the requesting receiving device 1. The receiving device 1 receives this structured metadata. The structured metadata transmitted from the metadata providing device 5 in this step are service meta (metadata related to the service (broadcast station)), content meta (metadata related to each piece of content), and event meta (metadata related to an event that occurs). The metadata providing device 5 may transmit the service meta, content meta, and event meta to the receiving device 1 in sequence.
[0064] In step S6, the conversion function unit 153 of the receiving device 1 extracts service information (broadcast station information) from the metadata (service meta) received in step S5. Specifically, the conversion function unit 153 extracts information on the service name from the service meta.
[0065] In step S7, the conversion function unit 153 of the receiving device 1 extracts content information (program information) from the metadata (content meta) received in step S5.
[0066] In step S8, the conversion function unit 153 of the receiving device 1 extracts information on the content name (program name) and the start and end times of the content distribution from the metadata (content meta) received in step S5.
[0067] Specifically, the conversion function unit 153 extracts elements from the "itemListElement" array of the content meta. Each element in this "itemListElement" array corresponds to one piece of content. The conversion function unit 153 also extracts the following information for each piece of content. That is, the conversion function unit 153 extracts information on the content name, distribution start date and time, and distribution end date and time from the content metadata. The extraction of information from the content meta will be explained later.
[0068] In step S9, the conversion function unit 153 of the receiving device 1 appropriately edits the acquired data and inserts the data into the HTML file for presentation in the receiving device 1 at the positions of the predetermined tags. That is, the conversion function unit 153 inserts a description using HTML tags into the HTML file. The tags to be read aloud and their attributes may be determined in advance. The conversion function unit 153 converts the information extracted in step S8 into the value of the predetermined attribute in the HTML file and embeds it.
[0069] 4, in step S10, the screen display unit 154 of the web application 150 running on the receiving device 1 displays the accessibility portal screen. The receiving device 1 has already received the accessibility portal screen in step S4 above. The screen display unit 154 of the receiving device 1 displays the accessibility portal screen on a liquid crystal display device or the like that the receiving device has. On the accessibility portal screen, as described later, the content name and the like are displayed in widgets (e.g., buttons) of a graphical user interface (GUI) (see FIG. 20).
[0070] In step S11, the environment determination unit 152 of the receiving device 1 determines the operating environment of the device itself. Specifically, the environment determination unit 152 calls an HC function to determine whether the operating environment of the device itself is a television or an information terminal (such as a PC). By making the determination in this step, the receiving device 1 can operate according to the environment in the following.
[0071] In step S12, the receiving device 1 executes reading of the text. Specifically, the receiving device 1 reads out aloud the character strings of the program name (content name) and broadcast time (broadcast start time and end time) surrounded by HTML tags corresponding to the widget in focus pointed to on the accessibility portal screen on the displayed HTML screen. In other words, the receiving device 1 reads out the character strings of the program name (content name) and broadcast time (broadcast start time and end time) of the content in focus.
[0072] When the receiving device 1 is a television, the receiving device 1 executes the reading by passing the character string (text) to be read aloud via a reading API. This reading API can be implemented using a Web Speech API or by writing a script using JavaScript. When reading aloud, the screen display unit 154 passes the text to be read that corresponds to the current focus to the reading function unit 17. The reading function unit 17 executes reading of the passed text, and the reading voice is output from the audio output unit 18. The reading of text in the following steps is also performed in a similar manner.
[0073] Furthermore, if the receiving device 1 is an information terminal (not a television), as described above, the receiving device 1 performs reading aloud using the function of a screen reader realized by hardware, software, or a combination of both.
[0074] In step S13, the receiving device 1 moves the focus on the accessibility portal screen. Specifically, the receiving device 1 detects that the user operates the pointing means of the receiving device itself, and moves the focus in response to the operation. As an example, the user can arbitrarily operate a keyboard or keypad, or up, down, left, right, or other keys arranged on a remote control device of the receiving device 1. The receiving device 1 detects the key operation, and moves the focus in response to the operated key. By moving the focus, for example, the content on which the user focuses (content of selection candidates) can be changed. Since data has already been embedded in tags in HTML in step S9, it is possible to extract the read-aloud text corresponding to the content each time the focus moves.
[0075] In step S14, the receiving device 1 executes reading aloud. Specifically, when the focus is moved in step S13, the screen display unit 154 passes the read-aloud text corresponding to the currently focused content to the read-aloud function unit 17. The read-aloud function unit 17 executes reading aloud of the passed text, and the read-aloud voice is output from the audio output unit 18.
[0076] In step S15, the receiving device 1 determines the content to be reproduced next. Specifically, the screen display unit 154 of the receiving device 1 moves the focus as described above, and when the user performs a confirm operation, the content corresponding to the focus at that time is determined as the content to be reproduced next. The above-mentioned confirm operation is performed, for example, by the user pressing a "confirm button." The confirm button may be located on a keyboard or keypad, or may be located on a remote control device for operating the receiving device 1. When the receiving device 1 detects that the confirm button has been pressed, it sets the content corresponding to the current focus as the "confirmed content."
[0077] Although the focus movement (step S13) is shown to be performed once until the content is determined (step S15) in FIG. 4, it can be performed any number of times, and reading out (step S14) is performed each time the focus is moved. That is, the set of processes of steps S13 and S14 is repeated once or multiple times until the content is determined (step S15). It is also possible to determine the content without moving the focus, that is, to determine the content corresponding to the focus when the accessibility portal screen is displayed (step S10). It is also possible to configure the reading out (step S14) after the focus movement to start processing when the focus remains stationary or continues to be on a widget corresponding to one content (selection target) for a predetermined time (for example, 1.0 second). It is also possible to configure the processing to stop at that point when the user operates to perform the focus movement (step S13) or the content determination (step S15) during the execution of reading out (steps S12, S14).
[0078] In step S16, the web application 150 on the receiving device 1 requests an accessibility playback screen from the web application server device 7. In response to this request, the web application server device 7 transmits the accessibility playback screen to the receiving device 1. The receiving device 1 can receive and display this accessibility playback screen.
[0079] In step S17, the receiving device 1 requests content (broadcast program or online streaming video content). The content requested by the receiving device 1 in this step is the content determined in step S15. When the receiving device 1 requests content in this step, it extracts and uses the URL (URI) of the content from the structured metadata. The URL of the content can indicate the location of a broadcast program (content distributed as a broadcast service) or the location of online streaming video content.
[0080] Here, the destination of the content request from the receiving device 1 is the content transmission device 3 specified by the above URL. The content transmission device 3 that has received this request can distribute the content to the receiving device 1 based on the request. However, if the content transmission device 3 is a broadcast transmission device, the content transmission device 3 transmits a broadcast signal regardless of the request from the receiving device 1. The content receiving unit 11 of the receiving device 1 receives the content transmitted from the content transmission device 3 via the receiving unit 31. The content receiving unit 11 reproduces the received content. That is, the content receiving unit 11 demodulates the received content and passes it to the decoding unit 12. The decoding unit 12 decodes resources (video, audio, etc.) included in the content and passes them to the presenting unit 13. The presenting unit 13 outputs the decoding result (video, audio, etc.) passed from the decoding unit 12. Specifically, the presenting unit 13 displays the video and text included in the content on a screen and outputs the audio from a speaker or the like (audio output unit 18).
[0081] 5, in step S18, the web application 150 of the receiving device 1 determines whether or not commentary audio is present. Commentary audio is content that can be distributed in association with the content (video content) being received in order to improve the accessibility of the content. The presence or absence of commentary audio can be determined, for example, by referring to metadata. Depending on the result of this determination (the presence or absence of commentary audio), the receiving device 1 determines whether or not to perform processing to output commentary audio in the next step S19.
[0082] Only when it is determined that there is a commentary audio, in step S19, the receiving device 1 receives and outputs the commentary audio. Location information (URL) of the commentary audio is described, for example, in metadata of the content body. When there is a commentary audio, the web application 150 requests the commentary audio from the content transmission device 3 based on the location information. In response to this request, the content transmission device 3 transmits the commentary audio to the requesting receiving device 1. The web application 150 of the receiving device 1 receives the commentary audio and passes it to the commentary audio playback unit 19. The commentary audio playback unit 19 plays back the commentary audio and outputs the commentary audio from the audio output unit 18.
[0083] A delivery device dedicated to commentary audio (commentary audio server) may be provided separately from the content transmission device 3. In this case, the web application 150 of the receiving device 1 can access the commentary audio using the above-mentioned location information. The commentary audio playback unit 19 outputs audio by, for example, passing audio data via an audio API (for example, a Web Audio API).
[0084] In step S20, the web application 150 of the receiving device 1 displays the accessibility playback screen. This accessibility playback screen is the one received in step S20 above. In this manner, the content is presented and the commentary audio is output (only when necessary).
[0085] In step S21, the receiving device 1 performs reading out. The specific processing procedure for executing reading out is as already described in steps S12 and S14.
[0086] In step S22, the receiving device 1 requests a carousel menu from the metadata providing device 5. In response to this request, the metadata providing device 5 transmits the carousel menu to the requesting receiving device 1. The receiving device 1 can receive and display the carousel menu. The screen including this carousel menu is also written in HTML.
[0087] In step S23, the receiving device 1 performs reading out. The specific processing procedure for executing reading out is as already described in steps S12 and S14.
[0088] The typical process (reading out metadata) of the receiving device 1 in this embodiment is as follows. The receiving device 1 may further receive metadata thereafter, embed information extracted from the metadata in HTML, and perform appropriate reading out processing.
[0089] Next, details of the data used when the receiving device 1 processes the data will be described. FIG. 6 is a schematic diagram showing an example of a user profile. FIG. 7 is a schematic diagram showing an example in which information acquired from metadata is inserted into HTML for display on the receiving device 1 side. FIG. 8 is a schematic diagram showing another example in which information acquired from metadata is inserted into HTML for display on the receiving device 1 side. 9 and 10 are schematic diagrams showing examples of service metadata. 11, 12, 13, 14, 15, 16, and 17 are schematic diagrams showing examples of content metadata. FIG. 18 is a schematic diagram showing an example of a script describing a processing procedure for playing back a commentary audio. FIG. 19 is a schematic diagram illustrating an example of event metadata. For the sake of convenience, line numbers are assigned to the data shown in Figures 6 to 19. Some of the lines included in the data shown in Figures 6 to 19 are displayed by wrapping around the middle of one line.
[0090] The user profile data shown in Figure 6 shows data for two users.
[0091] Lines 1 to 19 in Figure 6 are the data for the first user profile, and the user ID is "yamada" (line 2). Line 9 describes the profile settings for that user as ""accessibilityMode": true." This setting indicates that the receiving device 1 should operate with the accessibility mode "on". Additionally, the 10th line states "screenReaderAudio": true. This setting indicates that the receiving device 1 should operate with the screen reading audio function "on". Additionally, the 11th line states "guideAudio": true. This setting indicates that the receiving device 1 should operate with the commentary audio playback function "on".
[0092] Lines 20 to 38 of FIG. 6 are the data of the second user profile, and the user ID is "tanaka" (line 21). Line 28 describes the profile settings of the user as "accessibilityMode": false. This setting indicates that the receiving device 1 should operate with the accessibility mode "off". Line 29 describes "screenReaderAudio": false. This setting indicates that the receiving device 1 should operate with the screen reading audio function "off". Line 30 describes "guideAudio": false. This setting indicates that the receiving device 1 should operate with the commentary audio playback function "off".
[0093] In this way, the data of the user profile in Fig. 6 indicates whether or not each function is to be activated for that user when the receiving device 1 is operated. Note that the other rows of the data in Fig. 6 are as shown in the figure, and further explanation will be omitted here.
[0094] The HTML data element shown in FIG. 7 is an "img" element (image element). This "img" tag has an alt attribute. The Alt attribute represents alternative information for an image. The character string described as the value of this alt attribute can be read aloud by the receiving device 1. In this example, the value of the alt attribute is "NHK General Tokyo." This img tag is an image of the icon (logo mark) of a particular broadcasting service, and the value of the alt attribute is a character string representing the name of the service.
[0095] The HTML data element shown in Fig. 8 is a "div" element. This "div" tag has an aria-label attribute. The aria-label attribute is an attribute defined in WAI-ARIA (Way Area). WAI is an abbreviation for "Web Accessibility Initiative." The value of the aria-label attribute in the figure is a character string that can be read aloud by the receiving device 1.
[0096] As illustrated in the above Figs. 7 and 8, the information extracted from the structured metadata (information suitable for being read aloud) is embedded as a predetermined attribute value in HTML by the conversion function unit 153 of the receiving device 1. Note that, although the alt attribute and the aria-label attribute have been given as examples of attributes to be read aloud, other attributes or values of other elements used in HTML may also be used as information to be read aloud. For example, the title attribute of a button or list (e.g., " <button title="”再生ボタン”">") or heading elements (e.g. " <h1> Accessibility Portal Screen< / h1> ") and the caption element in a table (for example, " Program List ··· ") and other attributes and elements may be read aloud.
[0097] One piece of metadata (service metadata) shown in Figures 9 and 10 is metadata describing a content distribution service. From the seventh line of this service metadata (Figure 9), item list elements are listed. The block from the eighth line (Figure 9) to the 63rd line (Figure 10) (the part surrounded by curly braces on the left and right) is one of the item elements. This item element describes information about one service (broadcast service, broadcast station). Among them, ""name": "NHK General TV, Tokyo"" on the 12th line (Figure 9) describes the name of the broadcast service, and is the basis for the alt attribute value of the img element explained in Figure 7. Also, ""image": " / public / logo / nhk_g.png"" on the 35th line (Figure 10) is information indicating the location of the image of the logo mark of the service, and is associated with the value of the src attribute of the img element in Figure 7. The other rows in the data in FIG. 7 and FIG. 8 are as shown in the figures, and further explanation will be omitted here.
[0098] One piece of metadata (content metadata) shown in FIG. 11, FIG. 12, FIG. 13, FIG. 14, FIG. 15, FIG. 16, and FIG. 17 describes information about one piece of content (in this example, a news program in a broadcast). ""name": "NHK News 7: Mask relaxation reduces infections ▼ Evacuation of people requiring assistance from nuclear power plant [2][characters]"" on line 29 of this content metadata (FIG. 11) represents the name of the content (broadcast program). This content name information can be read out by the receiving device 1, and is embedded in the HTML data for display by the conversion function unit 153 of the receiving device 1. In addition, the block ""publication":" starting on line 58 of this content metadata (FIG. 12) contains information about the start time and end time of the content distribution (broadcast). Specifically, ""startDate": "2023-03-09T19:00:00+09:00" on line 62 (FIG. 12) represents the distribution start date and time. Also, "endDate": "2023-03-09T19:30:00+09:00" on the 63rd line (FIG. 12) represents the distribution end date and time. These dates and times are in a format including the year, month, day, hour, minute, second, and time zone (in this example, "+09:00" represents 9 hours ahead of Coordinated Universal Time). Information on the start date and time and end date and time of this distribution (broadcast) can be read aloud by the receiving device 1, and is embedded in the HTML data for display by the conversion function unit 153 of the receiving device 1. Also, when the receiving device 1 is a hybrid cast-compatible television, the information to be read aloud may be embedded in the hybrid cast-specific HTML data (for example, an object tag used for broadcast playback).
[0099] Furthermore, the "citation":" block starting on line 188 of this content metadata (Figure 16) contains information regarding the location of the commentary audio. Specifically, "@type: AudioObject" on line 190 (Figure 16) indicates that the type of object described here is an audio object. Furthermore, "name: Audio commentary of program contents added to main audio" on line 191 (Figure 16) is information of a string indicating the name of the audio object. In other words, the audio object in question is the commentary audio object mentioned above. Also, "url": "https: / / www.example.net / audioguide / 0001.mp3" on line 192 (FIG. 16) indicates the location information (URL) for accessing the commentary audio. Thus, information about the commentary audio is also included in the content metadata. The receiving device 1 performs the process of acquiring and playing the commentary audio described above by referring to this content metadata.
[0100] In the description of the processing procedure shown in Figure 18 (implementation example using the Web Audio API), the first line is simply a comment. The second line is a process to create a new AudioContext object and store it in the variable guideAudioCtx (context of the commentary audio). The third line is a process to call the method "createBuffer" of the above variable guideAudioCtx to create a buffer and store it in the variable guideAudioSrc. The fourth line is a process to create an XMLHttpRequest object and store it in the variable request. The fifth line is a process to store the string constant "https: / / www.example.net / audioguide / 0001.mp3" in the variable url. This string constant represents the URL for accessing the sample commentary audio "0001.mp3" (a file in MP3 (MPEG 1 Audio Layer-3) format).
[0101] Next, line 6 in Figure 18 is a process that calls the method open of the variable request (XMLHttpRequest object) whose value was stored in line 4. The actual arguments passed to the method open are, first, the string constant "GET", second, the variable url (whose value was stored in the process on line 5), and third, the value true. The process on line 6 opens an HTTP request. Line 7 is a process that stores the constant string "arraybuffer" in the variable responseType held by the above variable request. Line 8 is a process that executes the method send held by the above variable request. This causes the request to be sent.
[0102] Next, lines 9 to 15 in Figure 18 define the function of the variable onload that the variable request has. Lines 9 to 15 are one block surrounded by curly braces on both sides. Line 10 stores the value of the variable response that the variable request (object) has in the variable res. It is expected that the reply from the request destination is stored in request.reqponse. Lines 11 to 13 call the method "decodeAudioData" that the object of the variable guideAudioCtx (see line 1) has. Line 12 stores the value of the variable buf in the variable buffer that the object of the variable guideAudioSrc (see line 2) has. Line 14 executes the function guideAudioPlay (plays the commentary audio).
[0103] Next, lines 16 to 19 in Figure 18 are the definition of the above function guideAudioPlay (playback of commentary audio). Lines 16 to 19 are one block surrounded by curly braces on the left and right. The execution part of the function is lines 17 and 18. Line 17 is a process to execute the method "connect" of the object of the above variable guideAudioSrc. The actual argument passed to this method "connect" is the value of the variable "destination" of the object of the above variable guideAudioCtx. By executing this method "connect", a connection is made to the commentary audio generation function. Also, line 18 is a process to execute the method "start" of the object of the above variable guideAudioSrc. The actual variable passed to this method "start" is the numerical value "0". By executing this method "start", playback of the commentary audio begins.
[0104] FIG. 19 is a schematic diagram showing an example of event metadata. In this example, "dateModified": "2023-03-08T13:23:17+09:00" on the 17th line, "dateCreated": "2023-03-08T13:23:17+09:00" on the 18th line, and "datePosted": "2023-03-08T13:23:17+09:00" on the 19th line are date and time information related to the event. In addition, "name": "Earthquake Early Warning" on the 21st line is information representing the event name. In addition, "text": "Earthquake Early Warning An earthquake of seismic intensity __ will occur in approximately __ seconds" on the 22nd line is information representing text related to the event.
[0105] 20 is a schematic diagram showing examples of screens displayed by the receiving device 1 and transitions between those screens. In the figure, SC1 is an accessibility portal screen. SC2 is a playback screen. SC3 is a playback screen when a carousel menu is displayed.
[0106] In the portal screen SC1 according to this example, content information is displayed in the form of a matrix in the time axis direction (vertical direction) and by channel (by service) (horizontal direction). In addition, below the matrix, a list of information on recommended content (VOD) in a specific channel (service) is displayed (VOD1, VOD2, VOD3). As already described, the content information displayed in the portal screen SC1 can be focused on as a widget (e.g., a button) of a graphical user interface (GUI). The user can move the focus by key operation or the like to any of the content information displayed on the portal screen SC1. For the content corresponding to the current focus, the receiving device 1 can read out its metadata (content meta) by voice.
[0107] On the playback screen SC2, the receiving device 1 displays the content (moving image, etc.) being played back.
[0108] On the playback screen SC3 while the carousel menu is displayed, a time bar (also called a progress bar) and a character string "00:50:00 / 01:00:00" are displayed. This character string indicates that "0:50:00" (50 minutes) has already elapsed out of the total length (total playback time) "1:00:00" (1 hour) of the content being played. In other words, this time bar and character string represent the current playback position of the content being played (Internet distribution video content, etc.). On the playback screen SC3 while the carousel menu is displayed, information on a plurality of contents is displayed in the form of a carousel menu. In this example, the contents displayed as the carousel menu are the contents currently being broadcast in a specific service (two services, Ach and Bch, in this example) and a plurality of recommended contents in a specific service (Ach, in this example). When the user focuses on the information on the content displayed in the carousel menu, the receiving device 1 may read out the information on the content.
[0109] The screen transitions indicated by dashed arrows in Fig. 20 are as follows: In screen transition T12, when the portal screen SC1 is displayed and one of the presented contents is selected (focused), if the user performs a confirm operation, a transition to the playback screen SC2 occurs. That is, playback of the confirmed content starts on the playback screen SC2. The user's confirm operation is performed by pressing a "confirm" key on the screen or on a remote control device or the like.
[0110] As a screen transition T23, when the playback screen SC2 is displayed and the user performs an operation to display the carousel menu, a transition to the playback screen SC3 displaying the carousel menu occurs. That is, on the playback screen SC3 displaying the carousel menu, the content that was originally being played is displayed, and the carousel menu is also displayed. Note that the operation by the user to display the carousel menu is, for example, an operation in which the user presses the "Enter" key, the "Up" key, or the "Down" key on the screen or on a remote control device.
[0111] As a screen transition T31, when the user performs an operation to display a portal screen while the playback screen SC3 displaying the carousel menu is being displayed, a transition to the portal screen SC1 occurs. Note that the operation to display the portal screen by the user is, for example, an operation in which the user presses a specific key (for example, the "blue" key) assigned to display the portal screen on the screen or on a remote control device.
[0112] The transition from the playback screen SC3 displaying the carousel menu to the playback screen SC2 is performed in two ways. When the user presses the "back" key on the screen or on a remote control device or the like as screen transition T32A while the playback screen SC3 displaying the carousel menu is being displayed, a transition to the playback screen SC2 occurs. When the transition to the playback screen SC2 occurs in screen transition T32A, the content that was originally being played continues to be played. As a screen transition T32B, when the user performs an operation to "confirm" the selected content (content in focus) (such as pressing the "Confirm" key) while the playback screen SC3 displaying the carousel menu is being displayed, a transition to the playback screen SC2 occurs. When the transition to the playback screen SC2 occurs in the screen transition T32A, playback of the content newly selected (confirmed) by the user starts.
[0113] As a screen transition T21, when the user presses the "return" key on the screen or on the remote control device or the like while the playback screen SC2 is being displayed, a transition to the portal screen SC1 occurs.
[0114] FIG. 21 is a block diagram showing an example of the internal configuration (computer) of each device constituting the content distribution system 100. Each device (receiving device 1, content transmitting device 3, metadata providing device 5, web application server device 7, content distributor device 9) can be realized using a computer. As shown in the figure, the computer includes a central processing unit 901, a RAM 902, an input / output port 903, input / output devices 904 and 905, and a bus 906. The computer itself can be realized using existing technology. The central processing unit 901 executes instructions included in a program read from the RAM 902, etc. The central processing unit 901 writes data to the RAM 902, reads data from the RAM 902, and performs arithmetic and logical operations according to each instruction. The RAM 902 stores data and programs. Each element included in the RAM 902 has an address and can be accessed using the address. Note that RAM is an abbreviation for "random access memory." The input / output port 903 is a port through which the central processing unit 901 exchanges data with external input / output devices, etc. The input / output devices 904 and 905 exchange data with the central processing unit 901 via the input / output port 903. The bus 906 is a common communication path used inside the computer. For example, the central processing unit 901 reads and writes data from and to the RAM 902 via the bus 906. Also, for example, the central processing unit 901 accesses the input / output port 903 via the bus 906.
[0115] At least some of the functions of each of the above-mentioned devices can be realized by a computer and a program. In that case, a program for realizing the functions may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into a computer system and executed to realize the functions. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, CD-ROMs, DVD-ROMs, and USB memories, and storage devices such as hard disks built into a computer system. In other words, the term "computer-readable recording medium" may be a non-transitory computer-readable recording medium. The term "computer-readable recording medium" may also include a medium that temporarily and dynamically holds a program, such as a communication line when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, and a medium that holds a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in that case. The above-mentioned program may be a program for realizing some of the above-mentioned functions, or may be a program that can be realized in combination with a program already recorded in the computer system.
[0116] [Second embodiment] Next, a second embodiment of the present invention will be described. Note that the matters already described in the previous embodiment may not be described below. Here, the matters unique to this embodiment will be mainly described.
[0117] 22 is a block diagram showing a schematic functional configuration of a receiving device according to this embodiment. As shown in the figure, the receiving device 2 includes a receiving unit 31 (transmitting and receiving unit), a content receiving unit 11, a decoding unit 12, a presenting unit 13, a profile determining unit 151, an environment determining unit 152, a conversion function unit 153A, a screen display unit 154, a reading function unit 17, an audio output unit 18, a commentary audio reproducing unit 19, and a playback position reading function unit 21. The receiving device 2 of this embodiment is characterized in that it includes the playback position reading function unit 21 that the receiving device 1 of the first embodiment did not have. Moreover, the receiving device 2 includes a conversion function unit 153A instead of the conversion function unit 153 of the first embodiment.
[0118] The playback position reading function unit 21 reads out information about the playback position of the content being played when a carousel menu (playback operation menu) is displayed during playback of the online streaming video content selected (determined) by the user.
[0119] The carousel menu is as described in the first embodiment with reference to FIG. 20 (playback screen SC3 while the carousel menu is displayed). As also described in the first embodiment, the carousel menu screen displays information on the total playback time of the currently played content (e.g., online streaming video content) and the current playback position (which can be expressed as a relative time from the start position of the content, in hours, minutes, and seconds). In other words, the player (presentation unit 13) running on the receiving device 2 holds information on the total playback time and current playback position of the currently played content. Note that while the content is being played, the information on the current playback position continues to change.
[0120] The content player (presentation unit 13) plays and presents the content while retaining the information of the current playback position as described above. The player (presentation unit 13) repeatedly passes the information of the total playback time and the current playback position to the conversion function unit 153A at a predetermined time interval (for example, every 0.1 seconds).
[0121] The conversion function unit 153A embeds the information on the total playback time and the current playback position received from the player (presentation unit 13) as a predetermined attribute value in an HTML file for displaying a carousel menu screen. In other words, the conversion function unit 153A converts the received information on the total playback time and the current playback position into data for an HTML screen (in the format of the description of the alt attribute value or the description of the aria-label attribute value). Since the current playback position changes dynamically unless playback in the player (presentation unit 13) is stopped, the conversion function unit 153A dynamically and repeatedly updates the HTML file of the carousel menu screen. In other words, the conversion function unit 153A dynamically and repeatedly converts the information on the total playback time and the current playback position into data for an HTML screen.
[0122] In other words, the conversion function unit 153A receives information on the playback position of the currently playing content from the player (presentation unit 13) presenting the content, converts the received playback position information into a description of the attribute value of a specified attribute for the data to be read aloud in a markup language file for screen display, and dynamically embeds it in the markup language file.
[0123] Furthermore, when the data to be read out in the metadata changes dynamically, the conversion function unit 153A dynamically converts the changed data to be read out into a description of the attribute value of a predetermined attribute for the data to be read out in the markup language file for screen display. Metadata that can change dynamically is, for example, content metadata and event metadata. All information included in the content metadata may be data that can change dynamically. As an example, when the originally scheduled broadcast end time is changed due to emergency news (for example, news of a disaster such as an earthquake), the information on the broadcast end time in the content metadata changes dynamically. In the example of the content metadata described in the first embodiment, the description ""endDate": "2023-03-09T19:30:00+09:00"" on the 63rd line (FIG. 12) may change to a description such as ""endDate": "2023-03-09T20:00:00+09:00". The information on the broadcast end time may change before the broadcast starts, or may change after the broadcast starts (during the broadcast). In such cases, the conversion function unit 153A dynamically converts the changed information into a description of the attribute value of a predetermined attribute for the data to be read aloud. Event metadata may be generated dynamically in response to a sudden event such as an earthquake, and in this case, too, the conversion function unit 153A dynamically converts information about the event that has occurred into a description of the attribute value of a predetermined attribute for the data to be read aloud. In this way, when the conversion function unit 153A responds to a dynamic change in the data to be read aloud in the metadata, the information that the receiving device 1 actually reads aloud as voice is also changed.
[0124] When the conversion function unit 153A dynamically rewrites a markup language file, it means that the browser 15 directly rewrites the information that the browser 15 refers to when drawing a screen. For example, if a markup language file exists on a file system and the browser 15 expands it in its own working memory space to draw a screen based on that markup language file, and if the browser 15 does not refresh its working memory at a predetermined frequency, the conversion function unit 153A does not simply rewrite the markup language file on the file system, but also rewrites the markup language file expanded in the working memory. This allows data updates made by the conversion function unit 153A to be immediately reflected on the screen and in the read-aloud voice.
[0125] In other words, the conversion function unit 153A extracts specified data to be read aloud from the metadata, converts the extracted data to be read aloud into a description of the attribute value of a specified attribute for the data to be read aloud in a markup language file for screen display, and further dynamically converts dynamically changing data to be read aloud into a description of the attribute value of a specified attribute for the data to be read aloud in a markup language file for screen display, or converts the data to a description of the attribute value of the specified attribute and dynamically embeds it in the markup language file.
[0126] The dynamically changing read-aloud target data is at least one of the read-aloud target data in the metadata and information on the playback position, which is the playback time of the content being played. When the conversion function unit 153A receives information on the playback position of the content being played from the presentation unit 13, it converts the received information on the playback position and dynamically embeds it in the markup language file, and when the read-aloud target data in the metadata changes, it dynamically converts the changed read-aloud target data.
[0127] The presentation unit 13 performs control so as to perform a screen display based on the markup language file converted by the conversion function unit 153A, and to perform a process of reading out the attribute value of the predetermined attribute by voice.
[0128] It is also possible to implement a conversion device 301 having the conversion function unit 153A. The conversion device 301 can perform the above-mentioned data conversion.
[0129] When the focus is on a specific position on the carousel menu screen (for example, the display position of the total playback time and the current playback position), the playback position reading function unit 21 extracts the HTML element (text information) embedded by the conversion function unit 153A and reads out the element. The method of reading out the element has already been described in the first embodiment.
[0130] The conversion function unit 153A may dynamically rewrite not only HTML for the carousel menu screen but also other HTML. That is, the conversion function unit 153 described in the first embodiment extracts necessary information (service name, content name (program name), and distribution start and end dates and times) from the acquired metadata (service metadata, content metadata, and event metadata) and converts it into a description in an HTML file. The conversion function unit 153A of this embodiment dynamically performs such data conversion and updates the HTML file. That is, when the metadata is updated, the conversion function unit 153A dynamically reflects the update in the description in the HTML file being displayed.
[0131] Although a number of embodiments have been described above, the present invention can also be embodied in the following modified examples.
[0132] [Variations] In each of the first and second embodiments, the receiving device was equipped with a commentary audio playback unit 19. As a variation of each embodiment, the receiving device may be configured not to have the commentary audio playback unit 19. In this case, the receiving device does not search for the location of commentary audio related to the content being played, for example, in the content metadata. Therefore, the receiving device does not access and obtain the commentary audio, and therefore the receiving device does not play the commentary audio. Even in this variation, the function of the conversion function unit (153 or 153A) is valid, and the information extracted from the metadata is embedded in the HTML as data to be read aloud.
[0133] Although an embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and designs that do not deviate from the gist of the present invention are also included. [Industrial Applicability]
[0134] The present invention can be used, for example, in services relating to content distribution and in devices and apparatuses for such services. However, the scope of use of the present invention is not limited to the examples given here. [Explanation of symbols]
[0135] 1,2 Receiving device 3 Content transmission device 5. Metadata provider 7. Web application server device 9 Content distribution provider equipment 11 Content Receiving Unit 12 Decoding section 13 Presentation part 15 Browsers 17 Reading function section 18 Audio output section 19 Commentary audio playback section 31 Receiving section (transmitting and receiving section, metadata receiving section) 100 Content Delivery System 150 Web Applications 151 Profile Judgment Unit 152 Environment Judgment Department 153,153A Conversion function unit 154 Screen display section (presentation section) 301 Converter 901 Central Processing Unit 902 RAM 903 Input / Output Ports 904,905 Input / Output Devices 906 Bus SC1 Portal Screen SC2 playback screen SC3 Playback screen with carousel menu displayed< / button>
Claims
1. a metadata receiving unit for receiving metadata related to content distribution; a conversion function unit that extracts predetermined data to be read out from the metadata, converts the extracted data to be read out into a description of an attribute value of a predetermined attribute for the data to be read out in a markup language file for screen display, and further dynamically converts dynamically changing data to be read out into a description of an attribute value of a predetermined attribute for the data to be read out in a markup language file for screen display, or converts the data to a description of the attribute value of the predetermined attribute and dynamically embeds it in the markup language file; a presentation unit that performs a screen display based on the markup language file converted by the conversion function unit and controls a process of reading out the attribute value of the predetermined attribute by voice; A receiving device comprising:
2. The dynamically changing read-aloud target data is at least one of the read-aloud target data in the metadata and information on a playback position, which is a time at which the content being played has already been played; when the conversion function unit receives information on a playback position of the content being played back from the presentation unit, the conversion function unit converts the received information on the playback position and dynamically embeds the information in the markup language file, and when the data to be read out in the metadata is changed, the conversion function unit dynamically converts the changed data to be read out.
2. The receiving device according to claim 1.
3. a conversion function unit which extracts predetermined data to be read aloud from metadata related to content distribution, converts the extracted data to be read aloud into a description of an attribute value of a predetermined attribute for the data to be read aloud in a markup language file for screen display, and further dynamically converts dynamically changing data to be read aloud into a description of an attribute value of a predetermined attribute for the data to be read aloud in a markup language file for screen display, or converts the data to a description of the attribute value of the predetermined attribute and dynamically embeds it in the markup language file; A conversion device comprising:
4. a metadata receiving unit for receiving metadata related to content distribution; a conversion function unit that extracts predetermined data to be read out from the metadata, converts the extracted data to be read out into a description of an attribute value of a predetermined attribute for the data to be read out in a markup language file for screen display, and further dynamically converts dynamically changing data to be read out into a description of an attribute value of a predetermined attribute for the data to be read out in a markup language file for screen display, or converts the data to a description of the attribute value of the predetermined attribute and dynamically embeds it in the markup language file; a presentation unit that performs a screen display based on the markup language file converted by the conversion function unit and controls a process of reading out the attribute value of the predetermined attribute by voice; A program for causing a computer to function as a receiving device comprising the above.
5. a conversion function unit which extracts predetermined data to be read aloud from metadata related to content distribution, converts the extracted data to be read aloud into a description of an attribute value of a predetermined attribute for the data to be read aloud in a markup language file for screen display, and further dynamically converts dynamically changing data to be read aloud into a description of an attribute value of a predetermined attribute for the data to be read aloud in a markup language file for screen display, or converts the data to a description of the attribute value of the predetermined attribute and dynamically embeds it in the markup language file; A program for causing a computer to function as a conversion device comprising the above.
Citation Information
Patent Citations
Device for reading out loud on-screen information, and program for reading out loud on-screen information
JP2018206009A
