Iot card number conversion method, device and equipment and storage medium

Abstract

The application provides an Internet of Things card number conversion method, device, equipment and storage medium. The method comprises the following steps: receiving a first task request of a target Internet of Things device; performing legality verification on the target Internet of Things device according to the first task request to obtain a verification result, wherein the verification result comprises verification failure and verification success; if the verification result of the target Internet of Things device is verification success, a preset coding strategy is obtained; a target Internet of Things card number corresponding to the target Internet of Things device is determined according to the preset coding strategy and the first task request; and the first task request is processed according to the target Internet of Things card number. The method improves the security of data transmission between Internet of Things devices.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, and in particular to an IoT card number conversion method, apparatus, device, and storage medium. Background Technology

[0002] The Internet of Things (IoT) technology has been widely applied in various industries, and the number of IoT users is increasing rapidly. IoT technology can be used to realize data transmission between IoT devices.

[0003] In existing technologies, IoT devices have a unique IoT SIM card number, which can be used to identify IoT devices and enable data transmission between them. However, during information exchange between IoT devices, the IoT SIM card number is exposed on the network, making the IoT devices vulnerable to attacks and resulting in poor security for data transmission between them. Summary of the Invention

[0004] This application provides an IoT card number conversion method, apparatus, device, and storage medium to solve the technical problem of poor security in data transmission between IoT devices.

[0005] Firstly, this application provides an IoT card number conversion method, applied to operator equipment, including:

[0006] Receive the first task request from the target IoT device;

[0007] The target IoT device is validated according to the first task request, and a validation result is obtained, which includes validation failure and validation success.

[0008] If the verification result of the target IoT device is successful, then the preset encoding strategy is obtained;

[0009] Based on the preset encoding strategy and the first task request, the target IoT card number corresponding to the target IoT device is determined;

[0010] Based on the target IoT card number, the first task request is processed.

[0011] In one possible implementation, the first task request includes task request information and device information of the target IoT device; determining the target IoT card number corresponding to the target IoT device according to the preset encoding strategy and the first task request includes:

[0012] Determine whether a first IoT card number exists in the device information. The first IoT card number is used to enable data interaction between target IoT devices.

[0013] If it exists, the target IoT card number is determined according to the preset encoding strategy and the first IoT card number;

[0014] If it does not exist, the target IoT card number is determined according to the preset encoding strategy.

[0015] In one possible implementation, determining the target IoT card number based on the preset encoding strategy and the first IoT card number includes:

[0016] Determine whether the encoding rule of the first IoT card number conforms to the preset encoding strategy;

[0017] If the conditions are met, the target IoT card number is determined based on the first IoT card number;

[0018] If it does not meet the requirements, the target IoT card number is determined according to the preset encoding strategy.

[0019] In one possible implementation, determining the target IoT card number based on the first IoT card number includes:

[0020] Multiple card number conversion information is retrieved from memory, including historical IoT card numbers, historical locations, and historical request times.

[0021] Based on the first IoT card number, determine the first card number conversion information from the plurality of card number conversion information;

[0022] The target IoT card number is determined based on the device information and the first card number conversion information.

[0023] In one possible implementation, the device information includes a first IoT SIM card number, current location, and current request time; determining the target IoT SIM card number based on the device information and the first SIM card number conversion information includes:

[0024] The first historical location and the first historical request time of the target IoT device are determined from the first card number conversion information;

[0025] If the current location is the same as the first historical location, then the target IoT card number is determined based on the current request time and the first historical request time.

[0026] If the current location and the first historical location are not the same, the target IoT card number is determined according to the preset encoding strategy.

[0027] In one possible implementation, determining the target IoT card number based on the current request time and the first historical request time includes:

[0028] The request interval duration is determined based on the current request time and the first historical request time.

[0029] If the request interval is longer than a preset duration, the target IoT card number is determined according to the preset encoding strategy.

[0030] If the request interval is less than or equal to a preset duration, then the historical IoT card number in the first card number conversion information is determined as the target IoT card number.

[0031] In one possible implementation, the preset encoding strategy includes multiple parameters to be acquired and preset parameters; the device information also includes an initial IoT SIM card number; determining the target IoT SIM card number according to the preset encoding strategy includes:

[0032] Obtain parameter data of the plurality of parameters to be acquired from the initial IoT card number;

[0033] Obtain the parameter data of the preset parameters;

[0034] According to the preset encoding strategy, the parameter data of the multiple parameters to be acquired and the parameter data of the preset parameters are concatenated to obtain the target IoT card number.

[0035] In one possible implementation, the target IoT device is validated according to the first task request to obtain a validation result, including:

[0036] Obtain the certification information form for IoT devices;

[0037] If the initial IoT card number of the target IoT device exists in the authentication information table, the verification result of the legality verification of the target IoT device is successful.

[0038] If the initial IoT card number of the target IoT device is not found in the authentication information table, the verification result of the legality verification of the target IoT device is verification failure.

[0039] In one possible implementation, after determining the target IoT card number corresponding to the target IoT device according to the first task request, the method further includes:

[0040] Based on the target IoT card number and the device information, update the first conversion information of the target IoT device in memory;

[0041] If the target IoT device contains a first IoT card number, then the target IoT device deletes the first IoT card number and stores the target IoT card number.

[0042] Secondly, this application provides an IoT card number conversion device, applied to operator equipment, including a receiving module, a verification module, an acquisition module, a determination module, and a task processing module:

[0043] The receiving module is used to receive a first task request from the target IoT device.

[0044] The verification module is used to perform legality verification on the target IoT device according to the first task request and obtain a verification result, which includes verification failure and verification success.

[0045] The acquisition module is used to acquire a preset encoding strategy if the verification result of the target IoT device is successful.

[0046] The determining module is used to determine the target IoT card number corresponding to the target IoT device based on the preset encoding strategy and the first task request.

[0047] The task processing module is used to process the first task request based on the target IoT card number.

[0048] In one possible implementation, the first task request includes task request information and device information of the target IoT device; the determining module is specifically used for:

[0049] Determine whether a first IoT card number exists in the device information. The first IoT card number is used to enable data interaction between target IoT devices.

[0050] If it exists, the target IoT card number is determined according to the preset encoding strategy and the first IoT card number;

[0051] If it does not exist, the target IoT card number is determined according to the preset encoding strategy.

[0052] In one possible implementation, the determining module is specifically used for:

[0053] Determine whether the encoding rule of the first IoT card number conforms to the preset encoding strategy;

[0054] If the conditions are met, the target IoT card number is determined based on the first IoT card number;

[0055] If it does not meet the requirements, the target IoT card number is determined according to the preset encoding strategy.

[0056] In one possible implementation, the determining module is specifically used for:

[0057] Multiple card number conversion information is retrieved from memory, including historical IoT card numbers, historical locations, and historical request times.

[0058] Based on the first IoT card number, determine the first card number conversion information from the plurality of card number conversion information;

[0059] The target IoT card number is determined based on the device information and the first card number conversion information.

[0060] In one possible implementation, the device information includes a first IoT card number, current location, and current request time; the determining module is specifically used for:

[0061] The first historical location and the first historical request time of the target IoT device are determined from the first card number conversion information;

[0062] If the current location is the same as the first historical location, then the target IoT card number is determined based on the current request time and the first historical request time.

[0063] If the current location and the first historical location are not the same, the target IoT card number is determined according to the preset encoding strategy.

[0064] In one possible implementation, the determining module is specifically used for:

[0065] The request interval duration is determined based on the current request time and the first historical request time.

[0066] If the request interval is longer than a preset duration, the target IoT card number is determined according to the preset encoding strategy.

[0067] If the request interval is less than or equal to a preset duration, then the historical IoT card number in the first card number conversion information is determined as the target IoT card number.

[0068] In one possible implementation, the preset encoding strategy includes multiple parameters to be acquired and preset parameters; the device information also includes an initial IoT card number; the determining module is specifically used for:

[0069] Obtain parameter data of the plurality of parameters to be acquired from the initial IoT card number;

[0070] Obtain the parameter data of the preset parameters;

[0071] According to the preset encoding strategy, the parameter data of the multiple parameters to be acquired and the parameter data of the preset parameters are concatenated to obtain the target IoT card number.

[0072] In one possible implementation, the verification module is specifically used for:

[0073] Obtain the certification information form for IoT devices;

[0074] If the initial IoT card number of the target IoT device exists in the authentication information table, the verification result of the legality verification of the target IoT device is successful.

[0075] If the initial IoT card number of the target IoT device is not found in the authentication information table, the verification result of the legality verification of the target IoT device is verification failure.

[0076] In one possible implementation, the device further includes an update module and a deletion module:

[0077] The update module is used to update the first conversion information of the target IoT device in memory according to the target IoT card number and the device information;

[0078] The deletion module is used to delete the first IoT card number from the target IoT device and store the target IoT card number if the first IoT card number exists in the target IoT device.

[0079] Thirdly, this application provides an electronic device, including: a memory and a processor;

[0080] The memory stores computer-executed instructions;

[0081] The processor executes computer execution instructions stored in the memory, causing the processor to perform the IoT card number conversion method according to any one of the first aspects.

[0082] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the IoT card number conversion method described in any of the first aspects.

[0083] The IoT card number conversion method, apparatus, device, and storage medium provided in this application can verify the legitimacy of the target IoT device after obtaining the first task request of the target IoT device, and determine the target IoT card number based on the preset encoding strategy and the first task request. The conversion of the IoT card number of the target IoT device realizes the encryption of the IoT card number and improves the security of data transmission between IoT devices. Attached Figure Description

[0084] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0085] Figure 1 A schematic diagram illustrating the application scenarios provided in the embodiments of this application;

[0086] Figure 2 A flowchart illustrating an IoT card number conversion method provided in this application embodiment;

[0087] Figure 3 A flowchart illustrating another IoT card number conversion method provided in this application embodiment;

[0088] Figure 4 A schematic diagram illustrating a process for determining a target IoT card number, provided as an embodiment of this application;

[0089] Figure 5 A schematic diagram illustrating another process for determining a target IoT card number provided in an embodiment of this application;

[0090] Figure 6 This is a schematic diagram of the structure of the IoT card number conversion method provided in the embodiments of this application;

[0091] Figure 7 This is a schematic diagram of the structure of an IoT card number conversion device provided in an embodiment of this application;

[0092] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0093] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0094] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0095] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0096] Figure 1 This is a schematic diagram illustrating an application scenario provided in an embodiment of this application. Please refer to [link / reference]. Figure 1 This includes multiple IoT devices 101 and carrier equipment 102.

[0097] The IoT device 101 can be divided into active IoT devices and passive IoT devices. Passive IoT devices do not have power cords or built-in batteries; for example, they can obtain energy from light and radio waves. The IoT device 101 may include sensors, actuators, smart home devices, and smart city devices. Each IoT device 101 has its corresponding initial IoT SIM card number. The initial IoT SIM card number can be converted by the operator equipment 102 to obtain a target IoT SIM card number for each IoT device 101. Data transmission between IoT devices 101 can be achieved using the target IoT SIM card number.

[0098] The operator equipment 102 can receive the first task request from the IoT device 101, verify the legitimacy of the IoT device 101 according to the first task request, and after obtaining the preset encoding policy, determine the target IoT card number of the IoT device 101 according to the preset encoding policy and the first task request, and process the first task request according to the target IoT card number.

[0099] In existing technologies, IoT devices have a unique IoT SIM card number, which can be used to identify IoT devices and enable data transmission between them. However, during information exchange between IoT devices, the IoT SIM card number is exposed on the network, making the IoT devices vulnerable to attacks and resulting in poor security for data transmission between them.

[0100] In this embodiment of the application, after obtaining the first task request of the target IoT device, the legitimacy of the target IoT device can be verified, and the target IoT card number can be determined by a preset encoding strategy and the first task request. The conversion of the IoT card number of the target IoT device realizes the encryption of the IoT card number and improves the security of data transmission between IoT devices.

[0101] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0102] Figure 2 This is a flowchart illustrating an IoT card number conversion method provided in an embodiment of this application. Please refer to... Figure 2 The method may include:

[0103] S201, Receive the first task request from the target IoT device.

[0104] The execution entity in this application embodiment can be a carrier device or an IoT SIM card conversion device installed in the carrier device. The IoT SIM card conversion device can be implemented by software or by a combination of software and hardware.

[0105] The target IoT device can generate a first task request and send the first task request to the operator equipment. The first task request may include task request information and device information of the target IoT device.

[0106] The device information may include an initial IoT card number, a first IoT card number, the current location, and the current request time. The initial IoT card number is a unique device identifier for the target IoT device. The first IoT card number can be a target IoT card number generated before the current time of the target IoT device. Data transmission between IoT devices is conducted through the first IoT card number. The first IoT card number may not be present in the device information of the target IoT device.

[0107] For example, suppose the target IoT device is IoT device 1, and suppose the first task request of IoT device 1 is task request 1. Task request 1 can be received. Task request 1 may include task request information and device information of IoT device 1.

[0108] S202. Verify the legitimacy of the target IoT device according to the first task request and obtain the verification result.

[0109] Before performing a task, the target IoT device can be securely registered with the carrier's equipment to enable data exchange between IoT devices through the carrier's equipment.

[0110] Verification results can include verification failure and verification success. If the target IoT device successfully registers with the operator's equipment, the verification result for the target IoT device is verification success; if the target IoT device fails to register with the operator's equipment or registration fails, the verification result is verification failure.

[0111] S203. If the verification result of the target IoT device is successful, then obtain the preset encoding strategy.

[0112] The preset encoding strategy can be configured according to the user's needs, and the target IoT card number can be generated according to the preset encoding strategy.

[0113] The generation method of the target IoT card number can be updated by modifying the preset encoding strategy, which increases the flexibility of IoT card number conversion; if the target IoT card number can be simplified by the preset encoding strategy, the capability loss of the target IoT card number will be reduced, which is suitable for passive IoT devices.

[0114] S204. Determine the target IoT card number corresponding to the target IoT device according to the preset coding strategy and the first task request.

[0115] The target IoT card number can be determined in two ways:

[0116] Method 1: If the device information contains a first IoT card number, then determine the target IoT card number based on the first IoT card number.

[0117] The validity of the first IoT card number can be verified. If the verification is successful, the first IoT card number is determined as the target IoT card number. If the verification fails, the target IoT card number is regenerated.

[0118] Method 2: If the first IoT card number is not found in the device information, the target IoT card number is determined according to the preset encoding strategy.

[0119] For example, assuming the target IoT device is IoT device 1, the first task request received from IoT device 1 is task request 1. If the device information in task request 1 contains a first IoT card number, then the target IoT card number is determined based on the first IoT card number. If the device information in task request 1 does not contain a first IoT card number, then a preset encoding strategy is obtained, and the target IoT card number is determined based on the preset encoding strategy.

[0120] S205. Process the first task request based on the target IoT card number.

[0121] The target IoT device can process the task request information in the first task request based on the target IoT card number.

[0122] For example, assuming the target IoT device is IoT device 1 and the task request information is sending data 1, after receiving data 1, IoT device 2 can obtain the target IoT card number 1 of IoT device 1. IoT device 2 can use the target IoT card number 1 to send feedback information to IoT device 1. Similarly, assuming the target IoT card number of IoT device 2 is target IoT card number 2, then IoT device 1 can use the target IoT card number 2 to identify IoT device 2 and send information to IoT device 2.

[0123] The IoT SIM card number conversion method provided in this application can verify the legitimacy of the target IoT device after receiving a first task request from the target IoT device. If the verification result of the target IoT device is successful, the target IoT SIM card number is determined according to a preset encoding strategy and the first task request. Based on the target IoT SIM card number, the first task request is processed, which can improve the security of data transmission between IoT devices. Furthermore, the generated target IoT SIM card number can be modified by changing the preset encoding strategy, thereby improving the flexibility of IoT SIM card number conversion.

[0124] Figure 3 This is a flowchart illustrating another IoT card number conversion method provided in an embodiment of this application. Please refer to... Figure 2 The method may include:

[0125] S301, Receive the first task request from the target IoT device.

[0126] The execution process of S301 can be found in the execution process of S201, and will not be repeated here.

[0127] S302. Obtain the certification information form of the IoT device.

[0128] The authentication information table may include the initial IoT SIM card number of the IoT device and the authentication information of each IoT device. For example, the authentication information table may be as shown in Table 1.

[0129] Table 1

[0130] Initial IoT SIM card number 1 Authentication Information 1 Initial IoT card number 2 Authentication Information 2 Initial IoT SIM card number 3 Authentication Information 3

[0131] S303. If the initial IoT card number of the target IoT device exists in the authentication information table, the verification result of the legality verification of the target IoT device is successful.

[0132] For example, assuming the initial IoT card number of the target IoT device is initial IoT card number 2, and assuming the authentication information table is as shown in Table 1, and the initial IoT card number of the target IoT device exists in the authentication information table, then the verification result of the legality verification of the target IoT device is successful.

[0133] S304. If the initial IoT card number of the target IoT device is not found in the authentication information table, the verification result of the legality verification of the target IoT device is verification failure.

[0134] For example, assuming the initial IoT card number of the target IoT device is initial IoT card number 4, and assuming the authentication information table is as shown in Table 1, and the initial IoT card number of the target IoT device does not exist in the authentication information table, then the verification result of the legality verification of the target IoT device is verification failure.

[0135] S305. If the verification result of the target IoT device is successful, then determine whether the first IoT card number exists in the device information.

[0136] The first IoT card number can be used to enable data interaction between IoT devices.

[0137] If the target IoT device sent a task request before the current time, the first IoT card number may exist in the device information of the target IoT device; if it did not send a task request before the current time, the first IoT card number will not exist in the device information of the target IoT device.

[0138] Optionally, after the task request is processed, the target IoT device can delete the stored first IoT card number, so that the first IoT card number will not exist in the device information.

[0139] S306. If it exists, the target IoT card number is determined according to the preset encoding strategy and the first IoT card number.

[0140] The execution process of S306 can be described in the following embodiments, and will not be repeated here.

[0141] S307. If it does not exist, determine the target IoT card number according to the preset encoding strategy.

[0142] The execution process of S307 can be described in the following embodiments, and will not be repeated here.

[0143] S308. Process the first task request based on the target IoT card number.

[0144] The execution process of S301 can be found in the execution process of S204, and will not be repeated here.

[0145] S309. Based on the target IoT card number and device information, update the first card number conversion information of the target IoT device in memory.

[0146] After determining the target IoT card number, the first card number conversion information of the target IoT device in the memory of the operator's equipment can be updated to the target IoT card number.

[0147] It can also send the target IoT card number to the target IoT device, which can then use the target IoT card number for data transmission and communication.

[0148] S310. If the first IoT card number exists in the target IoT device, delete the first IoT card number from the target IoT device and store the target IoT card number.

[0149] For example, assuming that the device information in the first task request includes the first IoT card number 1, then the target IoT device contains the first IoT card number 1. After determining that the target IoT device corresponds to the target IoT card number 1, the first IoT card number 1 in the target IoT device is deleted, and the target IoT card number 1 is stored.

[0150] The IoT SIM card conversion method provided in this application can verify the legitimacy of the target IoT device based on the authentication information table, and determine the target IoT SIM card number based on the device information of the target IoT device, thereby improving the security of data transmission between IoT devices.

[0151] For ease of understanding, based on the above embodiments, the following, in conjunction with... Figure 4 The first step of the execution process of determining the target IoT card number based on the preset encoding strategy and the first IoT card number in step S306 is explained.

[0152] Figure 4 This is a schematic diagram illustrating a process for determining a target IoT card number, provided as an embodiment of this application. Please refer to [link / reference]. Figure 4 The method may include:

[0153] S401. Determine whether the encoding rule of the first IoT card number conforms to the preset encoding strategy.

[0154] If the preset encoding strategy has been reconfigured, the first IoT card number will not conform to the preset encoding strategy; if the preset encoding strategy has not been reconfigured, the first IoT card number will not conform to the preset encoding strategy.

[0155] S402. If the conditions are met, retrieve multiple card number conversion information from memory.

[0156] The card number conversion information may include historical IoT card numbers, historical locations, and historical request times.

[0157] For example, suppose that the conversion information for multiple card numbers can be as shown in Table 2.

[0158] Table 2

[0159] Card number conversion information 1 IoT card number 1 Position 1 Request time 1 Card number conversion information 2 IoT card number 2 Position 2 Request time 2 Card number conversion information 3 IoT card number 3 Position 3 Request time 3

[0160] S403. Based on the first IoT card number, determine the first card number conversion information from multiple card number conversion information.

[0161] For example, assuming the first IoT card number is IoT card number 3, and assuming multiple card number conversion information can be as shown in Table 2, then the first card number conversion information can be determined to be card number conversion information 3.

[0162] S404. Determine the first historical location and the first historical request time of the target IoT device in the first card number conversion information.

[0163] For example, assuming the first card number conversion information is card number conversion information 3, the first historical position can be determined as position 3 and the first historical request time is request time 3 from the multiple card number conversion information shown in Table 2.

[0164] S405. If the current position and the first historical position are the same, then determine the request interval duration based on the current request time and the first historical request time.

[0165] For example, assuming the current position is position 3, the first historical position is position 3, the current position and the first historical position are the same, and the current request time is 13:15:23 on November 23, 2020, and the first historical request time is 13:16:00 on November 23, 2020, then the request interval duration can be determined to be 37 seconds.

[0166] S406. If the requested interval is longer than the preset duration, the target IoT card number is determined according to the preset encoding strategy.

[0167] For example, assuming the request interval is 37 seconds and the preset duration is 30 seconds, that is, the request interval is longer than the preset duration, then the preset encoding strategy can be obtained.

[0168] The execution process of S406 can be described in the following embodiments, and will not be repeated here.

[0169] S407. If the requested interval is less than or equal to the preset interval, the historical IoT card number in the first card number conversion information shall be determined as the target IoT card number.

[0170] For example, assuming the request interval is 20 seconds and the preset duration is 30 seconds (meaning the request interval is less than the preset duration), and assuming the historical IoT card number is IoT card number 1, then IoT card number 1 will be determined as the target IoT card number.

[0171] S408. If the current location is different from the first historical location, the target IoT card number is determined according to the preset coding strategy.

[0172] For example, assuming the current position is position 2 and the first historical position is position 3, that is, the current position and the first historical position are not the same, then the preset encoding strategy can be obtained.

[0173] S409. If not, determine the target IoT card number according to the preset coding strategy.

[0174] The execution process of S408-S409 can be described in the following embodiments, and will not be repeated here.

[0175] The IoT card number conversion method provided in this application embodiment can determine the first historical location and the first historical request time of the target IoT device from multiple card number conversion information in memory. If the first historical location is the same as the current location and the request interval does not exceed a preset time, the historical IoT card number can be determined as the target IoT card number. If either the location or the time condition is not met, the target IoT card number is regenerated according to a preset encoding strategy, which can improve the security of data transmission between IoT devices.

[0176] For ease of understanding, based on the above embodiments, the following, in conjunction with... Figure 5 The first step of the execution process of determining the target IoT card number according to the preset encoding strategy in steps S307, S406, S408 and S409 is explained.

[0177] Figure 5 This is a schematic diagram illustrating another process for determining a target IoT card number, provided as an embodiment of this application. Please refer to... Figure 4 The method may include:

[0178] S501. Obtain parameter data for multiple parameters to be acquired from the initial IoT card number.

[0179] The initial IoT card number may include multiple parameters and the corresponding parameter data for each parameter.

[0180] Multiple parameters to be acquired can be key parameters of the initial IoT card number. Determining the target IoT card number based on the key parameters can make the target IoT card number shorter than the initial IoT card number, thereby reducing energy consumption in data transmission between IoT devices.

[0181] S502. Obtain the parameter data of the preset parameters.

[0182] Multiple preset data of preset parameters can be stored in memory. A preset data can be randomly selected from the multiple preset data and used as the parameter data of the preset parameters.

[0183] Once the preset data is used as parameter data for a target IoT card number, the preset data is locked and cannot be used as parameter data for the next target IoT card number until the target IoT card number containing the preset data is deleted or updated, at which point the preset data is unlocked.

[0184] For example, suppose there are three preset data sets, designated as preset data 1-3. If the parameter data for the target IoT SIM card number 1 of IoT device 1 is preset data 1, then preset data 1 is locked. If the target IoT device is IoT device 2, then preset data 2 or preset data 3 can be selected as the parameter data. If preset data 2 is selected as the parameter data for the target IoT SIM card number 2 of IoT device 2, then preset data 2 is locked. If the target IoT SIM card number 1 is deleted, then preset data 1 can be unlocked, and the next target IoT device can select its parameter data from preset data 1 and preset data 3.

[0185] At least one preset parameter can be included in the target IoT card number.

[0186] S503. According to the preset encoding strategy, the parameter data of multiple parameters to be acquired and the parameter data of the preset parameters are concatenated to obtain the target IoT card number.

[0187] The preset encoding strategy can include the concatenation position information of parameter data of multiple parameters to be acquired and the parameter data of preset parameters.

[0188] Based on the splicing position information, the parameter data of multiple parameters to be acquired and the parameter data of preset parameters can be spliced ​​together to obtain the target IoT card number.

[0189] For example, suppose there are 3 parameters to be acquired, namely parameters 1-3, and the preset parameter is preset parameter 1. Suppose the splicing position information is parameter 1 / parameter 2 / preset parameter / parameter 3, and the parameter data corresponding to parameter 1 is parameter data 1, the parameter data corresponding to parameter 2 is parameter data 2, the parameter data corresponding to parameter 3 is parameter data 3, and the parameter data of the preset parameter is preset data 2. Then the target IoT card number can be determined as parameter data 1 / parameter data 2 / preset data 2 / parameter data 3.

[0190] The parameters to be obtained may include carrier code, international code, domestic code, year, and province code.

[0191] Preset parameters may include check digit number and sequence code, etc.

[0192] The IoT card number conversion method provided in this application embodiment can obtain parameter data of multiple parameters to be obtained from the initial IoT card number of the target IoT device, and concatenate the parameter data of multiple parameters to be obtained and the parameter data of the preset parameters according to the preset encoding strategy to obtain the target IoT card number, which can improve the flexibility of IoT card number conversion.

[0193] Figure 6 This is a schematic diagram illustrating the structure of the IoT card number conversion method provided in this application embodiment. Please refer to... Figure 6 This includes target IoT devices and carrier equipment. The target IoT device can send a first task request to the carrier equipment, which can then verify the legitimacy of the target IoT device based on the first task request. Upon successful verification, a verification success message is sent to the target IoT device.

[0194] The first task request includes device information. If the device information contains a first IoT SIM card number, the first SIM card number conversion information of the target IoT device is determined. If the first SIM card number conversion information is correct, the first task request is processed. If the first SIM card number conversion information is incorrect, the target IoT SIM card number is determined according to a preset encoding strategy, the target IoT SIM card number is sent to the target IoT device, the first IoT SIM card number is deleted from the target IoT device and stored, the first SIM card number conversion information is updated in the operator's equipment, and the first task request is processed.

[0195] If the first IoT card number is not found in the device information, the target IoT card number is determined according to the preset encoding strategy and sent to the target IoT device. The target IoT device stores the target IoT card number, and the operator equipment processes the first task request based on the target IoT card number.

[0196] Figure 7 This is a schematic diagram of an IoT card number conversion device provided in an embodiment of this application. Please refer to [link / reference]. Figure 7 The IoT card number conversion device 10 may include a receiving module 11, a verification module 12, an acquisition module 13, a determination module 14, and a task processing module 15.

[0197] The receiving module 11 is used to receive the first task request from the target IoT device;

[0198] The verification module 12 is used to perform legality verification on the target IoT device according to the first task request and obtain the verification result, which includes verification failure and verification success.

[0199] The acquisition module 13 is used to acquire a preset encoding strategy if the verification result of the target IoT device is successful.

[0200] The determining module 14 is used to determine the target IoT card number corresponding to the target IoT device according to the preset encoding strategy and the first task request;

[0201] The task processing module 15 is used to process the first task request based on the target IoT card number.

[0202] The IoT card number conversion device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0203] In one possible implementation, the first task request includes task request information and device information of the target IoT device; the determining module 14 is specifically used for:

[0204] Determine whether the device information contains a first IoT card number, which is used to enable data interaction between target IoT devices;

[0205] If it exists, the target IoT card number is determined according to the preset encoding strategy and the first IoT card number;

[0206] If it does not exist, the target IoT card number will be determined according to the preset encoding strategy.

[0207] In one possible implementation, the determining module 14 is specifically used for:

[0208] Determine whether the encoding rules of the first IoT card number conform to the preset encoding strategy;

[0209] If the match is found, the target IoT card number is determined based on the first IoT card number;

[0210] If it does not meet the requirements, the target IoT card number will be determined according to the preset coding strategy.

[0211] In one possible implementation, the determining module 14 is specifically used for:

[0212] Retrieve multiple card number conversion information in memory, including historical IoT card numbers, historical locations, and historical request times;

[0213] Based on the first IoT card number, determine the first card number conversion information from multiple card number conversion information;

[0214] The target IoT card number is determined based on the device information and the first card number conversion information.

[0215] In one possible implementation, the device information includes a first IoT card number, current location, and current request time; the determination module 14 is specifically used for:

[0216] The first historical location and the first historical request time of the target IoT device are determined from the first card number conversion information;

[0217] If the current location is the same as the first historical location, the target IoT card number is determined based on the current request time and the first historical request time.

[0218] If the current location is different from the first historical location, the target IoT card number is determined according to the preset encoding strategy.

[0219] In one possible implementation, the determining module 14 is specifically used for:

[0220] Determine the request interval based on the current request time and the first historical request time;

[0221] If the request interval is longer than the preset duration, the target IoT card number will be determined according to the preset encoding strategy.

[0222] If the requested interval is less than or equal to the preset interval, the historical IoT card number in the first card number conversion information will be determined as the target IoT card number.

[0223] In one possible implementation, the preset encoding strategy includes multiple parameters to be acquired and preset parameters; the device information also includes an initial IoT card number; the determination module 14 is specifically used for:

[0224] Obtain parameter data for multiple parameters to be acquired from the initial IoT card number;

[0225] Retrieve parameter data for preset parameters;

[0226] According to the preset encoding strategy, the parameter data of multiple parameters to be acquired and the parameter data of the preset parameters are concatenated to obtain the target IoT card number.

[0227] In one possible implementation, the verification module 12 is specifically used for:

[0228] Obtain the certification information form for IoT devices;

[0229] If the initial IoT card number of the target IoT device exists in the authentication information table, the verification result of the legality verification of the target IoT device is successful.

[0230] If the initial IoT card number of the target IoT device is not found in the authentication information table, the verification result of the legality verification of the target IoT device is verification failure.

[0231] In one possible implementation, the device further includes an update module and a deletion module:

[0232] The update module is used to update the first conversion information of the target IoT device in memory based on the target IoT card number and device information;

[0233] The deletion module is used to delete the first IoT card number from the target IoT device and store the target IoT card number if the first IoT card number exists in the target IoT device.

[0234] The IoT card number conversion device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0235] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Please refer to... Figure 7 The electronic device 20 may include a processor 21 and a memory 22. Exemplarily, the processor 21 and the memory 22 are interconnected via a bus 23.

[0236] Memory 22 stores instructions executed by the computer;

[0237] The processor 21 executes computer execution instructions stored in the memory 22, causing the processor 21 to perform the IoT card number conversion method as shown in the above method embodiment.

[0238] Accordingly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the IoT card number conversion method described in the above method embodiments.

[0239] Accordingly, embodiments of this application may also provide a computer program product, including a computer program, which, when executed by a processor, can implement the IoT card number conversion method shown in the above method embodiments.

[0240] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0241] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0242] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0243] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0244] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0245] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0246] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0247] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0248] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for converting Internet of Things (IoT) card numbers, characterized in that, Applied to carrier equipment, including: Receive a first task request from the target IoT device, the first task request including task request information and device information of the target IoT device, the device information including an initial IoT card number; The target IoT device is validated according to the first task request, and a validation result is obtained, which includes validation failure and validation success. If the verification result of the target IoT device is successful, then a preset encoding strategy is obtained, which includes multiple parameters to be obtained and preset parameters; Based on the preset encoding strategy and the first task request, the target IoT card number corresponding to the target IoT device is determined; Based on the target IoT card number, the first task request is processed; The step of verifying the legitimacy of the target IoT device according to the first task request and obtaining the verification result includes: Obtain the certification information form for IoT devices; If the initial IoT card number of the target IoT device exists in the authentication information table, the verification result of the legality verification of the target IoT device is successful. If the initial IoT card number of the target IoT device is not found in the authentication information table, the verification result of the legality verification of the target IoT device is verification failure; The step of determining the target IoT card number corresponding to the target IoT device according to the preset encoding strategy and the first task request includes: Determine whether a first IoT card number exists in the device information. The first IoT card number is used to enable data interaction between target IoT devices. If it exists, the target IoT card number is determined according to the preset encoding strategy and the first IoT card number; If it does not exist, the parameter data of the plurality of parameters to be acquired is obtained from the initial IoT card number; the parameter data of the preset parameter is obtained; according to the preset encoding strategy, the parameter data of the plurality of parameters to be acquired and the parameter data of the preset parameter are concatenated to obtain the target IoT card number.

2. The method according to claim 1, characterized in that, Determining the target IoT card number based on the preset encoding strategy and the first IoT card number includes: Determine whether the encoding rule of the first IoT card number conforms to the preset encoding strategy; If the conditions are met, the target IoT card number is determined based on the first IoT card number; If it does not meet the requirements, the target IoT card number is determined according to the preset encoding strategy.

3. The method according to claim 2, characterized in that, Determining the target IoT card number based on the first IoT card number includes: Multiple card number conversion information is retrieved from memory, including historical IoT card numbers, historical locations, and historical request times. Based on the first IoT card number, determine the first card number conversion information from the plurality of card number conversion information; The target IoT card number is determined based on the device information and the first card number conversion information.

4. The method according to claim 3, characterized in that, The device information includes a first IoT SIM card number, current location, and current request time; determining the target IoT SIM card number based on the device information and the first SIM card number conversion information includes: The first historical location and the first historical request time of the target IoT device are determined from the first card number conversion information; If the current location is the same as the first historical location, then the target IoT card number is determined based on the current request time and the first historical request time. If the current location and the first historical location are not the same, the target IoT card number is determined according to the preset encoding strategy.

5. The method according to claim 4, characterized in that, Determining the target IoT card number based on the current request time and the first historical request time includes: The request interval duration is determined based on the current request time and the first historical request time. If the request interval is longer than a preset duration, the target IoT card number is determined according to the preset encoding strategy. If the request interval is less than or equal to a preset duration, then the historical IoT card number in the first card number conversion information is determined as the target IoT card number.

6. The method according to any one of claims 1-5, characterized in that, After determining the target IoT card number corresponding to the target IoT device according to the first task request, the method further includes: Based on the target IoT card number and the device information, update the first conversion information of the target IoT device in memory; If the target IoT device contains a first IoT card number, then the target IoT device deletes the first IoT card number and stores the target IoT card number.

7. An Internet of Things (IoT) card number conversion device, characterized in that, Applied to carrier equipment, it includes a receiving module, a verification module, an acquisition module, a determination module, and a task processing module: The receiving module is used to receive a first task request from the target IoT device, wherein the first task request includes task request information and device information of the target IoT device, and the device information includes an initial IoT card number. The verification module is used to perform legality verification on the target IoT device according to the first task request and obtain a verification result. The verification result includes verification failure and verification success. The step of performing legality verification on the target IoT device according to the first task request and obtaining a verification result includes: obtaining an authentication information table of the IoT device; if the initial IoT card number of the target IoT device exists in the authentication information table, the verification result of the legality verification of the target IoT device is verification success; if the initial IoT card number of the target IoT device does not exist in the authentication information table, the verification result of the legality verification of the target IoT device is verification failure. The acquisition module is used to acquire a preset encoding strategy if the verification result of the target IoT device is successful. The preset encoding strategy includes multiple parameters to be acquired and preset parameters. The determining module is used to determine the target IoT card number corresponding to the target IoT device according to the preset encoding strategy and the first task request, including: determining whether a first IoT card number exists in the device information, the first IoT card number being used to enable data interaction between target IoT devices; if it exists, determining the target IoT card number according to the preset encoding strategy and the first IoT card number; if it does not exist, obtaining parameter data of the plurality of parameters to be obtained from the initial IoT card number; obtaining parameter data of the preset parameters; and concatenating the parameter data of the plurality of parameters to be obtained and the parameter data of the preset parameters according to the preset encoding strategy to obtain the target IoT card number. The task processing module is used to process the first task request based on the target IoT card number.

8. An electronic device, characterized in that, include: Memory and processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the IoT card number conversion method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the IoT card number conversion method according to any one of claims 1 to 6.

Images