WO2005046128A1

WO2005046128A1 - A method of managing and maintaining in the next generation network terminal

Info

Publication number: WO2005046128A1
Application number: PCT/CN2004/001267
Authority: WO
Inventors: Qiang Wie; Feiguang Jin; Bing Luo
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2003-11-11
Filing date: 2004-11-08
Publication date: 2005-05-19

Abstract

The invention relates to a method of managing and maintaining in the next generation network terminal. The method comprises: step A: incubating the next generation network terminal (NGN), and synchronizing at least the incubation information achieved by the incubation with soft switch; step B: the NGN terminal accessing the network by use of the said incubation information, determining whether the program files currently used by the NGN terminal need to be upgraded, if so, downloading new program files and making an upgrade; and determining whether the configurable files on the NGN terminal need to be upgraded, if so, downloading new configurable files and making an upgrade; step C: the NGN terminal logging in soft switch, using soft switch after achieving authentication. The method achieves various courses in managing and maintaining on the whole. It doesn't need people to participate in the course of managing and maintaining, with the advantages of high efficiency, low error rate, good secrecy, low requirement to maintainers, and it can adapt the extending need of large-scale NGN terminals.

Description

Operation and maintenance method of next generation network terminal

Technical field

The present invention belongs to the technical field of Next Generation Network (NGN), and particularly relates to a method for operating and maintaining a next generation network terminal. Background of the invention

With the rapid development and popularization of NGN technology, the use of NGN terminals is increasing. To enable a large number of NGN terminals in the network to use various services normally, it is necessary to operate and maintain the NGN terminals.

The operation and maintenance of NGN terminals include: incubation of NGN terminals, service provisioning of NGN terminals, automatic upgrade of NGN terminals, automatic configuration of NGN terminals, and authentication of NGN terminals; the following describes these contents included in operation and maintenance respectively :

1. The incubation of NGN terminals refers to: before the NGN terminal equipment is put into use, the basic data configuration is completed on the NGN terminal equipment;

In the NGN network, there are a large number of NGN terminal equipment, such as integrated access equipment (IAD), video terminals, and intelligent terminals. In order to ensure the normal use of NGN terminal equipment in the network, it is necessary to These NGN terminal equipment are incubated to complete basic data configuration, so that users of NGN do not need to configure NGN terminal equipment before using the NGN terminal. The configured data includes at least:

Terminal identification code (TID). This TID is used to distinguish each NGN terminal. Each NGN terminal should be configured to have a different TID, and the TID of each NGN terminal device is the globally unique TID, so the TID is used to distinguish each NGN terminal equipment;

Key, which is used for the authentication process of the NGN terminal, Determine whether the NGN terminal equipment is entitled to use related services;

During the incubation process, the following data can be further configured:

A method for obtaining an IP address of an NGN terminal device, by which a dynamic IP address assigned to the NGN device can be obtained automatically; or a static IP address can also be assigned to the NGN terminal device;

If an integrated access device management system (IADMS) exists in the network, you need to configure the domain name of the IADMS by incubation so that NGN terminal devices can use the domain name to issue services to the IADMS;

2. The service provision of NGN terminals refers to: configuring the necessary data for NGN terminal operation to the softswitch; where, if there is an IADMS in the network, it is also necessary to configure these necessary data to the IADMS, the required data includes Data configured by the NGN terminal incubation process;

3. The automatic upgrade process of the NGN terminal refers to: determining whether the program version of the NGN terminal is lower than the program version provided by the server, and if so, automatically upgrading the program version; 4. The automatic configuration of the NGN terminal refers to: NGN terminal The device uses parameters obtained during the incubation process, downloads a configuration file from the server, and uses the configuration file to automatically complete data configuration;

V. NGN terminal authentication refers to: NGN terminal equipment registers with IADMS and softswitch to complete authentication; among them, the relevant content of registration and authentication can refer to the industry standard "Media Gateway Interworking Specification".

In the prior art, the above-mentioned operation and maintenance process of NGN terminal equipment is manually completed. Although this method can realize the operation and maintenance of NGN terminal equipment, it has the following disadvantages:

1. In the prior art, the overall lack of overall consideration for the operation and maintenance of NGN terminal equipment makes the account opening and incubation link, service issuance link, deployment configuration link of NGN terminal equipment, The upgrade and maintenance link and the access authentication link are disconnected from each other, so that it cannot meet the needs of large-scale distribution of NGN terminal equipment;

2. In the operation and maintenance process, the various links are disconnected from each other, so the safety in the operation and maintenance process is low;

3. Operation and maintenance are performed manually, which is relatively inefficient and prone to errors. In addition, since each NGN terminal device requires operation and maintenance, the workload of manual operation and maintenance is huge, which is not conducive to the rapid implementation of NGN terminals. Large-scale distribution

4. Due to the large variety of NGN terminal equipment, and the different operation and maintenance for different types of NGN terminal equipment, the manual maintenance of operation and maintenance requires higher maintenance personnel, which increases the NGN terminal equipment. Difficulty in realizing operation and maintenance; In addition, because maintenance personnel perform operation and maintenance, it is inevitable that there may be leakage of operation and maintenance data, which may cause corresponding losses. Summary of the invention

In view of this, the main object of the present invention is to provide an operation and maintenance method for NGN terminal equipment, which combines various links in operation and maintenance to implement the operation and maintenance process as a whole. During the operation and maintenance process, no maintenance personnel are required to participate. It can efficiently and reliably implement operation and maintenance, thereby meeting the needs of large-scale distribution of NGN terminals.

To achieve the above objective, the present invention provides an operation and maintenance method for a next-generation network terminal, which method includes:

Step A: Incubate the Next Generation Network (NGN) terminal, and synchronize the incubation information obtained from the incubation to the soft exchange;

Step B: The NGN terminal uses the incubation information to access the network to determine whether the program file currently used by the NGN terminal needs to be upgraded, and if so, downloads a new program file and upgrades; and determines whether the configuration file on the NGN terminal requires Upgrade, if yes, download New configuration file and upgrade;

Step C: The NGN terminal uses the incubation information to register services with the softswitch at least. After the authentication in the service registration is passed, the program file and the configuration file are used to implement the softswitch service.

Wherein, if the network includes an NGN terminal incubator, incubating the NGN terminal described in step A includes:

Step A1: pre-configure the IP address of the NGN terminal and the IP address of the NGN terminal incubator;

Step A2: According to the pre-configuration performed in step A1, the NGN terminal obtains its own IP address and the IP address of the NGN terminal incubator;

Step A3: The NGN terminal sends a management registration request to the NGN terminal incubator according to the obtained IP address of the NGN terminal incubator. The NGN terminal incubator obtains related information of the NGN terminal, and generates at least a terminal identification code (TID) and a secret based on the related information. Incubation information including keys;

Step A4: The NGN terminal incubator transmits and writes incubation information including at least a TID and a key to the NGN terminal.

Step A1 includes:

Pre-configure the NGN terminal IP address acquisition method, and pre-configure the default domain name of the Integrated Access Device Management System (I ADMS) on the NGN terminal;

Step A2 includes:

Obtain the IP address of the NGN terminal according to the pre-configured IP address acquisition method. The NGN terminal sends a DNS domain name resolution request to the DNS server. The request includes the pre-configured IADMS default domain name. The DNS server resolves the default domain name to the NGN terminal. The IP address of the incubator is returned to the NGN terminal.

Step A1 includes: In the DHCP protocol, define OPTION: the DHCP server configures the IP address of the incubator to the NGN terminal; and pre-configures the method of obtaining the IP address of the NGN terminal;

Step A2 includes:

The IP address of the NGN terminal is obtained according to a pre-configured IP address acquisition method; the DHCP protocol configures the IP address of the incubator to the NGN terminal by the DHCP server according to a preset OPTION.

The method for obtaining the IP address of the pre-configured NGN terminal described in step A1 is:

The uplink NGN terminal of ETH is configured to obtain the IP address of the NGN terminal through DHCP; obtaining the IP address of the NGN terminal described in step A2 is: obtaining the IP address through DHCP;

Alternatively, the method for obtaining a pre-configured NGN terminal IP address as described in step A1 is: For an xDSL uplink NGN terminal, configuring the NGN terminal to obtain an IP address through PPPoE; obtaining the IP address of the NGN terminal as described in step A2 is: through PPPoE Get the IP address.

Wherein, generating the incubation information by the NGN terminal incubator in step A3 includes: the NGN terminal incubator queries the NGN terminal for related information, where the related information includes: an equipment identifier (EID), a MAC address, an IP address, and a port number, and Generate TID and key based on EID, port number, MAC address and IP address.

Wherein, before generating the TID and the key in step A3, the method further includes:

Determine whether the incubation switch is on, and if so, perform the step of generating incubation information; otherwise, terminate the incubation process.

Step A1 further includes:

Step A11: Perform the configuration on modifying the default password of the TID and the key, and the NGN terminal obtains the default password of modifying the TID and the key according to the configuration; In step A3, the NGN terminal incubator obtaining related information of the NGN terminal further includes: the NGN terminal incubator obtaining the default password of the NGN terminal to modify the TID and key; the generating incubation information further includes: generating a modified TID and A new key password; between steps A4 and A3, the method further includes:

The NGN terminal incubator sends the modified TID and key default password and the modified TID and key new password to the NGN terminal. The NGN terminal determines whether the transmitted default password is consistent with the default password configured on the NGN terminal. If yes, perform step A4, and further replace the default password with a new password; otherwise, refuse to hatch.

The step A11 includes:

The default password for changing the TID and key is configured on the NGN terminal in advance, and the NGN terminal obtains the default password for changing the TID and key directly from itself according to the configuration.

The step A11 includes:

In the DHCP protocol, OPTION is defined in advance: the DHCP server configures and changes the default password of the TID and the key to the NGN terminal; according to the definition of the OPTION, the DHCP server configures and changes the default password of the TID. And the key to the NGN terminal.

Wherein, incubating the NGN terminal described in step A includes:

The EID, device type, port number, and manufacturer and model of the NGN terminal are entered into the incubator of the NGN terminal. The incubator of the NGN terminal generates incubation information including the TID and the key based on the entered information;

And, writing the incubation information into an NGN terminal.

Before writing the incubation information to the NGN terminal, the method further includes: transmitting a key to the NGN terminal, the NGN terminal determines whether the key is the same as the saved default key, and if the key is the same, executing the incubation information Steps of writing NGN terminal, otherwise refuse to write incubation information.

The incubation information further includes a domain name of the IADMS. In step A, the Synchronize hatching information to IADMS in one step.

Wherein, incubating the NGN terminal described in step A includes:

Step D1: Generate a configuration file according to the MAC address and port information of the NGN terminal, and save the configuration file in the server, where the configuration file includes at least a TID and a key;

Step D2: The NGN terminal obtains the server address where the configuration file is saved; and, 'The NGN terminal obtains the file name of the configuration file and the loading directory in the server;

Step D3: The NGN terminal obtains the configuration file from the server according to the server address, the configuration file file name, and the loading directory in the server, and saves the incubation information including the TID and the key in the configuration file in the NGN terminal.

The default domain name of the server, the file name of the configuration file, and the loading directory in the server are loaded in advance on the NGN terminal. Step D2 includes:

The NGN terminal sends the pre-configured default domain name of the server to the DNS server. After receiving the default domain name, the DNS server resolves the domain name to the IP address of the server, and then returns the IP address to the NGN terminal. Get the file name of the configuration file on itself and the loading directory on the server.

The siaddr field in the DHCP protocol is defined in advance, and the IP address of the TFTP / FTP server that stores the configuration file is provided by the DHCP server to the NGN terminal; and the OPTION in the DHCP protocol is defined in advance, and the configuration in which the configuration file is provided by the DHCP server to the NGN terminal is configured. Name and loading directory on the server;

Step D2 includes:

According to the siaddr in the DHCP protocol, the DHCP server provides the IP address of the TFTP / FTP server with the configuration file to the NGN terminal; and, through the definition of OPTION in the DHCP protocol, the DHCP server provides the name and Loading directories in the server. Wherein, if the network includes an IADMS, synchronizing the incubation information to the soft exchange as described in step A further includes:

Sync incubation information to the IADMS.

Wherein, determining whether the program file currently used by the NGN terminal needs to be upgraded as described in step B includes:

The IADMS sends the program version to the NGN terminal. The NGN terminal judges whether the received program version is consistent with the currently used program version. If it is inconsistent, it determines that the currently used program file needs to be upgraded.

The NGN terminal downloads the configuration file directly from the file server, and determines whether the program version needs to be upgraded according to whether the version of the program file currently used is consistent with the program version in the downloaded configuration file.

The NGN terminal provides the IADMS with the currently used program version, and the IADMS judges whether the NGN terminal needs a program version upgrade according to the currently used program version, and then sends a corresponding program version upgrade flag to the NGN terminal, and uses the flag to notify the NGN terminal whether or not to proceed. Program file upgrade.

Wherein, before determining whether the program file currently used by the NGN terminal needs to be upgraded, the method further includes:

Issue an automatic upgrade flag. If the flag indicates "upgrade is not allowed", it is no longer judged whether the program version needs to be upgraded. If the flag indicates "upgrade is allowed", then the program version needs to be upgraded. Judge.

Wherein, determining whether the configuration file on the NGN terminal needs to be upgraded includes: The IADMS sends a load configuration file flag to the NGN terminal. If the mark indicates "loading", it means that the configuration file needs to be upgraded.

The determining whether the configuration file on the NGN terminal needs to be upgraded includes: downloading the configuration file directly from the file server by the NGN terminal, and determining whether the NGN terminal determines whether the currently used configuration file is consistent with the verification data of the downloaded configuration file. The configuration file needs to be upgraded.

The determining whether the configuration file on the NGN terminal and the currently used program file need to be upgraded includes:

The NGN terminal downloads the configuration file directly from the file server. The NGN terminal determines whether the program file needs to be upgraded based on whether the version of the program file currently used is consistent with the version of the program file in the downloaded configuration file. The NGN terminal determines whether the program file needs to be upgraded. Whether the verification data of the configuration file is consistent to determine whether the configuration file needs to be upgraded.

The downloading the configuration file directly from the file server by the NGN terminal includes: downloading the configuration file directly from the file server according to the address, file name, and file directory of the file server configured on the NGN terminal.

The downloading of the configuration file directly from the file server by the NGN terminal includes: the IADMS sends the address, file name, and file directory of the file server to the NGN terminal, and the NGN terminal downloads the configuration file from the file server according to the received information. .

Wherein, the NGN terminal mentioned in step C uses at least incubation information to perform service registration with the softswitch including:

The NGN terminal obtains the IP address of the softswitch from the incubation information or configuration file, and sends the TID and key in the incubation information to the softswitch according to the IP address. The softswitch uses the TID and key for service registration. Authentication.

It can be seen that the present invention has the following beneficial effects: 1. For the deployment of NGN terminals, maintenance personnel do not need to go to the site to debug. Only the hardware installers need to complete the hardware installation to use the services, reducing the technical requirements for the deployment personnel;

2. The present invention combines various links in operation and maintenance, thereby achieving the overall operation and maintenance of the NGN terminal, greatly improving the work efficiency, and being able to realize the needs of the NGN terminal operation and maintenance in large quantities;

3. The present invention has lower requirements for operation and maintenance personnel, which does not require the person to know the configuration method for NGN terminals of different manufacturers, and because there is less human involvement in the operation and maintenance process, the possibility of leakage is also reduced. Brief description of the drawings

FIG. 1 is a flowchart for implementing the present invention;

FIG. 2 is a flowchart of implementing step 101 in an embodiment of the present invention;

FIG. 3 is a flowchart of implementing step 101 in an embodiment of the present invention. Mode of Carrying Out the Invention

The present invention is an operation and maintenance method for NGN terminal equipment. This method realizes all links in operation and maintenance as a whole. The operation and maintenance process does not require human participation, and has high efficiency, low error rate, good confidentiality, and low requirements for maintenance personnel. Advantages, can meet the needs of large-scale NGN terminal equipment distribution.

Before describing the present invention in detail, some concepts involved in the NGN network are described first:

IADMS: IADMS is mainly used for management and maintenance in NGN networks. According to the actual needs of operators, you can choose whether to configure whether to include the IADMS in the NGN network;

Softswitch: Softswitch is mainly used to process various services in the NGN network. Through this softswitch, each call process is specifically controlled to achieve related services; NGN terminal incubator: This incubator is used to interact with the NGN terminal, obtain the characteristic information of the NGN terminal, and generate configuration information including at least the TID and the key according to the characteristic information, and configure the configuration information into the NGN terminal The incubator is also configured at least to the softswitch through the internal interface to send the configuration information to the softswitch. If the network includes an IADMS, the incubator can be further configured to the IADMS to further send the configuration information to the IADMS; The incubator can be configured into the NGN network according to the needs of the operator. Without the incubator, the implementation of the present invention will not be affected;

Incubation room for NGN terminal: Since important information such as TID and key need to be assigned to the NGN terminal during the incubation process, in order to improve the security of the incubation process, the incubation process should be performed in a dedicated security environment. The incubation room provides such a secure environment. In the present invention, an internal local area network relatively isolated from an operator is used as the incubation room, and batch incubation of NGN terminals is performed in the incubation room, so that TID can be avoided. During the incubation process, important information such as keys and keys may be leaked due to transmission on the public network.

The present invention is described in detail below with reference to the drawings.

Referring to FIG. 1, the following steps are required to implement the present invention:

Step 101: Incubate the NGN terminal to complete the parameter configuration before use; Step 102: Service provision of the NGN terminal, and use this service to release at least the data required for the operation of the NGN terminal to the softswitch; where, when the NGN network When there is IADMS, in this step, you also need to synchronize the data required for the operation of the NGN terminal to the IADMS; Step 103: The NGN terminal uses the parameters configured in Step 101 to access the NGN network to determine the currently used program file. Whether an upgrade is needed, if yes, go to step 104, otherwise, go to step 105; upgrade, then go to step 105; Step 105: The NGN terminal determines whether the configuration file needs to be reloaded, and if so, executes step 106, otherwise, executes step 107;

Step 106: The NGN terminal automatically loads a configuration file and completes data configuration, and then, performs step 107;

Step 107: The NGN terminal uses the incubation information to perform service registration with the softswitch at least. After the authentication in the service registration is completed, the program file and the configuration file are used to implement the softswitch service. In this step 107, the NGN terminal may Obtain the softswitch IP address from the incubation information, and then send the TID and key in the incubation information to the softswitch according to the IP address. The softswitch uses the TID and key to determine whether the NGN terminal has passed authentication. If it is in the incubation information, If the IP address of the softswitch is not included, the NGN terminal may also obtain the IP address of the softswitch from the configuration file, and send the TID and key in the incubation information to the softswitch based on the IP address to implement service registration. Authentication.

Wherein, in the embodiment of the present invention, automatic upgrade is performed first, and then automatic configuration is performed. In other embodiments of the present invention, automatic configuration may be performed first and then automatic upgrade, or automatic upgrade and automatic configuration may be performed simultaneously. The order of execution between upgrade and automatic configuration does not affect the implementation of the present invention.

The specific implementation of the above steps is described in detail below with reference to the drawings:

1. The specific implementation of step 101. Because there are incubators and IADMS during the incubation process that will affect the specific implementation of the incubation process, the following describes the specific implementation of the incubation process in step 101 separately:

(I) Embodiment 1. Incubator and IADMS are involved in the incubation process. In this embodiment, in order to enable the incubation of NGN terminals, some pre-configurations need to be completed on the NGN terminals before incubation. The configuration methods are divided into Two types:

Method 1: Before the NGN equipment leaves the factory, the equipment manufacturer completes the pre-configuration on the NGN terminal. The configuration includes: 1. How to obtain the IP address of the NGN terminal:

For an NGN terminal with uplink ETH, configure the NGN terminal to obtain an IP address through DHCP;

For an xDSL upstream NGN terminal, configure the NGN terminal to obtain an IP address through PPPoE;

2. The default domain name of the IADMS. The equipment provider needs to configure the IADMS default domain name on the NGN terminal before leaving the factory. The default domain name is also provided in the terminal's information manual. The default domain name provided by the same manufacturer It should be the same, and IADMS.COM is recommended as the default domain name; while the default IADMS domain name is configured on the NGN terminal, the default IADMS domain name is also pointed to the IP address of the NGN terminal incubator in the DNS SERVER on the network. Therefore, during the incubation process, the DNS server can obtain the IP address of the NGN terminal incubator according to the default IADMS domain name provided by the NGN terminal, and provide the IP address to the NGN terminal;

3. Change the default password of the TID and key: In order to prevent changing the TID and key of the NGN terminal through the imitation of the NGN terminal incubator, the provider of the terminal configured to change the TID and key on the NGN terminal before leaving the factory. The default password is provided in the information manual to prevent the above problem of counterfeit NGN terminal incubators. Among them, the default password provided by the same manufacturer should be the same. In the embodiment of the present invention, an 8-digit password is used. A default password; in other embodiments of the present invention, if the above counterfeiting problem is not considered, the default password may not be set, which does not affect the implementation of the present invention;

4. MAC address: Since each NGN terminal does not have its own unique TID during the incubation process, the equipment provider needs to configure a MAC address on the NGN terminal to uniquely identify each NGN terminal with the MAC address; among them, the device Most providers print the MAC address of the NGN terminal on the device shell and packaging of the NGN terminal, so that users can easily obtain it; 5. Default TID: Considering that the incubation process is performed according to a certain protocol, the equipment provider sets a default TID value on the NGN terminal before leaving the NGN terminal, and the TID value is mostly an empty string;

The above method 1 has higher requirements for the equipment provider of the NGN terminal. In view of reducing the requirements on the supply, the method 2 can be used to complete the pre-incubation before incubation;

Method 2: Pre-configuration is performed through an option (OPTION) in the DHCP protocol, and specifically includes:

In the DHCP protocol, the OPTION option is defined, so that during the incubation process, the DHCP server configures the IP address of the incubator to the NGN terminal;

In the DHCP protocol, the OPTION option is defined, so that during the incubation process, the DHCP server configures and changes the default password of the TID and key to the NGN terminal;

In this method, it is also necessary to configure the method of obtaining the IP address of the NGN terminal, as well as the MAC address and the default TID, but it is not necessary for the device provider to configure the default IADMS domain name and change the default of the TID and key on the NGN terminal. Password, thereby reducing the requirements on the equipment provider;

In the first embodiment, after the pre-incubation configuration is completed, referring to FIG. 2, the implementation step 101 includes the following steps:

Step 201: The NGN terminal obtains its own IP address according to a pre-configured IP address obtaining method. In the embodiment of the present invention, the IP address of the NGN terminal is obtained by using a DHCP method.

Step 202: The NGN terminal obtains the IP address of the NGN terminal incubator according to the pre-configuration: In the embodiment of the present invention, the pre-configuration is performed by using the first method described above. Therefore, in this step, the NGN terminal sends a domain name resolution request to the DNS server. The request includes the pre-configured default IADMS domain name. After receiving the request, the DNS SERVER resolves the default IADMS domain name. Because the default IADMS domain has been set on the DNS server in advance The name points to the IP address of the NGN terminal incubator. Therefore, the DNS server resolves to obtain the IP address of the incubator, and sends the IP address to the NGN terminal.

In other embodiments of the present invention, the foregoing pre-configuration may also be implemented in the second manner, and the specific implementation of obtaining the IP address of the NGN terminal incubator in step 202 is:

The DHCP protocol configures the IP address of the incubator from the DHCP server to the NGN terminal according to the preset OPTION;

Step 203: After the NGN terminal obtains the IP address of the NGN terminal incubator, it sends a start message to the NGN terminal incubator to notify the NGN terminal incubator to start incubation; and, the NGN terminal also sends a management registration request to the incubator. The management registration request includes The default TID, IP address, MAC address of the NGN terminal, and the default password for changing the TID and key;

Wherein, in other embodiments of the present invention, considering the reliability of the implementation process, the following steps may be further included before step 203: No has reached or exceeded the preset number of times, and if so, follow the steps in the second embodiment. Complete the incubation of the NGN terminal as described without the incubator; otherwise, send a management registration request to the NGN terminal incubator and continue to perform the subsequent steps;

After step 203 is performed, if the incubator of the NGN terminal returns a successful registration result, the subsequent step 204 is continued; otherwise, the incubation of the NGN terminal is completed according to the situation without an incubator described in the second embodiment;

Step 204: The NGN terminal incubator generates related information including at least a TID and a key according to the related information of the NGN terminal, and specifically includes:

The NGN terminal incubator queries the NGN terminal for related information. The related information includes: equipment identification (EID), MAC address, manufacturer, product model, and port number. Then, the NGN terminal incubator judges the information. If not, end the incubation process; otherwise, the NGN terminal incubator determines whether the EID of the NGN terminal has been recorded on the incubator, and if so, generates a TID and key based on the EID, port number, MAC address, and IP address, otherwise, In addition to generating the TID and the key, further querying and modifying the default password of the TID and the key according to the device manufacturer name of the NGN terminal, and generating a new password for modifying the TID and the key; where if IADMS is included in the network, then The NGN terminal incubator needs to further generate the IADMS domain name;

Step 205: The NGN terminal incubator transmits and writes incubation information including at least the newly generated TID and key into the NGN terminal. If the network includes IADMS, the incubation information also includes the IADMS domain name;

In this step, if the NGN terminal incubator has determined in step 204 that the EID of the NGN terminal has been recorded on the incubator, indicating that the NGN terminal has been incubated, it will not be incubated; or under the control of the user, it will be restarted. incubation.

If the NGN terminal incubator has determined in step 204 that the EID of the NGN terminal is not recorded on the incubator, the NGN terminal incubator further includes: before writing the incubation information to the NGN terminal:

The incubator of the NGN terminal sends the default password of the modified TID and key of the NGN terminal and the generated new password of the modified TID and key to the NGN terminal, and the NGN terminal judges whether the default password is consistent with the default saved on the NGN terminal. The passwords are consistent. If so, write the incubation information and replace the default password for modifying the TID and key with a new password that modifies the TID and key. In other embodiments of the present invention, if the imitation of the NGN terminal is not considered for incubation , The above password verification process may also be omitted, and does not affect the implementation of the present invention;

In the embodiment of the present invention, in order to correspond to step 204, in step 205, after writing the incubation information, the incubation switch is further set to an off state;

So far, the NGN incubation process in Embodiment 1 has ended;

In this embodiment, the following manners can also be adopted for incubating NGN terminals: After the user goes through the account opening procedure in the business hall, the EID, equipment type, port number, and manufacturer and model of the NGN terminal obtained are entered into the incubator of the NGN terminal. The incubator of the NGN terminal generates TID and The incubation information including the key is printed out to the user through a password receipt. At the same time, the incubator of the NGN terminal also synchronizes the incubation information to the soft exchange; for the case of IADMS in the network, the incubation information is also returned. Including the domain name of IADMS, and the incubator of the NGN terminal also needs to synchronize the incubation information to the IADMS; after the user obtains the incubation information through the password receipt, configure the information on the NGN terminal to complete the incubation; among them, configure the incubation information Previously, the NGN terminal could further verify the correctness of the key. The user can obtain the key through, for example, a web page and enter it into the NGN terminal. The NGN terminal compares the key with the key stored by itself. , Configure incubation information; otherwise, refuse to configure incubation information.

(II) Embodiment 2: No incubator and IADMS participate in the incubation process: Because there is no IADMS in this embodiment, a configuration file is generated according to the MAC address and port information of the NGN terminal, and the configuration file is saved in a simple file In a transmission protocol (TFTP) server, the configuration file includes at least a TID and a key, and the configuration files are different for different terminal devices. The definition of the file name is as follows: manufacturer name-port information-MAC address. CFG; :

IAD208: huawei- 108- [0050bal9d349] .cfg

IAD 132: huawei- 132- [0050bal9d348] .cfg

While saving the configuration file in the TFTP server, some pre-configuration is required to enable the incubation of NGN terminals. There are two options for this pre-configuration: Solution 1. The equipment provider completes the pre-configuration before the NGN terminal leaves the factory. Configuration:

1. Load the default domain name of the TFTP / FTP server with the configuration file on the NGN terminal, usually: TFTPSERVER.COM;

2. Load the file name of the configuration file on the NGN terminal. The definition of the file name is the same as that described above. The definition of the configuration file file name stored in the server is the same;

3. Load the loading directory of the configuration file in the server on the NGN terminal so that

The NGN terminal can find the configuration file from the corresponding directory in the server according to the directory;

In order to reduce the requirements for the equipment provider, you can also use the second solution for pre-configuration: The second solution is to complete the pre-configuration by defining the OPTION in the DHCP protocol: 1. By defining the siaddr field in the DHCP protocol, the configuration is provided by the DHCP server to the NGN terminal IP address of the TFTP / FTP server where the configuration file is stored;

2. By defining the OPTION in the DHCP protocol, configure the DHCP server to provide the name of the configuration file to the NGN terminal and the loading directory on the server;

After the pre-configuration is performed as described above, referring to FIG. 3, completing the step 101 in the second embodiment requires the following steps:

Step 301: The NGN terminal obtains the address of the TFTP / FTP server where the configuration file is stored;

In the embodiment of the present invention, the second solution is used for pre-configuration. Therefore, according to the content of siaddr in the DHCP protocol, the embodiment of the present invention provides the IP address of the TFTP / FTP server where the configuration file is stored by the DHCP server to the NGN terminal;

In other embodiments of the present invention, the pre-configuration can also be performed by using the first scheme. In this case, the NGN terminal first sends the pre-configured default domain name of the TFTP / FTP server to the DNS server. Point the default domain name to the IP address of the TFTP / FTP server. Therefore, after receiving the default domain name, the DNS server resolves the domain name to the IP address of the TFTP / FTP server, and then returns the IP address to the NGN terminal. 302: The NGN terminal obtains the file name of the configuration file and the loading directory in the server.

In the embodiment of the present invention, since the foregoing pre-configuration is performed by using the second solution, the content defined by OPTION in the DHCP protocol is provided by the DHCP server to the NGN terminal. Provide the name of the configuration file and the loading directory in the server. In other embodiments of the present invention, the above-mentioned pre-configuration can also be performed by using solution 1. In this case, because the name of the configuration file is configured in the NGN terminal and in the server, Load the directory, so the NGN terminal can get this information directly from itself;

Step 303: According to the obtained IP address of the TFTP / FTP server, the file name of the configuration file, and the loading directory in the server, the NGN terminal obtains a configuration file from the TFTP / FTP server, obtains at least a TID and a key from the configuration file, and Save to complete the incubation of the NGN terminal;

The above is the specific implementation of step 101 in the present invention, and the specific implementation of step 102 is described in detail below.

2. The specific implementation of step 102. If there is no IADMS in the network, the NGN terminal incubator can synchronize the incubation information including at least the TID and the key to the softswitch. If there is an IADMS, then in step 102, the NGN The terminal further synchronizes the incubation information to the IADMS;

3. Specific implementation of steps 103 to 106:

Steps 103 to 106 involve program file upgrade and configuration file upgrade. To determine whether to perform the above upgrade, the following methods can be used:

(1) If IADMS exists in the network, the following methods can be used to determine: 1. The method of determining whether the program file is upgraded:

(1) The IADMS issues a program version to the NGN terminal, and the NGN terminal judges whether the received program version is consistent with the currently used program version. If they are not consistent, it determines that the currently used program file needs to be upgraded;

(2) The NGN terminal downloads the configuration file directly from the file server, and determines whether the program version needs to be upgraded according to whether the currently used program file version is consistent with the program version in the downloaded configuration file. In this way, the NGN terminal can Depending on configuration The file server's address, file name, and file directory can be used to upload and download configuration files directly from the file server. The IADMS can also send the file server address, file name, and file directory to the NGN terminal. The received information downloads the configuration file from the file server;

(3) The NGN terminal provides the IADMS with the currently used program version, and the IADMS determines whether the NGN terminal needs a program version upgrade according to the currently used program version, and then sends a corresponding program version upgrade flag to the NGN terminal, and uses the flag to notify NGN Whether the terminal performs program file upgrade;

Among the above judgment methods, IADMS can further issue an automatic upgrade flag before judging the program version. If the flag indicates "upgrade is not allowed", the program version is no longer judged. If the flag indicates " "Allow upgrade", then make the above judgment of the program version;

2. How to judge whether the configuration file is upgraded:

(1) The IADMS sends a load configuration file flag to the NGN terminal. If the mark indicates "loading", it means that the configuration file needs to be upgraded;

(2) The NGN terminal downloads the configuration file directly from the file server, and the NGN terminal determines whether the configuration file needs to be upgraded according to whether the currently used configuration file is consistent with the verification data of the downloaded configuration file; wherein, in this method, The NGN terminal can upload the configuration file directly from the file server according to the address, file name, and file directory of the file server configured on it, or the IADMS can issue the address, file name, and file directory of the file server to the NGN terminal. , The NGN terminal downloads the configuration file from the file server according to the received information;

(2) If there is no IADMS in the network, the following methods can be used to determine: The NGN terminal downloads the configuration file directly from the file server, and the NGN terminal determines whether the version of the program file currently used is the same as the version of the program file in the downloaded configuration file Consistent To determine whether the program file needs to be upgraded; the NGN terminal determines whether the configuration file needs to be upgraded according to whether the currently used configuration file is consistent with the verification data of the downloaded configuration file; wherein, in this way, the NGN terminal can be configured in the The address, file name, and file directory of the file server on it can directly download the configuration file from the file server. The IADMS can also issue the address, file name, and file directory of the file server to the NGN terminal. The information received downloads the configuration file from the file server.

According to the above judgment, if it is determined that the program file upgrade is required, the NGN terminal downloads the program file from the TFTP / FTP file server and loads the program file;

If it is determined that a configuration file upgrade is required, the NGN terminal downloads a configuration file from a TFTP / FTP file server and configures the configuration file in the NGN terminal; thus far, steps 103 to 106 have been implemented, and step 103 is performed after execution After step 106, step 107 shown in FIG. 1 is performed, and the NGN terminal performs service registration with the softswitch, so that the NGN terminal can use the softswitch service after completing authentication.

The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall be included in the present invention. Within the scope of protection.

Claims

Claim

1. An operation and maintenance method for a next-generation network terminal, characterized in that the method includes: Step A: incubating a next-generation network (NGN) terminal, and synchronizing the incubation information obtained from the incubation to a soft exchange;

Step B: The NGN terminal uses the incubation information to access the network to determine whether the program file currently used by the NGN terminal needs to be upgraded, and if so, downloads a new program file and upgrades; and determines whether the configuration file on the NGN terminal requires Upgrade, if yes, download a new configuration file and upgrade;

2. The method according to claim 1, wherein if the network includes an NGN terminal incubator, the incubating the NGN terminal in step A comprises:

3. The method according to claim 2, characterized in that: Step Al includes:

Pre-configure the NGN terminal IP address acquisition method, and pre-configure the default domain name of the integrated access device management system (IADMS) on the NGN terminal;

Step A2 includes:

Obtain the IP address of the NGN terminal according to the pre-configured IP address acquisition method. The NGN terminal sends a DNS domain name resolution request to the DNS server. The request includes the pre-configured IADMS default domain name. The DNS server resolves the default domain name to the NGN terminal incubator. And return it to the NGN terminal.

4. The method according to claim 2, characterized in that:

Step A1 includes:

In the DHCP protocol, define OPTION: the DHCP server configures the IP address of the incubator to the NGN terminal; and pre-configures the method of obtaining the IP address of the NGN terminal;

Step A2 includes:

Obtain the IP address of the NGN terminal according to the pre-configured IP address acquisition method; the DHCP protocol configures the IP address of the incubator to the NGN terminal by the DHCP server according to the preset OPTION.

5. The method according to claim 3 or 4, characterized in that:

The method for obtaining the IP address of the NGN terminal pre-configured in step A1 is: For an NGN terminal that is upstream from ETH, configure the NGN terminal to obtain an IP address through DHCP; obtaining the IP address of the NGN terminal as described in step A2 is: obtaining IP through DHCP Alternatively, the method for obtaining the pre-configured NGN terminal IP address as described in step A1 is: For an xDSL uplink NGN terminal, configuring the NGN terminal to obtain an IP address through PPPoE; obtaining the IP address of the NGN terminal as described in step A2 is: Obtain an IP address in PPPoE mode.

6. The method according to claim 2, wherein the NGN in step A3 The terminal incubator generating the incubation information includes:

The NGN terminal incubator queries the NGN terminal for related information, where the related information includes: an equipment identifier (EID), a MAC address, an IP address, and a port number, and then generates a TID and a key according to the EID, the port number, the MAC address, and the IP address. .

7. The method according to claim 2, characterized in that, in step A3, before the generating incubation information, the method further comprises:

8. The method according to claim 2, characterized in that step A1 further comprises: step A11: performing a configuration of modifying a default password of the TID and the key, and the NGN terminal obtains the modified TID and the key according to the configuration. Default password

In step A3, the NGN terminal incubator obtaining related information of the NGN terminal further includes: the NGN terminal incubator obtaining the default password of the NGN terminal to modify the TID and key; the generating incubation information further includes: generating a modified TID and A new key password; between steps A4 and A3, the method further includes:

9. The method according to claim 8, characterized in that step A11 comprises: pre-configuring a default password for changing the TID and key on the NGN terminal, and the NGN terminal directly obtains the changed TID and password from itself according to the configuration. The default password for the key.

10. The method according to claim 8, characterized in that step A11 comprises: predefining OPTION in the DHCP protocol: the DHCP server configures a default password for changing the TID and key to the NGN terminal; according to the definition of OPTION , DHCPserver Configure the default password for changing the TID and key to the NGN terminal.

11. The method according to claim 1, wherein incubating the NGN terminal in step A comprises:

The EID, device type, port number, and manufacturer and model of the NGN terminal are entered into the incubator of the NGN terminal, and the incubator of the NGN terminal generates incubation information including the TID and key based on the inputted information;

And, writing the incubation information into an NGN terminal.

12. The method according to claim 11, wherein before writing the incubation information to an NGN terminal, the method further comprises: transmitting a key to the NGN terminal, and the NGN terminal judges the key and the stored default Whether the keys are the same. If the keys are the same, perform the step of writing the incubation information to the NGN terminal; otherwise, refuse to write the incubation information.

13. The method according to claim 1, wherein the incubation information further includes a domain name of the IADMS, and in step A, the incubation information is further synchronized to the IADMS.

14. The method according to claim 1, wherein incubating the NGN terminal in step A comprises:

Step D2: The NGN terminal obtains the server address where the configuration file is saved; and, the NGN terminal obtains the file name of the configuration file and the loading directory in the server;

Step D3: The NGN terminal obtains a configuration file from Yueliang Server according to the server address, the configuration file file name, and the loading directory in the server, and saves the incubation information including the TID and the key in the configuration file in NGN In the terminal.

15. The method according to claim 14, wherein the default domain name of the server, the file name of the configuration file, and the loading in the server are pre-loaded on the NGN terminal. Directory, step 02 includes:

16. The method according to claim 14, wherein the siaddr field in the DHCP protocol is defined in advance, and the IP address of the TFTP / FTP server in which the configuration file is stored is provided by the DHCP server to the NGN terminal; and OPTION, configure the DHCP server to provide the name of the configuration file to the NGN terminal and the loading directory on the server;

Step D2 includes:

According to the siaddr content in the DHCP protocol, the DHCP server provides the IP address of the TFTP FTP server where the configuration file is stored to the NGN terminal; and, through the definition of OPTION in the DHCP protocol, the DHCP server provides the name and Load directory in the server.

17. The method according to claim 1, wherein, if the network includes IADMS, synchronizing the incubation information to the soft exchange in step A further comprises:

Sync incubation information to the IADMS.

18. The method according to claim 1, wherein the determining in step B whether the program file currently used by the NGN terminal needs to be upgraded comprises:

19. The method according to claim 1, wherein the determining in step B whether the program file currently used by the NGN terminal needs to be upgraded comprises: The NGN terminal downloads the configuration file directly from the file server, and determines whether the program version needs to be upgraded according to whether the currently used program file version is consistent with the program version in the downloaded configuration file.

20. The method according to claim 1, wherein the determining in step B whether the program file currently used by the NGN terminal needs to be upgraded comprises:

21. The method according to any one of claims 1, 18 to 20, characterized in that before performing the determining whether the program file currently used by the NGN terminal needs to be upgraded, the method further comprises:

22. The method according to claim 1, wherein the determining whether the configuration file on the NGN terminal needs to be upgraded comprises:

The IADMS sends a load configuration file flag to the NGN terminal. If the mark indicates "load", it means that the configuration file needs to be upgraded.

23. The method according to claim 1, wherein the determining whether a configuration file on the NGN terminal needs to be upgraded comprises:

The NGN terminal downloads the configuration file directly from the file server. The NGN terminal determines whether the configuration file needs to be upgraded according to whether the currently used configuration file is consistent with the verification data of the downloaded configuration file.

24. The method according to claim 1, wherein the judging the NGN Whether the configuration files on the terminal and the currently used program files need to be upgraded include:

The NGN terminal downloads the configuration file directly from the file server. The NGN terminal determines whether the program file needs to be upgraded according to whether the version of the program file currently used is consistent with the version of the program file in the downloaded configuration file. Whether the verification data of the configuration file is consistent to determine whether the configuration file needs to be upgraded.

25. The method according to claim 19, 23, or 24, wherein downloading the configuration file directly from a file server by the NGN terminal comprises:

The NGN terminal downloads the configuration file directly from the file server according to the address, file name, and file directory of the file server configured on the NGN terminal.

26. The method according to claim 19, 23, or 24, wherein the downloading a configuration file directly from a file server by the NGN terminal comprises:

The IADMS delivers the address, file name, and file directory of the file server to the NGN terminal, and the NGN terminal downloads the configuration file from the file server according to the received information.

27. The method according to claim 1, characterized in that, in step C, the NGN terminal uses at least incubation information to perform service registration with the softswitch, including:

The NGN terminal obtains the IP address of the softswitch from the incubation information or configuration file, and sends the TID and key in the incubation information to the softswitch according to the IP address. The softswitch uses the TID and key for service registration Authentication.