Authenticity query method and terminal equipment thereof

Abstract

The invention relates to an authenticity query method and terminal equipment thereof. Automatically reading network access permission information of the terminal equipment and displaying a first user interface containing the network access permission information and authenticity query interaction elements; and when an input of selecting an authenticity query interaction element by a user is received, sending an authenticity query request carrying the network access permission information to an authenticity verification server, receiving an authenticity query result corresponding to the network access permission information from the authenticity verification server, and displaying the authenticity query result. According to the scheme provided by the invention, a user can intuitively see the network access permission information of the terminal equipment through the user interface of the terminal equipment and conveniently inquire the authenticity of the terminal equipment, so that the authenticity inquiry convenience of the terminal equipment is remarkably improved.

Description

[0001] This application is a divisional application of the original application with the application number 201880100352.0 and the original filing date of December 22, 2018, and the entire contents of the original application are incorporated herein by reference. TECHNICAL FIELD

[0002] The present disclosure relates to the field of intelligent terminals, and more particularly, to a true and false query method and a terminal device thereof. BACKGROUND

[0003] China implements a network access permit system for telecommunications terminal equipment, radio communication equipment and telecommunications equipment related to interconnection between networks that are used to access public telecommunications networks. Telecommunications equipment implementing the network access permit system must obtain a network access permit issued by the Ministry of Industry and Information Technology.

[0004] Telecommunications equipment manufacturing enterprises shall affix a network access permit mark on the telecommunications equipment they produce that has obtained a network access permit. The network access permit mark is uniformly printed and issued by the Ministry of Industry and Information Technology and is a kind of quality mark. The network access permit mark cannot be affixed on telecommunications equipment that has not obtained a network access permit or whose network access permit has expired. The network access permit mark contains information such as network access permit number, equipment model, and scrambling code. Users can query and verify the information on the network access permit mark through a webpage to verify the authenticity of the equipment.

[0005] However, the network access permit mark is affixed on the equipment shell in the form of a paper label, which affects the appearance of the equipment. Moreover, the paper label has a high cost in terms of delivery, transportation, storage, affixing, and inspection processes, and the paper label is not easy to keep. If the label information is damaged or lost, the subsequent true and false verification operation cannot be performed. Furthermore, the user needs to manually log in to the website and enter the network access permit mark information on paper, which is poor in terms of operation experience. SUMMARY

[0006] A true and false query method and a terminal device thereof are described herein, which can provide a convenient and fast true and false query method for the terminal device.

[0007] To achieve the above-mentioned purpose, the embodiments of the present application adopt the following technical solutions:

[0008] In a first aspect, the present application provides a terminal device authenticity query method. The authenticity query method comprises: automatically reading in-network license information, the in-network license information comprising one or any combination of the following: in-network license number, terminal device model, scrambling code, International Mobile Terminal Equipment Identity (IMEI), Mobile Equipment Identity (MEID), in-network license application unit, terminal device name, in-network license certificate validity period or issuance date; displaying a first user interface, the first user interface comprising the in-network license information and authenticity query interaction elements; obtaining a first touch input selecting the authenticity query interaction elements; in response to the first touch input, sending an authenticity query request to an authenticity verification server, the authenticity query request containing the in-network license information; receiving an authenticity query result corresponding to the in-network license information from the authenticity verification server; and displaying the authenticity query result.

[0009] In the above authenticity query method, the user can intuitively view the in-network license information through the user interface, and trigger the authenticity query request and display the authenticity query result through the user interface. Compared with the previous paper in-network license sign, the terminal device authenticity query rate can be improved, because: 1. The user no longer needs to manually input the in-network license number; 2. The risk of losing the paper in-network license sign is eliminated, and the user can query the authenticity of the terminal device at any time after purchasing the terminal device.

[0010] In some possible implementations, the above in-network license information is stored in the non-volatile memory (e.g., read-only memory (ROM) or flash memory) of the terminal device. In this way, when the terminal device is powered off, the stored in-network license information will not be lost, and the user can view the in-network license information of the terminal device at any time.

[0011] In some possible implementations, the in-network license information displayed by the above first user interface is recorded in a quick response matrix code (Quick Response Code).

[0012] In some possible implementation manners, the above-mentioned quick response matrix code further records a query website (for example, https:\\www.tenaa.com.cn) for authenticity. In this way, the user can scan the quick response matrix code displayed in the first user interface by using a second terminal device (different from the terminal device displaying the first user interface), obtain the network access permission information and the query website for authenticity recorded in the quick response matrix code, access the query website for authenticity, and send the network access permission information to the authenticity verification server (for example, by using an HTTP POST method) to obtain a query result corresponding to the network access permission information from the authenticity verification server, and display the query result corresponding to the network access permission information.

[0013] In the above-mentioned implementation manners, the user can query the authenticity of the terminal device with the aid of the second terminal device. For example, when the user's newly purchased terminal device (for example, a smart watch) cannot connect to a network, the authenticity of the terminal device can be queried by scanning the quick response matrix code displayed by the terminal device by using a second terminal device (for example, a smart phone).

[0014] In some possible implementation manners, the above-mentioned method for querying the authenticity of the terminal device further includes starting an operating system setting wizard, and the first user interface is displayed in the operating system setting wizard.

[0015] In the above-mentioned implementation manners, after the terminal device is started for the first time, the terminal device starts an operating system setting wizard, and the first user interface containing the network access permission information is displayed in the operating system setting wizard. In this way, the user can verify the authenticity of the terminal device when the terminal device is started for the first time after being purchased, and obtain the query result for authenticity in time, thereby avoiding the risk of being deceived.

[0016] In some possible implementation manners, the step of sending the query request for authenticity to the authenticity verification server includes generating a uniform resource locator (URL) containing the network access permission information, and accessing a resource identified by the URL in the authenticity verification server by using a web browser application.

[0017] In some possible implementation manners, the authenticity verification server verifies whether the terminal device is authentic by querying whether there is network access permission information corresponding to the terminal device in a network access permission information database. If there is network access permission information corresponding to the terminal device, the terminal device is legal; if there is no network access permission information corresponding to the terminal device, the terminal device is illegal.

[0018] In a second aspect, embodiments of the present application provide a terminal device, comprising: a processor, a memory, a bus and a communication interface; the memory is configured to store computer-executable instructions, the processor is connected with the memory through the bus, when the terminal device is running, the processor executes the computer-executable instructions stored in the memory, so that the terminal device executes any of the terminal device authenticity query methods described above.

[0019] In a third aspect, embodiments of the present application provide a computer-readable storage medium, the computer-readable storage medium stores instructions, when the instructions are running on any of the terminal devices described above, the terminal device executes any of the terminal device authenticity query methods described above.

[0020] In a fourth aspect, embodiments of the present application provide a computer program product comprising instructions, when the instructions are running on any of the terminal devices described above, the terminal device executes any of the terminal device authenticity query methods described above.

[0021] In addition, the technical effects brought by any of the design methods in the second to fourth aspects can refer to the technical effects brought by the different design methods in the first aspect, which will not be repeated here.

[0022] In a fifth aspect, embodiments of the present application provide another terminal device authenticity query method, the authenticity query method comprises: a terminal device receives an authenticity query instruction sent by an authenticity verification device; the terminal device starts an authentication process for the terminal device in response to the authenticity query instruction; when the terminal device is authenticated, the terminal device automatically reads the network access permit information, the network access permit information comprises one or any combination of the following items: network access permit number, terminal device model, scrambling code, international mobile terminal equipment identity (IMEI), mobile terminal equipment identity (MEID), network access permit application unit, terminal device name, network access permit certificate validity period or certificate date; the terminal device sends the above network access permit information to the authenticity verification device, so that the authenticity verification device obtains the authenticity query result corresponding to the network access permit information.

[0023] The authenticity query method is mainly aimed at counterfeit terminals produced by some counterfeit terminal manufacturers. For example, the counterfeit terminal can also display a first user interface similar to the first aspect described above, and display counterfeit network access license information and authenticity query interactive elements in the user interface. When the user selects the authenticity query interactive element, the counterfeit terminal directly displays a query result such as "the logo information you queried is true and corresponds to the product serial number". In fact, the network access license information displayed by the counterfeit terminal is all fake, and only looks similar to the network access license information displayed by a regular terminal device (for example, the counterfeit terminal also displays information such as a two-dimensional code and a terminal device model, a network access license number, a scrambling code, etc.), and when the user selects the authenticity query interactive element, the counterfeit terminal does not send an authenticity query request to the authenticity verification server, but directly displays the query result "the logo information you queried is true and corresponds to the product serial number", so as to make the user mistakenly believe that the product purchased is genuine. In this case, the counterfeit terminal does not access the authenticity verification server at all, but only makes the user mistakenly believe that the product purchased is genuine through the counterfeit network access license information and the counterfeit authenticity query result.

[0024] In the authenticity query method of the fifth aspect described above, the authenticity verification device can be a authenticity detection device provided by the Ministry of Industry and Information Technology. If the user suspects that the terminal device purchased is a counterfeit product, the terminal device can be sent to a professional detection institution recognized by the Ministry of Industry and Information Technology for verification by using the authenticity query method described above. If the terminal device is a genuine product after the authenticity query, it is proved that the user purchased a genuine product.

[0025] In some possible implementation manners, authentication of the terminal device is performed between the terminal device and the authenticity verification device based on an asymmetric key encryption algorithm. For example, the terminal device and the authenticity verification device store an asymmetric key pair (i.e., a public key and a private key), one party (e.g., the terminal device) uses the private key to encrypt specific data (e.g., a random number), and the other party (e.g., the authenticity verification device) uses the public key to decrypt the data, and if the decryption is successful, it is considered that the terminal device is authenticated successfully. After the terminal device is authenticated successfully, the terminal device reads the network access license information and transmits the network access license information to the authenticity verification device. The authenticity verification device queries whether the network access license information is stored in the network access license information database, and if the network access license information exists, it is proved that the terminal device is a genuine product. In one implementation manner, the authenticity verification device locally stores the network access license information database. In another implementation manner, the network access license information database is stored in an authenticity verification server, and the authenticity verification device accesses the network access license information database stored in the authenticity verification server to determine the authenticity of the terminal device.

[0026] In some possible implementation manners, after the terminal device is authenticated successfully, the terminal device sends a product serial number (IMEI, MEID or other unique identifier of the terminal device (for example, a hardware serial number)) of the terminal device to the authenticity verification device in addition to sending the network access permit information to the authenticity verification device. After obtaining the serial number, the authenticity verification device queries whether the serial number matches a stored serial number delivered by a terminal device manufacturer. If the serial numbers match, it is indicated that the terminal device is an authentic product.

[0027] By using any of the design manners in the fifth aspect, a user can verify the authenticity of a terminal device by using an authenticity verification device provided by a professional authentication institution, which can prevent counterfeit and substandard products from entering the market to some extent. BRIEF DESCRIPTION OF DRAWINGS

[0028] Figure 1 is a schematic diagram of an in-network license management system provided by an embodiment of the present application;

[0029] Figure 2 is a schematic diagram of an in-network license management method provided by an embodiment of the present application;

[0030] Figure 3 is a schematic diagram of a terminal device provided by an embodiment of the present application;

[0031] Figure 4A is a schematic diagram of an authenticity verification system of a terminal device provided by an embodiment of the present application;

[0032] Figure 4B is a schematic diagram of various in-network license electronic signs provided by an embodiment of the present application;

[0033] Figure 5 is a schematic diagram of querying authenticity of a terminal device in an operating system setup wizard provided by an embodiment of the present application;

[0034] Figure 6A is an exemplary user interface of querying authenticity of a terminal device provided by an embodiment of the present application;

[0035] Figure 6B is an exemplary user interface of a result of querying authenticity of a terminal device provided by an embodiment of the present application;

[0036] Figure 7 is another exemplary user interface of querying authenticity of a terminal device provided by an embodiment of the present application;

[0037] Figure 8A , 8B, 8C and 8D show yet another exemplary user interface of querying authenticity of a terminal device provided by an embodiment of the present application;

[0038] Figure 9is an exemplary method flowchart for querying terminal device authenticity provided by an embodiment of the present application;

[0039] Figure 10 is another terminal device structural schematic diagram provided by an embodiment of the present application;

[0040] Figure 11 is still another terminal device structural schematic diagram provided by an embodiment of the present application;

[0041] Figure 12 is a terminal device authenticity query system schematic diagram provided by an embodiment of the present application;

[0042] Figure 13 is another terminal device authenticity query exemplary process diagram provided by an embodiment of the present application;

[0043] Figure 14 is still another terminal device authenticity query exemplary process diagram provided by an embodiment of the present application. DETAILED DESCRIPTION

[0044] The technical solutions in the embodiments of the present disclosure will be described below with reference to the accompanying drawings in the embodiments of the present disclosure.

[0045] Figure 1 An architecture diagram of an in-network license management system 100 according to various examples is shown. In some examples, the system 100 can implement functions such as application acceptance, issuance of in-network licenses, and use monitoring of in-network licenses. The term “in-network license” refers to an in-network license issued by an in-network license management organization (e.g., the Ministry of Industry and Information Technology of China), and a communication device that obtains the in-network license is allowed to access a public communication network for use and sale. The term “in-network license electronic sign” refers to a quality sign stored in electronic data form on a communication device that obtains an in-network license (this is a term used in relation to a paper in-network license tag in the prior art), and the in-network license electronic sign records in-network license information of the device.

[0046] As shown in Figure 1 , in some examples, the in-network license management system 100 includes an in-network license management server 102, and a device vendor (e.g., a manufacturer of a terminal device) in-network license data management client 104, an in-network license import device 106, and a terminal device 108 (e.g., a mobile phone 108 or a watch 108 in Figure 1 The device vendor in-network license data management client 104 and the in-network license management server 102 can communicate through one or more networks 110 according to a client-server model.

[0047] The network access license management server 102 is provided by a network access license management organization (e.g., an official organization such as the Ministry of Industry and Information Technology of the People's Republic of China or other third-party network access license management organization) and is managed and maintained. The network access license data management server 102 can provide server-side functions for the network access license data management client 104 of the terminal equipment manufacturer, such as application, issuance, and use monitoring of the network access license of each equipment manufacturer.

[0048] The equipment manufacturer network access license data management client 104 is provided by the equipment manufacturer (e.g., a mobile phone or smart watch manufacturer) and is managed and maintained. The equipment manufacturer network access license data management client 104 can provide client-side functions such as network access license application and network access license use reporting for the equipment manufacturer and communication with the network access license data management server.

[0049] The network access license import device 106 can be a production device on the production line of the equipment manufacturer production workshop, responsible for obtaining the network access license from the equipment manufacturer network access license data management client 104 and importing the network access license information to the terminal equipment 108. In some embodiments, the network access license import device 106 obtains the network access license number, terminal equipment model, and scrambling code from the equipment manufacturer network access license data management client 104, concatenates the three parameters in order with a comma to form a string "NAL" (where NAL stands for (Network Access License), and the comma-concatenated NAL string can be "network access license number, terminal equipment model, scrambling code"). In one example, the NAL string can be "02-5043-163526, MHA-AL00, 9YP24PAA2C152TA". Then, the above string is written to the terminal equipment (e.g., stored in a non-volatile memory). In some implementations, the digital signature of the above string (e.g., using a hash value obtained by hashing the "NAL" string once, and then encrypting the hash value with the private key of an asymmetric encryption algorithm as a signature) is also written to the terminal equipment. Finally, the network access license import device 106 reads the written "NAL" string from the terminal equipment 108 to determine whether the string is correctly written. If the string read from the terminal equipment 108 matches the string written at the beginning, it is proved that the network access license information is successfully written. In some implementations, if the "NAL" string and the signature information are saved together in the terminal equipment, the network access license import device 106 reads the signature information and decrypts the signature with the public key to obtain the "NAL" string, and then determines whether the string matches the written "NAL" string.

[0050] The network access license import device 106 also notifies the device manufacturer network access license data management client 104 of the network access license use of the production line (for example, a terminal device product serial number (such as an International Mobile Equipment Identity (IMEI) or Mobile Equipment Identifier (MEID) or other terminal device unique identifier (for example, a hardware serial number)) and a correspondence table of network access license information corresponding to the terminal device product serial number, where the network access license information corresponds one-to-one to the terminal device product serial number) and ultimately passes the network access license management server 102. The network access license information includes one or any combination of the following: a network access license number, a terminal device model, a scrambling code, an International Mobile Equipment Identity (IMEI), a Mobile Equipment Identifier (MEID), a network access license application unit, a terminal device name, a network access license certificate validity period, or a certificate issue date. The scrambling code is a number that each terminal device uniquely possesses and has uniqueness like the International Mobile Equipment Identity (IMEI) or Mobile Equipment Identifier (MEID).

[0051] In some examples, the network access license management server 102 can include a client-facing external I / O interface 112, one or more processing modules 114, and a storage module 116. The client-facing external I / O interface 112 can communicate with the device vendor network access license data management client 104 through one or more networks 110. The one or more processing modules 114 can process network access license applications, network access license issuance, and network access license usage monitoring of the device vendor network access license data management client 104. In addition, the one or more processing modules 114 generate network access licenses based on the device quantity, device model, and the like reported by the device vendor. The storage module 116 is used to store data and instructions. Among them, the storage module 116 can store device vendor network access license application data (such as network access license application forms, device vendor enterprise information, device information, device quality inspection reports, and the like), or network access license information usage data. In some embodiments, the network access license information usage data can be a correspondence table of terminal device product serial numbers (such as International Mobile Equipment Identity (IMEI), or Mobile Equipment Identifier (MEID), or other terminal device unique identifier (for example, hardware serial number)) reported by the device vendor every month and network access license information, wherein the network access license information corresponds to the terminal device product serial number one by one. In some embodiments, the network access license information usage data can also be a correspondence table of terminal device product serial numbers and network access license information serial numbers (network access license information serial numbers can also be referred to as network access license electronic sign serial numbers). Among them, the network access license management server 102 allocates a corresponding serial number for each network access license information.

[0052] In some examples, the equipment vendor network access license data management client 104 may include a server-facing external I / O interface 118, one or more processing modules 120, and a storage module 122. The server-facing external I / O interface 118 can communicate with the network access license management server 102 via one or more networks 110. One or more processing modules 120 can apply for network access licenses and transmit network access license usage information to the network access license management server 102 via the external I / O interface 118. Furthermore, one or more processing modules 120 can transmit the number and model of devices to the network access license management server 102 via the external I / O interface 118 to apply for network access licenses. The storage module 122 is used to store data and instructions. Specifically, the storage module 122 can store equipment vendor network access license application data (e.g., device model, device name, device quantity, device quality certification information, etc.) and network access license usage data (e.g., a table recording the correspondence between terminal device product serial numbers (IMEI or MEID) and network access license information, where the network access license information corresponds one-to-one with the terminal device product serial number). Of course, the network access license information data can also be a mapping table between terminal device product serial numbers and network access license information serial numbers. Specifically, the network access license management server 102 assigns a corresponding serial number to each piece of network access license information.

[0053] Terminal device 108 can be any suitable electronic device (its structure is described below). Figure 3 The described electronic device 300 may be a mobile phone or other portable multi-functional device (e.g., a laptop or tablet). Additionally, in some examples, the terminal device 108 may be a non-portable multi-functional device. Specifically, the terminal device 108 may be a desktop computer, game console, television, or set-top box. In some examples, the terminal device 108 may include a touch-sensitive surface (e.g., a touchscreen display and / or touchpad). Furthermore, the terminal device 108 may optionally include one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick. In some examples, the terminal device 108 may be a wearable electronic device, such as a smartwatch, smart bracelet, etc.

[0054] Examples of communication network 110 may include local area networks (LANs) and wide area networks (WANs), such as the Internet. Communication network 110 can be implemented using any known network protocol, including various wired or wireless protocols such as, for example, Ethernet, Universal Serial Bus (USB), Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Long Term Evolution (LTE), Bluetooth, Wi-Fi, and any other suitable communication protocol.

[0055] The network access license management server system 100 can be implemented on one or more standalone data processing devices or distributed networks. In some examples, the server system 100 can also employ various virtual devices and / or services of third-party service providers (e.g., third-party cloud service providers) to provide potential computing resources and / or infrastructure resources of the server system 100.

[0056] Figure 2 A schematic diagram of a network access license management method according to various examples is shown.

[0057] At step 202, the device vendor sends a network access license obtaining request to the network access license management server 102 through the device vendor network access license data management client 104 before producing the terminal device. The network access license obtaining request carries one or any combination of the following parameters: device manufacturer, device name, device model, device quantity, or device quality inspection report.

[0058] At step 204, the network access license management server 102 verifies the network access license obtaining request submitted by the device vendor network access license data management client 104. If the network access license management server 102 verifies that the request meets the conditions, the network access license management server 102 generates a network access license and sends network access license information to the device vendor network access license data management client 104. The network access license information includes one or any combination of the following: network access license number, terminal device model, scrambling code, International Mobile Terminal Equipment Identity (IMEI), Mobile Equipment Identity (MEID), network access license application unit, terminal device name, network access license certificate validity period, or license issue date.

[0059] In some implementations, the network access license management server 102 can also send a serial number corresponding to the network access license information (which can also be referred to as a network access license electronic sign serial number) to the device vendor network access license data management client 104 at step 204 in order to record the number of network access license information sent. In this way, the network access license management server 102 can easily count the number of network access license electronic signs issued according to the serial number.

[0060] At step 206, the network access license management server 102 transmits the network access license information to the device vendor network access license data management client 104. Thereafter, the device vendor network access license data management client 104 stores the above network access license information to the storage module 122 and transmits it to the network access license import device 106 at step 208.

[0061] In step 208, the network access license import device 106 sends the network access license information to the terminal device 108. For example, the license import device 106 on the equipment manufacturer's production line sends the network access license information to the terminal device 108 via AT commands or Diag commands, and the terminal device 108 saves it, for example, in the manufacturer information (e.g., Original Equipment Manufacturer (OEM) Information) stored in the non-volatile memory of the terminal device 108. A corresponding signature is also saved along with the network access license information to verify the identity of the requester requesting access to the network access license information. Afterwards, the terminal device 108 can call a series of interfaces to access the network access license information. Taking the terminal device 108 running the Android operating system as an example, the application layer of the terminal device 108 (e.g., a settings application or an operating system setup wizard application) obtains the network access license information saved by the terminal device 108 through the interface for obtaining network access license information corresponding to the framework layer. The framework layer verifies the permissions of applications requesting access to network access license information. If malicious access by an unauthorized application is detected, its access request is denied; if the application requesting access to network access license information has the necessary permissions, it is allowed to access the network access license information.

[0062] In step 210, the license import device 106 reports the usage status of the network access license information to the equipment vendor's network access license data management client 104. Specifically, the license import device 106 reports the mobile terminal device identification code, terminal device product serial number (IMEI number or MEID number), and the corresponding network access license information mapping table based on the actual number of devices produced and used. There is a one-to-one correspondence between the network access license information and the terminal device product serial number of the terminal device 108.

[0063] In some implementations, in step 210, the format of the mapping table returned by the equipment manufacturer to the network access license management server 102 is "product serial number, network access license information serial number". If the terminal device has multiple product serial numbers (for example, if the terminal device supports multiple SIM cards, it will have multiple IMEI numbers), then the number of mapping tables returned by the equipment manufacturer to the network access license management server 102 is "product serial number 1, product serial number 2, network access license information serial number". For example, taking a terminal device with two IMEIs and two MEIDs as an example, the returned mapping is "IMEI1, IMEI2, MEID1, MEID2, network access license information serial number".

[0064] In step 212, the equipment vendor's network access license data management client 104 reports the usage status of the network access license information to the network access license management server 102. For example, the equipment vendor's network access license data management client 104 reports the mapping table between the terminal device product serial number (IMEI number and / or MEID number) and the corresponding network access license information to the network access license management server 102.

[0065] The following is an implementation plan for terminal equipment with network access license information or electronic network access license mark. Figure 3 An embodiment according to this disclosure is shown. Figure 1 A schematic diagram of the structure of the terminal device 108. This terminal device 108 is... Figure 3 The following explanation uses the electronic device 300 as an example.

[0066] Electronic device 300 may include processor 310, external memory interface 320, internal memory 321, universal serial bus (USB) interface 330, charging management module 340, power management module 341, battery 342, antenna 1, antenna 2, mobile communication module 350, wireless communication module 360, audio module 370, speaker 370A, receiver 370B, microphone 370C, headphone jack 370D, sensor module 380, button 390, motor 391, indicator 392, camera 393, display screen 394, and subscriber identification module (SIM) card interface 395, etc. The sensor module 380 may include a pressure sensor 380A, a gyroscope sensor 380B, a barometric pressure sensor 380C, a magnetic sensor 380D, an accelerometer sensor 380E, a distance sensor 380F, a proximity light sensor 380G, a fingerprint sensor 380H, a temperature sensor 380J, a touch sensor 380K, an ambient light sensor 380L, a bone conduction sensor 380M, etc.

[0067] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 300. In other embodiments of this application, the electronic device 300 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0068] Processor 310 may include one or more processing units, such as application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0069] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0070] The processor 310 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 310 is a cache memory. This memory can store instructions or data that the processor 310 has just used or that are used repeatedly. If the processor 310 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 310, and thus improves the efficiency of the system.

[0071] In some embodiments, the processor 310 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0072] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 310 may include multiple I2C buses. The processor 310 can couple to the touch sensor 380K, charger, flash, camera 393, etc., through different I2C bus interfaces. For example, the processor 310 can couple to the touch sensor 380K through the I2C interface, enabling the processor 310 and the touch sensor 380K to communicate through the I2C bus interface, thereby realizing the touch function of the electronic device 300.

[0073] The I2S interface can be used for audio communication. In some embodiments, the processor 310 may include multiple I2S buses. The processor 310 can be coupled to the audio module 370 via the I2S bus to enable communication between the processor 310 and the audio module 370. In some embodiments, the audio module 370 can transmit audio signals to the wireless communication module 360 ​​via the I2S interface to enable the function of answering phone calls through a Bluetooth headset.

[0074] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 370 and the wireless communication module 360 ​​can be coupled via the PCM bus interface. In some embodiments, the audio module 370 can also transmit audio signals to the wireless communication module 360 ​​via the PCM interface, enabling the function of answering phone calls through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0075] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 310 and the wireless communication module 360. For example, the processor 310 communicates with the Bluetooth module in the wireless communication module 360 ​​via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 370 can transmit audio signals to the wireless communication module 360 ​​via the UART interface to enable music playback through Bluetooth headphones.

[0076] The MIPI interface can be used to connect the processor 310 to peripheral devices such as the display screen 394 and the camera 393. The MIPI interface includes a camera serial interface (CSI) and a display serial interface (DSI). In some embodiments, the processor 310 and the camera 393 communicate via the CSI interface to enable the electronic device 300 to capture images. The processor 310 and the display screen 394 communicate via the DSI interface to enable the electronic device 300 to display images.

[0077] The GPIO interface can be configured via software. It can be configured as a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 310 to a camera 393, a display screen 394, a wireless communication module 360, an audio module 370, a sensor module 380, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0078] USB port 330 is a USB standard compliant interface, which can be a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 330 can be used to connect a charger to charge electronic device 300, and can also be used for data transfer between electronic device 300 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0079] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the electronic device 300. In other embodiments of this application, the electronic device 300 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0080] The charging management module 340 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 340 receives charging input from the wired charger via a USB interface 330. In some wireless charging embodiments, the charging management module 340 receives wireless charging input via the wireless charging coil of the electronic device 300. While charging the battery 342, the charging management module 340 can also supply power to the electronic device via the power management module 341.

[0081] The power management module 341 connects the battery 342, the charging management module 340, and the processor 310. The power management module 341 receives input from the battery 342 and / or the charging management module 340, providing power to the processor 310, internal memory 321, display screen 394, camera 393, and wireless communication module 360. The power management module 341 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 341 may be located within the processor 310. In other embodiments, the power management module 341 and the charging management module 340 may be housed in the same device.

[0082] The wireless communication function of electronic device 300 can be realized through antenna 1, antenna 2, mobile communication module 350, wireless communication module 360, modem processor and baseband processor, etc.

[0083] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 300 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0084] The mobile communication module 350 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 300. The mobile communication module 350 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 350 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 350 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 350 may be housed in the processor 310. In some embodiments, at least some functional modules of the mobile communication module 350 and at least some modules of the processor 310 may be housed in the same device.

[0085] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 370A, receiver 370B, etc.) or displays images or videos through a display screen 394. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 310 and may be housed in the same device as the mobile communication module 350 or other functional modules.

[0086] The wireless communication module 360 ​​can provide solutions for wireless communication applications on the electronic device 300, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 360 ​​can be one or more devices integrating at least one communication processing module. The wireless communication module 360 ​​receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signal, and sends the processed signal to processor 310. The wireless communication module 360 ​​can also receive signals to be transmitted from processor 310, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0087] In some embodiments, antenna 1 of electronic device 300 is coupled to mobile communication module 350, and antenna 2 is coupled to wireless communication module 360, enabling electronic device 300 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0088] Electronic device 300 implements display functions through a GPU, a display screen 394, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 394 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 310 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0089] Display screen 394 is used to display images, videos, etc. Display screen 394 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 300 may include one or N displays 394, where N is a positive integer greater than 1.

[0090] Electronic device 300 can achieve shooting function through ISP, camera 393, video codec, GPU, display 394 and application processor.

[0091] The ISP (Image Signal Processor) is used to process data fed back from the camera 393. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and skin tone. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 393.

[0092] Camera 393 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 300 may include one or N cameras 393, where N is a positive integer greater than 1.

[0093] A digital signal processor (DSP) is used to process digital signals. Besides digital image signals, it can also process other digital signals. For example, when the electronic device 300 is selecting a frequency, the DSP is used to perform Fourier transforms on the frequency energy.

[0094] Video codecs are used to compress or decompress digital video. Electronic device 300 may support one or more video codecs. Thus, electronic device 300 can play or record video in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0095] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs can enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0096] The external storage interface 320 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 300. The external memory card communicates with the processor 310 through the external storage interface 320 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0097] Internal memory 321 can be used to store computer executable program code, which includes instructions. Internal memory 321 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 300 (such as audio data, phonebook, etc.). Furthermore, internal memory 321 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 310 executes various functional applications and data processing of electronic device 300 by running instructions stored in internal memory 321 and / or instructions stored in memory located in the processor.

[0098] Electronic device 300 can implement audio functions such as music playback and recording through audio module 370, speaker 370A, receiver 370B, microphone 370C, headphone jack 370D, and application processor.

[0099] The audio module 370 is used to convert digital audio information into analog audio signal output, and also to convert analog audio input into digital audio signal. The audio module 370 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 370 may be located in the processor 310, or some functional modules of the audio module 370 may be located in the processor 310.

[0100] The speaker 370A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. Electronic device 300 can listen to music or make hands-free calls through the speaker 370A.

[0101] The receiver 370B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the electronic device 300 answers a telephone call or voice message, the receiver 370B can be brought close to the listener's ear to hear the voice.

[0102] Microphone 370C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 370C, inputting the sound signal into microphone 370C. Electronic device 300 may have at least one microphone 370C. In some embodiments, electronic device 300 may have two microphones 370C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, electronic device 300 may have three, four, or more microphones 370C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc.

[0103] The 370D headphone jack is used to connect wired headphones. The 370D headphone jack can be a USB 330 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

[0104] Pressure sensor 380A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 380A can be disposed on display screen 394. There are many types of pressure sensors 380A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 380A, the capacitance between the electrodes changes. Electronic device 300 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 394, electronic device 300 detects the intensity of the touch operation based on pressure sensor 380A. Electronic device 300 can also calculate the touch position based on the detection signal from pressure sensor 380A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example: when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

[0105] The gyroscope sensor 380B can be used to determine the motion attitude of the electronic device 300. In some embodiments, the gyroscope sensor 380B can determine the angular velocity of the electronic device 300 around three axes (i.e., the x, y, and z axes). The gyroscope sensor 380B can be used for image stabilization. For example, when the shutter is pressed, the gyroscope sensor 380B detects the angle of the electronic device 300's shake, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to counteract the shake of the electronic device 300 through reverse movement, thus achieving image stabilization. The gyroscope sensor 380B can also be used in navigation and motion-sensing game scenarios.

[0106] The barometric pressure sensor 380C is used to measure air pressure. In some embodiments, the electronic device 300 calculates altitude using the air pressure value measured by the barometric pressure sensor 380C to assist in positioning and navigation.

[0107] The magnetic sensor 380D includes a Hall sensor. The electronic device 300 can use the magnetic sensor 380D to detect the opening and closing of the flip cover. In some embodiments, when the electronic device 300 is a flip phone, the electronic device 300 can detect the opening and closing of the flip cover using the magnetic sensor 380D. Then, based on the detected opening and closing state of the cover or the flip cover, features such as automatic flip unlocking can be set.

[0108] The accelerometer 380E can detect the magnitude of acceleration of an electronic device 300 in various directions (typically three axes). When the electronic device 300 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the posture of the electronic device, and can be applied to applications such as screen orientation switching and pedometers.

[0109] A distance sensor 380F is used to measure distance. Electronic device 300 can measure distance via infrared or laser. In some embodiments, during a shooting scene, electronic device 300 can utilize the distance sensor 380F to measure distance for rapid focusing.

[0110] The proximity sensor 380G may include, for example, a light-emitting diode (LED) and a light detector, such as a photodiode. The LED may be an infrared LED. The electronic device 300 emits infrared light outward through the LED. The electronic device 300 uses the photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that an object is near the electronic device 300. When insufficient reflected light is detected, the electronic device 300 can determine that no object is near the electronic device 300. The electronic device 300 can use the proximity sensor 380G to detect when a user holds the electronic device 300 close to their ear for a call, so as to automatically turn off the screen to save power. The proximity sensor 380G can also be used in holster mode and pocket mode for automatic unlocking and locking of the screen.

[0111] The ambient light sensor 380L is used to sense the brightness of ambient light. The electronic device 300 can adaptively adjust the brightness of its display screen 394 based on the sensed ambient light level. The ambient light sensor 380L can also be used to automatically adjust the white balance when taking photos. The ambient light sensor 380L can also work in conjunction with the proximity sensor 380G to detect whether the electronic device 300 is in a pocket, preventing accidental touches.

[0112] The fingerprint sensor 380H is used to collect fingerprints. The electronic device 300 can utilize the characteristics of the collected fingerprints to achieve fingerprint unlocking, accessing application locks, taking photos with fingerprints, answering calls with fingerprints, etc.

[0113] Temperature sensor 380J is used to detect temperature. In some embodiments, electronic device 300 uses the temperature detected by temperature sensor 380J to execute a temperature handling strategy. For example, when the temperature reported by temperature sensor 380J exceeds a threshold, electronic device 300 performs thermal protection by reducing the performance of a processor located near temperature sensor 380J to reduce power consumption. In other embodiments, when the temperature is below another threshold, electronic device 300 heats battery 342 to prevent abnormal shutdown of electronic device 300 due to low temperature. In still other embodiments, when the temperature is below yet another threshold, electronic device 300 boosts the output voltage of battery 342 to prevent abnormal shutdown due to low temperature.

[0114] Touch sensor 380K, also known as a "touch panel," can be located on display screen 394. The touch sensor 380K and display screen 394 together form a touchscreen, also known as a "touch screen." Touch sensor 380K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 394. In other embodiments, touch sensor 380K may also be located on the surface of electronic device 300, in a different position than display screen 394.

[0115] The bone conduction sensor 380M can acquire vibration signals. In some embodiments, the bone conduction sensor 380M can acquire vibration signals from the vibrating bone segments of the human vocal cords. The bone conduction sensor 380M can also contact the human pulse to receive blood pressure signals. In some embodiments, the bone conduction sensor 380M can also be incorporated into headphones to form bone conduction headphones. The audio module 370 can parse the voice signals from the vibrating bone segments of the vocal cords acquired by the bone conduction sensor 380M to realize voice functionality. The application processor can parse heart rate information from the blood pressure signals acquired by the bone conduction sensor 380M to realize heart rate detection functionality.

[0116] Buttons 390 include a power button, volume buttons, etc. Buttons 390 can be mechanical buttons or touch-sensitive buttons. Electronic device 300 can receive button input and generate key signal inputs related to user settings and function control of electronic device 300.

[0117] Motor 391 can generate vibration alerts. Motor 391 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can be corresponding to touch operations applied to different applications (such as taking photos, playing audio, etc.). Motor 391 can also correspond to different vibration feedback effects for touch operations applied to different areas of the display screen 394. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0118] Indicator 392 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0119] The SIM card interface 395 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 395 to make contact with and separate from the electronic device 300. The electronic device 300 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 395 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 395 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 395 is also compatible with different types of SIM cards. The SIM card interface 395 is also compatible with external memory cards. The electronic device 300 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 300 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 300 and cannot be separated from the electronic device 300.

[0120] In this embodiment, the processor 310 can execute program instructions stored in the memory 340 to implement the method executed by the terminal device in the following embodiments.

[0121] The electronic network access license mark or network access license information is a quality mark affixed to terminal devices that have obtained a network access license. Terminal devices can use the authenticity verification function of the verification system provided by the network access license management organization to query and verify all network access license information. Figure 4A A schematic diagram of the architecture of a terminal device authenticity verification system 400 based on various examples is shown.

[0122] See Figure 4A The terminal device authenticity verification system 400 may include an authenticity query client 408 executed on a terminal device 402, and an authenticity verification server 404. The authenticity query client-side portion 408 can communicate with the authenticity verification server 404 via one or more networks 406. The authenticity query client 402 can provide client-side functions, such as providing an authenticity query interface, receiving user query input, sending authenticity query requests, and displaying authenticity query results. The authenticity query client 402 may store the IP address of the authenticity verification server 404 to establish a communication connection with it. In some embodiments, the authenticity query client 402 may also store the URL of the authenticity query server 404, access the URL of the authenticity verification server 404 through a browser, and query the IP address corresponding to the URL of the authenticity verification server 404 through the Domain Name System (DNS) to establish a communication connection with the authenticity verification server 404. The authenticity verification server 404 can provide server-side functions for authenticity query clients 408 from multiple terminal devices.

[0123] In some examples, terminal device 402 can also communicate with authentication server 404 via second terminal device 410. Second terminal device 410 can be similar to or the same as terminal device 402; for example, second terminal device 410 can be similar to the one described above. Figure 3 The described electronic device 300. A second terminal device 410 can store the address of the authenticity verification server 404, and can also obtain the IP address of the authenticity verification server 404 from terminal device 402 to establish a communication connection with the authenticity verification server 404. In some embodiments, the second terminal device 410 can store the authenticity query URL corresponding to the authenticity verification server 404. Alternatively, the second terminal device 410 can obtain the authenticity query URL corresponding to the authenticity verification server 404 from terminal device 402, and query the IP address corresponding to the authenticity query URL of the authenticity verification server 404 through the Domain Name System (DNS) to establish a communication connection with the authenticity verification server 404. The second terminal device 410 queries the authenticity of terminal device 402 by accessing the authenticity verification server 404. Terminal device 402 can be configured to communicate with the second terminal device 410 via a direct communication connection (such as Bluetooth, Near Field Communication (NFC), etc.) or via a wired or wireless network (such as a Wi-Fi network). In some examples, the second terminal device 410 may be configured to act as a proxy between terminal device 402 and the authenticity verification server 404. For example, the authenticity query client 408 of terminal device 108 may be configured to transmit information (e.g., an authenticity query request received at terminal device 402) to the authenticity verification server 404 via the second terminal device 408. The authenticity verification server 404 may process this information and return relevant data (e.g., query results in response to the user's authenticity query request) to terminal device 402 via the second terminal device 410.

[0124] In some examples, terminal device 402 may display network access license information (or electronic network access license mark), which can be presented through any of the following: Quick Response Code (QR code), two-dimensional barcode, one-dimensional barcode, or serial number. Second terminal device 410 obtains the network access license information by scanning the QR code, two-dimensional barcode, or one-dimensional barcode provided by terminal device 402 using a camera, and uses the network access license information to generate a complete authenticity query request and transmit it to authenticity verification server 404. Figure 4AThe illustrated system architecture allows for the use of a second terminal device 410 (e.g., a mobile phone, laptop computer, tablet computer, etc.) to verify the authenticity of terminal device 402. If terminal device 402 is a newly purchased device and temporarily unable to access the network, but the second terminal device 410 has stored the IP address of the authenticity verification server 404, a communication connection can be established with the authenticity verification server 404. The user can then use the second terminal device 410 to send the network access license information of terminal device 402 to the authenticity verification server 404 and verify the authenticity of terminal device 402.

[0125] In some implementation methods, the presentation format of network access license information can be referenced. Figure 4B . Figure 4B The diagram illustrates three presentation formats for network access license information. Terminal device 402 can display the network access license information using any of these formats. 420 represents network access license information presented solely as a quick response matrix code. The quick response matrix code 420 can record the network access license information, and may also record the URL of a verification website (e.g., https: / / www.tenaa.com.cn). In some implementations, when a user uses a second terminal device to scan the verification QR code displayed on the terminal device's screen, the verification website can be automatically accessed to check the authenticity of the terminal device and receive the verification result. In 422, in addition to the network access license information recorded in the fast response matrix code, the corresponding text recording the network access license information is also displayed (for example, the text shown in 422 includes the network access license number "02-5043-163526", the device model "MHA-AL00", the device product serial number SN "A123456789012345", the scrambling code "9YP24PAA2C152TA" and the authenticity verification website "https:\\www.tenaa.com.cn"). In section 424, in addition to the network access license information recorded in the fast response matrix code, the corresponding text recording the network access license information is also displayed (for example, the text shown in section 426 includes the network access license number "02-5043-163526", the device model "MHA-AL00", the scrambling code "9YP24PAA2C152TA" and the authenticity verification website "https:\\www.tenaa.com.cn"), and the terminal device product serial number shown in barcode 428 ("A123456789012345"). The terminal device product serial number can be either IMEI or MEID.

[0126] In some embodiments, the error correction code level of the network access license information QR code is at least Level L, and the QR code size is 80 pixels × 80 pixels or larger. If the QR code is printed out, the error correction code level of the network access license information QR code is at least Level Q. This ensures the accuracy of QR code scanning.

[0127] A 404 authentication server can query a license information database to verify the authenticity of a terminal device. In some implementations, the 404 authentication server can... Figure 1 The network access license management server 102 stores the network access license information corresponding to each terminal device (for example, it stores a one-to-one correspondence table between network access license information and terminal device product serial numbers). In some implementations, the authenticity verification server 404 can establish a connection with... Figure 1 The system establishes a communication connection with the network access license management server 102, thereby accessing the network access license information database of the network access license management server. In this way, the authenticity verification server 404 verifies the authenticity of the terminal device by querying the network access license information database to see if there is network access license information corresponding to the terminal device. If corresponding network access license information exists, the terminal device is considered legitimate; if no corresponding network access license information exists, the terminal device is considered illegitimate (or counterfeit).

[0128] although Figure 4A Only two terminal devices 402 and 410 are shown in the diagram, but it should be understood that system 400 may include any number and type of terminal devices configured to communicate with the authenticity verification server 404.

[0129] Users typically check the authenticity of newly purchased terminal devices, but the verification rate for paper network access license marks is relatively low. There are two reasons for this: first, users need to manually enter the network access license number, making the check inconvenient; second, the network access license mark affixed to licensed telecommunications equipment is easily discarded by users, who find it gone when they want to verify authenticity. Therefore, a new method is needed to verify the authenticity of terminal devices during out-of-box experience (OOBE). According to some embodiments of this application, when the terminal device is first powered on after being unpacked or after a system reset, the operating system setup wizard (e.g., Android / iOS setup wizard) is launched, and the authenticity of the terminal device is verified during the setup wizard process. The operating system setup wizard follows a standard operating system setup process, which may include setting the operating system language, downloading operating system updates and bug fixes, and requesting the user to enter a Wi-Fi password to set up the network. The operating system setup wizard provides an authenticity verification interface, through which users can verify the authenticity of the terminal device.

[0130] Figure 5 A model process diagram 500 is shown for using an operating system setup wizard at a terminal device to verify the authenticity of the terminal device. Process diagram 500 begins when the operating system setup wizard 502 is launched, for example, when the terminal device is first unpacked and powered on, or after a system reset. The operating system setup wizard (boot wizard) 502 begins setting up the operating system. The operating system setup wizard 502 displays language selection, WLAN settings, password / fingerprint settings, or other customized interfaces. Figure 5 In step 504, the operating system setup wizard 502 first presents a vendor-specific welcome screen. For example, a vendor-specific welcome screen may include the vendor's logo and the word "Welcome" displayed on the screen. The vendor-specific welcome screen may also include prompts for any information from the vendor to the user, such as confirmation of the user's service plan.

[0131] The operating system setup wizard 502 then presents the WLAN setup interface in step 506, requiring the user device to connect to Wi-Fi. If the user sees the router's name, they can click the router's name on the terminal device's Wi-Fi connection interface, enter the router's Wi-Fi password, and then click Connect to connect to the Wi-Fi network. After connecting to the Wi-Fi network, the user can then verify the device's authenticity or perform download operations. If the user chooses to skip step 506 (connecting to Wi-Fi), the user device will need to connect to a mobile network before verifying its authenticity or downloading software updates, which may consume a significant amount of mobile data.

[0132] The operating system setup wizard 502 then presents the authenticity verification interface in step 508. This interface displays network access license information and provides interactive elements (such as authenticity verification buttons) for users to check the authenticity of the device.

[0133] Next, in step 510, the operating system setup wizard 502 will provide a user account addition interface, prompting you to add a user account, such as a username and password for cloud storage. If the user already has an account, they can enter the username and password and then click Next. If the user does not have an account, they can click Create a new account and fill in the relevant account information.

[0134] The operating system setup wizard 502 then provides a fingerprint scanning and enrollment interface in step 512, offering a high level of security for the terminal device. If the user wishes to use it, they can click "Set up fingerprint" to begin the fingerprint enrollment process; users can also add multiple fingerprints.

[0135] Those skilled in the art will understand that, in addition to the manufacturer welcome screen, WLAN settings screen, authenticity verification screen, user account addition screen, and fingerprint scanning screen mentioned above, the operating system setup wizard 502 may present more or fewer screens or processes than illustrated, and this application embodiment does not limit this. Furthermore, the manufacturer welcome screen, WLAN settings screen, authenticity verification screen, user account addition screen, and fingerprint scanning screen can be presented in any predetermined order. Figure 5 The example shown is just one scenario. In some cases, the authenticity verification interface can be displayed after the manufacturer's welcome screen. Furthermore, users can select the back button to return to the previous screen for further operations; for example, a user can return from the authenticity verification interface to the WLAN settings interface.

[0136] Figure 6A It shows according to Figure 5 This describes a user interface 600 for verifying authenticity. Similar user interfaces can be found in... Figure 3 Implemented on electronic device 300. For example... Figure 6A As shown, in some implementations, the user interface 600 includes the following elements or a subset thereof: a network access license information QR code 602 (the QR code in the figure contains the letters "NAL", which stands for Network Access License); a network access license number 604; an applicant 606 (A terminal equipment manufacturer); a device name 608; a device model 610; and a authenticity verification button 612.

[0137] It should be pointed out that, Figure 6AThe information shown in the authenticity verification interface is merely exemplary. For example, in some embodiments, the user interface 600 may also include other elements, such as scrambling codes or terminal device serial numbers (terminal device serial numbers include IMEI, MEID, or product serial number SN).

[0138] In some implementations, the user interface 600 may only display a network access license information QR code 602. The QR code 602 may be encoded from one or any combination of the following: network access license number, terminal device model, scrambling code, IMEI, MEID, product serial number, authenticity verification website, International Mobile Equipment Identity (IMEI), Mobile Equipment Identity (MEID), network access license applicant, terminal device name, and network access license certificate validity period or issuance date. The user uses a second terminal device (e.g., Figure 4A The second terminal device (410) scans the QR code 602. The second terminal device decodes the QR code to obtain the network access license information encoded in the QR code, such as at least one of the following: network access license number, terminal device model, scrambling code, IMEI, MEID, International Mobile Equipment Identity (IMEI), Mobile Equipment Identity (MEID), network access license applicant, terminal device name, and network access license certificate validity period or issuance date. The second terminal device can establish a communication connection with the authenticity verification server 404 using the IP address of the authenticity verification server it stores, and send the parsed network access license information (e.g., network access license number, device model, and information such as scrambling code) to the authenticity verification server (e.g., the authenticity verification server 404 in Figure 4). The user can use the camera on the second terminal device to scan the authenticity query QR code displayed on the terminal device's screen, for example, by opening a website or a authenticity query mobile application (e.g., Figure 4A The second terminal device can activate the camera to scan QR codes using a QR code verification client (408). The second terminal device can install QR code reading software to capture and decode the captured QR codes. For example, the second terminal device displays a QR code scanning interface and prompts the user to align the second terminal device with the QR code displayed on the terminal device screen. The decoded network access license information can be sent to a verification server to verify the authenticity of the terminal device. The second terminal device can also encrypt the network access license information and... Figure 4A The Network 406 protocol sends encrypted network access license information to a verification server to enhance the security of communication transmission. The verification server can access the license information database to verify whether the device is genuine.

[0139] In some embodiments, the QR code 602 records the URL of a website for verifying authenticity (e.g., https: / / www.tenaa.com.cn). In some embodiments, when a user uses a second terminal device to scan the QR code displayed on the screen of the terminal device, the website can be automatically accessed to verify the authenticity of the terminal device and receive the verification result. In other embodiments, when a user uses a second terminal device to scan the QR code displayed on the screen of the terminal device, the website can be automatically opened, and the user can enter network access license information (e.g., license number, device model, scrambling code, etc.) on the website to verify the authenticity of the terminal device.

[0140] In some implementations, the user interface 600 may not include the network access license information QR code 602 (for example, the screen resolution of the terminal device may not support displaying the complete network access license information QR code). In this case, one or any combination of the following items may be displayed in text: network access license number, terminal device model, scrambling code, IMEI, MEID, International Mobile Terminal Equipment Identity (IMEI), Mobile Terminal Equipment Identity (MEID), network access license applicant, terminal device name, and network access license certificate validity period or issuance date. In some implementations, after a user clicks the authenticity verification button 612, the terminal device establishes a connection with the authenticity verification server using the stored address of the authenticity verification server (or accesses the authenticity verification server through the stored URL of the authenticity verification website), and then sends an authenticity verification request (the authenticity verification request may include any one or any combination of the following parameters: network access license number, terminal device model, scrambling code, International Mobile Equipment Identity (IMEI), Mobile Equipment Identity (MEID), network access license applicant, terminal device name, network access license certificate validity period or issuance date) to the authenticity verification server, thereby obtaining the authenticity of the terminal device, and presenting the authenticity verification result on the terminal device's user interface. In some implementations, the terminal device can use the HTTP protocol's POST request method to submit network access license information to the authenticity verification server. The terminal device can use a "JSON" structure to transmit network access license information; for example, the authenticity verification request represented by a "JSON" structure is as follows:

[0141] {"BizCode":"VLD",

[0142] "L":"02-5043-163526",

[0143] "M":"MHA-AL00",

[0144] "R":"9YP24PAA2C152TA",

[0145] "C":"861234567890123,A0FFFFFF000000F"}

[0146] Where “BizCode” represents the service identifier, with a default value of “VLD”, “L” represents the network access license number, “M” represents the device model, “R” represents the scrambling code of the terminal device, and “C” represents the serial number of the terminal device. If there are multiple serial numbers (such as “861234567890123” and “A0FFFFFF000000F” shown above), the serial numbers are separated by commas.

[0147] The query results returned by the authenticity verification server can also be transmitted using a "JSON" structure. For example, the authenticity query results represented by a "JSON" structure are as follows:

[0148] {"RspCode":"0000",

[0149] "Result": "The flag information you queried is true and corresponds to the product serial number. This device supports TD-LTE / LTEFDD / TD-SCDMA / WCDMA / cdma2000 / CDMA 1X / GSM standards."

[0150] Here, "RspCode" represents the processing result identifier returned by the authenticity verification server, with 0000 indicating success and 0001 indicating failure. "Result" represents the query result information (for example, as shown above, "The flag information you queried is true and corresponds to the product serial number. This device supports TD-LTE / LTE FDD / TD-SCDMA / WCDMA / cdma2000 / CDMA 1X / GSM standards."). The query result information includes the authenticity of the device's network access license electronic mark and the network standards supported by the device. Figure 6B An example page showing the authenticity query results is displayed, containing the query result "The flag information you queried is true and corresponds to the product serial number. This device supports TD-LTE / LTE FDD / TD-SCDMA / WCDMA / cdma2000 / CDMA 1X / GSM standards."

[0151] In some implementations, users can also click the authenticity verification button 612. The terminal device uses network access license information (e.g., network access license number, terminal device model, scrambling code, International Mobile Terminal Equipment Identity (IMEI), Mobile Terminal Equipment Identity (MEID), network access license applicant, terminal device name, network access license certificate validity period or issuance date, at least one of these) to construct an authenticity verification link. By accessing this authenticity verification link, a corresponding authenticity verification page can be displayed, thereby obtaining the authenticity of the terminal device.

[0152] One exemplary implementation is that after the user clicks the authenticity verification button 612, the terminal device automatically obtains one or any combination of the following: network access license number (SN), device model (MODEL), scrambling code (SCRAMBLE), and terminal device serial number (e.g., International Mobile Equipment Identity (IMEI)). This information is then concatenated into a Uniform Resource Locator (URL) for authenticity verification. For example, if the terminal device's network access license number is 02-5043-163526, the device model is MHA-AL00, the scrambling code is 9YP24PAA2C152TA, and the IMEI is A123456789012345, the concatenated URL would be:

[0153] http: / / www.tenaa.com.cn / WSFW / FlagValidate_test.aspx?SN=02-5043-163526&MODEL=MHA-AL00&SCRAMBLE=9YP24PAA2C152TA&IMEI=A123456789012345

[0154] As can be seen, the network access license number (SN), device model (MODEL), scrambling code (SCRAMBLE), and IMEI are concatenated to form a Uniform Resource Locator (URL) for authenticity verification. In response to the touch event of the authenticity verification request button 612, the terminal device automatically opens a browser application and accesses the above URL. Examples of browsers include Internet Explorer, Mozilla, Firefox, Netscape, and Chrome. When the Ministry of Industry and Information Technology's authenticity verification server receives a request from a user's browser using the above link, it automatically parses the four parameters (SN, MODEL, SCRAMBLE, IMEI) and returns an authenticity verification page. Figure 7As shown, after the terminal device opens a browser and accesses the above URL, the terminal device displays the Telecom Equipment Network Access Management Authenticity Information Query Page 700. Four parameters (SN, MODEL, SCRAMBLE, IMEI) appear in the corresponding query boxes (702, 704, 706, 708), and the user clicks the verification button 710 to perform the verification. The display interface for the verification results and... Figure 6B Similarly, for example, the page might contain the query result "The flag information you queried is true and corresponds to the product serial number. This device supports TD-LTE / LTE FDD / TD-SCDMA / WCDMA / cdma2000 / CDMA 1X / GSM standards."

[0155] The above mainly describes a method for verifying the authenticity of a terminal device during the out-of-box experience (OOBE). Users not only need to verify authenticity upon initial power-on, but also during daily use. Figure 8A-8D An exemplary user interface for authenticity verification on a terminal device according to some other implementations is shown. Figure 8A-8D The user interface shown can be accessed in [location]. Figure 3 It is implemented on the electronic device 300.

[0156] See Figure 8A User click Figure 8A Accessing the settings icon (802) leads to the settings interface, which includes basic adjustments to various device attributes and function on / off switches. Settings is the most convenient way for users to customize electronic devices (e.g., mobile phones) according to their personal preferences, and it's one of the most frequently used modules in daily life.

[0157] The settings interface includes modules such as Wireless and Networks (primarily responsible for WLAN management, mobile network management, and SIM card management), Users and Accounts (responsible for managing accounts and synchronization, cloud services, etc.), Display, Storage, Battery, and System (including system updates, About phone, language, and input method, etc.). Users can access these by clicking on the System module. Figure 8B The system information interface will be displayed; click on it again. Figure 8B Enter the "About phone" button to access 804 errors. Figure 8C The "About" screen shown contains a "Network Access License" option (806). Users can tap this option to access... Figure 8D The page displayed shows the authenticity verification information. Figure 6A similar, Figure 8D The user interface shown includes the following elements or a subset thereof: a network access license information QR code 808, a network access license number 810, an applicant 812, a device name 814, a device model 816, and a authenticity verification button 818. Users can also...Figure 8D Click the "Check Authenticity" button on the displayed page to verify the authenticity of the terminal device. Specific methods and... Figure 6A 6B and Figure 7 Similar examples are shown below; please refer to them. Figure 6A 6B and Figure 7 And the corresponding methods. For example, the user uses a second terminal device (e.g., Figure 4A The second terminal device 410 scans the QR code 808. The second terminal device decodes the QR code to obtain the network access license number, device model, and at least one piece of information such as a scrambling code, applicant organization, or device name encoded in the QR code. The second terminal device can send the parsed network access license information (e.g., network access license number, device model, and information such as a scrambling code) to a verification server (e.g., [server name]). Figure 4A The server returns a 404 error (or a 404 error) to verify the authenticity of the document. For example, after clicking the authenticity verification button (818), the user enters a similar... Figure 7 The authenticity verification webpage shown in the image allows users to check the authenticity of the terminal device.

[0158] Of course, in some implementations, network access license information can also be viewed and the authenticity of the terminal device can be verified by using specialized software installed on the terminal device (e.g., software provided by the Ministry of Industry and Information Technology).

[0159] Figure 9 A flowchart 900 illustrating an exemplary method for verifying the authenticity of a terminal device is shown. For example, process 900 can be initiated when a user first starts the terminal device, after resetting the terminal device system, or when a user accesses the authenticity verification function through the settings icon.

[0160] like Figure 9 As shown, process 900 begins at step 910, automatically reading the network access license information. The network access license information includes one or any combination of the following: network access license number, terminal device model, scrambling code, International Mobile Equipment Identity (IMEI), Mobile Equipment Identity (MEID), network access license applicant, terminal device name, and network access license certificate validity period or issuance date.

[0161] In some implementations, network access license information is stored in the non-volatile memory of the terminal device. This allows the terminal device to automatically read the stored network access license information upon first power-on and... Figure 6A The interface shown presents the network access license information.

[0162] In some implementations, the terminal device receives a first touch input from the user. In response to this first touch input, it automatically reads network access permission information. For example, it receives user input... Figure 8CAfter the first touch input of the user interface shown in Figure 806 to select the network access license option, the network access license information is obtained and displayed as follows. Figure 8D The corresponding network access license information is shown in the image. Of course, input methods other than touch input can also be used, such as other types of gesture input, like 3D gestures or gesture input involving the movement of the terminal device.

[0163] In step 920, a first user interface is displayed, which contains the network access license information (or network access license electronic mark).

[0164] Specifically, in some embodiments, after the terminal device is first started and its system is reset, the terminal device executes the operating system setup wizard. For example, Figure 5 The operating system setup wizard 502 shown in Figure 502 displays the WLAN settings interface in step 506. After obtaining the user's first touch input in the WLAN settings interface (e.g., clicking a button such as "Next" or "Skip" in the WLAN settings interface), it displays a first user interface (e.g., a authenticity query interface). In other embodiments, the user enters a settings interface similar to that shown in Figure 8 through a settings icon, and then proceeds step by step to... Figure 8C The "About phone" screen shown captures the user's first touch input on the "About phone" screen (e.g., the user taps...). Figure 8C After displaying the network access license option 806, the first user interface is shown (e.g., Figure 8D The authenticity verification interface is shown.

[0165] In some embodiments, the first user interface further includes an interactive element for verifying authenticity. The first interface may also display information such as the International Mobile Terminal Equipment Identity (IMEI), Mobile Terminal Equipment Identity (MEID), the applicant for the network access license, the name of the terminal device, and the validity period or issuance date of the network access license certificate. The interactive element for verifying authenticity may be... Figure 6A The authenticity verification button 612 or Figure 8D The authenticity verification button in the middle is 818.

[0166] In some embodiments, network access license information may be recorded in a quick response matrix code, or recorded in the form of text or images.

[0167] In step 930, a first touch input is received to select a true / false query interaction element. In some embodiments, the user selection is obtained. Figure 6A The authenticity verification button 612 or Figure 8D The first touch input of the authenticity verification button 818 (e.g., clicking) Figure 6A The authenticity verification button 612 or Figure 8D The authenticity verification button (818) is located in the middle.

[0168] In step 940, in response to the first touch input, a verification request is sent to a verification request server, the verification request containing the aforementioned network access license information. In some embodiments, a verification request (e.g., an HTTP GET request) can be sent to the verification request server via a browser. For example, the user selects... Figure 6A The authenticity verification button 612 or Figure 8D The first touch input of the authenticity verification button 818 (e.g., clicking) Figure 6A The authenticity verification button 612 or Figure 8D After clicking the authenticity verification button (818) in the settings, the terminal device uses network access license information (e.g., at least one of the following: network access license number, device model, scrambling code, or terminal device serial number) to construct an authenticity verification link (e.g., a Uniform Resource Locator (URL)). Accessing this authenticity verification link through a web browser will display the corresponding authenticity verification page (e.g., ...). Figure 6A The authenticity verification page shown in the image obtains the user's input when clicking the authenticity verification button on that page (e.g., when the user clicks...). Figure 8D The verification button 710 sends a authenticity query request to the authenticity verification server.

[0169] In other embodiments, in response to user selection Figure 7 The authenticity verification button 612 or Figure 7 The first touch input of the authenticity verification button 818 (e.g., clicking) Figure 6A The authenticity verification button 612 or Figure 8D The authenticity verification button (818) allows you to send a verification request to the authenticity verification server without opening a browser (for example, the terminal device stores the network address of the authenticity verification server, and you can use it through...). Figure 6A One or more networks 406 send a authenticity query request to the authenticity verification server 404 and receive the query result from the authenticity verification server.

[0170] In step 950, the authenticity query result corresponding to the aforementioned network access license information is received from the authenticity query request server. The authenticity verification server processes the authenticity query request, obtains the network access license information from the authenticity query request, and queries the license information database to verify the authenticity of the terminal device.

[0171] In step 960, the results of the authenticity check are displayed.

[0172] Using the method described in this application, users can intuitively view the network access license information of a terminal device through its user interface and conveniently verify the authenticity of the terminal device through its authenticity verification interface. Compared to the previous paper network access license mark, this method improves the accuracy of terminal device authenticity verification, allowing users to check the authenticity of the terminal device at any time after purchase.

[0173] This application embodiment can divide the terminal device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0174] When dividing functional modules according to their respective functions, such as Figure 8D As shown, this application embodiment provides a terminal device 1000, which includes a first reading unit 1001, a first display unit 1002, a first receiving unit 1003, a sending unit 1004, a second receiving unit 1005, and a second display unit 1006. The related actions of these functional modules can all be referenced from... Figure 4A In the relevant description, for example, the first reading unit 1001 is used to perform step 910, the first display unit 1002 is used to perform step 920, the first receiving unit 1003 is used to perform step 930, the sending unit is used to perform step 940, the second receiving unit 1005 is used to perform step 950, and the second display unit 1006 is used to perform step 960.

[0175] When using integrated units, such as Figure 10 As shown, another possible structural diagram of the terminal device involved in the above embodiments is illustrated, including a processing module 1101, a communication module 1102, an input / output module 1103, and a storage module 1104. Figure 9 The terminal device shown is used to perform the method embodiments described above (e.g., Figure 11 The terminal device authenticity verification method described above.

[0176] The processing module 1101 controls and manages the actions of the terminal device. The communication module 1102 supports communication between the terminal device and other network entities. The input / output module 1103 receives information input by the user or outputs information provided to the user, as well as various menus of the terminal. The storage module 904 stores the program code and data of the terminal device.

[0177] When the processing module 1101 is a processor (e.g.) Figure 11 The processor 310 shown, and the communication module 1102 are... Figure 9 The mobile communication module 350 or wireless communication module 360 ​​shown, and the storage module 1104 are memory (such as...) Figure 3 The memory 321 shown is an input / output module 1103, which is a display screen (e.g., memory 321). Figure 3 When the display screen 394 shown is displayed, the terminal device provided in this application can be Figure 3 The electronic device 300 shown. The processor, communication module, display screen, and memory described above can be coupled together via a bus.

[0178] This application embodiment also provides a terminal device, including a processor and a memory. The memory is used to store computer program code, which includes computer instructions. When the processor executes the computer instructions, it performs the method embodiment described above (e.g., ...). Figure 3 The terminal device authenticity verification method described above.

[0179] This application embodiment also provides a computer storage medium storing computer program code. When the processor executes the computer program code, the device performs... Figure 3 The relevant method steps in the document implement the method in the above embodiments.

[0180] This application also provides a computer program product that, when run on a computer, causes the computer to perform... Figure 9 The relevant method steps in the document implement the method in the above embodiments.

[0181] In some cases, counterfeit terminals produced by counterfeit terminal manufacturers can also display similar information. Figure 9 or Figure 9 The user interface shown displays counterfeit network access license information and provides similar authenticity verification elements. When a user selects one of these elements, the counterfeit terminal directly displays a query result such as "The information you queried is genuine and corresponds to the product serial number." In reality, when a user selects this element, the counterfeit terminal does not send a verification request to the authenticity verification server. Instead, it directly displays the result, misleading the user into believing they are purchasing a genuine product. In this scenario, the counterfeit terminal does not access the authenticity verification server at all; it simply uses the counterfeit network access license information and the counterfeit verification result to deceive the user into believing they are buying a genuine product.

[0182] In response to the above-mentioned situation where counterfeit terminals mislead consumers, this application embodiment also provides another terminal device authenticity verification system.

[0183] See Figure 6A , Figure 8D The system includes a authenticity verification device 1202 and a terminal device 1204. The authenticity verification device 1202 can detect the authenticity of the terminal device 1204. The authenticity verification device 1202 can be a genuine product provided by the Ministry of Industry and Information Technology (MIIT) or a third-party testing organization. If a user suspects that the purchased terminal device is counterfeit, they can submit it to a professional testing organization recognized by the MIIT and verify it using the authenticity verification device 1202. If the terminal device passes the authenticity verification test, it means that the user purchased a genuine product.

[0184] The authenticity verification device 1202 and the terminal device 1204 can establish a connection 1212 via a wired method, for example, through a USB Type C or micro USB cable. Of course, the authenticity verification device 1202 and the terminal device 1204 can be connected in other ways (e.g., wireless connection, or other wired connection methods), and this application embodiment does not limit this.

[0185] The authenticity verification device 1202 displays a device manufacturer configuration interface element 1204 and a device model configuration interface element 1208. The device manufacturer configuration interface element 1204 is used to configure the manufacturer of the terminal device to be verified. Users can select the manufacturer of the terminal device (e.g., manufacturer H shown in the figure) using the drop-down button shown in 1210. The device model configuration interface element 1208 is used to configure the model of the terminal device to be verified. Users can select the model of the terminal device (e.g., "MHA-AL00" shown in the figure) using the drop-down button 1214. Of course, the authenticity verification device 1202 may also display other detection parameter configuration interface elements; this embodiment does not limit this. After the detection parameters such as device manufacturer and device model are configured, the "Start Verification" button 1216 can receive selection input from the testing personnel to start the authenticity verification process. If the terminal device 1204 passes the authenticity verification test, the authenticity verification device 1202 can display a verification result such as "The flag information you queried is true and corresponds to the product serial number. This device supports TD-LTE / LTE FDD / TD-SCDMA / WCDMA / cdma2000 / CDMA 1X / GSM standards".

[0186] Figure 12 It shows the use of Figure 12 The diagram illustrates an exemplary process for verifying the authenticity of a terminal device.

[0187] In step 1302, the terminal device receives a verification command sent by the authenticity verification device; for example, the inspector selects... Figure 13 The "Start Verification" button 1216 shown indicates that the authenticity verification device sends an authenticity query command to the terminal device to start the authenticity verification process.

[0188] In step 1304, the terminal device initiates an authentication process for the terminal device in response to the authenticity query command;

[0189] In some embodiments, authentication of the terminal device and the authentication device is performed using an asymmetric key encryption algorithm. Both the terminal device and the authentication device store at least one key pair for authentication (the key pair includes a private key and a public key). For example, the terminal device stores a public key and the authentication device stores a private key; or the terminal device stores a private key and the authentication device stores a public key. If one party encrypts data using the public key, the other party can only decrypt it using the corresponding private key; if one party encrypts data using the private key, the other party can only decrypt it using the corresponding public key.

[0190] For example, the terminal device uses a private key to encrypt specific data (e.g., a random number or the terminal device's unique identifier), while the authentication device uses a public key to decrypt the data. If decryption is successful, the terminal device is considered successfully authenticated. After successful authentication, the terminal device reads the network access license information and transmits it to the authentication device. The authentication device checks whether the aforementioned network access license information is stored in the network access license information database. If it exists, it proves that the terminal device is genuine.

[0191] In some embodiments, the authentication device can also obtain the terminal device's certificate and send the certificate to the terminal device manufacturer's CA (Certificate Authority) management server for verification. If the verification is successful, it means that the authentication of the terminal device is successful.

[0192] In step 1306, after the terminal device is authenticated, the terminal device automatically reads the network access license information, which includes one or any combination of the following: network access license number, terminal device model, scrambling code, International Mobile Terminal Equipment Identifier (IMEI), Mobile Terminal Equipment Identifier (MEID), network access license applicant, terminal device name, and network access license certificate validity period or issuance date. The terminal device sends the above-mentioned network access license information to the authenticity verification device so that the authenticity verification device can obtain the authenticity query result corresponding to the network access license information.

[0193] In some embodiments, in step 1306, after the terminal device is authenticated, in addition to sending network access license information to the authenticity verification device, the terminal device also sends the terminal device's product serial number (the unique identifier of the terminal device, such as IMEI, MEID, or hardware serial number) to the authenticity verification device. After obtaining the product serial number, the authenticity verification device queries whether the serial number matches the serial number transmitted by the terminal device manufacturer stored in the system. If they match, it indicates that the terminal device is genuine.

[0194] Figure 12 Figure 1400 illustrates an exemplary process for verifying the authenticity of another terminal device.

[0195] like Figure 12 As shown, process 1400 begins at step 1402, where the authenticity verification device 1202 sends an authenticity query command to the terminal device 1204. For example, third-party authentication agencies or operators from the Ministry of Industry and Information Technology can use the interface presented by the authenticity verification device 1202 (e.g., ...). Figure 14 The "Start Verification" button 1216 on the operation interface of the authenticity verification device 1202 (shown in the diagram) initiates the authenticity verification process. The operation interface of the authenticity verification device 1202 can be configured with terminal device manufacturer information (e.g., manufacturer name) or terminal device model information. In response to receiving input from the operator selecting the "Start Verification" button, the authenticity verification device sends an authenticity query command to the terminal device 1204.

[0196] In step 1404, terminal device 1204 responds to the true / false query command by generating a random number; for example, terminal device 1204 uses a random number generator to generate a random number through some random number generation algorithms.

[0197] In step 1406, terminal device 1204 encrypts the random number; the encryption algorithm can be an asymmetric encryption algorithm, such as RSA, ECC (Elliptic Curve Cryptography), DSA (Digital Signature Algorithm), etc. Terminal device 1204 and authentication device 1202 store at least one key pair for authentication (the key pair includes a private key and a public key). For example, terminal device 1204 stores a public key, and authentication device 1202 stores a private key; or terminal device 1204 stores a private key, and authentication device 1202 stores a public key. If one party encrypts data using the public key, the other party can only decrypt it using the corresponding private key; if one party encrypts data using the private key, the other party can only decrypt it using the corresponding public key. In step 1406, terminal device 1204 can use the public key (or private key) from the first key pair to perform the encryption of the random number.

[0198] In step 1408, the encrypted random number is transmitted to the authenticity verification device 1202;

[0199] In step 1410, the authenticity verification device 1202 decrypts the encrypted random number; in step 1406, if the terminal device 1204 uses the public key in the first key pair to encrypt the random number, the authenticity verification device 1202 can use the private key in the stored first key pair to decrypt the encrypted random number.

[0200] In step 1412, the authenticity verification device 1202 re-encrypts the decrypted random number; in step 1412, the authenticity verification device 1202 can use the public key (or private key) in the second key pair to perform the encryption of the random number. In some embodiments, the second key pair may be different from the first key pair.

[0201] In step 1414, the authenticity verification device 1202 transmits the re-encrypted random number to the terminal device 1202.

[0202] In step 1416, terminal device 1204 decrypts the re-encrypted random number. If, in step 1412, the authenticity verification device 1202 uses the public key from the second key pair to encrypt the random number, then terminal device 1204 can decrypt the encrypted random number using the private key from the stored second key pair.

[0203] In step 1418, the terminal device compares the random number decrypted in step 1416 with the random number generated in step 1404. If they are the same, step 1420 is executed. If the verification in step 1418 fails, it proves that the terminal device is an illegal device, and the authenticity verification process ends.

[0204] In step 1420, the terminal device returns a successful authentication result to the authentication device. Steps 1402 to 1420 only illustrate one authentication process for terminal device 1204. The authentication device 1202 can perform various authentication operations on terminal device 1204 to ensure the legitimacy of terminal device 1204's identity. For example, in some embodiments, after step 1420, the authentication device 1202 can also obtain the terminal device's certificate and send it to the terminal device manufacturer's CA (Certificate Authority) management server for verification. If the verification passes, it indicates successful authentication of terminal device 1204. For example, in step 1422, the authentication device 1202 obtains the device certificate from terminal device 1204.

[0205] In step 1424, the authenticity verification device 1202 verifies the validity of the aforementioned device certificate, which is used to prove the identity of the terminal device. The authenticity verification device 1202 can send the certificate to the terminal device manufacturer's CA (Certificate Authority) management server for verification; if the device certificate is valid, step 1426 is executed; if the device certificate is invalid, it proves that the terminal device is an illegitimate device, and the authenticity verification process ends.

[0206] In step 1426, the authenticity verification device 1202 obtains the network access license information from the terminal device 1204, and in step 1428, the authenticity verification device 1202 verifies whether the network access license information is legal.

[0207] If the network access license information is valid, proceed to step 1430; if the network access license information is invalid, the authenticity verification process ends. The authenticity verification device stores the network access license information of the terminal device. The device compares the acquired network access license information with the stored device network access license information to determine whether the terminal device is valid.

[0208] In addition to sending network access license information to the authenticity verification device, the terminal device can also send the terminal device's product serial number (the unique identifier of the terminal device, such as IMEI, MEID, or hardware serial number) to the authenticity verification device in step 1430. After obtaining the product serial number, the authenticity verification device queries whether the serial number matches the serial number transmitted by the terminal device manufacturer stored in the device. If they match, it means that the terminal device is genuine.

[0209] In step 1230, the authenticity verification device obtains the device serial number from the terminal device, and in step 1232, the authenticity verification device verifies the device serial number (which can be the terminal device's product serial number, such as the International Mobile Equipment Identity (IMEI) or Mobile Equipment Identifier (MEID)). If the device serial number is valid, step 1230 is executed; if the network access license information is invalid, the authenticity verification process ends. The authenticity verification device stores the terminal device's serial number and compares the obtained network access license information with the stored device serial number to determine the validity of the terminal device.

[0210] Figure 14 Figure 12 Figure 14 The demonstrated authentication method verifies the legitimacy of a terminal device through four authentication methods: random number authentication, device certificate authentication, network access license information authentication, and device serial number authentication. Failure at any one of these authentication steps indicates the terminal device is illegitimate, significantly increasing the difficulty of counterfeiting terminal devices and thus protecting the legitimate rights and interests of terminal device manufacturers and consumers. Of course, in some embodiments, any one or a combination of the above four authentication methods can be selected to verify the legitimacy of the terminal device.

[0211] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, it can appear, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0212] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be covered within the scope of protection of this application.

Claims

1. A method for verifying the authenticity of a terminal device, characterized in that, The method is applied to a terminal device, the terminal device including an interface for obtaining network access license information, the method comprising: By calling the interface, network access license information is obtained. The network access license information includes one or any combination of the following items: network access license number, terminal device model, scrambling code, international mobile terminal device identification code, mobile terminal device identification code, network access license applicant, terminal device name, network access license certificate validity period or issuance date. Display a first user interface, which includes the network access license information and authenticity query interactive elements; Receive the first input for selecting the authenticity query interaction element; In response to the first input, a verification request is sent to the server, the verification request containing the network access license information; Receive the authenticity query results corresponding to the network access license information from the server; Display the results of the authenticity query.

2. The method according to claim 1, characterized in that, Before obtaining the network access license information, the method further includes: Verify the permissions of the application requesting access to the network access license information; If the application has permission to access the network access license information, the application is allowed to access the network access license information.

3. The method according to claim 2, characterized in that, The applications include setup applications or operating system setup wizard applications.

4. The method according to claim 2, characterized in that, The application is located in the application layer of the operating system of the terminal device.

5. The method according to claim 1, characterized in that, The interface is located in the framework layer of the operating system of the terminal device.

6. The method according to claim 1, characterized in that, The authenticity verification result includes query result information, and displaying the authenticity verification result specifically includes: Display the query result information in the true / false query results.

7. The method according to claim 6, characterized in that, The authenticity query result also includes a processing result identifier, which is used to indicate success or failure.

8. The method according to claim 6 or 7, characterized in that, The results of the authenticity query are transmitted in JSON format.

9. The method according to claim 1, characterized in that, The authenticity query request is transmitted in JSON format.

10. The method as described in claim 1, characterized in that, The network access license information is stored in the non-volatile memory of the terminal device.

11. The method as described in claim 1 or 10, characterized in that, The network access license information displayed on the first user interface is recorded in the fast response matrix code.

12. The method as described in claim 1, characterized in that, The method further includes: The operating system setup wizard is launched, wherein the first user interface is presented during the operating system setup wizard process.

13. The method as described in claim 1, characterized in that, Sending the authenticity query request to the server includes: Generate a Uniform Resource Locator (URL) that contains the network access license information; Access the resource identified by the Uniform Resource Locator in the server through a web browser.

14. The method as described in claim 1, characterized in that, The server is managed by the network access license management organization.

15. A terminal device, comprising a memory, one or more processors, multiple applications, and one or more programs; wherein the one or more programs are stored in the memory; characterized in that, The terminal device includes an interface for obtaining network access license information. When the one or more processors execute the one or more programs, the terminal device performs the following steps: By calling the interface, network access license information is obtained. The network access license information includes one or any combination of the following items: network access license number, terminal device model, scrambling code, international mobile terminal device identification code, mobile terminal device identification code, network access license applicant, terminal device name, network access license certificate validity period or issuance date. Display a first user interface, which includes the network access license information and authenticity query interactive elements; Receive the first input for selecting the authenticity query interaction element; In response to the first input, a authenticity query request is sent to the authenticity verification server. The authenticity query request includes the network access license information. The authenticity verification server is managed by the network access license management organization. Receive the authenticity query results corresponding to the network access license information from the authenticity verification server; Display the results of the authenticity query.

16. The terminal device as described in claim 15, characterized in that, When the one or more processors execute the one or more programs, the terminal device also performs the following steps: Verify the permissions of the application requesting access to the network access license information; If the application has permission to access the network access license information, the application is allowed to access the network access license information.

17. The terminal device as described in claim 16, characterized in that, The applications include setup applications or operating system setup wizard applications.

18. The terminal device as described in claim 16, characterized in that, The application is located in the application layer of the operating system of the terminal device.

19. The terminal device as described in claim 15, characterized in that, The interface is located in the framework layer of the operating system of the terminal device.

20. The terminal device as described in claim 15, characterized in that, The authenticity query result includes query result information. When the one or more processors execute the one or more programs, the terminal device also performs the following steps: Display the query result information in the true / false query results.

21. The terminal device as described in claim 20, characterized in that, The authenticity query result also includes a processing result identifier, which is used to indicate success or failure.

22. The terminal device as described in claim 20 or 21, characterized in that, The results of the authenticity query are transmitted in JSON format.

23. The terminal device as described in claim 15, characterized in that, The authenticity query request is transmitted in JSON format.

24. The terminal device as described in claim 15, characterized in that, The network access license information is stored in the non-volatile memory of the terminal device.

25. The terminal device as described in claim 15 or 24, characterized in that, The network access license information displayed on the first user interface is recorded in the fast response matrix code.

26. The terminal device as described in claim 15, characterized in that, When the one or more processors execute the one or more programs, the terminal device also performs the following steps: The operating system setup wizard is launched, wherein the first user interface is presented during the operating system setup wizard process.

27. The terminal device as described in claim 15, characterized in that, Sending the authenticity query request to the authenticity verification server includes: Generate a Uniform Resource Locator (URL) that contains the network access license information; Access the resource identified by the Uniform Resource Locator in the authenticity verification server through a web browser.

28. The terminal device as described in claim 15, characterized in that, The server is managed by the network access license management organization.

29. A computer program product containing instructions, characterized in that, When the computer program product is run on a terminal device, the terminal device performs the method as described in any one of claims 1-14.

30. A computer-readable storage medium comprising instructions, characterized in that, When the instructions are executed on a terminal device, the terminal device causes the terminal device to perform the method as described in any one of claims 1-14.

Images