Service distribution method, device and system

Abstract

A service distribution method includes the steps of: firstly generating, by a management system, a corresponding configuration file from service information of a user, and sending the configuration file to an Optical Network Termination (ONT) of the user through an Optical Line Terminal (OLT); and then performing, by the ONT, corresponding configuration in accordance with the configuration file. A service distribution system and a management system are provided. The invention is applied to enable service distribution with good extendibility.

Claims

1. A method, comprising: receiving, at an Optical Network Terminal (ONT), a configuration file comprising common configuration information and personalized configuration information from an Optical Line Terminal (OLT), wherein the personalized configuration information comprises an ID of a specific user, and wherein the common configuration information is general configuration information in a common configuration file template corresponding to a type of the ONT, the type of the ONT indicates which Passive Optical Network (PON) technology the ONT is associated with, the common configuration file template is associated with the type of the ONT and is one of a plurality of common configuration file templates, each of the plurality of common configuration file templates is associated with a different type of ONT; parsing, at the ONT, the configuration file to obtain configuration information of the ONT; and configuring the ONT according to the configuration information.

2. The method according to claim 1, wherein the configuration file received is in an extensible Markup Language (XML) format.

3. The method according to claim 1, the method further comprises: receiving, at the ONT, the configuration file through an optical network unit management control interface (OMCI) channel.

4. The method according to claim 1, wherein the configuration file is associated with the type of the ONT and an identifier of an user.

5. An optical network terminal (ONT) comprising: a processor; and a non-transitory memory coupled to the processor and storing program instructions which, when executed by the processor, cause the processor to perform operations comprising: receiving a configuration file comprising common configuration information and personalized configuration information from an Optical Line Terminal (OLT), wherein the personalized configuration information comprises an ID of a specific user, and wherein the common configuration information is general configuration information in a common configuration file template corresponding to a type of the ONT, the type of the ONT indicates which Passive Optical Network (PON) technology the ONT is associated with, the common configuration file template is associated with the type of the ONT and is one of a plurality of common configuration file templates, each of the plurality of common configuration file templates is associated with a different type of ONT; parsing the configuration file to obtain configuration information of the ONT; and configuring the ONT according to the configuration information.

6. The ONT according to claim 5, the operations further comprise: receiving the configuration file through an optical network unit management control interface (OMCI) channel.

7. The ONT according to claim 5, wherein the configuration file received is in an extensible Markup Language (XML) format.

8. The ONT according to claim 5, wherein the configuration file is associated with the type of the ONT and an identifier of an user.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a schematic diagram of a networking structure of an existing PON system;

(2) FIG. 2 is a schematic diagram of a flow of an existing value-added service distribution method;

(3) FIG. 3 is a schematic diagram of a flow of a service distribution method according to an embodiment of the invention; and

(4) FIG. 4 is a schematic diagram of a structure of components in a service distribution system according to an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

(5) The invention will be further described in details below with reference to the drawings and the embodiments to make the object, technical solution and advantages of the invention more apparent.

(6) FIG. 3 is a schematic diagram of a service distribution method according to an embodiment of the invention. Referring to FIG. 3, the method includes the following steps:

(7) In the step 301, the EMS obtains service information of a user.

(8) In this step, the EMS may obtain the service information of the user from the OSS, from information input to the EMS by a network administrator or in any other feasible way in the prior art.

(9) In the prior art, the EMS can obtain the service information of the user from the OSS based upon a network protocol of TL1, Common Object Request Broker Architecture (CORBA), etc.

(10) In the step 302, the EMS generates a corresponding configuration file from the service information of the user.

(11) In this step, in order to facilitate rapid generation of the configuration file for the user, common configuration file templates corresponding to various ONT types can be generated in the EMS according to the ONT types and some common configuration information can be set in these common configuration file templates in advance. Thus, when the user registers for a service, the OSS system or the network administrator can firstly determine the ONT type of the user and then send only personalized configuration information corresponding to the user as the service information of the user to the EMS, and the EMS sets the personalized configuration information of the user in the common configuration file template corresponding to the ONT type of the user and generates the configuration file corresponding to the service information of the user.

(12) Here, the common configuration information refers to general configuration information common to the same category of users/ONTs, and personalized configuration information is a concept with respect to common configuration information, e.g., a phone number, a routing manner, etc., of the user, which are configuration information specific to a user or an ONT.

(13) In this step, the configuration file generated by the EMS can be in a format of currently popular eXtensible Markup Language (XML) or in another format, e.g., a text file (TXT) format or another self-defined format, provided that the ONT can normally parse the file to obtain configuration data upon receiving the configuration file.

(14) In this step, the configuration file generated by the EMS can be stored in the EMS or stored by the EMS into a file server.

(15) Here, the file server may be a file server based upon the File Transport Protocol (FTP) or a server based upon the Trivial File Transfer Protocol (TFTP), the SSH File Transfer Protocol (FTPS) or other file transport protocols.

(16) In the step 303, the EMS sends the configuration file to the OLT.

(17) In this step, the OLT sends the type of the ONT and the identifier (ID) of the user to the EMS when detecting that the ONT is online, and the EMS determines a configuration file to be sent in accordance with the type of the ONT and the ID of the user. The embodiment provides two methods for sending the configuration file to the OLT after the EMS determines the configuration file to be sent.

(18) In the first method, the EMS sends the configuration file directly to the OLT.

(19) In the second method, in the step 302, the EMS stores the generated configuration file in the file server and notifies the OLT about the determined configuration file after determining the configuration file to be sent, the OLT makes a request to the file server for downloading the configuration file, and then the file server sends the configuration file which the OLT requests to download to the OLT.

(20) In this step, the information of the type of the ONT, the ID of the user, etc., may be interacted between the EMS and the OLT based on a transportation means in a protocol of SNMP, Telnet, etc., and the configuration files may be transported between the EMS and the OLT or between the file server and the OLT by a transportation means in a protocol of FTP, TFTP or FTPS or in other file transport protocols.

(21) In the step 304, the OLT sends the configuration file to the ONT.

(22) In this step, the OLT may send the configuration file to the corresponding ONT through an OMCI file loading channel, details of which can be found in a data loading flow of OMCI in the prior art and will not be described here.

(23) In the step 305, the ONT performs corresponding configuration for hardware in the ONT in accordance with the configuration file.

(24) In this step, the ONT parses the configuration file from the OLT to obtain the configuration data corresponding to the service information of the user and performs corresponding configuration for hardware in the ONT in accordance with the configuration data.

(25) Thus, the service distribution flow according to the embodiment is finished.

(26) The service distribution system is described below by way of a system embodiment of the invention.

(27) FIG. 4 is a schematic diagram of a structure of components in the service distribution system according to an embodiment of the invention. Referring to FIG. 4, the system includes an OSS, an EMS, an OLT and an ONT.

(28) Particularly, the EMS is adapted to generate a corresponding configuration file from service information of a user and to send the configuration file through the OLT to the ONT corresponding to the user.

(29) The OLT is adapted to send the received configuration file to the ONT corresponding to the user.

(30) The ONT is adapted to perform corresponding configuration for hardware in the ONT in accordance with the configuration file.

(31) In the system illustrated in FIG. 4, the EMS is further adapted to set a common configuration file template containing common configuration information, which corresponds to the type of the ONT, to set the personalized configuration information of the user as the service information of the user in the common configuration file template corresponding to the ONT type of the user and to generate a configuration file corresponding to the service information of the user. Here, the EMS can obtain the service information of the user from the OSS based upon a network protocol of TL1, CORBA, etc., from information input to the EMS by a network administrator or in any other feasible way in the prior art.

(32) In the system illustrated in FIG. 4, the OLT can be adapted to detect the ONT and to send the type of the ONT and the ID of the user to the EMS when detecting that the ONT is online, and the EMS determines a configuration file to be sent in accordance with the type of the ONT and the ID of the user. The embodiment provides two methods for sending the configuration file to the OLT after the EMS determines the configuration file to be sent.

(33) In the first method, the EMS sends the configuration file directly to the OLT. In this method, the configuration file may be transported between the EMS and the OLT by a transportation means in a protocol of FTP, TFTP, FTPS or in other file transport protocols.

(34) In the second method, the system illustrated in FIG. 4 further includes a file server, so that the EMS stores the generated configuration file in the file server and notifies the OLT after determining the configuration file to be sent, the OLT initiates to the file server a file download request for downloading the configuration file, and then the file server sends the configuration file requested by the OLT to the OLT. In this method, the configuration file may be transported between the file server and the OLT by a transportation means in a protocol of FTP, TFTP, FTPS or in other file transport protocols.

(35) The OLT can send the configuration file to the corresponding ONT through an OMCI file loading channel upon receiving the configuration file.

(36) In the system illustrated in FIG. 4, the EMS may be adapted to generate the configuration file in a format of XML, TXT or other formats.

(37) The ONT is adapted to parse the configuration file in the format of XML, TXT or in other formats to obtain configuration data corresponding to the service information of the user and to perform corresponding configuration for hardware in the ONT in accordance with the obtained configuration data.

(38) As can be seen from the above embodiments, in the technical solutions of the embodiments of the invention, firstly the EMS generates the corresponding configuration file from the service information of the user and then sends the configuration file through the OLT to the ONT corresponding to the user, and finally the ONT performs corresponding configuration for hardware in the ONT in accordance with the configuration file, thereby accomplishing service configuration for the ONT by way of the configuration file. Since the configuration file may be extended flexibly, the service configuration information in the configuration file may also be extended flexibly.

(39) Furthermore, since in the above technical solutions the OLT can simply transport the configuration file from the EMS to the ONT without perceiving the configuration, so the coupling between the equipments of EMS, OLT and ONT may be reduced, thereby also resulting in enhanced extendibility of a service.

(40) Additionally, in order to facilitate rapid generation of the configuration file for the user, in the embodiment, common configuration file templates corresponding to different ONT types are set in the EMS, and thus the OSS or the network administrator can simply send the personalized configuration information of the user to the EMS, so that the EMS can generate the configuration file from the personalized configuration information.

(41) The foregoing descriptions are merely illustrative of the preferred embodiments of the invention but not intended to limit the scope of the invention. Any modifications, equivalents and adaptations made without departing from the spirit of the invention shall come into the scope of the claims appended to the invention.