Network configuration method of terminal device, management server and computer program product

Abstract

The invention discloses a network configuration method of terminal equipment, a management server, the terminal equipment and a computer program product, and relates to the technical field of communication, the network configuration method of the terminal equipment is applied to the management server, and the network configuration method of the terminal equipment comprises the following steps: obtaining a network configuration request of the terminal equipment, the network configuration request carries equipment information corresponding to the terminal equipment; according to the equipment information, querying based on a preset mapping relationship in a target sales information base to obtain target operator information corresponding to the terminal equipment; and generating a target configuration file according to the target operator information and the equipment information, and sending configuration information connected to the target remote server to the terminal equipment based on the target configuration file. The method and the device can effectively avoid errors of the remote server used in association with the terminal device due to the fact that the device association state cannot be updated timely and dynamically.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a network configuration method for a terminal device, a management server, and a computer program product. Background Technology

[0002] With the increasing number of telecom operators, terminal devices need to connect to more and more remote servers. Current technologies primarily store the association and binding information between the device and the operator on the terminal device side. The terminal device then reports the remote server parameters based on this stored association and binding information, thereby connecting to the corresponding remote server. However, operator status may change for various reasons, meaning the operator associated with the terminal device may change. Often, the association and binding information stored on the terminal device side cannot be updated in a timely manner to ensure real-time synchronization of the associated operator (one operator corresponds to one remote server). This leads to errors in the remote server used by the terminal device due to the inability to update the device association status dynamically and promptly. Summary of the Invention

[0003] The main objective of this application is to provide a network configuration method for terminal devices, a management server, and a computer program product, aiming to at least solve the technical problem that the inability to update the device association status in a timely and dynamic manner leads to errors in the remote server associated with the terminal device.

[0004] To at least achieve the above objectives, this application provides a network configuration method for a terminal device, applied to a management server, comprising: obtaining a network configuration request from the terminal device, wherein the network configuration request carries device information corresponding to the terminal device; querying target operator information corresponding to the terminal device based on the device information and a preset mapping relationship in a target sales information database, wherein the preset mapping relationship is configured to be dynamically updated; generating a target configuration file based on the target operator information and the device information; and sending configuration information for connecting to a target remote server to the terminal device based on the target configuration file, thereby triggering the terminal device to establish a communication connection with the target remote server based on the configuration information.

[0005] Furthermore, to at least achieve the above objectives, this application provides a network configuration method for a terminal device, applied to the terminal device, comprising: sending a network configuration request of the terminal device to a management server, wherein the network configuration request carries device information corresponding to the terminal device; upon receiving configuration information returned by the management server in response to the network configuration request, establishing a communication connection with a target remote server based on the configuration information; wherein the configuration information is determined by the management server based on the device information and the target operator information corresponding to the terminal device, and the target operator information is obtained by the management server in response to the device information from a preset mapping relationship stored in a target sales information database, wherein the preset mapping relationship is set to be dynamically updated.

[0006] In addition, to at least achieve the above objectives, this application also provides a management server, the management server comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being configured to implement the steps of the network configuration method for the terminal device as described above.

[0007] In addition, to at least achieve the above objectives, this application also provides a terminal device, the terminal device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the network configuration method of the terminal device as described above.

[0008] In addition, to at least achieve the above objectives, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the network configuration method for a terminal device as described above.

[0009] This application provides a network configuration method for a terminal device. In this embodiment, a network configuration request from the terminal device is first obtained, carrying device information corresponding to the terminal device. Based on this device information, target operator information corresponding to the terminal device is obtained by querying a preset mapping relationship in a target sales information database. This preset mapping relationship is set to be dynamically updated. Then, a target configuration file is generated based on the target operator information and the device information. Based on the target configuration file, configuration information connecting to a target remote server is sent to the terminal device to trigger the terminal device to establish a communication connection with the target remote server based on the configuration information. This allows the terminal device to store only its device information on the terminal device side, while all operator information (i.e., sales information associated with the terminal device) is stored on the server side. Before the terminal device sends the information to the operator, it does not need to associate device information and operator information. This avoids the inability to update the associated binding information stored on the terminal device side in a timely manner when the operator associated with the terminal device changes, thus effectively preventing the failure to update the device association status in a timely and dynamic manner, which could cause errors in the remote server associated with the terminal device. Attached Figure Description

[0010] 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.

[0011] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0012] Figure 1 A flowchart illustrating the network configuration method for the terminal device in this application (Example 1);

[0013] Figure 2 A flowchart illustrating the network configuration method for the terminal device in this application, provided in Embodiment 4;

[0014] Figure 3 A flowchart illustrating the network configuration method for the terminal device in this application, provided in Embodiment 5.

[0015] Figure 4 A flowchart illustrating the network configuration method for the terminal device of this application, provided in Embodiment Six;

[0016] Figure 5 This is a schematic diagram of the network communication structure of a specific embodiment of this application;

[0017] Figure 6 This is a flowchart illustrating a specific embodiment of the present application.

[0018] Figure 7 This is a schematic diagram of the management server structure of the hardware operating environment involved in the network configuration method of the terminal device in this application embodiment;

[0019] Figure 8 This is a schematic diagram of the terminal device structure, representing the hardware operating environment involved in the network configuration method of the terminal device in this application embodiment.

[0020] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0021] 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.

[0022] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0023] The main solution of this application is as follows: Obtaining a network configuration request from a terminal device, wherein the network configuration request carries device information corresponding to the terminal device; based on the device information, querying the target operator information corresponding to the terminal device according to a preset mapping relationship in a target sales information database, wherein the preset mapping relationship is set to be dynamically updated; generating a target configuration file based on the target operator information and the device information; and sending configuration information for connecting to a target remote server to the terminal device based on the target configuration file, thereby triggering the terminal device to establish a communication connection with the target remote server based on the configuration information.

[0024] This application first obtains a network configuration request from a terminal device, which carries device information corresponding to the terminal device. Based on this device information, it queries the target operator information corresponding to the terminal device using a preset mapping relationship in a target sales information database. This preset mapping relationship is configured to be dynamically updated. Then, a target configuration file is generated based on the target operator information and device information. Finally, based on the target configuration file, configuration information for connecting to a target remote server is sent to the terminal device to trigger the terminal device to establish a communication connection with the target remote server based on this configuration information. This allows this application to store only the terminal device's device information on the terminal device side, while all operator information (i.e., terminal...) is not required. Sales information associated with terminal devices is stored on the server side. Before the terminal device sends the information to the operator, the terminal device does not need to associate device information and operator information. This avoids the need to update the association status between the terminal device and the operator again after the operator status is updated. It also prevents errors in the association between the device and the operator when the association status is not updated in time, and avoids the inability to update the association binding information stored on the terminal device in time when the operator associated with the terminal device changes. This ensures that the operator associated with the terminal device (one operator corresponds to one remote server) is synchronized in real time, and effectively avoids the situation where the remote server used by the terminal device is incorrect due to the inability to update the device association status in a timely and dynamic manner.

[0025] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0026] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating the network configuration method for the terminal device in this application, as provided in Embodiment 1.

[0027] This application proposes a network configuration method for a terminal device according to a first embodiment. The network configuration method for the terminal device is applied to a management server and includes steps S100 to S300:

[0028] Step S100: Obtain a network configuration request from the terminal device, wherein the network configuration request carries device information corresponding to the terminal device;

[0029] In this embodiment, a terminal device refers to an electronic device that can connect to and exchange data with a remote server of an operator. The terminal device may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs (Televisions), desktop computers, etc.

[0030] It should be noted that "operators" refers to providers of network, communication, and other services, and "operators' remote servers" refers to server systems established and maintained by these operators and located in remote data centers. These servers are not located directly at the user's end, but rather communicate and exchange data with the user's terminal equipment via the Internet.

[0031] As those skilled in the art will recognize, a network configuration request is a special request initiated by a terminal device to a network server, aimed at obtaining or confirming the configuration information required for network connection. In this embodiment, the network configuration request is a request initiated by the terminal device to a management server to obtain the configuration information required for network connection. The network configuration request carries the device information corresponding to the terminal device, so that the management server can provide appropriate configuration information accordingly.

[0032] It is worth mentioning that the device information can be information that can uniquely identify the device, such as the terminal device's serial number (SN) or international mobile equipment identity (IMEI), or detailed data related to device configuration and compatibility, such as firmware version number, software version number, MAC (Media Access Control) address, device model, and manufacturer information.

[0033] Step S200: Based on the device information, query the target operator information corresponding to the terminal device according to the preset mapping relationship in the target sales information database, wherein the preset mapping relationship is set to be dynamically updated;

[0034] It should be noted that, in this embodiment, the target operator refers to the operator that is expected to connect to the terminal device and provide network services. The target operator information includes the target operator's name, network access point name, network configuration parameters, network service type, and other information. It is easy to understand that this target operator information is crucial data to ensure that the terminal device can be correctly configured and access the target operator's network. This target operator information includes information about the target remote server to which the terminal device connects. Specifically, it may include the target remote server's IP address or domain name, the port number used for communication, the network protocol to be used when the terminal device communicates with the target server, and related parameter settings and quality of service requirements (such as data transmission priority, latency requirements, bandwidth limits, etc.). It may even include specific authentication information or keys to ensure security.

[0035] Furthermore, it should be noted that the preset mapping relationship is a pre-defined logical correspondence rule that associates terminal devices with operators. When the device information of a terminal device is obtained, the target operator information corresponding to that terminal device can be retrieved from the target sales information database using this preset mapping relationship.

[0036] For example, the preset mapping relationship can be a mapping relationship between the SN of the terminal device and the name of the operator. The device information carried in the network configuration request of the terminal device includes the SN of the terminal device. At this time, the management server determines the name of the target operator based on the SN of the terminal device through the preset mapping relationship, and then queries the target operator information from the target sales information database based on the name of the target operator.

[0037] In this embodiment, the target sales information database can be a centralized database that stores information related to the sale, distribution, and network services of terminal devices. This target sales information database can store network configuration-related information such as the SN, IMEI, firmware version number, software version number, MAC address, device model, manufacturer information, and corresponding operator information for each terminal device sold. A corresponding mapping relationship, i.e., a preset mapping relationship, is established between the terminal device and the operator. This preset mapping relationship can be a mapping relationship between the device information of the terminal device and the operator information, or a mapping relationship between the SN of the terminal device and the name of the operator. This embodiment does not specifically limit this.

[0038] It is worth mentioning that the preset mapping relationship in this embodiment is set to be dynamically updated. That is, when the operator providing various services to the terminal device sends a change, the mapping relationship already established in the preset mapping relationship can be dynamically updated. For example, originally, operator B provided various services to terminal device A, and there was a mapping relationship between terminal device A and operator B in the preset mapping relationship. Now, it has changed to operator C providing various services to terminal device A. The administrator of the management server can update the preset mapping relationship, or the management server can automatically update the preset mapping relationship after detecting the change of operator status, so as to update the mapping relationship between terminal device A and operator B to the mapping relationship between terminal device A and operator C, thereby ensuring that terminal device A can correctly connect to the remote server of operator C.

[0039] In this embodiment, the dynamic update mechanism of the preset mapping relationship ensures that the system can flexibly respond to changes in operator services, market strategies, or cooperation models, thereby maintaining the timeliness and accuracy of terminal device configuration. Specifically, this mechanism brings several key advantages:

[0040] 1. Enhanced adaptability and flexibility: When the service provider of the terminal equipment changes, such as switching from operator B to operator C, the configuration strategy can be quickly adjusted by simply updating the preset mapping relationship, without the need for physical contact or software upgrade of the terminal equipment, which greatly improves the flexibility and response speed of service adjustment.

[0041] 2. Simplified Operation and Maintenance Management: The dynamic update mechanism allows network administrators or management systems to automatically respond to changes in the market or partners, reducing the complexity and potential errors of manual intervention, simplifying the operation and maintenance process, and lowering management costs.

[0042] 3. Enhance user experience: End users do not need to understand the complex details of operator changes in the background. Through automated configuration updates, their devices can seamlessly transition to the new service provider, ensuring service continuity and user experience stability.

[0043] 4. Enhanced system scalability: As business develops and new terminal models, operator partners, or service types are added, the dynamic nature of the preset mapping relationship ensures that the system can quickly integrate new data, support more diverse service configurations, and enhance the system's scalability and future adaptability.

[0044] This embodiment enhances the practicality and efficiency of the terminal device network configuration method through a dynamic update mechanism of preset mapping relationships. It also provides terminal device management with high flexibility and agile response to market changes, ensuring service reliability and end-user satisfaction.

[0045] Step S300: Generate a target configuration file based on the target operator information and the device information. Based on the target configuration file, send the configuration information for connecting to the target remote server to the terminal device to trigger the terminal device to establish a communication connection with the target remote server based on the configuration information.

[0046] In this embodiment, the target configuration file is a set of configuration instructions customized based on the target operator information and device information. The configuration information is used to guide the terminal device on how to correctly configure its network settings in order to access the target operator's services. The target remote server is a remote server provided by the target operator that the terminal device needs to connect to in order to obtain services or data.

[0047] It is worth mentioning that the configuration information can be the target configuration file, a compressed configuration file after converting the target configuration file into a data format that is easy to transmit, or an encrypted configuration file after encrypting the target configuration file.

[0048] In this embodiment, the management server can collect detailed information about the terminal device from the target sales information database through device information, including the terminal device's model and hardware capabilities, operating system and version, network interface information, and device-specific authentication information. Then, combined with the access point name, network authentication method and parameters, operator network configuration requirements, and specific services or functions in the target operator information, the server can automatically generate a target configuration file that can accurately adapt to the terminal device and its network environment through script writing, template filling, and other methods. This configuration information connecting to the target remote server is then sent to the terminal device to trigger the terminal device to establish a communication connection with the target remote server based on the configuration information, ensuring the smooth establishment and efficient operation of the communication connection.

[0049] This embodiment first obtains a network configuration request from a terminal device, which carries device information corresponding to the terminal device. Based on this device information, it queries the target operator information corresponding to the terminal device using a preset mapping relationship in the target sales information database. This preset mapping relationship is configured to be dynamically updated. Then, a target configuration file is generated based on the target operator information and device information. Finally, based on the target configuration file, configuration information for connecting to the target remote server is sent to the terminal device to trigger the terminal device to establish a communication connection with the target remote server based on this configuration information. This allows this embodiment to store only the terminal device's device information on the terminal device side, while all operator information (i.e., ...) is not stored. Sales information associated with terminal devices is stored on the server side. Before the terminal device sends the information to the operator, the terminal device does not need to associate device information and operator information. This avoids the need to update the association status between the terminal device and the operator again after the operator status is updated. It also prevents errors in the association between the device and the operator when the association status is not updated in time, and avoids the inability to update the association binding information stored on the terminal device in time when the operator associated with the terminal device changes. This ensures that the operator associated with the terminal device (one operator corresponds to one remote server) is synchronized in real time, and effectively avoids the situation where the remote server used by the terminal device is incorrect due to the inability to update the device association status in a timely and dynamic manner.

[0050] Based on the first embodiment described above, a network configuration method for a terminal device according to the second embodiment of this application is proposed.

[0051] In the second embodiment of this application, the same or similar content as in the above embodiments can be referred to the above description, and will not be repeated hereafter.

[0052] In this embodiment, the device information is obtained by encrypting the unique identification information corresponding to the terminal device, wherein the type of the unique identification information is the device's serial number (SN), International Mobile Equipment Identity (IMEI), firmware version number, or software version number.

[0053] Based on the device information, the target operator information corresponding to the terminal device is obtained by querying the preset mapping relationship in the target sales information database. A target configuration file is generated based on the target operator information and the device information, including steps A10 to A30:

[0054] Step A10: Decrypt the device information to obtain the unique identification information;

[0055] In this embodiment, the device information is obtained by encrypting the unique identification information corresponding to the terminal device. The unique identification information refers to information that can uniquely identify the identity of the terminal device. The type of the unique identification information is the device's serial number (SN), International Mobile Equipment Identity (IMEI), firmware version number, or software version number.

[0056] This embodiment effectively protects the security of sensitive information of the terminal device during transmission and storage by encrypting the unique identification information corresponding to the terminal device first, and then decrypting the device information on the management server. It ensures that even if the device information is intercepted in the network, this sensitive information (such as SN, IMEI, etc.) cannot be directly read and used without key decryption. This effectively prevents the risk of information leakage and identity impersonation, protects the privacy rights of terminal users, and avoids the exposure of personally associated device information in the public network environment, which complies with the increasingly stringent personal information protection regulations worldwide.

[0057] Furthermore, in this embodiment, the unique identification information obtained through decryption is the basis for generating the target configuration file. This means that the target configuration file is tailored to each specific terminal device and may contain specific settings, optimizations, or restrictions required by the terminal device, such as network configuration, operator service customization, etc., thereby ensuring that the terminal device can correctly and efficiently connect to the target remote server of the corresponding target operator.

[0058] This embodiment encrypts the unique identification information of the terminal device (such as SN, IMEI, firmware or software version number) and then decrypts it for use. This effectively protects the security of sensitive information of the device during transmission and storage, prevents information leakage, complies with the current strict data protection regulations, and enhances user trust.

[0059] Step A20: Based on the preset mapping relationship in the target sales information database, query the operator information mapped by the unique identity information, and use the operator information mapped by the unique identity information as the target operator information corresponding to the terminal device;

[0060] In this embodiment, the preset mapping relationship in the target sales information database is the mapping relationship between unique identification information and operator information. That is, in the target sales information database, the unique identification information of each terminal device is mapped to the corresponding operator information. After the management server decrypts and obtains the unique identification information, it can use the unique identification information as a query key to directly query the operator information mapped by the unique identification information from the target sales information database, and use it as the target operator information corresponding to the terminal device.

[0061] This embodiment automatically queries the operator information corresponding to unique identifiers through preset mapping relationships, greatly improving processing speed and accuracy, reducing the need for manual intervention, and thus enabling rapid response to the configuration needs of a large number of terminal devices. This is particularly beneficial in large-scale deployment projects, significantly improving work efficiency. Furthermore, the centralized management of preset mappings in the target sales information database through a management server greatly facilitates the updating and maintenance of these mapping relationships. When operator policies or network configurations change, only the mapping relationships in the database need to be adjusted to automatically adapt to these changes, eliminating the need for manual adjustments on each terminal device, thus reducing maintenance costs and complexity.

[0062] This embodiment utilizes the fact that the preset mapping relationship in the target sales information database can be dynamically updated. On the management server side, the unique identification information of the terminal device is associated with the target operator information. This allows the terminal device to store only the unique identification information, while the operator information is stored in the target sales information database on the management server. This enables the terminal device to dynamically request the configuration information of the remote server simply by encrypting the unique identification information into device information and sending it to the management server, thus saving the storage overhead of the terminal device.

[0063] Step A30: Generate a target configuration file based on the target operator information and the unique identification information.

[0064] In this embodiment, the management server first parses the specific configuration parameters required by the target operator based on the target operator information, including but not limited to network access point name, frequency band settings, operator-specific network protocols, authentication methods, and any proprietary service configurations. Then, through template filling, script writing, and other methods, the unique identification information of the terminal device is integrated into the configuration process to construct the target configuration file.

[0065] This embodiment automatically decrypts device information to obtain unique identification information, and automatically queries the corresponding target operator information from the target sales information database based on the unique identification information. Then, it automatically parses the target operator information, integrates the unique identification information, and generates a target configuration file. This not only improves the efficiency of target configuration file generation, but also reduces configuration errors caused by human operation mistakes, ensuring the accuracy and timeliness of configuration information.

[0066] Based on the first embodiment described above, a network configuration method for a terminal device according to a third embodiment of this application is proposed.

[0067] In the third embodiment of this application, the same or similar content as the above embodiments can be referred to the above description, and will not be repeated hereafter.

[0068] In this embodiment, the step of sending the configuration information for connecting to the target remote server to the terminal device based on the target configuration file may include steps B10 to B20:

[0069] Step B10: Encrypt the target configuration file to obtain configuration information for connecting to the target server;

[0070] Step B20: Send the configuration information to the terminal device.

[0071] In this embodiment, the configuration information is obtained by encrypting the target configuration file, and the specific encryption method is not limited in this embodiment.

[0072] This embodiment encrypts the target configuration file after it is generated, converting it into unreadable configuration information. This significantly improves data transmission security and effectively prevents the leakage of sensitive information. Simultaneously, the encryption process also provides anti-tampering functionality; any modification to the encrypted data during transmission will cause decryption failure at the receiving end, thus ensuring that the configuration information received by the terminal device is complete and has not been maliciously tampered with, guaranteeing correct configuration execution and system stability.

[0073] Furthermore, encrypted configuration information can be securely transmitted across public networks without geographical limitations, enabling remote configuration and greatly improving the management efficiency of large-scale distributed devices, making it particularly suitable for the deployment and maintenance of Internet of Things (IoT) devices.

[0074] It is worth mentioning that the target configuration file is encrypted into configuration information on the management server side. After the configuration information is sent to the terminal device, the terminal device will decrypt the configuration information using a decryption method corresponding to the encryption method used by the management server side, thereby obtaining the target configuration file. The terminal device will then configure the network according to the target configuration file to establish a communication connection with the target remote server.

[0075] Furthermore, in one feasible implementation, after the step of generating the target configuration file based on the target operator information and the device information, steps C10 to C20 are further included:

[0076] Step C10: Verify the target configuration file;

[0077] Step C20: If the target configuration file passes verification, the step of encrypting the target configuration file to obtain configuration information for connecting to the target server is triggered.

[0078] In this embodiment, after generating the target configuration file based on the target operator information and device information, the management server will also verify the target configuration file to ensure the correctness, integrity and compatibility of all configuration items, avoid device connection problems caused by configuration errors, and after the verification is passed, trigger the encryption process of the target configuration file to obtain the configuration information for connecting to the target server.

[0079] This implementation ensures the accuracy of all parameters in the generated target configuration file through the verification operation in step C10, including but not limited to network settings, authentication information, and protocol versions. This effectively prevents device connection failures, performance issues, or security risks caused by configuration errors, thus improving the network configuration success rate. Furthermore, the verification process also involves confirming the compatibility of the target configuration file with the hardware, software, and target operator network of the terminal device, avoiding runtime errors caused by compatibility issues. This is particularly important for supporting a diverse device ecosystem and enhances the applicability of the management server. Simultaneously, verifying the target configuration file can proactively identify and correct configuration errors, reducing the workload of troubleshooting and maintenance after the terminal device has configured the network, lowering technical support costs, accelerating communication between the terminal device and the target remote server, and improving overall operational efficiency.

[0080] In addition, in step C20 of this embodiment, encryption is only performed after verification, ensuring that only correct and valid configuration information is encrypted and sent to the terminal device. Invalid or incorrect configuration files are filtered out by verification, avoiding unnecessary encryption processing and waste of network transmission resources. This allows system resources to be allocated and used more efficiently, and further strengthens the security defense of the entire configuration transmission link, preventing potential security vulnerabilities from being maliciously exploited.

[0081] Furthermore, in one feasible implementation, the step of sending the configuration information to the terminal device may include steps D10 to D20:

[0082] Step D10: If the network connection status with the terminal device is determined to be connected, the configuration information is directly sent to the terminal device; or,

[0083] Step D20: If the network connection with the terminal device is determined to be disconnected, the configuration information is sent to other devices, which then relay the configuration information to the terminal device via near-field communication.

[0084] As those skilled in the art will know, Near Field Communication (NFC) is a short-range wireless communication technology that allows electronic devices to exchange data when they are close to each other.

[0085] It should be noted that, in this embodiment, other devices refer to network-connected devices near the terminal device that can interact with the terminal device via NFC, that is, these other devices can interact with the terminal device via near-field communication and have the function of connecting to the management server via the network.

[0086] In this embodiment, when the network connection between the terminal device and the management server is connected, the management server directly sends the configuration information to the terminal device. When the network connection between the terminal device and the management server is disconnected, the management server sends the configuration information to another device, which then forwards the configuration information to the terminal device via NFC. This ensures that the configuration information can be downloaded regardless of whether the terminal device is directly connected to the management server.

[0087] This implementation combines direct network transmission with NFC relay, making it highly adaptable to different network conditions. It can intelligently select the most suitable transmission path based on the currently available communication methods, which not only ensures the efficient, secure, and reliable transmission of configuration information, but also greatly enhances the deployment and maintenance capabilities in various network environments, improves the user experience, and reduces the dependence on stable network connections.

[0088] Please refer to Figure 7 , Figure 7 This is a schematic diagram of the management server structure of the hardware operating environment involved in the network configuration method of the terminal device in this application embodiment.

[0089] This application also provides a management server, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the network configuration method of the terminal device in the above embodiments.

[0090] The following is for reference. Figure 7 The diagram illustrates a structural schematic of a management server suitable for implementing embodiments of this application. The management server in these embodiments may include, but is not limited to, cloud computing servers, distributed cluster servers, edge computing servers, data processing servers, application servers, database servers, game servers, streaming media servers, mail servers, web servers, and any server capable of providing powerful computing capabilities, storage, and data processing services. Figure 7 The management server shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0091] like Figure 7 As shown, the management server may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 1002 or a program loaded from storage device 1003 into random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the management server. The processing device 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the management server to communicate wirelessly or wiredly with other devices to exchange data. Although the figure shows a management server with various systems, it should be understood that implementing or having all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0092] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0093] The management server provided in this application, employing the network configuration method for terminal devices in the above embodiments, can at least solve the technical problem that the inability to update the device association status in a timely and dynamic manner leads to errors in the remote server associated with the terminal device. Compared with the prior art, the beneficial effects of the management server provided in this application are the same as those of the network configuration method for terminal devices provided in the above embodiments, and other technical features of this management server are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0094] Furthermore, this application also proposes a network configuration method for a terminal device according to a fourth embodiment.

[0095] In the fourth embodiment of this application, the same or similar content as the above embodiments can be referred to the above description, and will not be repeated hereafter.

[0096] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating the network configuration method for the terminal device in this application, as provided in Embodiment 4.

[0097] In this embodiment, the network configuration method for the terminal device is applied to the terminal device, and the network configuration method for the terminal device includes steps S400 to S500:

[0098] Step S400: Send the network configuration request of the terminal device to the management server, wherein the network configuration request carries the device information corresponding to the terminal device;

[0099] Step S500: Upon receiving configuration information returned by the management server in response to the network configuration request, establish a communication connection with the target remote server based on the configuration information;

[0100] The configuration information is determined by the management server based on the device information and the target operator information corresponding to the terminal device, and the target operator information is obtained by the management server in response to the device information from a preset mapping relationship stored in the target sales information database. The preset mapping relationship is set to be dynamically updated.

[0101] It should be noted that, in this embodiment, the target operator information includes information about the target remote server to which the terminal device is connected.

[0102] This embodiment centralizes network configuration tasks on a management server. When a terminal device needs network configuration, it only needs to send a network configuration request carrying the device information to the management server. The management server then uses a preset mapping relationship in the target sales information database that can be dynamically updated to query the target operator information corresponding to the terminal device in real time to generate a target configuration file. This sends the network configuration information to the terminal device. After receiving the configuration information, the terminal device performs network configuration based on the configuration information and establishes a communication connection with the target remote server. This eliminates the need for the terminal device to have built-in complex logic to process configuration information from different operators, nor does it need to store specific parameters for various operators. This reduces the hardware cost and software complexity of the terminal device, making the design of the terminal device simpler and easier to manufacture and maintain.

[0103] Meanwhile, when operator information changes, such as a new operator joining, an old operator exiting the market, or adjustments to the operator's network configuration parameters, this embodiment only needs to update the preset mapping relationship on the management server side. There is no need to modify each terminal device individually. This allows the terminal devices to automatically receive the latest configuration information and adjust their network settings in real time through continuous communication with the management server, ensuring service continuity and reliability. It avoids service interruptions caused by outdated configurations, and can adapt to market and technological changes more quickly, improving the overall system's flexibility and response speed.

[0104] In addition, for large-scale deployment of terminal devices, the management server can serve as a central point to uniformly push configuration updates and execute batch operations, which greatly reduces the burden of operation and maintenance and improves management efficiency.

[0105] Based on the fourth embodiment described above, a network configuration method for a terminal device according to the fifth embodiment of this application is proposed.

[0106] In the fifth embodiment of this application, the same or similar content as in the above embodiments can be referred to the above description, and will not be repeated hereafter.

[0107] Please refer to Figure 3 , Figure 3 This is a flowchart illustrating the network configuration method for the terminal device in this application, as provided in Embodiment 5.

[0108] In this embodiment, before the step of sending the network configuration request of the terminal device to the management server, steps S600 to S700 may be included:

[0109] Step S600: Read the unique identification information corresponding to the terminal device, wherein the type of the unique identification information is the device's serial number (SN), International Mobile Equipment Identity (IMEI), firmware version number, or software version number;

[0110] Step S700: Encrypt the unique identification information to obtain device information, and generate a network configuration request for the terminal device based on the device information.

[0111] It should be noted that the step of generating a network configuration request based on device information in this embodiment actually generates a network configuration request carrying the device information. This network configuration request is sent to the management server, which then queries the corresponding operator information based on the device information and generates a target configuration file to return the configuration information required for network configuration of the terminal device to the terminal device.

[0112] In this embodiment, the terminal device uses the device's serial number (SN), International Mobile Equipment Identity (IMEI), firmware version number, or software version number as its unique identification information. This unique identification information is then encrypted to obtain device information. Based on this device information, data is generated to effectively prevent illegal interception and use during transmission, protecting user privacy and device security. At the same time, the encryption process also increases the confidentiality and integrity of the data and reduces the risk of identity theft.

[0113] This embodiment uses unique identification information as the basis for encrypting device information, ensuring that the generated network configuration request accurately matches a specific terminal device. This means that the management server can generate the most suitable configuration file for each terminal device based on its unique identification information, enabling personalized network configuration and optimizing user experience and compatibility.

[0114] Based on the fourth embodiment described above, a network configuration method for a terminal device according to the sixth embodiment of this application is proposed.

[0115] In the sixth embodiment of this application, the same or similar content as the above embodiments can be referred to the above description, and will not be repeated hereafter.

[0116] Please refer to Figure 4 , Figure 4 This is a flowchart illustrating the network configuration method for the terminal device in this application, as provided in Embodiment Six.

[0117] In this embodiment, the step of establishing a communication connection with the target remote server based on the configuration information may include steps S510 to S520:

[0118] Step S510: Decrypt the configuration information to obtain the target configuration file;

[0119] In this embodiment, the configuration information is obtained by the management server after encrypting the target configuration file. Therefore, after receiving the configuration information, the terminal device needs to decrypt the configuration information before it can obtain the target configuration file, load the target configuration file to complete the network configuration, and establish a communication connection with the target remote server.

[0120] It is worth mentioning that when the terminal device decrypts the configuration information, the software or firmware running on the terminal device can call pre-embedded security modules or libraries, and use specific decryption algorithms (such as AES, RSA, etc.) and corresponding keys or key pairs (public key / private key) to decrypt the received encrypted configuration information. These keys can be statically stored in the device's secure area, or they can be sent along with the configuration information by the management server.

[0121] Those skilled in the art will recognize that in secure communication, the encryption and decryption processes follow a fundamental principle: the use of correlated algorithms and key pairs. This means that if a management server uses a specific encryption algorithm and corresponding key or key pair to encrypt configuration information, then the terminal device, upon receiving this encrypted information, must use the corresponding decryption algorithm and key (or private key) to correctly decrypt the information.

[0122] Therefore, the decryption algorithm used by the terminal device in this embodiment is compatible with the encryption algorithm used by the management server. Only in this way can the configuration information be correctly and securely restored to the target configuration file, thereby completing network configuration and establishing a communication connection.

[0123] Furthermore, in one feasible implementation, step S510 may be followed by steps E10 to E20:

[0124] Step E10: Verify the target configuration file;

[0125] Step E20: If the target configuration file passes verification, the step of establishing a communication connection with the target remote server based on the target configuration file is triggered.

[0126] In this embodiment, after decrypting the configuration information to obtain the target configuration file, the terminal device will also perform a verification operation on the target configuration file to verify whether the configuration information has been tampered with during transmission, thereby further enhancing the security and reliability of the network configuration process.

[0127] The verification operation may include integrity verification and validity verification. For example, integrity verification can be achieved by comparing the hash value of the decrypted target configuration file with the hash value sent along with the configuration information, and validity verification can be achieved by checking whether the target configuration file contains valid structure and content.

[0128] This implementation method effectively prevents security vulnerabilities caused by malicious tampering or corruption of configuration data by adding a configuration file verification step. This enhances the overall security defense capabilities of the system, ensuring that every configuration change is based on an accurate configuration file. It reduces connection failures and service interruptions caused by configuration errors, improving system stability and reliability. This allows terminal devices to establish connections with the target server faster and more accurately, reducing user waiting time and improving user experience. Furthermore, the explicit verification steps help quickly locate configuration-related problems, facilitating troubleshooting and system optimization by maintenance personnel.

[0129] Step S520: Establish a communication connection with the target remote server based on the target configuration file.

[0130] This embodiment ensures the confidentiality and integrity of configuration data during transmission by encrypting the target configuration file on the management server side. On the terminal device side, an agreed algorithm is used to decrypt the configuration information, ensuring that only the correct terminal device can decrypt the configuration information and establish a connection with the target remote server. The network configuration operation is standardized through a unified encryption and decryption process, which complies with industry security standards and legal requirements.

[0131] It is worth mentioning that when problems occur during the network configuration process of terminal devices, the clear and standardized processing flow of configuration information makes it easier to locate the problem. Whether it is an error in the encryption and decryption process or an improper configuration parameter, this embodiment can quickly diagnose and repair it, effectively reducing service interruption time.

[0132] Furthermore, in one feasible implementation, the step of sending the network configuration request of the terminal device to the management server may include steps S410 to S420:

[0133] Step S410: If the network connection status with the management server is determined to be connected, the network configuration request of the terminal device is directly sent to the management server; or,

[0134] Step S420: If it is determined that the network connection with the management server is disconnected, the network configuration request of the terminal device is sent to other devices via near-field communication, and the network configuration request is relayed to the management server through the other devices.

[0135] In this embodiment, when the network connection between the terminal device and the management server is connected, the terminal device directly sends the network configuration request to the management server. When the network connection between the terminal device and the management server is disconnected, the terminal device sends the network configuration request to another device via NFC (Near Field Communication), and the other device then relays the configuration information to the management server. This ensures that the terminal device can send the network configuration request to the management server regardless of whether it is directly connected to the management server, thereby receiving the configuration information returned by the management server for network configuration.

[0136] This implementation combines direct network transmission with NFC relay, making it highly adaptable to different network conditions. It can intelligently select the most suitable transmission path based on the currently available communication methods, ensuring not only the efficient, secure, and reliable transmission of network configuration requests, but also greatly enhancing deployment and maintenance capabilities in various network environments, improving user experience, and reducing reliance on stable network connections.

[0137] Please refer to Figure 8 , Figure 8 This is a schematic diagram of the terminal device structure, representing the hardware operating environment involved in the network configuration method of the terminal device in this application embodiment.

[0138] This application also provides a terminal device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the network configuration method of the terminal device in the above embodiments.

[0139] The following is for reference. Figure 8 The diagram illustrates a structural schematic of a terminal device suitable for implementing embodiments of this application. The terminal device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 8 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0140] like Figure 8As shown, the terminal device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the terminal device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1003 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows terminal devices to communicate wirelessly or wiredly with other devices to exchange data. Although terminal devices with various systems are shown in the figures, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0141] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0142] The terminal device provided in this application, employing the network configuration method of the terminal device in the above embodiments, can at least solve the technical problem that the inability to update the device association status in a timely and dynamic manner leads to errors in the remote server associated with the terminal device. Compared with the prior art, the beneficial effects of the terminal device provided in this application are the same as those of the network configuration method of the terminal device provided in the above embodiments, and other technical features in this terminal device are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0143] To facilitate understanding of the technical concept or principle of the network configuration method for the terminal device in this application as described in the above embodiments, a specific embodiment is provided for reference. Figures 5 to 6 .

[0144] like Figure 5 As shown in this specific embodiment, the network communication structure for network configuration of the terminal device mainly includes a mobile internet device (in this specific embodiment, "mobile internet device" and "device" both refer to the terminal device), a management server, and a remote server parameter configuration tool on it. The management server accesses the device sales information of all mobile internet devices (including the operator information corresponding to the terminal device), can communicate with all mobile internet devices, receive network configuration requests from mobile internet devices, and issue corresponding configuration information. The remote server parameter configuration tool is responsible for decrypting the encrypted information uploaded by the mobile internet device (i.e., device information obtained by encrypting the unique identification information), generating a configuration file based on the device information and the device sales information accessed by the management server, verifying and encrypting the configuration file, that is, generating a target configuration file based on the target operator information and device information, verifying the target configuration file, and encrypting the target configuration file if the verification passes, thus obtaining the configuration information for connecting to the target server. The mobile internet device encrypts its basic device information (i.e., unique identification information) to obtain encrypted information, then uploads the encrypted information, sends a network configuration request carrying the encrypted information to the management server, and after the remote server parameter configuration tool generates and encrypts the configuration file, it downloads the configuration file from the management server, decrypts and verifies it, and uses the verified remote server configuration parameters (i.e., the configuration parameters required to connect to the target remote server in the target configuration file) to connect to the remote server.

[0145] like Figure 6 As shown, in this specific embodiment, the network configuration process of the terminal device includes:

[0146] Step S101: Encrypt the basic information of the mobile internet device.

[0147] In this specific embodiment, the mobile internet device is pre-installed with various applications capable of communicating and interacting with a remote server. These applications are not started by default. When the mobile internet device needs to establish a connection with the remote server, the mobile internet device will generate encrypted device information required for the remote server's configuration parameters, such as the device's SN, IMEI, firmware version number, and software version number, and then proceed to step S102.

[0148] Step S102: The mobile internet device uploads encrypted information;

[0149] In this specific embodiment, the mobile internet device uploads the encrypted information to the management server. In special scenarios, such as when the mobile internet device can only access the intranet and cannot directly connect to the management server, the encrypted information can be sent to other terminal devices, such as the user's mobile phone, via near-field communication (NFC). The other terminal device then completes the configuration file application process. That is, when it is determined that the network connection with the management server is disconnected, the terminal device sends the network configuration request to other devices via NFC, which then forward the network configuration request to the management server. Subsequently, the process proceeds to step S103.

[0150] Step S103: Start the remote server parameter configuration tool;

[0151] In this specific embodiment, the tool needs to access the sales information of all devices. When all devices are sent from the terminal factory to the operator, the operator information and the device information sent to the operator are entered into the sales information system (i.e., the target sales information database) for the remote server parameter configuration tool to access and use. That is, the remote server parameter configuration tool can query the target operator information corresponding to the terminal device based on the device information and the preset mapping relationship in the target sales information database. If the mobile Internet device is resold or other scenarios require updating the sales information (i.e., the operator status changes), and the system already has the device, the latest operator information is used to update and replace the operator information corresponding to the device in the system (that is, dynamically updating the preset mapping relationship in the target sales information database). This ensures that each device in the sales information system has one and only one corresponding operator information when the user actually uses it, achieving the effect of dynamically associating devices and remote servers based on sales information, and then proceeding to step S104.

[0152] Step S104: The parameter configuration tool obtains the encryption information;

[0153] In this specific embodiment, after the remote server parameter configuration tool obtains the encrypted information uploaded by the device, it proceeds to step S105.

[0154] Step S105: The parameter configuration tool decrypts the information to obtain device information;

[0155] In this specific embodiment, after the remote server parameter configuration tool decrypts the information, it obtains the device information required to generate the remote server configuration parameters (that is, it decrypts the device information to obtain unique identification information), and then proceeds to step S106.

[0156] Step S106: Generate a configuration file based on equipment information and equipment sales information;

[0157] In this specific embodiment, the remote server parameter configuration tool queries the sales information of the device in the sales information system based on the decrypted information. From the sales information, it determines the corresponding operator information for the device, thereby determining the remote server the device needs to connect to (i.e., based on a preset mapping relationship in the target sales information database, it queries the operator information mapped to the unique identifier information and uses this unique identifier information as the target operator information for the terminal device, where the target operator information includes information about the target remote server to which the terminal device connects). Then, it generates a remote server parameter configuration file for the device based on the device information and the remote server information; that is, it generates a target configuration file based on the target operator information and the unique identifier information.

[0158] For example, if the remote server parameter configuration tool queries device A in the sales information system and the query result has one and only one record similar to "device A was sold to operator A", then a remote server parameter configuration file for device A to connect to operator A will be generated.

[0159] Check C101 to see if the configuration file has passed verification;

[0160] In this specific embodiment, the remote server parameter configuration tool will also check whether the configuration file is normal. If it is, proceed to step S107; otherwise, proceed to step S104 to re-acquire the encrypted information uploaded by the device.

[0161] Step S107: Encrypt the configuration file;

[0162] In this specific embodiment, the remote server parameter configuration tool encrypts the generated configuration file and then proceeds to step S108.

[0163] Step S108: The mobile internet device requests and downloads the configuration file online;

[0164] In this specific embodiment, the mobile internet device requests and downloads the configuration file online from the management server. In fact, the request from the mobile internet device occurs in step S102; that is, step S102 actually sends a network configuration request carrying the encrypted information to the management server. Correspondingly, in special scenarios, such as when the mobile internet device can only access the intranet and cannot directly connect to the management server, other terminal devices, such as the user's mobile phone, send a network configuration request to the management server and download the configuration file online via near-field communication (NFC), and finally send the configuration file to the mobile internet device via NFC.

[0165] Step S109: Decrypt the configuration file on the mobile internet device;

[0166] In this specific embodiment, the mobile internet device decrypts the encrypted configuration file to obtain the original configuration file, that is, it decrypts the configuration information to obtain the target configuration file.

[0167] Check C102 to see if the configuration file has passed verification;

[0168] In this specific embodiment, the mobile internet device verifies the decrypted configuration file. If the verification is successful, it proceeds to step S110 (that is, verifying the target configuration file; if the target configuration file is verified, the step of establishing a communication connection with the target remote server based on the target configuration file is triggered). Otherwise, it proceeds to step S101 to restart the entire process, that is, to re-encrypt and upload the device information and send the network configuration request.

[0169] Step S110: Connect to the corresponding remote server using the configuration file.

[0170] In this specific embodiment, the mobile internet device launches the corresponding remote server connection application according to the configuration file and connects to the corresponding remote server, that is, it establishes a communication connection with the target remote server based on the target configuration file. After the communication connection is established, the process exits and the result is reported.

[0171] It should be noted that the specific embodiments listed are only for the purpose of assisting in understanding this application and do not constitute a limitation on the network configuration method of the terminal device of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0172] In addition, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the network configuration method for a terminal device as described above.

[0173] The computer program product provided in this application can at least solve the technical problem that the inability to update the device association status in a timely and dynamic manner leads to errors in the remote server used by the terminal device. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as the beneficial effects of the network configuration method for the terminal device provided in the above embodiments, and will not be repeated here.

[0174] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent scope of this application.

Claims

1. A network configuration method for a terminal device, applied to a management server, comprising: Obtain a network configuration request from a terminal device, wherein the network configuration request carries device information corresponding to the terminal device; Based on the device information, the target operator information corresponding to the terminal device is obtained by querying the preset mapping relationship in the target sales information database, wherein the preset mapping relationship is set to be dynamically updated; A target configuration file is generated based on the target operator information and the device information. Based on the target configuration file, configuration information for connecting to the target remote server is sent to the terminal device to trigger the terminal device to establish a communication connection with the target remote server based on the configuration information.

2. The network configuration method for a terminal device as described in claim 1, characterized in that, The device information is obtained by encrypting the unique identification information corresponding to the terminal device. The type of the unique identification information is the device's serial number (SN), International Mobile Equipment Identity (IMEI), firmware version number, or software version number.

3. The network configuration method for a terminal device as described in claim 2, characterized in that, Based on the device information, the target operator information corresponding to the terminal device is obtained by querying a preset mapping relationship in the target sales information database. A target configuration file is generated based on the target operator information and the device information, including: The device information is decrypted to obtain the unique identification information; Based on the preset mapping relationship in the target sales information database, the operator information mapped by the unique identity information is obtained by querying, and the operator information mapped by the unique identity information is used as the target operator information corresponding to the terminal device. A target configuration file is generated based on the target operator information and the unique identification information.

4. The network configuration method for a terminal device as described in claim 1, characterized in that, Based on the target configuration file, the configuration information for connecting to the target remote server is sent to the terminal device, including: The target configuration file is encrypted to obtain the configuration information for connecting to the target server; The configuration information is sent to the terminal device.

5. The network configuration method for a terminal device as described in claim 4, characterized in that, After generating the target configuration file based on the target operator information and the device information, the method further includes: Verify the target configuration file; If the target configuration file passes verification, the step of encrypting the target configuration file to obtain configuration information for connecting to the target server is triggered.

6. The network configuration method for the terminal device as described in any one of claims 4 or 5, characterized in that, Sending the configuration information to the terminal device includes: If the network connection status with the terminal device is determined to be connected, the configuration information is sent directly to the terminal device; or, If the network connection with the terminal device is determined to be disconnected, the configuration information is sent to other devices, which then relay the configuration information to the terminal device via near-field communication.

7. A network configuration method for a terminal device, applied to the terminal device, comprising: The network configuration request of the terminal device is sent to the management server, wherein the network configuration request carries the device information corresponding to the terminal device; Upon receiving configuration information returned by the management server in response to the network configuration request, a communication connection is established with the target remote server based on the configuration information; The configuration information is determined by the management server based on the device information and the target operator information corresponding to the terminal device, and the target operator information is obtained by the management server in response to the device information from a preset mapping relationship stored in the target sales information database. The preset mapping relationship is set to be dynamically updated.

8. The network configuration method for a terminal device as described in claim 7, characterized in that, Before sending the network configuration request of the terminal device to the management server, the process includes: Read the unique identification information corresponding to the terminal device, wherein the type of the unique identification information is the device's serial number (SN), International Mobile Equipment Identity (IMEI), firmware version number, or software version number; The unique identification information is encrypted to obtain device information, and a network configuration request for the terminal device is generated based on the device information.

9. The network configuration method for a terminal device as described in claim 7 or 8, characterized in that, Sending the network configuration request of the terminal device to the management server includes: If the network connection status with the management server is determined to be connected, the network configuration request of the terminal device is sent directly to the management server; or, If the network connection with the management server is determined to be disconnected, the network configuration request of the terminal device is sent to other devices via near-field communication, and the network configuration request is then relayed to the management server through the other devices.

10. A management server, characterized in that, The management server includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the network configuration method for the terminal device as described in any one of claims 1 to 6.

11. A terminal device, characterized in that, The terminal device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the network configuration method of the terminal device as described in any one of claims 7 to 9.

12. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the network configuration method for a terminal device as described in any one of claims 1 to 6 or 7 to 9.

Images