Abstract: A method and system for digital right management of digital contents is provided. Accordingly, the method comprises allowing a user to login into a system platform with login credential using a user device, generating a user token and issuing the user token to the user, generating an unique device token for the user device and issuing the device token to the user device, generating a digital content token associated with the digital content and delivering the digital content token to the user device, storing the digital content token in an arbitrary folder of the user device, verifying the user token, device token, and digital content token for the digital content, based on matches, allowing the user to access and read the digital content from the user device. In an embodiment, the folder location of digital content token is changed and/or updated when the user access the digital contents.
CLIAMS:1. A method for digital right management of digital contents, the method comprises
allowing a user to login into a system platform with login credential using a user device;
generating a user token and issuing the user token to the user;
generating an unique device token for the user device and issuing the device token to the user device;
generating a digital content token associated with the digital content and delivering the digital content token to the user device;
storing the digital content token in an arbitrary folder of the user device;
verifying the user token, device token, and digital content token for the digital content;
based on matches, allowing the user to access and read the digital content from the user device.
2. The method as claimed in claim 1, wherein said digital contents are downloaded in the user device from a server via a communication network.
3. The method as claimed in claim 1, wherein said digital contents are readable using a reader provided in the user device.
4. The method as claimed in claim 1, wherein said digital contents are stored in internal storage of the user device and are readable while offline from the network.
5. The method as claimed in claim 1, wherein folder location of digital content token is changed when the user access the digital contents.
6. A system for digital right management of digital contents, the system comprising
a user module that enables user to login and logout into the platform and generating user token;
a server module that enables for receiving request from user for user token, issuing user token, storing the details of users and digital contents;
a token management module that manages token for the digital content, user device and user;
a library module that enables to maintain the list of digital contents purchased by the user;
a download module that enables to download the digital content from the server and store the digital content in the internal storage of user device; and
an arbitrary memory module that enables to place the digital content token in a random location in the internal memory of user device
,TagSPECI:METHOD AND SYSTEM FOR DIGITAL RIGHT MANGEMENT OF DIGITAL CONTENTS
BACKGROUND
Technical Field
[0001] The embodiments herein generally relate to security platform. Specifically, the embodiments described herein relate to a method and system for digital right management of digital contents.
Description of the Related Art
[0002] Digital contents are stored and accessed by an electronic media in the form of text like electronic documents and/or multimedia files like audio or video files. The digital contents can be provided in the form of read only structures in order to protect the contents. Further, it can be protected in many ways which includes an encryption, a password protection etc. Due to viewing, copying, printing and altering of original works without consent can reflect a great loss to an author/owner. Therefore, the use of digital content requires stringent security methods and techniques to protect digital contents from piracy.
[0003] A digital rights management [DRM] is a technology used by owner/author/seller to control the access, copy of the digital contents after it has been given to customer. Digital Rights Management is applicable in distribution and delivery of content such as eBooks, eMagazines, & eJournals via software readers in authorized devices belonging to the authorized users. DRM is used to deny the user ability to copy the digital contents or converting it to other formats. And also DRM gives control to the hands of a computer program to protect the digital content from piracy. Thus, digital rights management provides an utmost level of security to the digital content.
[0004] The protection can be given to digital content by encryption and password security but it can be cracked by a host of programs available on the internet. There are also other types of security available to protect the digital content. One such type of security level is that providing security token associated with the user and other type of security level is that providing security token associated with the device to prevent the piracy. Hence many of the existing DRM techniques provides encryption, password protection, security key associated with the user and devices as the features of security that can be present individually or in one or more combinations. However, it has been observed that the security level present in the existing system is not full proof and further it can be enhanced.
[0005] Therefore there is a need to develop a system and method for improving the security plan for protecting digital content with an additional level of security. Further, there is a need to provide a system which can protect the digital content with various levels of security like encryption, password protection along with security token associated with the user, device and digital content such that the unauthorized users can’t copy and read the digital contents.
SUMMARY
[0006] In view of the foregoing, an embodiment herein provides a method and system for digital right management of digital contents. Accordingly, the method comprises allowing a user to login into a system platform with login credential using a user device, generating a user token and issuing the user token to the user, generating an unique device token for the user device and issuing the device token to the user device, generating a digital content token associated with the digital content and delivering the digital content token to the user device, storing the digital content token in an arbitrary folder of the user device, verifying the user token, device token, and digital content token for the digital content, based on matches, allowing the user to access and read the digital content from the user device.
[0007] In an embodiment, the digital contents are downloaded in the user device from a server via a communication network, and are readable using a reader provided in the user device. Further, digital contents are stored in internal storage of the user device and are readable while offline from the network.
[0008] In an embodiment, the folder location of digital content token is changed and/or updated when the user access the digital contents.
[0009] A system for digital right management of digital contents, the system comprising a user module that enables user to login and logout into the platform and generating user token, a server module that enables for receiving request from user for user token, issuing user token, storing the details of users and digital contents, a token management module that manages token for the digital content, user device and user, a library module that enables to maintain the list of digital contents purchased by the user, a download module that enables to download the digital content from the server and store the digital content in the internal storage of user device, and an arbitrary memory module that enables to place the digital content token in a random location in the internal memory of user device.
[00010] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.
BRIEF DESCRIPTION OF THE DRAWINGS
[00011] The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items.
[00012] Fig. 1 illustrates a sequence diagram of method for digital right management of digital contents in accordance with an example embodiment herein;
[00013] Fig. 2 illustrates a sample reader architecture for implementing system and method of digital right management of digital contents in accordance with an example embodiment herein;
[00014] Fig. 3 illustrates a sample token flowchat of digital contents if already downloaded in accordance with an example embodiment herein;
[00015] Fig. 4 illustrates a sample token flowchat of digital contents if not downloaded in accordance with an example embodiment herein; and
[00016] Fig. 5 illustrates a schematic diagram of various modules present in the digital content security system in accordance with an example embodiment herein;
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
[00017] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[00018] As mentioned above, there is a need to provide methods and systems for digital right management of digital contents using digital rights management. The embodiments herein achieve this by providing a token architecture for implementing methods and systems which can enable the author to protect their original work by providing enhanced layers of security to the digital contents. . Referring now to the drawings, and more particularly FIGS. 1 through 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
[00019] It is to be noted that even though the description of the invention has been explained using book, it should, in no manner, be construed to limit the scope of the invention. The systems and methods can be implemented for any types of digital content. The digital content can include but not limited to an electronic text document such as an e-book, an e-magazine, e-journal etc, and also a multimedia audio or video file.
[00020] In an embodiment, a digital content can be downloaded and/or stored in any type of user device which can include but not limited to a mobile phone, a tablet, a laptop, a personal digital assistant (PDA), a smart phone, a web appliance, or any device capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that device.
[00021] Figure 1 illustrates a sequence diagram 100 of method for digital right management of digital contents, according to an embodiment. Initially, a user can log in to a system platform 101 to read a digital content in a secure manner, wherein the system platform 101 is provided in the user device. In case, the user is entering in to the system platform for a first time means a unique user token may be generated 102 with the help of user’s details and the same can be stored in a server. The user device can connect and communicate with the server through a communication network, preferably internet. A unique device token can be generated 103 by the device and each device can include an own unique identity number may consists of 40 characters. The unique device identity / UDID can be used to recognize the device for validation.
[00022] In some example embodiments, a unique user token may be generated when the user can login in to the system platform while entering username and password details. An activation mail can be sent to the user for registration and the mail can include the activation for registration. The account can be activated by the above process and after the process of registration and activation then the user can login in to a unique session.
[00023] In some example embodiments, the user device as one of the security feature can have a unique identity number and every user can be limited to three devices. The system platform may check if the device is already exists in any other user’s device list or exceeds the user’s limit to add the device by comparing unique device identity / UDID.
[00024] In some example embodiments, every time the user logs in to an account a session key can be generated in order to provide an extra level of security and it can provide the validity of predetermined days for example ten days. If the session key expires it can be renewed for more days after the user log on to account.
[00025] In a preferred embodiment, a show library method can be used to display a list of digital contents preferably books which are purchased by the user 104. On clicking the book for the first time, a download book method is enabled and it can download the book from the server 105 and store it on the device memory. Digital content can include a unique token 106 for digital content to provide an extra level of security to the original work of the author. The digital content token 106 associated with the digital content can be stored in an arbitrary folder 107 to make the folder’s location dynamic and may keep on changing whenever a new book is opened or the same book is closed and again opened.
[00026] In a further embodiment, the system platform can construct 108 and check for the digital token preferably book token in the digital content if the digital token exists in the digital content 109 then the system platform can allow the digital content to be opened 113. If the user has a valid digital content token associated with the digital content, then the digital content can be opened or the system platform can reject the book from opening it. In another embodiment, if the digital content token is not present, then the system platform can enable refresh server 110 to get the information about subscribed books with which the token can be constructed. Again the system platform may check for the digital content token and, if the digital content token is present 111 then the digital content can be opened, otherwise the user can return to library 113.
[00027] Exemplary methods for implementing a system for digital right management of digital contents are described with reference to Fig 2 to 4. These exemplary methods can be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, and the like that perform particular functions or implement particular abstract data types. The methods can also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communication network. In a distributed computing environment, computer executable instructions may be located both in local and remote computer storage media, including memory storage devices.
[00028] The exemplary methods are illustrated as a collection of operations in a logical flow graph representing a sequence of operations that can be implemented in hardware, software, firmware, or a combination thereof. The order in which the methods are described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the methods, or alternate methods. Additionally, individual operations may be deleted from the methods without departing from the spirit and scope of the subject matter described herein. In the context of software, the operations represent computer instructions that, when executed by one or more processors, perform the recited operations.
[00029] Fig. 2 illustrates sample reader architecture for implementing system and method of digital right management of digital contents, according to an embodiment. Accordingly, a splash screen 201 can be generated to enter in to the system platform to start a process of accessing digital content. The user may login 202 with the user ID, password and unique device identity and the details can be passed to the server 203. If the entered details by the user are valid then the server can response to the system platform by unique user token or else the system platform can intimate the user to enter the correct details. Once the user login in to the system platform, the user ID and token are stored in the preference table and the user can be directed to a library 204.
[00030] In an embodiment, a data server 205 can include the list of digital contents preferably books purchased by the user. The library 204 can send the user ID and unique user token to the data server 205. After verification, the data server 205 can respond to the library with the list of books purchased by the user. The details of books are stored in the database 206 and the database 206 and the digital tokens are stored in arbitrary memory 207. The user can click to open the digital content, and simultaneously the system platform can check to see whether the digital content token is present in the arbitrary folder or not and only if the token is present then the book can be opened. Accordingly, the digital content can be opened in the reader if the token for the digital content is present in the arbitrary memory 207.
[00031] In a preferred embodiment, the digital content token can be stored within a random folder hierarchy generated programmatically in the internal storage 209, which can also contain junk file to divert the user attention from the real file which includes the token list. The token file can update/change the location every time when the user opens a new digital contents or closed and opened the same digital content. The token path can be saved in the preference table. The stored digital content URL and data can be stored in the database 206.
[00032] Fig. 3 illustrates a sample token flowchat of digital contents if already downloaded, according to an embodiment. Accordingly, the reader App in the system platform creates digital content token. Then, the downloaded digital contents 301 can check the arbitrary folder for the digital content token 302. If the token is present, the digital content is loaded to the reader 303. If the token is not present then the system platform can load the list of books purchased by the user and can store it in the new location of the internal memory. In another embodiment, if the token doesn’t match with the digital content then the user may go back to library 304.
[00033] Fig. 4 illustrates a sample token flowchat of digital contents if not downloaded, according to an embodiment. Whenever the digital content is tapped to open it, the system platform can ask the user to download the digital content if it is not downloaded. If the digital content us not downloaded 401, the system platform can display popup 402. On clicking the book for the first time, download option may be prompted to download the digital content and store it in the device’s memory. The file location can be decided by the user from using setting class 403 by default it can be the memory for example phone memory. In another embodiment, the digital contents can also be saved in the either in phone memory or SD card.
[00034] In an example embodiment, if phone memory is selected then the digital content can be stored in app_internalstorage/eReaders 405 folder. If the SD card is selected then the digital content the system platform can generate a folder called “eReaders” 404 and stores the digital content on it.
[00035] Figure 5 illustrates a schematic diagram of a various modules present in the digital content security system, according to an embodiment. The digital content security system can comprise a user module 501, a server module 502, a token management module 503, a library module 504, download module 505, an arbitrary memory module 506 and other optional modules 507. The components of the digital content security system can facilitate an extra level of security to the digital content.
[00036] In an embodiment, the user module 501 can be configured to enable the user to login and logout from the system platform by providing necessary login credentials. Further, the user module 501 can generate user token after successful login into the system platform.
[00037] In an embodiment, the server module 502 can be configured for receiving request from user for user token, issuing user token, storing the details of the users, digital contents purchased by the users, and handling all other server activities.
[00038] In an embodiment, the token management module 503 can be configured to manage the token management functions of the digital content. Further, the token management system can manage the details of the tokens for the digital content, user device and user. Further, token management module 503 can provide user token, device token, and digital content token.
[00039] In an embodiment, the library module 504 can be configured to maintain the list of digital contents purchased by the user. The library module 504 can form as the link between the user module 501 and server module 502. Further the library module 504 can store all digital content data into the database.
[00040] In an embodiment, the download module 505 can be configured to download the digital content from the data server 205 after varying with tokens related to the user, device. Further, the download module 505 can enable to download the digital content for the first time and further it can allow the digital content to access in offline.
[00041] In an embodiment, the arbitrary memory module 506 can be configured to place the digital content token in a random location. The digital content token can be stored within a random folder in the internal memory 209 which can also contain junk file to divert the user attention from the real file which may contains the token list. The token file can update the location of the digital content every time when the user opens a new book or the same book is closed and opened.
[00042] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications. Such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the appended claims.
| # | Name | Date |
|---|---|---|
| 1 | Form-2.pdf | 2013-10-18 |
| 1 | patent drawings - DRM.pdf | 2013-10-18 |
| 2 | Form-26.pdf | 2013-10-18 |
| 2 | Form-5.pdf | 2013-10-18 |
| 3 | Form-3.pdf | 2013-10-18 |
| 4 | Form-26.pdf | 2013-10-18 |
| 4 | Form-5.pdf | 2013-10-18 |
| 5 | Form-2.pdf | 2013-10-18 |
| 5 | patent drawings - DRM.pdf | 2013-10-18 |