WO2013187815A1

WO2013187815A1 - Network node and method for displaying a code on a screen

Info

Publication number: WO2013187815A1
Application number: PCT/SE2012/050646
Authority: WO
Inventors: Ola Andersson; Robert Skog; Jacob STRÖM
Original assignee: Telefonaktiebolaget L M Ericsson (Publ)
Priority date: 2012-06-14
Filing date: 2012-06-14
Publication date: 2013-12-19

Abstract

Method and network node (12, 20) for displaying a code on a screen (14) comprising receiving,from an operator node (10) comprised in the operator network (22), a data stream comprising data and meta data and extracting the data and the meta data from the received data stream. The network node sends the extracted data to be displayed on the screen and stores the meta data. The network node then retrieves a code generated from the stored meta data, when receiving from a pre-configured communication device (16) a request for the code and sends the code to be displayed on the screen.

Description

NETWORK NODE AND METHOD FOR DISPLAYING A CODE ON A SCREEN TECHNICAL FIELD

The present disclosure relates to displaying a code on a screen. More particularly, the disclosure relates to a method and a network node for displaying a code on a screen.

BACKGROUND

Television, TV, provides contents in the form of e.g. audio and video that attracts people all around the world. However, the TV is now a day experiencing competition from other medium such as websites .

In terms of advertisement revenues, the TV is still holding up and even experiencing growth in the near future. It is in the interest of broadcasters such as cable-TV companies to increase the impressiveness of the TV-experience in order to stay

competitive . To further attract users, access to additional material that is complementary to a TV-show has been introduced. As example, on the screen, links to web sites including additional material is often displayed or announced in e.g. a newscast. However, since the link to the web site has to be displayed on the screen or announced for a certain amount of time, it may be disturbing for the end user. Further, the end user has to remember the link to the website for later use.

Another attraction is to present links to web sites where the end user is able to buy items shown on the screen, e.g. clothing and jewellery items. The user may purchase an item of interest by simply clicking on it. However, the TV presenting the clickable items has to be equipped with a mouse or other pointing device. Further, the TV may not be the ideal device for surfing, making the purchase experience less than ideal. It is also known that a code, such as a Quick Response Code, QR- code or a barcode may be used in commercials allowing an end user to be directly taken to a web site selling an item, perhaps for a special price. The displayed code can be decoded by a code reader such as a barcode reader. Such a reader may be comprised in a user terminal or can be downloaded as an additional application to the user terminal. The end user is then able to obtain the code by scanning it, e.g. by taking a picture of it using the user terminal . The reader in the user terminal decodes the code and shows the content of it. The content may comprise e.g. a Uniform Resource Locator, URL, pointing to a specific site.

One example of a conventional architecture is shown by Figure 1, in which an operator node 10, a set-top-box, STB 12, an operator network 22, a screen 14 and a screen comprising an STB 20 is shown.

Usually an operator node may be connected to several STBs.

However, for simplicity only one STB 12 is shown in Figure 1. Further, the operator network 22 may be partly or totally owned by an operator supervising delivery of services.

In Figure 1, the operator node 10 is normally in communication with the STB 12 and may continuously send data to the STB 12 as shown in SI. The data in this context refers to media such as audio stream, video stream, subtitles, Electronic Programming

Guide (EPG) , etc. The data may also contain additional embedded material such as a URL, a barcode or a QR-code. Referring back to Figure 1, the STB 12 receives in SI the data and if needed renders the data to be suitable to be displayed on the screen 14. The STB 12 may also be part of the screen 14 which is illustrated in Figure 1 as dotted lines donated 20.

Further, the screen receives the data in S2 and displays it.

Additional material such as a URL or a code embedded in the data may also be shown to the end user. As example, while displaying a commercial, a code may also be displayed to the end user. The commercial in this example corresponds to the data and the code corresponds to the additional material embedded in the data.

Given that a commercial may be short in time and by displaying e.g. a URL or a code during the commercial, it can be quite a challenge for the end user to e.g. find the user terminal, start the code reader application and scanning the code before the commercial ends. Further, the code has to be big enough to be easily captured and has to stay on long enough in order for the user to have time to make the capturing. Moreover, even on a system with a hard drive, the user must take care to go back in time to revisit the place where the code is displayed.

Thus, it is desirable to efficiently provide the end user with additional material that is complementary to a TV-show.

SUMMARY

It is an ob ect of embodiments described hereinafter to address at least some of the issues outlined above. It is also an object to display to an end user a code on a screen when receiving a request from a pre-configured communication device. These objects and others are achieved by the method and the arrangement according to the appended independent claims, and by the embodiments according to the dependent claims.

According to a first exemplary aspect, embodiments provide a method in a set-top-box, STB, of an operator network for

displaying on a screen a code. The method comprises receiving from an operator node comprised in the operator network, a data stream comprising data and meta data. The method further

comprises extracting the data and the meta data from the received data stream and sending the extracted data to be displayed on the screen. Next, the method comprises storing the meta data and retrieving a code generated from the stored meta data, when receiving from a pre-configured communication device a request for the code and sending the code to be displayed on the screen.

According to one aspect of the above mentioned method, the code is one of a Quick Response Code, a QR code, or a bar code.

Optionally, the meta data is stored locally or at an external hard drive or at an external storage comprised in the operator network .

According to an aspect, the method comprises sending an

indication to be displayed on the screen, the indication

informing that at least one code is stored to be requested.

Optionally, the method comprises deleting the stored meta data based on any of: expiry of a timer comprised in the meta data, expiry of a predefined time period set in the STB or by a user request. According to a second exemplary aspect, embodiments provide a network node comprising a set-top-box, STB, of an operator network for displaying on a screen a code. The network node comprising a receiver circuit configured to receive, from an operator node comprised in the operator network, a data stream comprising data and meta data. The network node further comprises a logical circuit configured to extract the data and the meta data from the received data stream and a transmitter circuit configured to transmit the extracted data to be displayed on the screen. Further, a retriever circuit is configured to retrieve a code generated from the meta data, upon request from a pre- configured communication device. The transmitter circuit is further configured to transmit the code to be displayed on the screen .

According to one aspect, the network node comprises a storage circuit configured to store the meta data.

Optionally, the network node comprising requesting the meta data internally from the STB or from an external hard drive or from an external storage comprised in the operator network.

According to an aspect, the network node comprises the STB and the screen.

An advantage achieved by at least some of the above mentioned embodiments is that an end user may at any time request a code to be displayed on the screen, which gives a better end user service .

Further possible features and benefits of this solution will become apparent from the detailed description below. BREIF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments will now be described in more detail, and with reference to the accompanying drawings, in which: Figure 1 schematically illustrates a first conventional exemplary signalling diagram for sending data to be displayed on a screen.

Figure 2 is a flowchart illustrating an exemplary embodiment of a method in a set-top-box for displaying a code on a screen.

Figure 3 is a schematic block diagram showing some components of a network node.

Figure 4 schematically illustrates an exemplary signalling diagram for sending by a set-top-box a code to be displayed on a screen .

DETAILED DESCRIPTION

In the following description, the embodiments will be described in more detail with reference to certain embodiments and to accompanying drawings. For purposes of explanation and not limitation, specific details are set forth, such as particular scenarios, techniques, etc., in order to provide a thorough understanding. However, it is apparent to one skilled in the art that the present invention may be practised in other embodiments that depart from these specific details.

Moreover, those skilled in the art will appreciate that the functions and means explained herein below may be implemented using software functioning in conjunction with a programmed microprocessor or general purpose computer, and/or using an application specific integrated circuit (ASIC). It will also be appreciated that while the current invention is primarily described in the form of methods and devices, the invention may also be embodied in a computer program product as well as in a system comprising a computer processor and a memory coupled to the processor, wherein the memory is encoded with one or more programs that may perform the functions disclosed herein.

Figure 2 is a flowchart illustrating a method for sending a code to be displayed on a screen according to embodiment of this disclosure. The method is to be implemented in an STB 12.

The method comprises receiving S21 a data stream comprising data and meta data. The data stream is received from an operator node comprised in an operator network, not shown in Figure 2. However, an example of an operator node is shown in e.g. Figure 3 and

Figure 4 referred to as 10. Similarly, an example of an operator network is shown in e.g. Figure 3 and Figure 4 referred to as 22. According to this disclosure, the data may comprise audio and video stream, Electronic Programming guide, subtitles etc.

whereas the meta data relates to information that may be

translated into a code such as a QR-code which may be decoded using a code reader. The received meta data may also include other information such as deletion of the meta data upon expiry of a timer comprised in the meta data.

Normally the STB receives coded data according to a video format, such as the H.264 format, which is a standard for video

compression. According to this embodiment, the received data stream may correspond to the coded data. According to the H.264 standard, the data stream may comprise video and audio stream. However, additional material such as the meta data described above may also be comprised in the data stream. Such additional material may be inserted as user data in the data stream.

Referring back to Figure 2 and after receiving the data stream at the STB 12, the method comprises extracting S22 the received data stream, i.e. the data and the meta data. The extracting S22 may comprise decoding the received data stream. The decoding may be performed by a decoder comprised in the STB 12. Further, the STB 12 may also request an appropriate node in the operator network 22 to decode the data stream.

Once the data stream is decoded, the STB 12 locates the meta data as well as the data. The technique for decoding the received data stream is well-known as such and does not add any important sub ect matter to this disclosure, thus not explained any further .

If the STB 12 is a legacy STB, the meta data may not be

recognized and the H.264 standard simply demands the decoder in the legacy STB to ignores it, e.g. by stripping away the meta data. The legacy STB will however recognize the data and will deal with it, e.g. by sending it to be displayed on the screen as described in connection with S23 below. Going back to Figure 2 and after the extracting in S22, the method comprises sending S23 the extracted data, e.g. the audio and the video stream to be displayed on a screen, not shown in Figure 2. However, an example of a screen is shown in Figure 3 and in Figure 4 referred to as 14.

According to an embodiment, not shown in Figure 2, the screen may comprise the STB 12. Consequently the extracted data is sent internally from the STB 12 to be displayed on the screen 14. An example of a screen 14 comprising an STB 12 is shown in e.g.

Figure 3 and in Figure 4 referred to as 20. Referring back to Figure 2, the method comprises storing S24 the meta data. The meta data may be stored locally or at an external storage, such as an external hard drive or an external node comprised in the operator network 10. If the meta data is stored at an external storage, it may be retrieved upon a request from the STB 12.

Optionally, there may be a step of sending (not shown in Figure 2) an indication to be displayed on the screen, the indication informing that at least one code is stored. An example of such an indication is shown in e.g. Figure 4 referred to as S.47.

In Figure 2, the method further comprises receiving S25 a request for a code, e.g. a barcode or a QR-code. The request may be received from a communication device controlled by an end user, such as a remote control using infrared technique or any other communication device capable of communicating with the screen 14 and/or the STB 12 without active configuration of the device by the end user. A communication device not requiring active configuration is hereinafter referred to as a pre-configured communication device.

An example of a device that needs active configuration by an end user may relate to a device that is able to communicate with the screen 14 and/or the STB 12 after it has been configured by an end user. For instance, a device that requires the IP address of the STB 14 and a connection to the same network as the STB 14. An example is to connect a user terminal to the STB 14 wirelessly via WLAN or Bluetooth. Such a wireless connection (WLAN or

Bluetooth) must be configured by the end user before usage. The end user needs to configure the user terminal to connect to the wireless network and needs to provide the user terminal or an application comprised in the user terminal with the IP address of the STB 14.

An example of a pre-configured communication device may relate to a remote control belonging to the screen 14 or to the STB 12. Such a remote control does not need any configuration from the end user to communicate with the screen 14 and/or the STB 12. A remote control does not either require a network connection to communicate. Further, a remote control communicates over an infra-red connection that is preconfigured and user friendly.

The pre-configured communication device may comprise a "request code" button for requesting a code and/or a "menu" button for accessing the settings of the screen and/or the STB 12. The settings may comprise a "request code" function for requesting a code. Thus a code may be requested at any time using the above described button or function which is flexible from an end user perspective .

According to Figure 2 and after receiving S25 a request for the code, the method comprises retrieving S26 the code. The code is retrieved from the meta data. The retrieved code may include one of a Uniform Resource Identifier, URL, a plan text or a

combination of a URL and a plan text or any other information that may be interpreted by a code reader. The technique for generating the code from the stored meta data is well-known as such and is not necessary to describe here to understand the solution. If the meta data is stored in a an external storage the STB 12, may request the meta data and perform the generation locally. The STB 12 may also request the code from the external storage. In the later, it is assumed that the external storage is able to generate a code from the meta data.

Referring back to Figure 2, the method comprises sending S27, the retrieved code to be displayed on the screen. The code, e.g. the QR-code may be displayed on the screen according to a predefined setting such as covering a large portion of the screen or according to settings specified by the end user such as covering a large portion of the screen, covering the whole screen or covering a small portion of the screen etc. The screen may keep showing the indication until a "stop showing request" is received by the pre-configured communication device. The screen may also show the indication until an expiry of a timer for stop

displaying the code is reached. Such a timer may be preconfigured in the STB 12 and/or may be configured by the end user. As an option, there may be a step of deleting (not shown in

Figure 2) the stored meta data based on any of: expiry of a timer comprised in the meta data, expiry of a predefined time period set in the STB 12 or by an end user request. Thus, the end user is able to request a code without making any configuration between the screen 14 and/or the STB 12 and the pre-configured communication device.

A non limiting example of how a network node 12, 20 may be configured to accomplish the above described solution is

illustrated by the block diagram in Figure 3. The network node may be an STB 12 or a screen 14 comprising an STB 12 referred to as 20.

The network node 12, 20 comprises a receiver circuit 30

configured to receive from an operator node 10 a data stream comprising data and meta data. As previously mentioned, the data may comprise audio and video stream, Electronic Programming guide, subtitles, etc. Whereas the meta data relates to

information that may be translated into a code which may be decoded using a code reader.

Referring back to Figure 3, the network node comprises a logical circuit 32 configured to extract the data and the meta data from the received data stream and a transmitter circuit 34 configured to transmit the extracted data to be displayed on the screen 14.

The transmitter circuit 34 may in an optional step, send to the screen an indication to be displayed on the screen, the

indication informs the end user that additional information is available, e.g. that at least one code, e.g. a QR-code is available .

Going back to Figure 3, the network node comprises as an optional step a storage circuit 37a configured to store the extracted meta data. The storage may also be done externally e.g. in an external storage node 37b .

According to Figure 3, the network node comprises a retriever circuit 36 configured to retrieve a code generated from the meta data. The code may be requested by a pre-configured communication device such as a remote control or any other communication device capable of communicating with the screen and/or the STB 12 without active configuration of the device by an end user

Finally, the network node transmits by the transmitter circuit 34 the code to be displayed on the screen.

It should be noted that Figure 3 illustrates various functional circuits in the network node 12, 20 and the skilled person is able to implement these functional circuits in practice using suitable software and hardware. Thus, the solution is generally not limited to the shown structures of the network node 12, 20, and the functional circuits 30-37a may be configured to operate according to any of the features described in this disclosure, where appropriate.

The functional circuits 30-37a described above can be implemented in the network node by means of program modules of a respective computer program comprising code means which, when run by a processor "P" causes the network node to perform the above- described actions and procedures. The processor P may comprise a single Central Processing Unit (CPU) , or could comprise two or more processing units. For example, the processor P may include a general purpose microprocessor, an instruction set processor and/or related chips sets and/or a special purpose microprocessor such as an Application Specific Integrated Circuit (ASIC) . The processor P may also comprise a storage for caching purposes. Each computer program may be carried by a computer program product in the network node in the form of a memory "M" having a computer readable medium and being connected to the processor P. The computer program product or memory M thus comprises a computer readable medium on which the computer program is stored e.g. in the form of computer program modules "m" . For example, the memory M may be a flash memory, a Random-Access Memory (RAM) , a Read-Only Memory (ROM) or an Electrically Erasable Programmable ROM (EEPROM) , and the program modules m could in alternative embodiments be distributed on different computer program products in the form of memories within the network node.

One example of architecture describing an example according to this disclosure will now be described with reference to Figure 4. According to Figure 4 there is provided an operator node 10, a

STB 12, a Screen 14, a pre-configured communication device 16, an end device 18, an operator network 22 and a network node 20.

The operator node 10 and the STB 12 may be parts of the operator network 22. The operator network 22 may be a network partly or totally owned by an operator supervising delivery of services. Examples of such services are video on demand, TV on demand, streaming of sports events, regular TV shows etc.

The STB 12 is connected to a screen 14 such as a television, a computer display or any other types of displays. The STB 12 may be a separate node or may be part of a network node 20.

According to one embodiment, the network node 20 comprises the STB 12 and the screen 14. Examples of such a network node 20 are a TV/screen with an integrated STB 12, a media device system such as a computer comprising an STB functionality or any similar medium capable of receiving and interpreting a data stream.

In relation to Figure 4, data stream are sent according to step S41 from the operator node 10 to the STB 12. The data stream comprises data and meta data. The data may comprise audio, video,

Electronic Programming guide, subtitles etc. The meta data relates to information that may be translated into a code which may be decoded using a code reader.

The STB 12 receives the data stream from the operator node 10 and extracts in step S42 the data and the meta data from the received data stream.

If the STB 12 is a legacy STB, it will not be capable of interpreting the received meta data and will therefore discards it in step S43 . However, according to this disclosure, the STB 12 is able to recognize the extracted meta data and will therefore not discard it. As such, step S43 is illustrated as an optional step with a dotted arrow as it is only executed for a legacy STB. Still referring to Figure 4, the STB 12 transmits in step S44 the extracted data to be displayed on the screen 14 and stores in S45 the meta data. As mentioned above, the storage may be internally, i.e. in a memory comprised in the STB 12 or externally e.g. in a storage device or in a separate storage node located in the operator network 22.

Normally, the STB 12 continuously receives data streams from the operator node 10. For each data stream received, the STB 12 starts over and performs steps S42-S45, illustrated as a loop S46 in Figure 4. As such, the STB 12 will detect for each data stream whether meta data is comprised in the stream.

In Figure 4 and in an optional step S47 , the STB 12 may send an indication to the screen 14 indicating that a code exists and may be requested. The STB 12 may then receive in step 48 from the end user and via a pre-configured communication device 16 a request for retrieving the code. The STB 12 then retrieves in step S49 the requested code from the meta data and transmits in step S50 the code to be displayed on the screen 14. In optional steps S51 -S53 in Figure 4, the end user may in step S51 request the end device 18, e.g. a user terminal to take a picture or to scan the displayed code. The end device then takes in step S52 a picture of the code and decodes in step S53 the captured picture. The decoded picture, e.g. a decoded QR-code may comprise instructions to be executed by the end device. As example, the end device reads the QR-code and obtains there from instructions such as to enter a website using a Uniform Resource Identifier, URL, pointing to that website. The end user using the end device may then be directed to e.g. new applications, new websites, online shopping site etc.

Other instructions may be to show the content of the decoded QR- code which may comprise a plain text or a URL or a URL in combination with a plan text or any other instructions that can be interpreted by the end device.

Another not limiting example of implementing the solution in practice in the context of sending a code to be displayed on a screen will now be described.

An H.264 data stream is structured in Network Abstraction Layer- units (NAL-units) . A NAL-unit can contain the information necessary to decode a picture. The first byte of each NAL-unit is a header byte that contains an indication of the type of data in the NAL-unit and the remaining bytes contain payload data of the type indicated by the header. A typical sequence comprises 3 NAL- units may look as follows: 1. NAL: 2500 bytes

nal_unit_type = 1

Payload comprising information for decoding e.g. image 0

2. NAL: 1789 bytes

nal_unit_type = 1

Payload comprising information for decoding e.g. image 1 3. NAL: 257 bytes

nal_unit_type = 6

Payload comprising meta data that may be translated into a code, e.g. a QR-code. The first two NAL-units are of type 1 which means that they contain payload and pixel information of an image, the pixel information comprises information for decoding the image.

The third NAL-unit is of type 6, which means that the payload contains additional information. This NAL-unit does not contain data about the pixels. A legacy decoder comprised in an STB will recognize that the payload type is equal to 6 and will ignore it, so it should not impose any problems to a legacy STB. On the other hand, an STB according to this disclosure will parse the payload and will detect that it comprises meta data. The STB will further store the meta data internally or externally and will upon request retrieve a code from it. The retrieved code is then sent to be displayed on the screen.

While the solution has been described with reference to specific exemplary embodiments, the description is generally only intended to illustrate the inventive concept and should not be taken as limiting the scope of the solution. For example, the terms

"operator node", "network node", "end device", "set-top-box" and "screen" have been used throughout this description, although any other corresponding nodes, functions, and/or parameters could also be used having the features and characteristics described here. The solution is defined by the appended claims.

Claims

1. A method in a set-top-box, STB, (12) of an operator network (22) for displaying on a screen (14) a code, the method

comprises :

receiving (S21), from an operator node (10) comprised in the operator network (22), a data stream comprising data and meta data;

extracting (S22) the data and the meta data from the received data stream;

sending (S23) the extracted data to be displayed on the screen;

storing (S24) the meta data;

retrieving (S26) a code generated from the stored meta data, when receiving (S25) from a pre-configured communication device a request (16) for the code;

sending (S27) the code to be displayed on the screen.

2. The method according to claim 1 wherein the code is one of a Quick Response Code, a QR code, or a bar code.

3. The method according to claim 1 or 2 wherein storing (S24) the meta data comprises: storing the meta data locally or in an external hard drive or in an external storage comprised in the operator network.

4. The method according to claim 3 and wherein the meta data is stored in an external hard drive or in an external storage comprised in the operator network comprises: requesting the meta data;

5. The method according to any of the preceding claims 1-4 wherein retrieving (S26) a code generated from the stored meta data comprises:

Retrieving the code locally or requesting the code from the external hard drive or from the external storage comprised in the operator network.

6. The method according to any of the preceding claims 1-5 wherein the retrieving (S26) further comprises: retrieving a code including one of a Uniform Resource Identifier, URL, a plan text or a combination of a URL and a plan text.

7. The method according to any of the preceding claims 1-6, wherein the receiving (S25) comprises receiving the request (16! over a infra-red connection.

8. The method according to any of the preceding claims 1-7, wherein the method comprises: sending an indication to be displayed on the screen, the indication informing that at least one code is stored to be requested.

9. The method according to any of the preceding claims 1-8, wherein the method comprises deleting the stored meta data based on any of: expiry of a timer comprised in the meta data, expiry of a predefined time period set in the STB or by a user request.

10. A network node (12, 20) comprising a set-top-box, STB (12) of an operator network (22) for displaying on a screen (14) a code, the network node (12, 20) comprising:

- a receiver circuit (30) configured to receive, from an operator node (10) comprised in the operator network (22), a data stream comprising data and meta data; - a logical circuit (32) configured to extract the data and the meta data from the received data stream;

- a transmitter circuit (34) configured to transmit the extracted data to be displayed on the screen;

- a retriever circuit (36) configured to retrieve a code generated from the meta data, upon request from a pre- configured communication device(16);

- the transmitter circuit (34) is further configured to transmit the code to be displayed on the screen.

11. The network node (12, 20) according to claim 10 comprising: a storage circuit (37) configured to store the meta data;

12. The network node (12,20) according to claim 10-11 comprising: requesting the meta data internally from the STB or from an external hard drive or from an external storage comprised in the operator network.

13. The network node (12, 20) according to any of the preceding claims 10-12 wherein the code retrieved by the retriever circuit

(36) is one of a Quick Response Code, a QR code, or a bar code.

14. The network node (12, 20) according to any of the preceding claims 10-13 wherein the code retrieved by the retriever circuit (36) includes one of a Uniform Resource Identifier, URL, a plan text or a combination of a URL and a plan text.

15. The network node (12, 20) according to any of the preceding claims 10-14, wherein the transmitter circuit (34) is configured to send to the screen (14) an indication to be displayed on the screen, the indication informing that at least one code is stored.

16. The network node (12, 20) according to any of the preceding claims 10-15, wherein the stored meta data is deleted based on any of: expiry of a timer comprised in the meta data, expiry of a predefined time period set in the STB or by a user request.

17. The network node (20) according to any of the preceding claims 10-16, wherein the network node comprises the STB (12) and the screen ( 14 ) .