KR0174917B1 - How to cancel session release in DSM protocol - Google Patents

Abstract

The present invention relates to a client session release cancellation method for canceling a session release initiated by a client in the DSM-CC protocol. The present invention provides a method for canceling a session release, comprising: providing a client release cancellation request message from a client to a network in order to cancel the session release; ; When the client release cancel request message is received, forwarding a server release cancel instruction message to a server; In response to the server cancel cancellation instruction message, canceling the server's session cancellation if the server's session cancellation is cancelable, and sending a server cancellation cancellation response message to the network indicating that the server's session cancellation has been cancelled. ; And upon receiving the server release cancellation response message, canceling the session release of the network and transmitting a client release cancellation confirmation message to the client indicating that the session release of the network has been cancelled.

Description

How to cancel session release in DSM-CC protocol

1 is a diagram illustrating a regular procedure for session release initiated by a client under a DSM-CC protocol.

2 is an apparatus diagram between a server, a network, and a client to which the present invention is applied.

3 is a flowchart illustrating a method of canceling session release in the DSM-CC protocol according to the present invention.

* Explanation of symbols for main parts of the drawings

100: client 102: network interface

104: MPEG2 transport 106: MPEG2 decoder

108: graphic control unit 110: system control unit

112: cancel command processor 114: memory

200: network 202: session controller

204: Cancel command processor 206: Resource control unit

300: server 302: storage unit

304: MPEG2 stream control unit 306: Melt program control unit

308: Command control unit 310: Cancel command processor

The present invention relates to a command processing method between an interactive CATV, a server, and a network, and particularly disclosed by a client in a digital storage media command and control (hereinafter, abbreviated as DSM-CC) protocol. The session release cancellation method in the DSM-CC protocol allows one session release to be canceled.

Many digital storage media have different defined control commands. Thus, a user must know a set of differently defined digital storage media control commands in order to access MPEG bitstreams from other digital storage media.

The DSM-CC standard proposed by ISO to address these shortcomings is based on the ISO / IEC 11172 (MPEG-1) bitstream and ISO / IEC stored in the media, regardless of what digital storage media is used in the near or far-area. 13818 (MPEg-2) A set of protocols that define common operations and control functions for managing bitstreams.

On the other hand, to support a variety of applications such as video-on-demand (VOD), interactive video services, or video networks that respond instantly to demand in stand-alone and diverse network environments. Currently, DSM-CC has drafted an extension of the DSM-CC protocol (ISO / IEC 13818-6) in addition to the management of existing MPEG scrims.

FIG. 1 is a diagram illustrating a regular procedure of a command sequence when a client requests a session release under the conventional DSM-CC protocol.

In the first step, the client sends a Client Release Request message to the network to initiate the release of the session initiated by the client. The value of the session-ID field matches the existing session, the value of the reason field indicates why the client wants to release the session, and the value of the field in the user data counter indicates the UserDataByte displayed in the rest of the message. Same as number. While sending a client release request message, the client does not use any resources allocated for the session.

In a second step, upon receiving the client release request message, the network searches for the value of the session-ID to match the existing session. If the value of this field is valid and owned by the client, the network sends a Server Release Indication message to the server. The value of the session-ID field is the same as the session-ID received from the server, and the value of the reason field indicates that the session is released by the client's request. The value of the user data counter (userDataCount) and user data byte (userDataByte) fields Is the same as that received from the client.

In a third step, as soon as the server receives a Server Release Indication message, the server searches to see if the value of the field of the Session-ID matches an existing session. If the value of the session-ID field is valid, the server first releases all resources allocated to the session and sends a Server Release Respone message to the network. The value of the session-ID field is the same as the value of the session-ID field from the network, and the value of the userDataCount field is equal to the number of userDataBytes in the message. That is, from this point on, the server considers the session terminated.

In the fourth step, the network releases all resources allocated to the session as soon as it receives a Server Release Respone message, and then sends a Client Release Confirm message. The values of the fields of session-ID, user data counter (userDataCount), and user data byte (userDataByte) are the same as those received in the Server Release Respone.

In the fifth step, the client releases all resources allocated to the session as soon as the client releases a Client Release Confirm message, at which point the server considers the session terminated.

The command related information is briefly described as follows.

The Client Release Request consists of a Session-ID, a Reason, a User Data Count, and a User Data Byte.

Server Release Indication is composed of Session-ID, Reason, User Data Count, and User Data Byte.

The server release response consists of a session-ID, a response, a user data count, and a user data byte.

Client Release Confirm consists of Session-ID, Response, User Data Count, and User Data Byte.

As mentioned above, the interactive CATV uses a series of command sequences to process one session release command: client release request, server release indication, server release response, and client release confirmation. It must be sent and received between three subjects.

However, in some cases, the requester of the first session release command may need to change the session release command due to cancellation of the user or change of the network environment before receiving the confirmation command. In this case, since there is no command for processing the DSM-CC protocol in the prior art, the exchange of a new command may be performed only after a series of command exchanges are completed. More specifically, once you want to cancel the initiated session release, you must send a cancel session cancel command again after receiving a confirmation command that responds to the session release. As a result, the session release cancellation method of the conventional DSM-CC protocol has a disadvantage in that the utilization of time and resources is reduced by repeatedly performing two command exchanges.

Accordingly, the present invention has been made to solve the above-described problem, and an object of the present invention is to provide a method for canceling a session release in the DSM-CC protocol, which enables a simpler procedure for canceling a session release initiated by a client. To provide.

According to another aspect of the present invention, there is provided a method for canceling a session release, comprising: a first step of providing a client release cancellation request message from the client to the network to cancel the session release; When the client release cancellation request message is received from the client, transmitting a server release cancellation instruction message from the network to the server; In response to a server release cancel instruction message from the network, determining whether the server release is cancelable; If the server determines that the session release is irrevocable, a first server release cancellation response message is sent to the network informing that the server release is not canceled; Canceling a session release of the server and transmitting a second server release cancellation response message to the network informing that the session release of the server has been cancelled; In response to the first server release cancel response message in the network, send a first client cancel cancellation acknowledgment message to the client informing the client that the session release from the server has not been cancelled, and canceling the second server release canceled in the network. And, in response to the response message, after canceling the session release of the network, sending a second client release cancellation confirmation message to the client informing that the session release of the network has been cancelled.

Hereinafter, the present invention will be described in detail with reference to the illustrated drawings.

2 is a block diagram schematically illustrating a configuration between a server, a network, and a client applied to cancel a session release initiated by a client under the DSM-CC protocol according to the present invention.

The client 100 is composed of a network interface 102, an MPEG2 transport 104, an MPEG2 decoder 106, a graphics control unit 108, a system control unit 110, a cancellation command processor 112, and a memory 114. do.

The network interface 102 is connected to the network 200 and is responsible for an interface required for data transmission and reception between the client 100 side and the network 200.

The MPEG2 transport 104 performs a function of analyzing information bits of data transmitted and received and converting them to meet the MPEG2 standard.

The MPEG2 decoder 106 decodes data input from the MPEG2 transport 104 and provides the decoded data to the graphic control unit 108.

The graphic controller 108 performs graphics processing on the data decoded by the MPEG2 decoder 106 and outputs the same to the display apparatus.

The system control unit 110 controls the system initialization and the switching to the driving state and the overall operation of the system that occur during power-up or reboot (Re-Booting).

The cancel command processor 112 is configured to control and operate the cancel command to be applied to the present invention, and the memory 114 stores the decoded data from the MPEG2 decoder unit 106 or stores information and other data about the client. Is configured to.

The network 200 supports the program logic session control unit 202 for controlling the connection between the network interface 112 of the server and the network interface 301 of the client, the cancel command processor 204 and data information to be applied to the present invention. It consists of a resource control unit 206.

The server 300 standardizes and controls the data in the form of an MPEG2 bit stream when restoring the data stored in the storage unit 302 and the data stored in the storage unit 302. An MPEG-2 stream controller 304, an application controller 306 for recording an application program of the server 300 and supporting the program based on the MPEG-2 stream controller 304, a command related to the DSM-CC protocol, and a command controller for executing the command. 308, the cancel command processor 310 to be applied to the present invention and a network interface 312 for interfacing with the network 200.

The cancel session cancellation operation of the present invention configured as described above will be described in detail with reference to FIG.

When the client 100 applies a client release cancel request signal to the system controller 110 by the client, the system controller 110 receives relevant data about the client release cancel request signal from the cancel command processor 112 accordingly. Authorization is made to the network 200 via the network interface 102 (step 401). The client release cancellation request according to the present invention includes the same session-ID, reason, user data counter, and user data byte as the session release request.

Accordingly, the network 200 transmits a client release cancellation request, which is a signal transmitted through the network interface 102 of the client 100, to the session controller 202. The session control unit 202 determines whether the signal currently input by the command set by the cancellation command processor 204 and the resource control unit 206 is a client release cancellation request signal (step 402).

If it is determined in step 402 as a client release cancellation request signal, the process proceeds to step 404 where a server release cancellation instruction signal is supported from the resource control unit 206 of the network 200 and the server release cancellation instruction message is received. The control unit 202 transmits to the server 300 through the network interface 412 (step 404).

After the step 404, the command control unit 308 of the server 300 determines whether the signal transmitted from the network 200 is a server release cancel command signal based on the operation of the cancel command processor 310. (Step 405).

If it is determined in step 305 as the server release cancel command signal, the control proceeds to step 407 where it is determined by the command control unit 308 whether it is possible to cancel the session release in the server 300.

As a result of the determination in step 407, if cancellation of the session release is not possible at the server 300, the flow proceeds to step 408 to cancel the first server release indicating that the cancellation of the session cancellation at the server 300 side has not been cancelled. The response message is transmitted to the network 200.

However, in step 407, if it is possible to cancel the session release of the server 300, the flow proceeds to step 409 to cancel the release of the session of the server 300, indicating that the release of the session of the server 300 has been cancelled. The second server release cancel response message is transmitted to the session control unit 202 of the network 200 via the network interface 312 of the server 300 and proceeds to step 410.

In the above-described steps 408 and 409, distinguishing the first or second server cancel cancel response message, that is, distinguishing that the disconnection of the server 300 has not been canceled or canceled is indicated in the message response field of the DSM-CC. Provided on board.

In step 410, it is determined whether the first or second server cancel cancellation response message has been delivered to the network 200.

As a result of the determination in step 410, if the first or second server release cancellation response signal is not transmitted, it is determined whether or not the message is delivered again after a predetermined time delay (step 411). If the first or second server release cancellation response message has been delivered by step 410, the process proceeds to step 412 to determine whether the server release is canceled.

If it is determined from the first server cancel cancel response that the session cancel of the server 300 is not canceled, the flow proceeds to step 413, where the first client cancel cancel confirmation message informing the client that the cancel of the session cancel requested by the client is not cancelled. It will be delivered to the client 100, and with this, the server session set-up request is delivered back to the network (200).

However, in step 412, if it is determined from the second server cancel cancellation response that the server 300 cancels the session, the process proceeds to step 414 to cancel the disconnection from the network 200 and the network ( This is terminated by providing a second client release cancellation confirmation message to the client 100 informing that the session release at 200 has been cancelled.

In steps 413 and 414 described above, the classification of the first or second client cancel cancellation confirmation message, i.e., whether or not the session release of the network 300 has been canceled or has been canceled, is entered in the message response field of the DSM-CC. Provided on board.

In addition, the above-described message related to canceling the session release according to the present invention is configured using a user defined message scenario code (user defined message scenario code) assigned to the message scenario field (message scenario field) of the DSM-CC, the assigned message Code ID is shown in the following table.

As described above, the present invention does not have a command for canceling the session release initiated by the client in the existing DSM-CC, thereby compensating the disadvantage of greatly reducing the time and resource utilization between the server, the network, and the client. There is.

Claims (1)

A method of canceling a session release delivered from a client to a server via a network under a Digital Storage Media Command and Control (hereinafter abbreviated as DSM-CC) protocol, the client to cancel the session release. Providing a cancel cancellation request message from the client to the network; When the client release cancellation request message is received from the client, transmitting a server release cancellation instruction message from the network to the server; In response to a server release cancel instruction message from the network, determining whether the server release is cancelable; And if it is determined that the session release is irrevocable at the server, a first server release cancellation response message indicating that the session release of the server is not canceled is sent to the network, and if it is determined that the session release is cancelable, Canceling a session release of the server and transmitting a second server release cancellation response message to the network informing that the session release of the server has been cancelled; In response to the first server release cancel response message in the network, send a first client cancel cancellation acknowledgment message to the client informing the client that the session release from the server has not been cancelled; And according to the response message, after canceling the session release of the network, sending a second client release cancellation confirmation message to the client informing that the session release of the network has been cancelled. How to cancel client session disconnection in DSM-CC protocol.