1. Technical Field
Embodiments of the present disclosure relate to digital data, and more particularly to digital data processing system and a method for processing digital data thereof.
2. Description of Related Art
Many teachers use computers to teach and communicate with students in a class and outside the class. If digital data (e.g. electronic files of textbooks or outside readings) is stored in the computer, the teachers can interact with the students conveniently and the students can study anytime and anywhere. However, the digital data cannot be easily processed by the students, and the students cannot provide the digital data conveniently to communicate or interact with the teacher.
The present disclosure, including the accompanying drawings, is illustrated by way of examples and not by way of limitation. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean “at least one.”
In general, the word “module”, as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language. One or more software instructions in the modules may be embedded in firmware, such as in an erasable programmable read only memory (EPROM). The modules described herein may be implemented as either software and/or hardware modules and may be stored in any type of non-transitory computer-readable medium or other storage device. Some non-limiting examples of non-transitory computer-readable media include CDs, DVDs, BLU-RAY, flash memory, and hard disk drives.
In one embodiment, the storage device 11 includes a first database 110 storing digital data and parameters of the digital data. The digital data corresponds to one or more authorization levels which are available to be browsed. The parameters of each of the digital data include, but are not limited to, a name, a minimizing chart, a price, and a brief, for example. The first database 110 further includes registration information of each of the client devices 2. The registration information includes, but is not limited to, an account name, a password, and an authorization level of each of the client devices 2.
The charge unit 13 is a payment platform between the first server 1 and the client devices 2. The client devices 2 can pay money for the digital data to the first server 1 using the charge unit 13. If the payment is completed by the client devices 2, the charge unit 13 transmits a prompt of a successful trade to the first server 1.
Each of the client devices 2 includes a display screen 20 and a storage system 22. Each of the client devices 2 displays a user interface 21 provided by the first server 1, on the display screen 20. The user interface 21 includes a browsing interface and an editing interface. The client devices 2 is connected to the first server 1 to browse available digital data through the browsing interface, and to process digital data or to upload digital data through the editing interface. The storage system 22 stores data of each of the client devices 2, such as, downloaded digital data.
The second server 3 includes an authorization database 30 storing data of different authorization levels corresponding to account numbers of different client devices 2, and storing data of available operations on the digital data corresponding to each of the authorization levels. The available operations may include a downloading operation, a purchasing operation, and a uploading operation, for example. In other embodiments, the authorization database 30 may be included in the first server 1.
As shown in
In step S110, the validation module 100 validates whether the client device 2 is connected correctly using a password and account name. The validation module 100 compares the account name and the password received from the client device 2 with the registration information stored in the content database 110. If an account name in the registration information is the same as the received account name, and the received password matches a password corresponding to the account name, the validation module 100 determines that the client device 2 is connected to the server 1 correctly.
In step S111, when the client device 2 is connected to the first server 1 correctly (hereinafter the client device 2 is referred to as “the connected client device 2”), the obtaining module 102 obtains an authorization level of the connected client device 2 from the second server 3. The obtaining module 102 queries the authorization level of the connected client device 2 from the authorization database 30 according to the account name of the connected client device 2.
In step S112, the transmission module 104 searches for available digital data to be browsed corresponding to the obtained authorization level of the connected client device 2, and transmits parameters of the available digital data to the connected client device 2. The parameters of the available digital data is displayed on the display screen 20 of the connected client device 2.
In step S113, the receiving module 106 receives a process command for processing specified digital data from the connected client device 2. The specified digital data is selected from the available digital data. The processing command is to purchase or to download the specified digital data.
In step S114, the determination module 108 determines whether the connected client device 2 is authorized to process the specified digital data according to the obtained authorization level, when the processing command is received from the connected client device 2. If the connected client device 2 is authorized to process the specified digital data, step S116 is implemented. If the connected client device 2 is not authorized to process the specified digital data, step S115 is implemented.
In one embodiment, if the processing command of purchasing the specified digital data is received, the determination module 108 determines that the connected client device 2 is authorized to purchase the specified digital data, when the obtained authorization level indicates that the connected client device 2 is authorized to purchase the specified digital data and the first server 1 receives a prompt of a successful trade. The determination module 108 further determines that the connected client device 2 is not authorized to purchase the specified digital data, when the obtained authorization level indicates that the connected client device 2 is not authorized to purchase the specified digital data, or when the obtained authorization level indicates that the connected client device 2 is authorized to purchase the specified digital data, but the first server 1 has not received the prompt of a successful trade within a preset time duration or the first server 1 receives a prompt of a failure trade.
In step S115, the prompt module 110 transmits a prompt of a wrong processing authorization to the connected client device 2, and step S112 is repeated. The prompt module 110 may transmit a message of “wrong processing authorization” to be displayed on the display screen 20 of the connected client device 2.
In step S116, the storing module 112 transmits the specified digital data to the connected client device 2 for storing the specified digital data in the storage system 22 of the connected client device 2.
In step S120, when one client device 2 is connected to the first server 1 by transmitting an account name and a password of the client device 2 to the first server 1 through the editing interface, the validation module 100 validates whether the client device 2 is connected correctly. The validation module 100 compares the account name and the password received from the client device 2 with the registration information stored in the content database 110.
In step S121, when the client device 2 is connected to the first server 1 correctly, the obtaining module 102 obtains the authorization level of the connected client device 2 from the second server 3. The obtaining module 102 queries the authorization level of the connected client device 2 from the authorization database 30 according to the account name of the connected client device 2.
In step S122, the receiving module 106 receives an upload command of digital data selected from the connected client device 2. The connected client device 2 may select a preset option of the upload command to execute an upload operation. In one embodiment, the connected client device 2 can edit the uploaded digital data stored in the storage system 22.
In step S123, the determination module 108 determines whether the connected client device 2 has authorization to upload the digital data according to the obtained authorization level, when the uploading command is received from the connected client device 2. If the obtained authorization level indicates that the connected client device 2 is authorized to upload the digital data, step S125 is implemented. If the obtained authorization level indicates that the connected client device 2 is not authorized to purchase the specified digital data, step S124 is implemented.
In step S124, the prompt module 110 transmits a prompt of a wrong uploading authorization to the connected client device 2, and the procedure ends. The prompt module 110 may transmit a message of “wrong uploading authorization” to be displayed on the display screen 20 of the connected client device 2.
In step S125, the storing module 112 receives uploaded digital data from the connected client device 23 and stores the uploaded digital data into the first server 1 according to a predetermined format.
In one embodiment, in order to ensure safety of transmission of the digital data, the first server 1 may adopt a predetermined encoding method to encrypt the transmitted digital data. The client device 2 may use a decoding method corresponding to the encoding method to obtain the transmitted digital data.
All of the processes described above may be embodied in, and be fully automated via, functional code modules executed by one or more general-purpose processors. The code modules may be stored in any type of non-transitory computer-readable medium or other storage device. Some or all of the methods may alternatively be embodied in specialized hardware. Depending on the embodiment, the non-transitory computer-readable medium may be a hard disk drive, a compact disc, a digital video disc, a tape drive or other suitable storage medium.
The described embodiments are merely possible examples of implementations, set forth for a clear understanding of the principles of the present disclosure. Many variations and modifications may be made without departing substantially from the spirit and principles of the present disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and the described inventive embodiments, and the present disclosure is protected by the following claims.
Number | Date | Country | Kind |
---|---|---|---|
102119273 | May 2013 | TW | national |