WO2024045765A1 - Procédé de configuration de passerelle esclave, dispositif électronique et support de stockage lisible par ordinateur - Google Patents

Procédé de configuration de passerelle esclave, dispositif électronique et support de stockage lisible par ordinateur Download PDF

Info

Publication number
WO2024045765A1
WO2024045765A1 PCT/CN2023/100057 CN2023100057W WO2024045765A1 WO 2024045765 A1 WO2024045765 A1 WO 2024045765A1 CN 2023100057 W CN2023100057 W CN 2023100057W WO 2024045765 A1 WO2024045765 A1 WO 2024045765A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
configuration
slave
slave gateway
configuration file
Prior art date
Application number
PCT/CN2023/100057
Other languages
English (en)
Chinese (zh)
Inventor
邬立保
王阿琴
武云飞
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2024045765A1 publication Critical patent/WO2024045765A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles

Definitions

  • the present disclosure relates to the field of communications, and in particular, to a slave gateway configuration method, an electronic device, and a computer-readable storage medium.
  • FTTR Fiber to the Room
  • ACS Auto-Configuration Server
  • ITMS Integrated Terminal Management System
  • FTTR networking mode due to the large number of slave gateways, the master and slave gateways need to report 0boot when connecting for the first time, and slave gateway device status information needs to be reported periodically.
  • some ITMS specifications define the master gateway extended parameter LANDevice node LANPONInterfaceConfig . ⁇ i ⁇ To obtain the main gateway user-side optical port enablement, Passive Optical Network (PON, Passive Optical Network) port status, device information, logical identification (LOID) and other information, and actively report to the network management when the node status changes. And if the configuration and management of the gateway are all managed by the ITMS network management or cloud platform, it will have a certain impact on the processing load of the ITMS network management or cloud platform.
  • the present disclosure provides a slave gateway configuration method, an electronic device, and a computer-readable storage medium.
  • the present disclosure provides a slave gateway configuration method for a master gateway.
  • the slave gateway configuration method includes: configuring according to the current configuration parameters of the master gateway and the template corresponding to the slave gateway. configuration file to generate a slave gateway configuration file; when the slave gateway accesses the current primary gateway, deliver the slave gateway configuration file to the slave gateway.
  • the present disclosure also provides a slave gateway configuration method for the slave gateway.
  • the slave gateway configuration method includes: receiving a slave gateway configuration file issued by a master gateway currently connected to the slave gateway, wherein the slave gateway configuration The file includes a slave gateway configuration file generated based on the master gateway configuration parameters of the master gateway currently connected to the slave gateway and the template configuration file corresponding to the current slave gateway.
  • the present disclosure also provides an electronic device.
  • the electronic device includes: one or more processors; a memory on which one or more programs are stored. When the one or more programs are processed by the one or more The processor executes, causing the one or more processors to implement the slave gateway configuration method according to the present disclosure.
  • the present disclosure also provides a computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • the processor implements the slave gateway configuration method according to the present disclosure. .
  • Figure 1 is a flow chart of a slave gateway configuration method according to the present disclosure.
  • FIG. 2 is another flowchart of a slave gateway configuration method according to the present disclosure.
  • Figure 3 is a flow chart of a slave gateway configuration method according to the present disclosure.
  • Figure 4 is a flow chart of a slave gateway configuration method according to the present disclosure.
  • Figure 5 is a flow chart of a slave gateway configuration method according to the present disclosure.
  • Figure 6 is a flow chart of a slave gateway configuration method according to the present disclosure.
  • Figure 7 is a flow chart of a slave gateway configuration method according to the present disclosure.
  • Figure 8 is another flowchart of a slave gateway configuration method according to the present disclosure.
  • Figure 9 is another flowchart of a slave gateway configuration method according to the present disclosure.
  • Figure 10 is another flowchart of a slave gateway configuration method according to the present disclosure.
  • FIG 11 is another flowchart of a slave gateway configuration method according to the present disclosure.
  • Figure 12 is another flowchart of a slave gateway configuration method according to the present disclosure.
  • Figure 13 is another flowchart of a slave gateway configuration method according to the present disclosure.
  • Figure 14 is a schematic diagram of the traditional FTTR master and slave gateway configuration and management architecture.
  • Figure 15 is a schematic diagram of the FTTR master and slave gateway configuration file synchronization architecture according to the present disclosure.
  • Figure 16 is a flow chart of reporting file information in the MIB synchronization stage according to the present disclosure.
  • Figure 17 is a flowchart of querying file information after MIB synchronization according to the present disclosure.
  • Figure 18 is a normal flow chart for delivering a configuration file from a gateway according to the present disclosure.
  • Figure 19 is a flow chart of issuing exceptions from a gateway configuration file according to the present disclosure.
  • Figure 20 is a flow diagram for preflighting from a gateway configuration file in accordance with the present disclosure.
  • Figure 21 is a schematic diagram of a slave gateway XML configuration file format according to the present disclosure.
  • Figure 22 is a schematic diagram of a slave gateway JSON configuration file format according to the present disclosure.
  • Figure 23 is a schematic diagram of an electronic device according to the present disclosure.
  • Figure 24 is a schematic diagram of a computer-readable storage medium in accordance with the present disclosure.
  • the configurations of each slave gateway under the same master gateway are basically the same.
  • Configuration protocol (DHCP, Dynamic Host Configuration Protocol) address allocation, traffic forwarding control, WAN (Wide Area Network) connection configuration, interactive Internet TV (IPTV) business, wireless access and other parameter configurations.
  • DHCP Dynamic Host Configuration Protocol
  • IPTV interactive Internet TV
  • the configuration of the slave gateway is generally relatively simple, and most configurations can be synchronized directly from the main gateway, such as WIFI account passwords, etc. How to simplify the configuration management of the slave gateway to achieve plug-and-play from the slave gateway and reduce the processing load of the slave gateway on the ITMS network management or cloud platform requires an effective solution. In response to the above problems, for the FTTR comprehensive group How to simplify the configuration management of the slave gateway in the network scenario.
  • This disclosure provides a solution in which the master gateway directly issues the configuration file to the slave gateway. While simplifying the configuration management of the slave gateway, it also reduces the slave gateway's need for ITMS network management or The processing load of the cloud platform.
  • An embodiment of the present disclosure provides a slave gateway configuration method for a master gateway. As shown in Figure 1, the slave gateway configuration method includes the following steps S100 to S200.
  • step S100 a slave gateway configuration file is generated based on the configuration parameters of the current master gateway and the template configuration file corresponding to the slave gateway.
  • step S200 when the slave gateway accesses the current primary gateway, the slave gateway configuration file is delivered to the slave gateway.
  • the slave gateway configuration file can be generated based on the configuration parameters of the current master gateway.
  • a template configuration file in a pre-specified standard format is used as the basic template for all slave gateway configuration files.
  • the master gateway configuration parameters that need to be synchronized to the slave gateway are stored according to the format of the template configuration file and generated for the next step. Slave gateway configuration file sent to each slave gateway.
  • the template configuration file corresponding to the slave gateway includes configuration parameter templates respectively corresponding to each service of the slave gateway.
  • the slave gateways in a real network may be devices from many different manufacturers, and multiple different types of services are run on each slave gateway. Therefore, corresponding configuration parameter templates can be set for each slave gateway's device form and each service type.
  • the master gateway determines the configuration parameter template corresponding to each service based on the device form of the slave gateway and the various service types running on the slave gateway, obtains the template configuration file corresponding to the slave gateway, and combines it with the configuration of the master gateway itself parameters and the determined configuration template file to generate a slave gateway configuration file corresponding to the slave gateway.
  • the method before delivering the secondary gateway configuration file to the secondary gateway, the method further includes: obtaining the configuration parameters of the primary gateway through the service configuration issued by the network management or management platform to which the current primary gateway belongs.
  • the source of the master gateway configuration file is not limited.
  • the master gateway can automatically generate a slave gateway configuration file based on the business configuration issued by the current network management or management platform. You can also use the configuration file currently stored on the master gateway as the slave gateway configuration file.
  • the format of the generated configuration file is not limited. It can be a file encoding format such as Extensible Markup Language (XML, Extensible Markup Language) or JSON (JavaScript Object Notation) with a modular structure, which facilitates the addition of configuration parameters.
  • Deletion, assignment, modification, and other operations also facilitate subsequent direct distribution of the configuration file to the optical network unit through the optical network unit management and control interface (OMCI, ONU Management and Control Interface) or extended operations management and maintenance (OAM, Operations, Administration and Maintenance) protocol. from the gateway.
  • OMCI optical network unit management and control interface
  • OAM extended operations management and maintenance
  • the master gateway When accessing from the slave gateway, the preset LOID and password are used for the PON authentication process.
  • the master gateway that supports the Mini Optical Line Terminal (MiniOLT, Mini Optical Line Terminal) function can support Through physical layer operation management and maintenance (PLOAM, Physical Layer Operations, Administration and Maintenance) and OMCI management, the PON layer characteristics of the PON interface on the WAN side of the gateway are configured.
  • the gateway After the gateway is powered on, it can meet the basic Internet and IPTV business needs according to the default preconfiguration.
  • the basic configuration of the device includes: the default LOID and password registered to the main gateway PON port, the World Wide Web (WEB, World Wide Web) Login account password, wireless 2.4G and 5G wireless service set identifier (SSID, Service Set Identifier) name and key, each WAN connection working mode (bridge or routing, the default works in bridge mode), etc.
  • the slave gateway does not need to modify the configuration, and can automatically synchronize the ordinary user administrator password of the master device, and can automatically synchronize the master device Wi-Fi and other configurations.
  • the master gateway automatically generates the slave gateway XML or JSON configuration file based on the local configuration.
  • the slave gateway When the slave gateway is powered on and connected, it generates a Gigabit-Capable Passive optical network (GPON) Optical Network) or Ethernet Passive Optical Network (EPON, Ethernet Passive Optical Network) and other application scenarios, download through OMCI or extended OAM transparent channel transmission.
  • GPON Gigabit-Capable Passive optical network
  • EPON Ethernet Passive Optical Network
  • the instructions are displayed through the XML incremental configuration file, and the application programming interface (API, Application Program Interface) interface provided by the relevant business module is called after parsing from the gateway and takes effect synchronously in real time.
  • API Application Program Interface
  • the master gateway can achieve zero-configuration access after the slave gateway is powered on by synchronously delivering the slave gateway configuration file to the slave gateway. It no longer requires the ITMS network management to issue work orders or the cloud platform plug-in to issue configurations for management. It can achieve the advantages of plug and play.
  • the slave gateway configuration method further includes the following steps S211 to S212.
  • step S211 when the configuration parameters of the master gateway are changed, a slave gateway configuration file is regenerated based on the changed configuration parameters of the master gateway and the template configuration file corresponding to the slave gateway.
  • step S212 the regenerated slave gateway configuration file is delivered to the slave gateway corresponding to the changed configuration parameters.
  • the slave gateway since the slave gateway no longer updates the configuration file from the network management, but directly synchronizes the configuration file from the master gateway, when the user makes modifications to the configuration parameters of the current master gateway through the network management, or directly in the master gateway When some parameters are modified, or the parameters in the slave gateway configuration file are changed due to other reasons, the current master gateway needs to regenerate the changed slave gateway configuration file and actively synchronize the configuration with the slave gateway.
  • the master gateway Before the master gateway actively synchronizes the configuration to the slave gateway, it can first send an update instruction message to the slave gateway, and the slave gateway determines whether to synchronize the configuration based on the version information and verification information of the configuration file. If the secondary gateway determines that configuration synchronization is required, it sends a configuration file update request to the primary gateway. After receiving the update request, the master gateway starts to synchronize the changed slave gateway configuration file to the slave gateway.
  • the slave gateway configuration method further includes the following steps S221 to S222.
  • step S221 when the configuration parameters of the main gateway are changed, Generate an incremental configuration file for the slave gateway based on the changed configuration parameters of the master gateway and the template configuration file corresponding to the slave gateway, where the incremental configuration file is a modified configuration for the master gateway Parameter generated configuration fragment.
  • step S222 the incremental configuration file is delivered to the slave gateway connected to the current master gateway, so that the incremental configuration file is merged with the slave gateway configuration file stored on the slave gateway to form the changed From the gateway configuration file.
  • Changes in configuration parameters include operations such as adding, deleting, and modifying configuration parameters. Sometimes only a few parameters change. It would be a waste of network resources to regenerate the complete slave gateway configuration file every time and then synchronize the complete configuration file to all slave gateways. Therefore, in addition to generating a complete slave gateway configuration file based on the changed parameters, the master gateway can also use incremental configuration files to synchronize the configuration to the slave gateway in order to save resources and reduce the burden of file transfer on the network. For example, using modular file encoding formats such as XML and JSON, an incremental file only contains module content with parameter changes to achieve lightweight configuration synchronization. After receiving it from the gateway, only the parameters in the incremental configuration can be synchronously updated based on the existing configuration file, leaving other content unchanged.
  • the master gateway can first send an update instruction message to the slave gateway, and the slave gateway will determine whether to configure based on the version information and verification information of the configuration file. Synchronize. If the secondary gateway determines that configuration synchronization is required, it sends a configuration file update request to the primary gateway. After receiving the update request, the master gateway begins to deliver the incremental configuration file to the slave gateway.
  • the slave gateway configuration method further includes the following steps S231 to S232.
  • step S231 the slave gateway to be updated is determined according to the configuration update information of the slave gateway.
  • step S232 the slave gateway configuration file stored locally by the current master gateway is delivered to the slave gateway to be updated.
  • step S231 before determining the slave gateway to be updated according to the configuration update information of the slave gateway (ie, step S231), the following steps S233 to S234 are also included.
  • step S233 send a slave gateway to at least one slave gateway connected to the current master gateway.
  • Update check message for gateway configuration file
  • step S234 the configuration update information fed back by each slave gateway to the current master gateway in response to the update check message is received.
  • step S231 before determining the slave gateway to be updated according to the configuration update information of the slave gateway (ie, step S231), the following steps S235 to S236 are also included.
  • step S235 a configuration file query message is sent to the slave gateway connected to the current master gateway.
  • step S236 receive the configuration update information sent by the slave gateway for the configuration file query message.
  • determining the slave gateway to be updated according to the configuration update information of the slave gateway includes: parsing the configuration update information to obtain the version information of the slave gateway configuration file stored locally by the slave gateway; in the If the version information of the slave gateway configuration file stored on the slave gateway is different from the version information of the slave gateway configuration file stored locally on the current master gateway, the slave gateway is determined to be the slave gateway to be updated.
  • determining the slave gateway to be updated based on the configuration update information of the slave gateway includes: parsing the configuration update information, and obtaining the slave gateway stored in the slave gateway for verification. Hashcode of the configuration file integrity; if the hash code verification fails, the slave gateway is determined to be the slave gateway to be updated.
  • the slave gateway configuration file is delivered to the slave gateway through a privately defined channel of OMCI or a channel of extended OAM.
  • MIB Management Information Base
  • the main gateway will send an update check to all slave gateways registered with the current main gateway. According to Determine which slave gateway configuration files need to be synchronized from the version information fed back by the gateway.
  • the master gateway can also send a query (GET) message to the slave gateway through MIB audit (Audit) to obtain the version information, hashcode, time information, etc. of the configuration file stored on the slave gateway, and determine which Configuration files from the gateway need to be synchronized.
  • GET query
  • MIB audit MIB audit
  • the master gateway sends the version information containing the slave gateway configuration file to the slave gateway or the slave network When reporting the version information of the configuration file on the slave gateway to the master gateway, it can also send a Hashcode for verifying the integrity of the configuration file.
  • the master gateway checks the update status of the configuration file based on the "Hashcode" attribute value reported by the slave gateway. Based on the update status, it optionally initiates a configuration file delivery operation to the slave gateway.
  • GET message configuration file query message
  • delivering the secondary gateway configuration file to the secondary gateway further includes: in response to receiving a configuration file synchronization request from the secondary gateway, delivering the secondary gateway to the secondary gateway. Gateway configuration file.
  • step S200 the step of delivering the slave gateway configuration file to the slave gateway.
  • the slave gateway configuration file is delivered to the slave gateway through a privately defined channel of OMCI or a channel of extended OAM.
  • the various scenarios in which the master gateway delivers the slave gateway configuration file to the slave gateway can include the slave gateway configuration file sent by the master gateway when the slave gateway first accesses, or can include the master gateway configuration file when the master gateway configuration parameters change.
  • the changed slave gateway configuration file or incremental configuration file issued by the gateway can also include the slave gateway configuration file issued during the MIB synchronization or MIB audit phase. We will not list them one by one here. All the private gateway configuration files issued by the master gateway through OMCI Scenarios in which a defined channel or an extended OAM channel delivers a configuration file to a slave gateway fall within the protection scope of this disclosure.
  • the slave gateway can be an ONU
  • the master gateway can be an optical line terminal (OLT, Optical Line Terminal) or an ONU that supports the MiniOLT function.
  • OLT optical line terminal
  • the ONU is used as the slave gateway for illustration, but the present disclosure is not limited to the scenario of using the ONU as the slave gateway.
  • the default preconfiguration file is loaded from the gateway when it is powered on.
  • the default preconfiguration file presets the Internet bridge to implement basic Internet access and IPTV multicast services, and ensures that the slave gateway can register to the main gateway normally.
  • the master gateway saves the basic service XML or JSON default configuration file template of the slave gateway.
  • the XML or JSON file format content is defined according to the TR098 parameter specification and the internal DB storage parameters of each business module.
  • the master gateway After the master gateway is powered on, it reads and loads the slave gateway XML template configuration file. After the slave gateway is connected, it obtains the slave gateway's current configuration file version and last update time information, and confirms whether the slave gateway configuration file needs to be updated.
  • the main gateway checks the configuration file update.
  • the main gateway checks the configuration file update based on the "Hashcode" attribute value reported from the slave gateway, and optionally initiates a configuration file delivery operation. There are two options for reporting "Hashcode" from the gateway. One is during the MIB Upload stage, and the slave gateway reports it through the MIB Upload next response message; the other is that after the MIB audit is completed, the main gateway queries the slave gateway XML configuration file through the GET message. information.
  • the basic format of the XML file in the slave gateway is consistent with the default pre-configuration file of the master and slave gateway versions.
  • Figure 21 shows the basic format of the XML configuration file.
  • the basic content is as follows: Add the HashCode attribute to the ⁇ DB> tag, and the content is to perform the entire file
  • the value calculated by the MD5 digest algorithm is used to verify the integrity of the entire XML file content.
  • the CfgFile table only includes the field Version. Version represents the iteration of the configuration file. According to the Version, it is confirmed whether it is applicable to the current slave gateway. HashCode uses the MD5 digest algorithm. After the configuration file takes effect, it is used to save the hash value of the entire original configuration file received from the main gateway. After each subsequent restart, the content of this field is reported from the gateway to the main gateway to detect whether it needs to be updated. From the gateway configuration file.
  • the present disclosure also provides a slave gateway configuration method for the slave gateway.
  • the slave gateway configuration method includes the following steps S300.
  • step S300 receive the slave gateway configuration file issued by the master gateway currently connected to the slave gateway, wherein the slave gateway configuration file includes the master gateway configuration parameters based on the master gateway currently connected to the slave gateway and the configuration parameters related to the current slave gateway.
  • the gateway configuration file is generated from the template configuration file corresponding to the gateway.
  • the template configuration file corresponding to the slave gateway includes configuration parameter templates respectively corresponding to each service of the slave gateway.
  • the master gateway generates a slave gateway configuration file for the slave gateway registered in the current master gateway based on the service configuration of the current master gateway.
  • the master gateway will actively check for configuration updates, or query the configuration-related information of the slave gateway, determine the slave gateway to be updated, and indicate the slave gateway to be updated.
  • the slave gateway performs configuration synchronization; in other scenarios, such as powering on the slave gateway with an empty configuration, restarting the slave gateway, connecting to the network for the first time, etc., the slave gateway will also actively send a configuration synchronization request to the master gateway.
  • the slave gateway determines whether it is necessary to send a configuration synchronization request to the master gateway by comparing the version information of the configuration file currently stored on the slave gateway with the version information of the slave gateway configuration file generated by the master gateway. Different version information means different configuration files, and you need to perform the steps of synchronizing the slave gateway configuration file from the master gateway.
  • the slave gateway configuration method in the case that the current slave gateway has stored the slave gateway configuration file issued by the master gateway to which the current slave gateway is connected, the slave gateway configuration method also includes the following step S311 .
  • step S311 the slave gateway configuration file re-issued by the master gateway is received.
  • the slave gateway configuration method further includes the following steps S321 to S322.
  • step S321 the re-issued slave gateway configuration file is parsed to obtain an incremental configuration file.
  • the incremental configuration file is a configuration fragment generated by the master gateway for the changed master gateway configuration parameters.
  • step S322 the incremental slave gateway configuration file is merged with the slave gateway configuration file currently stored on the slave gateway to form a modified slave gateway configuration file.
  • the secondary gateway configuration method further includes the following step S331.
  • step S331 configuration update information is sent to the master gateway to represent the version of the current slave gateway.
  • step S332 is also included.
  • step S332 in response to the file update check message of the main gateway, configuration update information for the file update check message is fed back to the main gateway.
  • step S333 is also included.
  • step S333 in response to the configuration file query message of the main gateway, configuration update information for the configuration file query message will be sent to the main gateway.
  • the configuration update information includes: version information of the slave gateway configuration file stored on the slave gateway, and/or a hash code used to verify the integrity of the slave gateway configuration file stored on the slave gateway.
  • the master gateway GETs to the slave network in MIB audit If the configuration file version is inconsistent, etc., the master gateway will actively initiate configuration synchronization with the slave gateway.
  • the slave gateway will receive an update instruction from the master gateway to update the configuration file, and then perform the configuration synchronization steps.
  • the main gateway will first send an update check message to collect the version information fed back from the slave gateway and the hash code corresponding to the current configuration file.
  • the main gateway will determine whether to continue performing configuration synchronization. step.
  • step 300 after the step of receiving the slave gateway configuration file issued by the primary gateway to which the slave gateway is currently connected (ie, step 300), the following steps S341 to S343 are also included.
  • step S341 the slave gateway configuration file issued by the master gateway is verified.
  • step S342 if the verification fails, a download failure response is sent to the main gateway.
  • step S343 if the verification is successful, the relevant business module is called to configure parameters.
  • verifying the slave gateway configuration file issued by the master gateway includes at least one of the following verifications: file legality verification, time verification, download integrity Verification, content validity verification, configuration validity verification.
  • step S343 if the verification is successful, before the step of calling the relevant business module to configure parameters (ie, step S343), it also includes: performing the verification on the slave gateway configuration file issued by the master gateway. Configuration check.
  • the configuration check includes at least one of the following checks: file basic element check, file integrity check, and parameter value legality check.
  • the basic format of the XML file in the slave gateway is consistent with the default pre-configuration file of the master and slave gateway versions.
  • Figure 21 shows the basic format of the XML configuration file.
  • the basic content is as follows: Add the HashCode attribute in the ⁇ DB> tag, and the content is to perform the entire file
  • the value calculated by the MD5 digest algorithm is used to verify the integrity of the entire XML file content.
  • the CfgFile table only includes the field Version, which represents the configuration file. According to the iteration of the software, the product confirms whether it is suitable for the current gateway based on the Version.
  • the HashCode in the above XML configuration file header is generated based on the entire file using the MD5 algorithm. After the MD5 value is calculated, it is backfilled into the HashCode field. That is, the HashCode is the secret key of the MD5 algorithm.
  • the processing of XML configuration files from inside the gateway ONU is mainly divided into two processes: verification and configuration. During the verification phase, if a parameter fails to pass the verification, failure will be returned immediately. After all items have been successfully verified, the configuration phase will be entered. If any parameter configuration fails during the configuration phase, continue with subsequent configuration items. Layered verification of XML configuration files includes the following aspects:
  • the main gateway calculates the CRC based on the entire file, receives it from the gateway and calculates the comparison. This check is optional and its function is close to the MD5 function;
  • Configuration validity verification Pre-check the parameter content one by one, mainly checking whether the table is correct and whether the fields and field values are correct.
  • Parsing and configuring the XML configuration file includes calling the API interface provided by each module to configure parameters, so that the business configuration can take effect immediately.
  • Configuration checks are mainly divided into basic element checks of XML files, complete file integrity checks, and parameter value legality checks, among which:
  • the XML configuration file When changes are found in the master gateway configuration, if a slave gateway is involved, the XML configuration file will be updated synchronously and notified to be re-issued. The slave gateway will check the correctness and completeness of the content of the configuration file.
  • the slave gateway configuration file issued by the master gateway is received through a privately defined channel of OMCI or an extended OAM channel.
  • the file scenario can include the slave gateway configuration file issued by the master gateway when the slave gateway first accesses, or the changed slave gateway configuration file issued by the master gateway when the master gateway configuration parameters change, or incremental configuration. Files can also include slave gateway configuration files issued during the MIB synchronization or MIB audit phase. We will not list them all here. All master gateways issue configuration files to the slave gateway through the privately defined channel of OMCI or the extended OAM channel. All scenarios fall within the protection scope of this disclosure.
  • the slave gateway configuration method further includes: when the slave gateway detects that a synchronization condition is met, sending a configuration file synchronization request to the master gateway, wherein the synchronization condition includes at least one of the following conditions: Types: Power on from the gateway, restart from the gateway, newly join the network from the gateway, and only have the default configuration from the gateway.
  • the slave gateway can also actively request configuration synchronization.
  • the slave gateway defaults to zero configuration (it can also have a default pre-configuration)
  • the master gateway will deliver the gateway configuration file to the slave gateway, and the slave gateway configuration file will take effect immediately on the slave gateway, thereby realizing immediate deployment of the slave gateway. Plug and play.
  • One of the purposes of this disclosure is to simplify the process of ITMS network management to manage the slave gateway due to the complicated configuration and management of the slave gateway.
  • the slave gateway is no longer managed through the ITMS network management.
  • the slave gateway does not issue work orders separately, and the master gateway directly synchronizes key configurations (or Delivered) to the slave gateway, and the slave gateway implements plug-and-play.
  • the main advantages of this disclosed solution include: simplifying the configuration process of the slave gateway, enabling plug-and-play, and no longer requiring ITMS network management or cloud platforms to directly configure and manage the slave gateway, which is automatically generated by the master gateway based on the current network configuration. From the gateway's XML configuration file, load the XML file or incremental XML file from the gateway to meet business validation requirements.
  • FIG 14 is a schematic diagram of the configuration and management architecture of the FTTR master and slave gateways.
  • the configuration management of the master and slave gateways is still controlled by the ACS network management and cloud platform. For example, when accessing from a gateway, the master gateway needs to perform device platform authentication on behalf of the slave gateway. The master gateway controls the slave gateway based on the authentication results of the gateway management platform.
  • the configuration management of the above-mentioned slave gateway is basically the same as that of the master gateway, which puts a heavy load on the ACS network management and cloud platform.
  • the slave gateway In the existing master and slave gateway networking mode, the slave gateway generally works in bridge forwarding mode, and the network configuration is relatively simple.
  • the configuration parameters of the slave gateway depend on the master gateway. In fact, the configuration of the slave gateway can be directly downloaded through the master gateway. Send for synchronization.
  • This disclosure optimizes the configuration management architecture of the FTTR master and slave gateways.
  • FIG. 15 is a schematic diagram of the master and slave gateway configuration file synchronization framework according to the present disclosure.
  • This disclosure proposes a method for synchronizing the master and slave gateway configurations.
  • the master gateway (Master ONU) presets the slave gateway XML template configuration file, and the slave gateway (Slave ONU) successfully registers with the master gateway through LOID or serial number (SN, Serial Number). Afterwards, the slave gateway does not need to modify the configuration and can automatically synchronize the relevant configuration of the master device.
  • the slave gateway device is powered on and connected to the master gateway.
  • the master gateway can automatically generate the slave gateway XML configuration file according to the local configuration. When the slave gateway is powered on and connected, it is transmitted and downloaded through OMCI or extended OAM transparent channels.
  • the instructions are displayed through the XML incremental configuration file, and the API interface provided by the relevant business module is called after parsing from the gateway to take effect synchronously in real time.
  • the slave gateway defaults to zero configuration (it can also have default pre-configuration)
  • the master gateway delivers the XML configuration file to the slave gateway and it takes effect immediately.
  • FTTR networking When FTTR networking is activated, first save the basic template cfg.xml file to the main gateway. For example, pre-configure an Internet transparent transmission bridge and wireless service set identifier (SSID, Service Set Identifier) and key-related configurations as the default template configuration file to ensure that basic services can be implemented after accessing from the gateway.
  • SSID Internet transparent transmission bridge and wireless service set identifier
  • key-related configurations as the default template configuration file to ensure that basic services can be implemented after accessing from the gateway.
  • the gateway After the gateway is powered on or restored to factory settings, it automatically interacts with the main gateway to download the XML configuration file.
  • the ONU will call the relevant business module to reload the configuration and take effect immediately without restarting the ONU to reduce the impact of configuration upgrades on the user experience. Impact.
  • the configuration file can be viewed and modified through the local WEB page of the main gateway.
  • the main gateway When receiving relevant business configuration parameter change messages issued by ITMS network management or cloud platform, the slave gateway cfg.xml file will be dynamically and synchronously updated, and the cfg.xml configuration will be automatically delivered to multiple slave gateway ONUs.
  • the ONU must re-download cfg.xml.
  • the content in the above XML file is privately defined based on specific business scenarios and functional requirements, including basic data service forwarding configuration on the WAN side and LAN side. For new functional services, the XML file format needs to be expanded and adjusted simultaneously.
  • the XML file can also be pre-configured according to specific customization requirements.
  • the content of the XML file can be full configuration or incremental configuration.
  • Figure 16 is a flow chart of reporting file time information in the MIB synchronization stage according to the present disclosure, including the following steps 201 to 204.
  • step 201 the main gateway actively requests a file update check (MIB Upload next) during the MIB synchronization phase.
  • step 202 the gateway reports the MIB Upload next response message through the MIB Upload next response message, which includes: the version information FileVersion of the configuration file (xml cfg), and the hash code (HashCode) corresponding to the configuration file.
  • step 203 the master gateway checks whether the file needs to be updated.
  • step 204 if the XML configuration file needs to be updated, download the configuration file.
  • Figure 17 is a flow chart of querying file time information after MIB synchronization according to the present disclosure, including the following steps 301 to 304.
  • step 301 the master and slave gateway MIB audits are synchronized.
  • step 302 the master gateway actively queries (GET) the slave gateway XML file time information.
  • step 303 the master gateway receives the slave gateway query response (GET response) and checks whether the file needs to be updated.
  • GET response the slave gateway query response
  • step 304 if the XML configuration file needs to be updated, download the configuration file. load.
  • Figure 18 is a normal flow chart for delivering a configuration file from a gateway according to the present disclosure, including the following steps 401 to 406.
  • step 401 the master gateway requests to obtain the current configuration file version and update time (UpdateTime) of the slave gateway.
  • step 402 after receiving the request from the gateway, fill in relevant parameters and respond.
  • step 404 after receiving the download configuration file end message (EndDownLoad) from the gateway, the Cyclic Redundancy Check (CRC, Cyclic Redundancy Check) is checked to verify legality and integrity, and to verify the update time.
  • CRC Cyclic Redundancy Check
  • each relevant business module is called from the gateway for configuration, and the local XML file version and update time are updated.
  • Figure 19 is a flow chart of delivering an exception from a gateway configuration file according to the present disclosure, including the following steps 501 to 505.
  • Steps 501 to 504 are the same as steps 301 to 304 in Figure 17 and will not be described again.
  • Figure 20 is a flow chart of preflighting the gateway XML configuration file according to the present disclosure, including the following steps 601 to 605.
  • step 601 the XML configuration file download end event is received from the gateway, and the XML configuration file version and update time are checked and compared. If no update is required, a download failure of the main gateway that supports the MiniOLT function is responded to; if an update is required, proceed to step 602 as follows. .
  • step 602 calculate and verify the CRC. If the verification fails, respond to the main gateway that the MiniOLT download failed; if the verification succeeds, proceed to the following step 603.
  • step 603 calculate and verify the MD5. If the verification fails, respond to the main gateway that the MiniOLT download failed; if the verification succeeds, proceed to the following step 604.
  • each parameter field is checked table by table in a loop. If the intermediate verification fails, respond to the main gateway that the MiniOLT download failed; if the verification is successful, continue to load other entries.
  • step 605 in response to the successful download of MiniOLT from the main gateway, the relevant parameter nodes are parsed and the original TR069 related parameter API is called for service distribution to ensure that the service takes effect simultaneously and in real time.
  • Figure 21 is a schematic diagram of the format of the secondary gateway XML configuration file according to an embodiment of the present disclosure.
  • the format definition of this XML file can refer to the TR098 standard specification.
  • the specific parameter DB storage format of the WAN side or LAN side entity object can be redefined according to this specification. , such as InternetGatewayDevice.WANDevice. ⁇ i ⁇ .
  • WANConnectionDevice.XXX parameter configuration can be converted into each parameter item in the DB Table table WANC.
  • the configuration file can be delivered from the complete set of gateway service XML configuration files or incremental XML configuration parameter sets.
  • FIG 22 is a schematic diagram of the slave gateway JSON configuration file format according to an embodiment of the present disclosure.
  • the format definition of the JSON file is organized according to the key/value format of the JSON file standard, and parameter names and parameters are defined according to the requirements of each business object entity. value content.
  • the present disclosure discloses a method for FTTR master and slave gateways to synchronize business data through configuration files. This method can effectively simplify the configuration management of the slave gateway and realize plug-and-play of the slave gateway.
  • the master gateway can also act as the ITMS network management role and issue configurations to the slave gateways through TR069 work orders.
  • An embodiment of the present disclosure also provides an electronic device, as shown in Figure 23, which includes: one or more processors 701; and a memory 702, on which one or more programs are stored.
  • processors 701 When one or more programs are processed by a Or multiple processors execute, so that one or more processors implement the slave gateway configuration method according to various embodiments of the present disclosure.
  • the electronic device may also include one or more I/O interfaces 703, connected between the processor and the memory, and configured to implement information exchange between the processor and the memory.
  • the processor 701 is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.; the memory 702 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically such as SDRAM). , DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH); the I/O interface (read-write interface) 703 is connected between the processor 701 and the memory 702, and can Implement information interaction between the processor 701 and the memory 702, which includes but is not limited to a data bus (Bus), etc.
  • RAM random access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • FLASH flash memory
  • the I/O interface (read-write interface) 703 is connected between the processor 701 and the memory 702, and can Implement information interaction between the processor 701 and the memory 702, which includes but is not limited to a data bus (Bus), etc.
  • processor 701, memory 702, and I/O interface 703 are connected to each other and, in turn, to other components of the computing device via bus 704.
  • Embodiments of the present disclosure also provide a computer-readable storage medium. As shown in Figure 24, a computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, the slave gateway configuration method according to various embodiments of the present disclosure is implemented. .
  • this disclosure proposes a method for the FTTR master gateway to directly synchronize configuration files with the slave gateway to achieve business data synchronization.
  • the master gateway automatically generates a slave gateway configuration file based on the configuration information delivered to the current master gateway by the ITMS network management or cloud platform, and subsequently delivers the configuration file directly to the slave gateway through OCMI or extended OAM transparent channels.
  • This method no longer passes ITMS network management can effectively simplify the configuration and management process of the slave gateway, allowing zero-configuration access from the slave gateway and realizing plug-and-play from the slave gateway. While simplifying the configuration management of the slave gateway, it also reduces the processing load of the slave gateway on the ITMS network management or cloud platform.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may consist of several physical components. Components execute cooperatively. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit . Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
  • computer storage media includes volatile and nonvolatile media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. removable, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disk (DVD) or other optical disk storage, magnetic cassettes, tapes, disk storage or other magnetic storage devices, or may Any other medium used to store the desired information and that can be accessed by a computer.
  • communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente divulgation concerne un procédé de configuration de passerelle esclave, un dispositif électronique et un support de stockage lisible par ordinateur. Le procédé de configuration de passerelle esclave consiste à : générer un fichier de configuration de passerelle esclave selon un paramètre de configuration de la passerelle maître actuelle et un fichier de configuration de modèle qui correspond à une passerelle esclave; et émettre le fichier de configuration de passerelle esclave vers la passerelle esclave lorsque la passerelle esclave accède à la passerelle maître actuelle.
PCT/CN2023/100057 2022-08-30 2023-06-14 Procédé de configuration de passerelle esclave, dispositif électronique et support de stockage lisible par ordinateur WO2024045765A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211055723.2A CN117675555A (zh) 2022-08-30 2022-08-30 从网关配置方法、电子设备和计算机可读存储介质
CN202211055723.2 2022-08-30

Publications (1)

Publication Number Publication Date
WO2024045765A1 true WO2024045765A1 (fr) 2024-03-07

Family

ID=90079435

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/100057 WO2024045765A1 (fr) 2022-08-30 2023-06-14 Procédé de configuration de passerelle esclave, dispositif électronique et support de stockage lisible par ordinateur

Country Status (2)

Country Link
CN (1) CN117675555A (fr)
WO (1) WO2024045765A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117880068A (zh) * 2024-03-11 2024-04-12 四川天邑康和通信股份有限公司 基于fttr的主从网关设备同步方法、装置、设备及介质
CN117880372A (zh) * 2024-03-12 2024-04-12 四川天邑康和通信股份有限公司 Fttr系统的设备访问控制方法、网关设备及网关分布式系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103124240A (zh) * 2013-02-07 2013-05-29 北京华为数字技术有限公司 网关配置方法、网关设备及网络系统
CN103167543A (zh) * 2011-12-19 2013-06-19 中国科学院沈阳自动化研究所 一种基于wia网络的冗余网关
CN103973476A (zh) * 2013-02-06 2014-08-06 上海杰之能信息科技有限公司 网关、网关热备份系统及方法
US20180006880A1 (en) * 2016-06-29 2018-01-04 Nicira, Inc. Ranking of Gateways in Cluster
CN111934912A (zh) * 2020-07-15 2020-11-13 浙江中控技术股份有限公司 双主机隔离网关的热备冗余系统及控制方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103167543A (zh) * 2011-12-19 2013-06-19 中国科学院沈阳自动化研究所 一种基于wia网络的冗余网关
CN103973476A (zh) * 2013-02-06 2014-08-06 上海杰之能信息科技有限公司 网关、网关热备份系统及方法
CN103124240A (zh) * 2013-02-07 2013-05-29 北京华为数字技术有限公司 网关配置方法、网关设备及网络系统
US20180006880A1 (en) * 2016-06-29 2018-01-04 Nicira, Inc. Ranking of Gateways in Cluster
CN111934912A (zh) * 2020-07-15 2020-11-13 浙江中控技术股份有限公司 双主机隔离网关的热备冗余系统及控制方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117880068A (zh) * 2024-03-11 2024-04-12 四川天邑康和通信股份有限公司 基于fttr的主从网关设备同步方法、装置、设备及介质
CN117880372A (zh) * 2024-03-12 2024-04-12 四川天邑康和通信股份有限公司 Fttr系统的设备访问控制方法、网关设备及网关分布式系统
CN117880372B (zh) * 2024-03-12 2024-05-14 四川天邑康和通信股份有限公司 Fttr系统的设备访问控制方法、网关设备及网关分布式系统

Also Published As

Publication number Publication date
CN117675555A (zh) 2024-03-08

Similar Documents

Publication Publication Date Title
WO2024045765A1 (fr) Procédé de configuration de passerelle esclave, dispositif électronique et support de stockage lisible par ordinateur
WO2020140667A1 (fr) Système et procédé de gestion de nœud de chaîne de blocs de consortium
US11943376B1 (en) Template based credential provisioning
US7233975B1 (en) Private configuration of network devices
CN103297529B (zh) 基于时间戳的树型结构数据同步方法
CN102006334B (zh) 安装软件组件的方法、系统及装置
US7376719B1 (en) Automatic generation of configuration data using implementation-specific configuration policies
US8326953B2 (en) Configuration management method and system for customer premises equipment
US7558835B1 (en) Application of a configuration patch to a network device
US7865578B1 (en) Generation of a configuration patch for network devices
CN111404924B (zh) 集群系统的安全管控方法、装置、设备及存储介质
US20150305008A1 (en) Method and apparatus for updating information regarding specific resource in wireless communication system
WO2011137793A1 (fr) Procédé, appareil et système de réseau pour effectuer une mise à jour à distance de dispositifs zigbee
US20190286813A1 (en) Autonomous secrets management for a temporary shared access signature service
WO2019184775A1 (fr) Procédé et dispositif de stockage de données de gestion et support d'informations
WO2011082684A1 (fr) Procédé et appareil de configuration de données
CN111628886A (zh) 私有云环境下组建区块链网络的方法、装置、计算机设备
US7483965B1 (en) Generation of a configuration patch for network devices
KR102558266B1 (ko) 데이터 수집 방법, 장치, 디바이스 및 컴퓨터가 판독 가능한 저장 매체
CN105635218A (zh) 软件中心系统
CN110365524B (zh) 服务器节点固件的镜像升级方法及系统
WO2020010906A1 (fr) Procédé et dispositif d'installation par lots d'un système d'exploitation (os), et dispositif de réseau
WO2008151571A1 (fr) Procédé, système, client dm et serveur dm pour l'installation d'un composant logiciel
WO2016124075A1 (fr) Procédé et dispositif de commande de mode de gestion d'unité de réseau optique dans un réseau optique passif
WO2018036521A1 (fr) Procédé, appareil et système d'ajustement de ressource

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23858804

Country of ref document: EP

Kind code of ref document: A1