KR20100074818A - A method for providing a data broadcasting service and an apparatus thereof - Google Patents

Abstract

PURPOSE: A method for providing a data broadcasting service and an apparatus thereof are provided to store use information in an application in a simple cookie format. CONSTITUTION: A user information is inputted(S701), and an object for storing user information in a specific format is created. The object is serialized. A key is received to encode the serialized object data(S702). The serialized object data are encoded by using the received key, and the encoded object data are stored in a logical storage volume(S704).

Description

A method for providing a data broadcasting service and an apparatus thereof

The present invention relates to a data broadcasting service, and more particularly, to a method and apparatus for improving the usability or convenience of a user for an application for a data broadcasting service. will be.

Conventional services have been limited to audio and video, but recently, various and complicated applications are gradually coming out due to high specification of hardware. Accordingly, one application may be recognized and used as one service.

Broadcast environments are also changing to enable such applications.

Relatedly, some applications require input of information by a user for their execution. However, in the case of Java applications running on a platform for data broadcasting services, it is basically a stateless application. This means that the information input by the user is not stored separately. As a result, the information entered by the user during application execution is not stored separately and cannot be used again. In addition, if a user inputs information during several steps in the application execution process, if the application is terminated for some reason before all the steps are completed, the user may input the user information necessary for the steps already performed in the process of re-running the application. The inconvenience of having to re-enter the user has a problem of degrading the usability of the application.

In the present invention, to solve the above problems, an object of the present invention is to enable the application to store the necessary information in each state.

Another object of the present invention is to enable a concept of a cookie used by an existing web page in an application of a digital broadcasting receiver.

Still another object of the present invention is to prevent information leakage by using an encryption module for information stored in the form of cookies.

Another object of the present invention is to be able to further add a usage scenario of the application.

Another object of the present invention is to provide a method and apparatus for providing a data broadcast service.

In order to achieve the above object, an example of a method for storing user information for each user used to execute an application for a data broadcasting service according to the present invention includes: receiving user information; Generating an object for storing the received user information in a specific form; Serializing the generated object and receiving a key for encryption of the serialized object data; And encrypting the serialized object data by using the received key and storing the encrypted object data in a logical storage volume (LSV).

In this case, the method may further include storing the received key.

The specific form may include a cookie form.

In addition, the corresponding logical storage volume LSV may set a unique path for each user.

In addition, the logical storage volume LSV may be set such that ExtendedFileAccessPermission cannot be set dynamically in order to restrict access of a user other than the user of the corresponding path to each path.

In addition, the user information is defined by the corresponding application, and may include log-in information.

The object may include a map object, and the map object may include a hash map.

According to the present invention, a method for executing an application for a data broadcasting service using user information in a cookie form stored in the logical storage volume (LSV), wherein the application has access to a path where a cookie for the user is stored. Getting a storage proxy; And decoding the user information by accessing the logical storage volume (LSV) when a path in which the cookie for the user is stored is generated.

In this case, the method may further include determining whether the application has access to the path in which the cookie for the corresponding user is stored.

If there is no access right of the application as a result of the determination, the application may be denied access to the cookie in the logical storage volume (LSV).

In addition, the determination of whether the application has permission to access the path in which the cookie is stored may be determined as owning a persistent storage access authorized by a permission request file.

The method may further include determining whether a path for storing the cookie for the corresponding user has been previously generated.

In addition, if the path for storing the cookie for the user is not previously generated, the new path may be created in the logical storage volume LSV.

The decoding may include decrypting previously encrypted object data based on a previously received key; And deserializing the decoded object data to generate an object.

In addition, the object may include a map object, and the map object may include a hash map.

An example of a digital broadcast receiver according to the present invention includes a user interface unit for receiving a user input for user information used to execute an application; A processor unit controlling execution of a corresponding application based on a user input received from the user interface unit; And a decoder for decoding data according to the control of the processor unit, wherein the processor unit includes an application and middleware, and the application uses a key of the received user input. By generating and storing a path (path) for the user in a Logical Storage Volume (LSV) in a specific form, the middleware determines whether the path to the user is created according to the access request of the application If it is generated, the application determines whether to access the path, and if there is access authority, controls to access the path to decode pre-stored user input information.

In this case, if the path is not generated, the middleware may control to generate a new path in the logical storage volume LSV.

If the middleware does not have the access right of the application, the middleware may control to deny access to the path of the access.

Thus, according to the present invention,

First, the application can store user information in the form of simple cookies.

Second, there is an effect that the concept of the cookie used by the existing web page can be borrowed from the application of the digital broadcast receiver.

Third, there is an effect that can prevent information leakage by using the encryption module for information stored in the form of cookies.

Fourth, there is an effect that can further add the use scenario of the application.

Fifth, there is an effect that can increase the usability or accessibility of the user's application.

Hereinafter, with reference to the accompanying drawings, preferred embodiments of the present invention that can specifically realize the above object will be described. At this time, the configuration and operation of the present invention shown in the drawings and described by it will be described by at least one embodiment, by which the technical spirit of the present invention and its core configuration and operation is not limited.

The terms used in the present invention have been selected as general terms widely used as possible in consideration of the functions in the present invention, but may vary according to the intention or custom of a person skilled in the art or the emergence of a new technology. In addition, in certain cases, there is also a term arbitrarily selected by the applicant, in which case the meaning will be described in detail in the description of the invention. Therefore, it is intended that the terms used in the present invention should be defined based on the meanings of the terms and the general contents of the present invention rather than the names of the simple terms.

In relation to this, the term "middleware (M / W)" herein refers to middleware that is executed in a data broadcasting platform. In this case, the data broadcasting platform may include a multimedia home platform (MHP), an opencable application platform (OCA), an advanced common application platform (ACAP), and the like.

In addition, the term “application” refers to an application for digital broadcasting, including an application executed on the middleware (M / W) base. However, in the following specification, for convenience of description, a Java application executed on the middleware (M / W) based on ACAP among data broadcasting platforms will be described as an example. In this case, the Java application includes, for example, an Xlet application. The Xlet application includes interactive applications such as T-commerce or T-banking applications that require input of information by a user.

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

Hereinafter, in the present specification, a preferred embodiment for realizing the technical idea of the present invention stores the input information by the user in a specific form in the process of executing the application, and uses the input information by the user stored in the specific form for the application. It is intended to provide usability or accessibility. In this specification, for convenience of description, the specific form will be described by using a cookie method used in Http Web Sites having a stateless type as an example. In addition, the cookie for storing the input information by the user will be described using the concept of the external storage space used in the data broadcasting platform as an example. For example, the external storage space may be a persistent memory in a digital broadcast receiver set. Thus, the application may store the information input by the user in the persistence memory.

In the present specification, as described above in order to implement the technical idea of the present invention, the concept of a cookie used in a web page is borrowed from an application for data broadcasting.

In this regard, the present specification provides a storage proxy for storing and using cookies in an application. The storage proxy may provide a logical storage volume (LSV) for each user ID and / or application. In addition, the logical storage volume LSV may be secured by allowing only the corresponding user to access it. Herein, the present invention uses an encryption / decryption algorithm as an example so that only the corresponding user can access the logical storage volume (LSV). However, a more detailed description thereof will be described later.

In order to explain the present invention, an Xlet application will be described.

1 is a structural diagram illustrating a hierarchical structure of a broadcast receiver according to the present invention.

Referring to FIG. 1, the broadcast receiver 100 includes an application 110, middleware 120, and resources 130.

The application 110 is defined as a program executed to achieve various purposes in the broadcast receiver 100. Here, the application 110 may be executed by a plurality of applications 111 to 119 on the broadcast receiver 100.

The applications 111-119 are broadcast to the broadcast receiver 100 along with the digital television programs in a broadcast stream. The applications 111 to 119 can be broadcast in a carousel format according to a protocol such as the DSM-CC protocol specified under the relevant standard, and are broadcast periodically. Here, the applications 111 to 119 may be, for example, electronic program guides, play-along games, tele-banking, menu navigation options. ), Tele-shopping, electronic newspapers, and similar information services.

The broadcast receiver 100 receives these applications 111-119 and executes them locally.

Basic hardware for executing the Xlet includes a set-top box or digital broadcast receiver supporting a Java TV platform (eg, middleware 120 of FIG. 1). Xlets do not have a "main" way, they run the interface Xlet.

Xlets have a life cycle, and the life cycle method signature is defined by the interface Xlet. Interface Xlet provides lifecycle methods to notify you of Xlet state changes such as creation, initialization, startup, and destruction.

However, the interface Xlet does not provide execution for its lifecycle methods. All Java TV implementations have an application manager 127 that calls lifecycle methods to move one or more Xlets through various application states via an interface Xlet.

Interface Xlet does not provide execution for its lifecycle methods. Thus, the developer provides application-specific executions for those methods by defining what happens at each point in the Xlet life cycle. For example, the iniXlet method for a game Xlet will create user interface components. The Xlet is designed to notify the application manager 127 of the state changes by initiating some state changes themselves and causing methods in the XletContext interface.

The interface Xlet is defined by the javax.tv.xlet package, which is one of the packages defined in the Java TV ^TM Application Programming Interface (API). The Java TV API consists of interfaces and classes grouped into packages. These packages include interfaces and classes for processing video, audio, and data transmitted to a digital broadcast receiver via a broadcast stream sent by television networks.

The interface Xlet, defined in javax.tv.xlet, allows the application manager 127 to create, initialize, start, stop, and destroy Xlets. The application manager 127 maintains the state of the Xlet and causes methods on the Xlet through various lifecycle methods. The Xlet executes these methods to update its internal operations and resource usages as directed by the application manager 127.

2 is a conceptual diagram illustrating an example of a life cycle of an Xlet application in relation to the present invention.

Referring to FIG. 2, the method summary of the interface Xlet, as defined by javax.tv.xlet, is as follows.

The Xlet is in a loaded state 210. The initXlet initializes the Xlet itself in the loaded state 210 and signals the Xlet to enter the paused state 220. startXlet starts providing service and signals the Xlet to enter the active state (230). The PauseXlet signals the Xlet to stop providing service and enter the suspended state 220. destroyXlet terminates the service and signals the Xlet to enter the destroyed state (240).

The middleware 120 plays a role of mediating between the application 110 and the resource 130. For example, the middleware 120 receives the information or the command of the application 110, executes the received command to calculate a result for the received command, and transmits the calculated result to the application 120. Perform. To this end, the middleware 120 includes an interface 121 and a system service 126.

The interface 121 transmits and receives data, information, and commands between the application 110 and the system service 126. That is, the application 110 may use a service provided by the middleware 120 through the interface 121. In order for the producer of the application 110 to use the middleware 120, each broadcast standard defines a request form for requesting a specific service provided by the middleware 120. If the application 110 requests the middleware 120 to perform a specific service according to a request format defined in each broadcast standard, the interface 121 receives a request for performing a specific service and the system service 126. The request for execution of the specific service is transmitted to the system service 126 so that the specific service can perform the specific service requested. Here, the request form for requesting a specific service provided by the middleware 120 defined in the broadcast standard may be an API defined in Java. In this regard, "javax.tv.xlet.Xlet" is an entity that is a defined interface and that can be executed and recognized under the relevant specifications.

The system service 126 performs the service according to the request transmitted by the interface 121 and provides the result to the interface 126. In addition, the system service 126 downloads the application 110 from the broadcasting station, manages the life cycle of the downloaded application 110, allocates and returns the resource 130 to the application 110 in the activated state 230. It manages and manages information about allocated resources. The system service 126 includes an application manager 127 for this purpose. Here, the middleware 120 may be implemented according to a related standard as an example to support an API of the corresponding standard.

The application manager 127 is a module that manages life cycles of the applications 111 to 119. The application manager 127 manages generation, execution, and termination of the applications 111 to 119.

The resource 130 refers to a hardware entity having various functions, and may be expressed as a hardware resource and a software resource. Here, the hardware resource includes a tuner unit, a demodulator, a conditional access (CA), a demultiplexer, a decoder, a memory, a hard disk, and a network adapter. In addition, a software resource may represent a plurality of hardware entities grouped and includes resources defined on an operating system such as a press and a thread. Here, the thread refers to a flow unit executed in a process. Generally, a program has one thread, but depending on the program environment, more than one thread can be executed at the same time. Thus, the program can be executed in a multi-threaded manner. This multi-threaded approach is a method of execution in which each thread shares and uses memory within a process, unlike processes running independently and each taking up separate memory.

In addition, the resource 130 is provided transparently to the application 110 so that the application 110 can be used irrespective of the internal implementation. As described above, the middleware 120 may provide the application 110 with the application 110. And mediate the resource (130). In addition, the resource 130 may be divided into a shared resource and a non-shared resource. Here, the shared resource refers to a resource that applications 111 to 119 can share with each other as resources such as memory, thread, and network session, and the non-shared resource refers to a single application 111 as a resource such as a tuner. When this is used, it means a resource that other applications 112 to 119 cannot use.

To use the resource 130, the Xlet autonomously uses virtual machine memory and threads. The protocol or management of these resources is made entirely by the middleware 120, the application 110 is operated without great consideration for the usage of its own resources.

3 is a block diagram of a broadcast receiver configured according to an embodiment of the present invention.

Referring to FIG. 3, the broadcast receiver 300 according to the present invention includes a tuner 311, a demodulator 312, a CA 313, a demultiplexer 314, a media decoder 315, and a user. The interface unit 321, the storage medium 322, the network interface unit 323, and the processor unit 350 are included. Here, the tuner 311, the demodulator 312, the CA 313, the demultiplexer 314, the media decoder 315, the user interface 321, the storage medium 322, and the network interface. The unit 323 and the processor 350 are components corresponding to resources of the broadcast receiver.

The tuner 311 receives broadcast data from at least one of the terrestrial wave, satellite, and cable, and outputs the broadcast data to the demodulator 312. That is, the tuner 311 tunes the frequency of a specific channel among the broadcast signals 301 input through at least one of an antenna, a cable, and a satellite and outputs the frequency to the demodulator 312. The tuner 311 may be provided for each broadcast source, for example, terrestrial wave, cable, and satellite, or may be an integrated tuner. In addition, when the tuner unit 311 is assumed to be a terrestrial broadcast tuner, at least one digital tuner and an analog tuner may be provided, respectively, or may be a digital / analog integrated tuner. When the terrestrial wave is an example, the tuner 311 tunes a terrestrial broadcast content transmitted through an antenna, that is, a broadcast signal of a channel selected by a user from among broadcast signals, and outputs the tuned signal to the demodulator 312.

Here, the broadcast data received by the tuner unit 311 includes at least one of A / V data (Audio / Video data), MPEG section data, and application data. The MPEG section data may be data including System Information (SI), Emergency Alert System (EAS), Application Information Table (AIT), and eXtended AIT (XAIT). In particular, the AIT refers to a table including information on the application running in the receiver for data service, and in some cases is also called AMT. These AITs provide information about the application, such as the name of the application, the version of the application, the priority of the application, the ID of the application, the status of the application (auto-start, user-managed, kill, etc.), the type of application. (Java or HTML), the location of the stream containing the classes and data files of the application, the base directory of the application, the location of the icon of the application, and the like.

Application data refers to data including the program code of the application 370. The processor 350 may determine a transmission mode based on the AIT and control to download application data in the determined transmission mode. Here, the transmission mode refers to a transmission method and a type of transmission medium for receiving broadcast data. The transmission method refers to the type of protocol used for each network layer, and DSM-CC User-to-User, Data and Object Carousel protocols, HTTP, TCP, UDP, IP, MPEG-2 Transport Stream, Ethernet protocol, etc. Can be used. In addition, the transmission scheme may be Broadcast Channel Protocols and Interaction Channel Protocols defined in the relevant standard. Types of transmission media may include terrestrial, satellite, cable and Internet networks.

In addition, the transmission mode may include a transmission mode in which a transmission method and a transmission path vary depending on the type of broadcast data. That is, the broadcast receiver 300 may support a transmission mode in which A / V data is received through a cable and application data is received through an internet network.

In addition, the processor 350 may detect application data using the AIT. As a method of detecting application data using AIT, component_tag, original_network_id, transport_stream_id, and service_id may be detected. The component_tag refers to an elementary stream carrying a Download Server Initiate (DSI) of a corresponding object carousel, and the original_network_id represents a transport stream for providing a transport connection. DVB-SI original_network_id of TS). In addition, the transport_stream_id refers to the MPEG TS of the transport stream (TS) providing the transport connection, and the service_id refers to the DVB-SI of the service providing the transport connection. The original_network_id, transport_stream_id, and service_id may be used to obtain information on a specific channel.

The network interface 323 receives broadcast data through the Internet network, and outputs the received broadcast data to the CA unit 313 or the communication control unit 388.

The demodulator 312 demodulates the signal output from the tuner 311 and outputs the demodulated signal to the CA unit 313. The CA unit 313 descrambles the signal output from the demodulator 312 or the signal output from the network interface unit 323 and outputs the descrambled signal to the demultiplexer 314. The demultiplexer 314 is a digital data stream that is a signal output from the CA unit 313 in the form of a data stream (for example, MPEG-2 format) representing audio and video and a DSM-CC object carousel that is repeatedly broadcast. Demultiplex with data for applications Here, in another embodiment of the broadcast receiver capable of interfacing with the non-broadcast delivery channels, the tuner 311 may be replaced with a network interface suitable for the non-broadcast delivery channels. The non-broadcast delivery channel may be an internet protocol (IP) based delivery channel.

The media decoder 315 decodes the audio stream and the video stream demultiplexed by the demultiplexer 314 into audio 302 and video 303 which can be displayed, respectively. To this end, the media decoder 315 may include an audio decoder and a video decoder. Here, the displayed video 303 may include an image output from the user interface unit 321.

The processor 350 executes a plurality of applications 370 and middleware 380.

The middleware 380 may include a tuner unit 311, a demodulator 312, a CA 313, a demultiplexer 314, a media decoder 315, a user interface 321, a storage medium 322, and The network interface unit 323 is controlled or managed and assigned to the application 370. To this end, the middleware 380 includes a tuner controller 381, a CA controller 382, an MPEG-2 section filter 383, a service information processor 384, a DSM-CC 385, and a media controller. 386, a storage control unit 387, and a communication control unit 388.

The tuner controller 381 controls the tuner 311 to be assigned to the application 370 or to change the tuning frequency of the tuner 811 according to a command of the application 370. The CA control unit 382 controls the CA unit 313 to descramble the output signal of the demodulation unit 312.

The MPEG-2 section filter unit 383 extracts information for displaying the video by filtering a data stream related to the video demultiplexed by the demultiplexer 314, and the service information processor 384 extracts the information for the demultiplexer 314. The service information is extracted from the demultiplexed data and processed. That is, the MPEG-2 section filter unit 383 extracts MPEG section data from the received broadcast data. The MPEG-2 section filter unit 383 may extract host access guide information, which is guide information on a transmission mode, from the received broadcast data. In this case, the host access guide information may be included in an AIT and transmitted. In this case, the MPEG-2 section filter unit 383 may extract host access guide information by extracting AIT from broadcast data.

The DSM-CC 385 parses application data demultiplexed by the demultiplexer 314 to extract application program and application information, and stores the extracted information in the storage medium 322. The application program stored in the storage medium 322 is executed in the process 350.

The media controller 386 controls the media decoder 315 to display the audio 302 and the video 303. In addition, the media control unit 386 retrieves the host access guide information extracted by the MPEG-2 section filter unit 383 associated with the data access information stored in the storage medium 322, and transmits the information indicated by the retrieved host access guide information. The tuner 311 or the network interface 323 may be controlled to receive broadcast data in the mode. Here, instead of directly controlling the network interface 323, the media controller 386 allows the communication controller 388 to control the network interface 323 so that the host access guide information retrieved by the network interface 323 is indicated. The broadcast data can be received in the transmission mode.

The storage control unit 387 stores the audio stream, the video stream, the application program, the application information, and the service information in the storage medium 322, and the audio stream, the video stream, the application program, the application information, and the service information stored in the storage medium 322. Control access to The storage medium 322 may be any one of a RAM memory, a FLASH memory, and a hard disk (HDD), or may include a RAM memory, a FLASH memory, and a hard disk (HDD). The hard disk HDD may be an internal hard disk or an external hard disk.

The communication controller 388 supports the application 370 to enable network communication, and controls the network interface 323 for this purpose. In addition, the communication control unit 388 controls the network interface 323 to receive broadcast data. The communication control unit 388 may extract the application data from the broadcast data received by the network interface 323 and provide it to the storage control unit 387 so as to be stored in the storage medium. The / V data may be controlled to be output to the CA 313.

Here, the process 380 may be implemented as a single process or a multi-process, the tuner control unit 381, CA control unit 382, MPEG-2 section filter unit 383, service information processing unit 384 of the middleware 380 ), The DSM-CC 385, the media control unit 386, the storage control unit 387, and the communication control unit 388 may be hardware or firmware, respectively. In this case, the middleware 380 includes a tuner control unit 381, a CA control unit 382, an MPEG-2 section filter unit 383, a service information processing unit 384, and a DSM-CC in which the application 370 is hardware or firmware. 385, the media controller 386, the storage controller 387, and the communication controller 388 are used to mediate the use.

4 is a block diagram illustrating a relationship between a configuration of middleware, an application, and a logical storage volume (LSV) according to an embodiment of the present invention.

Referring to FIG. 4, the middleware 400 according to an embodiment of the present invention corresponds to the middleware 380 of FIG. 3, and includes an interface module 405 and a logical storage volume (LSV) control module 410. do. In this case, the interface module 405 and the logical storage volume (LSV) control module 410 are components corresponding to the interface 121 and the system service 126 in FIG. 1, respectively.

The application 415 is a component corresponding to the application 370 of FIG. 3 and includes a log-in server that transmits a cookie key or a user key with respect to information input by a user to access the application.

The logical storage volume (LSV) 425 may be a component corresponding to the storage medium 322 of FIG. 3. A more detailed description of the logical storage volume will be described later.

The interface module 405 exchanges information or commands with the application 415. For example, when the interface module 405 receives a control command request for storing and using a cookie according to the user's log-in from the application 415, the interface module 405 receives the received control command request in a logical storage volume (LSV) control module. To 410. In contrast, the interface module 405 receives the response when the logical storage volume (LSV) control module 410 transmits a response to the control command request for storing and using the cookie of the application 415. ).

Referring to FIG. 3, for example, the middleware 400 of FIG. 4 previously received information regarding application priority related to screen control according to the present invention included in a broadcast signal received from the broadcast receiver 300. Can assume At this time, the middleware 400 parses the received application priority information. The parsed information is stored in the storage medium 402.

5 illustrates a cookie class according to an embodiment of the present invention.

According to the present invention, the information of the user accessing the application is stored in the form of a cookie. To this end, in this specification, as shown in FIG. 5 as an example, an object called XletCookieManager is created and used. Therefore, according to the present invention, an application may manage cookies using the XletCookieManager object.

The cookie class according to the present invention will be described in more detail with reference to FIG. 5 below.

Each cookie may be stored in the form of a serialized Java map object. In this case, the map object uses, for example, a hash sequence having an advantage in searching. In other words, the map object includes a HashMap. The HashMap is stored as a value and key pair in a string. Here, the serialized object is encrypted using a user key stored in user information of an application server. Therefore, in order to read and play the encrypted cookie again, it must be decrypted using the corresponding user key. In addition, in connection with the present invention, the encrypt / decrypt algorithm and the key length may be performed using various methods and algorithms, but in the present specification, the same key is used for the encrypt / decrypt. The use of a single key algothrism is described as an example. However, detailed description thereof will be omitted here.

In the context of the present invention, userKey may use an encryption scheme to restrict access of other users for security purposes, because information specific to the user may be stored in storing cookies in the application, where encryption Refers to a key for use in an encrypt / decrypt process.

cookiePath means a path in which a cookie for each user is stored.

Init (String UserKey) sets a user key and, if a hash already exists, reads the file and then deserializes the decrypted information to restore the information.

getValue (String key) is for getting the value corresponding to the user key.

setValue (String key, String Value) is for setting the value corresponding to the user key.

writeCookie () is for serializing and storing the cookie hash map. Before saving, writeCookie () must encrypt the information using the user key.

readCookie () reads the cookie file and deserializes it to create a map. After reading the file, you must encrypt it using the user key.

According to the class according to the present invention, the cookie is stored as a value / key pair as a string, and is encrypted using a key that the user receives at log-in. By / encrypting / decrypting, only the user can access it.

6 illustrates a storage proxy according to an embodiment of the present invention.

Referring to FIG. 6, a cookie according to the present invention is stored using a storage proxy called ACAP_COOKIE. In the following description, for convenience of description, for example, a storage package portion of an OCAP is borrowed from the storage proxy, and a detailed description thereof will be omitted.

The storage package has a number of interfaces, but in the context of the present invention, the LogicalStorageVolume interface for representing a logical volume for a storage device and the StorageProxy interface for representing a persistent storage device are described.

Each storage proxy corresponding to the storage device may include logical storage volumes (LSVs). That is, each storage proxy has a logical storage volume (LSV) corresponding to each user ID (User 1, User 2). Here, each of the logical storage volumes (LSV) is created in, for example, the / <org_id> / <app_id> / <uid1> or <uid2> directory, and only the read / write function is granted to each application. Can be. Each cookie is stored in a cookiemap.cookie file.

7 is a flowchart illustrating a cookie storing process according to an embodiment of the present invention.

Referring to FIG. 7, a user inputs necessary information through a process such as, for example, a log-in in order to execute an application (S701).

In operation S701, the application receives a cookie key or a user key from a log-in server in connection with storing user information input by the user (S702).

The application stores the received user key in the (volatile) memory (S703).

When the user key is stored in the memory through the step S703, the application generates an ACAP_Cookie object to serialize the object and encrypts the object using the received user key. The application stores the user information input in step S701 in the form of a cookie in the logical storage volume LSV classified for each user after the encryption (S704). Here, the path of the logical storage volume (LSV) refers to the absolute path of the volume, and may be the only path through all the logical storage volume (LSV) instances without a storage proxy, for example, “~ / OCAP_LSV / user1”. The owner may be a receiver, for example, and the ExtendedFileAccessPermission may be, for example, “not dynamically set” to prevent access by a user other than that user.

8 is a flowchart illustrating a process of using user information stored in FIG. 7 according to an embodiment of the present invention.

The middleware determines whether the corresponding application has the persistent storage access right by the permission request file in the logical storage volume LSV (S801).

If the middleware determines that the step S801 determines that the application does not have persistent storage access by the permission request file, the middleware cannot access the logical storage volume (LSV) of the application (S802).

However, if the middleware determines in step S801 that the corresponding application has the persistent storage access right by the permission request file, the middleware allows access to the logical storage volume (LSV) of the corresponding application. Therefore, the middleware gets an ACAP_Cookie storage proxy (S803). Here, the middleware may call the getStorageProxy () method to obtain the storage proxy. For the call, the application may return a value that includes the storage proxy.

The middleware accesses the logical storage volume LSV according to the returned storage proxy (S804).

The middleware accesses the logical storage volume LSV and determines whether user information of the corresponding user is stored (S805). To this end, the middleware uses the getPath () function to obtain the absolute path of the volume where the user information of the user is stored, for example, “~ / OCAP_LSV / 0x1000_0x1000_user 1”, that is, for the user corresponding to user 1. Determine whether the path where the user information is stored exists.

As a result of the determination in step S805, if the logical storage volume LSV in which the user information of the user is stored does not exist, the middleware controls to generate a new logical storage volume LSV in association with the user (S806).

As a result of the determination in step S805, if the logical storage volume (LSV) in which the user information of the user is stored exists, the middleware may extract, decode, and use previously stored user information for the corresponding user in the logical storage volume (LSV). (S807). Here, the decoding process may include decrypting the cookie information encrypted and stored using the user key of FIG. 7, and deserializing the decrypted user information into an object form. As a result, the middleware can read / write or reference the cookie stored in the application using the ACAP_Cookie interface.

In FIGS. 7 to 8, the serialized cookie information is encrypted or decrypted using the user key. However, if you can't encrypt or decrypt using that user key, you can throw an exception.

According to the present invention described above, it is possible to greatly improve the usability of the application for the data broadcast service by providing the information required by the application developer in the form of a simple cookie to the digital broadcast receiver set. In addition, by restricting access to user information through encryption or the like, the user information can be protected. For example, in order for a user to purchase an item in an interlocked T-Commerce application, a purchase step and a corresponding payment step must be performed at one time, and the interlocked application terminates the program and changes the service ( When it is terminated due to a service change, etc., the user has to wait until the associated application is restarted in order to purchase the item again. At this time, if the application can store a simple shopping cart for each user in the set, the user only adds to the shopping cart in the linked application, and the handful payment process is executed during the advertisement after the broadcast. Scenarios can be added, which will increase usability or accessibility for the application.

Although the preferred embodiments of the present invention have been shown and described above, the present invention is not limited to the specific embodiments described above, and the present invention is not limited to the specific scope of the present invention as claimed in the claims. Anyone skilled in the art can make various modifications, as well as such modifications are within the scope of the claims.

1 is a structural diagram showing a hierarchical structure of a broadcast receiver according to the present invention;

2 is a conceptual diagram illustrating an example of a life cycle of an application in relation to the present invention;

3 is a block diagram of a broadcast receiver configured according to an embodiment of the present invention.

4 is a block diagram illustrating a relationship between a configuration of middleware, an application, and a logical storage volume (LSV) according to an embodiment of the present invention.

5 illustrates a cookie class according to an embodiment of the present invention.

6 is a diagram illustrating a storage proxy according to one embodiment of the present invention;

7 is a flowchart illustrating a cookie storage process according to an embodiment of the present invention, and

8 is a flowchart illustrating a process of using user information stored in FIG. 7 according to an embodiment of the present invention.

* Description of the main symbols in the drawing

311; Tuner 312; Demodulator

313; CA 314; Demultiplexer

315; Media decoder 321; User interface

322; Storage medium 323; Network interface

350; Process 370; application

380; Middleware

Claims (18)

A method of storing user information for each user used to execute an application for a data broadcasting service, Receiving user information; Generating an object for storing the received user information in a specific form; Serializing the generated object and receiving a key for encryption of serialized object data; And Encrypting the serialized object data by using the received key, and storing the encrypted object data in a logical storage volume (LSV). The method of claim 1, Storing the received key. The method of claim 2, The particular form comprises a cookie form. The method of claim 2, The corresponding logical storage volume (LSV), Characterized by setting a unique path distinguished for each user. The method of claim 4, wherein The logical storage volume (LSV), For each path, ExtendedFileAccessPermission is set to disable dynamic setting in order to restrict access of users other than the user of the path. The method of claim 1, The user information, A method as defined by the application, comprising log-in information. The method of claim 1, The object includes a map object, And the map object comprises a hash map. A method of executing an application for a data broadcasting service using user information in the form of a cookie stored in a logical storage volume (LSV) according to claim 1, If the application has access to a path in which a cookie is stored for the user, obtaining a storage proxy; And And decoding the user information by accessing the logical storage volume (LSV) when a path in which a cookie for the corresponding user is stored is generated. The method of claim 8, Determining whether the application has access to the path in which the cookie for the corresponding user is stored. 10. The method of claim 9, If the determination result that the application does not have access rights, characterized in that the application denies access to the cookie in the logical storage volume (LSV). 10. The method of claim 9, Determining whether the application has access to the path where the cookie is stored, Determining whether to own a persistent storage access authorized by a permission request file. 10. The method of claim 9, And determining whether a path for storing the cookie for the corresponding user has been previously generated. The method of claim 12, And if a path for storing the cookie for the user is not previously generated, creating a new path in the logical storage volume (LSV). The method of claim 8, The decoding step, Decrypting the previously encrypted object data based on a previously received key; And deserializing the decoded object data to generate an object. The method of claim 14, The object includes a map object, And the map object comprises a hash map. A user interface to receive a user input for user information used to execute an application; A processor unit controlling execution of a corresponding application based on a user input received from the user interface unit; And It is configured to include a decoder for decoding data under the control of the processor unit, The processor unit includes an application and middleware, The application generates and stores a path for a corresponding user in a logical storage volume LSV in a specific form by using a key. The middleware determines whether the path for the user is generated according to the access request of the application, and if so, determines whether the application has access to the path. And control to decode the input information. The method of claim 16, The middleware, And if the path has not been created, controls to create a new path in the logical storage volume (LSV). The method of claim 16, The middleware, And if there is no access right of the application, controlling to deny access to the path of the corresponding access.

Images