A gateway registration method, device, apparatus and storage medium

By allocating logical IDs to slave gateways and configuring them on the ACS system through the master gateway, the problem of unified management and control of multi-vendor equipment in FTTR network management is solved, and unified management of FTTR networks and collaborative management by operators are achieved.

CN116192566BActive Publication Date: 2025-10-21CHINA UNITED NETWORK COMM GRP CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202111423858.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-11-26
Publication Date
2025-10-21
Estimated Expiration
2041-11-26

AI Technical Summary

Technical Problem

In the existing technology, FTTR networks lack a unified and effective management solution. Traditional home network management systems are unable to uniformly control devices from multiple manufacturers, and ACS systems are unable to manage slave gateways in a two-level architecture.

Method used

The master gateway registers and authenticates on the ACS system, assigns a logical ID to the slave gateway, and sends configuration information so that the slave gateway can register and authenticate on the ACS system, thereby achieving unified management of the FTTR network by the ACS system.

Benefits of technology

It achieves unified and effective management and control of FTTR networks, facilitates operators to collaboratively manage equipment from different manufacturers, and improves the uniformity and convenience of network management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116192566B_ABST
    Figure CN116192566B_ABST
Patent Text Reader

Abstract

The application provides a gateway registration method and device, equipment and storage medium, relates to the technical field of communication, and can make the slave gateway in the FTTR network register and authenticate on the ACS system, so that the ACS system can directly control the slave gateway in the FTTR network. The method comprises the following steps: a first gateway performs authentication with an ACS system. The first gateway sends configuration information to a second gateway. The first gateway sends a second logical ID to the ACS system. The second gateway sends a request message to the ACS system, wherein the request message comprises the configuration information, and is used for the ACS system to register and authenticate the slave gateway according to the second logical ID and the configuration information. The ACS system registers and authenticates the second gateway according to the second logical ID and the configuration information. After the registration and authentication of the second gateway are passed, the ACS system sends a response message to the second gateway. The application can be used in the process of controlling the FTTR network by the ACS system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a gateway registration method, apparatus, device and storage medium. Background Art

[0002] Improved network infrastructure has provided a solid foundation for the prosperity of internet services, and innovative applications are emerging in an endless stream. New services such as 8K ultra-high-definition video, cloud virtual reality, cloud gaming, and live streaming are emerging one after another. These emerging services, in turn, place higher demands on network bandwidth, latency, and jitter, necessitating an urgent upgrade of broadband networks. To meet the increasing network demands of these new services, fiber-to-the-room (FTTR) technology has emerged. Traditional home networks have a single-tier architecture, with a single master gateway. Home networks using FTTR technology (referred to as FTTR networks) have a two-tier architecture, consisting of a master gateway and slave gateways. This is the most crucial aspect that distinguishes FTTR networks from traditional home networks. Therefore, FTTR technology is considered the most cutting-edge and suitable technology for home networks, providing greater broadband support.

[0003] There are currently two approaches to managing and controlling FTTR networks. One relies on the management systems provided by each FTTR equipment manufacturer. However, each manufacturer's management system can only manage its own equipment and cannot control equipment from other manufacturers. The other approach relies on the operator's Auto-Configuration Server (ACS) system to manage and control FTTR networks. However, due to the inherent imperfections of the ACS system, it cannot control the FTTR network's second-level terminals, namely the gateways. Therefore, there is currently no unified and effective management solution for FTTR networks. Summary of the Invention

[0004] The present application provides a gateway registration method, apparatus, device and storage medium, which enable slave gateways in an FTTR network to register and authenticate on an ACS system, so that the ACS system can directly manage and control the slave gateways in the FTTR network, thereby achieving unified and effective management and control of the FTTR network.

[0005] In a first aspect, the present application provides a gateway registration method, which is applied to a first gateway of a fiber-to-the-room (FTTR) network, wherein the first gateway serves as a master gateway and is connected to one or more second gateways serving as slave gateways. The method comprises: the first gateway authenticates with an automatic configuration server (ACS) system to obtain remote management parameter configuration items of the ACS system; the first gateway sends configuration information to the second gateway; wherein the configuration information comprises: remote management parameter configuration items and logical ID parameter configuration items of the ACS system, wherein the logical ID parameter configuration items comprise a second logical ID; the second logical ID is used to indicate the second gateway and to indicate that the second gateway is a slave gateway of the first gateway; the first gateway sends the second logical ID to the ACS system; the first gateway receives a request message from the second gateway and sends the request message to the ACS system; wherein the request message includes configuration information for the ACS system to register and authenticate the second gateway based on the second logical ID and the configuration information; the first gateway receives a response message from the ACS system and sends the response message to the second gateway, wherein the response message is used to indicate that the second gateway has successfully registered and authenticated on the ACS system.

[0006] In one possible implementation, before the first gateway sends the configuration information to the second gateway, the method further includes: the first gateway generates a second logical ID based on the first logical ID; wherein the second logical ID includes the first logical ID and a target suffix, and the first logical ID is the logical ID of the first gateway.

[0007] In another possible implementation, before the first gateway sends the configuration information to the second gateway, the above method also includes: the first gateway receives a registration authentication request message from the second gateway; the registration authentication request message is used to request authentication with the first gateway; the first gateway sends a registration authentication confirmation message to the second gateway; the registration authentication confirmation message is used to indicate that the authentication of the second gateway with the first gateway is successful.

[0008] In a second aspect, the present application provides a gateway registration method, which is applied to a second gateway of a fiber-to-the-room FTTR network, where the second gateway is connected to a first gateway as a master gateway as a slave gateway. The method includes: the second gateway receives configuration information from the first gateway; wherein the configuration information includes: remote management parameter configuration items and logical ID parameter configuration items of an automatic configuration server ACS system, and the logical ID parameter configuration items include a second logical ID; the second logical ID is used to indicate the second gateway and indicate that the second gateway is a slave gateway of the first gateway; the second gateway sends a request message to the ACS system, the request message includes configuration information, and is used by the ACS system to register and authenticate the second gateway based on the second logical ID and configuration information received from the first gateway; the second gateway receives a response message from the ACS system, and the response message is used to indicate that the second gateway has successfully registered and authenticated on the ACS system.

[0009] In a possible implementation, the second gateway sends a request message to the ACS system, including: the second gateway sends a request message to the ACS system through the first gateway; the second gateway receives a response message from the ACS system, including: the second gateway receives a response message sent by the ACS system through the first gateway.

[0010] In another possible implementation, before the second gateway receives the configuration information from the first gateway, the above method also includes: the second gateway sends a registration authentication request message to the first gateway; the registration authentication request message is used to request authentication with the first gateway; the second gateway receives a registration authentication confirmation message from the first gateway; the registration authentication confirmation message is used to indicate that the authentication of the second gateway with the first gateway is successful.

[0011] In a third aspect, the present application provides a gateway registration method, which is applied to an automatic configuration server ACS system of a fiber-to-the-room FTTR network, the method comprising: the ACS system authenticating with a first gateway so that the first gateway obtains remote management parameter configuration items of the ACS system; the ACS system receiving a second logical ID from the first gateway; the second logical ID is used to indicate a second gateway and to indicate that the second gateway is a slave gateway of the first gateway; the ACS system receiving a request message from the second gateway; wherein the request message includes configuration information, the configuration information including: remote management parameter configuration items and logical ID parameter configuration items of the ACS system, the logical ID parameter configuration items including the second logical ID; the ACS system registers and authenticates the second gateway based on the second logical ID and the configuration information; after the registration authentication of the second gateway is successful, the ACS system sends a response message to the second gateway; wherein the response message is used to indicate that the second gateway has successfully registered and authenticated on the ACS system.

[0012] In a possible implementation, the ACS system receives a request message from the second gateway, including: the ACS system receives a request message sent by the second gateway through the first gateway; the ACS system sends a response message to the second gateway, including: the ACS system sends a response message to the second gateway through the first gateway.

[0013] In another possible implementation, after the registration authentication of the second gateway is successful, the method further includes: the ACS system establishing a home network topology map based on the second logical ID, the home network topology map including the subordinate relationship between the first gateway and the second gateway. The ACS system manages the first gateway, and management of the first gateway includes one or more of the following: querying downstream optical interface information, managing the number of downstream devices, and querying downstream device information. The ACS system manages the second gateway, and management of the second gateway includes one or more of the following: reading gateway parameter information, configuring parameter information, updating software versions, restoring factory settings, and restarting the device.

[0014] The gateway registration method provided in this application sends configuration information to the slave gateway through the master gateway in the FTTR network and assigns a logical ID to the slave gateway, so that the slave gateway can use the configuration information and the logical ID to register and authenticate on the ACS system, so that the ACS system can control the slave gateways in the FTTR network, and then control the entire FTTR network, making up for the defects of the existing ACS system in controlling the FTTR network and realizing unified and effective control of the FTTR network.

[0015] Furthermore, in this solution, the master gateway generates the logical ID of the slave gateway connected to it based on its own logical ID. This allows the slave gateway to register and go online with the ACS system. The ACS system then creates a home network topology based on the logical ID, facilitating network management and maintenance for operators. Furthermore, the ACS system can directly manage and control the slave gateways in the FTTR network, querying their operating parameters and performing operations such as software updates, factory resets, and device reboots. This ensures timely maintenance of the slave gateway's operating status, and ultimately the entire FTTR network, providing users with a better user experience.

[0016] In a fourth aspect, the present application provides a gateway registration device, which is applied to a first gateway of a fiber-to-the-room FTTR network, wherein the first gateway serves as a master gateway and is connected to one or more second gateways serving as slave gateways. The device includes an authentication module, a sending module, and a receiving module; the authentication module is used to authenticate with an automatic configuration server (ACS) system to obtain remote management parameter configuration items of the ACS system; the sending module is used to send configuration information to the second gateway; wherein the configuration information includes: remote management parameter configuration items and logical ID parameter configuration items of the ACS system, and the logical ID parameter configuration items include a second logical ID; the second logical ID is used to indicate the second gateway and indicate that the second gateway is a slave gateway of the first gateway; the sending module is also used to send the second logical ID to the ACS system; the receiving module is used to receive a request message from the second gateway; the sending module is also used to send a request message to the ACS system; wherein the request message includes configuration information, which is used for the ACS system to register and authenticate the second gateway based on the second logical ID and the configuration information; the receiving module is also used to receive a response message from the ACS system, and the sending module is also used to send a response message to the second gateway, the response message being used to indicate that the second gateway has successfully registered and authenticated on the ACS system.

[0017] In one possible implementation, the apparatus further includes a generation module configured to generate a second logical ID based on the first logical ID, wherein the second logical ID includes the first logical ID and a target suffix, and the first logical ID is the logical ID of the first gateway.

[0018] In another possible implementation, the receiving module is further used to receive a registration authentication request message from the second gateway; the registration authentication request message is used to request authentication with the first gateway; the sending module is further used to send a registration authentication confirmation message to the second gateway; the registration authentication confirmation message is used to indicate that the authentication of the second gateway with the first gateway is successful.

[0019] In a fifth aspect, the present application provides a gateway registration device, which is applied to the second gateway of a fiber-to-the-room FTTR network, where the second gateway is connected to the first gateway as a master gateway as a slave gateway. The device includes a receiving module and a sending module; the receiving module is used to receive configuration information from the first gateway; wherein the configuration information includes: remote management parameter configuration items and logical ID parameter configuration items of the automatic configuration server ACS system, and the logical ID parameter configuration items include a second logical ID; the second logical ID is used to indicate the second gateway and indicate that the second gateway is a slave gateway of the first gateway; the sending module is used to send a request message to the ACS system, the request message includes configuration information, and is used for the ACS system to register and authenticate the second gateway based on the second logical ID and configuration information received from the first gateway; the receiving module is also used to receive a response message from the ACS system, and the response message is used to indicate that the second gateway has successfully registered and authenticated on the ACS system.

[0020] In a possible implementation, the sending module is specifically configured to send a request message to the ACS system through the first gateway; and the receiving module is specifically configured to receive a response message sent by the ACS system through the first gateway.

[0021] In another possible implementation, the sending module is also used to send a registration authentication request message to the first gateway; the registration authentication request message is used to request authentication with the first gateway; the receiving module is also used to receive a registration authentication confirmation message from the first gateway; the registration authentication confirmation message is used to indicate that the authentication of the second gateway with the first gateway is successful.

[0022] In a sixth aspect, the present application provides a gateway registration device, which is applied to an automatic configuration server ACS system of a fiber-to-the-room FTTR network. The device includes an authentication module, a receiving module, a registration module, and a sending module; the authentication module is used to authenticate with a first gateway so that the first gateway obtains remote management parameter configuration items of the ACS system; the receiving module is used to receive a second logical ID from the first gateway; the second logical ID is used to indicate a second gateway and indicate that the second gateway is a slave gateway of the first gateway; the receiving module is also used to receive a request message from the second gateway; wherein the request message includes configuration information, and the configuration information includes: remote management parameter configuration items and logical ID parameter configuration items of the ACS system, and the logical ID parameter configuration items include the second logical ID; the registration module is used to register and authenticate the second gateway based on the second logical ID and the configuration information; the sending module is used to send a response message to the second gateway; wherein the response message is used to indicate that the second gateway has successfully registered and authenticated on the ACS system.

[0023] In a possible implementation, the receiving module is specifically configured to receive a request message sent by the second gateway through the first gateway; and the sending module is specifically configured to send a response message to the second gateway through the first gateway.

[0024] In another possible implementation, the device further includes an establishment module and a management module; the establishment module is configured to establish a home network topology map based on the second logical ID, the home network topology map including the subordinate relationship between the first gateway and the second gateway. The management module is configured to manage the first gateway, and management of the first gateway includes one or more of the following: querying downstream optical interface information, managing the number of downstream devices, and querying downstream device information. The management module is also configured to manage the second gateway, and management of the second gateway includes one or more of the following: reading gateway parameter information, configuring parameter information, updating software versions, restoring factory settings, and restarting the device.

[0025] In the seventh aspect, the present application provides a gateway registration device, which includes: a processor and a memory; the memory stores instructions executable by the processor; when the processor is configured to execute the instructions, the gateway registration device implements the method of any one of the first to third aspects above.

[0026] In an eighth aspect, the present application provides a computer-readable storage medium, which includes: computer software instructions; when the computer software instructions are executed in a gateway registration device, the gateway registration device implements the method of any one of the first to third aspects above.

[0027] In the ninth aspect, the present application provides a gateway registration system, which is applied to a fiber-to-the-room FTTR network. The gateway registration system includes a first gateway, one or more second gateways and an automatic configuration server ACS system; the first gateway serves as a master gateway and is connected to one or more second gateways as slave gateways; wherein the first gateway includes the gateway registration device described in the fourth aspect; the second gateway includes the gateway registration device described in the fifth aspect; and the ACS system includes the gateway registration device described in the sixth aspect.

[0028] The beneficial effects of the fourth to ninth aspects mentioned above can be referred to the corresponding descriptions of the first to third aspects and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 A schematic diagram of an FTTR network deployment solution provided for this application;

[0030] Figure 2 A schematic diagram of the application environment of a gateway registration method provided in this application;

[0031] Figure 3 A schematic diagram of the gateway registration method provided for this application;

[0032] Figure 4 A flowchart of another gateway registration method provided for this application;

[0033] Figure 5 A schematic diagram of a home network topology provided for this application;

[0034] Figure 6 A schematic diagram of the composition of a gateway registration device provided in this application;

[0035] Figure 7 A schematic diagram of the composition of another gateway registration device provided by this application;

[0036] Figure 8 A schematic diagram of the composition of another gateway registration device provided by this application;

[0037] Figure 9 This is a schematic diagram of the structure of a gateway registration device provided in this application. DETAILED DESCRIPTION

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

[0039] It should be noted that in the embodiments of this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described in the embodiments of this application as "exemplarily" or "for example" should not be interpreted as being more preferred or advantageous than other embodiments or designs. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

[0040] In order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order.

[0041] With the emergence of various new network services, people have higher demands on network capabilities. To meet the network requirements of new services, FTTR technology came into being and gradually became popular.

[0042] A home network that uses FTTR technology is called an FTTR network, which includes a master gateway and multiple slave gateways. There are two deployment schemes for FTTR networks, such as Figure 1 The point-to-multipoint (P2MP) solution shown in (a) of FIG. Figure 1 The point-to-point (Point 2 Point) solution shown in (b) in FIG.

[0043] Among them, such as Figure 1 As shown in Figure (a), the P2MP solution is based on fiber optic networking. A master gateway is deployed in a home distribution box or central location. With the master gateway as the core, an FTTR network is constructed based on optical splitters and slave gateways. In the P2MP solution, the master gateway connects to the optical line terminal (OLT) and connects to multiple slave gateways using optical splitters and optical fibers.

[0044] like Figure 1 As shown in (b) of Figure 1, the P2P solution also relies on fiber optic networking. A master gateway is deployed in a home distribution box or central location. The master gateway serves as the core, and multiple slave gateways serve as downstream devices to form an FTTR network. In this P2P solution, the master gateway connects to the OLT and directly connects to multiple slave gateways using fiber optic cables.

[0045] In an FTTR network, the master gateway is a new home optical modem. Positioned between the optical line terminal (OLT) and slave gateways, the master gateway connects to the OLT via XG(S)-PON or 10GEPON, supporting Gigabit-to-the-home (GTT), and provides fiber optic interfaces for connecting to slave gateways. In an FTTR network, the optical network extends further down to each slave gateway, with the master gateway serving as a bridging link. As the center of the home network, the master gateway provides unified management and configuration for all slave gateways.

[0046] Slave gateways are distributed wireless fidelity (Wi-Fi) access devices in every room of the home. They connect to the main gateway via fiber optic cables and provide Wi-Fi 6 and Ethernet ports for access to various home internet terminals. Slave gateways are distributed networking devices deployed in each room of the FTTR network. They connect to the main gateway via fiber optic cables and operate in bridging mode. The main gateway uniformly allocates and manages Internet Protocol (IP) and IP addresses for downstream devices, forming a unified, interoperable local area network for the entire home.

[0047] There are currently two approaches to managing and controlling FTTR networks. One involves using a network management system developed by the manufacturer of FTTR equipment (such as the master or slave gateway in the FTTR network) for supporting FTTR equipment. However, because the network management system is developed by the manufacturer to complement its own products, its customized interface protocols and control methods are only applicable to its own equipment and cannot control equipment from other manufacturers, resulting in a tightly coupled system. Given the wide variety of FTTR equipment available on the market, relying on the manufacturer's network management system to manage FTTR networks would require operators to use multiple network management systems, increasing costs and significantly increasing the complexity of operations and maintenance. Subsequent maintenance and upgrades of the network management system would also require significant adjustments, making this approach unsuitable. Another approach involves using the operator's existing ACS system to manage and control the FTTR network. However, the ACS system is based on the international standard TR069 protocol to manage the master gateway in the home network and does not define control methods for a two-level architecture consisting of a master and slave gateway. This means that existing ACS systems cannot manage and control the slave gateways in the FTTR network. Therefore, there is currently no unified and effective control standard for FTTR networks.

[0048] Against this backdrop, embodiments of the present application provide a gateway registration method that enables slave gateways in an FTTR network to register and go online with an ACS system, enabling the ACS system to effectively manage and control slave gateways in the FTTR network. Furthermore, this method can be used to manage FTTR equipment from different manufacturers, facilitating collaborative management of FTTR networks by operators and achieving unified and effective control of FTTR networks.

[0049] The gateway registration method provided in this application can be applied to Figure 2 The gateway registration system shown in the figure. Figure 2 As shown, the gateway registration system may include: an ACS system 101, a master gateway 102 and one or more slave gateways 103. Figure 2 Two slave gateways 103 are shown in the figure, but the number of slave gateways in the gateway registration system is not limited.

[0050] The ACS system 101 is connected to the master gateway 102 via the L1 interface. The ACS system 101 is connected to one or more slave gateways 103 via the L2 interface. The master gateway 102 is connected to one or more slave gateways 103 via the L3 interface. The I1 interface is a logical interface between the master gateway and the ACS system, enabling the ACS to manage and control the master gateway. The I2 interface is a logical interface between the slave gateway and the ACS system, enabling the ACS to manage and control the slave gateways. The L3 interface is a logical interface between the master gateway and the slave gateways, enabling the master gateway to manage and control the slave gateways.

[0051] In some embodiments, when the ACS system 101 needs to control the slave gateway 103, the master gateway 102 may report the logical identity document (ID) of the slave gateway 103 to the ACS system, and the master gateway 102 may send configuration information and the logical ID of the slave gateway 103 to the slave gateway 103. The slave gateway 103 then registers and authenticates with the ACS system 101 based on the configuration information and the logical ID, allowing the ACS system 101 to control the slave gateway 103, thereby enabling the ACS system 101 to control the entire FTTR network.

[0052] Figure 3 A flow chart of a gateway registration method provided in an embodiment of the present application. Figure 3 As shown, the gateway registration method provided in this application can be implemented by the above-mentioned network element registration system, and can specifically include the following steps:

[0053] S301: The first gateway performs authentication with the ACS system.

[0054] The first gateway can be the primary gateway in the FTTR network. The primary gateway and the ACS system can authenticate based on the TR069 protocol. TR069 is a communication protocol for interaction between customer premises equipment (CPE) and the ACS system. Based on this protocol, the CPE can perform functions such as service provisioning, feature configuration, file upload and download, and system testing. In this solution, the primary gateway is the CPE.

[0055] The master gateway can register and authenticate on the ACS system to obtain remote management parameter configuration items of the ACS system. The remote management parameter configuration items can be used for registration and authentication of the slave gateway on the ACS system.

[0056] S302: The first gateway sends configuration information to the second gateway.

[0057] The second gateway may be a slave gateway in the FTTR network. The configuration information may include: a remote management parameter configuration item and a logical ID parameter configuration item of the ACS system. The logical ID parameter configuration item may include a second logical ID. The second logical ID is used to indicate the second gateway and to indicate that the second gateway is a slave gateway of the first gateway (or to indicate a subordinate relationship between the slave gateway and the master gateway).

[0058] After obtaining the remote management parameter configuration item of the ACS system, the master gateway may send the remote management parameter configuration item of the ACS system and the logical ID parameter configuration item including the second logical ID to the slave gateway.

[0059] S303: The first gateway sends the second logical ID to the ACS system.

[0060] The master gateway may send the second logical ID to the ACS system. After receiving the second logical ID, the ACS system may save the second logical ID to authenticate subsequent request messages from the slave gateway.

[0061] S304: The second gateway sends a request message to the ACS system, where the request message includes configuration information.

[0062] The request message may be used by the ACS system to perform registration authentication on the slave gateway according to the second logical ID and configuration information.

[0063] After S302, the slave gateway may receive the configuration information sent by the master gateway. After receiving the configuration information, the slave gateway may send a request message carrying the configuration information to the ACS system for registration and authentication of the slave gateway on the ACS system.

[0064] S305: The ACS system registers and authenticates the second gateway according to the second logical ID and configuration information.

[0065] After receiving the request message from the slave gateway, the ACS system can register and authenticate the slave gateway according to the remote management parameter configuration items and logical ID parameter configuration items of the ACS system in the configuration information carried in the request message, and the pre-stored second logical ID.

[0066] S306: After the registration authentication of the second gateway is successful, the ACS system sends a response message to the second gateway.

[0067] The response message is used to indicate that the second gateway has been successfully registered and authenticated on the ACS system.

[0068] After the ACS system authenticates the registration of the slave gateway according to the configuration information and the second logical ID, the ACS system may send a response message to the slave gateway to indicate that the registration authentication of the slave gateway on the ACS system is successful.

[0069] The gateway registration method provided in this application sends configuration information to the slave gateway through the master gateway in the FTTR network and assigns a logical ID to the slave gateway, so that the slave gateway can use the configuration information and the logical ID to register and authenticate on the ACS system. This allows the ACS system to control the slave gateways in the FTTR network, and then control the entire FTTR network, thus compensating for the shortcomings of the existing ACS system in controlling the FTTR network and achieving unified and effective control of the FTTR network. At the same time, the gateway registration method provided in this solution is based on the international standard TR069 protocol. FTTR equipment from different manufacturers can all use this method to register and authenticate on the ACS system, allowing operators to collaboratively manage equipment from different manufacturers and facilitating operators' unified management of the FTTR network.

[0070] The following will describe in detail a gateway registration method provided by the embodiment of the present application in conjunction with specific embodiments, which can be applied to a gateway registration system. Figure 4 As shown, the method may include:

[0071] S401: A first gateway authenticates with an ACS system to obtain remote management parameter configuration items of the ACS system.

[0072] The first gateway may be a main gateway in the FTTR network.

[0073] In some embodiments, the master gateway can authenticate with the ACS system. After authentication, the master gateway can obtain remote management parameter configuration items of the ACS system. These remote management parameter configuration items of the ACS system can be used by the slave gateway to register and authenticate with the ACS system. The specific process for registering and authenticating the master gateway with the ACS system is specified in the TR069 protocol and can be found in related art descriptions, so this will not be repeated here.

[0074] The remote management parameter configuration items of the ACS system may include one or more of the following parameters: ACS website, ACS authentication user name, ACS authentication password, and parameters related to the gateway periodically reporting its own online status.

[0075] For example, the remote management parameter configuration items of the ACS system may be as shown in Table 1 below:

[0076] Table 1

[0077]

[0078]

[0079] As shown in Table 1, the remote management parameter configuration items of the ACS system can include specific parameters and corresponding parameter information. It should be noted that in the data types in Table 1, Object is an object type; String is a string type, and String(256) indicates that the maximum length of the string is 256; Boolean is a Boolean type, and the Boolean type has only two states: True and False; Int is an integer type, UnsignedInt is an unsigned integer type, and UnsignedInt[1:] indicates slicing the unsigned integer data, taking only the data from the second digit to the end; DateTime is a timestamp type, and the timestamp format can be year-month-day-hour-minute-second. Under the corresponding write field in Table 1, the R indicates that the parameter is configurable and modifiable. Under the corresponding read field in Table 1, the R indicates that the parameter is readable. The description field in Table 1 is an explanation of the parameter.

[0080] For example, the parameter corresponding to the URL of the ACS system is the Uniform Resource Locator (URL), and the corresponding data type is a string type with a maximum length of 256. This parameter is readable and writable, and the description indicates that this parameter is the URL address of the ACS system. The parameter corresponding to the username of the ACS system is Username, and the corresponding data type is a string type with a maximum length of 256. This parameter is readable and writable, and the description indicates that this parameter is the authentication username. The parameter corresponding to the password of the ACS system is Password, and the corresponding data type is a string with a maximum length of 256. This parameter is readable and writable, and the description indicates that this parameter is the authentication password. Similarly, the parameters related to the gateway periodically reporting its own online status are PeriodicInformEnable, PeriodicInformInterval, and PeriodicInformTime, which will not be repeated here.

[0081] S402: The second gateway sends a registration authentication request message to the first gateway.

[0082] The second gateway may be a slave gateway of the FTTR network, and the registration authentication request message is used to request authentication with the first gateway.

[0083] The master gateway is the core of the FTTR network and is responsible for the unified management and configuration of all slave gateways. Only after the authentication relationship between the master and slave gateways is established can the master gateway manage and issue configuration information to the slave gateways.

[0084] In some embodiments, after a physical connection is established between the slave gateway and the master gateway (ie, there is an optical fiber connection between the master and slave gateways), the slave gateway may send a registration authentication request message to the master gateway to request authentication with the master gateway.

[0085] S403: The first gateway sends a registration authentication confirmation message to the second gateway.

[0086] The registration authentication confirmation message is used to indicate that the authentication between the second gateway and the first gateway is successful.

[0087] In some embodiments, after receiving a registration authentication request message from a slave gateway, the master gateway may authenticate the slave gateway based on the registration authentication request message. After successful authentication, the master gateway may send a registration authentication confirmation message to the slave gateway to indicate that authentication between the slave gateway and the master gateway is successful. After successful authentication, the master gateway may manage the slave gateway and may also send configuration information to the slave gateway.

[0088] S404: The first gateway generates a second logical ID according to the first logical ID.

[0089] The first logical ID may be the logical ID of the first gateway. The second logical ID is used to indicate the second gateway and to indicate that the second gateway is a slave gateway of the first gateway.

[0090] In some embodiments, after successful authentication between a master gateway and a slave gateway, the master gateway may generate a logical ID for the slave gateway based on its own logical ID. The number of logical IDs generated for slave gateways is determined by the number of slave gateways authenticated on the master gateway. The logical ID of a slave gateway is used to identify the slave gateway and the master gateway that manages the slave gateway, or in other words, to indicate the subordinate relationship between the master gateway and the slave gateway.

[0091] For example, after the master gateway and the slave gateway are successfully authenticated, the master gateway can generate the logical ID of the slave gateway by adding the suffix "-xx" after its own logical ID. For example, "xx" is a decimal number, which can start from 01 and range from 01 to 99. The suffix of each slave gateway is automatically assigned by the master gateway in a unified and default order according to the authentication time with the master gateway, and manual modification is allowed. It can be understood that the logical ID of the slave gateway is generated by adding a numerical suffix to the logical ID of the master gateway. Therefore, the logical ID of the slave gateway can not only indicate the slave gateway, but also indicate the slave gateway and the master gateway that manages the slave gateway.

[0092] For example, an FTTR network includes two master gateways, Master Gateway 1 and Master Gateway 2, and five slave gateways, Slave Gateway 1, Slave Gateway 2, Slave Gateway 3, Slave Gateway 4, and Slave Gateway 5. The logical ID of Master Gateway 1 is GW-DEVI, and the logical ID of Master Gateway 2 is GW-ACD. Slave Gateways 1, 2, and 3 are connected to Master Gateway 1 and are ordered in the order of authentication time: Slave Gateway 1 - Slave Gateway 2 - Slave Gateway 3. Master Gateway 1 can generate the logical ID GW-DEVI-01 for Slave Gateway 1, GW-DEVI-02 for Slave Gateway 2, and GW-DEVI-03 for Slave Gateway 3. Similarly, Slave Gateways 4 and 5 are connected to Master Gateway 2 and are ordered in the order of authentication time: Slave Gateway 4 - Slave Gateway 5. Then, the master gateway 2 can generate a logical ID of the slave gateway 4 as GW-ACD-01, and the master gateway 2 can generate a logical ID of the slave gateway 5 as GW-ACD-02.

[0093] S405: The first gateway sends configuration information to the second gateway.

[0094] The configuration information may include: a remote management parameter configuration item and a logical ID parameter configuration item of the ACS system, and the logical ID parameter configuration item may include the second logical ID.

[0095] In some embodiments, after the master gateway generates the second logical ID, it can automatically send configuration information to the slave gateway. This configuration information can include remote management parameter configuration items of the ACS system and logical ID parameter configuration items including the second logical ID. This configuration information can be used by the slave gateway to register and authenticate with the ACS system.

[0096] In other embodiments, after the master gateway generates the second logical ID, the master gateway may send configuration information to the slave gateway after receiving an operation instruction from the administrator, wherein the operation instruction may be an instruction for instructing the slave gateway to register and authenticate on the ACS system.

[0097] The logical ID parameter configuration item may include one or more parameters from the logical ID of the gateway, a password corresponding to the logical ID, and parameters related to matching between the gateway and the ACS system.

[0098] For example, in the configuration information, the remote management parameter configuration items of the ACS system are shown in Table 1 above, and the logical ID parameter configuration items are shown in Table 2 below:

[0099] Table 2

[0100]

[0101]

[0102] As shown in Table 2, the parameters included in the logical ID parameter configuration item and the corresponding parameter information. For example, the parameter corresponding to the logical ID is UserName, and the corresponding data type is string type. This parameter is readable and writable, and is described as the logical ID. The parameter corresponding to the password of the logical ID is UserId, and the corresponding data type is string type. This parameter is readable and writable, and is described as the password of the logical ID. The relevant parameters for the matching between the gateway and the ACS system include Status, and the corresponding data type of this parameter is unsigned integer type. This parameter is readable and writable, and is described as whether the platform has successfully matched the gateway: a value of 1 indicates that the ID card does not exist; a value of 2 indicates that the broadband account does not exist; a value of 3 indicates that the ID card and the broadband account fail to match; a value of 4 indicates a match timeout; a configuration of 6 indicates that the registration has already been completed and there is no new work order to be executed; a value of 99 indicates that there is no authentication result information. Similarly, the relevant parameters for the matching between the gateway and the ACS system also include the Limit parameter, the Times parameter, and the Result parameter, which will not be repeated here.

[0103] It should be noted that the remote management configuration parameter items of the ACS system in the configuration information sent by the master gateway to the connected slave gateways are the same and consistent with the master gateway. The parameter UserName indicating the logical ID in the logical ID parameter configuration items sent by the master gateway to different slave gateways is related to the logical ID of each slave gateway. Other parameters are the same and consistent with the master gateway. For example, the parameter UserName in the logical ID parameter configuration item sent by master gateway 1 to slave gateway 1 is GW-DEVI-01, the parameter UserName in the logical ID parameter configuration item sent by master gateway 1 to slave gateway 2 is GW-DEVI-02, and the parameter UserName in the logical ID parameter configuration item sent by master gateway 1 to slave gateway 3 is GW-DEVI-03.

[0104] S406: The first gateway sends the second logical ID to the ACS system.

[0105] In some embodiments, after the master gateway generates the logical ID of the slave gateway, the master gateway can proactively report the logical ID of the slave gateway to the ACS system. The reported logical ID can be used for subsequent registration and authentication of the slave gateway on the ACS system.

[0106] It should be noted that the step of the primary gateway sending the second logical ID to the ACS system may be performed before the above-mentioned S405, or after the step S405, or simultaneously with the step S405, and this embodiment of the present application does not impose any limitation on this.

[0107] For example, using the example in the above embodiment, after master gateway 1 generates logical IDs for slave gateways, it sends the logical IDs of the connected slave gateways, GW-DEVI-01, GW-DEVI-02, and GW-DEVI-03, to the ACS system. Similarly, after master gateway 2 generates logical IDs for slave gateways, it sends the logical IDs of the connected slave gateways, GW-ACD-01 and GW-ACD-02, to the ACS system. This facilitates subsequent registration and authentication of the slave gateways with the ACS system.

[0108] S407: The second gateway sends a request message to the first gateway.

[0109] The request message includes configuration information, and the request information is used to request registration and authentication on the ACS system from the gateway.

[0110] In some embodiments, the slave gateway registers and authenticates on the ACS system and needs to forward a request message to the ACS system through the master gateway. Therefore, the slave gateway can be modified to connect to the master gateway in bridging mode so that the master gateway can more easily forward the slave gateway's request message.

[0111] Furthermore, after receiving the configuration information sent by the master gateway, the slave gateway may send a request message carrying the configuration information to the master gateway to request registration and authentication on the ACS system.

[0112] S408: The first gateway sends a request message to the ACS system.

[0113] In the above embodiment, the request message includes configuration information, and the remote management configuration parameter item of the ACS system in the configuration information includes the URL of the ACS system. Therefore, after receiving the request message from the slave gateway, the master gateway forwards the request message from the slave gateway to the ACS system based on the ACS system URL in the request message, so that the ACS system can receive the request message from the slave gateway.

[0114] S409: The ACS system registers and authenticates the second gateway according to the second logical ID and configuration information.

[0115] In some embodiments, after receiving the request message from the slave gateway, the ACS system extracts the configuration information in the request message and performs registration authentication on the slave gateway according to the second logical ID pre-stored in the ACS system.

[0116] It should be noted that during the registration and authentication process for the slave gateway, the ACS system can authenticate the authentication username and authentication password in the ACS system's remote management parameter configuration item in the configuration information. This remote management parameter configuration item is used to verify whether the slave gateway is qualified to remotely manage the configuration. Furthermore, the ACS system can also authenticate the logical ID and logical ID password in the logical ID parameter configuration item in the configuration information. This logical ID parameter configuration item is used to verify the slave gateway's eligibility to register and authenticate with the ACS system. This is a double-safety mechanism set up by the ACS system based on the TR069 protocol. The specific authentication process can be referred to the description in the relevant technology and will not be repeated in the embodiments of this application.

[0117] S410: The ACS system sends a response message to the first gateway.

[0118] The response message is used to indicate that the second gateway has been successfully registered and authenticated on the ACS system.

[0119] In some embodiments, after the ACS successfully authenticates the slave gateway's registration, the ACS may send a response message to the master gateway corresponding to the slave gateway, indicating that the slave gateway has successfully registered and authenticated with the ACS. The response message may also carry the slave gateway's logical ID, which the master gateway forwards to the slave gateway corresponding to the logical ID.

[0120] S411. The first gateway sends a response message to the second gateway.

[0121] In some embodiments, after receiving a response message from the ACS, the master gateway forwards the response message to the slave gateway corresponding to the logical ID carried in the response message. This allows the slave gateway to register and authenticate with the ACS, allowing the ACS to directly manage and control the slave gateway.

[0122] After the slave gateway successfully registers and authenticates with the ACS system, the ACS system can manage the FTTR network. For example, it can create a home network topology, read the configuration information of the master and slave gateways, and send the configuration information to the master and slave gateways. For example, the following steps can be executed: S412-S414.

[0123] S412: The ACS system establishes a home network topology map according to the second logical ID.

[0124] In some embodiments, the ACS system may obtain the connection relationship and the subordinate relationship between the master and slave gateways from the logical ID of the slave gateway to establish a home network topology diagram.

[0125] For example, take the slave gateway 1 to the slave gateway 5 in the above example. The ACS system obtains the logical ID of the slave gateway 1 as GW-DEVI-01, the logical ID of the slave gateway 2 as GW-DEVI-02, and the logical ID of the slave gateway 3 as GW-DEVI-03. Since the logical ID of the slave gateway is generated by adding a digital suffix to the logical ID of the master gateway, the ACS system can determine that the master gateway connected by the slave gateway 1 to the slave gateway 3 is GW-DEVI. Similarly, the ACS system obtains the logical ID of the slave gateway 4 as GW-ACD-01, and the logical ID of the slave gateway 5 as GW-ACD-02, then the ACS system can determine that the master gateway connected by the slave gateway 4 and the slave gateway 5 is GW-ACD. Based on these connection relationships and subordinate relationships obtained, the ACS system can establish a home network topology diagram, such as the established home network topology diagram can be as shown below. Figure 5 As shown, the slave gateways GW-DEVI-01, GW-DEVI-02 and GW-DEVI-03 are connected to the master gateway GW-DEVI, and the slave gateways GW-ACD-01 and GW-ACD-02 are connected to the master gateway GW-ACD.

[0126] S413: The ACS system manages the first gateway.

[0127] In some embodiments, the ACS system can manage the master gateway, and the management of the master gateway includes one or more of the following: querying downstream optical interface information, managing the number of downstream devices, and querying downstream device information.

[0128] The downstream optical interface information may include the parameters shown in Table 3 below, specifically including parameters related to the downstream PON interface and parameters related to optical module status detection.

[0129] Table 3

[0130]

[0131]

[0132] As shown in Table 3, the downstream optical interface information of the main gateway can be obtained from Table 3, including the relevant information of the downstream PON interface and the optical module status detection information. For example, in the relevant information of the downstream PON interface, the parameter for enabling the connection of the downstream PON interface is Enable, and the corresponding data type is Boolean type. This parameter is readable and writable, and is described as the state of enabling the connection. True is to enable the connection, and False is to refuse the connection. The parameter of the physical connection status of the PON interface is Status, and the corresponding data type is string type. This parameter can only be read and is described as the physical connection status. Similarly, the relevant information of the downstream PON interface also includes parameters such as the interface standard used by the gateway, the maximum bandwidth that can be achieved by the upstream PON port, and the maximum bandwidth that can be achieved by the downstream PON port, which will not be repeated here.

[0133] In the optical module status detection information, the parameter corresponding to the optical module temperature is "Temperature," which is an integer data type and is read-only. It is described as a temperature in units of 1 / 256 degrees Celsius. The parameter corresponding to the optical module supply voltage is "Vcc," which is an unsigned integer data type and is read-only. It is described as the supply voltage in units of 100 microvolts. Similarly, the optical module status detection information also includes parameters such as the optical transmitter bias current, transmit power, and receive power, which are not detailed here.

[0134] The ACS system manages the master gateway and also manages the number of connected devices. The management parameters for the number of connected devices are shown in Table 4 below:

[0135] Table 4

[0136]

[0137] As shown in Table 4, the parameter for managing the number of downstream devices is NumberOfSubEdgeONT, which has a corresponding data type of UnsignedInt. This parameter can be read or configured, and describes the number of slave gateways allowed to connect. The ACS system can configure the NumberOfSubEdgeONT parameter to manage devices connected to the master gateway. To unrestrict the number of slave gateways, set the value to 0.

[0138] The ACS system's management of the master gateway also includes querying the information of the downstream devices, which may include the parameters shown in Table 5 below.

[0139] Table 5

[0140]

[0141]

[0142] As shown in Table 5, the information of the downstream device of the master gateway (i.e., the connected FTTR slave gateway) is as follows. For example, the parameter corresponding to the logical ID of the slave gateway is UserName, and the corresponding data type is a string type. This parameter can only be read and is described as the logical ID of the slave gateway. The parameter corresponding to the status of the slave gateway is Status, and the corresponding data type is a String type. This parameter can only be read and is described as the status of the slave gateway. In some examples, if the slave gateway is online, the value of the Status parameter is Online; if the slave gateway is offline, the value of the Status parameter is Offline. When the slave gateway is online or offline, the master gateway needs to actively report the status of the slave gateway to the ACS system so that the ACS system can obtain the status information of each gateway in the FTTR network in a timely manner to deal with the problem of failure of the slave gateway, so that the ACS system can maintain the FTTR network in a timely manner.

[0143] S414: The ACS system manages the second gateway.

[0144] In some embodiments, the ACS system can manage the slave gateway, and the management of the slave gateway includes one or more of the following: reading gateway parameter information, configuring parameter information, updating software version, restoring factory settings, and restarting the device.

[0145] The reading and configuration of gateway parameter information may include the parameters shown in Table 1. The software version update and device restart functions of the slave gateway are consistent with the software version update and device restart performed by the ACS system on the master gateway in the related art, and are not described in detail here.

[0146] The ACS system can also manage the slave gateway by restoring the factory settings. The configuration parameters for restoring the factory settings are shown in Table 6 below:

[0147] Table 6

[0148]

[0149] As shown in Table 6, the parameter corresponding to the factory reset mode is Mode, which has an integer data type. This parameter is both configurable and readable, and is described as factory reset mode. To restore the factory settings of a gateway, the ACS system can configure this Mode parameter. Setting the Mode value to 0 does not retain any key parameters after restoring the gateway to factory settings. Setting the Mode value to 1 retains key parameters after restoring the gateway to factory settings. For definitions of key parameters, refer to the terminal technical specifications.

[0150] The gateway can initiate a registration and authentication request to the ACS system, and the ACS system can also proactively initiate a registration and authentication request to the gateway. Therefore, this solution also provides a remote management parameter configuration item for the ACS system when the ACS system proactively initiates a registration and authentication request to the gateway, as shown in Table 7 below:

[0151] Table 7

[0152]

[0153] Table 7 provides the relevant parameters for the ACS system's proactive registration and authentication requests to the gateway. For example, the parameter corresponding to the gateway's URL is ConnectionRequestURL, which is a string with a maximum length of 256 characters. This parameter is read-only and describes the HTTP URL used by the ACS when initiating connection request notifications to the CPE. The parameter corresponding to the authentication username used by the ACS initiating registration and authentication requests to the gateway is ConnectionRequestUsername, which is a string with a maximum length of 256 characters. This parameter is both readable and writable and describes the username used during the authentication process when the ACS initiates connection requests to the CPE. The parameter corresponding to the authentication password is ConnectionRequestPassword, which is a string with a maximum length of 256 characters. This parameter is both readable and writable and describes the password used during the authentication process when the ACS initiates connection requests to the CPE. Similarly, when the ACS system proactively initiates registration and authentication requests to the gateway, the ACS system's remote management parameter configuration items also include the following parameters: UpgradesManaged, UDPConnectionRequestAddress, and UDPConnectionRequestAddressNotificationLimit, which are not detailed here.

[0154] In addition, depending on whether the Session Traversal Utilities for NAT (STUN) function is enabled on the gateway, this solution also adds parameters related to the STUN function to the remote management parameter configuration items of the ACS system, as shown in Table 8 below:

[0155] Table 8

[0156]

[0157] STUN is a network protocol that allows a client behind a Network Address Translation (NAT) to find out its public address, the type of NAT it is behind, and the Internet port to which the NAT binds a local port. This information is used to establish User Datagram Protocol (UDP) communication between two hosts behind NAT routers.

[0158] Table 8 shows the newly added STUN function-related parameters in the remote management parameter configuration items of the ACS system when the STUN function is enabled on the gateway. For example, the parameter corresponding to the IP address of the STUN server is STUNServerAddress, and the corresponding data type is a string with a maximum length of 256. This parameter is readable and writable, and is described as the IP address of the STUNServer. The parameter corresponding to the STUN username is STUNUsername, and the corresponding data type is a string with a maximum length of 256. This parameter is readable and writable, and is described as the STUN username. The parameter corresponding to the STUN password is STUNPassword, and the corresponding data type is a string with a maximum length of 256. This parameter is readable and writable, and is described as the STUN password. Similarly, other parameters related to the STUN function are not detailed here.

[0159] The technical solutions provided by the above-mentioned embodiments bring at least the following beneficial effects: This solution, through the master gateway in the FTTR network, sends configuration information to the slave gateway and assigns a logical ID to the slave gateway, allowing the slave gateway to use this configuration information and the logical ID to register and authenticate on the ACS system. This allows the ACS system to manage and control the slave gateways in the FTTR network, and thus the entire FTTR network, thus overcoming the shortcomings of the existing ACS system in managing the FTTR network and achieving unified and effective management of the FTTR network. Furthermore, the gateway registration method provided by this solution is based on the international standard TR069 protocol. FTTR equipment from different manufacturers can all use this method to register and authenticate on the ACS system, allowing operators to collaboratively manage equipment from different manufacturers and facilitating unified management of the FTTR network.

[0160] Furthermore, in this solution, the master gateway generates the logical ID of the slave gateway connected to it based on its own logical ID. This allows the slave gateway to register with the ACS system and then establish a home network topology based on the logical ID, facilitating network management and maintenance for operators. Furthermore, the ACS system can directly manage and control the slave gateways in the FTTR network, querying their operating parameters and performing operations such as software updates, factory resets, and device reboots. This ensures timely maintenance of the slave gateway's operating status, and ultimately the entire FTTR network, providing users with a better user experience.

[0161] In an exemplary embodiment, the present application further provides a gateway registration device, which may include one or more functional modules for implementing the gateway registration method of the above method embodiment.

[0162] For example, Figure 6 A schematic diagram of a gateway registration device provided in an embodiment of the present application. Figure 6 As shown, the gateway registration device includes: an authentication module 601, a sending module 602 and a receiving module 603. The authentication module 601, the sending module 602 and the receiving module 603 are connected.

[0163] The authentication module 601 is used to authenticate with the ACS system to obtain remote management parameter configuration items of the ACS system.

[0164] The sending module 602 is used to send configuration information to the second gateway. The configuration information includes: remote management parameter configuration items and logical ID parameter configuration items of the ACS system. The logical ID parameter configuration items include a second logical ID. The second logical ID is used to indicate the second gateway and to indicate that the second gateway is a slave gateway of the first gateway.

[0165] The sending module 602 is further configured to send the second logical ID to the ACS system; the receiving module is configured to receive a request message from the second gateway; and the sending module is further configured to send a request message to the ACS system; wherein the request message includes configuration information for the ACS system to register and authenticate the second gateway based on the second logical ID and the configuration information.

[0166] The receiving module 603 is further configured to receive a response message from the ACS system and send the response message to the second gateway, where the response message is used to indicate that the second gateway has been successfully registered and authenticated on the ACS system.

[0167] In some embodiments, the apparatus further includes: a generating module 604. The generating module 604 is configured to generate a second logical ID according to the first logical ID, wherein the second logical ID includes the first logical ID and a target suffix, and the first logical ID is the logical ID of the first gateway.

[0168] In some embodiments, the receiving module 603 is further configured to receive a registration authentication request message from the second gateway; the registration authentication request message is used to request authentication with the first gateway.

[0169] The sending module 602 is further configured to send a registration authentication confirmation message to the second gateway; the registration authentication confirmation message is used to indicate that the authentication between the second gateway and the first gateway is successful.

[0170] Figure 7 A schematic diagram of a gateway registration device provided in an embodiment of the present application. Figure 7 As shown, the gateway registration device includes: a receiving module 701 and a sending module 702. The receiving module 701 and the sending module 702 are connected.

[0171] Receiving module 701 is used to receive configuration information from a first gateway. The configuration information includes: remote management parameter configuration items and logical ID parameter configuration items of the ACS system. The logical ID parameter configuration items include a second logical ID. The second logical ID is used to indicate a second gateway and to indicate that the second gateway is a slave gateway of the first gateway.

[0172] The sending module 702 is configured to send a request message to the ACS system, where the request message includes configuration information, which is used by the ACS system to register and authenticate the second gateway according to the second logical ID and configuration information received from the first gateway.

[0173] The receiving module 701 is further configured to receive a response message from the ACS system, where the response message is used to indicate that the second gateway is successfully registered and authenticated on the ACS system.

[0174] In some embodiments, the sending module 702 is specifically configured to send a request message to the ACS system through the first gateway.

[0175] The receiving module 701 is specifically configured to receive a response message sent by the ACS system through the first gateway.

[0176] In some embodiments, the sending module 702 is further configured to send a registration authentication request message to the first gateway; the registration authentication request message is used to request authentication with the first gateway.

[0177] The receiving module 701 is further configured to receive a registration authentication confirmation message from the first gateway; the registration authentication confirmation message is used to indicate that the authentication between the second gateway and the first gateway is successful.

[0178] Figure 8 A schematic diagram of a gateway registration device provided in an embodiment of the present application. Figure 8As shown, the gateway registration device includes: an authentication module 801, a receiving module 802, a registration module 803 and a sending module 804. The authentication module 801, the receiving module 802, the registration module 803 and the sending module 804 are connected.

[0179] The authentication module 801 is configured to authenticate with the first gateway so that the first gateway can obtain remote management parameter configuration items of the ACS system.

[0180] The receiving module 802 is configured to receive a second logical ID from the first gateway; the second logical ID is used to indicate the second gateway and to indicate that the second gateway is a slave gateway of the first gateway.

[0181] The receiving module 802 is further configured to receive a request message from the second gateway. The request message includes configuration information, including remote management parameter configuration items and logical ID parameter configuration items of the ACS system. The logical ID parameter configuration items include the second logical ID.

[0182] The registration module 803 is configured to register and authenticate the second gateway according to the second logical ID and the configuration information.

[0183] The sending module 804 is configured to send a response message to the second gateway, wherein the response message is used to indicate that the second gateway has successfully registered and authenticated on the ACS system.

[0184] In some embodiments, the receiving module 802 is specifically configured to receive a request message sent by the second gateway through the first gateway.

[0185] The sending module 804 is specifically configured to send a response message to the second gateway through the first gateway.

[0186] In some embodiments, the apparatus further includes an establishment module 805 and a management module 806 .

[0187] The establishing module 805 is configured to establish a home network topology diagram according to the second logical ID, where the home network topology diagram includes a subordinate relationship between the first gateway and the second gateway.

[0188] The management module 806 is used to manage the first gateway. The management of the first gateway includes one or more of the following: querying the downlink optical interface information, managing the number of downstream devices, and querying the information of the downstream devices.

[0189] The management module 806 is also used for the ACS system to manage the second gateway. The management of the second gateway includes one or more of the following: reading gateway parameter information, configuring parameter information, updating software version, restoring factory settings and restarting the device.

[0190] In an exemplary embodiment, the present application also provides a gateway registration device, Figure 9 This is a schematic diagram of the structure of the gateway registration device provided in the embodiment of the present application. Figure 9 As shown, the gateway registration device may include: a processor 901 and a memory 902; the memory 902 stores instructions executable by the processor 901; when the processor 901 is configured to execute the instructions, the gateway registration device implements the method described in the aforementioned method embodiment.

[0191] In an exemplary embodiment, the present application also provides a computer-readable storage medium having computer program instructions stored thereon; when the computer program instructions are executed by a gateway registration device, the gateway registration device implements the method described in the aforementioned embodiment. The computer-readable storage medium can be a non-transitory computer-readable storage medium, for example, a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

[0192] In an exemplary embodiment, the present application also provides a computer program product. When the computer program product runs on a gateway registration device, it enables the gateway registration device to execute the above-mentioned related method steps to implement the gateway registration method in the above-mentioned embodiment.

[0193] The above are only specific embodiments of the present application, but the scope of protection of the present application is not limited thereto. Any changes or replacements within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A gateway registration method, characterized in that: A method for a first gateway in a fiber-to-the-room (FTTR) network, wherein the first gateway serves as a master gateway and is connected to one or more second gateways serving as slave gateways, includes: The first gateway authenticates with the automatic configuration server ACS system to obtain remote management parameter configuration items of the ACS system; The first gateway sends configuration information to the second gateway; wherein the configuration information includes: a remote management parameter configuration item and a logical ID parameter configuration item of the ACS system, the logical ID parameter configuration item includes a second logical ID; the second logical ID is used to indicate the second gateway and to indicate that the second gateway is a slave gateway of the first gateway; The first gateway sends the second logical ID to the ACS system; The first gateway receives the request message from the second gateway and sends the request message to the ACS system; wherein the request message includes the configuration information, which is used by the ACS system to register and authenticate the second gateway according to the second logical ID and the configuration information; The first gateway receives a response message from the ACS system and sends the response message to the second gateway, where the response message is used to indicate that the second gateway has successfully registered and authenticated on the ACS system.

2. The method according to claim 1, characterized in that Before the first gateway sends the configuration information to the second gateway, the method further includes: The first gateway generates the second logical ID according to the first logical ID; wherein the second logical ID includes the first logical ID and a target suffix, and the first logical ID is the logical ID of the first gateway.

3. The method according to claim 1 or 2, characterized in that Before the first gateway sends the configuration information to the second gateway, the method further includes: The first gateway receives a registration authentication request message from the second gateway; the registration authentication request message is used to request authentication with the first gateway; The first gateway sends a registration authentication confirmation message to the second gateway; the registration authentication confirmation message is used to indicate that the authentication between the second gateway and the first gateway is successful.

4. A gateway registration method, characterized in that: A second gateway is applied to a fiber-to-the-room (FTTR) network, the second gateway being connected as a slave gateway to a first gateway being a master gateway, the method comprising: The second gateway receives configuration information from the first gateway; wherein the configuration information includes: a remote management parameter configuration item and a logical ID parameter configuration item of the ACS system, the logical ID parameter configuration item includes a second logical ID; the second logical ID is used to indicate the second gateway and to indicate that the second gateway is a slave gateway of the first gateway; The second gateway sends a request message to the ACS system, where the request message includes the configuration information, for the ACS system to register and authenticate the second gateway according to the second logical ID and the configuration information received from the first gateway; The second gateway receives a response message from the ACS system, where the response message is used to indicate that the second gateway has been successfully registered and authenticated on the ACS system.

5. The method according to claim 4, characterized in that The second gateway sends a request message to the ACS system, including: The second gateway sends the request message to the ACS system through the first gateway; The second gateway receives a response message from the ACS system, including: The second gateway receives the response message sent by the ACS system through the first gateway.

6. The method according to claim 4 or 5, characterized in that Before the second gateway receives the configuration information from the first gateway, the method further includes: The second gateway sends a registration authentication request message to the first gateway; the registration authentication request message is used to request authentication with the first gateway; The second gateway receives a registration authentication confirmation message from the first gateway; the registration authentication confirmation message is used to indicate that the authentication between the second gateway and the first gateway is successful.

7. A gateway registration method, characterized in that: An automatic configuration server (ACS) system applied to a fiber-to-the-room (FTTR) network comprises: The ACS system authenticates the first gateway so that the first gateway obtains remote management parameter configuration items of the ACS system; The ACS system receives a second logical ID from the first gateway; the second logical ID is used to indicate a second gateway and to indicate that the second gateway is a slave gateway of the first gateway; The ACS system receives a request message from the second gateway; wherein the request message includes configuration information, the configuration information including: a remote management parameter configuration item and a logical ID parameter configuration item of the ACS system, the logical ID parameter configuration item including the second logical ID; The ACS system performs registration and authentication on the second gateway according to the second logical ID and the configuration information; After the registration authentication of the second gateway is passed, the ACS system sends a response message to the second gateway; wherein the response message is used to indicate that the registration authentication of the second gateway on the ACS system is successful.

8. The method according to claim 7, characterized in that The ACS system receives the request message from the second gateway, including: The ACS system receives the request message sent by the second gateway through the first gateway; The ACS system sends a response message to the second gateway, including: The ACS system sends the response message to the second gateway through the first gateway.

9. The method according to claim 7 or 8, characterized in that After the registration authentication of the second gateway is passed, the method further includes: The ACS system establishes a home network topology map according to the second logical ID, wherein the home network topology map includes a subordinate relationship between the first gateway and the second gateway; The ACS system manages the first gateway, and the management of the first gateway includes one or more of the following: querying downstream optical interface information, managing the number of downstream devices, and querying downstream device information; The ACS system manages the second gateway, and the management of the second gateway includes one or more of the following: reading gateway parameter information, configuring parameter information, updating software version, restoring factory settings, and restarting the device.

10. A gateway registration device, characterized in that: A first gateway applied to a fiber-to-the-room FTTR network, the first gateway serving as a master gateway connected to one or more second gateways serving as slave gateways, the device comprising an authentication module, a sending module, and a receiving module; The authentication module is used to authenticate with the automatic configuration server ACS system to obtain remote management parameter configuration items of the ACS system; The sending module is configured to send configuration information to the second gateway; wherein the configuration information includes: a remote management parameter configuration item and a logical ID parameter configuration item of the ACS system, the logical ID parameter configuration item including a second logical ID; the second logical ID is used to indicate the second gateway and to indicate that the second gateway is a slave gateway of the first gateway; The sending module is further configured to send the second logical ID to the ACS system; The receiving module is configured to receive a request message from the second gateway; The sending module is further configured to send the request message to the ACS system; wherein the request message includes the configuration information, and is used by the ACS system to register and authenticate the second gateway according to the second logical ID and the configuration information; The receiving module is further configured to receive a response message from the ACS system; The sending module is further configured to send the response message to the second gateway, where the response message is used to indicate that the second gateway has successfully registered and authenticated on the ACS system.

11. A gateway registration device, characterized in that: A second gateway used in a fiber-to-the-room FTTR network, the second gateway being connected as a slave gateway to a first gateway being a master gateway, the device comprising a receiving module and a transmitting module; The receiving module is configured to receive configuration information from the first gateway; wherein the configuration information includes: a remote management parameter configuration item and a logical ID parameter configuration item of an automatic configuration server ACS system, wherein the logical ID parameter configuration item includes a second logical ID; the second logical ID is used to indicate the second gateway and to indicate that the second gateway is a slave gateway of the first gateway; The sending module is configured to send a request message to the ACS system, wherein the request message includes the configuration information, and is configured for the ACS system to register and authenticate the second gateway according to the second logical ID and the configuration information received from the first gateway; The receiving module is further configured to receive a response message from the ACS system, where the response message is used to indicate that the second gateway has been successfully registered and authenticated on the ACS system.

12. A gateway registration device, characterized in that: An automatic configuration server (ACS) system for a fiber-to-the-room (FTTR) network includes an authentication module, a receiving module, a registration module, and a sending module. The authentication module is configured to authenticate with the first gateway so that the first gateway obtains the remote management parameter configuration items of the ACS system; The receiving module is configured to receive a second logical ID from the first gateway; the second logical ID is configured to indicate a second gateway and to indicate that the second gateway is a slave gateway of the first gateway; The receiving module is further configured to receive a request message from the second gateway; wherein the request message includes configuration information, the configuration information including: a remote management parameter configuration item and a logical ID parameter configuration item of the ACS system, the logical ID parameter configuration item including the second logical ID; The registration module is configured to register and authenticate the second gateway according to the second logical ID and the configuration information; The sending module is used to send a response message to the second gateway; wherein the response message is used to indicate that the second gateway has successfully registered and authenticated on the ACS system.

13. A gateway registration device, characterized in that: The gateway registration device includes: a processor and a memory; The memory stores instructions executable by the processor; When the processor is configured to execute the instructions, the gateway registration device implements the method according to any one of claims 1 to 9.

14. A computer-readable storage medium, characterized in that The computer-readable storage medium includes: computer software instructions; When the computer software instructions are executed in the gateway registration device, the gateway registration device is enabled to implement the method according to any one of claims 1 to 9.

15. A gateway registration system, characterized in that: Applied to a fiber-to-the-room FTTR network, the gateway registration system includes a first gateway, one or more second gateways, and an automatic configuration server ACS system; the first gateway serves as a master gateway and is connected to the one or more second gateways as slave gateways; Wherein, the first gateway comprises the gateway registration device according to claim 10; The second gateway comprises the gateway registration device according to claim 11; The ACS system includes the gateway registration device according to claim 12.

Citation Information

Patent Citations

  • Device, system and method for automatically configuring application terminal in family network

    CN101296203A

  • Method and system for communicating by using mobile terminal as slave gateway

    CN101895874A