Service packets record messages exchanged between devices and the HACA server. The following table describes service packet types specified by the msgType field.
Service Packet Type |
msgType |
Description |
|---|---|---|
Registration request packet |
1 | After setting up an HTTP/2 persistent connection with an HACA server, a device sends this packet to the HACA server to register device information. |
Registration response packet |
2 | The HACA server sends this packet to the device, indicating that a persistent connection has been set up successfully and they can exchange service packets. |
Authentication request packet |
3 | The device sends this packet to the HACA server. The HACA server determines whether to permit the access based on user information carried in this packet. |
Authentication response packet |
4 | The HACA server sends an authentication response packet to the device. If all attributes in the authentication request packet are acceptable, the server considers that the user passes the authentication and sends this packet. After receiving this packet, the device grants network access rights to the user. |
| Proactive authorization request packet | 6 | The HACA server sends this packet to the device after the user passes authentication. |
| Proactive authorization response packet | 5 | The device sends this packet to the HACA server and modifies user rights. |
| Accounting-start request packet | 7 | The device sends this packet to the HACA server when the user starts to access network resources. |
| Accounting response packet | 8 | After receiving and recording an accounting-start request packet, the HACA server returns an accounting response packet. |
| Logout notification packet | 9 | If the HACA server logs out the user, the device sends a logout notification packet and the HACA server does not need to reply. If accounting has been performed for the user, the packet carries accounting information. |
| Logout request packet | 11 | If the device triggers user logout, it sends a logout request packet to the HACA server. If the HACA server triggers user logout, it sends this packet to notify the device that a specified user has logged out. |
| Logout response packet | 12 | If the device triggers user logout, the HACA server sends a logout response packet to the device. If the HACA server triggers user logout, the device sends a logout response packet to the HACA server and releases the related authorization entry. |
| User synchronization request packet | 13 | User information can be periodically synchronized between the HACA server and device to ensure user information consistency. Either the device or the HACA server sends a user synchronization request packet to trigger user information synchronization. |
| User synchronization response packet | 14 | When the device or HACA server triggers user information synchronization, the peer end returns a user synchronization response packet. |
| CoA-Request packet | 16 | When an administrator needs to modify the rights of an online user (for example, prohibit the user from accessing a website), the HACA server sends this packet to the device, requesting the device to modify the user rights. |
| CoA-Response packet | 15 | If the device successfully modifies the user rights, it sends this packet to the HACA server. |