JP2021040323A - Communication device, information notification method and computer program - Google Patents

Abstract

To allow for succession of information about the components constituting a communication device or the communication device, with reassignment of the components constituting the communication device or the communication device.SOLUTION: A communication device is equipped with a holding part, which may be set as a home and may become the holding part during operation. Any one of the holding parts holding the information about a specific state during operation is set as a home, the information about a specific state during operation is held in the home, other holding part is notified always or intermittently of the information about the specific state during operation held in the holding part set as the home, and when the components or the communication device constituting the communication device becoming the re-assigned object are re-assigned, the holding part during operation notifies a holding part, that is not the notification object at least of the information about the specific state, while changing the notification destination so that the holding part of the reassignment destination is included in the notification destination at the time of reassignment.SELECTED DRAWING: Figure 1

Description

The present invention relates to communication devices, information notification methods and computer programs.

A communication system including a communication device includes, for example, a PON (Passive Optical Network) system. The PON system consists of an ONU (Optical Network Unit) installed in the customer's home, etc., and an OLT (Optical Line Terminal), which is a communication device installed in the station building. ) And an optical fiber network connecting the two (see Non-Patent Document 1).
In a communication device, a function that is less dependent on at least one of the device's conforming standard, generation, method, system, device type, and manufacturing vendor is made into a component, and an application programming interface (API) for that function is included. By clarifying at least a part of the output interface (IF) and enhancing versatility, portability, and expandability, devices with different compliance standards, generations, methods, systems, device types, and manufacturing vendors are used. It is possible to easily share the interface and add unique functions (see Non-Patent Document 2).

ITU-T Recommendation G.989.1 40-Gigabit-capable passive optical networks (NG-PON2), 2013 "FASA", [online], NTT, [Searched on July 28, 2016], Internet <http://www.ansl.ntt.co.jp/j/FASA/index.html>

When the function is made into parts, the parts are not always arranged in the same housing, but may be dispersed in a plurality of housings. Conversely, parts inside the housing may be used as parts that make up other devices. However, the components and communication devices that make up communication devices such as ONUs, transmitters, receivers, transmitters / receivers, CT (channel frequencies), OSUs (Optical Subscriber Units), and OLTs use the operational information held by the communication devices. When it is held on the side, operational information, especially information related to the reassignment of parts such as ONUs to be replaced due to the reassignment of parts such as ONU accommodation replacement to wavelength, core wire, mode, frequency, carrier, code, etc. For example, sleep state, operation system state, wavelength, core wire, core, code, frequency, carrier usage state, own device or opposite device state, multicast subscription / withdrawal / delivery status, attribution (accommodation) history, and in advance. Means are needed to inherit any of the defined or calculated future attribution (accommodation) replacement orders.

In view of the above circumstances, the present invention is to inherit the information related to the parts or the communication device constituting the communication device with the reassignment of the parts or the communication device constituting the communication device such as the replacement of the optical subscriber line terminal device. The purpose is to provide technology that can be used.

One aspect of the present invention is to hold information on a specific state of a component or communication device that constitutes a communication device such as an optical subscriber line termination device to be reassigned as a component or communication device that constitutes the communication device. The holding unit is a communication device including a unit, which notifies other holding units of information regarding the specific state being held when the attribution is changed.

One aspect of the present invention is the above-mentioned communication device, in which the holding portion is a component or a communication device that constitutes a communication device such as the optical subscriber line termination device, and the wavelength, core wire, mode, etc. Notify all of the holding units that hold the relevant information such as the frequency, carrier, and code of the information regarding the specific state.

One aspect of the present invention is the above-mentioned communication device, wherein the holding portion is any one of holding portions that holds information such as wavelength, core wire, mode, frequency, carrier, and code, which can be reassigned to the component. One is set as a home, information about the specific state is held in the home, and at least the holding unit corresponding to the wavelength, core wire, mode, frequency, carrier, code, etc. in operation is notified.

One aspect of the present invention is the above-mentioned communication device, and the holding portion relates to the above-mentioned specific state according to a component constituting the communication device such as the optical subscriber line termination device or a change of attribution of the communication device. The information is notified to the holding unit corresponding to the wavelength, core wire, mode, frequency, carrier, code, etc. of the transfer destination.

One aspect of the present invention is to hold information on a specific state of a component or communication device constituting a communication device such as an optical subscriber line termination device to be reassigned as a component or communication device constituting the communication device. This is an information notification method performed by a communication device including a unit, and the holding unit holds information about the specific state as another holding unit due to a change of attribution of a component or a communication device constituting the communication device. It is an information notification method to notify to.

One aspect of the present invention is a computer program for causing a computer to function as each functional unit provided in the communication device according to the present invention.

INDUSTRIAL APPLICABILITY According to the present invention, it is possible to inherit information related to a component or a communication device constituting a communication device with the assignment of a component or a communication device constituting the communication device.

It is a figure which shows the 1st example of the architecture of a communication device. It is a figure which shows the 2nd example of the architecture of a communication device. It is a figure which shows the 3rd example of the architecture of a communication device. It is a figure which shows the 4th example of the architecture of a communication device. It is a figure which shows another example of architecture. It is a figure which shows the example of the configuration of a communication device and an external server 16. It is a figure which shows the structure of OLT. It is a figure which shows the flow of the signal / information between the functional part in a communication device. It is a figure which shows the example of the functional structure which a PON main signal processing function part 300 has. It is a figure which shows the example of the functional structure which the PON access control function part 320 has. It is a figure which shows the example of the functional structure which the L2 main signal processing function part 340 has. It is a figure which shows the 1st example of the functional structure which the maintenance operation function part 330 has. It is a figure which shows the 2nd example of the structure of the function which the maintenance operation function part 330 has. It is a figure which shows the 3rd example of the functional structure which the maintenance operation function part 330 has. It is a figure which shows the example of the functional structure which the PON multicast functional part 350 has. It is a figure which shows the example of the functional structure which the power saving control function part 360 has. It is a figure which shows the example of the functional structure which the frequency / time synchronization function part 370 has. It is a figure which shows the example of the functional structure which the protection function part 380 has.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
(Embodiment 1)
The communication device is, for example, a device that executes communication with another communication device by a signal such as an optical signal passing through a communication network such as an optical fiber network such as PON. The communication device is, for example, an OLT. The communication device may be, for example, OSU. The communication device may be, for example, a combination of an OLT having or not having a switch unit (SW) for switching an optical signal and another switch unit (SW). The communication device may be, for example, a combination of OLT and ONU. The communication device may include a plurality of devices.

Communication between parts and communication devices that make up communication devices such as ONUs, transmitters, receivers, transmitters and receivers, CT, SNMP, and OLT is via middleware, which will be described later, but the communication devices' unique transfer paths and means are used. It may be used, or standardized means such as OPENFLOW, NETCONF / YANG, and SNMP (Simple Network Management Protocol) may be used. Further, any of the routes such as internal wiring, backboard, OAM unit, main signal line, dedicated wiring, operation system, controller or control panel (Cont panel) may be used. The exchange may be encapsulated in the OAM section or the main signal, or terminated at any point, such as internal wiring, backboard, OAM section, main signal line, dedicated wiring, operation system, controller or control panel, etc. It may be input via a route. When using the OAM section or the main signal line, it is desirable to encapsulate it in the OAM section or the main signal. When passing through the main signal line, it is desirable to distribute it at the OSU or the switch section at another location.

Next, as an example, the operation and the like will be illustrated on the premise of an OPT recommended compliant with an ITU-T recommendation such as a TWDM (Time and Wavelength Division Multiplex) -PON system. Here, TWDM-PON is used, but the PON may be a PON other than the TWDM-PON conforming to the ITU-T recommendation. For example, the PON may be an IEEE standard compliant PON such as GE (Gigabit Ethernet®-PON, 10GE-PON, etc.). The TC (Transmission Convergence) layer and the PMD (Physical Medium Dependent) layer are the same if they are read as the corresponding layers in the standard.

Hereinafter, ONU will be described as a representative as parts and communication devices constituting communication devices such as ONUs, transmitters, receivers, transmitters / receivers, CTs, OSUs, and OLTs to be reassigned, but the same applies to other than ONUs. ..
In the transmitter or receiver or transmitter / receiver or CT or OSU or OLT (communication device), operational information related to the ONU to be replaced, such as sleep state, operational system state, wavelength, core wire, core, code, frequency, etc. Sub) Carrier usage status, own device or opposite device status, multicast subscription / withdrawal / distribution status, set value, ONU state information, EqD, authentication information, filter setting information, usage history (history information) ), Billing information, contract information, Mac table (MAC Table) which is learning information such as Mac address, insufficient counter (Deficit Counter) regarding bandwidth usage and bandwidth allocation, response such as Multicast Leave / Join, etc. It may be the thing itself, or it may be an attribution (accommodation) history or a predetermined or calculated future attribution (accommodation) replacement order, and a holding unit that holds any of those specific states. To be equipped. The holding unit performs one of the following processes.

(1) Advertise (notify) operational information to all of the holding units that hold information such as wavelength, core wire, mode, frequency, (sub) carrier, and code that can be accommodated in the ONU. The advertisement or the notification described later may be constant or intermittent, and the upper limit of the intermittent cycle depends on the error of the state information. For example, assuming that 1 GB is an allowable error in the flow rate control, the error is equal to or less than the time interval in which the flow rate of 1 GB is generated. On the contrary, when the intermittent cycle is too long and the error exceeds the permissible value, the flow rate itself may be suppressed so that the error is less than or equal to the error. Further, the information written to the holding unit may be the operation information itself or information based on the result of statistically processing the operation information. The written information may be information based on the sum of the information for a certain period, the exponential average, the moving average, the average in the form of resetting the history at a predetermined interval, and other statistical processing. The write information may be changed according to the bandwidth and bandwidth time product of the communication path required for writing and the processing cost required for writing. It is desirable to satisfy the restrictions required for advertising or notification from the communication bandwidth consumed by sending and receiving operational information and the time required to transfer operational information. For example, as the transmission time, for example, in the case of a specified PLOAM response of 0.75 ms between OLT and ONU, the time required for the process is from the time allowed for the process, such as 0.75 ms. Is the reciprocating transmission time of the OSU-holding unit, which is equal to or less than the time obtained by subtracting. If there is a time variation (jitter) in the start time or processing time of the transmission time or the time required for processing such as framing for transmission or reading / writing from the holding unit, the time with the maximum jitter delay added. May be the time required for processing. The time allowed for processing and response may be longer than the specified value in standardization or the like, or longer than the specified value if the opposing device allows it. For example, in the case of PLOAM, the value may be higher than that if the ONU and OLT operate in correspondence with each other, such as not interrupting communication even for 0.75 milliseconds or more.

(2) One of the holding units that hold the wavelength, core wire, mode, frequency, (sub) carrier, and code information that can be accommodated in the ONU is set as the home, and the operation information is held at the home. Notify at least the holding part of the wavelength, core wire, mode, frequency, (sub) carrier, code, etc. in operation. The holding unit corresponding to the wavelength, core wire, mode, frequency, (sub) carrier, code, etc. in operation to be notified is to be accommodated at the time of accommodation change, and at least when the accommodation is to be changed outside the notification target, the accommodation change destination The notification destination is changed so that the notification destination includes the holding unit corresponding to the wavelength, the core wire, the mode, the frequency, the (sub) carrier, the code, and the like.

(3) At the time of accommodation change, the operation information is notified to the holding unit corresponding to the wavelength, core wire, mode, frequency, (sub) carrier, code, etc. of the accommodation change destination. The operational information of the accommodation source's holding unit to be replaced is as soon as it is notified to the accommodation destination's holding unit, the notification of the operation information storage from the accommodation destination's holding unit, or the operation information from the accommodation destination's holding unit is not yet available. It is desirable to delete it after confirming that it has not passed a predetermined period of storage or a predetermined cycle.

In (1) to (3), the transmitter, receiver, transmitter / receiver, CT, OSU, OLT, etc. corresponding to the holding unit that holds the information of the unaccommodated ONU, etc. are the paths, etc. according to the operation information in advance. It is desirable to set it, and if there is a problem of bandwidth reduction from the setting, it is desirable to set it and suspend the operation according to the setting.

Here, the accommodation change may be for the purpose of load balancing or power saving, or may be Type B switching or party switching. Switching triggers are lack of advertisement or notification for a predetermined period in the case of continuous or intermittent advertisement or notification, switching notification, LOS (Loss of Signal), LOBi (Loss of burst for ONUi), DyingGasp, OSU power off, OSU removal. , The core wire may be removed, or it may be detected by whether or not there is a new input to the holding unit, and the total band request from the ONU and the flow rate at the OSU, OLT, or SW are measured by the holding unit, respectively. It may be detected as an abnormality of the switching trigger when the values held and held are different from each other by a predetermined value or more without appropriate processing such as flow rate limitation. For example, in the case of forced switching and cold standby (Cold Standby), the frame is buffered by an external device such as a switch (SW), and the backup system OSU (Cold Standby) starts to start within 50 milliseconds after the instruction. However, the downlink traffic has no frame loss, the uplink traffic has no frame loss up to the ONU uplink buffer amount, and the communication in the operation information of the operation system is switched without the range processing. For example, in the case of OSU switching (information inheritance, failure, Cold Standby, buffering with SW in preparation for switching in advance), the package or fiber of the operating OSU is removed, and the set switching protection time and error +1 setting unit Since the backup system OSU (Cold Standby) starts to start within this time, frame loss occurs in the downlink traffic up to the set switching protection time + 1 set unit. Further, in the uplink traffic, the OSU is switched without causing frame loss up to the ONU uplink buffer amount. For example, in the case of OSU switching (forced switching, hot standby), the backup OSU (Cold Standby) starts to start within 50 milliseconds after the instruction, and no frame loss occurs in downlink traffic. In the uplink traffic, frame loss does not occur up to the amount of the ONU uplink buffer, and communication in the operation information of the operation system is switched without the range processing.
For example, in the case of ONU switching (forced switching, hot standby), startup of (Cold Standby) starts in the standby ONU within 50 milliseconds after the instruction, no frame loss occurs in downlink traffic, and in uplink traffic. A frame loss up to the time until activation, for example, 50 milliseconds, occurs, and communication of operation information of the operation system OSU is started.
If the operation information after the abnormal state is normal, the operation information after the transition may be used, but if the abnormal operation information is used, the abnormal state may occur. The risk can be reduced by using the operating state before the abnormality.

(Embodiment 1-1)
In the first embodiment, the configuration of the communication device constituting the communication system used for the TWDM-PON will be described. Hereinafter, examples 1 to 6 will be described as examples of the architecture of the communication device. The architecture of the communication device constituting the communication system may be an architecture other than the first to sixth examples described below. For example, the software part of the communication device in the first to sixth examples of the architecture may be a hardware part.

(First example of architecture)
FIG. 1 is a diagram showing a first example of a communication device architecture. In the first example of the architecture, the communication device is device-independent, with device-dependent section 110 that depends on compliant standards and manufacturing vendors, middleware 120 that hides the hardware and software differences of device-dependent section 110, and device-independent operation. It includes a general-purpose device-independent application 130. Therefore, the device-dependent section (vendor-dependent section) 110 is a functional section that depends on the standard to which the device of the communication device conforms and the manufacturing vendor of the device. In other words, the device-dependent unit 110 has low compatibility with other communication devices, and cannot be used as it is for newly manufactured communication devices (particularly, devices having different conforming standards or manufacturing vendors). The device-dependent unit 110 executes one or more functions provided in the network device.

Further, the device-independent application 130 is a functional unit that does not depend on the standard to which the device of the communication device conforms or the manufacturing vendor of the device. In other words, the device-independent application 130 is highly compatible with other communication devices, and can be used as it is for newly manufactured communication devices (particularly, devices having different conforming standards and manufacturing vendors). Specific examples of the application provided in the device-independent application 130 include an application that performs setting processing in a network device, an application that performs setting change processing, an application that performs algorithm processing, and the like.
The middleware 120 and the device-independent application 130 are connected via the device-independent API 21. The device-independent API 21 is an input / output IF that does not depend on the device.

The device-dependent unit 110 includes, for example, a hardware unit (PHY) 111, a hardware unit (MAC) 112, a software unit 113, and an OAM (Operation Management and Maintenance) unit 114. The hardware unit (PHY) 111, the hardware unit (MAC) 112, the software unit 113, the OAM unit 114, and the middleware 120 are connected via the device-dependent API 23. The device-dependent API 23 is an input / output IF that depends on the device. The device-dependent unit 110 further includes a NE (New Network Element) management / control unit 115. The NE management / control unit 115 and the middleware 120 are connected via the device-dependent API 25.

What kind of function is the device-dependent unit 110 or the device-independent application 130 depends on the restrictions derived from the processing for realizing the middleware 120 and the device-independent application 130, for example, the restrictions derived from the processing capacity of the software. In addition, it may be determined according to the update frequency of the function, the importance of the extended function, and the like. As a result, the communication device can facilitate the flexible and quick addition of the extended function unit (unique function unit) by the device-independent application 130, and can provide the communication service in a timely manner.

For example, the device-dependent unit 110 or device-independent, giving priority to functions that are frequently updated such as DBA (Dynamic Bandwidth Assignment) that improves the priority processing of the main signal and line utilization efficiency, or functions that contribute to communication service differentiation. You may decide to use app 130. Further, the device-independent application 130 may be used because the difference is small with respect to at least one of the standards, generations, methods, systems, device types, and manufacturing vendors to which the devices to be shared are compliant.

Any of the compliant standards, generations, methods, systems, equipment types, manufacturing vendor features, even if it is not optimal for at least one of the compliant standards, generations, methods, systems, equipment types, and manufacturing vendors. In order to generalize the above, a common IF for executing the function may be used. The common IF may include IFs and parameters that are not used in any of the standards, generations, methods, systems, device types, and manufacturing vendors to which the device-dependent unit 110 conforms.

The middleware 120 shown in FIGS. 1 and 2 described later, the driver of the device-dependent unit 110 shown in FIGS. 3 and 4 described later, and the device-dependent application unit (vendor-dependent) shown in FIGS. 2 and 4 described later. At least one of the application section) is further equipped with a conversion function section that converts IFs and parameters so that they correspond to the device-dependent section 110, and a function section that automatically sets IFs and parameters that are insufficient. May be good.

The hardware unit (PHY) 111 included in the device-dependent unit 110 shown in FIG. 1 executes (PHYsical sublayer processing) from the physical layer to the processing related to optical transmission / reception. The hardware unit (MAC) 112 executes MAC (Media Access Control) processing. The hardware unit (PHY) 111 and the hardware unit (MAC) 112 depend on the standards and manufacturing vendors to which they comply. The software unit 113 executes device-dependent drivers, firmware, applications, and the like.

In addition to these, the hardware unit (PHY) 111 and the hardware unit (MAC) 112 of the device-dependent unit 110 may include a general-purpose server, a layer 2 switch, and the like. The device-dependent unit 110 does not have to include the hardware unit (MAC) 112. The device-dependent unit 110 does not have to include a part of the hardware unit (PHY) 111. For example, the device-dependent unit 110 may have only optical-related functions without providing low-level signal processing such as modulation / demodulation signal processing, forward error correction (FEC, Forward Error Correction), code decoding processing, and encryption processing. Good. The device-dependent unit 110 does not have to include a PCS (Physical Coding Sublayer) which is a part for encoding data. The device-dependent unit 110 does not have to include a PMA (Physical Medium Attitude) for serializing data and a PCS. The device-dependent unit 110 does not have to include a PMD connected to a physical medium. The device-dependent unit 110 is a software unit when the middleware 120 directly drives, controls, operates or manages the hardware unit (PHY) 111 and the hardware unit (MAC) 112 of the device-dependent unit 110 without going through the software unit. It is not necessary to provide.

The device-independent application 130 is, for example, an extended function unit (in FIG. 1, extended function A131-1, extended function B131-2 and extended function C131-3) 131, a basic function unit 132, and a management / control agent unit 133. And. The management / control agent unit 133 acquires data from the EMS (Element Management System) 140. In the figure, the EMS 140 and the external device 150 are connected to the device-independent application 130 via the middleware 120, but the EMS 140 and the external device 150 need not necessarily be connected to the device-independent application 130 via the middleware 120. There is no. The EMS 140 and the external device 150 may be appropriately connected to the middleware 120, if necessary, or may be directly connected to the device-independent application 130. In addition, although it is expressed as "connecting via middleware 120", this expression is an expression from the viewpoint of the device-independent application 130. Actually, after the hardware connection, the function-independent applications are connected to each other via the middleware 120.

Hereinafter, matters common to the extended function unit will be referred to as "extended function unit" by omitting a part of the reference numerals. The EMS 140 is, for example, a NE controller. The device-independent application 130 does not have to include any one of the extended function unit, the basic function unit 132, and the management / control agent unit 133, and the management / control agent unit 133 is included in the basic function unit 132. The management / control agent unit 133 may be included in the basic function unit 132 or the middleware 120.

The device-independent application 130 may further include a configuration other than the extended function unit, the basic function unit 132, and the management / control agent unit 133. For example, when the extension function unit is unnecessary, the device-independent application 130 does not have to include the extension function unit. Further, the device-independent application 130 may include one or more extended function units.

It is preferable that the extended function unit can be added, deleted, replaced or changed independently without unnecessarily affecting other functions. For example, the extension function unit may be added, deleted, replaced, or changed as appropriate when, for example, a multicast service or an extension function unit that executes power saving measures is required according to a service request.

The basic function unit 132 may be included in the device-independent application 130 as a part of the extension function unit, or may be replaced by a function unit lower than the middleware 120. When the extended function unit includes the basic function unit 132, the device-independent application 130 does not have to include the basic function unit 132. When a functional unit lower than the middleware 120 replaces the basic functional unit 132, the device-independent application 130 does not have to include the basic functional unit 132. When the extended function unit includes the basic function unit 132 and the function unit lower than the middleware 120 replaces the basic function unit 132, the device-independent application 130 does not have to include the basic function unit 132.

When the management / control agent unit 133 automatically sets according to a predetermined setting without receiving communication from the EMS 140, the management / control agent unit 133 does not have to input / output with the EMS 140. Further, when the management / control agent unit 133 does not have the management setting function and the other device-independent application 130, the basic function unit 132, or the device-dependent unit 110 has the management setting function, the device-independent application 130 manages / controls. The control agent unit 133 may not be provided.

Information may be directly input / output between the EMS 140 and the device-independent application 130. Further, the device-dependent unit 110 may be replaced by the NE management / control unit 115 and the device-dependent application unit (see FIG. 2 and FIG. 4 described later) of the lower functional unit of the NE management / control unit 115. ..

When the management / control agent unit 133 automatically sets according to a predetermined setting, it is not necessary to input / output information to / from the EMS 140. Further, when the management / control agent unit 133 does not have the management setting function and the other device-independent application 130, the basic function unit 132, or the device-dependent unit 110 has the management setting function, the device-independent application 130 manages / controls. The agent unit 133 may not be provided. Information may be directly input / output between the EMS 140 and the device-independent application 130.

An example of input / output between the device-independent application 130 and the device-dependent unit 110 is as follows.
For example, the DBA application unit and the protection application unit input / output information to and from the embedded OAM engine (Embedded OAM Engine) of the TC layer. The DWBA (Dynamic Wavelength and Bandwidth Authentication) application and the ONU registration authentication application unit input / output information to and from the PLOAM engine of the TC layer. The power saving application unit inputs / outputs information to and from the OMCI and the L2 main signal processing function unit (L2 function unit). The MLD (Multicast Listener Discovery) proxy application unit inputs and outputs information to and from the L2 functional unit. The low-speed monitoring application (OMCI) inputs and outputs information to and from OMCI. The OMCI and L2 functional units operate the XGEM framer (XGPON Encapsulation Method Framer) and encryption. Here, DWBA and DBA may be separated, integrated or combined. For example, the management / control agent unit 133 inputs and outputs information to and from the EMS 140, which is an application unit of the maintenance operation function and is an NE controller or the like for the NE management / control unit 115.

The device-independent application 130 is a device vendor, method, device type, device generation, for example, ITU-T G.M. TWDM-PON conforming to the 989 series and ITU-T G. XG-PON conforming to the 987 series and ITU-T G. G-PON conforming to the 984 series and ITU-T G. It is an application that operates regardless of the B (Broadband) PON conforming to the 983 series. The device-independent application 130 differs in device vendor, method, device type, device generation, for example, 10GE-PON conforming to IEEE802.3av and IEEE1904.1, and GE-PON conforming to IEEE802.3ah. It is an app that works regardless of at least one of them.

As an extension function application, only for some vendors, methods, types, and generation devices, and for some vendors, methods, types, and generations, via device-independent API21. It may include an app that drives the features it provides.
The management / control agent unit 133 inputs / outputs to and from the EMS 140 and the middleware 120. The middleware 120 inputs / outputs NE management information and control information to / from the NE management / control unit 115. The NE management / control unit 115 may directly send / receive NE management information and control information to / from the EMS 140 without going through the middleware 120, or may send / receive NE management information and control information via the management / control agent unit 133. You may.

The middleware 120 inputs / outputs information via the device-independent application 130 and the device-independent API 21. The middleware 120 inputs / outputs information to / from the OAM unit 114, the driver, the firmware, the hardware unit, or the hardware unit of the device-dependent unit 110 via the device-dependent API 23. The middleware 120 outputs the input information as it is or in a predetermined format. For example, if the output destination is each part of the device-independent application 130, the middleware 120 converts the information into the input format of each part of the device-independent API 21. If the output destination is the OAM unit 114 of the device-dependent unit 110, the driver, the firmware, the hardware unit, or the hardware unit, the middleware 120 converts it to the device-dependent API 23 format to be input to each, or terminates it. After performing the predetermined processing, the information is transmitted to the output destination.

It is desirable that the middleware 120 deletes unnecessary input information at each input destination at the time of input, and if there is insufficient information, collects and supplements it via another device-independent API 21 or device-dependent API 23. .. Further, when inputting to the middleware 120, it may be broadcast or multicast to broadcast to a related application or the like.

In FIG. 1, the middleware 120 and the device-dependent unit 110 are illustrated as a single unit, but each may be composed of a plurality of units. When the hardware of the device-dependent unit 110 includes a plurality of processors, the middleware 120 may input / output across the processors and the hardware by using interprocessor communication or the like. The device-independent apps 130 and the device-independent apps 130 may be arranged in the user space on a single processor as an execution program such as DLL (Dynamic Link Library), or in the user space on a plurality of processors. It may be placed on top.

Further, the device-independent application 130 may be arranged in the kernel space after securing input / output IFs such as API, or may be arranged together with middleware 120 having an IF that can be independently replaced with firmware or the like. , It may be incorporated into the firmware or the like and recompiled. The user space and kernel space may be any combination for each device-independent application 130.

The device-independent application 130 corresponding to the same function may be implemented in both the user space and the kernel space. In this case, for example, it may be switched and either one may be selected, both may be processed in cooperation, or the actual processing may be performed by only one of them. The same applies to the software of the device-dependent unit 110.

Desirably, the more high-speed processing such as main signal processing, DBA processing, and low-layer signal processing is required, the more there is a trade-off with the immediacy of expandability / replacement, but high-speed processing with less overhead is expected. It is desirable to incorporate it in kernel space or firmware. The processor in which the device-dependent application unit (see FIGS. 2 and 4 described later) is also actually processed from the viewpoint of the influence on other programs due to the limitation of the bus and speed due to the inter-processor communication, the occupation of the communication path, etc. It is desirable to place it in the user space, kernel space, or firmware of the processor that performs the above or in the vicinity of the processor. However, in order to reduce the capacity of the processor that performs the actual processing or a processor in the vicinity thereof, the communication cost due to the inter-processor communication increases, but the processing may be performed by a remote processor.

It is desirable that the device-independent API 21 is provided in the middleware 120 in advance assuming an extension function unit to be added, but it is added as necessary in a form of suppressing modification of the device-dependent API 23 and other device-independent apps 130. Alternatively, it may be deleted.

In this example, the softened area is the basic function unit 132, the management / control agent unit 133, the extended function unit, and the middleware 120, but the softened area is the service adaptation (encryption, fragment processing, GEM frame). / XGEM framing, PHY adaptation FEC, scrambling, synchronous block generation / extraction, GTC (GPON Forward Convergences) framing, PHY framing, SP conversion, coding method may also be targeted. Implementation of architectural softening function An example and an example of function deployment corresponding to the hardware section (PHY) 111 and the hardware section (MAC) 112 will be described. The function deployment includes, for example, a software function in a network device or an external server. The same applies to the example of.

(Second example of architecture)
FIG. 2 is a diagram showing a second example of the architecture of the communication device. In FIG. 2, the communication device is configured to further include a device-dependent application unit 160 under the middleware 120 of the communication device shown in FIG. The second example of the architecture is the same as the first example of the architecture except that the device-dependent application unit 160 is provided.

In FIG. 2, the communication device includes the hardware unit (PHY) 111 and the hardware unit (MAC) 112, and the hardware unit (PHY) 111 and the hardware, which depend on the standard of the compliant device-dependent unit 110 or the equipment manufacturing vendor. A software unit that executes a driver, firmware, etc. that drives the wear unit (MAC) 112, and at least a part of the hardware unit (PHY) 111, the hardware unit (MAC) 112, and the software unit of the device-dependent unit 110 are driven. A device-dependent application unit 160, a middleware 120 that hides the differences between the hardware unit, hardware unit, software unit, and device-dependent application unit 160 of the device-dependent unit 110, and a general-purpose device-independent application 130 that does not depend on the device. Be prepared.

The middleware 120 and the device-dependent application unit 160 are connected by the device-dependent API 23. The device-dependent application unit 160, the OAM unit 114 of the device-dependent unit 110, the software unit, the hardware unit (PHY) 111, and the hardware unit (MAC) 112 are connected by the device-dependent API 24. The device-dependent application unit 160 and the management / control agent unit 133 are connected by an API.

The device-independent application 130 includes, for example, a management / control agent unit 133 that receives communication from the EMS 140, a basic function unit 132, and an extended function unit. The device-independent application 130 does not have to include any of the management / control agent unit 133, the basic function unit 132, and the extended function unit, as in the first example of the architecture. The device-independent application 130 may further include functional units other than the management / control agent unit 133, the basic function unit 132, and the extended function unit. Further, it is preferable that the extended function unit can be added, deleted, replaced or changed without affecting other functions, as in the first example of the architecture.

The basic function unit 132 may be included as a part of each extended function unit, or may be replaced by a lower level of the middleware 120. If the extended function unit includes the basic function unit 132, or if the lower level of the middleware 120 replaces the basic function unit 132, or if it is a combination thereof, the device-independent application 130 does not include the basic function unit 132. Good.
Further, a part of the basic function unit 132 may also be replaced by the device-dependent application unit 160, which is a lower level of the middleware 120. When the management / control agent unit 133 automatically sets according to a predetermined setting, it is not necessary to input / output information to / from the EMS 140. Further, when the management / control agent unit 133 does not have the management setting function and the other device-independent application 130, the basic function unit 132, or the device-dependent unit 110 has the management setting function, the device-independent application 130 manages / controls. The control agent unit 133 may not be provided.
The EMS 140 and the device-independent application 130 may be directly input / output. When the lower level of the middleware 120 replaces all of the basic function unit 132, the device-independent application 130 does not have to include the basic function unit 132.

In the communication device shown in FIG. 2, the device-dependent application unit 160 may input / output information via the middleware 120, or may directly input / output information from the management / control agent unit 133, or both. Information may be input / output to / from any of them, or may be directly input / output to / from EMS140. Further, when the device-dependent application unit 160 is automatically set according to a predetermined setting without receiving communication from the EMS 140 and can acquire management and control information from the EMS 140 via the middleware 120, there is no device. The dependent application 130 does not have to include the management / control agent unit 133.

The device-independent application 130 inputs / outputs information via the middleware 120 at least between the hardware unit (PHY) 111 and the hardware unit (MAC) 112 of the device-dependent unit 110 or between the software unit. The device-independent application 130 inputs / outputs to and from each other via the middleware 120 as needed. In particular, when the device-independent application 130 executes control or management according to the information input / output to / from the EMS 140, the device-independent application 130 inputs the information to / from the management / control agent unit 133 that receives the communication from the EMS 140. Output.
The NE management / control unit 115 inputs / outputs NE management information and control information to / from the management / control agent unit 133 via the middleware 120. The NE management / control unit 115 may directly input / output NE management information and control information to / from the EMS 140 without going through the middleware 120.

The device-dependent application unit 160 inputs / outputs NE management information and control information to / from the management / control agent unit 133. The device-dependent application unit 160 may directly input / output information to / from the EMS 140 without going through the management / control agent unit 133. The management / control agent unit 133 inputs / outputs information to / from the EMS 140, the middleware 120, and the device-dependent application unit 160. The middleware 120 inputs / outputs NE management information and control information to / from the NE management / control unit 115.
The NE management / control unit 115 may directly input / output NE management information and control information to / from the EMS 140 without going through the middleware 120. The middleware 120 inputs / outputs information to / from the device-independent application 130 via the device-independent API 21, and the OAM unit 114, the driver, the firmware, the hardware unit (PHY) 111, and the hardware of the device-dependent unit 110. Information is input / output to / from the unit (MAC) 112 via the device-dependent API 23.

The middleware 120 is input as it is or in a predetermined format as in the middleware 120 shown in FIG. It is desirable that the device-independent API 21 is provided in the middleware 120 in advance in anticipation of an extended function unit to be added later, but if necessary, the device-independent API 23 and other device-independent apps 130 are suppressed from being modified. You may add or delete with.

(Third example of architecture)
FIG. 3 is a diagram showing a third example of the architecture of the communication device. In FIG. 3, instead of the middleware 120 described in the first example of the architecture shown in FIG. 1, the basic function unit 132 includes the hardware unit (PHY) 111, the hardware unit (MAC) 112, and the extended function unit. Input / output. The other device-independent application 130 is the same as the first example of the architecture.

Compared to the first example of the architecture, the third example creates middleware 120 with a device-dependent API for each device that differs in at least one of the compliant standards, generations, methods, systems, device types, and manufacturing vendors. No need. As a result, the communication device of the third example of the architecture has the effect of generalizing and porting more functions between generations between devices, facilitating verification of connectivity, and making the functions of the devices robust.

The communication device according to the third example of the architecture includes a device-dependent unit 110 and a device-independent application 130. The device-dependent section 110 includes a hardware section (PHY) 111 and a hardware section (MAC) 112, and a hardware section (PHY) 111 and a hardware section (MAC) 112, which depend on a compliant standard or a device manufacturing vendor. It is equipped with a software unit such as a driver and firmware that drives the system. The driver or the like hides the difference in the device-dependent unit 110.

The device-independent application 130 includes an extended function unit and a basic function unit 132. The basic function unit 132 is device-dependent by the device-independent API 27 (porting IF) via a driver that hides the difference between the hardware unit (PHY) 111 and the hardware unit (MAC) 112 and the device-dependent software unit. Connect with unit 110. The device-independent application 130 uses a driver that hides the difference between the hardware unit (PHY) 111 and the hardware unit (MAC) 112 and the device-dependent software unit, and then the hardware unit (PHY) 111 and the hardware unit. Data is input and output between (MAC) 112 and the device-dependent software unit.

The basic function unit 132 and the extended function unit are connected via a device-independent API 22 (expansion IF). The basic function unit 132 and the device-dependent unit 110 are connected via the device-independent API 27. The basic function unit 132 in the device-independent application 130 inputs / outputs information to / from the hardware unit (PHY) 111, the hardware unit (MAC) 112, and the extended function unit instead of the middleware 120. ..
The device-independent application 130 inputs / outputs to and from each other via the basic function unit 132 as needed. The extended function unit of the device-independent application 130 inputs / outputs information via the basic function unit 132 and the device-independent API 27. The basic function unit 132 inputs and outputs information via the device-independent application 130 and the device-independent API 27, and the device-dependent unit 110 OAM unit 114, driver, firmware, hardware unit (PHY) 111, and hardware unit ( Information is input / output via the MAC) 112 and the device-independent API 27.

Similar to the middleware 120 shown in FIG. 1, the basic function unit 132 inputs operation information as it is or in a predetermined format. For example, in the case of another device-independent application 130, the basic function unit 132 converts each into the device-independent API format of the input format, and the device-dependent OAM unit 114, the driver, the firmware, and the hardware unit are used. If there is, the operation information is input after being converted into the device-independent API format of the input format, or after being terminated and performing a predetermined process. At the time of input, the basic function unit 132 deletes unnecessary input information at each input destination, and if there is insufficient information, collects and supplements it via another device-independent API or device-independent API. Is desirable. However, the basic function unit 132 may broadcast or multicast the input to the input destination to broadcast the input to the related application or the like.

The device-independent application 130 includes, for example, an extended function unit and a basic function unit 132. The device-independent application 130 does not have to include either the extended function unit or the basic function unit 132. The device-independent application 130 may further include functional units other than the extended function unit and the basic function unit 132. For example, when the extension function unit is unnecessary, the device-independent application 130 does not have to include the extension function unit.

It is preferable that the extended function unit can be added or deleted independently without affecting other functions. For example, when a multicast service or power saving support is set as an extension function unit according to a service request, the extension function unit is added as needed when it is needed, and deleted as needed when it is no longer needed. It may be replaced or changed according to the change.
It is desirable that the device-independent API 22 is provided in advance in the basic function unit 132 in anticipation of an extended function unit to be added later, but if necessary, the device-independent API 22, the device-independent API 27, and other device-independent API 22 are independent. It may be added or deleted in a form that suppresses the modification of the application 130.

(4th example of architecture)
FIG. 4 is a diagram showing a fourth example of the architecture of the communication device. The difference between the fourth example of the architecture and the third example of the architecture is that the communication device includes the device-dependent application unit 160 under the basic function unit 132. As described above, the communication device of the fourth example of the architecture has an effect that the configuration of the basic function unit 132 can be simplified by providing the device-dependent application unit 160.

The communication device shown in FIG. 4 includes a device-dependent unit 110 and a device-independent application 130. The device-dependent section 110 includes a hardware section (PHY) 111 and a hardware section (MAC) 112, and a hardware section (PHY) 111 and a hardware section (MAC) 112, which depend on a compliant standard or a device manufacturing vendor. It has a software unit such as a driver and firmware to be driven, and a device-dependent application unit 160 that drives at least a part of the device-dependent unit 110. The device-independent application 130 includes the portable IF and the hardware unit (PHY) 111 and the hardware unit (MAC) 112 via a driver that hides the difference between the device-dependent software or the portable IF and the device-dependent application unit. It is a general-purpose device-independent application 130 that executes device-independent processing via the 160. The basic function unit 132 in the device-independent application 130 and the device-dependent application unit 160 in the device-dependent unit 110 are connected via the device-independent API 27. The device-dependent application unit 160 and the device-dependent unit 110 are connected via the device-dependent API 24.
In the basic function unit 132 in the device-independent application 130, the basic function unit 132 performs input / output with the hardware and the extended function unit instead of the middleware 120. The basic function unit 132 may include a management / control agent unit 133 equivalent to receive communication from the EMS 140, or may include a management / control agent unit 133 as an extended function unit.

The basic function unit 132 inputs / outputs via the device-independent application 130 and the device-independent API 22 (expansion IF), and the device-dependent unit 110 OAM unit 114, driver, firmware, hardware unit (PHY) 111, and hardware. Input / output is performed via the driver of the device-dependent unit 110 that hides the difference between the wear unit (MAC) 112, the device-independent API 27 (porting IF), and the device-dependent unit 110, or the device-dependent application unit 160 and the device-dependent API 24.
Similar to the middleware 120 shown in FIG. 1, the basic function unit 132 inputs as it is or in a predetermined format. Similar to the third example of the architecture, the basic function unit 132 may include a management / control agent unit 133 equivalent to receive communication from the EMS 140, and a management / control agent unit 133 as an extension function unit is provided. You may.

The device-independent application 130 includes, for example, an extended function unit and a basic function unit 132. The device-independent application 130 does not have to include either the extended function unit or the basic function unit 132, as in the third example of the architecture. The device-independent application 130 may further include functional units other than the extended function unit and the basic function unit 132, as in the third example of the architecture. It is preferable that the extended function unit can be added, deleted, replaced or changed independently of each other without affecting other functions, as in the third example of the architecture. A part of the basic function unit 132 may be replaced by the device-dependent application unit 160. The device-dependent application unit 160 inputs / outputs information directly from the basic function unit 132, but even if the information is input / output to / from the EMS 140 as it is or after a predetermined conversion, the information is input / output to / from the EMS 140 without going through the basic function unit 132. Good.

Similar to the first example of the architecture shown in FIG. 1, it is desirable that the device-independent API 22 is provided in advance in the basic function unit 132, assuming an extended function unit to be added later. Dependent API 27, other device-independent application 130, device-dependent application unit 160, or device-dependent API 24 may be added or deleted as necessary in a form of suppressing modification.

(5th example of architecture)
The upper right figure of FIG. 5 is a diagram showing a fifth example of the architecture. The lower right figure of FIG. 5 corresponds to the first to fourth examples of the architecture. In this example, the communication device consists of existing / commercial hardware and external hardware. For example, existing / commercial hardware is a non-general-purpose device-dependent part that depends on the device, and there is no middleware that hides the difference between hardware and software on the external hardware, and no general-purpose device whose operation does not depend on the device. It has dependent apps. Therefore, the device-dependent section (vendor-dependent section) below the middleware in the figure is a functional section that depends on the standard to which the device of the communication device conforms and the manufacturing vendor of the device. Further, the device-independent application 130 is a functional unit that does not depend on the standard to which the device of the communication device conforms or the manufacturing vendor of the device.

The middleware and the device-independent application are connected via a device-independent API, which is a device-independent input / output IF. For example, the software part, OAM, hardware part (PHY) and hardware part (MAC) of the device-dependent part, and the middleware on the external hardware are the device-dependent API which is the input / output IF depending on the device and the existing one. / Connected via device-to-device connection between market hardware and external hardware.

This architecture facilitates the flexible and quick addition of extended function parts (unique function parts) by device-independent applications, and can provide communication services in a timely manner. Here, the device-dependent unit may be maintenance operation, access control, physical layer processing, and optical modular as shown in FIG. 5, and depends on the configuration of the device itself.

For example, it was decided to prioritize functions that are frequently updated, such as DBA, which improves main signal priority processing and line utilization efficiency, or functions that contribute to communication service differentiation, and make them device-dependent or device-independent apps. You may. Further, it may be a device-independent application because the difference is small with respect to at least one of the standards, generations, methods, systems, device types, and manufacturing vendors to which the devices to be shared are compliant.

Any of the compliant standards, generations, methods, systems, equipment types, manufacturing vendor features, even if it is not optimal for at least one of the compliant standards, generations, methods, systems, equipment types, and manufacturing vendors. In order to generalize the above, a common IF for executing the function may be used. The common IF may include IFs and parameters that are not used in any of the standards, generations, methods, systems, device types, and manufacturing vendors to which the device-dependent part complies.

At least one of the middleware, the driver of the device-dependent part, and the device-dependent application part (vendor-dependent application part), the conversion function part that converts IFs and parameters to correspond to the device-dependent part, and the insufficient IF It may be further provided with a function unit that is automatically set according to the parameters and parameters.
The device-dependent section includes a hardware section and a software section. The software section executes device-dependent drivers, firmware, applications, and the like.
The device-dependent unit may not include a PMD connected to a physical medium, a MAC, a PMA for serializing data, and a part of a PCS or PHY for encoding data. For example, it may have only optical-related functions without providing low-level signal processing such as modulation / demodulation signal processing, forward error correction (FEC), code decoding processing, and encryption processing.

The device-independent application is, for example, a management / control agent unit that acquires data from EMS, an extended function unit, and a basic function unit. Hereinafter, matters common to the extended function unit will be referred to as "extended function unit" by omitting a part of the reference numerals. EMS is, for example, a controller that controls network elements. The device-independent application does not have to include any of the management / control agent unit, the extended function unit, and the basic function unit.

The device-independent application may further include configurations other than the management / control agent unit, the extended function unit, and the basic function unit. For example, when the extension function unit is unnecessary, the device-independent application does not have to include the extension function unit. Further, the device-independent application may include one or more extended function units.
It is preferable that the extended function unit can be added, deleted, replaced or changed independently without unnecessarily affecting other functions. For example, the extension function unit may be added, deleted, replaced, or changed as appropriate when, for example, a multicast service or an extension function unit that executes power saving measures is required according to a service request.

The basic function unit may be included in the device-independent application as a part of the extension function unit, or may be replaced by a function unit lower than the middleware. When the extended function part includes the basic function part, the device-independent application does not have to include the basic function part. When a function part lower than the middleware replaces the basic function part, the device-independent application does not have to include the basic function part. When the extended function unit includes the basic function unit and the function unit lower than the middleware replaces the basic function unit, the device-independent application does not have to include the basic function unit.

When the management / control agent unit automatically sets according to a predetermined setting without receiving communication from the EMS, the management / control agent unit does not have to input / output with the EMS. Furthermore, if the management / control agent unit does not have a management setting function and other device-independent apps, basic function units, or device-dependent units have management setting functions, the device-independent application has a management / control agent unit. It does not have to be.

Information may be directly input / output between the EMS and the device-independent application. Further, the device-dependent unit does not have to include the NE management / control unit and the IF of the NE management / control unit.
The basic function unit may be included in the device-independent application as a part of the extension function unit, or may be replaced by a lower function unit of the middleware. When the extended function part includes the basic function part, when the lower function part of the middleware replaces the basic function part, or when they are a combination thereof, the device-independent application does not have to include the basic function part. Further, a part of the basic function part may be replaced by the device-dependent application part of the lower function part of the middleware.

When the management / control agent unit automatically sets according to a predetermined setting, it is not necessary to input / output information to / from the EMS. Furthermore, if the management / control agent section does not have the management setting function and other device-independent apps or the basic function section or device-dependent section has the management setting function, the device-independent app does not have the management / control agent section. You may. Information may be directly input / output between the EMS and the device-independent application.

The following is an example of input / output between the device-independent application and the device-dependent part. For example, the DBA application unit and the protection application unit input / output information to and from the embedded OAM engine of the TC layer. The DWBA application and the ONU registration authentication application unit input / output information to and from the PLOAM engine of the TC layer. The power saving application unit inputs / outputs information to and from the OMCI and the L2 main signal processing function unit (L2 function unit). The MLD proxy application unit inputs and outputs information to and from the L2 function unit. The low-speed monitoring application (OMCI) inputs and outputs information to and from OMCI. The OMCI and L2 functional units operate the XGEM framer and encryption. Here, the DWBA and the DBA may be separate, integrated, or combined. For example, the management / control agent unit is an application unit of the maintenance operation function, and inputs / outputs information to and from EMS, which is an NE controller or the like for the NE management / control unit.

Device-independent apps are device vendors, methods, device types, device generations, such as ITU-T G.M. TWDM-PON conforming to the 989 series and ITU-T G. XG-PON conforming to the 987 series and ITU-T G. G-PON conforming to the 984 series and ITU-T G. It is an application that operates regardless of any of the 983 series compliant BPON. The device-independent application is at least the difference between the device vendor, method, device type, device generation, for example, 10GE-PON conforming to IEEE802.3av and IEEE1904.1, and GE-PON conforming to IEEE802.3ah. It is an application that works regardless of either.

As an extension function application, only for some vendors, methods, types, and generation devices, and for some vendors, methods, types, and generation devices via device-independent API. It may include an app that drives the features it provides.
The management / control agent unit inputs / outputs to and from EMS and middleware. The middleware inputs and outputs NE management information and control information to and from the NE management / control unit. The NE management / control unit may directly send / receive NE management information and control information to and from the EMS without going through middleware, or may send / receive NE management information and control information via the management / control agent unit. Good.

The middleware inputs and outputs information via a device-independent application and a device-independent API. The middleware inputs / outputs information to / from the OAM unit, the driver, the firmware, the hardware unit, or the hardware unit of the device-dependent unit via the device-dependent API. The middleware outputs the input information as it is or in a predetermined format. For example, if the output destination is each part of the device-independent API, the middleware converts the information into the input format of each part of the device-independent API. If the output destination is the OAM part, driver, firmware, hardware part or hardware part of the device-dependent part, the middleware is determined after converting to the device-dependent API format of the format to be input to each, or by terminating. After performing the processing of, the information is sent to the output destination.

It is desirable that the middleware deletes unnecessary input information at each input destination at the time of input, and if there is insufficient information, collects and supplements it via another device-independent API or device-dependent API. In addition, when inputting to the middleware, it may be broadcast or multicast to broadcast to the related application or the like.
The middleware and device-dependent parts are illustrated as a single unit, but each may be composed of a plurality of parts. When the hardware of the device-dependent part includes a plurality of processors, the middleware may input / output across the processors and the hardware by using interprocessor communication or the like. Device-independent applications or device-independent applications may be arranged as an execution program such as DLL in the user space on a single processor, or may be arranged in the user space on a plurality of processors. ..

Further, the device-independent application may be arranged in the kernel space after securing the input / output IF such as API, or may be arranged together with the middleware having the IF that can be independently replaced with the firmware or the like, or the firmware. You may recompile it by incorporating it into the software. The user space and kernel space may be any combination for each device-independent application.
A device-independent application that supports the same function may be implemented in both user space and kernel space. In this case, for example, it may be switched and either one may be selected, both may be processed in cooperation, or the actual processing may be performed by only one of them. The same applies to the software of the device-dependent part.

Desirably, the more high-speed processing such as main signal processing, DBA processing, and low-layer signal processing is required, the more there is a trade-off with the immediacy of expandability / replacement, but high-speed processing with less overhead is expected. It is desirable to incorporate it in kernel space or firmware. The processor in which the device-dependent application unit is placed also has the user space of the processor that performs the actual processing or a processor in the vicinity thereof from the viewpoint of the influence on other programs due to the limitation of the bus and speed due to the communication between the processors and the occupation of the communication path. It is desirable to place it in the kernel space or on the firmware. However, in order to reduce the capacity of the processor that performs the actual processing or a processor in the vicinity thereof, the communication cost due to the inter-processor communication increases, but the processing may be performed by a remote processor.

It is desirable that the device-independent API is provided in the middleware in advance assuming the extension function part to be added, but it is added or deleted as necessary in a form that suppresses the modification of the device-dependent API and other device-independent apps. May be done.

(6th example of architecture)
The sixth example of the architecture is the hardware part (PHY) and the hardware part (MAC), and the hardware part (PHY) and the hardware part (MAC) depending on the standard conforming as the device-dependent part or the device manufacturing vendor. It is provided with a software unit such as a driver / firmware that drives the device, and a device-dependent application unit that drives at least a part of the device-dependent unit.

The device-dependent application unit and the device-dependent unit are connected via the device-dependent API. The device-dependent application unit may include a management / control agent unit that receives communication from the EMS. The device-dependent API may be added or deleted as necessary in a form that suppresses the modification of the device-dependent application unit and the device-dependent API.

The configuration of the communication device shown in the first to sixth examples of the architecture of the communication device is described on the premise of the IEEE of the PON conforming to the ITU-T recommendation such as TWDM-PON, but it is an ONU. It may be either an OLT or an ONU of an PON conforming to the ITU-T recommendation other than TWDM-PON, or it may be an IEEE standard compliant PON such as GE-PON and 10GE-PON, and TC. The same applies if the layer or PMD layer is read as the corresponding layer.

Hereinafter, TWDM-PON is a PON multicast function, a power saving control function, a frequency / time synchronization function, a protection function, a maintenance operation function, an L2 main signal processing function, a PON access control function, and a PON main signal. A case where the processing function is mainly provided will be described as an example. Hereinafter, the PON multicast function, the power saving control function, the frequency / time synchronization function, the protection function, the maintenance operation function, the L2 main signal processing function, the PON access control function, and the PON main signal processing function are described. It is called "8 main functions".

FIG. 6 is a diagram showing an example of the configuration of the communication device and the external server 16. The communication system includes a communication device and an external server 16. The communication device includes at least a part of a transmission / reception unit 11 (TRx), a switch unit 12 (SW), a switch unit 13 (SW), a control unit 14, and a proxy unit 15. The communication device may include an external server 16.
FIG. 6 shows a configuration in which a transmission / reception unit 11 that transmits / receives (communicates) optical signals of different wavelengths (λA to λN) is connected to the same switch unit 12, but the embodiment 1-1 is not limited to this. For example, in addition to the configuration in which the transmission / reception unit 11 for transmitting / receiving optical signals of different wavelengths (λA to λN) is connected to the same switch unit 12, the transmission / reception unit 11 for transmitting / receiving optical signals of the same wavelength is the same switch. It may be connected to the unit 12, or among the transmission / reception units 11 that transmit / receive optical signals of different wavelengths (λA to λN), a plurality of transmission / reception units 11 having at least some wavelengths are connected to the same switch unit 12. Alternatively, the transmission / reception unit 11 may be a part or all of the transmission / reception unit 11 that only transmits or receives.

A communication device such as an OLT may include a transmission / reception unit 11 to a control unit 14, and may further include an external server 16 in addition to these. Further, the OSU may be a transmission / reception unit 11, or may include a switch unit 12 (SW) or a switch unit 13 (SW) in addition to the transmission / reception unit 11. The communication system of the communication system configuration (1-1) includes a transmission / reception unit 11 (TRx), a switch unit 12 (SW), a switch unit 13 (SW), a control unit 14, a proxy unit 15, and an external server 16. (Fig. 6).

When the communication device is an OLT, the OLT may be composed of a transmission / reception unit 11 (TRx), a switch unit 12 (SW), a switch unit 13 (SW), and a control unit 14, or the transmission / reception unit 11 (TRx), a switch unit 12 (SW), a switch unit 13 (SW), a control unit 14, and an external server 16 may be configured. The OSU may be composed of a transmission / reception unit 11 (TRx), a transmission / reception unit 11 (TRx), a switch unit 12 (SW), a transmission / reception unit 11 (TRx), and a switch. It may be composed of a part 13 (SW). A transmission / reception unit 11 (TRx) for transmitting / receiving optical signals having different wavelengths (λA to λN) is connected to the switch unit 12. The transmission / reception unit 11 (TRx) performs autonomous control or is controlled by other components such as the switch unit 12 (SW), the switch unit 13 (SW), the control unit 14, the proxy unit 15, or the external server 16. Alternatively, it is controlled by an instruction transferred via other components such as the switch unit 12 (SW), the switch unit 13 (SW), the control unit 14, the proxy unit 15, or the external server 16. The transmission / reception unit 11 (TRx) performs a VLAN (Virtual Local Area Network), priority, disposal priority, or destination for a part or all of the traffic of the ODN (Optical Waste Network) or the switch unit 12 (SW) according to a predetermined procedure. Addition, deletion, replacement of tags of at least a part or a combination thereof, or processing of at least one or a combination thereof of aggregation, distribution, distribution, duplication, folding or transparency without changing tags. I do.

It should be noted that the upstream traffic is not always aggregated. In the configuration of the communication system configuration (1-1), the switch unit 12 (SW) mainly distributes for each wavelength, but represents aggregation, distribution, duplication, folding, transmission, VID (Virtual LAN Identifier), and priority disposal. Tags such as tags may be added or replaced. In the configuration of the communication system configuration (1-2) described later, the upstream traffic is mainly aggregated, but distribution, distribution, duplication, return, transparency, tag addition or tag replacement may be performed. Downstream traffic may also be aggregated, distributed, sorted, duplicated, folded, transparent, tagged or tagged, or at least in some combinations. Which one to use is decided according to the service policy. This also applies to the subsequent communication system configurations.

The switch unit 12 (SW) is connected to the switch unit 13 (SW). The switch unit 12 (SW) performs autonomous control or is controlled by other components such as the transmission / reception unit 11 (TRx), the switch unit 13 (SW), the control unit 14, the proxy unit 15, or the external server 16. Alternatively, it is controlled by an instruction transferred via other components such as a transmission / reception unit 11 (TRx), a switch unit 13 (SW), a control unit 14, a proxy unit 15, or an external server 16. The switch unit 12 (SW) attaches to a part or all of the traffic of the transmission / reception unit 11 (TRx) or the switch unit 13 (SW) to at least a part of the VLAN, priority, discard priority, destination, etc. according to a predetermined procedure. Addition, deletion, replacement of tags of the combination, or at least part of aggregation, distribution, distribution, duplication, folding, transparency or tagging or tag replacement or a combination thereof, without changing the tags. Perform processing. This also applies to the subsequent communication system configurations.

The switch unit 12 (SW) is not always controlled. There are cases where at least one of the proxy units 15 is controlled from the transmission / reception unit 11 and cases where control information is transferred from the transmission / reception unit 11 to at least one of the proxy units 15 without being controlled. As the transfer source, for example, there is a proxy unit 15 or an external server 16. In addition, the proxy unit 15 may move autonomously from the transmission / reception unit 11. This also applies to the subsequent communication system configurations.

The switch unit 13 (SW) is connected to the proxy unit 15 directly or via a concentrating SW or the like. This concentrating SW performs at least a part of aggregation, distribution, distribution, duplication, folding or transmission of traffic from or to a plurality of OLTs. The switch unit 13 (SW) performs autonomous control or is controlled by other components such as the transmission / reception unit 11 (TRx), the switch unit 12 (SW), the control unit 14, the proxy unit 15, or the external server 16. Alternatively, it is controlled by an instruction transferred via other components such as a transmission / reception unit 11 (TRx), a switch unit 12 (SW), a control unit 14, a proxy unit 15, or an external server 16. The switch unit 13 (SW) is used for a part or all of the traffic of the switch unit 12 (SW) or the proxy unit 15 in accordance with a predetermined procedure, at least a part of VLAN, priority, discard priority, destination, etc. Add, delete, replace tags, or process at least part of aggregation, distribution, distribution, duplication, folding or transparency, or a combination thereof, without changing tags.

The control unit 14 is a transmission / reception unit 11 (TRx), a switch unit 12 (SW), a switch unit 13 (SW), a proxy unit 15 or an external server 16, an external operating system (not shown), a controller (not shown) or an external unit. It is connected to the device (not shown). The control unit 14 controls other components such as the transmission / reception unit 11 (TRx), the switch unit 12 (SW), the switch unit 13 (SW), the proxy unit 15 or the external server 16, or the transmission / reception unit 11 (TRx). , The instruction is transferred via other components such as the switch unit 12 (SW), the switch unit 13 (SW), the proxy unit 15, or the external server 16.

The proxy unit 15 shown in FIG. 6 may be installed on the data path from the OLT to the OLT. However, it is not always directly connected because another device (for example, a concentrating SW that aggregates / distributes traffic from or to the OLT) may intervene between them. As a control flow, the proxy unit 15 may be provided in any of the transmission / reception unit 11 (TRx), the switch unit 12 (SW), the switch unit 13 (SW), the control unit 14, and the external server 16.

The proxy unit 15 is connected to a device (not shown) on the upper side directly or via a concentrating SW or the like. This concentrating SW performs at least a part of aggregation, distribution, distribution, duplication, folding or transmission of traffic from or to a plurality of OLTs. The proxy unit 15 performs autonomous control or is controlled by other components such as the transmission / reception unit 11 (TRx), the switch unit 12 (SW), the switch unit 13 (SW), the control unit 14, or the external server 16. Alternatively, it is controlled by an instruction transferred via other components such as the transmission / reception unit 11 (TRx), the switch unit 12 (SW), the switch unit 13 (SW), the control unit 14, or the external server 16. The proxy unit 15 applies to a part or all of the traffic of the switch unit 13 (SW) or the device on the upper side (not shown), at least a part of the VLAN, priority, discard priority, destination, etc., or a part thereof according to a predetermined procedure. Add, delete, replace tags of combinations, or process at least part of aggregation, distribution, distribution, duplication, folding or transparency, or combinations thereof, without changing tags.

The external server 16 is a transmission / reception unit 11 (TRx), a switch unit 12 (SW), a switch unit 13 (SW), a control unit 14, a proxy unit 15, an external operating system (not shown), a controller (not shown), or an external server. It is connected to the device (not shown). The external server 16 controls other components such as the transmission / reception unit 11 (TRx), the switch unit 12 (SW), the switch unit 13 (SW), the control unit 14, or the proxy unit 15, or the transmission / reception unit 11 (TRx). , The instruction is transferred via other components such as the switch unit 12 (SW), the switch unit 13 (SW), the control unit 14, or the proxy unit 15.

The transmission / reception unit 11 (TRx), the switch unit 12 (SW), the switch unit 13 (SW), the control unit 14, the proxy unit 15 or the external server 16 are the transmission / reception unit 11 (TRx), the switch unit 12 (SW), and the switch unit. 13 (SW), a part of the traffic of other components such as the proxy unit 15 or the external server 16, or all of the traffic itself or a copy thereof, a part of the received traffic, all of the traffic received, Other components such as the transmission / reception unit 11 (TRx), the switch unit 12 (SW), the switch unit 13 (SW), the proxy unit 15 or the external server 16 for the response to the partially or completely rewritten traffic or the received traffic , It may be transmitted to an external operating system (not shown), a controller (not shown) or an external device (not shown).

It should be noted that the element may not be included as appropriate, and the interaction with the element not included is skipped and exchanged with the element after that, for example. You may communicate with each other with the hub corpse.
In the communication system of the communication system configuration (1-2), the transmission / reception unit 11 (TRx) (λA) that transmits / receives optical signals of the same wavelength instead of different wavelengths is further applied to the configuration of the communication system configuration (1-1). ~ ΛA), transmission / reception unit 11 (TRx) (λB to λB), ..., Transmission / reception unit 11 (TRx) (λN to λN) are connected to the switch unit 12, respectively. Further, a plurality of transmission / reception units 11 having at least a part of the transmission / reception units 11 having different wavelengths may be connected to the switch unit 12. Others are similar.

In the optical access system according to FIG. 7, the ITU-T G.I. Compliant with the 989 series. In FIG. 7, the controller and the external device are not included in the OLT, but are described to illustrate communication with the FASA application API. The logical model is composed of a FASA application and a FASA platform that provides a FASA application API to the FASA application. The FASA platform includes middleware for FASA applications. The middleware for the FASA application API absorbs the differences in the vendors and methods of the hardware and software that make up the FASA platform. A vendor- and method-independent FASA application API set is defined on the middleware for the FASA application API, and the functions required for each service or each telecommunications carrier are realized by replacing the FASA application. Communication between FASA applications and setting management by a controller or the like are performed via middleware for FASA application API. In addition, it may not be possible to go through the middleware for FASA application API. The FASA application API set is a common API group used in the FASA application, and the API required for each FASA application is selected from the API set and used.

The connection relationships shown below are examples, and the intervening connections may be non-intervening connections, only a part of a plurality of connection relationships may be connected, or other connections may be used. .. This also applies to other explanations. This also applies to other explanations. The EMS that functions as a NE controller is an OLT setting management system such as NE-Ops, and is a setting management application (for example, a low-speed monitoring application (EMS-IF)) and a setting / management via an IF conversion application via middleware. App) is placed. The IF conversion application corresponds to an SBI application that converts an SBI (South Band Interface) command, which is a control IF for a Network Entity such as an OLT, from an EMS such as a NE controller. Here, the IF conversion application is supposed to perform IF conversion, but if the low-speed monitoring application (EMS-IF) and the setting / management application are equipped with an API that does not require IF conversion or IF conversion, the IF conversion application can be used. You don't have to prepare. The low-speed monitoring application (EMS-IF) connected to the L2 (layer 2) function and the setting / management application are connected to NE control / management that performs EMS, NE management, etc. via middleware. The low-speed monitoring application (OMCI), the MLD proxy application (multicast application), and the power saving application are each connected to the L2 function via middleware.

The protection app is connected to the PLOAM Engine and Embedded OAM Engine via middleware. The power saving app is connected to the OMCI and PLOAM Engine via middleware. The ONU registration authentication application and the DWBA application are connected to the PLOAM Engine via middleware, and the DBA application is connected to the Embedded OAM Engine via middleware. The power saving application may be operated between the protection application, the ONU registration authentication application, the DWBA application, and the DBA application via middleware. Input from an external device is connected to the DBA application via middleware. Note that these connections are examples, and input from an external device may be connected to an application other than the DBA application, such as a protection application or a DWBA application. Further, the input from the external device may be IF-converted via the IF conversion application via the middleware, or may be connected to the DBA application or the like via the setting / management application via the middleware.

FIG. 8 is a diagram showing a flow of signals / information between functional units in a communication device. The communication devices shown in the figure include a PON main signal processing function unit 300, a PMD unit 310, a PON access control function unit 320, a maintenance operation function unit 330 (PLOAM processing, OMCI processing), and an L2 main signal processing function unit. It includes a 340, a PON multicast function unit 350, a power saving control function unit 360, a frequency / time synchronization function unit 370, and a protection function unit 380.

The PON main signal processing function unit 300 has a PON main signal processing function. The PON main signal processing function is a group of functions for processing a main signal transmitted and received to and from the ONU, and includes generation and separation of PON frames, forward error correction (FEC), and the like. The PON access control function unit 320 has a PON access control function. The PON access control function is a group of control functions for transmitting and receiving the above-mentioned main signal, and includes dynamic bandwidth allocation, ONU registration authentication, and the like.

The maintenance / operation function unit 330 (PLOAM processing, OMCI processing) has a maintenance / operation function. The maintenance operation function is a group of functions for smooth maintenance and operation of services by access devices, such as functions for performing device settings of ONUs and OLTs (OSUs and switches), software updates, management of devices and services, and various types. It includes a function to monitor whether the function is operating normally, a function to actively issue an alarm when an abnormality occurs, a test function to investigate the range and cause when an abnormality occurs, and the like. In addition, the maintenance operation function is connected to the maintenance operation system that manages a large number of access devices, and realizes smooth maintenance operation even remotely.

The L2 main signal processing function unit 340 has an L2 main signal processing function. The L2 main signal processing function is a group of functions that transfers and processes a main signal between a PON side port and an SNI side port, and includes functions such as MAC address learning, VLAN control, priority control, and traffic monitoring. The PON multicast function unit 350 has a PON multicast function. The PON multicast function is a group of functions that forwards a multicast stream received from the SNI side to an appropriate user, and includes a function of identifying and distributing the multicast stream and setting an ONU filter.

The power saving control function unit 360 has a power saving control function. The power saving control function is a group of functions for reducing the power consumption of ONUs and OLTs. In addition to the power saving function specified in the standardization, the impact on the service is minimized by linking with the traffic monitor. However, it includes functions for maximizing the effect. The frequency / time synchronization function unit 370 has a frequency / time synchronization function. The frequency / time synchronization function is a group of functions for providing accurate frequency synchronization and time synchronization to the devices under the ONU, and has a function of subordinating its own real-time clock to a higher-level device and an ONU using a PON frame. Includes a function to notify time information.

The protection function unit 380 has a protection function. The protection function is a group of functions for continuing the service by switching or taking over from the active system to the standby system when a failure is detected in a configuration with multiple hardware such as between switches and OSUs. , Includes functions such as detection of switching triggers and execution of switching processing. In addition, the protection function provides a function for continuing to operate in degenerate operation without completely stopping the service when a failure is detected or when switching is performed manually. The PMD unit 310 has functions other than the eight main functions.

Even if the PON main signal processing function unit 300 is connected to the PMD unit 310, the PON access control function unit 320, the maintenance operation function unit 330 (PLOAM processing, OMCI processing), and the L2 main signal processing function unit 340. Good. The PON multicast function unit 350 is connected to a group consisting of a PON main signal processing function unit 300, a PMD unit 310, a PON access control function unit 320, a maintenance operation function unit 330, and an L2 main signal processing function unit 340. It may be. The power saving control function unit 360 is connected to a group consisting of a PON main signal processing function unit 300, a PMD unit 310, a PON access control function unit 320, a maintenance operation function unit 330, and an L2 main signal processing function unit 340. You may be doing it. The frequency / time synchronization function unit 370 is composed of a PON main signal processing function unit 300, a PMD unit 310, a PON access control function unit 320, a maintenance operation function unit 330, and an L2 main signal processing function unit 340. It may be connected. The protection function unit 380 is connected to a group consisting of a PON main signal processing function unit 300, a PMD unit 310, a PON access control function unit 320, a maintenance operation function unit 330, and an L2 main signal processing function unit 340. You may.

FIG. 9 is a diagram showing an example of a functional configuration of the PON main signal processing function unit 300. The PON main signal processing function unit 300 includes PHY adaptation, framing, and service adaptation in the order of upstream signal processing (downlink processing is in the reverse direction) as processing constituting the PON main signal processing function. You may. These processes may consist of basic processes. The basic processing is synchronous block generation / extraction, scrambling / descramble, FEC decoding / encoding, frame generation / separation, GEM (G-PON Encapsulation Method) encapsulation, fragment processing, and encryption. ..

The PHY adaptation may include synchronous block extraction, descramble, and FEC decoding in the order of upstream signal processing. The PHY adaptation may include FEC encoding, scrambling, and synchronous block generation in the order of downlink signal processing.
The PON main signal processing function unit 300 may realize equivalent processing by a combination of basic processing without providing PHY adaptation, framing, or service adaptation processing. The processing of PHY adaptation, framing or service adaptation may be in a different order. The PHY adaptation may include, for example, an FEC process other than the PHY adaptation.

In the main function of the PON main signal processing function unit 300, when processing 10 Gbit / s / λ and 2.5 Gbit / s / λ for each wavelength, respectively, 10 Gbit / s / λ and 2.5 Gbit / s / λ, respectively. If the above stream processing processes a plurality of wavelengths, a plurality of wavelengths are required.

FIG. 10 is a diagram showing an example of a functional configuration of the PON access control function unit 320. As a process constituting the PON access control function of the PON access control function unit 320, it has ONU registration or authentication, DBA, and λ setting switching (DWA). These processes may consist of basic processes. For example, ONU registration or authentication consists of initial processing such as rangening, authentication deletion, registration, start / stop, and DBA includes bandwidth request reception, traffic measurement, history retention, allocation calculation, allocation processing, setting switching calculation, setting switching processing, and setting. All or some of the switching status grasping, λ setting switching is from all or some of the bandwidth request reception, traffic measurement, history retention, allocation calculation, allocation processing, setting switching calculation, setting switching processing, setting switching status grasping. It may be configured. Equivalent processing may be realized by a combination of basic processing without providing ONU registration or authentication, DBA, and λ setting switching (DWA). Moreover, the order may be changed.

In the main functions of the PON access control function unit 320, ONU high-speed activation, BWMap within the DBA cycle, non-instantaneous interruption λ setting switching, and the like are required as necessary. As an example of function sharing, as registration or authentication, time-critical range processing may be performed as a device-dependent part, and subsequent authentication or key exchange may be performed as an application. In DBA / λ setting switching, simple iterative processing may be performed as a device-dependent part, and reflection in the ideal state may be used as an application.
FIG. 11 is a diagram showing an example of a functional configuration of the L2 main signal processing function unit 340. As the processing constituting the L2 main signal processing function of the L2 main signal processing function unit 340, MAC learning, VLAN control, path control, bandwidth control, priority control, delay control, and Copy are included. These processes are basic processes such as address management, classifier (classifier, classification unit), modifier (modifier, change unit), Policer / Shaper (poliser / shaper), Cross Connect (cross connect), Queue (queue), and so on. It may consist of a Scheduler, a Copy, and a traffic monitor. Equivalent processing may be realized by a combination of basic processing without providing MAC learning, VLAN control, path control, bandwidth control, priority control, delay control, and copy. Moreover, the order may be changed.

In the main function of the L2 main signal processing function unit 340, when processing 10 Gbit / s / λ and 2.5 Gbit / s / λ for each wavelength, respectively, 10 Gbit / s / λ and 2.5 Gbit / s / λ, respectively. If the above stream processing processes a plurality of wavelengths, a plurality of wavelengths are required.

FIG. 12 is a diagram showing a first example of the functional configuration of the maintenance / operation function unit 330. The processes that make up the maintenance and operation functions of the maintenance and operation function unit 330 include ONU, OSU, OLT, or SW device settings (manual, batch, automatic, operation trigger), setting backup, FW update, device control (reset), and redundancy. Has configuration support. These processes may be composed of basic processes such as CLI-IF, device management IF, operation IF, general-purpose Config-IF (NETCONF, SNMP, etc.), and table management. Equivalent processing may be realized by a combination of basic processing without providing device setting, setting backup, FW update, device control, and support for redundant configuration. Moreover, the order may be changed.

The main functions of the maintenance and operation function unit 330 are within 100 milliseconds from receiving the instruction to sending the ACK, and within 200 milliseconds from receiving the instruction to sending the reflection completion notification (however, setting backup including data transfer and FW update are performed. It is required to comply with regulations such as scale (specified according to size and number of users). As an example of the division of functions, an application can be used except for the hardware Config, and the software and setting data can be used as an application on the external server 16 of FIG. 6 without being held by the ONU or OLT. It can also be realized by unifying commands and defining sequences.

FIG. 13 is a diagram showing a second example of the configuration of the function of the maintenance / operation function unit 330. The processes constituting the functions of the maintenance / operation function unit 330 include device status monitoring (CPU / memory / power supply / switching), traffic monitoring, alarm monitoring (ONU abnormality, OLT abnormality), and test (loopback). These processes may be composed of alarm notification, log recording, L3 packet generation / processing, and table management, which are basic processes. For device status monitoring, traffic monitoring, alarm monitoring, and testing, equivalent processing may be realized by a combination of basic processing. Moreover, the order may be changed.

The main functions of the maintenance and operation function unit 330 are required to comply with regulations such as a latency of 100 milliseconds or less. As an example of function sharing, only the notification / display IF is used as an app, and items that require monitoring (CPU load, memory usage, power status, power consumption, Ethernet (registered trademark) link status, etc.) are device-dependent parts. , Notification reading from the device-dependent part, notification network (NW) transmission, writing to a file, etc. can also be processed by an application that can turn off the IF.

FIG. 14 is a diagram showing a third example of the functional configuration of the maintenance / operation function unit 330. As a process constituting the maintenance operation function of the maintenance operation function unit 330, it has high-speed monitoring / control input / output (sleep instruction / reply, λ setting switching instruction / reply, etc.). As a means of this processing, a physical layer OAM (PLOAM: Physical Layer OAM) message and a bit display (Embedded OAM) in the header are used. These processes may be composed of PLOAM process, which is a basic process, Embedded OAM process, communication with the power saving control function unit 360, communication with the protection function unit 380, and communication with the PON access control function unit 320. For monitoring / control input / output that requires high speed, equivalent processing may be realized by a combination of basic processing. Moreover, the order may be changed. The main functions of the maintenance and operation function unit 330 are required to comply with regulations such as setting the PLOAM processing within 750 microseconds.

FIG. 15 is a diagram showing an example of a functional configuration of the PON multicast functional unit 350. The processes constituting the PON multicast function of the PON multicast function unit 350 include identification or distribution of multicast streams, MLD proxy / snooping, ONU filter setting, and inter-wavelength setting transition. These processes may consist of basic processes such as L2 identification / sorting, L3 packet processing (preferably provided with IPv6 Parse), L3 packet generation, table management, and communication with the OMCI function. Multicast stream identification or distribution, MLD proxy / snooping, ONU filter setting, and inter-wavelength setting transition may realize equivalent processing by a combination of basic processing. Moreover, the order may be changed.

In the main function of the PON multicast function unit 350, when the identification / distribution is processed for each wavelength of 10 Gbit / s / λ and 2.5 Gbit / s / λ, respectively, 10 Gbit / s / λ and 2.5 Gbit / s, respectively. If stream processing of / λ or more processes multiple wavelengths, multiple wavelengths are required. Further, in the main function of the PON multicast function unit 350, the zapping performance (JOIN latency) is required to comply with the provisions such as 1.5 seconds or less on average as packet processing.
As an example of function sharing, the identification and distribution of multicast (MC) streams can be processed by software if it is a CPU with high-speed processing capability, but hardware + composite is desirable. In addition, since the frequency and delay restrictions of the application system and ONU settings for uploading are loose, the processing is performed by the application.

FIG. 16 is a diagram showing an example of the functional configuration of the power saving control function unit 360. As a process constituting the function of the power saving control function unit 360, it has a sleep proxy / traffic monitor, an ONU wavelength setting, and an inter-wavelength setting transition. Even if these processes are composed of basic processes such as L3 packet processing (preferably provided with IPv6 Parse), L3 packet generation, table management, OSU power saving state diagram (SD: State Diagram), and communication with OMCI function. Good. For the sleep proxy / traffic monitor, ONU wavelength setting, and inter-wavelength setting transition, the same processing may be realized by a combination of basic processing. Moreover, the order may be changed.
This main function requires that the transmission / reception rise time (receiver / transmitter) be 10 ms / 5 ms and the rise time (LC / OSU / OLT) be 100 ms / 1 second / 10 seconds. Be done.

As an example of the division of functions, a power save (PS: Power Save) application or, depending on the signal, proxy processing can also be processed by the application. Power saving control State transition management (driver part) requires speed, but it can also be processed by the application. As for the traffic monitor, only the config (config) can be processed by the application.

FIG. 17 is a diagram showing an example of the functional configuration of the frequency / time synchronization function unit 370. The OLT subordinately synchronizes its real-time clock (RTC) to a higher-level device by using SyncE (Synchronous Ethernet®) (for frequency synchronization) and IEEE 1588v2 (time synchronization). Further, OMCI is used to notify the ONU of the correspondence between the PON super frame counter (SFC) and the absolute time (ToD: Time of Day) information. These processes may consist of holding a real-time clock, which is a basic process. Equivalent processing may be realized by a combination of basic processing. Moreover, the order may be changed.

In this main function, frequency synchronization accuracy +/- 50ppb (LTE FDD, TDD), time synchronization accuracy +/- 1 to 1.5 microseconds (LTE TDD, small cell), +/- 1 microseconds (G.I. It is required to comply with the provisions of 987.3) and the like. As an example of the division of functions, the real-time clock itself is a device-dependent part, and the time adjustment calculation to the host device can be processed by the application (it can also be a device-dependent part depending on the accuracy).

FIG. 18 includes redundant switching (CT, SW, NNI, CONT, PON (Type A, B, C)) as a process constituting the protection function of the protection function unit 380. These processes may be composed of basic processes such as redundant path setting, switching trigger detection, switching notification transmission / reception, and switching processing. Equivalent processing may be realized by a combination of basic processing. Moreover, the order may be changed.

In this main function, forced switching is required to comply with regulations such as 50 milliseconds or less. As an example of the division of functions, it is also possible to perform processing by the application except for hardware switching trigger detection and switching processing such as failure detection. If the EMS side is instructed (from) when the switching trigger is detected without setting the redundant path in advance, it depends on the device.

The eight main functions may be provided as needed. For example, only the PON main signal processing function, the PON access control function, the L2 main signal processing function, and the maintenance operation function may be provided, or other functions may be provided. You may. In addition, the evaluation of whether or not each function can be made into software is an example on the premise that the processing capacity of the OLT expected in 2018 and the application of the soft switch are not assumed. It may be changed as appropriate assuming the assumed processing capacity and application of the soft switch. The function may or may not be softened. The internal configuration of each function may be another configuration as long as the same function can be realized.

The main softening area is the algorithm included in the eight main functions. The function used as the software area is the device-independent application 130 on the device-independent API 21. For example, the algorithms in the ONU registration or authentication function, the DWBA function, the setting / management / monitoring control function, and the power saving control function that contribute to the differentiation service are treated as the extended function unit in the device-independent application 130. The MLD proxy app includes a multicast function.
The extended function unit is an extended function unit according to the importance of updating the function and realizing the original specifications in the application. Those with low update frequency or low demand for realization of original specifications are preferably middleware other than the basic function unit 132 and the device-independent application 130, device-dependent software, hardware unit, and hardware unit. In particular, it is preferable to leave the hardware portion and the hardware portion as the functions having restrictions due to the processing capacity of the software. For example, priority processing of main signals and functions such as DBA that improve line utilization efficiency or contribute to service differentiation, and management that is closely related to the operator's business flow and requires unique specifications for each operator. From the control function to the extended function part.

The information processing unit is not limited to these softening functions, and may have other softening functions. The hardware unit and the hardware unit are not limited to the transmission / reception unit, the OSU, the switch, the control unit, and the information processing unit. For example, the information processing unit may be included in the transmission / reception unit, the OSU, the switch, and the control unit. Further, as shown in FIG. 6, the NNI (Network-Network Interface) side of the switch may be provided with a proxy unit or an external server that processes signals input / output to / from the switch. The external server may be an information processing function called a so-called cloud such as a data center equipped with a plurality of devices.

Each function may be appropriately arranged according to the demand for processing capacity and processing delay. Further, the OSU may be provided with a switch unit 12 or a switch unit 13, or may be provided with a switch (switch unit 12 when the switch unit 13 is provided) separately from the switch. It is desirable that the functions of the switches are appropriately shared between the switch unit 12 and the switch unit 13 according to the processing capacity of the switch without overlapping, but they may overlap.

The place where the software function is deployed is not limited to the information processing unit, and may be placed in a place where a plurality of arithmetic operations can be performed. For example, the places where the software function is deployed are other than the transmission / reception unit, the OSU switch, the OSU switch, the OLT control unit, the OLT switch, the OLT information processing unit, the OLT switch, the control unit, and the information processing unit. It may be either a proxy unit that processes signals input / output to / from the switch on the NNI side of the switch, or a processing device such as an external server.

Further, the arrangement of the softening functions may be for each softening function, or may be a part of the softening functions obtained by dividing a single softening function. For example, the parts related to the transmission / reception unit are other than the transmission / reception unit, for example, the OSU switch, the OSU transmission / reception unit and other than the switch, the OLT switch, the OLT control unit, the OLT information processing unit, and the rest of the OLT. It may be deployed to somewhere such as a proxy unit, an external server, etc. on the main signal path outside the OLT, or to a combination of a plurality of deployment locations. Other than the PON termination processing deployment location, for example, the OSU transmitter / receiver, OSU switch, OSU transmitter / receiver and other than the switch, OLT switch, OLT control unit, OLT information processing unit , Other than OLT, it may be deployed to somewhere such as a proxy unit, an external server, etc. on the path of the main signal outside the OLT, or to a combination of a plurality of deployment locations.

Other than the ONU switch, such as the transmitter / receiver, the OSU transceiver and other than the switch, the OLT switch, the OLT control unit, the OLT information processing unit, the other OLT, the OLT. It may be deployed to somewhere such as a proxy unit, an external server, etc. on the main signal path outside of the above, or to a combination of a plurality of deployment locations. Other than the OLT switch, for example, the transmitter / receiver, the OSU switch, the OSU transceiver and other than the switch, the OLT control unit, the OLT information processing unit, the other OLT, the OLT. It may be deployed to somewhere such as a proxy unit, an external server, etc. on the main signal path outside of the above, or to a combination of a plurality of deployment locations.
In addition, the location where the software function is deployed may be appropriately changed according to the deployment status of the extension function unit, the computing capacity of the computing location, the computing load, the power consumption, and the like.

The main functions related to the main signal processing of the OLT and the relationships between the functions will be described. The OLT function is transferred to the switch. A PON main signal processing function that performs PON section processing such as a PHY adaptation function, a framing function, and a service adaptation function is provided in the transmission / reception unit. PON access control functions such as ONU registration or authentication function, DBA control function, and DWA function are provided in the information processing unit. The switch is provided with L2 main signal processing functions such as VLAN control used in framing, priority control in the pre-stage of shaper, max or demax (MuX / Dmax) and queue (Queue), and shaper in the pre-stage of framing.
Deploy the multicast function such as the copy function in the previous stage of the shaper and the MLD proxy used for copying to the switch. In this way, by deploying the PON main signal processing function and the PON access control function deployed in the PON to the switch, the PON basic function unit 132 is reduced. In particular, it is preferable to avoid duplication of the L2 main signal processing and deploy it in the switch.

It should be noted that the switch functions are illustrated on the premise that Classifier, Modifier, Policer / Shaper, CrossConnect, Queue, and Scheduler are provided in this order. However, it may be changed as appropriate. For example, in the uplink direction, if processing is not performed within the bandwidth allocation unit, the input from the ONU is PON by removing the preamble and burst overhead for burst transmission, decapsulating the frame, and removing the LLID. All the functions of Classifier, Modifier, Policer / Shiper, Cross Connect, Queue, and Scheduler may be performed by the switch, or only Modifier, Cross Connect, Queue, and Scheduler may be performed by the switch.
Further, if a VID or the like describing the path or the like after the PON termination is given by the ONU, Cross Connect, Queue, or Scheduler may be used. If the upper network can be regarded as a single path, Queue and Scheduler may be used. Further, if the DBA is performed so that the frames do not collide with the Cross Connect, the frame can be a Classifier, a Modifier, a Policer / Shaper, or a CrossConnect. Furthermore, if processing is not performed in the bandwidth allocation unit in the upstream direction, the input from the ONU is removed from the preamble and burst overhead for burst transmission, the frame is decapsulated, and the LLID is removed to PON. Is only terminated, and if a VID or the like describing the path or the like after the PON termination is given by the ONU, only the Cross Connect can be used.

Further, in Classifier, Modifier, Policer / Sharper, CrossConnect, Queue, and Scheduler, Classifer, Policer / Shaper, Modifier, CrossConnect, Queue, and Queue may be placed in front of the quer. It may be a Modifier, Queue, Policer / Sharper, CrossConnect, Scheduler, or it may be a Classifer, Queuee, Policeer / Queue, Modifier, CrossConnect, Scheduler. Considering the burst transmission of PON, unnecessary police / shipping due to burst property caused by multiplexing priority traffic such as multicast, and the reception of leveled traffic on the receiving side, the police / shaper It is desirable to execute the processing by Police / Shipping after placing a Queue in the previous stage and leveling it.

(Embodiment 1-2)
Although the configuration used for TWDM-PON is illustrated in the first embodiment, it may be applied to TDM-PON. The TDM-PON is the same as the embodiment 1-1 except that it does not have to have a function of wavelength division multiplexing of the wavelength resource of the PON section of the ONU-OLT between ONUs such as λ setting switching (DWA). Is.

(Embodiment 1-3)
Although the configuration used for TWDM-PON is illustrated in the first embodiment, it may be applied to WDM-PON. The embodiment 1-3 is the embodiment 1-1, except that the WDM-PON does not have to have a function of time-dividing and multiplexing the band resources of the PON section of the ONU-OLT between ONUs such as DBA. Is similar to.

(Embodiment 1-4)
The present embodiment is a combination including OFDM (Orthogonal Frequency Division Multiplex) -PON, CDM (Code Division Multiplex) -PON, SCM (Subcarrier Multiplex) -PON, and core wire division multiplexing.

Although the configuration used for TWDM-PON is illustrated in the first embodiment, it may be applied to a PON that shares resources other than wavelength and time. For example, it may be applied to OFDM-PON that divides and multiplexes the frequency resource of electricity of one wavelength, SCM-PON that divides and multiplexes the frequency resource of electricity of one wavelength, CDM-PON that divides and multiplexes by a code, or core wire division. Multiplexing may be used in combination, space division multiplexing using a multi-core fiber or the like may be used in combination, or wavelength division multiplexing may not be used. The same applies if the function of dividing and multiplexing the wavelength resources of the TWDM-PON by wavelength division multiplexing is read as a function corresponding to the function required for dividing and multiplexing each of the multiplexed resources.

(Embodiment 2)
In the second embodiment, the configuration used for TWDM-PON performs GEM encapsulation. In this case, the switch is provided with an adapter that generates a GEM frame so that the GEM frame is conducted between the switch and other parts. By transferring the GEM encapsulation to the switch, the L2 functional part can be excluded from the protocol stack of the other part, and the overlap of the L2 functional part can be avoided in the switch and the other part.

Although TWDM-PON is taken as an example, if the frame for identification in the PON section is handled in the same manner as in the first to second embodiments to the first to fourth embodiments, the same applies to other PONs. The effect of is obtained. For example, in the case of IEEE standard GE-PON, 10GE-PON, etc., instead of the GEM frame, an LLID may be added so that the frame to which the LLID is given conducts between the switch and other parts. Good.

(Embodiment 3)
In the third embodiment, the control information used for the TWDM-PON goes through the switch. In this case, instead of transferring the bridge function-related to the switch, any one of PLOAM, Embedded OAM, and OMCI that retains control information is framed as necessary and processed via the switch. By inputting and outputting control information via the switch, there is an effect that processing other than the switch becomes lighter. In addition to the transfer of the third embodiment, the transfer of the bridge function of the first and second embodiments may be performed.
Although TWDM-PON is taken as an example, if the control information is handled in the same manner and processed via the switch, the same applies to other PONs as in the first to second embodiments of the first to fourth embodiments. The effect is obtained.

At least a part of the communication device in the above-described embodiment may be realized by a computer. In that case, the program for realizing this function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read by the computer system and executed. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built in a computer system. Further, a "computer-readable recording medium" is a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line, and dynamically holds the program for a short period of time. It may also include a program that holds a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or a client in that case. Further, the above program may be for realizing a part of the above-mentioned functions, and may be further realized for realizing the above-mentioned functions in combination with a program already recorded in the computer system. It may be realized by using a programmable logic device such as FPGA (Field Programmable Gate Array).

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment. The above-described embodiment is merely an example, and the present invention can be implemented in a form in which various modifications and improvements have been made based on the knowledge of those skilled in the art, and includes a design within a range that does not deviate from the gist of the present invention. ..

11 ... Transmission / reception unit, 12, 13 ... Switch unit, 14 ... Control unit, 15 ... Proxy unit, 16 ... External server, 21, 22, 27 ... Device-independent API, 23, 24, 25 ... Device-dependent API

Claims (3)

As a component or communication device that constitutes a communication device, a holding unit that holds information regarding a specific state of the component or communication device that constitutes the communication device to be reassigned is provided.
The holding unit may be set as a home and may be a holding unit during operation, and any one of the holding units that holds information regarding the specific state during operation is set as a home. Then, the information about the specific state in operation at the home is held, and the information about the specific state during operation held by the holding unit set as the home is constantly or intermittently transmitted to other holding units. Notify
When the parts or communication devices constituting the communication device to be reassigned are reassigned to at least the reholding unit that is not subject to notification of information regarding the specific state, the holding unit during operation is subject to reassignment. A communication device that changes the notification destination so that the notification destination includes the holding part of the attribution change destination and notifies the notification. A notification method performed by a communication device having a holding unit for holding information on a specific state of the component or communication device to be reassigned as a component or communication device constituting the communication device.
The holding unit may be set as a home and may be a holding unit during operation, and any one of the holding units that holds information regarding the specific state during operation is set as a home. Then, the information about the specific state in operation at the home is held, and the information about the specific state during operation held by the holding unit set as the home is constantly or intermittently transmitted to other holding units. Notify
When the parts or communication devices constituting the communication device to be reassigned are reassigned to the reholding unit during operation, which is not subject to notification of at least the information regarding the specific state, at the time of reassignment. An information notification method that changes the notification destination so that the holding part of the reassignment destination is included in the notification destination. A computer program for causing a computer to function as each functional unit provided in the communication device according to claim 1.

Images