KR100416028B1 - How to implement real-time davic service through web - Google Patents

Abstract

The present invention relates to a method for implementing a real-time DAVIC service through the web that enables subscribers to receive a DAVIC (Digital Audio Visual Council) service through a web browser.

According to the present invention, a web browser downloads a DAVIC service menu from a web server and then requests a client to establish a session so that the client establishes an S3 channel and an S2 channel with the DAVIC server. If necessary, the service transmits the string of the service selected by the subscriber on the DAVIC service menu to the DAVIC server through the client, interprets the string received by the DAVIC server, and then sets up an S1 channel with the client. By transmitting the contents of the service through the S1 channel in real time, and the service contents received by the client through the S1 channel in real time to the web browser, subscribers can use the DAVIC service using a web browser that is already familiar to use instead of MHEG. To be provided.

Description

A real-time DAVIC service implementation method through a web

The present invention relates to a DAVIC (Digital Audio Visual Council) service implementation method, and more particularly, to a real-time DAVIC service implementation method through a web that enables subscribers to receive a real-time DAVIC service through a web browser.

Standardization of interactive multimedia services in general is centered on DAVIC, a private standardization organization for digital audio / video services.

Davik, a private standardization organization established in March 1994, aims to establish open interfaces and protocols that ensure maximum interoperability between digital voice-visual applications and services.

In the present specification, an interactive multimedia service defined by DAVIC is referred to as a "DIVIC service", and a representative of these DAVI services includes a Video On Demand (VOD) service in which subscribers order and watch desired video when desired. .

FIG. 1 is a schematic configuration diagram of a DIVIC system proposed by the DAVIC standard, wherein the DIVIC system includes n clients (1-1 to 1-n), a transmission network (2), and a plurality of DAVIC servers ( 3a, 3b).

The clients 1-1 to 1-n request service to the DIV servers 3a and 3b through the delivery network 2 as a set top box (STB), and the DIV servers 3a and 3b It provides a predetermined DAVIC service to the subscriber via the delivery network (2). In addition, the DIVIC servers 3a and 3b include a subscriber management system for subscriber management.

In the above-mentioned DAVIC system, the connection point between the transport network 2 and the clients 1-1 to 1-n is defined as the A1 interface, and the connection point between the transport network 2 and the DABIC servers 3a and 3b is defined as the A9 interface. do.

In addition, the DAVIC system uses the "Digital Storage Media-Command Control (DSM-CC) protocol (ISO), a standard for common management and control of Moving Picture Experts Group (MPEG) bit streams stored on media regardless of the type of digital storage media. / IEC 13818-6) "is used for session establishment. Here, the session establishment refers to a task of creating an information exchange path between the subscriber and the davik server (3a, 3b) so that the subscriber can be provided with the davic service from the davik server (3a, 3b).

The DSM-CC protocol includes a DSM-CC UN (User to Network) protocol and a DSM-CC User to User (UU) protocol. The DSM-CC UN protocol sends and receives a message between a user (server or client) and a network, connects to a desired server from a client, establishes a session by allocating resources, controls a session, and releases resources. Provide a protocol to disconnect. The DSM-CC UU protocol is a media control protocol based on "CORBA (Common Object Request Broker Architecture)" which is a standard of heterogeneous distributed environment established by OMG (Object Management Group). In addition, Transmission Control Protocol / Internet Protocol (TCP / IP) is used as the underlying communication protocol of CORBA.

On the other hand, in the conventional DIV system, the client is provided with the desired DAVI service by accessing the DIV server through the DSM-CC using MHEG (Multimedia and Hypermedia information coding Expert Group) as a subscriber interface.

The MHEG is the most comprehensive multimedia / hypermedia information representation and interchange format standard suitable for network-based interaction type applications. The MHEG is a representation of the multimedia / hypermedia information, space-time synchronization, and mutual interaction so that information can be exchanged through a network. It defines encoding / decoding, including exchange, real-time transmission, and final form representation.

In order to operate the MHEG, the client must be equipped with a separate MHEG engine. The MHEG engine encodes / decodes multimedia / hypermedia information represented as MHEG objects, performs object interpretation for presentation processing, and interacts with a user. Here, the MHEG object refers to a coded representation of multimedia information.

However, the prior art as described above has a problem in that the subscribers have to interface with the Davi server using MHEG which is not familiar with the use of the Davi service to feel the inconvenience and unfamiliarity when using the Davi service.

The present invention has been made in order to solve the above problems, the subscriber can be provided by the web browser (Internet search tool) that is familiar to the user by providing the service to the DAVIC web that can facilitate the convenience of the subscriber The purpose is to provide a real-time davic service implementation method through.

In order to achieve the above object, a method for implementing a real-time DAVIC service through the web of the present invention includes a subscriber terminal having a client and a web browser installed therein, a DAVIC server providing a DAVIC service to the subscriber terminal, and A method for implementing a DIVIC service in a system having a web server for providing an Internet service, the method comprising: a first step of the web browser downloading a davic service menu from the web server, and the web browser establishing a session with the client; Requesting the client to set up the S3 channel and the S2 channel with the DIVIC server; and when the session setup is confirmed through the client, the web browser displays the string of the service selected on the DIVIC service menu. To the said DIVIC server via client A third step of transmitting, a fourth step of analyzing the string received by the DIVIC server, and then setting an S1 channel with the client to transmit the contents of the requested service in real time through the S1 channel; And a fifth step of delivering the service contents received through the S1 channel to the web browser in real time.

In addition, the present invention is a sixth step of the web browser transmits a service interruption string through the client via the client when the service interruption is requested while receiving the service content provided by the davic server through the client; And a seventh step of analyzing the string received by the DIVIC server, and then releasing the S1 channel with the client; and, if another service is selected on the DIVIC service menu before the session release request is made, the web browser is selected. An eighth step of transitioning to a third step of transmitting the string of characters to the DIVIC server through the client; and when the session release is requested, the web browser requests the client to release the session so that the client communicates with the DIVIC server. Ninth step of releasing the S2 channel and the S3 channel of the; When the release complete via the client session, a confirmation is preferably claim 10 wherein the web browser is closed the data big service menu display is further provided.

1 is a schematic configuration diagram of a DAVIC system proposed by the DAVIC standard;

2 is a schematic configuration diagram of a DAVIC system to which the present invention is applied;

3 is a sequence diagram of a real-time davic service implementation process through the web according to the present invention.

<Description of the symbols for the main parts of the drawings>

10: Personal Computer 11: Web Browser

12: Client 20: Davic Server

30: Session Resource Manager 40: Web server

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 2 is a schematic configuration diagram of a DIVIC system to which the present invention is applied. The DIVIC system includes a personal computer 10 equipped with a web browser 11 and a client 12, and the PC ( 10) session management and resource management between the DAVIC server 20 that provides the DAVI service using the Asynchronous Transfer Mode (ATM) as the backbone, and the PC 10 and the DAVIC server 20. A session resource manager (SRM) 30 to perform and a web server 40 for providing an Internet service having an Internet protocol (IP) as a backbone to the PC 10 are provided.

The web browser 11 provided in the PC 10 is connected to the web server 40 to receive various Internet services and to download a davic service menu in the form of HTTP (HyperText Transfer Protocol).

The web server 40 provides a davic service menu in HTTP format when requested by the web browser 11. The HTTP is a download protocol for transmitting the software of the web server 40 to the PC 10, and the software at this time is generally an image. Since the download protocol is a transfer data call from the PC 10 to the PC 10 required for initialization, the download protocol is preferably stored in the form of a ROM or a flash ROM.

The client 12 and the DAVIC server 20 support the DSM-CC protocol according to the DAVIC standard. Specifically, the S12 channel to which the DSM-CC UN protocol is applied must be set up. The channel and the S1 channel are set up, and the S2 channel and the S1 channel are set up before the subscriber can receive the DAVIC service (various information or data) from the DIVIC server 20. Here, the S1 channel is a media stream channel used to deliver high bandwidth bulk data, such as an MPEG-2 transport stream, the S2 channel is an application control channel used to accommodate subscriber needs, and the S3 channel is used with a subscriber. Session establishment signaling channels used to establish sessions between service providers, all of which are defined in the Davik specification.

In addition, the client 12 maps (ie, protocol converts) an HTTP string of a service selected on the DIVIC service menu to a DSM-CC protocol string, and transmits the MPEG-2 transmitted from the DIVIC server 20. Decodes the compressed video bit stream. The DIVIC server 20 stores the video bit stream compressed in MPEG-2 for each service, and reads the stored video bit stream in real time to the client 12 when the subscriber requests it.

The SRM 30 includes message decoding, a protocol finite state machine (PFSM), a message encoding, a command execution routine, and the like for performing session management and resource management. . The SRM 30 first opens a socket and pays attention to the message. When the message arrives, the SRM 30 decodes the message and determines what event it is. The event and current state variables are put into the PFSM to determine what the next state and the next run command are. Encode data to allocate sessions, allocate resources, and send messages. The encoded data is transmitted to the DIVIC server 20 or the client 12.

Referring to the sequence shown in FIG. 3, the real-time DAVIC service implementation process through the web in the DAVIC system configured as described above will be described in detail as follows.

3 is a sequence diagram of a real-time davic service implementation process through the web according to the present invention.

First, the subscriber operates the web browser 11 installed in the PC 10 and enters the Internet address of the web server 40 to access the web server 40.

The subscriber accessing the web server 40 requests the davic service menu in HTTP format through the web browser 11 and downloads the davic service menu from the web server 40.

The web browser 11 displays the downloaded DAVIC service menu on the screen of the PC 10 and delivers a "session setup and attach request" message to the client 12. 12 sets the DIC server 20, the S3 channel, and the S2 channel in order.

The setting of the S3 channel and the S2 channel is performed through the process of exchanging the DSM-CC UN protocol message between the client 12 and the DIV server 20. More specifically, the S3 channel and the S2 channel setting process are performed by the client ( 12) requests the setup of the S3 channel by sending the message "S3 flow setup request" to the DIVIC server 20, and then sets up the "S3 channel setup" from the DIVIC server 20 to (12). Receive the confirmation (S3 flow setup confirm) message to confirm the setting of the S3 channel, and transmits the "S2 channel setup request (S2 flow setup request)" message to the DIVIC server 20 again and then the DIVIC server ( Receiving an "S2 flow setup confirm" message from the 20) to confirm the configuration of the S2 channel.

When the setting of the S3 channel and the S2 channel is completed through the above process, that is, when the client 12 receives the "S2 channel setup confirmation" message from the DAVIC server 20, the session setup and the session are sent to the web browser 11. Message to indicate that the session setup is complete.

Thereafter, the web browser 11 delivers the HTTP string of the selected service to the client 12 when the service selected by the subscriber on the DAVID service menu exists. That is, when a subscriber selects a predetermined service by viewing a David service menu displayed on the screen of the PC 10 and operating a mouse or a keyboard (not shown), the web browser 11 displays a string of the selected service as a client. Deliver to (12).

In the above, the client 12 maps (protocol converts) the HTTP string of the service received from the web browser 11 to the DSM-CC UU string, and then transmits the HTTP string to the DIVIC server 20 through the S2 channel.

The DIVIC server 20 receives and interprets the string of the service selected by the subscriber through the S2 channel, and then transmits a "S1 channel setup request" message to the client 12 through the S2 channel. Request the configuration of the S1 channel, and then receive the message "S1 flow setup confirm" from the client 12 through the S2 channel again. Stream) is transmitted to the client 12 in real time through the S1 channel.

The client 12 decodes the MPEG-2 bit stream received from the DIVIC server 20 in real time through the S1 channel, converts the protocol, and then delivers the protocol to the web browser 11 in real time. As a result, the subscriber can be provided with the DAVIC service through the web browser 11 that can be used in a familiar manner, and when the subscriber wants to receive the DAVIC service even while using the Internet service, the subscriber can directly operate the DH service without using the MHEG engine. You can be provided with a service.

When the service is selected by the subscriber while receiving the DAVIC service through the above process, the web browser 11 delivers the HTTP string of the service to the client 12. That is, when the subscriber selects the service interruption from the DAVID service menu displayed on the screen of the PC 10, the web browser 11 delivers the string of the service interruption to the client 12.

When the client 12 receives the string of the service interruption, the client 12 maps the HTTP string to the DSM-CC UU string and transmits the string to the DIVIC server 20 through the S2 channel.

When the service interrupt string is received through the S2 channel, the DIVIC server 20 transmits an S1 flow release request message to the client 12 through the S2 channel to request the release of the S1 channel. The S1 channel is released through a process of confirming the release of the S1 channel by receiving a "S1 flow release confirm" message from the client 12 through the S2 channel.

On the other hand, if the subscriber selects another service on the DIVIC service menu after the S1 channel is released and before the session is requested to be released by the subscriber, the web browser 11 delivers the string of the selected service to the client 12 again. Is performed.

On the other hand, when the session release is requested by the subscriber after the S1 channel is released, the web browser 11 transmits a "session release and detatch request" message to the client 12 to the client 12. To release the DIC server 20, the S2 channel, and the S3 channel in sequence.

The release of the S3 channel and the S2 channel is performed through the process of exchanging the DSM-CC UN protocol message between the client 12 and the DIV server 20 as in the case of setting the channel. More specifically, the S3 channel and the S2 channel are performed. The release process requests that the client 12 release the S2 channel by sending a message “S2 flow release request” to the DIV server 20, and then, from the DAVID server 20 (12), Confirms the release of the S2 channel by receiving a "S2 flow release confirm" message, and transmits the "S3 flow release request" message to the DIVIC server 20 again. Receiving the "S3 flow release confirm" message from the DIVIC server 20 to confirm the release of the S3 channel.

When the release of the S2 channel and the S3 channel is completed through the above process, that is, when the client 12 receives the "S3 channel release confirmation" message from the DIV server 20, the session release and the session release to the web browser (11). Message indicating that session release is complete by sending a "session release and detatch confirm" message.

Thereafter, when the web browser 11 confirms the completion of the session release through the " session release and detach confirmation " message received from the client 12, the display of the davic service menu displayed on the screen of the PC 10 is displayed. To exit.

As described above, the present invention enables the subscriber to be provided with the DAVIC service by using a web browser that is already familiar to use instead of the MHEG.

Claims (2)

A method for implementing a DIVIC service in a system having a subscriber terminal having a client and a web browser installed therein, a DIVIC server providing a DIV service to the subscriber terminal, and a web server providing Internet service to the subscriber terminal, A first step of the web browser downloading a davic service menu from the web server, A second step of the web browser requesting the client to establish a session so that the client establishes an S3 channel and an S2 channel with the dabig server; A third step of transmitting, by the web browser, the string of the service selected on the DIVIC service menu to the DIVIC server through the client when it is confirmed that the session setup is completed through the client; A fourth step of interpreting the string received by the DIVIC server and then setting an S1 channel with the client to transmit the contents of the requested service in real time through the S1 channel; And a fifth step of delivering the service contents received by the client through the S1 channel to the web browser in real time. The method of claim 1, A sixth step of transmitting, by the web browser, a service interruption string to the davic server through the client when a service interruption is requested while receiving the service contents provided by the davic server through the client; A seventh step of analyzing the string received by the DIVIC server and then releasing the S1 channel with the client; An eighth step of transitioning to a third step of transmitting, by the web browser, the string of the selected service to the DAVID server through the client if another service is selected on the DAVID SERVICE menu before the session release is requested; A ninth step of requesting the client to release the session when the session release request is made, causing the client to release the S2 channel and the S3 channel with the DIVIC server; And a tenth step of terminating the display of the DIVIC service menu by the web browser when it is confirmed that the session release is completed through the client.