Security authentication method of intelligent set top box

By generating authentication information and two-way verification, the problem of easy decryption of authentication messages in smart set-top boxes is solved, achieving higher network security and management efficiency, and ensuring the protection of user data.

CN118890518APending Publication Date: 2024-11-01JIANGSU YINHE ELECTRONICS
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411027623.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-30
Publication Date
2024-11-01

AI Technical Summary

Technical Problem

In the existing security authentication method of smart set-top boxes, the authentication message is in a fixed mode, which makes the key easy to be decrypted, reduces the authentication security, and faces security threats such as network hackers and viruses.

Method used

Using the method of generating authentication information → IPoE authentication process → Access control list authentication → Configuration information authentication, the Option60 field in the DHCP Discover message is parsed through the BRAS system to generate a unique mapping relationship, combining the two-way of the RADIUS server and the middleware management system. Verification, using two-level key encryption and timestamps to ensure the security of authentication information.

Benefits of technology

Improve the network security and management efficiency of smart set-top boxes, ensure the protection of user information and business interests, and prevent unauthorized access and data leakage.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118890518A_ABST
    Figure CN118890518A_ABST
Patent Text Reader

Abstract

The invention discloses a security authentication method of an intelligent set top box. The security authentication method comprises the steps of authentication information generation, IPoE authentication process, access control list authentication and configuration information authentication. Two-way authentication between the set top box and the middleware management system is achieved, verification of the set top box on the middleware management system is that the middleware management system issues an AUTN containing a serial number, a message authentication code and an authentication management domain, in two levels of secret keys, a terminal secret key is transmitted to a terminal in a public key mode through an asymmetric secret key encryption method, and the terminal secret key is transmitted to the middleware management system through an authentication management domain. The private key is stored in the middleware management system and is not sent, and due to the one-to-one correspondence between the private key and the public key, even if the public key is eavesdropped in the transmission process, an attacker cannot decrypt the key; and the service key uses a symmetric key encryption method, the key is generated by the received random number rand (i), and the key is not transmitted in the network, so that the freshness of the authentication message is ensured, and the security of the key is ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of smart set-top boxes, and in particular to a security authentication method for a smart set-top box. Background Art

[0002] Smart set-top box, also known as smart TV box, is a set-top box device equipped with intelligent operating systems such as Alibaba Cloud or Android system. It not only has the basic functions of traditional TV boxes, such as watching TV and videos, but also integrates more intelligent features and Internet applications, such as integrating artificial intelligence technology to realize voice assistant, intelligent recommendation and other functions, providing users with a richer, smarter and more convenient entertainment experience. With the rapid development of science and technology and the popularization of the Internet, the development trend of smart set-top boxes is becoming increasingly significant. In the field of Internet TV, smart set-top boxes, as a common terminal device, are favored by users for their excellent performance and stable operation. Against the background of the rapid development of Internet TV business, smart set-top boxes are used on a large scale, and the number and models will increase. The development of digital TV is a fast and innovative field. With the continuous advancement of digital technology, people's demand for the security of smart set-top boxes is also increasing. However, while enjoying the convenience and fun brought by digitalization, it is also inevitable to face many security threats. These threats may come from network hackers, viruses, Trojans, fraud, etc., to obtain users' personal information, payment accounts and other sensitive data. In order to prevent this risk, it is necessary to effectively prevent security threats;

[0003] In the existing security authentication method for smart set-top boxes, the authentication message is in a fixed mode, and the generated key is in a fixed form, which makes it very easy to decrypt the authentication message after being eavesdropped on during transmission in the network, thus reducing the security of the authentication key. Therefore, there is an urgent need to construct a security authentication method for smart set-top boxes. Summary of the invention

[0004] The purpose of the present invention is to provide a security authentication method for an intelligent set-top box to solve the problems raised in the above background technology.

[0005] To achieve the above object, the present invention provides the following technical solutions:

[0006] A security authentication method for a smart set-top box, wherein the security authentication method includes: generating authentication information → IPoE authentication process → access control list authentication → configuration information authentication, and comprises the following steps:

[0007] Step 1: When the set-top box terminal starts and tries to access the network, the smart set-top box sends a DHCP Discover message to the BRAS system to initiate an authentication request. The BRAS system parses the message to identify the set-top box terminal and allocates the correct authentication information and network resources to it. The specific steps are as follows:

[0008] (1) When the BRAS system receives the DHCP Discover message sent by the set-top box, it parses the Option 60 field in the message;

[0009] (2) Based on the parsed Option 60 field content, a unique mapping relationship is defined for each type of set-top box terminal. The mapping relationship associates the Option 60 field content with authentication information such as the IPoE authentication account name and password, and the defined mapping relationship is configured in the BRAS system.

[0010] (3) The BRAS system uses the parsed Option 60 field content as a keyword and matches it with the mapping rules preset in the system;

[0011] (4) If the match is successful, the BRAS system will generate the corresponding IPoE authentication account name and password according to the mapping rules;

[0012] Step 2: After the IPoE authentication account name and password are generated, the BRAS system will send the generated authentication information to the RADIUS server for authentication. The specific process is as follows:

[0013] 1) The BRAS system constructs an authentication request message and includes the generated IPoE authentication account name and password as authentication information in the message. Then, the BRAS system sends the authentication request message to the RADIUS server;

[0014] 2) After receiving the authentication request message, the RADIUS server will parse the authentication information in the message and verify the authentication information according to the preset authentication policy;

[0015] 3) If the authentication is successful, the RADIUS server will send an authentication success response message to the BRAS system. After receiving the authentication success response message, the BRAS system will allocate corresponding network resources to the set-top box terminal, such as IP address and gateway, and allow it to access the network. If the authentication fails, the RADIUS server will reject the request and may return an error message;

[0016] Step 3: Through the set-top box with matching account and password, call the service access control list ACL, transfer the matching authentication account name to the corresponding domain, complete the IP address allocation, authentication, authorization and online process, and generate control table items. The specific steps are as follows:

[0017] (1) When the set-top box sends a data packet to request access, the DHCP server will first parse the IPoE authentication account name and password information in the data packet, and send the parsed IPoE authentication account name and password information to the verification server;

[0018] (2) The verification server will match the received IPoE authentication account name and password with the information pre-stored in the service access control list. If the account and password match successfully, the set-top box is considered to be a legitimate user and is allowed to continue the access process; if the match fails, the access request is rejected and an error message may be returned;

[0019] Step 4: After the account and password are successfully verified, the BRAS system will call the service access control list based on the account information and retrieve the configuration information corresponding to the account from the list, including the domain name to be transferred, IP address allocation policy, authentication method, and authorization authority. The specific steps are as follows:

[0020] (1) Domain name resolution and IP address allocation: Based on the information in the service access control list, the system transfers the set-top box account name to the corresponding domain name through the IP address pool management and allocation strategy of the DHCP server, and allocates a suitable IP address to the set-top box under the domain name;

[0021] (2) Authentication and authorization: After the IP address is assigned, the system will authenticate and authorize the set-top box according to the configuration information in the service access control list. The specific steps are as follows:

[0022] 1) The process of authenticating the set-top box includes further identity verification and key exchange

[0023] 2) The middleware management system and the set-top box bidirectionally verify the user's usage rights;

[0024] The set-top box first sends a login request to the middleware management system, including its identity information and encrypted credentials. Before sending the login request, the set-top box will collect user information and record the user's usage;

[0025] User information is encrypted with two levels of keys. The transmission of the business key itself is encrypted by the "set-top box terminal key" K1, and all authentication information uploaded by the user is encrypted by the "business secret key" K2. A timestamp is added to the transmission of the "business secret key". The K1 public key and the corresponding private key can only be stored in the business platform middleware management system, while K2 is pre-stored in the terminal's business authentication module and the business platform middleware management system. The specific steps are as follows:

[0026] First, when the set-top box sends a login request, the middleware management system generates an M-sequence random number rand(i) and an authentication management domain AUTN(i) after receiving the request. AUTN includes an encrypted sequence number and a message authentication code MAC.

[0027] Then, the middleware management system uses rand(i) and the service key "K2" to perform operation f1(i) on the encrypted user information to generate the expected response number XRES(i). The middleware management system sends rand(i) and AUTN to the set-top box;

[0028] Secondly, the set-top box first generates the expected message authentication code XMAC based on the received rand(i), and compares it with the MAC in the received AUTN. If MAC = XMAC, the response number RES(i) is calculated by the f1(i) function, and then the response number RES(i) is sent back. If they are different, the communication is stopped;

[0029] Again, the middleware management system compares the returned RES(i) with XRES(i). If RES(i) = XRES(i), it sends the set-top box terminal public key K1. Otherwise, it only returns the error authentication information.

[0030] Finally, after receiving the public key sent by the set-top box terminal, the service authentication module can upload the user's personal information. The service authentication module uses the service key CK generated by rand(i) and K2 and the public key K1 sent by the set-top box to double encrypt the user information and send it to the middleware management system after encryption;

[0031] After receiving it, the middleware management system uses the corresponding private key K1 and business key to decrypt, verify the user's usage authority, search the database, obtain the download address of the set-top box client, the business interface and the user's business authority, and return it to the set-top box, so that the subsequent application usage process can be carried out.

[0032] Preferably, in step 2, the authentication policy preset by the RADIUS server is as follows:

[0033] (1) User database management: A user database is maintained on the RADIUS server, which contains information such as user names, passwords, user groups, and access rights stored in encrypted form;

[0034] (2) Authentication method selection: RADIUS servers support multiple authentication methods, such as PAP, CHAP, and EAP;

[0035] (3) Multi-factor authentication (MFA): RADIUS servers can support multi-factor authentication (MFA). In addition to username and password, users are also required to provide other verification factors, such as dynamic tokens and fingerprint recognition.

[0036] (4) Policy Decision Point (PDP): The RADIUS server can be integrated with other security systems, such as the Policy Decision Point (PDP), to formulate authentication policies based on more complex rules and user attributes.

[0037] Preferably, in step 4, the IP address pool management and allocation strategy of the DHCP server, the computer of the DHCP server needs to install the TCP / IP protocol and have a static IP address, subnet mask, default gateway, etc.;

[0038] S1. IP address pool management: The IP address pool is a resource pool used by the DHCP server to allocate IP addresses. Effective IP address pool management can ensure the rational use and efficient allocation of IP addresses. The specific steps are as follows:

[0039] 1) Address pool planning: Reasonably plan the size of the IP address pool according to the network scale and number of devices to ensure that the IP addresses in the address pool do not conflict with other static IP addresses in the network;

[0040] 2) Address pool monitoring: Regularly monitor the usage of the address pool, including allocated, unallocated and conflicting IP addresses, and promptly discover and resolve IP address waste and conflict issues;

[0041] 3) Address pool optimization: dynamically adjust the size and scope of the address pool according to network changes, recycle unused IP addresses and reallocate them to the address pool;

[0042] S2. Allocation strategy: The DHCP server provides a variety of IP address allocation strategies to meet different network environments and customer needs, as follows:

[0043] 1) Dynamic allocation: After the client obtains an IP address from the DHCP server, it does not use the address permanently, but obtains it dynamically in the form of a lease. After the lease expires, the client needs to reapply for a lease from the DHCP server to continue using the IP address, or the DHCP server allocates the IP address to other clients. This can effectively utilize IP address resources and adapt to network environments where network devices frequently change;

[0044] 2) Automatic allocation: After the client obtains an IP address from the DHCP server for the first time, it will use the address permanently unless the client explicitly releases the address or the lease is manually deleted by the administrator. It is suitable for network environments where network devices are relatively stable and do not need to be changed frequently;

[0045] 3) Manual allocation: The network administrator statically binds a fixed IP address to a specific client, which is suitable for devices that require a fixed IP address.

[0046] Compared with the prior art, the invention has the following beneficial effects: bidirectional authentication between a set-top box and a middleware management system is realized, and the verification of the set-top box to the middleware management system is as follows: the middleware management system sends AUTN including a serial number, a message authentication code and an authentication management domain, and the set-top box calculates XMAC according to AUTN including a serial number, a message authentication code and an authentication management domain sent by the middleware management system, and if MAC=XMAC, the authentication is successful; the verification of the middleware management system to the set-top box is as follows: the middleware management system and the set-top box calculate response values ​​XRES and RES respectively, and if XRES=RES, the authentication is successful;

[0047] User information is encrypted with two levels of keys. All authentication information uploaded by users is encrypted by the "business key". The transmission of the business key itself is encrypted by the "set-top box terminal key". A timestamp is added to the transmission of the business key to make the business key time-effective. Even if it is intercepted, it will only have an impact for a short period of time.

[0048] In the two-level key, the terminal key is encrypted using an asymmetric key method and is transmitted to the terminal in the form of a public key. The private key is stored in the middleware management system and is not sent. Due to the one-to-one correspondence between the private key and the public key, even if the public key is eavesdropped during transmission, the attacker cannot decrypt the key. The service key uses a symmetric key encryption method. The key is generated by the received random number rand(i) and is not transmitted in the network. This ensures the freshness of the authentication message and the security of the key. The two-level key mechanism can protect the user's privacy information and the commercial interests of the digital TV operator, so that users can get better protection while enjoying digital TV services.

[0049] The IP address pool management and allocation strategy of the DHCP server, through reasonable planning and effective management strategies, can ensure that network devices can automatically and efficiently obtain IP addresses and other network configuration parameters, while improving the efficiency and security of network management; the mapping rules ensure that the BRAS system can accurately identify the set-top box terminal and allocate correct authentication information and network resources to it, thereby improving the security and management efficiency of the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 A schematic diagram of a process flow of a security authentication method for a smart set-top box of the present invention;

[0051] Figure 2 A flow chart of generating authentication information in a security authentication method for a smart set-top box of the present invention;

[0052] Figure 3 A flowchart of an IPoE authentication process in a security authentication method for a smart set-top box of the present invention;

[0053] Figure 4 A RADIUS server authentication flow chart in a security authentication method for a smart set-top box of the present invention;

[0054] Figure 5 It is a flow chart of access control list authentication in a security authentication method of a smart set-top box of the present invention;

[0055] Figure 6 A configuration information authentication flow chart of a security authentication method for a smart set-top box of the present invention;

[0056] Figure 7 A configuration information authentication framework diagram in a security authentication method for a smart set-top box of the present invention;

[0057] Figure 8 The present invention is a two-level key encryption flow chart of user information in a security authentication method for a smart set-top box. DETAILED DESCRIPTION

[0058] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0059] Example

[0060] See also Figure 1-8 The embodiment of the present invention provides a security authentication method for a smart set-top box, wherein the security authentication method comprises the following steps: generating authentication information → IPoE authentication process → access control list authentication → configuration information authentication:

[0061] Step 1: When the set-top box terminal starts and tries to access the network, the smart set-top box sends a DHCP Discover message to the BRAS system to initiate an authentication request. The BRAS system parses the message to identify the set-top box terminal and allocates the correct authentication information and network resources to it. The specific steps are as follows:

[0062] (1) When the BRAS system receives the DHCP Discover message sent by the set-top box, it parses the Option 60 field in the message and extracts the content of the Option 60 field, including identification information such as the vendor name, device model, and serial number, which is used to distinguish different types of set-top box terminals;

[0063] (2) Based on the parsed Option 60 field content, a unique mapping relationship is defined for each type of set-top box terminal. The mapping relationship associates the Option 60 field content with authentication information such as the IPoE authentication account name and password, and the defined mapping relationship is configured in the BRAS system.

[0064] (3) The BRAS system uses the parsed Option 60 field content as a keyword and matches it with the mapping rules preset in the system. The mapping rules define the correspondence between different Option 60 field contents and the IPoE authentication account name and password.

[0065] (4) If the match is successful, the BRAS system will generate the corresponding IPoE authentication account name and password according to the mapping rules. The authentication information will be used in the subsequent authentication process to ensure that only legitimate set-top box terminals can obtain network access rights;

[0066] Step 2: After generating the IPoE authentication account name and password, the BRAS system will send the generated authentication information to the RADIUS server for authentication.

[0067] First, preset the authentication policy of the RADIUS server, as follows:

[0068] (1) User database management: A user database is maintained on the RADIUS server, which contains information such as user names, passwords, user groups, and access rights stored in encrypted form;

[0069] (2) Authentication method selection: RADIUS servers support multiple authentication methods, such as PAP, CHAP, and EAP;

[0070] (3) Multi-factor authentication (MFA): RADIUS servers can support multi-factor authentication (MFA). In addition to username and password, users are also required to provide other verification factors, such as dynamic tokens and fingerprint recognition.

[0071] (4) Policy Decision Point (PDP): RADIUS servers can be integrated with other security systems, such as the Policy Decision Point (PDP), to formulate authentication policies based on more complex rules and user attributes, which helps to achieve fine-grained access control and more flexible security policies.

[0072] Then, according to the preset RADIUS server authentication policy, the generated authentication information is sent to the RADIUS server for authentication. The specific process is as follows:

[0073] 1) The BRAS system constructs an authentication request message and includes the generated IPoE authentication account name and password as authentication information in the message. Then, the BRAS system sends the authentication request message to the RADIUS server;

[0074] 2) After receiving the authentication request message, the RADIUS server will parse the authentication information in the message and verify the authentication information according to the preset authentication policy. The RADIUS server authentication process is as follows:

[0075] S1. The smart set-top box submits an authentication request through the BRAS system, including the generated IPoE authentication account name and password;

[0076] S2. The BRAS system forwards the authentication request to the RADIUS server.

[0077] S3, the RADIUS server receives the authentication request and performs identity authentication according to the preset authentication policy;

[0078] S4. The BRAS system determines whether to allow the user to access network resources based on the information returned by the RADIUS server.

[0079] 3) Authentication result: If the authentication is successful, the RADIUS server will send an authentication success response message to the BRAS system. After receiving the authentication success response message, the BRAS system will allocate corresponding network resources to the set-top box terminal, such as IP address and gateway, and allow it to access the network. If the authentication fails, the RADIUS server will reject the request and may return an error message;

[0080] Step 3: Through the set-top box with matching account and password, call the service access control list ACL, transfer the matching authentication account name to the corresponding domain, complete the IP address allocation, authentication, authorization and online process, and generate control table items. The specific steps are as follows:

[0081] (1) When the set-top box sends a data packet to request access, the DHCP server will first parse the IPoE authentication account name and password information in the data packet, and send the parsed IPoE authentication account name and password information to the verification server;

[0082] (2) The verification server will match the received IPoE authentication account name and password with the information pre-stored in the service access control list. If the account and password match successfully, the set-top box is considered to be a legitimate user and is allowed to continue the access process; if the match fails, the access request is rejected and an error message may be returned;

[0083] Step 4: After the account and password are successfully verified, the system will call the service access control list based on the account information and retrieve the configuration information corresponding to the account from the list, including the domain name to be transferred, IP address allocation strategy, authentication method, and authorization permissions. The specific steps are as follows:

[0084] (1) Domain name resolution and IP address allocation: Based on the information in the service access control list, the system transfers the set-top box account name to the corresponding domain name through the IP address pool management and allocation strategy of the DHCP server, and allocates a suitable IP address to the set-top box under the domain name;

[0085] Among them, the IP address pool management and allocation strategy of the DHCP server, the computer of the DHCP server needs to install the TCP / IP protocol and have a static IP address, subnet mask, default gateway, etc.;

[0086] 1) IP address pool management: The IP address pool is a resource pool used by the DHCP server to allocate IP addresses. Effective IP address pool management can ensure the rational use and efficient allocation of IP addresses. The specific steps are as follows:

[0087] S1. Address pool planning: Reasonably plan the size of the IP address pool according to the network scale and number of devices to ensure that the IP addresses in the address pool do not conflict with other static IP addresses in the network;

[0088] S2. Address pool monitoring: Regularly monitor the usage of the address pool, including allocated, unallocated and conflicting IP addresses, to promptly identify and resolve IP address waste and conflict issues;

[0089] S3, address pool optimization: dynamically adjust the size and range of the address pool according to network changes, recycle unused IP addresses and reallocate them to the address pool;

[0090] 2) Allocation strategy: The DHCP server provides a variety of IP address allocation strategies to meet different network environments and customer needs, as follows:

[0091] S1, Dynamic allocation: After the client obtains an IP address from the DHCP server, it does not use the address permanently, but obtains it dynamically in the form of a lease. After the lease expires, the client needs to reapply for a lease from the DHCP server to continue using the IP address, or the DHCP server allocates the IP address to other clients. This can effectively utilize IP address resources and adapt to network environments where network devices frequently change.

[0092] S2, automatic allocation: After the client obtains an IP address from the DHCP server for the first time, it will use the address permanently unless the client explicitly releases the address or the lease is manually deleted by the administrator. It is suitable for network environments where network devices are relatively stable and do not need to be changed frequently.

[0093] S3, manual allocation: The network administrator statically binds a fixed IP address to a specific client, which is suitable for devices that require a fixed IP address;

[0094] (2) Authentication and authorization: After the IP address is assigned, the system will authenticate and authorize the set-top box according to the configuration information in the service access control list. The specific steps are as follows:

[0095] 1) The process of authenticating the set-top box includes further identity verification and key exchange. The specific steps are as follows:

[0096] S1. Identity verification: After the initial verification of the account and password is passed, the system requires further identity verification, which involves verifying whether the device or user requesting access to the network has a legitimate identity and authority;

[0097] ① Multi-factor authentication: In addition to username and password, the system provides additional verification factors, such as mobile phone verification code, fingerprint recognition, and facial recognition, which can significantly improve the security of the account, because even if the password is leaked, the attacker needs to master other verification factors at the same time to successfully log in;

[0098] ② Challenge response mechanism: The system can send a random challenge to the user, such as a verification code or password question, and ask the user to give a corresponding response. Only users who can correctly respond to the challenge can be considered legitimate;

[0099] ③Device authentication: The system will also authenticate the device requesting access to ensure that the device itself is also legitimate by checking the device's MAC address, IP address, certificate and other information;

[0100] S2. Key exchange: It is one of the basic steps to establish encrypted communication. In set-top box network security, key exchange is used to ensure that both parties can safely share a key for encrypting and decrypting data. Before the password submitted by the user is transmitted to the RADIUS server, it is encrypted by encryption algorithms MD5 and SHA-1 to prevent the password from being intercepted and directly parsed on the network. In the RADIUS authentication protocol, an encrypted or hashed authentication credential is generated based on the password submitted by the user, and then the credential is sent to the RADIUS server for verification. The specific process may include the following steps;

[0101] ① Password storage: When a user registers for the first time or changes their password, the system usually uses a hash algorithm, such as MD5 or SHA-1, to hash the password and store the hash value in the database;

[0102] ②Authentication process: When a user tries to log in, the system prompts the user to enter a password. The system then hashes the entered password again using the same hashing algorithm and compares the generated hash value with the hash value stored in the database.

[0103] ③RADIUS authentication: In the RADIUS authentication scenario, the system uses a "challenge-response" mechanism protocol to verify the user's identity, such as Challenge Handshake Authentication Protocol (CHAP) and Microsoft Challenge Handshake Authentication Protocol version 2 (MS-CHAPv2), which generates a response based on the password and the challenge provided by the server, and then sends the response to the server for verification;

[0104] 2) The middleware management system and the set-top box bidirectionally verify the user's usage rights;

[0105] The set-top box first sends a login request to the middleware management system, including its identity information and encryption credentials. Before sending the login request, the set-top box will collect user information and record the user's usage. The user information is encrypted with two-level keys. The transmission of the business key itself is encrypted by the "set-top box terminal key" K1. All authentication information uploaded by the user is encrypted by the "business secret key" K2, and a timestamp is added to the transmission of the "business secret key". The K1 public key and the corresponding private key can only be stored in the middleware management system, and K2 is pre-stored in the terminal's business authentication module and the platform middleware management system. The specific steps are as follows:

[0106] First, when the set-top box sends a login request, the middleware management system generates an M-sequence random number rand(i) and an authentication management domain AUTN(i) after receiving the request. AUTN includes an encrypted serial number, a message authentication code MAC,

[0107] Then, the middleware management system uses rand(i) and the service key "K2" to perform operation f1(i) on the encrypted user information to generate the expected response number XRES(i). The middleware management system sends rand(i) and AUTN to the set-top box;

[0108] Secondly, the set-top box first generates the expected message authentication code XMAC based on the received rand(i), and compares it with the MAC in the received AUTN. If MAC = XMAC, the response number RES(i) is calculated by the f1(i) function, and then the response number RES(i) is sent back. If they are different, the communication is stopped;

[0109] Again, the middleware management system compares the returned RES(i) with XRES(i). If RES(i) = XRES(i), it sends the set-top box terminal public key K1. Otherwise, it only returns the error authentication information.

[0110] Finally, after receiving the public key sent by the set-top box terminal, the service authentication module can upload the user's personal information. The service authentication module uses the service key CK generated by rand(i) and K2 and the public key K1 sent by the set-top box to double encrypt the user information and send it to the middleware management system after encryption;

[0111] After receiving it, the middleware management system uses the corresponding private key K1 and business key to decrypt, verify the user's usage authority, search the database, obtain the download address of the set-top box client, the business interface and the user's business authority, and return it to the set-top box, so that the subsequent application usage process can be carried out.

[0112] It will be apparent to those skilled in the art that the invention is not limited to the details of the exemplary embodiments described above and that the invention can be implemented in other specific forms without departing from the spirit or essential features of the invention. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description, and it is intended that all variations falling within the meaning and scope of the equivalent elements of the claims be included in the invention. Any reference numeral in a claim should not be considered as limiting the claim to which it relates.

Claims

1. A security authentication method for a smart set-top box, wherein the security authentication method comprises: generating authentication information → IPoE authentication process → access control list authentication → configuration information authentication, and is characterized in that: The following steps are involved: Step 1: When the set-top box terminal starts and tries to access the network, the smart set-top box sends a DHCP Discover message to the BRAS system to initiate an authentication request. The BRAS system parses the message to identify the set-top box terminal and allocates the correct authentication information and network resources to it. The specific steps are as follows: (1) When the BRAS system receives the DHCP Discover message sent by the set-top box, it parses the Option 60 field in the message; (2) Based on the parsed Option 60 field content, a unique mapping relationship is defined for each type of set-top box terminal. The mapping relationship associates the Option 60 field content with authentication information such as the IPoE authentication account name and password, and the defined mapping relationship is configured in the BRAS system. (3) The BRAS system uses the parsed Option 60 field content as a keyword and matches it with the mapping rules preset in the system; (4) If the match is successful, the BRAS system will generate the corresponding IPoE authentication account name and password according to the mapping rules; Step 2: After the IPoE authentication account name and password are generated, the BRAS system will send the generated authentication information to the RADIUS server for authentication. The specific process is as follows: 1) The BRAS system constructs an authentication request message and includes the generated IPoE authentication account name and password as authentication information in the message. Then, the BRAS system sends the authentication request message to the RADIUS server; 2) After receiving the authentication request message, the RADIUS server will parse the authentication information in the message and verify the authentication information according to the preset authentication policy; 3) If the authentication is successful, the RADIUS server will send an authentication success response message to the BRAS system. After receiving the authentication success response message, the BRAS system will allocate corresponding network resources to the set-top box terminal, such as IP address and gateway, and allow it to access the network. If the authentication fails, the RADIUS server will reject the request and may return an error message; Step 3: Through the set-top box with matching account and password, call the service access control list ACL, transfer the matching authentication account name to the corresponding domain, complete the IP address allocation, authentication, authorization and online process, and generate control table items. The specific steps are as follows: (1) When the set-top box sends a data packet to request access, the DHCP server will first parse the IPoE authentication account name and password information in the data packet, and send the parsed IPoE authentication account name and password information to the verification server; (2) The verification server will match the received IPoE authentication account name and password with the information pre-stored in the service access control list. If the account and password match successfully, the set-top box is considered to be a legitimate user and is allowed to continue the access process; if the match fails, the access request is rejected and an error message may be returned; Step 4: After the account and password are successfully verified, the BRAS system will call the service access control list based on the account information and retrieve the configuration information corresponding to the account from the list, including the domain name to be transferred, IP address allocation policy, authentication method, and authorization authority. The specific steps are as follows: (1) Domain name resolution and IP address allocation: Based on the information in the service access control list, the system transfers the set-top box account name to the corresponding domain name through the IP address pool management and allocation strategy of the DHCP server, and allocates a suitable IP address to the set-top box under the domain name; (2) Authentication and authorization: After the IP address is assigned, the system will authenticate and authorize the set-top box according to the configuration information in the service access control list. The specific steps are as follows: 1) The process of authenticating the set-top box includes further identity verification and key exchange 2) The middleware management system and the set-top box bidirectionally verify the user's usage rights; The set-top box first sends a login request to the middleware management system, including its identity information and encrypted credentials. Before sending the login request, the set-top box will collect user information and record the user's usage; User information is encrypted with two levels of keys. The transmission of the business key itself is encrypted by the "set-top box terminal key" K1, and all authentication information uploaded by the user is encrypted by the "business secret key" K2. A timestamp is added to the transmission of the "business secret key". The K1 public key and the corresponding private key can only be stored in the business platform middleware management system, while K2 is pre-stored in the terminal's business authentication module and the business platform middleware management system. The specific steps are as follows: First, when the set-top box sends a login request, the middleware management system generates an M-sequence random number rand(i) and an authentication management domain AUTN(i) after receiving the request. AUTN includes an encrypted sequence number and a message authentication code MAC. Then, the middleware management system uses rand(i) and the service key "K2" to perform operation f1(i) on the encrypted user information to generate the expected response number XRES(i). The middleware management system sends rand(i) and AUTN to the set-top box; Secondly, the set-top box first generates the expected message authentication code XMAC based on the received rand(i), and compares it with the MAC in the received AUTN. If MAC = XMAC, the response number RES(i) is calculated by the f1(i) function, and then the response number RES(i) is sent back. If they are different, the communication is stopped; Again, the middleware management system compares the returned RES(i) with XRES(i). If RES(i) = XRES(i), it sends the set-top box terminal public key K1. Otherwise, it only returns the error authentication information. Finally, after receiving the public key sent by the set-top box terminal, the service authentication module can upload the user's personal information. The service authentication module uses the service key CK generated by rand(i) and K2 and the public key K1 sent by the set-top box to double encrypt the user information and send it to the middleware management system after encryption; After receiving it, the middleware management system uses the corresponding private key K1 and business key to decrypt, verify the user's usage authority, search the database, obtain the download address of the set-top box client, the business interface and the user's business authority, and return it to the set-top box, so that the subsequent application usage process can be carried out.

2. A method for managing a digital television receiving terminal according to claim 1, characterized in that: In step 2, the authentication policy preset by the RADIUS server is as follows: (1) User database management: A user database is maintained on the RADIUS server, which contains information such as user names, passwords, user groups, and access rights stored in encrypted form; (2) Authentication method selection: RADIUS servers support multiple authentication methods, such as PAP, CHAP, and EAP; (3) Multi-factor authentication (MFA): RADIUS servers can support multi-factor authentication (MFA). In addition to username and password, users are also required to provide other verification factors, such as dynamic tokens and fingerprint recognition. (4) Policy Decision Point (PDP): The RADIUS server can be integrated with other security systems, such as the Policy Decision Point (PDP), to formulate authentication policies based on more complex rules and user attributes.

3. A method for managing a digital television receiving terminal according to claim 1, characterized in that: In step 4, the IP address pool management and allocation strategy of the DHCP server, the computer of the DHCP server needs to install the TCP / IP protocol and have a static IP address, subnet mask, default gateway, etc.; S1. IP address pool management: The IP address pool is a resource pool used by the DHCP server to allocate IP addresses. Effective IP address pool management can ensure the rational use and efficient allocation of IP addresses. The specific steps are as follows: 1) Address pool planning: Reasonably plan the size of the IP address pool based on the network scale and number of devices to ensure that the IP addresses in the address pool do not conflict with other static IP addresses in the network; 2) Address pool monitoring: Regularly monitor the usage of the address pool, including allocated, unallocated and conflicting IP addresses, and promptly discover and resolve IP address waste and conflict issues; 3) Address pool optimization: dynamically adjust the size and scope of the address pool according to network changes, recycle unused IP addresses and reallocate them to the address pool; S2. Allocation strategy: The DHCP server provides a variety of IP address allocation strategies to meet different network environments and customer needs, as follows: 1) Dynamic allocation: After the client obtains an IP address from the DHCP server, it does not use the address permanently, but obtains it dynamically in the form of a lease. After the lease expires, the client needs to reapply for a lease from the DHCP server to continue using the IP address, or the DHCP server allocates the IP address to other clients. This can effectively utilize IP address resources and adapt to network environments where network devices frequently change; 2) Automatic allocation: After the client obtains an IP address from the DHCP server for the first time, it will use the address permanently unless the client explicitly releases the address or the lease is manually deleted by the administrator. It is suitable for network environments where network devices are relatively stable and do not need to be changed frequently; 3) Manual allocation: The network administrator statically binds a fixed IP address to a specific client, which is suitable for devices that require a fixed IP address.

Citation Information

Cited By

  • Internet of vehicles communication privacy protection method based on block chain

    CN115515127A