WO2016184197A1 - 授权信息的调整方法、装置和计算机存储介质 - Google Patents
授权信息的调整方法、装置和计算机存储介质 Download PDFInfo
- Publication number
- WO2016184197A1 WO2016184197A1 PCT/CN2016/074073 CN2016074073W WO2016184197A1 WO 2016184197 A1 WO2016184197 A1 WO 2016184197A1 CN 2016074073 W CN2016074073 W CN 2016074073W WO 2016184197 A1 WO2016184197 A1 WO 2016184197A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- authorization
- network element
- file
- base station
- identifier
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, and a computer storage medium for adjusting authorization information.
- each base station has a corresponding license (authorization, license) file for storing the authorization information of the base station.
- the physical identifier of the base station is stored in the license file, and is used to indicate the correspondence between the license file and the base station.
- an operator usually purchases a total amount of resources for a plurality of base stations, and then allocates the resources to each base station.
- the resources allocated to each base station at the same time can also be adjusted according to the operation of the base station.
- the operator applies to the vendor maintenance personnel for capacity adjustment and gives the adjusted authorization value of each base station.
- the maintenance personnel generates a new license file for the base station to be adjusted according to the requirements, and submits the new license file to the operator.
- the carrier sends the new license file to the base station, and the base station loads the new license file. Adjustment of the authorization information of the base station.
- embodiments of the present invention are expected to provide a method, an apparatus, and a computer storage medium for adjusting authorization information, and it is desirable to reduce an abnormal operation of the device.
- the present invention provides a method for adjusting authorization information, including:
- the authorization invalidation process includes:
- the authorization adjustment verification information includes: a physical identifier of the network element, the current authorization file identifier, and a revoke code; the revoke code is generated according to the physical identifier of the network element and the current authorization file identifier. .
- the method further includes:
- the invention also provides a method for adjusting authorization information, comprising:
- the authorization adjustment verification information of the to-be-adjusted network element includes: a physical identifier of the network element to be adjusted, a current authorization file identifier of the network element to be adjusted, and a revoke code; the revoke code is according to the to-be-adjusted network element.
- the physical identifier and the current authorized file identifier of the to-be-adjusted network element are generated.
- verifying the authorization adjustment verification information including:
- the verification is passed.
- the invention also provides a method for adjusting authorization information, which comprises:
- the authorization adjustment verification information of the network element to be adjusted includes: a physical identifier of the network element, a current authorization file identifier, and a revoke code; where the revoke code is based on the physical identifier of the network element and the current authorization The file identifier is generated.
- the invention also provides an apparatus for adjusting authorization information, comprising:
- a receiving unit configured to receive an authorization invalid operation instruction
- the processing unit is configured to perform authorization failure processing on the current authorization file according to the authorization invalidation operation instruction
- the sending unit is configured to generate and send an authorization adjustment verification information.
- the processing unit is configured to set an expiration date for the current authorization file.
- the authorization adjustment verification information includes: a physical identifier of the network element, the current authorization file identifier, and a revoke code; the revoke code is generated according to the physical identifier of the network element and the current authorization file identifier. .
- processing unit is further configured to:
- the invention also provides an apparatus for adjusting authorization information, comprising:
- the receiving unit is configured to receive authorization adjustment verification information of the network element to be adjusted,
- a verification unit configured to verify the authorization adjustment verification information
- Generating a unit configured to generate a new authorization text for the to-be-adjusted network element when the verification is passed Pieces.
- the authorization adjustment verification information of the to-be-adjusted network element includes: a physical identifier of the network element to be adjusted, a current authorization file identifier of the network element to be adjusted, and a revoke code; the revoke code is according to the to-be-adjusted network element.
- the physical identifier and the current authorized file identifier of the to-be-adjusted network element are generated.
- the verification unit includes:
- the parsing module is configured to parse the physical identifier of the network element and the identifier of the authorization file from the revoke code;
- the comparing module is configured to: when the parsed physical identifier of the network element is consistent with the physical identifier of the to-be-adjusted network element, and the identifier of the parsed authorization file is consistent with the current authorized file identifier of the to-be-adjusted network element, the verification succeeds.
- the embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute at least one of the foregoing adjustment methods of the authorization information.
- the solution of the embodiment of the present invention is that the network element performs the invalidation operation on the current authorization file, and after the file application server verifies the verification of the authorization information of the network element, The NE generates a new authorization file, which allows the NE to adjust the authorization information. That is to say, the solution of the embodiment of the present invention can ensure that the current authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby ensuring the solution of the embodiment of the present invention.
- the normal operation of the device is to ensure that the current authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby ensuring the solution of the embodiment of the present invention.
- FIG. 1 is a flowchart of a method for adjusting authorization information according to Embodiment 1 of the present invention
- FIG. 2 is a flowchart of a method for adjusting authorization information according to Embodiment 2 of the present invention
- FIG. 3 is a flowchart of a method for adjusting authorization information according to Embodiment 3 of the present invention.
- FIG. 4 is a flowchart of a method for adjusting authorization information according to Embodiment 4 of the present invention.
- FIG. 5 is a flowchart of a method for adjusting authorization information according to Embodiment 5 of the present invention.
- FIG. 6 is a flowchart of a method for adjusting authorization information according to Embodiment 6 of the present invention.
- FIG. 7 is a flowchart of a method for adjusting authorization information according to Embodiment 7 of the present invention.
- Embodiment 8 is a flowchart of a method for adjusting authorization information according to Embodiment 8 of the present invention.
- FIG. 9 is a schematic diagram of an apparatus for adjusting authorization information according to Embodiment 9 of the present invention.
- FIG. 10 is a schematic diagram of an apparatus for adjusting authorization information according to Embodiment 10 of the present invention.
- the method for adjusting the authorization information in the first embodiment of the present invention may be performed by a network element (such as a base station), including:
- Step 11 Receive an authorization invalid operation instruction.
- Each network element corresponds to an authorization file
- the authorization file has a unique identifier, where the identifier may be a file serial number.
- the operator allocates resources for each network element and loads the authorization file to each network element.
- the authorization file currently owned by the network element is referred to as the current authorization file.
- the operator finds that the existing allocated resources of the network element are not suitable, the resources allocated between the network elements need to be adjusted, that is, the authorization information of each network element needs to be adjusted.
- the operator proposes an authorization information adjustment request to the file application server, and the physical identification (ID) of the network element (hereinafter referred to as the to-be-adjusted network element) that needs to adjust the authorization information may be included in the requirement to request each The new authorization file for the network element.
- ID physical identification
- the file application server may send an authorization information adjustment instruction to the operation and maintenance center, where the authorization information adjustment instruction includes the physical identifier of the network element to be adjusted.
- the operation and maintenance center sends an authorization invalidation operation instruction to the network element according to the authorization information adjustment instruction, and is used to instruct the network element to perform authorization failure processing.
- Step 12 Authorize the current authorization file to be invalidated according to the authorization invalid operation instruction Reason.
- the network element after receiving the authorization invalidation operation instruction of the operation and maintenance center, the network element first searches whether the current authorization file is stored by itself.
- the operation failure confirmation response message is sent to the operation and maintenance center, and the physical identifier of the network element is included in the message.
- the network element may establish a correspondence between the file serial number and the expiration date in the configuration file, and set an expiration date for the current authorization file, for example, the expiration date of the current authorization file may be set to 60 days of the current authorization file. . When the 60-day validity period expires, the current authorization file is invalid. If a new authorization file is loaded before the expiration of the 60-day period, the setting of the usage period can be released.
- Step 13 Generate and send an authorization adjustment verification information.
- the authorization adjustment verification information includes: a physical identifier of the network element, the current authorization file identifier, and a disable code; the revoke code is based on the physical identifier of the network element and the The current authorization file identifier is generated.
- the revoke code is obtained as follows.
- the first method is that the revoke code of the current authorization file is obtained by the file application server by encrypting the physical identifier of the network element to be adjusted and its corresponding current authorization file identifier, and is carried in the current authorization file.
- the network element to be adjusted can obtain the revoke code of the current authorization file by parsing the current authorization file.
- the second method is: after the network element to be adjusted receives the authorization invalidation operation instruction of the operation and maintenance center, the physical identifier of the network element to be adjusted and the current authorization file identifier are encrypted.
- the network element may read the network element identifier field of the current authorization file and the file identifier field of the current authorization file to obtain the physical identifier of the network element and the current Authorization file identifier. Then, reading the invalidity of the current authorization file
- the code field determines whether the current authorization file itself includes a revoke code of the current authorization file.
- the information in the revoke code field is the first preset value
- the current authorization file itself includes the revoke code of the current authorization file
- the information in the revoke code field is the second preset value Indicates that the current authorization file itself does not include the revoke code of the current authorization file.
- the first preset value may be 0, and the second preset value may be 1 or the like.
- the current authorization file itself includes a revoke code of the current authorization file
- the current authorization file itself does not include a revoke code of the current authorization file And generating, according to the physical identifier of the network element and the current authorization file identifier, a revoke code of the current authorization file.
- the authorization adjustment verification information may be generated by using the authorization adjustment verification information, and the authorization invalidation operation response message is sent to the operation and maintenance center.
- the solution of the embodiment of the present invention is that the network element performs the invalidation operation on the current authorization file, and the verification of the verification information of the authorization adjustment of the network element by the file application server is passed. After that, a new authorization file is generated for the network element, and the authorization information of the network element is allowed to be adjusted. That is to say, the solution of the embodiment of the present invention can ensure that the current authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby ensuring the solution of the embodiment of the present invention. The normal operation of the device.
- the method for adjusting authorization information in the second embodiment of the present invention may be performed by a file application server, including:
- Step 21 Receive authorization adjustment verification information of the network element to be adjusted.
- the file application server sends an authorization information adjustment instruction to the operation and maintenance center, where the authorization information adjustment instruction includes the physical identifier of the network element to be adjusted.
- the physical identifier of the network element to be adjusted may be included in the command, and may include more than two physical identifiers of the network element to be adjusted.
- the operation and maintenance center obtains the authorization adjustment verification information of the NE to be adjusted, and sends the authorization adjustment verification information of the NE to be sent to the file application server. At this time, the file application server receives the authorization adjustment verification information of the network element sent by the operation and maintenance center.
- the authorization adjustment verification information of the network element to be adjusted includes: a physical identifier of the network element to be adjusted, a current authorization file identifier of the network element to be adjusted, and a revoke code; the revoke code is based on the physical identifier of the network element to be adjusted. And the current authorized file identifier of the network element to be adjusted is generated.
- Step 22 Verify the authorization adjustment verification information.
- the file application server may first parse the network element physical identifier and the authorization file identifier from the revoke code.
- the physical identifier of the network element to be adjusted and the identifier of the parsed authorization file are compared with the current authorized file identifier of the to-be-adjusted network element.
- the verification is passed. Otherwise the verification does not pass.
- Step 23 When the verification is passed, generate a new authorization file for the network element to be adjusted.
- the physical identifier of the network element to be adjusted and the current authorization file identifier in the authorization adjustment verification information, and the revoke code of the current authorization file are used.
- the information is stored in a corresponding field, and a new authorization file of the to-be-adjusted network element is generated according to the information in each field.
- the physical identifier of the network element to be adjusted is stored in the network element identification field
- the current authorization file identifier is stored in the file identification field
- the revoke code of the current authorization file is stored in the revoke code field, and then generated according to the information in each field.
- the solution of the embodiment of the present invention is that the network element performs the invalidation operation on the current authorization file, and the verification of the verification information of the authorization adjustment of the network element by the file application server is passed. After that, a new authorization file is generated for the network element, and the authorization information of the network element is allowed to be adjusted. That is, the solution of the embodiment of the present invention is utilized. It can be ensured that the original authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby ensuring the normal operation of the device by using the solution of the embodiment of the present invention.
- the method for adjusting the authorization information in the third embodiment of the present invention may be performed by an Operation and Maintenance Center (OMC), including:
- Step 31 Send an authorization invalid operation instruction to the network element to be adjusted.
- the OMC receives the authorization information adjustment instruction sent by the file application server, and includes the physical identifier of the network element to be adjusted in the authorization information adjustment instruction.
- the operation and maintenance center parses the instruction and obtains the physical identifier of the network element to be adjusted. And the OMC sends an authorization invalidation operation instruction to the to-be-adjusted network element according to the physical identifier of the to-be-adjusted network element.
- Step 32 Receive authorization adjustment verification information sent by the network element to be adjusted, where the authorization verification information is used by the file application server to generate a new authorization file for the to-be-adjusted network element.
- the OMC receives the authorization invalidation operation response message sent by the to-be-adjusted network element, and includes the authorization adjustment verification information of the to-be-adjusted network element in the authorization invalidation operation response message of the to-be-adjusted network element.
- the authorization adjustment verification information of the network element to be adjusted includes: a physical identifier of the network element, a current authorization file identifier, and a revoke code; where the revoke code is generated according to the physical identifier of the network element and the current authorization file identifier.
- the authorization adjustment verification information of the network element to be adjusted may be stored in the specified file, and then the specified file is sent to the file application server, thereby The authorization adjustment verification information of the network element to be adjusted is sent to the file application server.
- the specified file may be any form of file, such as a text file.
- the solution of the embodiment of the present invention is that the network element performs the invalidation operation on the current authorization file, and the verification of the verification information of the authorization adjustment of the network element by the file application server is passed. After that, a corresponding new authorization file is generated for the network element. In turn, the adjustment of the authorization information for the network element is allowed. That is to say, the solution of the embodiment of the present invention can ensure that the current authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby ensuring the solution of the embodiment of the present invention. The normal operation of the device.
- the implementation process of the method for adjusting the authorization information in the embodiment of the present invention is described in detail below with reference to the fourth embodiment to the seventh embodiment.
- the RRC user number of the base stations A, B, and C is adjusted as an example, wherein the agreed RRC user total authorization amount is 1000.
- the RRC user number of the base station A is adjusted as an example for description.
- the method for adjusting authorization information according to Embodiment 4 of the present invention includes:
- Step 41 The file application server generates a current authorization file for the base station A according to the initial requirement of the operator.
- Base station A 300.
- the operator sends the request to the file application server, and the file application server generates the current authorization file A1 for the base station A according to the requirement.
- the physical identifier ID1 of the base station A is stored in the network element identifier field of the current authorization file A1
- the serial number NO1 of the current authorization file A1 is stored in the file identification field
- the invalidation code Disable1 of the current authorization file is stored in the invalidation code field, where
- the revoke code is obtained by encrypting the physical identifier ID1 of the base station A and the sequence number NO1 of the current authorization file A1.
- the encryption method can be implemented by using any encryption method in the prior art.
- Step 42 The file application server provides the current authorization file A1 to the operator.
- Step 43 The operator loads the current authorization file A1 to the base station A through the OMC, and monitors the authorization result of the base station.
- Step 44 After a period of operation, the operator proposes an authorization information adjustment request to the file application server, and requires adjustment of the authorization information of the base station A.
- the adjusted distribution method As follows: Base station A: 500.
- Step 45 The file application server adjusts the requirement according to the authorization information of the operator, and sends an authorization information adjustment instruction to the OMC, where the physical information of the base station A is included in the authorization information adjustment instruction.
- Step 47 After receiving the authorization invalid operation instruction, the base station A performs a failure operation on the current authorization file.
- Base station A can first determine if it has stored a current authorization file. If not, the authorization invalidation operation failure response message is sent to the OMC, and the physical identifier of the base station A is carried in the message, and the entire process ends. If yes, the base station A sets the validity period of the current authorization file A1 for 60 days. In addition, the base station A also monitors the expiration date of the current authorization file A1.
- Step 48 Generate authorization adjustment verification information.
- the base station A obtains the physical identifier ID1 of the base station A, the serial number NO1 of the current authorization file, and the invalidation code Disable1 by reading the network element identification field, the file identification field, and the invalidation code field of the current authorization file A1, respectively, and obtains according to the obtained
- the physical identification ID of the base station A, the serial number NO1 of the current authorization file, and the invalidation code Disable1 generate an authorization invalidation operation response message.
- Step 49 The base station A sends an authorization invalidation operation response message to the OMC.
- Step 410 The base station A marks the current authorization file A1 to prevent the current authorization file A1 from being loaded again, thereby further ensuring the reliability of authorization for each base station.
- Step 411 The OMC sends an authorization invalidation operation response message of the base station A to the file application server.
- Step 412 The file application server verifies the authorization adjustment verification information of the base station A.
- the file application server parses the failure code Disable1 of the base station A, and obtains the physical standard of the base station A. ID2, the current serial number of the authorization file A1 is NO2. By comparison, ID1 is consistent with ID2, and NO1 is consistent with NO2, so the verification of base station A is passed. If the verification fails, the process ends.
- Step 413 The file application server generates a new authorization file for the base station A.
- Step 414 The file application server sends the new authorization file of the base station A to the operator.
- Step 415 The operator sends a new authorization file to the base station A through the OMC, and the base station A loads the new authorization file.
- the base station A if the base station A receives a new authorization file before the expiration of the validity period of the current authorization file, the base station directly loads the new authorization file. If the base station A does not receive the new authorization file before the expiration of the validity period of the current authorization file, the base station A will load the preset authorization file to ensure the operation of the device.
- the preset authorization file is used to minimize the amount of authorization between stations. For example, in this embodiment, the RRC user number is allocated by the preset authorization file as follows: base station A: 100.
- the solution of the embodiment of the present invention can ensure that the original authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby utilizing the solution of the embodiment of the present invention. It ensures the normal operation of the equipment and prevents the leakage of the license.
- the method for adjusting authorization information according to Embodiment 5 of the present invention includes:
- Step 51 The file application server generates a current authorization file for the base station A, the base station B, and the base station C according to the initial requirements of the operator.
- Base station A 300; base station B: 400; base station C: 300.
- the operator sends the request to the file application server, and the file application server according to the demand
- the current authorization files A1, B1, and C1 are generated for the base station A, the base station B, and the base station C, respectively.
- the physical identifier ID1 of the base station A is stored in the network element identification field of the file
- the serial number NO1 of the current authorization file A1 is stored in the file identification field
- the current authorization file is stored in the invalidation code field.
- the revoke code Disable1 wherein the revoke code is obtained by encrypting the physical identifier ID1 of the base station A and the sequence number NO1 of the current authorization file A1.
- the encryption method can be implemented by using any encryption method in the prior art.
- Step 52 The file application server provides the current authorization file A1, B1, and C1 to the operator.
- Step 53 The operator loads the current authorization files A1, B1, and C1 into the base station A, the base station B, and the base station C through the OMC, and monitors the authorization results of the base stations.
- Step 54 After the running for a period of time, the operator proposes an authorization information adjustment request to the file application server, and requires adjustment of the authorization information of the base station A, the base station B, and the base station C.
- the adjusted inter-station allocation mode is as follows: base station A: 500; base station B: 300; base station C: 200.
- Step 55 The file application server adjusts the requirement according to the authorization information of the operator, and sends an authorization information adjustment instruction to the OMC, where the authorization information adjustment instruction includes the physical identifiers of the base station A, the base station B, and the base station C.
- Step 56 The OMC sends an authorization invalidation operation instruction to the base station A, the base station B, and the base station C according to the physical identifiers of the base station A, the base station B, and the base station C.
- Step 57 After receiving the authorization invalid operation instruction, the base station A, the base station B, and the base station C respectively perform invalidation operations on the respective current authorization files.
- base station A can first determine whether it has a current authorization file stored therein. If not, the authorization invalidation operation failure response message is sent to the OMC, and the physical identifier of the base station A is carried in the message, and the entire process ends.
- the base station A sets the validity period of the current authorization file A1 for 60 days. In addition, the base station A also monitors the expiration date of the current authorization file A1.
- the base station B and the base station C also succeed in the manner of the base station A. Authorized invalidation operation.
- Step 58 Generate authorization adjustment verification information.
- base station A first obtains authorization adjustment verification information.
- the base station A obtains the physical identifier ID1 of the base station A, the serial number NO1 of the current authorization file, and the invalidation code Disable1 by reading the network element identification field, the file identification field, and the invalidation code field of the current authorization file A1, respectively, and obtains according to the obtained
- the physical identification ID of the base station A, the serial number NO1 of the current authorization file, and the invalidation code Disable1 generate an authorization invalidation operation response message.
- the base stations B and C also successfully generate the authorization adjustment verification information according to the manner of the base station A.
- Step 59 The base station A, the base station B, and the base station C respectively send an authorization invalidation operation response message to the OMC.
- Step 510 The base station A, the base station B, and the base station C respectively mark the current authorization file A1, the current authorization file B1, and the current authorization file C1, respectively, to prevent the current authorization file A1, the current authorization file B1, and the current authorization file C1 from being again It is loaded to further ensure the reliability of authorization for each base station.
- Step 511 The OMC sends an authorization invalidation operation response message of the base station A, the base station B, and the base station C to the file application server.
- Step 512 The file application server verifies the authorization adjustment verification information of the base station A, the base station B, and the base station C, respectively.
- the file application server resolves the failure code Disable1 of the base station A, obtains the physical identification ID2 of the base station A, and the standard serial number of the current authorization file A1 is NO2. By comparison, ID1 is consistent with ID2, and NO1 is consistent with NO2, so the verification of base station A is passed.
- Step 513 The file application server generates a new authorization file for the base station A, the base station B, and the base station C, respectively.
- Step 514 The file application server sends a new authorization file of the base station A, the base station B, and the base station C to the operator.
- Step 515 The operator sends a new authorization file to the base station A, the base station B, and the base station C through the OMC, and the base station A, the base station B, and the base station C respectively load respective new authorization files.
- the base station A, the base station B, and the base station C receive their respective new authorization files before the expiration of the validity period of the respective current authorization file, the base station directly loads. Their respective new authorization files. If the base station A, the base station B, and the base station C have not received the new authorization file before the expiration of the validity period of the respective current authorization file, the base station A, the base station B, and the base station C will load the respective default authorization files. To ensure the operation of the device.
- the preset authorization file is used to minimize the amount of authorization between stations. For example, in this embodiment, by means of the preset authorization file, the inter-station allocation manner of the RRC user number is as follows: base station A: 100; base station B: 100; base station C: 100.
- base station A Taking base station A as an example, if base station A receives a new authorization file before the expiration date of the current authorization file A1 expires, base station A loads the new authorization file. If not received, base station A loads its stored default authorization file.
- the solution of the embodiment of the present invention can ensure that the original authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby utilizing the solution of the embodiment of the present invention. It ensures the normal operation of the equipment and prevents the leakage of the license.
- the method for adjusting authorization information according to Embodiment 5 of the present invention includes:
- Steps 61-66 in this embodiment, the description of steps 61-66 is the same as the description of steps 51-56 of the fourth embodiment.
- Step 67 After receiving the authorization invalid operation instruction, the base station A, the base station B, and the base station C respectively perform invalidation operations on the respective current authorization files.
- base station A can first determine whether it has a current authorization file stored therein. If not, the authorization invalidation operation failure response message is sent to the OMC, and the physical identifier of the base station A is carried in the message, and the entire process ends. If yes, the base station A sets the validity period of the current authorization file A1 for 60 days. In addition, the base station A also monitors the expiration date of the current authorization file A1.
- the base station B and the base station C successfully perform the authorization invalidation operation according to the manner of the base station A.
- Step 68 Generate authorization adjustment verification information.
- the base station A obtains the physical identifier ID1 of the base station A, the serial number NO1 of the current authorization file, and the invalidation code Disable1 by reading the network element identification field, the file identification field, and the invalidation code field of the current authorization file A1, respectively.
- An authorization invalidation operation response message is generated according to the obtained physical identifier ID1 of the base station A, the serial number NO1 of the current authorization file, and the invalidation code Disable1.
- the base station B also successfully generates the authorization adjustment verification information according to the manner of the base station A.
- the base station C obtains the physical identifier ID5 of the base station C and the serial number NO5 of the current authorization file by reading the network element identification field and the file identification field of the current authorization file C1, and does not read the invalidation code field to obtain the Disable code, but is free. Obtained a Disable code Disable3.
- Step 69 The base station A, the base station B, and the base station C respectively send an authorization invalidation operation response message to the OMC.
- Step 610 The base station A, the base station B, and the base station C respectively mark the current authorization file A1, the current authorization file B1, and the current authorization file C1, respectively, to prevent the current authorization file A1, the current authorization file B1, and the current authorization file C1 from being again It is loaded to further ensure the reliability of authorization for each base station.
- Step 611 The OMC sends the base station A, the base station B, and the base station C to the file application server. Authorization invalidation operation response message.
- Step 612 The file application server verifies the authorization adjustment verification information of the base station A, the base station B, and the base station C, respectively.
- the file application server resolves the failure code Disable1 of the base station A, obtains the physical identification ID2 of the base station A, and the standard serial number of the current authorization file A1 is NO2. By comparison, ID1 is consistent with ID2, and NO1 is consistent with NO2, so the verification of base station A is passed.
- the verification of the base station B is also passed.
- the file application server parses the revoke code Disable3 of the base station C, obtains the physical identifier ID6 of the base station C, and the target serial number of the authorization file C1 is NO6. By comparison, ID5 is inconsistent with ID6, and NO5 is inconsistent with NO6. Therefore, the verification of base station C is not passed. Therefore, the file application server does not allow adjustment of the authorization information for the base stations A, B, and C.
- Step 613 The file application server sends a response message indicating that adjustment of the authorization information to the base stations A, B, and C is not allowed.
- the solution of the embodiment of the present invention can ensure that the original authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby utilizing the solution of the embodiment of the present invention. It ensures the normal operation of the equipment and prevents the leakage of the license.
- the method for adjusting authorization information according to Embodiment 6 of the present invention includes:
- Step 71 The file application server generates a current authorization file for the base station A, the base station B, and the base station C according to the initial requirement of the operator.
- Base station A 300; base station B: 400; base station C: 300.
- the operator sends the request to the file application server, and the file application server generates the current authorization files A1, B1, and C1 for the base station A, the base station B, and the base station C according to the requirement.
- Current grant For example, the right file A stores the physical identification ID1 of the base station A in the network element identification field of the file, and the serial number NO1 of the current authorization file A1 is stored in the file identification field.
- Step 72 The file application server provides the current authorization file A1, B1, and C1 to the operator.
- Step 73 The operator loads the current authorization files A1, B1, and C1 into the base station A, the base station B, and the base station C through the OMC, and monitors the authorization results of the base stations.
- Step 74 After the running for a period of time, the operator proposes an authorization information adjustment request to the file application server, and requires adjustment of the authorization information of the base station A, the base station B, and the base station C.
- the adjusted inter-station allocation mode is as follows: base station A: 500; base station B: 300; base station C: 200.
- Step 75 The file application server adjusts the requirement according to the authorization information of the operator, and sends an authorization information adjustment instruction to the OMC, where the authorization information adjustment instruction includes the physical identifiers of the base station A, the base station B, and the base station C.
- Step 76 The OMC sends an authorization invalidation operation instruction to the base station A, the base station B, and the base station C according to the physical identifiers of the base station A, the base station B, and the base station C.
- Step 77 After receiving the authorization invalid operation instruction, the base station A, the base station B, and the base station C respectively perform the invalidation operation on the respective current authorization files.
- base station A can first determine whether it has a current authorization file stored therein. If not, the authorization invalidation operation failure response message is sent to the OMC, and the physical identifier of the base station A is carried in the message, and the entire process ends. If yes, the base station A sets the validity period of the current authorization file A1 for 60 days. In addition, the base station A also monitors the expiration date of the current authorization file A1.
- the base station B and the base station C successfully perform the authorization invalidation operation according to the manner of the base station A.
- Step 78 Generate authorization adjustment verification information.
- the base station A obtains the physical identifier ID1 of the base station A and the current authorized file by reading the network element identification field and the file identification field of the current authorization file A1. Column number NO1.
- the base station generates a revoke code obtained by encrypting the physical identifier ID1 of the base station A and the sequence number NO1 of the current authorization file A1.
- the encryption method can be implemented by using any encryption method in the prior art.
- the base station A generates an authorization invalidation operation response message according to the obtained physical identifier ID1 of the base station A, the serial number NO1 of the current authorization file, and the invalidation code Disable1.
- the base station B and the base station C successfully generate the authorization adjustment verification information according to the manner of the base station A.
- Step 79 The base station A, the base station B, and the base station C respectively send an authorization invalidation operation response message to the OMC.
- Step 710 The base station A, the base station B, and the base station C respectively mark the current authorization file A1, the current authorization file B1, and the current authorization file C1, respectively, to prevent the current authorization file A1, the current authorization file B1, and the current authorization file C1 from being again It is loaded to further ensure the reliability of authorization for each base station.
- Step 711 The OMC sends an authorization invalidation operation response message of the base station A, the base station B, and the base station C to the file application server.
- Step 712 The file application server verifies the authorization adjustment verification information of the base station A, the base station B, and the base station C, respectively.
- the file application server parses the failure code Disable1 of the base station A, obtains the physical identification ID2 of the base station A, and the standard serial number of the current authorization file A1 is NO2. By comparison, ID1 is consistent with ID2, and NO1 is consistent with NO2, so the verification of base station A is passed.
- Step 713 The file application server generates a new authorization file for the base station A, the base station B, and the base station C, respectively.
- Step 714 The file application server respectively adds new authorizations of the base station A, the base station B, and the base station C. The file is sent to the operator.
- Step 715 The operator sends a new authorization file to the base station A, the base station B, and the base station C through the OMC, and the base station A, the base station B, and the base station C respectively load respective new authorization files.
- the base station A, the base station B, and the base station C receive their respective new authorization files before the expiration of the validity period of the respective current authorization file, the base station directly loads. Their respective new authorization files. If the base station A, the base station B, and the base station C have not received the new authorization file before the expiration of the validity period of the respective current authorization file, the base station A, the base station B, and the base station C will load the respective default authorization files. To ensure the operation of the device.
- the preset authorization file is used to minimize the amount of authorization between stations. For example, in this embodiment, by means of the preset authorization file, the inter-station allocation manner of the RRC user number is as follows: base station A: 100; base station B: 100; base station C: 100.
- base station A Taking base station A as an example, if base station A receives a new authorization file before the expiration date of the current authorization file A1 expires, base station A loads the new authorization file. If not received, base station A loads its stored default authorization file.
- the solution of the embodiment of the present invention can ensure that the original authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby utilizing the solution of the embodiment of the present invention. It ensures the normal operation of the equipment and prevents the leakage of the license.
- the method for adjusting authorization information according to Embodiment 7 of the present invention includes:
- Steps 81-86 in this embodiment, the description of steps 81-86 is the same as the description of steps 71-76 of embodiment 6.
- Step 87 After receiving the authorization invalid operation instruction, the base station A, the base station B, and the base station C respectively perform invalid operation on the respective current authorization files.
- base station A can first determine whether it has a current authorization file stored therein. If If not, the authorization invalidation operation failure response message is sent to the OMC, and the physical identifier of the base station A is carried in the message, and the entire process ends. If yes, the base station A sets the validity period of the current authorization file A1 for 60 days. In addition, the base station A also monitors the expiration date of the current authorization file A1.
- the base station B and the base station C successfully perform the authorization invalidation operation according to the manner of the base station A.
- Step 88 Generate authorization adjustment verification information.
- base station A may first obtain authorization adjustment verification information.
- the base station A obtains the physical identifier ID1 of the base station A and the serial number NO1 of the current authorization file by reading the network element identification field and the file identification field of the current authorization file A1.
- the base station generates a revoke code obtained by encrypting the physical identifier ID1 of the base station A and the sequence number NO1 of the current authorization file A1.
- the encryption method can be implemented by using any encryption method in the prior art.
- the base station A generates an authorization invalidation operation response message according to the obtained physical identifier ID1 of the base station A, the serial number NO1 of the current authorization file, and the invalidation code Disable1.
- the base station B also successfully generates the authorization adjustment verification information according to the manner of the base station A.
- the base station C obtains the physical identifier ID5 of the base station C and the serial number NO5 of the current authorization file by reading the network element identification field and the file identification field of the current authorization file C1, and randomly generates a Disable code Disable3.
- Step 89 The base station A, the base station B, and the base station C respectively send an authorization invalidation operation response message to the OMC.
- Step 810 The base station A, the base station B, and the base station C respectively mark the current authorization file A1, the current authorization file B1, and the current authorization file C1, respectively, to prevent the current authorization file A1, the current authorization file B1, and the current authorization file C1 from being again It is loaded to further ensure the reliability of authorization for each base station.
- Step 811 The OMC sends the base station A, the base station B, and the base station C to the file application server. Authorization invalidation operation response message.
- Step 812 The file application server verifies the authorization adjustment verification information of the base station A, the base station B, and the base station C, respectively.
- the file application server parses the failure code Disable1 of the base station A, obtains the physical identification ID2 of the base station A, and the standard serial number of the current authorization file A1 is NO2. By comparison, ID1 is consistent with ID2, and NO1 is consistent with NO2, so the verification of base station A is passed.
- the verification of the base station B is also passed.
- the file application server parses the revoke code Disable3 of the base station C, obtains the physical identifier ID6 of the base station C, and the target serial number of the authorization file C1 is NO6. By comparison, ID5 is inconsistent with ID6, and NO5 is inconsistent with NO6. Therefore, the verification of base station C is not passed. Therefore, the file application server does not allow adjustment of the authorization information for the base stations A, B, and C.
- Step 813 The file application server sends a response message, and the adjustment of the authorization information to the base stations A, B, and C is not allowed.
- the solution of the embodiment of the present invention can ensure that the original authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby utilizing the solution of the embodiment of the present invention. It ensures the normal operation of the equipment and prevents the leakage of the license.
- the ninth embodiment of the present invention further provides an apparatus for adjusting authorization information, where the apparatus may be located in a network element (such as a base station), including:
- the receiving unit 91 is configured to receive an authorization invalidation operation instruction
- the processing unit 92 is configured to perform authorization failure processing on the current authorization file according to the authorization invalidation operation instruction
- the sending unit 93 is configured to generate and send the authorization adjustment verification information.
- the processing unit 92 is configured to set an expiration date for the current authorization file.
- the authorization adjustment verification information includes: a physical identifier of the network element, and the The pre-authorization file identifier and the revoke code are generated according to the physical identifier of the network element and the current authorization file identifier.
- the receiving unit 91 and the sending unit 93 herein may correspond to a communication interface in the network element, where the communication interface may be a wired interface or a wireless interface.
- the processing unit 92 may correspond to an information processing structure in a network element, where the information processing structure may include a processor or processing circuit or the like.
- the processor can include a central processing unit, a microprocessor, a digital signal processor or a programmable array, and the like.
- the processing circuit can include an application specific integrated circuit or the like.
- processing unit 92 is further configured to: when the expiration date of the expiration of the expiration date, the current authorization file is invalid; or: when the new authorization file is loaded before the expiration of the expiration date, the usage period is released. Settings.
- the solution of the embodiment of the present invention can ensure that the original authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby utilizing the solution of the embodiment of the present invention.
- the normal operation of the device is guaranteed.
- the apparatus for adjusting authorization information according to the tenth embodiment of the present invention includes:
- the receiving unit 101 is configured to receive the authorization adjustment verification information of the network element to be adjusted, and the verification unit 102 is configured to verify the authorization adjustment verification information.
- the generating unit 103 is configured to be the network to be adjusted when the verification is passed. The meta generates a new authorization file.
- the authorization adjustment verification information of the network element to be adjusted may include: a physical identifier of the network element to be adjusted, a current authorization file identifier of the network element to be adjusted, and a revoke code; the revoke code is based on the physical identifier of the network element to be adjusted.
- the identifier of the to-be-adjusted network element is generated by the current authorization file identifier.
- the receiving unit 101 herein may correspond to various types of receiving interfaces.
- the verification unit 102 and the generation unit 103 may correspond to a processor or a processing circuit.
- the structure of the processor or processing circuit can be seen in the aforementioned corresponding part.
- the processor or the processing circuit described in the embodiment of the present invention can be stored The storage medium is connected, and the function of the corresponding unit can be completed by reading and executing the specified code in the storage medium.
- the verification unit 102 includes:
- the parsing module is configured to parse the physical identifier of the network element and the identifier of the authorization file from the revoke code
- the comparison module is configured to: when the physical identifier of the parsed network element is consistent with the physical identifier of the to-be-adjusted network element, When the identifier of the authorization file is consistent with the current authorization file identifier of the NE to be adjusted, the verification is passed.
- the solution of the embodiment of the present invention can ensure that the original authorization file of the network element cannot be loaded again due to the failure, so that the network element can load an accurate authorization file, thereby utilizing the solution of the embodiment of the present invention.
- the normal operation of the device is guaranteed.
- the embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute at least one of the foregoing methods for adjusting authorization information, such as executable One or more of the methods shown in Figures 1-8.
- the computer storage medium may include various types of storage media such as an optical disk, a hard disk, or a magnetic disk, and may be a non-transitory storage medium.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明实施例提供一种授权信息的调整方法及装置,涉及通信技术领域,为保证设备的正常运行而发明。该方法包括:接收授权失效操作指令;根据所述授权失效操作指令对当前授权文件进行授权失效处理;生成并发送授权调整验证信息。本发明实施例还公开了一种计算机存储介质。
Description
本发明涉及通信技术领域,尤其涉及一种授权信息的调整方法、装置和计算机存储介质。
通信系统中,每个基站都有对应的License(授权,许可)文件,用于存储基站的授权信息。同时,在该License文件中存储基站的物理标识,用于表示License文件和基站的对应关系。
现有技术中,运营商通常会为多个基站共购买一个总量的资源,然后将该资源分配给每个基站。同时分配给每个基站的资源还可根据基站的运行情况进行调整。在调整过程中,运营商向厂商维护人员申请做容量调整,并给出每个基站调整后的授权值。维护人员根据要求,为需要调整的基站生成新的License文件,并将新的License文件提交给运营商,由运营商将新的license文件发送给基站,基站加载新的license文件,从而完成对各个基站的授权信息的调整。
但是,在上述调整的过程中,如果基站在收到新的license文件后不进行加载而仍使用原来的授权文件,那么对该基站的授权信息的调整将会失败,从而影响了设备的正常运行。
发明内容
有鉴于此,本发明实施例期望提供一种授权信息的调整方法、装置和计算机存储介质,期望能够减少设备的运行异常。
本发明提供一种授权信息的调整方法,包括:
接收授权失效操作指令;
根据所述授权失效操作指令对当前授权文件进行授权失效处理;
生成并发送授权调整验证信息。
可选地,所述授权失效处理包括:
为所述当前授权文件设置使用有效期限。
可选地,所述授权调整验证信息包括:网元的物理标识、所述当前授权文件标识以及失效码;所述失效码是根据所述网元的物理标识和所述当前授权文件标识生成的。
可选地,所述方法还包括:
当所述使用有效期限届满时,所述当前授权文件失效;或者:
在所述使用有效期限届满前加载新的授权文件时,解除所述使用期限的设置。
本发明还提供一种授权信息的调整方法,包括:
接收待调整网元的授权调整验证信息,
对所述授权调整验证信息进行验证;
当验证通过时,为所述待调整网元生成新的授权文件。
可选地,所述待调整网元的授权调整验证信息包括:待调整网元的物理标识、待调整网元当前授权文件标识以及失效码;所述失效码是根据所述待调整网元的物理标识和所述待调整网元当前授权文件标识生成的。
可选地,对所述授权调整验证信息进行验证,包括:
从所述失效码中解析出网元物理标识和授权文件标识;
当解析出的网元物理标识与所述待调整网元的物理标识一致、且解析出的授权文件的标识与所述待调整网元当前授权文件标识一致时,验证通过。
本发明还提供一种授权信息的调整方法,其中,包括:
向待调整网元发送授权失效操作指令;
接收所述待调整网元发送的授权调整验证信息,所述授权验证信息用于文件申请服务器为所述待调整网元生成新的授权文件。
可选地,所述待调整网元的授权调整验证信息包括:网元的物理标识、当前授权文件标识以及失效码;所述是失效码是根据所述网元的物理标识和所述当前授权文件标识生成的。
本发明还提供一种授权信息的调整装置,包括:
接收单元,配置为接收授权失效操作指令;
处理单元,配置为根据所述授权失效操作指令对当前授权文件进行授权失效处理;
发送单元,配置为生成并发送授权调整验证信息。
可选地,所述处理单元配置为,为所述当前授权文件设置使用有效期限。
可选地,所述授权调整验证信息包括:网元的物理标识、所述当前授权文件标识以及失效码;所述失效码是根据所述网元的物理标识和所述当前授权文件标识生成的。
可选地,所述处理单元还配置为:
当所述使用有效期限届满时,所述当前授权文件失效;或者:
在所述使用有效期限届满前加载新的授权文件时,解除所述使用期限的设置。
本发明还提供一种授权信息的调整装置,包括:
接收单元,配置为接收待调整网元的授权调整验证信息,
验证单元,配置为对所述授权调整验证信息进行验证;
生成单元,配置为当验证通过时,为所述待调整网元生成新的授权文
件。
可选地,所述待调整网元的授权调整验证信息包括:待调整网元的物理标识、待调整网元当前授权文件标识以及失效码;所述失效码是根据所述待调整网元的物理标识和所述待调整网元当前授权文件标识生成的。
可选地,所述验证单元包括:
解析模块,配置为从所述失效码中解析出网元物理标识和授权文件标识;
比较模块,配置为当解析出的网元物理标识与所述待调整网元的物理标识一致、且解析出的授权文件的标识与所述待调整网元当前授权文件标识一致时,验证通过。
本发明实施例还提供一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,所述计算机可执行指令用于执行权利前述授权信息的调整方法的至少其中之一。
在本发明实施例公开的技术方案中,由于本发明实施例的方案是由网元对当前授权文件进行失效操作,并在文件申请服务器在对网元的授权调整验证信息验证通过后,才为网元生成对应的新的授权文件,进而允许对网元做授权信息的调整。也就是说,利用本发明实施例的方案能够保证网元原有的当前授权文件由于失效而不能再次被加载,从而使得网元可以加载准确的授权文件,从而利用本发明实施例的方案保证了设备的正常运行。
图1为本发明实施例一提供的授权信息的调整方法的流程图;
图2为本发明实施例二提供的授权信息的调整方法的流程图;
图3为本发明实施例三提供的授权信息的调整方法的流程图;
图4为本发明实施例四提供的授权信息的调整方法的流程图;
图5为本发明实施例五提供的授权信息的调整方法的流程图;
图6为本发明实施例六提供的授权信息的调整方法的流程图;
图7为本发明实施例七提供的授权信息的调整方法的流程图;
图8为本发明实施例八提供的授权信息的调整方法的流程图;
图9为本发明实施例九提供的授权信息的调整装置的示意图;
图10为本发明实施例十提供的授权信息的调整装置的示意图。
下面将结合附图和实施例,对本发明的具体实施方式作进一步详细描述。以下实施例用于说明本发明,但不用来限制本发明的范围。
如图1所示,本发明实施例一的授权信息的调整方法,可由网元(如基站)执行,包括:
步骤11、接收授权失效操作指令。
每个网元(如基站)对应有一个授权文件,该授权文件对应有唯一的标识,其中该标识可以是文件序列号。运营商会为各个网元分配资源,并向各个网元加载授权文件。在此将网元当前所拥有的授权文件称为当前授权文件。在各网元的运行过程中,若运营商发现网元现有的分配资源不合适,则需要对各网元之间分配的资源进行调整,也即需要对各网元的授权信息进行调整。此时,运营商向文件申请服务器提出授权信息调整需求,在该需求中可以包括需要调整授权信息的网元(以下简称待调整网元)的物理标识(Identification,ID),用以请求获得各网元的新的授权文件。
在此步骤中,当需要进行授权信息调整时,文件申请服务器向操作维护中心可发送授权信息调整指令,在所述授权信息调整指令中包括待调整网元的物理标识。此时,操作维护中心根据该授权信息调整指令向网元发送授权失效操作指令,用于指示网元进行授权失效处理。
步骤12、根据所述授权失效操作指令对当前授权文件进行授权失效处
理。
在本发明实施例中,当收到操作维护中心的授权失效操作指令后,网元首先查找自身是否存储有当前授权文件。
若没有存储当前授权文件,则向操作维护中心发送授权失效操作失败响应消息,在该消息中包括网元的物理标识。
若存储有当前授权文件,则对当前授权文件进行授权失效处理,可选地是为所述当前授权文件设置使用有效期限。可选地,网元可在其配置文件中建立文件序列号和使用有效期限的对应关系,为当前授权文件设置使用有效期限,例如可将当前授权文件的使用有效期限设置为当前授权文件60天。当60天的有效期限过后,该当前授权文件失效。如果在所述60天的期限届满前加载了新的授权文件时,那么可解除所述使用期限的设置。
步骤13、生成并发送授权调整验证信息。
在本发明实施例中,所述授权调整验证信息包括:网元的物理标识、所述当前授权文件标识以及失效(Disable)码;所述失效码是根据所述网元的物理标识和所述当前授权文件标识生成的。
其中,在本发明实施例中,该失效码通过如下方式获得。第一种方式是,所述当前授权文件的失效码由文件申请服务器通过对待调整网元的物理标识和其对应的当前授权文件标识进行加密的方式获得,并将其携带在当前授权文件中。待调整网元通过解析当前授权文件即可获得当前授权文件的失效码。第二种方式是,由待调整网元在收到操作维护中心的授权失效操作指令后,对待调整网元的物理标识和当前授权文件标识进行加密获得。
可选地,在获取授权调整验证信息时,网元可分别读取所述当前授权文件的网元标识字段和所述当前授权文件的文件标识字段获取所述网元的物理标识和所述当前授权文件标识。然后,读取所述当前授权文件的失效
码字段确定所述当前授权文件本身是否包括所述当前授权文件的失效码。当所述失效码字段中的信息为第一预设值时,表示所述当前授权文件本身包括所述当前授权文件的失效码;当所述失效码字段中的信息为第二预设值时,表示所述当前授权文件本身不包括所述当前授权文件的失效码。其中所述第一预设值可以是0,第二预设值可以是1等。若所述当前授权文件本身包括所述当前授权文件的失效码,解析所述当前授权文件获取所述当前授权文件的失效码;若所述当前授权文件本身不包括所述当前授权文件的失效码,根据所述网元的物理标识和所述当前授权文件标识加密生成所述当前授权文件的失效码。
当获得了授权调整验证信息后,可利用授权调整验证信息生成授权失效操作响应消息,并向操作维护中心发送所述授权失效操作响应消息。
根据以上的描述可以看出,在本发明实施例中,由于本发明实施例的方案是由网元对当前授权文件进行失效操作,并在文件申请服务器在对网元的授权调整验证信息验证通过后,才为网元生成对应的新的授权文件,进而允许对网元做授权信息的调整。也就是说,利用本发明实施例的方案能够保证网元原有的当前授权文件由于失效而不能再次被加载,从而使得网元可以加载准确的授权文件,从而利用本发明实施例的方案保证了设备的正常运行。
如图2所示,本发明实施例二的授权信息的调整方法,可由文件申请服务器执行,包括:
步骤21、接收待调整网元的授权调整验证信息。
当需要进行授权信息调整时,文件申请服务器向操作维护中心发送授权信息调整指令,在所述授权信息调整指令中包括待调整网元的物理标识。在该指令中可包括1个待调整网元的物理标识,还可以包括2个以上的待调整网元的物理标识。当收到了文件申请服务器发送的授权信息调整指令
后,操作维护中心会获取待调整网元的授权调整验证信息,并将待调整网元的授权调整验证信息发送给文件申请服务器。此时,文件申请服务器接收所述操作维护中心发送的网元的授权调整验证信息。
其中,所述待调整网元的授权调整验证信息包括:待调整网元的物理标识、待调整网元当前授权文件标识以及失效码;所述失效码是根据所述待调整网元的物理标识和所述待调整网元当前授权文件标识生成的。
步骤22、对所述授权调整验证信息进行验证。
在此步骤中,文件申请服务器可首先从所述失效码中解析出网元物理标识和授权文件标识。分别将解析出的网元物理标识与所述待调整网元的物理标识、解析出的授权文件的标识与所述待调整网元当前授权文件标识进行比较。当解析出的网元物理标识与所述待调整网元的物理标识一致、且解析出的授权文件的标识与所述待调整网元当前授权文件标识一致时,验证通过。否则验证不通过。
步骤23、当验证通过时,为所述待调整网元生成新的授权文件。
当对所述待调整网元的授权调整验证信息的验证通过时,将所述授权调整验证信息中的待调整网元的物理标识和所述当前授权文件标识、所述当前授权文件的失效码分别存储到对应的字段中,根据各字段中的信息生成所述待调整网元的新的授权文件。例如,将待调整网元的物理标识存储到网元标识字段,将当前授权文件标识存储到文件标识字段,将当前授权文件的失效码存储到失效码字段中,而后根据各字段中的信息生成待调整网元的新的授权文件。
根据以上的描述可以看出,在本发明实施例中,由于本发明实施例的方案是由网元对当前授权文件进行失效操作,并在文件申请服务器在对网元的授权调整验证信息验证通过后,才为网元生成对应的新的授权文件,进而允许对网元做授权信息的调整。也就是说,利用本发明实施例的方案
能够保证网元原有的当前授权文件由于失效而不能再次被加载,从而使得网元可以加载准确的授权文件,从而利用本发明实施例的方案保证了设备的正常运行。
如图3所示,本发明实施例三的授权信息的调整方法,可以由操作维护中心(Operation and Maintenance Center,OMC)执行,包括:
步骤31、向待调整网元发送授权失效操作指令。
在此步骤中,OMC接收文件申请服务器发送的授权信息调整指令,在所述授权信息调整指令中包括待调整网元的物理标识。当收到文件申请服务器的授权信息调整指令后,操作维护中心解析该指令,获得待调整网元的物理标识。根据所述待调整网元的物理标识,OMC向所述待调整网元发送授权失效操作指令。
步骤32、接收所述待调整网元发送的授权调整验证信息,所述授权验证信息用于文件申请服务器为所述待调整网元生成新的授权文件。
在此步骤中,OMC接收所述待调整网元发送的授权失效操作响应消息,在所述待调整网元的授权失效操作响应消息中包括所述待调整网元的授权调整验证信息。所述待调整网元的授权调整验证信息包括:网元的物理标识、当前授权文件标识以及失效码;所述是失效码是根据所述网元的物理标识和所述当前授权文件标识生成的。
在本发明实施例中,在收到待调整网元的授权调整验证信息后,可将待调整网元的授权调整验证信息存储在指定文件中,然后将指定文件发送给文件申请服务器,从而将待调整网元的授权调整验证信息发送给文件申请服务器。其中,所述指定文件可以是任意形式的文件,例如文本文件等。
根据以上的描述可以看出,在本发明实施例中,由于本发明实施例的方案是由网元对当前授权文件进行失效操作,并在文件申请服务器在对网元的授权调整验证信息验证通过后,才为网元生成对应的新的授权文件,
进而允许对网元做授权信息的调整。也就是说,利用本发明实施例的方案能够保证网元原有的当前授权文件由于失效而不能再次被加载,从而使得网元可以加载准确的授权文件,从而利用本发明实施例的方案保证了设备的正常运行。
以下,结合实施例四到实施例七详细描述本发明实施例的授权信息的调整方法的实现过程。在这些实施例中,以对基站A、B、C的RRC用户数进行调整为例进行描述,其中约定的RRC用户总授权量为1000。其中,在实施例四中,以对基站A的RRC用户数进行调整为例进行描述。
在实施例四中,假设在当前授权文件中包括失效码。如图4所示,本发明实施例四的授权信息调整方法包括:
步骤41、文件申请服务器根据运营商的初始需求为基站A生成当前授权文件。
假设,运营商初始对RRC用户数的分配方式如下:基站A:300。
运营商将该需求发送给文件申请服务器,文件申请服务器根据该需求分别为基站A生成当前授权文件A1。在当前授权文件A1的网元标识字段存储有基站A的物理标识ID1,在文件标识字段存储有当前授权文件A1的序列号NO1,在失效码字段存储有当前授权文件的失效码Disable1,其中该失效码是通过将基站A的物理标识ID1和当前授权文件A1的序列号NO1进行加密获得的。其中该加密方式可采用现有技术中的任意一种加密方式实现。
步骤42、文件申请服务器将当前授权文件A1提供给运营商。
步骤43、运营商将当前授权文件A1通过OMC加载到基站A,并对基站的授权结果进行监控。
步骤44、运行一段时间过后,运营商向文件申请服务器提出授权信息调整需求,要求对基站A的授权信息进行调整。其中,调整后的分配方式
如下:基站A:500。
步骤45、文件申请服务器根据运营商的授权信息调整需求,向OMC发送授权信息调整指令,在所述授权信息调整指令中包括基站A的物理标识。
步骤46、OMC根据基站A的物理标识向所述基站A发送授权失效操作指令。
步骤47、基站A在收到授权失效操作指令后,对当前授权文件进行失效操作。
基站A首先可确定自身是否存储有当前授权文件。若没有,则向OMC发送授权失效操作失败响应消息,在该消息中携带基站A的物理标识,整个流程结束。若有,基站A为当前授权文件A1设置使用有效期限60天。此外,基站A还对当前授权文件A1的使用有效期限进行监控。
步骤48、生成授权调整验证信息。
可选地,基站A通过读取当前授权文件A1的网元标识字段、文件标识字段、失效码字段分别获得基站A的物理标识ID1、当前授权文件的序列号NO1以及失效码Disable1,并根据获得的基站A的物理标识ID1、当前授权文件的序列号NO1以及失效码Disable1生成授权失效操作响应消息。
步骤49、基站A向OMC发送授权失效操作响应消息。
步骤410、基站A对当前授权文件A1进行标记,用以防止当前授权文件A1再次被加载,从而进一步的保证对各基站授权的可靠性。
步骤411、OMC向文件申请服务器发送基站A的授权失效操作响应消息。
步骤412、文件申请服务器对基站A的授权调整验证信息进行验证。
文件申请服务器解析基站A的失效码Disable1,获得基站A的物理标
识ID2,当前授权文件A1的标序列号为NO2。经比较,ID1与ID2一致,NO1与NO2一致,因此,对基站A的验证通过。若验证不通过,则流程结束。
步骤413、文件申请服务器为基站A生成新的授权文件。
步骤414、文件申请服务器将基站A的新的授权文件发送给运营商。
步骤415、运营商通过OMC向基站A发送新的授权文件,基站A加载新的授权文件。
需要注意的是,在上述步骤415的实施过程中,若基站A是在当前授权文件的使用有效期限到期之前收到了新的授权文件,则基站直接加载新的授权文件。如果基站A是在当前授权文件的使用有效期限到期之前仍未收到新的授权文件,则基站A将会加载预设的授权文件,从而保证设备的运行。其中,该预设的授权文件用以使得站间的授权量达到最小化。例如,在此实施例中,通过该预设的授权文件,对RRC用户数的分配方式如下:基站A:100。
由上可以看出,利用本发明实施例的方案能够保证网元原有的当前授权文件由于失效而不能再次被加载,从而使得网元可以加载准确的授权文件,从而利用本发明实施例的方案保证了设备的正常运行,并且能防止发生License泄露的情况。
在实施例五中,假设在当前授权文件中包括失效码。如图5所示,本发明实施例五的授权信息调整方法包括:
步骤51、文件申请服务器根据运营商的初始需求分别为基站A,基站B,基站C生成当前授权文件。
假设,运营商初始对RRC用户数的站间分配方式如下:
基站A:300;基站B:400;基站C:300。
运营商将该需求发送给文件申请服务器,文件申请服务器根据该需求
分别为基站A,基站B,基站C生成当前授权文件A1,B1,C1。
以当前授权文件A1为例,在该文件的网元标识字段存储有基站A的物理标识ID1,在文件标识字段存储有当前授权文件A1的序列号NO1,在失效码字段存储有当前授权文件的失效码Disable1,其中该失效码是通过将基站A的物理标识ID1和当前授权文件A1的序列号NO1进行加密获得的。其中该加密方式可采用现有技术中的任意一种加密方式实现。
步骤52、文件申请服务器将当前授权文件A1,B1,C1提供给运营商。
步骤53、运营商将当前授权文件A1,B1,C1通过OMC分别加载到基站A,基站B,基站C,并对各基站的授权结果进行监控。
步骤54、运行一段时间过后,运营商向文件申请服务器提出授权信息调整需求,要求对基站A,基站B,基站C的授权信息进行调整。其中,调整后的站间分配方式如下:基站A:500;基站B:300;基站C:200。
步骤55、文件申请服务器根据运营商的授权信息调整需求,向OMC发送授权信息调整指令,在所述授权信息调整指令中包括基站A、基站B、基站C的物理标识。
步骤56、OMC根据基站A、基站B、基站C的物理标识分别向所述基站A、基站B、基站C发送授权失效操作指令。
步骤57、基站A、基站B、基站C在收到授权失效操作指令后,分别对各自的当前授权文件进行失效操作。
以基站A为例,基站A首先可确定自身是否存储有当前授权文件。若没有,则向OMC发送授权失效操作失败响应消息,在该消息中携带基站A的物理标识,整个流程结束。
若有,基站A为当前授权文件A1设置使用有效期限60天。此外,基站A还对当前授权文件A1的使用有效期限进行监控。
假设,在本发明实施例中,基站B、基站C也按照基站A的方式成功
的进行了授权失效操作。
步骤58、生成授权调整验证信息。
以基站A为例,基站A首先获取授权调整验证信息。可选地,基站A通过读取当前授权文件A1的网元标识字段、文件标识字段、失效码字段分别获得基站A的物理标识ID1、当前授权文件的序列号NO1以及失效码Disable1,并根据获得的基站A的物理标识ID1、当前授权文件的序列号NO1以及失效码Disable1生成授权失效操作响应消息。
假设,在本发明实施例中,基站B、C也按照基站A的方式成功的生成了授权调整验证信息。
步骤59、基站A、基站B、基站C分别向OMC发送授权失效操作响应消息。
步骤510、基站A、基站B、基站C分别对各自的当前授权文件A1、当前授权文件B1、当前授权文件C1进行标记,用以防止当前授权文件A1、当前授权文件B1、当前授权文件C1再次被加载,从而进一步的保证对各基站授权的可靠性。
步骤511、OMC分别向文件申请服务器发送基站A、基站B、基站C的授权失效操作响应消息。
步骤512、文件申请服务器分别对基站A、基站B、基站C的授权调整验证信息进行验证。
还是以基站A为例,文件申请服务器解析基站A的失效码Disable1,获得基站A的物理标识ID2,当前授权文件A1的标序列号为NO2。经比较,ID1与ID2一致,NO1与NO2一致,因此,对基站A的验证通过。
假设,在本发明实施例中,对基站B、基站C的验证也通过。
步骤513、文件申请服务器分别为基站A、基站B、基站C生成新的授权文件。
步骤514、文件申请服务器分别将基站A、基站B、基站C的新的授权文件发送给运营商。
步骤515、运营商通过OMC分别向基站A、基站B、基站C发送新的授权文件,基站A、基站B、基站C分别加载各自的新的授权文件。
需要注意的是,在上述步骤515的实施过程中,若基站A、基站B、基站C是在各自的当前授权文件的使用有效期限到期之前收到了各自的新的授权文件,则基站直接加载各自的新的授权文件。如果基站A、基站B、基站C是在各自的当前授权文件的使用有效期限到期之前仍未收到新的授权文件,则基站A、基站B、基站C将会加载各自预设的授权文件,从而保证设备的运行。其中,该预设的授权文件用以使得站间的授权量达到最小化。例如,在此实施例中,通过该预设的授权文件,对RRC用户数的站间分配方式如下:基站A:100;基站B:100;基站C:100。
以基站A为例,若基站A在当前授权文件A1的使用有效期限到期前收到了新的授权文件,则基站A加载该新的授权文件。若没有收到,则基站A加载其存储的预设的授权文件。
由上可以看出,利用本发明实施例的方案能够保证网元原有的当前授权文件由于失效而不能再次被加载,从而使得网元可以加载准确的授权文件,从而利用本发明实施例的方案保证了设备的正常运行,并且能防止发生License泄露的情况。
在实施例六中,假设在当前授权文件中包括失效码。如图6所示,本发明实施例五的授权信息调整方法包括:
步骤61-66、在此实施例中,步骤61-66的描述与实施例四中步骤51-56的描述相同。
步骤67、基站A、基站B、基站C在收到授权失效操作指令后,分别对各自的当前授权文件进行失效操作。
以基站A为例,基站A首先可确定自身是否存储有当前授权文件。若没有,则向OMC发送授权失效操作失败响应消息,在该消息中携带基站A的物理标识,整个流程结束。若有,基站A为当前授权文件A1设置使用有效期限60天。此外,基站A还对当前授权文件A1的使用有效期限进行监控。
假设,在本发明实施例中,基站B、基站C也按照基站A的方式成功的进行了授权失效操作。
步骤68、生成授权调整验证信息。
以基站A为例,基站A通过读取当前授权文件A1的网元标识字段、文件标识字段、失效码字段分别获得基站A的物理标识ID1、当前授权文件的序列号NO1以及失效码Disable1,并根据获得的基站A的物理标识ID1、当前授权文件的序列号NO1以及失效码Disable1生成授权失效操作响应消息。
假设,在本发明实施例中,基站B也按照基站A的方式成功的生成了授权调整验证信息。
而基站C通过读取当前授权文件C1的网元标识字段、文件标识字段分别获得基站C的物理标识ID5、当前授权文件的序列号NO5,并未读取失效码字段获取Disable码,而是随意的获取了一个Disable码Disable3。
步骤69、基站A、基站B、基站C分别向OMC发送授权失效操作响应消息。
步骤610、基站A、基站B、基站C分别对各自的当前授权文件A1、当前授权文件B1、当前授权文件C1进行标记,用以防止当前授权文件A1、当前授权文件B1、当前授权文件C1再次被加载,从而进一步的保证对各基站授权的可靠性。
步骤611、OMC分别向文件申请服务器发送基站A、基站B、基站C
的授权失效操作响应消息。
步骤612、文件申请服务器分别对基站A、基站B、基站C的授权调整验证信息进行验证。
还是以基站A为例,文件申请服务器解析基站A的失效码Disable1,获得基站A的物理标识ID2,当前授权文件A1的标序列号为NO2。经比较,ID1与ID2一致,NO1与NO2一致,因此,对基站A的验证通过。
在本发明实施例中,对基站B的验证也通过。
而对基站C,文件申请服务器解析基站C的失效码Disable3,获得基站C的物理标识ID6,授权文件C1的标序列号为NO6。经比较,ID5与ID6不一致,NO5与NO6不一致,因此,对基站C的验证未通过。因此,文件申请服务器不允许对基站A、B、C做授权信息的调整。
步骤613、文件申请服务器发送响应消息,该消息表示不允许对基站A、B、C做授权信息的调整。
由上可以看出,利用本发明实施例的方案能够保证网元原有的当前授权文件由于失效而不能再次被加载,从而使得网元可以加载准确的授权文件,从而利用本发明实施例的方案保证了设备的正常运行,并且能防止发生License泄露的情况。
在实施例七中,假设在当前授权文件中不包括失效码,而是由基站自己生成失效码。如图7所示,本发明实施例六的授权信息调整方法包括:
步骤71、文件申请服务器根据运营商的初始需求为基站A,基站B,基站C生成当前授权文件。
假设,运营商初始对RRC用户数的站间分配方式如下:
基站A:300;基站B:400;基站C:300。
运营商将该需求发送给文件申请服务器,文件申请服务器根据该需求分别为基站A,基站B,基站C生成当前授权文件A1,B1,C1。以当前授
权文件A为例,在该文件的网元标识字段存储有基站A的物理标识ID1,在文件标识字段存储有当前授权文件A1的序列号NO1。
步骤72、文件申请服务器将当前授权文件A1,B1,C1提供给运营商。
步骤73、运营商将当前授权文件A1,B1,C1通过OMC分别加载到基站A,基站B,基站C,并对各基站的授权结果进行监控。
步骤74、运行一段时间过后,运营商向文件申请服务器提出授权信息调整需求,要求对基站A,基站B,基站C的授权信息进行调整。其中,调整后的站间分配方式如下:基站A:500;基站B:300;基站C:200。
步骤75、文件申请服务器根据运营商的授权信息调整需求,向OMC发送授权信息调整指令,在所述授权信息调整指令中包括基站A、基站B、基站C的物理标识。
步骤76、OMC根据基站A、基站B、基站C的物理标识分别向所述基站A、基站B、基站C发送授权失效操作指令。
步骤77、基站A、基站B、基站C在收到授权失效操作指令后,分别对各自的当前授权文件进行失效操作。
以基站A为例,基站A首先可确定自身是否存储有当前授权文件。若没有,则向OMC发送授权失效操作失败响应消息,在该消息中携带基站A的物理标识,整个流程结束。若有,基站A为当前授权文件A1设置使用有效期限60天。此外,基站A还对当前授权文件A1的使用有效期限进行监控。
假设,在本发明实施例中,基站B、基站C也按照基站A的方式成功的进行了授权失效操作。
步骤78、生成授权调整验证信息。
以基站A为例,可选地,基站A通过读取当前授权文件A1的网元标识字段、文件标识字段别获得基站A的物理标识ID1、当前授权文件的序
列号NO1。基站生成失效码,其中该失效码是通过将基站A的物理标识ID1和当前授权文件A1的序列号NO1进行加密获得的。其中该加密方式可采用现有技术中的任意一种加密方式实现。基站A根据获得的基站A的物理标识ID1、当前授权文件的序列号NO1以及失效码Disable1生成授权失效操作响应消息。
假设,在本发明实施例中,基站B、基站C也按照基站A的方式成功的生成了授权调整验证信息。
步骤79、基站A、基站B、基站C分别向OMC发送授权失效操作响应消息。
步骤710、基站A、基站B、基站C分别对各自的当前授权文件A1、当前授权文件B1、当前授权文件C1进行标记,用以防止当前授权文件A1、当前授权文件B1、当前授权文件C1再次被加载,从而进一步的保证对各基站授权的可靠性。
步骤711、OMC分别向文件申请服务器发送基站A、基站B、基站C的授权失效操作响应消息。
步骤712、文件申请服务器分别对基站A、基站B、基站C的授权调整验证信息进行验证。
还是以基站A为例,还是以基站A为例,文件申请服务器解析基站A的失效码Disable1,获得基站A的物理标识ID2,当前授权文件A1的标序列号为NO2。经比较,ID1与ID2一致,NO1与NO2一致,因此,对基站A的验证通过。
假设,在本发明实施例中,对基站B、基站C的验证也通过。
步骤713、文件申请服务器分别为基站A、基站B、基站C生成新的授权文件。
步骤714、文件申请服务器分别将基站A、基站B、基站C的新的授权
文件发送给运营商。
步骤715、运营商通过OMC分别向基站A、基站B、基站C发送新的授权文件,基站A、基站B、基站C分别加载各自的新的授权文件。
需要注意的是,在上述步骤715的实施过程中,若基站A、基站B、基站C是在各自的当前授权文件的使用有效期限到期之前收到了各自的新的授权文件,则基站直接加载各自的新的授权文件。如果基站A、基站B、基站C是在各自的当前授权文件的使用有效期限到期之前仍未收到新的授权文件,则基站A、基站B、基站C将会加载各自预设的授权文件,从而保证设备的运行。其中,该预设的授权文件用以使得站间的授权量达到最小化。例如,在此实施例中,通过该预设的授权文件,对RRC用户数的站间分配方式如下:基站A:100;基站B:100;基站C:100。
以基站A为例,若基站A在当前授权文件A1的使用有效期限到期前收到了新的授权文件,则基站A加载该新的授权文件。若没有收到,则基站A加载其存储的预设的授权文件。
由上可以看出,利用本发明实施例的方案能够保证网元原有的当前授权文件由于失效而不能再次被加载,从而使得网元可以加载准确的授权文件,从而利用本发明实施例的方案保证了设备的正常运行,并且能防止发生License泄露的情况。
在实施例八中,假设在当前授权文件中不包括失效码,而是由基站自己生成失效码。如图8所示,本发明实施例七的授权信息调整方法包括:
步骤81-86、在此实施例中,步骤81-86的描述与实施例六中步骤71-76的描述相同。
步骤87、基站A、基站B、基站C在收到授权失效操作指令后,分别对各自的当前授权文件进行失效操作。
以基站A为例,基站A首先可确定自身是否存储有当前授权文件。若
没有,则向OMC发送授权失效操作失败响应消息,在该消息中携带基站A的物理标识,整个流程结束。若有,基站A为当前授权文件A1设置使用有效期限60天。此外,基站A还对当前授权文件A1的使用有效期限进行监控。
假设,在本发明实施例中,基站B、基站C也按照基站A的方式成功的进行了授权失效操作。
步骤88、生成授权调整验证信息。
以基站A为例,可选地,基站A首先可获取授权调整验证信息。可选地,基站A通过读取当前授权文件A1的网元标识字段、文件标识字段别获得基站A的物理标识ID1、当前授权文件的序列号NO1。基站生成失效码,其中该失效码是通过将基站A的物理标识ID1和当前授权文件A1的序列号NO1进行加密获得的。其中该加密方式可采用现有技术中的任意一种加密方式实现。基站A根据获得的基站A的物理标识ID1、当前授权文件的序列号NO1以及失效码Disable1生成授权失效操作响应消息。
基站B也按照基站A的方式成功的生成了授权调整验证信息。
而基站C通过读取当前授权文件C1的网元标识字段、文件标识字段分别获得基站C的物理标识ID5、当前授权文件的序列号NO5,随意的生成了一个Disable码Disable3。
步骤89、基站A、基站B、基站C分别向OMC发送授权失效操作响应消息。
步骤810、基站A、基站B、基站C分别对各自的当前授权文件A1、当前授权文件B1、当前授权文件C1进行标记,用以防止当前授权文件A1、当前授权文件B1、当前授权文件C1再次被加载,从而进一步的保证对各基站授权的可靠性。
步骤811、OMC分别向文件申请服务器发送基站A、基站B、基站C
的授权失效操作响应消息。
步骤812、文件申请服务器分别对基站A、基站B、基站C的授权调整验证信息进行验证。
还是以基站A为例,还是以基站A为例,文件申请服务器解析基站A的失效码Disable1,获得基站A的物理标识ID2,当前授权文件A1的标序列号为NO2。经比较,ID1与ID2一致,NO1与NO2一致,因此,对基站A的验证通过。
在本发明实施例中,对基站B的验证也通过。
而对基站C,文件申请服务器解析基站C的失效码Disable3,获得基站C的物理标识ID6,授权文件C1的标序列号为NO6。经比较,ID5与ID6不一致,NO5与NO6不一致,因此,对基站C的验证未通过。因此,文件申请服务器不允许对基站A、B、C做授权信息的调整。
步骤813、文件申请服务器发送响应消息,不允许对基站A、B、C做授权信息的调整。
由上可以看出,利用本发明实施例的方案能够保证网元原有的当前授权文件由于失效而不能再次被加载,从而使得网元可以加载准确的授权文件,从而利用本发明实施例的方案保证了设备的正常运行,并且能防止发生License泄露的情况。
如图9所示,本发明实施例九还提供了一种授权信息的调整装置,该装置可位于网元(如基站)中,包括:
接收单元91,配置为接收授权失效操作指令;处理单元92,配置为根据所述授权失效操作指令对当前授权文件进行授权失效处理;发送单元93,配置为生成并发送授权调整验证信息。
所述处理单元92配置为:为所述当前授权文件设置使用有效期限。在本发明实施例中,所述授权调整验证信息包括:网元的物理标识、所述当
前授权文件标识以及失效码;所述失效码是根据所述网元的物理标识和所述当前授权文件标识生成的。
这里的接收单元91及发送单元93可对应于网元中的通信接口,这里的通信接口可为有线接口或无线接口。所述处理单元92可对应于网元中的信息处理结构,这里的信息处理结构可包括处理器或处理电路等。所述处理器可包括中央处理器、微处理器、数字信号处理器或可编程阵列等。所述处理电路可包括专用集成电路等。
此外,所述处理单元92还配置为:当所述使用有效期限届满时,所述当前授权文件失效;或者:在所述使用有效期限届满前加载新的授权文件时,解除所述使用期限的设置。
其中本发明实施例所述装置的工作流程可参照前述方法实施例的描述。
由上可以看出,利用本发明实施例的方案能够保证网元原有的当前授权文件由于失效而不能再次被加载,从而使得网元可以加载准确的授权文件,从而利用本发明实施例的方案保证了设备的正常运行。
如图10所示,本发明实施例十的授权信息的调整装置,包括:
接收单元101,配置为接收待调整网元的授权调整验证信息,验证单元102,配置为对所述授权调整验证信息进行验证;生成单元103,配置为当验证通过时,为所述待调整网元生成新的授权文件。
所述待调整网元的授权调整验证信息可包括:待调整网元的物理标识、待调整网元当前授权文件标识以及失效码;所述失效码是根据所述待调整网元的物理标识和所述待调整网元当前授权文件标识生成的。
这里的接收单元101可对应于各种类型的接收接口。所述验证单元102和生成单元103可对应于处理器或处理电路。所述处理器或处理电路的结构可参见前述对应部分。本发明实施例中记载的处理器或处理电路可与存
储介质相连,通过读取并执行存储介质中的指定代码,可以完成对应单元的功能。
其中,所述验证单元102包括:
解析模块,配置为从所述失效码中解析出网元物理标识和授权文件标识;比较模块,配置为当解析出的网元物理标识与所述待调整网元的物理标识一致、且解析出的授权文件的标识与所述待调整网元当前授权文件标识一致时,验证通过。
其中本发明实施例所述装置的工作流程可参照前述方法实施例的描述。
由上可以看出,利用本发明实施例的方案能够保证网元原有的当前授权文件由于失效而不能再次被加载,从而使得网元可以加载准确的授权文件,从而利用本发明实施例的方案保证了设备的正常运行。
本发明实施例还提供一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,所述计算机可执行指令用于执行前述授权信息的调整方法的至少其中之一,例如可执行如图1至图8所示方法中的一个或多个。
所述计算机存储介质可包括光盘、硬盘或磁盘等各种类型的存储介质,可选为非瞬间存储介质。
以上所述,仅为本发明的较佳实施例而已,并非用于限定本发明的保护范围。凡按照本发明原理所作的修改,都应当理解为落入本发明的保护范围。
Claims (17)
- 一种授权信息的调整方法,包括:接收授权失效操作指令;根据所述授权失效操作指令对当前授权文件进行授权失效处理;生成并发送授权调整验证信息。
- 根据权利要求1所述的方法,其中,所述授权失效处理包括:为所述当前授权文件设置使用有效期限。
- 根据权利要求1所述的方法,其中,所述授权调整验证信息包括:网元的物理标识、所述当前授权文件标识以及失效码;所述失效码是根据所述网元的物理标识和所述当前授权文件标识生成的。
- 根据权利要求1至3任一所述的方法,其中,所述方法还包括:当所述使用有效期限届满时,所述当前授权文件失效;或者:在所述使用有效期限届满前加载新的授权文件时,解除所述使用期限的设置。
- 一种授权信息的调整方法,包括:接收待调整网元的授权调整验证信息;对所述授权调整验证信息进行验证;当验证通过时,为所述待调整网元生成新的授权文件。
- 根据权利要求5所述的方法,其中,所述待调整网元的授权调整验证信息包括:待调整网元的物理标识、待调整网元当前授权文件标识以及失效码;所述失效码是根据所述待调整网元的物理标识和所述待调整网元当前授权文件标识生成的。
- 根据权利要求6所述的方法,其中,对所述授权调整验证信息进行验证,包括:从所述失效码中解析出网元物理标识和授权文件标识;当解析出的网元物理标识与所述待调整网元的物理标识一致、且解析出的授权文件的标识与所述待调整网元当前授权文件标识一致时,验证通过。
- 一种授权信息的调整方法,包括:向待调整网元发送授权失效操作指令;接收所述待调整网元发送的授权调整验证信息,所述授权验证信息用于文件申请服务器为所述待调整网元生成新的授权文件。
- 根据权利要求8所述的方法,其中,所述待调整网元的授权调整验证信息包括:网元的物理标识、当前授权文件标识以及失效码;所述是失效码是根据所述网元的物理标识和所述当前授权文件标识生成的。
- 一种授权信息的调整装置,包括:接收单元,配置为接收授权失效操作指令;处理单元,配置为根据所述授权失效操作指令对当前授权文件进行授权失效处理;发送单元,用于生成并发送授权调整验证信息。
- 根据权利要求10所述的装置,其中,所述处理单元配置为,为所述当前授权文件设置使用有效期限。
- 根据权利要求10所述的装置,其中,所述授权调整验证信息包括:网元的物理标识、所述当前授权文件标识以及失效码;所述失效码是根据所述网元的物理标识和所述当前授权文件标识生成的。
- 根据权利要求10至12任一所述的装置,其中,所述处理单元还配置为:当所述使用有效期限届满时,所述当前授权文件失效;或者:在所述使用有效期限届满前加载新的授权文件时,解除所述使用期限 的设置。
- 一种授权信息的调整装置,包括:接收单元,配置为接收待调整网元的授权调整验证信息,验证单元,配置为对所述授权调整验证信息进行验证;生成单元,配置为当验证通过时,为所述待调整网元生成新的授权文件。
- 根据权利要求14所述的装置,其中,所述待调整网元的授权调整验证信息包括:待调整网元的物理标识、待调整网元当前授权文件标识以及失效码;所述失效码是根据所述待调整网元的物理标识和所述待调整网元当前授权文件标识生成的。
- 根据权利要求15所述的装置,其中,所述验证单元包括:解析模块,配置为从所述失效码中解析出网元物理标识和授权文件标识;比较模块,配置为当解析出的网元物理标识与所述待调整网元的物理标识一致、且解析出的授权文件的标识与所述待调整网元当前授权文件标识一致时,验证通过。
- 一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,所述计算机可执行指令用于执行权利要求1至9所述授权信息的调整方法的至少其中之一。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510644802.0A CN106572468B (zh) | 2015-10-08 | 2015-10-08 | 一种授权信息的调整方法及装置 |
CN201510644802.0 | 2015-10-08 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016184197A1 true WO2016184197A1 (zh) | 2016-11-24 |
Family
ID=57319334
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2016/074073 WO2016184197A1 (zh) | 2015-10-08 | 2016-02-18 | 授权信息的调整方法、装置和计算机存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN106572468B (zh) |
WO (1) | WO2016184197A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110032834A (zh) * | 2018-01-12 | 2019-07-19 | 厦门雅迅网络股份有限公司 | 系统授权控制方法、终端设备及存储介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101146315A (zh) * | 2006-08-03 | 2008-03-19 | 华为技术有限公司 | 许可证文件管理方法、服务器及系统 |
CN101163004A (zh) * | 2006-10-13 | 2008-04-16 | 华为技术有限公司 | 一种实现认证的方法和系统 |
CN101384059A (zh) * | 2008-09-26 | 2009-03-11 | 华为技术有限公司 | 无线通信方法和系统 |
CN101945394A (zh) * | 2009-07-10 | 2011-01-12 | 华为技术有限公司 | 许可证管理方法、装置与系统 |
US20150095237A1 (en) * | 2013-09-30 | 2015-04-02 | Infinera Corp. | License Management System |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7810137B1 (en) * | 2003-12-22 | 2010-10-05 | Cisco Technology, Inc. | Method of controlling network access that induces consumption of merchant goods or services |
CN102033820A (zh) * | 2009-09-29 | 2011-04-27 | 北京爱国者存储科技有限责任公司 | 闪存装置及网络认证方法 |
CN102130837B (zh) * | 2011-03-31 | 2015-06-03 | 中兴通讯股份有限公司 | 一种业务license动态调控方法及其系统 |
-
2015
- 2015-10-08 CN CN201510644802.0A patent/CN106572468B/zh active Active
-
2016
- 2016-02-18 WO PCT/CN2016/074073 patent/WO2016184197A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101146315A (zh) * | 2006-08-03 | 2008-03-19 | 华为技术有限公司 | 许可证文件管理方法、服务器及系统 |
CN101163004A (zh) * | 2006-10-13 | 2008-04-16 | 华为技术有限公司 | 一种实现认证的方法和系统 |
CN101384059A (zh) * | 2008-09-26 | 2009-03-11 | 华为技术有限公司 | 无线通信方法和系统 |
CN101945394A (zh) * | 2009-07-10 | 2011-01-12 | 华为技术有限公司 | 许可证管理方法、装置与系统 |
US20150095237A1 (en) * | 2013-09-30 | 2015-04-02 | Infinera Corp. | License Management System |
Non-Patent Citations (1)
Title |
---|
ZTE: "Consideration on Small Cell Backhaul", 3GPP TSG-RAN WG3 MEETING #81, R3-131368, 23 August 2013 (2013-08-23), XP050719506 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110032834A (zh) * | 2018-01-12 | 2019-07-19 | 厦门雅迅网络股份有限公司 | 系统授权控制方法、终端设备及存储介质 |
CN110032834B (zh) * | 2018-01-12 | 2024-02-27 | 厦门雅迅网络股份有限公司 | 系统授权控制方法、终端设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN106572468B (zh) | 2021-07-30 |
CN106572468A (zh) | 2017-04-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
KR102018971B1 (ko) | 네트워크 액세스 디바이스가 무선 네트워크 액세스 포인트를 액세스하게 하기 위한 방법, 네트워크 액세스 디바이스, 애플리케이션 서버 및 비휘발성 컴퓨터 판독가능 저장 매체 | |
US9294468B1 (en) | Application-level certificates for identity and authorization | |
CN111434087B (zh) | 用于提供通信服务的方法和电子设备 | |
US9699185B2 (en) | Unauthorized device detection method, unauthorized device detection server, and unauthorized device detection system | |
US9537663B2 (en) | Manipulation and restoration of authentication challenge parameters in network authentication procedures | |
US10229291B2 (en) | Method and system for cryptographically enabling and disabling lockouts for critical operations in a smart grid network | |
CN107547571A (zh) | 用于管理访问控制的基于策略的技术 | |
US9807075B2 (en) | Methods for activation of an application on a user device | |
WO2012139528A1 (zh) | 授权方法和终端设备 | |
US10623952B2 (en) | Method and apparatus for authorizing management for embedded universal integrated circuit card | |
CN110069909B (zh) | 一种免密登录第三方系统的方法及装置 | |
KR20150036371A (ko) | 클라우드 서버를 위한 바우처 인가 | |
JP5856352B2 (ja) | デジタル証明書の自動申請方法、装置及びシステム | |
CN104935435A (zh) | 登录方法、终端及应用服务器 | |
CN109831435A (zh) | 一种数据库操作方法、系统及代理服务器和存储介质 | |
US9430638B2 (en) | Authentication method, authentication apparatus and authentication device | |
CN105391705A (zh) | 一种对应用服务进行认证的方法及装置 | |
CN111988262B (zh) | 认证方法、装置及服务器、存储介质 | |
US20210126802A1 (en) | Certificate renewal method, apparatus, system, medium, and device | |
CN114826660A (zh) | 云服务运行方法、电子设备和存储介质 | |
WO2016184197A1 (zh) | 授权信息的调整方法、装置和计算机存储介质 | |
KR101502999B1 (ko) | 일회성 비밀번호를 이용한 본인 인증 시스템 및 방법 | |
US20170359225A1 (en) | Information aggregation method and apparatus and system | |
US11943612B2 (en) | Method and network server for authenticating a communication apparatus | |
US11558202B2 (en) | Network device authentication |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16795684 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 16795684 Country of ref document: EP Kind code of ref document: A1 |