TWI617938B - Device of licensing program, device of purchasing program and method of licensing program thereof - Google Patents

Abstract

The present invention provides a device for authorizing a program, the program comprising a header, the device comprising a storage device, a file system, an operating system, and an authorization verification component. The operating system receives an activation program command and starts the program, and stores the header in the storage device for the operating system to read the header. The authorization verification component interrupts the operating system to load the program into a random access memory and cooperates with the operating system or a remote server to perform an authorization verification. When the authorization verification is passed, the authorization verification component allows the program to continue to load the random access memory for execution.

Description

Authorized program device, program transaction device, and method for authorizing program

The present invention relates to a method of authorizing a program, and more particularly to a method of authorizing a program in the cloud.

Cloud storage refers to the mode of data storage on the network, that is, the data is stored in multiple virtual servers that are usually hosted by third parties, rather than dedicated servers. According to the customer's needs, the data center operator prepares to store the virtualized resources on the back end and provides them in a storage pool. The storage resources pool can be used by the customer to store files or objects. Cloud computing is an Internet-based computing method in which shared software and hardware resources and messages can be provided to computers and other devices on demand. Cloud computing describes a new Internet-based information technology (IT) service addition, usage, and delivery model that typically involves providing dynamic transaction extensions over the Internet and often virtualized resources that users can access. Service software and information, service providers maintain infrastructure and platforms to maintain normal service operations. Services or software provided by service providers are often referred to as "on-demand software" and are usually charged based on hours of use. These services can be used only with low-complexity hardware and software devices, which saves the cost of the enterprise. Since the application is centrally available, updates can be released instantly, without the need for users to manually update or install new software. As a result, cloud computing enables organizations to deploy applications more quickly, reduce management complexity and maintenance costs, and allow rapid redistribution of IT resources to respond to rapid changes in business needs.

The concept of the cloud is beneficial to users or enterprises. It does not need to purchase all kinds of hardware devices and software with powerful processing performance. The maintenance and software update of these hardware devices are carried out by the service provider, and the user or enterprise It is to "virtualize" hardware devices and software as much as possible. However, whether the user or the enterprise user obtains the serial number after purchasing the software, the software can be used only after the software is installed or after the program is started, and the user must wait for the email to be collected after purchasing the software. If the letter obtains the serial number or obtains the serial number through the physical store, it takes several minutes to several days to wait for the waiting time, and there is a sequence number generator to crack the serial number or crack the software verification mechanism, etc., and it is easy to cause piracy.

Please refer to the first figure, which is a schematic diagram of the process of the custom authorization program. In step S101, the client system receives the launch application command. Step S102, the client system loads the application into the memory, and the memory may include a hard disk or a random dynamic access memory (RAM), and the application can be downloaded from the server of the server to the client system through the network. The hard drive then loads the application from the hard drive into RAM for execution. The application can also be directly executed from the internal file server of the enterprise and loaded into the RAM of the client system. In step S103, the application determines whether the authorization is passed. If there is authorization, the process proceeds to step S104. If the authorization is not passed, the process proceeds to step S105. Step S104, executing an application. In step S105, the application program asks the user to input the verification code. When the verification is successful, the process proceeds to step S104; when the verification fails, the process proceeds to step S106. After the application is executed in step S105 or after the verification fails, the process proceeds to step S106, and the flow of the program is ended.

In the steps of the prior authorization program, all applications are first loaded into the memory for authorization verification, and the application can be easily copied and falsified, bypassing the authorization verification action, thus easily causing the software. The situation of piracy. In another prior art, a verification-authorized program is used for authorization verification, which is not controlled by the driver of the client system to enable the operating system to verify, so the integrity and security of the authorization verification are reduced, resulting in The scam of pirated software. Moreover, such programs must be written for authorization verification according to various specific applications. If the access to the application files can be accessed through a necessary process, there is no need to write a program dedicated to verification and authorization according to different applications. . Therefore, it is desirable to have a method in which the driver of the client system can notify the operating system to perform authorization verification before allowing the software to load into the RAM before the software is loaded into the hard disk or the RAM, thereby avoiding the problem of piracy.

For the number of authorized software for internal software, it is usually that several computers within the enterprise buy several authorized quantities for software installation, and the software can only be used on the computer where the software is installed after installation. Since the installation of the same serial number on two different computers or devices does not comply with the software license, if you want to use it on another computer that is not installed, the software installed on the original computer needs to be uninstalled, and then the software. It can be installed on another computer, that is, the right to use the software must be different from the hardware device. The disadvantage of this authorization method is that when the number of authorized internal enterprises is less than the number of computers inside the enterprise, it still needs to be purchased. The number of licenses for all computers is not flexible. Therefore, it is desirable to have a license method that is independent of the computer or device, and only need to manage the number of licenses.

According to the above concept, the present invention provides a method for authorizing a program, which is stored in a storage device or a remote server and includes a plurality of executable files, the plurality of executable files including a first executable file and a second executable file. The first executable file includes a first header, and the second executable file includes a second header. The method includes the steps of: causing an operating system to receive a program launch command and launch the program. Having the operating system store the first header in the storage device to read the first header, and causing an authorization verification component to interrupt the operating system to load the first execution file into a random access memory carried out. The authorization verification component is mated with the operating system or the remote server for an authorization verification. After the first execution file is verified by the authorization, the authorization verification component allows the first execution file to be loaded into the random access memory for execution. When the second When the executable file is used, the operating system reads the second header and the authorization verification component cooperates with the operating system or the remote server to perform another authorization verification.

In accordance with the above concept, the present invention provides a method of authorizing a program comprising the steps of causing an operating system to receive a program launch command and launch the program. An authorization verification component is coupled to the operating system itself or a remote server to perform an authorization verification before the operating system loads the program. When the authorization verification is passed, the operating system or a storage device obtains a token.

In accordance with the above teachings, the present invention provides a device for authorizing a program, the program comprising a header, the device comprising a storage device, a file system, an operating system, and an authorization verification component. The file system is configured in the storage device, the operating system receives an activation program command and starts the program, and loads the header into the random access memory to read the header. The authorization verification component interrupts the operating system to load the program into the random access memory and cooperates with the operating system or a remote server to perform an authorization verification. When the authorization verification is passed, the authorization verification component allows the program to continue to load the random access memory for execution.

In accordance with the above concept, the present invention provides a method of authorizing a program comprising the steps of: selecting a particular program. An authorization verification is performed by a local operating system itself or a remote server. When the authorization verification is passed, the operating system loads the specific program into a specific memory.

In accordance with the above concept, the present invention provides a program transaction apparatus including a first access element, a second access element, and an authorization verification element. The first access element accesses a remote library, and the remote library includes a plurality of programs. The second access element is accessed by a local operating system to select a particular program from the plurality of programs. The authorization verification component cooperates with the local operating system itself or a remote server to perform an authorization verification, and the authorization verification After passing, the specific program is executed.

In accordance with the above concept, the present invention provides a device for authorizing a program, the device comprising a host and a mobile device. The host includes an operating system and a driver. The mobile device includes the program and an authorization verification component, the authorization verification component includes a firmware, wherein when the mobile device is coupled to the host, the mobile device interrupts transmission of the program from the mobile device to the host, and the The driver interrupts the program by loading the operating system into a random access memory, and the authorization verification component is activated to enable the operating system to cooperate with the firmware to perform an authorization verification via the driver. After verification, the program allows the program to be transferred from the mobile device to the host, and the driver allows the program to be loaded into the random access memory by the operating system.

According to the above concept, the present invention provides a method for authorizing a program in a program transaction device, the program transaction device comprising a host and a mobile device, the host comprising a driver, a random access memory, and an operation The system includes an authorization verification component and the program, the authorization verification component comprising a firmware, the method comprising the steps of: coupling the mobile device to the host. The body interrupts the transfer of the program from the mobile device to the host, and the driver interrupts the program execution by loading the random access memory by the operating system. The authorization verification component is activated to cause the operating system to cooperate with the firmware to perform an authorization verification via the driver. When the authorization is verified, the body allows the program to be transferred from the mobile device to the host, and the driver allows the program to be loaded by the operating system to load the random access memory.

With the method of authorizing a program and the program trading platform provided by the present invention, the number of licenses purchased by the enterprise user can be flexibly adjusted to reduce the number of unnecessary purchase authorizations, which can be installed by the enterprise user more economically to purchase the required software. And to meet the needs of enterprise users for the number of applications authorized. On the other hand, for vendors that provide applications, Tight authorization verification reduces the chances of application piracy, which is more secure for vendors who provide applications. The invention is also applicable to general users.

301‧‧‧ main application

302‧‧‧Local operating system

302‧‧‧File System

304‧‧‧ Random access memory

305‧‧‧Remote Server

306‧‧‧Storage device

307‧‧‧Authorization verification component

30‧‧‧Program Trading System

40‧‧‧Cloud System

32‧‧‧Program Trading Device

42‧‧‧public cloud

44‧‧‧Private cloud

421‧‧‧Cloud Host

422‧‧‧Internet

441‧‧‧Software host

442‧‧‧Local Network

443,444,445,446,447‧‧‧Computer host

50, 60‧‧‧ Authorized system

501‧‧‧File System

52, 62‧‧‧ Authorized device

502‧‧‧ operating system

503,603‧‧‧Authorization verification component

504, 604‧‧‧ Startup program instructions

505, 609‧‧‧ program

506‧‧‧Remote Server

5050, 6090‧‧ ‧ heading

507‧‧‧Storage device

508‧‧‧ random access memory

602‧‧‧ operating system

601‧‧‧ mobile device

607‧‧‧ Firmware

611‧‧‧Host

309,608‧‧‧Driver

The first figure is a schematic diagram of the process of authorizing a program.

The second figure is a schematic diagram of the flow of the authorization of the first preferred embodiment of the present invention.

Third, a schematic diagram of a program transaction system in accordance with a first preferred embodiment of the present invention.

Fourth, a schematic diagram of a cloud system authorization according to a second preferred embodiment of the present invention.

Figure 5 is a schematic illustration of a method of authorizing a program in accordance with a third preferred embodiment of the present invention.

Figure 6 is a schematic diagram of a program authorized by a fourth preferred embodiment of the present invention.

Figure 7 (a) is a schematic illustration of a system for authorizing a program in accordance with another preferred embodiment of the present invention.

Figure 7(b) is a schematic illustration of a system for authorizing a program in accordance with another preferred embodiment of the present invention.

Figure 8 is a schematic illustration of a method of authorizing a program in accordance with another preferred embodiment of the present invention.

Figure 9 is a schematic illustration of a method of authorizing a program in a program transaction device in accordance with the present invention.

The detailed description of the present invention is to be understood by the claims The present invention is not limited to the embodiments shown in the accompanying drawings. The present invention is not limited to the embodiments described herein.

Please refer to the second figure, which is a schematic diagram of the flow of authorization according to the first preferred embodiment of the present invention. The client system must install the main application before using the application trading platform. The main application is provided to the user for download and installation free of charge. The main application includes the driver for communicating the operating system and the hardware device, and the operating system of the client system. Information about the memory space that needs to be read. Step S201: The client system receives the launch application command. In step S202, the authorization is determined. In step S202, the authorization data is transmitted by the operating system of the client system to the remote server for authorization verification before accessing the file of the purchased application. Before the authorization verification is performed, when the flow of the operating system of the client system proceeds to the process of reading the purchased application file, the driver stops reading the purchased application file, and the operating system of the client system at this time To perform authorization verification. When the authorization verification is successful, the driver allows to continue reading the purchased application file, and proceeds to step S203; when the authorization verification is successful, proceeds to step S204. In step S203, the driver delivers the purchased application file to the operating system control of the client system. Step S204, the remote server requires the user to provide an account and a password to log in to the remote server's authorization system. Step S205, the remote server checks the payment status of the account. When the payment status of the account is the paid status, the process goes to step S203, and then proceeds to steps S206 and S207 in sequence; when the payment status of the account is not When the status of the payment is made, the process proceeds to step S207. Step S206: The operating system loads the purchased application file into a random access memory (RAM) of the client system for execution. Step S207 ends the main application.

Please refer to the third figure, which is a schematic diagram of a program transaction system 30 according to a first preferred embodiment of the present invention. The program transaction system 30 includes a program transaction device 32 and a remote server 305. The program transaction device 32 includes a first access element, a second access element, and an authorization verification component 307. For example, the first access element is a storage device 306 and the second access element is a random access memory 304. The first access element accesses a remote program library of the remote server 305, and the remote program library includes a plurality of programs, that is, an application to be purchased. The second access element is accessible to the local operating system 302 to select a particular program from the plurality of programs. The authorization verification component 307 cooperates with the local operating system itself 302 or the remote server 305 to perform an authorization verification, and when the authorization verification is passed, the specific program is executed.

In the third figure, the program transaction device 32 further includes a main application 301, a local operating system 302, a driver 309, and a file system 303. When the application to be purchased is selected to be executed, the local operating system 302 reads the header of the purchased application to confirm information such as the size of the memory required by the purchased application, and then allocates (allocate) a new process for the purchased application, and start the new program, at which time the authorization verification component 307 is activated to transmit the verification information 2 to perform authorization verification, authorization to the remote server 305. The verification component 307, after being notified of the authorization verification, transmits one of the control messages 1, 2, and 3 to control one of the storage device 306, the file system 303, and the driver 309, respectively, to allow the purchase. The application file is stored from the remote server 305 to the storage device 306, the purchased application file is stored from the storage device 306 to the file system 303 through the driver 309, and the purchase is made by the local operating system 302. The application file is loaded from the file system 303 into the random access memory 304 for execution. In another preferred embodiment, the authorization verification component 307 can also transmit the verification information 1 to the local operating system 302 for authorization verification. After the authorization verification is passed, the authorization verification component 307 transmits the control message 1 and the control message 2 to allow. The purchased application file from the far end The library of server 305 is loaded into random access memory 304 for execution. In the third figure, the dotted line between the storage device 306 and the random access memory 304 represents that the purchased application file is indirectly accessed therebetween, that is, the information of the purchased application file is transmitted through the storage device 306. The program 309, the file system 303, and the operating system 302 are then loaded into the random access memory 304 for execution.

In the third figure, storage device 306 can be a hard disk of remote server 305, a local hard disk, a dedicated random access memory block, or any combination thereof. The location of the purchased application file is different depending on the design, and the file system 303 is assigned where to access the purchased application file. . In order for the local operating system 302 to access data for a particular profile at a particular location, the profile system 303 is modeled on the storage device 306 for receiving instructions from the local operating system 302 to access data for a particular profile at a particular location. The authorization verification component 307 can include a driver and a portion of the main application 301, or the main application 301 can include the driver and the authorization verification component 307. The authorization verification component 307 is tasked with the local operating system 302 or The remote server 305 cooperates to verify the authorization, and after passing the authorization verification, the authorization verification component 307 allows the purchased application file to be stored to or read from the storage device 306 to the file system 303, or The operating system 302 loads from the file system 303 to the random access memory 304, depending on whether the authorization verification component 307 can control the hard disk to the storage device 306, the file system 303, and the remote server 305. The present invention primarily disables the purchased application file from the storage device 306 to the file system 303 prior to authorization verification, or causes the local operating system 302 to disable the purchased application file from the file. System 303 is loaded into the random access memory 304.

When the purchased application file is loaded into the random access memory 304, the local operating system 302 calls the application entry point based on an application entry point recorded by the header of the purchased application file. The operating system 302 will then execute the right It is handled by this new program.

Please refer to the fourth figure, which is a schematic diagram of the authorization of the cloud system 40 according to the second preferred embodiment of the present invention. The cloud system 40 includes a public cloud 42 in the external environment of the enterprise and a private cloud 44 inside the enterprise. The private cloud 44 includes a software host 441, a local area network 442, and a plurality of computer hosts 443, 444, 445, 446, 447. The public cloud 42 includes a cloud host 421. The application software on the cloud host 421 can be distributed to the enterprise software host 441 after the enterprise purchases a certain amount of application software license, and the software host 441 distributes the specific number of application software to the plurality of computer hosts. 443, 444, 445, 446, 447. In the fourth figure, only the cloud host 421 is connected to an enterprise software host 441 through an Internet 422. In another preferred embodiment, the cloud host 421 can be connected to a plurality of software hosts through the Internet. Each software host in the complex software host is owned by a different enterprise.

In the fourth figure, the authorization verification between the cloud host 421 and the in-house software host 441 and the use of the purchased application file can be managed by the cloud host 421. The cloud host 421 has a first key, which serves as a signature for the authorized number. The software host 441 in the enterprise has a second key, which serves as a purpose for verifying the authorized quantity. After the enterprise first purchases a certain amount of authorization from the server, the cloud host 421 encrypts the authorized quantity data using the first key, and then encrypts the encrypted authorized quantity data for signature authentication, so once the authorized quantity is The data has been tampered with, and the encrypted authorized data will be different from the signature-certified information. The signed and authenticated information is transmitted to the software host 441 in the enterprise via the Internet 422, and the software host 441 decrypts the signed and authenticated information by using the second key to verify the authorized quantity, so when the authorized quantity is When tampering, the information after the signature verification is not met during verification, and the cloud host 421 will directly reject all authorized actions. If the signature is met, the purchased application file can be downloaded to the internal software host 441 via the Internet 422, or the company's information personnel can store the signed and certified information to another computer. Use another computer Downloading the purchased application via the Internet 422, such offline download of the software host 441 can avoid the risk of the software host 441 being smashed or poisoned.

In the fourth figure, the software host 441 inside the enterprise can manage the authorized number of the cloud host 421 authentication. In a preferred embodiment, there are five computer hosts 443, 444, 445, 446, 447 in the local area network 422 of the enterprise, but only three sets of application files are required for the purchase, so only three authorized quantities are purchased, for example, The host computer 443, 444 first installs the main application and then uses the same purchased application. The software host 441 records how many computer hosts the purchased application has been used, and reduces the number of authorized numbers in the software host 441 by two. When the host computer 445 installs the main application and uses the same purchased application, the number of authorized numbers is reduced by one. When the host computer 446 installs the main application and uses the same purchased application, the count of the authorized number has become negative. It indicates that the software host 441 has verified that the authorized number has exceeded, and the computer host 446 is not executed. When the host computer 443 does not use the purchased application, the downloaded application file stored in the storage device 306 in the third figure is not loaded into the random access memory 304 by the local operating system 302, and the software host is executed. The number of licenses in 441 is increased by 1, so that one of the host computers 446 or 447 can use the same purchased application.

In a preferred embodiment, the program transaction device 32 in the third figure is the software host 441, and the remote server 305 is the cloud host 421. In another preferred embodiment, the program transaction device 32 is any one of a plurality of computer hosts 443, 444, 445, 446, 447, and the remote server 305 is the software host 441. The authorization verification component 307 inside the software host 441 is not loaded by the local operating system 302 into the random access memory 304 when the authorization verification fails. Similarly, any of the plurality of computer hosts 443, 444, 445, 446, 447 does not allow the purchased application to be stored in the storage device 306 or loaded into the random access memory before the authorized number of verifications is passed. 304.

When the plurality of computer hosts 443, 444, 445, 446, 447 are in different local area networks, the network speed is slower and the delay is higher. After the authorization verification is passed, the purchased application files can be stored in the storage device 306 first, and then the purchased application files are saved. Loaded from storage device 306 into random access memory 304 via file system 303 and local operating system 302. That is, in RAM for execution.

The person who uses the computer host inside the enterprise must log in to the account inside the enterprise. This account has different permissions according to different identities. When one of the host computers 443~447 passes the authorization verification, the software host 441 will issue a right. The stick has the authority associated with the account, and the local operating system 302 or the authorization verification component 307 of the authorized computer host determines how the purchased application file is processed according to the token, for example, the purchased application The file is loaded into random access memory 304 or the application file of the purchased application is interrupted. Similarly, the cloud host 421 can also serve as a server for authorization verification. After the enterprise user logs in to the software host 441 with an account having a specific authority, the cloud host 421 of the public cloud 42 authorizes the software host 441 according to the specific authority, so that the application file purchased by the enterprise user is downloaded to the software host 441. Of course, the local operating system 302 or the authorization verification component 307 in the software host 441 also determines how the purchased application file is processed according to the token, for example, loading the purchased application file into the random access memory of the software host 441. In 304, or the loading of the application file that was interrupted for purchase.

The purchased application file is stored in storage device 306 upon authorization. In order to prevent the application files from being copied and used, these files are protected by a specific key encryption, and the specific key is in the token, and the application file purchased by the token can be allowed to be download. When the purchased application file is executed on the host computer 443, the activated token will be recorded by the software host 441, and the activated token will remain in the record, that is, the authorized number of counts will be recorded by the software host 441, if The application that was deleted after the record was deleted The program file could not be read. If the authorized number is tampered with the cloud host disconnected, the authorization verification component 307 prohibits the purchased application file from being read from the remote server 305 of the software host 441 to the random access memory 304 of the host computer 443. in.

Authorization verification can be divided into full authorization and partial authorization according to the usage of the purchased application file. When the purchased application contains multiple applications with multiple different functions, the multiple applications can be divided into different files according to their functions. This allows partial authorization based on the file. Some licenses are applicable when only a portion of the functionality of the application is purchased.

Please refer to FIG. 5, which is a schematic diagram of a method for authorizing a program according to a third preferred embodiment of the present invention. The program is stored in a storage device or a remote server and includes a plurality of executable files. The plurality of executable files includes a first executable file and a second executable file. The first executable file includes a first header. The second executable file includes a second header. The method includes the following steps: Step S501, causing an operating system to receive a program start command and start the program. Step S502, the operating system loads the first header into the storage device to read the first header, and causes an authorization verification component to interrupt the operating system to load the first execution file into a random access. In memory. Step S503, the authorization verification component is cooperated with the operating system or the remote server to perform an authorization verification. Step S504, after the first execution file passes the authorization verification, the authorization verification component allows the first execution file to be loaded into the random access memory for execution. Step S505, when the second execution file is used, the operating system reads the second header, and the authorization verification component cooperates with the operating system or the remote server to perform another authorization verification.

In the fifth figure, when the authorization verification fails, the operating system reads a corrupted file to end the purchased application, or makes the operating system unable to read the purchased application to make the purchased application. An error occurred in the program to end the purchased application. The authorization verification can be divided into a permanent authorization verification and a rental authorization inspection according to the valid period of use. The certificate, and a trial authorization verification, the authorization verification includes one of them. When the authorization is verified as the permanent authorization verification, the program is allowed to be used indefinitely. When the authorization verification is the rental authorization verification, the program is allowed to be used within a specific time interval, when the authorization is verified as the trial. At the time of authorization verification, the program is stopped when a trial period expires.

The authorization verification further includes a network authorization or a telephone authorization, and the network authorization is performed by using a verification first authorization code, where the first authorization code includes a person privacy related information, and the personal privacy related information includes an identity card. The font size, birthday, or any combination thereof, the telephone authorization uses a telephone number for authorization verification. When the telephone authorization is verified, the telephone number is used to obtain a second authorization code, and the second authorization code is used. Authorization verification authorized by the phone. Verification by personal privacy-related messages avoids sharing serial numbers or authorization codes, and avoids the problem of programs being stolen without paying.

When the authorization verification is passed, the operating system can obtain a token. The token includes an anonymous token and a non-anonymous token. The anonymous token is used for a public computer and the non-anonymous token is used for a personal computer. The purpose of the token is to allow access to the purchased application file. The purpose of the anonymous token is to allow access to the purchased application file, but once the computer is shut down, the purchased application file will be cleared. This applies to The public computer. The purpose of the non-anonymous token is to allow access to the purchased application file, but once the computer is turned off, the purchased application file will not be erased, which applies to the private computer.

Please refer to a sixth figure, which is a schematic diagram of a program authorized by the fourth preferred embodiment of the present invention. The method for authorizing a program includes the following steps: Step S601, causing an operating system to receive a program start command and start the program. Step S602, before the operating system loads the program, an authorization verification component is cooperated with the operating system itself or a remote server to perform an authorization verification. Step S603, after the authorization verification is passed, the operating system obtains a token.

The token contains the encryption key, and the encryption key can be used to purchase the application. The file is decrypted for reading. The authorization verification includes one of a permanent authorization verification, a lease authorization verification, and a trial authorization verification. When the authorization verification is the lease authorization verification or the trial authorization verification, the authorization verification component cooperates with the remote server to perform the authorization verification. When the authorization verification is the permanent authorization verification, and the remote server cannot be connected, the authorization verification component cooperates with the operation system to perform the authorization verification. In this case, although temporary authorization verification is performed, although temporary authorization verification is performed, After a fixed period of time, for example, after one week, it is mandatory to connect to the remote server for authorization verification to ensure that the purchased application is not stolen.

In the sixth figure, the method further includes the following steps: when the anonymous token is checked and the program is closed, the program's data is restored to a preset value. When the non-anonymous token is checked and the program is closed, the program's data remains in its original state.

Please refer to FIG. 7(a), which is a schematic diagram of a system 50 for authorizing a program according to another preferred embodiment of the present invention, which includes a device 52 for authorizing a program and a remote server 506. The authorized device 52 includes a file system 501, a storage device 507, an operating system 502, and an authorization verification component 503. The program 505 is included in the software library of the remote server 506, and the program 505 includes a header 5050. The operating system 502 receives an activation program command 504 and launches the program 505, and stores the header 5050 in the storage device 508 for the operating system 502 to read the header 5050. The authorization verification component 503 interrupts the operating system 502 to load the program 505 into a random access memory 508 for execution and cooperates with the operating system 502 or the remote server 506 to perform an authorization verification. When the authorization verification is passed, the authorization verification component 503 allows the program 505 to continue loading into the random access memory 508 for execution.

In another preferred embodiment, the program 505 has not been stored in the storage device 501, but the authorization verification component 503 interrupts the operation of the program 505 to the storage device 507. The authorization verification component 503 is remote from the operating system 502. The end server 506 cooperates to perform the authorization verification. When the authorization verification is passed, the authorization verification component 503 allows the program 505 to store The program is stored in the storage device 507 and loaded by the operating system 502 from the file system 501 into the random access memory 508.

Please refer to FIG. 7(b), which is a schematic diagram of a system 60 for authorizing a program according to another preferred embodiment of the present invention, including a device 62 for authorizing a program and a remote server 606. The device-authorized device 62 includes a mobile device 601 and a host 611. The host 611 includes an operating system 602, a driver 608, and a random access memory 612. The mobile device 601 includes a firmware 607 and a program 609. The program 609 includes a header 6090. In a preferred embodiment, the operating system 602 receives an initiator command 604 and launches the program 609 and reads the header 6090.

In the seventh diagram (b), the operating system 602 and the mobile device 601 are controlled by a driver 608, which includes the authorization verification component 603, and the cartridge 607 cooperates with the driver 608 to transmit and Control the program 609. When the mobile device 601 is coupled to the host 611, the header 6090 of the program 609 is read in the random access memory 612 by the driver 608 and the operating system 602 before the authorization verification. The program 609 requires information such as the size of the memory, and then the operating system 604 allocates a new program to the program 609 and launches it, at which point the authorization verification component 603 is activated to cause the operating system 604 to pass the driver. The program 608 cooperates with the firmware 607 for authorization verification. Before the authorization verification is passed, the body 607 interrupts the transfer of the program 609 from the mobile device to the host 611, and the driver 608 interrupts the operating system 604 to load the program 609 into the random access memory 612 for execution.

After the authorization verification is passed, the firmware 607 allows the program 609 to be transferred from the mobile device to the host 611 without being interrupted. The driver 608 allows the program 609 to be loaded into the random access memory 612 by the operating system 602. Without being interrupted by the driver 608, in another preferred embodiment, authorization verification may be performed by the authorization verification component 603 in conjunction with the remote server 606 or the operating system 602.

In the seventh diagram (b), the mobile device 601 can be a portable hard disk. The operating system 602 includes one of an embedded operating system, a Windows operating system, a Linux operating system, and a Solaris operating system.

Please refer to the eighth figure, which is a schematic diagram of a method for authorizing a program according to another preferred embodiment of the present invention. The method comprises the following steps: Step S801, selecting a specific program. In step S802, an authorization verification is performed by a local operating system itself or a remote server. Step S803, after the authorization verification is passed, the operating system is allowed to load the specific program into a specific memory.

In the eighth figure, the specific memory system selects a memory path by a user, and the method further comprises: storing the specific program from a cloud host to a software host. Transfer the specific program from the software host to a regional network host. The method further comprises: interrupting execution of the program, and the authorization verification component allows the program to continue execution after the authorization verification is passed.

Please refer to the ninth figure, which is a schematic diagram of a method for authorizing a program 609 in a program transaction device 62. The program transaction device 62 includes a host 611 and a mobile device 601. The method includes the following steps: Step S901, The mobile device 601 is coupled to the host 611. Step S902, a unit 607 in the mobile device 601 interrupts the program 609 from the mobile device 601 to the host 611, and a driver 608 in the host 611 interrupts the program 609 by one of the hosts 611. The operating system 602 is loaded into a random access memory 612 in the host 611 for execution. In step S903, an authorization verification component 603 in the mobile device 601 is activated to enable the operating system 602 to cooperate with the firmware 607 to perform an authorization verification via the driver 608. Step S904, after the authorization verification is passed, the body 607 allows the program 609 to be transferred from the mobile device 601 to the host 611, and the driver 608 allows the program 609 to load the random access by the operating system 602. Memory 612 is executed.

Example

A method for authorizing a program, the program being stored in a storage device or a remote server and comprising a plurality of executable files, the plurality of executable files comprising a first execution file and a second execution file, the first execution The file includes a first header and the second executable includes a second header. The method includes the steps of: causing an operating system to receive a program launch command and launch the program. Having the operating system store the first header in the storage device to read the first header, and causing an authorization verification component to interrupt the operating system to load the first execution file into a random access memory carried out. The authorization verification component is mated with the operating system or the remote server for an authorization verification. After the first execution file is verified by the authorization, the authorization verification component allows the first execution file to be loaded into the execution memory. When the second executable is used, the operating system reads the second header and the authorization verification component cooperates with the operating system or the remote server to perform another authorization verification.

2. The method of embodiment 1, further comprising the step of: when the authorization verification fails, the operating system reads a corrupted file to end the program or disable the operating system from reading the program. And the program has an error to end the program. . After the second executable file is verified by the other authorization, the authorization verification component allows the second execution file to be loaded into the random access memory.

3. A method of authorizing a program comprising the steps of: causing an operating system to receive a program launch command and launch the program. An authorization verification component is coupled to the operating system itself or a remote server to perform an authorization verification before the operating system loads the program. When the authorization verification is passed, the operating system or a storage device obtains a token.

4. The method of embodiment 3, wherein: the authorization verification component interrupts the operating system to load the program, and the authorization verification component allows the operating system to continue loading the program after the authorization verification is passed. . The token includes an anonymous token and a non-anonymous token. The anonymous token is used for a public computer and the non-anonymous token is used for a personal computer. This authorization verification contains One of a permanent authorization verification, a lease authorization verification, and a trial authorization verification. When the authorization verification is the lease authorization verification or the trial authorization verification, the authorization verification component cooperates with the remote server to perform the authorization verification. When the authorization is verified as the permanent authorization verification and the remote server is unable to connect, the authorization verification component cooperates with the operating system to perform the authorization verification. The method further includes the following steps: when the anonymous token is checked and the program is closed, the program's data is restored to a preset value. When the non-anonymous token is checked and the program is closed, the program's data remains in its original state.

5. A device for authorizing a program, the program comprising a header, the device comprising a storage device, a file system, an operating system, and an authorization verification component. The operating system receives an activation program command and starts the program, and stores the header in the storage device for the operating system to read the header. The authorization verification component interrupts the operating system to load the program into a random access memory and cooperates with the operating system or a remote server to perform an authorization verification. When the authorization verification is passed, the authorization verification component allows the program to continue to load the random access memory for execution.

6. The device of embodiment 5, wherein the device further comprises a driver, the authorization verification component transmitting a first control message, a second control message, and a third control after being notified of the authorization verification. One of the messages to control one of the storage device, the file system, and the driver to allow the program to be stored from the remote server to the storage device, and the program is The storage device is stored in the file system, and the program is loaded from the file system into the random access memory by the operating system. When the authorization verification fails, the operating system reads a corrupted file to end the program, or makes the operating system unable to read the program and causes the program to make an error to end the program. The method of authorization verification includes one of a permanent authorization verification, a lease authorization verification, and a trial authorization verification. When the authorization is verified as the permanent authorization verification, the program is allowed to be unlimited Period use. When the authorization is verified as the lease authorization verification, the program is allowed to be used at a specific time interval. When the authorization is verified as the trial authorization verification, the program is stopped when the trial time expires. The authorization verification further includes a network authorization or a telephone authorization, and the network authorization method is to perform authorization verification by using a verification first authorization code, where the first authorization code includes a person privacy related information, and the personal privacy related information includes The identity card number, birthday, or any combination thereof, the way the phone is authorized is to use a phone number for authorization verification, when the phone authorization is verified, the phone number is used to obtain a second authorization code, the second authorization The code is used to authenticate the authorization authorized by the phone.

7. A method of authorizing a program comprising the steps of: selecting a particular program. An authorization verification is performed by a local operating system itself or a remote server. When the authorization verification is passed, the operating system loads the specific program into a specific memory.

8. The method of embodiment 7, wherein the method further comprises: storing the particular program from a cloud host to a software host. Transfer the specific program from the software host to a regional network host. The method further comprises: interrupting execution of the program, and the authorization verification component allows the program to continue execution after the authorization verification is passed. The authorization verification verifies the personal confidential information, which includes the identity card number, birthday, or any combination thereof. The particular memory system selects a memory path by a user.

9. A program transaction device comprising a first access element, a second access element, and an authorization verification element. The first access element accesses a remote library, and the remote library includes a plurality of programs. The second access element is accessed by a local operating system to select a particular program from the plurality of programs. The authorization verification component cooperates with the local operating system itself or a remote server to perform an authorization verification, and when the authorization verification is passed, the specific program is executed.

10. The device of embodiment 9, wherein the first access element is an agent A server hard disk or a cloud hard disk, the second access element is a dynamic random access memory (RAM). The authorization verification component interrupts the local operating system to load the program into the RAM for execution. After the authorization verification is passed, the authorization verification component allows the local operating system to continue loading the program into the RAM for execution. When the program transaction device is a software host, the remote server is a cloud host, and the authorization verification is performed on the cloud host, and the program is accessed at the software host. When the program transaction device is a software host, and the remote server cannot be connected, and the remote server is a cloud host, the authorization verification is performed on the software host, and the program is accessed at the computer host. When the program transaction device is a computer host, the remote server is the software host, and the authorization verification is performed on the software host, and the program is accessed at the computer host. When the authorization verification is the lease authorization verification or the trial authorization verification, the authorization verification component cooperates with the remote server to perform the authorization verification. When the authorization is verified as the permanent authorization verification and the remote server is unable to connect, the authorization verification component cooperates with the operating system to perform the authorization verification. When the authorization verification fails, the operating system reads a corrupted file until the authorization verification passes, the authorization verification component allows the operating system to load the specific program into the first access element or the second storage Take the component. The authorization verification includes one of a permanent authorization verification, a lease authorization verification, and a trial authorization verification. When the authorization is verified as the permanent authorization verification, the program is allowed to be used indefinitely. When the authorization is verified as the lease authorization verification, the program is allowed to be used at a specific time interval. When the authorization is verified as the trial authorization verification, the program is stopped when the trial time expires. The authorization verification further includes a network authorization or a telephone authorization, and the network authorization method is to perform authorization verification by using a verification first authorization code, where the first authorization code includes a person privacy related information, and the personal privacy related information includes The identity card number, birthday, or any combination thereof, the way the phone is authorized is to use a phone number for authorization verification, when the phone authorization is verified, the phone number is used to obtain a second authorization code, the second authorization The code is used to authenticate the authorization authorized by the phone.

11. A device for authorizing a program, the device comprising a host and a mobile device. The host includes an operating system and a driver. The mobile device includes the program and a firmware, the firmware includes an authorization verification component, wherein when the mobile device is coupled to the host, the firmware interrupts transmission of the program from the mobile device to the host, and the driver Interrupting the program is performed by the operating system loading a random access memory, the authorization verification component being activated to enable the operating system to cooperate with the firmware to perform an authorization verification via the driver, when the authorization verification is passed Thereafter, the body allows the program to be transferred from the mobile device to the host, and the driver allows the program to be loaded into the random access memory by the operating system.

12. A method of authorizing a program in a program transaction device, the program transaction device comprising a host and a mobile device, the method comprising the steps of: coupling the mobile device to the host. A device in the mobile device interrupts the transfer of the program from the mobile device to the host, and a driver in the host interrupts the program to load a random access in the host by a working system in the host Memory execution. An authorization verification component of the mobile device is activated to cause the operating system to cooperate with the firmware to perform an authorization verification via the driver. When the authorization is verified, the body allows the program to be transferred from the mobile device to the host, and the driver allows the program to be loaded by the operating system to load the random access memory.

In the above, the description and the embodiments of the present invention have been disclosed, and are not intended to limit the present invention, and those skilled in the art can make various changes without departing from the spirit and scope of the present invention. And modifications, which still fall within the scope of the present invention.

Claims (12)

A method for authorizing an application, the application is stored in a storage device or a remote server and includes a plurality of executable files, the plurality of executable files including a first execution file and a second execution file, the first execution The file includes a first file header, the second executable file includes a second file header, the method includes the steps of: causing an operating system to receive an application launch command and launching the application; causing the operating system to Storing a first file header in the storage device to read the first file header; causing an authorization verification component to transmit a control message to a driver to process a file system associated with the operating system; The component interrupts the operating system loading the first executable file into a random access memory for execution; causing the authorization verification component to cooperate with the operating system or the remote server to perform an authorization verification; when the first After the execution file is verified by the authorization, the authorization verification component notifies the driver by using the control message, so that the driver allows the first executable file to be from the file. Loading into the random access memory; and when the second executable is used, the operating system reads the second archive header and the verification component and the operating system or the remote servo The device cooperates to perform another authorization verification. The method of claim 1, further comprising the step of: when the authorization verification fails, the operating system reads a corrupted file to end the application, or makes the operating system unable to read the The application causes the application to make an error to end the application; After the second executable file is verified by the other authorization, the authorization verification component allows the second execution file to be loaded into the random access memory for execution. A method of authorizing an application, comprising the steps of: causing an operating system to receive a program launch command and launching the application; prior to loading the application system, an authorization verification component and the operating system itself or a remote server cooperates to perform an authorization verification; causes the authorization verification component to transmit a control message to a driver to process a file system associated with the operating system; causing the authorization verification component to interrupt the operating system to the application Loading into a random access memory for execution; and when the authorization verification is passed, causing the operating system or a storage device to obtain a token, and causing the authorization verification component to notify the driver by using the control message, thereby enabling The driver allows the application to execute from the file system loaded into the random access memory. The method of claim 3, wherein: the authorization verification component interrupts the operating system to load the application, and the authorization verification component allows the operating system to continue loading the application after the authorization verification is passed The token includes an anonymous token and a non-anonymous token; the anonymous token is for a public computer, the non-anonymous token is for a personal computer; the authorization verification includes a permanent authorization verification, a rental authorization verification, And one of the trial authorization verifications; when the authorization verification is the lease authorization verification or the trial authorization verification, the authorization verification component cooperates with the remote server to perform the authorization verification; When the authorization verification is the permanent authorization verification, and the remote server is unable to connect, the authorization verification component cooperates with the operating system to perform the authorization verification; and the method further comprises the following steps: when the anonymous token is When the verification passes and the application is closed, the application's data is restored to a preset value; and when the non-anonymous token is verified and the application is closed, the application's data remains in its original state. A device for authorizing an application, the application comprising a file header, the device comprising: a storage device; a file system disposed on the storage device; an operating system receiving an application launching command and launching the application And storing the file header in the storage device for the operating system to read the file header; and an authorization verification component, notifying a driver to process the file system, interrupting the operating system, and loading the application Performing in a random access memory and cooperating with the operating system or a remote server to perform an authorization verification, wherein when the authorization verification is passed, the authorization verification component notifies the driver, and the driver is enabled The program allows the application to continue to load from the file system into the random access memory for execution. The device of claim 5, wherein: the authorization verification component transmits one of a first control message, a second control message, and a third control message after being notified of the authorization verification. Separately controlling one of the storage device, the file system, and the driver to allow the application to be remote from the remote The server stores the storage device, stores the application from the storage device to the file system through the driver, and loads the application from the file system into the random access memory by the operating system; When the authorization verification fails, the operating system reads a corrupted file to end the application, or makes the operating system unable to read the application and causes the application to generate an error to end the application; the authorization verification The method includes one of a permanent authorization verification, a lease authorization verification, and a trial authorization verification; when the authorization verification is the permanent authorization verification, the application is allowed to be used indefinitely; when the authorization is verified as the lease authorization During verification, the application is allowed to be used at a specific time interval; when the authorization verification is the trial authorization verification, the application is stopped when a trial time expires; and the authorization verification further includes a network Authorization or a telephone authorization, the way to authorize the network is to use the verification first authorization code for authorization verification. The first authorization code includes a person privacy related message, where the personal privacy related message includes an identity card number, a birthday, or any combination thereof, and the method of authorizing the phone uses a phone number for authorization verification, when the phone authorization is verified. The telephone number is used to obtain a second authorization code, which is used to verify the authorization authorized by the telephone. A method for authorizing a program, comprising the steps of: selecting a first specific program; performing an authorization verification by a local operating system itself or a remote server; notifying a second specific program to process the related local operating system a file system; Interrupting the local operating system itself to load the first specific program into a random access memory; and, when the authorization verification is passed, notifying the second specific program, so that the second specific program allows the operating system The first specific program is loaded from the file system into a particular memory. The method of claim 7, wherein the method further comprises: storing the first specific program from a cloud host to a software host; and transmitting the first specific program from the software host to an area a network host; the method further comprises: interrupting execution of the first specific program, the second specific program allowing the first specific program to continue after the authorization verification is passed; the first specific program is an application; The specific program is a driver; the authorization verification is to verify personal confidential information, which includes an identity card number, a birthday, or any combination thereof; and the specific memory system selects a memory path by a user. A program transaction device comprising: a first access component, accessing a remote library, the remote library comprising a plurality of programs; and a second access component for access by a local operating system to Selecting a specific program from the program; and an authorization verification component that cooperates with the local operating system itself or a remote server to perform an authorization verification, the authorization verification component notifying a driver, interrupting the local operating system The program is loaded into a random access memory for execution, and when the authorization verification is passed, the authorization verification component notifies the driver, and the driver allows the specific program to be executed. The device of claim 9, wherein the first access component is a proxy server hard disk or a cloud hard disk, and the second access component is a dynamic random access memory (RAM). The authorization verification component interrupts the local operating system to load the specific program into the RAM, and after the authorization verification is passed, the authorization verification component allows the local operating system to continue loading the specific program into the RAM; When the program transaction device is a software host, the remote server is a cloud host, and the authorization verification is performed on the cloud host, and the specific program is accessed by the software host; when the program transaction device is a software host, and When the remote server is unable to connect, and the remote server is a cloud host, the authorization verification is performed on the software host, and the specific program is accessed on a computer host; when the program transaction device is a computer host The remote server is the software host, the authorization verification is performed on the software host, and the specific program is accessed on the computer host; when the authorization verification is a lease authorization verification When the authorization verification is performed, the authorization verification component cooperates with the remote server to perform the authorization verification; when the authorization verification is a permanent authorization verification, and the remote server cannot be connected, the authorization verification component and the The operating system cooperates to perform the authorization verification; when the authorization verification fails, the operating system reads a corrupted file until the authorization verification passes, the authorization verification component allows the operating system to load the specific program into the first An access element or the second access element; the authorization verification includes a permanent authorization verification, a lease authorization verification, and a trial authorization One of the verifications; when the authorization is verified as the permanent authorization verification, the specific program is allowed to be used indefinitely; when the authorization verification is the rental authorization verification, the specific program is allowed to be used at a specific time interval; When the authorization verification is the trial authorization verification, the specific program is stopped when a trial time expires; and the authorization verification further includes a network authorization or a telephone authorization, and the network authorization method uses the verification one. The first authorization code is used for authorization verification. The first authorization code includes a person privacy related message, where the personal privacy related message includes an identity card number, a birthday, or any combination thereof, and the method of authorizing the phone is authorized by using a phone number. It is verified that when the telephone authorization is verified, the telephone number is used to obtain a second authorization code, which is used for authorization verification by the telephone authorization. An apparatus for authorizing an application, comprising: a host, comprising an operating system, a random access memory, and a driver; a mobile device coupled to the host and including a firmware, including an authorization verification The component performs an authorization verification, wherein when the mobile device is connected to the host, the body interrupts the application from the mobile device to the host, and the driver interrupts the program by loading the operating system The random access memory is executed, and the authorization verification component is activated to enable the operating system to cooperate with the firmware to perform an authorization verification via the driver, and when the authorization verification fails, the driver causes the operating system to read Take a corrupted file to end the application, or make the operating system unable to read the application and cause the application to make an error to end the application. When the authorization is verified, the entity allows the application Transferred from the mobile device to the host, and the driver allows the application to load the random access memory by the operating system . A method for authorizing an application in a program transaction device, the program transaction device comprising a host and a mobile device, the method comprising the steps of: coupling the mobile device with the host; and interrupting a body in the mobile device Transmitting the application from the mobile device to the host, and a driver in the host interrupts the application execution by loading a random access memory in the host by a working system in the host; the mobile device An authorization verification component is activated to enable the operating system to cooperate with the firmware to perform an authorization verification via the driver; when the authorization verification fails, the driver causes the operating system to read a corrupted file. Ending the application, or causing the operating system to fail to read the application, causing the application to make an error to end the application; and when the authorization is verified, the entity allows the application to be removed from the mobile device Transferred to the host, and the driver allows the application to be loaded by the operating system to load the random access memory.