A multi-handle terminal access authentication method and system for a cosmetic device

Abstract

The application relates to the technical field of communication access authentication, and discloses a beauty equipment multi-handle terminal access authentication method and system, which comprises the following steps: a handle terminal collects interface identification parameters and determines a candidate hardware identity; a mainboard sends identity query messages in sequence through a shared communication bus, obtains a response hardware identity and a software identity; the current query hardware identity is used to query an identity registration relationship, and a registration software identity is obtained; when the hardware identity and the software identity are consistent, a directional verification message is sent, and an authentication result is determined according to a verification response; and the handle terminal that passes the authentication is registered as an effective access terminal and subsequent communication is carried out. The application reduces the possibility of mismatch between the actual identity and the communication identity in the multi-handle access process by combining handle hardware identification, software identity verification and directional verification, and improves the accuracy of terminal access identification and communication relationship establishment.

Description

Technical Field

[0001] This invention relates to the field of communication access authentication technology, and more specifically, to a method and system for access authentication of multi-handheld terminals for beauty devices. Background Technology

[0002] Beauty devices typically consist of a main unit and multiple functional handles connected to it. These handles can perform functions such as freezing, heating, pneumatic operation, or other functions depending on the beauty procedure. The main unit and handles exchange device identity, operating status, and parameters via a serial communication link, and establish a communication relationship based on the handle's connection status. For pluggable handles, existing device access technologies usually obtain terminal identification information after the handle is inserted or reconnected, and determine whether the terminal is allowed to participate in subsequent communication through identity recognition or access authentication.

[0003] For example, Chinese invention patent application CN103221962A discloses a peripheral device authentication technology. The host device determines whether the peripheral device can be authenticated based on information read or received from the peripheral device, and further determines the trusted status of the peripheral device through an authentication protocol. The peripheral device identification information can be obtained using the resistance on the interface identification line. This application can achieve identity verification before the peripheral device connects. However, in scenarios where multiple pluggable functional terminals are connected to the same host, frequent plugging and unplugging, reconnection, or sharing of communication links can lead to mismatches between the access entity and the identity information used during communication. The host may find it difficult to accurately determine which access terminal the current response data actually comes from, easily causing confusion in terminal identity recognition and errors in establishing subsequent communication relationships.

[0004] Therefore, it is necessary to design a multi-handheld terminal access authentication method and system for beauty devices to solve the problems existing in the current technology. Summary of the Invention

[0005] In view of this, the present invention proposes a method and system for authentication of multi-handheld terminal access in beauty devices, aiming to solve the problem that the actual identity and communication identity of the terminal are easily mismatched during the access process of multi-handheld terminals, making it difficult for the motherboard to accurately identify the access terminal and establish a reliable communication relationship.

[0006] This invention proposes a multi-handheld terminal access authentication method for beauty devices, comprising: For gamepad terminals connected to the motherboard, the gamepad terminal collects the identification parameters of the gamepad interface and determines the candidate hardware identity identifier based on the identity range in which the identification parameters are located. The handheld terminal sequentially sends identity query messages carrying query hardware identity identifiers through a shared communication bus. When the query hardware identity identifier matches its own candidate hardware identity identifier, the handheld terminal returns an identity response message and obtains the response hardware identity identifier and software identity identifier from the identity response message. Based on the current hardware identity identifier, query the pre-established identity registration relationship to obtain the registration software identity identifier; When the responding hardware identity identifier is consistent with the currently queried hardware identity identifier, and the software identity identifier is consistent with the registered software identity identifier, a targeted verification message is sent with the currently queried hardware identity identifier; if a verification response message carrying the same hardware identity identifier is received within the response period, the authentication is determined to be successful; otherwise, the authentication is determined to be unsuccessful. Register authenticated gamepads as valid access terminals and conduct subsequent communication according to the currently queried hardware identity; leave unauthenticated gamepads in an unauthenticated state.

[0007] Further, determining the candidate hardware identity includes: The voltage divider of the identification resistor at the handle interface is collected, and the resistance value of the identification resistor is determined based on the voltage divider. The resistance value of the identification resistor is compared with each identity interval, and the hardware identity identifier that falls into the identity interval is determined as the candidate hardware identity identifier. If it does not fall into any identity interval, it remains in an unidentified state.

[0008] Furthermore, when sending the identity query message, the following are included: Hardware identity identifiers are selected one by one according to the pre-set query order as the current query hardware identity identifier, and an identity query message carrying the current query hardware identity identifier is sent; after the current response period ends, the next hardware identity identifier is selected for query.

[0009] Furthermore, when returning the identity response message, it includes: The handset terminal checks the identity query message for its frame header, length, and checksum. If the check passes, it extracts the query hardware identity identifier. When the query hardware identity identifier matches its own candidate hardware identity identifier, the candidate hardware identity identifier is used as the response hardware identity identifier and written into the identity response message along with the locally stored software identity identifier.

[0010] Furthermore, the identity registration relationship consists of a hardware identity identifier and an allowed access software identity identifier; the identity registration relationship is retrieved using the currently queried hardware identity identifier, and if the retrieval is successful, the registered software identity identifier is read; if the currently queried hardware identity identifier is not found, the authentication is determined to have failed.

[0011] Furthermore, when performing identity consistency checks, the following steps are included: Compare the response hardware identity identifier with the currently queried hardware identity identifier; if they match, continue to compare the software identity identifier with the registered software identity identifier; if both comparisons match, proceed to targeted verification; if either comparison does not match, authentication is deemed unsuccessful.

[0012] Furthermore, the targeted verification includes: Write the current queried hardware identity into the address field of the directed verification message and send it; the handset terminal whose candidate hardware identity matches the address field returns a verification response message; if the verification response message is received within the response period, and the frame check passes and the hardware identity in it matches the current queried hardware identity, the authentication is confirmed to be successful.

[0013] Furthermore, when the identity consistency judgment fails or the targeted verification fails, the following applies: Retain the currently queried hardware identity and continue to query the remaining hardware identities; after completing one round of queries, re-authenticate the retained queried hardware identity, and remain unauthenticated if the re-authentication fails.

[0014] Furthermore, periodic communication is performed with the valid access terminal; when no valid response is received, the connection count of the valid access terminal is increased, and when a valid response is received, the connection count is decreased; when the connection count reaches the offline threshold, the valid access state is cleared, and when the handheld terminal is detected again, access authentication is performed again.

[0015] Compared with existing technologies, the advantages of this invention are as follows: The gamepad terminal determines candidate hardware identity identifiers based on interface identification parameters, and the motherboard sequentially sends identity query messages via a shared communication bus to obtain the actual response hardware identity identifier and software identity identifier returned by the gamepad terminal. Based on this, the registered software identity identifier is obtained from a pre-established identity registration relationship according to the currently queried hardware identity identifier. A consistency check is performed on the response hardware identity identifier, the queried hardware identity identifier, the software identity identifier, and the registered software identity identifier. If the identities match, a targeted verification is further performed using the currently queried hardware identity identifier. Only gamepad terminals that have completed the identity consistency check and targeted verification are registered as valid access terminals. Therefore, in situations where multiple gamepad terminals share a communication bus and are plugged in, replaced, or reconnected, the hardware identity formed by the gamepad interface, the terminal identity returned by actual communication, and the allowed access identity registered by the motherboard can be combined for continuous confirmation. This avoids establishing communication relationships directly based on a single identity information, reduces the possibility of mismatch between the actual access identity of the gamepad and the identity used during communication, leading to incorrect access or communication, and improves the accuracy and reliability of multi-gamepad terminal access identification and subsequent communication relationship establishment.

[0016] On the other hand, this application also provides a multi-handheld terminal access authentication system for beauty devices, used to apply the above-mentioned multi-handheld terminal access authentication method for beauty devices, including: The identity recognition unit is used to collect the recognition parameters of the gamepad interface of the gamepad terminal connected to the motherboard, and determine the candidate hardware identity identifier based on the identity range in which the recognition parameters are located. An identity query unit is used to sequentially send identity query messages carrying query hardware identity identifiers via a shared communication bus. When the query hardware identity identifier matches its own candidate hardware identity identifier, the handle terminal returns an identity response message and obtains the response hardware identity identifier and software identity identifier from the identity response message. The registration and query unit is used to query pre-established identity registration relationships based on the current query hardware identity identifier to obtain the registration software identity identifier; An identity authentication unit is configured to send a directed verification message using the current query hardware identity when the responding hardware identity is consistent with the currently queried hardware identity and the software identity is consistent with the registered software identity; and to determine that authentication is successful when a verification response message carrying the same hardware identity is received within the response period, otherwise to determine that authentication is unsuccessful. The access management unit is used to register authenticated handset terminals as valid access terminals and conduct subsequent communication according to the currently queried hardware identity identifier; and to keep unauthenticated handset terminals in an unauthenticated state.

[0017] It is understandable that the above-mentioned multi-handheld terminal access authentication method and system for beauty devices have the same beneficial effects, and will not be elaborated further here. Attached Figure Description

[0018] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 A flowchart of a multi-handheld terminal access authentication method for beauty devices provided in an embodiment of the present invention; Figure 2 This is a flowchart of the multi-handheld terminal authentication process provided in an embodiment of the present invention; Figure 3 This is a functional block diagram of a multi-handle terminal access authentication system for beauty devices provided in an embodiment of the present invention. Detailed Implementation

[0019] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the disclosure to those skilled in the art. It should be noted that, unless otherwise specified, embodiments and features in the embodiments of the present invention can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0020] In some embodiments of this application, see Figures 1-2 As shown, this application proposes a multi-handheld terminal access authentication method for beauty devices, including: S100: For gamepad terminals connected to the motherboard, the gamepad terminal collects the identification parameters of the gamepad interface and determines the candidate hardware identity identifier based on the identity range in which the identification parameters are located. S200: The handheld terminal sequentially sends identity query messages carrying the query hardware identity identifier through the shared communication bus. When the query hardware identity identifier matches its own candidate hardware identity identifier, the handheld terminal returns an identity response message and obtains the response hardware identity identifier and software identity identifier from the identity response message. S300: Based on the current query hardware identity identifier, query the pre-established identity registration relationship to obtain the registration software identity identifier; S400: When the responding hardware identity identifier is consistent with the currently queried hardware identity identifier and the software identity identifier is consistent with the registered software identity identifier, a directed verification message is sent with the currently queried hardware identity identifier; if a verification response message carrying the same hardware identity identifier is received within the response period, the authentication is determined to be successful; otherwise, the authentication is determined to be unsuccessful. S500: Registers authenticated handset terminals as valid access terminals and performs subsequent communication according to the currently queried hardware identity identifier; keeps unauthenticated handset terminals in an unauthenticated state.

[0021] Specifically, in one embodiment, the beauty device includes a motherboard, a shared communication bus, and multiple pluggable handheld terminals. The multiple handheld terminals are connected to the motherboard via the same shared communication bus. The motherboard is responsible for sending query messages to each handheld terminal and receiving data returned by the handheld terminals. In this embodiment, the shared communication bus uses an RS485 bus. The handheld terminals are equipped with a processor, an identification resistor sampling circuit, and an RS485 communication interface. The processor acquires the identification parameters of the handheld interface through an ADC.

[0022] Under normal operating conditions, different gamepads connected to the same shared communication bus use different gamepad physical identities. When the motherboard queries a specific hardware identity, only gamepads with that hardware identity respond, thus enabling each gamepad to participate in communication on the same communication bus according to its respective identity.

[0023] In this embodiment, the candidate hardware identity identifier refers to the hardware identity determined locally by the gamepad terminal based on its own interface identification parameters; the query hardware identity identifier refers to the hardware identity carried in the current identity query message of the motherboard; and the response hardware identity identifier refers to the hardware identity written by the gamepad terminal in the identity response message and actually received by the motherboard. The software identity identifier is a pre-set software ID in the gamepad program, and the registered software identity identifier is obtained by the motherboard from the identity registration relationship based on the currently query hardware identity identifier.

[0024] The handle interface is equipped with an identification resistor, which is connected to a voltage divider circuit. The voltage divider node is connected to the ID_Pin of the handle terminal processor. When the beauty device is powered on, the handle terminal is inserted, or handle identification is re-performed, the handle terminal starts ADC sampling. The handle terminal can collect the voltage data of ID_Pin within a 100ms task and convert the collected voltage into the resistance value of the identification resistor according to the voltage divider circuit.

[0025] To reduce the impact of single-sample fluctuations on the identity recognition results, multiple ADC sample values ​​can be continuously acquired during a single recognition process, for example, 8 to 16 sample values. After removing the maximum and minimum values, the remaining sample values ​​are averaged, and the recognition resistor value is calculated according to the ADC reference voltage and voltage divider relationship. ADC sampling and resistance value calculation based on the voltage divider can employ conventional resistor voltage divider processing methods.

[0026] In this embodiment, 500Ω, 1000Ω, 1500Ω, 2000Ω, and 3000Ω resistors can be used as identification resistors for five different handle types, forming identification ranges approximately 10% above and below the nominal resistance value. For example, 450Ω–550Ω corresponds to ID1, 900Ω–1100Ω to ID2, 1350Ω–1650Ω to ID3, 1800Ω–2200Ω to ID4, and 2700Ω–3300Ω to ID5.

[0027] When using identification resistors of different specifications, the identity range can also be redefined. Specifically, the handle terminals corresponding to each specification of identification resistor can be plugged in and sampled multiple times under normal conditions. The resistance range obtained by each specification of identification resistor under normal conditions is recorded, and a certain error margin is reserved on both sides of the resistance range. Then, it is checked whether adjacent identity ranges overlap. If they overlap, the error margin or the nominal resistance value of the adjacent identification resistor is adjusted so that a normal identification resistance value falls into only one identity range.

[0028] After obtaining the resistance value of the identification resistor, the controller terminal compares it with each identity interval. When the resistance value falls into a certain identity interval, the hardware identity identifier marked in that identity interval is determined as a candidate hardware identity identifier; when the resistance value does not fall into any identity interval, the controller terminal remains in an unidentified state and can re-identify in subsequent sampling cycles.

[0029] For example, if a gamepad terminal calculates an identification resistance value of 1018Ω, and since 1018Ω falls within the 900Ω to 1100Ω identity range, ID2 is determined as a candidate hardware identity identifier for this gamepad terminal. If the calculated identification resistance value is 1250Ω, this value is neither within the ID2 identity range nor the ID3 identity range, so it remains unidentified and is not directly assigned to that identity based on its proximity to a certain nominal resistance value.

[0030] After completing local identification, the motherboard begins identity lookup. The motherboard has pre-set queryable hardware identifiers, such as ID1 to ID5, and queries are performed sequentially according to ID1, ID2, ID3, ID4, and ID5. Each time a query is performed, a hardware identifier is selected from this query sequence as the currently queried hardware identifier.

[0031] In this embodiment, the RS485 messages between the motherboard and the gamepad terminal use 0xBB55 as the frame header. The message may include a length field, an identity field, a type field, a command field, a data field, and a CRC field. When sending an identity query message, the current hardware identity identifier is written into the identity field, and the identity query command is written into the command field.

[0032] The CRC field is used to check for data errors during message transmission. The sending end calculates the checksum according to the CRC rule used by both the motherboard and the gamepad terminal, and writes the checksum into the message. After receiving the message, the receiving end recalculates the checksum according to the same rule and compares them. If the checksums match, the message continues to be processed; if the checksums do not match, the current message is discarded.

[0033] After sending the identity query message, the motherboard enters a response period and does not switch to the next hardware identity identifier before the end of the current response period. The response period can be determined based on the communication time required for a normal gamepad terminal to complete one identity query and identity response. Specifically, during device debugging, the identity query can be repeatedly executed, and the time required from sending the identity query message to receiving the complete identity response message can be recorded, with a certain margin added to the larger normal response time.

[0034] For example, if the response time during normal communication is approximately 12ms, the response period can be set to 18ms to 20ms. This embodiment uses 20ms as the response period for one identity query. This response period is used for one query and response during the access authentication phase, and is a different timing process from the 100ms periodic communication used during normal device operation.

[0035] Upon receiving an identity query message, each handset terminal on the shared communication bus first checks the frame header, length, and checksum. If the check fails, the current message is not processed further; if the check passes, the query hardware identity identifier is read from the identity query message and compared with its own candidate hardware identity identifier.

[0036] If the two are inconsistent, the controller terminal does not return an identity response message; if they are consistent, the controller terminal generates an identity response message, writes its own candidate hardware identity identifier into the identity response message, and uses this field as the response hardware identity identifier. At the same time, it reads the locally stored software identity identifier and writes the software identity identifier into the identity response message as well.

[0037] The software identity identifier can be pre-saved as a configuration parameter in the gamepad program, for example, using numbers such as SID01, SID02, etc. After the gamepad receives the identity query command and meets the identity response conditions, it reads the current software identity identifier and returns it to the motherboard along with the responding hardware identity identifier.

[0038] For example, a certain gamepad terminal has a candidate hardware identity identifier of ID2 and a software identity identifier of SID02. When the motherboard queries ID1, the gamepad terminal determines that the queried hardware identity ID1 is inconsistent with the candidate hardware identity ID2, and therefore does not return an identity response; when the motherboard queries ID2, the two are consistent, and the gamepad terminal returns an identity response message containing the responses for hardware identity ID2 and software identity SID02.

[0039] The motherboard pre-establishes an identity registration relationship to record the combination of hardware and software identity identifiers that beauty devices are allowed to access. This identity registration relationship can be stored in a non-volatile memory area readable by the motherboard and retrieved when access authentication is required.

[0040] For example, identity registration relationships can be established between ID1 and SID01, ID2 and SID02, ID3 and SID03, ID4 and SID04, and ID5 and SID05. When establishing identity registration relationships, based on the identity of the handle and its software identity that the beauty device is allowed to use, the hardware identity identifier and the allowed access software identity identifier are written into the same registration record.

[0041] Upon receiving the identity response message, the motherboard retrieves the responding hardware identity identifier and software identity identifier from the message and searches for identity registration relationships based on the currently queried hardware identity identifier. If a registration record for the currently queried hardware identity identifier is found, the software identity identifier within that record is read and used as the registered software identity identifier. If the currently queried hardware identity identifier is not found in the identity registration relationships, the current authentication is deemed unsuccessful, and subsequent targeted verification is not performed.

[0042] After obtaining the registered software identity identifier, the motherboard first compares the responded hardware identity identifier with the currently queried hardware identity identifier. If they match, it continues to compare the software identity identifier and the registered software identity identifier; if they do not match, it determines that the current identity consistency judgment has failed.

[0043] It's important to note that the comparison between the responding hardware identity and the currently queried hardware identity is a check performed by the motherboard after receiving the identity response message; it's not a re-identification of the controller's identity using another hardware parameter. Normally, the controller only generates an identity response message when the queried hardware identity matches its own candidate hardware identity. Therefore, the returned responding hardware identity usually matches the currently queried hardware identity. However, because the motherboard continuously queries based on multiple hardware identities, the receiving end still confirms whether the message belongs to the current query process based on the actual responding hardware identity carried in the identity response message.

[0044] For example, when the motherboard is currently processing the query result for ID2, it will only use the response hardware identity in the identity response message to continue subsequent software identity verification. If the received identity response message carries a different hardware identity, it means that the message is inconsistent with the currently queried hardware identity, and the motherboard will not use the message to continue completing this authentication. This ensures that the current query process and the actual received identity response message are consistent.

[0045] After the hardware identity identifier matches the currently queried hardware identity identifier, the motherboard continues to compare the software identity identifier with the registered software identity identifier. The software identity can be determined by comparing complete values; if the two values ​​match, the software identities are considered consistent; otherwise, they are considered inconsistent.

[0046] For example, the motherboard currently queries ID2, reads the responding hardware identity ID2 and software identity SID02 from the identity response message, and reads the registered software identity SID02 of ID2 from the identity registration relationship. At this time, the responding hardware identity matches the currently queried hardware identity, and the software identity also matches the registered software identity, so it proceeds to targeted verification. If the responding hardware identity is ID2, but the software identity is SID03, then the software identity verification fails, and targeted verification does not proceed.

[0047] After the identity consistency check is passed, the motherboard further performs targeted verification instead of directly registering the current gamepad terminal as a valid access terminal. The motherboard generates a targeted verification message and writes the currently queried hardware identity identifier into the address field of the targeted verification message.

[0048] Upon receiving a directed authentication message, the handset terminal on the shared communication bus performs a frame check on the message and reads the addressing field. Handetset terminals whose candidate hardware identity matches the hardware identity in the addressing field return an authentication response message; other handset terminals do not return this response message. The authentication response message must contain at least the hardware identity of the handetset terminal.

[0049] After the motherboard sends the directed verification message, it enters the response period. Upon receiving a verification response message during the response period, it performs a frame check on the message and reads the hardware identity identifier. If the frame check passes and the hardware identity identifier in the response message matches the currently queried hardware identity identifier, the directed verification is confirmed to be successful, and the current gamepad terminal authentication is confirmed to be successful.

[0050] If no verification response message is received within the response period, or the received verification response message fails the frame check, or the hardware identity identifier in the verification response message is inconsistent with the currently queried hardware identity identifier, then the targeted verification is determined to have failed.

[0051] Therefore, the aforementioned identity response stage is mainly used to obtain the hardware identity and software identity returned by the current controller terminal, and to complete the identity attribution check and software identity registration verification of the current response message; the targeted verification stage is to initiate a targeted communication with the confirmed query hardware identity after the aforementioned judgment is passed, and determine the final authentication result based on whether the controller can return a verification response normally according to the hardware identity.

[0052] Taking ID2 as an example, the motherboard has already obtained ID2 and SID02 through the identity response message and confirmed that they are consistent with the currently queried hardware identity and identity registration relationship. Subsequently, the motherboard sends a directed verification message with ID2 as the address field. The gamepad terminal with candidate hardware identity ID2 returns a verification response message carrying ID2. If the motherboard receives this message within the 20ms response period, and the frame check passes and the read hardware identity is still ID2, then the gamepad terminal is confirmed to be successfully authenticated.

[0053] When the identity consistency judgment fails or the targeted verification fails, the motherboard retains the currently queried hardware identity identifier and continues to complete the query of the remaining hardware identity identifiers in this round, instead of continuously sending authentication messages to the same hardware identity.

[0054] After completing one round of queries, the motherboard performs access authentication again on the hardware identity identifiers retained from this round. The re-authentication process follows the same sequence: identity query, identity response, identity registration relationship query, identity consistency judgment, and targeted verification. If the re-authentication succeeds, a valid access state is established; if the re-authentication fails again, the user remains in an unauthenticated state.

[0055] This embodiment employs a single re-authentication. In actual use, the number of re-authentications can be determined based on the operation of the shared communication bus. For example, an occasional message anomaly during normal communication can usually be resolved during the next query, allowing for a single re-authentication. For devices with complex communication environments, the number of re-authentications can be increased, but excessively long continuous authentication times should be avoided to prevent interference with access queries from other handset terminals.

[0056] After the handheld terminal is authenticated, the motherboard registers it as a valid access terminal and saves the confirmed hardware identity, software identity, authentication status, and connection count in the handheld status table. In actual beauty equipment, the handheld status table can also save operating data such as working status, temperature, target temperature, water flow, and air pressure.

[0057] After establishing a valid access state, the motherboard sends a regular query message or control message to the handset terminal according to the authenticated hardware identity. Upon receiving a regular communication message, the handset terminal continues to filter messages based on the identity field, processing only messages whose identity field matches its own hardware identity. Handset terminals that fail authentication do not establish a valid access state and do not enter normal service communication.

[0058] For a handset terminal that has established a valid access status, the motherboard performs periodic communication. In this embodiment, a 100ms period is used as the normal communication period. Within each communication period, the motherboard sends a status query message to the validly accessed terminal.

[0059] If no valid response is received during the current communication cycle, the connection count of the valid access terminal is increased by 1; if a valid response is received that passes frame inspection and confirms the correct identity, the connection count is decreased. This embodiment specifically uses the method of reducing the connection count to 0. Therefore, the connection count can reflect the situation where the currently valid access terminal has continuously failed to establish valid communication.

[0060] The offline threshold can be determined based on the possibility of consecutive unresponsive events occurring under normal connection conditions. Specifically, the handset terminal can maintain a normal connection and continuously perform periodic communication, recording the maximum number of consecutive unresponsive events without actual disconnection, and retaining a certain margin as the offline threshold.

[0061] For example, if the maximum number of consecutive unresponsive attempts under normal communication conditions is 2, the offline threshold can be set to 5. In a 100ms communication cycle, if no valid response is received for 5 consecutive communication cycles, the connection count reaches 5, and the motherboard clears the valid access status of the gamepad terminal.

[0062] If the gamepad is subsequently connected or detected again, the motherboard does not directly restore the cleared valid access status. Instead, it re-identifies and re-authenticates the gamepad. After successful re-authentication, the gamepad is then registered as a valid access terminal.

[0063] In one complete embodiment, the beauty device includes a motherboard and handheld terminals A, B, C, and D connected via the same RS485 bus. The motherboard sets five queryable hardware identities: ID1, ID2, ID3, ID4, and ID5, and performs queries in the order of ID1 to ID5.

[0064] The motherboard pre-stores the identity registration relationships, where the software identity registered under ID1 is SID01, ID2 is SID02, ID3 is SID03, ID4 is SID04, and ID5 is SID05. The response time for identity query and targeted verification is set to 20ms, the normal business communication cycle is set to 100ms, and the offline threshold is set to 5.

[0065] After the four gamepad terminals are connected, each terminal acquires its own ID_Pin. After ADC sampling and voltage division, gamepad terminal A obtains an identification resistor value of 508Ω, gamepad terminal B obtains 996Ω, gamepad terminal C obtains 1518Ω, and gamepad terminal D obtains 1984Ω. Based on the aforementioned identity range, gamepad terminal A determines candidate hardware identity ID1, gamepad terminal B determines candidate hardware identity ID2, gamepad terminal C determines candidate hardware identity ID3, and gamepad terminal D determines candidate hardware identity ID4.

[0066] The software identity identifier for gamepad terminal A is SID01, that for gamepad terminal B is SID02, that for gamepad terminal C is SID08, and that for gamepad terminal D is SID04. Notably, the software identity SID08 of gamepad terminal C is different from the software identity SID03 registered in ID3 of the motherboard identity registration relationship.

[0067] The motherboard first queries ID1. After receiving the identity query message, gamepad terminal A completes frame checking, confirming that the queried hardware identity ID1 matches its own candidate hardware identity ID1. Therefore, it generates an identity response message, writing the response hardware identity ID1 and software identity SID01 into the message and returning it. Other gamepad terminals, because their own candidate hardware identity is not ID1, do not return identity response messages.

[0068] After receiving the identity response message within the 20ms response period, the motherboard reads the response hardware identity ID1 and software identity SID01 from the message, and retrieves the identity registration relationship based on the currently queried hardware identity ID1 to obtain the registered software identity SID01.

[0069] The motherboard first confirms that the response hardware identity ID1 in the currently received identity response message is consistent with the query hardware identity ID1 being processed, thus confirming that the current response message belongs to the ID1 query process; then it compares the software identity SID01 with the registered software identity SID01, and the two are consistent, so it enters the targeted verification.

[0070] The motherboard sends a directed authentication message with address field ID1. After receiving this message, gamepad terminal A returns an authentication response message carrying ID1. The motherboard receives this message within 20ms, confirms that the frame check is successful and the hardware identity is still ID1, thus determining that gamepad terminal A has been authenticated and registering it as a valid access terminal.

[0071] The motherboard then queries ID2. Gamepad B returns a response with hardware identity ID2 and software identity SID02. The motherboard retrieves the registered software identity SID02 from the identity registration relationship. Since the hardware identity ID2 matches the currently queried ID2, and the software identity SID02 matches the registered software identity SID02, the targeted verification of ID2 continues. After successful targeted verification, gamepad B is registered as a valid access terminal.

[0072] The motherboard continues querying ID3. The gamepad terminal C returns a response with hardware identity ID3 and software identity SID08. The motherboard retrieves the registered software identity SID03 from the identity registration relationship. The response hardware identity ID3 matches the currently queried hardware identity ID3, therefore the current identity response message belongs to the ID3 query process; however, the software identity SID08 differs from the registered software identity SID03, therefore the identity consistency check fails. The motherboard retains ID3 and continues querying the next hardware identity, without establishing a valid access state for ID3.

[0073] When the motherboard queries ID4, the gamepad terminal D returns ID4 and SID04. The motherboard obtains the registered software identity SID04 from ID4, and after responding to identity checks, software identity verification, and targeted verification, registers the gamepad terminal D as a valid access terminal.

[0074] When the motherboard queries ID5, since there is currently no candidate hardware terminal with ID5, no identity response message is received within the 20ms response period, and this ID5 query ends.

[0075] After completing one round of queries for IDs 1 through 5, the motherboard reads ID 3, which was retained in this round, and performs another access authentication on ID 3. The gamepad terminal C returns ID 3 and SID 08 again. The motherboard still reads the registration software identity as SID 03, therefore the second authentication fails again, and the gamepad terminal C remains unauthenticated.

[0076] After completing this round of authentication, controller terminals A, B, and D enter the valid access state. The motherboard conducts normal business communication according to ID1, ID2, and ID4 respectively, and sends status query messages at a period of 100ms.

[0077] For example, if the controller terminal B does not receive a valid response for two consecutive communication cycles during normal connection, its connection count increases from 0 to 2; after receiving a valid response again in the third communication cycle, the connection count decreases from 2 to 0, and the controller terminal B continues to maintain a valid access state.

[0078] After the controller terminal D is unplugged, the motherboard fails to obtain a valid response from ID4 for five consecutive 100ms communication cycles. The connection count increases to the offline threshold of 5, and the motherboard clears the valid access status of the controller terminal D.

[0079] When a gamepad terminal with ID4 identity is connected again, the motherboard does not directly use the original valid access state. Instead, the gamepad terminal re-collects the interface identification parameters and re-executes the candidate hardware identity determination, identity query, identity registration relationship query, response identity check, software identity verification, and targeted verification. After successful re-authentication, the valid access state of ID4 is then established.

[0080] Through the above process, the gamepad terminal first obtains candidate hardware identities based on interface identification parameters. The motherboard then queries each hardware identity item by item and uses the identity response message to confirm the consistency between the current communication response and the queried identity. At the same time, it verifies whether the software identity meets the identity registration relationship. After the above judgment is passed, it confirms through targeted verification that the gamepad can complete targeted communication according to the current hardware identity. Only gamepad terminals that have completed the above authentication establish a valid access state, and this state is cleared if there is a continuous loss of connection, thus forming a complete process of gamepad identity recognition, access authentication, and subsequent communication management.

[0081] Based on another preferred embodiment described above, see [link to preferred embodiment]. Figure 3 As shown, this embodiment provides a multi-handheld terminal access authentication system for beauty devices, used to apply the above-mentioned multi-handheld terminal access authentication method for beauty devices, including: The identity recognition unit is used to collect the recognition parameters of the gamepad interface of the gamepad terminal connected to the motherboard, and determine the candidate hardware identity identifier based on the identity range in which the recognition parameters are located. The identity query unit is used to send identity query messages carrying the query hardware identity identifier sequentially through the shared communication bus. When the query hardware identity identifier matches its own candidate hardware identity identifier, the handheld terminal returns an identity response message and obtains the response hardware identity identifier and software identity identifier from the identity response message. The registration and query unit is used to query pre-established identity registration relationships based on the current query hardware identity identifier to obtain the registration software identity identifier; The identity authentication unit is used to send a directed verification message with the current query hardware identity when the responding hardware identity is consistent with the currently queried hardware identity and the software identity is consistent with the registered software identity; if a verification response message carrying the same hardware identity is received within the response period, the authentication is determined to be successful; otherwise, the authentication is determined to be unsuccessful. The access management unit is used to register authenticated handset terminals as valid access terminals and conduct subsequent communication according to the currently queried hardware identity identifier; and to keep unauthenticated handset terminals in an unauthenticated state.

[0082] It is understandable that the above-mentioned multi-handheld terminal access authentication method and system for beauty devices have the same beneficial effects, and will not be elaborated further here.

[0083] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do not depart from the spirit and scope of the present invention should be covered within the protection scope of the present invention.

Claims

1. A method for authentication of multi-handheld terminals in a beauty device, characterized in that, include: For gamepad terminals connected to the motherboard, the gamepad terminal collects the identification parameters of the gamepad interface and determines the candidate hardware identity identifier based on the identity range in which the identification parameters are located. The handheld terminal sequentially sends identity query messages carrying query hardware identity identifiers through a shared communication bus. When the query hardware identity identifier matches its own candidate hardware identity identifier, the handheld terminal returns an identity response message and obtains the response hardware identity identifier and software identity identifier from the identity response message. Based on the current hardware identity identifier, query the pre-established identity registration relationship to obtain the registration software identity identifier; When the responding hardware identity identifier is consistent with the currently queried hardware identity identifier, and the software identity identifier is consistent with the registered software identity identifier, a targeted verification message is sent using the currently queried hardware identity identifier; If a verification response message carrying the same hardware identity is received within the response period, the authentication is deemed successful; otherwise, the authentication is deemed unsuccessful. Register authenticated gamepads as valid access terminals and conduct subsequent communication according to the currently queried hardware identity; leave unauthenticated gamepads in an unauthenticated state.

2. The multi-handheld terminal access authentication method for beauty devices according to claim 1, characterized in that, Determining the candidate hardware identity includes: The voltage divider of the identification resistor at the handle interface is collected, and the resistance value of the identification resistor is determined based on the voltage divider. The resistance value of the identification resistor is compared with each identity interval, and the hardware identity identifier that falls into the identity interval is determined as the candidate hardware identity identifier. If it does not fall into any identity interval, it remains in an unidentified state.

3. The multi-handheld terminal access authentication method for beauty devices according to claim 1, characterized in that, Sending the identity query message includes: Hardware identity identifiers are selected one by one according to the pre-set query order as the current query hardware identity identifier, and an identity query message carrying the current query hardware identity identifier is sent; after the current response period ends, the next hardware identity identifier is selected for query.

4. The multi-handheld terminal access authentication method for beauty devices according to claim 3, characterized in that, When returning the identity response message, it includes: The handset terminal checks the identity query message for its frame header, length, and checksum. If the check passes, it extracts the query hardware identity identifier. When the query hardware identity identifier matches its own candidate hardware identity identifier, the candidate hardware identity identifier is used as the response hardware identity identifier and written into the identity response message along with the locally stored software identity identifier.

5. The multi-handheld terminal access authentication method for beauty devices according to claim 1, characterized in that, The identity registration relationship consists of a hardware identity identifier and an allowed access software identity identifier; the identity registration relationship is retrieved using the currently queried hardware identity identifier. If the retrieval is successful, the registered software identity identifier is read. If the currently queried hardware identity identifier is not found, the authentication is deemed unsuccessful.

6. The multi-handheld terminal access authentication method for beauty devices according to claim 5, characterized in that, When performing identity consistency checks, the following are included: Compare the response hardware identity identifier with the currently queried hardware identity identifier; if they match, continue to compare the software identity identifier with the registered software identity identifier; if both comparisons match, proceed to targeted verification; if either comparison does not match, authentication is deemed unsuccessful.

7. The multi-handheld terminal access authentication method for beauty devices according to claim 6, characterized in that, The targeted verification includes: Write the current queried hardware identity into the address field of the directed verification message and send it; the handset terminal whose candidate hardware identity matches the address field returns a verification response message; if the verification response message is received within the response period, and the frame check passes and the hardware identity in it matches the current queried hardware identity, the authentication is confirmed to be successful.

8. The multi-handheld terminal access authentication method for beauty devices according to claim 7, characterized in that, When the identity consistency check fails or the targeted verification fails, including: Retain the currently queried hardware identity and continue to query the remaining hardware identities; after completing one round of queries, re-authenticate the retained queried hardware identity, and remain unauthenticated if the re-authentication fails.

9. The multi-handheld terminal access authentication method for beauty devices according to claim 1, characterized in that, Periodic communication is performed with the valid access terminal; when no valid response is received, the connection count of the valid access terminal is increased, and when a valid response is received, the connection count is decreased; when the connection count reaches the offline threshold, the valid access status is cleared, and when the handheld terminal is detected again, access authentication is performed again.

10. A multi-handheld terminal access authentication system for beauty devices, used to apply the multi-handheld terminal access authentication method for beauty devices as described in any one of claims 1-9, characterized in that, include: The identity recognition unit is used to collect the recognition parameters of the gamepad interface of the gamepad terminal connected to the motherboard, and determine the candidate hardware identity identifier based on the identity range in which the recognition parameters are located. An identity query unit is used to sequentially send identity query messages carrying query hardware identity identifiers via a shared communication bus. When the query hardware identity identifier matches its own candidate hardware identity identifier, the handle terminal returns an identity response message and obtains the response hardware identity identifier and software identity identifier from the identity response message. The registration and query unit is used to query pre-established identity registration relationships based on the current query hardware identity identifier to obtain the registration software identity identifier; An identity authentication unit is used to send a targeted verification message using the current query hardware identity when the responding hardware identity identifier is consistent with the currently queried hardware identity identifier and the software identity identifier is consistent with the registered software identity identifier; If a verification response message carrying the same hardware identity is received within the response period, the authentication is deemed successful; otherwise, the authentication is deemed unsuccessful. The access management unit is used to register authenticated handset terminals as valid access terminals and conduct subsequent communication according to the currently queried hardware identity identifier; and to keep unauthenticated handset terminals in an unauthenticated state.

Images