Authentication management method and device applied to cloud card equipment

Abstract

The invention relates to an authentication management method and device applied to cloud card equipment, and the method comprises the steps: transmitting a ping request of a first system for preset times to a network side, so as to simulate the operation of transmitting a service request to the network side; judging whether the number of times of received authentication reaches a preset authentication number threshold value or not in the process of simulating the operation of sending the service request to the network side; and when the number of times of received authentication reaches a preset authentication number threshold, determining that the adopted operator card has an authentication process of frequently initiating a service request, and executing a service request authentication elimination operation. Whether the authentication process of frequently initiating the service request exists or not is determined through active testing, and frequent authentication is eliminated, so that the user experience is improved. According to the authentication management method and device applied to the cloud card equipment, the problem of user network interruption caused by authentication can be reduced, and the user experience is effectively improved.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method and device for authentication management applied to cloud card equipment. Background Art

[0002] Cloud SIM card (i.e. Cloud SIM, which is a virtual SIM card, for ease of explanation, the present invention will refer to it as cloud card for short) technology is widely used in various application scenarios, such as MiFi (i.e. Mobile WIFI, which is a portable broadband wireless device), locators, routers, etc. The main difference between cloud cards and physical cards is that cloud cards are remote authentication, while physical cards are local authentication. Among them, cloud cards have many advantages, such as the ability to switch operator cards at any time, recycle numbers at any time, increase network coverage and reduce costs. However, since cloud cards are remote authentication, authentication must use the data of the ignition card to complete the interaction between the authentication data and the authentication server. This process will have a short data interruption, affecting the user experience. Among them, the ignition card can be composed of a seed card pre-installed in the cloud card device. During the authentication process, the corresponding seed card data is used to complete the interaction between the authentication data and the authentication server.

[0003] Authentication is a verification method initiated by the operator's network side to detect whether the device is legal. Usually, the authentication operation will be performed when the device is first stationed on the network.

[0004] In the prior art, when the device successfully joins the cloud card network, the device and the core network will establish an RRCConnection (full name: Radio Resource Control Connection, also referred to as RRC connection in this application). When the device does not use the network for a period of time, the RRC connection will be released, and the release time is generally 5-20s. During this process, the device will enter an idle state and release the RRC connection. At this time, it is in the RRC idle state (RRCidle is a state of the RRC layer (radio resource control layer), indicating that the terminal currently has no RRC connection with the network, that is, it is in an idle state); and when the device has data traffic, the device re-establishes the RRC Connection and initiates a Service Request to the network side (that is, a service request, a process initiated by the UE (user equipment) when it is in an idle state or needs to establish an access and mobility management function (AMF) connection).

[0005] However, some operators will authenticate the device again (the authentication in this process is referred to as SR authentication in the present invention) when the device re-initiates the Service Request after releasing the RRC connection to verify the legitimacy of the device. For example, when the device has initiated multiple Service Requests to the network side, the core network will re-authenticate the device, and the device can continue to use the network only after the authentication is completed. Although this process will improve security, it will also lead to frequent authentication to a certain extent.

[0006] If there are frequent authentication operations on the operator's network side, the cloud card device will constantly experience network interruptions due to authentication issues, which will lead to a very poor user experience when using the cloud card device. Summary of the invention

[0007] In view of the above-mentioned defects of the prior art, the present invention provides a method and device for authentication management of cloud card devices, which can effectively manage the authentication process of cloud card devices, reduce network interruptions caused by authentication problems due to frequent authentication on the operator network side, effectively improve user experience, and is easy to use.

[0008] In a first aspect, the present invention provides a method for authentication management applied to a cloud card device, the method comprising:

[0009] Sending a ping request preset by the first system a number of times to the network side, and the time interval for each sending of the ping request is the time interval preset by the first system, so as to simulate the operation of sending a service request to the network side;

[0010] Determine whether the number of authentications received during the operation of simulating the service request to the network side reaches a preset authentication number threshold;

[0011] When the number of received authentications reaches a preset authentication number threshold, it is determined that the adopted operator card has an authentication process for frequently initiating service requests, and a service request authentication elimination operation is performed.

[0012] In some embodiments, the service request authentication elimination operation includes:

[0013] Continue to send the ping request to the network side at a time interval preset by the second system; or

[0014] Send a request for replacing the operator card to obtain an operator card that does not have an authentication process that frequently initiates service requests.

[0015] In some embodiments, the first system preset time interval is greater than a system preset release time of a radio resource control connection, and the second preset time interval is shorter than a system preset release time of a radio resource control connection.

[0016] In some embodiments, the method further comprises:

[0017] When the number of received authentications does not reach the preset authentication number threshold, it is determined that the adopted operator card does not have an authentication process for frequently initiating service requests, and the sending of the ping request to the network side is stopped.

[0018] In some embodiments, the operator card with authentication procedures that frequently initiate service requests is recorded, and when the operator card with authentication procedures that frequently initiate service requests is configured again, the service request authentication elimination operation is directly performed.

[0019] In a second aspect, an embodiment of the present invention further provides a device for authentication management applied to a cloud card device, the device comprising:

[0020] A test module is used to perform a frequent authentication process judgment operation, wherein the frequent authentication process judgment operation includes: sending a ping request preset by the first system to the network side, and the time interval for each sending of the ping request is the time interval preset by the first system, so as to simulate the operation of issuing a service request to the network side, and by judging whether the number of authentications received during the process of simulating the operation of issuing a service request to the network side reaches a preset authentication number threshold, it is determined whether the adopted operator card has an authentication process for frequently initiating service requests;

[0021] The service request authentication elimination module is used to execute a service request authentication elimination operation to eliminate the frequently initiated service request authentication process when it is determined that the operator card has frequently initiated service request authentication processes.

[0022] In some embodiments, the service request authentication elimination operation includes:

[0023] Continue to send the ping request to the network side at a time interval preset by the second system; or

[0024] Send a request for replacing the operator card to obtain an operator card that does not have an authentication process that frequently initiates service requests.

[0025] In some embodiments, the first system preset time interval is greater than a system preset release time of a radio resource control connection, and the second preset time interval is shorter than a system preset release time of a radio resource control connection.

[0026] In some embodiments, the apparatus further comprises:

[0027] The recording module is used to record the operator card that has frequently initiated the authentication process of service request determined through testing, so that when the operator card is used again, the service request authentication elimination operation can be directly performed.

[0028] In a third aspect, an embodiment of the present invention further provides a system for authentication management applied to a cloud card device, comprising: at least one processor; a memory coupled to the at least one processor, the memory storing executable instructions, wherein the executable instructions, when executed by the at least one processor, implement the method described in any one of the first aspects above.

[0029] In a fourth aspect, an embodiment of the present invention further provides a chip for executing the method in the first aspect. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip is used to execute the method in the first aspect.

[0030] In a fifth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method described in any one of the first aspects above is implemented.

[0031] In a sixth aspect, an embodiment of the present invention further provides a computer program product, comprising computer program instructions, which enable a computer to execute the method in the first aspect.

[0032] It can be seen that the above technical solution simulates the issuance of a service request to the network side by utilizing the ping request, and actively determines whether the adopted operator card has an authentication process for frequently initiating service requests. When it is determined that the adopted operator card has an authentication process for frequently initiating service requests, the ping request is continuously sent to the network side at a preset time interval of the second system to avoid frequent authentication, thereby solving the problem of user experience being affected by network interruption during the cloud card authentication process.

[0033] The method and device for authentication management applied to cloud card devices can effectively eliminate continuous authentication operations generated by service requests, reduce user network interruption problems caused by authentication, and effectively improve user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The concept, specific structure and technical effects of the present invention will be further described below in conjunction with the accompanying drawings to fully understand the purpose, characteristics and effects of the present invention.

[0035] Figure 1 It is a flowchart of a method for authentication management applied to a cloud card device in one embodiment of the present invention. DETAILED DESCRIPTION

[0036] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0037] It should be noted that, in this document, relational terms such as “first” and “second” are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations.

[0038] When using cloud card devices in the prior art, some cloud cards assigned by operators (also referred to as operator cards in this application) will be encountered. After completing the initial establishment of the wireless resource control connection and releasing it to the idle state, when initiating a service request again, it is necessary to perform authentication again. When the cloud card device uses this type of cloud card assigned by the operator (also referred to as operator card in this application), it will encounter the problem of frequent authentication due to the need to send service requests, which will cause the cloud card device to continuously have network interruptions due to authentication problems, which will in turn cause the user experience of using the cloud card device to be very poor.

[0039] In view of the above problems, the present invention provides a method and device for authentication management applied to cloud card devices to improve user experience. The present invention is further described below in conjunction with specific embodiments:

[0040] In a first aspect, this embodiment provides a method for authentication management applied to a cloud card device, the method comprising:

[0041] Sending a ping request preset by the first system a number of times to the network side, and the time interval for each sending of the ping request is the time interval preset by the first system, so as to simulate the operation of sending a service request to the network side;

[0042] Determine whether the number of authentications received during the operation of simulating the service request to the network side reaches a preset authentication number threshold;

[0043] When the number of authentications received reaches a preset authentication number threshold, it is determined that the adopted operator card has an authentication process for frequently initiating service requests, and the ping request is continuously sent to the network side at a preset time interval of the second system; when the number of authentications received does not reach the preset authentication number threshold, it is determined that the adopted operator card does not have an authentication process for frequently initiating service requests, and the ping request is stopped from being sent to the network side;

[0044] The operator card with the authentication process of frequently initiating service requests is recorded, and when the operator card with the authentication process of frequently initiating service requests is configured again, the ping request is directly continuously sent to the network side according to the preset time interval of the second system.

[0045] In this embodiment, the first system preset time interval is greater than the system preset release time of the radio resource control connection, and the second preset time interval is shorter than the system preset release time of the radio resource control connection.

[0046] Through the authentication management method applied to the cloud card device in this embodiment, it is possible to actively detect whether the operator card has an authentication process that frequently initiates service requests. When it is determined that the adopted operator card has an authentication process that frequently initiates service requests, the ping request can be continuously sent to the network side at a preset time interval of the second system, so that the device will not release the radio resource control connection, eliminate the frequent SR authentication of the operator card (that is, when the device re-initiates the Service Request after releasing the RRC connection, the authentication initiated to the device again) to avoid the subsequent frequent authentication affecting the user experience. At the same time, for the operator card detected that there is no authentication process for frequently initiating service requests, the ping request is stopped from being sent to the network side, thereby reducing the impact on the power consumption of the device and effectively saving power loss. At the same time, in this embodiment, the operator card with the authentication process that frequently initiates service requests is also recorded, so that when the cloud card assigned by the corresponding operator is used again, it is no longer necessary to detect whether there is an authentication process for service requests, but directly send the ping request to the network side at a preset time interval of the second system to avoid repeated detection and improve operation efficiency.

[0047] In order to enable those skilled in the art to better understand the technical solution, the following is a detailed description of the technical solution and the Figure 1 Further explanation of the scheme:

[0048] Step 1: After the device cloud card is online, choose whether to start the SR authentication mechanism according to the server configuration switch. If it is turned on, execute the subsequent step 2 to start the detection task (i.e. start the ping task);

[0049] Step 2: Start a ping test thread, perform a ping test every 30 seconds according to the preset time, and simulate actively initiating a Service Request action (wherein, the ping test frequency can be configured and modified. In this embodiment, the preset time interval of the first system is set to 30 seconds, that is, in the step, a ping request is sent to the network side every 30 seconds to simulate the operation of issuing a service request to the network side);

[0050] Step 3: Perform 20 consecutive ping tests to complete the operation of simulating the sending of a service request to the network side (i.e., in this step, the preset number of times of the first system is set to 20 times, and after 20 ping requests are sent to the network side, the operation of simulating the sending of a service request to the network side is completed). After the ping test is completed, detect whether authentication exceeding the preset number of times is received during the test (i.e., determine whether the number of authentications received during the operation of simulating the sending of a service request to the network side reaches the preset authentication number threshold);

[0051] Step 4: If the number of authentications received reaches the preset authentication number threshold, it means that the operator card has frequent SR authentication (i.e., it is determined that the adopted operator card has an authentication process that frequently initiates service requests), then the continuous ping times are started, and a ping action is performed every 5 seconds according to the preset frequency (i.e., the preset time of the second system in this embodiment is 5 seconds, and the ping request is sent to the network side every 5 seconds) to maintain the RRC Connection state (i.e., the radio resource control connection state) to eliminate the problem of frequent authentication of the operator card;

[0052] If the number of authentications received does not reach the preset authentication threshold, it means that the operator card does not have frequent SR authentication, and the continuous ping test process will not be started to reduce the impact on device power consumption;

[0053] Step 5: If it is detected that a certain operator card must have frequent SR authentication, the next time the device is assigned such a card, the configuration can be sent to directly start a continuous ping test without the need for re-detection (that is, when the device is assigned to the operator's cloud card again, it directly sends the ping request to the network side at a preset time interval of the second system, so that the device will not release the wireless resource control connection, eliminating the frequent SR authentication of the operator card).

[0054] For detailed procedures, please refer to Figure 1As shown, in this embodiment, the operator SR authentication request can be actively triggered through a ping test of a certain frequency (such as greater than the RRC automatic release time of 30 seconds). If the set number of authentications is received within the specified time, it is determined that the operator has frequent SR authentications, and a continuous ping test is started to keep the RRC connection (such as performing a data service once less than the RRC automatic release time of 5 seconds) from being released, thereby eliminating the operator's frequent SR authentication and avoiding subsequent frequent authentications from affecting the user experience. When the present invention is implemented, the operation of simulating the issuance of a service request to the network side can be executed after the operator card is assigned to complete the first network request, so as to promptly determine whether the operator card has frequent authentications. This solution can detect whether the operator card has frequent authentications, and eliminate continuous SR authentications, reduce user network interruptions caused by authentication, and affect the use of the network by cloud card device users, thereby greatly improving the user experience.

[0055] In a second aspect, this embodiment provides a method for authentication management applied to a cloud card device, the method comprising:

[0056] Sending a ping request to the network side a number of times preset by the first system, and the time interval for each sending of the ping request is a time interval preset by the first system, so as to simulate the operation of sending a service request to the network side, wherein the time interval preset by the first system is greater than the release time of the radio resource control connection preset by the system;

[0057] Determine whether the number of authentications received during the operation of simulating the service request to the network side reaches a preset authentication number threshold;

[0058] When the number of authentications received reaches a preset authentication number threshold, it is determined that the adopted operator card has an authentication process that frequently initiates service requests, and an operator card replacement request is sent to obtain an operator card that does not have an authentication process that frequently initiates service requests; (wherein, during specific execution, a request may be sent to the server to request a new operator card to be reassigned);

[0059] The operator cards with authentication processes that frequently initiate service requests are recorded. When the operator card with authentication processes that frequently initiate service requests is configured again, an operator card replacement request is directly sent to obtain an operator card with authentication processes that do not frequently initiate service requests.

[0060] When requesting to replace an operator card, this scheme can implement the replacement of the operator card by checking whether the assigned operator card has an authentication process that frequently initiates service requests each time, and stop checking when an operator card that does not have an authentication process that frequently initiates service requests is obtained. Other methods can also be used to obtain an operator card that does not have an authentication process that frequently initiates service requests.

[0061] The authentication management method applied to cloud card devices can actively initiate a detection of whether the operator card has an authentication process that frequently initiates service requests. When it is determined that the operator card used has an authentication process that frequently initiates service requests, the operator card can be replaced to select an operator card that does not have an authentication process that frequently initiates service requests to achieve communication, thereby avoiding continuous authentication operations caused by service requests, reducing user network interruption problems caused by authentication, and effectively improving user experience.

[0062] In a third aspect, this embodiment provides an apparatus for authentication management applied to a cloud card device, the apparatus comprising:

[0063] A test module is used to perform a frequent authentication process judgment operation, wherein the frequent authentication process judgment operation includes: sending a ping request preset by the first system to the network side, and the time interval for each sending of the ping request is the time interval preset by the first system, so as to simulate the operation of issuing a service request to the network side, and by judging whether the number of authentications received during the process of simulating the operation of issuing a service request to the network side reaches a preset authentication number threshold, it is determined whether the adopted operator card has an authentication process for frequently initiating service requests;

[0064] A service request authentication elimination module, configured to, when it is determined that the operator card has frequently initiated an authentication process for service requests, continuously send the ping request to the network side at a preset time interval of the second system to eliminate the authentication process for the frequently initiated service requests;

[0065] The recording module is used to record the operator card that has the authentication process of frequently initiating service requests determined through testing, so that when the operator card is used again, the service request authentication elimination module can be directly driven to continuously send the ping request to the network side at a preset time interval of the second system.

[0066] In this embodiment, the first system preset time interval is greater than the system preset release time of the radio resource control connection, and the second preset time interval is shorter than the system preset release time of the radio resource control connection.

[0067] The technical solution in this embodiment can effectively realize active discovery of frequent authentication and avoid frequent authentication, thereby solving the problem of network interruption affecting user experience during cloud card authentication. At the same time, when it is determined that the adopted operator card does not have an authentication process that frequently initiates service requests, stop sending ping requests to reduce the loss of terminal power. And by setting a recording module, the operator card that has an authentication process that frequently initiates service requests determined by testing is recorded, so that when the operator card is used again, the service request authentication elimination module can be directly driven to continuously send the ping request to the network side at the preset time interval of the second system, without the need for further detection operations.

[0068] In a fourth aspect, the embodiment provides an apparatus for authentication management applied to a cloud card device, the apparatus comprising:

[0069] A test module is used to perform a frequent authentication process judgment operation, wherein the frequent authentication process judgment operation includes: sending a ping request preset by the first system to the network side, and the time interval for each sending of the ping request is the time interval preset by the first system, so as to simulate the operation of issuing a service request to the network side, and by judging whether the number of authentications received during the process of simulating the operation of issuing a service request to the network side reaches a preset authentication number threshold, it is determined whether the adopted operator card has an authentication process for frequently initiating service requests;

[0070] A service request authentication elimination module is used to send an operator card replacement request when it is determined that the operator card has an authentication process that frequently initiates service requests, and obtain an operator card that does not have an authentication process that frequently initiates service requests, so as to eliminate the authentication process of the frequently initiated service requests;

[0071] The recording module is used to record the operator card with the authentication process of frequently initiating service requests determined through testing, so that when the operator card is used again, an operator card replacement request can be directly sent to obtain an operator card with no authentication process of frequently initiating service requests.

[0072] The device for authentication management applied to cloud card devices can actively perform detection on whether there are frequent authentication processes for operator cards, and when frequent authentication processes are detected, by replacing the operator card, select an operator card that does not have an authentication process that frequently initiates service requests to achieve communication, thereby avoiding continuous authentication operations caused by service requests, reducing user network interruption problems caused by authentication, and effectively improving user experience.

[0073] In a fifth aspect, the present invention further provides a system for authentication management applied to a cloud card device, comprising:

[0074] At least one processor; a memory coupled to the at least one processor, the memory storing executable instructions, wherein the executable instructions, when executed by the at least one processor, implement the method of the first aspect of the present invention.

[0075] This embodiment provides a system for authentication management applied to a cloud card device, including: at least one processor; and a memory coupled to the at least one processor. The processor and the memory may be provided separately or integrated together.

[0076] For example, the memory may include a random access memory, a flash memory, a read-only memory, a programmable read-only memory, a non-volatile memory or a register, etc. The processor may be a central processing unit (CPU), etc. or a graphic processing unit (GPU). The memory may store executable instructions. The processor may execute the executable instructions stored in the memory to implement the various processes described herein.

[0077] It can be understood that the memory in this embodiment can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a ROM (Read-Only Memory), a PROM (Programmable ROM), an EPROM (Erasable PROM), an EEPROM (Electrically EPROM), or a flash memory. The volatile memory can be a RAM (Random Access Memory), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as SRAM (Static RAM), DRAM (Dynamic RAM), SDRAM (Synchronous DRAM), DDR SDRAM (Double Data Rate SDRAM), ESDRAM (Enhanced SDRAM), SLDRAM (Synchlink DRAM), and DRRAM (Direct Rambus RAM). The memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0078] In some embodiments, the memory stores the following elements, upgrade packages, executable units or data structures, or a subset thereof, or an extended set thereof: an operating system and an application program.

[0079] The operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application program includes various application programs, which are used to implement various application services. The program for implementing the method of the embodiment of the present invention can be included in the application program.

[0080] In an embodiment of the present invention, the processor calls a program or instruction stored in a memory, specifically, a program or instruction stored in an application program, and the processor is used to execute the method steps provided in the first aspect.

[0081] In a sixth aspect, an embodiment of the present invention further provides a chip for executing the method in the first aspect. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip is used to execute the method in the first aspect.

[0082] In addition, in a seventh aspect, the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method of the first aspect of the present invention are implemented.

[0083] For example, machine-readable storage media may include, but are not limited to, various known and unknown types of non-volatile memory.

[0084] In an eighth aspect, an embodiment of the present invention further provides a computer program product, comprising computer program instructions, which enable a computer to execute the method in the first aspect.

[0085] It will be appreciated by those skilled in the art that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0086] In the embodiments of the present application, the disclosed systems, devices and methods can be implemented in other ways. For example, the division of units is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system. In addition, the coupling between the various units can be direct coupling or indirect coupling. In addition, the various functional units in the embodiments of the present application can be integrated into a processing unit, or can be separate physical existences, etc.

[0087] It should be understood that in the various embodiments of the present application, the size of the serial number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0088] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a machine-readable storage medium. Therefore, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a machine-readable storage medium, which can include several instructions to enable an electronic device to perform all or part of the technical solution described in the embodiments of the present application. The above-mentioned storage medium may include various media that can store program codes, such as ROM, RAM, removable disk, hard disk, magnetic disk or optical disk.

[0089] The present invention simulates sending a service request to the network side by using a ping request to determine whether the adopted operator card has an authentication process that frequently initiates service requests. When it is determined that the adopted operator card has an authentication process that frequently initiates service requests, the ping request is continuously sent to the network side at a preset time interval of the second system to avoid frequent authentication, thereby solving the problem of user experience being affected by network interruption during the cloud card authentication process. The method and device for authentication management applied to cloud card devices can effectively eliminate continuous authentication operations caused by service requests, reduce user network interruption problems caused by authentication, and effectively improve user experience.

[0090] The above contents are only specific implementation methods of the present application, and the protection scope of the present application is not limited thereto. Those skilled in the art may make changes or substitutions within the technical scope disclosed in the present application, and these changes or substitutions shall be within the protection scope of the present application.

Claims

1. A method for authentication management applied to cloud card devices, characterized in that: The method comprises: Sending a ping request preset by the first system a number of times to the network side, and the time interval for each sending of the ping request is the time interval preset by the first system, so as to simulate the operation of sending a service request to the network side; Determine whether the number of authentications received during the operation of simulating the service request to the network side reaches a preset authentication number threshold; When the number of received authentications reaches a preset authentication number threshold, it is determined that the adopted operator card has an authentication process for frequently initiating service requests, and a service request authentication elimination operation is performed.

2. The method for authentication management applied to cloud card devices according to claim 1, characterized in that: The service request authentication elimination operation includes: Continue to send the ping request to the network side at a time interval preset by the second system; or Send a request for replacing the operator card to obtain an operator card that does not have an authentication process that frequently initiates service requests.

3. The method for authentication management applied to cloud card devices according to claim 2, characterized in that: The first system preset time interval is greater than a system preset release time of a radio resource control connection, and the second preset time interval is shorter than a system preset release time of a radio resource control connection.

4. The method for authentication management applied to cloud card devices according to claim 1, characterized in that: The method further comprises: When the number of received authentications does not reach the preset authentication number threshold, it is determined that the adopted operator card does not have an authentication process for frequently initiating service requests, and the sending of the ping request to the network side is stopped.

5. The method for authentication management applied to cloud card devices according to claim 1, characterized in that: The operator card with the authentication process of frequently initiating service requests is recorded, and when the operator card with the authentication process of frequently initiating service requests is configured again, the service request authentication elimination operation is directly performed.

6. A device for authentication management of cloud card equipment, characterized in that: The device comprises: A test module is used to perform a frequent authentication process judgment operation, wherein the frequent authentication process judgment operation includes: sending a ping request preset by the first system to the network side, and the time interval for each sending of the ping request is the time interval preset by the first system, so as to simulate the operation of issuing a service request to the network side, and by judging whether the number of authentications received during the process of simulating the operation of issuing a service request to the network side reaches a preset authentication number threshold, it is determined whether the adopted operator card has an authentication process for frequently initiating service requests; The service request authentication elimination module is used to execute a service request authentication elimination operation to eliminate the frequently initiated service request authentication process when it is determined that the operator card has frequently initiated service request authentication processes.

7. The device for authentication management applied to cloud card equipment according to claim 6, characterized in that: The service request authentication elimination operation includes: Continue to send the ping request to the network side at a time interval preset by the second system; or Send a request for replacing the operator card to obtain an operator card that does not have an authentication process that frequently initiates service requests.

8. The device for authentication management applied to cloud card equipment according to claim 7, characterized in that: The first system preset time interval is greater than a system preset release time of a radio resource control connection, and the second preset time interval is shorter than a system preset release time of a radio resource control connection.

9. The device for authentication management applied to cloud card equipment according to claim 6, characterized in that: The device also includes: The recording module is used to record the operator card that has frequently initiated the authentication process of service request determined through testing, so that when the operator card is used again, the service request authentication elimination operation can be directly performed.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method as described in any one of claims 1 to 5 are implemented.

Images